• Nenhum resultado encontrado

INSTALANDO PATCH NO ORACLE RAC 11GR2 COM ZERO DOWNTIME. Renan Parisotto

N/A
N/A
Protected

Academic year: 2021

Share "INSTALANDO PATCH NO ORACLE RAC 11GR2 COM ZERO DOWNTIME. Renan Parisotto"

Copied!
22
0
0

Texto

(1)

INSTALANDO PATCH

NO ORACLE RAC 11GR2

COM ZERO DOWNTIME

Renan Parisotto [email protected]

(2)

DESCRIÇÃO

Neste artigo falaremos sobre o processo de aplicação

de Patch no Oracle RAC 11gR2 com zero downtime

(Rolling Patch) que pode ser executado em ambientes

críticos onde a infraestrutura deve permanecer on-line.

Antes de iniciarmos vamos explicar a diferença entre

PSU (Patch Set Update), CPU (Critical Patch Update) e

SPU Security Patch Updates.

Correções de erros críticos com abertura de chamados

no MOS (My Oracle Support) são caracterizados como

CPU e SPU.

O PSU é um pacote de correções que a Oracle

disponibiliza trimestralmente com correções críticas de

segurança; este pacote é composto pelo CPU e SPU. No

exemplo abaixo vamos utilizar o PSU de Julho/2016.

Atualmente há 3 métodos diferentes de instalação de

patch em ambiente Oracle RAC, listados a seguir.

(3)

Neste modo, aplica-se o patch no servidor local em primeiro

lugar, depois a instalação é iniciada nos servidores remotos

e finalmente atualiza o inventário. Para este caso, o ambiente

Oracle RAC estará totalmente indisponível.

• Shutdown das instances de todos os servidores;

• Instalação do patch em todos os homes de todos os

servidores;

• Startup de todas as instances de todos os servidores.

INSTALANDO O PATCH COMO ÚNICA

INSTÂNCIA (ALL-NODE PATCH)

(4)

Neste caso, baixe o servidor primário; esse servidor será o primeiro a

receber a aplicação do patch. As conexões serão direcionadas para

o servidor secundário. Após a instalação do patch, inicie o Oracle no

servidor primário. As conexões serão balanceadas e direcionadas para o

servidor primário. Em seguida baixe o servidor secundário; esse servidor

será o segundo a receber a instalação do patch, aplica-se o patch no

servidor secundário e atualize o inventário. O tempo de inatividade que

aconteceria entre o desligamento do servidor secundário e a inicialização

do servidor primário.

• Shutdown das instances do servidor 1;

• Instalação no home do servidor 1;

• Shutdown das instances do servidor 2;

• Instalação no home do servidor 2;

• Shutdown das instances do servidor 3;

• Startup das instances nos servidores 1 e 2;

• Instalação no home do servidor 3;

• Startup das instances no servidor 3.

INSTALANDO O PATCH COM MÍNIMO

DOWN-TIME (MIN. DOWNTIME PATCH)

(5)

Com este método, não há indisponibilidade. Cada servidor será

atualizado com o patch individualmente enquanto todos os outros

servidores estarão funcionando.

Neste caso, move-se as conexões para o servidor secundário, esse

servidor será o segundo a receber a aplicação do patch.

Aplica-se o patch no servidor primário, move-se as conexões do servidor

secundário, aplica-se o patch no servidor secundário e atualizamos o

inventário.

É recomendado que após a instalação do ambiente Oracle RAC seja

aplicado o último patch disponível.

• Shutdown das instances do servidor 1;

• Instalação no home do servidor 1;

• Startup das instances no servidor 1;

• Shutdown das instances do servidor 2;

• Instalação no home do servidor 2;

• Startup das instances no servidor 2.

No link abaixo você poderá encontrar mais informações sobre os

patchs.

http://www.oracle.com/technetwork/topics/security/alerts-086861.html

INSTALANDO O PATCH COM ZERO

DOWNTIME (ROLLING PATCH)

(6)

Agora vamos demonstrar como instalar o PSU com zero downtime. O

primeiro passo é atualizar o OPatch que está localizado no ORACLE_

HOME de todos os servidores do cluster.

No exemplo abaixo, estamos utilizando a versão 11.2.0.3.12 do OPatch

Temos conexão na instance FOX1 do servidor RAC1, neste caso vamos

instalar o PSU na instance FOX2 do servidor RAC2.

Estou conectado na instance FOX1.

[oracle@rac1 ~]$ opatch version OPatch Version: 11.2.0.3.12 OPatch succeeded.

[oracle@rac2 ~]$ opatch version OPatch Version: 11.2.0.3.12 OPatch succeeded.

[oracle@rac1 ~]$ opatch version OPatch Version: 11.2.0.3.12 OPatch succeeded.

[oracle@rac2 ~]$ opatch version OPatch Version: 11.2.0.3.12 OPatch succeeded.

[oracle@rac1 ~]$ opatch version OPatch Version: 11.2.0.3.12 OPatch succeeded.

[oracle@rac2 ~]$ opatch version OPatch Version: 11.2.0.3.12 OPatch succeeded.

@RAC> select instance_name from v$instance; INSTANCE_NAME

(7)

---Baixando o CRS no servidor RAC2.

[oracle@rac1 ~]$ opatch version OPatch Version: 11.2.0.3.12 OPatch succeeded.

[oracle@rac2 ~]$ opatch version OPatch Version: 11.2.0.3.12 OPatch succeeded.

[root@rac2 ~]# crsctl stop crs

CRS-2791: Starting shutdown of Oracle High Availability Services-managed resources on ‘rac2’

CRS-2673: Attempting to stop ‘ora.crsd’ on ‘rac2’

CRS-2790: Starting shutdown of Cluster Ready Services-managed resources on ‘rac2’ CRS-2673: Attempting to stop ‘ora.LISTENER.lsnr’ on ‘rac2’

CRS-2673: Attempting to stop ‘ora.fox.acesso.svc’ on ‘rac2’

CRS-2673: Attempting to stop ‘ora.LISTENER_SCAN1.lsnr’ on ‘rac2’ CRS-2677: Stop of ‘ora.LISTENER_SCAN1.lsnr’ on ‘rac2’ succeeded CRS-2673: Attempting to stop ‘ora.scan1.vip’ on ‘rac2’

CRS-2677: Stop of ‘ora.LISTENER.lsnr’ on ‘rac2’ succeeded CRS-2677: Stop of ‘ora.scan1.vip’ on ‘rac2’ succeeded CRS-2672: Attempting to start ‘ora.scan1.vip’ on ‘rac1’ CRS-2676: Start of ‘ora.scan1.vip’ on ‘rac1’ succeeded

CRS-2672: Attempting to start ‘ora.LISTENER_SCAN1.lsnr’ on ‘rac1’ CRS-2677: Stop of ‘ora.fox.acesso.svc’ on ‘rac2’ succeeded

CRS-2673: Attempting to stop ‘ora.rac2.vip’ on ‘rac2’ CRS-2673: Attempting to stop ‘ora.OCR.dg’ on ‘rac2’

CRS-2673: Attempting to stop ‘ora.registry.acfs’ on ‘rac2’ CRS-2673: Attempting to stop ‘ora.fox.db’ on ‘rac2’

CRS-2677: Stop of ‘ora.rac2.vip’ on ‘rac2’ succeeded CRS-2672: Attempting to start ‘ora.rac2.vip’ on ‘rac1’ CRS-2676: Start of ‘ora.rac2.vip’ on ‘rac1’ succeeded

CRS-2676: Start of ‘ora.LISTENER_SCAN1.lsnr’ on ‘rac1’ succeeded CRS-2677: Stop of ‘ora.fox.db’ on ‘rac2’ succeeded

CRS-2673: Attempting to stop ‘ora.DATA.dg’ on ‘rac2’ CRS-2673: Attempting to stop ‘ora.TESTE.dg’ on ‘rac2’ CRS-2677: Stop of ‘ora.registry.acfs’ on ‘rac2’ succeeded CRS-2677: Stop of ‘ora.OCR.dg’ on ‘rac2’ succeeded

CRS-2677: Stop of ‘ora.TESTE.dg’ on ‘rac2’ succeeded CRS-2677: Stop of ‘ora.DATA.dg’ on ‘rac2’ succeeded

(8)

[oracle@rac1 ~]$ opatch version OPatch Version: 11.2.0.3.12 OPatch succeeded.

[oracle@rac2 ~]$ opatch version OPatch Version: 11.2.0.3.12 OPatch succeeded.

CRS-2673: Attempting to stop ‘ora.asm’ on ‘rac2’ CRS-2677: Stop of ‘ora.asm’ on ‘rac2’ succeeded CRS-2673: Attempting to stop ‘ora.ons’ on ‘rac2’ CRS-2677: Stop of ‘ora.ons’ on ‘rac2’ succeeded

CRS-2673: Attempting to stop ‘ora.net1.network’ on ‘rac2’ CRS-2677: Stop of ‘ora.net1.network’ on ‘rac2’ succeeded

CRS-2792: Shutdown of Cluster Ready Services-managed resources on ‘rac2’ has com-pleted

CRS-2677: Stop of ‘ora.crsd’ on ‘rac2’ succeeded CRS-2673: Attempting to stop ‘ora.ctssd’ on ‘rac2’ CRS-2673: Attempting to stop ‘ora.evmd’ on ‘rac2’ CRS-2673: Attempting to stop ‘ora.asm’ on ‘rac2’ CRS-2673: Attempting to stop ‘ora.mdnsd’ on ‘rac2’

CRS-2673: Attempting to stop ‘ora.drivers.acfs’ on ‘rac2’ CRS-2677: Stop of ‘ora.ctssd’ on ‘rac2’ succeeded

CRS-2677: Stop of ‘ora.evmd’ on ‘rac2’ succeeded CRS-2677: Stop of ‘ora.mdnsd’ on ‘rac2’ succeeded

CRS-2677: Stop of ‘ora.drivers.acfs’ on ‘rac2’ succeeded CRS-2677: Stop of ‘ora.asm’ on ‘rac2’ succeeded

CRS-2673: Attempting to stop ‘ora.cluster_interconnect.haip’ on ‘rac2’ CRS-2677: Stop of ‘ora.cluster_interconnect.haip’ on ‘rac2’ succeeded CRS-2673: Attempting to stop ‘ora.cssd’ on ‘rac2’

CRS-2677: Stop of ‘ora.cssd’ on ‘rac2’ succeeded CRS-2673: Attempting to stop ‘ora.crf’ on ‘rac2’ CRS-2677: Stop of ‘ora.crf’ on ‘rac2’ succeeded CRS-2673: Attempting to stop ‘ora.gipcd’ on ‘rac2’ CRS-2677: Stop of ‘ora.gipcd’ on ‘rac2’ succeeded CRS-2673: Attempting to stop ‘ora.gpnpd’ on ‘rac2’ CRS-2677: Stop of ‘ora.gpnpd’ on ‘rac2’ succeeded

CRS-2793: Shutdown of Oracle High Availability Services-managed resources on ‘rac2’ has completed

(9)

Observe que a conexão na instance FOX1 do servidor RAC1 permanece ativa.

Instalando o PSU de Julho/2016 no servidor RAC2.

[oracle@rac1 ~]$ opatch version OPatch Version: 11.2.0.3.12 OPatch succeeded.

[oracle@rac2 ~]$ opatch version OPatch Version: 11.2.0.3.12 OPatch succeeded.

[oracle@rac1 ~]$ opatch version OPatch Version: 11.2.0.3.12 OPatch succeeded.

[oracle@rac2 ~]$ opatch version OPatch Version: 11.2.0.3.12 OPatch succeeded.

@RAC> select instance_name from v$instance; INSTANCE_NAME

---FOX1

[oracle@rac2 22502456]$ opatch apply

Oracle Interim Patch Installer version 11.2.0.3.12

Copyright (c) 2016, Oracle Corporation. All rights reserved. Oracle Home : /u01/app/oracle/product/11.2.0/db_1

Central Inventory : /u01/app/oraInventory

from : /u01/app/oracle/product/11.2.0/db_1/oraInst.loc OPatch version : 11.2.0.3.12

OUI version : 11.2.0.4.0

Log file location : /u01/app/oracle/product/11.2.0/db_1/cfgtoollogs/opatch/opatc Verifying environment and performing prerequisite checks...

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

y

User Responded with: Y All checks passed.

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.

(10)

[oracle@rac1 ~]$ opatch version OPatch Version: 11.2.0.3.12 OPatch succeeded.

[oracle@rac2 ~]$ opatch version OPatch Version: 11.2.0.3.12 OPatch succeeded.

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]: Y This node is part of an Oracle Real Application Cluster.

Remote nodes: ‘rac1’ Local node: ‘rac2’

Please shutdown Oracle instances running out of this ORACLE_HOME on the local sys-tem.

(Oracle Home = ‘/u01/app/oracle/product/11.2.0/db_1’) Is the local system ready for patching? [y|n]

y

User Responded with: Y Backing up files...

Applying sub-patch ‘21948347’ to OH ‘/u01/app/oracle/product/11.2.0/db_1’

ApplySession: Optional component(s) [ oracle.tfa, 11.2.0.4.0 ] not present in the Oracle Home or a higher version is found.

Patching component oracle.sysman.agent, 10.2.0.4.5... Patching component oracle.ovm, 11.2.0.4.0...

Patching component oracle.xdk, 11.2.0.4.0... Patching component oracle.rdbms, 11.2.0.4.0...

Patching component oracle.nlsrtl.rsf, 11.2.0.4.0...

Patching component oracle.xdk.parser.java, 11.2.0.4.0... Patching component oracle.sysman.console.db, 11.2.0.4.0...

(11)

OPatch succeeded.

[oracle@rac2 ~]$ opatch version OPatch Version: 11.2.0.3.12 OPatch succeeded.

Patching component oracle.xdk.rsf, 11.2.0.4.0... Patching component oracle.rdbms.rsf, 11.2.0.4.0...

Patching component oracle.sysman.oms.core, 10.2.0.4.5...

Applying sub-patch ‘22502456’ to OH ‘/u01/app/oracle/product/11.2.0/db_1’

ApplySession: Optional component(s) [ oracle.tfa, 11.2.0.4.0 ] not present in the Oracle Home or a higher version is found.

Patching component oracle.precomp.common, 11.2.0.4.0... Patching component oracle.oraolap.dbscripts, 11.2.0.4.0... Patching component oracle.rdbms.olap, 11.2.0.4.0...

Patching component oracle.oraolap, 11.2.0.4.0... Patching component oracle.rdbms.rsf, 11.2.0.4.0... Patching component oracle.rdbms.rman, 11.2.0.4.0... Patching component oracle.rdbms, 11.2.0.4.0...

Patching component oracle.rdbms.dbscripts, 11.2.0.4.0... Patching in rolling mode.

The node ‘rac1’ will be patched next.

Please shutdown Oracle instances running out of this ORACLE_HOME on ‘rac1’. (Oracle Home = ‘/u01/app/oracle/product/11.2.0/db_1’)

(12)

[oracle@rac1 ~]$ opatch version OPatch Version: 11.2.0.3.12 OPatch succeeded.

[oracle@rac2 ~]$ opatch version OPatch Version: 11.2.0.3.12 OPatch succeeded.

[oracle@rac1 ~]$ opatch version OPatch Version: 11.2.0.3.12 OPatch succeeded.

[oracle@rac2 ~]$ opatch version OPatch Version: 11.2.0.3.12 OPatch succeeded.

Is the node ready for patching? [y|n] N

User Responded with: N NApply exits on request

You may exit the patching session and patch remaining nodes later from an un-patched node. Do you want to continue?

Do you want to proceed? [y|n] N

Patching aborted on node “rac1”, no remaining nodes.

UtilSession failed: Patching aborted on node “rac1”, no remaining nodes. Log file location: /u01/app/oracle/product/11.2.0/db_1/cfgtoollogs/opatch/ opatch2016-08-12_14-02-40PM_1.log

OPatch failed with error code 73

[root@rac1 ~]# crsctl stop crs

CRS-2791: Starting shutdown of Oracle High Availability Services-managed resources on ‘rac1’

CRS-2673: Attempting to stop ‘ora.crsd’ on ‘rac1’

CRS-2790: Starting shutdown of Cluster Ready Services-managed resources on ‘rac1’ CRS-2673: Attempting to stop ‘ora.LISTENER.lsnr’ on ‘rac1’

CRS-2673: Attempting to stop ‘ora.fox.acesso.svc’ on ‘rac1’

CRS-2673: Attempting to stop ‘ora.LISTENER_SCAN1.lsnr’ on ‘rac1’ CRS-2677: Stop of ‘ora.LISTENER_SCAN1.lsnr’ on ‘rac1’ succeeded CRS-2673: Attempting to stop ‘ora.scan1.vip’ on ‘rac1’

CRS-2677: Stop of ‘ora.LISTENER.lsnr’ on ‘rac1’ succeeded CRS-2677: Stop of ‘ora.scan1.vip’ on ‘rac1’ succeeded CRS-2672: Attempting to start ‘ora.scan1.vip’ on ‘rac1’ CRS-2676: Start of ‘ora.scan1.vip’ on ‘rac1’ succeeded

(13)

[oracle@rac2 ~]$ opatch version OPatch Version: 11.2.0.3.12 OPatch succeeded.

CRS-2677: Stop of ‘ora.fox.acesso.svc’ on ‘rac1’ succeeded CRS-2673: Attempting to stop ‘ora.rac1.vip’ on ‘rac1’

CRS-2673: Attempting to stop ‘ora.OCR.dg’ on ‘rac1’

CRS-2673: Attempting to stop ‘ora.registry.acfs’ on ‘rac1’ CRS-2673: Attempting to stop ‘ora.fox.db’ on ‘rac1’

CRS-2677: Stop of ‘ora.rac1.vip’ on ‘rac1’ succeeded CRS-2672: Attempting to start ‘ora.rac1.vip’ on ‘rac1’ CRS-2676: Start of ‘ora.rac1.vip’ on ‘rac1’ succeeded

CRS-2676: Start of ‘ora.LISTENER_SCAN1.lsnr’ on ‘rac1’ succeeded CRS-2677: Stop of ‘ora.fox.db’ on ‘rac1’ succeeded

CRS-2673: Attempting to stop ‘ora.DATA.dg’ on ‘rac1’ CRS-2673: Attempting to stop ‘ora.TESTE.dg’ on ‘rac1’ CRS-2677: Stop of ‘ora.registry.acfs’ on ‘rac1’ succeeded CRS-2677: Stop of ‘ora.OCR.dg’ on ‘rac1’ succeeded

CRS-2677: Stop of ‘ora.TESTE.dg’ on ‘rac1’ succeeded CRS-2677: Stop of ‘ora.DATA.dg’ on ‘rac1’ succeeded CRS-2673: Attempting to stop ‘ora.asm’ on ‘rac1’ CRS-2677: Stop of ‘ora.asm’ on ‘rac1’ succeeded CRS-2673: Attempting to stop ‘ora.ons’ on ‘rac1’ CRS-2677: Stop of ‘ora.ons’ on ‘rac1’ succeeded

CRS-2673: Attempting to stop ‘ora.net1.network’ on ‘rac1’ CRS-2677: Stop of ‘ora.net1.network’ on ‘rac1’ succeeded

CRS-2792: Shutdown of Cluster Ready Services-managed resources on ‘rac1’ has com-pleted

CRS-2677: Stop of ‘ora.crsd’ on ‘rac1’ succeeded CRS-2673: Attempting to stop ‘ora.ctssd’ on ‘rac1’ CRS-2673: Attempting to stop ‘ora.evmd’ on ‘rac1’ CRS-2673: Attempting to stop ‘ora.asm’ on ‘rac1’ CRS-2673: Attempting to stop ‘ora.mdnsd’ on ‘rac1’

CRS-2673: Attempting to stop ‘ora.drivers.acfs’ on ‘rac1’ CRS-2677: Stop of ‘ora.ctssd’ on ‘rac1’ succeeded

CRS-2677: Stop of ‘ora.evmd’ on ‘rac1’ succeeded CRS-2677: Stop of ‘ora.mdnsd’ on ‘rac1’ succeeded

(14)

[oracle@rac1 ~]$ opatch version OPatch Version: 11.2.0.3.12 OPatch succeeded.

[oracle@rac2 ~]$ opatch version OPatch Version: 11.2.0.3.12 OPatch succeeded.

CRS-2677: Stop of ‘ora.asm’ on ‘rac1’ succeeded

CRS-2673: Attempting to stop ‘ora.cluster_interconnect.haip’ on ‘rac1’ CRS-2677: Stop of ‘ora.cluster_interconnect.haip’ on ‘rac1’ succeeded CRS-2673: Attempting to stop ‘ora.cssd’ on ‘rac1’

CRS-2677: Stop of ‘ora.cssd’ on ‘rac1’ succeeded CRS-2673: Attempting to stop ‘ora.crf’ on ‘rac1’ CRS-2677: Stop of ‘ora.crf’ on ‘rac1’ succeeded CRS-2673: Attempting to stop ‘ora.gipcd’ on ‘rac1’ CRS-2677: Stop of ‘ora.gipcd’ on ‘rac1’ succeeded CRS-2673: Attempting to stop ‘ora.gpnpd’ on ‘rac1’ CRS-2677: Stop of ‘ora.gpnpd’ on ‘rac1’ succeeded

CRS-2793: Shutdown of Oracle High Availability Services-managed resources on ‘rac1’ has completed

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

[oracle@rac1 ~]$ opatch version OPatch Version: 11.2.0.3.12 OPatch succeeded.

[oracle@rac2 ~]$ opatch version OPatch Version: 11.2.0.3.12 OPatch succeeded.

DBACORP@rac> select instance_name from v$instance; INSTANCE_NAME

---FOX1

DBACORP@rac> select instance_name from v$instance; INSTANCE_NAME

---FOX2

Observe abaixo que a conexão que estava na instance FOX1 passou para instance

FOX2 sem perder a conexão, isso acontece pois estamos utilizando serviço do

Server Control (SRVCTL).

(15)

Instalando o PSU de Julho/2016 no servidor RAC1.

[oracle@rac1 ~]$ opatch version OPatch Version: 11.2.0.3.12 OPatch succeeded.

[oracle@rac2 ~]$ opatch version OPatch Version: 11.2.0.3.12 OPatch succeeded.

[oracle@rac1 22502456]$ opatch apply

Oracle Interim Patch Installer version 11.2.0.3.12

Copyright (c) 2016, Oracle Corporation. All rights reserved. Oracle Home : /u01/app/oracle/product/11.2.0/db_1

Central Inventory : /u01/app/oraInventory

from : /u01/app/oracle/product/11.2.0/db_1/oraInst.loc OPatch version : 11.2.0.3.12

OUI version : 11.2.0.4.0

Log file location : /u01/app/oracle/product/11.2.0/db_1/cfgtoollogs/opatch/opatc Verifying environment and performing prerequisite checks...

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

y

User Responded with: Y All checks passed.

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]: Y This node is part of an Oracle Real Application Cluster.

Remote nodes: ‘rac1’ Local node: ‘rac1’

(16)

sys-[oracle@rac1 ~]$ opatch version OPatch Version: 11.2.0.3.12 OPatch succeeded.

[oracle@rac2 ~]$ opatch version OPatch Version: 11.2.0.3.12 OPatch succeeded.

tem.

(Oracle Home = ‘/u01/app/oracle/product/11.2.0/db_1’) Is the local system ready for patching? [y|n]

y

User Responded with: Y Backing up files...

Applying sub-patch ‘21948347’ to OH ‘/u01/app/oracle/product/11.2.0/db_1’

ApplySession: Optional component(s) [ oracle.tfa, 11.2.0.4.0 ] not present in the Oracle Home or a higher version is found.

Patching component oracle.sysman.agent, 10.2.0.4.5... Patching component oracle.ovm, 11.2.0.4.0...

Patching component oracle.xdk, 11.2.0.4.0... Patching component oracle.rdbms, 11.2.0.4.0...

Patching component oracle.nlsrtl.rsf, 11.2.0.4.0...

Patching component oracle.xdk.parser.java, 11.2.0.4.0... Patching component oracle.sysman.console.db, 11.2.0.4.0... Patching component oracle.xdk.rsf, 11.2.0.4.0...

Patching component oracle.rdbms.rsf, 11.2.0.4.0...

Patching component oracle.sysman.oms.core, 10.2.0.4.5...

Applying sub-patch ‘22502456’ to OH ‘/u01/app/oracle/product/11.2.0/db_1’

ApplySession: Optional component(s) [ oracle.tfa, 11.2.0.4.0 ] not present in the Oracle Home or a higher version is found.

(17)

OPatch succeeded.

[oracle@rac2 ~]$ opatch version OPatch Version: 11.2.0.3.12 OPatch succeeded.

Patching component oracle.oraolap.dbscripts, 11.2.0.4.0... Patching component oracle.rdbms.olap, 11.2.0.4.0...

Patching component oracle.oraolap, 11.2.0.4.0... Patching component oracle.rdbms.rsf, 11.2.0.4.0... Patching component oracle.rdbms.rman, 11.2.0.4.0... Patching component oracle.rdbms, 11.2.0.4.0...

Patching component oracle.rdbms.dbscripts, 11.2.0.4.0... Patching in rolling mode.

The node ‘rac1’ will be patched next.

Please shutdown Oracle instances running out of this ORACLE_HOME on ‘rac1’. (Oracle Home = ‘/u01/app/oracle/product/11.2.0/db_1’)

Is the node ready for patching? [y|n] N

User Responded with: N NApply exits on request

You may exit the patching session and patch remaining nodes later from an un-patched node. Do you want to continue?

Do you want to proceed? [y|n] N

Patching aborted on node “rac1”, no remaining nodes.

(18)

[oracle@rac1 ~]$ opatch version OPatch Version: 11.2.0.3.12 OPatch succeeded.

[oracle@rac2 ~]$ opatch version OPatch Version: 11.2.0.3.12 OPatch succeeded.

Log file location: /u01/app/oracle/product/11.2.0/db_1/cfgtoollogs/opatch/ opatch2016-08-12_14-02-40PM_1.log

OPatch failed with error code 73

Instalando o PSU de Julho/2016 no servidor RAC1.

[oracle@rac1 ~]$ opatch version OPatch Version: 11.2.0.3.12 OPatch succeeded.

[oracle@rac2 ~]$ opatch version OPatch Version: 11.2.0.3.12 OPatch succeeded.

ACTION_TIME ACTION VERSION ID COMMENTS --- --- ---08/04/16 16:30:38,735265 APPLY 11.2.0.4 8 PSU 11.2.0.4.8 12/08/16 15:30:10,869899 APPLY 11.2.0.4 160419 PSU 11.2.0.4.160419

(19)

CONCLUSÃO

Cada método de instalação do PSU tem as suas

particularidades, cabe ao DBA juntamente com

a área de negócio avaliar a melhor estratégia de

atualização dos binários do Oracle.

(20)

REFERÊNCIAS E METALINK

(21)

serviços que oferecemos.

Temos soluções sob medida para os mais diversos

projetos em banco de dados, infraestrutura e cloud

computing.

Oferecemos serviços como suporte 24x7x365,

alocação de profissionais, venda de licenças,

monitoração proativa, alta disponibilidade e

sustentação.

Tudo isso com equipes certificadas de DBAs e

de infraestrutura, prontas para atender todos os

segmentos e tamanhos de empresas.

E para garantir ainda mais a qualidade, a DBACorp

é parceira dos principais players do mercado, como

Oracle, Microsoft, Amazon Web Services e WMware.

(22)

São Paulo - SP

R. Samuel Morse, 74, Conj. 21 Brooklin Novo - CEP 04576-060 +55 11 2348-4699

Rio de Janeiro - RJ

Av. Rio Branco, 1 - 12º andar Centro - CEP 20090-003 +55 21 2588-8150

REDES SOCIAIS

Renan Parisotto

Referências

Documentos relacionados

De ordem do Excelentíssimo Senhor Presidente do Tribunal de Contas do Estado do Pará, Conselheiro CIPRIANO SABINO DE OLIVEIRA JUNIOR, em cumprindo ao disposto no

Em nosso parecer, as Demonstrações Financeiras apresentadas a seguir dão, em conformidade com os requisitos legais e regulamentares luxemburgueses, de forma verdadeira e justa,

Gardener Diarmuid Gavin and the Harrods team of illustrators, landscape architects and plantspeople plan schemes for gardens as well as designs for city roof terraces,

À Assembleia Geral, órgão máximo da sociedade que representa a universalidade dos Acionistas, compete em especial: eleger e destituir a sua própria Mesa, bem como os membros

Considerando que esta percepção (conjuntos Fuzzy) se acomoda com maior propriedade para os estudos pretendidos, passamos a descrever as etapas necessárias para que possam inscrever

DEVEDOR CREDOR DEBITO CREDITO DEVEDOR CREDOR TRANSPORTE .... SALDO DA GERÊNCIA ANTERIOR MOVIMENTO ANUAL SALDO PARA A GERÊNCIA SEGUINTE COD. CONTA TERCEIRO DESIGNACAO.. DEVEDOR

PROCEDIMENTOS DE LAVAGEM, ARMAZENAMENTO, DEVOLUÇÃO, TRANSPORTE E DESTINAÇÃO DE EMBALAGENS VAZIAS E RESTOS DE PRODUTOS IMPRÓPRIOS PARA UTIILIZAÇÃO OU EM

os servidores que ingressarem no serviço público a partir da sua instituição, os benefícios previdenciários concedidos pelos regimes próprios dos servidores ficarão