R12.2-Autoconfig-Testmode

 Purpose : How to run autoconfig in test mode in EBS 12.2 Database and Application

Source : https://docs.oracle.com/cd/E26401_01/doc.122/e22953/T174296T589913.htm (Section: Using the check config utility - adchkcfg.sh )

>>>> DB Tier

> Source the run file system environment

cd /u01/install/APPS/12.1.0/ . EBSDB_apps.env

> Navigate to $ORACLE_HOME/appsutil/bin

> Execute the command - ./adchkcfg.sh contextfile=$CONTEXT_FILE

The script generates both HTML and TEXT reports in $ORACLE_HOME/appsutil/out/$CONTEXT_NAME/MONDDHHMI/ directory on Database Tier

The reports contain both the File System Changes and Database Changes

File System Changes :

• Autoconfig Context File Changes
• Service Group Status
• Changed Configuration Files
• New Configuration Files
• Template Customizations

Database Changes :

• Profile Value Changes
• Profile Values
• Other Database Updates

[oracle@apps bin]$ cd $ORACLE_HOME/appsutil/bin

[oracle@apps bin]$

[oracle@apps bin]$ ./adchkcfg.sh contextfile=$CONTEXT_FILE

Enter the APPS password:

The log file for this session is located at: /u01/install/APPS/12.1.0/appsutil/log/EBSDB_apps/06120427/adconfig.log

AutoConfig is running in test mode and building diffs...

AutoConfig will consider the custom templates if present.

        Using ORACLE_HOME location : /u01/install/APPS/12.1.0

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

        Using Context file          : /u01/install/APPS/12.1.0/appsutil/out/EBSDB_apps/06120427/EBSDB_apps.xml

Context Value Management will now update the test Context file

        Updating test Context file...COMPLETED

        [ Test mode ]

        No uploading of Context File and its templates to database.

Updating rdbms version in Context file to db121

Updating rdbms type in Context file to 64 bits

Testing templates from ORACLE_HOME ...

Differences text report is located at: /u01/install/APPS/12.1.0/appsutil/out/EBSDB_apps/06120427/cfgcheck.txt

        Generating Profile Option differences report...COMPLETED

Differences text report for the Database is located at: /u01/install/APPS/12.1.0/appsutil/out/EBSDB_apps/06120427/ProfileReport.txt

        Generating File System differences report......COMPLETED

Differences html report is located at: /u01/install/APPS/12.1.0/appsutil/out/EBSDB_apps/06120427/cfgcheck.html

Differences Zip report is located at: /u01/install/APPS/12.1.0/appsutil/out/EBSDB_apps/06120427/ADXcfgcheck.zip

AutoConfig completed successfully.

[oracle@apps bin]$

=========================================================================

>>>> Application Tier

> Source the run file system environment

> Navigate to $AD_TOP/bin

> Execute the command - ./adchkcfg.sh contextfile=$CONTEXT_FILE

The script generates both HTML and TEXT reports in $INST_TOP/admin/out/MONDDHHMI/ directory on Application Tier

[oracle@apps ~]$ cd /u01/install/APPS [oracle@apps APPS]$ . EBSapps.env RUN E-Business Suite Environment Information ---------------------------------------- RUN File System : /u01/install/APPS/fs1/EBSapps/appl PATCH File System : /u01/install/APPS/fs2/EBSapps/appl Non-Editioned File System : /u01/install/APPS/fs_ne DB Host: apps.example.com Service/SID: EBSDB Sourcing the RUN File System ... [oracle@apps APPS]$ cd $AD_TOP/bin [oracle@apps bin]$ ./adchkcfg.sh contextfile=$CONTEXT_FILE Enter the APPS password: The log file for this session is located at: /u01/install/APPS/fs1/inst/apps/EBSDB_apps/admin/log/06120432/adconfig.log wlsDomainName: EBS_domain WLS Domain Name is VALID. AutoConfig is running in test mode and building diffs... AutoConfig will consider the custom templates if present. Using CONFIG_HOME location : /u01/install/APPS/fs1/inst/apps/EBSDB_apps Classpath : /u01/install/APPS/fs1/FMW_Home/Oracle_EBS-app1/shared-libs/ebs-appsborg/WEB-INF/lib/ebsAppsborgManifest.jar:/u01/install/APPS/fs1/EBSapps/comn/java/classes Using Context file : /u01/install/APPS/fs1/inst/apps/EBSDB_apps/admin/out/06120432/EBSDB_apps.xml Context Value Management will now update the test Context file Updating test Context file...COMPLETED [ Test mode ] No uploading of Context File and its templates to database. Testing templates from all of the product tops... Testing AD_TOP........COMPLETED Testing FND_TOP.......COMPLETED Testing ICX_TOP.......COMPLETED Testing MSC_TOP.......COMPLETED Testing IEO_TOP.......COMPLETED Testing BIS_TOP.......COMPLETED Testing CZ_TOP........COMPLETED Testing SHT_TOP.......COMPLETED Testing AMS_TOP.......COMPLETED Testing CCT_TOP.......COMPLETED Testing WSH_TOP.......COMPLETED Testing CLN_TOP.......COMPLETED Testing OKE_TOP.......COMPLETED Testing OKL_TOP.......COMPLETED Testing OKS_TOP.......COMPLETED Testing CSF_TOP.......COMPLETED Testing IBY_TOP.......COMPLETED Testing JTF_TOP.......COMPLETED Testing MWA_TOP.......COMPLETED Testing CN_TOP........COMPLETED Testing CSI_TOP.......COMPLETED Testing WIP_TOP.......COMPLETED Testing CSE_TOP.......COMPLETED Testing EAM_TOP.......COMPLETED Testing GMF_TOP.......COMPLETED Testing PON_TOP.......COMPLETED Testing FTE_TOP.......COMPLETED Testing ONT_TOP.......COMPLETED Testing AR_TOP........COMPLETED Testing AHL_TOP.......COMPLETED Testing IES_TOP.......COMPLETED Testing OZF_TOP.......COMPLETED Testing CSD_TOP.......COMPLETED Testing IGC_TOP.......COMPLETED Differences text report is located at: /u01/install/APPS/fs1/inst/apps/EBSDB_apps/admin/out/06120432/cfgcheck.txt Generating Profile Option differences report...COMPLETED Differences text report for the Database is located at: /u01/install/APPS/fs1/inst/apps/EBSDB_apps/admin/out/06120432/ProfileReport.txt Generating File System differences report......COMPLETED Differences html report is located at: /u01/install/APPS/fs1/inst/apps/EBSDB_apps/admin/out/06120432/cfgcheck.html Differences Zip report is located at: /u01/install/APPS/fs1/inst/apps/EBSDB_apps/admin/out/06120432/ADXcfgcheck.zip AutoConfig completed successfully. [oracle@apps bin]$

Background Media Recovery terminated with ORA-1274 after adding a Datafile

Symptom : Recently I got error in alert log of DR database like :-

Managed Standby Recovery not using Real Time Apply
MRP0: Background Media Recovery terminated with error 1111
Errors in file /ora/visprod/home/product/11.2.0/log/diag/rdbms/visprodr/VISPRODR/trace/VISPRODR_pr00_25255.trc:
ORA-01111: name for data file 286 is unknown - rename to correct file
ORA-01110: data file 286: '/ora/visprod/home/product/11.2.0/dbs/UNNAMED00286'
ORA-01157: cannot identify/lock data file 286 - see DBWR trace file
ORA-01111: name for data file 286 is unknown - rename to correct file
ORA-01110: data file 286: '/ora/visprod/home/product/11.2.0/dbs/UNNAMED00286'
Slave exiting with ORA-1111 exception
Errors in file /ora/visprod/home/product/11.2.0/log/diag/rdbms/visprodr/VISPRODR/trace/VISPRODR_pr00_25255.trc:
ORA-01111: name for data file 286 is unknown - rename to correct file
ORA-01110: data file 286: '/ora/visprod/home/product/11.2.0/dbs/UNNAMED00286'
ORA-01157: cannot identify/lock data file 286 - see DBWR trace file
ORA-01111: name for data file 286 is unknown - rename to correct file
ORA-01110: data file 286: '/ora/visprod/home/product/11.2.0/dbs/UNNAMED00286'
Recovery Slave PR00 previously exited with exception 1111
MRP0: Background Media Recovery process shutdown (VISPRODR)

Reason :- Datafile was added on Prod on one mount point, on DR site there was no space left out so newly added datafile went to $ORACLE_HOME/dbs/UNNAMED00286 name. This stop archivelog to apply on DR database and if we try to start MRP process, it failed to start.

Solution: - 

1. Shutdown DR database.

2. Change pfile parameter "Standy_file_management" and set to MANUAL.

3. Mount DR with pfile.

4.  alter database create datafile '/ora/visprod/home/product/11.2.0/dbs/UNNAMED00286' as 'New FileName';

5.Shutdown DR database. 

6. Change again "Standy_file_management" to Auto

7. Start DR on Mount. 

8. Start MRP process. 

Now Archive will start applying.

How to compile invalid objects

UTL_RECOMP

This script is particularly useful after a major-version upgrade that typically invalidates all PL/SQL and Java objects. Although invalid objects are recompiled automatically on use, it is useful to run this script prior to operation because this will either eliminate or minimize subsequent latencies due to on-demand automatic recompilation at runtime.

Parallel recompilation can exploit multiple CPUs to reduce the time taken to recompile invalid objects. The degree of parallelism is specified by the first argument to RECOMP_PARALLEL Procedure.

In general, a parallelism setting of one thread for each available CPU provides a good initial setting. However, please note that the process of recompiling an invalid object writes a significant amount of data to system tables and is fairly I/O intensive. A slow disk system may be a significant bottleneck and limit speedups available from a higher degree of parallelism.

Examples

Recompile all objects sequentially:

EXECUTE UTL_RECOMP.RECOMP_SERIAL();

Recompile objects in schema SCOTT sequentially:

EXECUTE UTL_RECOMP.RECOMP_SERIAL('SCOTT');

Recompile all objects using 4 parallel threads:

EXECUTE UTL_RECOMP.RECOMP_PARALLEL(4);

Recompile objects in schema JOE using the number of threads specified in the parameter JOB_QUEUE_PROCESSES:

EXECUTE UTL_RECOMP.RECOMP_PARALLEL(NULL, 'JOE');

Another simple method is to use utlrp.sql command located in $ORACLE_HOME/rdbms/admin

 

sqlplus "/as sysdba"

sqlplus >@$ORACLE_HOME/rdbms/admin/utlrp.sql;

How to restore archive logs from rman backup

If some one need archive log to extract on disk for various purpose (cloning/Apply to DR) then we can follow below mention steps. For example purpose I will extract required archive log in /usr/tmp location. If we do not mention location the archive will be extracted to default location i.e $IRACLE_HOME/dbs

Step 1. Connect to rman (Target or catalog)

rman target /

 

Step 2. Example to restore 10 archive log from logseq 112710 to 112720

run
{
set archivelog destination to '/usr/tmp';
restore archivelog from logseq=112710 until logseq=112720 thread 1;
}

Other examples:-

1. Restore single archive log
 

run
{
set archivelog destination to '/usr/tmp';
restore archivelog from logseq=112710  thread 1;
}

2. Restore archive log in RAC environment 

If we want to restore archive log from Node 2 RAC then user thread 2, or use thread 1 for Node 1.

 

run
{
set archivelog destination to '/usr/tmp';
restore archivelog from logseq=112710 until logseq=112720 thread 2;
}

How to change Apps Password in R12.2

Apps password change routine in Release 12.2 E-Business Suite changed a little bit. We have now extra options to change password, as well as some manual steps after changing the password using FNDCPASS.

Whether you use FNDCPASS or AFPASSWD to change the APPLSYS/APPS password, you must also perform some additional steps. This is because in R12.2, the old AOL/J connection pooling is replaced with Weblogic Connection Pool ( JDBC Datasource ).  Currently this procedure is not yet automated. It would be good, if this can be automated using some WLS scripting.

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

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

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

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

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

1.   Log in to WLS Administration Console.

2.   Click Lock & Edit in Change Center.

3.   In the Domain Structure tree, expand Services, then select Data Sources.

4.   On the "Summary of JDBC Data Sources" page, select EBSDataSource.

5.   On the "Settings for EBSDataSource" page, select the Connection Pool tab.

6.   Enter the new password in the "Password" field.

7.   Enter the new password in the "Confirm Password" field.

8.   Click Save.

9.   Click Activate Changes in Change Center.

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

6.   Verify the WLS Datastore changes as follows:

1.   Log in to WLS Administration Console.

2.   In the Domain Structure tree, expand Services, then select Data Sources.

3.   On the "Summary of JDBC Data Sources" page, select EBSDataSource.

4.   On the "Settings for EBSDataSource" page, select Monitoring > Testing.

5.   Select "oacore_server1".

6.   Click Test DataSource

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

How to apply HRGLOBAL in R12.2

Step 1 -Apply hrglobal.drv

There are some changes to apply HRGLOBAL in R12.2 w.r.t previous EBS version. We need to apply hrglobal same as adop patch life cycle. Steps are as below mention.

a) Start an online patching cycle
Source the run edition environment file: Example: UNIX: $RUN_BASE/EBSapps/appl/APPS$CONTEXT_NAME.env

$ adop phase=prepare

b) Run DataInstall from PATCH edition

The command line DataInstall java utility should be run on the tier which has the $APPL_TOP available. It will perform view creation actions against the database pertaining to the options selected. For multi-node/RAC setups, DataInstall need only to be run on the primary node.

Run the DataInstall java utility in order to select the legislations you want to apply as follows:

java oracle.apps.per.DataInstall <un> <pw> thin <host:port: sid >

where

< un > is the username of the main apps account
<pw> is the password for this account
<host:port: sid > represents the database connection information

For example: java oracle.apps.per.DataInstall apps apps thin dbsvr1:1521:testdb

12.2 SPECIFIC: For an Online patch enabled instance, DataInstall will only be runnable against the Patch Edition (Environment is prepared using "adop phase=prepare").
In order to retain the same command line usage from previous codelines, if the connect information passed to the DataInstall utility points to the Run Edition, then DataInstall will internally switch to operate against the Patch Edition.
Aside from this scenario, or for environments that are not Online patch enabled, DataInstall will operate exactly as before.

RUP Upgrade best practice:
On upgrade to a newer RUP, it is advised to apply all live localisations and Core (even if no new prereqs are listed).
For customers running non supported localisations, they should install just Core on RUP upgrade

Usage of DataInstall is fairly straightforward, basically select/deselect legislations to install using the index number of the legislation shown in the list in menu 1 followed by I for install or C for clear;
e.g. In menu 1, to install Global choose 1I, to cancel a selected operation, choose 1C etc. Menu 4 to choose to save your changes when you are OK with them.

c) Apply hrglobal.drv

The driver is located at $PER_TOP/patch/115/driver/hrglobal.drv and should be run on the tier which has the $APPL_TOP available. In most cases this will be the Apps tier.
hrglobal.drv is a pure "database, d type" driver so the actions in the driver apply only to the database. As such, for RAC/multi-node setups, it is only required to run the hrglobal.drv on one node. Be mindful to only run the driver located in the directory $PER_TOP/patch/115/driver hrglobal.drv driver should be applied as per a normal patch using the adop utility.

12.2 SPECIFIC: The driver will be applied via the adop patcing utility, as opposed to adpatch which was used prior to 12.2.

Care must be taken when applying hrglobal.drv via adop that the following parameters are passed with the adop command line:

options=nocopyportion,nogenerateportion,forceapply

Example: adop phase=apply patchtop=$PER_TOP/patch/115 patches=driver:hrglobal.drv options=nocopyportion,nogenerateportion,forceapply
where $PER_TOP corresponds to the patch file system

These options are mandatory in order to
a) avoid adop trying to sync the file system when applying a patch (in this case the hrglobal.drv file) that contains database operations only and
b) ensure that adop will not consider during an upgrade to have been installed previously and proceed with the current request.
Please also ensure the forceapply parameter is at the end of the options list.

Note:
- adop apply phase by default runs in autoskip mode, meaning that if there is failure, it will be skipped and the failed file will be mentioned in the autoskip.log
- users wont see the failures on the screen where the adop command is running
- users need to review the autoskip.log file after the completion of hrglobal to find any failed files which are skipped and take appropriate action

Once completed and no issues are reported in the autoskip.log file, you have successfully installed your legislative HRMS data.

d) Complete the online patching cycle by running the following commands in the order shown:

1. $ adop phase=finalize
2. $ adop phase=cutover
3. $ adop phase=cleanup

Step 2 - OPTIONAL

For customers using other languages than US and wishing to apply translated legislative seed data, please apply the relevant language specific version of the consolidated translation patch after successfully completing the hrglobal.drv above.