Oracle E-Business Suite R12.2: Step-by-Step Guide to Change APPS Password Using FNDCPASS

This blog explains the complete procedure to change the APPS/APPLSYS password in Oracle E-Business Suite R12.2 using FNDCPASS and update the WebLogic Data Sources accordingly. The guide is useful for Oracle Apps DBAs and middleware administrators managing Oracle EBS environments.

Overview

In Oracle E-Business Suite R12.2, changing the APPS password requires careful synchronization between the database tier and the WebLogic application tier. If the WebLogic datasource passwords are not updated properly, EBS services may fail to start or users may encounter login issues.

Reference Document

Reference: R12.2: Steps to Change the APPS, APPLSYS, and APPS_NE Password Using FNDCPASS or AFPASSWD (Doc ID 1674462.1)

Prerequisites

• Ensure full EBS backup exists before starting.
• Ensure all application tier services are stopped.
• Keep WebLogic admin password available.
• Know the existing APPS password.
• Validate database connectivity before proceeding.
• Source the correct EBS environment file.

Step 1: Source Environment File and Change APPS Password

Open a new terminal session or source the EBS environment file before running FNDCPASS.

FNDCPASS apps/<existing_pwd> 0 Y system/oracle SYSTEM APPLSYS <new_apps_pw>

Explanation of the command:
– apps/<existing_pwd> : Existing APPS schema password
– system/oracle : SYSTEM user credentials
– APPLSYS : Target schema
– <new_apps_pw> : New APPS password

This utility updates the APPS/APPLSYS password throughout the EBS system.

Step 2: Run AutoConfig

After changing the password, run AutoConfig first on the database tier and then on the application tier.

# Run on Database Tier
adautocfg.sh

# Run on Application Tier
adautocfg.sh

AutoConfig synchronizes configuration files and updates context-specific parameters.

Step 3: Start WebLogic Admin Server

[appltest1@erpdev01 scripts]$ adadminsrvctl.sh start

Enter the WebLogic Admin password:
Enter the APPS Schema password:

Starting WLS Admin Server…

Useful log file locations:

Admin Script Log:
/u01/appl8030/fs1/inst/apps/ORA8030_erpdev01/logs/appl/admin/log/adadminsrvctl.txt

AdminServer Logs:
/u01/appl8030/fs1/FMW_Home/user_projects/domains/EBS_domain/servers/AdminServer/logs

Access the WebLogic Console using:

http://<hostname.domain_name>:7001

Username: weblogic
Password: <password>

Step 4: Start Only AdminServer

Do not start other EBS application tier services yet. Only the WebLogic AdminServer should be running at this stage.

$INST_TOP/admin/scripts/adadminsrvctl.sh start

Step 5: Update EBSDataSource Password in WebLogic

1. Login to WebLogic Administration Console.
2. Click ‘Lock & Edit’ in Change Center.
3. Expand Services → Data Sources.
4. Select EBSDataSource.
5. Open the Connection Pool tab.
6. Enter the new APPS password.
7. Confirm the password.
8. Click Save.
9. Click Activate Changes.

This step is critical because WebLogic uses EBSDataSource to connect to the Oracle database.

Step 6: Start All Application Tier Services

$INST_TOP/admin/scripts/adstrtal.sh

This script starts all Oracle E-Business Suite services including oacore, forms, oafm, Apache, concurrent managers, and managed servers.

Step 7: Verify WebLogic DataSource Connectivity

10. Login to WebLogic Administration Console.
11. Navigate to Services → Data Sources.
12. Select EBSDataSource.
13. Go to Monitoring → Testing.
14. Select oacore_server1.
15. Click Test DataSource.

Expected Successful Message:
“Test of EBSDataSource on server oacore_server1 was successful”

Step 8: Update OAEADataSource for ISG

If Integrated SOA Gateway (ISG) is implemented, repeat the same datasource password update process for OAEADataSource.

Verify that all oafm_cluster managed servers start successfully.

Common Issues and Troubleshooting

• Managed servers fail to start due to incorrect datasource passwords.
• oacore services remain in failed state.
• Database connection refused due to stale credentials.
• AutoConfig not executed after password change.
• WebLogic AdminServer inaccessible due to service issues.

Best Practices

• Always take backups before password changes.
• Perform changes during maintenance windows.
• Validate all services after startup.
• Update password vault/documentation securely.
• Monitor AdminServer and oacore logs after restart.

Conclusion

Changing the APPS password in Oracle EBS R12.2 involves updates at both the database and middleware layers. Proper synchronization using AutoConfig and WebLogic datasource updates ensures a successful password rotation without service disruption.