Changing APPS or APPLSYS Password on R12.2 Instance

The below are steps to change the Apps password in R12.2:

1. Normally working instance.

1

Now lets change APPLSYS password

Important: These steps must be carried out on the run file system.

1. Shut down the application tier services using the

$INST_TOP/admin/scripts/adstpall.sh

2

2. Change the APPLSYS password.

FNDCPASS apps/<existing apps passwd>  0 Y system/<system password> SYSTEM APPLSYS <new apps passwd>

3

FNDCPASS apps/apps 0 Y system/manager SYSTEM APPLSYS testpwd

3. Start AdminServer using the $INST_TOP/admin/scripts/adadminsrvctl.sh

script. Do not start any other application tier services.

4

4. Change the “apps” password in WLS Datasource as follows:

  • Log in to WLS Administration Console.

http:/r122.localdomain:7002/console

5

  • Click Lock & Edit in Change Center.
  • 6
  • In the Domain Structure tree, expand Services, then select Data Sources.
  • 7
  • On the “Summary of JDBC Data Sources” page, select EBSDataSource
  • On the “Settings for EBSDataSource” page, select the Connection Pool tab.
  • 8
  • Enter the new password in the “Password” field.
  • Enter the new password in the “Confirm Password” field.
  • Click Save.
  • 9
  • Click Activate Changes in Change Center.
  • 10

Check whether you are able to connect to db using apps

sqlplus apps/<newpassword> from application tier.

Before Starting all the services. Run Autoconfig.

cd $ADMIN_SCRIPTS_HOME

sh adautocfg.sh

Now start the services.

  • Start all the application tier services using the
  • $INST_TOP/admin/scripts/adstrtal.sh script.

11

6. Verify the WLS Datastore changes as follows:

  • Log in to WLS Administration Console.
  • In the Domain Structure tree, expand Services, then select Data Sources.
  • On the “Summary of JDBC Data Sources” page, select EBSDataSource.
  • On the “Settings for EBSDataSource” page, select Monitoring > Testing.
  • Select “oacore_server1″.
  • Click Test DataSource
  • Look for the message “Test of EBSDataSource on server oacore_server1 was successful”.
  • 12