Summary
The reference is 6.13 Scenario 12: Converting a Physical Standby to a Snapshot Standby .
References
Oracle Manuals
- Oracle ® Data Guard Broker 12c Release 1 (12.1)
- 6 Scenarios Using the DGMGRL Command-Line Interface
- 7 Oracle Data Guard Command-Line Interface Reference
- Oracle ® Data Guard Concepts and Administration 12c Release 1 (12.1)
Procedure Using DGMGRL
Connect to Data Guard Manager
Use the dgmgrl command to connect to the local Data Guard Manager as follows:
dgmgrl sys/**********
Sample output is:
DGMGRL for Linux: Version 12.1.0.2.0 - 64bit Production Copyright (c) 2000, 2013, Oracle. All rights reserved. Welcome to DGMGRL, type "help" for information. Connected as SYSDG.
Verify Configuration
Use the following command to ensure that:
- Protection mode is Maximum Performance because we are running a single standby.
- Fast Start Failover is disabled.
- Primary database is open for Read/Write
- Physical Standby is mounted
- There are no warnings or errors
show configuration
The expected output is similar:
Configuration - ocm12.yaocm.id.au Protection Mode: MaxPerformance Members: ocm12 - Primary database ocm12_botany - Physical standby database Fast-Start Failover: DISABLED Configuration Status: SUCCESS (status updated 51 seconds ago)
Convert to Snapshot Standby
Use the following command to convert the physical standby database into a snapshot standby:
convert database ocm12_botany to snapshot standby;
The expected output is:
Converting database "ocm12_botany" to a Snapshot Standby database, please wait... Database "ocm12_botany" converted successfully
NOTE:
If the password provided for connection is incorrect, the following messages will appear:
If the password provided for connection is incorrect, the following messages will appear:
Converting database "ocm12_botany" to a Physical Standby database, please wait... Operation requires shut down of instance "ocm12" on database "ocm12_botany" Shutting down instance "ocm12"... ORA-01017: invalid username/password; logon denied Warning: You are no longer connected to ORACLE. Please complete the following steps and reissue the CONVERT command: shut down instance "ocm12" of database "ocm12_botany" start up and mount instance "ocm12" of database "ocm12_botany"
Verify Configuration
Use the following command to verify
show configuration
The expected output is:
Configuration - ocm12.yaocm.id.au
Protection Mode: MaxPerformance
Members:
ocm12 - Primary database
ocm12_botany - Snapshot standby database
Fast-Start Failover: DISABLED
Configuration Status:
SUCCESS (status updated 6 seconds ago)