A opera\u00e7\u00e3o de Failover em um ambiente Data Guard \u00e9 a resposta a um evento de falha, ou seja, uma situa\u00e7\u00e3o n\u00e3o planejada, ocorrendo devido indisponibilidade do Primary. Como consequ\u00eancia, o Standby passa a operar como Primary (no modo maximum performance), e caso queiramos mudar esse modo para outro valor, \u00e9 necess\u00e1rio antes realizar o “reinstate” do primary antigo, ou criar um novo standby database.<\/p>\n\n\n\n
Para esse artigo, vamos simular de maneira controlada esse evento. Checando o ambiente primary,standby e que o Redo Apply (por ser um physical standby) est\u00e1 operando normalmente:<\/p>\n\n\n
\n[oracle@fornix1 ~]$ dgmgrl sys\/oracle@CORTEX\nDGMGRL for Linux: Release 19.0.0.0.0 - Production on Tue Apr 20 20:30:39 2021\nVersion 19.3.0.0.0\n \nCopyright (c) 1982, 2019, Oracle and\/or its affiliates. All rights reserved.\n \nWelcome to DGMGRL, type "help" for information.\nConnected to "cortex"\nConnected as SYSDBA.\nDGMGRL> SHOW CONFIGURATION;\n \nConfiguration - cortex\n \n Protection Mode: MaxPerformance\n Members:\n cortex - Primary database\n cortexdr - Physical standby database\n \nFast-Start Failover: Disabled\n \nConfiguration Status:\nSUCCESS (status updated 12 seconds ago)\n \nDGMGRL> SHOW DATABASE CORTEX\n \nDatabase - cortex\n \n Role: PRIMARY\n Intended State: TRANSPORT-ON\n Instance(s):\n cortex\n \nDatabase Status:\nSUCCESS\n \nDGMGRL> SHOW DATABASE CORTEXDR;\n \nDatabase - cortexdr\n \n Role: PHYSICAL STANDBY\n Intended State: APPLY-ON\n Transport Lag: 0 seconds (computed 0 seconds ago)\n Apply Lag: 0 seconds (computed 0 seconds ago)\n Average Apply Rate: 1.00 KByte\/s\n Real Time Query: OFF\n Instance(s):\n CORTEXDR\n \nDatabase Status:\nSUCCESS\n \nDGMGRL>\n<\/pre><\/div>\n\n\nPara simular o evento de falha, vamos logar no banco primary e realizar um shutdown abort:<\/p>\n\n\n
\n[oracle@fornix1 ~]$ sqlplus \/ as sysdba\n \nSQL*Plus: Release 19.0.0.0.0 - Production on Tue Apr 20 20:34:31 2021\nVersion 19.3.0.0.0\n \nCopyright (c) 1982, 2019, Oracle. All rights reserved.\n \n \nConnected to:\nOracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production\nVersion 19.3.0.0.0\n \nSQL> SELECT INSTANCE_NAME,STATUS FROM V$INSTANCE;\n \nINSTANCE_NAME STATUS\n---------------- ------------\ncortex OPEN\n \nSQL> SHU ABORT;\nORACLE instance shut down.\nSQL> !ps -ef | grep pmon\ngrid 3398 1 0 04:45 ? 00:00:02 asm_pmon_+ASM\noracle 31763 31728 0 20:34 pts\/1 00:00:00 \/bin\/bash -c ps -ef | grep pmon\noracle 31765 31763 0 20:34 pts\/1 00:00:00 grep pmon\n<\/pre><\/div>\n\n\nUma vez identificado a falha, e antes de realizar o failover, podemos verificar se o standby est\u00e1 apto para esta opera\u00e7\u00e3o com o comando abaixo:<\/p>\n\n\n
\n[oracle@fornix2 ~]$ dgmgrl sys\/oracle@CORTEXDR\nDGMGRL for Linux: Release 19.0.0.0.0 - Production on Tue Apr 20 20:35:59 2021\nVersion 19.3.0.0.0\n \nCopyright (c) 1982, 2019, Oracle and\/or its affiliates. All rights reserved.\n \nWelcome to DGMGRL, type "help" for information.\nConnected to "cortexDR"\nConnected as SYSDBA.\nDGMGRL> VALIDATE DATABASE VERBOSE CORTEXDR;\n \n Database Role: Physical standby database\n Primary Database: cortex\n Warning: primary database was not reachable\n \n Ready for Switchover: No\n Ready for Failover: Yes (Primary Not Running)\n \n Flashback Database Status:\n cortex : Unknown\n cortexdr: On\n \n Capacity Information:\n Database Instances Threads\n cortex Unknown Unknown\n cortexdr 1 1\n \n Managed by Clusterware:\n cortex : Unknown\n cortexdr: YES\n Validating static connect identifier for the primary database cortex...\nORA-01017: invalid username\/password; logon denied\n \n Warning: Ensure primary database's StaticConnectIdentifier property\n is configured properly so that the primary database can be restarted\n by DGMGRL after switchover\n \n Temporary Tablespace File Information:\n cortex TEMP Files: Unknown\n cortexdr TEMP Files: 1\n \n Data file Online Move in Progress:\n cortex: Unknown\n cortexdr: No\n \n Standby Apply-Related Information:\n Apply State: Running\n Apply Lag: 0 seconds (computed 91 seconds ago)\n Apply Delay: 0 minutes\n \n Transport-Related Information:\n Transport On: No\n Gap Status: Unknown\n Transport Lag: 0 seconds (computed 91 seconds ago)\n Transport Status: Success\n \n Log Files Cleared:\n cortex Standby Redo Log Files: Unknown\n cortexdr Online Redo Log Files: Unknown\n cortexdr Standby Redo Log Files: Unknown\n \n Apply-Related Property Settings:\n Property cortex Value cortexdr Value\n DelayMins 0 0\n ApplyParallel AUTO AUTO\n ApplyInstances 0 0\n \n Transport-Related Property Settings:\n Property cortex Value cortexdr Value\n LogShipping ON ON\n LogXptMode ASYNC ASYNC\n Dependency <empty> <empty>\n DelayMins 0 0\n Binding optional optional\n MaxFailure 0 0\n ReopenSecs 300 20\n NetTimeout 30 20\n RedoCompression DISABLE DISABLE\n<\/pre><\/div>\n\n\nUma vez pronto, podemos realizar o failover:<\/p>\n\n\n
\nDGMGRL> FAILOVER TO CORTEXDR;\nPerforming failover NOW, please wait...\nFailover succeeded, new primary is "cortexdr"\n<\/pre><\/div>\n\n\nChecando nova configura\u00e7\u00e3o:<\/p>\n\n\n
\n[oracle@fornix2 trace]$ dgmgrl sys\/oracle@CORTEXDR\nDGMGRL for Linux: Release 19.0.0.0.0 - Production on Tue Apr 20 20:44:10 2021\nVersion 19.3.0.0.0\n \nCopyright (c) 1982, 2019, Oracle and\/or its affiliates. All rights reserved.\n \nWelcome to DGMGRL, type "help" for information.\nConnected to "CORTEXDR"\nConnected as SYSDBA.\nDGMGRL> SHOW CONFIGURATION;\n \nConfiguration - cortex\n \n Protection Mode: MaxPerformance\n Members:\n cortexdr - Primary database\n cortex - Physical standby database (disabled)\n ORA-16661: the standby database needs to be reinstated\n \nFast-Start Failover: Disabled\n \nConfiguration Status:\nSUCCESS (status updated 19 seconds ago)\n \nDGMGRL> SHOW DATABASE CORTEX;\n \nDatabase - cortex\n \n Role: PHYSICAL STANDBY\n Intended State: APPLY-ON\n Transport Lag: (unknown)\n Apply Lag: (unknown)\n Average Apply Rate: (unknown)\n Real Time Query: OFF\n Instance(s):\n cortex\n \nDatabase Status:\nDISABLED - ORA-16661: the standby database needs to be reinstated\n \nDGMGRL> SHOW DATABASE CORTEXDR;\n \nDatabase - cortexdr\n \n Role: PRIMARY\n Intended State: TRANSPORT-ON\n Instance(s):\n CORTEXDR\n \nDatabase Status:\nSUCCESS\n<\/pre><\/div>\n\n\nPerforming Primary Database Reinstate<\/h2>\n\n\n\n
Montando o primary database antigo:<\/p>\n\n\n
\n[oracle@fornix1 ~]$ sqlplus \/ as sysdba\n \nSQL*Plus: Release 19.0.0.0.0 - Production on Tue Apr 20 20:51:39 2021\nVersion 19.3.0.0.0\n \nCopyright (c) 1982, 2019, Oracle. All rights reserved.\n \nConnected to an idle instance.\n \nSQL> startup mount;\nORACLE instance started.\n \nTotal System Global Area 2583690520 bytes\nFixed Size 8899864 bytes\nVariable Size 553648128 bytes\nDatabase Buffers 2013265920 bytes\nRedo Buffers 7876608 bytes\nDatabase mounted.\nSQL>\n<\/pre><\/div>\n\n\nConectando no novo primary database, e realizando a opera\u00e7\u00e3o de reinstate do primary antigo:<\/p>\n\n\n
\n[oracle@fornix2 trace]$ dgmgrl sys\/oracle@CORTEXDR\nDGMGRL for Linux: Release 19.0.0.0.0 - Production on Tue Apr 20 20:55:27 2021\nVersion 19.3.0.0.0\n \nCopyright (c) 1982, 2019, Oracle and\/or its affiliates. All rights reserved.\n \nWelcome to DGMGRL, type "help" for information.\nConnected to "CORTEXDR"\nConnected as SYSDBA.\nDGMGRL> REINSTATE DATABASE CORTEX;\nReinstating database "cortex", please wait...\nReinstatement of database "cortex" succeeded\n<\/pre><\/div>\n\n\nChecando nova configura\u00e7\u00e3o:<\/p>\n\n\n
\nDGMGRL> SHOW CONFIGURATION;\n \nConfiguration - cortex\n \n Protection Mode: MaxPerformance\n Members:\n cortexdr - Primary database\n cortex - Physical standby database\n \nFast-Start Failover: Disabled\n \nConfiguration Status:\nSUCCESS (status updated 36 seconds ago)\n \nDGMGRL> SHOW DATABASE CORTEX;\n \nDatabase - cortex\n \n Role: PHYSICAL STANDBY\n Intended State: APPLY-ON\n Transport Lag: 0 seconds (computed 1 second ago)\n Apply Lag: 0 seconds (computed 1 second ago)\n Average Apply Rate: 44.00 KByte\/s\n Real Time Query: OFF\n Instance(s):\n cortex\n \nDatabase Status:\nSUCCESS\n \nDGMGRL> SHOW DATABASE CORTEXDR;\n \nDatabase - cortexdr\n \n Role: PRIMARY\n Intended State: TRANSPORT-ON\n Instance(s):\n CORTEXDR\n \nDatabase Status:\nSUCCESS\n<\/pre><\/div>\n\n\nA partir daqui, se quisermos voltar o ambiente na condi\u00e7\u00e3o original, podemos realizar um switchover conforme abaixo:<\/p>\n\n\n
\nDGMGRL> VALIDATE DATABASE CORTEX;\n \n Database Role: Physical standby database\n Primary Database: cortexdr\n \n Ready for Switchover: Yes\n Ready for Failover: Yes (Primary Running)\n \n Managed by Clusterware:\n cortexdr: YES\n cortex : YES\n \n Log Files Cleared:\n cortexdr Standby Redo Log Files: Cleared\n cortex Online Redo Log Files: Not Cleared\n cortex Standby Redo Log Files: Available\n \n Transport-Related Property Settings:\n Property cortexdr Value cortex Value\n ReopenSecs 20 300\n NetTimeout 20 30\n \nDGMGRL> SWITCHOVER TO CORTEX;\nPerforming switchover NOW, please wait...\nOperation requires a connection to database "cortex"\nConnecting ...\nConnected to "cortex"\nConnected as SYSDBA.\nNew primary database "cortex" is opening...\nOracle Clusterware is restarting database "cortexdr" ...\nConnected to an idle instance.\nConnected to an idle instance.\nConnected to an idle instance.\nConnected to an idle instance.\nConnected to an idle instance.\nConnected to "cortexDR"\nConnected to "cortexDR"\nSwitchover succeeded, new primary is "cortex"\nDGMGRL>\n<\/pre><\/div>\n\n\nAmbiente operando nas condi\u00e7\u00f5es originais:<\/p>\n\n\n
\nDGMGRL> SHOW CONFIGURATION;\n \nConfiguration - cortex\n \n Protection Mode: MaxPerformance\n Members:\n cortex - Primary database\n cortexdr - Physical standby database\n \nFast-Start Failover: Disabled\n \nConfiguration Status:\nSUCCESS (status updated 2 second ago)\n<\/pre><\/div>\n\n\nObs: Este procedimento foi criado pelo senhor Ahmed Baraka (www.ahmedbaraka.com) e foi apenas reproduzido por mim em um laborat\u00f3rio pessoal para fins de aprendizado.<\/p>\n","protected":false},"excerpt":{"rendered":"
A opera\u00e7\u00e3o de Failover em um ambiente Data Guard \u00e9 a resposta a um evento de falha, ou seja, uma situa\u00e7\u00e3o n\u00e3o planejada, ocorrendo devido indisponibilidade do Primary. Como consequ\u00eancia, o Standby passa a operar como Primary (no modo maximum performance), e caso queiramos mudar esse modo para outro valor, \u00e9 necess\u00e1rio antes realizar o […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[5],"tags":[],"class_list":["post-3988","post","type-post","status-publish","format-standard","hentry","category-high-availability"],"_links":{"self":[{"href":"https:\/\/swiv.com.br\/index.php\/wp-json\/wp\/v2\/posts\/3988","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/swiv.com.br\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/swiv.com.br\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/swiv.com.br\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/swiv.com.br\/index.php\/wp-json\/wp\/v2\/comments?post=3988"}],"version-history":[{"count":1,"href":"https:\/\/swiv.com.br\/index.php\/wp-json\/wp\/v2\/posts\/3988\/revisions"}],"predecessor-version":[{"id":9162,"href":"https:\/\/swiv.com.br\/index.php\/wp-json\/wp\/v2\/posts\/3988\/revisions\/9162"}],"wp:attachment":[{"href":"https:\/\/swiv.com.br\/index.php\/wp-json\/wp\/v2\/media?parent=3988"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/swiv.com.br\/index.php\/wp-json\/wp\/v2\/categories?post=3988"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/swiv.com.br\/index.php\/wp-json\/wp\/v2\/tags?post=3988"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}