Manual switchover

Hi all,
I am working on Oracle 10g EE (10.2.0.4).I have a standby configuration havim prim and standby database.I am doing manual switchover...
Switch-over Process
1.     Shutdown the primary database.
2.     Make sure all the archive logs are transferred and applied on DR site.
3.     Shutdown the standby database, Copy the controlfile and online redo log files of primary database to DR site.
4.     Copy the standby controlfile from DR site to primary site.
5.     Startup the primary database (Current standby database). Here we may have to do recovery to apply changes of online redo logfiles. This must be a complete recovery.
6.     Startup the standby database (Current primary).
7.     Check the databases & their role.
This method is working fine..for the file structure same for dc and dr.
But for the different file structure dc dr...this process is not working...
1.First I have checked the log sequence on both prim and standby. Then shut down both database, copied prim’s logfile,control file to standby and standby’s logfile,controlfile to prim.
2.But as the location is not same so the primary controlfile will not be able to identify standby location’s file.
3.I have backup control file to trace and then from trace I have created control file creation script.
4. The current prim(former standby ) is open now and working fine.
5.But not able to create controlfile for current standby(former prim) with error .
ora-01503 create controlfile failed ora-01192.
•     How to switchover standby database on different directory structure using manual switchover process.

I know these switchover stape, but in my case the shipping of redo/archivelog is not automatic due to excessive transaction and lower network bandwidth.
In my setup.. log shipping between prim and standby database is manual.I uses to zip logs from prim and register those logs to standby and then manually apply them to When you talk about excessive transactions and not been applied, Its again pain to copy all of them perform recovery. Again archive log data contains all data + changes (committed & Uncommitted) so in case of huge archive logs then go for incremental SCN rollforward instead of zipping unzipping & performing recover.
http://www.oracle-ckpt.com/rman-incremental-backups-to-roll-forward-a-physical-standby-database-2/
standby.In "prim" database log_archive_dest_state_2 is defer and also log_archive_config is not used.So general switchover is not possible.Control file and redolog
file copy method is OK.But i have the problem for same different directory structure on primary and standby site.When you have unset these parameters, There is no shipping between primary & standby, Even if you apply if directory structure different you can perform recovery. Use above link from my web site.
HTH.

Similar Messages

Manual\DGMGRL Switchover Standby ora-01033 error

I have created a standby server for my SAP application as a part of test Disaster Recovery scenario. I can see the redo logs getting applied from primary to standby. However when I manually switchover the roles i encounters ORA -01033 error at NEW PRIMARY server and logs are also not getting applied in this scenario.
When i again changes the roles it works fine. I am not sure what is cause of ORA -01033 error. Here are the detailed tnsnames.ora of both sites.
Primary Server
P11.WORLD=
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS =
(COMMUNITY = SAP.WORLD)
(PROTOCOL = TCP)
(HOST = 10.0.1.104)
(PORT = 1527)
(CONNECT_DATA =
(SID = P11)
(GLOBAL_NAME = P11.WORLD)
TO_STANDBY.WORLD=
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS =
(COMMUNITY = SAP.WORLD)
(PROTOCOL = TCP)
(HOST = 10.0.1.102)
(PORT = 1527)
(CONNECT_DATA =
(SID = P11)
(GLOBAL_NAME = TO_STANDBY.WORLD)
TO_PRIMARY.WORLD=
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS =
(COMMUNITY = SAP.WORLD)
(PROTOCOL = TCP)
(HOST = 10.0.1.104)
(PORT = 1527)
(CONNECT_DATA =
(SID = P11)
(GLOBAL_NAME = TO_PRIMARY.WORLD)
LISTENER_P11.WORLD=(address=(protocol= tcp)(host=10.0.1.104)(port= 1527))
Standby Site
TO_PRIMARY.WORLD=
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS =
(COMMUNITY = SAP.WORLD)
(PROTOCOL = TCP)
(HOST = 10.0.1.104)
(PORT = 1527)
(CONNECT_DATA =
(SID = P11)
(GLOBAL_NAME = TO_PRIMARY.WORLD)
P11.WORLD=
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS =
(COMMUNITY = SAP.WORLD)
(PROTOCOL = TCP)
(HOST = 10.0.1.104)
(PORT = 1527)
(CONNECT_DATA =
(SID = P11)
(GLOBAL_NAME = P11.WORLD)
TO_STANDBY.WORLD=
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS =
(COMMUNITY = SAP.WORLD)
(PROTOCOL = TCP)
(HOST = 10.0.1.102)
(PORT = 1527)
(CONNECT_DATA =
(SID = P11)
(GLOBAL_NAME = TO_STANDBY.WORLD)
LISTENER_P11.WORLD=(address=(protocol= tcp)(host=10.0.1.104)(port= 1527))
Now , when i enable the DGMGRL configuration and add standby database at primary the " log_archive_dest_2=''" goes empty . Here is the pfile of primary after enable of the DGMGRL.
pfile of Primary
*._B_TREE_BITMAP_PLANS=FALSE
*._IN_MEMORY_UNDO=FALSE
*._INDEX_JOIN_ENABLED=FALSE
*._OPTIM_PEEK_USER_BINDS=FALSE
*._OPTIMIZER_MJC_ENABLED=FALSE
*._SORT_ELIMINATION_COST_RATIO=10
*._TABLE_LOOKUP_PREFETCH_SIZE=0
*.archive_lag_target=0
*.background_dump_dest='D:\oracle\P11\saptrace\background'
*.compatible='10.2.0'
*.control_file_record_keep_time=30
*.control_files='D:\oracle\P11\origlogA\cntrl\cntrlP11.dbf','D:\oracle\P11\origlogB\cntrl\cntrlP11.dbf','D:\oracle\P11\sapdata1\cntrl\cntrlP11.dbf'
*.core_dump_dest='D:\oracle\P11\saptrace\background'
*.db_block_size=8192
*.db_cache_size=260938137
*.db_files=254
*.db_name='P11'
*.db_unique_name='P11_primary'
*.dg_broker_start=TRUE
*.dml_locks=4000
*.event='10191 trace name context forever, level 1'
*.FAL_Client='to_primary'
*.FAL_Server='to_standby'
*.FILESYSTEMIO_OPTIONS='setall'
*.job_queue_processes=1
*.log_archive_config='nodg_config'
*.log_archive_dest_1='LOCATION=C:\oracle\P11\oraarch\P11arch VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=P11_primary'
p11.log_archive_dest_1='location="C:\oracle\P11\oraarch\P11arch"','valid_for=(ONLINE_LOGFILE,ALL_ROLES)'
*.log_archive_dest_2=''
*.log_archive_dest_state_1='enable'
p11.log_archive_dest_state_1='ENABLE'
*.log_archive_dest_state_2='ENABLE'
p11.log_archive_format='ARC%S_%R.%T'
*.log_archive_max_processes=10
*.log_archive_min_succeed_dest=1
p11.log_archive_trace=0
*.log_buffer=1048576
*.log_checkpoint_interval=0
*.log_checkpoints_to_alert=true
*.open_cursors=800
*.parallel_execution_message_size=16384
*.pga_aggregate_target=347917516
*.processes=80
*.query_rewrite_enabled='false'
*.recyclebin='off'
*.remote_login_passwordfile='exclusive'
*.remote_os_authent=true
*.replication_dependency_tracking=false
*.sessions=96
*.sga_max_size=521876275
*.shared_pool_reserved_size=26093813
*.shared_pool_size=300938137
*.sort_area_retained_size=0
*.sort_area_size=2097152
p11.standby_archive_dest=''
*.standby_file_management='AUTO'
*.star_transformation_enabled='true'
*.undo_management='AUTO'
*.undo_retention=43200
*.undo_tablespace='PSAPUNDO'
*.user_dump_dest='D:\oracle\P11\saptrace\usertrace'
pfile of standy DB
*._B_TREE_BITMAP_PLANS=FALSE
*._IN_MEMORY_UNDO=FALSE
*._INDEX_JOIN_ENABLED=FALSE
*._OPTIM_PEEK_USER_BINDS=FALSE
*._OPTIMIZER_MJC_ENABLED=FALSE
*._SORT_ELIMINATION_COST_RATIO=10
*._TABLE_LOOKUP_PREFETCH_SIZE=0
*.background_dump_dest='D:\oracle\P11\saptrace\background'
*.compatible='10.2.0'
*.control_file_record_keep_time=30
*.control_files='D:\oracle\P11\origlogA\cntrl\control01.ctl','D:\oracle\P11\origlogB\cntrl\control02.ctl','D:\oracle\P11\sapdata1\cntrl\control03.ctl'
*.core_dump_dest='D:\oracle\P11\saptrace\background'
*.db_block_size=8192
*.db_cache_size=155870822
*.db_files=254
*.db_name='P11'
*.db_unique_name='P11_disaster'
*.dg_broker_start=TRUE
*.dml_locks=4000
*.event='10191 trace name context forever, level 1'
*.FAL_Client='to_standby'
*.FAL_Server='to_primary'
*.FILESYSTEMIO_OPTIONS='setall'
*.job_queue_processes=1
*.log_archive_config='DG_CONFIG= (P11_primary, P11_disaster)'
*.log_archive_dest_1='LOCATION=C:\oracle\P11\oraarch\P11arch VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=P11_disaster'
*.log_archive_dest_2='SERVICE=to_primary LGWR ASYNC DELAY=5 VALID_FOR=(ONLINE_LOGFILES, PRIMARY_ROLE) DB_UNIQUE_NAME=P11_primary'
*.log_archive_dest_state_1='enable'
*.log_archive_dest_state_2='enable'
*.log_archive_max_processes=10
*.log_buffer=1048576
*.log_checkpoint_interval=0
*.log_checkpoints_to_alert=true
*.open_cursors=800
*.parallel_execution_message_size=16384
*.pga_aggregate_target=207827763
*.processes=80
*.query_rewrite_enabled='false'
*.recyclebin='off'
*.remote_login_passwordfile='exclusive'
*.remote_os_authent=true
*.replication_dependency_tracking=false
*.sessions=96
*.sga_max_size=311741644
*.shared_pool_reserved_size=15587082
*.shared_pool_size=300870822
*.sort_area_retained_size=0
*.sort_area_size=2097152
*.standby_file_management='AUTO'
*.star_transformation_enabled='true'
*.undo_management='AUTO'
*.undo_retention=43200
*.undo_tablespace='PSAPUNDO'
*.user_dump_dest='D:\oracle\P11\saptrace\usertrace'
Here are the alert logs of primary DB.
LTER SYSTEM SET log_archive_dest_2='service="(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=PROD102)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=p11_disaster_XPT)(INSTANCE_NAME=p11)(SERVER=dedicated)))"',' ARCH SYNC NOAFFIRM delay=5 OPTIONAL max_failure=0 max_connections=1 reopen=300 db_unique_name="p11_disaster" register net_timeout=180 valid_for=(online_logfile,primary_role)' SCOPE=BOTH;
Sat Jul 02 16:29:22 2011
ALTER SYSTEM SET log_archive_dest_state_2='ENABLE' SCOPE=BOTH;
Sat Jul 02 16:29:22 2011
ALTER SYSTEM SET log_archive_trace=0 SCOPE=BOTH SID='p11';
Sat Jul 02 16:29:22 2011
ALTER SYSTEM SET log_archive_format='ARC%S_%R.%T' SCOPE=SPFILE SID='p11';
Sat Jul 02 16:29:22 2011
ALTER SYSTEM SET standby_archive_dest='' SCOPE=BOTH SID='p11';
Sat Jul 02 16:29:22 2011
ALTER SYSTEM SET log_archive_dest_1='location="C:\oracle\P11\oraarch\P11arch"','valid_for=(ONLINE_LOGFILE,ALL_ROLES)' SCOPE=BOTH SID='p11';
Sat Jul 02 16:29:23 2011
ALTER SYSTEM SET log_archive_dest_state_1='ENABLE' SCOPE=BOTH SID='p11';
Sat Jul 02 16:29:23 2011
ALTER SYSTEM SET standby_file_management='AUTO' SCOPE=BOTH SID='*';
Sat Jul 02 16:29:23 2011
ALTER SYSTEM SET archive_lag_target=0 SCOPE=BOTH SID='*';
Sat Jul 02 16:29:23 2011
ALTER SYSTEM SET log_archive_max_processes=10 SCOPE=BOTH SID='*';
Sat Jul 02 16:29:23 2011
ALTER SYSTEM SET log_archive_min_succeed_dest=1 SCOPE=BOTH SID='*';
Sat Jul 02 16:29:27 2011
Beginning log switch checkpoint up to RBA [0x3b7.2.10], SCN: 7939485
Thread 1 advanced to log sequence 951
Current log# 4 seq# 951 mem# 0: D:\ORACLE\P11\ORIGLOGB\LOG_G14M1.DBF
Current log# 4 seq# 951 mem# 1: C:\ORACLE\P11\MIRRLOGB\LOG_G14M2.DBF
Sat Jul 02 16:29:28 2011
ALTER SYSTEM SET log_archive_dest_2='service="(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=PROD102)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=p11_disaster_XPT)(INSTANCE_NAME=p11)(SERVER=dedicated)))"',' ARCH SYNC NOAFFIRM delay=5 OPTIONAL max_failure=0 max_connections=1 reopen=300 db_unique_name="p11_disaster" register net_timeout=180 valid_for=(online_logfile,primary_role)' SCOPE=BOTH;
Sat Jul 02 16:29:28 2011
ALTER SYSTEM SET log_archive_dest_state_2='ENABLE' SCOPE=BOTH;
Beginning log switch checkpoint up to RBA [0x3b8.2.10], SCN: 7939487
Thread 1 advanced to log sequence 952
Current log# 2 seq# 952 mem# 0: D:\ORACLE\P11\ORIGLOGB\LOG_G12M1.DBF
Current log# 2 seq# 952 mem# 1: C:\ORACLE\P11\MIRRLOGB\LOG_G12M2.DBF
Sat Jul 02 16:29:29 2011
Error 12541 received logging on to the standby
Check whether the listener is up and running.
Sat Jul 02 16:29:29 2011
Errors in file d:\oracle\p11\saptrace\background\p11_arc1_2396.trc:
ORA-12541: TNS:no listener
FAL[server, ARC1]: Error 12541 creating remote archivelog file '(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=PROD102)(PORT=1521)))(CONNECT_DATA=
Here is the Alert log of standby
RFS[2]: Identified database type as 'physical standby'
Sat Jul 02 16:21:00 2011
RFS[3]: Assigned to RFS process 1620
RFS[3]: Identified database type as 'physical standby'
Sat Jul 02 16:21:00 2011
RFS[2]: Archived Log: 'C:\ORACLE\P11\ORAARCH\P11ARCH\ARC00947_0755040789.001'
Sat Jul 02 16:21:00 2011
RFS[3]: Archived Log: 'C:\ORACLE\P11\ORAARCH\P11ARCH\ARC00948_0755040789.001'
Sat Jul 02 16:21:00 2011
Media Recovery Log C:\ORACLE\P11\ORAARCH\P11ARCH\ARC00947_0755040789.001
Identified End-Of-Redo for thread 1 sequence 947
Sat Jul 02 16:21:01 2011
Media Recovery End-Of-Redo indicator encountered
Sat Jul 02 16:21:01 2011
Media Recovery Applied until change 7934481
Media Recovery archivelogs detected beyond End-Of-REDO
Resetting standby activation ID 1369083708 (0x519a8f3c)
Completed: Alter Database Recover Managed Standby Database
Sat Jul 02 16:21:29 2011
Alter Database Recover Managed Standby Database Disconnect
MRP0 started with pid=28, OS id=996
Managed Standby Recovery not using Real Time Apply
parallel recovery started with 2 processes
Clearing online redo logfile 1 D:\ORACLE\P11\ORIGLOGA\LOG_G11M1.DBF
Clearing online log 1 of thread 1 sequence number 949
Sat Jul 02 16:21:36 2011
Completed: Alter Database Recover Managed Standby Database Disconnect
Sat Jul 02 16:21:37 2011
Clearing online redo logfile 1 complete
Clearing online redo logfile 2 D:\ORACLE\P11\ORIGLOGB\LOG_G12M1.DBF
Clearing online log 2 of thread 1 sequence number 946
Clearing online redo logfile 2 complete
Clearing online redo logfile 3 D:\ORACLE\P11\ORIGLOGA\LOG_G13M1.DBF
Clearing online log 3 of thread 1 sequence number 944
Clearing online redo logfile 3 complete
Clearing online redo logfile 4 D:\ORACLE\P11\ORIGLOGB\LOG_G14M1.DBF
Clearing online log 4 of thread 1 sequence number 945
Clearing online redo logfile 4 complete
Media Recovery Log C:\ORACLE\P11\ORAARCH\P11ARCH\ARC00948_0755040789.001
Media Recovery Waiting for thread 1 sequence 949
Sat Jul 02 16:22:37 2011
RFS[1]: No standby redo logfiles created
RFS[1]: Archived Log: 'C:\ORACLE\P11\ORAARCH\P11ARCH\ARC00949_0755040789.001'
Sat Jul 02 16:22:37 2011
RFS[1]: Archive log thread 1 sequence 949 available in 5 minute(s)
Sat Jul 02 16:22:37 2011
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
RFS[4]: Assigned to RFS process 2200
RFS[4]: Identified database type as 'physical standby'
Primary database is in MAXIMUM PERFORMANCE mode
Primary database is in MAXIMUM PERFORMANCE mode
RFS[4]: No standby redo logfiles created
Sat Jul 02 16:22:38 2011
Media Recovery Delayed for 5 minute(s) (thread 1 sequence 949)
Sat Jul 02 16:27:38 2011
Media Recovery Log C:\ORACLE\P11\ORAARCH\P11ARCH\ARC00949_0755040789.001
Media Recovery Waiting for thread 1 sequence 950 (in transit)
Sat Jul 02 16:29:42 2011
RFS[4]: Possible network disconnect with primary database
Aborting archivelog file creation: C:\ORACLE\P11\ORAARCH\P11ARCH\ARC00950_0755040789.001
If this a network disconnect, then this archivelog will be fetched again
by GAP resolution mechanism.
Please advice as i am not sure of i have created something in listener file for DGMGRL configuration..
Regards

DGMGRL> show configuration
Configuration
Name: my_dg
Enabled: YES
Protection Mode: MaxPerformance
Fast-Start Failover: DISABLED
Databases:
P11_primary - Primary database
P11_disaster - Physical standby database
Current status for "my_dg":
Warning: ORA-16607: one or more databases have failed
DGMGRL> SHOW DATABASE 'P11_primary' 'StatusReport';
STATUS REPORT
INSTANCE_NAME SEVERITY ERROR_TEXT
p11 ERROR ORA-16737: the redo transport service for standby database "P11_disaster" has an error
p11 WARNING ORA-16715: redo transport-related property LogXptMode of standby database "P11_disaster" is inconsistent
DGMGRL> SHOW DATABASE 'P11_primary' 'LogXptStatus';
LOG TRANSPORT STATUS
PRIMARY_INSTANCE_NAME STANDBY_DATABASE_NAME STATUS
p11 P11_disaster ORA-12541: TNS:no listener
After this when i check the status of listener at P11_disaster site it was up . I restarted the listener and found following message in listener log at standby ( p11_primary) . These are the last lines of listener log.
03-JUL-2011 13:36:40 * (CONNECT_DATA=(SID=P11)(GLOBAL_NAME=TO_STANDBY.WORLD)(CID=(PROGRAM=d:\oracle\p11\102\bin\ORACLE.EXE)(HOST=PROD104)(USER=SYSTEM))) * (ADDRESS=(PROTOCOL=tcp)(HOST=10.0.1.104)(PORT=2244)) * establish * P11 * 0
03-JUL-2011 13:36:40 * (CONNECT_DATA=(SID=P11)(GLOBAL_NAME=TO_STANDBY.WORLD)(CID=(PROGRAM=d:\oracle\p11\102\bin\ORACLE.EXE)(HOST=PROD104)(USER=SYSTEM))) * (ADDRESS=(PROTOCOL=tcp)(HOST=10.0.1.104)(PORT=2245)) * establish * P11 * 0
03-JUL-2011 13:45:25 * ping * 0
No longer listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=\\.\pipe\P11.WORLDipc)))
No longer listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=\\.\pipe\P11ipc)))
No longer listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=10.0.1.102)(PORT=1527)))
Listener completed notification to CRS on stop
03-JUL-2011 13:45:34 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=)(USER=p11adm))(COMMAND=stop)(ARGUMENTS=64)(SERVICE=LISTENER)(VERSION=169869824)) * stop * 0
TNSLSNR for 64-bit Windows: Version 10.2.0.2.0 - Production on 03-JUL-2011 13:45:42
Copyright (c) 1991, 2005, Oracle. All rights reserved.
System parameter file is D:\oracle\P11\102\network\admin\listener.ora
Log messages written to D:\oracle\P11\102\network\log\listener.log
Trace information written to D:\oracle\P11\102\network\trace\listener.trc
Trace level is currently 0
Started with pid=624
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=\\.\pipe\P11.WORLDipc)))
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=\\.\pipe\P11ipc)))
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=10.0.1.102)(PORT=1527)))
Listener completed notification to CRS on start
TIMESTAMP * CONNECT DATA [* PROTOCOL INFO] * EVENT [* SID] * RETURN CODE
03-JUL-2011 13:45:46 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=)(USER=p11adm))(COMMAND=status)(ARGUMENTS=64)(SERVICE=LISTENER)(VERSION=169869824)) * status * 0
I am sure this is some configuration issue , however does not have clue :(

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

Question about broker Switchover command

Hi guys
i have one question about switchover cmd . For example, i have 1 primary database called stdby3 and 2 standby databases that are called stdby1 and stdby2. When i performed switchover cmd to stdby2 standby database, why the old primary database stdby3 could not become new standby database after i performed a switchover; furthermore the new primary and standby databases are not opened after the switchover process is completed
output screen:
DGMGRL> show configuration;
Configuration
Name: stdby1
Enabled: YES
Protection Mode: MaxProtection
Databases:
stdby3 - Primary database
stdby1 - Physical standby database
stdby2 - Physical standby database
Fast-Start Failover: DISABLED
Current status for "stdby1":
SUCCESS
DGMGRL> SWITCHOVER TO stdby2
Performing switchover NOW, please wait...
Operation requires shutdown of instance "stdby3" on database "stdby3"
Shutting down instance "stdby3"...
ORA-01109: database not open
Database dismounted.
ORACLE instance shut down.
Operation requires shutdown of instance "stdby2" on database "stdby2"
Shutting down instance "stdby2"...
ORA-01109: database not open
Database dismounted.
ORACLE instance shut down.
Operation requires startup of instance "stdby3" on database "stdby3"
Starting instance "stdby3"...
Unable to connect to database
ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
Failed.
You are no longer connected to ORACLE
Please connect again.
Unable to start instance "stdby3"
You must start instance "stdby3" manually
Operation requires startup of instance "stdby2" on database "stdby2"
You must start instance "stdby2" manually
Switchover succeeded, new primary is "stdby2"
DGMGRL> show configuration;
Error:
ORA-01034: ORACLE not available
Process ID: 0
Session ID: 130 Serial number: 45
DGMGRL> exit;
oracle@localhost ~$ dgmgrl
DGMGRL for Linux: Version 11.1.0.6.0 - Production
Copyright (c) 2000, 2005, Oracle. All rights reserved.
Welcome to DGMGRL, type "help" for information.
DGMGRL> connect sys
Password:
Connected.
DGMGRL> show configuration;
Error:
ORA-01034: ORACLE not available
Process ID: 0
Session ID: 0 Serial number: 0
DGMGRL> connect sys@stdby3
Password:
Connected.
DGMGRL> show configuration;
Error:
ORA-01034: ORACLE not available
Process ID: 0
Session ID: 0 Serial number: 0
DGMGRL>
Edited by: user6981287 on Jan 6, 2010 9:27 AM

this is my configuration
DGMGRL> show configuration
Configuration
Name: matrix
Enabled: YES
Protection Mode: MaxPerformance
Databases:
stdby1 - Primary database
stdby2 - Physical standby database
stdby3 - Physical standby database
Fast-Start Failover: DISABLED
Current status for "matrix":
SUCCESS
--- this is my first successful switchover -----
DGMGRL> switchover to stdby2
Performing switchover NOW, please wait...
New primary database "stdby2" is opening...
Operation requires shutdown of instance "stdby1" on database "stdby1"
Shutting down instance "stdby1"...
ORA-01109: database not open
Database dismounted.
ORACLE instance shut down.
Operation requires startup of instance "stdby1" on database "stdby1"
Starting instance "stdby1"...
ORACLE instance started.
Database mounted.
Switchover succeeded, new primary is "stdby2"
-------------------this is my second switchover -------------
DGMGRL> switchover to stdby1
Performing switchover NOW, please wait...
New primary database "stdby1" is opening...
Operation requires shutdown of instance "stdby2" on database "stdby2"
Shutting down instance "stdby2"...
ORA-01109: database not open
Database dismounted.
ORACLE instance shut down.
Operation requires startup of instance "stdby2" on database "stdby2"
Starting instance "stdby2"...
Unable to connect to database
ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
Failed.
You are no longer connected to ORACLE
Please connect again.
Unable to start instance "stdby2"
You must start instance "stdby2" manually
Switchover succeeded, new primary is "stdby1"
DGMGRL>
Edited by: user6981287 on Jan 7, 2010 12:57 AM
Edited by: user6981287 on Jan 7, 2010 1:00 AM

Question re dgmgrl switchover

oracle 10.2.0.4 on OEL 5.4
My lab is Two machines running under VMworkstation on my laptop
Primary database 'houston' is on server vmlnx01
physical standby 'smyrna' is on server vmlnx02.
Everything seems to be working - albiet a bit slow - but when I tested the switchover . . . this log is from the primary - houston on vmlnx01
DGMGRL> connect sys/halftrack
Connected.
DGMGRL> switchover to smyrna;
Performing switchover NOW, please wait...
Operation requires shutdown of instance "houston" on database "houston"
Shutting down instance "houston"...
ORA-01109: database not openOdd ... why would it report database not open .. it most certainly is, and I was watching the alert log (tail -f alert*) in another putty session
Database dismounted.
ORACLE instance shut down.
Operation requires shutdown of instance "smyrna" on database "smyrna"
Shutting down instance "smyrna"...
ORA-01109: database not openthat one makes sense, that is the standby that was in MOUNT, not OPEN
Database dismounted.
ORACLE instance shut down.
Operation requires startup of instance "houston" on database "houston"
Starting instance "houston"...
Unable to connect to database
ORA-12514: TNS:listener does not currently know of service requested in connect descriptorhuh??? I'm not depending on dynamic registration. A quick check of the listener status on this box shows
Service "houston" has 2 instance(s).
Instance "houston", status UNKNOWN, has 1 handler(s) for this service...
Instance "houston", status READY, has 1 handler(s) for this service...and continuing with the console log (not the alert log)
Failed.
You are no longer connected to ORACLE
Please connect again.
Unable to start instance "houston"
You must start instance "houston" manually
Operation requires startup of instance "smyrna" on database "smyrna"
You must start instance "smyrna" manually
Switchover succeeded, new primary is "smyrna"
DGMGRL> exit
[oracle@vmlnx01 ~]$ sqlpulus / as sysdba
SQL*Plus: Release 10.2.0.4.0 - Production on Thu May 5 11:16:19 2011
Copyright (c) 1982, 2007, Oracle. All Rights Reserved.
Connected to an idle instance.
SQL> startup mount
ORACLE instance started.
Total System Global Area 285212672 bytes
Fixed Size 1267068 bytes
Variable Size 100665988 bytes
Database Buffers 180355072 bytes
Redo Buffers 2924544 bytes
Database mounted.
SQL> exit

Nothing in B14239-05 as far as I can see.
OK, this is a mission, will setup another test on my last 10G server.
mseberg
Have Database is 10.2.0.4.0 running on Linux (Red Hat AS 4) 64 bit OS and Database.
Primary = SMYRNA
Standby = HOUSTON
Data Guard working, will setup Broker soon.
Edited by: mseberg on May 10, 2011 11:42 AM
Summary
Broker barked at me hard but "Make sure that the /etc/hosts files have entries of all other servers, with name and IP address." seemed to fix that
Database is 10.2.0.4.0 running on Linux (Red Hat AS 4) 64 bit OS and Database.
Primary = SMYRNA
INIT file after creation of Database is :
SMYRNA.__db_cache_size=889192448
SMYRNA.__java_pool_size=16777216
SMYRNA.__large_pool_size=16777216
SMYRNA.__shared_pool_size=285212672
SMYRNA.__streams_pool_size=0
*.audit_file_dest='/u01/app/oracle/admin/SMYRNA/adump'
*.background_dump_dest='/u01/app/oracle/admin/SMYRNA/bdump'
*.compatible='10.2.0.3.0'
*.control_files='/u01/app/oracle/oradata/SMYRNA/control01.ctl','/u01/app/oracle/oradata/SMYRNA/control02.ctl','/u01/app/oracle/oradata/SMYRNA/control03.ctl'
*.core_dump_dest='/u01/app/oracle/admin/SMYRNA/cdump'
*.db_block_size=8192
*.db_domain='MYDOMAIN'
*.db_file_multiblock_read_count=16
*.db_name='SMYRNA'
*.db_recovery_file_dest='/u01/app/oracle/flash_recovery_area'
*.db_recovery_file_dest_size=2147483648
*.dispatchers='(PROTOCOL=TCP) (SERVICE=SMYRNAXDB)'
*.job_queue_processes=10
*.open_cursors=300
*.pga_aggregate_target=406847488
*.processes=150
*.remote_login_passwordfile='EXCLUSIVE'
*.sga_target=1221591040
*.undo_management='AUTO'
*.undo_tablespace='UNDOTBS1'
*.user_dump_dest='/u01/app/oracle/admin/SMYRNA/udump'
Flashback and Archivelog are on. Logging is forced.
3 standby redo logs were created :
ALTER DATABASE ADD STANDBY LOGFILE GROUP 4 '/u01/app/oracle/oradata/SMYRNA/redo04.log' SIZE 50M;
ALTER DATABASE ADD STANDBY LOGFILE GROUP 5 '/u01/app/oracle/oradata/SMYRNA/redo05.log' SIZE 50M;
ALTER DATABASE ADD STANDBY LOGFILE GROUP 6 '/u01/app/oracle/oradata/SMYRNA/redo06.log' SIZE 50M;
The following is added to the INIT file :
*.FAL_SERVER=HOUSTON
*.FAL_CLIENT=SMYRNA
*.STANDBY_FILE_MANAGEMENT=AUTO
*.DB_UNIQUE_NAME=SMYRNA
*.log_archive_dest_1='LOCATION=USE_DB_RECOVERY_FILE_DEST VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=SMYRNA'
*.log_archive_dest_2='SERVICE=HOUSTON LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE)'
*.LOG_ARCHIVE_DEST_STATE_1=ENABLE
*.LOG_ARCHIVE_DEST_STATE_2=ENABLE
*.LOG_ARCHIVE_MAX_PROCESSES=30
Shutdown the database
startup nomount pfile='/u01/app/oracle/admin/SMYRNA/pfile/initSMYRNA.ora';
create spfile from pfile='/u01/app/oracle/admin/SMYRNA/pfile/initSMYRNA.ora';
shutdown immediate
scp the database file to the same directory on the standby server.
Standby INIT is as follows :
SMYRNA.__db_cache_size=889192448
SMYRNA.__java_pool_size=16777216
SMYRNA.__large_pool_size=16777216
SMYRNA.__shared_pool_size=285212672
SMYRNA.__streams_pool_size=0
*.audit_file_dest='/u01/app/oracle/admin/SMYRNA/adump'
*.background_dump_dest='/u01/app/oracle/admin/SMYRNA/bdump'
*.compatible='10.2.0.3.0'
*.control_files='/u01/app/oracle/oradata/SMYRNA/control01.ctl','/u01/app/oracle/oradata/SMYRNA/control02.ctl','/u01/app/oracle/oradata/SMYRNA/control03.ctl'
*.core_dump_dest='/u01/app/oracle/admin/SMYRNA/cdump'
*.db_block_size=8192
*.db_domain='MYDOMAIN'
*.db_file_multiblock_read_count=16
*.db_name='SMYRNA'
*.db_recovery_file_dest='/u01/app/oracle/flash_recovery_area'
*.db_recovery_file_dest_size=2147483648
*.dispatchers='(PROTOCOL=TCP) (SERVICE=HOUSTONXDB)'
*.job_queue_processes=10
*.open_cursors=300
*.pga_aggregate_target=406847488
*.processes=150
*.remote_login_passwordfile='EXCLUSIVE'
*.sga_target=1221591040
*.undo_management='AUTO'
*.undo_tablespace='UNDOTBS1'
*.user_dump_dest='/u01/app/oracle/admin/SMYRNA/udump'
*.FAL_SERVER=SMYRNA
*.FAL_CLIENT=HOUSTON
*.STANDBY_FILE_MANAGEMENT=AUTO
*.DB_UNIQUE_NAME=HOUSTON
*.log_archive_dest_1='LOCATION=USE_DB_RECOVERY_FILE_DEST VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=HOUSTON'
*.log_archive_dest_2='SERVICE=SMYRNA LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE)'
*.LOG_ARCHIVE_DEST_STATE_1=ENABLE
*.LOG_ARCHIVE_DEST_STATE_2=DEFER
*.LOG_ARCHIVE_MAX_PROCESSES=30
On the Primary
startup mount;
alter database create standby controlfile as 'STANDBY.ctl';
Listener on Primary
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(SID_NAME = PLSExtProc)
(ORACLE_HOME = /u01/app/oracle/product/10.2.0)
(PROGRAM = extproc)
(SID_DESC =
(global_dbname = SMYRNA_DGMGRL.mydomain)
(ORACLE_HOME = /u01/app/oracle/product/10.2.0)
(sid_name = SMYRNA)
Listener on Standby
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(SID_NAME = PLSExtProc)
(ORACLE_HOME = /u01/app/oracle/product/10.2.0)
(PROGRAM = extproc)
SID_DESC =
(global_dbname = HOUSTON_DGMGRL.mydomain)
(ORACLE_HOME = /u01/app/oracle/product/10.2.0)
(sid_name = HOUSTON)
Oracle Net on Primary
SMYRNA =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = primary.server)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = SMYRNA.MYDOMAIN)
HOUSTON =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = standby.server)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = HOUSTON.MYDOMAIN)
Oracle Net on Standby
SMYRNA =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = primary.server)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = SMYRNA.MYDOMAIN)
HOUSTON =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = standby.server)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = HOUSTON.MYDOMAIN)
TNSPING test successful.
Copy /u01/app/oracle/product/10.2.0/dbs/orapwSMYRNA to Standby server and rename to orapwHOUSTON
Standby control file copied to HOUSTON server and renamed to replace control file(s).
cp /u01/app/oracle/oradata/SMYRNA/STANDBY.ctl /u01/app/oracle/oradata/SMYRNA/control01.ctl
cp /u01/app/oracle/oradata/SMYRNA/STANDBY.ctl /u01/app/oracle/oradata/SMYRNA/control02.ctl
cp /u01/app/oracle/oradata/SMYRNA/STANDBY.ctl /u01/app/oracle/oradata/SMYRNA/control03.ctl
Sid is changed
export ORACLE_SID=HOUSTON
startup nomount pfile='/u01/app/oracle/admin/SMYRNA/pfile/initSMYRNA.ora';
create spfile from pfile='/u01/app/oracle/admin/SMYRNA/pfile/initSMYRNA.ora';
Shutdown database
startup mount;
alter database recover managed standby database disconnect from session;
Open the primary database
Check and Data Guard is working.
-----BROKER CONFIGURATION-----
On both Primary and Standby sites, change the initialization parameter in the spfile to enable the Data guard broker.
Alter system set dg_broker_start=True scope=both;
DGMGRL> connect sys/password@SMYRNA
create configuration 'broker1' as
primary database is 'SMYRNA'
connect identifier is 'SMYRNA';
Configuration "?broker1?" created with SMYRNA database "SMYRNA"
DGMGRL>
DGMGRL> add database 'HOUSTON' as
connect identifier is 'HOUSTON'
maintained as physical;
Database "HOUSTON" added
DGMGRL>
Note: Create the HOUSTON in the SMYRNA DGMGRL
DGMGRL> SHOW CONFIGURATION;
Warning: ORA-16610: command 'Broker automatic health check' in progress
Make sure that the /etc/hosts files have entries of all other servers, with name and IP address.
Warning: ORA-16610: command 'EDIT DATABASE HOUSTON SET PROPERTY' in progress
But if you wait...
DGMGRL> SHOW CONFIGURATION;
Configuration
Name: broker1
Enabled: YES
Protection Mode: MaxPerformance
Fast-Start Failover: DISABLED
Databases:
SMYRNA - Primary database
HOUSTON - Physical standby database
Current status for "broker1":
SUCCESS
DGMGRL> SWITCHOVER TO "HOUSTON"
Performing switchover NOW, please wait...
Operation requires shutdown of instance "SMYRNA" on database "SMYRNA"
Shutting down instance "SMYRNA"...
ORA-01109: database not open
Database dismounted.
ORACLE instance shut down.
Operation requires shutdown of instance "HOUSTON" on database "HOUSTON"
Shutting down instance "HOUSTON"...
ORA-01109: database not open
Database dismounted.
ORACLE instance shut down.
Operation requires startup of instance "SMYRNA" on database "SMYRNA"
Starting instance "SMYRNA"...
ORACLE instance started.
Database mounted.
Operation requires startup of instance "HOUSTON" on database "HOUSTON"
Starting instance "HOUSTON"...
ORACLE instance started.
Database mounted.
Switchover succeeded, new primary is "HOUSTON"
DGMGRL>
Hope this helps
mseberg
Edited by: mseberg on May 10, 2011 3:34 PM
If you have to remove broker this note is worth a look :
How to Safely Remove a Data Guard Broker Configuration [ID 261336.1]
Edited by: mseberg on May 10, 2011 4:00 PM

Switchover using dgmgrl throwing ORA-12514: TNS:listener does not

Hi,
oracle version : 11.1.0.7
os : sun soalris
i am able to switchover the roles of primary and standby but i am getting this error
DGMGRL> switchover to qecgpoca;
Performing switchover NOW, please wait...
New primary database "qecgpoca" is opening...
Operation requires shutdown of instance "qecgpoce" on database "qecgpoce"
Shutting down instance "qecgpoce"...
ORA-01109: database not open
Database dismounted.
ORACLE instance shut down.
Operation requires startup of instance "qecgpoce" on database "qecgpoce"
Starting instance "qecgpoce"...
Unable to connect to database
ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
Failed.
You are no longer connected to ORACLE
Please connect again.
Unable to start instance "qecgpoce"
You must start instance "qecgpoce" manually
Switchover succeeded, new primary is "qecgpoca"i have set db_unique_name_DGMGRL for listener still i am getting
appreciated any inputs..
Thanks
Prakash

Review the basics:
1. ORACLE_HOME
2. ORACLE_SID
3. ping
4. tnsping
5. the docs

Getting ORA-12514 errotr while switchover using DGBROKER

Hi ,
Please see the error log.
DGMGRL> switchover to dgtest1dr1;
Performing switchover NOW, please wait...
Operation requires shutdown of instance "dgtest1" on database "dgtest1"
Shutting down instance "dgtest1"...
ORA-01109: database not open
Database dismounted.
ORACLE instance shut down.
Operation requires shutdown of instance "dgtest1dr1" on database "dgtest1dr1"
Shutting down instance "dgtest1dr1"...
ORA-01109: database not open
Database dismounted.
ORACLE instance shut down.
Operation requires startup of instance "dgtest1" on database "dgtest1"
Starting instance "dgtest1"...
Unable to connect to database
ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
Failed.
You are no longer connected to ORACLE
Please connect again.
Unable to start instance "dgtest1"
You must start instance "dgtest1" manually
Operation requires startup of instance "dgtest1dr1" on database "dgtest1dr1"
You must start instance "dgtest1dr1" manually
Switchover succeeded, new primary is "dgtest1dr1"
What could be the cause?

Hi Naveed,
Still iam getting the same error.
I am pasting the Tns-entry for both the primary & standby:
dgtest1 =
(DESCRIPTION =
(SDU=32767)
(MDU=32767)
(TDU=32767)
(RECV_BUF_SIZE=9375000)
(SEND_BUF_SIZE=9375000)
(ADDRESS = (PROTOCOL = TCP)(HOST = sdal201)(PORT = 1522))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = dgtest1_DGB)
dgtest1dr1 =
(DESCRIPTION =
(SDU=32767)
(MDU=32767)
(TDU=32767)
(RECV_BUF_SIZE=9375000)
(SEND_BUF_SIZE=9375000)
(ADDRESS = (PROTOCOL = TCP)(HOST = smro181)(PORT = 1522))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = dgtest1dr1_DGMGRL)
Listener.ora in standby.
SID_LIST_LISTENER_dgtest1dr1 =
(SID_LIST =
(SID_DESC =
(GLOBAL_DBNAME = dgtest1dr1_DGMGRL)
(ORACLE_HOME = /apps/oracle/product/10.2.0.4)
(SID_NAME = dgtest1dr1)
(SID_DESC =
(GLOBAL_DBNAME = dgtest1dr1_DGB)
(ORACLE_HOME = /apps/oracle/product/10.2.0.4)
(SID_NAME = dgtest1dr1)
LISTENER_dgtest1dr1 =
(DESCRIPTION_LIST =
(DESCRIPTION =
(SDU=32767)
(MDU=32767)
(TDU=32767)
(RECV_BUF_SIZE=9375000)
(SEND_BUF_SIZE=9375000)
(ADDRESS = (PROTOCOL = TCP)(HOST = smro181)(PORT = 1522))
Listener.ora in primary.
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(GLOBAL_DBNAME = dgtest1_DGMGRL)
(ORACLE_HOME = /fosappdalprod1/fos5/product/10.2.0.4)
(SID_NAME = dgtest1)
(SID_DESC =
(GLOBAL_DBNAME = dgtest1_DGB)
(ORACLE_HOME = /fosappdalprod1/fos5/product/10.2.0.4)
(SID_NAME = dgtest1)
LISTENER_dgtest1 =
(DESCRIPTION_LIST =
(DESCRIPTION =
(SDU=32767)
(MDU=32767)
(TDU=32767)
(RECV_BUF_SIZE=9375000)
(SEND_BUF_SIZE=9375000)
(ADDRESS = (PROTOCOL = TCP)(HOST = sdal201)(PORT = 1522))
Kindly help me on this.

Job schedule in switchover

Hi
in switchover dose we need to disable default jobs that is defined and run by Database automatically like JOB= ORACLE_OCM.MGMT_CONFIG_JOB?

To ensure that no more jobs are running please change set job_queue_processes parameter in Primary.
SQL> alter system set job_queue_processes = 0;
This will ensure that no more schedule jobs (including the ones with ORACLE_OCM as owner) will run in the future and you can safety make the manual switchover.
SQL> select owner, job_name from dba_scheduler_jobs;

Supervisor 6L-E frequently switchover

Hi all, I have a frequently problem on Catalyst 4507E with SSO, modules 1 e 2 always fail after not manually switchover, I need to use "hw-module module reset" to change the state of modules.
Do you have any idea of the cause of this problem? I notice "comm link down=1", what is mean?
VMCH-A-Cat4507#sh redundancy counters
Redundancy Facility OMs
               comm link up = 2
             comm link down = 1
          invalid client tx = 0
          null tx by client = 0
                tx failures = 0
      tx msg length invalid = 0
      client not rxing msgs = 0
rx peer msg routing errors = 0
           null peer msg rx = 0
        errored peer msg rx = 0
                 buffers tx = 69850
     tx buffers unavailable = 0
                 buffers rx = 73927
      buffer release errors = 0
duplicate client registers = 0
failed to register client = 0
       Invalid client syncs = 0
VMCH-A-Cat4507#sh redundancy switchover history
Index Previous Current Switchover             Switchover
       active    active   reason                 time
   1       3        4     active unit failed     14:47:59 Italy Wed Aug 8 2012
Could you help me?
Regards
Marco

Yes, it is compatible with non-e chassis.
see below:
The Cisco Catalyst 4500 Supervisor Engine 6L-E is also compatible with classic Cisco Catalyst 4500 line cards, chassis (3-, 6-, and 7-slot), and power supplies, providing full investment protection.
link to data sheet:
http://www.cisco.com/c/en/us/products/collateral/switches/catalyst-4500-series-switches/data_sheet_c78-530856.html
HTH

WLC 5508 HA-SSO 90-day timer

Hello everybody
We have 2 5508 in HA SSO (212licenses + 50permanentfor the secondary)
it is not clear what is written in the documentations about the 90-day timer
– If the new WLC has a higher AP count than the previous, the 90-day counter is reset.
– If the new WLC has a lower AP count than the previous, the 90-day counter is not reset.
What about same ap count???
let's assume the primary goes down and the secondary becomes active...
the 90-day timer will start (as reported in the docs) and 212 licenses are inherited from primary unit
now for example after 90 days the secondary controller starts nagging messages and the netadmin notices it, he forces a failover to revert back to the primary controller as the primary has no issues (it was just a failover caused by temporary gateway unreachability)
so the primary becomes the new active with its original licenses
The question is :
what happens to the 90-day timer, does it get reset?
if a new failover occurrs will the ap join the backup controller?
is there any way to show the remaining days for inherited license?
Thank you

Thank you Scott
hope I did understand correctly...
after 90d you were not able to access the secondary unit anymore... i assume cli was locked too.. so no manual switchover via cli command... (just unplug?)
you did test a new switchover right?... was the wireless infrastructure still working with config synced with the primary unit?
then you did a factory reset... rebuilt the secondary unit and had again the 90-day timer not zeroed? (looks like the primary controller is totally unaware of how much time the standby controller was online as primary)
sorry for the many questions , cisco's documentation about this is really frustrating and I really can't understand why... if I did understand correctly I think this is a really bad behaviour (imho) at least the counter shoud be meant to stop when primary controller comes back online in standby hot state... reboots often happen cause of software failure and someone may never notice a switchover occurred until the timer is over... and we have no way to know how much time is left for the standby controller...

ORA-16020: fewer destinations available than specified by LOG_ARCHIVE_MIN_S

Hi all,
I'm testing setup of primary and standby database and everything seems to work normally.
Now, I want to set up DG Broker so I can test switching it over and back.
So, I went through steps by Gavin (ref. http://gavinsoorma.com/2010/03/11g-data-guard-broker-dgmgrl-configuration-quick-steps/).
All went well until I showed configuration after enabling the broker.
Then I got error: ORA-16020: fewer destinations available than specified by LOG_ARCHIVE_MIN_SUCCEED_DEST
So, then I check the DG log files and on the standby database, I see errors:
2013-03-26 11:03:52.457                      Executing SQL [ALTER SYSTEM SET log_archive_min_succeed_dest=1 SCOPE=BOTH sid='*']
2013-03-26 11:03:52.457                      SQL Execution error=604, sql=[ALTER SYSTEM SET log_archive_min_succeed_dest=1 SCOPE=BOTH sid='*']. See error stack below.
2013-03-26 11:03:52.457                        ORA-00604: error occurred at recursive SQL level 1
2013-03-26 11:03:52.457                        ORA-02097: parameter cannot be modified because specified value is invalid
2013-03-26 11:03:52.457                        ORA-16020: fewer destinations available than specified by LOG_ARCHIVE_MIN_SUCCEED_DEST
2013-03-26 11:03:52.458                      RSM0: Failed to set property LogArchiveMinSucceedDest
2013-03-26 11:03:52.458                      RSM0: return status of set property 'LogArchiveMinSucceedDest' is ORA-16788
2013-03-26 11:03:52.458 02010000 1827537550 Operation EDIT_RES_PROP canceled during phase 1, error = ORA-16788
2013-03-26 11:03:52.458 02010000 1827537550 DMON: Entered rfm_release_chief_lock() for EDIT_RES_PROP
2013-03-26 11:03:52.460 02010000 1827537550 DMON: EDIT_RES_PROP operation completedSo now, i check the DG InconsistentProperties
First, standby:   tststby2
================
DGMGRL> show database 'tststby2' InconsistentProperties;
INCONSISTENT PROPERTIES
   INSTANCE_NAME        PROPERTY_NAME         MEMORY_VALUE         SPFILE_VALUE         BROKER_VALUE
        tststby2 LogArchiveMinSucceedDest                    1                                         1
Then, primary: tstprim2
================
DGMGRL> show database 'tstprim2' InconsistentProperties;
INCONSISTENT PROPERTIES
   INSTANCE_NAME        PROPERTY_NAME         MEMORY_VALUE         SPFILE_VALUE         BROKER_VALUESo, looking now in the database, I check standby and it shows:
log_archive_min_succeed_dest integer 1
And, checking primary, it shows:
log_archive_min_succeed_dest integer 1
Okay, so what's next?
I tried resetting the LogArchiveMinSucceedDest to see if that would help, but it just gave me error.
DGMGRL> edit database 'tststby2' set property 'LogArchiveMinSucceedDest'=1;
Error: ORA-16788: unable to set one or more database configuration property valuesI do see that my LOG_ARCHIVE_DEST_STATE_2 is set to ENABLE in primary, and is set to DEFER in standby, but it doesn't seem to let me change it in standby.
What else can I check?
Adding a couple of more things that might shed light on this:
======================================
on tstprim2 (primary)
==============
SQL> sho parameter convert
NAME                                 TYPE        VALUE
db_file_name_convert                 string      tststby2, tstprim2
log_file_name_convert                string      tststby2, tstprim2
on tststby2 (standby)
==============
NAME                                 TYPE        VALUE
db_file_name_convert                 string      tstprim2, tststby2
log_file_name_convert                string      tstprim2, tststby2
SQL> SELECT PROCESS, STATUS FROM V$MANAGED_STANDBY;
PROCESS   STATUS
ARCH      CLOSING
ARCH      CLOSING
RFS       IDLE
RFS       IDLE
RFS       IDLE
RFS       IDLE
MRP0      APPLYING_LOG <== as you can see, the standby database is working properly
35 rows selected.Edited by: 974632 on Mar 26, 2013 9:06 AM

Okay, I will check that.
Meanwhile, I'm trying a standard manual switchover, which worked fine.
But, when I try to switch logfiles, it is just hanging.
When i check alert log, it shows errors:
Tue Mar 26 12:24:31 2013
ARCH: Archival stopped, error occurred. Will continue retrying
ORACLE Instance tststby2 - Archival Error
ORA-16014: log 1 sequence# 380 not archived, no available destinations
ORA-00312: online log 1 thread 1: '/redo1/tststby2/redo01a.rdo'
ORA-00312: online log 1 thread 1: '/redo2/tststby2/redo01b.rdo'
Tue Mar 26 12:24:33 2013
krsk_srl_archive_int: Enabling archival of deferred physical standby SRLs
krsk_srl_archive_int: Enabling archival of deferred physical standby SRLsI have a feeling it might be because I don't have my dest_2 set correctly.
The reason I suspect that is because, when I try to enable dest_2, I see error:
SQL> alter system archive log all;
alter system archive log all
ERROR at line 1:
ORA-16020: fewer destinations available than specified by LOG_ARCHIVE_MIN_SUCCEED_DEST
SQL> alter system set log_archive_dest_state_2=enable;
alter system set log_archive_dest_state_2=enable
ERROR at line 1:
ORA-02097: parameter cannot be modified because specified value is invalid
ORA-16028: new LOG_ARCHIVE_DEST_STATE_2 causes less destinations than LOG_ARCHIVE_MIN_SUCCEED_DEST requiresMy dest_2 is set at (remember this is now primary on my standby server):
log_archive_dest_2                   string      SERVICE=tststby2 LGWR ASYNC
                                                 VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE)
                                                 DB_UNIQUE_NAME=tststby2My dest_1 is set at:
log_archive_dest_1                   string      LOCATION=USE_DB_RECOVERY_FILE_DEST
                                                 VALID_FOR=(ALL_LOGFILES,ALL_ROLES)
                                                 DB_UNIQUE_NAME=tstprim2Okay, so now, out of desperation, here's what I did, which seems to have worked.
(I had previously also enabled dest_state_3 per the instructions in the original web page notes)
SQL> alter system set log_archive_dest_3='LOCATION=/arch/tststby2';
System altered.
SQL> alter system archive log all;
System altered.Now, when I check my location, i see new files just put into that location.
$ <tststby2> /arch/tststby2>ll
total 13484
drwxr-xr-x 2 oracle dba    4096 Mar 26 12:47 ./
drwxr-xr-x 6 oracle 300    4096 Mar 22 10:56 ../
-rw-r----- 1 oracle dba 7453184 Mar 26 12:47 log_1_376_809878919.arc
-rw-r----- 1 oracle dba 6177792 Mar 26 12:47 log_1_377_809878919.arc
-rw-r----- 1 oracle dba   14336 Mar 26 12:47 log_1_378_809878919.arc
-rw-r----- 1 oracle dba   96768 Mar 26 12:47 log_1_380_809878919.arc
-rw-r----- 1 oracle dba   47616 Mar 26 12:47 log_1_381_809878919.arcOne other point of reference is that I created my primary and standby based on your webpage:
http://www.visi.com/~mseberg/data_guard_on_oracle_11_step_by_step.html
The only main differences are path locations and names of primary and standby database.
(Thank you mseberg. You are very good explaining things very well.)

Data Guard on Win2003 R2 & Oracle 9.2.0.8

Hi Team. We have 28 databases oracle 9208 in a windows 2003 R2 Server and we need to create a contingency in a server that is exactly the same as the primary (hardware, OS, patch level and directory structure).
Questions:
1- It is possible to create data broker configurations for all db?
2- How can I configure Windows database services in standby server so when it reboot doesn't startup standby databases?
3- Does anybody have an step-by-step guide for configuring dataguard 9208 on windows servers?
Thanks in advance!

A Broker configuration is tied to a set of databases. The configuration files are stored on each database's system and the broker processes all run on each database in a configuration. So there is no concept of 28 configurations on one system. if you have 28 Primary databases on one system with 28 standby on another system then you will have 28 broker configurations defined with the configuration files and processes for each database stored/running on each database.
If you have 28 systems each with its own Primary and 28 corresponding standby systems with a corresponding standby for each Primary then you will have 28 broker configurations defined with the configuration files and processes for each database stored/running on each database.
So I am not sure what you are asking.
But yes, you can always do manual switchover/failover. See the manual - http://download.oracle.com/docs/cd/B10501_01/server.920/a96653/role_management.htm#1033701
Larry

Whats is diffrence between Dataguard and Stand by?

Hi All
I was asked for diffrence between Dataguard and StandBy Database in an interview.
I answered that prior to 9I, (in 8i) It was called StandBy Database and from 9I onwards, It is called DataGuard.
But interviewer doesnt seems to be satisfied with my answer. Not sure why?
Then i was asked for Diffrence in Logical Dataguard and Physical Dataguard?
I replied with "Logical DG" is one in which sql stements are applied onto standby whereas "Physical DG" is one in which redo logs are shipped from one server to other by itself (with services) and secondary upgrades itself from those. Again, interviewer didnt feel happy enough.
This has made me think, was my answer incorrect because i answered whatever i know. which i feel like is correct.
Please help me identify correct answer.
Thanks
aps

aps wrote:
Hi All
I was asked for diffrence between Dataguard and StandBy Database in an interview.
I answered that prior to 9I, (in 8i) It was called StandBy Database and from 9I onwards, It is called DataGuard.No - DataGuard is intimately involved with Standby Database, but it is NOT standby. A Data Guard 'configuration' actually includes the primary database and one or more standby databases as well as some additional processes and the connectivity between these things.
In simplistic terms:
Standby Database is an operating mode of the database in which it continuously applies redo logs that are shipped from another (primary) database. The mode of operation often stops the database from being accessible to users.
Logical standby database uses a 'recieving process' (SQL Apply) that extracts from the log and creates SQL statements which are applied to keep the standyby database in step with the primary.
Physical standby database uses a form of continuous database recovery by directly applying the redo logs received from the primary.
Data Guard was originally a set of scripts, but now is the entire environment including a set of processes that control the extraction of redo (directly from log bugger, from redo logs or archive redo logs) from the primary, shipping to the standby, ensuring that the logs are applied. Data Guard processes also include the mechanics needed to make the standby database active automatically (failover) or manually (switchover) and also to re-sync and make the original database active again (switchback).
You could (should) read more about this. Oracle has a fine set of documentation which you can access from http://tahiti.oracle.com - indeed selecting Database 10gR2, and switching to the Books tab you get to http://www.oracle.com/pls/db102/portal.portal_db?selected=3 . And by scrolling down a little to "Data Guard Concepts and Administration" you would get decent introduction in the first 2 pages of Chapter 1 "Introduction to Oracle Data Guard".
But interviewer doesnt seems to be satisfied with my answer. Not sure why?I would not be satisfied either. Especially if I was looking for swomeone to be responsible for availability scenarios for my corporate data.
Then i was asked for Diffrence in Logical Dataguard and Physical Dataguard?
I replied with "Logical DG" is one in which sql stements are applied onto standby whereas "Physical DG" is one in which redo logs are shipped from one server to other by itself (with services) and secondary upgrades itself from those. Again, interviewer didnt feel happy enough.Well ... you are moderately close on this. However, you seem to be missing "how do we get data from the primary in the SQL Apply case". The implication is that you are not at all comfortable with the basic concepts.
Again, I would not be terribly happy either. I would not be confident that you had read Chapter 1 of the Data Guard Concepts manual. And that could imply that you had not read Chapter 1 of ANY of the Concepts manuals. That chapter in each of the manuals is an easy read, complete with pictures, and it describes the basics of operating the big machine that the interviewer wants to entrust you with.
All that said, Data Guard is only available on Enterprise Edition. Standby capability is available on Standard Edition. And there are commercial products around that provide capability similar to Data Guard for Standard Edition.

Database rolling upgrade cpu patch with minimal service outage

Oracle 11gR2 Primary Instance
Oracle 11gR2 Active Physical Standby
Requirement of applying CPU and CVE patches with minimal downtime. I believe that I've been able to apply CPU patch to Active Standby after deferring redo transport and applying patch to active physical standby first and then performing a manual switchover to have the standby become the primary and former-primary become the standby and they apply CPU Patch there and then perform another role transition to its original role.
Appreciate your experience with primary and active physical standby rolling upgrades/patches. Thanks

Hello;
I believe you are over thinking this. All you have to do on the Standby is install the patch. No switchover, no SQL. No nothing.
The SQL will move from the Primary to the Standby.
Check the readme for the patch closely or post the patch number if you want to confirm.
OR
How do you apply a Patchset,PSU or CPU in a Data Guard Physical Standby configuration [ID 278641.1]
( If it helps I had the same thoughts after my first Data Guard setup !! )
If you are trying to avoid downtime entirely the switchover will take about as long as the patch.
If you have RAC this is interesting :
http://javeedkaleem.blogspot.com/2010/05/how-to-apply-oracle-database-patch.html
As is this :
http://docs.oracle.com/cd/B28359_01/server.111/b28282/schedule_outage.htm
Best Regards
mseberg

Exchange Server Dynamic quorum for two AD site

Hello All,
I have some query regarding the Dynamic Quorum issue:
The environment is two Exchange 2013 in first AD site and another Exchange server 2013 on second AD site. So, total 3 node exchange server.
1. Can i configure DAG with dynamic quorum on this scenario?
2. If first site is totally down then second site can work without any interruption.
3. Is there any need manual switchover in this scenario?
4. OWA and outlook can work if first site down?
5. If first site down then second site exchange server db can automatically mounted.
Thanks,
Parvez

Hi,
1. Can i configure DAG with dynamic quorum on this scenario?
By default dynamic quorum will be enabled once the node is added to the DAG
2. If first site is totally down then second site can work without any interruption.
1.sequential failure on dag nodes - first node in dag will go down and after a short time second node will go down .
2.simultaneous failure on dag nodes - majority of the nodes will go down at a time .On your case majority is two.
Dynamic quorum will support sequential failure of nodes and it will not support the simultaneous failure .
So on your case if you perform manual sequential failure on the dag nodes you can make utilize the dynamic quorum feature .
Note : Please refer the below mentioned blog which will give you a good clarity.Like you they have also demonstrated with three nodes.
Reference
blog : http://www.msexchange.org/articles-tutorials/exchange-server-2013/high-availability-recovery/exchange-2013-dag-dynamic-quorum-part2.html
3. Is there any need manual switchover in this scenario?
Yes it is available .You can follow the below mentioned article .Though it is for exchange 2010 but it will support 2013 .
http://smtpport25.wordpress.com/2010/12/10/exchange-2010-dag-local-and-site-drfailover-and-fail-back/
4. OWA and outlook can work if first site down?
You need to point the outlook and owa namespaces to the exchange 2013
server in DR site or else it would be to an LB in DR site.
5. If first site down then second site exchange server db can automatically mounted.
At a time , If the entire site goes down then the automatic failover will not happen ,because
the dynamic quorum doesn't have the enough time to recalculate the dynamic weight.
Please feel free to reply me if you have any queries.
Thanks & Regards S.Nithyanandham

Manual switchover

Similar Messages

Maybe you are looking for