AFPASSWD utility to change apps password R12.2.10

 R12.2.10: Steps to Change the APPS, APPLSYS, and APPS_NE Password Using FNDCPASS or AFPASSWD 

Whenever using FNDCPASS or AFPASSWD to change the APPS, APPLSYS, and APPS_NE password, one must also perform the following actions:

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 apps/****

###Change the APPLSYS password using.


###AFPASSWD:

AFPASSWD is an enhanced version of FNDCPASS, and includes the following features:

• AFPASSWD only prompts for passwords required for the current operation, allowing separation of duties between applications administrators and database administrators. This also improves interoperability with Oracle Database Vault. In contrast, the FNDCPASS utility currently requires specification of the APPS and the SYSTEM usernames and corresponding passwords, preventing separation of duties between applications administrators and database administrators.

• When changing a password with AFPASSWD, the user is prompted to enter the new password twice to confirm.

• In Oracle E-Business Suite Release 12.2.3 and higher, you can also use the AFPASSWD utility to migrate Oracle E-Business Suite user passwords to a password hashing scheme.

Syntax for using AFPASSWD:

# AFPASSWD [-c <APPSUSER>[@<TWO_TASK>]] -s <APPLSYS>

Syntax for using AFPASSWD:

AFPASSWD -c apps@PDB -s APPLSYS


NOTE: The steps 3 to 7 are mandatory 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.

In the next prepare phase after the password change, ADOP will invoke EBS Domain Configuration to ensure 

that the WLS datasource on the patch file system will be synchronized with the new APPS password.

 3. Run autoconfig with the newly changed password.

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

Do not start any other application tier services.

#####. Change the "apps" password in WLS Datasource as follows:

#stop all apps service

cd $ADMIN_SCRIPTS_HOME

./adstpall.sh apps/****

# start admin server.

cd $ADMIN_SCRIPTS_HOME

./adadminsrvctl.sh start

 Log in to WLS Administration Console.

http://host_name:7005/console   <Depend on your FILE_EDITION(RUN/PATCH) WLS port will change>

weblogic/*****

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. <<enter new apps password>>

g. Enter the new password in the "Confirm Password" field. <<re-enter new apps password>>

h. Click Save.

i. Click Activate Changes in Change Center.

Message icon - Success All changes have been activated. No restarts are necessary.

#Start all the application tier services using the below script

cd $ADMIN_SCRIPTS_HOME

./adstrtal.sh apps/****


 REFERENCES :

(Doc ID 1674462.1)

No comments:

SHRD0014: GLLEZL - process exiting with failure

  SYMPTOMS Journal Import completes with the following error: Error ------ ORA-01653 : unable to extend table GL.GL_IMPORT_REFERENCES ORA-01...