Aplicação Bundle Patch SuperCluster

 

A atividade é a aplicação de Bundle Patch JUL2014 – 11.2.0.4.9 no servidor Super Cluster .

Atividades:

– Estratégia de aplicação.

– Problemas encontrados.

1. Aplicação dos patches foi efetuada conforme documentação e seguindo os procedimentos descritos no documento de aplicação do patch conforme descrito abaixo:

Para aplicação do patch é necessário atualizar o OPach que de estar na versão 11.2.0.3.6 ou superior.

Obs: para check da versão do opatch utilizar o comando [ opatch version].
Criar o arquivo de response file (com.rsp) utilizando o comando [$ORACLE_HOME/OPatch/com/Bin/emocmrsp] será solicitado para informar e-mail (pode deixar em branco ) e se deseja continuar [ YES ] , [ NO ] informar [YES] será criado um arquivo ocm.rsp no diretório corrente , este arquivo é utilizado para aplicar o patch tanto para o Grid Infra como para o Banco de Dados e deve ter permissões de acesso e leitura.

# /u01/app/11.2.0.4/grid/OPatch/ocm/bin/emocmrsp

OCM Installation Response Generator 10.3.4.0.0 – Production

Copyright (c) 2005, 2010, Oracle and/or its affiliates. All rights reserved.

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:

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]:

Email address/User Name:

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.

• Verificar as informações do Inventário utilizando o comando [opatch lsinventory –detail –oh $ORACLE_HOME ]

Exemplo:

Oracle Interim Patch Installer version 11.2.0.3.6

Copyright (c) 2013, Oracle Corporation.  All rights reserved.

Oracle Home       : /u01/app/oracle/product/11.2.0.4/dbhome_1

Central Inventory : /u01/app/oraInventory

from           : /u01/app/oracle/product/11.2.0.4/dbhome_1/oraInst.loc

OPatch version    : 11.2.0.3.6

OUI version       : 11.2.0.4.0

Log file location : /u01/app/oracle/product/11.2.0.4/dbhome_1/cfgtoollogs/opatch/opatch2014-09-       08_20-48-03PM_1.log

Lsinventory Output file location :        /u01/app/oracle/product/11.2.0.4/dbhome_1/cfgtoollogs/opatch/lsinv/lsinventory2014-09-08_20-48-       03PM.txt

——————————————————————————–

Installed Top-level Products (1):

Oracle Database 11g                                                  11.2.0.4.0

There are 1 product(s) installed in this Oracle Home.

Interim patches (2) :

Patch  17984784     : applied on Tue Apr 15 15:08:32 BRT 2014

Unique Patch ID:  17080567

Patch description:  “CRS PATCH FOR EXADATA (JAN2014 – 11.2.0.4.3) : (17984784)”

Created on 10 Jan 2014, 03:57:42 hrs UTC

Bugs fixed:

16346413, 17065496, 16613232, 17551223, 14525998

Patch  17943261     : applied on Tue Apr 15 15:07:30 BRT 2014

Unique Patch ID:  17080567

Patch description:  “DATABASE PATCH FOR EXADATA (JAN2014 – 11.2.0.4.3) : (17943261)”

Created on 2 Jan 2014, 05:21:15 hrs UTC

Sub-patch  17741631; “DATABASE PATCH FOR EXADATA (DEC 2013 – 11.2.0.4.2) : (17741631)”

Sub-patch  17628006; “DATABASE PATCH FOR EXADATA (NOV 2013 – 11.2.0.4.1) : (17628006)”

Bugs fixed:

17288409, 13944971, 16450169, 17265217, 16180763, 16220077, 17465741

17614227, 16069901, 14010183, 16285691, 17726838, 13364795, 17088068

17612828, 17443671, 17080436, 17761775, 16721594, 16043574, 16837842

17446237, 16863422, 17332800, 13609098, 17610798, 17501491, 17239687

17468141, 17752121, 17602269, 16850630, 17346671, 17313525, 14852021

17783588, 17437634, 13866822, 12905058, 17546761

• Descompactar o patch do SuperCluster (JUL2014 – 11.2.0.4.9) em um diretorio
  Exemplo:

mkdir /u01/app/oracle/patches

cd /u01/app/oracle/patches

unzip p18840215_112040_SOLARIS64.zip

chown -R oracle:oinstall /u01/app/oracle/patches/18840215

 

• Check de conflito utilizando os comandos abaixo para o GI e BD o resultado deve ser passed.

      

       Para Grid Infrastructure Home, usuario do grid:

% $ORACLE_HOME/OPatch/opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir          <UNZIPPED_PATCH_LOCATION>/18840215/18825509         % $ORACLE_HOME/OPatch/opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir          <UNZIPPED_PATCH_LOCATION>/18840215/18522515         % $ORACLE_HOME/OPatch/opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir          <UNZIPPED_PATCH_LOCATION>/18840215/18522514

      

       Para Database home, usuario do oracle DB:

% $ORACLE_HOME/OPatch/opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir          <UNZIPPED_PATCH_LOCATION>/18840215/18825509         % $ORACLE_HOME/OPatch/opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir          <UNZIPPED_PATCH_LOCATION>/18840215/18522515/custom/server/18522515

• Check de SystemSpace abaixo para o GI e BD o resultado deve ser passed.

       Para Grid Infrastructure Home, usuario do Grid:

% $ORACLE_HOME/OPatch/opatch prereq CheckSystemSpace -phBaseDir          <UNZIPPED_PATCH_LOCATION>/18840215/18825509         % $ORACLE_HOME/OPatch/opatch prereq CheckSystemSpace -phBaseDir          <UNZIPPED_PATCH_LOCATION>/18840215/18522515         % $ORACLE_HOME/OPatch/opatch prereq CheckSystemSpace -phBaseDir          <UNZIPPED_PATCH_LOCATION>/18840215/18522514

Para Database home, usuario do oracle DB:

% $ORACLE_HOME/OPatch/opatch prereq CheckSystemSpace -phBaseDir          <UNZIPPED_PATCH_LOCATION>/18840215/18825509         % $ORACLE_HOME/OPatch/opatch prereq CheckSystemSpace -phBaseDir          <UNZIPPED_PATCH_LOCATION>/18840215/18522515/custom/server/18522515

• Instalação do Patch pode ser efetuado em um nó do cluster por vez , deve-se utilizar usuário root , exportar variáveis de ambiente do caminho do OPatch .

  Aplicar o path primeiro no GI conforme descrito abaixo:                    export PATH=$PATH:<GI_HOME>/OPatch         # opatch auto <PATH_TO_PATCH_DIRECTORY> -oh <GI_HOME> –ocmrf <$/ocm.rsp>

Observações:

Na documentação não é informado o parametro –ocmrf ( arquivo do response file ), quando é executado o comando opatch auto sem o parâmetro –ocmrf o aplicativo solicita para ser inserido o caminho do arquivo este procedimento causa problemas, o patch não é aplicado e o aplicativo não retorna erro ele retorna que o patch foi instalado com sucesso conforme visto abaixo: opatch auto /u01/patches/18840215 -oh /u01/app/11.2.0.4/gridExecuting /u01/app/11.2.0.4/grid/perl/bin/perl /u01/app/11.2.0.4/grid/OPatch/crs/patch11203.pl -patchdir /u01/patches -patchn 18840215 -oh /u01/app/11.2.0.4/grid -paramfile /u01/app/11.2.0.4/grid/crs/install/crsconfig_paramsThis is the main log file: /u01/app/11.2.0.4/grid/cfgtoollogs/opatchauto2014-09-07_13-11-15.logThis file will show your detected configuration and all the steps that opatchauto attempted to do on your system:/u01/app/11.2.0.4/grid/cfgtoollogs/opatchauto2014-09-07_13-11-15.report.log2014-09-07 13:11:15: Starting Clusterware Patch SetupUsing configuration parameter file: /u01/app/11.2.0.4/grid/crs/install/crsconfig_paramsOPatch is bundled with OCM, Enter the absolute OCM response file path:/u01/patches/ocm.rspStopping CRS…Stopped CRS successfullypatch /u01/patches/18840215/18825509 apply successful for home /u01/app/11.2.0.4/gridpatch /u01/patches/18840215/18522515 apply successful for home /u01/app/11.2.0.4/gridpatch /u01/patches/18840215/18522514 apply successful for home /u01/app/11.2.0.4/gridStarting CRS…Installing Trace File AnalyzerCRS-4123: Oracle High Availability Services has been started.opatch auto succeeded.Ao executar o comando opatch lsinventory vemos que o patch não foi instalado.

Aplicar o path no DB conforme descrito abaixo:         # opatch auto <PATH_TO_PATCH_DIRECTORY> -oh <GI_HOME> –ocmrf <$/ocm.rsp>           Executar do comando no Banco de Dados [$rdbms/admin/catbundle.sql exa apply ]com o usuário sys via        sqlplus após instalar o patch em todos os nós do cluster.  SQL> @rdbms/admin/catbundle.sql exa apply

Observações:

Aplicar o patch para o GI e DB em todos os nós do cluster e rodar o comando SQL> @rdbms/admin/catbundle.sql exa apply

• Verificar as informações do Inventário utilizando o comando [opatch lsinventory –detail –oh $ORACLE_HOME ]

Oracle Interim Patch Installer version 11.2.0.3.6 Copyright (c) 2013, Oracle Corporation. All rights reserved.

Oracle Home       : /u01/app/oracle/product/11.2.0.4/dbhome_1

Central Inventory : /u01/app/oraInventory

from           : /u01/app/oracle/product/11.2.0.4/dbhome_1/oraInst.loc

OPatch version   : 11.2.0.3.6

OUI version       : 11.2.0.4.0

Log file location : /u01/app/oracle/product/11.2.0.4/dbhome_1/cfgtoollogs/opatch/opatch2014-09-       09_10-29-31AM_1.log

Lsinventory Output file location :        /u01/app/oracle/product/11.2.0.4/dbhome_1/cfgtoollogs/opatch/lsinv/lsinventory2014-09-09_10-29-       31AM.txt

——————————————————————————–

Installed Top-level Products (1):

Oracle Database 11g                                                 11.2.0.4.0

There are 1 product(s) installed in this Oracle Home.

Interim patches (2) :

Patch 18522515     : applied on Tue Sep 09 10:22:16 BRT 2014

Unique Patch ID: 17743109

Patch description: “OCW Patch Set Update : 11.2.0.4.3 (18522515)”

Created on 23 Jun 2014, 10:12:35 hrs UTC

Bugs fixed:

18024089, 18428146, 18328800, 18187697, 14525998, 18352845, 17391726

17750548, 17387214, 18414137, 17001914, 17927970, 16346413, 17551223

15832129, 17305100, 18272135, 18180541, 17985714, 17292250, 17378618

16206997, 17500165, 16876500, 16429265, 17065496, 18343490, 18848125

18336452, 13991403, 16613232, 17955615, 14693336, 17273003, 17273020

17238586, 17089344, 12928658, 18226143, 17531342, 17172091, 18229842

17155238, 17159489, 16543190, 17039197, 17483479, 17947785, 16317771

10052729, 17481314, 18199185, 17405302, 18399991

Patch 18825509     : applied on Tue Sep 09 10:20:13 BRT 2014

Unique Patch ID: 17743109

Patch description: “DATABASE PATCH FOR EXADATA (JUL2014 – 11.2.0.4.9) : (18825509)”

Created on 4 Jul 2014, 11:19:59 hrs UTC Sub-patch 18642122; “DATABASE PATCH FOR EXADATA        (JUN2014 – 11.2.0.4.8) : (18642122)”

Sub-patch 18552960; “DATABASE PATCH FOR EXADATA (MAY2014 – 11.2.0.4.7) : (18552960)”

Sub-patch 18293775; “DATABASE PATCH FOR EXADATA (APR2014 – 11.2.0.4.6) : (18293775)”

Sub-patch 18136151; “DATABASE PATCH FOR EXADATA (MAR2014 – 11.2.0.4.5) : (18136151)”

Sub-patch 18006299; “DATABASE PATCH FOR EXADATA (FEB2014 – 11.2.0.4.4) : (18006299)”

Sub-patch 17943261; “DATABASE PATCH FOR EXADATA (JAN2014 – 11.2.0.4.3) : (17943261)”

Sub-patch 17741631; “DATABASE PATCH FOR EXADATA (DEC 2013 – 11.2.0.4.2) : (17741631)”

Sub-patch 17628006; “DATABASE PATCH FOR EXADATA (NOV 2013 – 11.2.0.4.1) : (17628006)”

Bugs fixed:

17288409, 16188701, 16930924, 17811429, 17205719, 17501296, 17754782

17726838, 13364795, 17311728, 18418934, 17441661, 17284817, 16477664

13645875, 14193240, 16992075, 16542886, 17446237, 14015842, 14565184

18324129, 17071721, 18317132, 17610798, 17375354, 17397545, 17265093

18230522, 17982555, 16360112, 17235750, 13866822, 17478514, 12905058

14338435, 13944971, 17811789, 16929165, 12747740, 17230905, 17546973

14054676, 17088068, 16885125, 18780342, 17016369, 17042658, 14602788

18686405, 17158214, 14657740, 17775506, 17332800, 13951456, 16315398

18483595, 18744139, 17186905, 16850630, 18767554, 17561405, 17437634

19049453, 17883081, 17296856, 14333054, 18277454, 17232014, 17249711

16855292, 10136473, 17179434, 17997507, 17865671, 18554871, 17635021

17588480, 18304997, 17551709, 17344412, 18681862, 16306373, 18139690

13609098, 17501491, 17239687, 17752121, 17602269, 17313525, 18818847

18025431, 17600719, 17571306, 18094246, 17011832, 17165204, 16785708

17174582, 17477958, 16180763, 17465741, 18522509, 17323222, 16875449

16524926, 16980342, 14822091, 17596908, 17811438, 17811447, 18031668

16912439, 14373152, 18077632, 18061914, 17545847, 17082359, 17614134

17341326, 14034426, 18339044, 17716305, 18133214, 17752995, 16392068

17209410, 17767676, 12608451, 17205005, 18384391, 17614227, 17040764

17381384, 14084247, 17389192, 17006570, 17612828, 17721717, 13853126

18203837, 17390431, 18456874, 16043574, 16863422, 18325460, 17402822

14486653, 17468141, 17786518, 14460384, 18226122, 18244962, 18203838

16956380, 17478145, 17394950, 18619917, 17027426, 14000767, 16268425

18247991, 14458214, 17839474, 18436307, 12716670, 16618055, 17265217

13498382, 17786278, 17227277, 17734862, 16042673, 16314254, 17952061

17443671, 18154779, 16228604, 18783969, 16837842, 17393683, 18247351

13073613, 15861775, 18135678, 18614015, 16399083, 18191542, 18192858

18018515, 17082612, 16472716, 18830412, 17050888, 17325413, 14010183

18832544, 17036973, 16613964, 17080436, 17761775, 16721594, 15979965

13651346, 18203835, 17297939, 17811456, 16731148, 18205490, 14133975

17385178, 16450169, 17357979, 17655634, 10194190, 18160822, 17892268

17648596, 16220077, 16069901, 11733603, 16285691, 18180390, 17393915

18096714, 17238511, 13816053, 13877071, 14285317, 17622427, 16943711

17346671, 18996843, 14852021, 17783588, 16618694, 17672719, 17546761

Rac system comprising of multiple nodes

Local node = osc01r5z9db01cn1-client

Remote node = osc02r5z10db03cn3-client

• Opções adicionais para aplicação do Patch e Rollback do Patch.

  Aplicação do patch no GI home e todos Oracle RAC database homes:

# opatch auto <UNZIPPED_PATCH_LOCATION> -ocmrf <ocm response file>

Para rollback do patch para o GI home e todos Oracle RAC database home:

# opatch auto <UNZIPPED_PATCH_LOCATION> -rollback -ocmrf <ocm response file>

Para rollback do patch para o GI home:

# opatch auto <UNZIPPED_PATCH_LOCATION> -oh <path to GI home> -rollback -ocmrf <ocm                                    response file>

Para rollback do patch para o Oracle RAC database home:

# opatch auto <UNZIPPED_PATCH_LOCATION> -oh <path to RAC database home> -rollback -ocmrf                   <ocm response file>