This discussion is archived
1 2 Previous Next 18 Replies Latest reply: Oct 15, 2012 3:31 AM by Sunny kichloo Go to original post RSS
  • 15. Re: ORA-16057: DGID from server not in Data Guard configuration
    Suddhasatwa_Bhaumik Newbie
    Currently Being Moderated
    Hi

    Thanks for the pointers. However I have checked the lo_archive_dest_* entries as well, and they look fine.
    Please advice.

    Thanks,
    Suddhasatwa
  • 16. Re: ORA-16057: DGID from server not in Data Guard configuration
    Sunny kichloo Expert
    Currently Being Moderated
    show the output of

    tnsping <service name of standby database> from primary database

    and have you just verified your parameters from the doc link that i have mentioned in previous link
  • 17. Re: ORA-16057: DGID from server not in Data Guard configuration
    Shivananda Rao Guru
    Currently Being Moderated
    SBhaumik_DBA wrote:
    Hello All

    DB Version - 10.2.0.3
    OS: Solaris 9

    I have created a physical standby database for one of my databases. While I was performing a manual switch over I got the error "ORA-16057: DGID from server not in Data Guard configuration". Below are the steps I have followed:
    1.  Check for the status in primary database as below:
    
    SQL> Select Database_role from v$Database;
    
    DATABASE_ROLE
    ----------------
    PRIMARY
    
    SQL>
    SQL> Select switchover_status from v$Database;
    
    SWITCHOVER_STATUS
    --------------------
    TO STANDBY
    
    2. To perform manual switch-over I used the below command:
    
    SQL> Alter Database Commit to Switchover to Physical Standby with session Shutdown;
    
    Database altered.
    
    3. Restarted the DB to Open stage. Now it is showing read-only which is obvious. 
    
    4. Check the status of the database now, which earlier was primary but now should show as standby. 
    
    SQL> Select Database_role from v$Database;
    
    DATABASE_ROLE
    ----------------
    PHYSICAL STANDBY
    
    SQL> Select switchover_status from v$Database;
    
    SWITCHOVER_STATUS
    --------------------
    TO PRIMARY
    
    
    5. On the standby database, issue the below command to cancel the MRP process:
    
    SQL> Alter database Recover Managed Standby Database Cancel;
    
    Database Altered.
    
    6. Recover the standby database using the below command before switching it over as primary:
    
    SQL> alter database recover managed standby database finish;
    
    Database altered.
    
    7. Now switch over the standby database as primary:
    
    SQL> Alter Database Commit to Switchover to PRIMARY with session Shutdown;
    
    Database altered.
    
    8. Restart the DB in open stage for settings to take effect:
    
    SQL> shutdown immediate;
    ORA-01507: database not mounted
    
    
    ORACLE instance shut down.
    SQL> startup;
    ORA-32004: obsolete and/or deprecated parameter(s) specified
    ORACLE instance started.
    
    Total System Global Area 3221225472 bytes
    Fixed Size                  2131880 bytes
    Variable Size             985561176 bytes
    Database Buffers         2231369728 bytes
    Redo Buffers                2162688 bytes
    Database mounted.
    Database opened.
    SQL>
    SQL> select name, open_mode from v$database;
    
    NAME      OPEN_MODE
    --------- ----------
    SBDBPROD  READ WRITE
    
    
    9. Confirm that the standby DB is now the primary DB:
    
    SQL> Select Database_role from v$Database;
    
    DATABASE_ROLE
    ----------------
    PRIMARY
    Now I get the below error:
    SQL> list
    1* Select Status, Error from v$Archive_dest where dest_id=2
    SQL> /
    
    STATUS    ERROR
    --------- -----------------------------------------------------------------
    DISABLED  ORA-16057: DGID from server not in Data Guard configuration
    Please advice how this can be rectified.

    Thanks.
    Suddhasatwa
    Reviewing your steps, you are perfect till STEP 4, but you are lost from STEP 6.

    The command you have used in STEP 6 "*alter database recover managed standby database finish*;" is used at the time of FAILOVER and not SWITCHOVER. The FINISH clause initiates failover on the target physical standby database and recovers the current standby redo log files. Use the FINISH clause only in the event of the failure of the primary database.

    Now, it looks like you have performed a FAILOVER and not SWITCHOVER
  • 18. Re: ORA-16057: DGID from server not in Data Guard configuration
    Sunny kichloo Expert
    Currently Being Moderated
    Thanks Shivananda for updating that missed that thing
1 2 Previous Next

Legend

  • Correct Answers - 10 points
  • Helpful Answers - 5 points