The ifsapp-amm pod's startup probe keeps failing with 'Unable to connect to database,' even though the ifsmon-password and ifsapp-user passwords used to connect have both been double-checked and look correct.

All FAQ questions / Developer Studio, deployment, and upgrades

Answer

Check whether the underlying Oracle account is locked, not just whether the password is correct — a correct password on a locked Oracle account (in this case the ifsmonitoring account that ifsapp-amm connects with) produces the same kind of connection failure as a wrong password, so verifying the password alone isn't enough; also confirm the account's lock status in the database and unlock it if needed.

Documentation-based answer. Confirm the product and release before applying it. This answer has not been verified in an IFS environment.

← Browse Developer Studio, deployment, and upgrades questions