Oracle ADOP Patching Cycle Explained (Prepare to Clean-up)

Introduction

In Oracle E-Business Suite (EBS) R12.2, patching is performed using the Online Patching utility (ADOP). This approach allows administrators to apply patches with minimal downtime, ensuring that the system remains available to users during most of the patching process.

ADOP uses Edition-Based Redefinition (EBR) to maintain two database editions:

• Run Edition – Used by end users for normal operations

• Patch Edition – Used by DBAs to apply patches

Once patching is completed, the patch edition becomes the new run edition during cutover.

The ADOP patching cycle consists of several phases:

• Prepare

• Apply

• Finalize

• Cutover

• Cleanup

This article explains each phase of the Oracle ADOP patching cycle from Prepare to Cleanup.

ADOP Patching Cycle Phases

1. Prepare Phase

The Prepare phase initializes the online patching cycle and prepares the system for patching.

Key activities in this phase:

• Creates the patch edition in the database

• Synchronizes the file system between run and patch editions

• Verifies system readiness for patching

• Starts required services for the patch edition

Command

adop phase=prepare

Example

adop phase=prepare apps_user=apps apps_pwd=*****

Verification

Check the status of the patching session:

adop -status

2. Apply Phase

The Apply phase is where the patch is actually applied to the patch edition of the system.

During this phase:

• Patch files are applied to the patch file system

• Database changes are applied to the patch edition

• Users continue working on the run edition

Command

adop phase=apply patches=<patch_number>

Example

adop phase=apply patches=12345678

Multiple Patches

You can apply multiple patches at once:

adop phase=apply patches=12345678,87654321

3. Finalize Phase

The Finalize phase prepares the system for the cutover phase.

This phase performs several tasks to reduce downtime during cutover.

Key activities:

• Compiles invalid objects

• Validates patch edition changes

• Prepares data dictionary objects

• Ensures system readiness for cutover

Command

adop phase=finalize

4. Cutover Phase

The Cutover phase is the only phase that requires system downtime.

During cutover:

• The patch edition becomes the new run edition

• The old run edition becomes obsolete

• Services are restarted

Command

adop phase=cutover

Activities performed:

• Stops application services

• Promotes patch edition to run edition

• Restarts services

Cutover typically takes a few minutes, depending on the environment.

5. Cleanup Phase

The Cleanup phase removes obsolete data from previous editions.

Key tasks:

• Drops the old database edition

• Removes unused objects

• Frees database space

Command

adop phase=cleanup

Cleanup Options

Standard cleanup:

adop phase=cleanup

Full cleanup:

adop phase=cleanup cleanup_mode=full

Check ADOP Status

You can check the status of the patching cycle using:

adop -status

This command displays:

• Current phase

• Session ID

• Patch progress

Best Practices for ADOP Patching

Always run ETCC (EBS Technology Codelevel Checker) before patching
Ensure sufficient disk space in both file systems
Take a backup before starting the patching cycle
Monitor logs during the apply phase
Run cleanup regularly to remove old editions

Caution: Your use of any information or materials on this Blog is entirely at your own risk. It is provided for educational purposes only.

How to Enable Archive Log Mode and Change Archive Log Destination in Oracle 19c

Introduction

Archive logging is a critical feature in Oracle databases that enables database recovery and online backups. When the database runs in ARCHIVELOG mode, Oracle archives redo log files before they are overwritten. These archived logs can later be used for point-in-time recovery and disaster recovery.

In this article, we will walk through:

• Checking the current archive log status

• Enabling ARCHIVELOG mode

• Configuring the Fast Recovery Area (FRA)

• Changing the archive log destination

• Verifying archive log generation

This guide applies to Oracle 19c running on Linux.

Step 1: Check the Current Archive Log Location and Archive Log Status

First, connect to the database and verify the current archive log destination.

Explanation

• Database log mode: No Archive Mode – The database is not archiving redo logs.

• Automatic archival: Disabled – Archive log generation is turned off.

• Archive destination: Default location where archive logs will be stored once archiving is enabled.

• Log sequence numbers: Show the redo log sequence currently in use.

Since the database is in NOARCHIVELOG mode, you cannot perform point-in-time recovery or hot backups.

Step 2: Steps to Enable ARCHIVELOG Mode

Shutdown the Database

Start Database in Mount Mode

Enable ARCHIVELOG Mode

Open the Database

Step 3: Verify Archive Log Mode

Step 4: Configure Fast Recovery Area (FRA)

The Fast Recovery Area (FRA) is a central location where Oracle stores:

• Archive logs

• Flashback logs

• Backup files

• Control file backups

Check the FRA parameters.

Set FRA Size

Step 5: Set Archive Log Destination

Step 6: Confirm Archive Destination

Step 7: Generate Archive Logs

Caution: Your use of any information or materials on this Blog is entirely at your own risk. It is provided for educational purposes only.

Oracle Database Security Assessment Tool (DBSAT) Version: 4.2.0.0.0

What is Oracle Database Security Assessment?

Oracle Database Security Assessment is the process of reviewing database configurations, user privileges, and security settings to detect vulnerabilities and ensure that security policies are properly implemented.

The goal is to identify risks such as:

Weak password policies

Excessive user privileges

Unpatched vulnerabilities

Lack of auditing and monitoring

Misconfigured database parameters

By performing regular security assessments, organizations can strengthen their database security posture and prevent unauthorized access.

Database security is a critical responsibility for every DBA. Regular security assessments help identify vulnerabilities before attackers can exploit them.

Oracle Database Security Assessment Tool (DBSAT) consists of three main components: Collector, Reporter, and Discoverer, each designed to analyze and evaluate different aspects of database security.

The Collector and Reporter work together to detect potential security risks in the Oracle Database environment and generate the Database Security Assessment Report, while the Discoverer operates independently to identify and report sensitive data through the Database Sensitive Data Assessment Report.

Collector:

The Collector gathers information from the target database by executing SQL queries and operating system commands. It mainly retrieves metadata from database dictionary views and stores the collected data in a JSON file, which is later used by the Reporter for analysis.

Reporter:

The Reporter processes and analyzes the data collected by the Collector. Based on this analysis, it generates a detailed security assessment report that highlights potential risks and configuration issues. The report can be produced in multiple formats, including HTML, Excel, JSON, and Text.

Discoverer:

The Discoverer is responsible for locating sensitive data within the database. It runs SQL queries on database dictionary views according to the rules defined in configuration files. The output identifies potentially sensitive information and provides reports in HTML, CSV, and JSON formats.

How to download DBSAT Tool?

To download you need to use below link. 

https://support.oracle.com/support/?anchorId=&kmContentId=2138254&page=sptemplate&sptemplate=km-article 

Demo: Running a Security Assessment Using DBSAT

Installing DBSAT 

Create directory to install DBSAT

mkdir dbsat4

Download or copy the dbsat.zip file to the database server

Unzip the DBSAT zip file

Collect Data

Let's  reviewing all DBSAT command-line parameters

Run DBSAT to collect data from TEST

Generate the report 

Unpack the file to view the reports

Analyze Report

Discover Sensitive Data

Unpack the file to view the reports

View Sensitive Data

Caution: Your use of any information or materials on this Blog is entirely at your own risk. It is provided for educational purposes only.

Apply Patch RU on Database 19c(19.30)

 

Environment:- 

      DB Version : Oracle 19c, File system: Normal

       Platform : Linux86_64

Download Patch from My Oracle Support:- 

https://support.oracle.com/support/anchorId=&documentId=CPU4&page=sptemplate&sptemplate=km-article

Unzip Patch:-

Unzip Bundle Patch

First, apply the Database RU patch 38632161.
Minimum required OPatch version for this patch is 12.2.0.1.48.
Let’s verify our current OPatch version before proceeding.

Current Version:-

Let’s upgrade the OPatch version by downloading Patch 6880880.
While downloading, select "OPatch for DB 19.0.0.0.0" from the Select a Release dropdown menu, as shown in the screenshot below.

Now, the OPatch version has been upgraded.

 Interim Patch Conflict Detection and Resolution

Shutdown database and as well listener

Let's Apply Database RU patch 

Applying OJVM Patch 

Current Version Apply SQL Changes(DataPatch)

Verify from dba_registry_sqlpatch

Caution: Your use of any information or materials on this Blog is entirely at your own risk. It is provided for educational purposes only.

Install Oracle database 19c

 Step-by-Step Installation of Oracle 19c (Release 3) on Linux 8 Download Software

All prerequisite configurations have already been completed, including memory allocation, swap configuration, kernel parameter settings, creation of required groups and users, and profile setup.

Download Software 

https://www.oracle.com/database/technologies/oracle19c-linux-downloads.html

 Unzip Software

Invoke ./runInstaller

Start the Oracle Universal Installer by issuing the  command.

Note :- Use of any information or materials provided on this website is solely at your own risk. The content is intended for educational purposes only