These accounts and corresponding passwords are well-known, and they should be changed, especially for a database to be used in a production environment as a best practice. Default schemas come from different sources and can be classified as below :
1. Default database administration schemas
2. Schemas belonging to optional database features neither used nor patched by E-Business Suite
3. Schemas belonging to optional database features used but not patched by E-Business Suite
4. Schemas belonging to optional database features used and patched by E-Business Suite
5. Schemas common to all E-Business Suite products
6. Schemas associated with specific E-Business Suite products
For the schemas in categories 1, 2 and 3, use standard database commands to change a password:
SQL> alter user [SCHEMA] identified by [NEW_PASSWORD];
For the schemas in categories 4, 5 and 6, use the application password change tool:
$ FNDCPASS APPS/apps_pwd 0 Y SYSTEM/system_pwd ORACLE [SCHEMA] [NEW_PWD]
To save time, category six (6) schema passwords may be changed en masse using FNDCPASS. FNDCPASS accepts a keyword ALLORACLE forcing a change of all managed schemas to the new password. If your version of FNDCPASS does not already support the ALLORACLE keyword, apply patch 5080487.
$ FNDCPASS APPS/apps_pwd 0 Y SYSTEM/system_pwd ALLORACLE [NEW_PWD]
To determine which schemas are managed by E-Business Suite (categories 4, 5 and 6), run the AD adutconf.sql script.
No comments:
Post a Comment