1. Download and install the Password changing utility available from patch 1685689 or later if not already included in your version of Applications.
NOTE 1: FNDCPASS should be run from the database tier to prevent encryption issues.
2. Issue the commands at the Unix command line similar to the following:
To change the APPS and APPLSYS passwords:
FNDCPASS apps/apps 0 Y system/manager SYSTEM APPLSYS
Ex: $FNDCPASS apps/apps 0 Y system/manager SYSTEM APPLSYS NEWPASSWORD
NOTE 2: Changing the APPLSYS password automatically changes the APPS password
to match as these two must always agree.
To change an Oracle user password:
FNDCPASS apps/apps 0 Y system/manager ORACLE
Ex: FNDCPASS apps/apps 0 Y system/manager ORACLE GL GLPASSWORD
NOTE 3: Altering the ORACLE User name (schemas) passwords with FNDCPASS without first updating the APPS/APPLSYS password with FNDCPASS will cause the ORACLE User password to be undecodable by Applications.
Use FNDCPASS to “refresh” the APPS/APPLSYS password, even if it is to the same value.
To change an application user password:
FNDCPASS apps/apps 0 Y system/manager USER
Ex: FNDCPASS apps/apps 0 Y system/manager USER VISION WELCOME
NOTE 4: VERY IMPORTANT!!
When changing the password for APPS it is important to manually change the APPS password in the following files as well as necessary:
1. $ORACLE_HOME/listener/cfg/wdbsvr.app file as well. (Otherwise users will not be able to login to the Personal Home Page or Self-service web apps.) This may also be necessary in the $IAS_ORACLE_HOME/Apache/modplsql/cfg/wdbsvr.app file
2. Workflow Notification Mailer – $FND_TOP/resource/wfmail.cfg
3. The concurrent manager start script.
5. $AD_TOP/admin/template/CGIcmd.dat may contain the password if it is being used.
(Please refer to Note 159033.1 How to Setup Oracle Reports in Portal to Use CGICMD.DAT File)
6. If you instance is Multi-node and Autoconfig enabled, it may be necessary to invoke Autoconfig to implement the above changes.
Before using FNDCPASS and changing the passwords from default to some thing else, always follow the following best practices.
7. Keep the back of tables FND_USER and FND_ORACLE_USERID. You can take back of these tables using CREATE TABLE — AS SELECT * FROM —. You must have backup of these tables before running FNDCPASS. In case if FNDCPASS fails then it might corrupt the passwords of your application and worst can happen that the application wont come up. So always be cautions about this command.
8. If possible also keep an export dump of these two tables, FND_USER and FND_ORACLE_USERID.
9. Verify each argument you are providing to FNDCPASS. Like verify that apps and system passwords you are providing is correct.
10. Never update apps, applsys or any schema password directly from database using the alter command. Always use FNDCPASS. System password can be set directly using ALTER command in database.
11. Try to check for any customized hardcoded package or procedure in database by running the query below.
SQL> select name,text from all_source
where text like ‘%conn%apps%’
Reference: Metalink Note 159244.1
Next» Oracle Diagnostics Link