elcarOnOsdnaH: June 2012

Sunday, June 17, 2012

OEM Grid Agent Re-sync with repository fails

Scenario -
You have installed the new Agent or re-installed the agent on the same host and deleted the target host configured by old agent from OEM Console
OR
After unblocking the agents when re-sync is tried, it fails with errors.

Error –

Agent Operation completed with errors. For those targets that could not be saved, please go to the target's monitoring configuration page to save them. All other targets have been saved successfully. Agent has not been unblocked.

Internal Repository Error Message: SQL Exception occured while syncing pdp settings | Exception: java.sql.SQLException: ORA-20206: Target does not exist: racnode1.localdomain:host
ORA-06512: at "SYSMAN.MGMT_TARGET", line 571 ORA-06512: at "SYSMAN.MGMT_CREDENTIALS_UI", line 303 ORA-06512: at line 1

[oracle@racnode1 emd]$ /u01/app/oracle/product/agent/agent11g/bin/emctl stop agent
Oracle Enterprise Manager 11g Release 1 Grid Control 11.1.0.1.0
Copyright (c) 1996, 2010 Oracle Corporation. All rights reserved.
Stopping agent ... stopped.

Cause –
Agent is reinstalled on the host. However, the HOST target has not been discovered by the Agent. The Repository is trying to push the details that it knows about the Host target, but this target no longer exists at the Agent side. Due to this, the Agent Re-synchronization does not complete

Solution –

1) Delete the Agent target from the Grid Console: Targets -> All Targets -> Search: Agent -> Go.
Click on the link for the Agent: agentmachine.domain:3872 -> Click Remove -> Confirm the deletion.

2) Recreate the targets.xml file with the Values from /u01/app/oracle/product/11.1.0/agent11g/sysman/config/emd.properties for targets.xml

agentSeed=852592608
EMD_URL=https://racnode1:3872/emd/main/

-- Backup the old targets.xml file and create new one.
#vi /u01/app/oracle/product/agent11g/sysman/emd/targets.xml

<Targets AGENT_SEED="852592608">
<Target TYPE="oracle_emd" NAME="racnode1:3872"/>
<Target TYPE="host" NAME="racnode1"/>
</Targets>
Save and exit.

-- Now do the manual discovery using AGENTCA Utility.

[oracle@racnode1 emd]$ /u01/app/oracle/product/11.1.0/agent11g/bin/agentca -d

Stopping the agent using /u01/app/oracle/product/11.1.0/agent11g/bin/emctl stop agent
Oracle Enterprise Manager 11g Release 1 Grid Control 11.1.0.1.0
Copyright (c) 1996, 2010 Oracle Corporation. All rights reserved.
Agent is Not Running
Running agentca using /u01/app/oracle/product/agent11g/oui/bin/runConfig.sh ORACLE_HOME=/u01/app/oracle/product/a ACTION=Configure MODE=Perform RESPONSE_FILE=/u01/app/oracle/product/agent11g/response_file RERUN=TRUE INV_PTR_LOC=/u01/cle/product/agent11g/oraInst.loc
COMPONENT_XML={oracle.sysman.top.agent.10_2_0_1_0.xml}
Perform - mode is starting for action: Configure

Perform - mode finished for action: Configure

-- Next, one has to secure the agent with OMS

[oracle@racnode1 emd]$ /u01/app/oracle/product/11.1.0/agent11g/bin/emctl secure agent
Oracle Enterprise Manager 11g Release 1 Grid Control 11.1.0.1.0
Copyright (c) 1996, 2010 Oracle Corporation. All rights reserved.
Agent is already stopped...   Done.
Securing agent...   Started.
Enter Agent Registration Password :
Securing agent...   Successful.

-- Start the agent.

[oracle@racnode1 emd/u01/app/oracle/product/11.1.0/agent11g/bin/emctl start agent
Oracle Enterprise Manager 11g Release 1 Grid Control 11.1.0.1.0
Copyright (c) 1996, 2010 Oracle Corporation. All rights reserved.
Starting agent ..... started.

-- Check the status of the agent.

Friday, June 15, 2012

Upgrade Oracle E-Business Suite from R12.1.2 to R12.1.3

Reference -

Oracle E-Business Suite Applications Technology Readme for Release 12.1.3 (R12.ATG_PF.B.delta.3,Patch 8919491) (Doc ID 1066312.1)

I’m going to divide the whole patching process into three diff parts for better understanding and manageability. It will be good idea to apply the pre-req patches in one cycle and then keep systems running for some time to make sure you don’t have any adverse effects of the patches applied. Also, it is recommended you do at-least two cycle of patching on your test environments before proceeding with same to Prod gear.

1. Pre-req patches pre 12.1.3 patches ( this patches are to be applied on IAS & Forms n Reports Server )

2. Apply 12.1.3 patches

3. Post patch process (some more patches)

1. Pre-req patches

n Make sure your current release is on 12.1.2

SQL> select release_name from apps.fnd_product_groups;

RELEASE_NAME

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

12.1.2

Before Applying Oracle E-Business Suite Applications Technology Release 12.1.3

(R12.ATG_PF.B.delta.3) , please refer Document 761570.1 thoroughly to ensure that all patches for your specific database release are applied on the environment before you upgrade to Oracle E-Business Suite Applications Technology Release 12.1.3 (R12.ATG_PF.B.delta.3).

As per the patch document one needs to apply following patches on your respective IAS or forms n reports server. Please check patch readme file and check where the patch needs to applied.

Imp Note - Before starting with patching one need to check the IAS version of their env. IAS version should be 10.1.3.5 before one can apply 12.1.3 patches. One can schedule the upgrade of IAS before or after the application of the pre-req patches.

I chose to do it before.

To follow the detailed guidelines on how to upgrade IAS from 10.1.3.4 to 10.1.3.5 pls check the following post

http://handsonoracle.blogspot.in/2012/06/upgrade-oracle-iashttp-server-from-10.html

Result of the checks in my environment is as follows

9295268 - Needs to apply

7121788 - Needs to apply

6995251 - Needs to apply

8528194 - Needs to apply

6857221 - Already applied

4407272 - Already applied

4526825 - Already applied

7329300 - Already applied

8557019 - Needs to apply

9084276 - Needs to apply

8940272 - Needs to apply

8947375 - Needs to apply

6998181 - Needs to apply

9357237 - Needs to apply

7552880 - Needs to apply

7016961 - Already applied

5917053 - Already applied

6371228 - Already applied

6497684 - Needs to apply

7426842 - Needs to apply

7140392 - Needs to apply

8300196 - Already applied

8602992 - Needs to apply

8919489 - Needs to apply

Download the patches you need to apply from My Oracle Support and check the readme of the each patch to find out application process.

MAKE SURE YOU SOURCE PROPER OPATCH FOR RESPECTIVE HOME

[oracle@appsnode 9295268]$ export PATH=$PATH:/u01/app/oracle/visr12/apps/tech_st/10.1.2/OPatch

[oracle@appsnode 9295268]$ opatch apply

Backing up comps.xml ... OPatch detected non-cluster Oracle Home from the inventory and will patch the local system only. Please shut down Oracle instances running out of this ORACLE_HOME (Oracle Home = /u01/app/oracle/visr12/apps/tech_st/10.1.2)

Is this system ready for updating? Please respond Y|N > Y Rolling back patch 7229760...

Creating log file "/u01/app/oracle/visr12/apps/tech_st/10.1.2/.patch_storage/7229760/RollBack_7229760_06-04-2012_09-31-29.log"

Inventory is good and does not have any dangling patches.

Updating inventory...

Verifying patch...

Backing up comps.xml ...

OPatch succeeded.

[oracle@appsnode 9295268]$ opatch lsinventory | grep 9295268

Patch 9295268 applied on Mon Jun 04 09:31:51 GMT+05:30 2012

[oracle@appsnode 6995251]$ opatch apply

Oracle Interim Patch Installer version 1.0.0.0.64

Oracle recommends you to use the latest OPatch version

and read the OPatch documentation available in the OPatch/docs

directory for usage. For information about the latest OPatch and

Updating inventory...

Verifying patch...

Backing up comps.xml ...

OPatch succeeded.

[oracle@appsnode 8528194]$ opatch apply

Oracle Interim Patch Installer version 1.0.0.0.64

Oracle recommends you to use the latest OPatch version

and read the OPatch documentation available in the OPatch/docs

Verifying patch...

Backing up comps.xml ...

OPatch succeeded.

[oracle@appsnode pre-req-patches]$ opatch lsinventory | grep 6857221

19) Patch 6857221 applied on Thu Mar 26 13:22:08 GMT+05:30 2009

[ Bug fixes: 6857221 ]

[oracle@appsnode pre-req-patches]$ opatch lsinventory | grep 4407272

18) Patch 4407272 applied on Thu Mar 26 13:24:27 GMT+05:30 2009

[ Bug fixes: 4407272 ]

[oracle@appsnode pre-req-patches]$ opatch lsinventory | grep 4526825

17) Patch 4526825 applied on Thu Mar 26 13:27:27 GMT+05:30 2009

[ Bug fixes: 4526825 ]

[oracle@appsnode pre-req-patches]$ opatch lsinventory | grep 7329300

6) Patch 7329300 applied on Thu Mar 26 13:58:46 GMT+05:30 2009

[ Bug fixes: 7329300 ]

[oracle@appsnode 8557019]$ opatch apply

Oracle Interim Patch Installer version 1.0.0.0.64

Applying patch 8557019...

Updating inventory...

Verifying patch...

Backing up comps.xml ...

OPatch succeeded.

[oracle@appsnode 9084276]$ opatch apply

Oracle Interim Patch Installer version 1.0.0.0.64

Applying patch 9084276...

Updating inventory...

Verifying patch...

Backing up comps.xml ...

OPatch succeeded.

[oracle@appsnode 8940272]$ opatch apply

Oracle Interim Patch Installer version 1.0.0.0.64

Applying patch 8940272...

Patching archive files...

Running make for target sharedlib.

Running make for target install.

Inventory is good and does not have any dangling patches.

Updating inventory...

Verifying patch...

Backing up comps.xml ...

OPatch succeeded.

[oracle@appsnode 8947375]$ opatch apply

Oracle Interim Patch Installer version 1.0.0.0.64

Applying patch 8947375...

Patching archive files...

Running make for target sharedlib.

Running make for target install.

Inventory is good and does not have any dangling patches.

Updating inventory...

Verifying patch...

Backing up comps.xml ...

OPatch succeeded.

[oracle@appsnode 6998181]$ opatch apply

Oracle Interim Patch Installer version 1.0.0.0.64

Applying patch 6998181...

Patching archive files...

Running make for target sharedlib.

Updating inventory...

Verifying patch...

Backing up comps.xml ...

OPatch succeeded.

[oracle@appsnode 9357237]$ opatch napply

Oracle Interim Patch Installer version 1.0.0.0.64

The fixes for Patch 8447875, are included in the patch currently

being installed (8447875). OPatch will roll back the subset patch(es) and

install the new patch (8447875).

Backing up comps.xml ...

OPatch detected non-cluster Oracle Home from the inventory and will patch the local system only.

Please shut down Oracle instances running out of this ORACLE_HOME

(Oracle Home = /u01/app/oracle/visr12/apps/tech_st/10.1.2)

Is this system ready for updating?

Please respond Y|N >

OPatch succeeded.

OPatch is going to apply the patch "/home/oracle/1213Patches/pre-req-patches/9357237/9352208".

Do you want to proceed?

Please respond Y|N >

Patch(es) 7379122, conflict with the patch currently being installed (9352208).

If you continue, patch(es) 7379122, will be rolled back and the new patch (9352208) will be installed.

Rolling back patch 7379122...

OPatch succeeded.

OPatch is going to apply the patch "/home/oracle/1213Patches/pre-req-patches/9357237/9357234".

Do you want to proceed?

Please respond Y|N > Y

Verifying patch...

Backing up comps.xml ...

OPatch succeeded.

[oracle@appsnode 7552880]$ opatch apply

Oracle Interim Patch Installer version 1.0.0.0.64

Verifying patch...

Backing up comps.xml ...

OPatch succeeded.

[oracle@appsnode 6497684]$ opatch apply

Oracle Interim Patch Installer version 1.0.0.0.64

MISSING_COMPONENT : oracle.developer.forms, 10.1.2.2.1 (found a component with higher version)

This Oracle Home does not have components/versions required by the patch.

ERROR: OPatch failed during prerequisite check.

Patch - 7426842

Note – As per MOS, this patch has been classified as an obsolete patch hence one can avoid it safely.

Bug 7426842 has been replaced by new bug 11780669

[oracle@appsnode 7140405]$ opatch apply

Oracle Interim Patch Installer version 1.0.0.0.64

Removing patch 7140405...

Restoring jar files...

Updating inventory...

Back to applying patch 7140405...

Verifying patch...

Backing up comps.xml ...

OPatch succeeded.

[oracle@appsnode 7140405]$ opatch lsinventory | grep 8300196

14) Patch 8300196 applied on Thu Mar 26 14:02:55 GMT+05:30 2009

[ Bug fixes: 8300196 ]

[oracle@appsnode 8602992]$ opatch apply

Oracle Interim Patch Installer version 1.0.0.0.64

Verifying patch...

Backing up comps.xml ...

OPatch succeeded.

[oracle@appsnode 8919489]$

[oracle@appsnode 8919489]$ adpatch defaultsfile=/u01/app/oracle/visr12/apps/apps_st/appl/admin/visr12/adalldefaults.txt driver=u8919489.drv logfile=patch_8919489.log workers=4

Done purging timing information for prior sessions.

AutoPatch is complete.

The 8919489 patch requires the 9583541 patch as part of post patch process. So one has to apply it as follows....

[oracle@appsnode 9583541]$ adpatch defaultsfile=/u01/app/oracle/visr12/apps/apps_st/appl/admin/visr12/adalldefaults.txt driver=u9583541.drv logfile=patch_9583541.log workers=4

Enter the directory where your Oracle Applications patch has been unloaded

The default directory is [/home/oracle/1213Patches/pre-req-patches/9583541] :

AutoPatch is complete.

[oracle@appsnode bin]$ perl ./admkappsutil.pl

Starting the generation of appsutil.zip

Log file located at /u01/app/oracle/visr12/inst/apps/visr12_appsnode/admin/log/MakeAppsUtil_06050540.log

output located at /u01/app/oracle/visr12/inst/apps/visr12_appsnode/admin/out/appsutil.zip

[oracle@appsnode bin]$ cd /u01/app/oracle/visr12/inst/apps/visr12_appsnode/admin/out/

[oracle@appsnode out]$ ll -ltr

-rw-r--r-- 1 oracle oinstall 2796794 Jun 5 05:40 appsutil.zip

ON DB Side –

[oracle@appsdbnode ~]$ cd /u01/app/oracle/visr12/db/tech_st/11.1.0/

[oracle@appsdbnode 11.1.0]$ . ./visr12_appsdbnode.env

[oracle@appsdbnode 11.1.0]$ mv appsutil appsutil.old

[oracle@appsdbnode 11.1.0]$ unzip appsutil.zip

-- Start the apps stack and check the history from Apps console

[oracle@appsnode 1213Patches]$ /u01/app/oracle/visr12/inst/apps/visr12_appsnode/admin/scripts/adstrtal.sh apps/apps

2. Apply 12.1.3 patches

Oracle Applications DBA 12.1.3 Product Release Update Pack

Update - 9239089

Pre-install Tasks

On Apps Node -

[oracle@appsnode 1213Patches]$ cd 9239089/

[oracle@appsnode 9239089]$ cd admin/

[oracle@appsnode admin]$ scp adgrants.sql appsdbnode:/u01/app/oracle/visr12/db/tech_st/11.1.0/appsutil/admin

adgrants.sql 100% 52KB 51.8KB/s 00:00

On DB Node -

[oracle@appsdbnode admin]$ sqlplus /nolog

SQL*Plus: Release 11.1.0.7.0 - Production on Tue Jun 5 05:58:34 2012

SQL> @adgrants.sql apps

Connected.

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

Commit complete.

Apply patch

This patch contains the following unified driver file to be applied with

AutoPatch: u9239089.drv (This is the unified driver)

[oracle@appsnode 9239089]$ adpatch defaultsfile=/u01/app/oracle/visr12/apps/apps_st/appl/admin/visr12/adalldefaults.txt driver=u9239089.drv logfile=patchapply_9239089.log workers=4

The default directory is [/home/oracle/1213Patches/9239089] :

Purging timing information for prior sessions.

sqlplus -s APPS/***** @/u01/app/oracle/visr12/apps/apps_st/appl/ad/12.0.0/sql/adtpurge.sql 10 1000

Done purging timing information for prior sessions.

AutoPatch is complete.

Apply 8919491 Patch -

[oracle@appsnode 8919491]$ adpatch defaultsfile=/u01/app/oracle/visr12/apps/apps_st/appl/admin/visr12/adalldefaults.txt driver=u8919491.drv logfile=patchapply_u8919491.log workers=4 patchtop=/home/oracle/1213Patches/8919491

An error occurred while relinking application programs.

Continue as if it were successful [No] :Yes

There are now 355 jobs remaining (current phase=A3):

0 running, 6 ready to run and 349 waiting.

Assigned: file bnesdk.odf on worker 1 for product bne username BNE.

Assigned: file afflex.odf on worker 2 for product fnd username APPLSYS.

Assigned: file afoam.odf on worker 3 for product fnd username APPLSYS.

Assigned: file fnd_cp_delivery_options.xdf on worker 4 for product fnd username APPS.

Completed: file bnesdk.odf on worker 1 for product bne username BNE.

Assigned: file fnd_soa_log_category.xdf on worker 1 for product fnd username APPS.

Completed: file afoam.odf on worker 3 for product fnd username APPLSYS.

Assigned: file fnd_soa_request.xdf on worker 3 for product fnd username APPS.

Completed: file afflex.odf on worker 2 for product fnd username APPLSYS.

Done running SQL scripts and EXEC commands.

Compiling invalid objects...

sqlplus -s APPS/***** @/u01/app/oracle/visr12/apps/apps_st/appl/ad/12.0.0/sql/adutlrcmp.sql APPLSYS ***** APPS ***** ***** 4 0 NONE FALSE

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

sqlplus -s APPS/***** @/u01/app/oracle/visr12/apps/apps_st/appl/ad/12.0.0/sql/adtpurge.sql 10 1000

Connected.

Done purging timing information for prior sessions.

AutoPatch is complete.

12.1.3:11GCS AND FNDCPASS USER EXIT MERGE CONSOLIDATION PATCH

Update - 12964564

[oracle@appsnode 12964564]$ adpatch defaultsfile=/u01/app/oracle/visr12/apps/apps_st/appl/admin/visr12/adalldefaults.txt logfile=patchapply_12964564.log driver=u12964564.drv patchtop=/home/oracle/1213Patches/12964564 workers=4

Purging timing information for prior sessions.

sqlplus -s APPS/***** @/u01/app/oracle/visr12/apps/apps_st/appl/ad/12.0.0/sql/adtpurge.sql 10 1000

Done purging timing information for prior sessions.

AutoPatch is complete

BTW, during this patch I Hit the following error during execution –

/u01/applprod/prod/apps/apps_st/appl/fem/12.0.0/lib/libfem.a(FCMathExecOp.o)

collect2: ld returned 1 exit status

make: *** [/u01/applprod/prod/apps/apps_st/appl/fem/12.0.0/bin/FEMCCE] Error 1

Done with link of fem executable 'FEMCCE

Solution –

["Relink Of Module Femcce Failed" R12 Errors On Oracle Enterprise Linux 5.2 or Red Hat 5.2 [ID 751250.1] ]

The following i386 packages are not part of the OS distribution media and must be downloaded separately (from http://oss.oracle.com/projects/compat-oracle/files/Enterprise_Linux for both OEL 5 and RHEL 5) and installed manually:

openmotif21-2.1.30-11.EL5.i3861

xorg-x11-libs-compat-6.8.2-1.EL.33.0.1.i386

binutils-2.17.50.0.6-6.0.1.i3862

[root@appsnode ~]# rpm -qa | grep binutils

binutils-2.17.50.0.6-14.el5

[root@appsnode oracle]# rpm -Uvh --oldpackage binutils-2.17.50.0.6-6.0.1.el5.i386.rpm

Preparing... ########################################### [100%]

1:binutils ########################################### [100%]

[root@appsnode oracle]# rpm -qa | grep binutils

binutils-2.17.50.0.6-6.0.1.el5

3. Post Install Patches

Apply post-install Oracle E-Business Suite Applications Technology patches. (Required)

Apply the following mandatory patches:

9817770:R12.ATG_PF.B (POST-R12.ATG_PF.B.DELTA.3 CONSOLIDATED PATCH), Patch 9817770

[oracle@appsnode 9817770]$ adpatch defaultsfile=/u01/app/oracle/visr12/apps/apps_st/appl/admin/visr12/adalldefaults.txt driver=u9817770.drv logfile=patchapply_9817770.log patchtop=/home/oracle/1213Patches/9817770 workers=4

AutoPatch is complete.

-- 9966055:R12.FND.B, Patch 9966055

[oracle@appsnode 9966055]$ adpatch defaultsfile=/u01/app/oracle/visr12/apps/apps_st/appl/admin/visr12/adalldefaults.txt driver=u9966055.drv logfile=patchapply_9966055.log patchtop=/home/oracle/1213Patches/9966055 workers=4

AutoPatch is complete.

Update database tier nodes to the Oracle E-Business Suite Applications Technology Release 12.1.3 (R12.ATG_PF.B.delta.3) code level. (Required)

Application tier:

Run the admkappsutil.pl utility to create the file appsutil.zip in the <INST_TOP>/admin/out directory.

[oracle@appsnode 9966055]$ cd /u01/app/oracle/visr12/apps/apps_st/appl/ad/12.0.0/bin

[oracle@appsnode bin]$ perl ./admkappsutil.pl

-- Copy or FTP the appsutil.zip file to the <RDBMS ORACLE_HOME>.

[oracle@appsnode out]$ cd /u01/app/oracle/visr12/inst/apps/visr12_appsnode/admin/out/

[oracle@appsnode out]$ scp appsutil.zip appsdbnode:/u01/app/oracle/visr12/db/tech_st/11.1.0/

appsutil.zip

On DB Node -

[oracle@appsdbnode 11.1.0]$ unzip -o appsutil.zip

 Run AutoConfig on the <RDBMS ORACLE_HOME>.

[oracle@appsdbnode bin]$ perl ./adbldxml.pl appsuser=apps appspass=apps

Error -

Starting context file generation for db tier..

JRE_TOP or java executable not found at its desired location /u01/app/oracle/visr12/db/tech_st/11.1.0/appsutil/jre, /u01/app/oracle/visr12/db/tech_st/11.1.0/appsutil/jre/bin/java Restart ./adbldxml.pl with value for jtop as an necessary argument

Solution –

[oracle@appsdbnode 11.1.0]$ cp -R appsutil.old/jre appsutil/

[oracle@appsdbnode 11.1.0]$ cd appsutil/bin/

[oracle@appsdbnode bin]$ perl ./adbldxml.pl appsuser=apps appspass=apps

Starting context file generation for db tier..

Using JVM from /u01/app/oracle/visr12/db/tech_st/11.1.0/appsutil/jre/bin/java to execute java programs..

The log file for this adbldxml session is located at:

/u01/app/oracle/visr12/db/tech_st/11.1.0/appsutil/log/adbldxml_06060536.log

The context file has been created at:

/u01/app/oracle/visr12/db/tech_st/11.1.0/appsutil/visr12_appsdbnode.xml

- Run autoconfig again...

[oracle@appsdbnode bin]$ sh ./adconfig.sh

Enter the full path to the Context file: /u01/app/oracle/visr12/db/tech_st/11.1.0/appsutil/visr12_appsdbnode.xml

Enter the APPS user password:

The log file for this session is located at: /u01/app/oracle/visr12/db/tech_st/11.1.0/appsutil/log/visr12_appsdbnode/06060539/adconfig.log

AutoConfig is configuring the Database environment...

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

Updating rdbms version in Context file to db111

Updating rdbms type in Context file to 32 bits

Configuring templates from ORACLE_HOME ...

AutoConfig completed successfully.

 Run AutoConfig on all nodes with an Appl_Top.

[oracle@appsnode out]$ sh adautocfg.sh

Enter the APPS user password:

AutoConfig completed successfully.

 perl adpreclone.pl dbTier

[oracle@appsdbnode visr12_appsdbnode]$ pwd

/u01/app/oracle/visr12/db/tech_st/11.1.0/appsutil/scripts/visr12_appsdbnode

[oracle@appsdbnode visr12_appsdbnode]$ perl ./adpreclone.pl dbTier

Completed Stage...

 perl adpreclone.pl appsTier

[oracle@appsnode scripts]$ pwd

/u01/app/oracle/visr12/inst/apps/visr12_appsnode/admin/scripts

[oracle@appsnode scripts]$ perl ./adpreclone.pl appsTier

Completed Stage...

Generate Message Files for FND. (Required)

Generate message files for FND using FNDMDGEN.

FNDMDGEN <Oracle ID/password> 0 Y <LANG_CODE> FND

Where:

Oracle ID/password is the APPS schema username and password.

LANG_CODE is the language code of the base language, such as US.

For example:

[oracle@appsnode scripts]$ cd $FND_TOP

[oracle@appsnode 12.0.0]$ pwd

/u01/app/oracle/visr12/apps/apps_st/appl/fnd/12.0.0

[oracle@appsnode bin]$ ./FNDMDGEN apps/apps 0 Y US FND

Log filename : L395202.log

Report filename : O395202.out

That is it. If you now check the release name from back-end DB, you will see the stack will be now upgraded to 12.1.3.

If everything seems fine then start your apps stack and check the patches applied from OAM. if the patches are applied successfully and uploaded to DB, you should be able to verify them using OAM.

Sunday, June 10, 2012

Upgrade Oracle IAS/HTTP Server from 10.1.3.4 to 10.1.3.5

In this post I am going to show how to upgrade Oracle IAS (Application Server) 10g from 10.1.3.4 to 12.1.3.5. IAS 10.1.3.4 comes default with Apps/EBS R12.1.1. Hence when you try to upgrade it with R12.1.3, as one of the pre-requisite, one has to upgrade IAS to 10.1.3.5.

Note – This upgrade installer is riddled with few bugs so pls refer to Troubleshooting section, when you come across any issues. I will really appreciate it you hit some new issue, please leave a comment about the issue and I will try to answer that.

Background –

Oracle Application Server 10g Release 3 (10.1.3) Patch Set 5 (10.1.3.5.0) is not a complete software distribution. You must install this patch set over an existing installation. Specifically, this patch set can be applied only to the following Oracle Application Server releases:

Oracle Application Server 10g Release 3 (10.1.3.0.0)

Oracle Application Server 10g Release 3 (10.1.3.1.0), which included the Oracle SOA Suite

Oracle Application Server 10g Release 3 (10.1.3.2.0), which included the Oracle WebCenter Suite

Oracle Application Server 10g Release 3 Patch Set 3 (10.1.3.3.0)

Oracle Application Server 10g Release 3 (10.1.3.4.0)

Any Oracle Application Server 10g Release 3 (10.1.3.n) standalone installation

Patch Set Application

Back up Your Existing Environment

There is no automatic procedure for removing 10g Release 3 (10.1.3) Patch Set 5 (10.1.3.5.0). Oracle strongly recommends that you make a backup of your existing environment before you install Oracle Application Server 10gRelease 3 (10.1.3) Patch Set 5 (10.1.3.5.0). If you choose to remove Oracle Application Server 10g Release 3 (10.1.3) Patch Set 5 (10.1.3.5.0), or if you encounter a problem with application of the patch, then you can restore your original environment.

You must make a back up of the database schema that is being used so that the database can be reverted back to the original state.

Imp Note -

As part of the pre-requisite patch I first decided to apply latest OPatch. The reason being is that at the end of patch, the OUI uses OPatch to apply one off patches. The OPatch, one needs to apply is 6880880 for 10g. Be aware that you don’t apply 11g OPatch, as it is the latest one, you might confronted with Java invalid or unsupported class errors. The reason is that 11g OPatch uses higher version of Java.

Pre-requisite Patch (OPatch Upgrade) –

n Download p6880880_101000_LINUX.zip patch for your suitable Linux distribution

n Make sure you are pointing to correct ORACLE HOME i.e. 10.1.3 IAS Home

[oracle@appsnode 10.1.3]$ unzip /home/oracle/1213Patches/pre-req-patches/p6880880_101000_LINUX.zip -d /u01/app/oracle/visr12/apps/tech_st/10.1.3/

Archive: /home/oracle/1213Patches/pre-req-patches/p6880880_101000_LINUX.zip

creating: /u01/app/oracle/visr12/apps/tech_st/10.1.3/OPatch/ocm/

extracting: /u01/app/oracle/visr12/apps/tech_st/10.1.3/OPatch/ocm/ocm.zip

creating: /u01/app/oracle/visr12/apps/tech_st/10.1.3/OPatch/ocm/lib/

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

inflating: /u01/app/oracle/visr12/apps/tech_st/10.1.3/OPatch/perl_modules/XML.pm

[oracle@appsnode 10.1.3]$ cd OPatch

[oracle@appsnode OPatch]$ ./opatch version

Oracle Interim Patch Installer version 1.0.0.0.64

Oracle recommends you to use the latest OPatch version

and read the OPatch documentation available in the OPatch/docs

directory for usage. For information about the latest OPatch and

other support-related issues, refer to document ID 293369.1

available on My Oracle Support (https://myoraclesupport.oracle.com)

OPatch Version: 1.0.0.0.64

[oracle@appsnode 10.1.2]$ unzip /home/oracle/1213Patches/pre-req-patches/p6880880_101000_LINUX.zip -d /u01/app/oracle/visr12/apps/tech_st/10.1.2/

Archive: /home/oracle/1213Patches/pre-req-patches/p6880880_101000_LINUX.zip

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

inflating: /u01/app/oracle/visr12/apps/tech_st/10.1.2/OPatch/perl_modules/XML.pm

[oracle@appsnode 10.1.2]$ cd OPatch

[oracle@appsnode OPatch]$ ./opatch version

Oracle Interim Patch Installer version 1.0.0.0.64

Oracle recommends you to use the latest OPatch version

and read the OPatch documentation available in the OPatch/docs

directory for usage. For information about the latest OPatch and

other support-related issues, refer to document ID 293369.1

available on My Oracle Support (https://myoraclesupport.oracle.com)

OPatch Version: 1.0.0.0.64

Once the OPatch is successfully upgraded, one needs to start the upgrade Installer as follows

n Download patch 8626084 PLACEHOLDER BUG TO UPLOAD AS 10.1.3.5 PATCH-SET ON ARU (Patchset)

n Unzip the patch in the stage location

[oracle@appsnode Disk1]$ ./runInstaller

Starting Oracle Universal Installer...

Select the existing IAS 10.1.3 home to upgrade

Ignore the options to download patches and updates if you wish

During pre-checks the installer will say, it cant detect the OPMN processes running even though they are up and healthy. Check Troubleshooting Section for workaround/fix

If the OPMN stack is down, start it up as follows..

[oracle@appsnode tech_st]$ cd $ADMIN_SCRIPTS_HOME

[oracle@appsnode scripts]$ ./adstrtal.sh apps/apps

Next screen will prompt you to enter oc4jadmin user password. If you don't remember it you can choose to change it.

Pls check troubleshooting section for further info.

Once the authentication is successful, the installer will start. Review the progress...

At the end you will be asked to execute root.sh as follows

[oracle@appsnode config]$ su -

Password:

[root@appsnode ~]# cd /u01/app/oracle/visr12/apps/tech_st/10.1.3

[root@appsnode 10.1.3]# ./root.sh

Check version post installation -

[oracle@appsnode config]$ pwd

/u01/app/oracle/visr12/apps/tech_st/10.1.3/config

[oracle@appsnode config]$ vi ias.properties

Version=10.1.3.5.0

Troubleshooting -

Issue -1

Please make sure you navigate to the $INST_TOP/ora/10.1.3 and source the <sid_machine>.env file to set your 10.1.3 ORACLE_HOME before running the installer. This is already mentioned in (Upgrading to the Latest OracleAS 10g 10.1.3.x Patch Set in Oracle E-Business Suite Release 12 [ID 454811.1]).

Issue -2

OPMN is not start while applying patch 10.1.3.5 stops at 83%

Problem:

OPMN is not start while applying patch 10.1.3.5 stops at 83%

While Upgrading to the Latest OracleAS 10g 10.1.3.x Patch Set in Oracle E-Business Suite Release 12 [ID 454811.1]

Installer gave an error as show below exactly when reaching 83%

#########

OPMN is failing to start. OPMN must be started in order to correctly install and configure the patchset. Please start OPMN manually in order to continue with the patchset installation.

#########

$IAS_ORACLE_HOME/opmn/bin/opmnctl is trying to read opmn.xml from path pointed by $ORACLE_CONFIG_HOME which points to 10.1.2 home instead opmnctl should need 10.1.3 home

Do below:

Point ORACLE_CONFIG_HOME to 10.1.3 home and test by running the below command before running the installer again.

$IAS_ORACLE_HOME/opmn/bin/opmnctl status (or) startall

Export the environment variable before invoking runinstaller and this should be able to bypass the issue.

Solution:

$ echo $ORACLE_CONFIG_HOME

$ export ORACLE_CONFIG_HOME=/erpapp/aderp/inst/apps/adtmp_erptest-temp/ora/10.1.3

$ echo $ORACLE_CONFIG_HOME

/erpapp/aderp/inst/apps/adtmp_erptest-temp/ora/10.1.3

Issue 3 –

If the 'oc4jadmin' password for the OAFM oc4j instance is not known, then reset the password in the files as bellow. before running the script. Take the backup of system-jazn-data.xml before resetting the password.

Replace the modified system-jazn-data.xml with backup of system-jazn-data.xml after running the script.

File 1 - $INST_TOP/ora/10.1.3/j2ee/oafm/config/system-jazn-data.xml

file 2 - /u01/app/oracle/visr12/apps/tech_st/10.1.3/j2ee/oafm/config

For example, if you want to reset the password to 'welcome12', below should be the entry:

<user>

<name>oc4jadmin</name>

<display-name>OC4J Administrator</display-name>

<guid>23C8E4F0BDDE11DCBFB8AF3B7E0DDB2D</guid>

<description>OC4J Administrator</description>

<credentials>!welcome12</credentials>

</user>

Issue 4 –

OCM patch required even though you're not using OCM

While installing OAS 10gR3 patch 8626084 to upgrade OAS to 10.1.3.5, I received an error that step "Run One-off OPatches" had failed.

Looking at the log file, I found the following:

This is a OCM patch.

Home has OCM installed but not configured.

To run in silent mode, OPatch requires a response file for Oracle Configuration Manager (OCM).

Run /u01/app/oracle/product/oas10gr3/OPatch/ocm/bin/emocmrsp to generate an OCM response file. The generated response file can be reused on different platforms and in multiple OPatch silent installs.

To regenerate an OCM response file, rerun /u01/app/oracle/product/oas10gr3/OPatch/ocm/bin/emocmrsp.

ERROR: OPatch failed because of cmd. args. problem.

The following did the trick and I was able to complete the patch installation.

/u01/app/oracle/product/oas10gr3/ccr/bin/setupCCR -s -d