How can Can We Use Hot Patch

Visit the Below Website to access unlimited exam questions for all IT vendors and Get Oracle Certifications for FREE
http://www.free-online-exams.com

Problem:    

How can Can We Use Hot Patch 

If you use hotpatch and a file in the patch is in use by the application, it will not be updated
by the patch as the file will be locked and will not be over-written by the copy portion of the
patch driver

During a patch application the recommended option is to Enable Maintenance node. If the Maintenance Mode is not enable you will get an error like :

sqlplus -s &un_apps/***** @$AD_TOP/patch/115/sql/adsetmmd.sql ENABLE 
Error: 
Program exited with status 3 
Cause: The program terminated, returning status code 3. 
Action: Check your installation manual for the meaning of this code on this operating system. 
An error occurred while running adsetmmd.sql. 
Continue as if it were successful [No] : Yes 
Could not enable Maintenance Mode. 
Review the messages above, then press [Return] to continue.
...
To apply a patch without maintenance mode enabled use this syntax :

 adpatch options=hotpatch  

References:

Note  375130.1

    

Get Oracle Certifications for all Exams
Free Online Exams.com

How patches are applied when you have shared appltop?

Visit the Below Website to access unlimited exam questions for all IT vendors and Get Oracle Certifications for FREE
http://www.free-online-exams.com

How patches are applied when you have shared appltop?

When you have you apps environment on two nodes with a shared appltop

Database --- Two node RAC Instance.
Application --- Two node with shared APPL_TOP.

Explanation:

You need to apply the patch on admin node on shared APPL_TOP and run the auto-config on other node only. 

    

Get Oracle Certifications for all Exams
Free Online Exams.com

FAILED: file fwk_tbx_lookup_types_tl.xdf on worker 1 while applying RUP 6

Visit the Below Website to access unlimited exam questions for all IT vendors and Get Oracle Certifications for FREE
http://www.free-online-exams.com

Problem:

After merging the pre_req  ,RUP6 and post-req patches together and apply the new merged patch,  

We got the below Error while applying RUP6.
we are running this patch using adctrl distributed=y.

FAILED: file fwk_tbx_lookup_types_tl.xdf on worker 1.
FAILED: file fwk_tbx_lookup_codes_b.xdf on worker 2.

Note DOC ID 5347952 did not help

Solution:

merge the pre-req patches alone and apply it then apply the RUP6 patch and then apply the post-req patches

apply the pre-req patches alone first and then apply the RUP6 patch and check whether issue got resolved or not

if it does not work, do the below:


1. Run scripts manually:

adjava -Xmx512M -nojit oracle.apps.fnd.odf2.FndXdfCmp ak ak apps apps_pwd
thin
"(DESCRIPTION=(ADDRESS=(PROTO =tcp)(HOST=<i.e. us.oracle.com>)(PORT=<db_por
t#>)
(CONNECT_DATA=(SERVICE_NAME=<i.e oracle.com)(INSTANCE_NAME=<SID_NAME>)))"
table
<full path to $FND_TOP/patch/115/fwk_tbx_lookup_types_tl.xdf
<full path to $FND_TOP/patch/115/xdf_xsl

adjava -Xmx512M -nojit oracle.apps.fnd.odf2.FndXdfCmp ak ak apps apps_pwd
thin
"(DESCRIPTION=(ADDRESS=(PROTO =tcp)(HOST=<i.e. us.oracle.com>)(PORT=
<db_port#>)
(CONNECT_DATA=(SERVICE_NAME=<i.e oracle.com)(INSTANCE_NAME=<SID_NAME>)))"
table
<full path to $FND_TOP/patch/115/fwk_tbx_lookup_codes_b.xdf
<full path to $FND_TOP/patch/115/xdf_xsl

2. Run adctrl and skip failed workers;

3. Continue adaptch;

Replace the entries by the ones from your environment.

    

Get Oracle Certifications for all Exams
Free Online Exams.com

Common questions about merge apps patches

Visit the Below Website to access unlimited exam questions for all IT vendors and Get Oracle Certifications for FREE
http://www.free-online-exams.com

Question:

Can we merge patches in Oracle apps?

Answer:

You can merge multiple patches into a single patch by using AD Merge Patch. This AD
command line utility merges multiple AutoPatch-compatible patches into a single,
integrated patch. Once the merged patch is created, you use AutoPatch to apply it in a
single operation. Applying a merged patch reduces the time it takes to complete the
patching process.

In general, you can safely merge any Oracle Applications patch with any other Oracle
Applications patch. Older split driver patches can be merged with newer unified
driver patches. Patches can and should be merged with their listed prerequisite
patches to make patch application easier.

Additional Information: See AD Merge Patch in Oracle Applications
Maintenance Utilities.

Question:

Can we merge the NLS patches along with US patch and apply the same

Answer:

You can merge .However the recommended method is:

If an Oracle Applications system contains multiple languages other than American
English (US) and you are applying multiple patches for each language, the
recommended method is to merge all US patches into a single patch and all patches for
every non-US language into a single patch. Then, apply the merged US patch followed
by the merged language patch.

You can also merge US patches with the additional language patches or merge each
language in separate language-specific patches. Depending on your downtime
window and your system topology, it may be necessary to keep the US and non-US
patches separate. (See Applying an Emergency NLS Patch in this chapter). This
procedure assumes that you will apply US and language patches separately.

 Basically you can try 2-3 times on a test system which is cloned from production to apply the merged patch US and ARABIC .
If no errors then you can apply on production.

Question:

What are the cases merging will not work out?

Answer:

AD Merge Patch cannot merge patches of 

different releases,
different parallel modes, 

different platforms. 

However, it can merge patches for a specific platform with a generic patch, or
patches with different source character sets. 

AD Merge Patch
notifies you if you try to merge incompatible patches.

However, patches that affect the Applications DBA (AD) product must be handled
separately. AD patches can be merged with other AD patches, but AD patches and
non-AD patches cannot be merged because AD patches may change the AutoPatch
utility itself. Merged AD patches must be created separately and applied before you
apply non-AD patches.

Get Oracle Certifications for all Exams
Free Online Exams.com

Can we merge the NLS patches along with US patch and apply the same

Visit the Below Website to access unlimited exam questions for all IT vendors and Get Oracle Certifications for FREE
http://www.free-online-exams.com

Problem Description:

Problem Description: Can we merge the NLS patches along with US patch and apply the same

Solution:

You can merge .However the recommended method is:
If an Oracle Applications system contains multiple languages other than American
English (US) and you are applying multiple patches for each language, the
recommended method is to merge all US patches into a single patch and all patches for
every non-US language into a single patch. Then, apply the merged US patch followed
by the merged language patch.
You can also merge US patches with the additional language patches or merge each
language in separate language-specific patches. Depending on your downtime
window and your system topology, it may be necessary to keep the US and non-US
patches separate. (See Applying an Emergency NLS Patch in this chapter). This
procedure assumes that you will apply US and language patches separately.


Basically you can try 2-3 times on a test system which is cloned from production to apply the merged patch US and ARABIC .
If no errors then you can apply on production.

Get Oracle Certifications for all Exams
Free Online Exams.com

Applying arabic syncronization patch [8466814] for EBS using adpatch fails

Visit the Below Website to access unlimited exam questions for all IT vendors and Get Oracle Certifications for FREE
http://www.free-online-exams.com

### Detailed Problem Statement ###
Applying  arabic syncronization patch [8466814] for EBS using adpatch fails ( @ the end after workers have finished thier jobs) with :

The following Oracle Forms objects did not generate successfully:


on forms/AR PNXVAREN.fmx

Trouble shooing

LOG FILE
-----------------------
Filename =adadmin.log
See the following error:

The following Oracle Forms objects did not generate successfully:
pn forms/AR PNXVAREN.fmx

The US version of the form has been regenerated successfully.

Solution:

This is explained in the following bug:
Bug.6436010 - FORM PNXVAREN FAILED TO REGENERATE DURING NLS TRANSLATION

After applied the patch run adadmin generate the forms and update the status

Get Oracle Certifications for all Exams
Free Online Exams.com

AutoPatch error:ATTENTION: All workers either have failed or are waiting:FAILED: file xxxx on worker x.

Visit the Below Website to access unlimited exam questions for all IT vendors and Get Oracle Certifications for FREE
http://www.free-online-exams.com

AutoPatch error:ATTENTION: All workers either have failed or are waiting:FAILED: file xxxx on worker x.

Whatever listed below is from my own experience for cases and issues I faced while I am working as an Apps DBA .
It does not nessassary to apply on all cases just it will give you a hint or clu to where you should focus.


Here what you are going to do if you face the below error while applying patches using adpatch

ATTENTION: All workers either have failed or are waiting:
FAILED: file xxxx on worker x.
ATTENTION: Please fix the above failed worker(s) so the manager can continue


Check the worker ID log file ( adworkerxx.log ) from $APPL_TOP/admin/$SID/log , the exact issue should be mentioned in it, take an action and resolve the issue then do the following to proceed with the adpatch:


Run adctrl
Choose option 1 "Show Worker Status" which should show the status failed.
Then choose option "2. Tell worker to restart a failed job". Enter the number of worker which you want to restart.
The status will change to "fixed,restart" and the patch will progress.

Get Oracle Certifications for all Exams
Free Online Exams.com

AutoPatch error:adfrjp(): Error running jobs in workers" After your adpatch session disconnects inproperly

Visit the Below Website to access unlimited exam questions for all IT vendors and Get Oracle Certifications for FREE
http://www.free-online-exams.com

Whatever listed below is from my own experience for cases and issues I faced while I am working as an Apps DBA .

It does not nessassary to apply on all cases just it will give you a hint or clu to where you should focus.


While I was trying to reapply a patch using adpatch after my old session got disconnected inproperly ( This includes you close your session by mistake, your PC reboots , network issues),

I ran the adpatch again and select "YES" for continue from previous run so it will resume from the last point befire it got terminated by using the *.rf9 files in $APPL_TOP/admin/$sid/restart


Thats would be in an ideal situation,however sometimes it fails  throwing the following error:

"AutoPatch error:
The worker should not have status 'Running' or 'Restarted' at this point.


Telling workers to quit...


All workers have quit.


AutoPatch error:
adfrjp(): Error running jobs in workers"


What is caused it is an "inconsistency between fnd_install_processes, ad_deferred_jobs and .rf9 files".

What to do next is to use adctrl utility  and select option "1. Show worker status" ==> Show Running
it you try  to quit the worker by hitting option "3. Tell worker to quit" , you will get "Control code already set to 'Quit' for worker xxx".


Here what you going to do to get on the top of this issue:
Hit on option "4. Tell manager that a worker failed its job" from the adctrl utility and type the worker id you saw above to change his status from "Running" to "Failed"
Then tell this gentelman worker to restart his failed job by hitting "2. Tell worker to restart a failed job"


and hopefully will get your issue resolved and it will proceed with your adpatch

Get Oracle Certifications for all Exams
Free Online Exams.com

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

Visit the Below Website to access unlimited exam questions for all IT vendors and Get Oracle Certifications for FREE
http://www.free-online-exams.com

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
/erpapp/aderp/inst/apps/adtmp_erptest-temp/ora/10.1.2
$ 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


Run the installer again and you will pass the 83% error.


      

Get Oracle Certifications for all Exams
Free Online Exams.com