Skip to main content

AD online patching in Oracle EBS R12.2

ADOP – Applications DBA Online Patching Tool 


Oracle introduced ADOP in Oracle E-Business R12.2 . This is a new patching mechanism (online patching) that allow the application of patches while your environment is up and running.You don't need to stop the application or put it on maintains mode as we use to do before. 

ADOP phases:

1) Prepare – This will prepare the instance for patch application.
2) Apply – This will apply patches .
3) Finalize – This will get ready the instance for cutover.
4) Cutover – This will make the patch edition the new run edition (fs1 to fs2).
5) Cleanup – This will drop obsolete objects and data from old editions.

Steps to apply patch on R12.2 using ADOP:

1) Download and unzip the patch

2) Read the readme carefully

3) run the environment as below in new cmd prompt.

$ source <run APPL_TOP path>/APPS<CONTEXT_NAME>.env

4) confirm the staus of adop by below command.

$ adop -status

5) start from first phase by Preparing the system for patching.

$ adop phase=prepare

6) NOw apply the patch to patch edition.

$ adop phase=apply patches=<patch number>,workers=<number_of_worker>
e.g adop phase=apply patches=1111,2222 workers=6

7) check for the logs and complete the rest of the phases as below:-

$ adop phase=finalize
$ adop phase=cutover
$ adop phase=cleanup

8) We have to Synchronize the file system, which copy the new run edition code and configuration to the patch file system.

$ adop phase=fs_clone


Note:- You can use in one go  "adop phase=prepare,apply,finalize,cutover,cleanup patches=<patch_number1>,<patch_number2>"

 Thanks ;)
Labels:

Comments

Post a Comment

Popular posts from this blog

DBA_SCHEDULER_JOB_RUN_DETAILS and PURGE_LOG

How to purge DBA_SCHEDULER_JOB_RUN_DETAILS? Manually deleting from DBA_SCHEDULER_JOB_RUN_DETAILS is not recommended by oracle.DBA_SCHEDULER_JOB_RUN_DETAILS is a view that is using two master tables (scheduler$_job_run_details and scheduler$_event_log) and display the information about jobs history. As there is one procedure named PURGE_LOG and Oracle have Scheduler for this procedure. It will purges all rows in the job log that are older than 30 days.This is the default behavior of this procedure. You can change this to any number of days you want by setting the attribute "SET_SCHEDULER_ATTRIBUTE". e.g. exec DBMS_SCHEDULER.SET_SCHEDULER_ATTRIBUTE('log_history','15'); It will purge all logs older than 15days and it will maintain the history of 15days. But If you want manually purge these logs, you can use below solution:- exec DBMS_SCHEDULER.PURGE_LOG(log_history => 15, which_log => 'JOB_LOG'); It will purge all entries from the jog log that are o...
Post a Comment
Read more

ORA-65016: FILE_NAME_CONVERT must be specified

ORA-65016: FILE_NAME_CONVERT must be specified I just started working on 12C version of oracle database.It's new to me and facing many problems. Error code: ORA-65016: FILE_NAME_CONVERT must be specified Description:"ORA-65016: FILE_NAME_CONVERT must be specified" normally occurs when you create a PDB.I will explain later what is a PDB. Cause and solution :  ORA-65016: FILE_NAME_CONVERT must be specified caused when Data files, and possibly other files, needed to be copied as a part of creating a pluggable database.Enable OMF or define PDB_FILE_NAME_CONVERT system parameter before issuing CREATE PLUGGABLE DATABASE statement, or specify FILE_NAME_CONVERT clause as a part of the statement and make sure the path you are giving to convert the file exists. I think if you are creating the PDB's using GUI then you will not face this error "ORA-65016: FILE_NAME_CONVERT must be specified". If you creating ODB using script and you have gave a wrong path then may you f...
2 comments
Read more

ORA-02051 Another Session Or Branch In Same Transaction Failed

ORA-02051 Another Session Or Branch In Same Transaction Failed (Doc ID 2253226.1)          SYMPTOMS for ORA-02051 Another Session Or Branch In Same Transaction Failed. Database performance is slow and caused   the transactions ORA-02051 another session or branch in same transaction failed or finalized CAUSE for ORA-02051 Another Session Or Branch In Same Transaction Failed. Session transactions branches caused the issue Excessive Waits On The Event "Global transaction acquire instance locks" SOLUTION Please use below sql and identified underscore parameter values for ORA-02051 Another Session Or Branch In Same Transaction Failed : SQL> select a.ksppinm "Parameter", b.ksppstvl "Session Value",c.ksppstvl "Instance Value"  FROM x$ksppi a,x$ksppcv b, x$ksppsv c  WHERE a.indx = b.indx AND a.indx = c.indx AND a.ksppinm LIKE '/_%' escape '/'  AND (a.ksppinm like '%clusterwide_global%' or a.ksppinm like '%disable_autotune_...
Post a Comment
Read more