{"id":163,"date":"2014-09-07T18:27:16","date_gmt":"2014-09-07T21:27:16","guid":{"rendered":"http:\/\/www.fernandosimon.com\/blog\/?p=163"},"modified":"2015-01-25T23:28:51","modified_gmt":"2015-01-26T02:28:51","slug":"oracle-e-maa-artigo-vii-switchover-broker","status":"publish","type":"post","link":"https:\/\/www.fernandosimon.com\/blog\/oracle-e-maa-artigo-vii-switchover-broker\/","title":{"rendered":"Oracle e MAA \u2013 Artigo VII \u2013 Switchover Broker"},"content":{"rendered":"

Seguindo uma ordem cronol\u00f3gica dos artigos sobre Oracle RAC e MAA vamos fazer um switchover usando o Broker. Em um ambiente de produ\u00e7\u00e3o voc\u00ea n\u00e3o seguiria esta ordem de eventos, mas para fins did\u00e1ticos \u00e9 interessante observar os passos.<\/p>\n

No \u00faltimo artigo<\/a> \u201cfor\u00e7amos\u201d um failover do ambiente, o banco \u201cmaa\u201d que rodava como primary sofreu um failover e o banco \u201cmaastb\u201d \u00e9 agora o primary.\u00a0 Al\u00e9m disso, no mesmo artigo o banco \u201cmaa\u201d sofre um reinstate e passou a atuar como physical standby. Diferentemente do primeiro artigo<\/a> que falei sobre failover, o \u00faltimo foi atrav\u00e9s do Broker. Todos os comandos partiram dele, do failover ao reinsate. Como disse no \u00faltimo artigo, o ambiente ainda n\u00e3o est\u00e1 100%, precisamos configurar o Fast-Start Failover para ter um ambiente completo com MAA.<\/p>\n

Infelizmente algumas atividades impediram publicar este artigo de maneira mais r\u00e1pida, isso deixou este arigo um pouco afastado dos demais. Recomendaria a releitura dos artigos anteriores para relembrar alguns pontos.<\/p>\n

S\u00c9TIMO ARTIGO<\/strong><\/p>\n

Neste artigo vamos ver como realizar o switchover do ambiente atrav\u00e9s do Broker. O banco \u201cmaastb\u201d que atua como primary sofrer\u00e1 uma troca de papeis com o seu banco \u201cmaa\u201d (que opera como physical standby).<\/p>\n

Vamos ver aqui que atrav\u00e9s do Broker os passos e comandos ficam mais simples (quando comparado com o switchover manual que foi realizado neste artigo<\/a>), basicamente iremos acompanhar alguns logs. Claro que tudo isso s\u00f3 acontecer\u00e1 pois j\u00e1 tomamos diversos cuidados no caminho at\u00e9 aqui, destaco como uma das principais a conex\u00e3o do Broker a cada inst\u00e2ncia (StaticConnectIdentifier<\/em>) por permitir enviar os comandos diretamente uma a uma.<\/p>\n

<\/p>\n

AMBIENTE<\/strong><\/p>\n

Para este artigo temos o banco \u201cmaastb\u201d operando como primary, enquanto o banco \u201cmaa\u201d opera como physical standby. Ambos s\u00e3o bancos Oracle RAC e completamente sincronizados. Al\u00e9m disso, o Broker est\u00e1 habilitado e \u201cmonitorando\u201d o ambiente.<\/p>\n

Como estamos com dois Oracle RAC de dois n\u00f3s cada temos 4 alertlog para demonstrar, bem como 4 logs do Broker para acompanhar. Desta forma, n\u00e3o se assuste com o tamanho do artigo, ele pode parecer extenso mas estar\u00e1 recheado de detalhes t\u00e9cnicos para observar.<\/p>\n

SWITCHOVER<\/strong><\/p>\n

Como disse no primeiro artigo sobre switchover, a diferen\u00e7a b\u00e1sica entre ele e um failover \u00e9 que no switchover ambos os bancos (primary e standby) est\u00e3o ativos e sabem da troca de papeis. Voc\u00ea n\u00e3o precisar\u00e1 fazer o reinstate do seu antigo primary, o standby assume no ponto subsequente ao que o primary chaveou. N\u00e3o h\u00e1 perda de archives ou de qualquer informa\u00e7\u00e3o da base de dados.<\/p>\n

Status do Ambiente<\/strong><\/p>\n

A primeira coisa a verificar antes de fazer o swictover \u00e9 se ambos, primary e standby, est\u00e3o sincronizados. N\u00e3o pode existir qualquer gap nos archives entre eles, se existir eu recomendo a voc\u00ea corrigir para depois dar sequ\u00eancia aos passos.<\/p>\n

Para verificar o ambiente voc\u00ea pode usar o sqlplus ou o Broker. No Broker eu recomendo verificar a configura\u00e7\u00e3o b\u00e1sica e o status de envio dos logs, observe:<\/p>\n

DGMGRL> SHOW CONFIGURATION;\r\n\r\nConfiguration - dgrac\r\n\r\n  Protection Mode: MaxAvailability\r\n  Databases:\r\n\tmaastb - Primary database\r\n\tmaa    - Physical standby database\r\n\r\nFast-Start Failover: DISABLED\r\n\r\nConfiguration Status:\r\nSUCCESS\r\n\r\nDGMGRL>\r\nDGMGRL> SHOW DATABASE maastb LogXptStatus;\r\nLOG TRANSPORT STATUS\r\nPRIMARY_INSTANCE_NAME STANDBY_DATABASE_NAME               STATUS\r\n\t\t\t maastb2                  maa\r\n\t\t\t maastb1                  maa\r\n\r\nDGMGRL>\r\n<\/pre>\n
No sqlplus basta fazer a consulta abaixo:<\/p>\n
SQL> SELECT protection_mode, protection_level, database_role FROM v$database;\r\n\r\nPROTECTION_MODE      PROTECTION_LEVEL     DATABASE_ROLE\r\n-------------------- -------------------- ----------------\r\nMAXIMUM AVAILABILITY MAXIMUM AVAILABILITY PRIMARY\r\n\r\nSQL>\r\n<\/pre>\n
Para ilustrar que n\u00e3o iremos perder qualquer informa\u00e7\u00e3o podemos usar a mesma tabela que criamos em artigos anteriores. Os dados ser\u00e3o removidos e no final vamos verificar se isso se mant\u00eam ap\u00f3s a troca de papeis:<\/p>\n
SQL> SELECT * FROM testedg;\r\n\r\n\t\tC1 C2\r\n---------- ---------\r\n\t\t 1 11-MAY-14\r\n\t\t 2 11-MAY-14\r\n\r\nSQL> DELETE FROM testedg;\r\n\r\n2 rows deleted.\r\n\r\nSQL> commit;\r\n\r\nCommit complete.\r\n\r\nSQL>\r\n<\/pre>\n
Swicthover to<\/strong><\/p>\n
Com a garantia de que a sincronia entre os ambientes est\u00e1 correta, basta fazer o switchover atrav\u00e9s do Broker (a conex\u00e3o pode ser em qualquer lado, mas recomendo ser no primary atual):<\/p>\n
DGMGRL> CONNECT sys@maastb;\r\nPassword:\r\nConnected.\r\nDGMGRL>\r\nDGMGRL> SWITCHOVER TO maa;\r\nPerforming switchover NOW, please wait...\r\nNew primary database \"maa\" is opening...\r\nOperation requires shutdown of instance \"maastb2\" on database \"maastb\"\r\nShutting down instance \"maastb2\"...\r\nORACLE instance shut down.\r\nOperation requires startup of instance \"maastb2\" on database \"maastb\"\r\nStarting instance \"maastb2\"...\r\nORACLE instance started.\r\nDatabase mounted.\r\nSwitchover succeeded, new primary is \"maa\"\r\nDGMGRL>\r\n<\/pre>\n
Viu como foi simples, mas antes de iniciarmos com a an\u00e1lise dos logs (alertlog e logs do broker) vamos ver o comando acima. Observe que a primeira a\u00e7\u00e3o do Broker foi conectar-se e abrir o novo primary (maa) e depois realizar o shutdown do antigo primary (maastb). Estas conex\u00f5es utilizam o StaticConnectIdentifier<\/em> para garantir uma conex\u00e3o direta e exclusiva. Observe tamb\u00e9m que todas as inst\u00e2ncias do antigo primary foram desligadas e posteriormente o banco foi montado.<\/p>\n
Um detalhe que cabe ressaltar antes de mostrar os logs abaixo, por um erro no meu ambiente as datas e horas dos Oracle RAC primary e standby est\u00e3o fora de sincronia, com diferen\u00e7a aproximada de 3 horas e 30 minutos. De qualquer forma, entre os n\u00f3s do mesmo cluster elas est\u00e3o sincronizadas.<\/p>\n
Tentarei mostrar de forma cronol\u00f3gica a ordem dos eventos que ocorreram. Para iniciar a an\u00e1lise temos o log do Broker da inst\u00e2ncia \u201cmaastb2\u201d (inst\u00e2ncia que recebeu a conex\u00e3o que fizemos no Broker no passo anterior):<\/p>\n
06\/10\/2014 03:02:55\r\nSWITCHOVER TO maa<\/strong>\r\nNotifying Oracle Clusterware to teardown primary database for SWITCHOVER\r\nDatabase Switchover needs instance count reduced to 1\r\n06\/10\/2014 03:03:26\r\nCommand SWITCHOVER TO maa completed\r\n06\/10\/2014 03:03:47\r\n>> Starting Data Guard Broker bootstrap <<\r\nBroker Configuration File Locations:\r\n\t  dg_broker_config_file1 = \"+DG01\/maastb\/dr1maastb.dat\"\r\n\t  dg_broker_config_file2 = \"+FRA\/maastb\/dr2maastb.dat\"\r\n06\/10\/2014 03:03:52\r\nDMON Registering service maastb_DGB with listener(s)\r\nBroker Configuration:       \"dgrac\"\r\n\t  Protection Mode:            Maximum Availability\r\n\t  Fast-Start Failover (FSFO): Disabled, flags=0x0, version=0\r\n\t  Primary Database:           maa (0x01010000)\r\n\t  Standby Database:           maastb, Enabled Physical Standby (0x02010000)\r\n06\/10\/2014 03:04:03\r\nCreating process RSM0\r\n06\/10\/2014 03:04:07\r\nSQL Execution error=604, sql=[alter system set log_archive_dest_1='']. See error stack below.\r\n  ORA-00604: error occurred at recursive SQL level 1\r\n  ORA-02097: parameter cannot be modified because specified value is invalid\r\n  ORA-16028: new LOG_ARCHIVE_DEST_1 causes less destinations than LOG_ARCHIVE_MIN_SUCCEED_DEST requires\r\n06\/10\/2014 03:04:26\r\nNotifying Oracle Clusterware to buildup standby database after SWITCHOVER\r\nData Guard notifying Oracle Clusterware to start services and other instances change\r\n06\/10\/2014 03:04:29\r\nCommand SWITCHOVER TO maastb completed\t\r\n<\/strong><\/pre>\n
Observe acima que ap\u00f3s receber o comando de switchover o Broker requisitou que somente uma inst\u00e2ncia do atual primary (maastb2) estive online. A solu\u00e7\u00e3o da Oracle n\u00e3o \u00e9 muito elegante (como voc\u00eas ir\u00e3o ver abaixo), mas resolve o problema. O log acima tem mais informa\u00e7\u00f5es, mas vamos pular para o alertlog da inst\u00e2ncia para ver a solu\u00e7\u00e3o da Oracle.<\/p>\n
Como vimos acima, quem est\u00e1 orquestrando o switchover \u00e9 a inst\u00e2ncia maastb2, desta forma (provavelmente) a inst\u00e2ncia \u201cmaastb1\u201d ter\u00e1 que ser desligada para que o switchover tenha sequ\u00eancia. Assim temos o alerlog da inst\u00e2ncia maastb1:<\/p>\n
Tue Jun 10 03:02:59 2014\r\nShutting down instance (abort)\r\nLicense high water mark = 6\r\nUSER (ospid: 29396): terminating the instance\r\nInstance terminated by USER, pid = 29396\r\nTue Jun 10 03:03:00 2014\r\nInstance shutdown complete\r\nTue Jun 10 03:04:35 2014\r\nStarting ORACLE instance (normal)\r\n...\r\n...\r\n<\/pre>\n
Observe acima a solu\u00e7\u00e3o \u201celegante\u201d escolhida pela Oracle para reduzir o n\u00famero de inst\u00e2ncias do primary ativas, um belo abort<\/strong> sem d\u00f3 nem piedade. Depois disso, vamos ao alertlog da inst\u00e2ncia maastb2 (\u00fanica do primary ativa e respons\u00e1vel pelo switchover):<\/p>\n
Tue Jun 10 03:03:01 2014\r\nReconfiguration started (old inc 4, new inc 6)<\/strong>\r\nList of instances:\r\n 2 (myinst: 2)\r\n Global Resource Directory frozen\r\n * dead instance detected - domain 0 invalid = TRUE<\/strong>\r\n Communication channels reestablished\r\n Master broadcasted resource hash value bitmaps\r\n Non-local Process blocks cleaned out\r\nTue Jun 10 03:03:01 2014\r\n LMS 0: 0 GCS shadows cancelled, 0 closed, 0 Xw survived\r\n Set master node info\r\n Submitted all remote-enqueue requests\r\n Dwn-cvts replayed, VALBLKs dubious\r\n All grantable enqueues granted\r\nTue Jun 10 03:03:01 2014\r\nminact-scn: master found reconf\/inst-rec before recscn scan old-inc#:4 new-inc#:4\r\n Post SMON to start 1st pass IR\r\nTue Jun 10 03:03:01 2014\r\nStarting background process CJQ0\r\n Submitted all GCS remote-cache requests\r\n Post SMON to start 1st pass IR\r\n Fix write in gcs resources\r\nTue Jun 10 03:03:01 2014\r\nInstance recovery: looking for dead threads\r\nReconfiguration complete<\/strong>\r\nBeginning instance recovery of 1 threads\r\nTue Jun 10 03:03:02 2014\r\nCJQ0 started with pid=60, OS id=14435\r\n parallel recovery started with 2 processes\r\nArchivelog destination LOG_ARCHIVE_DEST_2 validated for no-data-loss recovery\r\nARCH: Standby redo logfile selected for thread 1 sequence 185 for destination LOG_ARCHIVE_DEST_2\r\nStarted redo scan\r\nCompleted redo scan\r\n read 1916 KB redo, 735 data blocks need recovery\r\nStarted redo application at\r\n Thread 1: logseq 185, block 20041\r\nRecovery of Online Redo Log: Thread 1 Group 1 Seq 185 Reading mem 0\r\n  Mem# 0: +DG01\/maastb\/onlinelog\/group_1.257.844716051\r\n  Mem# 1: +FRA\/maastb\/onlinelog\/group_1.568.844716053\r\nCompleted redo application of 1.67MB\r\nCompleted instance recovery at<\/strong>\r\n Thread 1: logseq 185, block 23874, scn 11510215\r\n 676 data blocks read, 778 data blocks written, 1916 redo k-bytes read\r\nTue Jun 10 03:03:08 2014<\/strong>\r\nSetting recovery pair for thread 1: nab 23874 seq 185\r\nSMON: Completed archiving log 1 thread 1 sequence 185 (maastb2)\r\nThread 1 advanced to log sequence 186 (thread recovery)\r\nRedo thread 1 internally disabled at seq 186 (SMON)\r\nminact-scn: master continuing after IR\r\nminact-scn: Master considers inst:1 dead\r\nTue Jun 10 03:03:12 2014\r\nALTER DATABASE COMMIT TO SWITCHOVER TO PHYSICAL STANDBY WITH SESSION SHUTDOWN<\/strong>\r\nALTER DATABASE COMMIT TO SWITCHOVER TO PHYSICAL STANDBY [Process Id: 11540] (maastb2)<\/strong>\r\nTue Jun 10 03:03:13 2014\r\n******************************************************************\r\nLGWR: Setting 'active' archival for destination LOG_ARCHIVE_DEST_2\r\n******************************************************************\r\nLGWR: Standby redo logfile selected to archive thread 2 sequence 163\r\nLGWR: Standby redo logfile selected for thread 2 sequence 163 for destination LOG_ARCHIVE_DEST_2\r\nThread 2 advanced to log sequence 163 (LGWR switch)\r\n  Current log# 3 seq# 163 mem# 0: +DG01\/maastb\/onlinelog\/group_3.269.844716063\r\n  Current log# 3 seq# 163 mem# 1: +FRA\/maastb\/onlinelog\/group_3.562.844716065\r\nTue Jun 10 03:03:13 2014\r\nArchived Log entry 1019 added for thread 1 sequence 185 ID 0x2b1de48e dest 1:\r\nThread 2 cannot allocate new log, sequence 164\r\nCheckpoint not complete\r\n  Current log# 3 seq# 163 mem# 0: +DG01\/maastb\/onlinelog\/group_3.269.844716063\r\n  Current log# 3 seq# 163 mem# 1: +FRA\/maastb\/onlinelog\/group_3.562.844716065\r\nStopping background process QMNC\r\nTue Jun 10 03:03:14 2014\r\nStopping background process CJQ0\r\nTue Jun 10 03:03:14 2014\r\nArchived Log entry 1020 added for thread 2 sequence 162 ID 0x2b1de48e dest 1:\r\nTue Jun 10 03:03:14 2014\r\nARC3: LGWR is actively archiving destination LOG_ARCHIVE_DEST_2\r\nCLOSE: killing server sessions.\r\nActive process 14386 user 'oracle' program 'oracle@rac11stb02.tjsc.jus.br (W000)'\r\nActive process 14386 user 'oracle' program 'oracle@rac11stb02.tjsc.jus.br (W000)'\r\n...\r\n...\r\nCLOSE: all sessions shutdown successfully.\r\nWaiting for all non-current ORLs to be archived...\r\nAll non-current ORLs have been archived.\r\nWaiting for all FAL entries to be archived...<\/strong>\r\nAll FAL entries have been archived.<\/strong>\r\nWaiting for dest_id 2 to become synchronized...<\/strong>\r\nActive, synchronized Physical Standby switchover target has been identified<\/strong>\r\nSwitchover End-Of-Redo Log thread 2 sequence 163 has been fixed<\/strong>\r\nSwitchover: Primary highest seen SCN set to 0x0.0xaff3c1\r\nARCH: Noswitch archival of thread 2, sequence 163\r\nARCH: End-Of-Redo Branch archival of thread 2 sequence 163\r\nARCH: LGWR is actively archiving destination LOG_ARCHIVE_DEST_2<\/strong>\r\nARCH: Standby redo logfile selected for thread 2 sequence 163 for destination LOG_ARCHIVE_DEST_2\r\nArchived Log entry 1023 added for thread 2 sequence 163 ID 0x2b1de48e dest 1:\r\nARCH: Archiving is disabled due to current logfile archival\r\nPrimary will check for some target standby to have received alls redo<\/strong>\r\nFinal check for a synchronized target standby. Check will be made once.<\/strong>\r\nLOG_ARCHIVE_DEST_2 is a potential Physical Standby switchover target<\/strong>\r\nActive, synchronized target has been identified<\/strong>\r\nTarget has also received all redo<\/strong>\r\nBackup controlfile written to trace file \/u01\/app\/oracle\/diag\/rdbms\/maastb\/maastb2\/trace\/maastb2_rsm0_11540.trc\r\nClearing standby activation ID 723379342 (0x2b1de48e)\r\nThe primary database controlfile was created using the\r\n'MAXLOGFILES 192' clause.\r\nThere is space for up to 188 standby redo logfiles\r\nUse the following SQL commands on the standby database to create\r\nstandby redo logfiles that match the primary database:\r\nALTER DATABASE ADD STANDBY LOGFILE 'srl1.f' SIZE 52428800;\r\nALTER DATABASE ADD STANDBY LOGFILE 'srl2.f' SIZE 52428800;\r\nALTER DATABASE ADD STANDBY LOGFILE 'srl3.f' SIZE 52428800;\r\nALTER DATABASE ADD STANDBY LOGFILE 'srl4.f' SIZE 52428800;\r\nALTER DATABASE ADD STANDBY LOGFILE 'srl5.f' SIZE 52428800;\r\nArchivelog for thread 2 sequence 163 required for standby recovery\r\nSwitchover: Primary controlfile converted to standby controlfile succesfully.<\/strong>\r\nSwitchover: Complete - Database shutdown required<\/strong>\r\nCompleted: ALTER DATABASE COMMIT TO SWITCHOVER TO PHYSICAL STANDBY WITH SESSION SHUTDOWN\r\n<\/strong>Tue Jun 10 03:03:19 2014\r\nProcess (ospid 11546) is suspended due to switchover to physical standby operation.\r\nTue Jun 10 03:03:26 2014\r\nPerforming implicit shutdown abort due to switchover to physical standby\r\nShutting down instance (abort)<\/strong>\r\nLicense high water mark = 11\r\nUSER (ospid: 14458): terminating the instance\r\nInstance terminated by USER, pid = 14458\r\nTue Jun 10 03:03:28 2014\r\nInstance shutdown complete\r\nORA-1092 : opitsk aborting process\r\nTue Jun 10 03:03:29 2014\r\nStarting ORACLE instance (normal)\r\n...\r\n...\r\n<\/pre>\n
Analisando atentamente o log acima temos algumas informa\u00e7\u00f5es importantes (destacadas em negrito). Primeiro, a inst\u00e2ncia \u201cmaastb2\u201d detectou que a \u201cmaastb1\u201d n\u00e3o est\u00e1 mais ativa e iniciou o recovery de qualquer informa\u00e7\u00e3o perdida, iniciou as 03:03:01 e conclui as 03:03:08. Ap\u00f3s esse ajuste necess\u00e1rio, a maastb2 recebeu o comando de commit para swicthover (lembre-se que no artigo anterior isso foi manual). Na sequ\u00eancia tudo o que precisava ser arquivado foi e registrado em todos os FAL\u2019s. Al\u00e9m disso o poss\u00edvel destino (dest_2) foi identificado e o Oracle detectou que o target estava sincronizado (no log acima: Active, synchronized target has been identified<\/em>). Depois disso, a inst\u00e2ncia e o banco atual foram convertidos para physical standby (No log acima: Switchover: Primary controlfile converted to standby controlfile succesfully<\/em>). Observe que o swicthover iniciou as 03:03:12 e as 03:03:19 estava tudo conclu\u00eddo, esperando que a nova primary estivesse dispon\u00edvel.<\/p>\n
Dando sequ\u00eancia temos o log da inst\u00e2ncia \u201cmaa1\u201d, respons\u00e1vel por aplicar os redo recebidos da primary. Por isso, ela ser\u00e1 a inst\u00e2ncia que coordenar\u00e1 a transforma\u00e7\u00e3o de standby em primary do banco \u201cmaa\u201d. O alertlog abaixo foi \u201ccortado\u201d, as informa\u00e7\u00f5es sobre falhas de TNS foram retiradas. Estas falhas estavam ocorrendo devido ao banco standby (o \u201cmaastb\u201d) ainda n\u00e3o estar dispon\u00edvel para receber os redo do \u201cmaa\u201d.<\/p>\n
Tue Jun 10 06:22:05 2014\r\nRFS[2]: Possible network disconnect with primary database<\/strong>\r\nRFS[5]: Possible network disconnect with primary database\r\nTue Jun 10 06:22:06 2014\r\nRFS[4]: Possible network disconnect with primary database\r\nTue Jun 10 06:22:06 2014\r\nRFS[6]: Possible network disconnect with primary database\r\nTue Jun 10 06:22:09 2014\r\nPrimary database is in MAXIMUM AVAILABILITY mode<\/strong>\r\nStandby controlfile consistent with primary\r\nIdentified standby redo log 6 for instance\/crash recovery\r\nStandby controlfile consistent with primary\r\nRFS[11]: Assigned to RFS process 7457\r\nRFS[11]: Selected log 6 for thread 1 sequence 185 dbid 722024964 branch 847284763\r\nTue Jun 10 06:22:15 2014\r\nArchived Log entry 979 added for thread 1 sequence 185 ID 0x2b1de48e dest 1:\r\nTue Jun 10 06:22:19 2014\r\nArchived Log entry 980 added for thread 2 sequence 162 ID 0x2b1de48e dest 1:\r\nTue Jun 10 06:22:19 2014\r\nPrimary database is in MAXIMUM AVAILABILITY mode\r\nStandby controlfile consistent with primary<\/strong>\r\nStandby controlfile consistent with primary\r\nRFS[12]: Assigned to RFS process 7459\r\nRFS[12]: Selected log 8 for thread 2 sequence 163 dbid 722024964 branch 847284763\r\nTue Jun 10 06:22:21 2014\r\nMedia Recovery Waiting for thread 1 sequence 186 (in transit)<\/strong>\r\nTue Jun 10 06:22:21 2014\r\nRFS[13]: Assigned to RFS process 7461\r\nRFS[13]: Opened log for thread 1 sequence 186 dbid 722024964 branch 847284763<\/strong>\r\nArchived Log entry 981 added for thread 1 sequence 186 rlc 847284763 ID 0x2b1de48e dest 2:\r\nMedia Recovery Log +FRA\/maa\/archivelog\/2014_06_10\/thread_1_seq_186.1103.849853341\r\nMedia Recovery Waiting for thread 2 sequence 163 (in transit)\r\nRecovery of Online Redo Log: Thread 2 Group 8 Seq 163 Reading mem 0\r\n  Mem# 0: +DATA\/maa\/onlinelog\/group_8.259.843615383\r\n  Mem# 1: +FRA\/maa\/onlinelog\/group_8.703.843615385\r\nRFS[12]: Possible network disconnect with primary database\r\nTue Jun 10 06:22:23 2014\r\nRFS[14]: Assigned to RFS process 7465\r\nRFS[14]: Selected log 8 for thread 2 sequence 163 dbid 722024964 branch 847284763\r\nTue Jun 10 06:22:24 2014\r\nArchived Log entry 982 added for thread 2 sequence 163 ID 0x2b1de48e dest 1:\r\nResetting standby activation ID 723379342 (0x2b1de48e)\r\nMedia Recovery End-Of-Redo indicator encountered<\/strong>\r\nMedia Recovery Continuing\r\nMedia Recovery Waiting for thread 2 sequence 164\r\nTue Jun 10 06:22:25 2014\r\nALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL<\/strong>\r\nMRP0: Background Media Recovery cancelled with status 16037\r\nErrors in file \/u01\/app\/oracle\/diag\/rdbms\/maa\/maa1\/trace\/maa1_pr00_3715.trc:\r\nORA-16037: user requested cancel of managed recovery operation\r\nTue Jun 10 06:22:25 2014\r\nManaged Standby Recovery not using Real Time Apply\r\nRecovery interrupted!\r\nTue Jun 10 06:22:25 2014\r\nMRP0: Background Media Recovery process shutdown (maa1)\r\nManaged Standby Recovery Canceled (maa1)\r\nCompleted: ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL<\/strong>\r\nALTER DATABASE COMMIT TO SWITCHOVER TO PRIMARY WAIT WITH SESSION SHUTDOWN<\/strong>\r\nALTER DATABASE SWITCHOVER TO PRIMARY (maa1)<\/strong>\r\nMaximum wait for role transition is 15 minutes.\r\nTue Jun 10 06:22:26 2014\r\nkrsv_proc_kill: Killing 3 processes (all RFS)\r\nBackup controlfile written to trace file \/u01\/app\/oracle\/diag\/rdbms\/maa\/maa1\/trace\/maa1_rsm0_3682.trc\r\nSwitchOver after complete recovery through change 11531201<\/strong>\r\nOnline log +DATA\/maa\/onlinelog\/group_1.272.843488553: Thread 1 Group 1 was previously cleared\r\nOnline log +FRA\/maa\/onlinelog\/group_1.286.843488555: Thread 1 Group 1 was previously cleared\r\nOnline log +DATA\/maa\/onlinelog\/group_2.271.843488555: Thread 1 Group 2 was previously cleared\r\nOnline log +FRA\/maa\/onlinelog\/group_2.285.843488555: Thread 1 Group 2 was previously cleared\r\nOnline log +DATA\/maa\/onlinelog\/group_3.257.843489101: Thread 2 Group 3 was previously cleared\r\nOnline log +FRA\/maa\/onlinelog\/group_3.284.843489101: Thread 2 Group 3 was previously cleared\r\nOnline log +DATA\/maa\/onlinelog\/group_4.262.843489103: Thread 2 Group 4 was previously cleared\r\nOnline log +FRA\/maa\/onlinelog\/group_4.283.843489103: Thread 2 Group 4 was previously cleared\r\nStandby became primary SCN: 11531199\r\nSwitchover: Complete - Database mounted as primary\r\nCompleted: ALTER DATABASE COMMIT TO SWITCHOVER TO PRIMARY WAIT WITH SESSION SHUTDOWN\r\nALTER DATABASE OPEN\r\nData Guard Broker initializing...\r\nThis instance was first to open<\/strong>\r\nPicked broadcast on commit scheme to generate SCNs\r\nThread 2 advanced to log sequence 165 (before internal thread enable)\r\nTue Jun 10 06:22:33 2014\r\nARC3: Becoming the 'no SRL' ARCH\r\nARCH: LGWR is scheduled to archive destination LOG_ARCHIVE_DEST_2 after log switch\r\n...\r\n...\r\n...\r\nError 12514 received logging on to the standby\r\nARCH: Error 12514 Creating archive log file to 'maastb'<\/strong>\r\nArchived Log entry 983 added for thread 2 sequence 164 ID 0x0 dest 1:\r\nThread 2 advanced to log sequence 166 (after internal thread enable)\r\nARC1: Becoming the 'no SRL' ARCH\r\nArchived Log entry 984 added for thread 2 sequence 165 ID 0x0 dest 1:\r\nTue Jun 10 06:22:34 2014\r\nAssigning activation ID 728027883 (0x2b64d2eb)\r\nLGWR: Primary database is in MAXIMUM AVAILABILITY mode\r\nDestination LOG_ARCHIVE_DEST_2 is UNSYNCHRONIZED<\/strong>\r\nLGWR: Destination LOG_ARCHIVE_DEST_1 is not serviced by LGWR\r\nThread 1 advanced to log sequence 188 (thread open)\r\nThread 1 opened at log sequence 188\r\n  Current log# 2 seq# 188 mem# 0: +DATA\/maa\/onlinelog\/group_2.271.843488555\r\n  Current log# 2 seq# 188 mem# 1: +FRA\/maa\/onlinelog\/group_2.285.843488555\r\nSuccessful open of redo thread 1\r\nMTTR advisory is disabled because FAST_START_MTTR_TARGET is not set\r\nTue Jun 10 06:22:34 2014\r\n...\r\n...\r\n...\r\nError 12514 received logging on to the standby\r\nPING[ARC2]: Heartbeat failed to connect to standby 'maastb'. Error is 12514.\r\nInstance recovery: looking for dead threads\r\nInstance recovery: lock domain invalid but no dead threads\r\nTue Jun 10 06:22:40 2014\r\nminact-scn: Inst 1 is now the master inc#:3 mmon proc-id:3517 status:0x7\r\nminact-scn status: grec-scn:0x0000.00000000 gmin-scn:0x0000.00000000 gcalc-scn:0x0000.00000000\r\nminact-scn: Master returning as live inst:2 has inc# mismatch instinc:0 cur:3 errcnt:0\r\nTue Jun 10 06:22:40 2014\r\n[3682] Successfully onlined Undo Tablespace 2.\r\nUndo initialization finished serial:0 start:385367814 end:385369304 diff:1490 (14 seconds)\r\nDictionary check beginning\r\nDictionary check complete\r\nVerifying file header compatibility for 11g tablespace encryption..\r\nVerifying 11g file header compatibility for tablespace encryption completed\r\nSMON: enabling tx recovery\r\nDatabase Characterset is WE8MSWIN1252\r\nNo Resource Manager plan active\r\nStarting background process GTX0\r\nTue Jun 10 06:22:44 2014\r\nGTX0 started with pid=27, OS id=7470\r\nStarting background process RCBG\r\nTue Jun 10 06:22:44 2014\r\nRCBG started with pid=32, OS id=7472\r\nreplication_dependency_tracking turned off (no async multimaster replication found)\r\nStarting background process QMNC\r\nTue Jun 10 06:22:45 2014\r\nQMNC started with pid=40, OS id=7474\r\nLOGSTDBY: Validating controlfile with logical metadata\r\nLOGSTDBY: Validation complete\r\nCompleted: ALTER DATABASE OPEN<\/strong>\r\nALTER SYSTEM SET log_archive_trace=0 SCOPE=BOTH SID='maa1';\r\nALTER SYSTEM SET log_archive_format='arch_%t_%s_%r.arc' SCOPE=SPFILE SID='maa1';\r\nALTER SYSTEM SET standby_file_management='AUTO' SCOPE=BOTH SID='*';\r\nALTER SYSTEM SET archive_lag_target=0 SCOPE=BOTH SID='*';\r\nALTER SYSTEM SET log_archive_max_processes=4 SCOPE=BOTH SID='*';\r\nALTER SYSTEM SET log_archive_min_succeed_dest=1 SCOPE=BOTH SID='*';\r\nALTER SYSTEM SET db_file_name_convert='+DG01\/maastb','+DATA\/maa','+FRA\/maastb','+FRA\/maa' SCOPE=SPFILE;\r\nALTER SYSTEM SET log_file_name_convert='+DG01\/maastb','+DATA\/maa','+FRA\/maastb','+FRA\/maa' SCOPE=SPFILE;\r\nTue Jun 10 06:22:48 2014\r\nARC2: STARTING ARCH PROCESSES\r\nTue Jun 10 06:22:48 2014\r\nARC4 started with pid=49, OS id=7486\r\nALTER SYSTEM SET log_archive_dest_state_2='ENABLE' SCOPE=BOTH;\r\nALTER SYSTEM ARCHIVE LOG\r\nTue Jun 10 06:22:49 2014<\/strong>\r\n*********************************************************************\r\nWARNING: Detected remote instance standby database network disconnect\r\nWARNING: Current instance standby database disconnect may be required\r\n*********************************************************************\r\nARC4: Archival started\r\nARC2: STARTING ARCH PROCESSES COMPLETE\r\n...\r\n...\r\n...\r\nError 12528 received logging on to the standby\r\nError 12528 for archive log file 1 to 'maastb'\r\nLGWR: Failed to archive log 1 thread 1 sequence 189 (12528)\r\nThread 1 advanced to log sequence 189 (LGWR switch)\r\n  Current log# 1 seq# 189 mem# 0: +DATA\/maa\/onlinelog\/group_1.272.843488553\r\n  Current log# 1 seq# 189 mem# 1: +FRA\/maa\/onlinelog\/group_1.286.843488555\r\nTue Jun 10 06:22:52 2014\r\nStarting background process CJQ0\r\nTue Jun 10 06:22:53 2014\r\nCJQ0 started with pid=52, OS id=7510\r\nTue Jun 10 06:22:53 2014\r\nALTER SYSTEM SET log_archive_dest_state_2='ENABLE' SCOPE=MEMORY SID='*';\r\nTue Jun 10 06:22:53 2014\r\nArchived Log entry 988 added for thread 1 sequence 188 ID 0x2b64d2eb dest 1:\r\nTue Jun 10 06:22:54 2014\r\nStarting background process SMCO\r\nTue Jun 10 06:22:54 2014\r\nSMCO started with pid=54, OS id=7516\r\nTue Jun 10 06:22:55 2014\r\nActive Session History (ASH) performed an emergency flush. This may mean that ASH is undersized. If emergency flushes are a recurring issue, you may consider increasing ASH size by setting the value of _ASH_SIZE to a sufficiently large value. Currently, ASH size is 4194304 bytes. Both ASH size and the total number of emergency flushes since instance startup can be monitored by running the following query:\r\n select total_size,awr_flush_emergency_count from v$ash_info;\r\nThread 1 cannot allocate new log, sequence 190\r\nCheckpoint not complete\r\n  Current log# 1 seq# 189 mem# 0: +DATA\/maa\/onlinelog\/group_1.272.843488553\r\n  Current log# 1 seq# 189 mem# 1: +FRA\/maa\/onlinelog\/group_1.286.843488555\r\nTue Jun 10 06:22:56 2014\r\n...\r\n...\r\n...\r\nSetting Resource Manager plan SCHEDULER[0x3189]:DEFAULT_MAINTENANCE_PLAN via scheduler window\r\nSetting Resource Manager plan DEFAULT_MAINTENANCE_PLAN via parameter\r\nTue Jun 10 06:22:57 2014\r\nStarting background process VKRM\r\nTue Jun 10 06:22:57 2014\r\nVKRM started with pid=41, OS id=7530\r\nTue Jun 10 06:23:01 2014\r\nLGWR: Standby redo logfile selected to archive thread 1 sequence 190\r\nLGWR: Standby redo logfile selected for thread 1 sequence 190 for destination LOG_ARCHIVE_DEST_2\r\nThread 1 advanced to log sequence 190 (LGWR switch)\r\n  Current log# 2 seq# 190 mem# 0: +DATA\/maa\/onlinelog\/group_2.271.843488555\r\n  Current log# 2 seq# 190 mem# 1: +FRA\/maa\/onlinelog\/group_2.285.843488555\r\nTue Jun 10 06:23:03 2014\r\nArchived Log entry 989 added for thread 1 sequence 189 ID 0x2b64d2eb dest 1:\r\nTue Jun 10 06:23:06 2014\r\nBegin automatic SQL Tuning Advisor run for special tuning task  \"SYS_AUTO_SQL_TUNING_TASK\"\r\nTue Jun 10 06:23:07 2014\r\nShutting down archive processes\r\nARCH shutting down\r\nARC4: Archival stopped\r\nEnd automatic SQL Tuning Advisor run for special tuning task  \"SYS_AUTO_SQL_TUNING_TASK\"\r\nThread 1 cannot allocate new log, sequence 191\r\nCheckpoint not complete\r\n  Current log# 2 seq# 190 mem# 0: +DATA\/maa\/onlinelog\/group_2.271.843488555\r\n  Current log# 2 seq# 190 mem# 1: +FRA\/maa\/onlinelog\/group_2.285.843488555\r\nTue Jun 10 06:23:13 2014\r\nDestination LOG_ARCHIVE_DEST_2 is SYNCHRONIZED<\/strong>\r\nLGWR: Standby redo logfile selected to archive thread 1 sequence 191\t\r\n<\/pre>\n
Novamente analisando com calma o log acima (destaquei pontos importantes em negrito) observamos que o processo come\u00e7a com a detec\u00e7\u00e3o da indisponibilidade do primary e a garantia de que tudo est\u00e1 sincronizado. O \u00faltimo redo recebido \u00e9 aberto e detecta-se um End-Of-Redo. Ap\u00f3s isso, as 06:22:25, o standby cancela a aplica\u00e7\u00e3o dos redo que estava aplicando e realiza o switchover para primary. Como tudo est\u00e1 sincronizado o banco inicia o processo de open. Ainda assim, o log_archive_dest_2<\/em> n\u00e3o est\u00e1 sincronizado, mas quando o novo standby subir, tudo ficar\u00e1 sincronizado. O processo de finaliza as 06:22:49 logo ap\u00f3s o open, o que vem ap\u00f3s isso \u00e9 a espera pelo novo standby estar dispon\u00edvel para sincroniza\u00e7\u00e3o.<\/p>\n
Analisando abaixo temos o alertlog da outra inst\u00e2ncia do novo primary, a \u201cmaa2\u201d. As informa\u00e7\u00f5es contidas s\u00e3o mais simples, um simples abort e sincroniza\u00e7\u00f5es com a nova standby (deste log somente cortei os erros de TNS\/indisponibilidade do standby):<\/p>\n
Tue Jun 10 06:22:25 2014\r\nManaged Standby Recovery not using Real Time Apply\r\nSwitchover: Complete - Database mounted as primary\r\nTue Jun 10 06:22:32 2014<\/strong>\r\nALTER DATABASE OPEN<\/strong>\r\nData Guard Broker initializing...\r\nPicked broadcast on commit scheme to generate SCNs\r\nTue Jun 10 06:22:35 2014\r\nLGWR: Primary database is in MAXIMUM AVAILABILITY mode<\/strong>\r\nDestination LOG_ARCHIVE_DEST_2 is UNSYNCHRONIZED<\/strong>\r\nLGWR: Destination LOG_ARCHIVE_DEST_1 is not serviced by LGWR\r\nThread 2 advanced to log sequence 167 (thread open)\r\nTue Jun 10 06:22:35 2014\r\nARC2: Becoming the 'no SRL' ARCH\r\nThread 2 opened at log sequence 167\r\n  Current log# 4 seq# 167 mem# 0: +DATA\/maa\/onlinelog\/group_4.262.843489103\r\n  Current log# 4 seq# 167 mem# 1: +FRA\/maa\/onlinelog\/group_4.283.843489103\r\nSuccessful open of redo thread 2\r\nMTTR advisory is disabled because FAST_START_MTTR_TARGET is not set\r\nTue Jun 10 06:22:35 2014\r\nSMON: enabling cache recovery\r\nTue Jun 10 06:22:36 2014\r\n...\r\n...\r\n...\r\nError 12514 received logging on to the standby\r\nPING[ARC1]: Heartbeat failed to connect to standby 'maastb'. Error is 12514.\r\nArchived Log entry 986 added for thread 2 sequence 166 ID 0x2b64d2eb dest 1:\r\n[3843] Successfully onlined Undo Tablespace 4.\r\nUndo initialization finished serial:0 start:385365424 end:385366584 diff:1160 (11 seconds)\r\nVerifying file header compatibility for 11g tablespace encryption..\r\nVerifying 11g file header compatibility for tablespace encryption completed\r\nSMON: enabling tx recovery\r\nDatabase Characterset is WE8MSWIN1252\r\nTue Jun 10 06:22:41 2014\r\nminact-scn: Inst 2 is a slave inc#:3 mmon proc-id:3731 status:0x2\r\nminact-scn status: grec-scn:0x0000.00000000 gmin-scn:0x0000.00000000 gcalc-scn:0x0000.00000000\r\nNo Resource Manager plan active\r\nTue Jun 10 06:22:44 2014\r\nStarting background process GTX0\r\nTue Jun 10 06:22:44 2014\r\nGTX0 started with pid=47, OS id=12888\r\nStarting background process RCBG\r\nTue Jun 10 06:22:44 2014\r\nRCBG started with pid=48, OS id=12890\r\nreplication_dependency_tracking turned off (no async multimaster replication found)\r\nStarting background process QMNC\r\nTue Jun 10 06:22:45 2014\r\nQMNC started with pid=49, OS id=12892\r\nCompleted: ALTER DATABASE OPEN\r\nALTER SYSTEM SET log_archive_trace=0 SCOPE=BOTH SID='maa2';\r\nALTER SYSTEM SET log_archive_format='arch_%t_%s_%r.arc' SCOPE=SPFILE SID='maa2';\r\nTue Jun 10 06:22:48 2014\r\nARC1: STARTING ARCH PROCESSES\r\nTue Jun 10 06:22:48 2014\r\nARC4 started with pid=52, OS id=12903\r\nTue Jun 10 06:22:49 2014\r\n******************************************************************\r\nLGWR: Setting 'active' archival for destination LOG_ARCHIVE_DEST_2\r\n******************************************************************\r\nTue Jun 10 06:22:49 2014\r\n...\r\n... \r\n...\r\nError 12528 received logging on to the standby\r\nError 12528 for archive log file 3 to 'maastb'\r\nLGWR: Failed to archive log 3 thread 2 sequence 168 (12528)\r\nThread 2 advanced to log sequence 168 (LGWR switch)\r\n  Current log# 3 seq# 168 mem# 0: +DATA\/maa\/onlinelog\/group_3.257.843489101\r\n  Current log# 3 seq# 168 mem# 1: +FRA\/maa\/onlinelog\/group_3.284.843489101\r\nARC4: Archival started\r\nARC1: STARTING ARCH PROCESSES COMPLETE\r\n*********************************************************************\r\nWARNING: Detected remote instance standby database network disconnect\r\nWARNING: Current instance standby database disconnect may be required\r\n*********************************************************************\r\nTue Jun 10 06:22:51 2014\r\nArchived Log entry 987 added for thread 2 sequence 167 ID 0x2b64d2eb dest 1:\r\nTue Jun 10 06:22:54 2014\r\nStarting background process CJQ0\r\nTue Jun 10 06:22:54 2014\r\nCJQ0 started with pid=53, OS id=12920\r\nThread 2 cannot allocate new log, sequence 169\r\nCheckpoint not complete\r\n  Current log# 3 seq# 168 mem# 0: +DATA\/maa\/onlinelog\/group_3.257.843489101\r\n  Current log# 3 seq# 168 mem# 1: +FRA\/maa\/onlinelog\/group_3.284.843489101\r\nTue Jun 10 06:22:58 2014\r\nSetting Resource Manager plan DEFAULT_MAINTENANCE_PLAN via parameter\r\nTue Jun 10 06:22:58 2014\r\nStarting background process VKRM\r\nTue Jun 10 06:22:58 2014\r\nVKRM started with pid=54, OS id=12930\r\nTue Jun 10 06:22:59 2014\r\nLGWR: Standby redo logfile selected to archive thread 2 sequence 169\r\nLGWR: Standby redo logfile selected for thread 2 sequence 169 for destination LOG_ARCHIVE_DEST_2\r\nThread 2 advanced to log sequence 169 (LGWR switch)\r\n  Current log# 4 seq# 169 mem# 0: +DATA\/maa\/onlinelog\/group_4.262.843489103\r\n  Current log# 4 seq# 169 mem# 1: +FRA\/maa\/onlinelog\/group_4.283.843489103\r\nTue Jun 10 06:23:05 2014\r\nArchived Log entry 990 added for thread 2 sequence 168 ID 0x2b64d2eb dest 1:\r\nTue Jun 10 06:23:08 2014\r\nErrors in file \/u01\/app\/oracle\/diag\/rdbms\/maa\/maa2\/trace\/maa2_j001_12934.trc:\r\nORA-12012: error on auto execute of job \"ORACLE_OCM\".\"MGMT_CONFIG_JOB_2_2\"\r\nORA-29280: invalid directory path\r\nORA-06512: at \"ORACLE_OCM.MGMT_DB_LL_METRICS\", line 2436\r\nORA-06512: at line 1\r\nTue Jun 10 06:23:12 2014\r\nThread 2 cannot allocate new log, sequence 170\r\nCheckpoint not complete\r\n  Current log# 4 seq# 169 mem# 0: +DATA\/maa\/onlinelog\/group_4.262.843489103\r\n  Current log# 4 seq# 169 mem# 1: +FRA\/maa\/onlinelog\/group_4.283.843489103\r\nDestination LOG_ARCHIVE_DEST_2 is SYNCHRONIZED<\/strong>\r\nLGWR: Standby redo logfile selected to archive thread 2 sequence 170\r\nLGWR: Standby redo logfile selected for thread 2 sequence 170 for destination LOG_ARCHIVE_DEST_2\r\nThread 2 advanced to log sequence 170 (LGWR switch)\r\n  Current log# 3 seq# 170 mem# 0: +DATA\/maa\/onlinelog\/group_3.257.843489101\r\n  Current log# 3 seq# 170 mem# 1: +FRA\/maa\/onlinelog\/group_3.284.843489101\r\nTue Jun 10 06:23:16 2014\r\nArchived Log entry 1002 added for thread 2 sequence 169 ID 0x2b64d2eb dest 1:\r\nTue Jun 10 06:23:22 2014\r\nThread 2 cannot allocate new log, sequence 171\r\nCheckpoint not complete\r\n  Current log# 3 seq# 170 mem# 0: +DATA\/maa\/onlinelog\/group_3.257.843489101\r\n  Current log# 3 seq# 170 mem# 1: +FRA\/maa\/onlinelog\/group_3.284.843489101\r\nLGWR: Standby redo logfile selected to archive thread 2 sequence 171\r\nLGWR: Standby redo logfile selected for thread 2 sequence 171 for destination LOG_ARCHIVE_DEST_2\r\nThread 2 advanced to log sequence 171 (LGWR switch)\r\n  Current log# 4 seq# 171 mem# 0: +DATA\/maa\/onlinelog\/group_4.262.843489103\r\n  Current log# 4 seq# 171 mem# 1: +FRA\/maa\/onlinelog\/group_4.283.843489103\r\nTue Jun 10 06:24:17 2014\r\nALTER SYSTEM SET log_archive_dest_state_2='ENABLE' SCOPE=BOTH;\r\nTue Jun 10 06:27:49 2014\r\nStarting background process SMCO\r\nTue Jun 10 06:27:49 2014\r\nSMCO started with pid=39, OS id=13041\r\n<\/pre>\n
Vamos voltar ao alertlog do banco \u201cmaastb\u201d que parei a an\u00e1lise ap\u00f3s o seu shutdown e que no ambiente atual este banco deve ser iniciado para atuar como standby a partir de agora. Abaixo a continua\u00e7\u00e3o do alertlog da inst\u00e2ncia \u201cmaastb2\u201d que estava coordenando esta troca de papeis:<\/p>\n
Tue Jun 10 03:03:28 2014\r\nInstance shutdown complete\r\nORA-1092 : opitsk aborting process\r\nTue Jun 10 03:03:29 2014\r\nStarting ORACLE instance (normal)<\/strong>\r\n****************** Large Pages Information *****************\r\n\r\nTotal Shared Global Region in Large Pages = 0 KB (0%)\r\n\r\nLarge Pages used by this instance: 0 (0 KB)\r\nLarge Pages unused system wide = 0 (0 KB) (alloc incr 4096 KB)\r\nLarge Pages configured system wide = 0 (0 KB)\r\nLarge Page size = 2048 KB\r\n\r\nRECOMMENDATION:\r\n  Total Shared Global Region size is 1026 MB. For optimal performance,\r\n  prior to the next instance restart increase the number\r\n  of unused Large Pages by atleast 513 2048 KB Large Pages (1026 MB)\r\n  system wide to get 100% of the Shared\r\n  Global Region allocated with Large pages\r\n***********************************************************\r\nLICENSE_MAX_SESSION = 0\r\nLICENSE_SESSIONS_WARNING = 0\r\nPrivate Interface 'eth2:1' configured from GPnP for use as a private interconnect.\r\n  [name='eth2:1', type=1, ip=169.254.212.125, mac=00-0c-29-0a-ae-e2, net=169.254.0.0\/16, mask=255.255.0.0, use=haip:cluster_interconnect\/62]\r\nPublic Interface 'eth0' configured from GPnP for use as a public interface.\r\n  [name='eth0', type=1, ip=10.17.42.50, mac=00-0c-29-0a-ae-ce, net=10.17.42.0\/26, mask=255.255.255.192, use=public\/1]\r\nPublic Interface 'eth0:1' configured from GPnP for use as a public interface.\r\n  [name='eth0:1', type=1, ip=10.17.42.34, mac=00-0c-29-0a-ae-ce, net=10.17.42.0\/26, mask=255.255.255.192, use=public\/1]\r\nPublic Interface 'eth0:3' configured from GPnP for use as a public interface.\r\n  [name='eth0:3', type=1, ip=10.17.42.33, mac=00-0c-29-0a-ae-ce, net=10.17.42.0\/26, mask=255.255.255.192, use=public\/1]\r\nPublic Interface 'eth0:5' configured from GPnP for use as a public interface.\r\n  [name='eth0:5', type=1, ip=10.17.42.51, mac=00-0c-29-0a-ae-ce, net=10.17.42.0\/26, mask=255.255.255.192, use=public\/1]\r\nPicked latch-free SCN scheme 3\r\nAutotune of undo retention is turned on.\r\nLICENSE_MAX_USERS = 0\r\nSYS auditing is disabled\r\nStarting up:\r\nOracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production\r\nWith the Partitioning, Real Application Clusters and Real Application Testing options.\r\nORACLE_HOME = \/u01\/app\/oracle\/product\/11.2.0.3\/db_1\r\nSystem name:    Linux\r\nNode name:      rac11stb02.tjsc.jus.br\r\nRelease:        2.6.39-400.17.1.el6uek.x86_64\r\nVersion:        #1 SMP Fri Feb 22 18:16:18 PST 2013\r\nMachine:        x86_64\r\nVM name:        VMWare Version: 6\r\nUsing parameter settings in server-side pfile \/u01\/app\/oracle\/product\/11.2.0.3\/db_1\/dbs\/initmaastb2.ora\r\nSystem parameters with non-default values:\r\n  processes                = 150\r\n  spfile                   = \"+DG01\/maastb\/spfilemaastb.ora\"\r\n  sga_target               = 1G\r\n  control_files            = \"+DG01\/maastb\/controlfile\/current.273.844715953\"\r\n  control_files            = \"+FRA\/maastb\/controlfile\/current.579.844715953\"\r\n  db_file_name_convert     = \"+DATA\/maa\"\r\n  db_file_name_convert     = \"+DG01\/maastb\"\r\n  db_file_name_convert     = \"+FRA\/maa\"\r\n  db_file_name_convert     = \"+FRA\/maastb\"\r\n  log_file_name_convert    = \"+DATA\/maa\"\r\n  log_file_name_convert    = \"+DG01\/maastb\"\r\n  log_file_name_convert    = \"+FRA\/maa\"\r\n  log_file_name_convert    = \"+FRA\/maastb\"\r\n  db_block_size            = 8192\r\n  compatible               = \"11.2.0.0.0\"\r\n  log_archive_dest_1       = \"LOCATION=USE_DB_RECOVERY_FILE_DEST VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=maastb\"\r\n  log_archive_dest_2       = \"service=\"maa\"\"\r\n  log_archive_dest_2       = \"LGWR SYNC AFFIRM delay=0 optional compression=disable max_failure=0 max_connections=1 reopen=300 db_unique_name=\"maa\" net_timeout=30\"\r\n  log_archive_dest_2       = \"valid_for=(all_logfiles,primary_role)\"\r\n  log_archive_dest_state_2 = \"ENABLE\"\r\n  log_archive_min_succeed_dest= 1\r\n  fal_server               = \"maa\"\r\n  log_archive_trace        = 0\r\n  log_archive_config       = \"DG_CONFIG=(maa,maastb)\"\r\n  log_archive_format       = \"arch_%t_%s_%r.arc\"\r\n  log_archive_max_processes= 4\r\n  archive_lag_target       = 0\r\n  cluster_database         = TRUE\r\n  db_create_file_dest      = \"+DG01\"\r\n  db_recovery_file_dest    = \"+FRA\"\r\n  db_recovery_file_dest_size= 10G\r\n  standby_file_management  = \"AUTO\"\r\n  thread                   = 2\r\n  undo_tablespace          = \"UNDOTBS2\"\r\n  instance_number          = 2\r\n  remote_login_passwordfile= \"EXCLUSIVE\"\r\n  db_domain                = \"\"\r\n  remote_listener          = \"rac11stb-scan.tjsc.jus.br:1521\"\r\n  audit_file_dest          = \"\/u01\/app\/oracle\/admin\/maastb\/adump\"\r\n  audit_trail              = \"DB\"\r\n  db_name                  = \"maa\"\r\n  db_unique_name           = \"maastb\"\r\n  open_cursors             = 300\r\n  pga_aggregate_target     = 256M\r\n  dg_broker_start          = TRUE\r\n  dg_broker_config_file1   = \"+DG01\/maastb\/dr1maastb.dat\"\r\n  dg_broker_config_file2   = \"+FRA\/maastb\/dr2maastb.dat\"\r\n  diagnostic_dest          = \"\/u01\/app\/oracle\"\r\nCluster communication is configured to use the following interface(s) for this instance\r\n  169.254.212.125\r\ncluster interconnect IPC version:Oracle UDP\/IP (generic)\r\nIPC Vendor 1 proto 2\r\nTue Jun 10 03:03:31 2014\r\nPMON started with pid=2, OS id=14478\r\nTue Jun 10 03:03:31 2014\r\nPSP0 started with pid=3, OS id=14480\r\nTue Jun 10 03:03:32 2014\r\nVKTM started with pid=4, OS id=14482 at elevated priority\r\nVKTM running at (1)millisec precision with DBRM quantum (100)ms\r\nTue Jun 10 03:03:32 2014\r\nGEN0 started with pid=5, OS id=14486\r\nTue Jun 10 03:03:32 2014\r\nDIAG started with pid=6, OS id=14488\r\nTue Jun 10 03:03:32 2014\r\nDBRM started with pid=7, OS id=14491\r\nTue Jun 10 03:03:32 2014\r\nPING started with pid=8, OS id=14493\r\nTue Jun 10 03:03:32 2014\r\nACMS started with pid=9, OS id=14496\r\nTue Jun 10 03:03:32 2014\r\nDIA0 started with pid=10, OS id=14498\r\nTue Jun 10 03:03:32 2014\r\nLMON started with pid=11, OS id=14500\r\nTue Jun 10 03:03:33 2014\r\nLMD0 started with pid=12, OS id=14502\r\n* Load Monitor used for high load check\r\n* New Low - High Load Threshold Range = [1920 - 2560]\r\nTue Jun 10 03:03:33 2014\r\nLMS0 started with pid=13, OS id=14504 at elevated priority\r\nTue Jun 10 03:03:33 2014\r\nRMS0 started with pid=14, OS id=14508\r\nTue Jun 10 03:03:33 2014\r\nMMAN started with pid=16, OS id=14512\r\nTue Jun 10 03:03:33 2014\r\nLMHB started with pid=15, OS id=14510\r\nTue Jun 10 03:03:33 2014\r\nDBW0 started with pid=17, OS id=14514\r\nTue Jun 10 03:03:33 2014\r\nLGWR started with pid=18, OS id=14516\r\nTue Jun 10 03:03:33 2014\r\nCKPT started with pid=19, OS id=14518\r\nTue Jun 10 03:03:33 2014\r\nSMON started with pid=20, OS id=14520\r\nTue Jun 10 03:03:33 2014\r\nRECO started with pid=21, OS id=14522\r\nTue Jun 10 03:03:33 2014\r\nRBAL started with pid=22, OS id=14524\r\nTue Jun 10 03:03:33 2014\r\nASMB started with pid=23, OS id=14526\r\nTue Jun 10 03:03:33 2014\r\nMMON started with pid=24, OS id=14528\r\nTue Jun 10 03:03:33 2014\r\nMMNL started with pid=25, OS id=14532\r\nlmon registered with NM - instance number 2 (internal mem no 1)\r\nNOTE: initiating MARK startup\r\nStarting background process MARK\r\nTue Jun 10 03:03:33 2014\r\nMARK started with pid=26, OS id=14534\r\nNOTE: MARK has subscribed\r\nReconfiguration started (old inc 0, new inc 2)\r\nList of instances:\r\n 2 (myinst: 2)<\/strong>\r\n Global Resource Directory frozen\r\n* allocate domain 0, invalid = TRUE\r\n Communication channels reestablished\r\n Master broadcasted resource hash value bitmaps\r\n Non-local Process blocks cleaned out\r\n LMS 0: 0 GCS shadows cancelled, 0 closed, 0 Xw survived\r\n Set master node info\r\n Submitted all remote-enqueue requests\r\n Dwn-cvts replayed, VALBLKs dubious\r\n All grantable enqueues granted\r\n Post SMON to start 1st pass IR\r\n Submitted all GCS remote-cache requests\r\n Post SMON to start 1st pass IR\r\n Fix write in gcs resources\r\nReconfiguration complete<\/strong>\r\nTue Jun 10 03:03:34 2014\r\nLCK0 started with pid=28, OS id=14540\r\nStarting background process RSMN\r\nTue Jun 10 03:03:34 2014\r\nRSMN started with pid=29, OS id=14542\r\nORACLE_BASE from environment = \/u01\/app\/oracle\r\nTue Jun 10 03:03:34 2014\r\nDMON started with pid=30, OS id=14546\r\nTue Jun 10 03:03:35 2014\r\nalter database  mount\r\nThis instance was first to mount<\/strong>\r\nTue Jun 10 03:03:35 2014\r\nALTER SYSTEM SET local_listener='(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=10.17.42.51)(PORT=1521))))' SCOPE=MEMORY SID='maastb2';\r\nNOTE: Loaded library: \/opt\/oracle\/extapi\/64\/asm\/orcl\/1\/libasm.so\r\nNOTE: Loaded library: System\r\nSUCCESS: diskgroup DG01 was mounted\r\nNOTE: dependency between database maastb and diskgroup resource ora.DG01.dg is established\r\nSUCCESS: diskgroup FRA was mounted\r\nNOTE: dependency between database maastb and diskgroup resource ora.FRA.dg is established\r\nTue Jun 10 03:03:42 2014\r\nNSS2 started with pid=31, OS id=14576\r\nARCH: STARTING ARCH PROCESSES\r\nTue Jun 10 03:03:42 2014\r\nARC0 started with pid=34, OS id=14578\r\nARC0: Archival started\r\nARCH: STARTING ARCH PROCESSES COMPLETE\r\nARC0: STARTING ARCH PROCESSES\r\nTue Jun 10 03:03:43 2014\r\nARC1 started with pid=35, OS id=14580\r\nTue Jun 10 03:03:43 2014\r\nARC2 started with pid=36, OS id=14582\r\nTue Jun 10 03:03:43 2014\r\nARC1: Archival started\r\nARC2: Archival started\r\nARC3 started with pid=37, OS id=14584\r\nARC1: Becoming the 'no FAL' ARCH\r\nARC1: Becoming the 'no SRL' ARCH\r\nARC1: Thread not mounted\r\nARC2: Becoming the heartbeat ARCH\r\nARC2: Thread not mounted\r\nTue Jun 10 03:03:43 2014\r\nSuccessful mount of redo thread 2, with mount id 728394567\r\nAllocated 3981120 bytes in shared pool for flashback generation buffer\r\nStarting background process RVWR\r\nTue Jun 10 03:03:43 2014\r\nRVWR started with pid=38, OS id=14586\r\nPhysical Standby Database mounted.\r\nLost write protection disabled\r\nARC2: Becoming the active heartbeat ARCH\r\nARC2: Becoming the active heartbeat ARCH\r\nARC3: Archival started\r\nARC0: STARTING ARCH PROCESSES COMPLETE\r\nCompleted: alter database  mount\r\nTue Jun 10 03:03:47 2014\r\nStarting Data Guard Broker (DMON)<\/strong>\r\nTue Jun 10 03:03:47 2014\r\nINSV started with pid=40, OS id=14604\r\nTue Jun 10 03:03:50 2014\r\nUsing STANDBY_ARCHIVE_DEST parameter default value as USE_DB_RECOVERY_FILE_DEST\r\nTue Jun 10 03:03:52 2014\r\nNSV0 started with pid=43, OS id=14622\r\nTue Jun 10 03:03:52 2014\r\nPrimary database is in MAXIMUM AVAILABILITY mode<\/strong>\r\nChanging standby controlfile to RESYNCHRONIZATION level\r\nStandby controlfile consistent with primary\r\nRFS[1]: Assigned to RFS process 14624\r\nRFS[1]: Selected log 8 for thread 2 sequence 169 dbid 722024964 branch 847284763\r\nTue Jun 10 03:03:54 2014\r\nPrimary database is in MAXIMUM AVAILABILITY mode\r\nStandby controlfile consistent with primary\r\nStandby controlfile consistent with primary\r\nRFS[2]: Assigned to RFS process 14626\r\nRFS[2]: Selected log 5 for thread 1 sequence 190 dbid 722024964 branch 847284763\r\nTue Jun 10 03:03:58 2014\r\nRFS[3]: Assigned to RFS process 14628\r\nRFS[3]: Opened log for thread 2 sequence 164 dbid 722024964 branch 847284763\r\nTue Jun 10 03:03:58 2014\r\nRFS[4]: Assigned to RFS process 14630\r\nRFS[4]: Opened log for thread 2 sequence 165 dbid 722024964 branch 847284763\r\nTue Jun 10 03:04:01 2014\r\nRFS[5]: Assigned to RFS process 14606\r\nRFS[5]: Opened log for thread 1 sequence 187 dbid 722024964 branch 847284763\r\nTue Jun 10 03:04:01 2014\r\nRFS[6]: Assigned to RFS process 14612\r\nRFS[6]: Opened log for thread 2 sequence 166 dbid 722024964 branch 847284763\r\nArchived Log entry 1025 added for thread 2 sequence 165 rlc 847284763 ID 0x0 dest 2:\r\nTue Jun 10 03:04:01 2014\r\nRFS[7]: Assigned to RFS process 14632\r\nRFS[7]: Opened log for thread 1 sequence 188 dbid 722024964 branch 847284763\r\nArchived Log entry 1026 added for thread 2 sequence 164 rlc 847284763 ID 0x0 dest 2:\r\nRFS[4]: Opened log for thread 2 sequence 167 dbid 722024964 branch 847284763\r\nRFS[3]: Opened log for thread 2 sequence 168 dbid 722024964 branch 847284763\r\nArchived Log entry 1027 added for thread 1 sequence 187 rlc 847284763 ID 0x2b64d2eb dest 2:\r\nArchived Log entry 1028 added for thread 2 sequence 166 rlc 847284763 ID 0x2b64d2eb dest 2:\r\nArchived Log entry 1029 added for thread 1 sequence 188 rlc 847284763 ID 0x2b64d2eb dest 2:\r\nTue Jun 10 03:04:03 2014\r\nRSM0 started with pid=54, OS id=14652\r\nRFS[5]: Opened log for thread 1 sequence 189 dbid 722024964 branch 847284763\r\nArchived Log entry 1030 added for thread 2 sequence 167 rlc 847284763 ID 0x2b64d2eb dest 2:\r\nArchived Log entry 1031 added for thread 2 sequence 168 rlc 847284763 ID 0x2b64d2eb dest 2:\r\nArchived Log entry 1032 added for thread 1 sequence 189 rlc 847284763 ID 0x2b64d2eb dest 2:\r\nTue Jun 10 03:04:07 2014\r\nChanging standby controlfile to MAXIMUM AVAILABILITY level<\/strong>\r\nALTER SYSTEM SET log_archive_dest_state_1='ENABLE' SCOPE=BOTH;\r\nALTER SYSTEM SET log_archive_trace=0 SCOPE=BOTH SID='maastb2';\r\nALTER SYSTEM SET log_archive_format='arch_%t_%s_%r.arc' SCOPE=SPFILE SID='maastb2';\r\nRFS[2]: Selected log 6 for thread 1 sequence 191 dbid 722024964 branch 847284763\r\nALTER SYSTEM SET standby_file_management='AUTO' SCOPE=BOTH SID='*';\r\nALTER SYSTEM SET archive_lag_target=0 SCOPE=BOTH SID='*';\r\nTue Jun 10 03:04:08 2014\r\nALTER SYSTEM SET log_archive_max_processes=4 SCOPE=BOTH SID='*';Archived Log entry 1033 added for thread 1 sequence 190 ID 0x2b64d2eb dest 1:\r\nALTER SYSTEM SET log_archive_min_succeed_dest=1 SCOPE=BOTH SID='*';\r\nALTER SYSTEM SET db_file_name_convert='+DATA\/maa','+DG01\/maastb','+FRA\/maa','+FRA\/maastb' SCOPE=SPFILE;\r\nALTER SYSTEM SET log_file_name_convert='+DATA\/maa','+DG01\/maastb','+FRA\/maa','+FRA\/maastb' SCOPE=SPFILE;\r\nALTER SYSTEM SET fal_server='maa' SCOPE=BOTH;\r\nALTER DATABASE RECOVER MANAGED STANDBY DATABASE  THROUGH ALL SWITCHOVER DISCONNECT  USING CURRENT LOGFILE\r\nAttempt to start background Managed Standby Recovery process (maastb2)\r\nTue Jun 10 03:04:08 2014\r\nMRP0 started with pid=55, OS id=14655\r\nMRP0: Background Managed Standby Recovery process started (maastb2)\r\nTue Jun 10 03:04:09 2014\r\nStandby controlfile consistent with primary<\/strong>\r\nRFS[1]: Selected log 9 for thread 2 sequence 170 dbid 722024964 branch 847284763\r\nTue Jun 10 03:04:09 2014\r\nArchived Log entry 1034 added for thread 2 sequence 169 ID 0x2b64d2eb dest 1:\r\n started logmerger process\r\nTue Jun 10 03:04:13 2014\r\nManaged Standby Recovery starting Real Time Apply\r\nParallel Media Recovery started with 2 slaves\r\nWaiting for all non-current ORLs to be archived...\r\nAll non-current ORLs have been archived.\r\nClearing online redo logfile 1 +DG01\/maastb\/onlinelog\/group_1.257.844716051\r\nClearing online log 1 of thread 1 sequence number 190\r\nTue Jun 10 03:04:15 2014\r\nCompleted: ALTER DATABASE RECOVER MANAGED STANDBY DATABASE  THROUGH ALL SWITCHOVER DISCONNECT  USING CURRENT LOGFILE<\/strong>\r\nTue Jun 10 03:04:21 2014\r\nStandby controlfile consistent with primary\r\nRFS[1]: Selected log 8 for thread 2 sequence 171 dbid 722024964 branch 847284763\r\nTue Jun 10 03:04:21 2014\r\nClearing online redo logfile 1 complete\r\nClearing online redo logfile 2 +DG01\/maastb\/onlinelog\/group_2.268.844716057\r\nTue Jun 10 03:04:21 2014\r\nArchived Log entry 1035 added for thread 2 sequence 170 ID 0x2b64d2eb dest 1:\r\nClearing online log 2 of thread 1 sequence number 191\r\nTue Jun 10 03:04:24 2014\r\nStandby controlfile consistent with primary\r\nRFS[2]: Selected log 5 for thread 1 sequence 192 dbid 722024964 branch 847284763\r\nTue Jun 10 03:04:25 2014\r\nArchived Log entry 1036 added for thread 1 sequence 191 ID 0x2b64d2eb dest 1:\r\nClearing online redo logfile 2 complete\r\nClearing online redo logfile 3 +DG01\/maastb\/onlinelog\/group_3.269.844716063\r\nClearing online log 3 of thread 2 sequence number 171\r\nTue Jun 10 03:04:35 2014\r\nClearing online redo logfile 3 complete\r\nClearing online redo logfile 4 +DG01\/maastb\/onlinelog\/group_4.270.844716067\r\nClearing online log 4 of thread 2 sequence number 171\r\nClearing online redo logfile 4 complete\r\nTue Jun 10 03:04:42 2014\r\nMedia Recovery Log +FRA\/maastb\/archivelog\/2014_06_10\/thread_2_seq_162.709.849841395\r\nMedia Recovery Log +FRA\/maastb\/archivelog\/2014_06_09\/thread_1_seq_183.717.849834887\r\nTue Jun 10 03:04:45 2014\r\nReconfiguration started (old inc 2, new inc 4)\r\nList of instances:\r\n 1 2 (myinst: 2)<\/strong>\r\n Global Resource Directory frozen\r\n Communication channels reestablished\r\nTue Jun 10 03:04:45 2014\r\n * domain 0 valid = 0 according to instance 1\r\n Master broadcasted resource hash value bitmaps\r\n Non-local Process blocks cleaned out\r\nTue Jun 10 03:04:45 2014\r\n LMS 0: 0 GCS shadows cancelled, 0 closed, 0 Xw survived\r\n Set master node info\r\n Submitted all remote-enqueue requests\r\n Dwn-cvts replayed, VALBLKs dubious\r\n All grantable enqueues granted\r\n Post SMON to start 1st pass IR\r\n Submitted all GCS remote-cache requests\r\n Post SMON to start 1st pass IR\r\n Fix write in gcs resources\r\nReconfiguration complete\r\nMedia Recovery Log +FRA\/maastb\/archivelog\/2014_06_09\/thread_1_seq_184.713.849834919\r\nTue Jun 10 03:04:56 2014\r\nMedia Recovery Log +FRA\/maastb\/archivelog\/2014_06_10\/thread_1_seq_185.710.849841391\r\nMedia Recovery Log +FRA\/maastb\/archivelog\/2014_06_10\/thread_1_seq_186.707.849841395\r\nMedia Recovery Log +FRA\/maastb\/archivelog\/2014_06_10\/thread_2_seq_163.706.849841397\r\nIdentified End-Of-Redo (switchover) for thread 2 sequence 163 at SCN 0x0.aff3c1\r\nResetting standby activation ID 0 (0x0)\r\nTue Jun 10 03:05:07 2014\r\nMedia Recovery End-Of-Redo indicator encountered<\/strong>\r\nMedia Recovery Continuing<\/strong>\r\nMedia Recovery Log +FRA\/maastb\/archivelog\/2014_06_10\/thread_2_seq_164.704.849841439\r\nMedia Recovery Log +FRA\/maastb\/archivelog\/2014_06_10\/thread_2_seq_165.702.849841439\r\nMedia Recovery Log +FRA\/maastb\/archivelog\/2014_06_10\/thread_1_seq_187.700.849841441\r\nMedia Recovery Log +FRA\/maastb\/archivelog\/2014_06_10\/thread_2_seq_166.696.849841441\r\nMedia Recovery Log +FRA\/maastb\/archivelog\/2014_06_10\/thread_1_seq_188.481.849841441\r\nMedia Recovery Log +FRA\/maastb\/archivelog\/2014_06_10\/thread_2_seq_167.693.849841443\r\nTue Jun 10 03:05:20 2014\r\nMedia Recovery Log +FRA\/maastb\/archivelog\/2014_06_10\/thread_2_seq_168.691.849841443\r\nMedia Recovery Log +FRA\/maastb\/archivelog\/2014_06_10\/thread_1_seq_189.689.849841443\r\nMedia Recovery Log +FRA\/maastb\/archivelog\/2014_06_10\/thread_2_seq_169.444.849841449\r\nMedia Recovery Log +FRA\/maastb\/archivelog\/2014_06_10\/thread_1_seq_190.685.849841447\r\nTue Jun 10 03:05:31 2014\r\nMedia Recovery Log +FRA\/maastb\/archivelog\/2014_06_10\/thread_1_seq_191.681.849841465\r\nMedia Recovery Log +FRA\/maastb\/archivelog\/2014_06_10\/thread_2_seq_170.682.849841461\r\nMedia Recovery Waiting for thread 2 sequence 171 (in transit)\r\nRecovery of Online Redo Log: Thread 2 Group 8 Seq 171 Reading mem 0\r\n  Mem# 0: +DG01\/maastb\/onlinelog\/group_8.261.844716089\r\n  Mem# 1: +FRA\/maastb\/onlinelog\/group_8.611.844716093\r\nMedia Recovery Waiting for thread 1 sequence 192 (in transit)\r\nRecovery of Online Redo Log: Thread 1 Group 5 Seq 192 Reading mem 0\r\n  Mem# 0: +DG01\/maastb\/onlinelog\/group_5.271.844716073\r\n  Mem# 1: +FRA\/maastb\/onlinelog\/group_5.553.844716075\r\n<\/pre>\n
Acima temos alguns detalhes interessantes, come\u00e7ou com um o startup de uma inst\u00e2ncia do banco maastb mas neste caso o banco j\u00e1 inicia e fica comente em modo mount.\u00a0 Depois disso o processo do Broker inicializa e seta v\u00e1rios par\u00e2metros, detecta o modo que o primary opera. Por fim, o novo standby inicia a sincroniza\u00e7\u00e3o de redo\u2019s e efetivamente come\u00e7a a operar com um physical standby. Os redo\u2019s s\u00e3o aplicados (incluindo o End-Of-Redo) e tudo fica sincronizado.<\/p>\n
Se voc\u00ea notou acima, durante o processo de startup (ap\u00f3s o comando do switchover) a outra inst\u00e2ncia foi inciada. Isso ocorre pois o Broker deixa iniciada todas as inst\u00e2ncias que comp\u00f5em o Oracle RAC do standby. Abaixo temos o alertlog desta outra inst\u00e2ncia do cluster, basicamente comandos simples (um simples mount), pois o servi\u00e7o pesado j\u00e1 foi feito pela primeria inst\u00e2ncia que iniciou:<\/p>\n
Tue Jun 10 03:03:00 2014\r\nInstance shutdown complete\r\nTue Jun 10 03:04:35 2014\r\nStarting ORACLE instance (normal)\r\n****************** Large Pages Information *****************\r\n\r\nTotal Shared Global Region in Large Pages = 0 KB (0%)\r\n\r\nLarge Pages used by this instance: 0 (0 KB)\r\nLarge Pages unused system wide = 0 (0 KB) (alloc incr 4096 KB)\r\nLarge Pages configured system wide = 0 (0 KB)\r\nLarge Page size = 2048 KB\r\n\r\nRECOMMENDATION:\r\n  Total Shared Global Region size is 1026 MB. For optimal performance,\r\n  prior to the next instance restart increase the number\r\n  of unused Large Pages by atleast 513 2048 KB Large Pages (1026 MB)\r\n  system wide to get 100% of the Shared\r\n  Global Region allocated with Large pages\r\n***********************************************************\r\nLICENSE_MAX_SESSION = 0\r\nLICENSE_SESSIONS_WARNING = 0\r\nPrivate Interface 'eth2:1' configured from GPnP for use as a private interconnect.\r\n  [name='eth2:1', type=1, ip=169.254.172.112, mac=00-0c-29-3a-65-3a, net=169.254.0.0\/16, mask=255.255.0.0, use=haip:cluster_interconnect\/62]\r\nPublic Interface 'eth0' configured from GPnP for use as a public interface.\r\n  [name='eth0', type=1, ip=10.17.42.48, mac=00-0c-29-3a-65-26, net=10.17.42.0\/26, mask=255.255.255.192, use=public\/1]\r\nPublic Interface 'eth0:1' configured from GPnP for use as a public interface.\r\n  [name='eth0:1', type=1, ip=10.17.42.52, mac=00-0c-29-3a-65-26, net=10.17.42.0\/26, mask=255.255.255.192, use=public\/1]\r\nPublic Interface 'eth0:2' configured from GPnP for use as a public interface.\r\n  [name='eth0:2', type=1, ip=10.17.42.35, mac=00-0c-29-3a-65-26, net=10.17.42.0\/26, mask=255.255.255.192, use=public\/1]\r\nPicked latch-free SCN scheme 3\r\nAutotune of undo retention is turned on.\r\nLICENSE_MAX_USERS = 0\r\nSYS auditing is disabled\r\nStarting up:\r\nOracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production\r\nWith the Partitioning, Real Application Clusters and Real Application Testing options.\r\nORACLE_HOME = \/u01\/app\/oracle\/product\/11.2.0.3\/db_1\r\nSystem name:    Linux\r\nNode name:      rac11stb01.tjsc.jus.br\r\nRelease:        2.6.39-400.17.1.el6uek.x86_64\r\nVersion:        #1 SMP Fri Feb 22 18:16:18 PST 2013\r\nMachine:        x86_64\r\nVM name:        VMWare Version: 6\r\nUsing parameter settings in server-side pfile \/u01\/app\/oracle\/product\/11.2.0.3\/db_1\/dbs\/initmaastb1.ora\r\nSystem parameters with non-default values:\r\n  processes                = 150\r\n  spfile                   = \"+DG01\/maastb\/spfilemaastb.ora\"\r\n  sga_target               = 1G\r\n  control_files            = \"+DG01\/maastb\/controlfile\/current.273.844715953\"\r\n  control_files            = \"+FRA\/maastb\/controlfile\/current.579.844715953\"\r\n  db_file_name_convert     = \"+DATA\/maa\"\r\n  db_file_name_convert     = \"+DG01\/maastb\"\r\n  db_file_name_convert     = \"+FRA\/maa\"\r\n  db_file_name_convert     = \"+FRA\/maastb\"\r\n  log_file_name_convert    = \"+DATA\/maa\"\r\n  log_file_name_convert    = \"+DG01\/maastb\"\r\n  log_file_name_convert    = \"+FRA\/maa\"\r\n  log_file_name_convert    = \"+FRA\/maastb\"\r\n  db_block_size            = 8192\r\n  compatible               = \"11.2.0.0.0\"\r\n  log_archive_dest_1       = \"LOCATION=USE_DB_RECOVERY_FILE_DEST VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=maastb\"\r\n  log_archive_dest_2       = \"service=\"maa\"\"\r\n  log_archive_dest_2       = \"LGWR SYNC AFFIRM delay=0 optional compression=disable max_failure=0 max_connections=1 reopen=300 db_unique_name=\"maa\" net_timeout=30\"\r\n  log_archive_dest_2       = \"valid_for=(all_logfiles,primary_role)\"\r\n  log_archive_dest_state_1 = \"ENABLE\"\r\n  log_archive_dest_state_2 = \"ENABLE\"\r\n  log_archive_min_succeed_dest= 1\r\n  fal_server               = \"maa\"\r\n  log_archive_trace        = 0\r\n  log_archive_config       = \"DG_CONFIG=(maa,maastb)\"\r\n  log_archive_format       = \"arch_%t_%s_%r.arc\"\r\n  log_archive_max_processes= 4\r\n  archive_lag_target       = 0\r\n  cluster_database         = TRUE\r\n  db_create_file_dest      = \"+DG01\"\r\n  db_recovery_file_dest    = \"+FRA\"\r\n  db_recovery_file_dest_size= 10G\r\n  standby_file_management  = \"AUTO\"\r\n  thread                   = 1\r\n  undo_tablespace          = \"UNDOTBS1\"\r\n  instance_number          = 1\r\n  remote_login_passwordfile= \"EXCLUSIVE\"\r\n  db_domain                = \"\"\r\n  remote_listener          = \"rac11stb-scan.tjsc.jus.br:1521\"\r\n  audit_file_dest          = \"\/u01\/app\/oracle\/admin\/maastb\/adump\"\r\n  audit_trail              = \"DB\"\r\n  db_name                  = \"maa\"\r\n  db_unique_name           = \"maastb\"\r\n  open_cursors             = 300\r\n  pga_aggregate_target     = 256M\r\n  dg_broker_start          = TRUE\r\n  dg_broker_config_file1   = \"+DG01\/maastb\/dr1maastb.dat\"\r\n  dg_broker_config_file2   = \"+FRA\/maastb\/dr2maastb.dat\"\r\n  diagnostic_dest          = \"\/u01\/app\/oracle\"\r\nCluster communication is configured to use the following interface(s) for this instance\r\n  169.254.172.112\r\ncluster interconnect IPC version:Oracle UDP\/IP (generic)\r\nIPC Vendor 1 proto 2\r\nTue Jun 10 03:04:41 2014\r\nPMON started with pid=2, OS id=29428\r\nTue Jun 10 03:04:41 2014\r\nPSP0 started with pid=3, OS id=29430\r\nTue Jun 10 03:04:42 2014\r\nVKTM started with pid=4, OS id=29432 at elevated priority\r\nVKTM running at (1)millisec precision with DBRM quantum (100)ms\r\nTue Jun 10 03:04:42 2014\r\nGEN0 started with pid=5, OS id=29436\r\nTue Jun 10 03:04:42 2014\r\nDIAG started with pid=6, OS id=29438\r\nTue Jun 10 03:04:42 2014\r\nDBRM started with pid=7, OS id=29440\r\nTue Jun 10 03:04:43 2014\r\nPING started with pid=8, OS id=29442\r\nTue Jun 10 03:04:43 2014\r\nACMS started with pid=9, OS id=29444\r\nTue Jun 10 03:04:43 2014\r\nDIA0 started with pid=10, OS id=29446\r\nTue Jun 10 03:04:43 2014\r\nLMON started with pid=11, OS id=29448\r\nTue Jun 10 03:04:43 2014\r\nLMD0 started with pid=12, OS id=29450\r\n* Load Monitor used for high load check\r\n* New Low - High Load Threshold Range = [1920 - 2560]\r\nTue Jun 10 03:04:43 2014\r\nLMS0 started with pid=13, OS id=29452 at elevated priority\r\nTue Jun 10 03:04:43 2014\r\nRMS0 started with pid=14, OS id=29456\r\nTue Jun 10 03:04:43 2014\r\nLMHB started with pid=15, OS id=29458\r\nTue Jun 10 03:04:43 2014\r\nMMAN started with pid=16, OS id=29460\r\nTue Jun 10 03:04:43 2014\r\nDBW0 started with pid=17, OS id=29462\r\nTue Jun 10 03:04:43 2014\r\nLGWR started with pid=18, OS id=29464\r\nTue Jun 10 03:04:43 2014\r\nCKPT started with pid=19, OS id=29466\r\nTue Jun 10 03:04:43 2014\r\nSMON started with pid=20, OS id=29468\r\nTue Jun 10 03:04:43 2014\r\nRECO started with pid=21, OS id=29470\r\nTue Jun 10 03:04:43 2014\r\nRBAL started with pid=22, OS id=29472\r\nTue Jun 10 03:04:43 2014\r\nASMB started with pid=23, OS id=29474\r\nTue Jun 10 03:04:43 2014\r\nMMON started with pid=24, OS id=29476\r\nTue Jun 10 03:04:43 2014\r\nMMNL started with pid=25, OS id=29478\r\nlmon registered with NM - instance number 1 (internal mem no 0)\r\nNOTE: initiating MARK startup\r\nStarting background process MARK\r\nTue Jun 10 03:04:44 2014\r\nMARK started with pid=26, OS id=29483\r\nNOTE: MARK has subscribed\r\nReconfiguration started (old inc 0, new inc 4)\r\nList of instances:\r\n 1 2 (myinst: 1)\r\n Global Resource Directory frozen\r\n* allocate domain 0, invalid = TRUE\r\n Communication channels reestablished\r\n * domain 0 not valid according to instance 2\r\n * domain 0 valid = 0 according to instance 2\r\n Master broadcasted resource hash value bitmaps\r\n Non-local Process blocks cleaned out\r\n LMS 0: 0 GCS shadows cancelled, 0 closed, 0 Xw survived\r\n Set master node info\r\n Submitted all remote-enqueue requests\r\n Dwn-cvts replayed, VALBLKs dubious\r\n All grantable enqueues granted\r\n Post SMON to start 1st pass IR\r\n Submitted all GCS remote-cache requests\r\n Post SMON to start 1st pass IR\r\n Fix write in gcs resources\r\nReconfiguration complete\r\nTue Jun 10 03:04:45 2014\r\nLCK0 started with pid=28, OS id=29489\r\nTue Jun 10 03:04:45 2014\r\nStarting background process RSMN\r\nTue Jun 10 03:04:46 2014\r\nRSMN started with pid=29, OS id=29491\r\nORACLE_BASE not set in environment. It is recommended\r\nthat ORACLE_BASE be set in the environment\r\nReusing ORACLE_BASE from an earlier startup = \/u01\/app\/oracle\r\nTue Jun 10 03:04:46 2014\r\nDMON started with pid=30, OS id=29493\r\nTue Jun 10 03:04:47 2014\r\nALTER SYSTEM SET local_listener='(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=10.17.42.52)(PORT=1521))))' SCOPE=MEMORY SID='maastb1';\r\nALTER DATABASE MOUNT \/* db agent *\/\/* {2:12604:3042} *\/\r\nNOTE: Loaded library: \/opt\/oracle\/extapi\/64\/asm\/orcl\/1\/libasm.so\r\nNOTE: Loaded library: System\r\nSUCCESS: diskgroup DG01 was mounted\r\nNOTE: dependency between database maastb and diskgroup resource ora.DG01.dg is established\r\nSUCCESS: diskgroup FRA was mounted\r\nNOTE: dependency between database maastb and diskgroup resource ora.FRA.dg is established\r\nARCH: STARTING ARCH PROCESSES\r\nTue Jun 10 03:04:53 2014\r\nNSS2 started with pid=33, OS id=29514\r\nTue Jun 10 03:04:53 2014\r\nARC0 started with pid=34, OS id=29516\r\nARC0: Archival started\r\nARCH: STARTING ARCH PROCESSES COMPLETE\r\nARC0: STARTING ARCH PROCESSES\r\nTue Jun 10 03:04:54 2014\r\nARC1 started with pid=35, OS id=29521\r\nTue Jun 10 03:04:54 2014\r\nARC2 started with pid=36, OS id=29523\r\nTue Jun 10 03:04:54 2014\r\nARC3 started with pid=37, OS id=29525\r\nARC1: Archival started\r\nARC2: Archival started\r\nARC2: Becoming the 'no FAL' ARCH\r\nARC2: Becoming the 'no SRL' ARCH\r\nARC2: Thread not mounted\r\nARC1: Becoming the heartbeat ARCH\r\nTue Jun 10 03:04:54 2014\r\nSuccessful mount of redo thread 1, with mount id 728394567\r\nAllocated 3981120 bytes in shared pool for flashback generation buffer\r\nStarting background process RVWR\r\nTue Jun 10 03:04:54 2014\r\nRVWR started with pid=38, OS id=29527\r\nARC3: Archival started\r\nARC0: STARTING ARCH PROCESSES COMPLETE\r\nPhysical Standby Database mounted.\r\nLost write protection disabled\r\nCompleted: ALTER DATABASE MOUNT \/* db agent *\/\/* {2:12604:3042} *\/\r\nTue Jun 10 03:04:59 2014\r\nStarting Data Guard Broker (DMON)\r\nTue Jun 10 03:04:59 2014\r\nINSV started with pid=41, OS id=29542\r\nTue Jun 10 03:05:03 2014\r\nNSV0 started with pid=40, OS id=29552\r\nTue Jun 10 03:05:11 2014\r\nRSM0 started with pid=44, OS id=29558\r\nUsing STANDBY_ARCHIVE_DEST parameter default value as USE_DB_RECOVERY_FILE_DEST\r\nALTER SYSTEM SET log_archive_trace=0 SCOPE=BOTH SID='maastb1';\r\nALTER SYSTEM SET log_archive_format='arch_%t_%s_%r.arc' SCOPE=SPFILE SID='maastb1';\r\n<\/pre>\n
De forma simples e com um \u00fanico comando o switchover foi realizado atrav\u00e9s do Broker. Comparando com o artigo anterior sobre switchover os passos foram mais simples, mas claro que dependenmos de um Broker configurado e de uma sincronia entre as primary e standby operando em plenitude.<\/p>\n
Status do ambiente #2<\/strong><\/p>\n
Como visto acima a troca de papeis entre o primary e standby foi conclu\u00edda com sucesso. Observe abaixo no Broker que a sincronia entre eles est\u00e1 correta e que n\u00e3o existe nenhum gap entre eles:<\/p>\n
DGMGRL> SHOW CONFIGURATION;\r\n\r\nConfiguration - dgrac\r\n\r\n  Protection Mode: MaxAvailability\r\n  Databases:\r\n\tmaa    - Primary database\r\n\tmaastb - Physical standby database\r\n\r\nFast-Start Failover: DISABLED\r\n\r\nConfiguration Status:\r\nSUCCESS\r\n\r\nDGMGRL>\r\nDGMGRL> SHOW DATABASE maa;\r\n\r\nDatabase - maa\r\n\r\n  Role:            PRIMARY\r\n  Intended State:  TRANSPORT-ON\r\n  Instance(s):\r\n\tmaa1\r\n\tmaa2\r\n\r\nDatabase Status:\r\nSUCCESS\r\n\r\nDGMGRL>\r\nDGMGRL> SHOW DATABASE maa LogXptStatus;\r\nLOG TRANSPORT STATUS\r\nPRIMARY_INSTANCE_NAME STANDBY_DATABASE_NAME               STATUS\r\n\t\t\t\tmaa1               maastb\r\n\t\t\t\tmaa2               maastb\r\n\r\nDGMGRL> \r\n<\/pre>\n
Na nossa tabela de controle (observe o hostname):<\/p>\n
[oracle@rac11pri01 ~]$ sqlplus \/ as sysdba\r\n\r\nSQL*Plus: Release 11.2.0.3.0 Production on Tue Jun 10 00:34:53 2014\r\n\r\nCopyright (c) 1982, 2011, Oracle.  All rights reserved.\r\n\r\n\r\nConnected to:\r\nOracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production\r\nWith the Partitioning, Real Application Clusters and Automatic Storage Management options\r\n\r\nSQL> SELECT * FROM testedg;\r\n\r\nno rows selected\r\n\r\nSQL>\r\n<\/pre>\n
AMBIENTE FINAL<\/strong><\/p>\n
Acredito que tenha ficado claro que atrav\u00e9s do Broker a troca de papeis pelo switchover foi bem mais simples. Com um \u00fanico comando ocorreu a troca sem que tiv\u00e9ssemos que executar manualmente o \u201ccancel\u201d da sincronia e \u201cabort\u201d das bases. Indo al\u00e9m, n\u00e3o nos preocupamos com nada, o Broker fez tudo por n\u00f3s.<\/p>\n
Claro que nem tudo s\u00e3o flores, o Broker n\u00e3o corrigiu o CRS completamente, o novo primary ainda est\u00e1 definido para subir em modo mount e o novo standby aparece no CRS para ficar em open. J\u00e1 corrigimos isso em outros artigos, mas os passo seriam (na primary):<\/p>\n
[oracle@rac11pri01 ~]$ srvctl config database -d maa -v\r\nDatabase unique name: maa\r\nDatabase name: maa\r\nOracle home: \/u01\/app\/oracle\/product\/11.2.0.3\/db_1\r\nOracle user: oracle\r\nSpfile: +DATA\/maa\/spfilemaa.ora\r\nDomain:\r\nStart options: mount\r\nStop options: immediate\r\nDatabase role: PRIMARY\r\nManagement policy: AUTOMATIC\r\nServer pools: maa\r\nDatabase instances: maa1,maa2\r\nDisk Groups: DATA,FRA\r\nMount point paths:\r\nServices:\r\nType: RAC\r\nDatabase is administrator managed\r\n[oracle@rac11pri01 ~]$\r\n[oracle@rac11pri01 ~]$\r\n[oracle@rac11pri01 ~]$\r\n[oracle@rac11pri01 ~]$ srvctl modify database -d maa -s OPEN\r\n[oracle@rac11pri01 ~]$\r\n[oracle@rac11pri01 ~]$\r\n[oracle@rac11pri01 ~]$ srvctl config database -d maa -v\r\nDatabase unique name: maa\r\nDatabase name: maa\r\nOracle home: \/u01\/app\/oracle\/product\/11.2.0.3\/db_1\r\nOracle user: oracle\r\nSpfile: +DATA\/maa\/spfilemaa.ora\r\nDomain:\r\nStart options: open\r\nStop options: immediate\r\nDatabase role: PRIMARY\r\nManagement policy: AUTOMATIC\r\nServer pools: maa\r\nDatabase instances: maa1,maa2\r\nDisk Groups: DATA,FRA\r\nMount point paths:\r\nServices:\r\nType: RAC\r\nDatabase is administrator managed\r\n[oracle@rac11pri01 ~]$\r\n<\/pre>\n
E no standby:<\/p>\n
[oracle@rac11stb01 ~]$ srvctl config database -d maastb -v\r\nDatabase unique name: maastb\r\nDatabase name:\r\nOracle home: \/u01\/app\/oracle\/product\/11.2.0.3\/db_1\r\nOracle user: oracle\r\nSpfile:\r\nDomain:\r\nStart options: open\r\nStop options: immediate\r\nDatabase role: PHYSICAL_STANDBY\r\nManagement policy: AUTOMATIC\r\nServer pools: maastb\r\nDatabase instances: maastb1,maastb2\r\nDisk Groups: DG01,FRA\r\nMount point paths:\r\nServices:\r\nType: RAC\r\nDatabase is administrator managed\r\n[oracle@rac11stb01 ~]$\r\n[oracle@rac11stb01 ~]$\r\n[oracle@rac11stb01 ~]$ srvctl modify database -d maastb -s MOUNT\r\n[oracle@rac11stb01 ~]$\r\n[oracle@rac11stb01 ~]$\r\n[oracle@rac11stb01 ~]$ srvctl config database -d maastb -v\r\nDatabase unique name: maastb\r\nDatabase name:\r\nOracle home: \/u01\/app\/oracle\/product\/11.2.0.3\/db_1\r\nOracle user: oracle\r\nSpfile:\r\nDomain:\r\nStart options: mount\r\nStop options: immediate\r\nDatabase role: PHYSICAL_STANDBY\r\nManagement policy: AUTOMATIC\r\nServer pools: maastb\r\nDatabase instances: maastb1,maastb2\r\nDisk Groups: DG01,FRA\r\nMount point paths:\r\nServices:\r\nType: RAC\r\nDatabase is administrator managed\r\n[oracle@rac11stb01 ~]$\r\n<\/pre>\n
\n","protected":false},"excerpt":{"rendered":"
Seguindo uma ordem cronol\u00f3gica dos artigos sobre Oracle RAC e MAA vamos fazer um switchover usando o Broker. Em um ambiente de produ\u00e7\u00e3o voc\u00ea n\u00e3o seguiria esta ordem de eventos, mas para fins did\u00e1ticos \u00e9 interessante observar os passos. No \u00faltimo artigo \u201cfor\u00e7amos\u201d um failover do ambiente, o banco \u201cmaa\u201d que rodava como primary sofreu […]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"ngg_post_thumbnail":0,"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":false,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2}},"categories":[30,50,41,29,6,5,49],"tags":[],"class_list":["post-163","post","type-post","status-publish","format-standard","hentry","category-banco-de-dados","category-broker","category-data-guard","category-database","category-exadata","category-oracle","category-switchover"],"yoast_head":"\nOracle e MAA \u2013 Artigo VII \u2013 Switchover Broker<\/title>\n<meta name=\"description\" content=\"Realizando o Switchover com o Broker em um ambiente Oracle com Maximum Availability Architecture (MAA), Data Guard (DG) e RAC. Dicas, detalhes e truques\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.fernandosimon.com\/blog\/oracle-e-maa-artigo-vii-switchover-broker\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Oracle e MAA \u2013 Artigo VII \u2013 Switchover Broker\" \/>\n<meta property=\"og:description\" content=\"Realizando o Switchover com o Broker em um ambiente Oracle com Maximum Availability Architecture (MAA), Data Guard (DG) e RAC. Dicas, detalhes e truques\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.fernandosimon.com\/blog\/oracle-e-maa-artigo-vii-switchover-broker\/\" \/>\n<meta property=\"og:site_name\" content=\"Fernando Simon\" \/>\n<meta property=\"article:published_time\" content=\"2014-09-07T21:27:16+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2015-01-26T02:28:51+00:00\" \/>\n<meta name=\"author\" content=\"Simon\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Simon\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"45 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/www.fernandosimon.com\/blog\/oracle-e-maa-artigo-vii-switchover-broker\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.fernandosimon.com\/blog\/oracle-e-maa-artigo-vii-switchover-broker\/\"},\"author\":{\"name\":\"Simon\",\"@id\":\"https:\/\/www.fernandosimon.com\/blog\/#\/schema\/person\/386da956604bca0d5be5dd52210c1dd9\"},\"headline\":\"Oracle e MAA \u2013 Artigo VII \u2013 Switchover Broker\",\"datePublished\":\"2014-09-07T21:27:16+00:00\",\"dateModified\":\"2015-01-26T02:28:51+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.fernandosimon.com\/blog\/oracle-e-maa-artigo-vii-switchover-broker\/\"},\"wordCount\":1732,\"commentCount\":2,\"articleSection\":[\"Banco de Dados\",\"Broker\",\"Data Guard\",\"Database\",\"Exadata\",\"Oracle\",\"Switchover\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/www.fernandosimon.com\/blog\/oracle-e-maa-artigo-vii-switchover-broker\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.fernandosimon.com\/blog\/oracle-e-maa-artigo-vii-switchover-broker\/\",\"url\":\"https:\/\/www.fernandosimon.com\/blog\/oracle-e-maa-artigo-vii-switchover-broker\/\",\"name\":\"Oracle e MAA \u2013 Artigo VII \u2013 Switchover Broker\",\"isPartOf\":{\"@id\":\"https:\/\/www.fernandosimon.com\/blog\/#website\"},\"datePublished\":\"2014-09-07T21:27:16+00:00\",\"dateModified\":\"2015-01-26T02:28:51+00:00\",\"author\":{\"@id\":\"https:\/\/www.fernandosimon.com\/blog\/#\/schema\/person\/386da956604bca0d5be5dd52210c1dd9\"},\"description\":\"Realizando o Switchover com o Broker em um ambiente Oracle com Maximum Availability Architecture (MAA), Data Guard (DG) e RAC. Dicas, detalhes e truques\",\"breadcrumb\":{\"@id\":\"https:\/\/www.fernandosimon.com\/blog\/oracle-e-maa-artigo-vii-switchover-broker\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.fernandosimon.com\/blog\/oracle-e-maa-artigo-vii-switchover-broker\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.fernandosimon.com\/blog\/oracle-e-maa-artigo-vii-switchover-broker\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/www.fernandosimon.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Oracle e MAA \u2013 Artigo VII \u2013 Switchover Broker\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/www.fernandosimon.com\/blog\/#website\",\"url\":\"https:\/\/www.fernandosimon.com\/blog\/\",\"name\":\"Fernando Simon\",\"description\":\"Have you hugged your backup today?\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/www.fernandosimon.com\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/www.fernandosimon.com\/blog\/#\/schema\/person\/386da956604bca0d5be5dd52210c1dd9\",\"name\":\"Simon\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.fernandosimon.com\/blog\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/a3dbc48de62fffb1829befb4a588d789ec6dc5e05977afabb3407a5f37a16482?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/a3dbc48de62fffb1829befb4a588d789ec6dc5e05977afabb3407a5f37a16482?s=96&d=mm&r=g\",\"caption\":\"Simon\"},\"sameAs\":[\"http:\/\/www.fernandosimon.com\"],\"url\":\"https:\/\/www.fernandosimon.com\/blog\/author\/simon\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Oracle e MAA \u2013 Artigo VII \u2013 Switchover Broker","description":"Realizando o Switchover com o Broker em um ambiente Oracle com Maximum Availability Architecture (MAA), Data Guard (DG) e RAC. Dicas, detalhes e truques","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.fernandosimon.com\/blog\/oracle-e-maa-artigo-vii-switchover-broker\/","og_locale":"en_US","og_type":"article","og_title":"Oracle e MAA \u2013 Artigo VII \u2013 Switchover Broker","og_description":"Realizando o Switchover com o Broker em um ambiente Oracle com Maximum Availability Architecture (MAA), Data Guard (DG) e RAC. Dicas, detalhes e truques","og_url":"https:\/\/www.fernandosimon.com\/blog\/oracle-e-maa-artigo-vii-switchover-broker\/","og_site_name":"Fernando Simon","article_published_time":"2014-09-07T21:27:16+00:00","article_modified_time":"2015-01-26T02:28:51+00:00","author":"Simon","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Simon","Est. reading time":"45 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.fernandosimon.com\/blog\/oracle-e-maa-artigo-vii-switchover-broker\/#article","isPartOf":{"@id":"https:\/\/www.fernandosimon.com\/blog\/oracle-e-maa-artigo-vii-switchover-broker\/"},"author":{"name":"Simon","@id":"https:\/\/www.fernandosimon.com\/blog\/#\/schema\/person\/386da956604bca0d5be5dd52210c1dd9"},"headline":"Oracle e MAA \u2013 Artigo VII \u2013 Switchover Broker","datePublished":"2014-09-07T21:27:16+00:00","dateModified":"2015-01-26T02:28:51+00:00","mainEntityOfPage":{"@id":"https:\/\/www.fernandosimon.com\/blog\/oracle-e-maa-artigo-vii-switchover-broker\/"},"wordCount":1732,"commentCount":2,"articleSection":["Banco de Dados","Broker","Data Guard","Database","Exadata","Oracle","Switchover"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.fernandosimon.com\/blog\/oracle-e-maa-artigo-vii-switchover-broker\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.fernandosimon.com\/blog\/oracle-e-maa-artigo-vii-switchover-broker\/","url":"https:\/\/www.fernandosimon.com\/blog\/oracle-e-maa-artigo-vii-switchover-broker\/","name":"Oracle e MAA \u2013 Artigo VII \u2013 Switchover Broker","isPartOf":{"@id":"https:\/\/www.fernandosimon.com\/blog\/#website"},"datePublished":"2014-09-07T21:27:16+00:00","dateModified":"2015-01-26T02:28:51+00:00","author":{"@id":"https:\/\/www.fernandosimon.com\/blog\/#\/schema\/person\/386da956604bca0d5be5dd52210c1dd9"},"description":"Realizando o Switchover com o Broker em um ambiente Oracle com Maximum Availability Architecture (MAA), Data Guard (DG) e RAC. Dicas, detalhes e truques","breadcrumb":{"@id":"https:\/\/www.fernandosimon.com\/blog\/oracle-e-maa-artigo-vii-switchover-broker\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.fernandosimon.com\/blog\/oracle-e-maa-artigo-vii-switchover-broker\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.fernandosimon.com\/blog\/oracle-e-maa-artigo-vii-switchover-broker\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.fernandosimon.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Oracle e MAA \u2013 Artigo VII \u2013 Switchover Broker"}]},{"@type":"WebSite","@id":"https:\/\/www.fernandosimon.com\/blog\/#website","url":"https:\/\/www.fernandosimon.com\/blog\/","name":"Fernando Simon","description":"Have you hugged your backup today?","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.fernandosimon.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/www.fernandosimon.com\/blog\/#\/schema\/person\/386da956604bca0d5be5dd52210c1dd9","name":"Simon","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.fernandosimon.com\/blog\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/a3dbc48de62fffb1829befb4a588d789ec6dc5e05977afabb3407a5f37a16482?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/a3dbc48de62fffb1829befb4a588d789ec6dc5e05977afabb3407a5f37a16482?s=96&d=mm&r=g","caption":"Simon"},"sameAs":["http:\/\/www.fernandosimon.com"],"url":"https:\/\/www.fernandosimon.com\/blog\/author\/simon\/"}]}},"jetpack_publicize_connections":[],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"jetpack_shortlink":"https:\/\/wp.me\/p5ofTp-2D","_links":{"self":[{"href":"https:\/\/www.fernandosimon.com\/blog\/wp-json\/wp\/v2\/posts\/163","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.fernandosimon.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.fernandosimon.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.fernandosimon.com\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.fernandosimon.com\/blog\/wp-json\/wp\/v2\/comments?post=163"}],"version-history":[{"count":0,"href":"https:\/\/www.fernandosimon.com\/blog\/wp-json\/wp\/v2\/posts\/163\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.fernandosimon.com\/blog\/wp-json\/wp\/v2\/media?parent=163"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.fernandosimon.com\/blog\/wp-json\/wp\/v2\/categories?post=163"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.fernandosimon.com\/blog\/wp-json\/wp\/v2\/tags?post=163"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}