Apply RU on Database 19c

  Apply RU on Database 19c

Caution:  It is provided for educational purposes only. It has been tested internally, however; we do not guarantee that it will work for you. Ensure that you run it in your test environment before using.

Applying RU (Release Update) on Oracle Database 19c

Goal: We are going to apply Patch 30557433 – Database Release Update 19.4.0.0.190716

Table of Contents
___________________________________________________________________________________

1. Environment
2. Introduction
3. Download the patch from MOS (My Oracle Support)
4. Unzip patch
5. List patches which were applied
6. Check Conflict
7. Shutdown Databaseand  LISTENER
8. Backup Oracle Home / Inventory
9. Apply Patch
10. Startup Database
11. Apply SQL changes (datapatch)
12. Verify from dba_registry_sqlpatch
13. Start LISTENER
14. Verify INVALID objects
__________________________________________________________________________________

1. Environment

Platform   : Linuxx86_64

Server IP  : 

DB Version : Oracle 19c, File system: Normal, RAC: Non-RAC

DB Name    : orcl

Oracle Home: 

2. Introduction

What is an RU? Release Update (formerly known as Proactive Bundle Patches).

 

RU are the second number,eg.19.6.0.0.0

 

Each release update can also be updated with PSUs, still the last number, for example 19.6.0.0.200114

 

You must use the OPatch utility version 12.2.0.1.17 or later

 

3. Download the patch from MOS (My Oracle Support)

https://updates.oracle.com/download/30557433.html

4. Unzip patch 

5. List patches which were applied

6. Check Conflict

7. Shutdown Database and LISTENER

8. Backup Oracle Home / Inventory

      Already done

9.Apply Patch

10. Startup Database

11.Apply SQL changes (datapatch)

12. Verify from dba_registry_sqlpatch

SET LINESIZE 500

SET PAGESIZE 1000

SET SERVEROUT ON

SET LONG 2000000

COLUMN action_time FORMAT A12

COLUMN action FORMAT A10

COLUMN patch_type FORMAT A10

COLUMN description FORMAT A32

COLUMN status FORMAT A10

COLUMN version FORMAT A10

alter session set "_exclude_seed_cdb_view"=FALSE;

select CON_ID,

TO_CHAR(action_time, 'YYYY-MM-DD') AS action_time,

PATCH_ID,

PATCH_TYPE,

ACTION,

DESCRIPTION,

SOURCE_VERSION,

TARGET_VERSION

from CDB_REGISTRY_SQLPATCH

order by CON_ID, action_time, patch_id;

13. Start LISTENER

14. Verify INVALID objects