Oracle Patch

(1)

Version 변경일자 변경자(작성자) 주요내용

1 2018-04-08 박대성 최초 작성

2 3

Author 박대성 Creation Date 2018-04-08

Last Updated Version

Copyright(C) 2004 Goodus Inc.

All Rights Reserved

Oracle Patch

(2)

3 개월 후 다음 RUR 이 출시 될 예정이며, 이제는 새로운 보안 및 Regression 수정만 다시 포함 할 것 입니다. 이 시점에서 새로운 옵티마이저 또는 기능 수정이 추가되지는 않습니다. 위의 사진과 아래의 사 진 (RUR-1 및 RUR-2)을 비교하면 초기 RU-1 에서와 똑같은 옵티마이저 및 기능 수정이 표시됩니다.

세 번째 릴리스 업데이트 개정판 (RUR-3) 은 계획되어 있지 않다는 점에 유의해야 합니다. 이 모델은

RU 당 2 개의 RUR 만을 허용합니다.

(12)

3.3. Patch version numbering 변경

Oracle Database, Enterprise Manager and Middleware - Change to Patch Numbering from Nov 2015 onwards (Doc ID 2061926.1)

(In November 2015) Bundle Patches, Patch Set Updates and Security Patch Updates for Oracle Database 의 버전 번호가 "YYMMDD" 형식의 출시 날짜로 형식이 변경되었습니다.

Release Update Introduction and FAQ (Doc ID 2285040.1)

2018 년부터 12.2.0.2 와 같은 기존 명명법 대신에 Year.Update.Revision (18.1.0) 으로 구성된 세 개의 필

드 형식으로 변경되었습니다.

(13)

Oracle Database - Overview of Database Patch Delivery Methods - 12.1.0.2 and older (Doc ID 1962125.1)

Version Numbers

3.4. Where to find last Patches for Database?

Assistant: Download Reference for Oracle Database/GI PSU, SPU(CPU), Bundle Patches, Patchsets and Base Releases (Doc ID 2118136.2)

(14)

3.5. 12.1.0.1 이후 변경 사항

Database Security Patching from 12.1.0.1 onwards (Doc ID 1581950.1)

Starting with Oracle Database version 12.1.0.1 , Oracle will only provide Patch Set Update (PSU) patches to meet the Critical Patch Update (CPU) program requirements for security patching.

SPU (Security Patch Update) patches will no longer be available.

SPU 항목이 사라진 것을 확인 할 수 있습니다.

(15)

3.6. Summary

Others 부분은 하기 MOS 문서 참조

Oracle Database - Overview of Database Patch Delivery Methods - 12.1.0.2 and older (Doc ID 1962125.1) Oracle Database - Overview of Database Patch Delivery Methods for 12.2.0.1 and later versions (Doc ID 2337415.1)

(16)

4. Conflict Check

새로 적용할 패치와 기존에 적용된 패치와의 Conflict Check 수행 방법에 대해 살펴보겠습니다.

1) MOS Patch Conflict Checker tool

How to Use the My Oracle Support Conflict Checker Tool for Patches Installed with OPatch [Video] (Doc ID 1091294.1)

OPatch Inventory file 을 생성합니다.

[oracle:MTI:/home/oracle> $ORACLE_HOME/OPatch/opatch lsinv

생성된 파일을 PC 로 가져옵니다.

[oracle:MTI:/home/oracle> cd $ORACLE_HOME/cfgtoollogs/opatch/lsinv

[oracle:MTI:/oracle/mti/product/12.1.0/cfgtoollogs/opatch/lsinv> ls -alrt

-rw-r---. 1 oracle oinstall 8804 2018-04-02 20:37 lsinventory2018-04-02_20-37-02PM.txt

새로 적용할 패치 다운로드 화면에서 Press “Analyze with OPatch...” button 선택합니다.

Attach File 선택하여 lsinventory 파일 업로드 한 후 Analyze for Conflict 를 선택합니다.

분석 진행 화면입니다.

(17)

해당 Issues & Resolve 를 보여줍니다.

(해당 패치 적용에 기존 패치와 Conflict 없음)

(해당 패치 적용에 기존 패치와 Conflict 있음)

(18)

2) Manual Patch Conflict Check with OPatch utility 적용할 패치 location 에서 해당 명령어를 수행합니다.

[oracle:MTI:/oramedia/26925311> $ORACLE_HOME/OPatch/opatch prereq CheckConflictAgainstOHWithDetail - ph ./

Oracle Interim Patch Installer version 12.2.0.1.12

PREREQ session

Oracle Home : /oracle/mti/product/12.1.0 Central Inventory : /oracle/oraInventory

from : /oracle/mti/product/12.1.0/oraInst.loc OPatch version : 12.2.0.1.12

OUI version : 12.1.0.2.0

Log file location : /oracle/mti/product/12.1.0/cfgtoollogs/opatch/opatch2018-04-03_11-02-57AM_1.log Invoking prereq "checkconflictagainstohwithdetail"

Prereq "checkConflictAgainstOHWithDetail" passed.

OPatch succeeded.

[oracle:MTI:/oramedia/26925311> $ORACLE_HOME/OPatch/opatch prereq CheckConflictAmongPatches -ph ./

PREREQ session

Oracle Home : /oracle/mti/product/12.1.0 Central Inventory : /oracle/oraInventory

from : /oracle/mti/product/12.1.0/oraInst.loc OPatch version : 12.2.0.1.12

Log file location : /oracle/mti/product/12.1.0/cfgtoollogs/opatch/opatch2018-04-03_11-03-23AM_1.log Invoking prereq "checkconflictamongpatches"

Prereq "checkConflictAmongPatches" passed.

OPatch succeeded.

(19)

5. OPatch Utility

OPatch 는 Oracle Software 에 패치 apply & rollback 프로세스를 지원하는 Oracle 제공 플랫폼 종속 유틸 리티입니다.

l Requirements for OPatch

JRE version 1.4 or higher, Java commands for Windows, and ar, cp, fuser, and make commands for UNIX must be made available.

<11.2.0.4 예시>

PSU 적용을 위해서는 해당 패치 미디어의 README 파일을 참조하여 패치를 진행합니다.

2018 년 01 월 16 일 11.2.0.4 GI PSU

You must use the OPatch utility version 11.2.0.3.6 or later to apply this patch. Oracle

recommends that you use the latest released OPatch version for 11.2 releases, which is available for download from My Oracle Support patch 6880880 by selecting ARU link for the 11.2.0.0.0 release.

사전에 Opatch Utility 최신 버전 설치를 권고하며 최신버전은 하기 문서를 참조하여 다운로드 받습니다.

How To Download And Install The Latest OPatch(6880880) Version (Doc ID 274526.1)

(20)

6. 실습 - GI PSU 적용 ( opatch auto )

실습 환경

DB Version

Enterprise Edition 11.2.0.4 ( 2node RAC)

OS Version

OEL 6.8 ( Linux x86-64 )

GRID_HOME

/oragrid/11.2.0/grid_2

ORACLE_HOME

/oracle/app/product/11.2.0_2

User

oragrid & oracle

[root:rac1/root> crsctl stat res -t

--- NAME TARGET STATE SERVER STATE_DETAILS

--- Local Resources

--- ora.DATA.dg

ONLINE ONLINE rac1 ONLINE ONLINE rac2 ora.LISTENER.lsnr

ONLINE ONLINE rac1 ONLINE ONLINE rac2 ora.OCRVOTE.dg

ONLINE ONLINE rac1 ONLINE ONLINE rac2 ora.RECO.dg

ONLINE ONLINE rac1 ONLINE ONLINE rac2 ora.asm

ONLINE ONLINE rac1 Started ONLINE ONLINE rac2 Started ora.gsd

OFFLINE OFFLINE rac1 OFFLINE OFFLINE rac2 ora.net1.network

ONLINE ONLINE rac1 ONLINE ONLINE rac2 ora.ons

ONLINE ONLINE rac1 ONLINE ONLINE rac2

--- Cluster Resources

--- ora.LISTENER_SCAN1.lsnr

1 ONLINE ONLINE rac1 ora.cvu

1 ONLINE ONLINE rac1 ora.oc4j

1 ONLINE ONLINE rac1 ora.rac1.vip

1 ONLINE ONLINE rac1 ora.rac2.vip

1 ONLINE ONLINE rac2 ora.scan1.vip

1 ONLINE ONLINE rac1 ora.younha.db

1 ONLINE ONLINE rac1 Open 2 ONLINE ONLINE rac2 Open

(21)

6.1. 사전 준비

6.2. OCM Configuration < 1node & 2node >

OPatch 유틸리티는 실행될 때 OCM (Oracle Configuration Manager) Response File 을 묻는 메시지를 표 시합니다. 현재 환경에서 OCM Response File 을 만든 경우 OCM Response File 의 전체 경로를 입력해야 합니다.

[oragrid:+ASM1:/home/oragrid> cd /oragrid/11.2.0/grid_2/OPatch/ocm/bin/

[oragrid:+ASM1:/oragrid/11.2.0/grid_2/OPatch/ocm/bin> ./emocmrsp OCM Installation Response Generator 10.3.7.0.0 - Production

Provide your email address to be informed of security issues, install and initiate Oracle Configuration Manager. Easier for you if you use your My Oracle Support Email address/User Name.

Visit http://www.oracle.com/support/policies.html for details.

Email address/User Name: ENTER

You have not provided an email address for notification of security issues.

Do you wish to remain uninformed of security issues ([Y]es, [N]o) [N]: Y The OCM configuration response file (ocm.rsp) was successfully created.

[oragrid:+ASM1:/oragrid/11.2.0/grid_2/OPatch/ocm/bin> ls -al total 24

drwxr-x--- 2 oragrid dba 4096 Feb 24 16:04 . drwxr-x--- 5 oragrid dba 4096 Jan 23 06:54 ..

-rwxr-x--- 1 oragrid dba 9063 Nov 27 2009 emocmrsp -rw-r--r-- 1 oragrid oinstall 624 Feb 24 16:04 ocm.rsp

(23)

6.3. Validation of Oracle Inventory < 1node & 2node >

패치 적용을 시작하기 전에 GRID_HOME 및 패치 할 각 ORACLE_HOME 에 대한 인벤토리 정보의 일관 성을 점검합니다.

[oragrid:+ASM1:/home/oragrid> opatch lsinventory Oracle Interim Patch Installer version 11.2.0.3.18

Oracle Home : /oragrid/11.2.0/grid_2 Central Inventory : /oragrid/oraInventory

from : /oragrid/11.2.0/grid_2/oraInst.loc OPatch version : 11.2.0.3.18

<중략>

There are no Interim patches installed in this Oracle Home.

--- OPatch succeeded.

[oracle:YOUNHA1:/home/oracle> opatch lsinventory

<중략>

OPatch succeeded.

적용할 패치와 Conflict 확인합니다. ( GRID_HOME & ORACLE_HOME 확인 ) 4 장 log file (3,4,8,9,10 번 절차 확인)

[oragrid:+ASM1:/home/oragrid> opatch prereq CheckConflictAgainstOHWithDetail -ph /oramedia/27107360/22502505/ -oh /oragrid/11.2.0/grid_2/

PREREQ session

Oracle Home : /oragrid/11.2.0/grid_2 Central Inventory : /oragrid/oraInventory

from : /oragrid/11.2.0/grid_2//oraInst.loc OPatch version : 11.2.0.3.18

Log file location : /oragrid/11.2.0/grid_2/cfgtoollogs/opatch/opatch2018-02-24_16-14-05PM_1.log Invoking prereq "checkconflictagainstohwithdetail"

OPatch succeeded.

[oragrid:+ASM1:/home/oragrid> opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir /oramedia/27107360 -oh /oragrid/11.2.0/grid_2/

(24)

6.4. Patching ORACLE_HOME and GRID_HOME Together

OPatch 유틸리티는 root 권한으로 실행할 때 (opatch auto) GRID_HOME & ORACLE_HOME 패치를 자동 으로 수행합니다.

1 번 노드 & 2 번 노드 순차적 수행

[root:rac1/oramedia> /oragrid/11.2.0/grid_2/OPatch/opatch auto /oramedia/27107360/ -ocmrf /oragrid/11.2.0/grid_2/OPatch/ocm/bin/ocm.rsp

Executing /oragrid/11.2.0/grid_2/perl/bin/perl /oragrid/11.2.0/grid_2/OPatch/crs/patch11203.pl - patchdir /oramedia -patchn 27107360 -ocmrf /oragrid/11.2.0/grid_2/OPatch/ocm/bin/ocm.rsp - paramfile /oragrid/11.2.0/grid_2/crs/install/crsconfig_params

This is the main log file: /oragrid/11.2.0/grid_2/cfgtoollogs/opatchauto2018-02-24_16-44-51.log This file will show your detected configuration and all the steps that opatchauto attempted to do on your system:

/oragrid/11.2.0/grid_2/cfgtoollogs/opatchauto2018-02-24_16-44-51.report.log 2018-02-24 16:44:51: Starting Clusterware Patch Setup

Using configuration parameter file: /oragrid/11.2.0/grid_2/crs/install/crsconfig_params Stopping RAC /oracle/app/product/11.2.0_2 ...

Stopped RAC /oracle/app/product/11.2.0_2 successfully

patch /oramedia/27107360/26925576 apply successful for home /oracle/app/product/11.2.0_2 patch /oramedia/27107360/26609929/custom/server/26609929 apply successful for

home /oracle/app/product/11.2.0_2 Stopping CRS...

Stopped CRS successfully

patch /oramedia/27107360/26925576 apply successful for home /oragrid/11.2.0/grid_2 patch /oramedia/27107360/26609929 apply successful for home /oragrid/11.2.0/grid_2 patch /oramedia/27107360/22502505 apply successful for home /oragrid/11.2.0/grid_2 Starting CRS...

Installing Trace File Analyzer

CRS-4123: Oracle High Availability Services has been started.

Starting RAC /oracle/app/product/11.2.0_2 ...

Started RAC /oracle/app/product/11.2.0_2 successfully opatch auto succeeded.

log file 을 통해 opatchauto 수행 절차를 확인 할 수 있습니다.

[root:rac1/root> cat /oragrid/11.2.0/grid_2/cfgtoollogs/opatchauto2018-02-24_16-44-51.report.log

*********** Configuration Data ***********

* It shows only those targets that will be patched in this session *

crs_home=/oragrid/11.2.0/grid_2 owner=oragrid opatch_ver=11.2.0.3.18 rac_home=/oracle/app/product/11.2.0_2 owner=oracle opatch_ver=11.2.0.3.18

*********** Steps to be executed as owner unless specified as root ***********

1: /oracle/app/product/11.2.0_2/OPatch/opatch prereq CheckComponents -ph /oramedia/27107360/26925576 -oh /oracle/app/product/11.2.0_2

2: /oracle/app/product/11.2.0_2/OPatch/opatch prereq CheckComponents -ph /oramedia/27107360/26609929/custom/server/26609929 - oh /oracle/app/product/11.2.0_2

3: /oracle/app/product/11.2.0_2/OPatch/opatch prereq CheckConflictAgainstOH -ph /oramedia/27107360/26925576 -oh /oracle/app/product/11.2.0_2

4: /oracle/app/product/11.2.0_2/OPatch/opatch prereq CheckConflictAgainstOH -ph /oramedia/27107360/26609929/custom/server/26609929 -oh /oracle/app/product/11.2.0_2

(25)

5: /oragrid/11.2.0/grid_2/OPatch/opatch prereq CheckComponents -ph /oramedia/27107360/26925576 -oh /oragrid/11.2.0/grid_2 6: /oragrid/11.2.0/grid_2/OPatch/opatch prereq CheckComponents -ph /oramedia/27107360/26609929 -oh /oragrid/11.2.0/grid_2 7: /oragrid/11.2.0/grid_2/OPatch/opatch prereq CheckComponents -ph /oramedia/27107360/22502505 -oh /oragrid/11.2.0/grid_2

8: /oragrid/11.2.0/grid_2/OPatch/opatch prereq CheckConflictAgainstOH -ph /oramedia/27107360/26925576 -oh /oragrid/11.2.0/grid_2

11: /oracle/app/product/11.2.0_2/bin/emctl stop dbconsole 12: /oracle/app/product/11.2.0_2/bin/emctl stop agent

13: /oracle/app/product/11.2.0_2/OPatch/opatch prereq CheckApplicable -ph /oramedia/27107360/26925576 -oh /oracle/app/product/11.2.0_2

14: /oracle/app/product/11.2.0_2/OPatch/opatch prereq CheckApplicable -ph /oramedia/27107360/26609929/custom/server/26609929 -oh /oracle/app/product/11.2.0_2

15: /oracle/app/product/11.2.0_2/bin/srvctl stop home -o /oracle/app/product/11.2.0_2 -s /oracle/app/product/11.2.0_2/srvm/admin/stophome.txt -n rac1 -f

16: /oramedia/27107360/26609929/custom/server/26609929/custom/scripts/prepatch.sh -dbhome /oracle/app/product/11.2.0_2

17: /oracle/app/product/11.2.0_2/OPatch/opatch napply /oramedia/27107360/26925576 -local -silent -ocmrf /oragrid/11.2.0/grid_2/OPatch/ocm/bin/ocm.rsp -oh /oracle/app/product/11.2.0_2 -invPtrLoc

/oracle/app/product/11.2.0_2/oraInst.loc

18: /oracle/app/product/11.2.0_2/OPatch/opatch napply /oramedia/27107360/26609929/custom/server/26609929 -local -silent - ocmrf /oragrid/11.2.0/grid_2/OPatch/ocm/bin/ocm.rsp -oh /oracle/app/product/11.2.0_2 -invPtrLoc

/oracle/app/product/11.2.0_2/oraInst.loc

19: /oramedia/27107360/26609929/custom/server/26609929/custom/scripts/postpatch.sh -dbhome /oracle/app/product/11.2.0_2 20: /oragrid/11.2.0/grid_2/crs/install/rootcrs.pl -unlock : run as root

21: /oragrid/11.2.0/grid_2/tfa/bin/tfactl stop : run as root

22: /sbin/fuser -k /oragrid/11.2.0/grid_2/bin/crsctl.bin : run as root

23: /oragrid/11.2.0/grid_2/OPatch/opatch prereq CheckApplicable -ph /oramedia/27107360/26925576 -oh /oragrid/11.2.0/grid_2 24: /oragrid/11.2.0/grid_2/OPatch/opatch prereq CheckApplicable -ph /oramedia/27107360/26609929 -oh /oragrid/11.2.0/grid_2 25: /oragrid/11.2.0/grid_2/OPatch/opatch prereq CheckApplicable -ph /oramedia/27107360/22502505 -oh /oragrid/11.2.0/grid_2

26: /oragrid/11.2.0/grid_2/OPatch/opatch napply /oramedia/27107360/26925576 -local -silent -ocmrf

/oragrid/11.2.0/grid_2/OPatch/ocm/bin/ocm.rsp -oh /oragrid/11.2.0/grid_2 -invPtrLoc /oragrid/11.2.0/grid_2/oraInst.loc

/oragrid/11.2.0/grid_2/OPatch/ocm/bin/ocm.rsp -oh /oragrid/11.2.0/grid_2 -invPtrLoc /oragrid/11.2.0/grid_2/oraInst.loc 29: /oragrid/11.2.0/grid_2/bin/emctl start dbconsole

30: /oragrid/11.2.0/grid_2/rdbms/install/rootadd_rdbms.sh : run as root 31: /oragrid/11.2.0/grid_2/crs/install/rootcrs.pl -patch : run as root 32: /oracle/app/product/11.2.0_2/bin/emctl start dbconsole

33: /oracle/app/product/11.2.0_2/bin/emctl start agent

34: /oracle/app/product/11.2.0_2/bin/srvctl start home -o /oracle/app/product/11.2.0_2 -s /oracle/app/product/11.2.0_2/srvm/admin/stophome.txt -n rac1

1 번 노드가 완료되면 2 번 노드도 동일하게 수행합니다.

(26)

6.5. Patch Post-Installation Instructions

수정된 SQL 파일을 데이터베이스에 Load 합니다. RAC 환경에서는 한 노드에서만 수행하시면 됩니다.

( 만약 여러 개의 데이터베이스가 존재한다면 각각 수행합니다. )

[oracle:YOUNHA1:/home/oracle> sqlplus "/as sysdba"

Connected to:

Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production

With the Partitioning, Real Application Clusters, Automatic Storage Management, OLAP, Data Mining and Real Application Testing options

SQL> @?/rdbms/admin/catbundle.sql psu apply

$ORACLE_BASE/cfgtoollogs/catbundle 에서 log 파일 확인합니다.

[oracle:YOUNHA1:/home/oracle> cd /oracle/app/cfgtoollogs/catbundle/

[oracle:YOUNHA1:/oracle/app/cfgtoollogs/catbundle> ls catbundle_PSU_YOUNHA_APPLY_2018Feb24_17_36_37.log catbundle_PSU_YOUNHA_GENERATE_2018Feb24_17_36_35.log

6.6. Patch Check

SQL> set line 333

col comments for a30 col action_time for a30 col action for a10

select action_time, comments , action, version from dba_registry_history;

ACTION_TIME COMMENTS ACTION VERSION --- --- --- --- 15-FEB-18 05.21.23.010225 PM Patchset 11.2.0.2.0 APPLY 11.2.0.4 24-FEB-18 05.37.39.472287 PM PSU 11.2.0.4.180116 APPLY 11.2.0.4

opatch lsinventory 명령어를 통해 20180116 패치 적용 확인합니다. ( GRID_HOME & ORACLE_HOME )

(27)

6.7. Patch Deinstallation

패치 적용 후 이전 상태로 다시 Rollback 하기 위해서는 –rollback 옵션을 부여하여 수행합니다.

[root:rac1/oramedia> /oragrid/11.2.0/grid_2/OPatch/opatch auto /oramedia/27107360/ -rollback - ocmrf /oragrid/11.2.0/grid_2/OPatch/ocm/bin/ocm.r 네

<중략>

Stopping RAC /oracle/app/product/11.2.0_2 ...

Stopped RAC /oracle/app/product/11.2.0_2 successfully

patch 26925576 rollback successful for home /oracle/app/product/11.2.0_2 patch 26609929 rollback successful for home /oracle/app/product/11.2.0_2 Stopping CRS...

Stopped CRS successfully

patch 26925576 rollback successful for home /oragrid/11.2.0/grid_2 patch 26609929 rollback successful for home /oragrid/11.2.0/grid_2 patch 22502505 rollback successful for home /oragrid/11.2.0/grid_2 Starting CRS...

Installing Trace File Analyzer

Starting RAC /oracle/app/product/11.2.0_2 ...

Started RAC /oracle/app/product/11.2.0_2 successfully opatch auto succeeded.

1 번 노드가 완료되면 2 번 노드도 동일하게 수행하고 수정된 SQL 파일을 데이터베이스에 Load 합니다.

마찬가지로 한 노드에서만 수행하시면 됩니다.

SQL> @catbundle_PSU_<database SID PREFIX>_ROLLBACK.sql

SQL> @?/rdbms/admin/catbundle_PSU_YOUNHA_ROLLBACK.sql

SQL> set line 333

col comments for a30 col action_time for a30 col action for a10

select action_time, comments , action, version from dba_registry_history;

ACTION_TIME COMMENTS ACTION VERSION --- --- --- --- 15-FEB-18 05.21.23.010225 PM Patchset 11.2.0.2.0 APPLY 11.2.0.4 24-FEB-18 05.37.39.472287 PM PSU 11.2.0.4.180116 APPLY 11.2.0.4 24-FEB-18 07.57.00.239311 PM PSU 11.2.0.4.180116 ROLLBACK 11.2.0.4 24-FEB-18 07.57.17.737270 PM Patchset 11.2.0.2.0 APPLY 11.2.0.4

opatch lsinventory 명령어를 통해 확인합니다. ( GRID_HOME & ORACLE_HOME )

(28)

6.8. 11g vs 12c

l 5.2 OCM Configuration < 1node & 2node >

12c 부터는 2 번 step 을 생략합니다. 더 이상 Ocm response file 이 필요없습니다.

l 5.4 Patching ORACLE_HOME and GRID_HOME Together

Ocm response file 이 필요없고 명령어가 opatch auto vs opatchauto apply 로 변경되었습니다.

11g

# <GI_HOME>/OPatch/opatch auto <UNZIPPED_PATCH_LOCATION> -ocmrf <ocm response file>

12c

# <GI_HOME>/OPatch/opatchauto apply <UNZIPPED_PATCH_LOCATION>

l 5.5 Patch Post-Installation Instructions

11g

cd $ORACLE_HOME/rdbms/admin sqlplus /nolog

SQL> CONNECT / AS SYSDBA SQL> STARTUP

SQL> @catbundle.sql psu apply

12c

(29)

7. 실습 - GI PSU 적용 ( manual )

실습 환경

DB Version

Enterprise Edition 12.2.0.1 ( 2node RAC)

OS Version

OEL 6.8 ( Linux x86-64 )

GRID_HOME

/oragrid/12.2.0/grid

ORACLE_HOME

/oracle/app/product/12.2.0

User

oragrid & oracle

[root:younha1/root> crsctl stat res -t

--- Name Target State Server State details

--- Local Resources

---

<중략>

--- Cluster Resources

--- ora.LISTENER_SCAN1.lsnr

1 ONLINE ONLINE younha2 STABLE ora.MGMTLSNR

1 ONLINE ONLINE younha2 169.254.7.74 10.10.1 0.168,STABLE

ora.asm

1 ONLINE ONLINE younha1 Started,STABLE 2 ONLINE ONLINE younha2 Started,STABLE 3 OFFLINE OFFLINE STABLE

ora.cvu

1 ONLINE ONLINE younha2 STABLE ora.mgmtdb

1 ONLINE ONLINE younha2 Open,STABLE ora.qosmserver

1 ONLINE ONLINE younha2 STABLE ora.scan1.vip

1 ONLINE ONLINE younha2 STABLE ora.younha.db

1 ONLINE ONLINE younha1 Open,HOME=/oracle/ap p/product/12.2.0,STA BLE

2 ONLINE ONLINE younha2 Open,HOME=/oracle/ap p/product/12.2.0,STA BLE

ora.younha1.vip

1 ONLINE ONLINE younha1 STABLE ora.younha2.vip

1 ONLINE ONLINE younha2 STABLE

---

(30)

7.1. 사전 준비

7.2. Manual Patch

1 번노드부터 Manual Patch 를 진행합니다.

Supplemental Readme - Grid Infrastructure Release Update 12.2.0.1.x (Doc ID 2246888.1)

-- DB Shutdown

Connected to:

Oracle Database 12c Enterprise Edition Release 12.2.0.1.0 - 64bit Production SQL> shutdown immediate;

1. Stop the CRS managed resources running from DB homes.

database home owner execute

$ <ORACLE_HOME>/bin/srvctl stop home -o <ORACLE_HOME> -s <status file location> -n <node name>

[oracle:YOUNHA1:/home/oracle> /oracle/app/product/12.2.0/bin/srvctl stop home -o /oracle/app/product/12.2.0/ -s /home/oracle/status -n younha1

2. Run the pre root script.

root user execute

# <GI_HOME>/crs/install/rootcrs.sh -prepatch

[root:younha1/root> /oragrid/12.2.0/grid/crs/install/rootcrs.sh -prepatch

Using configuration parameter file: /oragrid/12.2.0/grid/crs/install/crsconfig_params The log of current session can be found at:

/oragrid/grid_base/crsdata/younha1/crsconfig/crspatch_younha1_2018-03-03_04-27-11PM.log Oracle Clusterware active version on the cluster is [12.2.0.1.0]. The cluster upgrade state is [NORMAL]. The cluster active patch level is [0].

CRS-2791: Starting shutdown of Oracle High Availability Services-managed resources on 'younha1' CRS-2673: Attempting to stop 'ora.crsd' on 'younha1'

CRS-2790: Starting shutdown of Cluster Ready Services-managed resources on server 'younha1' CRS-2673: Attempting to stop 'ora.MGMT.dg' on 'younha1'

CRS-2673: Attempting to stop 'ora.LISTENER.lsnr' on 'younha1' CRS-2673: Attempting to stop 'ora.chad' on 'younha1'

CRS-2677: Stop of 'ora.MGMT.dg' on 'younha1' succeeded CRS-2673: Attempting to stop 'ora.OCR_VOTE.dg' on 'younha1' CRS-2673: Attempting to stop 'ora.DATA.dg' on 'younha1' CRS-2673: Attempting to stop 'ora.RECO.dg' on 'younha1' CRS-2677: Stop of 'ora.OCR_VOTE.dg' on 'younha1' succeeded CRS-2677: Stop of 'ora.DATA.dg' on 'younha1' succeeded CRS-2677: Stop of 'ora.RECO.dg' on 'younha1' succeeded CRS-2673: Attempting to stop 'ora.asm' on 'younha1'

CRS-2677: Stop of 'ora.LISTENER.lsnr' on 'younha1' succeeded CRS-2673: Attempting to stop 'ora.younha1.vip' on 'younha1' CRS-2677: Stop of 'ora.asm' on 'younha1' succeeded

CRS-2673: Attempting to stop 'ora.ASMNET1LSNR_ASM.lsnr' on 'younha1' CRS-2677: Stop of 'ora.younha1.vip' on 'younha1' succeeded

CRS-2677: Stop of 'ora.ASMNET1LSNR_ASM.lsnr' on 'younha1' succeeded

(32)

CRS-2677: Stop of 'ora.chad' on 'younha1' succeeded

CRS-2672: Attempting to start 'ora.younha1.vip' on 'younha2' CRS-2676: Start of 'ora.younha1.vip' on 'younha2' succeeded CRS-2673: Attempting to stop 'ora.ons' on 'younha1'

CRS-2677: Stop of 'ora.ons' on 'younha1' succeeded

CRS-2673: Attempting to stop 'ora.net1.network' on 'younha1' CRS-2677: Stop of 'ora.net1.network' on 'younha1' succeeded

CRS-2792: Shutdown of Cluster Ready Services-managed resources on 'younha1' has completed CRS-2677: Stop of 'ora.crsd' on 'younha1' succeeded

CRS-2673: Attempting to stop 'ora.asm' on 'younha1' CRS-2673: Attempting to stop 'ora.crf' on 'younha1'

CRS-2673: Attempting to stop 'ora.drivers.acfs' on 'younha1' CRS-2673: Attempting to stop 'ora.gpnpd' on 'younha1'

CRS-2673: Attempting to stop 'ora.mdnsd' on 'younha1' CRS-2677: Stop of 'ora.drivers.acfs' on 'younha1' succeeded CRS-2677: Stop of 'ora.crf' on 'younha1' succeeded

CRS-2677: Stop of 'ora.gpnpd' on 'younha1' succeeded CRS-2677: Stop of 'ora.mdnsd' on 'younha1' succeeded CRS-2677: Stop of 'ora.asm' on 'younha1' succeeded

CRS-2673: Attempting to stop 'ora.cluster_interconnect.haip' on 'younha1' CRS-2677: Stop of 'ora.cluster_interconnect.haip' on 'younha1' succeeded CRS-2673: Attempting to stop 'ora.ctssd' on 'younha1'

CRS-2673: Attempting to stop 'ora.evmd' on 'younha1' CRS-2677: Stop of 'ora.ctssd' on 'younha1' succeeded CRS-2677: Stop of 'ora.evmd' on 'younha1' succeeded CRS-2673: Attempting to stop 'ora.cssd' on 'younha1' CRS-2677: Stop of 'ora.cssd' on 'younha1' succeeded CRS-2673: Attempting to stop 'ora.gipcd' on 'younha1' CRS-2677: Stop of 'ora.gipcd' on 'younha1' succeeded

CRS-2793: Shutdown of Oracle High Availability Services-managed resources on 'younha1' has completed

CRS-4133: Oracle High Availability Services has been stopped.

2018/03/03 16:28:19 CLSRSC-4012: Shutting down Oracle Trace File Analyzer (TFA) Collector.

2018/03/03 16:28:28 CLSRSC-4013: Successfully shut down Oracle Trace File Analyzer (TFA) Collector.

2018/03/03 16:28:29 CLSRSC-347: Successfully unlock /oragrid/12.2.0/grid

3. Patch GI home.

GI home owner execute

$ <GI_HOME>/OPatch/opatch apply -oh <GI_HOME> -local <UNZIPPED_PATCH_LOCATION>/%BUGNO%/%OCW TRACKING BUG%

$ <GI_HOME>/OPatch/opatch apply -oh <GI_HOME> -local <UNZIPPED_PATCH_LOCATION>/%BUGNO%/%ACFS TRACKING BUG%

$ <GI_HOME>/OPatch/opatch apply -oh <GI_HOME> -local <UNZIPPED_PATCH_LOCATION>/%BUGNO%/%DBWLM TRACKING BUG%

$ <GI_HOME>/OPatch/opatch apply -oh <GI_HOME> -local <UNZIPPED_PATCH_LOCATION>/%BUGNO%/%DB RU TRACKING BUG%

$ <GI_HOME>/OPatch/opatch apply -oh <GI_HOME> -local <UNZIPPED_PATCH_LOCATION>/%BUGNO%/%TOMCAT RU TRACKING BUG%

(33)

[oragrid:+ASM1:/home/oragrid> /oragrid/12.2.0/grid/OPatch/opatch apply -oh /oragrid/12.2.0/grid/

-local /oramedia/27100009/27335416/

Oracle Home : /oragrid/12.2.0/grid Central Inventory : /oragrid/oraInventory

from : /oragrid/12.2.0/grid//oraInst.loc OPatch version : 12.2.0.1.12

Log file location : /oragrid/12.2.0/grid/cfgtoollogs/opatch/opatch2018-03-03_16-31-34PM_1.log Verifying environment and performing prerequisite checks...

OPatch continues with these patches: 27335416 Do you want to proceed? [y|n]

y

User Responded with: Y All checks passed.

Please shutdown Oracle instances running out of this ORACLE_HOME on the local system.

(Oracle Home = '/oragrid/12.2.0/grid')

Is the local system ready for patching? [y|n]

y

User Responded with: Y Backing up files...

Applying interim patch '27335416' to OH '/oragrid/12.2.0/grid' Patching component oracle.has.deconfig, 12.2.0.1.0...

Patching component oracle.has.rsf, 12.2.0.1.0...

Patching component oracle.has.crs, 12.2.0.1.0...

Patching component oracle.has.db, 12.2.0.1.0...

Patching component oracle.has.cvu, 12.2.0.1.0...

Patching component oracle.has.common.cvu, 12.2.0.1.0...

Patching component oracle.has.common, 12.2.0.1.0...

Patch 27335416 successfully applied.

Log file location: /oragrid/12.2.0/grid/cfgtoollogs/opatch/opatch2018-03-03_16-31-34PM_1.log OPatch succeeded.

-local /oramedia/27100009/27128906/

-local /oramedia/27100009/26839277/

-local /oramedia/27100009/27105253/

-local /oramedia/27100009/27144050/

(34)

4. Patch DB home.

database home owner execute

$ <UNZIPPED_PATCH_LOCATION>/%BUGNO%/%OCW TRACKING BUG%/custom/scripts/prepatch.sh -dbhome <ORACLE_HOME>

$ <ORACLE_HOME>/OPatch/opatch apply -oh <ORACLE_HOME> -local <UNZIPPED_PATCH_LOCATION>/%BUGNO%/%OCW TRACKING BUG%

$ <ORACLE_HOME>/OPatch/opatch apply -oh <ORACLE_HOME> -local <UNZIPPED_PATCH_LOCATION>/%BUGNO%/%DB RU TRACKING BUG%

$ <UNZIPPED_PATCH_LOCATION>/%BUGNO%/%OCW TRACKING BUG%/custom/scripts/postpatch.sh -dbhome <ORACLE_HOME>

[oracle:YOUNHA1:/home/oracle> /oramedia/27100009/27335416/custom/scripts/prepatch.sh -dbhome /oracle/app/product/12.2.0/

/oramedia/27100009/27335416/custom/scripts/prepatch.sh completed successfully.

[oracle:YOUNHA1:/home/oracle> /oracle/app/product/12.2.0/OPatch/opatch apply -oh /oracle/app/product/12.2.0/ -local /oramedia/27100009/27335416/

[oracle:YOUNHA1:/home/oracle> /oracle/app/product/12.2.0/OPatch/opatch apply -oh /oracle/app/product/12.2.0/ -local /oramedia/27100009/27105253/

[oracle:YOUNHA1:/home/oracle> /oramedia/27100009/27335416/custom/scripts/postpatch.sh -dbhome /oracle/app/product/12.2.0/

Reading /oracle/app/product/12.2.0//install/params.ora..

Found uninstantiated /oracle/app/product/12.2.0//crs/sbs/srvctl.sbs file, copying to /oracle/app/product/12.2.0//bin/srvctl

Parsing file /oracle/app/product/12.2.0//bin/srvctl Parsing file /oracle/app/product/12.2.0//bin/srvconfig Parsing file /oracle/app/product/12.2.0//bin/cluvfy Verifying file /oracle/app/product/12.2.0//bin/srvctl Verifying file /oracle/app/product/12.2.0//bin/srvconfig Verifying file /oracle/app/product/12.2.0//bin/cluvfy

Reapplying file permissions on /oracle/app/product/12.2.0//bin/srvctl Reapplying file permissions on /oracle/app/product/12.2.0//bin/srvconfig Reapplying file permissions on /oracle/app/product/12.2.0//bin/cluvfy Reapplying file permissions on /oracle/app/product/12.2.0//bin/diskmon.bin Reapplying file permissions on /oracle/app/product/12.2.0//bin/lsnodes Reapplying file permissions on /oracle/app/product/12.2.0//bin/osdbagrp Reapplying file permissions on /oracle/app/product/12.2.0//bin/rawutl

Reapplying file permissions on /oracle/app/product/12.2.0//srvm/admin/ractrans Reapplying file permissions on /oracle/app/product/12.2.0//srvm/admin/getcrshome Reapplying file permissions on /oracle/app/product/12.2.0//bin/crsdiag.pl

Postpatch completed successfully

(35)

5. Run the post script.

root user execute

# <GI_HOME>/rdbms/install/rootadd_rdbms.sh

# <GI_HOME>/crs/install/rootcrs.sh -postpatch

[root:younha1/root> /oragrid/12.2.0/grid/rdbms/install/rootadd_rdbms.sh [root:younha1/root> /oragrid/12.2.0/grid/crs/install/rootcrs.sh -postpatch

Using configuration parameter file: /oragrid/12.2.0/grid/crs/install/crsconfig_params The log of current session can be found at:

/oragrid/grid_base/crsdata/younha1/crsconfig/crspatch_younha1_2018-03-03_04-44-38PM.log 2018/03/03 16:44:56 CLSRSC-4015: Performing install or upgrade action for Oracle Trace File Analyzer (TFA) Collector.

2018/03/03 16:45:37 CLSRSC-4003: Successfully patched Oracle Trace File Analyzer (TFA) Collector.

2018/03/03 16:45:41 CLSRSC-329: Replacing Clusterware entries in file 'oracle-ohasd.conf' CRS-4123: Starting Oracle High Availability Services-managed resources

CRS-2672: Attempting to start 'ora.mdnsd' on 'younha1' CRS-2672: Attempting to start 'ora.evmd' on 'younha1' CRS-2676: Start of 'ora.mdnsd' on 'younha1' succeeded CRS-2676: Start of 'ora.evmd' on 'younha1' succeeded CRS-2672: Attempting to start 'ora.gpnpd' on 'younha1' CRS-2676: Start of 'ora.gpnpd' on 'younha1' succeeded CRS-2672: Attempting to start 'ora.gipcd' on 'younha1' CRS-2676: Start of 'ora.gipcd' on 'younha1' succeeded

CRS-2672: Attempting to start 'ora.cssdmonitor' on 'younha1' CRS-2676: Start of 'ora.cssdmonitor' on 'younha1' succeeded CRS-2672: Attempting to start 'ora.cssd' on 'younha1' CRS-2672: Attempting to start 'ora.diskmon' on 'younha1' CRS-2676: Start of 'ora.diskmon' on 'younha1' succeeded CRS-2676: Start of 'ora.cssd' on 'younha1' succeeded

<중략>

Oracle Clusterware active version on the cluster is [12.2.0.1.0]. The cluster upgrade state is [ROLLING PATCH]. The cluster active patch level is [0].

Connecting to database...OK

Note: Datapatch will only apply or rollback SQL fixes for PDBs

that are in an open state, no patches will be applied to closed PDBs.

Please refer to Note: Datapatch: Database 12c Post Patch SQL Automation (Doc ID 1585822.1)

Determining current state...done

Adding patches to installation queue and performing prereq checks...done Installation queue:

For the following PDBs: CDB$ROOT PDB$SEED GIMR_DSCREP_10 Nothing to roll back

The following patches will be applied:

27105253 (DATABASE RELEASE UPDATE 12.2.0.1.180116) Installing patches...

Patch installation complete. Total patches installed: 3 Validating logfiles...done

SQL Patching tool complete on Sat Mar 3 16:54:05 2018

(36)

6. Start the CRS managed resources that were earlier running from DB homes.

database home owner execute

$ <ORACLE_HOME>/bin/srvctl start home -o <ORACLE_HOME> -s <status file location> -n <node name>

[oracle:YOUNHA1:/home/oracle> /oracle/app/product/12.2.0/bin/srvctl start home -o /oracle/app/product/12.2.0/ -s /home/oracle/status -n younha1

-- DB Startup

Connected to an idle instance.

SQL> startup

2 번 노드도 동일하게 수행합니다. 1 번 & 6 번 Step 의 node name 값만 주의해주시면 명령어는 동일합 니다.

5 번 Step 에서 아래와 같이 cluster patch level 을 확인할 수 있습니다.

Oracle Clusterware active version on the cluster is [12.2.0.1.0]. The cluster upgrade state is [NORMAL]. The cluster active patch level is [2960767134].

(37)

7. For each database instance running on the Oracle home being patched, run the datapatch utility

database home owner execute

$ <ORACLE_HOME>/OPatch/datapatch -verbose

한 노드에서만 수행하면 된다.

[oracle:YOUNHA1:/home/oracle> /oracle/app/product/12.2.0/OPatch/datapatch -verbose SQL Patching tool version 12.2.0.1.0 Production on Sat Mar 3 17:22:41 2018

Log file for this invocation:

/oracle/app/cfgtoollogs/sqlpatch/sqlpatch_22331_2018_03_03_17_22_41/sqlpatch_invocation.log Connecting to database...OK

Bootstrapping registry and package to current versions...done Determining current state...done

Current state of SQL patches:

Bundle series DBRU:

ID 180116 in the binary registry and not installed in the SQL registry Adding patches to installation queue and performing prereq checks...

Installation queue:

Nothing to roll back

27105253 (DATABASE RELEASE UPDATE 12.2.0.1.180116) Installing patches...

Patch installation complete. Total patches installed: 1 Validating logfiles...

Patch 27105253 apply: SUCCESS logfile:

/oracle/app/cfgtoollogs/sqlpatch/27105253/21862470/27105253_apply_YOUNHA_2018Mar03_17_23_23.log (no errors)

SQL Patching tool complete on Sat Mar 3 17:26:10 2018 [oracle:YOUNHA1:/home/oracle> sqlplus "/as sysdba"

SQL> select patch_id, version, action, status, bundle_id from dba_registry_sqlpatch;

PATCH_ID VERSION ACTION STATUS BUNDLE_ID --- --- --- --- --- 27105253 12.2.0.1 APPLY SUCCESS 180116

(38)

7.3. 11g vs 12c

11g 와 12c 는 수행 절차는 동일하나 명령어의 차이가 있다. 11g R2 Manual 명령어만 기술하겠다.

Database Shutdown ( 1&2 노드 )

< 1 번노드 >

1

. $ <ORACLE_HOME>/bin/srvctl stop home -o <ORACLE_HOME> -s <status file location> -n <node name>

2. # <GI_HOME>/crs/install/rootcrs.pl –unlock

3. $<GI_HOME>/OPatch/opatch napply -oh <GI_HOME> -local

<UNZIPPED_PATCH_LOCATION>/<GI_PSU_number>/<OCW Components_number>

$ <GI_HOME>/OPatch/opatch napply -oh <GI_HOME> -local

<UNZIPPED_PATCH_LOCATION>/<GI_PSU_number>/<ACFS Components_number>

$ <GI_HOME>/OPatch/opatch apply -oh <GI_HOME> -local

<UNZIPPED_PATCH_LOCATION>/<GI_PSU_number>/<DB_PSU_number>

4. $<UNZIPPED_PATCH_LOCATION>/<GI_PSU_number>/<OCW Components_number>/custom/server/

<OCW Components_number>/custom/scripts/prepatch.sh -dbhome <ORACLE_HOME>

$ <ORACLE_HOME>/OPatch/opatch napply -oh <ORACLE_HOME> -local

<UNZIPPED_PATCH_LOCATION>/<GI_PSU_number>/<OCW Components_number>

/custom/server/<OCW Components_number>

$ <ORACLE_HOME>/OPatch/opatch apply -oh <ORACLE_HOME> -local

<UNZIPPED_PATCH_LOCATION>/<GI_PSU_number>/<DB_PSU_number>

$ <UNZIPPED_PATCH_LOCATION>/<GI_PSU_number>/<OCW Components_number>/custom/server/

<OCW Components_number>/custom/scripts/postpatch.sh -dbhome <ORACLE_HOME>

5. # <GI_HOME>/rdbms/install/rootadd_rdbms.sh

# <GI_HOME>/crs/install/rootcrs.pl –patch

6.

$ <ORACLE_HOME>/bin/srvctl start home -o <ORACLE_HOME> -s <status file location> -n <node name>

<2 번 노드도 동일하게 수행>

1 ~ 6

Database Startup ( 1&2 노드 )

<한노드에서만 수행>

7. cd $ORACLE_HOME/rdbms/admin

SQL> @catbundle.sql psu apply

(39)

8. 실습 – DB PSU 적용

실습 환경

DB Version

Enterprise Edition 12.1.0.2 ( Single )

OS Version

HP

ORACLE_HOME

/oracle/product/12.1.0/

9. 실습 – Interim Patch

Interim Patch 는 특정 이슈에 대한 패치로서 하기와 같이 Bug 로 인한 DB 장애 상황을 가정하겠습니다.

문제 설명

RAC 11.2.0.4~12.2.0.1 특정 PSU 버전에서, 서버 Reboot or CRS Restart 과정에서 Cluster Join 이 실패하 였습니다.

이 문제는 AWS 등 여러 IaaS Cloud 환경에서 Oracle DB 를 사용할 수 있도록 하는 code 가 추가된 버전 들에서 발생하며, cloud 환경 여부를 체크하는 과정에서 정상적으로 확인이 이루어지지 않아 발생하는 것으로 추정됩니다.

현재 해당 문제가 Fix 된 Patch (interim : 27213224, OCW Patch : 27309269 )를 support.oracle.com 에서 다운로드 할 수 있습니다.

영향받는 버전 11.2.0.4.170814

12.1.0.2.170814, 12.1.0.2.171017, 12.1.0.2.180116 12.2.0.1.170814, 12.2.0.1.171003, 12.2.0.1.180116

27213224 "NODES ARE NOT ABLE JOIN TO GRID INFRASTRCTURE CSSD FAILING WITH NO NETWORK HB - 3rd party cloud service

사전 확인

아래 명령 수행시

http 200 OK 를 리턴하면 문제 발생

$ curl "http://169.254.169.254/latest/meta-data/services/domain" -v

Patch 27309269: TRACKING BUG TO PROVIDE FIX FOR 27213224 IN OCWPSU BUNDLES

Patch 27213224: NODES ARE NOT ABLE JOIN TO GRID INFRASTRCTURE CSSD FAILING WITH NO

NETWORK HB

(42)

Read Me

패치를 하기 위해서는 사전에 Read Me 를 참고하여 테스트 후 운영에 적용하시길 바랍니다.

Read Me 의 일부만 기술했습니다.

Oracle Database 12c Release 12.2.0.1.180116DBJAN2018RU

ORACLE DATABASE Patch for Bug# 27213224 for Linux-x86-64 Platforms

(I) Prerequisites (사전 확인) ---

Before you install or deinstall the patch, ensure that you meet the following requirements:

Note: In case of an Oracle RAC environment, meet these prerequisites on each of the nodes.

Ensure that you have OPatch 12c Release 12.2.0.1.7 or higher. Oracle recommends that you use the lates t version available for 12c Release 12.2.0.1.7.

패치 미디어 Unzip

[root:younha1/oramedia> unzip p27213224_12201180116DBJAN2018RU_Linux-x86-64.zip Archive: p27213224_12201180116DBJAN2018RU_Linux-x86-64.zip

creating: 27213224/

creating: 27213224/etc/

creating: 27213224/etc/config/

inflating: 27213224/etc/config/actions.xml inflating: 27213224/etc/config/inventory.xml creating: 27213224/files/

creating: 27213224/files/lib/

creating: 27213224/files/lib/libgeneric12.a/

inflating: 27213224/files/lib/libgeneric12.a/kgcs.o inflating: 27213224/README.txt

inflating: PatchSearch.xml

[root:younha1/oramedia> chmod -R 777 27213224/

Conflict Check

[oracle:YOUNHA1:/oramedia/27213224> opatch prereq CheckConflictAgainstOHWithDetail -ph ./

(43)

PREREQ session

Oracle Home : /oracle/app/product/12.2.0 Central Inventory : /oragrid/oraInventory

from : /oracle/app/product/12.2.0/oraInst.loc OPatch version : 12.2.0.1.12

Log file location : /oracle/app/product/12.2.0/cfgtoollogs/opatch/opatch2018-04-05_16-37- 17PM_1.log

Invoking prereq "checkconflictagainstohwithdetail"

OPatch succeeded.

1 번노드 서비스 종료

[oracle:YOUNHA1:/home/oracle> srvctl stop instance -d younha -n younha1 [root:younha1/oramedia> crsctl stop crs

(II) Installation ---

To install the patch, follow these steps:

[oracle:YOUNHA1:/home/oracle> cd /oramedia/27213224/

[oracle:YOUNHA1:/oramedia/27213224> opatch apply Oracle Interim Patch Installer version 12.2.0.1.12

Verifying environment and performing prerequisite checks...

OPatch continues with these patches: 27213224 Do you want to proceed? [y|n]

y

User Responded with: Y All checks passed.

Please shutdown Oracle instances running out of this ORACLE_HOME on the local system.

(Oracle Home = '/oracle/app/product/12.2.0') Is the local system ready for patching? [y|n]

y

User Responded with: Y Backing up files...

Applying interim patch '27213224' to OH '/oracle/app/product/12.2.0'

(44)

Patching component oracle.rdbms.rsf, 12.2.0.1.0...

Patching component oracle.rdbms, 12.2.0.1.0...

Patch 27213224 successfully applied.

Log file location: /oracle/app/product/12.2.0/cfgtoollogs/opatch/opatch2018-04-05_16-48- 01PM_1.log

OPatch succeeded.

Verify whether the patch has been successfully installed by running the following command:

[oracle:YOUNHA1:/oramedia/27213224> opatch lsinventory Oracle Interim Patch Installer version 12.2.0.1.12

Lsinventory Output file location :

/oracle/app/product/12.2.0/cfgtoollogs/opatch/lsinv/lsinventory2018-04-05_17-17-48PM.txt ---

Local Machine Information::

Hostname: younha1 ARU platform id: 226

ARU platform description:: Linux x86-64 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 27213224 : applied on Thu Apr 05 16:48:09 KST 2018 Unique Patch ID: 21919615

Created on 1 Feb 2018, 13:43:24 hrs PST8PDT Bugs fixed:

27213224

This patch overlays patches:

27105253

This patch needs patches:

27105253 as prerequisites

Patch 27335416 : applied on Thu Mar 29 14:08:28 KST 2018 Unique Patch ID: 21843624

Patch description: "OCW JAN 2018 RELEASE UPDATE 12.2.0.1.180116 (27335416)"

Created on 8 Jan 2018, 23:51:29 hrs PST8PDT

<하략>

Oracle Patch

Copyright(C) 2004 Goodus Inc.

All Rights Reserved

Oracle Patch

Contents

1. 문서 개요 ... 3

2. ORACLE RELEASE 정책 ... 5

3. 패치 제공 방식 ... 6

3.1. 12.1.0.2 and older ... 6

3.2. 12.2.0.1 and later versions... 9

3.3. Patch version numbering 변경 ... 12

3.4. Where to find last Patches for Database? ... 13

3.5. 12.1.0.1 이후 변경 사항 ... 14

3.6. Summary ... 15

4. Conflict Check ... 16

5. OPatch Utility ... 19

6. 실습 - GI PSU 적용 ( opatch auto ) ... 20

6.1. 사전 준비 ... 21

6.2. OCM Configuration < 1node & 2node >... 22

6.3. Validation of Oracle Inventory < 1node & 2node > ... 23

6.4. Patching ORACLE_HOME and GRID_HOME Together ... 24

6.5. Patch Post-Installation Instructions ... 26

6.6. Patch Check ... 26

6.7. Patch Deinstallation ... 27

6.8. 11g vs 12c ... 28

7. 실습 - GI PSU 적용 ( manual ) ... 29

7.1. 사전 준비 ... 30

7.2. Manual Patch ... 31

7.3. 11g vs 12c ... 38

8. 실습 – DB PSU 적용 ... 39

9. 실습 – Interim Patch ... 41

10. OPLAN ... 47

11. OPatch TrobleShooting ... 50

12. Appendix... 55

1. 문서 개요

오라클에서 Release 출시 후 발견된 Bug 에 대한 Fixes 및 보안 관련 사항에 대해 개별 패치, Patch Set Update 등을 제공합니다.

이번 화에서는 오라클 패치의 개념 및 정책에 대해 알아보고 실습을 통해 패치적용 방법을 기술하였습 니다.

ReadMe 를 참고하여 실습 부분을 작성하였습니다.

운영 환경 & 버전에 따라 패치 적용 Step 이 기술되어 있으며 해당 패치에 대한 Known Issue 사항이 정리되어 있습니다.

꼭 패치를 적용하시기 전에 ReadMe 를 보시고 테스트 하기를 당부드립니다.

Oracle® OPatch User’s Guide 에서 발췌한 Patch Process 의 개요입니다.

환경의 패치 요구 사항에 관계없이 기본 패치 방법론은 동일합니다.

간략하게 요약해 보면 다음과 같이 나눌 수 있습니다.

필요로 하는 패치가 무엇인가?

운영/개발 환경에 맞는 패치 및 OPatch 다운로드 & Conflict 체크를 수행하여 해당 패치 적용 가능 확인 개발 패치 및 테스트 후 운영 적용 및 서비스 확인

위의 기본 패치 방법론에 도움이 될 수 있도록 소개 & 실습을 진행하겠습니다.

2. ORACLE RELEASE 정책

각 버전에 대해 하기와 같이 Update, Fixes, Security Alerts 을 MOS 에서 제공하고 있습니다.

( 해당 버전의 마지막 Release 에서 Extended Support 적용 ( ex> 11.2.0.4, 12.1.0.2, 19c ) )

11.2.0.3 버전을 살펴보면 Premier Support 는 완료되어 신규 버그 & 보안 등 이슈에 대한 패치가 나오 지 않는 상황입니다.

상기와 같이 2015 년 7 월이 마지막 PSU 이며 SR 진행시에도 신규로 발견된 버그에 대해서는 Fixed 를

지원 받을 수 없습니다.

3. 패치 제공 방식

3.1. 12.1.0.2 and older

Oracle provides patches for both proactive and reactive maintenance

● Reactive Patches

일반적으로 "Interim Patches" 로 제공됩니다. (과거의 "one-off" patch)

"defect, version, platform" 조합의 요청에 의해 제공됩니다.

Specific bugs 에 대한 응답으로 고객이 사용할 수 있는 bug fix 입니다.

● Proactive Patches

♦ Security Patch Update (SPU)

Oracle 의 크리티컬 패치 업데이트 (CPU) 프로그램의 일환으로 발표된 보안 패치 모음입니다.

SPU 는 CPU 프로그램의 보안 패치만 포함됩니다.

미리 정의된 분기별 일정에서 제공됩니다. (1, 4, 7, 10 월 중순 화요일)

Note : 데이터베이스 SPU 는 데이터베이스 릴리스 12c 부터 단계적으로 폐지되고 있습니다.

♦ Patch Set Update (PSU)

현장에서 발생하는 입증된 영향력이 큰 버그에 대한 누적된 수정 사항 모음입니다.

옵티마이저에 대한 변경 혹은 응용 프로그램의 동작을 변경하는 수정을 포함하지 않습니다.

PSU 는 CPU 프로그램 보안 수정 및 추가 효과가 높은 / 낮은 위험 심각한 BUG 수정이 포함됩니다.

미리 정의 된 분기별 일정에서 제공됩니다. (1, 4, 7, 10 월 중순 화요일)

♦ Bundle Patch (BP)

주어진 기능, 제품 또는 구성의 버그를 해결하기 위한 누적된 수정 사항 모음입니다.

BP 는 모든 PSU 수정을 포함합니다.

PSU 의 슈퍼 세트입니다.

PSU 출시보다 더 빈번한 미리 정의된 일정에서 제공됩니다.

2016 년 4 월 시점에서 Database Patch for Engineered Systems and Database In-Memory 는 "Database

Proactive Bundle Patch"로 개명되었습니다.

다양한 pro-active 패치 데이터베이스 패치의 내용은 다음과 같습니다.

SPU 는 CPU 프로그램의 보안 패치만 포함됩니다.

PSU 는 CPU 프로그램 보안 수정 및 추가 효과가 높은 / 낮은 위험 심각한 BUG 수정이 포함됩니다.

3.3. Patch version numbering ^변경 ... 12

3.5. 12.1.0.1 ^이후 ^변경 ^사항 ... 14

6.1. ^사전 ^준비 ... 21

7.1. ^사전 ^준비 ... 30