APP-FND-01496 Results From FNDCPASS Chaning The APPLSYS password

APP-FND-01496 Results From FNDCPASS Chaning The APPLSYS password

AFTER manually using the ‘alter user’ in sqlplus the following error occurs in the log for every application user account:

ERROR
APP-FND-01496: Cannot access application ORACLE password
Cause: Application Object Library was unable access your ORACLE password.

The APPLSYS (APPS) password became corrupted using ALTER USER because an applications session was not maintained at the same time. This apps session is necessary to change the APPLSYS password in:
‘Security> Oracle> Register’ WHILE being in SQL*PLUS as the SYSTEM user.

The supported method is use of FNDCPASS.

To implement the solution, please execute the following steps:

1. Restore the FND_ORACLE_USERID and FND_USER tables from a backup.

2. Then run FNDCPASS to change the APPLSYS password. Ex.

FNDCPASS apps/ 0 Y system/ SYSTEM APPLSYS WELCOME

FNDCPASS Fails With ORA-01005 Using Underscore or Dollar Sign in Passwords?

FNDCPASS Fails With ORA-01005 Using Underscore or Dollar Sign in Passwords?

To implement the solution, please execute the following steps:

Using the Underscore ( _ ) or Dollar Sign ( $ ) as well as Parentheses ( ) and Comma ( , ) will cause the following error to be generated:

Routine AFPCSQ encountered an ORACLE error. ORA-01005: null password given; logon denied
Review your error messages for the cause of the error. (=)

Only alphanumeric characters should be for passwords. Bug 523929 – UNABLE USE THE PUNCTUATION MARK IN FNDCPASS UTILITY has been logged to address using special characters such as the _, #, and $.

FNDCPASS Gives: APP-FND-01502: Cannot Encrypt Application ORACLE Password

FNDCPASS Gives: APP-FND-01502: Cannot Encrypt Application ORACLE Password

APP-FND-01502: Cannot encrypt application ORACLE password
Application Object Library was unable encrypt your ORACLE password.
Action: Contact your support representative. (ORACLEUSER=APPS_SERV)

The table fnd_oracle_userid contain rows for schemas that does not exist. Those rows must be deleted
from the table.

To implement the solution, please execute the following steps:

1. Execute the following select statement:

select * from fnd_oracle_userid
where oracle_username not in
(select username from all_users);

If this returns any rows, then delete them.

APP-FND-01496 Received When Changing The APPLSYS Password With FNDCPASS

APP-FND-01496: Cannot access application ORACLE password
Cause: Application Object Library was unable access your ORACLE password.

The ALTER command was run manually against the APPS user before running FNDCPASS. The APPS and APPLSYS user passwords must be identical.

To implement the solution, execute the following steps:

1. Run the ALTER command against the APPS and APPLSYS users in sqlplus to change back to the old passwords:

sql>ALTER USER APPLSYS IDENTIFIED BY XXX;
sql>ALTER USER APPS IDENTIFIED BY XXX;

2. Afterwards run FNDCPASS:

FNDCPASS apps/ 0 Y system/ SYSTEM APPLSYS
Ex: $FNDCPASS apps/ 0 Y system/ SYSTEM APPLSYS NEWPASSWORD

Note: Changing the APPLSYS password automatically changes the APPS password to match as these two must always agree.

FNDCPASS Not Able To Decrypt Password For APPLSYSPUB When Changing The APPS Password

The APPS password appears to have been successfully updated and Autoconfig runs without issue.
However, Discoverer users have authentication problems.

The issue is caused by a data corruption issue in the fnd_user table.

To implement the solution, execute the following steps:

1. Use FNDCPASS to reset the APPLSYSPUB password.

e.g. FNDCPASS apps/ 0 Y system/ ORACLE APPLSYSPUB PUB

2. Retest for the issue.

Log In Fails With: You Don’t Have Permission To Access /pls/…/fnd_icx_launch.launch On This Server

Log In Fails With: You Don’t Have Permission To Access /pls/…/fnd_icx_launch.launch On This Server

The apps account is locked from repeatedly running FNDCPASS or logging into sqlplus as apps using the wrong password.

To implement the solution, execute the following steps:

1. Log-in as system owner and run:

SQL> alter profile DEFAULT limit failed_login_attempts unlimited;
SQL> alter user apps account unlock;

The first line (optional) results in preventing repeated failed log in attempts from locking the account.
The second line (required) simply unlocks the apps account.

2. Restart the services.