Important: These steps must be carried out on the run file system. The FND_USER and FND_ORACLE_USERID tables should be backed up before any passwords are changed. Remove the backups after you have confirmed that the changes are successfully completed. Passwords for all the 3 schemas, APPS, APPLSYS and APPS_NE will be changed together while changing APPLSYS password.
1. Shut down the application tier services using the below script:
$INST_TOP/admin/scripts/adstpall.sh
2. Change the APPLSYS password using
 
There are 2 ways to change the APPLSYS password:
 
A. FNDCPASS:
 
[applmgr@erpapp01 ~]$ FNDCPASS apps/apps 0 Y system/manager SYSTEM APPLSYS apps_pwd
Log filename : L7909719.log
 
Report filename : O7909719.out
[applmgr@erpapp01 ~]$ cat L7909719.log
+---------------------------------------------------------------------------+
Application Object Library: Version : 12.2
Copyright (c) 1998, 2013, Oracle and/or its affiliates. All rights reserved.
FNDCPASS:
+---------------------------------------------------------------------------+
Current system time is 27-AUG-2017 15:46:25
+---------------------------------------------------------------------------+
Working...
FNDCPASS completed successfully.
+---------------------------------------------------------------------------+
Concurrent request completed successfully
Current system time is 27-AUG-2017 15:46:30
+---------------------------------------------------------------------------+
B. AFPASSWD:
 
AFPASSWD is an enhanced version of FNDCPASS, and includes the following features:
 
 
 
Syntax for using AFPASSWD:
AFPASSWD [-c [@]] -s
 
[applmgr@erpapp01 ~]$ AFPASSWD -c apps@ERPUPG -s APPLSYS
Enter the ORACLE password of Application Object Library 'APPSUSER':
Connected successfully to APPS.
Enter the password for your 'SYSTEM' ORACLE schema:
Connected successfully to SYSTEM.
Log file: AFPWD_ERPUPG_943215.log
Enter new password for user:
Verify new password for user:
AFPASSWD completed successfully.
 
NOTE: The steps 3 to 7 are mandatory for both FNDCPASS and AFPASSWD and are only applicable when changing the APPLSYS password. They are not applicable when changing passwords for product schemas like PO, GL etc or the SYSTEM schema.
3. Run autoconfig on the application tier with the newly changed APPS password.
4. Start AdminServer. Do not start any other application tier services.
 
[applmgr@erpapp01 ~]$ adadminsrvctl.sh start
You are running adadminsrvctl.sh version 120.10.12020000.10
Enter the WebLogic Admin password:
Enter the APPS Schema password:
Starting WLS Admin Server...
Refer /u02/oracle/ERPUPG/fs1/inst/apps/ERPUPG_ERPUPGapp-01/logs/appl/admin/log/adadminsrvctl.txt for details
AdminServer logs are located at /u02/oracle/ERPUPG/fs1/FMW_Home/user_projects/domains/EBS_domain_ERPUPG/servers/AdminServer/logs
adadminsrvctl.sh: exiting with status 0
adadminsrvctl.sh: check the logfile /u02/oracle/ERPUPG/fs1/inst/apps/ERPUPG_ERPUPGapp-01/logs/appl/admin/log/adadminsrvctl.txt for more information ...
 
[applmgr@erpapp01 ~]$ adadminsrvctl.sh status
You are running adadminsrvctl.sh version 120.10.12020000.10
Enter the WebLogic Admin password:
Enter the APPS Schema password:
The AdminServer is running
AdminServer logs are located at /u02/oracle/ERPUPG/fs1/FMW_Home/user_projects/domains/EBS_domain_ERPUPG/servers/AdminServer/logs
adadminsrvctl.sh: exiting with status 0
adadminsrvctl.sh: check the logfile /u02/oracle/ERPUPG/fs1/inst/apps/ERPUPG_ERPUPGapp-01/logs/appl/admin/log/adadminsrvctl.txt for more information ...
5. Change the “apps” password in WLS Datasource as follows:
 
a. Log in to WLS Administration Console.
 
b. Click Lock & Edit in Change Center.
 
 
c. In the Domain Structure tree, expand Services, then select Data Sources.
 
d. On the "Summary of JDBC Data Sources" page, select EBSDataSource.
 
e. On the "Settings for EBSDataSource" page, select the Connection Pool tab.
 
f. Enter the new password in the “Password” field.
 
g. Enter the new password in the “Confirm Password” field.
 
i. Click Activate Changes in Change Center.
6. Start all the application tier services using the below script:
 
$INST_TOP/admin/scripts/adstrtal.sh
7. Verify the WLS Datasource changes as follows:
 
a. Log in to WLS Administration Console.
 
b. In the Domain Structure tree, expand Services, then select Data Sources.
 
c. On the "Summary of JDBC Data Sources" page, select EBSDataSource.
 
d. On the "Settings for EBSDataSource" page, select Monitoring > Testing.
 
e. Select "oacore_server1".
 
f. Click Test DataSource
 
g. Look for the message “Test of EBSDataSource on server oacore_server1 was successful”.