Skip to main content

ADOP - Useful Commands

ADOP - Useful Commands


I this post I am sharing different options available for ADOP.


    Display examples of the various adop parameters by entering the command:
    adop -examples
      To obtain help about the basics of adop operation
      adop -help
        Online Patching Cycle
        source <ebs_root>/EBSapps.env run
adop phase=prepare
adop phase=apply patches=123456
adop phase=finalize
adop phase=cutover
source <ebs_root>/EBSapps.env run
adop phase=cleanup
          Run Prepare Phase
          adop phase=prepare
            Run apply phase
            adop phase=apply patches=123456
              Run Finalize phase
              adop phase=finalize
                Run Cutover phase
                adop phase=cutover
                  Run Cleanup phase
                  adop phase=cleanup
                    Run fs_clone phase
                    adop phase=fs_clone
                      Combining multiple in a single adop command. Example – combined finalize/cutover/cleanup:
                      adop phase=finalize,cutover,cleanup
                        Restart the failed adop session incase you want to start from failure
                        adop phase=apply patches=123456 restart=yes
                          Restart the failed adop session incase you want to start from the very beginning
                          adop phase=apply patches=123456 abandon=yes
                            If you want to ignore a previously failed patch and apply a different one instead, you need to specify the new patch number and abandon=yes on the command line:
                            adop phase=apply patches=123456 abandon=yes
                              “Continue As If It Were Successful” error:
                              $ adop phase=apply patches=<patch list> abandon=no restart=yes flags=autoskip
                                 How to define workers in adop:
                                $ adop phase=apply patches=<patch list> workers=5
                                  How to re-apply patch forcefully:
                                  $ adop phase=apply patches=<patch list> options=forceapply
                                    How to define patchtop in adop:
                                    $ adop phase=apply patches=<patch list> patchtop=<patch location base>
                                      How to merge patch in adop
                                      $ adop phase=apply patches=<patch list> merge=yes
                                        How to stop application from restarting after cutover
                                        adop phase=cutover mtrestart=no
                                          adop exit incase of failure in jobs. If you want it to wait for action through adctrl.
                                          adop phase=apply patches=123456 wait_on_failed_job=yes
                                            How to apply patch directly to run file system with no downtime
                                            $ adop phase=apply patches=<patch_list> hotpatch=yes
                                              How apply a single patch to an NLS installation
                                              This procedure assumes that you will apply US and language patches separately.
a. Use adop to start a new patching cycle 

adop phase=prepare

b. Use adop to apply the patch driver of the US patch.

adop phase=prepare patches=123456

c. Use adop to apply the patch drivers of each NLS patch. If you have merged the individual NLS patches for a system that runs multiple languages, apply the driver for the merged NLS patch.

adop phase=apply patches=123456_JA:u123456.drv workers=8

d. Use adop to complete the patching cycle 
adop phase=finalize, cutover, cleanup phase
                                                How to apply multiple patches to an NLS installationThis example assumes the system has American English, French, and German installed.
                                                a. Use adop to start a new patching cycle. 

adop phase=prepare

b. Use AD Merge Patch to merge the US (American English) patches into a single patch.

c. Use AD Merge Patch to merge the French and German patches into a single NLS patch.

d. Use adop to apply all drivers of the merged US patch.

e. Use adop to apply all drivers of the merged NLS patch.

f. Use adop to complete the patching cycle (finalize, cutover, cleanup phases).
                                                  How to apply the Apply hrglobal.drv
                                                  adop phase=apply patchtop=$PER_TOP/patch/115 patches=driver:hrglobal.drv workers=8 options=nocopyportion,nogenerateportion,forceapply
                                                    How to apply the xla driver
                                                    $ adop phase=apply options=nocopyportion patchtop=$XLA_TOP/patch/115 patches=driver:xla5584908.drv
                                                      How to multiple patches using separate apply commands:
                                                      source <ebs_root>/EBSapps.env run
adop phase=prepare
adop phase=apply patches=123456
adop phase=apply patches=324356
adop phase=finalize
adop phase=apply patches=445657
adop phase=finalize
adop phase=cutover
source <ebs_root>/EBSapps.env run
adop phase=cleanup
                                                        How to clean up old version
                                                        $ adop phase=prepare
$ adop phase=actualize_all
$ adop phase=finalize finalize_mode=full
$ adop phase=cutover
$ adop phase=cleanup cleanup_mode=full
                                                          How to abort the adop patching cycle
                                                          $ adop phase=abort,cleanup cleanup_mode=full
$ adop phase=fs_clone
                                                            How to validate the system before starting prepare or cutover
                                                            adop -validate
                                                              How to find the running online patching cycle
                                                              adop -status
                                                                If you want additional details of operations performed:
                                                                $ adop -status -detail
                                                                Run adop in downtime mode

                                                                $ adop phase=apply patches=123456 apply_mode=downtime

                                                                To run pre-install Mode
                                                                $ adop preinstall=y


                                                                If you like please follow and comment
                                                                Labels:

                                                                Comments

                                                                Post a Comment

                                                                Popular posts from this blog

                                                                WebLogic migration to OCI using WDT tool

                                                                WebLogic migration to OCI using WDT tool Oracle WebLogic Deploy Tool (WDT) is an open-source project designed to simplify and streamline the management of Oracle WebLogic Server domains. With WDT, you can export configuration and application files from one WebLogic Server domain and import them into another, making it a highly effective tool for tasks like migrating on-premises WebLogic configurations to Oracle Cloud. This blog outlines a detailed step-by-step process for using WDT to migrate WebLogic resources and configurations. Supported WLS versions Why Use WDT for Migration? When moving Oracle WebLogic resources from an on-premises environment to Oracle Cloud (or another WebLogic Server), WDT provides an efficient and reliable approach to: Discover and export domain configurations and application binaries. Create reusable models and archives for deployment in a target domain. Key Pre-Requisites Source System: An Oracle WebLogic Server with pre-configured resources such as: Applica...
                                                                Post a Comment
                                                                Read more

                                                                Rename a PDB in Oracle Database Multitenant Architecture in TDE and Non TDE Environment

                                                                Rename a PDB in Oracle Database Multitenant Architecture I am sharing a step-by-step guide to help you rename a PDB. This approach uses SQL commands. Without TDE or encryption Wallet Initial Check Check the Current Database Name and Open Mode: SQL > SELECT NAME, OPEN_MODE FROM V$DATABASE; NAME OPEN_MODE --------- -------------------- BEECDB READ WRITE List Current PDBs: SQL > SHOW PDBS; CON_ID CON_NAME OPEN MODE RESTRICTED ---------- ------------------------------ ---------- ---------- 2 PDB$SEED READ ONLY NO 3 FUAT READ WRITE NO We need to RENAME FUAT to BEE  Steps to Rename the PDB Step 1: Export ORACLE_SID Set the Oracle SID to the Container Database (CDB): export ORACLE_SID=BEECDB Step 2: Verify Target PDB Name Availability If the target PDB name is different from the current PDB name, ensure no service exists with the target PDB name. Run SQL to Check Exi...
                                                                Post a Comment
                                                                Read more

                                                                How to make flash work on IE or Edge with IE Compatibility

                                                                How to make flash work on IE or Edge with IE Compatibility With flash been ended from 1-Jan-2021, many applications using flash have stopped working the way they were built (like OEM, OBIEE, etc). The option you have to upgrade.  This method will give a workaround in IE or Edge in IE compatibility mode without upgrading. 1. Verify you have installed flash.ocx on your desktop. Typically, flash.ocx file is located in C:\Windows\System32\Macromed\Flash or C:\Windows\SysWOW64\Macromed\Flash according to your laptop OS system. 2. Edit mms.cfg from the location as a System Administrator In the case of the 64bit system, it might have mms.cfg under C:\Windows\SysWOW64\Macromed\Flash 3. Add below options into mms.cfg file. Note: AllowListUrlPattern list is an example. The URLs need to be replaced to your hosts those have Flash pages. SilentAutoUpdateEnable=0 AutoUpdateDisable=1 EOLUninstallDisable=1 EnableAllowList=1 AllowListUrlPattern=http://www.google.com/ AllowListUrlPattern=http://goo...
                                                                Post a Comment
                                                                Read more