pat98's always & forever

간만에 제대로 된  SF 탄생 !!

네오 클래시컬 + 아포칼립스 + 오키도키

- 11g -> 19c 업그레이드 작업후 후속작업 진행시 compatible 문제로 startup 불가..

- 장애상황

업그레이드 완료후 11.2.0.4 -> 19.0.0 으로 compatible 변경 진행하였으나 실패

startup 실패함.

ORA-38880: Cannot advance compatibility from 11.2.0.4.0 to 19.0.0.0.0 due toguaranteed restore points

- Solution

1. 변경 작업전 parameter 백업

SQL> show parameter compat

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
compatible                           string      11.2.0.4.0
noncdb_compatible                    boolean     FALSE
plsql_v2_compatibility               boolean     FALSE
SQL> show parameter pfile

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
spfile                               string      /u01/app/oracle/product/19.0.0
                                                 .0/dbhome_1/dbs/spfileORCL.ora
SQL> create pfile='/tmp/test.ora' from spfile;

File created.

2. 11.2.0.4.0 -> 19.0.0 으로 compatible 변경
-> compatible 값은 downgrade 가 되지 않으므로 반드시 parameter 백업을 받아야 한다.

SQL> alter system set compatible='19.0.0' scope=spfile;

System altered.

SQL> shutdown immediate
startup
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> ORACLE instance started.

Total System Global Area 3053449792 bytes
Fixed Size                  8929856 bytes
Variable Size             620756992 bytes
Database Buffers         2415919104 bytes
Redo Buffers                7843840 bytes


ORA-38880: Cannot advance compatibility from 11.2.0.4.0 to 19.0.0.0.0 due to
guaranteed restore points

-> 업그레이드시 사용한 GRP 영역 때문에 변경이 되지 않는다.

3. 백업 받은 화일의 이전 값으로  다시 startup
SQL> startup pfile='/tmp/test.ora'
ORACLE instance started.

Total System Global Area 3053449792 bytes
Fixed Size                  8929856 bytes
Variable Size             620756992 bytes
Database Buffers         2415919104 bytes
Redo Buffers                7843840 bytes
Database mounted.
Database opened.


4. 오픈되면 GRP 영역을 확인한 후, drop 처리한다.
SQL> set lines 121
SQL> col name for A30
SQL> col time for A40
SQL> col DATABASE_INCARNATION# for 99999999
SQL> SELECT NAME, SCN, TO_CHAR(TIME,'YYYY-MM-DD HH24:MI:SS') TIME, DATABASE_INCARNATION#, GUARANTEE_FLASHBACK_DATABASE,STORAGE_SIZE FROM V$RESTORE_POINT WHERE GUARANTEE_FLASHBACK_DATABASE = 'YES';

NAME                                  SCN TIME                                     DATABASE_INCARNATION# GUA STORAGE_SIZE
------------------------------ ---------- ---------------------------------------- --------------------- --- ------------
AUTOUPGRADE_9212_ORCL112040        266377 2024-04-09 15:34:16                                          1 YES    681574400

SQL> drop restore point AUTOUPGRADE_9212_ORCL112040;

Restore point dropped.

5. 다시 재기동  
SQL> shutdown immediate
startup
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> ORACLE instance started.

Total System Global Area 3053449792 bytes
Fixed Size                  8929856 bytes
Variable Size             620756992 bytes
Database Buffers         2415919104 bytes
Redo Buffers                7843840 bytes
Database mounted.
Database opened.

6. 정상 확인
SQL> show parameter compatible

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
compatible                           string      19.0.0
noncdb_compatible                    boolean     FALSE

- silent mode 에서 전부 Big file 로 만드는 방법 (Tablespace 별 개별적으로 true로 하지 않고)

1. Templates 화일의 최소 충족요건으로 변경

$ORACLE_HOME/assistants/dbca/templates/New_Database.dbt 화일내의 USERS tabllespace 의 datafile 최소크기를 최소 7M 로 변경함.

      <DatafileAttributes id="{ORACLE_BASE}/oradata/{DB_UNIQUE_NAME}/users01.dbf">
         <tablespace>USERS</tablespace>
         <temporary>false</temporary>
         <online>true</online>
         <status>0</status>
         <size unit="MB">7</size>
         <reuse>true</reuse>
         <autoExtend>true</autoExtend>
         <increment unit="KB">1280</increment>
         <maxSize unit="MB">-1</maxSize>
      </DatafileAttributes>

2. -useBigFileForTablespace 옵션 사용 
dbca -silent -createDatabase -gdbName BIGORCL -templateName New_Database.dbt -useBigFileForTablespace true


3. 확인
sys@BIGORCL> select TABLESPACE_NAME, BIGFILE from DBA_TABLESPACES;

TABLESPACE_NAME                BIG
------------------------------ ---
SYSTEM                         YES
SYSAUX                         YES
UNDOTBS1                       YES
TEMP                           YES
USERS                          YES

장애 증상 :

- OLD ORACLE_HOME
/oracle/app/11.2.0.4

- NEW ORACLE_HOME
/u01/app/oracle/product/11.2.0.4/dbhome_2

신규설치가 원활하지 않아 11.2.0.4 기존 서버에서 ORACLE_HOME 을 통쨰로 tar 압축하여 신규 ORACLE_HOME 에 압축해제 후 relink all 작업함.

dbca 로 database 생성시 계속 이전 ORACLE_HOME 을 바라보고 있음..

[ORCL]oracle@upgrade:/home/oracle# dbca
java.lang.UnsatisfiedLinkError: Can't load library: /oracle/product/11.2.0.4/oui/lib/linux64/liboraInstaller.so
        at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1652)
        at java.lang.Runtime.load0(Runtime.java:769)
        at java.lang.System.load(System.java:968)
        at oracle.sysman.oii.oiip.osd.unix.OiipuUnixOps.loadNativeLib(OiipuUnixOps.java:384)
        at oracle.sysman.oii.oiip.osd.unix.OiipuUnixOps.<clinit>(OiipuUnixOps.java:126)
        at oracle.sysman.oii.oiip.oiipg.OiipgEnvironment.getEnv(OiipgEnvironment.java:201)
        at oracle.sysman.oii.oiip.oiipg.OiipgPropertyLoader.initUnixPtrFileLoc(OiipgPropertyLoader.java:212)
        at oracle.sysman.oii.oiip.oiipg.OiipgPropertyLoader.<clinit>(OiipgPropertyLoader.java:125)
        at oracle.sysman.oii.oiic.OiicStandardInventorySession.updateProperties(OiicStandardInventorySession.java:492)
        at oracle.sysman.oii.oiic.OiicStandardInventorySession.initSession(OiicStandardInventorySession.java:266)
        at oracle.sysman.oii.oiic.OiicStandardInventorySession.initSession(OiicStandardInventorySession.java:240)
        at oracle.sysman.oii.oiic.OiicStandardInventorySession.initSession(OiicStandardInventorySession.java:189)
        at oracle.sysman.assistants.util.InventoryUtil.getOUIInvSession(InventoryUtil.java:346)
        at oracle.sysman.assistants.util.InventoryUtil.getOUILoc(InventoryUtil.java:122)
        at oracle.sysman.assistants.util.hasi.HAUtils.getOUILoc(HAUtils.java:2332)
        at oracle.sysman.assistants.util.hasi.HAUtils.<init>(HAUtils.java:240)
        at oracle.sysman.assistants.util.hasi.HAUtils.getInstance(HAUtils.java:281)
        at oracle.sysman.assistants.util.NetworkUtils.getAllListeners(NetworkUtils.java:349)
        at oracle.sysman.assistants.util.step.StepContext.<init>(StepContext.java:337)
        at oracle.sysman.assistants.dbca.backend.Host.<init>(Host.java:828)
        at oracle.sysman.assistants.dbca.ui.UIHost.<init>(UIHost.java:258)
        at oracle.sysman.assistants.dbca.ui.InteractiveHost.<init>(InteractiveHost.java:54)
        at oracle.sysman.assistants.dbca.Dbca.getHost(Dbca.java:173)
        at oracle.sysman.assistants.dbca.Dbca.execute(Dbca.java:113)
        at oracle.sysman.assistants.dbca.Dbca.main(Dbca.java:189)

relink 효과없음.

genclntsh 효과없음

조치방법 :

오라클 HOME detach 후 다시 attach 함.

/u01/app/oracle/product/11.2.0.4/dbhome_2/oui/bin/runInstaller -silent -waitforcompletion -detachHome ORACLE_HOME='/u01/app/oracle/product/11.2.0.4/dbhome_2' -local \
-intPtrLoc /app/oracle/oraInventory/oraInst.loc

/usr/bin/perl clone.pl ORACLE_BASE=/u01/app/oracle ORACLE_HOME=/u01/app/oracle/product/11.2.0.4/dbhome_2 ORACLE_HOME_NAME=OraDb11g_home1  OSDBA_GROUP=dba OSOPER_GROUP=dba

[ORCL]oracle@upgrade:/home/oracle# dbca   <-------- 에러없이 정상수행됨.

증상 : 19.20 -> 19.22 RU 패치 작업한 후 각각 노드의 패치정보가 다르게 인식됨.

보통의 경우 아래와 같은 방법으로 해결이 됨. (Doc ID 1639285.1)

/u01/app/19.0.0/grid/crs/install/rootcrs.sh -unlock
/u01/app/19.0.0/grid/bin/clscfg -localpatch (Corrects patch level at OLR)
/u01/app/19.0.0/grid/bin/clscfg -patch (corrects patch level at OCR)
/u01/app/19.0.0/grid/crs/install/rootcrs.sh -lock

- But 해당 경우는 위의 작업을 해도 소용이 없었음.

[root@gtexadb01 /root]# kfod op=patches
---------------
List of Patches
===============
33575402
35943157
35956421
35967489
36115038

[root@gtexadb02 /root]# kfod op=patches
---------------
List of Patches
===============
33575402
35332537  <--- 19.20 패치정보가 남아있음?
35571653  <--- 19.20 패치정보가 남아있음?
35943157
35956421
35967489
36115038

- rollback 시도 실패
[gtexa2]oracle@gtexadb02:/home/oracle$ opatch nrollback -id 35332537,35571653 -oh /u01/app/oracle/product/19.0.0/dbhome_1
Oracle Interim Patch Installer version 12.2.0.1.41
Copyright (c) 2024, Oracle Corporation.  All rights reserved.

Oracle Home       : /u01/app/oracle/product/19.0.0/dbhome_1
Central Inventory : /u01/app/oraInventory
   from           : /u01/app/oracle/product/19.0.0/dbhome_1/oraInst.loc
OPatch version    : 12.2.0.1.41
OUI version       : 12.2.0.7.0
Log file location : /u01/app/oracle/product/19.0.0/dbhome_1/cfgtoollogs/opatch/opatch2024-04-03_12-52-28PM_1.log

Following patches are not present in the Oracle Home.
35332537,35571653
UtilSession failed: Prereq. API succeeds but no patch is available for rollback.
Log file location: /u01/app/oracle/product/19.0.0/dbhome_1/cfgtoollogs/opatch/opatch2024-04-03_12-52-28PM_1.log

OPatch failed with error code 73

- OCR 정보 수정 실패
[root@gtexadb02 /root]# $GI_HOME/bin/clscfg -patch
clscfg: -patch mode specified
clscfg: EXISTING configuration version 19 detected.
Successfully accumulated necessary OCR keys.
Creating OCR keys for user 'root', privgrp 'root'..
Operation successful.

[root@gtexadb01 /root]# crsctl stop rollingpatch
CRS-1171: Rejecting rolling patch mode change because the patch level is not consistent across all nodes in the cluster. The patch level on nodes gtexadb02 is not the same as the patch level [3844574830] found on nodes gtexadb01.
CRS-4000: Command Stop failed, or completed with errors.

- 아직 조회시 노드별 다른 정보 조회되는 상태
[root@gtexadb01 /u01/app/19.0.0/grid/crs/install]# crsctl  query crs activeversion -f
Oracle Clusterware active version on the cluster is [19.0.0.0.0]. The cluster upgrade state is [ROLLING PATCH]. The cluster active patch level is [4059512333].
[root@gtexadb01 /u01/app/19.0.0/grid/crs/install]# crsctl query crs releasepatch
Oracle Clusterware release patch level is [3844574830] and the complete list of patches [33575402 35943157 35956421 35967489 36115038 ] have been applied on the local node. The release patch string is [19.22.0.0.0].

[root@gtexadb02 /root]# crsctl  query crs activeversion -f
Oracle Clusterware active version on the cluster is [19.0.0.0.0]. The cluster upgrade state is [ROLLING PATCH]. The cluster active patch level is [4059512333].

[root@gtexadb02 /root]# crsctl query crs releasepatch
Oracle Clusterware release patch level is [2795171529] and the complete list of patches [33575402 35332537 35571653 35943157 35956421 35967489 36115038 ] have been applied on the local node. The release patch string is [19.22.0.0.0].

- Solution
$GI_HOME/crs/install/rootcrs.sh -prepatch

(grid)
19.20 패치 제거하는 경우 <--- library 화일에서 해당 patch list 를 삭제함.
$GI_HOME/bin/patchgen commit -rb 35332537
$GI_HOME/bin/patchgen commit -rb 35571653

추가하는 경우는
$GI_HOME/bin/patchgen commit -pi 35332537
$GI_HOME/bin/patchgen commit -pi 35571653

- 각 노드 패치 리스트 비교 확인 
$GI_HOME/bin/kfod op=patches
$GI_HOME/bin/kfod op=patchlvl

- 이제 정상적으로 조회됨.
[root@gtexadb01 /root]# $GI_HOME/bin/kfod op=patches
---------------
List of Patches
===============
33575402
35943157
35956421
35967489
36115038
[root@gtexadb01 /root]# $GI_HOME/bin/kfod op=patchlvl
-------------------
Current Patch level
===================
3844574830

[root@gtexadb02 /root]# $GI_HOME/bin/kfod op=patches
---------------
List of Patches
===============
33575402
35943157
35956421
35967489
36115038
[root@gtexadb02 /root]# $GI_HOME/bin/kfod op=patchlvl
-------------------
Current Patch level
===================
3844574830

(root)
$GI_HOME/crs/install/rootcrs.sh -postpatch

- 정상 기동된 후 양 노드 정보확인
crsctl query crs softwarepatch
Oracle Clusterware patch level on node gtexadb01 is [3844574830].

[root@gtexadb01 /root]# crsctl query crs activeversion -f
Oracle Clusterware active version on the cluster is [19.0.0.0.0]. The cluster upgrade state is [NORMAL]. The cluster active patch level is [3844574830].

sys@gtexa1> select sys_context('SYS_CLUSTER_PROPERTIES', 'CLUSTER_STATE') from dual;
SYS_CONTEXT('SYS_CLUSTER_PROPERTIES','CLUSTER_STATE')
------------------------------------------------------------------------------------------------------------------------
Normal
Elapsed: 00:00:00.00

sys@gtexa1> select sys_context('SYS_CLUSTER_PROPERTIES', 'CURRENT_PATCHLVL') from dual;
SYS_CONTEXT('SYS_CLUSTER_PROPERTIES','CURRENT_PATCHLVL')
------------------------------------------------------------------------------------------------------------------------
320077824

* 또한 Patch level 관련 이상있을시 Cell 노드를 리부팅하는 경우 ACTIVATE 시 OFFLINE -> ONLINE 이 자동으로 되지 않음
패치문제 조치 후 바로 정상 OFFLINE -> ONLINE 변경됨

- 조치 전
[root@gtexacel01 ~]# cellcli -e list griddisk attributes name,status,asmmodestatus,asmdeactivationoutcome
DATAC1_CD_00_gtexacel01         active  OFFLINE         Yes
DATAC1_CD_01_gtexacel01         active  OFFLINE         Yes
DATAC1_CD_02_gtexacel01         active  OFFLINE         Yes
DATAC1_CD_03_gtexacel01         active  OFFLINE         Yes
DATAC1_CD_04_gtexacel01         active  OFFLINE         Yes
DATAC1_CD_05_gtexacel01         active  OFFLINE         Yes
DBFSC1_CD_02_gtexacel01         active  OFFLINE         Yes
DBFSC1_CD_03_gtexacel01         active  OFFLINE         Yes
DBFSC1_CD_04_gtexacel01         active  OFFLINE         Yes
DBFSC1_CD_05_gtexacel01         active  OFFLINE         Yes
RECOC1_CD_00_gtexacel01         active  OFFLINE         Yes
RECOC1_CD_01_gtexacel01         active  OFFLINE         Yes
RECOC1_CD_02_gtexacel01         active  OFFLINE         Yes
RECOC1_CD_03_gtexacel01         active  OFFLINE         Yes
RECOC1_CD_04_gtexacel01         active  OFFLINE         Yes
RECOC1_CD_05_gtexacel01         active  OFFLINE         Yes

- 조치 후                      
[root@gtexacel01 ~]# cellcli -e list griddisk attributes name,status,asmmodestatus,asmdeactivationoutcome
DATAC1_CD_00_gtexacel01         active  ONLINE  Yes
DATAC1_CD_01_gtexacel01         active  ONLINE  Yes
DATAC1_CD_02_gtexacel01         active  ONLINE  Yes
DATAC1_CD_03_gtexacel01         active  ONLINE  Yes
DATAC1_CD_04_gtexacel01         active  ONLINE  Yes
DATAC1_CD_05_gtexacel01         active  ONLINE  Yes
DBFSC1_CD_02_gtexacel01         active  ONLINE  Yes
DBFSC1_CD_03_gtexacel01         active  ONLINE  Yes
DBFSC1_CD_04_gtexacel01         active  ONLINE  Yes
DBFSC1_CD_05_gtexacel01         active  ONLINE  Yes
RECOC1_CD_00_gtexacel01         active  ONLINE  Yes
RECOC1_CD_01_gtexacel01         active  ONLINE  Yes
RECOC1_CD_02_gtexacel01         active  ONLINE  Yes
RECOC1_CD_03_gtexacel01         active  ONLINE  Yes
RECOC1_CD_04_gtexacel01         active  ONLINE  Yes
RECOC1_CD_05_gtexacel01         active  ONLINE  Yes

- 이상 있을 시 리부팅 되지 않은 타 노드에서 상태 조회했을 시 내용                     
[root@gtexacel02 ~]# cellcli -e list griddisk attributes name,status,asmmodestatus,asmdeactivationoutcome
DATAC1_CD_00_gtexacel02         active  ONLINE  "Cannot deactivate because partner disk DATAC1_CD_02_GTEXACEL01 is not online"
DATAC1_CD_01_gtexacel02         active  ONLINE  "Cannot deactivate because partner disk DATAC1_CD_00_GTEXACEL01 is not online"
DATAC1_CD_02_gtexacel02         active  ONLINE  "Cannot deactivate because partner disk DATAC1_CD_03_GTEXACEL01 is not online"
DATAC1_CD_03_gtexacel02         active  ONLINE  "Cannot deactivate because partner disk DATAC1_CD_00_GTEXACEL01 is not online"
DATAC1_CD_04_gtexacel02         active  ONLINE  "Cannot deactivate because partner disk DATAC1_CD_01_GTEXACEL01 is not online"
DATAC1_CD_05_gtexacel02         active  ONLINE  "Cannot deactivate because partner disk DATAC1_CD_04_GTEXACEL01 is not online"
DBFSC1_CD_02_gtexacel02         active  ONLINE  "Cannot deactivate because partner disk DBFSC1_CD_04_GTEXACEL01 is not online"
DBFSC1_CD_03_gtexacel02         active  ONLINE  "Cannot deactivate because partner disk DBFSC1_CD_05_GTEXACEL01 is not online"
DBFSC1_CD_04_gtexacel02         active  ONLINE  "Cannot deactivate because partner disk DBFSC1_CD_04_GTEXACEL01 is not online"
DBFSC1_CD_05_gtexacel02         active  ONLINE  "Cannot deactivate because partner disk DBFSC1_CD_05_GTEXACEL01 is not online"
RECOC1_CD_00_gtexacel02         active  ONLINE  "Cannot deactivate because partner disk RECOC1_CD_04_GTEXACEL01 is not online"
RECOC1_CD_01_gtexacel02         active  ONLINE  "Cannot deactivate because partner disk RECOC1_CD_02_GTEXACEL01 is not online"
RECOC1_CD_02_gtexacel02         active  ONLINE  "Cannot deactivate because partner disk RECOC1_CD_05_GTEXACEL01 is not online"
RECOC1_CD_03_gtexacel02         active  ONLINE  "Cannot deactivate because partner disk RECOC1_CD_05_GTEXACEL01 is not online"
RECOC1_CD_04_gtexacel02         active  ONLINE  "Cannot deactivate because partner disk RECOC1_CD_02_GTEXACEL01 is not online"
RECOC1_CD_05_gtexacel02         active  ONLINE  "Cannot deactivate because partner disk RECOC1_CD_03_GTEXACEL01 is not online"


-참고 문서
CRS-6706: Oracle Clusterware Release patch level ('nnn') does not match Software patch level ('mmm') (Doc ID 1639285.1)
[OCI] Scale-up Failed in DBCS With ORA-15032: not all alterations performed, ORA-15137: The ASM cluster is in rolling patch state (Doc ID 2681040.1)
Software Patch Mismatch After Applying Bundle Patch or PSU on Grid Home and the Cluster Upgrade State is [ROLLING PATCH] (Doc ID 2176790.1)
SEHA Patching on Windows: CRS startup encounters - Patch Levels don't match. Local Patch Level [XXXXXXXXXXX] != Cache Writer Patch Level [XXXXXXXXXXX] (Doc ID 2923424.1)

2023년에 팻 매시니 옹의 새 앨범이 나왔었다.

그저 감사할 뿐.

한 동안 무한반복해서 들어야 겠다.

앨범의 분위기는 <One Quiet Night> 과 유사하다

1. The Waves Are Not the Ocean
2. From the Mountains
3. Ole & Gard
4. Trust Your Angels
5. Never Was Love
6. I Fall in Love Too Easily
7. P.C. of Belgium
8. Morning of the Carnival
9. Clouds Can't Change the Sky
10. Blue in Green (2LP Version Only)

- ASM 환경인데 아래와 같이 file system 에 잘못 만들었을 때..당황하지 말고 move 하자..단 DML 작업 있을 시 감안하여 작업

SQL> create tablepsace TEST datafile '/test/test01.dbf' size 100M;

TABLESPACE_NAME      FILE_NAME                                           TOT_KB      FREE_KB USAGE_P
-------------------- --------------------------------------------- ------------ ------------ -------
TEST                 /test/test01.dbf                                   102,400      101,376     1.0
 
SQL> alter database move datafile '/test/test01.dbf' to '+DATAC1';

TABLESPACE_NAME      FILE_NAME                                           TOT_KB      FREE_KB USAGE_P
-------------------- --------------------------------------------- ------------ ------------ -------
TEST                 +DATAC1/GTEXA/DATAFILE/test.281.1163090277         102,400      101,376     1.0

19c Patch 작업후에 rman 접속할 때 아래와 같은 메세지 발생할 때 조치!!

[gtexa1]oracle@gtexadb01:/home/oracle$ rman target /
Recovery Manager: Release 19.0.0.0.0 - Production on Thu Mar 7 16:21:03 2024
Version 19.22.0.0.0

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

PL/SQL package SYS.DBMS_BACKUP_RESTORE version 19.20.00.00 in TARGET database is not current
PL/SQL package SYS.DBMS_RCVMAN version 19.20.00.00 in TARGET database is not current

--------------------------------------------------------------------------------------------------------------------------------
PL/SQL package SYS.DBMS_BACKUP_RESTORE Version is Not Current (Doc ID 2741760.1)

- 해당 Package Compile 수행

@?/rdbms/admin/dbmsrman.sql
@?/rdbms/admin/dbmsbkrs.sql
@?/rdbms/admin/prvtrmns.plb
@?/rdbms/admin/prvtbkrs.plb

완료후 재접속 정상!!

[gtexa1]oracle@gtexadb01:/home/oracle$ rman target /

Recovery Manager: Release 19.0.0.0.0 - Production on Thu Mar 7 16:59:45 2024
Version 19.22.0.0.0

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

connected to target database: GTEXA (DBID=2412954275)

Oracle Single 환경에 OCW Patch 를 적용해야 할까?

기본적으로 19.3 버전을  초기 설치하게 되면 non RAC / non ASM 환경임에도 
29585399;OCW RELEASE UPDATE 19.3.0.0.0 (29585399) 해당 패치가 같이 설치가 된다.

이후 Patch 관리를 해줘야 할 떄, Database RU 외에 OCW (Grid)도 같이 해 줘야 하나? 하는 의문이 생긴다.

-> 결론부터 말하면 선택사항이며 오라클에서는 보안패치가 포함되어 있기 때문에 같이 해줄것을 권장하고 있다.
-> 같이 관리해 주고 싶다면 GI RU 를 받아서 OCW와 DB RU를 개별적으로 Patch 적용해 주면 된다.

==========================================================================

APPLIES TO:

Oracle Database - Enterprise Edition - Version 19.3.0.0.0 and later
Information in this document applies to any platform.

GOAL

Is it or not necessary to apply OCW patches on my ORACLE_HOME even if I don't use ASM, RAC or CLUSTERWARE?

It is optional, but even if no GI Stack (ASM, Clusterware or RAC) is used inside the server, it is recommended not to ignore the security patches of the installed components. And apply the most recent OCW Patch.

From version 19c onwards, the Patch 29585399 OCW RU is included from the initial installation.  

[oracle@localhost ~]$ opatch lspatches
29585399;OCW RELEASE UPDATE 19.3.0.0.0 (29585399)
29517242;Database Release Update : 19.3.0.0.190416 (29517242) 

OPatch succeeded. 

SOLUTION

To apply the latest OCW patch, it is necessary to do it manually. This must be done by downloading the latest GI RU patch, unzipping it and placing it in the directory corresponding to the OCW and apply it using "opatch apply". 

Applying OCW and DB RUs 

Patch 35319490: GI RELEASE UPDATE 19.20.0.0.0.0 will be used.

You can download it from the following link:
https://updates.oracle.com/download/35319490.html 

NOTE: For rollback, installation, and post-installation instructions refer to README of the respective patches.

[oracle@localhost ~]$ unzip p35319490_190000_Linux-x86-64.zip

[oracle@localhost ~]$ cd 35319490/35320149 ◄◄◄ OCW Patch ID

[oracle@localhost ~]$ opatch apply

Patch 35320149 successfully applied.
OPatch succeeded.

[oracle@localhost ~]$ cd cd 35319490/35320081 ◄◄◄ DB RU Patch ID

[oracle@localhost ~]$ opatch apply

Patch 35320081 successfully applied.
OPatch succeeded.

Proceed to start the database and execute datapatch

SQL> startup
SQL> exit

[oracle@localhost ~]$ datapatch -verbose
SQL Patching tool complete on Sat Aug 26 21:29:07 2023 

[oracle@localhost ~]$ opatch lspatches

35320081;Database Release Update : 19.20.0.0.230718 (35320081)
35320149;OCW RELEASE UPDATE 19.20.0.0.0 (35320149)

OPatch succeeded.

[oracle@localhost ~]$

Already updated OCW and DB Release Update to the latest version