Perform the Failover by using the DGMGRL (Observer Utility) in our Test Env

-
Perform the Failover by using the DGMGRL (Observer Utility) in our Test Env

 On Primary Database

 [oracle@pr ~]$ !sq

sqlplus / as sysdba

SQL*Plus: Release 11.2.0.4.0 Production on Mon Jun 12 02:28:04 2017
Copyright (c) 1982, 2013, Oracle.  All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options

 SQL>  SELECT NAME,DB_UNIQUE_NAME, OPEN_MODE,DATABASE_ROLE FROM V$DATABASE;

NAME      DB_UNIQUE_NAME                 OPEN_MODE            DATABASE_ROLE
--------- ------------------------------ -------------------- ----------------
PR        pr                             READ WRITE           PRIMARY

 On Standby Database

[oracle@std scripts]$ !sq

sqlplus / as sysdba
SQL*Plus: Release 11.2.0.4.0 Production on Mon Jun 12 02:28:21 2017
Copyright (c) 1982, 2013, Oracle.  All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options

 SQL> SELECT NAME,DB_UNIQUE_NAME, OPEN_MODE,DATABASE_ROLE FROM V$DATABASE;

NAME      DB_UNIQUE_NAME                 OPEN_MODE            DATABASE_ROLE
--------- ------------------------------ -------------------- ----------------
PR        std                            MOUNTED              PHYSICAL STANDBY

SQL> exit

Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options

 [oracle@std scripts]$ dgmgrl

DGMGRL for Linux: Version 11.2.0.4.0 - 64bit Production
Copyright (c) 2000, 2009, Oracle. All rights reserved.
Welcome to DGMGRL, type "help" for information.
DGMGRL> connect sys/xxx
Connected.

 DGMGRL> show configuration

Configuration - PRDG
  Protection Mode: MaxPerformance
  Databases:
    pr  - Primary database
    std - Physical standby database
Fast-Start Failover: DISABLED
Configuration Status:
SUCCESS

DGMGRL> show database 'pr';
Database - pr
  Role:            PRIMARY
  Intended State:  TRANSPORT-ON
  Instance(s):
    pr
Database Status:
SUCCESS

Shutdown abort on Primay Database  - (Consider the Primary DB is Intentionally or Due to some issue the Primary DB is no more exist, Therefore we need to perform the failover on standby database)

 SQL> shutdown abort
ORACLE instance shut down.

 On standby database

 DGMGRL> failover to 'std'

Performing failover NOW, please wait...
Failover succeeded, new primary is "std"
Check the standby database status

 Verify the Standby database as Primary

 SQL> select status from v$instance;

STATUS
------------
OPEN

SQL> SELECT NAME,DB_UNIQUE_NAME, OPEN_MODE,DATABASE_ROLE FROM V$DATABASE;

NAME      DB_UNIQUE_NAME                 OPEN_MODE            DATABASE_ROLE
--------- ------------------------------ -------------------- ----------------
PR        std                            READ WRITE           PRIMARY

 [oracle@std scripts]$ dgmgrl

DGMGRL for Linux: Version 11.2.0.4.0 - 64bit Production
Copyright (c) 2000, 2009, Oracle. All rights reserved.
Welcome to DGMGRL, type "help" for information.

 DGMGRL> connect sys/xxx
Connected

DGMGRL> SHOW CONFIGURATION

Configuration - PRDG
  Protection Mode: MaxPerformance
  Databases:
    std - Primary database
    pr  - Physical standby database (disabled)
      ORA-16661: the standby database needs to be reinstated
Fast-Start Failover: DISABLED
Configuration Status:

SUCCESS

 DGMGRL> show database 'pr'

Database - pr
  Role:            PHYSICAL STANDBY
  Intended State:  APPLY-ON
  Transport Lag:   (unknown)
  Apply Lag:       (unknown)
  Apply Rate:      (unknown)
  Real Time Query: OFF
  Instance(s):
    pr
Database Status:

ORA-16661: the standby database needs to be reinstated

 SQL> SELECT NAME,DB_UNIQUE_NAME, OPEN_MODE,DATABASE_ROLE FROM 
V$DATABASE;

NAME      DB_UNIQUE_NAME                 OPEN_MODE            DATABASE_ROLE
--------- ------------------------------ -------------------- ----------------
PR        std                            READ WRITE           PRIMARY

 SQL> SELECT USERNAME FROM DBA_USERS;

USERNAME
------------------------------
MGMT_VIEW
SYS
SYSTEM
DBSNMP
SYSMAN

(etc - Can view all the users which was exist on Primary DB)

39 rows selected.

Hence the standby database becomes as primary after the failover operation.

Comments

Post a Comment

Popular posts from this blog

ORA-01110: data file 1: '/oradata/datafiles/system01.dbf'

-
ORA-01110: data file 1: '/oradata/datafiles/system01.dbf' Error occur while restoring the database from the backup of RMAN RMAN> alter database open resetlogs; using target database control file instead of recovery catalog RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-03002: failure of alter db command at 09/03/2017 16:05:14 ORA-01194: file 1 needs more recovery to be consistent ORA-01110: data file 1: '/oradata/datafiles/system01.dbf' To resolve this error fallow the below procedure – Hopefully you will succeed If you’re primary database is flashback & it has the standby – Fallow below procedure RMAN> run { 2> recover database; 3> } ORA-00283: recovery session canceled due to errors RMAN-11003: failure during parse/execution of SQL statement: alter datab
Read more

Expdp from Higher version 12c (12.1.0.2) to lower version 11g (11.2.0.4)

-
Expdp from Higher version 12c (12.1.0.2) to lower version 11g (11.2.0.4) Export on 12c (12.1.0.2)   – Tested in our env : 10.20.0.82 ==================== SQL> select instance_name,version from v$instance; INSTANCE_NAME    VERSION ---------------- ----------------- ora12c           12.1.0.2.0 SQL> conn sys/sys as sysdba Connected. SQL> conn hassan/( password ); Connected. SQL> select table_name from user_tables; TABLE_NAME -------------------------------------------------------------------------------- TEST SQL> select * from test; COLUMN1              NAME -------------------- -------------------- 1                    abc 2                    xyz [oracle@ora12c u02]$ mkdir dump [oracle@ora12c u02]$ chmod -R 777 dump/ [oracle@ora12c u02]$ sqlplus / as sysdba SQL*Plus: Release 12.1.0.2.0 Production on Wed Jan 25 16:22:46 2017 Copyright (c) 1982, 2014, Oracle.  All
Read more

Solutions: error while starting of Oracle Single instance ASM Database

-
1 st – Starting ASM [root@asmdb ~]#su - grid [grid@asmdb ~]$ asmcmd Connected to an idle instance ASMCMD> ls ASMCMD-08102: no connection to ASM; command requires ASM to run ASMCMD> [grid@asmdb ~]$ sqlplus / as sysasm SQL*Plus: Release 11.2.0.4.0 Production on Mon Jan 23 17:44:30 2017 Copyright (c) 1982, 2013, Oracle.  All rights reserved. Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production With the Automatic Storage Management option SQL> conn / as sysasm Connected to an idle instance SQL> startup ORA-01078: failure in processing system parameters ORA-29701: unable to connect to Cluster Synchronization Service SQL> exit Disconnected 2nd : Starting DB [oracle@asmdb ~]$ sqlplus / as sysdba SQL*Plus: Release 11.2.0.4.0 Production on Mon Jan 23 17:15:15 2017 Copyright (c) 1982, 2013, Oracle.  All rights reserved. Connected to an idle instance. SQL> startup ORACLE instance started. Total System Gl
Read more