12.2 Grid RUR 安裝

xychong123發表於2018-08-09

資料庫版本：12.2.0.1.0 

RUR:p28251142_122010_Linux-x86-64.zip

12.2.0.1 Grid Infrastructure Release Update Revision (Revision)

Release Date Version Download Link
17-Jul-2018 GI Jan2017 Release Update Revision 12.2.0.1.180717 Patch 28251142
17-Jul-2018 GI Apr2017 Release Update Revision 12.2.0.1.180717 Patch 28251239
17-Apr-2018 GI Oct2017 Release Update Revision 12.2.0.1.180417 Patch 27696758
17-Apr-2018 GI Jan2017 Release Update Revision 12.2.0.1.180417 Patch 27696736
16-Jan-2018 GI Jul2017 Release Update Revision 12.2.0.1.180116 Patch 27224023
16-Jan-2018 GI Oct2017 Release Update Revision 12.2.0.1.180116 Patch 27224075
17-Oct-2017 GI Jul2017 Release Update Revision 12.2.0.1.171017


1,opatch 版本確定

#grid

[grid@prod04 ~]$ /u01/app/grid_home/OPatch/opatch version

OPatch Version: 12.2.0.1.14

#database

[oracle@prod04 soft]$ /u01/app/oracle/product/12.2.0/dbhome_1/OPatch/opatch version

OPatch Version: 12.2.0.1.14


2,grid 使用者解壓補丁



3，RUR 安裝

[root@prod04 ~]# /u01/app/grid_home/OPatch/opatchauto apply /soft/28251142 -nonrolling 


遇到報錯，補丁安裝

4，故障解決方法

$GRID_HOME/bin/clscfg -localpatch

$GRID_HOME/crs/install/rootcrs.sh  -lock


手動啟動has報錯：

[root@prod04 ~]# /u01/app/grid_home/bin/crsctl start crs

CRS-6706: Oracle Clusterware Release patch level ('3106313030') does not match Software patch level ('0'). Oracle Clusterware cannot be started.

CRS-4000: Command Start failed, or completed with errors


執行如下2條命令，叢集軟體正常啟動：

[root@prod04 ~]# /u01/app/grid_home/bin/clscfg -localpatch

Creating OCR keys for user 'root', privgrp 'root'..

Operation successful.

[root@prod04 ~]# /u01/app/grid_home/crs/install/rootcrs.sh -lock

Using configuration parameter file: /u01/app/grid_home/crs/install/crsconfig_params

The log of current session can be found at:

  /u01/app/grid/crsdata/prod04/crsconfig/crslock_prod04_2018-08-09_01-47-23PM.log

2018/08/09 13:47:27 CLSRSC-329: Replacing Clusterware entries in file 'oracle-ohasd.service'

[root@prod04 ~]# /u01/app/grid_home/bin/crsctl start crs

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


5，資料庫應用補丁

[oracle@prod04 ~]$ sqlplus / as sysdba


SQL*Plus: Release 12.2.0.1.0 Production on Thu Aug 9 13:50:22 2018


Copyright (c) 1982, 2016, Oracle.  All rights reserved.


Connected to an idle instance.


SQL> startup



ORACLE instance started.


Total System Global Area 2466250752 bytes

Fixed Size     8795760 bytes

Variable Size   738199952 bytes

Database Buffers 1711276032 bytes

Redo Buffers     7979008 bytes

Database mounted.

Database opened.

SQL> SQL> SQL> alter pluggable database all open;

show pdbs;


Pluggable database altered.


SQL> 

    CON_ID CON_NAME   OPEN MODE  RESTRICTED

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

2 PDB$SEED   READ ONLY  NO

3 PDB01   READ WRITE NO

SQL> select patch_id,action,status,BUNDLE_SERIES from dba_registry_sqlpatch;


no rows selected

SQL> exit

Disconnected from Oracle Database 12c Enterprise Edition Release 12.2.0.1.0 - 64bit Production

[oracle@prod04 ~]$ 

[oracle@prod04 ~]$ cd /u01/app/oracle/product/12.2.0/dbhome_1/OPatch/

[oracle@prod04 OPatch]$ 

[oracle@prod04 OPatch]$ ./datapatch -verbose

SQL Patching tool version 12.2.0.1.0 Production on Thu Aug  9 13:54:35 2018

Copyright (c) 2012, 2018, Oracle.  All rights reserved.


Log file for this invocation: /u01/app/oracle/cfgtoollogs/sqlpatch/sqlpatch_38873_2018_08_09_13_54_35/sqlpatch_invocation.log


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)

Bootstrapping registry and package to current versions...done

Determining current state...done


Current state of SQL patches:

Bundle series 12.2.0.1.180717DBJAN2018RUR:

  ID 180717 in the binary registry and not installed in any PDB


Adding patches to installation queue and performing prereq checks...

Installation queue:

  For the following PDBs: CDB$ROOT PDB$SEED PDB01

    Nothing to roll back

    The following patches will be applied:

      27872031 (DATABASE JAN 2018 RELEASE UPDATE REVISION 12.2.0.1.180717)


Installing patches...

Patch installation complete.  Total patches installed: 3


Validating logfiles...

Patch 27872031 apply (pdb CDB$ROOT): SUCCESS

  logfile: /u01/app/oracle/cfgtoollogs/sqlpatch/27872031/22311840/27872031_apply_CDB_CDBROOT_2018Aug09_13_55_39.log (no errors)

Patch 27872031 apply (pdb PDB$SEED): SUCCESS

  logfile: /u01/app/oracle/cfgtoollogs/sqlpatch/27872031/22311840/27872031_apply_CDB_PDBSEED_2018Aug09_13_58_16.log (no errors)

Patch 27872031 apply (pdb PDB01): SUCCESS

  logfile: /u01/app/oracle/cfgtoollogs/sqlpatch/27872031/22311840/27872031_apply_CDB_PDB01_2018Aug09_13_58_16.log (no errors)

SQL Patching tool complete on Thu Aug  9 13:59:54 2018



select patch_id,action,status,BUNDLE_SERIES from dba_registry_sqlpatch;


6，補丁狀態檢測

Patch Numbers Getting Installed as Part of this Bundle Patch

Patch Number Description Applicable Homes

27872031

Database Jan 2018 Release Update Revision 12.2.0.1.180717

Only DB Home for non-Oracle RAC setup. Both DB Homes and Grid Home for Oracle RAC setup.

28222334

OCW Jan 2018 Release Update Revision 12.2.0.1.180620

Both DB Homes and Grid Home

27128906

ACFS Jan 2018 Release Update 12.2.0.1.180116 Footnote 2

Only Grid Home

26839277

DBWLM Release Update 12.2.0.1.170913 Footnote 2

Only Grid Home

27144050

Tomcat Release Update 12.2.0.1.171023 Footnote 2

Only Grid Home

Footnote 2

ACFS, DBWLM and TOMCAT subpatches are not applicable to the HP-UX Itanium and Linux on IBM System z platforms.


[grid@prod04 ~]$ opatch lspatches

28222334;OCW JAN 2018 RELEASE UPDATE REVISION 12.2.0.1.0(ID:180620) (28222334)

27872031;Database Jan 2018 Release Update Revision : 12.2.0.1.180717 (27872031)

27144050;Tomcat Release Update 12.2.0.1.0(ID:171023.0830) (27144050)

27128906;ACFS Release Update : 12.2.0.1.0 (27128906)

26839277;DBWLM RELEASE UPDATE 12.2.0.1.0(ID:170913) (26839277)

OPatch succeeded.

[oracle@prod04 ~]$ /u01/app/oracle/product/12.2.0/dbhome_1/OPatch/opatch lspatches

28222334;OCW JAN 2018 RELEASE UPDATE REVISION 12.2.0.1.0(ID:180620) (28222334)

27872031;Database Jan 2018 Release Update Revision : 12.2.0.1.180717 (27872031)

OPatch succeeded.


select patch_id,action,status,BUNDLE_SERIES from dba_registry_sqlpatch;






附錄：

RUR按照日誌：

[root@prod04 ~]# /u01/app/grid_home/OPatch/opatchauto apply /soft/28251142 -nonrolling 


OPatchauto session is initiated at Wed Aug  8 14:14:36 2018


System initialization log file is /u01/app/grid_home/cfgtoollogs/opatchautodb/systemconfig2018-08-08


Session log file is /u01/app/grid_home/cfgtoollogs/opatchauto/opatchauto2018-08-08_02-14-54PM.log

The id for this session is 4VBV


Executing OPatch prereq operations to verify patch applicability on home /u01/app/grid_home


Executing OPatch prereq operations to verify patch applicability on home /u01/app/oracle/product/12.

Patch applicability verified successfully on home /u01/app/oracle/product/12.2.0/dbhome_1


Patch applicability verified successfully on home /u01/app/grid_home



Verifying SQL patch applicability on home /u01/app/oracle/product/12.2.0/dbhome_1

SQL patch applicability verified successfully on home /u01/app/oracle/product/12.2.0/dbhome_1



Preparing to bring down database service on home /u01/app/oracle/product/12.2.0/dbhome_1

Successfully prepared home /u01/app/oracle/product/12.2.0/dbhome_1 to bring down database service



Bringing down database service on home /u01/app/oracle/product/12.2.0/dbhome_1

Following database(s) and/or service(s) are stopped and will be restarted later during the session: 

Database service successfully brought down on home /u01/app/oracle/product/12.2.0/dbhome_1



Bringing down CRS service on home /u01/app/grid_home

Prepatch operation log file location: /u01/app/grid/crsdata/prod04/crsconfig/crspatch_prod04_2018-08

CRS service brought down successfully on home /u01/app/grid_home



Performing prepatch operation on home /u01/app/oracle/product/12.2.0/dbhome_1

Perpatch operation completed successfully on home /u01/app/oracle/product/12.2.0/dbhome_1



Start applying binary patch on home /u01/app/oracle/product/12.2.0/dbhome_1

Binary patch applied successfully on home /u01/app/oracle/product/12.2.0/dbhome_1



Performing postpatch operation on home /u01/app/oracle/product/12.2.0/dbhome_1

Postpatch operation completed successfully on home /u01/app/oracle/product/12.2.0/dbhome_1



Start applying binary patch on home /u01/app/grid_home




Binary patch applied successfully on home /u01/app/grid_home



Starting CRS service on home /u01/app/grid_home

Postpatch operation log file location: /u01/app/grid/crsdata/prod04/crsconfig/crspatch_prod04_2018-0

Failed to start CRS service on home /u01/app/grid_home


Execution of [GIStartupAction] patch action failed, check log for more details. Failures:

Patch Target : prod04->/u01/app/grid_home Type[crs]

Details: [

---------------------------Patching Failed---------------------------------

Command execution failed during patching in home: /u01/app/grid_home, host: prod04.

Command failed:  /u01/app/grid_home/perl/bin/perl -I/u01/app/grid_home/perl/lib -I/u01/app/grid_home /u01/app/grid_home/OPatch/auto/dbtmp/bootstrap_prod04/patchwork/crs/install/rootcrs.pl -postpatch -

Command failure output: 

Using configuration parameter file: /u01/app/grid_home/OPatch/auto/dbtmp/bootstrap_prod04/patchwork/

The log of current session can be found at:

  /u01/app/grid/crsdata/prod04/crsconfig/crspatch_prod04_2018-08-08_02-26-32PM.log

2018/08/08 14:26:45 CLSRSC-4015: Performing install or upgrade action for Oracle Trace File Analyzer

2018/08/08 14:27:37 CLSRSC-4003: Successfully patched Oracle Trace File Analyzer (TFA) Collector.

2018/08/08 14:27:42 CLSRSC-329: Replacing Clusterware entries in file 'oracle-ohasd.service'

2018/08/08 14:27:58 CLSRSC-180: An error occurred while executing the command '/u01/app/grid_home/bi


After fixing the cause of failure Run opatchauto resume


]

OPATCHAUTO-68061: The orchestration engine failed.

OPATCHAUTO-68061: The orchestration engine failed with return code 1

OPATCHAUTO-68061: Check the log for more details.

OPatchAuto failed.


OPatchauto session completed at Wed Aug  8 14:28:00 2018

Time taken to complete the session 13 minutes, 25 seconds


 opatchauto failed with error code 42


來自 “ ITPUB部落格 ” ，連結：http://blog.itpub.net/20747382/viewspace-2199398/，如需轉載，請註明出處，否則將追究法律責任。

相關文章