Steps to change password for APPS in EBS R12.2

Today, we will delve into the process of changing the EBS APPS password in Oracle E-Business Suite R12.2. While this is a routine and fundamental task for every appsdba, it is essential to perform the steps cautiously to avoid any potential risks or unforeseen complications.

What is the Apps Schema?

The Apps schema refers to a schema that does not contain any tables of its own. It serves as the shared runtime schema for all E-Business Suite products. It includes synonyms for all tables in Oracle apps and also consists of packages, functions, and procedures. The default password for this schema is “apps.”

What is the Applsys Schema?

The Applsys schema comprises all the necessary tables for administrative purposes. The default password for this schema is also “apps.” It consolidates the database objects of various technical products into a single schema called Applsys.

What is the Applsyspub Schema?

The Applsyspub schema primarily handles password checking. Its default password is “pub.” Applsyspub is utilized for authentication through read-only views.

Why should the Apps and Applsys passwords always be the same?

The requirement for having the same password for both the Apps and Applsys schemas is due to the authentication process. When signing on to Apps, it initially connects to a public schema named APPLSYSPUB. This schema validates the AOL username and password entered, typically using the guest user account (operations/welcome). Once this authentication is confirmed, selecting a responsibility triggers validation by the APPLSYS schema, followed by the connection to the APPS schema.

Step 7: Modifying the Password in WebLogic

A) If your EBS R12.2 AD TXK Delta is 7 or higher, you should follow the subsequent steps.

[applmgr@ebslive scripts] $perl $FND_TOP/patch/115/bin/txkManageDBConnectionPool.pl
Please select from list of valid options
        updateDSPassword - Update WebLogic Datasource Password
        updateDSJdbcUrl  - Update WebLogic Datasource Connection String
Enter Your Choice : updateDSPassword
Enter the full path of Applications Context File [DEFAULT -]:
Enter weblogic admin server password: <enter Weblogic Password>
Enter the APPS user password: <enter New APPS Password>

B) If your EBS R12.2 AD TXK Delta is lower than 7, you should utilize the following steps.

1. Access the WebLogic console through a web browser.
2. Click on the “Lock and Edit” button.
3. Navigate to the “Domain structure” section and select “Services” -> “Data Sources.”
4. Locate and select the “EBSDataSource” entry.
5. In the “Settings of EBSDataSource” page, go to the connection pool section.
6. Enter the updated password for the apps user and save the changes.
7. Finally, click on “Activate changes” to apply the modifications.

Step 8 . Start the application services.

[applmgr@ebslive appl]$ pwd

  /u01/app/PROD/fs2/EBSapps/appl

[applmgr@ebslive appl]$ adstrtal.sh

 You are running adstrtal.sh version 120.24.12020000.6

 Enter the APPS username: apps 

 Enter the APPS password:

 Enter the WebLogic Server password:

 All enabled services for this node are started.

 adstrtal.sh: Exiting with status 0

Step 9: Validate WLS Datastore Modifications by Following These Steps

1. Access the WLS Administration Console and log in.
2. In the Domain Structure tree, expand the “Services” section, then choose “Data Sources.”
3. Locate and select “EBSDataSource” on the “Summary of JDBC Data Sources” page.
4. Navigate to the “Settings for EBSDataSource” page and select “Monitoring” followed by “Testing.”
5. Select “oacore_server1” from the available options.
6. Click on “Test DataSource.”
7. Look for the confirmation message stating “Test of EBSDataSource on server oacore_server1 was successful.”
8. If Integrated SOA Gateway (ISG) is implemented, repeat the steps for “OAEADataSource”. Verify “oafm_cluster*” managed servers are started successfully.

Special Characters in APPS Password using FNDCPASS

Today, we will discuss the use of special characters in Oracle E-Business Suite (EBS) APPS passwords and the implications of using the FNDCPASS utility for password changes.

Using special characters in passwords, particularly for database users like APPS, APPLSYS, and GL, is not supported when utilizing the FNDCPASS utility.

If you attempt to include a special character in a database user’s password using FNDCPASS, you are likely to encounter one of the following errors:

1. Cause: change password failed due to ORA-01403: no data found.
2. Syntax error: unexpected end of file.
3. Syntax error near unexpected token `newline’.
4. APP-FND-02704: Unable to alter user APPS to change password.
5. APP-FND-01564: ORACLE error 1017 in AFPCOA.
6. FNDCPASS was unable to decrypt the password for user ‘APPS’ during applsys password change.
7. Passwords must be at least 5 characters long. (This error may occur even when the password is longer than 5 characters.)
8. It may not be possible to access the schema or change the password if the stored value is unknown.
9. The specific error encountered depends on factors such as the database user being modified, the special character being used, and the position of the special character in the password (e.g., first or second character).

However, it is possible to use FNDCPASS to change the password of certain EBS users, such as SYSADMIN, and include special characters from a provided list. It is important to note that there may be specific considerations or restrictions for certain characters, which can be found in a table given below. In some cases, enclosing the new password in quotation marks may be necessary.

In summary, while the use of special characters in EBS passwords with FNDCPASS is generally unsupported, there are exceptions for certain users. It is essential to follow Oracle’s guidelines and restrictions for password management in EBS.

Note:

Please take note of the following details:

• An important deviation from the standardization of mixed case passwords is observed with the APPLSYSPUB account. Its password continues to remain in uppercase.
• Currently, Oracle E-Business Suite does not support passwords containing special characters or multibyte characters.

Reference Document : R12: How to change passwords to include special characters using FNDCPASS? (Doc ID 1336479.1)

[edsanimate_start entry_animation_type= “fadeIn” entry_delay= “0” entry_duration= “1” entry_timing= “linear” exit_animation_type= “” exit_delay= “” exit_duration= “” exit_timing= “” animation_repeat= “infinite” keep= “yes” animate_on= “load” scroll_offset= “” custom_css_class= “”]OUTPUT POST PROCESSOR (OPP) LOG CONTAINS ERROR “JAVA.LANG.OUTOFMEMORYERROR”[edsanimate_end]

(more…)

  Today We are going to Explore how to Ddd Managed Server on Oracle E-Business Suite R12.2. By default, every application tier node contains only a single instance of the OACORE, OAFM, FORMS and FORMS-C4WS Services.

To increase the Web logic performance, we need to add up managed servers. For example, we are going to add an OACORE Managed Server.

Step 1:  Execute the following command to add a new managed server.

$ perl $AD_TOP/patch/115/bin/adProvisionEBS.pl

ebs-create-managedserver -contextfile=

-managedsrvname= -servicetype=

-managedsrvport= -logfile=

Step 2: Source the Run File System.

Step 3: Now, perform the following steps on all application tier nodes participating in the same cluster where this managed server is added

Execute the following command to add details of the newly added managed servers into the OHS configuration files mod_wl_ohs.conf and apps.conf on the current node:

$ perl $FND_TOP/patch/115/bin/txkSetAppsConf.pl

-contextfile= <context_file>

-configoption=addMS

-oacore=<host>.<domain>:port

-oafm=<host>.<domain>:port

-forms=<host>.<domain>:port

-formsc4ws=<host>.<domain>:port

For example, if the managed server oacore_server2 has been added on host ‘ebsapps‘ and domain ‘prod.com‘ with port 7207, the following command should be executed: 

$ perl $FND_TOP/patch/115/bin/txkSetAppsConf.pl -contextfile=$CONTEXT_FILE

-configoption=addMS -oacore=ebsapps.prod.com:7207

Step – 4:  Run Context File Synchronization

perl $AD_TOP/bin/adSyncContext.pl contextfile=$CONTEXT_FILE

Step 5:  Starting the Newly Added Managed Server

On Unix:
$ sh ./admanagedsrvctl.sh start <managedserver_name>

Example:

$ sh ./admanagedsrvctl.sh start oacore_server2

Step 6:    Bounce apache(adapcctl.sh stopall/startall)

sh<ADMIN_SCRIPTS_HOME>/adapcctl.sh stopall

sh<ADMIN_SCRIPTS_HOME>/adapcctl.sh startall