Dataguard switchover issue

Hi all,
I am facing physical standby switchover issue. I set up a physical standby database everything works well. Last week I tried switching between primary abd standby, switchover also done well.
Switchover happend log sequence at 1011.
After a couple of days I tried switch over it back, then alter database switchover camand is taking too long.
I queried on standby for any archive log gap,
SQL>select * from v$archive_gap;
THREAD# LOW_SEQUENCE# HIGH_SEQUENCE#
1 1012 1012
When I look into primary database archivelog destination I did not find any archive log with sequence number 1012
I also notice that in Primary after 1011 sequence number next comes 1013
please see the details of primary archives,
SQL> select sequence#,applied from v$archived_log;
SEQUENCE# APPLIED
1007 YES
1008 YES
1009 YES
1010 YES
1011 YES
1013 NO
1 NO
1014 NO
1015 NO
1016 NO
1017 NO
1018 NO
1019 NO
1020 NO
1021 NO
1022 NO
1014 NO
1013 NO
1022 NO
1016 NO
1015 NO
1019 NO
1018 NO
1021 NO
1017 NO
1020 NO
1023 NO
1023 NO
1024 NO
1024 NO
1025 NO
1025 NO
1026 NO
1026 NO
1027 NO
1027 NO
1028 NO
1029 NO
1030 NO
1030 NO
1031 NO
1031 NO
1032 NO
1032 NO
1033 NO
1033 NO
1034 NO
1034 NO
1035 NO
1035 NO
1036 NO
1036 NO
1037 NO
1037 NO
1038 NO
1038 NO
I checked in standby I found that after sequence 1011 there is no archives applied on standby
SEQUENCE# APPLIED
999 YES
1000 YES
1001 YES
1002 YES
997 YES
999 YES
1002 YES
1001 YES
1000 YES
998 YES
1003 YES
1003 YES
1004 YES
1004 YES
1005 YES
1005 YES
1006 YES
1006 YES
1007 YES
1007 YES
1008 YES
1008 YES
1009 YES
1009 YES
1010 YES
1010 YES
1011 YES
1 YES
1 YES
I tried with recover manages standby commnads but nothing worked out. I wonder how a sequence number 1 has come on primary database, I manually copied the sequence 1 to stand by and regitered it, after that also it show archivelog gap?
Could you please help me in this?
-Thanks & cheers
Antony

Dear Antonypaulm,
What is being written in the alert.log files and can you please also show the last few lines of v$dataguard_status dynamic performance view?
By the way are you using data guard broker?
Regards.
Ogan

Similar Messages

Grid control switchover issue

Hi,
I have carried out the following
a 10g database install on 2 servers
enabled dataguard between them so I have a primary and a standby database.
I then installed Grid Control onto each server using the opetion to install into an existing database. this worked.
On the standby server opmnctl is shutdown and the database is a PHYSICAL STANDBY.
when I do a dataguard switchover I see the standby database is now the primary. I restart opmnctl and go to the web browser to look at Grid Control.
The issue I have is that Grid Control, even though it is on the standby server, points to the primary server. How can I change this behaviour
When I first started Grid Control I had to perform the following actions
[oracle@griddg bin]$ ./emctl status emkey
Oracle Enterprise Manager 10g Release 3 Grid Control
Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
Please enter repository password:
The Em Key exists in the Management Repository, but is not configured properly or is corrupted in the file system.
Configure the Em Key by running "emctl config emkey -repos".
[oracle@griddg bin]$ ./emctl config emkey -repos
Oracle Enterprise Manager 10g Release 3 Grid Control
Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
Please enter repository password:
The Em Key has been configured successfully.
after this gridcontrol was able to start but points to the wrong host.
rgds
alan

hi,
the steps I took are as follows
1 - precreate a database on the primary and standby.
2 - configure the tnsnames and listener files so that the databases can talk to each other
3 - create a standby control file from the primary database.
4 - copy all database files from the primary to the standby
5 - copy the standby controlfile to the standby
6 - start the primary database
7 - start the standby database but only mounted, check database_role from v$database; it should be physical standby
8 - install Grid Control on the primary server with the option to install onto an existing database. Complete this installation.
9 - Install Grid Control onto the standby server with the option to install onto an existing database. Complete the installation and then carry out an 'opmnctl stopall'
10 - all being well Grid Control should now show both hosts and databases.
11 - create a dataguard configuration from within GC
The standby database cannot be discovered correctly in GC and this must be because it is in a mount state, not sure what to do about this. This then meant that I had to carry out a switchover from the command line. I am just testing this now and will post back when complete.
regards
Alan

DATAGUARD SWITCHOVER 절차

제품 : ORACLE SERVER
작성날짜 : 2002-12-11
DATAGUARD SWITCHOVER 절차
=======================
I.     Failover와 Switchover의 차이점
1.     Failover
-     Unplanned
-     Primary는 new standby가 될 수 없고 discard되어야 한다.
-     Standby는 "alter database activate standby database" 명령을 사용하여
Primary로서 Open 된다. 이 명령이 수행되는 동안 resetlogs operation이 수행되기
때문에 primary 는 discard될 수 밖에 없다.
-     New standby 를 생성하는데 상당한 시간이 걸리므로 그 만큼 risk에 상당시간
노출되게 된다.
-     Oracle 9i에서도 incomplete recovery를 위해 여전히 사용 가능하다.
2.     Switchover
-     Planned
-     Primary는 discard되지 않고 new standby가 된다.
-     Switchover는 다음과 같은 조건이 만족될 때 가능하다
a)     Primary가 graceful shutdown 수행(normal, transactional, immediate)
b)     Standby를 primary의 시점과 같게 만들어줄 모든Archive log가 필요하다.
c)     Primary의 online redo log가 available해야 한다.
NOTE:
RAC 환경에서는 switchover operation을 위해서 오직 한 instance만이 허용된다.
Switchover operation동안 다른 instance는 반드시 shutdown되어 있어야 한다.
II. DATABASE SWITCHOVER STEPS
Step 1) Switchover를 수행하는 session을 제외한 Primary database와
standby database의 모든 session을 종료한다.
Step 2) Primary database가 standby database로 switchover될 수 있는지를 check한다.
     SQL> select switchover_status from v$database;
Switchover_status가 'TO STANDBY' 이면 switchover operation이 가능하다.
그러나 'SESSION ACTIVE'라면 모든 session이 아직 종료되지 않았다는
의미이므로 다시금 session 상태를 check하여 기타 아직 종료되지 않은
session을 종료 시켜야 한다.
Step 3) 다음과 같은 명령을 수행한다
SQL> ALTER DATABASE COMMIT TO SWITCHOVER TO PHYSICAL STANDBY;
이 명령어는 다음과 같은 과정을 수행한다.
-     Primary database를 close한다
-     Unarchived log file을 archive하고 그것을 standby database에 보낸다
-     Archiving되고 있는 마지막 log file에 END-OF-REDO marker를 더함.
-     Current controlfile의 backup을 생성하고 current controlfile을 standby
control file로 converion함.
Step 4) Shutdown normal;
Step 5) initSID.ora 안에서 primary role parameter들을 disable하고 standby
parameter를 enable한다.
Step 6) startup nomount;
Step 7) alter database mount standby database;
Step 8) Standby database가 Primary database로 switchover될 수 있는지를 check한다.
     SQL> select switchover_status from v$database;
Switchover_status가 'TO PRIMARY' 이면 switchover operation이 가능하다.
그러나 'SESSION ACTIVE'라면 모든 session이 아직 종료되지 않았다는 의미이므로
다시금 session 상태를 check하여 기타 아직 종료되지 않은 session을 종료 시켜야 한다.
Step 9) 다음과 같은 명령을 수행한다.
ALTER DATABASE COMMIT TO SWITCHOVER TO PHYSICAL PRIMARY;
이 명령어는 다음과 같은 과정을 수행한다.
-     End-of-redo marker를 포함하고 있는 마지막 redo log를 받아서 적용한 것을
보장한다
-     Standby database의 read-only transaction으로 open되어 있으면 close한다.
-     Standby control file을 current control file로 conversion한다.
Step 10) Database를 shutdown 한다.
Step 11) initSID.ora 에서 Primary role로 변경한다.
Step 12) Database를 startup한다.
Step 13) Standby database를 managed recovery mode로 바꾼다
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE;
Step 14) Primary database로부터 Standby database로 log archiving을 시도하여
정상인지 check한다.
Reference Documents
-------------------

Hi,
since OCI library is required for TAF (transparent application failover)
you can switchover using JDBC OCI driver, but not the THIN driver.
Andrey

Dataguard Post Switchover issue

Hi All,
OS:AIX
DB:11.2.0.3
I have just performed the switcover from my primary to standby database. The switchover was smooth but the archives are not getting shipped and applied on the new DR. I have checked the process and found that the RFS process is not up. Upon further checking I have found that the alert of my new DR is giving me this line
Resetting standby activation ID 0 (0x0)
Please let me know what does this indicates
Regards

The message Resetting standby activation ID 0 (0x0)" is a normal message after switchover. It hard to think about a problem with so little details. Check this metalink note, this might help. There was also a similar kind of bug but in 10.2.0.4
11.2 Data Guard Physical Standby Switchover Best Practices using SQL*Plus (Doc ID 1304939.1)
There was also a similar kind of bug but in 10.2.0.4. Workaround is to reboot the database. You can try rebooting the database. It might fix the issue.
Bug 5476236 - RFS logminer client inoperative after physical standby switchover to primary (Doc ID 5476236.8)

Manually create EM on Dataguard switchover got issue.

Hello everyone,
My site configuration quite complicated a little bit. And my English is not so good. Please forgive me.
My site have 2 server and 1 shared storage
Linux RHEL 5.3 and Linux clusterware had been installed
I configured failover database by Linux cluster.
I installed Oracle11g Enterprise Edition.
I configured Oracle DataGuard between 2 nodes and every databases (PROD and STB) can switchover between 2 nodes.
note. PROD is a Primary database and located on Node1
note. STB is a Physical Standby database and located on Node2
now I switchover between Primary and Physical standby by DGMGRL.It's cause Primary shutdown and failover from node1 to node2. And work properly. And all database located on Node2
Questions
1. Do I have to recreate EM?
2. I tried to recreate EM but I got ora-600 [4406], there are something wrong?
Thanks for every answers
Bua

1. EM is nice but never required.
2. ORA-600 equals open an SR at metalink.
Not sure why you installed Linux clusterware. It is not required either.

DG broker Switchover issue, ORA-16535: CRS is prevent execution of a broker

I am having setup of 2 node 10.2.0.4.0 RAC setup on ASM with Single Instance Physical standby on File System (OS: REHL 5.4). I configured DG Broker without any major issues. Getting all output of 'show configuration' and all DG related logs are clear. Archives are getting transferred from both Primary nodes.
DGMGRL> show configuration
Configuration
Name: dg_rac
Enabled: YES
Protection Mode: MaxPerformance
Fast-Start Failover: DISABLED
Databases:
livestdby - Primary database
livedg - Physical standby database
Current status for "dg_rac":
SUCCESS
Now I am getting error Error: ORA-16535: CRS is preventing execution of a broker operation.
DGMGRL> switchover to livedg;
Performing switchover NOW, please wait...
Error: ORA-16535: CRS is preventing execution of a broker operation
Oracle Says
Cause
A broker operation was underway that required CRS to stop managing the instances of this database, but CRS management could not be stopped on behalf of the broker"s request on
at least some of the instances, so the broker operation was canceled.
Action
Suspend CRS management of this database using SRVCTL STOP DATABASE -D <name> -O NONE. Then reissue the broker request.
But this command is not working as it's given to stop the database.
One more thing, it's nowhere said to stop CRS while performing Switchover / Switchback using DG Broker. When we do Switchover / Switchback we keep open only one of the Primary database.
Anybody knows regarding this error???? or is there any solution for this ???? (is it bug ???)
is there any documentation / link available to switchover of RAC database using dgmgrl (DG Broker)
Any help would be appreciated.
regards,
manish

Hello;
I would check the tnsnames.ora on the Standby that's about to become the new Primary.
Based on the information you provided I'm thinking you cannot connect from the Standby site to the Primary and thus the switchover fails and throws this error.
If that checks out make sure the firewall rules for both server line up.
Best Regards
mseberg

RAC Dataguard Switchover timing taking more than expected time

I have Dataguard setup in RAC environment and my dataguard is also configured and it is working fine.
Our goal is to do the switchover using DGMGRL withing the 5 minutes. We have followed the proper setup and MAA tuning document and everything is working fine, Just the switchover timeing is 8 to 10 minutes. which varies depending on some parameters but not meeting our goal of less than 5 minutes.
The only observation that we have seen is as follow
After switchover to <db_name> comman in DGMGRL
1) it will shutdown abort the 2nd instance
2) transfter all the archivelog ( using LGWR in ASYNC mode) of instance 1
3) Now it looks for the archive log of 2nd instance, this steps take time upto 4 minutes
we do not know why it takes that much time and how to tune this??
4) Now converts primary to standby
5) Now starts the old standby as new primary
here All steps are tunined except the step 3, that where our lot of time is going any Idea or explanation
why it takes such a long time to find the exact archive log 2nd instance (Aborted) to transfer to standby site?
Can any one give explanation or solution to tune this???
Regards
Bhushan

Hi Robert,
I am on 10.2.0.4 and we have used "MAA_WP_10gR2_DataGuardNetworkBestPractices.pdf", which is available on oracle site.
Here are by configuration details
GMGRL> connect sys@dv01aix
Password:
Connected.
DGMGRL> show configuration;
Configuration
Name: dv00aix_dg
Enabled: YES
Protection Mode: MaxPerformance
Fast-Start Failover: DISABLED
Databases:
dv00aix - Physical standby database
dv01aix - Primary database
Current status for "dv00aix_dg":
SUCCESS
DGMGRL> show database verbose dv00aix
Database
Name: dv00aix
Role: PHYSICAL STANDBY
Enabled: YES
Intended State: ONLINE
Instance(s):
dv00aix1 (apply instance)
dv00aix2
Properties:
InitialConnectIdentifier = 'dv00aix'
ObserverConnectIdentifier = ''
LogXptMode = 'ASYNC'
Dependency = ''
DelayMins = '0'
Binding = 'OPTIONAL'
MaxFailure = '0'
MaxConnections = '4'
ReopenSecs = '300'
NetTimeout = '60'
LogShipping = 'ON'
PreferredApplyInstance = 'dv00aix1'
ApplyInstanceTimeout = '0'
ApplyParallel = 'AUTO'
StandbyFileManagement = 'AUTO'
ArchiveLagTarget = '900'
LogArchiveMaxProcesses = '5'
LogArchiveMinSucceedDest = '1'
DbFileNameConvert = ''
LogFileNameConvert = '+SPARE1/dv01aix/,+SPARE/dv00aix/'
FastStartFailoverTarget = ''
StatusReport = '(monitor)'
InconsistentProperties = '(monitor)'
InconsistentLogXptProps = '(monitor)'
SendQEntries = '(monitor)'
LogXptStatus = '(monitor)'
RecvQEntries = '(monitor)'
HostName(*)
SidName(*)
LocalListenerAddress(*)
StandbyArchiveLocation(*)
AlternateLocation(*)
LogArchiveTrace(*)
LogArchiveFormat(*)
LatestLog(*)
TopWaitEvents(*)
(*) - Please check specific instance for the property value
Current status for "dv00aix":
SUCCESS
DGMGRL> show database verbose dv01aix
Database
Name: dv01aix
Role: PRIMARY
Enabled: YES
Intended State: ONLINE
Instance(s):
dv01aix1
dv01aix2
Properties:
InitialConnectIdentifier = 'dv01aix'
ObserverConnectIdentifier = ''
LogXptMode = 'ASYNC'
Dependency = ''
DelayMins = '0'
Binding = 'OPTIONAL'
MaxFailure = '0'
MaxConnections = '4'
ReopenSecs = '300'
NetTimeout = '60'
LogShipping = 'ON'
PreferredApplyInstance = 'dv01aix1'
ApplyInstanceTimeout = '0'
ApplyParallel = 'AUTO'
StandbyFileManagement = 'AUTO'
ArchiveLagTarget = '0'
LogArchiveMaxProcesses = '2'
LogArchiveMinSucceedDest = '1'
DbFileNameConvert = '+SPARE/dv00aix/, +SPARE1/dv01aix/'
LogFileNameConvert = '+SPARE/dv00aix/,+SPARE1/dv01aix/'
FastStartFailoverTarget = ''
StatusReport = '(monitor)'
InconsistentProperties = '(monitor)'
InconsistentLogXptProps = '(monitor)'
SendQEntries = '(monitor)'
LogXptStatus = '(monitor)'
RecvQEntries = '(monitor)'
HostName(*)
SidName(*)
LocalListenerAddress(*)
StandbyArchiveLocation(*)
AlternateLocation(*)
LogArchiveTrace(*)
LogArchiveFormat(*)
LatestLog(*)
TopWaitEvents(*)
(*) - Please check specific instance for the property value
Current status for "dv01aix":
SUCCESS
DGMGRL>
log_archive_dest_2 string service="(DESCRIPTION=(ADDRESS
_LIST=(ADDRESS=(PROTOCOL=TCP)(
HOST=*****-vip0)(PORT=1527))
)(CONNECT_DATA=(SERVICE_NAME=d
v00aix_XPT)(INSTANCE_NAME=dv00
aix1)(SERVER=dedicated)))",
LGWR ASYNC NOAFFIRM delay=0 O
PTIONAL max_failure=0 max_conn
ections=4 reopen=300 db_uniq
ue_name="dv00aix" register net
NAME TYPE VALUE
timeout=60 validfor=(online
logfile,primaryrole)
NAME TYPE VALUE
fal_client string (DESCRIPTION=(ADDRESS_LIST=(AD
DRESS=(PROTOCOL=TCP)(HOST=*****
-vip0)(PORT=1527)))(CONNECT
DATA=(SERVICENAME=dv01aix_XP
T)(INSTANCE_NAME=dv01aix1)(SER
VER=dedicated)))
fal_server string (DESCRIPTION=(ADDRESS_LIST=(AD
DRESS=(PROTOCOL=TCP)(HOST=*****
-vip0)(PORT=1527))(ADDRESS=
(PROTOCOL=TCP)(HOST=*****-vi
p0)(PORT=1527)))(CONNECT_DATA=
(SERVICE_NAME=dv00aix_XPT)(SER
VER=dedicated)))
db_recovery_file_dest string +SPARE1
db_recovery_file_dest_size big integer 100G
recovery_parallelism integer 0
fast_start_parallel_rollback string LOW
parallel_adaptive_multi_user boolean TRUE
parallel_automatic_tuning boolean FALSE
parallel_execution_message_size integer 2152
parallel_instance_group string
parallel_max_servers integer 8
parallel_min_percent integer 0
parallel_min_servers integer 0
parallel_server boolean TRUE
parallel_server_instances integer 2
parallel_threads_per_cpu integer 2
recovery_parallelism integer 0

WLC 5508 Switchover Issue

Hi There,
Our issue is about a WLC 5508 conected to a HP Switch L3 model HP7500 using link-aggregation. Sometimes the controller change to the secondary box and log the error message: Switchover Reason = Default gateway is not reachable, Switchover Time
Manufacturer's Name.............................. Cisco Systems Inc.
Product Name..................................... Cisco Controller
Product Version.................................. 7.6.120.0
Bootloader Version............................... 1.0.1
Field Recovery Image Version..................... 6.0.182.0
Firmware Version................................. FPGA 1.7, Env 1.8, USB console 2.2
Build Type....................................... DATA + WPS
management LAG untagged x.y.z.a Static Yes No
redundancy-management LAG untagged x,y.z.b Static No No
redundancy-port - untagged 169.254.0.12 Static No No
(Cisco Controller) >show redundancy summary
Redundancy Mode = SSO ENABLED
Local State = ACTIVE
Peer State = STANDBY HOT
Unit = Primary
Unit ID = 6C:41:6A:5F:75:00
Redundancy State = SSO (Both AP and Client SSO)
Mobility MAC = 6C:41:6A:5F:75:00
Average Redundancy Peer Reachability Latency = 488 usecs
Average Management Gateway Reachability Latency = 748 usecs
Redundancy Management IP Address................. x.y.z.a
Peer Redundancy Management IP Address............ x.y.z.b
Redundancy Port IP Address....................... 169.254.0.12
Peer Redundancy Port IP Address.................. 169.254.0.13
Peer Service Port IP Address..................... 0.0.0.0
Switchover History[1]:
Previous Active = 10.140.0.13, Current Active = x.y.z.a
Switchover Reason = Default gateway is not reachable, Switchover Time = Tue Aug 19 05:32:44 2014
Any idea what´s the problem could be? We check alllan environment spanning-tree, vlan, routing, no physical issues.
My best regards
Adriano Porcaro

Show sysinfo results :
Manufacturer's Name.............................. Cisco Systems Inc.
Product Name..................................... Cisco Controller
Product Version.................................. 7.0.116.0
Bootloader Version............................... 1.0.1
Field Recovery Image Version..................... 6.0.182.0
Firmware Version................................. FPGA 1.3, Env 1.6, USB console 1.27
Build Type....................................... DATA + WPS

Active Dataguard switchover puts new standby in real time query

Hi Gurus,
If using Active Dataguard ,after swicthover/failover using dg broker and observer does sthe new standby will be put in real time query mode(ADG) or manually have to open the db in read only mode.
Please let me know.
Thanks

Yes it does:
[uhesse]$ dgmgrl sys/oracle@prima
DGMGRL for Linux: Version 11.2.0.1.0 - Production
Copyright (c) 2000, 2009, Oracle. All rights reserved.
Welcome to DGMGRL, type "help" for information.
Connected.
DGMGRL> show configuration
Configuration - myconf
Protection Mode: MaxAvailability
Databases:
    prima - Primary database
    logst - Logical standby database
    physt - Physical standby database
Fast-Start Failover: DISABLED
Configuration Status:
SUCCESS
DGMGRL> show database physt
Database - physt
Role:            PHYSICAL STANDBY
Intended State: APPLY-ON
Transport Lag:   0 seconds
Apply Lag:       0 seconds
Real Time Query: ON
Instance(s):
    physt
Database Status:
SUCCESS
DGMGRL> switchover to physt;
Performing switchover NOW, please wait...
New primary database "physt" is opening...
Operation requires shutdown of instance "prima" on database "prima"
Shutting down instance "prima"...
ORA-01109: database not open
Database dismounted.
ORACLE instance shut down.
Operation requires startup of instance "prima" on database "prima"
Starting instance "prima"...
ORACLE instance started.
Database mounted.
Database opened.
Switchover succeeded, new primary is "physt"
DGMGRL> show configuration
Configuration - myconf
Protection Mode: MaxAvailability
Databases:
    physt - Primary database
    prima - Physical standby database
    logst - Logical standby database
Fast-Start Failover: DISABLED
Configuration Status:
SUCCESS
DGMGRL> show database prima
Database - prima
Role:            PHYSICAL STANDBY
Intended State: APPLY-ON
Transport Lag:   0 seconds
Apply Lag:       0 seconds
Real Time Query: ON
Instance(s):
    prima
Database Status:
SUCCESSKind regards
Uwe Hesse
http://uhesse.wordpress.com

Dataguard broker issues

hi all,
am getting the following errors from the broker
Welcome to DGMGRL, type "help" for information.
DGMGRL> connect sys/Fes7Evu6@emrep
Connected.
DGMGRL> switchover to offsite_emrep;
Performing switchover NOW, please wait...
Operation requires shutdown of instance "emrep" on database "office_emrep"
Shutting down instance "emrep"...
ORA-01109: database not open
Database dismounted.
ORACLE instance shut down.
Operation requires shutdown of instance "emrep" on database "offsite_emrep"
Shutting down instance "emrep"...
ORA-01109: database not open
Database dismounted.
ORACLE instance shut down.
Operation requires startup of instance "emrep" on database "office_emrep"
Starting instance "emrep"...
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 "emrep"
You must start instance "emrep" manually
Operation requires startup of instance "emrep" on database "offsite_emrep"
You must start instance "emrep" manually
Switchover succeeded, new primary is "offsite_emrep"
DGMGRL>
If I disable the broker and carry out the switchover from the database evrything works as it should. Can anyone point me in the right direction to resolve this issue.
rgds
Alan

hi,
so if my listener file is
# listener.ora Network Configuration File: /u01/app/oracle/product/10.2.0/db10g/network/admin/listener.ora
# Generated by Oracle configuration tools.
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(SID_NAME = PLSExtProc)
(ORACLE_HOME = /u01/app/oracle/product/10.2.0/db10g)
(PROGRAM = extproc)
(SID_DESC =
(GLOBAL_DBNAME = emrep.domain.net)
(ORACLE_HOME = /u01/app/oracle/product/10.2.0/db10g)
(SID_NAME = emrep)
(SID_DESC =
(GLOBAL_DBNAME = emrepdg.domain.net)
(ORACLE_HOME = /u01/app/oracle/product/10.2.0/db10g)
(SID_NAME = emrep)
LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1))
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = griddg.domain.net)(PORT = 1521))
what needs to be added to it? I have reivewd the doc and think something like
(SID_DESC =
(GLOBAL_DBNAME =offsite_emrep_DGMGRL.emrepdg.domain.net)
(ORACLE_HOME = /u01/app/oracle/product/10.2.0/db10g)
(SID_NAME = emrep)
(SERVICE_NAME=emrepdg)
This I have tried but it still doesn't work.
regards
Alan

DGMGRL 11gr2 switchover issues

Hi all,
im new to 11gr2 datagaurd setup using DGMGRL and currently troubleshooting an issue with switchover which was setup by teammate and he is on annual leave.
Details: 11gr2 linux 64-bit RHEL5
both Prod and DR is configured with same DBNAME,INSTANCE,SERVICE and both share the same file system structure.
below are my configuration:
DGMGRL> connect sys@POZW1COL_PRD
Password:
Connected.
DGMGRL> show configuration
Configuration - COLDGCONFIG
Protection Mode: MaxPerformance
Databases:
PCOLPRIM - Primary database
PCOLSTBY - Physical standby database
Fast-Start Failover: DISABLED
Configuration Status:
SUCCESS
DGMGRL> show database 'PCOLPRIM'
Database - PCOLPRIM
Role: PRIMARY
Intended State: TRANSPORT-ON
Instance(s):
POZW1COL
Database Status:
SUCCESS
DGMGRL> show database 'PCOLSTBY'
Database - PCOLSTBY
Role: PHYSICAL STANDBY
Intended State: APPLY-ON
Transport Lag: 0 seconds
Apply Lag: 0 seconds
Real Time Query: OFF
Instance(s):
POZW1COL
Database Status:
SUCCESS
scenario: SWICTHOVER to standby
DGMGRL> SWITCHOVER TO 'PCOLSTBY'
Performing switchover NOW, please wait...
New primary database "PCOLSTBY" is opening...
Operation requires shutdown of instance "POZW1COL" on database "PCOLPRIM"
Shutting down instance "POZW1COL"...
ORACLE instance shut down.
Operation requires startup of instance "POZW1COL" on database "PCOLPRIM"
Starting instance "POZW1COL"...
ORACLE instance started.
Database mounted.
Switchover succeeded, new primary is "PCOLSTBY"
DGMGRL> show configuration
Configuration - COLDGCONFIG
Protection Mode: MaxPerformance
Databases:
PCOLSTBY - Primary database
PCOLPRIM - Physical standby database
Fast-Start Failover: DISABLED
Configuration Status:
SUCCESS
DGMGRL> show database 'PCOLPRIM'
Database - PCOLPRIM
Role: PHYSICAL STANDBY
Intended State: APPLY-ON
Transport Lag: 0 seconds
Apply Lag: 0 seconds
Real Time Query: OFF
Instance(s):
POZW1COL
Database Status:
SUCCESS
DGMGRL> show database 'PCOLSTBY'
Database - PCOLSTBY
Role: PRIMARY
Intended State: TRANSPORT-ON
Instance(s):
POZW1COL
Database Status:
SUCCESS
SWICTHOVER TO PRIMARY (OLD PRIMARY):
DGMGRL> SWITCHOVER TO 'PCOLPRIM'
Performing switchover NOW, please wait...
New primary database "PCOLPRIM" is opening...
Operation requires shutdown of instance "POZW1COL" on database "PCOLSTBY"
Shutting down instance "POZW1COL"...
ORACLE instance shut down.
Operation requires startup of instance "POZW1COL" on database "PCOLSTBY"
Starting instance "POZW1COL"...
Unable to connect to database
ORA-12545: Connect failed because target host or object does not exist
Failed.
Warning: You are no longer connected to ORACLE.
Please complete the following steps to finish switchover:
start up and mount instance "POZW1COL" of database "PCOLSTBY"
DGMGRL>
above you could see the issue can anyone highlight me where it was wrong.

Hi mahir,
Now i tried to switch over from primary to standby.
it was sucessfull,
DGMGRL> SWITCHOVER TO 'PCOLSTBY'
Performing switchover NOW, please wait...
New primary database "PCOLSTBY" is opening...
Operation requires shutdown of instance "POZW1COL" on database "PCOLPRIM"
Shutting down instance "POZW1COL"...
ORACLE instance shut down.
Operation requires startup of instance "POZW1COL" on database "PCOLPRIM"
Starting instance "POZW1COL"...
ORACLE instance started.
Database mounted.
Switchover succeeded, new primary is "PCOLSTBY"
Also contents from Primary datagaurd broker log.
Command SWITCHOVER TO PCOLSTBY completed
09/03/2012 09:05:44
Starting Data Guard Broker bootstrap <<Broker Configuration File Locations:
dg_broker_config_file1 = "/u01/app/oracle/product/db/11gR2/dbs/dr1PCOLPRIM.dat"
dg_broker_config_file2 = "/u01/app/oracle/product/db/11gR2/dbs/dr2PCOLPRIM.dat"
09/03/2012 09:05:47
DMON Registering service PCOLPRIM_DGB with listener(s)
Broker Configuration: "COLDGCONFIG"
Protection Mode: Maximum Performance
Fast-Start Failover (FSFO): Disabled, flags=0x0, version=0
Primary Database: PCOLSTBY (0x02010000)
Standby Database: PCOLPRIM, Enabled Physical Standby (0x01010000)
09/03/2012 09:05:51
Creating process RSM0
09/03/2012 09:05:54
*SQL Execution error=604, sql=[alter system set log_archive_dest_1='']. See error stack below.*
ORA-00604: error occurred at recursive SQL level 1
ORA-02097: parameter cannot be modified because specified value is invalid
ORA-16028: new LOG_ARCHIVE_DEST_1 causes less destinations than LOG_ARCHIVE_MIN_SUCCEED_DEST requires09/03/2012 09:06:03
Notifying Oracle Clusterware to buildup standby database after SWITCHOVER
Data Guard notifying Oracle Clusterware to start services and other instances change
Command SWITCHOVER TO PCOLPRIM completed

DataGuard Lagging Issue

Hi,
DataGuard is lagging behind primary database.
For that i had shipped the missing archived log files and register them in DG side.
But still on the DG side showing there is gap archived files of DG and Primary.
Thread Last Sequence Received Last Sequence Applied Difference
1 42899 42775 124
2 42637 42637 0
3 42779 42626 153
what might be the reason and what is possible solution.
Can you please help in finding out the cause?
Thanks
Vijay
Edited by: cherukuri on Jul 2, 2011 4:32 PM
Edited by: cherukuri on Jul 2, 2011 4:33 PM

cherukuri wrote:
HI,
This is the measage on Primary Db
\Error 16191 connecting to destination LOG_ARCHIVE_DEST_2 standby host 'ITSMPRD_dg'
Error 16191 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'ITSMPRD_dg'
ORA-16191: Primary log shipping client not logged on standby
*** 2011-06-19 05:44:52.264 64896 kcrr.c
PING[ARC4]: Heartbeat failed to connect to standby 'ITSMPRD_dg'. Error is 16191.
*** 2011-06-19 05:44:52.264 63005 kcrr.c
kcrrfail: dest:2 err:16191 force:0 blast:1
*** 2011-06-19 05:49:52.381
Redo shipping client performing standby login
ORA-01017: invalid username/password; logon denied
OCI_DBVER attribute value retrieval failed error=1017
*** 2011-06-19 05:49:52.599 64896 kcrr.c
Error 1017 received logging on to the standby
and this is on DG side
Media Recovery Waiting for thread 1 sequence 42600
Fetching gap sequence in thread 1, gap sequence 42600-42699
Fri Jul 01 14:01:57 EDT 2011
FAL[client]: Failed to request gap sequence
GAP - thread 1 sequence 42600-42699
DBID 3152143266 branch 697006498
FAL[client]: All defined FAL servers have been attempted.
and I just shipped missing archive logs and registered them after what i need to do.
Thanks
Vijay
16191, 0000, "Primary log shipping client not logged on standby"
// *Cause: An attempt to ship redo to standby without logging on
// to standby or with invalid user credentials.
// *Action: Check that primary and standby are using password files and that
//          both primary and standby have the same SYS password.
//          Restart primary and/or standby after ensuring that
//          password file is accessible and REMOTE_LOGIN_PASSWORDFILE
//          initialization parameter is set to SHARED or EXCLUSIVE. copy the external password file from the Primary to the Standby system

Dataguard switchover with different patches

Hi,
we are planning to do a db switchover from primary to DR.But we have no patches installed in Primary but in DR PSU 3 patch is installede along with some one off patches .The base version is 11.2.0.1 .Should I rollback the patches from DR before switch over or is it fine this way.
Log transfer and log apply is going fine as of now.

we are planning to do a db switchover from primary to DR.But we have no patches installed in Primary but in DR PSU 3 patch is installede along with some one off patches .The base version is 11.2.0.1 .Should I rollback the patches from DR before switch over or is it fine this way.
Log transfer and log apply is going fine as of now.Why you didnt applied on primary?
As a process you have to apply binaries of standby, then binaries of primary and run catbundle psu on primary. So that when you start log transport then automatically all the changes will be applicable/view modifications/Compile will be done through archivelogs from primary to standby.
check this note how to apply CPU/PSU in standby environments.
*How do you apply a Patchset,PSU or CPU in a Data Guard Physical Standby configuration [ID 278641.1]*

DataGuard Brooker Issue

DB:11.2.0.1
OS:Linux
RAC:11.2.0.2
I have a two node RAC database in Primary as well as in DR site. When i did a switchover .
DGMGRL> switchover to eioidp1_rtp
Performing switchover NOW, please wait...
New primary database "eioidp1_rtp" is opening...
Operation requires shutdown of instance "eioidp11" on database "eioidp1"
Shutting down instance "eioidp11"...
ORA-01109: database not open
Database dismounted.
ORACLE instance shut down.
Operation requires startup of instance "eioidp11" on database "eioidp1"
Starting instance "eioidp11"...
Unable to connect to database
ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
Failed.
Warning: You are no longer connected to ORACLE.
Please complete the following steps to finish switchover:
start up instance "eioidp11" of database "eioidp1"
After That i started the instance eioidp11 of database eioidp1 manually.When i am checking the configuration
DGMGRL> show configuration
Configuration - eioidp1_dg
Protection Mode: MaxPerformance
Databases:
eioidp1_rtp - Primary database
Warning: ORA-16809: multiple warnings detected for the database
eioidp1 - Physical standby database
Fast-Start Failover: DISABLED
Configuration Status:
WARNING
DGMGRL> show database verbose eioidp1_rtp
Database - eioidp1_rtp
Role: PRIMARY
Intended State: TRANSPORT-ON
Instance(s):
eioidp11
Warning: ORA-16715: redo transport-related property LogXptMode of standby database "eioidp1" is inconsistent
Warning: ORA-16715: redo transport-related property ReopenSecs of standby database "eioidp1" is inconsistent
Warning: ORA-16715: redo transport-related property NetTimeout of standby database "eioidp1" is inconsistent
eioidp12
Warning: ORA-16715: redo transport-related property LogXptMode of standby database "eioidp1" is inconsistent
Warning: ORA-16715: redo transport-related property ReopenSecs of standby database "eioidp1" is inconsistent
Warning: ORA-16715: redo transport-related property NetTimeout of standby database "eioidp1" is inconsistent
Properties:
DGConnectIdentifier = 'eioidp1_rtp_dgb'
ObserverConnectIdentifier = ''
LogXptMode = 'ASYNC'
DelayMins = '0'
Binding = 'OPTIONAL'
MaxFailure = '0'
MaxConnections = '1'
ReopenSecs = '300'
NetTimeout = '30'
RedoCompression = 'DISABLE'
LogShipping = 'ON'
PreferredApplyInstance = ''
ApplyInstanceTimeout = '0'
ApplyParallel = 'AUTO'
StandbyFileManagement = 'AUTO'
ArchiveLagTarget = '0'
LogArchiveMaxProcesses = '4'
LogArchiveMinSucceedDest = '1'
DbFileNameConvert = '+DB_ORCL_DAT0099, DB_ORCL_DAT0098, DB_ORCL_FRA0099, +DB_ORCL_FRA0098'
LogFileNameConvert = '+DB_ORCL_DAT0099, DB_ORCL_DAT0098, DB_ORCL_FRA0099, +DB_ORCL_FRA0098'
FastStartFailoverTarget = ''
StatusReport = '(monitor)'
InconsistentProperties = '(monitor)'
InconsistentLogXptProps = '(monitor)'
SendQEntries = '(monitor)'
LogXptStatus = '(monitor)'
RecvQEntries = '(monitor)'
HostName(*)
SidName(*)
StaticConnectIdentifier(*)
StandbyArchiveLocation(*)
AlternateLocation(*)
LogArchiveTrace(*)
LogArchiveFormat(*)
TopWaitEvents(*)
(*) - Please check specific instance for the property value
Database Status:
WARNING
Please suggest what i need to do .

Hi,
First problem with switchover looks like missing configuration in listeners - check if your DGMGRL services are registered.
ORA-16715 - it mean that you have different values between instances eioidp11 and eioidp12. Best way to check is to create pfile from current spfile and check it for instance specific parameters.
SQL> create pfile='/tmp/check' from spfile;
Then open /tmp/check file and look for parameters started with eioidp11.log_archive_dest_x and eioidp12.log_archive_dest_x and compare it.
regards,
Marcin Przepiorowski
http://oracleprof.blogspot.com/

Dataguard switchover & failover testing

i want to build new physical & logical dbs just for testing & learning, as per menalink notes 736863.1 & 748595.1
wondering that configuration will let me test switchover & failover testing?

Hi there,
Those notes help you to build a proper data guard configuration in both Physical and Logical Standby enviromnment.
I would also recommend to check:
- [The Oracle online documentation|http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/toc.htm]
- [Oracle Maximum Availability Architecture site on OTN|http://www.oracle.com/technology/deploy/availability/htdocs/maa.htm]
These documents can provide a big picture of Data Guard configurations from different approaches as well as I would also recommend to learn and practice more advanced techniques and features such as Flasback database, Fast-start-failover or Cascaded destinations.
Hope this helps,
Good luck and regards,
Jozsef

Dataguard switchover issue

Similar Messages

Maybe you are looking for