DGMGRL In Dataguard
Hi,
I have two question regarding dataguard.
1) If One archivelog is missing from Primary Database without Applying in Standby Database, then what will happen?
2) What is DGMGRL?
Thanks...
Asit
Edited by: asitkmohanty on 04-Oct-2012 05:49
1) If archivelog is missing from Primary Database without Applying in Standby Database, then what will happen?It is obvious that the standby database would go out of sync. If the archivelog is missing and you have the backup of it, then use this backup and restore and recover it on the standby, so that it would be in sync.
If you do not have the archive and you do not have the backup of the missed archive, they you'll have to use roll forward method to get your standby in sync. For this take a look at http://shivanandarao.wordpress.com/2012/03/26/roll-forward-physical-standby-database-using-rman-incremental-backup/
2) What is DGMGRL?DGMGRL is an utility that is used to monitor the standby databases. For this refer
http://docs.oracle.com/cd/B28359_01/server.111/b28295/dgmgrl.htm
http://docs.oracle.com/cd/B28359_01/server.111/b28295/concepts.htm
Similar Messages
-
UPDATE STANDBY SITE NAME with DATAGUARD BROKE "DGMGRL"
I've a llitlle PB with my Dataguard
After shutdown both sites to increase SGA size in Primary site and update in secondary site too
I start the Primary site without Pb.
But the Secondary site don't want to start.
When I do a startup it fails.i check in Dataguard and i found
The Pb is the secondary site name is not ('DMWEBDG_srvsdmwebp02')
bu only "DMWEBDG"
And I can't find any way to update the site name in Dataguarg.
the Alter command doesn't explain very well.
Soes anyone knows how to do it?
Thxs
DGMGRL> show site verbose 'DMWEBDG_srvsdmwebp02'
Site
Name: 'DMWEBDG_srvsdmwebp02'
Hostname: 'srvsdmwebp02'
Instance name: 'DMWEBDG'
Service Name: '(DESCRIPTION=(ADDRESS_LIST = (ADDRESS=(PROTOCOL=tcp)(HOST=srvsdmwebp02.int.imd.ch)(PORT=1525)))(CONNECT_DATA=(SID=DMWEBDG)(SERVER=DEDICATED)))'
Standby Type: 'physical'
Number Built-in Processes: '2'
Number Generic Processes: '0'
Enabled: 'yes'
Required: 'yes'
Default state: 'STANDBY'
Intended state: 'STANDBY'
PFILE: ''
Number of resources: 1
Resources:
Name: DMWEBDG_srvsdmwebp02 (default) (verbose name='DMWEBDG_srvsdmwebp02')
Current status for "DMWEBDG_srvsdmwebp02":
Warning: ORA-01034: ORACLE not availableThxs
The PB was Solved. -
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
BhushanHi 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 -
Hi ,
I have confusion about standby database in oracle 10g ,bcoz dataguard and physical standby database is same or not ?
if same what is Dataguard Broker in standby?
what is the difference between enable dg_broker_start = true and false / also what is the nature of job?
Regards,
S.MugunthanI have confusion about standby database in oracle 10g ,bcoz dataguard and physical standby database is same or not ?Data Guard is again priced product & Standby Database is a standard feature. You only may need another database license for the instance.
But you have to do all your own scripting to move archived redo logs to the standby to be applied, including any error checking.
Dataguard is the process to mirroring your Production/primary database. Dataguard manage your database primary and your database standby.
Even you can perform Switchovers & also failovers.
With Data Guard Oracle provides all that as part of the package, plus some management tools. The core still remains a Standby Database, either physical or logical.
if same what is Dataguard Broker in standby? You can say Datagaurd broker instead of standby broker, Broker will be enabled when it is configured in both primary & also standby database.
is again a utility where you can manage all Monitoring, Drilling (switching/faliver) via DGMGRL
In detail for this utility please do refer http://docs.oracle.com/cd/B28359_01/server.111/b28295/concepts.htm
what is the difference between enable dg_broker_start = true and false / also what is the nature of job?DG_BROKER_START enables Oracle to determine whether or not the Data Guard broker (DMON) process should be started. DMON is a non-fatal Oracle background process and exists as long as the instance exists, whenever this parameter is set to true.
In detail refer http://docs.oracle.com/cd/B19306_01/server.102/b14237/initparams060.htm
HTH. -
DataGuard Broker in 11gR2 - StaticConnectIdentifier
Ok, I have read that in 11gR2 you no longer have the requirement of putting in a static entry in your listener.ora file with <SID>_DGMGRL if you use the Dataguard Broker parameter: StaticConnectIdentifier. I have used this new parameter and it was set up automatically to be:
StaticConnectIdentifier = '(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=DB1)(PORT=1521))(CONNECT_DATA=(SERVICE_NAME=prod_sb_DGMGRL)(INSTANCE_NAME=prod_sb)(SERVER=DEDICATED)))'
My question is that there is no entry anywhere that specifies the SERVICE_NAME as prod_sb_DGMGRL. Will my switchover work without that SERVICE_NAME being defined no where? Am I missing a step? Thanks folks.Hello;
I'm thinking the switchover will fail with an ORA-12514. Without the listener.ora entry DGMGRL will not be able to connect to the databases after they have been stopped.
So you still need the _DGMGRL or at least a static entry in the listener.ora. In any event the static entry will not cause an issue.
*Switchover Failed With ORA-12521 using Dataguard Broker [ID 1380949.1]*
For additional information see - 8.3.40 StaticConnectIdentifier in "Data Guard Broker 11g Release 2 (11.2) E17023-04"
"A connect identifier that refers to a service that is statically registered"
Best Regards
mseberg
Edited by: mseberg on Sep 20, 2012 4:04 AM -
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.
ThanksYes 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 -
Post switch over in oracle dataguard 11g
Dear Guru,
Switch over has been completed successfully from primary database to standby database.
new primaray database is open and accessible but its showing his satus in v$database as below.
database_role = primary
switchover_status = not allowed
db_unique_name = dg1_stdby
old primaray database which is now standby showing his satus in v$database as below.
database_role = physical standby
switchover_status = session active
db_unique_name = dg1_primy
when check status in data guard broker its
for both the databases - dg1_primy and dg1_stdby its showing error ORA-16810: multiple errors or warnings detected for the database.
when checked dataguard log file on new primary server its showing
ORA-16816: incorrect database role
ORA-16700: the standby database has diverged from the primary database
Please guide me how to resolved issue.
Thanks & Regards,
Nikunj ThakerHi Nikunj,
You can find the scenario, in the "Problem : Data Guard Broker Switchover fails With ORA-16665 using Active Data Guard", on metalink.oracle.com
First of all manually complete the Switchover, ie. restart the Databases in its new Role. Note that the final Role Change has not been recognized by the Broker, so you have to rebuild the Data Guard Broker Configuration when the Databases have been restarted:
DGMGRL> remove configuration;
DGMGRL> create configuration ...
DGMGRL> add database ...
DGMGRL> enable configuration;
Best regards,
Orkun Gedik -
TAF On 11g DataGuard with FSFO
Hi All,
Today, i have created TAF for my 11.1.0.7 Oracle database running on RHEL 5.4 64 bit.
I have configured my databases with FSFO enabled. (MaxAvailibility with LGWR SYNC AFFIRM transport)
I created TAF with following entries:
1) Created and enabled a dedicated service in primary :
I have local_listener parameter set in my primary and standby databases.
begin
dbms_service.create_service('taf_test','taf_test');
end;
begin
DBMS_SERVICE.START_SERVICE('taf_test');
end;
begin
dbms_service.modify_service
('taf_test',
FAILOVER_METHOD => 'BASIC',
FAILOVER_TYPE => 'SELECT',
FAILOVER_RETRIES => 200,
FAILOVER_DELAY => 1);
end;
/2) Made sure that listener is listening to above created service:
lsnrctl services l_payee1fe_dg_001
LSNRCTL for Linux: Version 11.1.0.7.0 - Production on 21-JAN-2010 09:52:27
Copyright (c) 1991, 2008, Oracle. All rights reserved.
Services Summary...
Service "taf_test.us" has 1 instance(s).
Instance "payee1fe", status READY, has 1 handler(s) for this service...
Handler(s):
"DEDICATED" established:13 refused:0 state:ready
LOCAL SERVER3) TNS Entry :
taf_test.us=
(DESCRIPTION=
(SDU= 32767)
(ENABLE=BROKEN)
(ADDRESS_LIST=
(FAILOVER=ON)
(LOAD_BALANCE=YES)
(ADDRESS=(PROTOCOL=TCP)(HOST=payee1fe-orasvr.db.us.com)(PORT=58003))
(ADDRESS=(PROTOCOL=TCP)(HOST=payee1fe-orasvr.db.us.com)(PORT=58003))
(CONNECT_DATA=
(SERVICE_NAME = taf_test.us)
)4)Trigger for setting service on appropriate primary database :
create trigger taf_test after startup on database
declare
v_role varchar(30);
begin
select database_role into v_role from v$database;
if v_role = 'PRIMARY' then
DBMS_SERVICE.START_SERVICE('taf_test');
else
DBMS_SERVICE.STOP_SERVICE('taf_test');
end if;
end;
/5) Ran a big SELECT on primary and after 5 sec, kill primary's pmon to do fail-over.
6) After sometime, i saw that SELECT was hanged for some time and once, DGMGRL has open new primary (org standby), startup trigger got fired and SELECT started fetching rows from the point where it hanged.
In that way, my TAF was working properly as expected.
My question is :
How come new Primary got the session state of SELECT which originated on old primary and then failed-over to new primary ? I confimed that,SELECT was NOT re-executed on new primary and started fetching rows from the row where it hanged at the time of fail-over.
Since both the databases have different cache and controlfiles, i want to understand how TAF works on dataguard.
In RAC,there is always a GRD through which session state can be co-ordinated between different instances. But this is not the case in DG.
I did not find anything in PRIMARY's alert log. Though STANDBY alert log was containing below statement:
ALTER SYSTEM SET service_names='taf_test' SCOPE=MEMORY SID='payee1fe';Can anyone shed light on internal working of TAF in DG.
Regards,
Bhavik DesaiHi,
Just now i tested,SELECT FAIL-OVER for SELECT with PARALLEL (4) hint. I got below msg and SELECT did not executed on new primary:
ERROR:
ORA-25401: can not continue fetches
4350 rows selected.However, i observed that the session is failed-over to new primary. After getting above msg in SQLPLUS window, when i saw number of slaves given to my new sessions, i got :
SQL> select *From v$pq_tqstat;
DFO_NUMBER TQ_ID SERVER_TYP NUM_ROWS BYTES OPEN_TIME AVG_LATENCY WAITS TIMEOUTS PROCES INSTANCE
1 0 Producer 19800 65296 0 0 3 0 P002 1
1 0 Producer 19800 65296 0 0 4 1 P001 1
1 0 Producer 19800 65294 0 0 3 0 P000 1
1 0 Producer 19800 65296 0 0 3 0 P003 1
1 0 Consumer 4351 65296 0 0 8 0 QC 1Does it mean that, SELECT fail-over is only supported for serialized SELECTs ? Or there is other alternative to achive PARALLEL SELECT fail-over ?
Regards,
Bhavik Desai
Edited by: BhavikDe on Jan 24, 2010 11:30 PM -
Problem with dataguard on 10g peace of !"·$%&/
Hello everyone
I have problems with the dataguard, when i switchover to physical standby the error ora-16775 the dmgrl log says:
0 2 0 ORA-16775 Error: the target standby database has some redo log(s) missing. Cannot proceed with the switchover operation
I have made i think all the solutions around here to send or activate the redo log transport, this happend to me because disable the log_archive_dest_state on physical standby, so y make a cold backup of the primary database and set this to standby with the commands:
SQL> STARTUP NOMOUNT;
SQL> ALTER DATABASE MOUNT STANDBY DATABASE;
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION;
I attach the orcla.ora and orclb.ora to this question:
ORCLA: (primary)
orcla.__db_cache_size=868220928
orcla.__java_pool_size=16777216
orcla.__large_pool_size=16777216
orcla.__shared_pool_size=163577856
orcla.__streams_pool_size=0
*.archive_lag_target=0
*.audit_file_dest='c:\oracle\product\10.2.0/admin/orcla/adump'
*.background_dump_dest='c:\oracle\product\10.2.0/admin/orcla/bdump'
*.compatible='10.2.0.1.0'
*.control_files='C:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCLA\CONTROL01.CTL','C:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCLA\CONTROL02.CTL','C:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCLA\CONTROL03.CTL'#Restore Controlfile
*.core_dump_dest='c:\oracle\product\10.2.0/admin/orcla/cdump'
*.db_block_size=8192
*.db_domain=''
*.db_file_multiblock_read_count=16
*.db_name='ORCLA'
*.db_recovery_file_dest='c:\oracle\product\10.2.0/flash_recovery_area'
*.db_recovery_file_dest_size=2147483648
*.DB_UNIQUE_NAME='ORCLA'
*.dg_broker_start=TRUE
*.dispatchers='(PROTOCOL=TCP) (SERVICE=orclaXDB)'
*.fal_client='(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=SRV-LOGMEC-001)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=ORCLA_XPT)(INSTANCE_NAME=ORCLSID)(SERVER=dedicated)))'
*.fal_server='(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=SRV-LOGMEC-002)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=ORCLB_XPT)(SERVER=dedicated)))'
*.instance_name='ORCLSID'
*.job_queue_processes=10
*.log_archive_config='dg_config=(ORCLB)'
*.log_archive_dest_1='LOCATION=D:\oradata\archivelogs\orcla VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=ORCLA'
orcla.log_archive_dest_1='location="D:\oradata\archivelogs\orcla"','valid_for=(ONLINE_LOGFILE,ALL_ROLES)'
*.log_archive_dest_2='service="(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=SRV-LOGMEC-002)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=ORCLB_XPT)(INSTANCE_NAME=ORCLSID)(SERVER=dedicated)))"',' LGWR ASYNC NOAFFIRM delay=0 OPTIONAL max_failure=0 max_connections=1 reopen=300 db_unique_name="ORCLB" register net_timeout=180 valid_for=(online_logfile,primary_role)'
*.log_archive_dest_state_1='ENABLE'
orcla.log_archive_dest_state_1='ENABLE'
*.log_archive_dest_state_2='ENABLE'
*.log_archive_format='DBSID_%t_%s_%r.arc'
orcla.log_archive_format='DBSID_%t_%s_%r.arc'
*.log_archive_max_processes=2
*.log_archive_min_succeed_dest=1
orcla.log_archive_trace=0
*.log_checkpoint_interval=10000
*.log_checkpoint_timeout=1800
*.open_cursors=3000
*.optimizer_mode='RULE'
*.pga_aggregate_target=16777216
*.processes=400
*.remote_login_passwordfile='EXCLUSIVE'
*.sga_max_size=1073741824
*.sga_target=1073741824
orcla.standby_archive_dest=''
*.standby_file_management='auto'
*.undo_management='AUTO'
*.undo_tablespace='UNDOTBS1'
*.user_dump_dest='c:\oracle\product\10.2.0/admin/orcla/udump'
ORCLB: (standby)
orclb.__db_cache_size=868220928
orclb.__java_pool_size=16777216
orclb.__large_pool_size=16777216
orclb.__shared_pool_size=163577856
orclb.__streams_pool_size=0
*.aq_tm_processes=0
*.archive_lag_target=0
*.audit_file_dest='c:\oracle\product\10.2.0/admin/orclb/adump'
*.background_dump_dest='c:\oracle\product\10.2.0/admin/orclb/bdump'
*.compatible='10.2.0.1.0'
*.control_files='c:\oracle\product\10.2.0/oradata/orclb/\stand.ctl'
*.core_dump_dest='c:\oracle\product\10.2.0/admin/orclb/cdump'
*.db_block_size=8192
*.db_domain=''
*.db_file_multiblock_read_count=16
*.db_name='ORCLA'
*.db_recovery_file_dest='c:\oracle\product\10.2.0/flash_recovery_area'
*.db_recovery_file_dest_size=2147483648
*.DB_UNIQUE_NAME='ORCLB'
*.dg_broker_start=TRUE
*.dispatchers='(PROTOCOL=TCP) (SERVICE=orclaXDB)'
*.fal_client='(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=SRV-LOGMEC-002)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=ORCLB_XPT)(INSTANCE_NAME=ORCLSID)(SERVER=dedicated)))'
*.fal_server='(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=SRV-LOGMEC-001)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=ORCLA_XPT)(SERVER=dedicated)))'
*.instance_name='ORCLSID'
*.job_queue_processes=10
*.log_archive_config='dg_config=(ORCLA)'
*.log_archive_dest_1='LOCATION=C:\oracle\product\10.2.0\oradata\orclb VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=ORCLB'
orclb.log_archive_dest_1='location="C:\oracle\product\10.2.0\oradata\orclb"','valid_for=(ALL_LOGFILES,ALL_ROLES)'
*.log_archive_dest_2=''
orclb.log_archive_dest_2='location="D:\oradata\archivelogs\orclb"','valid_for=(STANDBY_LOGFILE,STANDBY_ROLE)'
*.log_archive_dest_state_1='ENABLE'
orclb.log_archive_dest_state_1='ENABLE'
*.log_archive_dest_state_2='ENABLE'
orclb.log_archive_dest_state_2='ENABLE'
*.log_archive_format='DBSID_%t_%s_%r.arc'
orclb.log_archive_format='DBSID_%t_%s_%r.arc'
*.log_archive_max_processes=2
*.log_archive_min_succeed_dest=1
*.log_archive_trace=0
orclb.log_archive_trace=0
*.log_checkpoint_interval=10000
*.log_checkpoint_timeout=1800
*.open_cursors=3000
*.optimizer_mode='RULE'
*.pga_aggregate_target=16777216
*.processes=400
*.remote_login_passwordfile='EXCLUSIVE'
*.sga_max_size=1073741824
*.sga_target=1073741824
orclb.standby_archive_dest='D:\oradata\archivelogs\orclb'
*.standby_file_management='auto'
*.undo_management='AUTO'
*.undo_tablespace='UNDOTBS1'
*.user_dump_dest='c:\oracle\product\10.2.0/admin/orclb/udump'
DGMGRL (primary)
DG 2009-11-11-22:05:17 0 2 702684180 DMON: CTL_ENABLE of ORCLB
DG 2009-11-11-22:05:17 0 2 702684180 requires reset of LOG XPT Engine
DG 2009-11-11-22:05:17 0 2 702684180 on Site ORCLA
DG 2009-11-11-22:05:17 0 2 0 Reset Log Transport Resource: SetState ONLINE, phase BUILD-UP, External Cond ENABLE
DG 2009-11-11-22:05:17 0 2 0 Set log transport destination: SetState ONLINE, phase BUILD-UP, External Cond ENABLE
DG 2009-11-11-22:05:17 0 2 0 Executing SQL [alter system set log_archive_dest_2 = 'service="(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=SRV-LOGMEC-002)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=ORCLB_XPT)(INSTANCE_NAME=ORCLSID)(SERVER=dedicated)))"', ' LGWR ASYNC NOAFFIRM delay=0 OPTIONAL max_failure=0 max_connections=1 reopen=300 db_unique_name="ORCLB" register net_timeout=180 valid_for=(online_logfile,primary_role)']
DG 2009-11-11-22:05:17 0 2 0 SQL [alter system set log_archive_dest_2 = 'service="(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=SRV-LOGMEC-002)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=ORCLB_XPT)(INSTANCE_NAME=ORCLSID)(SERVER=dedicated)))"', ' LGWR ASYNC NOAFFIRM delay=0 OPTIONAL max_failure=0 max_connections=1 reopen=300 db_unique_name="ORCLB" register net_timeout=180 valid_for=(online_logfile,primary_role)'] Executed successfully
DG 2009-11-11-22:05:17 0 2 0 Executing SQL [alter system set log_archive_dest_state_2 = 'ENABLE']
DG 2009-11-11-22:05:17 0 2 0 SQL [alter system set log_archive_dest_state_2 = 'ENABLE'] Executed successfully
DG 2009-11-11-22:05:17 0 2 0 Executing SQL [ALTER SYSTEM SWITCH ALL LOGFILE]
DG 2009-11-11-22:05:22 0 2 0 SQL [ALTER SYSTEM SWITCH ALL LOGFILE] Executed successfully
DG 2009-11-11-22:05:22 0 2 0 DMON: site 01001000, instance 00000001 queuing healthcheck lock request
DG 2009-11-11-22:05:22 0 2 0 DMON: Releasing healthcheck master lock
DG 2009-11-11-22:05:22 0 2 0 DMON: Health check master lock conversion successful
DG 2009-11-11-22:05:22 0 2 0 DMON: a process acquired the healthcheck master lock
DG 2009-11-11-22:05:22 0 2 702684180 DMON: status from rfi_post_instances() for ENABLE = ORA-00000
DG 2009-11-11-22:05:22 0 2 0 INSV: Received message for inter-instance publication
DG 2009-11-11-22:05:22 0 2 702684180 DMON: ENABLE Complete, Object ORCLB
DG 2009-11-11-22:05:22 0 2 0 req_id 2.1.702684180, opcode CTL_ENABLE, phase END, flags 5
DG 2009-11-11-22:05:22 0 2 702684180 enabled in State STANDBY
DG 2009-11-11-22:05:22 0 2 702684180 rfm_inst_phase_dispatch 16 END phase processing
DG 2009-11-11-22:05:22 0 2 0 INSV: All instances have replied for message
DG 2009-11-11-22:05:22 0 2 0 req_id 2.1.702684180, opcode CTL_ENABLE, phase END
DG 2009-11-11-22:05:22 0 2 702684180 DMON: CTL_ENABLE operation completed
DG 2009-11-11-22:05:22 0 2 702684180 DMON: Entered rfm_release_chief_lock for CTL_ENABLE
DGMGRL (standby)
SCOPE=SPFILE sid='orclb']
DG 2009-11-11-22:04:06 0 2 0 SQL [ALTER SYSTEM SET log_archive_format='DBSID_%t_%s_%r.arc' SCOPE=SPFILE sid='orclb'] Executed successfully
DG 2009-11-11-22:04:07 0 2 0 Setting init.ora parameter with SQL [ALTER SYSTEM SET standby_file_management='AUTO' SCOPE=BOTH sid='*']
DG 2009-11-11-22:04:07 0 2 0 Executing SQL [ALTER SYSTEM SET standby_file_management='AUTO' SCOPE=BOTH sid='*']
DG 2009-11-11-22:04:07 0 2 0 SQL [ALTER SYSTEM SET standby_file_management='AUTO' SCOPE=BOTH sid='*'] Executed successfully
DG 2009-11-11-22:04:07 0 2 0 Setting init.ora parameter with SQL [ALTER SYSTEM SET archive_lag_target=0 SCOPE=BOTH sid='*']
DG 2009-11-11-22:04:07 0 2 0 Executing SQL [ALTER SYSTEM SET archive_lag_target=0 SCOPE=BOTH sid='*']
DG 2009-11-11-22:04:07 0 2 0 SQL [ALTER SYSTEM SET archive_lag_target=0 SCOPE=BOTH sid='*'] Executed successfully
DG 2009-11-11-22:04:07 0 2 0 Setting init.ora parameter with SQL [ALTER SYSTEM SET log_archive_max_processes=2 SCOPE=BOTH sid='*']
DG 2009-11-11-22:04:07 0 2 0 Executing SQL [ALTER SYSTEM SET log_archive_max_processes=2 SCOPE=BOTH sid='*']
DG 2009-11-11-22:04:07 0 2 0 SQL [ALTER SYSTEM SET log_archive_max_processes=2 SCOPE=BOTH sid='*'] Executed successfully
DG 2009-11-11-22:04:07 0 2 0 Setting init.ora parameter with SQL [ALTER SYSTEM SET log_archive_min_succeed_dest=1 SCOPE=BOTH sid='*']
DG 2009-11-11-22:04:07 0 2 0 Executing SQL [ALTER SYSTEM SET log_archive_min_succeed_dest=1 SCOPE=BOTH sid='*']
DG 2009-11-11-22:04:07 0 2 0 SQL [ALTER SYSTEM SET log_archive_min_succeed_dest=1 SCOPE=BOTH sid='*'] Executed successfully
DG 2009-11-11-22:04:07 0 2 0 Executing SQL [ALTER SYSTEM SET fal_server='(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=SRV-LOGMEC-001)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=ORCLA_XPT)(SERVER=dedicated)))']
DG 2009-11-11-22:04:07 0 2 0 SQL [ALTER SYSTEM SET fal_server='(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=SRV-LOGMEC-001)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=ORCLA_XPT)(SERVER=dedicated)))'] Executed successfully
DG 2009-11-11-22:04:07 0 2 0 Executing SQL [ALTER SYSTEM SET fal_client='(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=SRV-LOGMEC-002)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=ORCLB_XPT)(INSTANCE_NAME=ORCLSID)(SERVER=dedicated)))']
DG 2009-11-11-22:04:07 0 2 0 SQL [ALTER SYSTEM SET fal_client='(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=SRV-LOGMEC-002)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=ORCLB_XPT)(INSTANCE_NAME=ORCLSID)(SERVER=dedicated)))'] Executed successfully
DG 2009-11-11-22:04:07 0 2 0 Database Resource SetState succeeded
DG 2009-11-11-22:04:07 0 2 0 RSM 0 received SETSTATE request: rid=0x02031000, sid=1, phid=2, econd=7, sitehndl=0x7fffffff
DG 2009-11-11-22:04:07 0 2 0 Physical Apply Resource: SetState ONLINE, phase BUILD-UP, External Cond ENABLE
DG 2009-11-11-22:04:07 0 2 0 Executing SQL [ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL]
DG 2009-11-11-22:04:13 0 2 0 SQL [ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL] Executed successfully
DG 2009-11-11-22:05:11 0 2 0 Executing SQL [ALTER DATABASE RECOVER MANAGED STANDBY DATABASE THROUGH ALL SWITCHOVER DISCONNECT USING CURRENT LOGFILE]
DG 2009-11-11-22:05:17 0 2 0 SQL [ALTER DATABASE RECOVER MANAGED STANDBY DATABASE THROUGH ALL SWITCHOVER DISCONNECT USING CURRENT LOGFILE] Executed successfully
DG 2009-11-11-22:05:17 0 2 0 INSV: All instances have replied for message
DG 2009-11-11-22:05:17 0 2 0 req_id 2.1.702684180, opcode CTL_ENABLE, phase BUILDUP
DG 2009-11-11-22:05:17 0 2 702684180 DMON: Entered rfm_release_chief_lock for CTL_ENABLE
DG 2009-11-11-22:05:22 0 2 702684180 DMON: Entered rfm_get_chief_lock() for CTL_ENABLE, reason 0
DG 2009-11-11-22:05:22 0 2 702684180 DMON: chief lock convert for write op CTL_ENABLE
DG 2009-11-11-22:05:22 0 2 702684180 DMON: chief lock convert for enable
DG 2009-11-11-22:05:22 0 2 702684180 DMON: CLSR being notified to enable services and startup standby instances as appropriate during ENABLE.
DG 2009-11-11-22:05:22 0 2 702684180 DMON: status from rfi_post_instances() for ENABLE = ORA-00000
DG 2009-11-11-22:05:22 0 2 0 INSV: Received message for inter-instance publication
DG 2009-11-11-22:05:22 0 2 0 req_id 2.1.702684180, opcode CTL_ENABLE, phase END, flags 5
DG 2009-11-11-22:05:22 0 2 702684180 rfm_inst_phase_dispatch 16 END phase processing
DG 2009-11-11-22:05:22 0 2 0 INSV: All instances have replied for message
DG 2009-11-11-22:05:22 0 2 0 req_id 2.1.702684180, opcode CTL_ENABLE, phase END
DG 2009-11-11-22:05:22 0 2 702684180 DMON: Entered rfm_release_chief_lock for CTL_ENABLE
DG 2009-11-11-22:05:22 0 2 702684180 DMON: Data Guard Broker initiated operation complete
DG 2009-11-11-22:05:22 0 2 702684180 DMON: CTL_ENABLE operation completed
Alert oracle primary:
FAL[server]: Fail to queue the whole FAL gap
GAP - thread 1 sequence 731-731
DBID 2809078314 branch 696087148
Wed Nov 11 22:05:17 2009
ALTER SYSTEM SET log_archive_dest_2='service="(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=SRV-LOGMEC-002)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=ORCLB_XPT)(INSTANCE_NAME=ORCLSID)(SERVER=dedicated)))"',' LGWR ASYNC NOAFFIRM delay=0 OPTIONAL max_failure=0 max_connections=1 reopen=300 db_unique_name="ORCLB" register net_timeout=180 valid_for=(online_logfile,primary_role)' SCOPE=BOTH;
Wed Nov 11 22:05:17 2009
ALTER SYSTEM SET log_archive_dest_state_2='ENABLE' SCOPE=BOTH;
Wed Nov 11 22:05:17 2009
Thread 1 cannot allocate new log, sequence 805
Private strand flush not complete
Current log# 2 seq# 804 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCLA\REDO02.LOG
Thread 1 advanced to log sequence 805
Current log# 3 seq# 805 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCLA\REDO03.LOG
Wed Nov 11 22:05:22 2009
LNS: Failed to archive log 2 thread 1 sequence 804 (3113)
LGWR: Setting 'active' archival for destination LOG_ARCHIVE_DEST_2
LNS: Standby redo logfile selected for thread 1 sequence 805 for destination LOG_ARCHIVE_DEST_2
Alter oracle standby
Primary database is in MAXIMUM PERFORMANCE mode
Wed Nov 11 22:05:22 2009
RFS LogMiner: Client disabled from further notification
Primary database is in MAXIMUM PERFORMANCE mode
RFS[1]: Successfully opened standby log 4: 'C:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ORCLA\ONLINELOG\O1_MF_4_59HJ9T8L_.LOG'
Wed Nov 11 22:05:46 2009
FAL[client]: Failed to request gap sequence
GAP - thread 1 sequence 731-731
DBID 2809078314 branch 696087148
FAL[client]: All defined FAL servers have been attempted.
Check that the CONTROL_FILE_RECORD_KEEP_TIME initialization
parameter is defined to a value that is sufficiently large
enough to maintain adequate log switch information to resolve
archivelog gaps.
Wed Nov 11 22:06:01 2009
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
RFS[2]: Assigned to RFS process 5848
RFS[2]: Identified database type as 'physical standby'
Wed Nov 11 22:17:54 2009
db_recovery_file_dest_size of 2048 MB is 0.00% used. This is a
user-specified limit on the amount of space that will be used by this
database for recovery-related files, and does not reflect the amount of
space available in the underlying filesystem or ASM diskgroup.
Can anyone see what !"·$%& is wrong whit this? maybe is the gap? this is a exact copy of the primary but set to standby.SQL> recover database using backup controlfile;
ORA-00279: el cambio 25608871 generado en 09/24/2009 23:08:11 es necesario para
el thread 1
ORA-00289: sugerencia: D:\ORADATA\ARCHIVELOGS\ORCLB\DBSID_1_731_696087148.ARC
ORA-00280: el cambio 25608871 para el thread 1 estß en la secuencia n·mero 731
Especificar log: {<RET>=sugerido | nombre_archivo | AUTO | CANCEL}
ORA-00308: no se puede abrir el archive log
'D:\ORADATA\ARCHIVELOGS\ORCLB\DBSID_1_731_696087148.ARC'
ORA-27041: no se ha podido abrir el archivo
OSD-04002: no se ha podido abrir el archivo
O/S-Error: (OS 2) El sistema no puede hallar el archivo especificado.
So how i can recreate this file if i dont have it? anyone can help, please!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! -
Starup of active dataguard in RAC
Hi,
i have a setup of active dataguard in RAC. This is my first time implementing dataguard in RAC.
Primary - RAC
Standby - RAC with active dataguard
when ever standby server(anyone of the RAC instance) reboots it is getting till mount state. And after that how can i get the database be opened and put in recovery mode to do redo apply.
I tried to push manual script as a startup script . Intially i kept sleep command for 15-20min and then connect to db instance and try to recovery from mounted database. But my mounted database is taking 15-30min to comeup once the server is rebooted.
please help me how we configure startup statements once the RAC is in mount state(cluster is getting till this point) after server reboot.Hello;
If you are not using Data Guard Broker you need to open the standby database and set it in read only mode and then start the managed recovery as shown below.
SQL> shutdown immediate;
SQL> startup
SQL> recover managed standby database using current logfile disconnect;
With broker its like this :
Stop redo apply with the following command from Data Guard Broker
DGMGRL> EDIT DATABASE '?' SET STATE='APPLY-OFF';
Open standby read-only via SQL*Plus
SQL> alter database open read only;
Restart redo apply via broker
DGMGRL> EDIT DATABASE '?' SET STATE='APPLY-ON';
Best Regards
mseberg -
Creaton of Standby database and dataguard broker
Hi Experts,
I am using Linux with Oracle version 11gR2. We have planned to create a physical standby database and also configure dataguard broker for the standby database.
Also, I've read the documents that active dataguard is a feature on 11g. Is it not possible on 10g ?
Can someone please provide me the steps to create the standby database and configure the dataguard broker.Hello;
A simple Data Broker setup would be :
On both Primary and Standby sites, change the initialization parameter in the spfile to enable the Data guard broker.
SQL> Alter system set dg_broker_start=True scope=both;
On the PRIMARY site, open the ‘cmd’ and start Command Line Interface (CLI) of the Dataguard Broker (DGMGRL).
/home/oracle:PRIMARY >dgmgrl
DGMGRL for Linux: Version 11.2.0.1.0 - 64bit Production
DGMGRL> connect sys/password@PRIMARY
Create broker configuration.
DGMGRL> create configuration ‘broker1’ as
primary database is 'PRIMARY'
connect identifier is primary;Configuration "?broker1?" created with primary database "PRIMARY"
DGMGRL>
(‘primary’ in Connect identifier is the service name through which the broker is connected to the PRIMARY database)
Add Standby Database to the above configuration.
DGMGRL> add database 'standby' as
connect identifier is 'STANDBY'
maintained as physical;
Database "standby" added
(‘to_standby’ in Connect identifier is the service name through which the broker is connected to the STANDBY database)
Now the configuration has been set up but it is still disabled. You can view the configuration by executing:
DGMGRL> show configuration
The next step is to ENABLE the configuration ‘broker1’.
DGMGRL> enable configuration;
Enabled.
Again view the configuration.
DGMGRL> show configuration
Configuration - ?broker1?
Protection Mode: MaxPerformance
Databases:
PRIMARY - Primary database
standby - Physical standby database
Fast-Start Failover: DISABLED
Configuration Status:
SUCCESSIn my humble opinion its a good idea to setup Data Guard without Broker and get the "feel" of it first.
Remember, once you setup Broker, you cannot use SQL to change your Data Guard setup.
Best Regards
mseberg -
Dataguard broker Warning: ORA-16610
Hi
Oracle 10g.
I just configured dataguard broker and followed all the steps in:
http://apunhiran.blogspot.com/2009/09/how-to-configure-data-guard-broker.html
However, I am constantly getting ORA-16610.
any idea, how to resolve this ?
DGMGRL> SHOW CONFIGURATION
Configuration
Name: CatalogDR
Enabled: YES
Protection Mode: MaxPerformance
Fast-Start Failover: DISABLED
Databases:
orclprd_wlg - Primary database
orclprd_akl - Physical standby database
Current status for "CatalogDR":
Warning: ORA-16610: command 'Broker automatic health check' in progressAh broker!
My friend calls it "data broken"
I have my setup notes I can post if you want. I had it working and I like its speed, but I found it to be a pain and went back to SQL for all my commands.
My offer to post my broker setup notes stands
mseberg
Later
John;
I checked my setup note and here's what i have on your current error :
ORA-16607 on SHOW CONFIGURATION
Problem: After creating your configuration and adding the standby database, you issued a SHOW CONFIGURATION as suggested. Instead of the expected SUCCESS, the report ends up with
Warning: ORA-16607: one or more databases have failed
. Checking with oerr ora 16607 was not very helpful (see above), and you neither can find anything in your alert.log nor any trace files.
Cause: Probably at least one of your databases is not using an SPFILE.
Solution: Check whether your databases have an SPFILE associated. It is usually located in $ORACLE_HOME/dbs/spfile$ORACLE_SID.ora. If it does not exist, create it: Login to your database as SYSDBA, and issue the command CREATE SPFILE FROM PFILE;. Even if it exists, to make the database using it you need to restart the instance - it must be used already at startup.Edited by: mseberg on Aug 11, 2011 8:12 PM -
Hi,
We've configured dataguard on our system and have been performing manual switchovers (via SQL) smoothly. We would now like to configure Broker for this purpose- via the dgmgrl command line since we don't have 10G Grid. While we're finding immense documentation on how to do so on the 10g database, we're unable to find anything with regards to EBS. Basically we want confirmation that the configuration for EBS is the same as for the database alone, since based on past experience we know that the EBS factor can make things a little different.
If anyone has implemented Broker on EBS please let me know. Btw, we're currently on EBS 11.5.10.2 and DB 10.2.0.4. Thanks.
Lia.We've configured dataguard on our system and have been performing manual switchovers (via SQL) smoothly. We would now like to configure Broker for this purpose- via the dgmgrl command line since we don't have 10G Grid. While we're finding immense documentation on how to do so on the 10g database, we're unable to find anything with regards to EBS. Basically we want confirmation that the configuration for EBS is the same as for the database alone, since based on past experience we know that the EBS factor can make things a little different.It is the same.
If anyone has implemented Broker on EBS please let me know. Btw, we're currently on EBS 11.5.10.2 and DB 10.2.0.4.Refer to "Oracle® Data Guard Broker 10g Release 2 (10.2)" manual.
Oracle® Data Guard Broker 10g Release 2 (10.2)
http://download-uk.oracle.com/docs/cd/B19306_01/server.102/b14230/toc.htm -
Hopefully my last dataguard topic - Failover & reinstate
So I have a 10.2 setup with a primary and physical standby.
I've configured dataguard broker and it all looks good.
Now I'm trying to test failover. I shutdown the primary, executed a failover command in dgmgrl to failover to the standby and it's up and running....
I can't get the new standby (old primary) to reinstate. All I get is ORA-16653: failed to reinstate database. The docs say if it fails, you have to go through the steps to create a standby database as you did at the start of this entire process.
Okay, well from where I'm sitting, all of the settings are already done (since I set them all on the primary before it was disabled), so the only thing I should need is to get a standby control file from the primary and copy it in...but it still won't reinstate. I copied the database from primary over to secondary...still won't. I can mount it but cannot select from any of the v$ views. I've restarted the listener, no help.
The way this is configured, is I have the exact same instance name on two different servers. The only difference between them is the unique_db_name (band & bandbackup). I created tnsnames entries on each box that correspond to the unique names.
I guess I don't see why this is so hard. I have two databases, the current primary is originally a copy of the old primary which had all of the needed alters run on it. The only difference was in the spfile settings (opposite unique_db_names for delivery) and I've verified those are set. What am I missing?Look, here's what I do to reinstantiate a failed standby:
1. Remove all the DataGuard configuration including DataGuard parameters in Primary and Standby init files.
2. Change the DB_UNIQUE_NAME of the Primary to what it should be (BAND, for you)
3. Put every tablespaces in turn in BACKUP mode and rcp their DATAFILEs to remote standby host.
4. Create a standby controlfile, rcp it to remote standby host.
5. Multiplex the standby controlfile as needed
6. Create a pfile from the primary spfile and change needed parameters (LOG_ARCHIVE_DEST_n, DB_UNIQUE_NAME) to reflect it's a STANDBY database now.
Transfer this pfile to remote standby host and build a spfile from it
7. Startup the standby in mount mode, check the necessary archive log files to bring it to a concistent point in time.
Because the rcps and other processes can take time it's a fuzzy copy of the main database. Then rcp the archived redo logs to the standby and "recover standby database until cancel".
Once this is done, put the standby in recover managed mode, check if MRP is started up (from v$bgprocess) and check apply status (from v$managed_standby).
8. choose a LOG_ARCHIVE_DEST_n from the Primary and set a SERVICE to the new standby.
Then switch current logfile. Check the sending status in alert log. Check on standby host the archive is received.
9. check apply progress in v$managed_standby
10. no step 10 all is OK.And this has always worked for me!
About your other question: "what does the DG Broker do?"
The GB Broker, as for me helps in mainly 2 points:
. Check the configuration. It monitors if everything is ok, and ensores log sending and in max protection mode the shutdown of the primary if standby is unrechable, and so on.
. Enables the switchover option, which isn't available without a DG Broker (IIRC).
Good Luck,
Yoann. -
Hi Gurus,
I have implemented datagurad set up. Where my primary database is mydb and standby database is orcl. Now I am implementing dataguard broker and while after the configuration of broker I am seeing the disabled keyword is coming in front of physical standby database. Please check below.
Before enabling the configuration:
DGMGRL> show configuration;
Configuration - PACKT
Protection Mode: MaxPerformance
Databases:
mydb_un - Primary database
orcl_un - Physical standby database
Fast-Start Failover: DISABLED
Configuration Status:
DISABLED
Enabling the configuration:
DGMGRL> enable configuration;
Enabled.
After enbaling the configuration:
DGMGRL> show configuration;
Configuration - PACKT
Protection Mode: MaxPerformance
Databases:
mydb_un - Primary database
orcl_un - Physical standby database (disabled)
Fast-Start Failover: DISABLED
Configuration Status:
SUCCESS
Please check the red color font and kindly let me know what is the meaning of it and why it is coming as disabled.
Regards,
Michel.Hi Tobi,
No, redo are not appling to orcl_un database now. I don't know what happened Suddenly. Please check below:
On standby database:
SQL> select sequence#, first_time, next_time from v$archived_log order by sequence#;
SEQUENCE# FIRST_TIM NEXT_TIME
35 05-JAN-14 05-JAN-14
36 05-JAN-14 05-JAN-14
37 05-JAN-14 07-JAN-14
38 07-JAN-14 07-JAN-14
39 07-JAN-14 07-JAN-14
40 07-JAN-14 07-JAN-14
41 07-JAN-14 07-JAN-14
42 07-JAN-14 07-JAN-14
43 07-JAN-14 07-JAN-14
44 07-JAN-14 07-JAN-14
45 07-JAN-14 07-JAN-14
SEQUENCE# FIRST_TIM NEXT_TIME
46 07-JAN-14 07-JAN-14
47 07-JAN-14 07-JAN-14
48 07-JAN-14 07-JAN-14
49 07-JAN-14 07-JAN-14
50 07-JAN-14 07-JAN-14
51 07-JAN-14 07-JAN-14
52 07-JAN-14 07-JAN-14
53 07-JAN-14 07-JAN-14
19 rows selected.
Now switch logfile on primary database:
SQL> alter system switch logfile;
System altered.
Again now I checked standby database:
SQL> select sequence#, first_time, next_time from v$archived_log order by sequence#;
SEQUENCE# FIRST_TIM NEXT_TIME
35 05-JAN-14 05-JAN-14
36 05-JAN-14 05-JAN-14
37 05-JAN-14 07-JAN-14
38 07-JAN-14 07-JAN-14
39 07-JAN-14 07-JAN-14
40 07-JAN-14 07-JAN-14
41 07-JAN-14 07-JAN-14
42 07-JAN-14 07-JAN-14
43 07-JAN-14 07-JAN-14
44 07-JAN-14 07-JAN-14
45 07-JAN-14 07-JAN-14
SEQUENCE# FIRST_TIM NEXT_TIME
46 07-JAN-14 07-JAN-14
47 07-JAN-14 07-JAN-14
48 07-JAN-14 07-JAN-14
49 07-JAN-14 07-JAN-14
50 07-JAN-14 07-JAN-14
51 07-JAN-14 07-JAN-14
52 07-JAN-14 07-JAN-14
53 07-JAN-14 07-JAN-14
19 rows selected.
On standby database:
SQL> select db_unique_name, database_role, open_mode from v$database;
DB_UNIQUE_NAME DATABASE_ROLE OPEN_MODE
orcl_un PHYSICAL STANDBY MOUNTED
SQL> show parameter log_archive_config
NAME TYPE VALUE
log_archive_config string nodg_config
SQL> show parameter fal_server
NAME TYPE VALUE
fal_server string
# output of /u01/app/oracle/diag/rdbms/orcl_un/orcl/trace/orcl_arc2_32019.trc
*** 2014-01-07 15:03:50.728
*** 2014-01-07 15:03:50.728 4539 krsu.c
Logged on to standby successfully
Client logon and security negotiation successful!
Error 16009 attaching RFS server to standby instance at host 'mydb'
Error 16009 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'mydb'
ORA-16009: invalid redo transport destination
*** 2014-01-07 15:03:50.761 4132 krsh.c
PING[ARC2]: Heartbeat failed to connect to standby 'mydb'. Error is 16009.
*** 2014-01-07 15:03:50.762 2747 krsi.c
krsi_dst_fail: dest:2 err:16009 force:0 blast:1
*** 2014-01-07 15:09:50.836
Redo shipping client performing standby login
*** 2014-01-07 15:09:51.325 4539 krsu.c
Logged on to standby successfully
Client logon and security negotiation successful!
Error 16009 attaching RFS server to standby instance at host 'mydb'
Error 16009 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'mydb'
ORA-16009: invalid redo transport destination
*** 2014-01-07 15:09:51.330 4132 krsh.c
PING[ARC2]: Heartbeat failed to connect to standby 'mydb'. Error is 16009.
*** 2014-01-07 15:09:51.330 2747 krsi.c
krsi_dst_fail: dest:2 err:16009 force:0 blast:1
Redo shipping client performing standby login
*** 2014-01-07 15:15:51.592
*** 2014-01-07 15:15:51.592 4539 krsu.c
Logged on to standby successfully
Client logon and security negotiation successful!
Error 16009 attaching RFS server to standby instance at host 'mydb'
Error 16009 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'mydb'
ORA-16009: invalid redo transport destination
*** 2014-01-07 15:15:51.654 4132 krsh.c
PING[ARC2]: Heartbeat failed to connect to standby 'mydb'. Error is 16009.
*** 2014-01-07 15:15:51.654 2747 krsi.c
krsi_dst_fail: dest:2 err:16009 force:0 blast:1
*** 2014-01-07 15:21:51.743
Redo shipping client performing standby login
*** 2014-01-07 15:21:51.919
*** 2014-01-07 15:21:51.919 4539 krsu.c
Logged on to standby successfully
Client logon and security negotiation successful!
Error 16009 attaching RFS server to standby instance at host 'mydb'
Error 16009 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'mydb'
ORA-16009: invalid redo transport destination
*** 2014-01-07 15:21:51.937 4132 krsh.c
PING[ARC2]: Heartbeat failed to connect to standby 'mydb'. Error is 16009.
*** 2014-01-07 15:21:51.938 2747 krsi.c
krsi_dst_fail: dest:2 err:16009 force:0 blast:1
*** 2014-01-07 15:27:52.000
Redo shipping client performing standby login
*** 2014-01-07 15:27:52.734 4539 krsu.c
Logged on to standby successfully
Client logon and security negotiation successful!
Error 16009 attaching RFS server to standby instance at host 'mydb'
*** 2014-01-07 15:27:52.880
Error 16009 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'mydb'
ORA-16009: invalid redo transport destination
*** 2014-01-07 15:27:52.881 4132 krsh.c
PING[ARC2]: Heartbeat failed to connect to standby 'mydb'. Error is 16009.
*** 2014-01-07 15:27:52.881 2747 krsi.c
krsi_dst_fail: dest:2 err:16009 force:0 blast:1
Redo shipping client performing standby login
*** 2014-01-07 15:32:55.707
*** 2014-01-07 15:32:55.707 4539 krsu.c
Logged on to standby successfully
Client logon and security negotiation successful!
Error 16009 attaching RFS server to standby instance at host 'mydb'
Error 16009 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'mydb'
ORA-16009: invalid redo transport destination
*** 2014-01-07 15:32:55.778 4132 krsh.c
PING[ARC2]: Heartbeat failed to connect to standby 'mydb'. Error is 16009.
*** 2014-01-07 15:32:55.778 2747 krsi.c
krsi_dst_fail: dest:2 err:16009 force:0 blast:1
*** 2014-01-07 15:38:55.925
Redo shipping client performing standby login
*** 2014-01-07 15:38:56.353 4539 krsu.c
Logged on to standby successfully
Client logon and security negotiation successful!
Error 16009 attaching RFS server to standby instance at host 'mydb'
Error 16009 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'mydb'
ORA-16009: invalid redo transport destination
*** 2014-01-07 15:38:56.488 4132 krsh.c
PING[ARC2]: Heartbeat failed to connect to standby 'mydb'. Error is 16009.
*** 2014-01-07 15:38:56.488 2747 krsi.c
krsi_dst_fail: dest:2 err:16009 force:0 blast:1
Redo shipping client performing standby login
*** 2014-01-07 15:44:56.778
*** 2014-01-07 15:44:56.778 4539 krsu.c
Logged on to standby successfully
Client logon and security negotiation successful!
Error 16009 attaching RFS server to standby instance at host 'mydb'
Error 16009 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'mydb'
ORA-16009: invalid redo transport destination
*** 2014-01-07 15:44:56.793 4132 krsh.c
PING[ARC2]: Heartbeat failed to connect to standby 'mydb'. Error is 16009.
*** 2014-01-07 15:44:56.793 2747 krsi.c
krsi_dst_fail: dest:2 err:16009 force:0 blast:1
*** 2014-01-07 15:50:56.908
Redo shipping client performing standby login
*** 2014-01-07 15:50:57.167 4539 krsu.c
Logged on to standby successfully
Client logon and security negotiation successful!
This database DGID not in Data Guard configuration at 'mydb'
Error 16057 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'mydb'
ORA-16057: server not in Data Guard configuration
*** 2014-01-07 15:50:57.241 4132 krsh.c
PING[ARC2]: Heartbeat failed to connect to standby 'mydb'. Error is 16057.
*** 2014-01-07 15:50:57.241 2747 krsi.c
krsi_dst_fail: dest:2 err:16057 force:0 blast:1
*** 2014-01-07 15:56:57.425
Redo shipping client performing standby login
*** 2014-01-07 15:56:57.729 4539 krsu.c
Logged on to standby successfully
Client logon and security negotiation successful!
This database DGID not in Data Guard configuration at 'mydb'
Error 16057 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'mydb'
ORA-16057: server not in Data Guard configuration
*** 2014-01-07 15:56:57.743 4132 krsh.c
PING[ARC2]: Heartbeat failed to connect to standby 'mydb'. Error is 16057.
*** 2014-01-07 15:56:57.743 2747 krsi.c
krsi_dst_fail: dest:2 err:16057 force:0 blast:1
Redo shipping client performing standby login
*** 2014-01-07 16:02:58.145
*** 2014-01-07 16:02:58.145 4539 krsu.c
Logged on to standby successfully
Client logon and security negotiation successful!
This database DGID not in Data Guard configuration at 'mydb'
Error 16057 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'mydb'
ORA-16057: server not in Data Guard configuration
*** 2014-01-07 16:02:58.157 4132 krsh.c
PING[ARC2]: Heartbeat failed to connect to standby 'mydb'. Error is 16057.
*** 2014-01-07 16:02:58.157 2747 krsi.c
krsi_dst_fail: dest:2 err:16057 force:0 blast:1
*** 2014-01-07 16:08:58.250
Redo shipping client performing standby login
*** 2014-01-07 16:08:58.386 4539 krsu.c
Logged on to standby successfully
Client logon and security negotiation successful!
This database DGID not in Data Guard configuration at 'mydb'
Error 16057 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'mydb'
ORA-16057: server not in Data Guard configuration
*** 2014-01-07 16:08:58.397 4132 krsh.c
PING[ARC2]: Heartbeat failed to connect to standby 'mydb'. Error is 16057.
*** 2014-01-07 16:08:58.397 2747 krsi.c
krsi_dst_fail: dest:2 err:16057 force:0 blast:1
Redo shipping client performing standby login
*** 2014-01-07 16:14:59.007
*** 2014-01-07 16:14:59.007 4539 krsu.c
Logged on to standby successfully
Client logon and security negotiation successful!
This database DGID not in Data Guard configuration at 'mydb'
Error 16057 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'mydb'
ORA-16057: server not in Data Guard configuration
*** 2014-01-07 16:14:59.018 4132 krsh.c
PING[ARC2]: Heartbeat failed to connect to standby 'mydb'. Error is 16057.
*** 2014-01-07 16:14:59.018 2747 krsi.c
krsi_dst_fail: dest:2 err:16057 force:0 blast:1
*** 2014-01-07 16:20:59.086
Redo shipping client performing standby login
*** 2014-01-07 16:20:59.246 4539 krsu.c
Logged on to standby successfully
Client logon and security negotiation successful!
This database DGID not in Data Guard configuration at 'mydb'
Error 16057 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'mydb'
ORA-16057: server not in Data Guard configuration
*** 2014-01-07 16:20:59.295 4132 krsh.c
PING[ARC2]: Heartbeat failed to connect to standby 'mydb'. Error is 16057.
*** 2014-01-07 16:20:59.296 2747 krsi.c
krsi_dst_fail: dest:2 err:16057 force:0 blast:1
*** 2014-01-07 16:26:59.377
Redo shipping client performing standby login
*** 2014-01-07 16:26:59.505 4539 krsu.c
Logged on to standby successfully
Client logon and security negotiation successful!
This database DGID not in Data Guard configuration at 'mydb'
Error 16057 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'mydb'
ORA-16057: server not in Data Guard configuration
*** 2014-01-07 16:26:59.514 4132 krsh.c
PING[ARC2]: Heartbeat failed to connect to standby 'mydb'. Error is 16057.
*** 2014-01-07 16:26:59.514 2747 krsi.c
krsi_dst_fail: dest:2 err:16057 force:0 blast:1
Redo shipping client performing standby login
*** 2014-01-07 16:32:59.873
*** 2014-01-07 16:32:59.873 4539 krsu.c
Logged on to standby successfully
Client logon and security negotiation successful!
This database DGID not in Data Guard configuration at 'mydb'
Error 16057 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'mydb'
ORA-16057: server not in Data Guard configuration
*** 2014-01-07 16:32:59.884 4132 krsh.c
PING[ARC2]: Heartbeat failed to connect to standby 'mydb'. Error is 16057.
*** 2014-01-07 16:32:59.884 2747 krsi.c
krsi_dst_fail: dest:2 err:16057 force:0 blast:1
Redo shipping client performing standby login
*** 2014-01-07 17:05:52.903
*** 2014-01-07 17:05:52.903 4539 krsu.c
Logged on to standby successfully
Client logon and security negotiation successful!
This database DGID not in Data Guard configuration at 'mydb'
Error 16057 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'mydb'
ORA-16057: server not in Data Guard configuration
*** 2014-01-07 17:05:52.908 4132 krsh.c
PING[ARC2]: Heartbeat failed to connect to standby 'mydb'. Error is 16057.
*** 2014-01-07 17:05:52.908 2747 krsi.c
krsi_dst_fail: dest:2 err:16057 force:0 blast:1
*** 2014-01-07 17:10:53.827
Redo shipping client performing standby login
*** 2014-01-07 17:10:54.214
*** 2014-01-07 17:10:54.214 4539 krsu.c
Logged on to standby successfully
Client logon and security negotiation successful!
This database DGID not in Data Guard configuration at 'mydb'
Error 16057 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'mydb'
ORA-16057: server not in Data Guard configuration
*** 2014-01-07 17:10:54.352 4132 krsh.c
PING[ARC2]: Heartbeat failed to connect to standby 'mydb'. Error is 16057.
*** 2014-01-07 17:10:54.352 2747 krsi.c
krsi_dst_fail: dest:2 err:16057 force:0 blast:1
*** 2014-01-07 17:16:54.439
Redo shipping client performing standby login
*** 2014-01-07 17:16:54.586 4539 krsu.c
Logged on to standby successfully
Client logon and security negotiation successful!
This database DGID not in Data Guard configuration at 'mydb'
Error 16057 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'mydb'
ORA-16057: server not in Data Guard configuration
*** 2014-01-07 17:16:54.599 4132 krsh.c
PING[ARC2]: Heartbeat failed to connect to standby 'mydb'. Error is 16057.
*** 2014-01-07 17:16:54.599 2747 krsi.c
krsi_dst_fail: dest:2 err:16057 force:0 blast:1
Redo shipping client performing standby login
*** 2014-01-07 17:22:54.863
*** 2014-01-07 17:22:54.863 4539 krsu.c
Logged on to standby successfully
Client logon and security negotiation successful!
This database DGID not in Data Guard configuration at 'mydb'
Error 16057 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'mydb'
ORA-16057: server not in Data Guard configuration
*** 2014-01-07 17:22:54.874 4132 krsh.c
PING[ARC2]: Heartbeat failed to connect to standby 'mydb'. Error is 16057.
*** 2014-01-07 17:22:54.874 2747 krsi.c
krsi_dst_fail: dest:2 err:16057 force:0 blast:1
*** 2014-01-07 17:28:54.943
Redo shipping client performing standby login
*** 2014-01-07 17:28:56.629
*** 2014-01-07 17:28:56.629 4539 krsu.c
Logged on to standby successfully
Client logon and security negotiation successful!
This database DGID not in Data Guard configuration at 'mydb'
Error 16057 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'mydb'
ORA-16057: server not in Data Guard configuration
*** 2014-01-07 17:28:56.668 4132 krsh.c
PING[ARC2]: Heartbeat failed to connect to standby 'mydb'. Error is 16057.
*** 2014-01-07 17:28:56.668 2747 krsi.c
krsi_dst_fail: dest:2 err:16057 force:0 blast:1
Redo shipping client performing standby login
*** 2014-01-07 17:34:57.155
*** 2014-01-07 17:34:57.155 4539 krsu.c
Logged on to standby successfully
Client logon and security negotiation successful!
*** 2014-01-07 17:34:57.344
This database DGID not in Data Guard configuration at 'mydb'
Error 16057 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'mydb'
ORA-16057: server not in Data Guard configuration
*** 2014-01-07 17:34:57.362 4132 krsh.c
PING[ARC2]: Heartbeat failed to connect to standby 'mydb'. Error is 16057.
*** 2014-01-07 17:34:57.362 2747 krsi.c
krsi_dst_fail: dest:2 err:16057 force:0 blast:1
*** 2014-01-07 17:39:58.619
Redo shipping client performing standby login
*** 2014-01-07 17:39:58.760 4539 krsu.c
Logged on to standby successfully
Client logon and security negotiation successful!
This database DGID not in Data Guard configuration at 'mydb'
Error 16057 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'mydb'
ORA-16057: server not in Data Guard configuration
*** 2014-01-07 17:39:58.785 4132 krsh.c
PING[ARC2]: Heartbeat failed to connect to standby 'mydb'. Error is 16057.
*** 2014-01-07 17:39:58.785 2747 krsi.c
krsi_dst_fail: dest:2 err:16057 force:0 blast:1
*** 2014-01-07 17:45:58.868
Redo shipping client performing standby login
*** 2014-01-07 17:45:59.198 4539 krsu.c
Logged on to standby successfully
Client logon and security negotiation successful!
This database DGID not in Data Guard configuration at 'mydb'
Error 16057 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'mydb'
ORA-16057: server not in Data Guard configuration
*** 2014-01-07 17:45:59.203 4132 krsh.c
PING[ARC2]: Heartbeat failed to connect to standby 'mydb'. Error is 16057.
*** 2014-01-07 17:45:59.203 2747 krsi.c
krsi_dst_fail: dest:2 err:16057 force:0 blast:1
Redo shipping client performing standby login
*** 2014-01-07 18:24:33.861
*** 2014-01-07 18:24:33.861 4539 krsu.c
Logged on to standby successfully
Client logon and security negotiation successful!
This database DGID not in Data Guard configuration at 'mydb'
Error 16057 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'mydb'
ORA-16057: server not in Data Guard configuration
*** 2014-01-07 18:24:34.152 4132 krsh.c
PING[ARC2]: Heartbeat failed to connect to standby 'mydb'. Error is 16057.
*** 2014-01-07 18:24:34.152 2747 krsi.c
krsi_dst_fail: dest:2 err:16057 force:0 blast:1
*** 2014-01-07 18:29:37.942
Redo shipping client performing standby login
*** 2014-01-07 18:29:38.394 4539 krsu.c
Logged on to standby successfully
Client logon and security negotiation successful!
This database DGID not in Data Guard configuration at 'mydb'
Error 16057 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'mydb'
ORA-16057: server not in Data Guard configuration
*** 2014-01-07 18:29:38.473 4132 krsh.c
PING[ARC2]: Heartbeat failed to connect to standby 'mydb'. Error is 16057.
*** 2014-01-07 18:29:38.473 2747 krsi.c
krsi_dst_fail: dest:2 err:16057 force:0 blast:1
*** 2014-01-07 18:35:38.554
Redo shipping client performing standby login
*** 2014-01-07 18:35:38.912 4539 krsu.c
Logged on to standby successfully
Client logon and security negotiation successful!
This database DGID not in Data Guard configuration at 'mydb'
Error 16057 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'mydb'
ORA-16057: server not in Data Guard configuration
*** 2014-01-07 18:35:38.938 4132 krsh.c
PING[ARC2]: Heartbeat failed to connect to standby 'mydb'. Error is 16057.
*** 2014-01-07 18:35:38.938 2747 krsi.c
krsi_dst_fail: dest:2 err:16057 force:0 blast:1
Redo shipping client performing standby login
*** 2014-01-07 18:40:39.370
*** 2014-01-07 18:40:39.370 4539 krsu.c
Logged on to standby successfully
Client logon and security negotiation successful!
This database DGID not in Data Guard configuration at 'mydb'
Error 16057 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'mydb'
ORA-16057: server not in Data Guard configuration
*** 2014-01-07 18:40:39.397 4132 krsh.c
PING[ARC2]: Heartbeat failed to connect to standby 'mydb'. Error is 16057.
*** 2014-01-07 18:40:39.397 2747 krsi.c
krsi_dst_fail: dest:2 err:16057 force:0 blast:1
*** 2014-01-07 18:46:39.475
Redo shipping client performing standby login
*** 2014-01-07 18:46:40.213
*** 2014-01-07 18:46:40.213 4539 krsu.c
Logged on to standby successfully
Client logon and security negotiation successful!
This database DGID not in Data Guard configuration at 'mydb'
Error 16057 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'mydb'
ORA-16057: server not in Data Guard configuration
*** 2014-01-07 18:46:40.717 4132 krsh.c
PING[ARC2]: Heartbeat failed to connect to standby 'mydb'. Error is 16057.
*** 2014-01-07 18:46:40.718 2747 krsi.c
krsi_dst_fail: dest:2 err:16057 force:0 blast:1
*** 2014-01-07 18:52:40.787
Redo shipping client performing standby login
*** 2014-01-07 18:52:41.059 4539 krsu.c
Logged on to standby successfully
Client logon and security negotiation successful!
This database DGID not in Data Guard configuration at 'mydb'
Error 16057 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'mydb'
ORA-16057: server not in Data Guard configuration
*** 2014-01-07 18:52:41.448 4132 krsh.c
PING[ARC2]: Heartbeat failed to connect to standby 'mydb'. Error is 16057.
*** 2014-01-07 18:52:41.448 2747 krsi.c
krsi_dst_fail: dest:2 err:16057 force:0 blast:1
Redo shipping client performing standby login
*** 2014-01-07 18:58:43.444
*** 2014-01-07 18:58:43.444 4539 krsu.c
Logged on to standby successfully
Client logon and security negotiation successful!
This database DGID not in Data Guard configuration at 'mydb'
Error 16057 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'mydb'
ORA-16057: server not in Data Guard configuration
*** 2014-01-07 18:58:43.500 4132 krsh.c
PING[ARC2]: Heartbeat failed to connect to standby 'mydb'. Error is 16057.
*** 2014-01-07 18:58:43.500 2747 krsi.c
krsi_dst_fail: dest:2 err:16057 force:0 blast:1
*** 2014-01-07 19:04:43.584
Redo shipping client performing standby login
*** 2014-01-07 19:04:44.210 4539 krsu.c
Logged on to standby successfully
Client logon and security negotiation successful!
This database DGID not in Data Guard configuration at 'mydb'
Error 16057 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'mydb'
ORA-16057: server not in Data Guard configuration
*** 2014-01-07 19:04:44.278 4132 krsh.c
PING[ARC2]: Heartbeat failed to connect to standby 'mydb'. Error is 16057.
*** 2014-01-07 19:04:44.278 2747 krsi.c
krsi_dst_fail: dest:2 err:16057 force:0 blast:1
Redo shipping client performing standby login
*** 2014-01-07 19:10:44.750
*** 2014-01-07 19:10:44.750 4539 krsu.c
Logged on to standby successfully
Client logon and security negotiation successful!
This database DGID not in Data Guard configuration at 'mydb'
Error 16057 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'mydb'
ORA-16057: server not in Data Guard configuration
*** 2014-01-07 19:10:44.807 4132 krsh.c
PING[ARC2]: Heartbeat failed to connect to standby 'mydb'. Error is 16057.
*** 2014-01-07 19:10:44.808 2747 krsi.c
krsi_dst_fail: dest:2 err:16057 force:0 blast:1
I would like to let you know I was working fine before 7-8 hours. Please let me know how should I resolve it.
Regards,
Michel
Maybe you are looking for
-
I am the victim of Identity Theft. The perpetrator has taken over as Roaming Administrator of my PC's. I once had 7 of them, but she has stolen/destroyed all but 2. She is taking online classes at college from Microsoft, and puts her class notes on o
-
Exchange Gain Loss Revaluation - Error Message No. F5429
Hi, While peforming the foreign currency revaluation of open items as at 31.12.2007, using the T Code FAGL_FC_VAL, the system calculates the Exchange Rate difference but the documents do not get posted. The Document display shows an error - Document
-
What type of airport/time capsule do i need to acces my music from every device
Hello, i need some good advice.... I have an old external drive with my music on, and now i want to buy a new system/drive from where i can acces it from my windows pc with itunes and my iphone 5s. I was looking for a NAS with itunes-server possibili
-
How to check usage picture in Albums vs Moments
Removing a picture in Moments could make Albums unmeaned incomplete. Better is to show the Albums at that moment.
-
Re: HDMI Resolution Chopping Border on my TV.
Hello, Just bought a new Mac Mini. I hooked it up to the mini-dvi to dvi cable. I then connected that dvi-to-hdmi and hooked it up to my 42" LG TV. I started configuring it for HDMI resolution. It chops the border of the screen off. I called Apple an