Skip to main content

Steps for Changing Apps Password in R12.2

Steps for Changing Apps Password in R12.2


In this post I am going to share steps to change apps password step by step in R12.2.

1. Stop Application Tier Services

$INST_TOP/admin/scripts/adstpall.sh

2. Changing APPS password from FNDCPASS

FNDCPASS apps/<old_apps_password> 0 Y system/<system_password> SYSTEM APPLSYS <new_apps_password>

Check the log file it should show the successful status.

3. Run autoconfig on both application nodes

1st in Node 2 (Slave Node) Cd $ADMIN_SCRIPTS_HOME Sh adautocfg.sh

2nd in Node 1 (Master Node) Cd $ADMIN_SCRIPTS_HOME Sh adautocfg.sh 

4. Starting AdminServer

$INST_TOP/admin/scripts/adadminsrvctl.sh start
** Do not start any other application tier services. 

5. Changing APPS password in WLS Data source

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.

h. Click Save.

i. Click Activate Changes in Change Center.

6. Starting Application Tier Services 

$INST_TOP/admin/scripts/adstrtal.sh

7. Verifying the WLS Data source Change

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". 

8.) If any third party integrations are present, Please update apps password in that as well.





If you like please follow and comment
Labels:

Comments

Post a Comment

Popular posts from this blog

WebLogic migration to OCI using WDT tool

WebLogic migration to OCI using WDT tool Oracle WebLogic Deploy Tool (WDT) is an open-source project designed to simplify and streamline the management of Oracle WebLogic Server domains. With WDT, you can export configuration and application files from one WebLogic Server domain and import them into another, making it a highly effective tool for tasks like migrating on-premises WebLogic configurations to Oracle Cloud. This blog outlines a detailed step-by-step process for using WDT to migrate WebLogic resources and configurations. Supported WLS versions Why Use WDT for Migration? When moving Oracle WebLogic resources from an on-premises environment to Oracle Cloud (or another WebLogic Server), WDT provides an efficient and reliable approach to: Discover and export domain configurations and application binaries. Create reusable models and archives for deployment in a target domain. Key Pre-Requisites Source System: An Oracle WebLogic Server with pre-configured resources such as: Applica...
Post a Comment
Read more

Rename a PDB in Oracle Database Multitenant Architecture in TDE and Non TDE Environment

Rename a PDB in Oracle Database Multitenant Architecture I am sharing a step-by-step guide to help you rename a PDB. This approach uses SQL commands. Without TDE or encryption Wallet Initial Check Check the Current Database Name and Open Mode: SQL > SELECT NAME, OPEN_MODE FROM V$DATABASE; NAME OPEN_MODE --------- -------------------- BEECDB READ WRITE List Current PDBs: SQL > SHOW PDBS; CON_ID CON_NAME OPEN MODE RESTRICTED ---------- ------------------------------ ---------- ---------- 2 PDB$SEED READ ONLY NO 3 FUAT READ WRITE NO We need to RENAME FUAT to BEE  Steps to Rename the PDB Step 1: Export ORACLE_SID Set the Oracle SID to the Container Database (CDB): export ORACLE_SID=BEECDB Step 2: Verify Target PDB Name Availability If the target PDB name is different from the current PDB name, ensure no service exists with the target PDB name. Run SQL to Check Exi...
Post a Comment
Read more

How to make flash work on IE or Edge with IE Compatibility

How to make flash work on IE or Edge with IE Compatibility With flash been ended from 1-Jan-2021, many applications using flash have stopped working the way they were built (like OEM, OBIEE, etc). The option you have to upgrade.  This method will give a workaround in IE or Edge in IE compatibility mode without upgrading. 1. Verify you have installed flash.ocx on your desktop. Typically, flash.ocx file is located in C:\Windows\System32\Macromed\Flash or C:\Windows\SysWOW64\Macromed\Flash according to your laptop OS system. 2. Edit mms.cfg from the location as a System Administrator In the case of the 64bit system, it might have mms.cfg under C:\Windows\SysWOW64\Macromed\Flash 3. Add below options into mms.cfg file. Note: AllowListUrlPattern list is an example. The URLs need to be replaced to your hosts those have Flash pages. SilentAutoUpdateEnable=0 AutoUpdateDisable=1 EOLUninstallDisable=1 EnableAllowList=1 AllowListUrlPattern=http://www.google.com/ AllowListUrlPattern=http://goo...
Post a Comment
Read more