Modern Oracle DBA

How to check EBS CPU level Copy Select max (CODELEVEL) "CPU" from AD_TRACKABLE_ENTITIES where ABBREVIATION in ('ebscpu'); How to check AD and TXK Code level Copy Select abbreviation,codelevel from ad_trackable_entities where abbreviation in( 'ad','txk','cc_pf','atg_pf','scp_pf' ) order by abbreviation; How to check Patch applied status Copy Select bug_number,creation_date from ad_bugs where bug_number= How to check Installed language in EBS Copy SELECT Language_code, NLS_language, Installed_flag FROM fnd_languages WHERE installed_flag IN ('I', 'B'); I- Installed Language B- Base Language Is System crash/Unable to continue the Adop session  Execute below querys to find which session is causing theissue Copy select adop_session_id from ad_adop_sessions where status='R'; Copy select ADOP_SESSION_ID,PREPARE_...

Adop Apply Phase Frequently Using Commands: - How to apply the patch adop phase=prepare adop phase=apply patches=<Patch_Number> adop phase=finalize adop phase=cutover adop phase=cleanup adop phase=fs_clone How to apply Multiple patches  adop phase=apply patches=<Patch1>,<Patch2>,<Patch3> How to apply Merge patch adop phase=apply patches=<Patch1>,<Patch2>,<Patch3>  merge=yes How to apply Patch Run File System/Hot Patch Mode adop phase=apply patches=<Patch_Number>   hotpatch=yes How to apply the patch downtimemode adop phase=apply patches=<Patch_Number>  apply_mode=downtime How to reapply the patch adop phase=apply patches=<Patch_Number>  options=forceapply How to restart the patch from where patch failed adop phase=apply patches=<Patch_Number>  restart=yes How to restart the failed patch from begining adop phase=apply patches=<Patch_Number>  abandon=yes How to ignore the failed patc...

Step 1: Download the Patches Search for the following keywords on Oracle Metalink to download the CPU patches: Critical Patch Update (CPU) Program JAN 2022 Critical Patch Update (CPU) Program APR 2022 Critical Patch Update (CPU) Program JUL 2022 Critical Patch Update (CPU) Program OCT 2022 Download the Latest OPatch Version: Verify the current OPatch version: I opened for the July patch, and here we need to click Patch availability for Oracle products -> 3.1 Oracle database. Oracle database (3.1) Many Oracle products patches are listed here. I need only Oracle database patches. So, I'll go with the Oracle database 3.1.7 My DB version is 19c So I will choose 3.1.7.3 Oracle database 19c Here I will download the below database patch and grid patch (GI) One interesting fact is that if you download the GI Patch Database patch, it will also come under GI Patch. As a result, there is no need to download a database patch separately. Note : If you only apply the patch in Oracle Home, you...

  OTM Patching Steps Step 1: Download the required patch and unzip at location:"/apps/patch/OTMPATCHES" Step 2: Shutdown the OTM application services Step 3: Go to patch directory where the patch is unziped. Step 4: Run the command " Java -jar <filename> " Step 5: Check for any errors and fix it as per instructions. Step 6: Start the OTM application services and test. Patching Rollback steps: Step 1: Shutdown the application Step 2: Go to patch directory where jar file is located. Step 3: Run the command " java -jar <filename> uninstall " Step 4: Check for any errors or special instructions. Step 5: Start the application. How to check patch applied status in OTM /apps/applmgr/otm643/otm/glog/config [applmgr@otm_lab config]$ cat glog.patches.properties |grep 29134625 installed_patch=otm643_quickpatch_29134625 (29134625)

  Dropping old database editions: As online patching cycles are completed, the system will build up several old database editions. When the number of old database editions reach about 25, you should consider running a special maintenance operation to drop old database editions. Use below script to find DB edition details Cd $AD_TOP/sql/ ADZDSHOWED.sql Output: SQL> @ADZDSHOWED.sql ========================================================================= = Editions ========================================================================= Edition Name Type Status Current? --------------- -------- -------- -------- --------- V_20210318_1313 ACTIVE V_20210323_0209 ACTIVE V_20210421_0706 ACTIVE V_20210428_1036 ACTIVE V_20210505_0620 OLD ACTIVE V_20210507_2006 RUN ACTIVE CURRENT Disconnected from Oracle Database 19c EE Extreme Perf Release 19.0.0.0.0 - Production Actualize_All and Full Cleanup will clear the old database Example adop phase=prepar...

Before jumping into actual patching, it helps to understand the technology stack behind Oracle E-Business Suite (EBS) 12.2 patching. This includes the tools used for each component. This post gives a quick background on Application Technology patches, with a focus on the WebLogic Server (BSU) patching process. What Are Application Technology Patches? Application Technology patches cover the middle-tier components of EBS 12.2 and are applied using different utilities depending on the component: Component Home Patching Tool Oracle HTTP Server (OHS) OHS Home OPatch Oracle WebLogic Server FMW Home BSU (Smart Update) Oracle Forms (10.1.2 ORACLE_HOME) Forms Home OPatch These patches can be applied directly on the Run edition , after which adop fs_clone is executed to sync the file system. Alternatively, they can be applied through the standard Patch edition cycle as part of an adop patching session. Applying Middle Tier ETCC Patches As part of routine maintenance, two key patch categories...

Adadmin (Ad administration): It’s performance the maintenance tasks for Oracle E-business suite. AD Administration Main Menu 1. Generate Applications Files menu 2. Maintain Applications Files menu 3. Compile/Reload Applications Database Entities menu 4. Maintain Applications Database Entities menu 5. Change Maintenance Mode 6. Exit AD Administration 1. Generate Applications Files menu 1. Generate message files 2. Generate form files 3. Generate report files 4. Generate graphics files 5. Generate product JAR files 6. Return to Main Menu 2-Maintain Applications Files 1. Relink Applications programs 2. Create Applications environment file 3. Copy files to destinations 4. Convert character set 5. Maintain snapshot information 6. Check for missing files 7. Return to Main Menu 3-Compile/Reload Applications Database Entitie 1. Compile APPS schema 2. Compile menu information 3. Compile flexfields 4. Reload J...

 Adop Phase=fs_clone What is the fs_clone Phase? The fs_clone phase in Oracle EBS refers to the process of cloning the patch edition file system from the run edition.  It is used for file system cloning, and the usual cloning (adcfgclone.pl) script cannot be used to synchronize the run and patch file systems. Normally, fs_clone deletes the patch file system and restores the run system. When to Use  fs_clone Consider using the  fs_clone  phase in the following scenarios: After Aborting an Online Patching Cycle If a previous online patching cycle is aborted, the file system must be synchronized. If Technology Stack Patch is Applied in the Run Edition If any manual changes are made in the run file system, such as applying a technology stack patch, the file system must be synchronized. After Applying a RUP Patch Using  fs_clone  will synchronization between run and patch file and its help complete the prepare phase quickly. How to Execute fs_clone? adop Ph...

What is the ADOP Finalize Phase? After applying the patches in the patch edition, it will create lots of invalid objects. The finalize phase will compile the invalid objects, and it will prepare the environment for the cutover phase. The finalize phase is the optional phase in the patching cycle. After applying the patch, if we missed it, run Finalize and directorally run the cutover. The cutover phase will check if the if the finalize phase is completed or not. If not completed, the finalize phase cutover phase will start. Key Actions during the Finalize Phase Mode Selection : ADOP offers two modes for finalization - "quick" and "full": Quick Mode : This mode prioritizes speed by skipping non-essential tasks, making it ideal for scenarios where minimal downtime is critical. Full Mode : In contrast, full mode executes additional actions such as gathering statistics to the DML statment and enhance system performance after the patch is applied. This mode is beneficial...

adop phase=prepare Understanding ADOP Prepare Parameters Before diving into the prepare phase, let's go over the key parameters: skipsyncerror : This parameter specifies whether to ignore errors that may occur during incremental file system synchronization. Options :  yes  or  no  (default:  no ) Usage : Set to  yes  if you encountered errors in a previous patching cycle but decided to continue with the cutover. This will ignore apply errors during the next synchronization. sync_mode : This parameter determines the method used to synchronize the patch file system with the run file system. Options :  delta  or  patch  (default:  patch ) Usage : delta : Uses the file system synchronization command specified in  $AD_TOP/patch/115/etc/delta_sync_drv.txt . patch : Reapplies patches applied on the run file system. Example Command adop phase=prepare skipsyncerror= yes sync_mode=delta Step-by-Step Execution 1. Validating Passwo...

ERROR: This Patch seems to have been applied already. Solution: The only way to bypass that is using the forceapply option adop phase=apply patches=<Patch_Number>  options=forceapply Refer: How to bypass the error "This Patch seems to have been applied already. Would you like to continue anyway" when applying a patch via ADOP ? (Doc ID 1920187.1)

To optimize the process of upgrading to E-Business Suite Release 12.2, the AD Delta 5 Release Update Pack introduced downtime mode, which is used as follows : $ adop phase=apply patches=<patch_number> apply_mode=downtime Downtime mode does not use an online patching cycle The process of applying a patch in downtime mode completes more quickly than in online mode, but at the cost of increased system downtime.  There is no capability to abort a failed patch and return to the existing run edition. Apply Steps: Step 1:Source environment. Step 2: Stop application services Step 3: adop phase=apply  apply_mode=downtime  patches=PATCH_NUMBER adop phase=apply  apply_mode=downtime  patches=26387471