Invalid APPS Database User Credentials in txkPostPDBCreationTasks After PDB Creation in Oracle EBS 12.2

Introduction:

When performing a Post-PDB Creation Task in Oracle EBS 12.2, you may encounter the following error while running the txkPostPDBCreationTasks.pl script:

FUNCTION: main::validateAppsSchemaCredentials [ Level 1 ]
ERRORMSG: Invalid APPS database user credentials.

This issue typically happens when database authentication parameters are mismatched between the EBS application tier and the newly created Pluggable Database (PDB).

Root Cause

After creating or cloning a PDB for EBS 12.2, the APPS schema login from the application tier might fail due to:

  • Case-sensitive passwords enforced in the database while APPS password is stored in uppercase.
  • Listener mismatches preventing proper database connection.
  • Login version restrictions in sqlnet.ora blocking older JDBC connections.

Step-by-Step Solution

  1. Check and Reset Local Listener

If local_listener is set to a non-default value, it can cause application tier connection failures.

SQL> sho parameter local;

SQL> alter system set local_listener='' scope=both;

SQL> alter system register;

This ensures the database registers with the default listener.

  1. Disable Case-Sensitive Logon Temporarily

Some older APPS passwords are stored in uppercase. Disable case-sensitive authentication so the connection can succeed.

SQL> alter system set sec_case_sensitive_logon=FALSE scope=both;

Note: You should re-enable case sensitivity after confirming APPS connectivity.

  1. Allow Older Client Login Versions

If your sqlnet.ora is enforcing stricter login versions, EBS may fail to connect.

Edit $ORACLE_HOME/network/admin/sqlnet.ora and add:

SQLNET.ALLOWED_LOGON_VERSION_SERVER=10

Check if it’s applied:

cat $ORACLE_HOME/network/admin/sqlnet.ora | grep -i

ALLOWED_LOGON_VERSION_SERVER

  1. Re-Run the Post-PDB Creation Script

Once the above changes are done, re-run:

$ perl txkPostPDBCreationTasks.pl

It should now pass the APPS credentials check.

Best Practices

  • Always test APPS connectivity after PDB creation:

sqlplus apps/<password>@<TNS_ALIAS>

  • Maintain secure login settings and only relax them temporarily for troubleshooting.
  • Keep listener configuration simple unless custom routing is needed.

Conclusion:

These changes help resolve Invalid APPS database user credentials errors by ensuring the listener, authentication method, and SQL*Net parameters are in sync between EBS 12.2 and Oracle 19c PDB. Once fixed, revert relaxed security settings for compliance.

Recent Posts