Switchover in Standby database.

Hi All,
DB:11g
OS:AIX
If I am performing a switchover for a Physical standby database, and I have successfully converted my Primary database to new Standby database and when I am trying to convert my Old Standby database to a new Primary database and let us say due to some error (the error is not the important here) I am not able to switch my Old standby database to a new primary database.
What should be my possible steps to undo the switchover or to get me out of this hole?
Regards,
Sphinx

Hi Mohamed,
Thanks!
Well, I was asked this question in an interview and I cross questioned him "What is the error?". He said that the error is irrelevant and you have to give me back a Primary database in minimum time.
Since the original primary is now converted to a standby database and the old standby database is not getting converted to Primary database, so what steps I will have to do to get a Primary database in minimum time, at this moment even if I do not have a standby database that will do as per the interviewer.
This is my concern, finding the error is secondary which I can dig once my Primary is back.
In a nutshell, I just want to know if in the middle of a switchover that I have to perform in a time constrain, if my switchover fails as I have explained above. What approach or steps that I have to take to undo the swicthover or at least get my Primary back.
Hope it calirifes.
Regards,
Sphinx

Similar Messages

Standby database archive log apply in production server.

Dear All,
How I apply standby database archive log apply in production server.
Please help me.
Thanks,
Manas

How can i use standby database as primary for that 48 hour ?Perform a switchover (role transitions).
First check if the standby is in sync with the primary database.
Primary database:
sql>select max(sequence#) from v$archived_log; ---> Value AStandby database:
sql>select max(sequence#) from v$archived_log where applied='YES'; -----> Value BCheck if Value B is same as Value A.
If the standby is in sycn with the primary database, then perform the switchover operation (refer the below link)
http://www.articles.freemegazone.com/oracle-switchover-physical-standby-database.php
http://docs.oracle.com/cd/B19306_01/server.102/b14230/sofo.htm
http://www.oracle-base.com/articles/9i/DataGuard.php#DatabaseSwitchover
manas
Handle: manas
Email: [email protected]
Status Level: Newbie
Registered: Jan 24, 2012
Total Posts: 10
Total Questions: 3 (3 unresolved)
Name Manas
Location kolkata Mark your questions as answered if you feel that you have got better answers rather than building up a heap of unanswered questions.

Switchover of a manual standby database (no data guard)

Hi all,
I have a standby database .
I am using Oracle Standard Edition 10.2.0.4 / 10.2.0.5 so I have build a manual standby .
I am able to do a failover in the case something goes wrong; I was thinking if it is possible to do a manual switchover . and failback.
Do you thick that mounting the primary database and applying ALL archivelogs and online redolog to the standby database is enough ?
Do you think this is a supported operation?
How can I check the current scn of a mounted database? (v$database.current_scn shows 0 until the database is opened )
thnk you for every answer
Andrea

helter_skelter wrote:
hi,
You can see current_scn of standby database in v$database.current_scn. It is null only on primary database if it's in mount state.that's the problem: I am unable to mount both database and to check they have the same current_scn
not all changes are written to ARL so you can't recover standby database to exact the same SCN as primaryI thinks this is because the last changes are only recorder in online redolog, so I was thinking that a possible way to simulate a clean switchover could be as follow:
1 - shutdown immediate the primary database on server prod1
2 - shutdown abort the (manual) standby database on server dr2
3 - copy archivelog, controlfiles, tempfiles, onlinelogs from primary to the standby database
3 - copy controlfiles from standby database to primary database
4 - open the database on server dr2. It should open "read write" cleanly (mount + recover from archivelog + recover from onlinelog + open noresetlogs )
5 - mount the database on server prod1. It should mount as a physical standby database.
What do you think about it?
thanks,
andrea

Switchover to a Physical Standby Database

Hello all,
i have completed Switchover to a Physical Standby Database succesfully, there is no error in alter log file but when i fire on my new primary database " select * from dba_segments order by 2" then it give me following error
SQL Error: ORA-00604: error occurred at recursive SQL level 1
ORA-06553: PLS-801: internal error [56319]
ORA-06544: PL/SQL: internal error, arguments: [56319], [], [], [], [], [], [], []
ORA-06553: PLS-801: internal error [56319]
00604. 00000 - "error occurred at recursive SQL level %s"
*Cause:    An error occurred while processing a recursive SQL statement
(a statement applying to internal dictionary tables).
*Action:   If the situation described in the next error on the stack
can be corrected, do so; otherwise contact Oracle Support.
my database version is
Oracle Database 11g Enterprise Edition Release 11.1.0.6.0 - 64bit Production
Thank You All For Advance Response.

Though this MOS note applies to 10.1, see if it helps,
*ORA-06544: PL/SQL: internal error, arguments: [56319], ORA-06553: PLS-801: internal error [56319]" errors while running catupgrd.sql [ID 863633.1*
HTH
Aman....

Standby Database Switchover Question

I have a Primary and a physical standby database. I have tested switchover and failover to a point. I can't get my client applications to navigate to the "new" primary DB after switchover or failover. I assume it may be something to do with my tnsnames.ora and listener.ora files in my configuration. I will place the contents of the files below.
I was expecting to be able to add the failover syntax to my client tnsnames file and things would be fine. Unfortunately, clinet apps don't failover to "new" Primary ("old" standby DB) when testing failovers; Additionally, when testing switchovers, the client apps try to connect to the "new" standby DB ("old" Primary) instead of the "new" Primary DB.
I was hoping someone might see a syntactical error that is preventing a transparent application failover.
Thanks.
Jim
tnsnames.ora on client:
TESTDB =
(DESCRIPTION=(SOURCE_ROUTE=yes)
     (ADDRESS=(PROTOCOL=tcp)(HOST = oracle1.datacenter.staging)(PORT = 1521))
     (ADDRESS_LIST=(FAILOVER=on)(LOAD_BALANCE=off)
     (ADDRESS=(PROTOCOL=tcp)(HOST = oracle2.datacenter.staging)(PORT = 1521))(CONNECT_DATA=(SERVICE_NAME=orcl10STANDBY)))
     (CONNECT_DATA=(SERVICE_NAME=orcl10)))
tnsnames.ora (on both Primary and Standby DB's)
ORCL10 =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = oracle1.datacenter.staging)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = orcl10)
ORCL10STANDBY =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = oracle2.datacenter.staging)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = orcl10STANDBY)
listener.ora - Primary
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(SID_NAME = PLSExtProc)
(ORACLE_HOME = D:\oracle\product\10.2.0\db_10)
(PROGRAM = extproc)
(SID_DESC =
(ORACLE_HOME = D:\oracle\product\10.2.0\db_10)
(SID_NAME = ORCL10)
LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1))
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = oracle1.datacenter.staging)(PORT = 1521))
listener.ora - Standby
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(SID_NAME = PLSExtProc)
(ORACLE_HOME = D:\oracle\product\10.2.0\db_1)
(PROGRAM = extproc)
(SID_DESC =
(ORACLE_HOME = D:\oracle\product\10.2.0\db_1)
(SID_NAME = ORCL10STANDBY)
LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1))
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = oracle2.datacenter.staging)(PORT = 1521))
)

Hi another way can be configuring client tnsname files to support failover:
EXAMPLE=
(description=
(address_list=
(load_balance=off)
(failover=on)
(address=(protocol=tcp)(host=X)(port=1521))
(address=(protocol=tcp)(host=Y)(port=1521)))
(connect_data=(service_name=XXX)))
if the listener on host X (primary db) fails, client tries to connect the standby database on host Y.

Stantard Edition-standby database-switchover standby (primary) to primary

i hace two server standar editon , i configure manual standby database fisical .
Database size = 700GB
DBP : database primary
DBS : database standby
All ok, my configuration is ok, everything works fine, but one day I had to do n switchover by hardware problems
note : manual standby database fisica
DBP to standby - do nothing, receive nothing or apply anything
DBS to Primary - receives user requests read and write
all ok.
the downtime of DBP = 7 horas:
archivelogs generated of DBS = 198 MB.
i want this:
DBP ( standby - nothing) to primary
DBS ( primary ok ) to standby
but
but I have to do, I have to do all settings again and for me no problem.
the point is how i can DBP = DBS ( data update) .
my problema is database size 700GB , is very big for me for hotbackup or backup rman
would have to generate a backup and apply DBS to DBP.
I can apply only archivi logs generated in DBS (198 mb), and as I do because eh searched and can not find documentation.
please help.
note : my english is very bad!!! =P

hmmmm, it is veyi interesting,
TNS-03505: Failed to resolve name
Cause: The service name you provided could not be found in TNSNAMES.ORA, an Oracle Names server, or a native naming service.
Action: Verify that you entered the service name correctly. You may need to ensure that the name was entered correctly into the network configuration.
Please check this link:
Oracle in World: Troubleshoot ORA-12154 TNS-12154 TNS-03505: Failed to resolve name
Thank you.

Problem in switchover to physical standby database

Hi All,
I am doing switchover from primary to physical standby database. Physical standby is in 'managed recovery' mode using real time apply and is in mount mode. I executed alter database commit to switchover to physical standby with session shutdown command. Now i am waiting for standby mrp to exit after processing eor record, but it seems mrp was hanged.
Below is the content from standby database:
Recovery of Online Redo Log: Thread 1 Group 5 Seq 620 Reading mem 0
Mem# 0: /oracle/app/oracle/dbrac/th1-redo5a.log
Resetting standby activation ID 749049115 (0x2ca5951b)
Media Recovery End-Of-Redo indicator encountered
Media Recovery Continuing
Media Recovery Waiting for thread 1 sequence 621
Archived Log entry 14 added for thread 1 sequence 620 ID 0x2ca5951b dest 1:
Need some help to resolve.
Thanks
Sandy.

Hello;
After after you issue ( successfully ) a :
alter database commit to switchover to physical standby with session shutdownYou need to :
Shutdown the former primary and mount as a standby databaseCheck out my step by step :
http://www.visi.com/~mseberg/data_guard/Data_Guard_switchover.html
Read everything ( all the steps ) before you proceed.
Best Regards
mseberg

Can I use data guard to create a RAC standby database for a non RAC primary

Hi,
we need to RAC our production database but the normal methods will mean a long outage. It is possible to create a standby as a single node RAC database and when ready do a graceful failover to the standby database and open it for business. The next step would be to create another RAC node from this on the original server.
servers are already cluster aware, using ASM etc
Oracle 10.2

Yes, you will be able to setup RAC stnadby for a non-RAC Primary. For primary it just needs a available destination for redo shipping it doesn't matter whether it's RAC enabled or not. And ofcourse you are using 10.2 anyway only one node will be running MRP and that is too in standby mount mode.
However since you have are using You may follow below sequence.
1. Setup a new standby as RAC enabled.
2. Perform a switchover.
3. Shutdown the Old primary (which is standby now).
4. Install CRS and RDBMS on the old primary and it's new node.
5. Modify the cluster_database=TRUE and cluster_database_instances=<required number of instances>.
With above modification mount the standby database in standby mode and start MRP.
6. Introduce the database and instances to the OCR using SRVCTL add command.
7. Once you your database is synchronized with Primary do a switchover.
9. Now you can repeat step 3 to 6 on the other site too. <- if you need your secondary site to be RAC enabled too
10. Finally both the sites should be RAC enabled.
Hope this is helpful!!!
Thanks,
Asif Haliyal

Switching between Primary and Standby database

Hi,
I managed to setup a standby database that is updated by the primary db either when doing a log file switch or when changing the role of the primary db to standby.
Now I want to put the standby database (that was in primary role for a short period) back into its standby role. I entered
"Alter database commit to switchover to physical standby with session shutdown;"
The archived redo logs as well as the control file are updated on the primary database (which was in standby role for the same short period). When I enter
"Alter database commit to switchover to primary" I am receiving the following error message:
SQL> alter database commit to switchover to primary;
alter database commit to switchover to primary
ERROR at line 1:
ORA-16139: media recovery required
After issuing the recovery statement I get this message:
SQL> recover database
ORA-00283: recovery session canceled due to errors
ORA-01610: recovery using the BACKUP CONTROLFILE option must be done
At the same time this log entry is written into the alert log:
Database not available for switchover
End-Of-REDO archived log file has been received
Archived log files detected beyond End-Of-REDO
Incomplete recovery SCN:0:962365 archive SCN:0:977340
Switchover: Media recovery required - standby not in limbo
ORA-16139 signalled during: alter database commit to switchover to primary...
But when I try to use the BACKUP CONTROLFILE statement during recovery I get this error message:
SQL> recover database using backup controlfile;
ORA-00283: recovery session canceled due to errors
ORA-01666: control file is for a standby database
Although being quite a newbie it's obvious that the primary database (which was standby for a short period) is worried that there are older archived redo logs than online logs. I guess this happens because of the log_archive_dest definition on the standby database :
*.LOG_ARCHIVE_DEST_3='SERVICE=ORAMPPRD REOPEN=60 MAX_FAILURE=3 LGWR SYNC
VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=ORAMPPRD'
Changes are applied immediately and only written to the archive.
But how can it be managed that the online redo logs on the primary system are also updated when switching back from standby ???
Thanks,
Philipp.

Thanks, it's working now.
I think it's important to explizitely follow the steps to switchover standby and primary for it to work. I maybe shutdown the standby to early.
Cheers,
Philipp.

Running a physical standby database in noarchivelog mode

Primary Database: 2 node rac cluster, 11.2.0.2 GI and RDBMS
Standby Database: single instance 11.2.0.2
OS: AIX 7.1
Hello,
I'm in the process of implementing a data guard standby system. To make this system simpler to admin, I want to run the standby database in NOARCHIVELOG mode. This standby is used only as a mirror of production (to be copied to a 3rd site for separate user activity) and will never be switched to active mode. Maintaining another set of archive logs seems to be redundant to me and another point of failure, so I want to disable archiving. I wanted to ask if any of the DG experts on the forums have ever had experience with this? Does anyone know if this is recommended? I've searched the Oracle Data guard documentation online... it says that the primary obviously needs to be in archive mode, but I'm not seeing anything specific about the standby. Please let me know if anyone has experience with this.
Thanks

Hello again;
If this is the case, then I have nothing to worry about here. Does that sound right to you?Yes.
For this :
b) monthly, shutdown this system and copy it to a 3rd site to host a separate set of business activityI would consider RMAN Duplicate in which case you may avoid the shutdown.
And for this :
resync the "mirror" with productionAll you have to do if DEFER the primary to the standby, then ENABLE and Data Guard will catch up.
--- Will post a detailed example here in a moment.
Right at the first of the year they wanted to work on our Primary server room ( Power ). What I did was switchover to the Standby but I kept log_archive_dest_state_2 on the new primary set to DEFER. Then I shutdown
all the databases at the Primary site. At the end of work two days later I started the databases at the Primary site in standby mode. Switched log_archive_dest_state_2 to ENABLE. When the databases were back in SYNC
I did another switchover and it was done. I used TAF and none of the users even noticed.
Best Regards
mseberg

Configuring more than 2 standby database

Hi,
iam trying to configure 2 standby databases my primary database name is anupp1 and standby database name is anups1 and anups2 respectively (physical standby databases)when i configured means archiving is received at both databases but when i switchover at that time archiving is received at only one database
my primary database is anupp1 and standby databases are anups1 ,anups2
now when i perform switchover at that time ie primary is anups1 and standby are anupp1 and anups2
so archive log are nnoy shipped on anups2 they are on anupp1 iam posting the contents of all the pfiles
pfile of anupp1
db_unique_name='anupp1'
log_archive_dest_1='LOCATION=/u01/app/oracle/oradata/anupp1/arch/
VALID_FOR=(ALL_LOGFILES,ALL_ROLES)
db_unique_name=anupp1'
log_archive_dest_2='SERVICE=anups1 LGWR ASYNC
VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE)
db_unique_name=anups1'
log_archive_dest_3='SERVICE=anups2 LGWR ASYNC
VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE)
db_unique_name=anups2'
log_archive_dest_state_1=enable
log_archive_dest_state_2=enable
log_archive_dest_state_3=enable
fal_server=anups1
fal_client=anupp1
pfile of anups1
db_unique_name='anups1'
log_archive_dest_1='LOCATION=/u01/app/oracle/oradata/anups1/arch/
VALID_FOR=(ALL_LOGFILES,ALL_ROLES)
db_unique_name=anups1'
log_archive_dest_2='SERVICE=anupp1 LGWR ASYNC
VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE)
db_unique_name=anupp1'
log_archive_dest_state_1=enable
log_archive_dest_state_2=enable
fal_server=anupp1
fal_client=anups1
log_file_name_convert='/u01/app/oracle/oradata/anupp1/','/u01/app/oracle/oradata/anups1/'
db_file_name_convert='/u01/app/oracle/oradata/anupp1/','/u01/app/oracle/oradata/anups1/'
pfile of anups2
db_unique_name='anups2'
log_archive_dest_1='LOCATION=/u01/app/oracle/oradata/anups2/arch/
VALID_FOR=(ALL_LOGFILES,ALL_ROLES)
db_unique_name=anups2'
log_archive_dest_2='SERVICE=anupp1 LGWR ASYNC
VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE)
db_unique_name=anupp1'
log_archive_dest_state_1=enable
log_archive_dest_state_2=enable
log_file_name_convert='/u01/app/oracle/oradata/anupp1/','/u01/app/oracle/oradata/anups2/'
db_file_name_convert='/u01/app/oracle/oradata/anupp1/','/u01/app/oracle/oradata/anups2/'
so above are the contents ...... pls let me know which parameter is not set correctly or what modifications i need to do
Thanks in Advance
Regards
Kavita

Hi
Sir i apologize for the late reply yes i have added the parameters in all the pfiles as what u mentioned and apart from ther e i have also did network configuration on anups1 for anups2 and vice versa so they can ship the logs ....... Sir only posted parameters related to dataguard i never pasted the whole alert log file
Sir in pfile of anup1
i have addded
log_archive_dest_3='SERVICE=anups2 LGWR ASYNC
VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE)
db_unique_name=anups2
in pfile of anups1
log_archive_dest_3='SERVICE=anups2 LGWR ASYNC
VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE)
db_unique_name=anups2
in pfile of anups2
log_archive_dest_1='LOCATION=/u01/app/oracle/oradata/anups2/arch/
VALID_FOR=(ALL_LOGFILES,ALL_ROLES)
db_unique_name=anups2'
log_archive_dest_2='SERVICE=anupp1 LGWR ASYNC
VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE)
db_unique_name=anupp1'
and did the network configuration on both standby databases so that can ping each other and when i perfom switchover at that time standby1 becomes primary and able to ship to both the databases Sir my net was down and at that time i tried to added these parameter and it worked i have checked now my account on otn .Sir will also try as mentioned by you
Thanks in Advance
Regards
Kavita

Standby Database

Hi all,
Its ciirctical
We have prodution database in 10.2.0.1 on sun solaris and its standby with same configuration on remote site.
Both the database are operating in maximum avaialbilty mode:
select protection_mode,protection_level name ,db_unique_name from v$database;
PROTECTION_MODE NAME DB_UNIQUE_NAME
MAXIMUM AVAILABILITY RESYNCHRONIZATION STANDBY
I have switched primary to standby and it worked fine but when i reverting back i am getting below error:
SQL> /
alter database commit to switchover to standby
ERROR at line 1:
ORA-16416: Switchover target is not synchronized with the primary
When i tried to perform recovery on standby machine it completed successfully. And all archived are applied . But still i am getting same error on primary site when i am trying to switch over to standby.
Please refer alert log file of primary:
Destination LOG_ARCHIVE_DEST_2 is SYNCHRONIZED
LNSb started with pid=20, OS id=1252
Sat Oct 23 14:53:50 2010
Destination LOG_ARCHIVE_DEST_2 is UNSYNCHRONIZED
Sat Oct 23 14:53:50 2010
Errors in file /export/home/oracle/product/10.2.0/db1/admin/PRIMARY/bdump/standby_lgwr_1104.trc:
ORA-16086: standby database does not contain available standby log files
LGWR: Failed to archive log 2 thread 1 sequence 190 (16086)
Thread 1 advanced to log sequence 190
Current log# 2 seq# 190 mem# 0: /export/home/oracle/product/10.2.0/db1/oradata/PRIMARY/redo02.log
Please refer standby alert_log :
Destination LOG_ARCHIVE_DEST_2 is SYNCHRONIZED
LNSb started with pid=20, OS id=1252
Sat Oct 23 14:53:50 2010
Destination LOG_ARCHIVE_DEST_2 is UNSYNCHRONIZED
Sat Oct 23 14:53:50 2010
Errors in file /export/home/oracle/product/10.2.0/db1/admin/PRIMARY/bdump/standby_lgwr_1104.trc:
ORA-16086: standby database does not contain available standby log files
LGWR: Failed to archive log 2 thread 1 sequence 190 (16086)
Thread 1 advanced to log sequence 190
Current log# 2 seq# 190 mem# 0: /export/home/oracle/product/10.2.0/db1/oradata/PRIMARY/redo02.log
Sat Oct 23 15:00:49 2010
Destination LOG_ARCHIVE_DEST_2 is SYNCHRONIZED
LNSb started with pid=20, OS id=1270
Sat Oct 23 15:00:52 2010
Destination LOG_ARCHIVE_DEST_2 is UNSYNCHRONIZED
Sat Oct 23 15:00:52 2010
Errors in file /export/home/oracle/product/10.2.0/db1/admin/PRIMARY/bdump/standby_lgwr_1104.trc:
ORA-16086: standby database does not contain available standby log files
LGWR: Failed to archive log 3 thread 1 sequence 191 (16086)
Thread 1 advanced to log sequence 191
Current log# 3 seq# 191 mem# 0: /export/home/oracle/product/10.2.0/db1/oradata/PRIMARY/redo03.log

Add one or more standby log files to the standby database. This can be done while the standby database is mounted.
Errors in file /export/home/oracle/product/10.2.0/db1/admin/PRIMARY/bdump/standby_lgwr_1104.trc
Please check standby_lgwr_1104.trc file.

Creating standby database

Hi
I want create standby database in Oracle 10g.
I can create standart database by using database configuration assistant.
How can I create standby database in Oracle 10g?

Hi,
Standby databases, in a nutshell, acts as a failover for our mission critical production databases. When production database crashes, applications can quickly switchover to the stand by databases.
What type of Standy you are willing to go for ??
Physical Standby Database
Standby database is called “physical” if the physical structure of stand by exactly matches with stand by structure. Archived redo log transferred from primary database will be directly applied to the stand by database.
Logical Standby Database
Stand by database is called “logical”, the physical structure of both
databases do not match and from the archived redo log we create SQL statements then these statements will be applied to stand by database.
Follow this link for creating standby database
http://www.oracle-base.com/articles/8i/StandbyDatabase.php
http://download.oracle.com/docs/cd/B10501_01/server.920/a96653/create_ps.htm
Thanks
Pavan Kumar N

What is the Use of "Alter database activate standby database"

Hi ,
I appreciate your time.
I just wanted to know what is the use of "Alter database activate standby database" command when doing the failover. How different it will act in failover process. Can we use this command in SwitchOver.
Thanks in advance.

Hi Uwe Hesse,
Wonderfull... good info....
So my understanding is that the use of "ACTIVATE PHYSICAL STANDBY DATABASE" is conditional and depends on the redo log gap and the Database status(Able to mount or not).
Condition 1: If the Db is in Mount state and Redo log gap is successfully filled.
1) Flush any unsent redo from the primary database to the target standby database.
SQL> ALTER SYSTEM FLUSH REDO TO target_db_name;
Note: If the above Statement Completes successfully without any errors.
2) Stop Redo Apply.
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;
3) Finish applying all received redo data.
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE FINISH;
4) Verify that the target standby database is ready to become a primary database.
SQL> SELECT SWITCHOVER_STATUS FROM V$DATABASE;
5) Switch the physical standby database to the primary role.
SQL> ALTER DATABASE COMMIT TO SWITCHOVER TO PRIMARY WITH SESSION SHUTDOWN;
Condition 2: If the DB is not able Mount and Redo Gap can't be filled.
Important Note: If the the above command in STEP3 gives error, some received redo data was not applied. Try to resolve the cause of the error and re-issue the statement before proceeding.
If the error condition cannot be resolved, a failover can still be performed (with some data loss) by issuing the following SQL statement on the target standby database:
SQL> ALTER DATABASE ACTIVATE PHYSICAL STANDBY DATABASE;
Thanks in advance.

How to open a standby database for use?

First, let me state that I am not a DBA nor am I a systems guy; I'm a software developer.
At work, we recently built a new virtualized db server by cloning our disaster recovery (DR) database server. The DR database was kept in 'standby' mode (I think that's the correct term) and was synched with production daily via archive logs.
So now, we have this new virtualized server that has a clone of that 'standby' database on it, and I need to 'open' that database so that it's usable (ie, no longer a standby db). How do I do that?? We recently lost our DBA so this has fallen into my lap.
From searching the web, I've found all sorts of instructions. It seems that I need to issue some commands via SQL*Plus? But as what user? From where do I issue these commands (I assume from the virtualized server)? And what are the commands?
This is Oracle 10g v10.2.0.3.0 running on Solaris 10 for x86.
Thanks!
Dave

Hi Dave, I do this each time we do a DR test. I have 10.2.0.3 in physical standby mode.
First, I make sure I have flashback turned on (here is what I've done):
connect / as sysdba
startup nomount
alter database mount standby database;
alter database flashback on;
alter database recover managed standby database through all switchover disconnect using current logfile;
exit;Activate the physical standby:
alter database recover managed standby database cancel;
alter database activate physical standby database;
alter database open;
exit;When completed with DR test we return the database back to physical standby mode:
Find the SCN when the physical standby was activated (this is so we can flashback to that point in time)
select standby_became_primary_scn from v$database;connect / as sysdba
flashback database to scn <this is the value returned from above>;
alter database convert to physical standby;
shutdown immediate
startup mount
alter database recover managed standby database disconnect from session;
exit;I hope that helps,
Michael Cunningham
Edited by: Michael C on Nov 10, 2011 8:59 AM
Edited by: Michael C on Nov 10, 2011 9:00 AM

Switchover in Standby database.

Similar Messages

Maybe you are looking for