Monday 17 February 2020

Apply Patch on 12c RAC Database in rolling fashion step by step-Patch 30116802(GI OCT 2019)


Apply Patch on 12c RAC Database in rolling fashion step by step-Patch 30116802(GI OCT 2019)


Patch details
==============
Patch 30116802: GI OCT 2019 RELEASE UPDATE 12.2.0.1.191015

Note : This patch will used for both Grid Home and Database patching and before applying patch on rdbms home ,it need to applied on Grid Home



1) Download GI OCT 2019 (Patch 30116802) from Oracle support
and Unzip the Latest OPatch to all cluster nodes using Grid user
chown oracrs:dba p28349311_121020_AIX64-5L.zip
unzip p30116802_122010_AIX64-5L.zip


2) Stop oem Agent and Oswatcher on both node in case it is running
3) check free space in RDBMS Home (atleast 15 GB free space) and /TMP


node1[/home/TestDB]$ cd $ORACLE_HOME
node1[/u01/oracle/TestDB/product/12.2.0.1]$ df -g .
Filesystem GB blocks Free %Used Iused %Iused Mounted on
/dev/sampptu01lv 35.00 10.00 72% 93983 4% /u01
node1[/u01/oracle/TestDB/product/12.2.0.1]$


From 12c second release ,Oracle provide command to check necessary space required during patching as below

For Database home, as home user:

Create file /tmp/patch_list_dbhome.txt with the following content:

% cat /tmp/patch_list_dbhome.txt
<UNZIPPED_PATCH_LOCATION>/30116802/30138470
<UNZIPPED_PATCH_LOCATION>/30116802/30122814

Run opatch command to check if enough free space is available in the Database Home:

% $ORACLE_HOME/OPatch/opatch prereq CheckSystemSpace -phBaseFile /tmp/patch_list_dbhome.txt



4) Stop database instance on node1

srvctl stop instance -d testdb -i testdb1 -o immediate

5) Take backup of oracle RDBMS home and inventory on node1(delete unnecessary log from RDBMS home, otherwise backup will take more time , remove file like old trc, aud log

find . -name '*.trc' -mtime +10 -exec ls -lrt {} \;

find . -name '*.trc' -mtime +10 -exec rm -rf {} \;

find . -name '*.aud' -mtime +10 -exec ls -lrt {} \;

find . -name '*.aud' -mtime +10 -exec rm -rf {} \;



Backup Oracle home Backup

cd /u01/oracle/testdb/product/12.2.0.1

tar -cvf /oswatcher/oracle_home_database.tar .

du -sg /oswatcher/oracle_home_database.tar

Backup for inventory

cd /u02/oracle/oraInventory

tar -cvf /staging/Cent_oracle_home_inventory.tar .
du -hP center_oracle_home_inventory.tar



6)Star database instance on node1 and verify
ps -ef|grep pmon
ps -ef|grep tns

srvctl start instance -d testdb -i testdb1
Since opatchauto will stop database automatically while patching .Database instance should be up and running

7) Validate inventory using using opatch lsinventory 8) Verify database registry

select to_char(action_time,'DD-MON-YYYY') as action_time_2, patch_id, patch_uid, action, version, description from dba_registry_sqlpatch order by action_time;

9) check invalid objects , components on database

set head on feed on pagesize 200 linesize 200
select owner, object_name, object_type from dba_objects where owner in ('SYS','SYSTEM') and status like 'INVALID';
col action_time format a13;
col action format a10;
col namespace format a10;
col comments format a25;
col version format a13;
set lin 200 head on feed on pagesize 100;
select i.instance_name,r.* from v$instance i, registry$history r;

10) run gather stats for dictionary

EXECUTE dbms_stats.gather_dictionary_stats;

11) Check opatch version and recommended to have latest opatch and download it from oracle support (6880880) and unzip it in instance Home after renaming Old Opatch folder
We must use the OPatch utility version 12.2.0.1.17 or later to apply this patch for all platforms

or

To update Opatch, use the following instructions:

A. Download the OPatch utility to a temporary directory.
B. For each Oracle RAC database home that are being patched, run the following commands as the home owner to extract the OPatch utility.

$ unzip <OPATCH-ZIP> -d <ORACLE_HOME>


chown instance_owner:dba p6880880_122010_AIX64-5L.zip


12) verify version opatch version and Perform Validation of Oracle Home Inventory on both node


$ <ORACLE_HOME>/OPatch/opatch version

<ORACLE_HOME>/OPatch/opatch lsinventory -detail -oh <ORACLE_HOME>

13) Verify the Patches on both GI and RDBMS HOMES:


$ORACLE_HOME/OPatch/opatch lsinventory -oh $RDBMS_HOME
$ORACLE_HOME/OPatch/opatch lsinventory -oh $RDBMS_HOME | grep <patch no>


14 ) Run OPatch Conflict Check

Determine whether any currently installed one-off patches conflict with this patch 30116802 as follows:

For Database home, as home user:

% $ORACLE_HOME/OPatch/opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir <UNZIPPED_PATCH_LOCATION>/30116802/30138470
% $ORACLE_HOME/OPatch/opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir <UNZIPPED_PATCH_LOCATION>/30116802/30122814
eg

For Database home, as home user:

/u01/oracle/TestDB/product/12.2.0.1/OPatch/opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir /oswatcher/2020_patch/30116802/30138470
/u01/oracle/TestDB/product/12.2.0.1/OPatch/opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir /oswatcher/2020_patch/30116802/30122814


15) run analyze command using opatchauto from root user after setting proper path ,we must carefully should give Oracle home path

#ORACLE_HOME/OPatch/opatchauto apply <UNZIPPED_PATCH_LOCATION>/26635815 -analyze -oh <ORACLE_RAC_HOME>
ed


[node1:root:/u06/oracle/testdb/product/12.1.0.2/OPatch:]

export PATH=$PATH:/u06/oracle/testdb/product/12.1.0.2/OPatch
cd /u06/oracle/testdb/product/12.1.0.2/OPatch


./opatchauto apply /oswatcher/28349311 -analyze -oh /u06/oracle/testdb/product/12.1.0.2


16) Apply patch from opatchauto on root user on Oracle Home

[node1:root:/u01/oracle/sam44ppt/product/12.2.0.1/OPatch:]
[node1:root:/u01/oracle/sam44ppt/product/12.2.0.1/OPatch:]
[node1:root:/u01/oracle/sam44ppt/product/12.2.0.1/OPatch:] ps -ef|grep pmon
oracrs 15990844 1 0 08:48:18 - 0:01 asm_pmon_+ASM1
root 47907058 47448286 1 05:20:52 pts/1 0:00 grep pmon
oracrs 50724900 1 0 08:50:07 - 0:01 mdb_pmon_-MGMTDB
oracrs 53411842 1 0 08:48:38 - 0:00 apx_pmon_+APX1
sam44ppt 27328982 1 0 05:15:12 - 0:00 ora_pmon_SAM44PPT1
[node1:root:/u01/oracle/sam44ppt/product/12.2.0.1/OPatch:] id
uid=0(root) gid=0(system) groups=208(tivlogs)
[node1:root:/u01/oracle/sam44ppt/product/12.2.0.1/OPatch:] echo $PATH
/usr/bin:/etc:/usr/sbin:/usr/ucb:/usr/bin/X11:/sbin:/usr/java7_64/jre/bin:/usr/java7_64/bin:/usr/local/bin:/usr/ETC/bin:/opt/DoOnceAIX/SecTools/aix64db2cops:/opt/DoOnceAIX/SecTools/aixdb2cops:/opt/DoOnceAIX/SecTools/aixtsmcops:/opt/DoOnceAIX/SecTools/logkeeper:/opt/DoOnceAIX/SecTools/loglooker:/u01/oracle/sam44ppt/product/12.2.0.1/OPatch
[node1:root:/u01/oracle/sam44ppt/product/12.2.0.1/OPatch:] opatchauto apply /oswatcher/2020_patch/30116802 -analyze -oh /u01/oracle/sam44ppt/product/12.2.0.1
[node1:root:/u01/oracle/sam44ppt/product/12.2.0.1/OPatch:] ./opatchauto apply /oswatcher/2020_patch/30116802 -analyze -oh /u01/oracle/sam44ppt/product/12.2.0.1

Start database instance instances on node1 if not started automatically


17)verify patch details
ps -ef|grep pmon
ps -ef|grep tns

patch lsinventory
select * from dba_registry_sqlpatch;


On second node repeat above same steps

But on apply patch on second node , It will apply patch on Oracle Home as well as Load modified SQL Files into the Database as well ( there is no need to run catbundle or datapatch)

Note:
The step "Loading Modified SQL Files into the Database" has been removed from this section as the execution of opatchauto automatically performs the load of the modified SQL files into the Database.


Start database database instances on node2 in case not started automatically

you may see invalid objects after execution of datapatch in the previous step. If this is the case, run utlrp.sql to revalidate these objects.
cd $ORACLE_HOME/rdbms/admin
sqlplus /nolog
SQL> CONNECT / AS SYSDBA
SQL> @utlrp.sql


18 ) Upgrade Oracle Recovery Manager Catalog

If you are using the Oracle Recovery Manager, the catalog needs to be upgraded. Enter the following command to upgrade it. The UPGRADE CATALOG command must be entered twice to confirm the upgrade.



$ rman catalog username/password@alias


RMAN> UPGRADE CATALOG;
RMAN> UPGRADE CATALOG;
RMAN> EXIT;

19)verify select * from dba_registry_sqlpatch ;
20)Validate objects , components and verify if patch is installed properly
21)Start the application and Release all related jobs which were on hold
22)Application team will check the application if that working as it is





Details steps
------------------

1) node1[/home/TestDB]$ cd $ORACLE_HOME
node1[/u01/oracle/TestDB/product/12.2.0.1]$ df -g .
Filesystem GB blocks Free %Used Iused %Iused Mounted on
/dev/sampptu01lv 35.00 10.00 72% 93983 4% /u01
node1[/u01/oracle/TestDB/product/12.2.0.1]$


verify space using newly oracle provided script

For Database home, as home user:

Create file /tmp/patch_list_dbhome.txt with the following content:

% cat /tmp/patch_list_dbhome.txt
<UNZIPPED_PATCH_LOCATION>/30116802/30138470
<UNZIPPED_PATCH_LOCATION>/30116802/30122814

Run opatch command to check if enough free space is available in the Database Home:

% $ORACLE_HOME/OPatch/opatch prereq CheckSystemSpace -phBaseFile /tmp/patch_list_dbhome.txt



vi /tmp/patch_list_dbhome.txt


/oswatcher/2020_patch/30116802/30138470
/oswatcher/2020_patch/30116802/30122814



node1[/u01/oracle/TestDB/product/12.2.0.1]$
node1[/u01/oracle/TestDB/product/12.2.0.1]$ cd OPatch
node1[/u01/oracle/TestDB/product/12.2.0.1/OPatch]$ id
uid=257(TestDB) gid=207(oinstall) groups=1(staff),203(dba),206(gprd),220(controlm),212(asmdba)
node1[/u01/oracle/TestDB/product/12.2.0.1/OPatch]$
node1[/u01/oracle/TestDB/product/12.2.0.1/OPatch]$ opatch prereq CheckSystemSpace -phBaseFile /tmp/patch_list_dbhome.txt
Oracle Interim Patch Installer version 12.2.0.1.14
Copyright (c) 2020, Oracle Corporation. All rights reserved.

PREREQ session

Oracle Home : /u01/oracle/TestDB/product/12.2.0.1
Central Inventory : /u02/oracle/oraInventory
from : /u01/oracle/TestDB/product/12.2.0.1/oraInst.loc
OPatch version : 12.2.0.1.14
OUI version : 12.2.0.1.4
Log file location : /u01/oracle/TestDB/product/12.2.0.1/cfgtoollogs/opatch/opatch2020-02-15_12-33-41PM_1.log

Invoking prereq "checksystemspace"

Prereq "checkSystemSpace" failed.

The details are:
Required amount of space(13768.217MB) is not available.

OPatch succeeded.
node1[/u01/oracle/TestDB/product/12.2.0.1/OPatch]$

After adding space ,it is passed

---------------------------

node1[/u01/oracle/TestDB/product/12.2.0.1/OPatch]$ opatch prereq CheckSystemSpace -phBaseFile /tmp/patch_list_dbhome.txt
Oracle Interim Patch Installer version 12.2.0.1.14
Copyright (c) 2020, Oracle Corporation. All rights reserved.

PREREQ session

Oracle Home : /u01/oracle/TestDB/product/12.2.0.1
Central Inventory : /u02/oracle/oraInventory
from : /u01/oracle/TestDB/product/12.2.0.1/oraInst.loc
OPatch version : 12.2.0.1.14
OUI version : 12.2.0.1.4
Log file location : /u01/oracle/TestDB/product/12.2.0.1/cfgtoollogs/opatch/opatch2020-02-15_12-46-38PM_1.log

Invoking prereq "checksystemspace"

Prereq "checkSystemSpace" passed.

OPatch succeeded.
node1[/u01/oracle/TestDB/product/12.2.0.1/OPatch]$


3) update opatch version

node1[/u01/oracle/TestDB/product/12.2.0.1]$ mv OPatch OPatch_feb16
node1[/u01/oracle/TestDB/product/12.2.0.1]$


ls -ltr /oswatcher/2020_patch


cp /oswatcher/2020_patch/p6880880_122010_AIX64-5L.zip /u01/oracle/TestDB/product/12.2.0.1/

unzip p6880880_122010_AIX64-5L.zip

opatch version
node1[/u01/oracle/TestDB/product/12.2.0.1/OPatch]$ opatch version
OPatch Version: 12.2.0.1.19

OPatch succeeded.
node1[/u01/oracle/TestDB/product/12.2.0.1/OPatch]$


opatch lsiventory

node1[/u01/oracle/TestDB/product/12.2.0.1/OPatch]$ opatch lsinventory
Oracle Interim Patch Installer version 12.2.0.1.19
Copyright (c) 2020, Oracle Corporation. All rights reserved.


Oracle Home : /u01/oracle/TestDB/product/12.2.0.1
Central Inventory : /u02/oracle/oraInventory
from : /u01/oracle/TestDB/product/12.2.0.1/oraInst.loc
OPatch version : 12.2.0.1.19
OUI version : 12.2.0.1.4
Log file location : /u01/oracle/TestDB/product/12.2.0.1/cfgtoollogs/opatch/opatch2020-02-16_04-29-02AM_1.log

Lsinventory Output file location : /u01/oracle/TestDB/product/12.2.0.1/cfgtoollogs/opatch/lsinv/lsinventory2020-02-16_04-29-02AM.txt
--------------------------------------------------------------------------------
Local Machine Information::
Hostname: node1
ARU platform id: 212
ARU platform description:: IBM_AIX

Installed Top-level Products (1):

Oracle Database 12c 12.2.0.1.0
There are 1 products installed in this Oracle Home.


Interim patches (3) :

Patch 28440725 : applied on Thu May 30 12:04:31 BST 2019
Unique Patch ID: 22458824
Patch description: "OJVM RELEASE UPDATE: 12.2.0.1.181016 (28440725)"
Created on 21 Sep 2018, 09:08:40 hrs UTC
Bugs fixed:
25811105, 25890046, 26023042, 26570134, 27000702, 27461740, 27952586
27642235, 27539876, 28502098


opatch lsinventory -detail -oh /u01/oracle/TestDB/product/12.2.0.1


4) shutdown database and take backup of home and inventory

node1[/u01/oracle/TestDB/product/12.2.0.1/OPatch]$
node1[/u01/oracle/TestDB/product/12.2.0.1/OPatch]$ ps -ef|grep pmon
oracrs 15990844 1 0 08:48:18 - 0:01 asm_pmon_+ASM1
TestDB 19726514 1 0 12:18:28 - 0:04 ora_pmon_TestDB1
oracrs 50724900 1 0 08:50:07 - 0:01 mdb_pmon_-MGMTDB
oracrs 53411842 1 0 08:48:38 - 0:00 apx_pmon_+APX1
TestDB 5439984 17956886 1 04:36:18 pts/0 0:00 grep pmon
node1[/u01/oracle/TestDB/product/12.2.0.1/OPatch]$


srvctl stop instance -d TestDB -i TestDB1 -o immediate



Backup home
----------------
cd /u01/oracle/TestDB/product/12.2.0.1

tar -cvf /oswatcher/oracle_home_database.tar .

du -sg /oswatcher/oracle_home_database.tar

Backup for inventory

cd /u02/oracle/oraInventory

tar -cvf /staging/Cent_oracle_home_inventory.tar .
du -hP center_oracle_home_inventory.tar


cd /u01/oracle/TestDB/product/12.2.0.1

tar -cvf /staging/oracle_home_inventory.tar .
du -hP oracle_home_inventory.tar

start database

srvctl start instance -d TestDB -i TestDB1



5) Run OPatch Conflict Check



For Database home, as home user:

% $ORACLE_HOME/OPatch/opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir <UNZIPPED_PATCH_LOCATION>/30116802/30138470
% $ORACLE_HOME/OPatch/opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir <UNZIPPED_PATCH_LOCATION>/30116802/30122814


For Database home, as home user:

/u01/oracle/TestDB/product/12.2.0.1/OPatch/opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir /oswatcher/2020_patch/30116802/30138470
/u01/oracle/TestDB/product/12.2.0.1/OPatch/opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir /oswatcher/2020_patch/30116802/30122814

node1[/u01/oracle/TestDB/product/12.2.0.1/OPatch]$ /u01/oracle/TestDB/product/12.2.0.1/OPatch/opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir /oswatcher/2020_patch/30116802/30138470
Oracle Interim Patch Installer version 12.2.0.1.19
Copyright (c) 2020, Oracle Corporation. All rights reserved.

PREREQ session

Oracle Home : /u01/oracle/TestDB/product/12.2.0.1
Central Inventory : /u02/oracle/oraInventory
from : /u01/oracle/TestDB/product/12.2.0.1/oraInst.loc
OPatch version : 12.2.0.1.19
OUI version : 12.2.0.1.4
Log file location : /u01/oracle/TestDB/product/12.2.0.1/cfgtoollogs/opatch/opatch2020-02-16_04-54-10AM_1.log

Invoking prereq "checkconflictagainstohwithdetail"

Prereq "checkConflictAgainstOHWithDetail" passed.

OPatch succeeded.
node1[/u01/oracle/TestDB/product/12.2.0.1/OPatch]$ /u01/oracle/TestDB/product/12.2.0.1/OPatch/opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir /oswatcher/2020_patch/30116802/30122814
Oracle Interim Patch Installer version 12.2.0.1.19
Copyright (c) 2020, Oracle Corporation. All rights reserved.

PREREQ session

Oracle Home : /u01/oracle/TestDB/product/12.2.0.1
Central Inventory : /u02/oracle/oraInventory
from : /u01/oracle/TestDB/product/12.2.0.1/oraInst.loc
OPatch version : 12.2.0.1.19
OUI version : 12.2.0.1.4
Log file location : /u01/oracle/TestDB/product/12.2.0.1/cfgtoollogs/opatch/opatch2020-02-16_04-54-28AM_1.log

Invoking prereq "checkconflictagainstohwithdetail"

Prereq "checkConflictAgainstOHWithDetail" passed.

OPatch succeeded.
node1[/u01/oracle/TestDB/product/12.2.0.1/OPatch]$




6) One-off Patch Conflict Detection and Resolutio from root user

cd /u01/oracle/TestDB/product/12.2.0.1/OPatch

export PATH=$PATH:/u01/oracle/TestDB/product/12.2.0.1/OPatch

/u01/oracle/TestDB/product/12.2.0.1/OPatch/opatchauto apply /oswatcher/2020_patch/30116802 -analyze -oh /u01/oracle/TestDB/product/12.2.0.1

eg

[node1:root:/u01/oracle/TestDB/product/12.2.0.1/OPatch:]
[node1:root:/u01/oracle/TestDB/product/12.2.0.1/OPatch:]
[node1:root:/u01/oracle/TestDB/product/12.2.0.1/OPatch:]
[node1:root:/u01/oracle/TestDB/product/12.2.0.1/OPatch:] ps -ef|grep pmon
oracrs 15990844 1 0 08:48:18 - 0:01 asm_pmon_+ASM1
root 47907058 47448286 1 05:20:52 pts/1 0:00 grep pmon
oracrs 50724900 1 0 08:50:07 - 0:01 mdb_pmon_-MGMTDB
oracrs 53411842 1 0 08:48:38 - 0:00 apx_pmon_+APX1
TestDB 27328982 1 0 05:15:12 - 0:00 ora_pmon_TestDB1
[node1:root:/u01/oracle/TestDB/product/12.2.0.1/OPatch:] id
uid=0(root) gid=0(system) groups=208(tivlogs)
[node1:root:/u01/oracle/TestDB/product/12.2.0.1/OPatch:] echo $PATH
/usr/bin:/etc:/usr/sbin:/usr/ucb:/usr/bin/X11:/sbin:/usr/java7_64/jre/bin:/usr/java7_64/bin:/usr/local/bin:/usr/ETC/bin:/opt/DoOnceAIX/SecTools/aix64db2cops:/opt/DoOnceAIX/SecTools/aixdb2cops:/opt/DoOnceAIX/SecTools/aixtsmcops:/opt/DoOnceAIX/SecTools/logkeeper:/opt/DoOnceAIX/SecTools/loglooker:/u01/oracle/TestDB/product/12.2.0.1/OPatch
[node1:root:/u01/oracle/TestDB/product/12.2.0.1/OPatch:] opatchauto apply /oswatcher/2020_patch/30116802 -analyze -oh /u01/oracle/TestDB/product/12.2.0.1
[node1:root:/u01/oracle/TestDB/product/12.2.0.1/OPatch:] ./opatchauto apply /oswatcher/2020_patch/30116802 -analyze -oh /u01/oracle/TestDB/product/12.2.0.1

OPatchauto session is initiated at Sun Feb 16 05:22:21 2020

System initialization log file is /u01/oracle/TestDB/product/12.2.0.1/cfgtoollogs/opatchautodb/systemconfig2020-02-16_05-22-48AM.log.

Session log file is /u01/oracle/TestDB/product/12.2.0.1/cfgtoollogs/opatchauto/opatchauto2020-02-16_05-25-53AM.log
The id for this session is DADB

Executing OPatch prereq operations to verify patch applicability on home /u01/oracle/TestDB/product/12.2.0.1
Patch applicability verified successfully on home /u01/oracle/TestDB/product/12.2.0.1


Verifying SQL patch applicability on home /u01/oracle/TestDB/product/12.2.0.1
SQL patch applicability verified successfully on home /u01/oracle/TestDB/product/12.2.0.1

OPatchAuto successful.

--------------------------------Summary--------------------------------

Analysis for applying patches has completed successfully:

Host:node1
RAC Home:/u01/oracle/TestDB/product/12.2.0.1
Version:12.2.0.1.0


==Following patches were SKIPPED:

Patch: /oswatcher/2020_patch/30116802/30122828
Reason: This patch is not applicable to this specified target type - "rac_database"

Patch: /oswatcher/2020_patch/30116802/26839277
Reason: This patch is not applicable to this specified target type - "rac_database"

Patch: /oswatcher/2020_patch/30116802/30093408
Reason: This patch is not applicable to this specified target type - "rac_database"


==Following patches were SUCCESSFULLY analyzed to be applied:

Patch: /oswatcher/2020_patch/30116802/30122814
Log: /u01/oracle/TestDB/product/12.2.0.1/cfgtoollogs/opatchauto/core/opatch/opatch2020-02-16_05-26-32AM_1.log

Patch: /oswatcher/2020_patch/30116802/30138470
Log: /u01/oracle/TestDB/product/12.2.0.1/cfgtoollogs/opatchauto/core/opatch/opatch2020-02-16_05-26-32AM_1.log



OPatchauto session completed at Sun Feb 16 05:30:05 2020
Time taken to complete the session 7 minutes, 46 seconds
[node1:root:/u01/oracle/TestDB/product/12.2.0.1/OPatch:]






7) apply patch using opatchauto from root user and make sure database is up and running and
As part of patching process, database would brough down automatically and applied applied and bring up automatically


cd /u01/oracle/TestDB/product/12.2.0.1/OPatch

export PATH=$PATH:/u01/oracle/TestDB/product/12.2.0.1/OPatch



./opatchauto apply /oswatcher/2020_patch/30116802 -oh /u01/oracle/TestDB/product/12.2.0.1

eg


[node1:root:/u01/oracle/TestDB/product/12.2.0.1/OPatch:]
[node1:root:/u01/oracle/TestDB/product/12.2.0.1/OPatch:] ./opatchauto apply /oswatcher/2020_patch/30116802 -oh /u01/oracle/TestDB/product/12.2.0.1

OPatchauto session is initiated at Sun Feb 16 05:32:43 2020

System initialization log file is /u01/oracle/TestDB/product/12.2.0.1/cfgtoollogs/opatchautodb/systemconfig2020-02-16_05-33-02AM.log.

Session log file is /u01/oracle/TestDB/product/12.2.0.1/cfgtoollogs/opatchauto/opatchauto2020-02-16_05-35-06AM.log
The id for this session is JUBZ

Executing OPatch prereq operations to verify patch applicability on home /u01/oracle/TestDB/product/12.2.0.1
Patch applicability verified successfully on home /u01/oracle/TestDB/product/12.2.0.1


Verifying SQL patch applicability on home /u01/oracle/TestDB/product/12.2.0.1
SQL patch applicability verified successfully on home /u01/oracle/TestDB/product/12.2.0.1


Preparing to bring down database service on home /u01/oracle/TestDB/product/12.2.0.1
Successfully prepared home /u01/oracle/TestDB/product/12.2.0.1 to bring down database service


Bringing down database service on home /u01/oracle/TestDB/product/12.2.0.1
Following database(s) and/or service(s) are stopped and will be restarted later during the session: TestDB
Database service successfully brought down on home /u01/oracle/TestDB/product/12.2.0.1


Performing prepatch operation on home /u01/oracle/TestDB/product/12.2.0.1
Perpatch operation completed successfully on home /u01/oracle/TestDB/product/12.2.0.1


Start applying binary patch on home /u01/oracle/TestDB/product/12.2.0.1
Successfully executed command: /usr/sbin/slibclean

Binary patch applied successfully on home /u01/oracle/TestDB/product/12.2.0.1


Performing postpatch operation on home /u01/oracle/TestDB/product/12.2.0.1
Postpatch operation completed successfully on home /u01/oracle/TestDB/product/12.2.0.1


Starting database service on home /u01/oracle/TestDB/product/12.2.0.1
Database service successfully started on home /u01/oracle/TestDB/product/12.2.0.1


Preparing home /u01/oracle/TestDB/product/12.2.0.1 after database service restarted
No step execution required.........


Trying to apply SQL patch on home /u01/oracle/TestDB/product/12.2.0.1
SQL patch applied successfully on home /u01/oracle/TestDB/product/12.2.0.1

OPatchAuto successful.

--------------------------------Summary--------------------------------

Patching is completed successfully. Please find the summary as follows:

Host:node1
RAC Home:/u01/oracle/TestDB/product/12.2.0.1
Version:12.2.0.1.0
Summary:

==Following patches were SKIPPED:

Patch: /oswatcher/2020_patch/30116802/30122828
Reason: This patch is not applicable to this specified target type - "rac_database"

Patch: /oswatcher/2020_patch/30116802/26839277
Reason: This patch is not applicable to this specified target type - "rac_database"

Patch: /oswatcher/2020_patch/30116802/30093408
Reason: This patch is not applicable to this specified target type - "rac_database"


==Following patches were SUCCESSFULLY applied:

Patch: /oswatcher/2020_patch/30116802/30122814
Log: /u01/oracle/TestDB/product/12.2.0.1/cfgtoollogs/opatchauto/core/opatch/opatch2020-02-16_05-39-10AM_1.log

Patch: /oswatcher/2020_patch/30116802/30138470
Log: /u01/oracle/TestDB/product/12.2.0.1/cfgtoollogs/opatchauto/core/opatch/opatch2020-02-16_05-39-10AM_1.log



OPatchauto session completed at Sun Feb 16 05:52:44 2020
Time taken to complete the session 20 minutes, 2 seconds
[node1:root:/u01/oracle/TestDB/product/12.2.0.1/OPatch:]



- Apply patch on second node------------------

node1[/u01/oracle/TestDB/product/12.2.0.1/OPatch]$ /u01/oracle/TestDB/product/12.2.0.1/OPatch/opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir /oswatcher/2020_patch/30116802/30138470
Oracle Interim Patch Installer version 12.2.0.1.19
Copyright (c) 2020, Oracle Corporation. All rights reserved.

PREREQ session

Oracle Home : /u01/oracle/TestDB/product/12.2.0.1
Central Inventory : /u02/oracle/oraInventory
from : /u01/oracle/TestDB/product/12.2.0.1/oraInst.loc
OPatch version : 12.2.0.1.19
OUI version : 12.2.0.1.4
Log file location : /u01/oracle/TestDB/product/12.2.0.1/cfgtoollogs/opatch/opatch2020-02-16_06-45-36AM_1.log

Invoking prereq "checkconflictagainstohwithdetail"

Prereq "checkConflictAgainstOHWithDetail" passed.

OPatch succeeded.
node1[/u01/oracle/TestDB/product/12.2.0.1/OPatch]$ /u01/oracle/TestDB/product/12.2.0.1/OPatch/opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir /oswatcher/2020_patch/30116802/30122814
Oracle Interim Patch Installer version 12.2.0.1.19
Copyright (c) 2020, Oracle Corporation. All rights reserved.

PREREQ session

Oracle Home : /u01/oracle/TestDB/product/12.2.0.1
Central Inventory : /u02/oracle/oraInventory
from : /u01/oracle/TestDB/product/12.2.0.1/oraInst.loc
OPatch version : 12.2.0.1.19
OUI version : 12.2.0.1.4
Log file location : /u01/oracle/TestDB/product/12.2.0.1/cfgtoollogs/opatch/opatch2020-02-16_06-45-53AM_1.log

Invoking prereq "checkconflictagainstohwithdetail"

Prereq "checkConflictAgainstOHWithDetail" passed.

OPatch succeeded.
node1[/u01/oracle/TestDB/product/12.2.0.1/OPatch]$ exit
node1[/home/eibm994]$ sudo su -
[YOU HAVE NEW MAIL]
[node1:root:/home/root:] cd /u01/oracle/TestDB/product/12.2.0.1/OPatch
[node1:root:/u01/oracle/TestDB/product/12.2.0.1/OPatch:] export PATH=$PATH:/u01/oracle/TestDB/product/12.2.0.1/OPatch
[node1:root:/u01/oracle/TestDB/product/12.2.0.1/OPatch:] /u01/oracle/TestDB/product/12.2.0.1/OPatch/opatchauto apply /oswatcher/2020_patch/30116802 -analyze -oh /u01/oracle/TestDB/product/12.2.0.1

OPatchauto session is initiated at Sun Feb 16 06:46:52 2020

System initialization log file is /u01/oracle/TestDB/product/12.2.0.1/cfgtoollogs/opatchautodb/systemconfig2020-02-16_06-47-13AM.log.

Session log file is /u01/oracle/TestDB/product/12.2.0.1/cfgtoollogs/opatchauto/opatchauto2020-02-16_06-49-23AM.log
The id for this session is 6713

Executing OPatch prereq operations to verify patch applicability on home /u01/oracle/TestDB/product/12.2.0.1
Patch applicability verified successfully on home /u01/oracle/TestDB/product/12.2.0.1


Verifying SQL patch applicability on home /u01/oracle/TestDB/product/12.2.0.1
SQL patch applicability verified successfully on home /u01/oracle/TestDB/product/12.2.0.1

OPatchAuto successful.

--------------------------------Summary--------------------------------

Analysis for applying patches has completed successfully:

Host:node1
RAC Home:/u01/oracle/TestDB/product/12.2.0.1
Version:12.2.0.1.0


==Following patches were SKIPPED:

Patch: /oswatcher/2020_patch/30116802/30122828
Reason: This patch is not applicable to this specified target type - "rac_database"

Patch: /oswatcher/2020_patch/30116802/26839277
Reason: This patch is not applicable to this specified target type - "rac_database"

Patch: /oswatcher/2020_patch/30116802/30093408
Reason: This patch is not applicable to this specified target type - "rac_database"


==Following patches were SUCCESSFULLY analyzed to be applied:

Patch: /oswatcher/2020_patch/30116802/30122814
Log: /u01/oracle/TestDB/product/12.2.0.1/cfgtoollogs/opatchauto/core/opatch/opatch2020-02-16_06-49-55AM_1.log

Patch: /oswatcher/2020_patch/30116802/30138470
Log: /u01/oracle/TestDB/product/12.2.0.1/cfgtoollogs/opatchauto/core/opatch/opatch2020-02-16_06-49-55AM_1.log



OPatchauto session completed at Sun Feb 16 06:53:24 2020
Time taken to complete the session 6 minutes, 33 seconds
[node1:root:/u01/oracle/TestDB/product/12.2.0.1/OPatch:]
[node1:root:/u01/oracle/TestDB/product/12.2.0.1/OPatch:] id
uid=0(root) gid=0(system) groups=208(tivlogs)
[node1:root:/u01/oracle/TestDB/product/12.2.0.1/OPatch:] echo $PATH
/usr/bin:/etc:/usr/sbin:/usr/ucb:/usr/bin/X11:/sbin:/usr/java7_64/jre/bin:/usr/java7_64/bin:/usr/local/bin:/usr/ETC/bin:/opt/DoOnceAIX/SecTools/aix64db2cops:/opt/DoOnceAIX/SecTools/aixdb2cops:/opt/DoOnceAIX/SecTools/aixtsmcops:/opt/DoOnceAIX/SecTools/logkeeper:/opt/DoOnceAIX/SecTools/loglooker:/u01/oracle/TestDB/product/12.2.0.1/OPatch
[node1:root:/u01/oracle/TestDB/product/12.2.0.1/OPatch:] ps -ef|grep pmon
root 65929284 65142854 1 06:55:25 pts/0 0:00 grep pmon
oracrs 2883870 1 0 11:52:12 - 0:00 apx_pmon_+APX2
oracrs 4522416 1 0 11:51:53 - 0:01 asm_pmon_+ASM2
TestDB 12779934 1 0 06:42:48 - 0:00 ora_pmon_TestDB2
[node1:root:/u01/oracle/TestDB/product/12.2.0.1/OPatch:] ./opatchauto apply /oswatcher/2020_patch/30116802 -oh /u01/oracle/TestDB/product/12.2.0.1

OPatchauto session is initiated at Sun Feb 16 06:55:58 2020

System initialization log file is /u01/oracle/TestDB/product/12.2.0.1/cfgtoollogs/opatchautodb/systemconfig2020-02-16_06-56-14AM.log.

Session log file is /u01/oracle/TestDB/product/12.2.0.1/cfgtoollogs/opatchauto/opatchauto2020-02-16_06-58-11AM.log
The id for this session is EAM3

Executing OPatch prereq operations to verify patch applicability on home /u01/oracle/TestDB/product/12.2.0.1
Patch applicability verified successfully on home /u01/oracle/TestDB/product/12.2.0.1


Verifying SQL patch applicability on home /u01/oracle/TestDB/product/12.2.0.1
SQL patch applicability verified successfully on home /u01/oracle/TestDB/product/12.2.0.1


Preparing to bring down database service on home /u01/oracle/TestDB/product/12.2.0.1
Successfully prepared home /u01/oracle/TestDB/product/12.2.0.1 to bring down database service


Bringing down database service on home /u01/oracle/TestDB/product/12.2.0.1
Following database(s) and/or service(s) are stopped and will be restarted later during the session: TestDB
Database service successfully brought down on home /u01/oracle/TestDB/product/12.2.0.1


Performing prepatch operation on home /u01/oracle/TestDB/product/12.2.0.1
Perpatch operation completed successfully on home /u01/oracle/TestDB/product/12.2.0.1


Start applying binary patch on home /u01/oracle/TestDB/product/12.2.0.1
Successfully executed command: /usr/sbin/slibclean

Binary patch applied successfully on home /u01/oracle/TestDB/product/12.2.0.1


Performing postpatch operation on home /u01/oracle/TestDB/product/12.2.0.1
Postpatch operation completed successfully on home /u01/oracle/TestDB/product/12.2.0.1


Starting database service on home /u01/oracle/TestDB/product/12.2.0.1
Database service successfully started on home /u01/oracle/TestDB/product/12.2.0.1


Preparing home /u01/oracle/TestDB/product/12.2.0.1 after database service restarted
No step execution required.........


Trying to apply SQL patch on home /u01/oracle/TestDB/product/12.2.0.1
SQL patch applied successfully on home /u01/oracle/TestDB/product/12.2.0.1

OPatchAuto successful.

--------------------------------Summary--------------------------------

Patching is completed successfully. Please find the summary as follows:

Host:node1
RAC Home:/u01/oracle/TestDB/product/12.2.0.1
Version:12.2.0.1.0
Summary:

==Following patches were SKIPPED:

Patch: /oswatcher/2020_patch/30116802/30122828
Reason: This patch is not applicable to this specified target type - "rac_database"

Patch: /oswatcher/2020_patch/30116802/26839277
Reason: This patch is not applicable to this specified target type - "rac_database"

Patch: /oswatcher/2020_patch/30116802/30093408
Reason: This patch is not applicable to this specified target type - "rac_database"


==Following patches were SUCCESSFULLY applied:

Patch: /oswatcher/2020_patch/30116802/30122814
Log: /u01/oracle/TestDB/product/12.2.0.1/cfgtoollogs/opatchauto/core/opatch/opatch2020-02-16_07-02-55AM_1.log

Patch: /oswatcher/2020_patch/30116802/30138470
Log: /u01/oracle/TestDB/product/12.2.0.1/cfgtoollogs/opatchauto/core/opatch/opatch2020-02-16_07-02-55AM_1.log



OPatchauto session completed at Sun Feb 16 07:18:38 2020
Time taken to complete the session 22 minutes, 41 seconds
[node1:root:/u01/oracle/TestDB/product/12.2.0.1/OPatch:]


Verification

dba_registry_sqlpatch

cd $ORACLE_HOME/rdbms/admin
sqlplus /nolog
SQL> CONNECT / AS SYSDBA
SQL> @utlrp.sql

SQL> select owner, object_name, object_type,status from dba_objects where owner in ('SYS','SYSTEM') and status like 'INVALID'
/
2
no rows selected

SQL> select owner, object_name, object_type,status from dba_objects where status like 'INVALID'
/ 2

no rows selected

SQL> select count(1) from dba_objects where status like 'INVALID'
/
2
COUNT(1)
----------
0

SQL> set lines 200 pages 200
SQL> col action_time format a40
col action format a30
col namespace format a10
col comments format a30
col version format a13
set lin 200 head on feed on pagesize 100
/


select i.instance_name,r.* from v$instance i, registry$history r
/SQL> SQL> SQL> SQL> SQL> SQL>
COUNT(1)
----------
0

1 row selected.

SQL> SQL> SQL> 2

INSTANCE_NAME ACTION_TIME ACTION NAMESPACE VERSION ID COMMENTS BUNDLE_SERIES
---------------- ---------------------------------------- ------------------------------ ---------- ------------- ---------- ------------------------------ ------------------------------
TestDB2 01-OCT-13 10.55.45.938537 PM APPLY SERVER 11.2.0.4 0 Patchset 11.2.0.2.0 PSU
TestDB2 10-OCT-14 10.40.27.269173 AM APPLY SERVER 11.2.0.4 3 PSU 11.2.0.4.3 PSU
TestDB2 14-OCT-14 08.49.10.244673 AM APPLY SERVER 11.2.0.4 3 PSU 11.2.0.4.3 PSU
TestDB2 22-DEC-15 10.58.03.812964 PM APPLY SERVER 11.2.0.4 8 PSU 11.2.0.4.8 PSU
TestDB2 29-DEC-16 05.01.59.430436 PM APPLY SERVER 11.2.0.4 161018 PSU 11.2.0.4.161018 PSU
TestDB2 17-FEB-18 01.18.14.712937 PM APPLY SERVER 11.2.0.4 171017 PSU 11.2.0.4.171017 PSU
TestDB2 BOOTSTRAP DATAPATCH 12.2.0.1 RDBMS_12.2.0.1.0DBOCT2019RU_AI
X.PPC64_190909

TestDB2 17-MAY-19 03.37.08.381001 PM VIEW INVALIDATE 8289601 view invalidation
TestDB2 17-MAY-19 03.41.49.618934 PM UPGRADE SERVER 12.2.0.1.0 Upgraded from 11.2.0.4.0
TestDB2 17-MAY-19 03.44.52.592435 PM APPLY SERVER 12.2.0.1.1810 0 OJVM PSU post-install
16OJVMRU

TestDB2 29-MAY-19 01.19.05.597980 PM jvmpsu.sql SERVER 12.2.0.1.1810 0 RAN jvmpsu.sql
16OJVMRU

TestDB2 29-MAY-19 01.19.05.614035 PM ROLLBACK SERVER 12.2.0.1.1810 0 OJVM PSU post-deinstall
16OJVMRU

TestDB2 29-MAY-19 04.05.33.216384 PM DOWNGRADE
TestDB2 29-MAY-19 11.32.08.327286 PM RELOAD SERVER 11.2.0.4.0 Reloaded after downgrade from
11.2.0

TestDB2 30-MAY-19 03.13.15.237730 PM VIEW INVALIDATE 8289601 view invalidation
TestDB2 30-MAY-19 03.18.38.418612 PM UPGRADE SERVER 12.2.0.1.0 Upgraded from 11.2.0.4.0
TestDB2 30-MAY-19 03.21.37.733353 PM APPLY SERVER 12.2.0.1.1810 0 OJVM PSU post-install
16OJVMRU


17 rows selected.

SQL> set lines 200 pages 200
/

column comp_name format a50
/

SELECT comp_id,comp_name, status, version FROM dba_registry
/SQL>
INSTANCE_NAME ACTION_TIME ACTION NAMESPACE VERSION ID COMMENTS BUNDLE_SERIES
---------------- ---------------------------------------- ------------------------------ ---------- ------------- ---------- ------------------------------ ------------------------------
TestDB2 01-OCT-13 10.55.45.938537 PM APPLY SERVER 11.2.0.4 0 Patchset 11.2.0.2.0 PSU
TestDB2 10-OCT-14 10.40.27.269173 AM APPLY SERVER 11.2.0.4 3 PSU 11.2.0.4.3 PSU
TestDB2 14-OCT-14 08.49.10.244673 AM APPLY SERVER 11.2.0.4 3 PSU 11.2.0.4.3 PSU
TestDB2 22-DEC-15 10.58.03.812964 PM APPLY SERVER 11.2.0.4 8 PSU 11.2.0.4.8 PSU
TestDB2 29-DEC-16 05.01.59.430436 PM APPLY SERVER 11.2.0.4 161018 PSU 11.2.0.4.161018 PSU
TestDB2 17-FEB-18 01.18.14.712937 PM APPLY SERVER 11.2.0.4 171017 PSU 11.2.0.4.171017 PSU
TestDB2 BOOTSTRAP DATAPATCH 12.2.0.1 RDBMS_12.2.0.1.0DBOCT2019RU_AI
X.PPC64_190909

TestDB2 17-MAY-19 03.37.08.381001 PM VIEW INVALIDATE 8289601 view invalidation
TestDB2 17-MAY-19 03.41.49.618934 PM UPGRADE SERVER 12.2.0.1.0 Upgraded from 11.2.0.4.0
TestDB2 17-MAY-19 03.44.52.592435 PM APPLY SERVER 12.2.0.1.1810 0 OJVM PSU post-install
16OJVMRU

TestDB2 29-MAY-19 01.19.05.597980 PM jvmpsu.sql SERVER 12.2.0.1.1810 0 RAN jvmpsu.sql
16OJVMRU

TestDB2 29-MAY-19 01.19.05.614035 PM ROLLBACK SERVER 12.2.0.1.1810 0 OJVM PSU post-deinstall
16OJVMRU

TestDB2 29-MAY-19 04.05.33.216384 PM DOWNGRADE
TestDB2 29-MAY-19 11.32.08.327286 PM RELOAD SERVER 11.2.0.4.0 Reloaded after downgrade from
11.2.0

TestDB2 30-MAY-19 03.13.15.237730 PM VIEW INVALIDATE 8289601 view invalidation
TestDB2 30-MAY-19 03.18.38.418612 PM UPGRADE SERVER 12.2.0.1.0 Upgraded from 11.2.0.4.0
TestDB2 30-MAY-19 03.21.37.733353 PM APPLY SERVER 12.2.0.1.1810 0 OJVM PSU post-install
16OJVMRU


17 rows selected.

SQL> SQL> SQL>
INSTANCE_NAME ACTION_TIME ACTION NAMESPACE VERSION ID COMMENTS BUNDLE_SERIES
---------------- ---------------------------------------- ------------------------------ ---------- ------------- ---------- ------------------------------ ------------------------------
TestDB2 01-OCT-13 10.55.45.938537 PM APPLY SERVER 11.2.0.4 0 Patchset 11.2.0.2.0 PSU
TestDB2 10-OCT-14 10.40.27.269173 AM APPLY SERVER 11.2.0.4 3 PSU 11.2.0.4.3 PSU
TestDB2 14-OCT-14 08.49.10.244673 AM APPLY SERVER 11.2.0.4 3 PSU 11.2.0.4.3 PSU
TestDB2 22-DEC-15 10.58.03.812964 PM APPLY SERVER 11.2.0.4 8 PSU 11.2.0.4.8 PSU
TestDB2 29-DEC-16 05.01.59.430436 PM APPLY SERVER 11.2.0.4 161018 PSU 11.2.0.4.161018 PSU
TestDB2 17-FEB-18 01.18.14.712937 PM APPLY SERVER 11.2.0.4 171017 PSU 11.2.0.4.171017 PSU
TestDB2 BOOTSTRAP DATAPATCH 12.2.0.1 RDBMS_12.2.0.1.0DBOCT2019RU_AI
X.PPC64_190909

TestDB2 17-MAY-19 03.37.08.381001 PM VIEW INVALIDATE 8289601 view invalidation
TestDB2 17-MAY-19 03.41.49.618934 PM UPGRADE SERVER 12.2.0.1.0 Upgraded from 11.2.0.4.0
TestDB2 17-MAY-19 03.44.52.592435 PM APPLY SERVER 12.2.0.1.1810 0 OJVM PSU post-install
16OJVMRU

TestDB2 29-MAY-19 01.19.05.597980 PM jvmpsu.sql SERVER 12.2.0.1.1810 0 RAN jvmpsu.sql
16OJVMRU

TestDB2 29-MAY-19 01.19.05.614035 PM ROLLBACK SERVER 12.2.0.1.1810 0 OJVM PSU post-deinstall
16OJVMRU

TestDB2 29-MAY-19 04.05.33.216384 PM DOWNGRADE
TestDB2 29-MAY-19 11.32.08.327286 PM RELOAD SERVER 11.2.0.4.0 Reloaded after downgrade from
11.2.0

TestDB2 30-MAY-19 03.13.15.237730 PM VIEW INVALIDATE 8289601 view invalidation
TestDB2 30-MAY-19 03.18.38.418612 PM UPGRADE SERVER 12.2.0.1.0 Upgraded from 11.2.0.4.0
TestDB2 30-MAY-19 03.21.37.733353 PM APPLY SERVER 12.2.0.1.1810 0 OJVM PSU post-install
16OJVMRU


17 rows selected.

SQL> SQL> 2 set lines 200 pages 200
col action_time format a40
col DESCRIPTION format a60
/

select PATCH_ID,SOURCE_VERSION,ACTION_TIME,STATUS,ACTION,DESCRIPTION from dba_registry_sqlpatch
/

select * from dba_registry_sqlpatch
3 4 5 /set lines 200 pages 200
*
ERROR at line 2:
ORA-00933: SQL command not properly ended


SQL> SQL> 2 select PATCH_ID,SOURCE_VERSION,ACTION_TIME,STATUS,ACTION,DESCRIPTION from dba_registry_sqlpatch
*
ERROR at line 1:
ORA-00904: "SOURCE_VERSION": invalid identifier


SQL> SQL> 2
SQL> select PATCH_ID,SOURCE_VERSION,ACTION_TIME,STATUS,ACTION,DESCRIPTION from dba_registry_sqlpatch
2 ;
select PATCH_ID,SOURCE_VERSION,ACTION_TIME,STATUS,ACTION,DESCRIPTION from dba_registry_sqlpatch
*
ERROR at line 1:
ORA-00904: "SOURCE_VERSION": invalid identifier


SQL> select * from dba_registry_sqlpatch;

PATCH_ID PATCH_UID VERSION FLAGS ACTION STATUS INSTALL_ID ACTION_TIME
---------- ---------- ------------- ---------- ------------------------------ ------------------------- ---------- ----------------------------------------
DESCRIPTION BUNDLE_SERIES BUNDLE_ID
---------------------------------------------------------------------------------------------------- ------------------------------ ----------
BUNDLE_DATA
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
PATCH_DESCRIPTOR
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
PATCH_DIRECTORY
----------------------------------------------------------------------------------------------------------------------------------------------------------------
LOGFILE
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
28440725 22458824 12.2.0.1 NJJ APPLY SUCCESS 1 30-MAY-19 03.27.34.807404 PM
OJVM RELEASE UPDATE: 12.2.0.1.181016 (28440725)


504B0304140000000800E343504D98FB08838E020000C00600001200000032383434303732355F6170706C792E73716C9D54DB4EE330107DF757CC036A8A8428648B166DC58A901A1A2937C529887DB1
/u01/oracle/TestDB/cfgtoollogs/sqlpatch/28440725/22458824/28440725_apply_TestDB_2019May30_15_21_30.log

28662603 22499819 12.2.0.1 NB APPLY SUCCESS 1 30-MAY-19 03.27.40.835917 PM
DATABASE OCT 2018 RELEASE UPDATE 12.2.0.1.181016 DBRU 181016
<?xml version="1.0" encoding="US-ASCII"?>
<bundledata version="12.2.0.1.170516"
<?xml version="1.0" encoding="US-ASCII"?>
<sqlPatch ID="28662603" uniquePatchID=
504B03041400000008003C634C4DF14EDDCD320300006B1A00000C00000032383636323630332E786D6CC5595D6F9B30147DDFAFB0FCBC2540080129A46A9B6C9AD435559356DD5365B09BD2D986D8CE
/u01/oracle/TestDB/cfgtoollogs/sqlpatch/28662603/22499819/28662603_apply_TestDB_2019May30_15_21_37.log

30138470 23136421 12.2.0.1 NB APPLY SUCCESS 2 16-FEB-20 07.18.37.508210 AM
DATABASE OCT 2019 RELEASE UPDATE 12.2.0.1.191015 DBRU 191015
<?xml version="1.0" encoding="US-ASCII"?>
<bundledata version="12.2.0.1.170516"
<?xml version="1.0" encoding="US-ASCII"?>
<sqlPatch ID="30138470" uniquePatchID=
504B030414000000080081A13B4FA56D469D320400000D2A00000C00000033303133383437302E786D6CC55ADF73DA38107EEF5FE1F1F31DC836F8C70CD04902777333B9924968A77D62644B09EEC996
/u01/oracle/TestDB/cfgtoollogs/sqlpatch/30138470/23136421/30138470_apply_TestDB_2020Feb16_07_15_13.log


3 rows selected.

SQL>



1.2.6.3 Upgrade Oracle Recovery Manager Catalog

If you are using the Oracle Recovery Manager, the catalog needs to be upgraded. Enter the following command to upgrade it. The UPGRADE CATALOG command must be entered twice to confirm the upgrade.

$ rman catalog username/password@alias


RMAN> UPGRADE CATALOG;
RMAN> UPGRADE CATALOG;
RMAN> EXIT;

eg
eanor[/home/TestDB]$
node1[/home/TestDB]$ . oraenv
ORACLE_SID = [TestDB1] ?
The Oracle base remains unchanged with value /u01/oracle/TestDB
node1[/home/TestDB]$ id
uid=257(TestDB) gid=207(oinstall) groups=1(staff),203(dba),206(gprd),220(controlm),212(asmdba)
node1[/home/TestDB]$ . oraen
node1[/home/TestDB]$
node1[/home/TestDB]$ rman

Recovery Manager: Release 12.2.0.1.0 - Production on Sun Feb 16 07:33:00 2020

Copyright (c) 1982, 2017, Oracle and/or its affiliates. All rights reserved.

RMAN> connect catalog rmc_TestDB/TestDB_rmc@rmcprd

connected to recovery catalog database

RMAN> connect target /

connected to target database: TestDB (DBID=1014003833)

RMAN> UPGRADE CATALOG;

recovery catalog owner is RMC_TestDB
enter UPGRADE CATALOG command again to confirm catalog upgrade

RMAN> UPGRADE CATALOG;


recovery catalog upgraded to version 12.02.00.01
DBMS_RCVMAN package upgraded to version 12.02.00.01
DBMS_RCVCAT package upgraded to version 12.02.00.01.

RMAN>

1 comment:

  1. Your Affiliate Profit Machine is ready -

    And making money online using it is as simple as 1---2---3!

    This is how it works...

    STEP 1. Choose which affiliate products the system will promote
    STEP 2. Add PUSH BUTTON traffic (this LITERALLY takes 2 minutes)
    STEP 3. See how the system grow your list and sell your affiliate products all by itself!

    Do you want to start making money??

    Your MONEY MAKING affiliate solution is RIGHT HERE

    ReplyDelete