Changing Passwords in 12.2


The AFPASSWD command is used with the relevant command line options to perform the desired action.

AFPASSWD [-c [@]] -f

AFPASSWD [-c [@]] -o

AFPASSWD [-c [@]] -a



AFPASSWD [-c [@]] -s

AFPASSWD [-c [@]] -h
These options have the following functions:

-c [@] – Specifies the connection string to use, the Oracle E-Business Suite user, and/or the value of TWO_TASK. This option can be use in combination with others. If it is not specified, default values from the environment will be used.

Note: The password will be prompted for, and should not be provided in the connection string.

-f – Changes the password for an Oracle E-Business Suite user. Specify the user name. A user name that contains spaces or special characters must be enclosed in double quotation marks; for example, “JOHN SMITH” or “JOHN.DOE@EXAMPLE.COM”..

-o – Changes the password for an Oracle E-Business Suite database user. Specify the user name.

Note: This only applies to users listed in the FND_ORACLE_USERID table, not database users in general.

-a – Changes all Oracle passwords for schemas that are registered as base product schemas in the FND_ORACLE_USERID table (excluding the passwords of APPS, APPLSYS, and APPS_NE) to the same password, in the same way as the ALLORACLE mode does in FNDCPASS.

-l – Locks or unlocks an individual Oracle E-Business Suite database user (ORACLE_USER) (except required schemas). Specify TRUE to lock or FALSE to unlock.

-L – Locks or unlocks all Oracle E-Business Suite database users (except required schemas). Specify TRUE to lock or FALSE to unlock.

-s – Changes the password for the APPLSYS user, the APPS user, and the APPS_NE user. This requires the execution of AutoConfig on all tiers. After changing the APPLSYS password, you must also perform the steps listed in Important Additional Instructions to Update WLS Datasource.

-h – Displays help.

Important Additional Instructions to Update WLS Datasource

Whenever you use FNDCPASS or AFPASSWD in SYSTEM mode to change the APPS or APPLSYS schema passwords, you must also perform the actions listed below.

Note: Using SYSTEM mode with either APPLSYS or APPS will simultaneously update both the APPLSYS and APPS schemas: the respective passwords are kept in sync by both FNDCPASS and AFPASSWD.

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

Shut down the application tier services using the $INST_TOP/admin/scripts/ script.

Change the APPLSYS password, as described for the utility you are using.

Start AdminServer using the $INST_TOP/admin/scripts/ script. Do not start any other application tier services.

Change the APPS password in WLS Data Source by running the the following script as shown:

  1. $ perl $FND_TOP/patch/115/bin/

    When prompted, select ‘updateDSPassword’ to change the APPS password in the WLS Datasource.

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

Verify the WLS Datasource 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”.

Important: Steps 4, 5 and 6 are only applicable when changing the APPLSYS password. They are not applicable when changing passwords for product schemas 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.

R12.2, Service Manager Will Not Start

Recently, I was working with a client when the managers in their 12.2 environment quit working. We had shutdown the applications tier to reboot the server, and when it came back up, only the Internal Manager (ICM) would run. After working through all the usual steps, relinking, autoconfig, cmclean, answering the same questions from Oracle repeatedly, etc., we still could not get the managers to start. The Administer Concurrent Managers form showed the Internal Manager running with a matching target (1), and the Service Manager running with a target of 0. This was the state every time we started the managers even after rebooting both the database and applications servers. To make things even stranger, if you viewed the processes under the Service Manager from the Administer Concurrent Managers form, all the processes were Terminated or Deactivated and no new entries were being made in spite of the parent form showing that one was running (If the managers were shutdown, the running count went to 0). Even starting the concurrent managers with DIAG=Y did not add any useful information to the logs for this issue.

I reached out to one of my contacts through OAUG (one of the major reasons to be active in user groups is to develop quality contacts), Michael Barone, to see if he could think of something I had not tried. One of his suggestions was to run FND_CONC_CLONE.SETUP_CLEAN and then rerun AutoConfig. This did not solve the problem, but it did cause a new message in the ICM log, we now had a message that the apps tier could not ping. We tried ping from the command line and got the error, ping: imp open socket: operation not permitted. As a result of this, we discovered that /bin/ping had permissions and ownership:
-rwxrwxr-x root root
instead of the expected:
-rwsrwxr-x root root

As soon as we issued chmod u+s /bin/ping, the service manager (and therefore all the other managers) started. This occurred on a Redhat 6.4 server, and we do not know why the permissions changed on ping between the previous time we started the managers and the reboot. I also am not clear why the ping error did not show up every time we attempted to start the managers (we did find it in the first ICM log after the reboot, but it was not in any subsequent logs until after running doing the setup clean and autoconfig).

If you have an issue with the concurrent managers not starting, check the permissions, verify that you can run ping as the applications owner.

Changes to EBS Support Policies

Just before Openworld started, made several major announcements that all users of the E-Business Suite should be know about.

Support Changes
The exception to sustaining support for has been extended until Dec 2015. Oracle will also supply 1099 forms for the US in 2014. For HR customers, regulatory updates will be provided for the. US, UK and Canada through the end of fiscal year 2014.

Premier support for R12.1 has been extended from May. 2014 to Dec 2016. The change increased the support period for extended support until Dec 2019.

Database Certifications and 12c (without the new features such as pluggable databases) was announced for, R12.0.x and R12.1.x

JRE and JDK 7 are certified for use with the DBS.

Windows 8 and Safari on iPads have been certified.

RSS to e-mail and Oracle Linux Public Yum

I found a very useful service to help keep up with information that is released on the various Oracle blogs. allows you to subscribe to feeds and have them sent to your e-mail. This can be set up realtime on in digest mode (at 2 hour, 4 hour, 6 hour, 8 hour, 12 hour, or daily intervals).

I stumbled upon when I realized that I had missed a blog announcement that Oracle Linux patches were now available on Oracle’s public yum site. This is a major announcement for companies considering what flavor of Linux to use. Many companies debate which flavor or Linux to use between Oracle and Redhat (and others, but those seem to be the big two for companies that are using Oracle products). The fact that you can now set up development systems without any cost for getting the linux patches and still run the same version of linux that you are paying for support on in production is another big plus for Oracle Enterprise Linux. There are a couple of downsides to using the public yum vs. paying the $119/year for network support that companies still need to consider. For more information, check out the blog entry on the Oracle Linux Blog.

For an excellent overview of the value proposition is using Oracle Linux, check out this entry on Wim Coekaerts Blog.