Switchover to 1 of 3 Physical Standby (oracle 10g R2)

Hi all,
Previously I already had done switchover primary to standby (only 1 Physical standby was in the configuration)
now i have some additional physical standbys (3 Physical standbys)
stby1
stby2
stby3
i want to switch to stby1 ,what needs to be done at stby2,stby3 to make them capable of identifying stby1 as their new primary.
Kindly suggest!
Best Regards,
Muhammad Shakeel Azeem

921542 wrote:
Hi all,
Previously I already had done switchover primary to standby (only 1 Physical standby was in the configuration)
now i have some additional physical standbys (3 Physical standbys)
stby1
stby2
stby3
i want to switch to stby1 ,what needs to be done at stby2,stby3 to make them capable of identifying stby1 as their new primary.
Kindly suggest!
Best Regards,
Muhammad Shakeel AzeemAzeem,
Welcome to OTN,
Once you performed switchover, You need to perform changes with some parameters from standby FAL_SERVER
Earlier this parameter points to old primary, Now after switchover you have to put service name of new primary database service.
Also Make changes with remote destinations log_archive_dest_n with correct service names.
Refer this manual to work with multiple standby databases.
http://www.oracle.com/technetwork/database/features/availability/maa10gr2multiplestandbybp-1-131937.pdf

Similar Messages

Lost datafile on Standby Oracle 10g

Hi all.
i have lost one datafile on my standby ,how to recover it ,this file is created when primary database is in noarchive mode (before i set up the data guard) ,so i can't use alter database create datafile statement bocz i dont have all the archive log to recover it ,
plz help me out to solve this ..

969752 wrote:
Hi all.
i have lost one datafile on my standby ,how to recover it ,this file is created when primary database is in noarchive mode (before i set up the data guard) ,so i can't use alter database create datafile statement bocz i dont have all the archive log to recover it ,
plz help me out to solve this ..What is the version you are using?
Even though your primary database is in noarchive log mode before configuring data guard, still its not a problem. Follow high level steps as below
1) Take missing datafile on primary using RMAN (or) you can use tablespace backup with traditional method
2) copy that datafile from primary to standby system
3) Ensure you have properly set for DB_FILE_NAME_CONVERT(bounce required), and set standby_file_management to manual
4) take the dummy file and rename with the new file(step 2) by using alter database create command
5) later change standby_file_managment to auto & start MRP

Data guard synchronization after link down b/w primary and physical standby

Hi All,
I have configured data guard on oracle 11gr2 db. Normally switchover between my primary and physical standby happens smoothly and the Apply lag would be zero. Recently We had to test a scenario when the network link between Primary and Physical standby is completely down and Physical standby is isolated completely for more than half an hour.
When we brought up the link every thing worked smoothly but apply lag started increasing from 0 to around 3 hrs. And then it started reducing to 0. Currently Apply lag and transport lag shows 0.
But is this normal behaviour of oracle data guard that when the link between primary and physical standby is completely down, It requires 3-4 hrs for resynchronization ??? Even when during isolation, there were very few transactions happend on primary database ??
Are there any documents available for this scenario??
Thanks

Hi, after the link is up, if there were some transactions and produced archive logs it's normal to take some time for resync. To check if 3-4 hours is normal or not, you can repeat the scenario and this time check
- how many archivelogs does primary produce in this period.
- after the link is up, does archivelog transfer immediately starts from primary to standby? Is primary able to send these archivelogs parallel?
- Is there anything wrong with the apply process?
check primary & standby alert log files, and run this query on standby to check the transport and apply processes:
SELECT PROCESS, STATUS, THREAD#, SEQUENCE#, BLOCK#, BLOCKS FROM V$MANAGED_STANDBY;
regards

Failover to Physical Standby

Hi All,
I have a configured data guard in my local system . Please find the below configuration of the Data guard
Data Guard Type : - Physical Standby (Oracle version 11g)
Service Responsible for Log Transport : - ARCH
No Standby Redo log : - Neither in Primary Nor in Standby
I am trying to fail over by using command "alter database recover managed standby database finish"
Please find the below alert log info after this command .
Tue Dec 03 01:42:14 2013
alter database recover managed standby database finish
Attempt to do a Terminal Recovery (PRD)
Media Recovery Start: Managed Standby Recovery (PRD)
Fast Parallel Media Recovery enabled
Managed Standby Recovery not using Real Time Apply
Media Recovery Waiting for thread 1 sequence 145
Terminal Recovery timestamp is '12/03/2013 01:42:15'
Terminal Recovery: applying standby redo logs.
Terminal Recovery: thread 1 seq# 145 redo required
Media Recovery Waiting for thread 1 sequence 145
Terminal Recovery: End-Of-Redo log allocation
Terminal Recovery: standby redo logfile 3 created '/data/PRD_DR/arch/arch_1_0_831359165.arch'
This standby redo logfile is being created as part of the failover
operation. This standby redo logfile should be deleted after the
switchover to primary operation completes.
Media Recovery Log /data/PRD_DR/arch/arch_1_0_831359165.arch
Terminal Recovery: log 3 reserved for thread 1 sequence 145
Recovery of Online Redo Log: Thread 1 Group 3 Seq 145 Reading mem 0
Mem# 0: /data/PRD_DR/arch/arch_1_0_831359165.arch
Identified End-Of-Redo for thread 1 sequence 145
Incomplete recovery applied all redo ever generated.
Recovery completed through change 559773 time 11/23/2013 13:38:13
Media Recovery Complete (PRD)
Terminal Recovery: successful completion
Resetting standby activation ID 1895332757 (0x70f87b95)
Completed: alter database recover managed standby database finish
Tue Dec 03 01:42:50 2013
alter database commit to switchover to primary
ALTER DATABASE SWITCHOVER TO PRIMARY (PRD)
Maximum wait for role transition is 15 minutes.
Backup controlfile written to trace file /apps/oracle/diag/rdbms/stand/PRD/trace/PRD_ora_9466.trc
tkcrrxms: Killing 3 processes (all RFS)
Standby terminal recovery start SCN: 559772
RESETLOGS after complete recovery through change 559773
Online log /data/PRD_DR/REDOLOG11.LOG: Thread 1 Group 1 was previously cleared
Online log /data/PRD_DR/REDOLOG21.LOG: Thread 1 Group 2 was previously cleared
Standby became primary SCN: 559771
Tue Dec 03 01:42:53 2013
Here my question is , why oracle implicitly creates a standby redo log in Standby database for successful completion of 'alter database recover managed standby database finish'.
Thanks,

Terminal Recovery timestamp is '12/03/2013 01:42:15'
Terminal Recovery: applying standby redo logs.
Terminal Recovery: thread 1 seq# 145 redo required
Media Recovery Waiting for thread 1 sequence 145
Terminal Recovery: End-Of-Redo log allocation
Terminal Recovery: standby redo logfile 3 created '/data/PRD_DR/arch/arch_1_0_831359165.arch'
This standby redo logfile is being created as part of the failover
operation. This standby redo logfile should be deleted after the
switchover to primary operation completes.
Media Recovery Log /data/PRD_DR/arch/arch_1_0_831359165.arch
Terminal Recovery: log 3 reserved for thread 1 sequence 145
Recovery of Online Redo Log: Thread 1 Group 3 Seq 145 Reading mem 0
Mem# 0: /data/PRD_DR/arch/arch_1_0_831359165.arch
Identified End-Of-Redo for thread 1 sequence 145
Looks like, its due to the following bug.
Bug 5889025 : FINISH FAILOVER GENERATES INCORRECT STANDBY REDO LOG.

About physical standby database

We have physical standby database(10g). what are steps to put standby database in ready only mode for time being and then put it back in primary-secondary relationship once cheking is done?

Cancel the redo Apply
SQL>ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;Open The database
SQL>ALTER DATABASE OPEN;Do your stuff.
Once done, shut it down, then mount it again and resume the redo apply
SQL>SHUTDOWN IMMEDIATE;
SQL>STARTUP NOMOUNT;
SQL>ALTER DATABASE MOUNT STANDBY DATABASE;
SQL>ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT;If you use real-time redo apply, you may want to issue the following command instead of the previous one.
SQL>ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE DISCONNECT;...and pretty much that is it.
Be aware that while running it in read-only mode, no logs from the primary are being applied. Also you may hit some bugs when you open your standby database. So if this standby is your production one, make sure you know how to deal in a situation when you need to resolve possible issues.
Jason Arnell has explained one possible buggy scenario on his blog - LINK.
--Mihajlo

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....

Switchover to physical standby failed

Hi gurus,
Could anyone pls help for this issue, i'm working on oracle 9i dataguard in solaris box. we succesully switchover our physical standby to primary but when tried to bring back again to physical standby it is throwing an error
SQL> alter database commit to switchover to physical standby;
alter database commit to switchover to physical standby
ERROR at line 1:
ORA-16014: log 1 sequence# 91775 not archived, no available destinations
ORA-00312: online log 1 thread 1: '/oracle/u07/oradata/odb/redo_1a.log'
ORA-00312: online log 1 thread 1: '/oracle/u08/oradata/odb/redo_1b.log'
ORA-00312: online log 1 thread 1: '/oracle/u09/oradata/odb/redo_1c.log'
Please advice
regards,
shaan

Hi,
There is already a thread which you opened Up you can reply back in that..
switchover to physical standby failed
- Pavan Kumar N

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

Error while creating physical standby database using Oracle Grid 10.2.0.5

Hi All,
I am setting up data guard using oracle grid.
Primary database version: - 10.2.0.4
Standby database version: - 10.2.0.4
Primary OS Red Hat Enterprise Linux AS release 4 (Nahant Update 8)2.6.9
Standby OS Red Hat Enterprise Linux AS release 4 (Nahant Update 8)2.6.9
I am creating physical standby database using EM. But it is getting failed with error message in sqlnet.ora file
Fatal NI connect error 12533, connecting to:
(DESCRIPTION=(ADDRESS_LIST=)(CONNECT_DATA=(SERVICE_NAME=INPRDSB_XPT)(SERVER=dedicated)(CID=(PROGRAM=oracle)(HOST=indb50.oii.com)(USER=oracle))))
VERSION INFORMATION:
        TNS for Linux: Version 10.2.0.4.0 - Production
        TCP/IP NT Protocol Adapter for Linux: Version 10.2.0.4.0 - Production
Time: 17-AUG-2010 02:40:07
Tracing not turned on.
Tns error struct:
    ns main err code: 12533
    TNS-12533: TNS:illegal ADDRESS parameters
    ns secondary err code: 0
    nt main err code: 0
    nt secondary err code: 0As we can see, address_list is empty.
Can anyone suggest what could be the reason behind this?

Dear user13295317,
Here is the error explanation;
Oracle Error :: TNS-12533
TNS:illegal ADDRESS parameters
Cause
An illegal set of protocol adapter parameters was specified.
In some cases, this error is returned when a connection cannot be made to the protocol transport.
Action
Verify that the destination can be reached using the specified protocol.
Check the parameters within the ADDRESS section of TNSNAMES.ORA.
Legal ADDRESS parameter formats may be found in the Oracle operating system specific documentation for your platform.
Protocols that resolve names at the transport layer (such as DECnet object names) are vulnerable to this error if not properly configured or names are misspelled.Hope That Helps.
Ogan

Db_file parameter change in oracle 8i with physical standby configured

i have oracle 8i (8.1.7) with physical standby configured.
i need to change the db_file parameter value. kindly check the below steps are correct? Thanks.
1. alter database backup controlfile to trace;
2. edit the init.ora file as db_file=<new value> (after backing up the existing pfile)
3. edit the create control file statement in udump -- max datafile (and also remove the first line startup nomount)
4. shutdown immediate;
5. startup pfile ='file name';
6. in sqlplus run the create control file statement;
7. alter database backup controfl file for standby;
8. move the standby control file to standby db server
9. shutdown immediate in standby
10. copy the pfile and edit the new values
11. startup mount pfile='new pfile' (in standby)
12. recover control file <location> from rman
13. start the recovering of standby.
Thanks,
Raman.

Just change the db_files value to some higher value in the init.ora file and restart the database. With this you can create more datafiles no need to create control file.

Question-Recovering tablespace in physical Standby...Oracle 10g?

Hello:
I have an interesting issue. I thought I will ask the group.
I have a physical standby database in 10g. Once of the datafile is in inconsistent state due to a crashed DB during recovery from the last time around.
I do not have any archivelogs, either on standby or primary .. Unfortunately.
However, the primary database is alive and well.
How do I recover my datafile selectively? Is a complete restore/recreation of the standby is the only option?
Any ideas?
Thanks in advance.
Ganesh

read that link
http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/scenarios.htm#CIHIAADCKhurram

Oracle 10g physical standby error

Hi all,
We been frequently getting this error on our standby DB and not sure if it's network related or a possible configuration tuning.
RFS[425]: Assigned to RFS process 3640
RFS[425]: Identified database type as 'physical standby'
Primary database is in MAXIMUM PERFORMANCE mode
Primary database is in MAXIMUM PERFORMANCE mode
RFS[425]: No standby redo logfiles created
Mon Nov 23 09:47:28 2009
Fetching gap sequence in thread 1, gap sequence 35418-35418
Mon Nov 23 09:48:02 2009
FAL[client]: Failed to request gap sequence
GAP - thread 1 sequence 35418-35418
DBID 3292763437 branch 615642223
FAL[client]: All defined FAL servers have been attempted.
Check that the CONTROL_FILE_RECORD_KEEP_TIME initialization
parameter is defined to a value that is sufficiently large
enough to maintain adequate log switch information to resolve
archivelog gaps.
Mon Nov 23 09:48:17 2009
RFS[384]: No standby redo logfiles created
Mon Nov 23 09:48:21 2009
RFS[425]: Possible network disconnect with primary database
Closing latent archivelog for thread 1 sequence 35419
EOF located at block 1201 low SCN 0:-1055223653 next SCN 0:-1055223015
Latent archivelog 'E:\ORACLE\ARCH\xxxxx\LOG_615642223_1_35419.ARC'
If you wish to failover to this standby database, you should use the
following command to manually register the archivelog for recovery:
ALTER DATABASE REGISTER LOGFILE 'E:\ORACLE\ARCH\xxxxx\LOG_xxx615642223_1_35419.ARC';
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
RFS[426]: Assigned to RFS process 3200
RFS[426]: Identified database type as 'physical standby'
Primary database is in MAXIMUM PERFORMANCE mode
Primary database is in MAXIMUM PERFORMANCE mode
RFS[426]: No standby redo logfiles created
Any ideas?
thx

I've inherited this DB and never really looked at the settings.
The error I see in the primary DB is
FAL[server]: Fail to queue the whole FAL gap
Protection level on primary is
SQL> SELECT PROTECTION_MODE, PROTECTION_LEVEL FROM V$DATABASE;
PROTECTION_MODE PROTECTION_LEVEL
MAXIMUM PERFORMANCE MAXIMUM PERFORMANCE
Edited by: jrmtl on Nov 23, 2009 7:32 AM

How to apply Oracle patch when physical standby database in place

Dear All,
I want to apply Oracle patchset 8 on 10.2.0.5 when physical standby database in place. What are the steps for Primary site and for standby site.
Thanks in advance
Kamran Laeeq

Hi Kamran,
You will not upgrade or patch the standby database by importing offline redologs. On the contrary, there is a procedure to do this. Please note that you will not transitiate the role from standby to primary or startup the database. You will just startup the database by executing "startup mount" and "startup upgrade", during the upgrade. It means that you will not change database role standby to primary and you will be able to continue to the log shipment after the respective upgrade.
But, it is very important that you should stop the log shipment and apply all the offline redologs, before the upgrade. Technically, you can import offline redologs after the upgrade, by changing "compatibility" parameter in oracle, but regarding to my experiences it may cause some problems after you transitiate the role from standby to primary.
In short;
In order to stop log shipment, at the primary site;
alter system set log_archive_dest_state_2=defer;
In order to import all the offline redologs without a delay, at the standby site;
alter database recover managed standby database cancel;
alter database recover managed standby database nodelay disconnect from session;
I hope that I clarified the issue,
Best regards,
Orkun Gedik

Oracle DataGuard - Standy Redo log on physical Standby db

Hello Guys,
A quick question on my 10.2.0.2 db with Windows 2003 x64 OSs.
I have 2 machines - One for primary & the other for physical standby
I have successfully setup DG with Real Time Apply and also tested switchover & failover scenarios and they work well and as expected...
But I have a query which popped up when I was trying to set this up at home.
I create the physical standby db by shutting the primary db and copying all the datafiles, tempfiles,online redo logs and then creating a standby control file which will be used for the physical standby db to start off with.
After mounting the standby db, I tried to create standby redo logs files starting with Group 4 but I got error that standby group 4 already exists.
Upon querying v$logfile view, I noticed that the standby redo logs that I created on primary are also showing up on the standby db which I understand is from the standby control file.
So here is my quesiton: What is correct method of creating these standby redo logs on the standby database?
I know that I could drop those 4 standby redo logs from the standby db and recreate them but all the DG docs online and the documents that I have referred say that I should create the standby redo logs on the standby as I did on the primary but how can this duplication be avoided i.e. from the standby control file?
I know that I could use another method to create a hot backup such as RMAN etc...but I wanted to follow this way of shutting down the primary and copy the relevant database files.
Any help appreciated...and thanks in advance guys!
-Bharath

so with the setup that I used, i.e. create a standby control file which contains info about the standby redo logs at the primary site, should I also copy over the standby redo logs from the primary to standby as I only copied the datafiles, tempfile(s) & online redo logs? But then the filenames of the standby redo logs will be the exact same as that of the primary. Will that cause any issue during a switchover/failover?
I don't remember exactly how I did it when I got the whole thing working but I have a vague remembrance that I drop the std. redo log files entries from the std database and then recreate new ones with different filenames (as compared to primary).
Thanks

Oracle Configuration Manager 10.2.7 on physical standby database

Hi
Did anybody succeed to install and get running OCM on physical standby-database? When starting collection configuration script, i get
an known error ORA-01219.
Any help any tipps?
Felice

Hi Tom
Thank you for the information. I think it is the right place to install OCM - not standalone installation - software installed with Oracle Database Enterprise Edition. The problem is only that installCCRSQL.sh can't handle Mounted Database (Standby-Database).
We got similar problems with Grid Control Management Agents, when doing health checks.
Mayby there is as workaround/patch (Opatch).
Regards
Felice

Switchover to 1 of 3 Physical Standby (oracle 10g R2)

Similar Messages

Maybe you are looking for