How to Disable all scheduled Concurrent Request in R12

How to Disable all scheduled Concurrent Request in R12

Script to disable all scheduled requests - After cloning

From Front End:

1) Login with the same user, who scheduled the concurrent program
2) Go to view requests from the responsibility it's been scheduled -->View Requests--> Query for the program
3) You should get one record in scheduled state
4) Click on view details end date the schedule and cancel the request.

From Back End

Use below query to cancel scheduled concurrent program.

UPDATE fnd_concurrent_requests
SET phase_code = 'C', status_code = 'X'
WHERE status_code IN ('Q','I')
AND requested_start_date > SYSDATE
AND hold_flag = 'N'
AND CONCURRENT_PROGRAM_ID=&P_CONCURRENT_PROGRAM_ID;

COMMIT;

or 

update fnd_concurrent_requests
set phase_code='C',
status_code='D'
where phase_code = 'P'
and (status_code = 'I' OR status_code = 'Q');
and requested_start_date >= SYSDATE
and hold_flag = 'N';
COMMIT;

The following is the metalink reference articles.

a. 170107.1

b. 152209.1

Concurrent Manager Status using SQL

Concurrent Manager Status using SQL

The below query is used to get all the concurrent manager status from back end. 

Most of the times we need to quickly check the status of the CM.  

select decode(CONCURRENT_QUEUE_NAME,
 'FNDICM','Internal Manager',
 'FNDCRM','Conflict Resolution Manager',
 'AMSDMIN','Marketing Data Mining Manager',
 'C_AQCT_SVC','C AQCART Service',
 'FFTM','FastFormula Transaction Manager',
 'FNDCPOPP','Output Post Processor',
 'FNDSCH','Scheduler/Prereleaser Manager',
 'FNDSM_AQHERP','Service Manager: AQHERP',
 'FTE_TXN_MANAGER','Transportation Manager',
 'IEU_SH_CS','Session History Cleanup',
 'IEU_WL_CS',
 'UWQ Worklist Items Release for Crashed session',
 'INVMGR','Inventory Manager','
 INVTMRPM','INV Remote Procedure Manager','OAMCOLMGR',
 'OAM Metrics Collection Manager',
 'PASMGR','PA Streamline Manager',
 'PODAMGR','PO Document Approval Manager',
 'RCVOLTM','Receiving Transaction Manager',
 'STANDARD','Standard Manager',
 'WFALSNRSVC','Workflow Agent Listener Service',
 'WFMLRSVC','Workflow Mailer Service','WFWSSVC',
 'Workflow Document Web Services Service',
 'WMSTAMGR','WMS Task Archiving Manager',
 'XDP_APPL_SVC','SFM Application Monitoring Service',
 'XDP_CTRL_SVC',
 'SFM Controller Service',
 'XDP_Q_EVENT_SVC','SFM Event Manager Queue Service',
 'XDP_Q_FA_SVC','SFM Fulfillment Actions Queue Service',
 'XDP_Q_FE_READY_SVC','SFM Fulfillment Element Ready Queue Service',
 'XDP_Q_IN_MSG_SVC','SFM Inbound Messages Queue Service',
 'XDP_Q_ORDER_SVC',
 'SFM Order Queue Service',
 'XDP_Q_TIMER_SVC','SFM Timer Queue Service',
 'XDP_Q_WI_SVC','SFM Work Item Queue Service',
 'XDP_SMIT_SVC','SFM SM Interface Test Service') as "Concurrent Manager's Name",
  max_processes as "TARGET Processes",
  running_processes as "ACTUAL Processes" 
  from apps.fnd_concurrent_queues 
 where CONCURRENT_QUEUE_NAME 
 in ('FNDICM','FNDCRM','AMSDMIN',

'C_AQCT_SVC','FFTM','FNDCPOPP','FNDSCH',

'FNDSM_AQHERP','FTE_TXN_MANAGER','IEU_SH_CS',

'IEU_WL_CS','INVMGR','INVTMRPM',
 'OAMCOLMGR','PASMGR','PODAMGR','RCVOLTM','STANDARD',

'WFALSNRSVC','WFMLRSVC','WFWSSVC','WMSTAMGR',

'XDP_APPL_SVC','XDP_CTRL_SVC','XDP_Q_EVENT_SVC',
 'XDP_Q_FA_SVC','XDP_Q_FE_READY_SVC',

'XDP_Q_IN_MSG_SVC','XDP_Q_ORDER_SVC',

'XDP_Q_TIMER_SVC','XDP_Q_WI_SVC',

'XDP_SMIT_SVC')
 order by max_processes
 /

Output

------

Concurrent Manager's Name                     |TARGET Processes|ACTUAL Processes
----------------------------------------------|----------------|----------------
Workflow Mailer Service                       |               0|               0
SFM SM Interface Test Service                 |               0|               0
SFM Application Monitoring Service            |               0|               0
SFM Timer Queue Service                       |               0|               0
SFM Inbound Messages Queue Service            |               0|               0
SFM Event Manager Queue Service               |               0|               0
SFM Fulfillment Element Ready Queue Service   |               0|               0
SFM Fulfillment Actions Queue Service         |               0|               0
SFM Work Item Queue Service                   |               0|               0
SFM Order Queue Service                       |               0|               0
SFM Controller Service                        |               0|               0
C AQCART Service                              |               0|               0
Transportation Manager                        |               0|               0
Workflow Document Web Services Service        |               0|               0
WMS Task Archiving Manager                    |               0|               0
FastFormula Transaction Manager               |               0|               0
Internal Manager                              |               0|               1
Workflow Agent Listener Service               |               0|               0
Inventory Manager                             |               1|               0
PA Streamline Manager                         |               1|               1
Receiving Transaction Manager                 |               1|               0
PO Document Approval Manager                  |               1|               0
Session History Cleanup                       |               1|               0
Scheduler/Prereleaser Manager                 |               1|               0
Output Post Processor                         |               1|               1
Conflict Resolution Manager                   |               1|               0
OAM Metrics Collection Manager                |               1|               0
UWQ Worklist Items Release for Crashed session|               1|               0
                                              |               1|               0
Marketing Data Mining Manager                 |               1|               0
Standard Manager                              |              15|               0

31 rows selected.

Generate CONTEXT FILE USING AUTOCONFIG while upgrade

When Upgrading Database on EBS (11.2.4 to 12.1.0)
Generate CONTEXT FILE USING AUTOCONFIG while upgrade 

For generating a context file .Before running autoconfig follow steps

Go to Application Tier first
--------------------------------
All services are stopped now.

If You execute autoconfig .It will generate an error

execute
---------
Execute admkappsutil.pl utility to create the file appsutil.zip
$ perl $AD_TOP/bin/admkappsutil.pl admkappsutil.pl utility will create appsutil.zip in $INST_TOP/admin/out directory

copy this appsutil.zip to database tier under ORACLE HOME folder.

Now under new Oracle Home where .appsutil.zip  is copied

Copy the created appsutil.zip file from $INST_TOP/admin/out to the

 Uncompress appsutil.zip under the  

     $ cd $ORACLE_HOME

     $ unzip -o appsutil.zip

Step 4: Create Contextfile

     $ cd $ORACLE_HOME/appsutil/bin

$ perl adbldxml.pl appsuser=apps password=***

(Issues you will face) 

perl and java 

(perl adbldxml.pl

Can't locate Config.pm (Go to perl adbldxml.pl document) and find out the solution 

export Perl file 

and java You need to set jtop (example JTOP not found at its desired location /u01/oracle/OFIN/12102/jdk

Restart adbldxml.pl with valid jtop or without jtop(to take default JRE_TOP)

execute 

perl adbldxml.pl jtop=$ORACLE_HOME/12102/jdk/

it will complete successfully.

context file will be generated.

Go to APPLICATION Tier 

and execute autoconfig

 

perl adbldxml.pl error

perl adbldxml.pl error 

Unable to build database context file, using adbldxml.pl

while creating context file  we ran perl adbldxml.pl on dbTier and  got the error 

perl adbldxml.pl

Can't locate Config.pm in @INC (@INC contains: ../../..//12102/perl/lib/5.10.0 ../../.././/db/12102/perl/lib/site_perl/5.10.0 ../lib/site_perl/5.14.1/sun4-solaris-thread-multi-64 ../lib/site_perl/5.14.1 ../lib/5.14.1/sun4-solaris-thread-multi-64 ../lib/5.14.1 .) at adbldxml.pl line 31.
BEGIN failed--compilation aborted at adbldxml.pl line 31.

Unable to build database context file, using adbldxml.pl
11gR2 Database with EBS R12 Perl lib version doesn't match executable version

RC-00110: Fatal: Error occurred while relinking of ApplyDBTechStack


Resolved -
Setting the PERL5LIB environment variable on the Database tier

By default, the PERL5LIB environment variable is set to the following on the Database tier:

/perl/lib/5.8.3:/perl/site_perl/5.8.3:/appsutil/perl

But for an instance with 11gR2 Database, the perl version on the database tier is '5.10.0'. So the variable 'PERL5LIB' on the 11gR2 database tier needs to be set as follows:

export PERL5LIB=/perl/lib/5.10.0:/perl/site_perl/5.10.0:/appsutil/perl

For Ex:

export PERL5LIB=/perl/lib/5.10.0:/perl/site_perl/5.10.0:/appsutil/perl


Answer 2

Please check the outputs below:- 

#echo `which perl`
/usr/bin/perl

#`which perl` -v

export ORACLE_HOME=/u01/app/oracle/oas_home/10.1.3
export PERL5LIB=$ORACLE_HOME/perl/lib/5.8.3:$ORACLE_HOME/perl/lib/site_perl/5.8.3:
export PERL5LIB=$PERL5LIB:$ORACLE_HOME/perl/lib/site_perl/5.8.3/i686-linux-thread-multi:$PERL5LIB
export PATH=$ORACLE_HOME/perl/bin:$PATH

Browser settings for Ebusiness suite R12

Internet Explorer is the recommended browser for Ebusiness R12

Recommended Browsers for Oracle E-Business Suite Release 12 (Doc ID 389422.1)

IE11 Enterprise Mode and Compatibility View (Required)

Oracle E-Business Suite 12 is not certified with IE11 using either 'Enterprise Mode' or 'Compatibility View'.

Enterprise Mode: Internet Explorer 11 includes an 'Enterprise mode' which can be used to emulate Internet Explorer 8 behavior and provide compatibility for earlier browser standards. This should not be used with Oracle E-Business Suite as it will have no effect on certain issues. If you need to use 'Enterprise Mode' for other applications then EBS should be added as an exception to bypass it .

Compatibility View: Due to Display Issues in FWK (IE9 and 10) it was previously recommended to run E-Business Suite using the browsers 'Compatibility View'. These display issues have been fixed for IE11 through the patches listed in the IE 11 Prerequisite Patch Requirements below. Once you have applied the prerequisite patches, you should run E-Business Suite pages without enabling the 'Compatibility View' feature in the browser. You can check this by navigating to Internet Explorer 11 -> Tools -> Compatibility View settings, and ensuring that:

Your instance domain is NOT part of the Compatibility View settings, and
The 'Display intranet sites in Compatibility View' is unchecked.
Having this setting checked can cause display issues as outlined under EBS 12.2.5 and Higher: Login Page Button Misalignment.


Internet Explorer: Recommended Browser Settings


The use of certain functions within Oracle E-Business Suite will require the default browser settings to be altered as outlined below. With the exception of these changes, IE is tested with the default parameter settings.

Java(TM) was blocked because it is out of date and needs to be updated


Oracle's recommendation has always been to run Oracle E-Business Suite through the 'Trusted sites' zone as outlined under the Internet Explorer: Recommended Browser Settings section within this document. Users that have followed this advisory or run their environments through the Local Intranet zone will not be affected by this change within IE.

Users that are running their Oracle E-Business Suite environments through any other zone and are also using an old JRE version on any stream will not be able to access forms or any other Java content. Microsoft provide a workaround in their documentation to turn this feature off which can be used to workaround this issue if desired. However, Oracle continues to recommend running your Oracle E-Business Suite environments to through the 'Trusted sites' zone of the browser which will avoid this issue occurring.


Security Zones

Microsoft Internet Explorer offers four different security zones to run your application through. Which zone is used is dependant how you are accessing your site (Internet or Local Intranet) and set up within the zones themselves (Trusted sites & Restricted sites).

It is advisable to have the security setting at Medium for run-time use.

The Security Internet Options on Microsoft Internet Explorer can be accessed by going to:

Tools -> Internet Options -> Security tab from the Internet Explorer Menu Bar.

Each zone carries its own default security level that may need to be adjusted when accessing Oracle E-Business Suite through it. The defaults are as follows:

NOTE: It is recommended that Oracle E-Business Suite is run through the 'Trusted Sites' zone, with a 'Medium' Security Setting.

Trusted Sites Zone

Certain products and functions within Oracle E-Business Suite require the manipulation of the default browser security zone settings to function correctly. Altering security settings in the Internet Zone is not recommended because you are accessing more widespread web data of which you may not know the source. The Trusted Sites zone allows you to precisely control which specific sites or domains will be accessed through this zone. This allows you, if required, to manipulate the settings with minimal security risk.

Setting up Oracle E-Business Suite to run through the 'Trusted Sites' zone with a 'Medium' Security Setting.

Step 1: Select Tools -> Internet Options -> Security tab -> Trusted Sites icon -> Sites (button) from the Internet Explorer Menu Bar.
Step 2: If required, set the Security Level for this Zone to Medium.
Step 3: In the Add this Web site to the zone: field, enter the 'hostname and domain' of your Oracle E-Business Suite environment,
e.g. https://., then click the Add button.
Alternatively you can simply add the domain name precede7 d by *, so that all sites under that domain go through this zone, e.g. *.
Note: If you are entering an http://... or *.domain address, you must first uncheck the Require server verification (https:) for all sites in this zone check box. You may re-check this steeing again after entering your values.

Pop-up Blocker

Certain content within Oracle E-Business Suite requires pop-ups to function in the browser. If you are blocking pop-ups through your browser settings, add the domain name from your URL ( e.g. *.example.com ) as an allowed site using one of the following paths:

Tools -> Pop-up Blocker -> Pop-up Blocker Settings -> Allowed Sites
Tools -> Internet Options -> Privacy -> Pop-up Blocker: Settings -> Allowed sites

Internet Explorer Browser Settings for User Download of oaj2se.exe

Oracle recommends that customers running Oracle E-Business Suite through Internet Explorer (IE) should use a 'Medium' security setting through the 'Trusted Sites' zone in the browser at runtime. This setting does not automatically download the oaj2se.exe file from the middle tier if the user does not already have the appropriate version installed on their desktop.

The JRE plug-in will download and install from the webserver on a medium security setting. After clicking on a 'forms link', a message similar to the following will appear at the top of the browser window:

'The website wants to install the following add-on: 'Java SE Runtime Environment 8 Update 101' from 'Oracle America, Inc.'.

To install the plug-in:-

1. Click the Install Button.
2. Do you want to allow the following program to make changes to your computer
3. Once the browser has stopped processing, click on the 'forms link' again, and the oaj2se.exe file should start to download.
4. Once the download has completed, a security warning pop-up window will ask, 'Do you want to allow the following program to make changes to your computer?'. Click the Yes button.
5. When the Java Setup window opens click n the 'Install' button and follow the on screen instructions.

Alternatively for ease of access when downloading this file temporarily alter the security settings within the browser using one of the two methods below:

Method A: Change Individual Parameter Settings

1. Select 'Tools' -> 'Internet Options -> 'Security' (Tab)' from the browser menu.
2. Select 'Trusted Sites' -> 'Custom Level' (button)
3. Under 'Settings' -> 'ActiveX controls and Plug-ins'
4. Change 'Automatic prompting for ActiveX controls' to 'Enable'
5. Change 'Download unsigned ActiveX controls' to 'Prompt'
6. Click the 'OK' button and accept the changes and click the 'OK' buttons to close the window
7. Close the browser and start a new browser session for the settings to take effect.
8. After downloading the oaj2se.exe file onto your desktop, you may reset the default values for runtime use, if required:
   'Automatic prompting for ActiveX controls' to 'Disable' and
   'Download unsigned ActiveX controls' to 'Disable'.

Method B: Temporarily Change Security Setting to Medium-low

1. Select 'Tools' -> 'Internet Options -> 'Security' (Tab)' from the browser menu.
2. Select 'Trusted Sites' -> 'Custom Level' (button)
3. From the 'Reset custom settings' drop down select 'Medium-low'
4. Click the 'Reset...' button and accept the changes.
5. Press the 'okay' buttons to close the window.
6. Close the browser and start a new browser session for the settings to take effect.
7. After launching Oracle E-Business Suite and downloading the oaj2se.exe file onto your desktop, please reset the security setting back to 'Medium'

Internet Explorer: Running IE 11 in 64-bit Mode

Internet Explorer runs in a multi-process architecture whereby there is a Frame (Manager) process and one or more Tab (Content) processes. There is no longer a separate 32-bit and 64-bit install of the browser when running a 64-bit version of Windows. In this instance the Frame (Manager) process always runs as 64-bit while the Tab (Content) process can run as either 32-bit or 64-bit.

Internet Explorer Settings

To run Oracle E-Business Suite through a 64-bit browser using a 64-bit JRE release you will need to set the following values in Internet Explorer:

Windows 7 (64-bit)

Select (Check) the following values:

Tools -> Internet Options -> Security -> (e.g. Trusted Sites) -> Enable Protected Mode
Tools -> Internet Options -> Advanced -> Enable Enhanced Protection Mode

Windows 10 (64-bit) and Windows 8.1 (64-bit)

Select (Check) the following values:

Tools -> Internet Options -> Security -> (e.g. Trusted Sites) -> Enable Protected Mode
Tools -> Internet Options -> Advanced -> Enable 64-bit processes for Enhanced Protection Mode

Do not select (Uncheck) the following value:

Tools -> Internet Options -> Advanced -> Enable Enhanced Protection Mode

Clear Browsing history

Unable to Authenticate Session

If you receive an 'Unable to authenticate session' error in your browser when running multiple sessions, please set the -noframemerging option as outlined in the Multiple EBS Sessions section above.
If this does not resolve the problem or you are not running multiple sessions, please try clearing your browser cache by deleting the 'Temporary Internet Files' through:




Tools -> Internet Options -> General (tab) -> Browsing History -> Delete (button)










how to know ports of appTier services in EBS R12

How to know ports of appTier services in ebusiness suite R12

Using the context file grep for s_wls and pipe grep port to list all weblogic (Admin & Managed) server ports. 

-bash-3.2$ egrep 'port_pool|s_wls' $CONTEXT_FILE |grep port

egrep 'port_pool|s_wls' $CONTEXT_FILE |grep port

If you look at the context file for an existing Oracle E-Business Suite Release 12.2 system,, you will see each WebLogic server has a base port number. For example, the oacore server has a base port of 7201. During installation of Oracle E-Business Suite, you can if desired specify a port pool. 

The run and patch file systems for a Release 12.2 system must each use a different port pool. And if you install two separate Oracle E-Business Suite Release 2.2 environments on the same server, they also must use different port pools.

Note: Be aware that the same web ports are used for both fs1 and fs2, so the entry points for users will also remain the same. However, different ports are used for WLS administration activities on the patch file system while the run file system is in use. You may find it useful to make a note of the WLS Admin ports.

How to Change Applications Passwords using Applications Schema Password Change Utility (FNDCPASS or AFPASSWD) (Doc ID 437260.1)

Change Applications Passwords using Applications Schema Password Change Utility (FNDCPASS or AFPASSWD) 

Oracle Metalink Document and very helpful

In this Document

Goal

Solution

Using the FNDCPASS Utility:

Verify the new password.

Examples:

Using the AFPASSWD Utility as of R12.1.2:

Diagnostics & Utilities Community:

Troubleshooting FNDCPASS

References

---

APPLIES TO:

Oracle Application Object Library - Version 11.5.10.2 to 12.2 [Release 11.5 to 12.2]
Information in this document applies to any platform.

GOAL

• The goal of this document is to help understand the process of changing passwords in Oracle Applications. As the Applications directory structure has changed a little, the files that need to be updated have also changed, although the FNDCPASS commands to change/reset the passwords remained pretty much the same.
• For R12.1.2, an enhanced version of FNDCPASS is available using AFPASSWD noted at the bottom of this document.

SOLUTION

Since changing passwords frequently helps ensure database security, Oracle Applications provides a command line utility, FNDCPASS, to change/reset Oracle Applications schema passwords. This utility changes the password registered in Oracle Applications tables, changes the schema password in the database and can also change user passwords.

NOTE :

• One cannot change a schema name, such as APPLSYS or GL, after a product is installed, with FNDCPASS.
• Ensure that the entire Oracle Applications system has been shut down before changing any schema passwords.
• All users should log out and the Applications system should be down before running this utility. 
• If Oracle Applications user passwords are being changed then the relevant users should not be logged in. 
• Before changing any passwords, you should make a backup of the tables FND_USER and FND_ORACLE_USERID.
• Do not use any special characters in password because FNDCPASS utility does not support special characters.

Autoconfig needs to be run after changing 'APPLSYSPUB' or 'GUEST' user password !

Note: SOURCE the environment FIRST.  Ex:

1. Log into the Operating system level by way of the applmgr user.
2. Run the environment script APPSORA.env:
a. cd $APPL_TOP
b. Run APPSORA.env.
c. The above should also run _.env, but can verify by running it.
d. cd admin.
e. Run adovars.env.

Using the FNDCPASS Utility:

FNDCPASS / 0 Y \

/

Please set the depending on your needs:

Note:
The SYSTEM token is used when changing the APPLSYS password.
The ORACLE token is used when changing a SINGLE Applications schema password.
The ALLORACLE token is used when changing ALL Applications schema passwords.
The USER token is used when changing an Applications USER password.

Note: Passwords for APPLSYS and the APPS schemas -- including the MRC schema -- must be the same. If you change the password for one, FNDCPASS automatically changes the others. When changing APPS (or APPLSYS) and APPLSYSPUB passwords, do not restart the system until the entire password change process has been completed.

Verify the new password.

If you changed the password for APPS (and APPLSYS), restart all concurrent managers, then log on to Oracle Applications to test the new password.

Examples:

A). To change the APPS and APPLSYS schema password:

Use the following command to change passwords for schema that are used by shared components of Oracle Applications. 

FNDCPASS  0 Y  SYSTEM  

FNDCPASS uses the following arguments when changing the APPLSYS password. When specifying the SYSTEM token, FNDCPASS expects the next arguments to be the APPLSYS username and the new password. 

• logon                           The Oracle username/password.
• system/password     The username and password for the SYSTEM DBA account.
• username                   The APPLSYS username. For example, 'applsys'.
• new_password         The new password.

This command does the following:

1. Validates APPLSYS.
2. Re-registers password in Oracle Applications.
3. Changes the APPLSYS and all APPS passwords (for multi-APPS schema installations) to the same password.
   Because everything with a Privilege Level [set to any of ('E', 'U', 'D')] in the FND_ORACLE_USERID table must always have the same password, FNDCPASS updates these passwords as well as APPLSYS's password.
   For example, the APPS password will be updated when the APPLSYS password is changed.
4. ALTER USER is executed to change the ORACLE password for the above ORACLE users.

For instance, the following command changes the APPLSYS password to 'WELCOME'.

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

B). To change an Oracle Applications schema password (other than APPS/APPLSYS):

 Use this command to change the password of a schema provided by an individual product in Oracle Applications. 

FNDCPASS  0 Y  ORACLE  

Use the above command with the following arguments. When specifying the ORACLE token, FNDCPASS expects the next arguments to be an ORACLE username and the new password.

• logon                           The Oracle username/password.
• system/password     The username and password for the SYSTEM DBA account.
• username                   The Oracle username. For example, 'GL'.
• new_password         The new password.

For example, the following command changes the GL user password to 'GL1'.

FNDCPASS apps/apps 0 Y system/manager ORACLE GL GL1

C). To change all ORACLE schema passwords:

 Use this command to change the passwords of all schemas provided by Oracle Applications products. 

FNDCPASS  0 Y  ALLORACLE 

Use the above command with the following arguments. When specifying the ALLORACLE token, FNDCPASS expects the next argument to be the new password.

• logon                             The Oracle username/password.
• system/password       The username and password for the SYSTEM DBA account.
• new_password           The new password.

For example, the following command changes all ORACLE schema passwords to "WELCOME":

FNDCPASS apps/apps 0 Y system/manager ALLORACLE WELCOME 

For additional information on the use of ALLORACLE, please reference NOTE 189367.1 - Best Practices for Securing the E-Business Suite

D). To change an Oracle Applications user's password:

Use this command to change an individual Oracle Applications user's password.

FNDCPASS  0 Y  USER   

Use the above command with the following arguments. When specifying the USER token, FNDCPASS expects the next arguments to be an Oracle Applications username and the new password.

• logon                            The Oracle username/password.
• system/password      The username and password for the System DBA account.
• username                    The Oracle Applications username. For example, 'VISION'.
• new_password          The new password.

For example, if you were changing the password for the user VISION to 'WELCOME', you would use the following command:

FNDCPASS apps/apps 0 Y system/manager USER VISION WELCOME 

Using the AFPASSWD Utility as of R12.1.2:

For Applications release 12.1.2, please reference page 11-8 of the 'Oracle E-Business Suite System Administrator's Guide - Configuration' for use of the AFPASSWD utility.  Document 457166.1 must be used for migration from FNDCPASS.

NOTE:
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.


$ AFPASSWD
Usage:
    AFPASSWD [-c [@]] -f
    AFPASSWD [-c [@]] -o
    AFPASSWD [-c [@]] -a
    AFPASSWD [-c [@]] -l {TRUE|FALSE}
    AFPASSWD [-c [@]] -L {TRUE|FALSE}
    AFPASSWD [-c [@]] -s

For further details see section "Oracle E-Business Suite Password Management" of the Oracle E-Business Suite Maintenance Guide Release 12.2.

Diagnostics & Utilities Community:

• Diagnostics
  Please access the EbusinessSecurity section on security diagnostics for the latest releases as reflected in Document 421245.1 E-Business Suite Diagnostics References for R12.
• Utilities CommunityVisit the Utilities community for help from industry experts or to share knowledge.

Troubleshooting FNDCPASS

Please reference Document 1306938.1 FNDCPASS Troubleshooting Guide For Login and Changing Applications Passwords which is a consolidation of Top Documents providing a Single Source for Troubleshooting common problems with FNDCPASS.

adtasktim.sql ORA-01017: invalid username/password; logon denied

adtasktim.sql ORA-01017: invalid username/password; logon denied 

Got error while while doing adop phase=abort. 

EBS 12.2 applications and utilities unable to access database problem resolved after setting sec_case_sensitive_logon parameter ACTION PLAN: During apply phase -- and subsequently abort , adtasktim.sql script is failing because password for applsys user is not recognized anymore. So, reset the password for applsys to exactly what was at the time when the patching process was initiated (adop session id #). (you can use FNDCPASS) also verify value for db parameter: sec_case_sensitive_logon : show parameter sec_case_sensitive_logon; --> and set it temporarily to FALSE, in case the value returned for the query above is TRUE (you can use: alter system set sec_case_sensitive_logon = FALSE) This way adop will be able to recognize the password. Test first the sqlplus connection for the applsys -- to confirm . Then, re-initiate adop phase=abort. 3-11464439901 - Oracle Applications DBA 12.2.4 1001: "ORA-01017: invalid username/password; logon denied" While applying patch 19007053 SOLUTION: My problem is now resolved by changing parameter sec_case_sensitive_logon to false in the init.ora en spfile.ora.

Steps to change the APPS, APPLSYS, and APPS_NE password using FNDCPASS or AFPASSWD for EBS 12.2 (oacore_server1)

Steps to change the APPS, APPLSYS, and APPS_NE password using FNDCPASS or AFPASSWD for EBS 12.2 (Doc ID 1674462.1)

Oacore services are not coming up  (Check down Steps) from step 5

APPLIES TO:

Oracle Application Object Library - Version 12.2 and later
Information in this document applies to any platform.

GOAL

What are the steps to change the APPS, APPLSYS, and APPS_NE password using FNDCPASS for E-Business Suite (EBS) 12.2?
 

SOLUTION

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

2. Change the APPLSYS password using

A. FNDCPASS:

Use the below syntax:

FNDCPASS 0 Y / SYSTEM APPLSYS

For example, the following command changes the APPLSYS password to 'WELCOME':

FNDCPASS apps/ 0 Y system/manager SYSTEM APPLSYS WELCOME

Note: Please note that you have $FND_TOP/patch/115/sql/ AFSCJAVS.pls file version 120.12.12020000.8 or above before running FNDCPASS on 12.2.X.
Else you need to apply the patch 19127427 : UNABLE TO CHANGE PASSWORD USING FNDCPASS - NO ERRORS IN THE LOG, If not FNDCPASS with fail to change the password.

 B. 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 [@]] -s

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

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

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. Start all the application tier services using the below script

$INST_TOP/admin/scripts/adstrtal.sh

7. Verify the WLS Datastore changes as follows:

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

R12 system crashes when adop is running

R12.2 If system crashes when adop is running  

When system crashes when adop is running adop fails to update the status in the internal repository.

The next attempt to run adop will give the following error.

Error: Unable to continue as already another user is using adzdoptl.pl.
Previous session exist, cannot continue as per user input.

Workaround: Update the internal adop repository table for the latest session setting the status to completed.

Run the following statement to find out the session that is in running state:

SQL>

select adop_session_id from ad_adop_sessions where status='R';

Set the status to 'C' (Completed) for that session, to re-try the phase that was interrupted:

SQL>

update ad_adop_sessions set status='C' where status='R;

commit;

On command Prompt.

Run

set Environment variables

adop -status

12cR1 Upgrade in Oracle Applications EBS R12.2

Upgrade Database 11.2 to 12.2
(Article From Toadworld.com)
Easily explained and steps to upgrade.

Introduction:

Oracle E-Business suite R12.2 is shipped with Oracle Database Version 11.2.0.3. There will be always a requirement for upgrading your database to latest available release for fixing bugs, using new features and to be on supported version of database. This article will outline all steps required for upgrading and using 12cR1 database with your Oracle E-Business suite R12.2

Environment details:

Host : erpnode3 ( Oracle Enterprise Linux 5.7)

Installation Type :

Host Details	erpnode3 - Oracle Enterprise Linux 5.7 64 Bit
EBS Installation Type	Single Node (DB + Application)
EBS Version	R12.2.4
Database Version	11.2.0.3

STEPS for Upgrade:

1) Pre-Upgrade Steps:

1.1 - Install 12cR1 RDBMS Software

1.2 - Install R12cR1 Examples CD

1.3 - Create /nls/data/9idata directory

1.4 - Install all pre-requisite Database and Application patches

1.5 - Verify the JRE version in Oracle Home

1.6 - Verify Application patching cycle is complete

1.7 - Drop SYS.ENABLED$INDEXES

1.8 - Remove the MGDSYS schema

1.9 - Run pre upgrade tool

2) Upgrade Database

2.1 - Use DBUA for upgrading database

3) Post Upgrade Steps:

3.1 - Install patch post Installation steps for all RDBMS patches (opatches)

3.2 - Start Listener from 12cR1 Home

3.3 - Application Database accounts Expired & Locked

3.4 - Run adgrants.sql

3.5 - Grant create procedure privilege on CTXSYS

3.6 - Compile Invalid Objects

3.7 - Set CTXSYS parameter

3.8 - Validate Workflow ruleset

3.9 - Create context file and run autoconfig on dbTier

3.10 - Run script "adstats.sql" to gather SYS stats

3.11 - Create new MGDSYS schema

3.12 - Apply post upgrade WMS patches

3.13 - Recreate grants and synonyms

3.14 - Start Application services

3.15 - Run concurrent Request "Synchronize workflow views"

3.16 - Verify the upgraded version from OAM

4) Issues

4.1 - Unable to proceed with 12c runInstaller with error "[INS-10102] Installer initialization failed"

4.2 - DBUA not listing the database

4.3 - Invalid specification of system parameter "LOCAL_LISTENER"

4.4 - Application Database account locked after upgrade

1.1 - Install 12cR1 RDBMS Software

Install 12cR1 RDBMS Oracle Home in a separate directory from the existing Oracle Home. The current Oracle Home location is "/u01/ora_test/11.2.0" and 12cR1 Oracle Home will be Installed in "/u01/ora_test/12.1.0"

- Set the Proper Display Variable and execute "runInstaller"

- Here select option "Install Database software only"

- Select "Single Instance Database"

- If you have any other language Installed and configured than add required languages.

- Select Enterprise Edition

- Provide the valid Oracle Base and Oracle home location.

- Select the valid groups for all roles. In my case only one group is used.

- If there are any missing pre-requisites listed then fix it. Some of these pre-requisites can be fixed using fixup script and missing rpm package cannot be fixed using fixup script. Hence install any listed missing rpm packages.

- Execute fixup script from the specified location as "root" user.

- Check "summary" of setting configured for Installation. If there are any changes you can edit it from the same screen.

- Execute "root.sh" script from root user.

- Here the Installation of RDBMS software completed.

1.2 - Install R12cR1 Examples CD

- Installation of Examples CD is mandatory and one should not skip its Installation before starting the upgrade process. Examples CD will be Installed in existing newly Installed 12cR1 Oracle home.

- set the proper display variable and execute runInstaller

- Here select the existing 12cR1 Oracle home (/u01/ora_test/12.1.0)

- Check "summary" for configured settings.

- Installation of "Examples CD" completed successfully.

1.3 -Create /nls/data/9idata directory

Execute "cr9idata.pl" script from 12c Home ($ORACLE_HOME/nls/data/old/cr9idata.pl). Configure "ORA_NLS10" Environment variable with directory created in 12c Home

[oraebs@erpnode3 ~]$ perl $ORACLE_HOME/nls/data/old/cr9idata.pl

Creating directory /u01/ora_test/12.1.0/nls/data/9idata ...

Copying files to /u01/ora_test/12.1.0/nls/data/9idata...

Copy finished.

Please reset environment variable ORA_NLS10 to /u01/ora_test/12.1.0/nls/data/9idata!

[oraebs@erpnode3 ~]$

1.4 - Install all pre-requisite Database and Application patches

Application Patches:

Current EBS environment is running on latest release EBS R12.2.4 so there are no additional application patches are required to be Installed.

Database Patches:

The following RDBMS patches need to be Installed as a pre-requisites before upgrading the Database.

Patches Linux X86-84 Bit - Version 12.1.0.1.0

17695298 (see Footnote 2), 14237793, 16989137, 17184721, 17448638, 17600719, 17801303, 17892268, 17912217, 17973865, 17973883, 18288676, 18419770, 18604144, 18614015, 18665660, 18685209, 19466632, 19603897 (see Footnote 3), 19393542

Footnote 2 - This is the Database Bundle Patch for 12.1.0.1.0 and must be applied first. This includes the database patch for 18241194 which will be removed in one of the subsequent patches as it is no longer needed.

Footnote 3 - If a conflict is reported with 18241194, either roll back 18241194 first (opatch rollback, then apply 19603897), or allow opatch to roll it back when applying Patch 19603897.

Configure 12c Enviroment variables:

[oraebs@erpnode3 ~]$ cat 12c.env

export ORACLE_HOME=/u01/ora_test/12.1.0

export PATH=$ORACLE_HOME/bin:$ORACLE_HOME/OPatch:$PATH

export ORA_NLS10=/u01/ora_test/12.1.0/nls/data/9idata

[oraebs@erpnode3 ~]$

[oraebs@erpnode3 ~]$ export ORACLE_HOME=/u01/ora_test/12.1.0

[oraebs@erpnode3 ~]$ export PATH=$ORACLE_HOME/bin:$PATH

[oraebs@erpnode3 ~]$ export PATH=$ORACLE_HOME/bin:$ORACLE_HOME/OPatch:$PATH

[oraebs@erpnode3 ~]$ vi 12c.env

[oraebs@erpnode3 ~]$ which opatch

/u01/ora_test/12.1.0/OPatch/opatch

[oraebs@erpnode3 ~]$ opatch lsinventory

Oracle Interim Patch Installer version 12.1.0.1.0

Copyright (c) 2012, Oracle Corporation. All rights reserved.

Oracle Home : /u01/ora_test/12.1.0

Central Inventory : /u01/ora_test/oraInventory

from : /u01/ora_test/12.1.0/oraInst.loc

OPatch version : 12.1.0.1.0

OUI version : 12.1.0.1.0

Log file location : /u01/ora_test/12.1.0/cfgtoollogs/opatch/opatch2014-11-17_15-53-52PM_1.log

Lsinventory Output file location : /u01/ora_test/12.1.0/cfgtoollogs/opatch/lsinv/lsinventory2014-11-17_15-53-52PM.txt

------------------------------------------------------------------------------

Installed Top-level Products (2):

Oracle Database 12c 12.1.0.1.0

Oracle Database 12c Examples 12.1.0.1.0

There are 2 products installed in this Oracle Home.

There are no Interim patches installed in this Oracle Home.

------------------------------------------------------------------------------OPatch succeeded.

[oraebs@erpnode3 ~]$

The above command lists the Installed products in an Existing Oracle home. All pre-requisites patches needs to be Installed in 12.1.0.1.0 Oracle home.

As per footnote2 patch "17695298" should be Installed first as this patch contains the consolidated bug fixes.

As per footnode3 If a conflict is detected with patch "18241194" than uninstall this patch than Install patch "19603897".

Refer Attached file for Installing all RDBMS opatches.

[applebs@erpnode3 appl_test]$ adop phase=cutover,cleanup

12c_Opatches.doc

1.5 - Verify the JRE version in Oracle Home

To upgrade to 12cR1 minimum version of JRE required is version 6. Please make sure that Installed version of JRE in an existing Oracle Home. If the Installed version is lower than required then please upgrade it.

In current setup the Installed version is version 7 so no action is required.

[oraebs@erpnode3 bin]$ pwd

/u01/ora_test/11.2.0/appsutil/jre/bin

[oraebs@erpnode3 bin]$ ./java -version

java version "1.7.0_17"

Java(TM) SE Runtime Environment (build 1.7.0_17-b02)

Java HotSpot(TM) 64-Bit Server VM (build 23.7-b01, mixed mode)

[oraebs@erpnode3 bin]$

1.6 - Verify Application patching cycle is complete

Before starting the upgrade process verify the Application patching cycle is complete and there no pending actions.

[applebs@erpnode3 appl_test]$ adop phase=cutover,cleanup

1.7 - Drop SYS.ENABLED$INDEXES 

If table SYS.ENABLED$INDEXEX exists then drop this table with sysdba user. In current setup this table doesn't exists.

[oraebs@erpnode3 11.2.0]$ sqlplus / as sysdba

SQL*Plus: Release 11.2.0.3.0 Production on Tue Nov 18 11:39:15 2014

Copyright (c) 1982, 2011, Oracle. All rights reserved.

Connected to:

Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production

With the Partitioning, OLAP, Data Mining and Real Application Testing options

SQL> drop table sys.enabled$indexes;

drop table sys.enabled$indexes

*

ERROR at line 1:

ORA-00942: table or view does not exist

SQL> desc sys.enabled$indexes;

ERROR:

ORA-04043: object sys.enabled$indexes does not exist

SQL>

1.8 - Remove the MGDSYS schema

If upgrading from database version prior to 12c than drop MGDSYS schema from the existing database. Execute script "catnomgdidcode.sql " from an existing Oracle home.

SQL> @?/md/admin/catnomgdidcode.sql

User dropped.

Synonym dropped.

Synonym dropped.

Synonym dropped.

Synonym dropped.

SQL>

1.9 - Run pre upgrade tool

Pre Upgrade tool will lists all changes need to be performed before starting the upgrade process.

Copy pre upgrade scripts from 12cR1Oracle home to any other directory. I used "db_scripts" directory to keep all upgrade related scripts in one location.

[oraebs@erpnode3]$cp /u01/ora_test/12.1.0/rdbms/admin/preupgrd.sql .

[oraebs@erpnode3]$cp /u01/ora_test/12.1.0/rdbms/admin/utluppkg.sql .

Make sure that preupgrd.sql and utluppkg.sql files are copied in the same directory.

- Connect from 11.2.0.3 Home as sysdba and run pre-upgrade tool

SQL> @preupgrd.sql

Loading Pre-Upgrade Package...

Executing Pre-Upgrade Checks...

Pre-Upgrade Checks Complete.

************************************************************

Results of the checks are located at:

/u01/ora_test/11.2.0/cfgtoollogs/test/preupgrade/preupgrade.log

Pre-Upgrade Fixup Script (run in source database environment):

/u01/ora_test/11.2.0/cfgtoollogs/test/preupgrade/preupgrade_fixups.sql

Post-Upgrade Fixup Script (run shortly after upgrade):

/u01/ora_test/11.2.0/cfgtoollogs/test/preupgrade/postupgrade_fixups.sql

************************************************************

Fixup scripts must be reviewed prior to being executed.

************************************************************

************************************************************

====>> USER ACTION REQUIRED <<====

************************************************************

The following are *** ERROR LEVEL CONDITIONS *** that must be addressed

prior to attempting your upgrade.

Failure to do so will result in a failed upgrade.

1) Check Tag: INVALID_SYS_TABLEDATA

Check Summary: Check for invalid (not converted) table data

Fixup Summary:

"UPGRADE Oracle supplied table data prior to the database upgrade."

+++ Source Database Manual Action Required +++

You MUST resolve the above error prior to upgrade

************************************************************

SQL>

Oracle Database 12c Pre upgrade utility will generate preupgrade.log, preupgrade_fixups.sql and postupgrade_fixup.sql

We need to review preupgrade.log file and check for all recommendation. This will be helpful if you are performing the manual upgrade.

- perform full database backup.

2) Upgrade Database

2.1 - Use DBUA for upgrading database

- Configure the temporary environment file during upgrade process. After enabling autoconfig on 12c Home it will generate new environment file with all required EBS parameters

- Execute dbua from 12c Home

Make sure that oratab file contains a valid SID entry in "/etc/oratab" file. In my environment after fresh installation this entry was missing and dbua was not able to list the database. After manually adding entry in oratab file it was listed in dbua window.

Its gathering the information required for upgrading the database.

- Performing the pre-requisite checks

As mentioned in the tech notewe can safely ignore DBMS LDAP dependencies. If there are any Invalid objects in the database try to compile them.

- Select "ignore" and set action "ignore" then click on next.

- You can select Parallelism parameters based on available hardware resources. If you want to upgrade the Timezone Data then check "Upgrade Timezone Data" it will upgrade your Timezone Data to V18, the current version of Timezone is 17.

- Listener will be configured after upgrading the database. So do not select to configure listener.

- You can perform a backup before starting the upgrade process if there is no backup policy in place. If you backed up your database already then you can select "I have my own backup and restore strategy"

- This error was encountered as there are no listeners configured in 12.1.0.1 Oracle Home. You can safely ignore this error. We will manually configure the listener after completion of database upgrade process. To avoid this error you can create the listener from 12cR1 Oracle home before starting dbua.

- You can also avoid this error by removing the LOCAL_LISTENER parameter from the spfile created by dbua and re-run dbua.

- There was an error in upgrade alert log "SYSTEM.EBS_LOGON ORA-01031:Insufficient privileges"

By default SYSTEM.EBS_LOGON trigger is enabled. To avoid this error disable this trigger.

- Upgrade completed successfully. Click on "upgrade results" to check full details.

- The new spfile has been created in 12cR1 Oracle home.

- Time zone version has been upgraded from version 17 to version 18

- sec_case_sensitive_logon parameter was removed.

3) Post Upgrade Steps:

3.1 - Install patch post Installation steps for all RDBMS patches (opatches)

Perform post Installation steps for all Installed patches prior to upgrade. If DATAPATCH is required to run then it can be run but only once.

3.2 - Start Listener from 12cR1 Home:

Copy TNS_ADMIN directory from 11gR2 Home to 12cR1 home and modify all required files with 12c Oracle Home location.

[oraebs@erpnode3 admin]$ ls -lrt

total 12

-rw-r--r-- 1 oraebs dbaerp 205 May 11 2011 shrept.lst

drwxr-xr-x 2 oraebs dbaerp 4096 Oct 27 21:25 samples

drwxr-xr-x 2 oraebs dbaerp 4096 Oct 27 23:11 test_erpnode3

[oraebs@erpnode3 admin]$ cp -pr test_erpnode3/u01/ora_test/12.1.0/network/admin

[oraebs@erpnode3 admin]$ pwd

/u01/ora_test/11.2.0/network/admin

[oraebs@erpnode3 admin]$

- Configured listener.ora and tnsnames.ora

Network_files_12c.doc

- Start listener from 12c Home

[oraebs@erpnode3 test_erpnode3]$ pwd

/u01/ora_test/12.1.0/network/admin/test_erpnode3

[oraebs@erpnode3 test_erpnode3]$ export TNS_ADMIN=/u01/ora_test/12.1.0/network/admin/test_erpnode3

[oraebs@erpnode3 test_erpnode3]$ lsnrctl start test

LSNRCTL for Linux: Version 12.1.0.1.0 - Production on 20-NOV-2014 08:55:35

Copyright (c) 1991, 2013, Oracle. All rights reserved.

Starting /u01/ora_test/12.1.0/bin/tnslsnr: please wait...

TNSLSNR for Linux: Version 12.1.0.1.0 - Production

System parameter file is /u01/ora_test/12.1.0/network/admin/test_erpnode3/listener.ora

Log messages written to /u01/ora_test/12.1.0/network/admin/test.log

Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=erpnode3.oralabs.com)(PORT=1529)))

Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=erpnode3.oralabs.com)(PORT=1529)))

STATUS of the LISTENER

------------------------

Alias test

Version TNSLSNR for Linux: Version 12.1.0.1.0 - Production

Start Date 20-NOV-2014 08:55:36

Uptime 0 days 0 hr. 0 min. 0 sec

Trace Level off

Security ON: Local OS Authentication

SNMP OFF

Listener Parameter File /u01/ora_test/12.1.0/network/admin/test_erpnode3/listener.ora

Listener Log File /u01/ora_test/12.1.0/network/admin/test.log

Listening Endpoints Summary...

(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=erpnode3.oralabs.com)(PORT=1529)))

Services Summary...

Service "test" has 1 instance(s).

Instance "test", status UNKNOWN, has 1 handler(s) for this service...

The command completed successfully

[oraebs@erpnode3 test_erpnode3]$

3.3 - Application Database accounts Expired& Locked

After successful completion of upgrade we noticed that all database accounts was expired and locked Including APPS, APPLSYS and APPLSYSPUB except "SYS" and "SYSTEM".

This is the default behavior of 12c DBUA and its mentioned in MOS tech note " 1516557.1" in section known Issues. You should not encounter this Issue if you are manually upgrading your database using upgrade script.

As per Oracle documentation and procedure we should change the Application Database account using FNDCPASS utility. As the APPS account is locked and expired it was not allowing to change the password using FNDCPASS utility.

Solution:

- As there was no alternate available then changed the password for APPS using alter command to the same old password.

- Changed password again using FNCPASS utility for APPLSYS and APPLSYSPUB user.

- Changed password for all Application Oracle users

- Run autoconfig on application and database Tiers

Tried login with APPS user:

[oraebs@erpnode3 db_scripts]$ sqlplus

SQL*Plus: Release 12.1.0.1.0 Production on Thu Nov 20 00:23:07 2014

Copyright (c) 1982, 2013, Oracle. All rights reserved.

Enter user-name: apps

Enter password:

ERROR:

ORA-28000: the account is locked

Enter user-name: /as sysdba

Connected to:

Oracle Database 12c Enterprise Edition Release 12.1.0.1.0 - 64bit Production

With the Partitioning, OLAP, Advanced Analytics and Real Application Testing options

SQL> alteruser apps account unlock;

User altered.

SQL>

Check the account Status:

SQL> select username,account_status, lock_date , expiry_date from dba_users where username='APPS';

USERNAME ACCOUNT_ST LOCK_DATE EXPIRY_DA

---------- ---------- --------- ---------

APPS EXPIRED 18-NOV-14

[applebs@erpnode3 sql]$ pwd

/u01/appl_test/fs1/EBSapps/appl/ad/12.0.0/patch/115/sql

[applebs@erpnode3 sql]$ FNDCPASS apps/APPS 0 Y system/manager APPLSYS APPS

APP-FND-01564: ORACLE error 28001 in AFPCOA

Cause: AFPCOA failed due to ORA-28001: the password has expired

.

The SQL statement being executed at the time of the error was: and was executed from the file .

[applebs@erpnode3 sql]$

- Changed password manually for APPS user:

[applebs@erpnode3 sql]$ sqlplus

SQL*Plus: Release 10.1.0.5.0 - Production on Thu Nov 20 09:18:26 2014

Copyright (c) 1982, 2005, Oracle. All rights reserved.

Enter user-name: apps

Enter password:

ERROR:

ORA-28001: the password has expired

Changing password for apps

New password:

Retype new password:

Password changed

Connected to:

Oracle Database 12c Enterprise Edition Release 12.1.0.1.0 - 64bit Production

With the Partitioning, OLAP, Advanced Analytics and Real Application Testing options

SQL>

- In Weblogic admin server APPS password is configured, hence changed password again with FNDCAPSS utility and updated the same password in weblogic admin server datasource.

[applebs@erpnode3 ~]$ FNDCPASS apps/APPS 0 Y system/manager SYSTEM APPLSYS APPS

Log filename : L462324.log

Report filename : O462324.out

[applebs@erpnode3 ~]$

In R12.2 the process for changing the APPS password is same as prior releases with some additional steps in Weblogic Admin Server.

Steps:

• Start Admin server (Do not start any other services/managed servers)
• Log in to Weblogic Server Admin Console
• Click Lock & Edit in Change Center
• In the Domain >expand Services and select Data Sources
• On "Summary of JDBC Data Sources" page > select EBSDataSource
• On the "Settings for EBSDataSource" > select the Connection Pool tab
• Enter the new password
• Click on Save
• Click on Activate Changes in Change Center
• stop admin server
• Run autoconfig on Database Tier and Application Tier

All other Oracle Application schemas accounts are expired and locked. We need to change password for APPLSYSPUB and other schema (like AR, GL) using FNDCPASS ALLORACLE.

- Change password for APPLYSPUB using alter command.

- Change password for all Oracle User using FNDCPASS utility.

[applebs@erpnode3 appl_test]$ FNDCPASS apps/apps 0 Y system/manager ALLORACLE oracle

Log filename : L466353.log

Report filename : O466353.out

[applebs@erpnode3 appl_test]$

- After changing passwords all Application database accounts will now have new password but still these accounts are locked. All these users should be unlocked using alter command.

- Use below SQL command to generate script for altering users which are locked.

- script attached "db_unlock_users.sql"

SQL>select 'alter user '||username||' account unlock;' from dba_users

where ACCOUNT_STATUS='LOCKED';

- As per the procedure we should run autoconfig after changing the password using FNDCPASS. But we will run autoconfig later while enabling autoconfig on 12c Home dbTier.

After successful completion of autconfig on dbTier than run autoconfig on Application Tier.

- Script to unlock Application database accounts:

db_account_unlock.sql

3.4 - Run adgrants.sql

Run "adgrants.sql" script from $APPL_TOP/admin

[oraebs@erpnode3 db_scripts]$ ls

adgrants.sql preupgrd.sql utluppkg.sql

[oraebs@erpnode3 db_scripts]$ mv adgrants.sql adgrants.sql.12.2.0

[oraebs@erpnode3 db_scripts]$ cp /u01/appl_test/fs1/EBSapps/appl/admin/adgrants.sql .

[oraebs@erpnode3 db_scripts]$ ls -lrt

total 596

-rwxr-xr-x 1 oraebs dbaerp 99663 Nov 4 21:11 adgrants.sql.12.2.0

-rw-r--r-- 1 oraebs dbaerp 5231 Nov 14 23:48 preupgrd.sql

-rw-r--r-- 1 oraebs dbaerp 381893 Nov 14 23:53 utluppkg.sql

-rwxr-xr-x 1 oraebs dbaerp 99663 Nov 20 00:14 adgrants.sql

[oraebs@erpnode3 db_scripts]$

SQL>@adgrants.sql APPS

Connected.

---------------------------------------------------

--- adgrants.sql started at 2014-11-20 00:16:02 ---

Creating PL/SQL profiler objects.

PL/SQL procedure successfully completed.

End of PURGE DBA_RECYCLEBIN.

Commit complete.

Disconnected from Oracle Database 12c Enterprise Edition Release 12.1.0.1.0 - 64bit Production

With the Partitioning, OLAP, Advanced Analytics and Real Application Testing options

[oraebs@erpnode3 db_scripts]$

3.5 - Grant create procedure privilege on CTXSYS

Run script "adctxprv.sql" from $AD_TOP/sql by connecting as SYSDBA user

[oraebs@erpnode3 db_scripts]$ cp /u01/appl_test/fs1/EBSapps/appl/ad/12.0.0/patch/115/sql/adctxprv.sql .

[oraebs@erpnode3 db_scripts]$ sqlplus

SQL*Plus: Release 12.1.0.1.0 Production on Thu Nov 20 09:24:00 2014

Copyright (c) 1982, 2013, Oracle. All rights reserved.

Enter user-name: apps

Enter password:

Last Successful login time: Thu Nov 20 2014 09:21:59 +03:00

Connected to:

Oracle Database 12c Enterprise Edition Release 12.1.0.1.0 - 64bit Production

With the Partitioning, OLAP, Advanced Analytics and Real Application Testing options

SQL>@adctxprv.sql manager CTXSYS

Connecting to SYSTEM

Connected.

PL/SQL procedure successfully completed.

Commit complete.

Disconnected from Oracle Database 12c Enterprise Edition Release 12.1.0.1.0 - 64bit Production

With the Partitioning, OLAP, Advanced Analytics and Real Application Testing options

[oraebs@erpnode3 db_scripts]$

3.6 - Compile Invalid Objects

[oraebs@erpnode3 db_scripts]$ sqlplus / as sysdba

SQL*Plus: Release 12.1.0.1.0 Production on Thu Nov 20 09:25:57 2014

Copyright (c) 1982, 2013, Oracle. All rights reserved.

Connected to:

Oracle Database 12c Enterprise Edition Release 12.1.0.1.0 - 64bit Production

With the Partitioning, OLAP, Advanced Analytics and Real Application Testing options

SQL>@$ORACLE_HOME/rdbms/admin/utlrp.sql

3.7 - Set CTXSYS parameter

Execute following procedure with "SYSDBA" account

SQL> exec ctxsys.ctx_adm.set_parameter('file_access_role', 'public');

PL/SQL procedure successfully completed.

SQL>

3.8 - Validate Workflow ruleset

On admin server node, run script "$FND_TOP/patch/115/sql/wfaqupfix.sql" as below:

[applebs@erpnode3 sql]$ pwd

/u01/appl_test/fs1/EBSapps/appl/fnd/12.0.0/patch/115/sql

[applebs@erpnode3 sql]$ ls -lrt wfaqupfix.sql

-rwxr-xr-x 1 applebs dbaerp 4942 Nov 6 18:39 wfaqupfix.sql

[applebs@erpnode3 sql]$ sqlplus

SQL*Plus: Release 10.1.0.5.0 - Production on Thu Nov 20 09:32:35 2014

Copyright (c) 1982, 2005, Oracle. All rights reserved.

Enter user-name: apps

Enter password:

Connected to:

Oracle Database 12c Enterprise Edition Release 12.1.0.1.0 - 64bit Production

With the Partitioning, OLAP, Advanced Analytics and Real Application Testing options

SQL>@wfaqupfix.sql APPLSYS APPS

PL/SQL procedure successfully completed.

Commit complete.

Disconnected from Oracle Database 12c Enterprise Edition Release 12.1.0.1.0 - 64bit Production

With the Partitioning, OLAP, Advanced Analytics and Real Application Testing options

[applebs@erpnode3 sql]$

3.9 - Create context file and run autoconfig on dbTier

In 12c Oracle Home "appsutil" directory doesn’t exists, We have to copy the appsutil directory from 11g Oracle Home to 12c Oracle Home.

§  Run script to generate latest appsutil.zip

§  Copy appsutil directory from 11g Home to 12c Home

§  copy and unzip appsutil.zip in 12c Oracle Home

§  Generate new contextfile using "adbldxml.pl" script

§  Execute adconfig.sh script

[applebs@erpnode3 bin]$ ls -l admkappsutil.pl

-rwxr-xr-x 1 applebs dbaerp 7232 Nov 24 2012 admkappsutil.pl

[applebs@erpnode3 bin]$ perl admkappsutil.pl

Starting the generation of appsutil.zip

Log file located at /u01/appl_test/fs1/inst/apps/test_erpnode3/admin/log/MakeAppsUtil_11200942.log

output located at /u01/appl_test/fs1/inst/apps/test_erpnode3/admin/out/appsutil.zip

MakeAppsUtil completed successfully.

[applebs@erpnode3 bin]$

Copy Existing appsutil directory from 11gR2 Home to 12cR1 Home.

Run script "$AD_TOP/bin/admkapsutil.pl" to generate new appsutil.zip file, It will generate file in $INST_TOP/out directory. Copy this file to 12c Oracle Home and unzip it.

[oraebs@erpnode3 12.1.0]$ cp -pr /u01/ora_test/11.2.0/appsutil .

[oraebs@erpnode3 12.1.0]$ cp /u01/appl_test/fs1/inst/apps/test_erpnode3/admin/out/appsutil.zip .

[oraebs@erpnode3 12.1.0]$ ls -lrt appsutil.zip

-rw-r--r-- 1 oraebs dbaerp 3538270 Nov 20 09:45 appsutil.zip

[oraebs@erpnode3 12.1.0]$

- Unzip file "appsutil.zip" file from 12.1 Home

[oraebs@erpnode3 12.1.0]$ unzip -o appsutil.zip

Archive: appsutil.zip

inflating: appsutil/template/adclobtmp.sql

inflating: appsutil/template/afinit_db112.ora

inflating: appsutil/template/adstrtdb.sql

inflating: appsutil/template/adregtools.drv.........................................

[oraebs@erpnode3 bin]$ perl adbldxml.pl

Starting context file generation for db tier..

Using JVM from /u01/ora_test/12.1.0/appsutil/jre/bin/java to execute java programs..

APPS Password:

The log file for this adbldxml session is located at:

/u01/ora_test/12.1.0/appsutil/log/adbldxml_11200955.log

Could not Connect to the Database with the above parameters, Please answer the Questions below

Enter Hostname of Database server: erpnode3

Enter Port of Database server: 1529

Enter SID of Database server: test

Enter Database Service Name: test

Enter the value for Display Variable: 0.0

The context file has been created at:

/u01/ora_test/12.1.0/appsutil/test_erpnode3.xml

[oraebs@erpnode3 bin]$

- Execute autoconfig on database Tier:

[oraebs@erpnode3 appsutil]$ pwd

/u01/ora_test/12.1.0/appsutil

[oraebs@erpnode3 appsutil]$ cd bin/

[oraebs@erpnode3 bin]$ sh adconfig.sh

Enter the full path to the Context file: /u01/ora_test/12.1.0/appsutil/test_erpnode3.xml

Enter the APPS user password:

The log file for this session is located at: /u01/ora_test/12.1.0/appsutil/log/test_erpnode3/11201009/adconfig.log

AutoConfig is configuring the Database environment...

AutoConfig will consider the custom templates if present.

Using ORACLE_HOME location : /u01/ora_test/12.1.0

Classpath : :/u01/ora_test/12.1.0/jdbc/lib/ojdbc6.jar:/u01/ora_test/12.1.0/appsutil/java/xmlparserv2.jar:/u01/ora_test/12.1.0/appsutil/java:/u01/ora_test/12.1.0/jlib/netcfg.jar:/u01/ora_test/12.1.0/jlib/ldapjclnt12.jar

Using Context file : /u01/ora_test/12.1.0/appsutil/test_erpnode3.xml

Context Value Management will now update the Context file

Updating Context file...COMPLETED

Attempting upload of Context file and templates to database...COMPLETED

Updating rdbms version in Context file to db121

Updating rdbms type in Context file to 64 bits

Configuring templates from ORACLE_HOME ...

AutoConfig completed successfully.

[oraebs@erpnode3 bin]$

- Run autoconfig on appsTier Run &Patch File system:

Execute autconfig on run filesystem by sourcing environmental variables for RUN file system and on patch file system after sourcing environmental variable on patch file system.

Ignore errors encountered while running autoconfig on patch file system.

[applebs@erpnode3 scripts]$ adautocfg.sh

Enter the APPS user password:

The log file for this session is located at: /u01/appl_test/fs1/inst/apps/test_erpnode3/admin/log/11201225/adconfig.log

AutoConfig is configuring the Applications environment...

AutoConfig will consider the custom templates if present.

Using CONFIG_HOME location : /u01/appl_test/fs1/inst/apps/test_erpnode3

Classpath : /u01/appl_test/fs1/FMW_Home/Oracle_EBS-app1/shared-libs/ebsappsborg/WEBINF/lib/ebsAppsborgManifest.jar:/u01/appl_test/fs1/EBSapps/comn/java/classes

Using Context file : /u01/appl_test/fs1/inst/apps/test_erpnode3/appl/admin/test_erpnode3.xml

Context Value Management will now update the Context file

Updating Context file...COMPLETED

Attempting upload of Context file and templates to database...COMPLETED

Configuring templates from all of the product tops...

Configuring AD_TOP........COMPLETED

Configuring FND_TOP.......COMPLETED

Configuring ICX_TOP.......COMPLETED

Configuring MSC_TOP.......COMPLETED

Configuring IEO_TOP.......COMPLETED

...................................

...................................

Configuring GMF_TOP.......COMPLETED

Configuring PON_TOP.......COMPLETED

Configuring FTE_TOP.......COMPLETED

Configuring ONT_TOP.......COMPLETED

Configuring AR_TOP........COMPLETED

Configuring AHL_TOP.......COMPLETED

Configuring IES_TOP.......COMPLETED

Configuring OZF_TOP.......COMPLETED

Configuring CSD_TOP.......COMPLETED

Configuring IGC_TOP.......COMPLETED

AutoConfig completed successfully.

[applebs@erpnode3 scripts]$

3.10 - Run script "adstats.sql" to gather SYS stats

Run script "$APPL_TOP/admin/adstats.sql" as SYSDBA user to gather statistic for sys user. Enable restricted mode before running the script and should be disabled once finished.

[oraebs@erpnode3 db_scripts]$ cd /u01/appl_test/fs1/EBSapps/appl/admin

[oraebs@erpnode3 admin]$ ls -l adstats.sql

-rwxr-xr-x 1 applebs dbaerp 2752 Nov 24 2012 adstats.sql

[oraebs@erpnode3 admin]$ sqlplus / as sysdba

SQL*Plus: Release 12.1.0.1.0 Production on Thu Nov 20 13:53:08 2014

Copyright (c) 1982, 2013, Oracle. All rights reserved.

Connected to:

Oracle Database 12c Enterprise Edition Release 12.1.0.1.0 - 64bit Production

With the Partitioning, OLAP, Advanced Analytics and Real Application Testing options

SQL>alter system enable restricted session;

System altered.

SQL>@adstats.sql

Connected.

-------------------------------------------------

--- adstats.sql started at 2014-11-20 13:53:50 ---

Checking for the DB version and collecting statistics ...

PL/SQL procedure successfully completed.

------------------------------------------------

--- adstats.sql ended at 2014-11-20 14:30:35 ---

Commit complete.

Disconnected from Oracle Database 12c Enterprise Edition Release 12.1.0.1.0 - 64bit Production

With the Partitioning, OLAP, Advanced Analytics and Real Application Testing options

[oraebs@erpnode3 admin]$

[oraebs@erpnode3 ~]$ sqlplus / as sysdba

SQL*Plus: Release 12.1.0.1.0 Production on Thu Nov 20 14:33:18 2014

Copyright (c) 1982, 2013, Oracle. All rights reserved.

Connected to:

Oracle Database 12c Enterprise Edition Release 12.1.0.1.0 - 64bit Production

With the Partitioning, OLAP, Advanced Analytics and Real Application Testing options

SQL>alter system disable restricted session;

System altered.

3.11 - Create new MGDSYS schema

MGDSYS schema was dropped before starting the upgrade. If you're planning to use MGDSYS schema then you should create it again by running script "@?/rdbms/admin/catmgd.sql"

SQL>@?/rdbms/admin/catmgd.sql

.. Creating MGDSYS schema

User created.

.. Granting permissions to MGDSYS

Grant succeeded.

Grant succeeded.

3.12 - Apply post upgrade WMS patches

If upgraded prior version to 12c we have to apply patch "19007053". As we are upgraded from version 11g then we should apply this patch.

[applebs@erpnode3 admin]$adop phase=apply patches=19007053 apply_mode=downtime

3.13 - Recreate grants and synonyms

Using adadmin from Admin server node recreate grants and synonyms for APPS schema:

AD Administration Main Menu

--------------------------------------------------

1. Generate Applications Files menu

2. Maintain Applications Files menu

3. Compile/Reload Applications Database Entities menu

4. Maintain Applications Database Entities menu

5. Exit AD Administration

Enter your choice [5] : 4

Maintain Applications Database Entities

---------------------------------------------------

1. Validate APPS schema

2. Re-create grants and synonyms for APPS schema

3. Maintain multi-lingual tables

4. Check DUAL table

5. Return to Main Menu

- Verify adadmin logfile for Errors.

3.14 - Start Application services

Start Application services using “adstrtal.sh" script and make sure all services started successfully without any errors.

- Login to WLS Admin server and check both Admin and managed servers are working normally.

- Login to Oracle Application and verify all functionalities are working normally.

3.15 - Run concurrent Request "Synchronize workflow views"

Run concurrent request by specifying the following parameters and make sure request completed successfully without any Issues.

3.16 - Verify the upgraded version from OAM

Login to OAM as sysadmin user:

Navigate to system administrator responsibility > sitemap > Monitor > database

4. Issues:

4.1 - Unable to proceed with 12c runInstaller with error "[INS-10102] Installer initialization failed"

Refer:

http://www.toadworld.com/platforms/oracle/b/weblog/archive/2014/11/14/ins-21003-installer-has-detected-that-an-invalid-inventory-pointer-location-file-was-specified-oracle-12c.aspx

4.2 - DBUA not listing the database

This is the fresh Installation of EBS R12.2. File "/etc/oratab" does not contain entry for SID. Hence DBUA was unable to detect SID from 11g Oracle home. Manually add entry in "/etc/oratab" file and rerun dbua.

4.3 - Invalid specification of system parameter "LOCAL_LISTENER"

"ORA-00119: Invalid specification for system parameter LOCAL_LISTENER"

"ORA-00132: syntax error or unresolved network name test_LOCAL"

This Issue occurred due to incorrect configuration of LOCAL_LISTENER parameter in dbua created spfile. This Issue can be avoided by setting the valid parameter of LOCAL_LISTENER in the spfile or by removing this parameter from spfile.

4.4 Application Database account locked after upgrade

After completion of upgrade noticed all database account are locked & Expired including APPS, APPLSYS and APPLSYSPUB except sys and system.

This is a known Issue if database is upgraded using 12c DBUA then it will expire all database accounts except SYS and SYSTEM.

Please refer section "3.3 - Application Database accounts Expired & Locked"