How to apply Oracle 19C RU - January 2026 step by step

 Hi All,

In this post i am going to share about Oracle 19C JAN-2026 RU patch apply step by step lab .

Firstly we need to login support.oracle.com and click on critical patch updates , then click on the JAN-2026 CPU patch document 

you can able to see below 

Click on database >  that will navigate to below Oracle Critical Patch Update (CPU) Jan 2026 for Oracle Database Products

Depends on your OS download the patch, here in this lab  i used Linux X86-64 bit OS for oracle 19C Database 

Click on the patch that will redirect to patch download page .. if you have valid CIS number only you can download else you can see download option disabled.

i have download that patch using right credentials, copy that patch to database server and read the read me file for pre-requisites if anything before apply the RU.

 

post copy the patch unzip

Check the current patch level in database also opatch version .

take invalid count before apply the patch on both CDB$ROOT and PDB1. 

stop the database and listener :

as part of pre-requisite we need to upgrade opatch version .

upgading the opatch version from 

[oracle@ggnode1 OPatch]$ ./opatch version

OPatch Version: 12.2.0.1.17  to 12.2.0.1.48 or later 

download and copy the latest opatch 

export PATH=/u01/app/oracle/product/19.0.0/OPatch/bin:$PATH

apply the RU 2026 database patch :

Patch applied 

start the database and listener services 

run the datapatch verbose and check the db invalid objects 

before and after invalid count same 1 

we have successfully completed the oracle database 2026 RU patch .

reference oracle note id : updates.oracle.com/Orion/Services/download?type=readme&aru=28482211

Thanks,

Srini.

Oracle 19C Golden Gate Pre-Requisites for replication Complete step by step lab

 Hi All,

in this post i am going to share about oracle golden gate post install pre-requisites for replication.

lab environment :

2 servers >> source and target server 

source golden gate server >> ggnode1 

target golden gate server >> ggnode2

note : i have installed the oracle 19c database and Oracle 19C golden gate software on both the nodes .

set the Source node environment : 

set the Target Node environment : 

In order for GoldenGate to replicate data from Source database to target database, there are some pre-requisite steps to be performed on both Source & Target Database like

>> Set Parameter Enable_GoldeGate_Replication to TRUE (on both source & target database)

>> Create Global User in Database 19c with prefix C##  (on both source & target database)

>> Grant DBA Role to this user (on both source & target database)

>> Enable Supplemental Logging (on source database)

>> Enable Database in Archive Log Mode (on source database).

Pre-requisite on Source Node :::

      Enable Goldengate Replication >>   set the environment and enable it on CDB$ROOT leave this parameter cant enable on PDB level..

If you try to enable at pdb level you can see below error :

Now CREATE GLOBAL USER & GRANT DBA ROLE 

Note Below tablespace needs to be present in both Container and pluggable. 

Make sure you are connected to first container and then Plugabble database before creating tablespace. Otherwise you will hit with an error while starting the PDB 

1. Create tablespace ggs_tblsp in both container and pluggable db's 

Connect to Container (ggdb1):

create tablespace ggs_tblsp datafile '/u01/app/oracle/oradata/GGDB1/gg.dbf' size 2G;

Connect to Pluggable (pdb1):

create tablespace ggs_tblsp datafile '/u01/app/oracle/oradata/GGDB1/pdb1/gg.dbf' size 2G;

2. Create a user in container database with prefix c##. 

Note: In 19c this user is common to all the pluggables present. (In 19c all common users and roles are created with prefix c##)

SQL> create user c##sourcegg1 identified by Welcome1 default tablespace ggs_tblsp;

SQL> grant dba to c##sourcegg1 container=all; 

SQL> exec dbms_goldengate_auth.grant_admin_privilege ('c##sourcegg1',container=>'all');

ENABLE SUPPLEMENTAL LOGGING 

Note : To Enable Supplemental Looging please make sure conneted with CDB Database

Enable supplemental Logging as 

alter database add supplemental log data (all) columns;

Import step is database should be archive log mode enable :

check if it not enable , enable it .

open database 

this concludes source side pre-requisites are completed .

Pre-requisite on Target Node :::

     Enable Goldengate Replication >>

CREATE GLOBAL USER & GRANT DBA ROLE 

Note : Below tablespace needs to be present in both Container and pluggable. 

Make sure you are connected to first container and then Plugabble database before creating tablespace. 

Otherwise you will hit with an error while starting the PDB 

1. Create tablespace ggs_tblsp in both container OGGDB2 and Pluggable PDB2

Create tablespace ggs_tblsp in both container and pluggable as

create tablespace ggs_tblsp datafile '/u01/app/oracle/oradata/GGDB2/gg.dbf' size 2G;

Connect to Pluggable (pdb2):

create tablespace ggs_tblsp datafile '/u01/app/oracle/oradata/GGDB2/pdb2/gg.dbf' size 2G;

2. Create a user in container database with prefix c##.

Note: In 19c this user is common to all the pluggables present. (In 19c all common users and roles are created with prefix c##)

create user c##sourcegg2 identified by Welcome1 default tablespace ggs_tblsp;

grant dba to c##sourcegg2 container=all; 

exec dbms_goldengate_auth.grant_admin_privilege ('c##sourcegg2',container=>'all');

we have successfully completed the Oracle 19C golden gate pre-requisites for replication on both golden gate servers.

Thanks,

Srini

ADRCI (Automatic Diagnostic Repository Command Interpreter) in Oracle 19c Lab Exercise

 Hi All,

In this post i am going to share about ADRCI useful Handson Lab exercise. 

ADRCI (Automatic Diagnostic Repository Command Interpreter) in Oracle  19c a command-line tool used to investigate database problems, view health checks and manage diagnostic data , It is primarily used to troubleshoot database errors, read alert logs, and package incident data for Oracle Support.

ensure this $ORACLE_HOME/bin should added in your OS path.

Connect to ADRCI prompt:

set home if you are using multiple homes in same server .

if you want to set the new home >> set homepath <newhomepath>

check the alert log for all database , listener , tns and other alerts on database use below command

give 1 option to check database alert log, 4 option for listener logs .... Q for quit .

if you are not given any option it will gives an error .. 

if you want to see specific home set the homepath then use commands ..

how to delete the old alert or trace .. ?

purge -age 600 -type ALERT ( it will purge older than 600 minutes )

LONGP_POLICY is used to purge below data . Default value is 365 days.

>> ALERT ,INCIDENT, SWEEP etc .

SHORTP_POLICY is used to purge for below data Default value is 30 days.

>> TRACE , CDUMP  etc ..

ADRCI >> Control policy 

if you want to set custom policies :

i have reduced shortp_policy from 720 t0 240 

adrci>  set control (LONGP_POLICY = 8760)

adrci> set control (SHORTP_POLICY = 720)

adrci>

check the incident and create package using adrci

pack all incident with in the specific time frame :

adrci> ips pack time '2026-05-20 12:00:00.00' to '2026-05-21 13:00:00.00'

 

check the package details - all package details 

specific package details :

How to Delete the complete package using adrci 

adrci> ips delete package 2

how to Remove incidents from the packages using adrci 

adrci > ips remove incident 2 package 1

How to Remove the problem keys from packages using adrci 

adrci > ips remove problem 4 package 3

Thanks,

Srini