Data Guard NET_TIMEOUT
Hi,
I'm getting confused on the documentation relating to the NET_TIMEOUT paramater associated with an archive destination.
I want to run in MAXIMUM_AVAILABILITY mode, and if the network goes, drop to MAXIMUM_PERFORMANCE fast, without stalling the production database for an excessive number of seconds.
The DG Concepts and Administration's documentation, Chapter 12, for NET_TIMEOUT says I can set this down to 15 seconds. It also says I should set the SQLNET.EXPIRE_TIME on the standby to something lower, but as this value is in minutes, the only thing lower is 0, which means don't check for dead connections!
Have I misunderstood something, or does the documentation not reflect reality for small timeout values?
A bit later in the same section, it talks about the LGWR tring to automatically reconnect, and gives a guideline of 2 minutes of reconnect attempts for MAXIMUM_AVAILABILITY. is this occurring in the background, or does this mean that whatever I set NET_TIMEOUT to be, I could stall the production database for 2 minutes.
Any help appreciated.
Graham
But, in dgmgrl, it shows it is 180. See below...
DGMGRL> show database verbose 'MERCY';
Database
Name: MERCY
Role: PRIMARY
Enabled: YES
Intended State: ONLINE
Instance(s):
MERCY
Properties:
InitialConnectIdentifier = 'MERCY'
ObserverConnectIdentifier = ''
LogXptMode = 'SYNC'
Dependency = ''
DelayMins = '0'
Binding = 'OPTIONAL'
MaxFailure = '0'
MaxConnections = '1'
ReopenSecs = '300'
NetTimeout = '180'
LogShipping = 'ON'
PreferredApplyInstance = ''
ApplyInstanceTimeout = '0'
ApplyParallel = 'AUTO'
StandbyFileManagement = 'AUTO'
ArchiveLagTarget = '0'
LogArchiveMaxProcesses = '4'
LogArchiveMinSucceedDest = '1'
DbFileNameConvert = ''
LogFileNameConvert = ''
FastStartFailoverTarget = ''
StatusReport = '(monitor)'
InconsistentProperties = '(monitor)'
InconsistentLogXptProps = '(monitor)'
SendQEntries = '(monitor)'
LogXptStatus = '(monitor)'
RecvQEntries = '(monitor)'
HostName = 'csctestprd1'
SidName = 'MERCY'
LocalListenerAddress = '(ADDRESS=(PROTOCOL=tcp)(HOST=csctestprd1)(PORT=1521))'
StandbyArchiveLocation = 'dgsby_MERCY'
AlternateLocation = ''
LogArchiveTrace = '0'
LogArchiveFormat = '%t_%s_%r.arc'
LatestLog = '(monitor)'
TopWaitEvents = '(monitor)'
Current status for "MERCY":
Error: ORA-16778: redo transport error for one or more databases
Similar Messages
-
Data Guard: net_timeout parameter causing ORA-16163
Hello all,
I seem to be having a problem setting up our "TEST" data guard environment.
First, this is 10.2.0.4 on AIX 5.3.
My primary and standby databases are set up (with what I thought I had it set before when it was working).
Now, however, after rebuilding the whole environment again, I seem to be having a problem with the net_timeout parameter used in my "log_archive_dest_2" string.
When I start my databases as primary/standby, I am getting errors in my primary alert log as:
Mon Dec 14 10:48:41 2009
LGWR: Error 16163 creating archivelog file '(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=csctestprd2)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=MERCYSTB_XPT)(INSTANCE_NAME=MERCYSTB)(SERVER=dedicated)))'
Mon Dec 14 10:48:41 2009
Errors in file /oracle/product/10.2.0/admin/MERCY/bdump/mercy_lgwr_434430.trc:
ORA-16163: LGWR network server host attach error
LGWR: Failed to archive log 3 thread 1 sequence 771 (16163)
From what I've been able to tell, the ORA-16163 is being thrown by the setting of the log_archive_dest_2 "net_timeout" value.
Even though I have it set to 180, it keeps coming up with a setting of '1' when I show my log_archive_dest_2 parameter.
What could be causing this to reset itself from 180 to 1 automatically.
I checked the DG Broker settings, and they seem correct, however, after stopping and restarting the database (and dgmgr), I'm now getting an error when I show database...
Current status for "MERCY":
Error: ORA-16797: database is not using a server parameter fileBut, in dgmgrl, it shows it is 180. See below...
DGMGRL> show database verbose 'MERCY';
Database
Name: MERCY
Role: PRIMARY
Enabled: YES
Intended State: ONLINE
Instance(s):
MERCY
Properties:
InitialConnectIdentifier = 'MERCY'
ObserverConnectIdentifier = ''
LogXptMode = 'SYNC'
Dependency = ''
DelayMins = '0'
Binding = 'OPTIONAL'
MaxFailure = '0'
MaxConnections = '1'
ReopenSecs = '300'
NetTimeout = '180'
LogShipping = 'ON'
PreferredApplyInstance = ''
ApplyInstanceTimeout = '0'
ApplyParallel = 'AUTO'
StandbyFileManagement = 'AUTO'
ArchiveLagTarget = '0'
LogArchiveMaxProcesses = '4'
LogArchiveMinSucceedDest = '1'
DbFileNameConvert = ''
LogFileNameConvert = ''
FastStartFailoverTarget = ''
StatusReport = '(monitor)'
InconsistentProperties = '(monitor)'
InconsistentLogXptProps = '(monitor)'
SendQEntries = '(monitor)'
LogXptStatus = '(monitor)'
RecvQEntries = '(monitor)'
HostName = 'csctestprd1'
SidName = 'MERCY'
LocalListenerAddress = '(ADDRESS=(PROTOCOL=tcp)(HOST=csctestprd1)(PORT=1521))'
StandbyArchiveLocation = 'dgsby_MERCY'
AlternateLocation = ''
LogArchiveTrace = '0'
LogArchiveFormat = '%t_%s_%r.arc'
LatestLog = '(monitor)'
TopWaitEvents = '(monitor)'
Current status for "MERCY":
Error: ORA-16778: redo transport error for one or more databases -
ORA-16525: the Data Guard broker is not yet available while conneting ...
Hi,
I am trying to connect oracle database instance in dgmgrl prompt.
Following error message appear ...
DGMGRL>
DGMGRL> connect sys/<password>@<oracle_service_name>
Connected.
Error:
ORA-16525: the Data Guard broker is not yet available
ORA-06512: at "SYS.DBMS_DRS", line 124
ORA-06512: at line 1
DGMGRL> exit
$ e
We are using oracle enterprise manager ...
SSMDG broker is the way to go. There are only minor points you can't control - like when you have standby redo logs and no redo application delay, dg broker will always start real-time apply.
Also, DG broker is the only way if you want fast-start failover (10gR2 feature).
What is the latency of your nework, especially under load? Add this latency to each commit - will the commit time be acceptable? If not, you cannot use sync.
What version do you use? In 10gR1, there are issues with async - there is only about 50MB buffer, and if you get such backlog, even with async commit will wait for standby. (In 10gR2 this is solved, async will read from disk redo logs.)
NET_TIMEOUT - set it low for sync (so commits won't hang long), higher for async. Default is 180 seconds, Oracle recommends minimum value to 10 seconds. I would start with 10 sec for sync, 180 for sync. The main question is, how reliable your network is, and how long brownouts you want to survive without affecting data protection (with the expense of performance).
Regarding the proper setting of all bells and whistles of archive_log_dest_n - I had best experience with leaving it to dg broker. Just set LogXptMode property to sync/async/arch, and let dg broker set everything else (service, valid_for, affirm, retries...).
The authoritative source: http://www.oracle.com/technology/deploy/availability/htdocs/maa.htm#Publications
If you are on 10.2.0.1 - 10.2.0.3, please see metalink bug 5578157, 5587231 - if sqlnet.outbound_connection_timeout is not set, the lgwr can hang even if net_timeout is set. (Yes, real-world experience:-) -
Data Guard Transport and Real Time Apply Configuration
Hello,
I'm configuring a Data Guard configuration using Oracle 12.1.0.2 and I have observed that in a máximum perfomance configuration, that is the default.
The system upgrade to a SYNC configuration.
DGMGRL> show configuration
Configuration - DRSolution
Protection Mode: MaxPerformance
Members:
orcl - Primary database
STBY - Physical standby database
Fast-Start Failover: DISABLED
Configuration Status:
SUCCESS (status updated 53 seconds ago)
SQL> show parameters log_archive_Dest_2
NAME TYPE VALUE
log_archive_dest_2 string service="stby", ASYNC NOAFFIRM
delay=0 optional compression=
disable max_failure=0 max_conn
ections=1 reopen=300 db_unique
_name="STBY" net_timeout=30, v
alid_for=(online_logfile,all_r
oles)
However, if I insert 1 row in a test table at primary database and commit, immediately I see the change in the standby database.
If this behavior new in this versión?
How can I revert to the classic max performance configuration, where only send the archive when it is full.
Thanks
Arturo>How can I revert to the classic max performance configuration, where only send the archive when it is full.
That is ARCH shipping. The default in 11.2 and above LGWR shipping. So LGWR ships the redo immediately. The only thing with ASYNC is that it doesn't wait for the Standby to acknowledge before it returns a COMMIT to the user. In a low-load environment, if the standby can apply the redo fast enough, ASYNC is virtually the same as SYNC. That is MaximumPerformance becomes the same as MaximumAvailability. Only when the redo load is higher than the available bandwidth or the speed at which the Standby can apply it , will you see a lag in the Standby. (To force an explicit lag, there is a separate DELAY parameter).
ARCH shipping is deprecated. -
Hi,
I have Data Guard implemented on Oracle 10gR2 10.2.0.1 database. OS-Windows 2003 Server. I am facing the following error
ORA-16146: standby destination control file enqueue unavailable
I get this alert in my alert log. After sometime it gets resovled on its own. When I check logs status...all logs are applied on standby and no gaps are found. What may be the possible cause for it? And solution ?Thank you for those kind words. :^) We try hard. WHat you are hearing is not really different. I am just providing a few more details on Data Guard's redo transport that further clarifies what you have heard, at least I hope so :^)
All I was trying to do is clarify what process is actually shipping redo and when. The syntax for the LOG_ARCHIVE_DEST_n parameter up to 10g is ARCH, LGWR ASYNC or LGWR SYNC. The syntax says LGWR but in fact underneath the LGWR process starts up an LNS process for any ASYNC or SYNC standby destination and it is that process that actually has the network connection to the standby. This way if there is a network hang it is the LNS process that gets stalled and the LGWR process (when in SYNC mode) will wait for NET_TIMEOUT seconds before deciding that the standby is unreachable and continuing to do its work ignoring that standby destination until it is reachable again (something discovered by the ARCH ping process).
If you say ARCH for a standby then one of your ARCn processes will ship the redo when it is in the form of a complete archive log file. Hence nothing gets shipped to an ARCH standby until a log switch happens at the Primary.
The reason everybody says that LGWR ASYNC or LGWR SYNC is better is that the redo is shipped at the time it is written to the online redo log file hence your potential data loss is much much much less than with ARCH. And I agree with that sentiment.
Please note that from 11g on the syntax is ASYNC or SYNC. The LGWR keyword is no longer necessary (although it will still be parsed) and ARCH has been deprecated as ASYNC is so much better. ARCH will work for backwards compatibility but will go away at some point.
Does this clear things up for you?
Thanks.
Larry -
HI There
I have recently configure Data guard with Database 10g (10.2.0.4-64 bits) on Windows 2007 server.
My Data Gurad Configuration show Success status with 2 databases on same (or local) location.
My questions are
1-When I query SHOW PARAMETER LOG ARCH
DG_CONFIG(PRMDB)
ONLY 1 (PRIMARY DATABASE IS DISPLAYED ONLY NOT 2 DTATABASES
e.g. DG_CONFIG(PRMDB, STLDB)
2- How to check the log applied interval or time (either transaction by transaction, timing etc)
Kind Regards
Thunder2777THANKS FOR REPLY
BOTH TNSNAMES.ORA AND LISTENER.ORA IN SAME DIRECTORY
C:\oracle\product\10.2.0\db_1\NETWORK\ADMIN
TNSNAMES.ORA
# tnsnames.ora Network Configuration File: C:\oracle\product\10.2.0\db_1\network\admin\tnsnames.ora
# Generated by Oracle configuration tools.
PRMDB =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = CV-SERVER)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = PRMDB)
STLDB =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = CV-SERVER)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = STLDB)
LISTENER.ORA
# listener.ora Network Configuration File: C:\oracle\product\10.2.0\db_1\network\admin\listener.ora
# Generated by Oracle configuration tools.
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(SID_NAME = PLSExtProc)
(ORACLE_HOME = C:\oracle\product\10.2.0\db_1)
(PROGRAM = extproc)
(SID_DESC =
(SID_NAME = STLDB)
(ORACLE_HOME = C:\oracle\product\10.2.0\db_1)
# PRIMARY DATABASE SPFILE
SPFILEPRMDB.ORA
prmdb.__db_cache_size=922746880
prmdb.__java_pool_size=16777216
prmdb.__large_pool_size=16777216
prmdb.__shared_pool_size=285212672
prmdb.__streams_pool_size=0
*.archive_lag_target=0
*.audit_file_dest='C:\oracle\product\10.2.0\admin\PRMDB\adump'
*.background_dump_dest='C:\oracle\product\10.2.0\admin\PRMDB\bdump'
*.compatible='10.2.0.3.0'
*.control_files='C:\oracle\product\10.2.0\oradata\PRMDB\control01.ctl','C:\oracle\product\10.2.0\oradata\PRMDB\control02.ctl','C:\oracle\product\10.2.0\oradata\PRMDB\control03.ctl'
*.core_dump_dest='C:\oracle\product\10.2.0\admin\PRMDB\cdump'
*.db_block_size=8192
*.db_domain=''
*.db_file_multiblock_read_count=16
*.db_name='PRMDB'
*.db_recovery_file_dest='C:\oracle\product\10.2.0\flash_recovery_area'
*.db_recovery_file_dest_size=2147483648
*.dg_broker_start=TRUE
*.dispatchers='(PROTOCOL=TCP) (SERVICE=PRMDBXDB)'
*.job_queue_processes=10
*.log_archive_config='dg_config=(stldb)'
*.log_archive_dest_1='service="(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=CV-SERVER)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=stldb_XPT)(INSTANCE_NAME=stldb)(SERVER=dedicated)))"',' LGWR ASYNC NOAFFIRM delay=0 OPTIONAL max_failure=0 max_connections=1 reopen=300 db_unique_name="stldb" register net_timeout=180 valid_for=(online_logfile,primary_role)'
*.log_archive_dest_state_1='ENABLE'
prmdb.log_archive_format='ARC%S_%R.%T'
*.log_archive_max_processes=2
*.log_archive_min_succeed_dest=1
prmdb.log_archive_trace=0
*.open_cursors=300
*.pga_aggregate_target=417333248
*.processes=150
*.remote_login_passwordfile='EXCLUSIVE'
*.sga_target=1253048320
prmdb.standby_archive_dest=''
*.standby_file_management='MANUAL'
*.undo_management='AUTO'
*.undo_tablespace='UNDOTBS1'
*.user_dump_dest='C:\oracle\product\10.2.0\admin\PRMDB\udump'
# STANDBY DATABASE INITSTLDB
INITSTLDB.ORA
STLDB.__db_cache_size=922746880
STLDB.__java_pool_size=16777216
STLDB.__large_pool_size=16777216
STLDB.__shared_pool_size=285212672
STLDB.__streams_pool_size=0
*.audit_file_dest='C:\oracle\product\10.2.0\admin\STLDB\adump'
*.background_dump_dest='C:\oracle\product\10.2.0\admin\STLDB\bdump'
*.compatible='10.2.0.3.0'
*.control_files='D:\ORACLE\ORADATA\STLDB\CONTROLFILE\control01.ctl'
*.core_dump_dest='C:\oracle\product\10.2.0\admin\STLDB\cdump'
*.db_block_size=8192
*.db_domain=''
*.db_file_multiblock_read_count=16
*.db_name='PRMDB'
*.db_unique_name='STLDB'
*.db_recovery_file_dest='D:\oracle\FRA'
*.db_recovery_file_dest_size=2147483648
*.dispatchers='(PROTOCOL=TCP) (SERVICE=STLDBXDB)'
*.LOG_ARCHIVE_DEST_1='LOCATION=USE_DB_RECOVERY_FILE_DEST
VALID_FOR=(ALL_LOGFILES,ALL_ROLES)
DB_UNIQUE_NAME=STLDB'
*.LOG_ARCHIVE_DEST_STATE_1='ENABLE'
*.job_queue_processes=10
*.open_cursors=300
*.pga_aggregate_target=417333248
*.processes=150
*.remote_login_passwordfile='EXCLUSIVE'
*.sga_target=1253048320
*.undo_management='MANUAL'
*.undo_tablespace='UNDOTBS1'
*.user_dump_dest='C:\oracle\product\10.2.0\admin\STLDB\udump'
THANKS -
Data Guard Missing Redo Archive Logs
Hi All Gurus
I have setup data guard on windows 2008 server sp2 with oracle 10.2.0.4.0 (Both OS & Oracle DB are 64 bits).
The Network Admin have shutdown Backup server. Now when I checked the Archive status as follows
1. select * from v$archive_gap; It shows a gap in archives e.g. 891 - 920.
2. SELECT THREAD#, SEQUENCE#, APPLIED FROM V$ARCHIVED_LOG; e.g. 891-920 Not Applied.
Now I issue following command
1. SELECT RECOVERY_MODE FROM V$ARCHIVE_DEST_STATUS; e.g. MANAGED REAL TIME APPLY
2. DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;
or ALTER DATABASE RECOVER managed standby database disconnect from session ;
e.g. incompatible Media Recovery in Progress
3. Alert Log says Adjust CONTROL_FILE_RECORD_KEEP_TIME to sufficient limits.
I have also adjusted CONTROL_FILE_RECORD_KEEP_TIME to 90 days as follows
4. show parameter control_file e.g. CONTROL_FILE_RECORD_KEEP_TIME=90
5. I have checked firewall and tnsping for both Primary and Standby Server e.g. tnsping CVMIS (Primary), CVMISBK (Standby)
Both are OK. TNSPING is showing 10-30msec delay.
6. I have checked the web for gap Removal, Mostly are using RMAN method to Backup and then Restore to Standby DB.
Is there any other way to fill this gap without using RMAN? I mean DG automatically fill it by using some commands
are settings?
Kind Regards
Thunder2777Hi CKPT
Thanks for the scripts which I executed today on 24 Mon 2013. Here are the Results.
Standby Database Script Output:
NAME DISPLAY_VALUE
db_file_name_convert
db_name UMIS
db_unique_name UMISBK
dg_broker_config_file1 C:\ORACLE\PRODUCT\10.2.0\DB_1\DATABASE\DR1UMISBK.DAT
dg_broker_config_file2 C:\ORACLE\PRODUCT\10.2.0\DB_1\DATABASE\DR2UMISBK.DAT
dg_broker_start TRUE
fal_client (DESCRIPTION=(ADDRESS_LIST=(AD
DRESS=(PROTOCOL=tcp)(HOST=WIN-
7VSLKL4CGU2)(PORT=1521)))(CONN
ECT_DATA=(SERVICE_NAME=umisbk_
XPT)(INSTANCE_NAME=umisbk)(SER
VER=dedicated)))
fal_server (DESCRIPTION=(ADDRESS_LIST=(AD
DRESS=(PROTOCOL=tcp)(HOST=CV-A
JKDB)(PORT=1521)))(CONNECT_DAT
A=(SERVICE_NAME=umis_XPT)(SERV
ER=dedicated)))
local_listener
log_archive_config DG_CONFIG=(UMIS,UMISBK)
log_archive_dest_2 SERVICE=UMIS LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=UMIS
log_archive_dest_state_2 ENABLE
log_archive_max_processes 10
log_file_name_convert E:\oracle\product\10.2.0\flash_recovery_area\UMIS\, D:\ORACLE\FRA\UMISBK
remote_login_passwordfile EXCLUSIVE
standby_archive_dest D:\ORACLE\FRA\UMISBK\ARCHIVELOG\
standby_file_management AUTO
NAME DB_UNIQUE_NAME PROTECTION_MODE DATABASE_R OPEN_MODE
UMIS UMISBK MAXIMUM PERFORMANCE PHYSICAL STANDBY MOUNTED
THREAD# MAX(SEQUENCE#)
1 890
PROCESS STATUS THREAD# SEQUENCE#
ARCH CONNECTED 0 0
ARCH CONNECTED 0 0
ARCH CONNECTED 0 0
ARCH CONNECTED 0 0
ARCH CLOSING 1 1062
ARCH CONNECTED 0 0
ARCH CONNECTED 0 0
ARCH CONNECTED 0 0
ARCH CONNECTED 0 0
ARCH CONNECTED 0 0
MRP0 WAIT_FOR_GAP 1 891
RFS IDLE 1 1063
RFS IDLE 0 0
NAME VALUE UNIT TIME_COMPUTED
apply finish time day(2) to second(1) interval
apply lag day(2) to second(0) interval
estimated startup time 22 second
standby has been open N
transport lag day(2) to second(0) interval
THREAD# LOW_SEQUENCE# HIGH_SEQUENCE#
1 891 948
NAME Size MB Used MB
D:\ORACLE\FRA 2048 0
STANDBY Alert Log:
Mon Jun 24 10:19:55 2013
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
RFS[2]: Assigned to RFS process 1868
RFS[2]: Identified database type as 'physical standby'
RFS[2]: Successfully opened standby log 5: 'D:\ORACLE\ORADATA\UMISBK\SLOG02.LOG'
Mon Jun 24 10:22:09 2013
Adjusting the default value of parameter parallel_max_servers
from 160 to 135 due to the value of parameter processes (150)
Mon Jun 24 10:22:09 2013
Starting ORACLE instance (normal)
Mon Jun 24 10:22:09 2013
alter database mount standby database
ORA-1154 signalled during: alter database mount standby database...
Mon Jun 24 10:22:09 2013
alter database recover managed standby database using current logfile disconnect from session
Mon Jun 24 10:22:40 2013
ORA-1153 signalled during: alter database recover managed standby database using current logfile disconnect from session...
Adjusting the default value of parameter parallel_max_servers
from 160 to 135 due to the value of parameter processes (150)
Mon Jun 24 10:24:40 2013
Starting ORACLE instance (normal)
Mon Jun 24 10:24:40 2013
alter database mount standby database
ORA-1154 signalled during: alter database mount standby database...
Mon Jun 24 10:24:40 2013
alter database recover managed standby database using current logfile disconnect from session
Mon Jun 24 10:25:11 2013
ORA-1153 signalled during: alter database recover managed standby database using current logfile disconnect from session...
Mon Jun 24 10:26:46 2013
Adjusting the default value of parameter parallel_max_servers
from 160 to 135 due to the value of parameter processes (150)
Mon Jun 24 10:26:46 2013
Starting ORACLE instance (normal)
Mon Jun 24 10:28:04 2013
alter database mount standby database
Mon Jun 24 10:28:04 2013
ORA-1154 signalled during: alter database mount standby database...
PRIMARY Database Script Output:
NAME DISPLAY_VALUE
db_file_name_convert UMIS, UMISBK
db_name UMIS
db_unique_name UMIS
dg_broker_config_file1 E:\ORACLE\PRODUCT\10.2.0\DB_1\DATABASE\DR1UMIS.DAT
dg_broker_config_file2 E:\ORACLE\PRODUCT\10.2.0\DB_1\DATABASE\DR2UMIS.DAT
dg_broker_start TRUE
fal_client UMIS
fal_server UMISBK
local_listener
log_archive_config DG_CONFIG=(UMIS,UMISBK)
log_archive_dest_2 service="(DESCRIPTION=(ADDRESS
_LIST=(ADDRESS=(PROTOCOL=tcp)(
HOST=WIN-7VSLKL4CGU2)(PORT=152
1)))(CONNECT_DATA=(SERVICE_NAM
E=umisbk_XPT)(INSTANCE_NAME=um
isbk)(SERVER=dedicated)))",
LGWR ASYNC NOAFFIRM delay=0 O
PTIONAL max_failure=0 max_conn
ections=1 reopen=300 db_uniq
ue_name="umisbk" register net_
timeout=180 valid_for=(online
_logfile,primary_role)
log_archive_dest_state_2 ENABLE
log_archive_max_processes 2
log_file_name_convert E:\oracle\product\10.2.0\flash_recOvery_area\UMIS ARCHIVELOG\, D:\ORACLE\FRA\UMISBK\ARCHIVELOG\
remote_login_passwordfile EXCLUSIVE
standby_archive_dest
standby_file_management AUTO
NAME DB_UNIQUE_NAME PROTECTION_MODE DATABASE_R OPEN_MODE SWITCHOVER_STATUS
UMIS UMIS MAXIMUM PERFORMANCE PRIMARY READ WRITE SESSIONS ACTIVE
THREAD# MAX(SEQUENCE#)
1 1062
Thread Last Sequence Received Last Sequence Applied Difference
1 1062 1062 0
1 1062 1062 0
SEVERITY ERROR_CODE timestamp MESSAGE
Error 12514 24-JUN-2013 10:08:02 LGWR: Error 12514 creating archivelog file '(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=WIN-7VSLKL4CGU2)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=umisbk_XPT)(INSTANCE_NAME=umisbk)(SERVER=dedicated)))
Error 12514 24-JUN-2013 10:08:04 LGWR: Error 12514 creating archivelog file '(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=WIN-7VSLKL4CGU2)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=umisbk_XPT)(INSTANCE_NAME=umisbk)(SERVER=dedicated)))
Error 12514 24-JUN-2013 10:08:07 FAL[server, ARC1]: Error 12514 creating remote archivelog file '(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=WIN-7VSLKL4CGU2)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=umisbk_XPT)(INSTANCE_NAME=umisbk)(SERVER=dedicated)))'
Error 12514 24-JUN-2013 10:08:31 LGWR: Error 12514 creating archivelog file '(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=WIN-7VSLKL4CGU2)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=umisbk_XPT)(INSTANCE_NAME=umisbk)(SERVER=dedicated)))
Error 12514 24-JUN-2013 10:08:59 FAL[server, ARC1]: Error 12514 creating remote archivelog file '(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=WIN-7VSLKL4CGU2)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=umisbk_XPT)(INSTANCE_NAME=umisbk)(SERVER=dedicated)))'
Error 12514 24-JUN-2013 10:14:57 PING[ARC1]: Heartbeat failed to connect to standby '(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=WIN-7VSLKL4CGU2)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=umisbk_XPT)(INSTANCE_NAME=umisbk)(SERVER=dedicated)))'. Error is 12514.
ID STATUS DB_MODE TYPE RECOVERY_MODE PROTECTION_MODE SRLs ACTIVE ARCHIVED_SEQ#
1 VALID OPEN ARCH IDLE MAXIMUM PERFORMANCE 0 0 1062
2 VALID UNKNOWN LGWR UNKNOWN MAXIMUM PERFORMANCE 4 3 1054
NAME Size MB Used MB
E:\oracle\product\10.2.0\flash_recovery_area 2048 0
Primary Alert Log:
System parameters with non-default values:
processes = 150
__shared_pool_size = 335544320
__large_pool_size = 16777216
__java_pool_size = 33554432
__streams_pool_size = 0
sga_target = 1258291200
control_files = E:\ORACLE\PRODUCT\10.2.0\ORADATA\UMIS\CONTROL01.CTL, E:\ORACLE\PRODUCT\10.2.0\ORADATA\UMIS\CONTROL02.CTL, E:\ORACLE\PRODUCT\10.2.0\ORADATA\UMIS\CONTROL03.CTL
db_file_name_convert = UMIS, UMISBK
log_file_name_convert = E:\oracle\product\10.2.0\flash_recOvery_area\UMIS ARCHIVELOG\, D:\ORACLE\FRA\UMISBK\ARCHIVELOG\
control_file_record_keep_time= 90
db_block_size = 8192
__db_cache_size = 855638016
compatible = 10.2.0.3.0
log_archive_config = DG_CONFIG=(UMIS,UMISBK)
log_archive_dest_1 = location="E:\oracle\product\10.2.0\flash_recovery_area\UMIS\ARCHIVELOG", valid_for=(ONLINE_LOGFILE,ALL_ROLES)
log_archive_dest_2 = service="(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=WIN-7VSLKL4CGU2)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=umisbk_XPT)(INSTANCE_NAME=umisbk)(SERVER=dedicated)))", LGWR ASYNC NOAFFIRM delay=0 OPTIONAL max_failure=0 max_connections=1 reopen=300 db_unique_name="umisbk" register net_timeout=180 valid_for=(online_logfile,primary_role)
log_archive_dest_state_1 = ENABLE
log_archive_dest_state_2 = ENABLE
log_archive_max_processes= 2
log_archive_min_succeed_dest= 1
standby_archive_dest =
log_archive_trace = 0
log_archive_format = ARC_s%S_r%R_t%T.arc
fal_client = UMIS
fal_server = UMISBK
archive_lag_target = 0
db_file_multiblock_read_count= 16
db_recovery_file_dest = E:\oracle\product\10.2.0\flash_recovery_area
db_recovery_file_dest_size= 2147483648
standby_file_management = AUTO
undo_management = AUTO
undo_tablespace = UNDOTBS1
remote_login_passwordfile= EXCLUSIVE
db_domain =
dispatchers = (PROTOCOL=TCP) (SERVICE=UMISXDB)
job_queue_processes = 10
audit_file_dest = E:\ORACLE\PRODUCT\10.2.0\ADMIN\UMIS\ADUMP
background_dump_dest = E:\ORACLE\PRODUCT\10.2.0\ADMIN\UMIS\BDUMP
user_dump_dest = E:\ORACLE\PRODUCT\10.2.0\ADMIN\UMIS\UDUMP
core_dump_dest = E:\ORACLE\PRODUCT\10.2.0\ADMIN\UMIS\CDUMP
db_name = UMIS
open_cursors = 300
pga_aggregate_target = 417333248
dg_broker_start = TRUE
PSP0 started with pid=3, OS id=2824
MMAN started with pid=4, OS id=2820
DBW0 started with pid=5, OS id=2396
LGWR started with pid=6, OS id=2676
CKPT started with pid=7, OS id=2692
SMON started with pid=8, OS id=2096
RECO started with pid=9, OS id=2924
CJQ0 started with pid=10, OS id=2832
MMON started with pid=11, OS id=3052
Mon Jun 24 10:07:34 2013
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
Mon Jun 24 10:07:34 2013
starting up 1 shared server(s) ...
MMNL started with pid=12, OS id=2700
DMON started with pid=15, OS id=2908
PMON started with pid=2, OS id=2812
Mon Jun 24 10:07:35 2013
alter database mount exclusive
Mon Jun 24 10:07:40 2013
Setting recovery target incarnation to 2
Mon Jun 24 10:07:42 2013
Successful mount of redo thread 1, with mount id 316954407
Mon Jun 24 10:07:42 2013
Database mounted in Exclusive Mode
Completed: alter database mount exclusive
Mon Jun 24 10:07:42 2013
alter database open
Mon Jun 24 10:07:47 2013
Starting Data Guard Broker (DMON)
NSV1 started with pid=16, OS id=3552
Mon Jun 24 10:07:50 2013
Beginning crash recovery of 1 threads
parallel recovery started with 7 processes
INSV started with pid=24, OS id=3628
Mon Jun 24 10:07:52 2013
Started redo scan
Mon Jun 24 10:07:53 2013
Completed redo scan
144 redo blocks read, 60 data blocks need recovery
Mon Jun 24 10:07:53 2013
Started redo application at
Thread 1: logseq 1059, block 8380
Mon Jun 24 10:07:53 2013
Recovery of Online Redo Log: Thread 1 Group 3 Seq 1059 Reading mem 0
Mem# 0: E:\ORACLE\PRODUCT\10.2.0\ORADATA\UMIS\REDO03.LOG
Mon Jun 24 10:07:53 2013
Completed redo application
Mon Jun 24 10:07:53 2013
Completed crash recovery at
Thread 1: logseq 1059, block 8524, scn 26461769
60 data blocks read, 60 data blocks written, 144 redo blocks read
Mon Jun 24 10:07:57 2013
LGWR: STARTING ARCH PROCESSES
ARC0 started with pid=25, OS id=3804
ARC1 started with pid=26, OS id=3808
Mon Jun 24 10:07:57 2013
ARC0: Archival started
ARC1: Archival started
LGWR: STARTING ARCH PROCESSES COMPLETE
RSM0 started with pid=27, OS id=3812
LNS1 started with pid=28, OS id=3824
Mon Jun 24 10:08:01 2013
Thread 1 advanced to log sequence 1060 (thread open)
Thread 1 opened at log sequence 1060
Current log# 1 seq# 1060 mem# 0: E:\ORACLE\PRODUCT\10.2.0\ORADATA\UMIS\REDO01.LOG
Successful open of redo thread 1
Mon Jun 24 10:08:02 2013
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
Mon Jun 24 10:08:02 2013
ARC1: STARTING ARCH PROCESSES
Mon Jun 24 10:08:02 2013
ARC0: Becoming the 'no FAL' ARCH
ARC0: Becoming the 'no SRL' ARCH
Mon Jun 24 10:08:02 2013
ARC2: Archival started
Mon Jun 24 10:08:02 2013
ARC1: STARTING ARCH PROCESSES COMPLETE
ARC2 started with pid=29, OS id=3544
ARC1: Becoming the heartbeat ARCH
Mon Jun 24 10:08:02 2013
LGWR: Setting 'active' archival for destination LOG_ARCHIVE_DEST_2
Error 12514 received logging on to the standby
LGWR: Error 12514 creating archivelog file '(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=WIN-7VSLKL4CGU2)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=umisbk_XPT)(INSTANCE_NAME=umisbk)(SERVER=dedicated)))'
Mon Jun 24 10:08:02 2013
Errors in file e:\oracle\product\10.2.0\admin\umis\bdump\umis_lns1_3824.trc:
ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
Mon Jun 24 10:08:02 2013
SMON: enabling cache recovery
Mon Jun 24 10:08:03 2013
ALTER SYSTEM SET log_archive_dest_2='service="(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=WIN-7VSLKL4CGU2)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=umisbk_XPT)(INSTANCE_NAME=umisbk)(SERVER=dedicated)))"',' LGWR ASYNC NOAFFIRM delay=0 OPTIONAL max_failure=0 max_connections=1 reopen=300 db_unique_name="umisbk" register net_timeout=180 valid_for=(online_logfile,primary_role)' SCOPE=BOTH;
Mon Jun 24 10:08:03 2013
LNS: Failed to archive log 1 thread 1 sequence 1060 (12514)
Mon Jun 24 10:08:03 2013
ALTER SYSTEM SET log_archive_dest_state_2='ENABLE' SCOPE=BOTH;
Mon Jun 24 10:08:03 2013
ALTER DATABASE OPEN
Mon Jun 24 10:08:03 2013
ORA-1531 signalled during: ALTER DATABASE OPEN...
Mon Jun 24 10:08:04 2013
Error 12514 received logging on to the standby
LGWR: Error 12514 creating archivelog file '(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=WIN-7VSLKL4CGU2)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=umisbk_XPT)(INSTANCE_NAME=umisbk)(SERVER=dedicated)))'
Mon Jun 24 10:08:04 2013
Errors in file e:\oracle\product\10.2.0\admin\umis\bdump\umis_lns1_3824.trc:
ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
LNS: Failed to archive log 1 thread 1 sequence 1060 (12514)
Mon Jun 24 10:08:04 2013
Successfully onlined Undo Tablespace 1.
Mon Jun 24 10:08:04 2013
SMON: enabling tx recovery
Mon Jun 24 10:08:05 2013
Database Characterset is WE8MSWIN1252
Opening with internal Resource Manager plan
where NUMA PG = 1, CPUs = 8
Mon Jun 24 10:08:06 2013
Error 12514 received logging on to the standby
Mon Jun 24 10:08:06 2013
Errors in file e:\oracle\product\10.2.0\admin\umis\bdump\umis_arc1_3808.trc:
ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
FAL[server, ARC1]: Error 12514 creating remote archivelog file '(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=WIN-7VSLKL4CGU2)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=umisbk_XPT)(INSTANCE_NAME=umisbk)(SERVER=dedicated)))'
FAL[server, ARC1]: FAL archive failed, see trace file.
Mon Jun 24 10:08:07 2013
replication_dependency_tracking turned off (no async multimaster replication found)
Mon Jun 24 10:08:07 2013
Errors in file e:\oracle\product\10.2.0\admin\umis\bdump\umis_arc1_3808.trc:
ORA-16055: FAL request rejected
Mon Jun 24 10:08:07 2013
ARCH: FAL archive failed. Archiver continuing
Mon Jun 24 10:08:08 2013
Starting background process QMNC
QMNC started with pid=28, OS id=3984
Mon Jun 24 10:08:15 2013
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.
Mon Jun 24 10:08:15 2013
Completed: alter database open
Mon Jun 24 10:08:19 2013
ALTER SYSTEM SET standby_archive_dest='' SCOPE=BOTH SID='umis';
Mon Jun 24 10:08:19 2013
ALTER SYSTEM SET log_archive_trace=0 SCOPE=BOTH SID='umis';
Mon Jun 24 10:08:19 2013
ALTER SYSTEM SET log_archive_format='ARC_s%S_r%R_t%T.arc' SCOPE=SPFILE SID='umis';
Mon Jun 24 10:08:20 2013
ALTER SYSTEM SET standby_file_management='AUTO' SCOPE=BOTH SID='*';
Mon Jun 24 10:08:20 2013
ALTER SYSTEM SET archive_lag_target=0 SCOPE=BOTH SID='*';
Mon Jun 24 10:08:20 2013
ALTER SYSTEM SET log_archive_max_processes=2 SCOPE=BOTH SID='*';
Mon Jun 24 10:08:21 2013
ALTER SYSTEM SET log_archive_min_succeed_dest=1 SCOPE=BOTH SID='*';
Mon Jun 24 10:08:21 2013
ALTER SYSTEM SET db_file_name_convert='UMIS','UMISBK' SCOPE=SPFILE;
Mon Jun 24 10:08:21 2013
ALTER SYSTEM SET log_file_name_convert='E:\oracle\product\10.2.0\flash_recOvery_area\UMIS ARCHIVELOG\','D:\ORACLE\FRA\UMISBK\ARCHIVELOG\' SCOPE=SPFILE;
Mon Jun 24 10:08:21 2013
ALTER SYSTEM ARCHIVE LOG
Mon Jun 24 10:08:21 2013
Thread 1 cannot allocate new log, sequence 1061
Private strand flush not complete
Current log# 1 seq# 1060 mem# 0: E:\ORACLE\PRODUCT\10.2.0\ORADATA\UMIS\REDO01.LOG
Mon Jun 24 10:08:22 2013
Shutting down archive processes
Mon Jun 24 10:08:22 2013
Thread 1 advanced to log sequence 1061 (LGWR switch)
Mon Jun 24 10:08:22 2013
Current log# 2 seq# 1061 mem# 0: E:\ORACLE\PRODUCT\10.2.0\ORADATA\UMIS\REDO02.LOG
Mon Jun 24 10:08:27 2013
ARCH shutting down
ARC2: Archival stopped
Mon Jun 24 10:08:27 2013
ALTER SYSTEM SET log_archive_dest_2='service="(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=WIN-7VSLKL4CGU2)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=umisbk_XPT)(INSTANCE_NAME=umisbk)(SERVER=dedicated)))"',' LGWR ASYNC NOAFFIRM delay=0 OPTIONAL max_failure=0 max_connections=1 reopen=300 db_unique_name="umisbk" register net_timeout=180 valid_for=(online_logfile,primary_role)' SCOPE=BOTH;
Mon Jun 24 10:08:27 2013
ALTER SYSTEM SET log_archive_dest_state_2='ENABLE' SCOPE=BOTH;
Mon Jun 24 10:08:27 2013
ALTER SYSTEM ARCHIVE LOG
Mon Jun 24 10:08:27 2013
Thread 1 cannot allocate new log, sequence 1062
Private strand flush not complete
Current log# 2 seq# 1061 mem# 0: E:\ORACLE\PRODUCT\10.2.0\ORADATA\UMIS\REDO02.LOG
LNS1 started with pid=29, OS id=4204
Mon Jun 24 10:08:31 2013
Thread 1 advanced to log sequence 1062 (LGWR switch)
Current log# 3 seq# 1062 mem# 0: E:\ORACLE\PRODUCT\10.2.0\ORADATA\UMIS\REDO03.LOG
Mon Jun 24 10:08:31 2013
Error 12514 received logging on to the standby
LGWR: Error 12514 creating archivelog file '(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=WIN-7VSLKL4CGU2)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=umisbk_XPT)(INSTANCE_NAME=umisbk)(SERVER=dedicated)))'
Mon Jun 24 10:08:31 2013
Errors in file e:\oracle\product\10.2.0\admin\umis\bdump\umis_lns1_4204.trc:
ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
LNS: Failed to archive log 3 thread 1 sequence 1062 (12514)
Mon Jun 24 10:08:59 2013
Error 12514 received logging on to the standby
Mon Jun 24 10:08:59 2013
Errors in file e:\oracle\product\10.2.0\admin\umis\bdump\umis_arc1_3808.trc:
ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
FAL[server, ARC1]: Error 12514 creating remote archivelog file '(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=WIN-7VSLKL4CGU2)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=umisbk_XPT)(INSTANCE_NAME=umisbk)(SERVER=dedicated)))'
FAL[server, ARC1]: FAL archive failed, see trace file.
Mon Jun 24 10:08:59 2013
Errors in file e:\oracle\product\10.2.0\admin\umis\bdump\umis_arc1_3808.trc:
ORA-16055: FAL request rejected
ARCH: FAL archive failed. Archiver continuing
Mon Jun 24 10:14:57 2013
Error 12514 received logging on to the standby
Mon Jun 24 10:14:57 2013
Errors in file e:\oracle\product\10.2.0\admin\umis\bdump\umis_arc1_3808.trc:
ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
PING[ARC1]: Heartbeat failed to connect to standby '(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=WIN-7VSLKL4CGU2)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=umisbk_XPT)(INSTANCE_NAME=umisbk)(SERVER=dedicated)))'. Error is 12514.
Mon Jun 24 10:18:46 2013
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
Mon Jun 24 10:19:23 2013
ALTER SYSTEM SET log_archive_dest_2='service="(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=WIN-7VSLKL4CGU2)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=umisbk_XPT)(INSTANCE_NAME=umisbk)(SERVER=dedicated)))"',' LGWR ASYNC NOAFFIRM delay=0 OPTIONAL max_failure=0 max_connections=1 reopen=300 db_unique_name="umisbk" register net_timeout=180 valid_for=(online_logfile,primary_role)' SCOPE=BOTH;
Mon Jun 24 10:19:23 2013
ALTER SYSTEM SET log_archive_dest_state_2='ENABLE' SCOPE=BOTH;
Mon Jun 24 10:19:23 2013
ALTER SYSTEM ARCHIVE LOG
Mon Jun 24 10:19:24 2013
Thread 1 cannot allocate new log, sequence 1063
Private strand flush not complete
Current log# 3 seq# 1062 mem# 0: E:\ORACLE\PRODUCT\10.2.0\ORADATA\UMIS\REDO03.LOG
LNS1 started with pid=18, OS id=4300
Mon Jun 24 10:19:28 2013
Thread 1 advanced to log sequence 1063 (LGWR switch)
Current log# 1 seq# 1063 mem# 0: E:\ORACLE\PRODUCT\10.2.0\ORADATA\UMIS\REDO01.LOG
Mon Jun 24 10:19:28 2013
LNS: Standby redo logfile selected for thread 1 sequence 1063 for destination LOG_ARCHIVE_DEST_2
Mon Jun 24 10:19:58 2013
ARC1: Standby redo logfile selected for thread 1 sequence 1062 for destination LOG_ARCHIVE_DEST_2
Well there seems to be some connectivity issue on Primary DB (I Guess!!!).
But when I issue tnsping from Primary Database, the result is
SQL> host tnsping umisbk (Standy DB Name) ---> Status: OK [10-30msec]
And when I issue tnsping from Standby Database, the result is
SQL> host tnsping umis (Primary DB Name) ---> Status: OK [10-30msec]
So what your Recommendation.
Kind Regards
Thuhnder2777 -
In dataguard when i check view log(OBJECT-Viewlog) it return
"Data Guard Remote Process Startup Fail"?
Regardshi there,
What's your question and you need to provide the version and the type of standby db too? -
Data Guard adding new data files to a tablespace.
In the past, if you were manually updating an Oracle physical standby database there were issues with adding a data file to a tablespace. It was suggested that the data file should be created small and then the small physical file copied to the standby database. Once the small data file was in place it would be resized on the primary database then the repication would change the size on the standby.
My question is, does Data Guard take care of this automaticlly for a physical standby? I can't find any specific reference on how it handles a new datafile.Never mind, I found the answer.
STANDBY_FILE_MANAGEMENT=auto
Set on the standby database will create the datafiles. -
Problem with logminer in Data Guard configuration
Hi all,
I experience strange problem with applying of the logs in DataGuard configuration on the logical standby database side.
I've set up the configuration step by step as it is described in documentation (Oracle Data Guard Concepts and Administration, chapter 4).
Everything went fine until I issued
ALTER DATABASE START LOGICAL STANDBY APPLY;
I saw that log applying process was started by checking the output of
SELECT NAME, VALUE FROM V$LOGSTDBY_STATS WHERE NAME = 'coordinator state';
and
SELECT TYPE, HIGH_SCN, STATUS FROM V$LOGSTDBY;
but in few minutes it stoped and quering DBA_LOGSTDBY_EVENTS I saw the following records:
ORA-16111: log mining and apply setting up
ORA-01332: internal Logminer Dictionary error
Alert log says the following:
LOGSTDBY event: ORA-01332: internal Logminer Dictionary error
Wed Jan 21 16:57:57 2004
Errors in file /opt/oracle/admin/whouse/bdump/whouse_lsp0_5817.trc:
ORA-01332: internal Logminer Dictionary error
Here is the end of the whouse_lsp0_5817.trc
error 1332 detected in background process
OPIRIP: Uncaught error 447. Error stack:
ORA-00447: fatal error in background process
ORA-01332: internal Logminer Dictionary error
But the most useful info I found in one more trace file (whouse_p001_5821.trc):
krvxmrs: Leaving by exception: 604
ORA-00604: error occurred at recursive SQL level 1
ORA-01031: insufficient privileges
ORA-06512: at "SYS.LOGMNR_KRVRDREPDICT3", line 68
ORA-06512: at line 1
Seems that somewhere the correct privileges were not given or smth like this. By the way I was doing all the operations under SYS account (as SYSDBA).
Could smb give me a clue where could be my mistake or what was done in the wrong way?
Thank you in advance.Which is your SSIS version?
Please Mark This As Answer if it solved your issue
Please Vote This As Helpful if it helps to solve your issue
Visakh
My MSDN Page
My Personal Blog
My Facebook Page -
Data guard synchronization after link down b/w primary and physical standby
Hi All,
I have configured data guard on oracle 11gr2 db. Normally switchover between my primary and physical standby happens smoothly and the Apply lag would be zero. Recently We had to test a scenario when the network link between Primary and Physical standby is completely down and Physical standby is isolated completely for more than half an hour.
When we brought up the link every thing worked smoothly but apply lag started increasing from 0 to around 3 hrs. And then it started reducing to 0. Currently Apply lag and transport lag shows 0.
But is this normal behaviour of oracle data guard that when the link between primary and physical standby is completely down, It requires 3-4 hrs for resynchronization ??? Even when during isolation, there were very few transactions happend on primary database ??
Are there any documents available for this scenario??
ThanksHi, after the link is up, if there were some transactions and produced archive logs it's normal to take some time for resync. To check if 3-4 hours is normal or not, you can repeat the scenario and this time check
- how many archivelogs does primary produce in this period.
- after the link is up, does archivelog transfer immediately starts from primary to standby? Is primary able to send these archivelogs parallel?
- Is there anything wrong with the apply process?
check primary & standby alert log files, and run this query on standby to check the transport and apply processes:
SELECT PROCESS, STATUS, THREAD#, SEQUENCE#, BLOCK#, BLOCKS FROM V$MANAGED_STANDBY;
regards -
Data Guard Failover after primary site network failure or disconnect.
Hello Experts:
I'll try to be clear and specific with my issue:
Environment:
Two nodes with NO shared storage (I don't have an Observer running).
Veritas Cluser Server (VCS) with Data Guar Agent. (I don't use the Broker. Data Guard agent "takes care" of the switchover and failover).
Two single instance databases, one per node. NO RAC.
What I'm being able to perform with no issues:
Manual switch(over) of the primary database by running VCS command "hagrp -switch oraDG_group -to standby_node"
Automatic fail(over) when primary node is rebooted with "reboot" or "init"
Automatic fail(over) when primary node is shut down with "shutdown".
What I'm NOT being able to perform:
If I manually unplug the network cables from the primary site (all the network, not only the link between primary and standby node so, it's like a server unplug from the energy source).
Same situation happens if I manually disconnect the server from the power.
This is the alert logs I have:
This is the portion of the alert log at Standby site when Real Time Replication is working fine:
Recovery of Online Redo Log: Thread 1 Group 4 Seq 7 Reading mem 0
Mem# 0: /u02/oracle/fast_recovery_area/standby_db/onlinelog/o1_mf_4_9c3tk3dy_.log
At this moment, node1 (Primary) is completely disconnected from the network. SEE at the end when the database (standby which should be converted to PRIMARY) is not getting all the archived logs from the Primary due to the abnormal disconnect from the network:
Identified End-Of-Redo (failover) for thread 1 sequence 7 at SCN 0xffff.ffffffff
Incomplete Recovery applied until change 15922544 time 12/23/2013 17:12:48
Media Recovery Complete (primary_db)
Terminal Recovery: successful completion
Forcing ARSCN to IRSCN for TR 0:15922544
Mon Dec 23 17:13:22 2013
ARCH: Archival stopped, error occurred. Will continue retrying
ORACLE Instance primary_db - Archival ErrorAttempt to set limbo arscn 0:15922544 irscn 0:15922544
ORA-16014: log 4 sequence# 7 not archived, no available destinations
ORA-00312: online log 4 thread 1: '/u02/oracle/fast_recovery_area/standby_db/onlinelog/o1_mf_4_9c3tk3dy_.log'
Resetting standby activation ID 2071848820 (0x7b7de774)
Completed: ALTER DATABASE RECOVER MANAGED STANDBY DATABASE FINISH
Mon Dec 23 17:13:33 2013
ALTER DATABASE RECOVER MANAGED STANDBY DATABASE FINISH
Terminal Recovery: applying standby redo logs.
Terminal Recovery: thread 1 seq# 7 redo required
Terminal Recovery:
Recovery of Online Redo Log: Thread 1 Group 4 Seq 7 Reading mem 0
Mem# 0: /u02/oracle/fast_recovery_area/standby_db/onlinelog/o1_mf_4_9c3tk3dy_.log
Identified End-Of-Redo (failover) for thread 1 sequence 7 at SCN 0xffff.ffffffff
Incomplete Recovery applied until change 15922544 time 12/23/2013 17:12:48
Media Recovery Complete (primary_db)
Terminal Recovery: successful completion
Forcing ARSCN to IRSCN for TR 0:15922544
Mon Dec 23 17:13:22 2013
ARCH: Archival stopped, error occurred. Will continue retrying
ORACLE Instance primary_db - Archival ErrorAttempt to set limbo arscn 0:15922544 irscn 0:15922544
ORA-16014: log 4 sequence# 7 not archived, no available destinations
ORA-00312: online log 4 thread 1: '/u02/oracle/fast_recovery_area/standby_db/onlinelog/o1_mf_4_9c3tk3dy_.log'
Resetting standby activation ID 2071848820 (0x7b7de774)
Completed: ALTER DATABASE RECOVER MANAGED STANDBY DATABASE FINISH
Mon Dec 23 17:13:33 2013
ALTER DATABASE RECOVER MANAGED STANDBY DATABASE FINISH
Attempt to do a Terminal Recovery (primary_db)
Media Recovery Start: Managed Standby Recovery (primary_db)
started logmerger process
Mon Dec 23 17:13:33 2013
Managed Standby Recovery not using Real Time Apply
Media Recovery failed with error 16157
Recovery Slave PR00 previously exited with exception 283
ORA-283 signalled during: ALTER DATABASE RECOVER MANAGED STANDBY DATABASE FINISH...
Mon Dec 23 17:13:34 2013
Shutting down instance (immediate)
Shutting down instance: further logons disabled
Stopping background process MMNL
Stopping background process MMON
License high water mark = 38
All dispatchers and shared servers shutdown
ALTER DATABASE CLOSE NORMAL
ORA-1109 signalled during: ALTER DATABASE CLOSE NORMAL...
ALTER DATABASE DISMOUNT
Shutting down archive processes
Archiving is disabled
Mon Dec 23 17:13:38 2013
Mon Dec 23 17:13:38 2013
Mon Dec 23 17:13:38 2013
ARCH shutting downARCH shutting down
ARCH shutting down
ARC0: Relinquishing active heartbeat ARCH role
ARC2: Archival stopped
ARC0: Archival stopped
ARC1: Archival stopped
Completed: ALTER DATABASE DISMOUNT
ARCH: Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
Mon Dec 23 17:13:40 2013
Stopping background process VKTM
ARCH: Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
Mon Dec 23 17:13:43 2013
Instance shutdown complete
Mon Dec 23 17:13:44 2013
Adjusting the default value of parameter parallel_max_servers
from 1280 to 470 due to the value of parameter processes (500)
Starting ORACLE instance (normal)
************************ Large Pages Information *******************
Per process system memlock (soft) limit = 64 KB
Total Shared Global Region in Large Pages = 0 KB (0%)
Large Pages used by this instance: 0 (0 KB)
Large Pages unused system wide = 0 (0 KB)
Large Pages configured system wide = 0 (0 KB)
Large Page size = 2048 KB
RECOMMENDATION:
Total System Global Area size is 3762 MB. For optimal performance,
prior to the next instance restart:
1. Increase the number of unused large pages by
at least 1881 (page size 2048 KB, total size 3762 MB) system wide to
get 100% of the System Global Area allocated with large pages
2. Large pages are automatically locked into physical memory.
Increase the per process memlock (soft) limit to at least 3770 MB to lock
100% System Global Area's large pages into physical memory
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Initial number of CPU is 32
Number of processor cores in the system is 16
Number of processor sockets in the system is 2
CELL communication is configured to use 0 interface(s):
CELL IP affinity details:
NUMA status: NUMA system w/ 2 process groups
cellaffinity.ora status: cannot find affinity map at '/etc/oracle/cell/network-config/cellaffinity.ora' (see trace file for details)
CELL communication will use 1 IP group(s):
Grp 0:
Picked latch-free SCN scheme 3
Autotune of undo retention is turned on.
IMODE=BR
ILAT =88
LICENSE_MAX_USERS = 0
SYS auditing is disabled
NUMA system with 2 nodes detected
Starting up:
Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options.
ORACLE_HOME = /u01/oracle/product/11.2.0.4
System name: Linux
Node name: node2.localdomain
Release: 2.6.32-131.0.15.el6.x86_64
Version: #1 SMP Tue May 10 15:42:40 EDT 2011
Machine: x86_64
Using parameter settings in server-side spfile /u01/oracle/product/11.2.0.4/dbs/spfileprimary_db.ora
System parameters with non-default values:
processes = 500
sga_target = 3760M
control_files = "/u02/oracle/orafiles/primary_db/control01.ctl"
control_files = "/u01/oracle/fast_recovery_area/primary_db/control02.ctl"
db_file_name_convert = "standby_db"
db_file_name_convert = "primary_db"
log_file_name_convert = "standby_db"
log_file_name_convert = "primary_db"
control_file_record_keep_time= 40
db_block_size = 8192
compatible = "11.2.0.4.0"
log_archive_dest_1 = "location=/u02/oracle/archivelogs/primary_db"
log_archive_dest_2 = "SERVICE=primary_db ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=primary_db"
log_archive_dest_state_2 = "ENABLE"
log_archive_min_succeed_dest= 1
fal_server = "primary_db"
log_archive_trace = 0
log_archive_config = "DG_CONFIG=(primary_db,standby_db)"
log_archive_format = "%t_%s_%r.dbf"
log_archive_max_processes= 3
db_recovery_file_dest = "/u02/oracle/fast_recovery_area"
db_recovery_file_dest_size= 30G
standby_file_management = "AUTO"
db_flashback_retention_target= 1440
undo_tablespace = "UNDOTBS1"
remote_login_passwordfile= "EXCLUSIVE"
db_domain = ""
dispatchers = "(PROTOCOL=TCP) (SERVICE=primary_dbXDB)"
job_queue_processes = 0
audit_file_dest = "/u01/oracle/admin/primary_db/adump"
audit_trail = "DB"
db_name = "primary_db"
db_unique_name = "standby_db"
open_cursors = 300
pga_aggregate_target = 1250M
dg_broker_start = FALSE
diagnostic_dest = "/u01/oracle"
Mon Dec 23 17:13:45 2013
PMON started with pid=2, OS id=29108
Mon Dec 23 17:13:45 2013
PSP0 started with pid=3, OS id=29110
Mon Dec 23 17:13:46 2013
VKTM started with pid=4, OS id=29125 at elevated priority
VKTM running at (1)millisec precision with DBRM quantum (100)ms
Mon Dec 23 17:13:46 2013
GEN0 started with pid=5, OS id=29129
Mon Dec 23 17:13:46 2013
DIAG started with pid=6, OS id=29131
Mon Dec 23 17:13:46 2013
DBRM started with pid=7, OS id=29133
Mon Dec 23 17:13:46 2013
DIA0 started with pid=8, OS id=29135
Mon Dec 23 17:13:46 2013
MMAN started with pid=9, OS id=29137
Mon Dec 23 17:13:46 2013
DBW0 started with pid=10, OS id=29139
Mon Dec 23 17:13:46 2013
DBW1 started with pid=11, OS id=29141
Mon Dec 23 17:13:46 2013
DBW2 started with pid=12, OS id=29143
Mon Dec 23 17:13:46 2013
DBW3 started with pid=13, OS id=29145
Mon Dec 23 17:13:46 2013
LGWR started with pid=14, OS id=29147
Mon Dec 23 17:13:46 2013
CKPT started with pid=15, OS id=29149
Mon Dec 23 17:13:46 2013
SMON started with pid=16, OS id=29151
Mon Dec 23 17:13:46 2013
RECO started with pid=17, OS id=29153
Mon Dec 23 17:13:46 2013
MMON started with pid=18, OS id=29155
Mon Dec 23 17:13:46 2013
MMNL started with pid=19, OS id=29157
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
starting up 1 shared server(s) ...
ORACLE_BASE from environment = /u01/oracle
Mon Dec 23 17:13:46 2013
ALTER DATABASE MOUNT
ARCH: STARTING ARCH PROCESSES
Mon Dec 23 17:13:50 2013
ARC0 started with pid=23, OS id=29210
ARC0: Archival started
ARCH: STARTING ARCH PROCESSES COMPLETE
ARC0: STARTING ARCH PROCESSES
Successful mount of redo thread 1, with mount id 2071851082
Mon Dec 23 17:13:51 2013
ARC1 started with pid=24, OS id=29212
Allocated 15937344 bytes in shared pool for flashback generation buffer
Mon Dec 23 17:13:51 2013
ARC2 started with pid=25, OS id=29214
Starting background process RVWR
ARC1: Archival started
ARC1: Becoming the 'no FAL' ARCH
ARC1: Becoming the 'no SRL' ARCH
Mon Dec 23 17:13:51 2013
RVWR started with pid=26, OS id=29216
Physical Standby Database mounted.
Lost write protection disabled
Completed: ALTER DATABASE MOUNT
Mon Dec 23 17:13:51 2013
ALTER DATABASE RECOVER MANAGED STANDBY DATABASE
USING CURRENT LOGFILE DISCONNECT FROM SESSION
Attempt to start background Managed Standby Recovery process (primary_db)
Mon Dec 23 17:13:51 2013
MRP0 started with pid=27, OS id=29219
MRP0: Background Managed Standby Recovery process started (primary_db)
ARC2: Archival started
ARC0: STARTING ARCH PROCESSES COMPLETE
ARC2: Becoming the heartbeat ARCH
ARC2: Becoming the active heartbeat ARCH
ARCH: Archival stopped, error occurred. Will continue retrying
ORACLE Instance primary_db - Archival Error
ORA-16014: log 4 sequence# 7 not archived, no available destinations
ORA-00312: online log 4 thread 1: '/u02/oracle/fast_recovery_area/standby_db/onlinelog/o1_mf_4_9c3tk3dy_.log'
At this moment, I've lost service and I have to wait until the prmiary server goes up again to receive the missing log.
This is the rest of the log:
Fatal NI connect error 12543, connecting to:
(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=node1)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=primary_db)(CID=(PROGRAM=oracle)(HOST=node2.localdomain)(USER=oracle))))
VERSION INFORMATION:
TNS for Linux: Version 11.2.0.4.0 - Production
TCP/IP NT Protocol Adapter for Linux: Version 11.2.0.4.0 - Production
Time: 23-DEC-2013 17:13:52
Tracing not turned on.
Tns error struct:
ns main err code: 12543
TNS-12543: TNS:destination host unreachable
ns secondary err code: 12560
nt main err code: 513
TNS-00513: Destination host unreachable
nt secondary err code: 113
nt OS err code: 0
Fatal NI connect error 12543, connecting to:
(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=node1)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=primary_db)(CID=(PROGRAM=oracle)(HOST=node2.localdomain)(USER=oracle))))
VERSION INFORMATION:
TNS for Linux: Version 11.2.0.4.0 - Production
TCP/IP NT Protocol Adapter for Linux: Version 11.2.0.4.0 - Production
Time: 23-DEC-2013 17:13:55
Tracing not turned on.
Tns error struct:
ns main err code: 12543
TNS-12543: TNS:destination host unreachable
ns secondary err code: 12560
nt main err code: 513
TNS-00513: Destination host unreachable
nt secondary err code: 113
nt OS err code: 0
started logmerger process
Mon Dec 23 17:13:56 2013
Managed Standby Recovery starting Real Time Apply
MRP0: Background Media Recovery terminated with error 16157
Errors in file /u01/oracle/diag/rdbms/standby_db/primary_db/trace/primary_db_pr00_29230.trc:
ORA-16157: media recovery not allowed following successful FINISH recovery
Managed Standby Recovery not using Real Time Apply
Completed: ALTER DATABASE RECOVER MANAGED STANDBY DATABASE
USING CURRENT LOGFILE DISCONNECT FROM SESSION
Recovery Slave PR00 previously exited with exception 16157
MRP0: Background Media Recovery process shutdown (primary_db)
Fatal NI connect error 12543, connecting to:
(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=node1)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=primary_db)(CID=(PROGRAM=oracle)(HOST=node2.localdomain)(USER=oracle))))
VERSION INFORMATION:
TNS for Linux: Version 11.2.0.4.0 - Production
TCP/IP NT Protocol Adapter for Linux: Version 11.2.0.4.0 - Production
Time: 23-DEC-2013 17:13:58
Tracing not turned on.
Tns error struct:
ns main err code: 12543
TNS-12543: TNS:destination host unreachable
ns secondary err code: 12560
nt main err code: 513
TNS-00513: Destination host unreachable
nt secondary err code: 113
nt OS err code: 0
Mon Dec 23 17:14:01 2013
Fatal NI connect error 12543, connecting to:
(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=node1)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=primary_db)(CID=(PROGRAM=oracle)(HOST=node2.localdomain)(USER=oracle))))
VERSION INFORMATION:
TNS for Linux: Version 11.2.0.4.0 - Production
TCP/IP NT Protocol Adapter for Linux: Version 11.2.0.4.0 - Production
Time: 23-DEC-2013 17:14:01
Tracing not turned on.
Tns error struct:
ns main err code: 12543
TNS-12543: TNS:destination host unreachable
ns secondary err code: 12560
nt main err code: 513
TNS-00513: Destination host unreachable
nt secondary err code: 113
nt OS err code: 0
Error 12543 received logging on to the standby
FAL[client, ARC0]: Error 12543 connecting to primary_db for fetching gap sequence
Archiver process freed from errors. No longer stopped
Mon Dec 23 17:15:07 2013
Using STANDBY_ARCHIVE_DEST parameter default value as /u02/oracle/archivelogs/primary_db
Mon Dec 23 17:19:51 2013
ARCH: Archival stopped, error occurred. Will continue retrying
ORACLE Instance primary_db - Archival Error
ORA-16014: log 4 sequence# 7 not archived, no available destinations
ORA-00312: online log 4 thread 1: '/u02/oracle/fast_recovery_area/standby_db/onlinelog/o1_mf_4_9c3tk3dy_.log'
Mon Dec 23 17:26:18 2013
RFS[1]: Assigned to RFS process 31456
RFS[1]: No connections allowed during/after terminal recovery.
Mon Dec 23 17:26:47 2013
flashback database to scn 15921680
ORA-16157 signalled during: flashback database to scn 15921680...
Mon Dec 23 17:27:05 2013
alter database recover managed standby database using current logfile disconnect
Attempt to start background Managed Standby Recovery process (primary_db)
Mon Dec 23 17:27:05 2013
MRP0 started with pid=28, OS id=31481
MRP0: Background Managed Standby Recovery process started (primary_db)
started logmerger process
Mon Dec 23 17:27:10 2013
Managed Standby Recovery starting Real Time Apply
MRP0: Background Media Recovery terminated with error 16157
Errors in file /u01/oracle/diag/rdbms/standby_db/primary_db/trace/primary_db_pr00_31486.trc:
ORA-16157: media recovery not allowed following successful FINISH recovery
Managed Standby Recovery not using Real Time Apply
Completed: alter database recover managed standby database using current logfile disconnect
Recovery Slave PR00 previously exited with exception 16157
MRP0: Background Media Recovery process shutdown (primary_db)
Mon Dec 23 17:27:18 2013
RFS[2]: Assigned to RFS process 31492
RFS[2]: No connections allowed during/after terminal recovery.
Mon Dec 23 17:28:18 2013
RFS[3]: Assigned to RFS process 31614
RFS[3]: No connections allowed during/after terminal recovery.
Do you have any advice?
Thanks!
Alex.Hello;
What's not clear to me in your question at this point:
What I'm NOT being able to perform:
If I manually unplug the network cables from the primary site (all the network, not only the link between primary and standby node so, it's like a server unplug from the energy source).
Same situation happens if I manually disconnect the server from the power.
This is the alert logs I have:"
Are you trying a failover to the Standby?
Please advise.
Is it possible your "valid_for clause" is set incorrectly?
Would also review this:
ORA-16014 and ORA-00312 Messages in Alert.log of Physical Standby
Best Regards
mseberg -
How do i find dataloss in Data Guard?
We are using redo log, in async mode, following is our setting.
SERVICE=xxx_sb max_failure=100 reopen=600 LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=xxx_sb
When i query V$managed_Standby for delay_mins, its always zero. Meaning there is no delay in copying a log. I have 2 questions..
1. How can i communicate to business that in worst case we will lose x Mintues of data? Its an OLTP, where the transactions are less then 2mins. Also during the night there are some batch jobs where the transactions are 60mins longs.
2. Most of the time during peak hours there is a log switch happening every 10-15mins but during non-peak it may not happen for a long period of time, is it advisable to set ARCHIVE_LAG_TIME to 10 mins? as im not using archiver , we are using log writer for standby.
any explanation or point to documentation would be appreciated,
Thanks,Production databases who are running with fully fined configured Data Guard, do'nt have any dataloss because failover operation ensures zero data loss if dataguard is configured with maximum protection mode or maximum availability mode at failover time.
http://www.dbazone.com/docs/oracle_10gDataGuard_overview.pdf
The above pdf is oracle white paper which too confirmed it.
LGWR SYNC AFFIRM in Oracle Data Guard is used for zero data loss. How does one ensure zero data loss? Well, the redo block generated at the primary has to reach the standby across the network (that's where the SYNC part comes in - i.e. it is a synchronous network call), and then the block has to be written on disk on the standby (that's where the AFFIRM part comes in) - typically on a standby redo log.
Can you have LGWR SYNC NOAFFIRM? Yes sure. Then you will have synchronous network transport, but the only thing you are guaranteed is that the block has reached the remote standby's memory. It has not been written on to disk yet. So not really a zero data loss solution (e.g. what if the standby instance crashes before the disk I/O).
To sum up -> LGWR SYNC AFFIRM means primary transaction commits are waiting for ntk I/O + disk I/O acks. LGWR SYNC NOAFFIRM means primary transaction commits are waiting for ntk I/O only.
Source:http://www.dbasupport.com/forums/showthread.php?t=54467
HTH
Girish Sharma -
I have one problem with Data Guard. My archive log files are not applied.
I have one problem with Data Guard. My archive log files are not applied. However I have received all archive log files to my physical Standby db
I have created a Physical Standby database on Oracle 10gR2 (Windows XP professional). Primary database is on another computer.
In Enterprise Manager on Primary database it looks ok. I get the following message Data Guard status Normal
But as I wrote above the archive log files are not applied
After I created the Physical Standby database, I have also done:
1. I connected to the Physical Standby database instance.
CONNECT SYS/SYS@luda AS SYSDBA
2. I started the Oracle instance at the Physical Standby database without mounting the database.
STARTUP NOMOUNT PFILE=C:\oracle\product\10.2.0\db_1\database\initluda.ora
3. I mounted the Physical Standby database:
ALTER DATABASE MOUNT STANDBY DATABASE
4. I started redo apply on Physical Standby database
alter database recover managed standby database disconnect from session
5. I switched the log files on Physical Standby database
alter system switch logfile
6. I verified the redo data was received and archived on Physical Standby database
select sequence#, first_time, next_time from v$archived_log order by sequence#
SEQUENCE# FIRST_TIME NEXT_TIME
3 2006-06-27 2006-06-27
4 2006-06-27 2006-06-27
5 2006-06-27 2006-06-27
6 2006-06-27 2006-06-27
7 2006-06-27 2006-06-27
8 2006-06-27 2006-06-27
7. I verified the archived redo log files were applied on Physical Standby database
select sequence#,applied from v$archived_log;
SEQUENCE# APP
4 NO
3 NO
5 NO
6 NO
7 NO
8 NO
8. on Physical Standby database
select * from v$archive_gap;
No rows
9. on Physical Standby database
SELECT MESSAGE FROM V$DATAGUARD_STATUS;
MESSAGE
ARC0: Archival started
ARC1: Archival started
ARC2: Archival started
ARC3: Archival started
ARC4: Archival started
ARC5: Archival started
ARC6: Archival started
ARC7: Archival started
ARC8: Archival started
ARC9: Archival started
ARCa: Archival started
ARCb: Archival started
ARCc: Archival started
ARCd: Archival started
ARCe: Archival started
ARCf: Archival started
ARCg: Archival started
ARCh: Archival started
ARCi: Archival started
ARCj: Archival started
ARCk: Archival started
ARCl: Archival started
ARCm: Archival started
ARCn: Archival started
ARCo: Archival started
ARCp: Archival started
ARCq: Archival started
ARCr: Archival started
ARCs: Archival started
ARCt: Archival started
ARC0: Becoming the 'no FAL' ARCH
ARC0: Becoming the 'no SRL' ARCH
ARC1: Becoming the heartbeat ARCH
Attempt to start background Managed Standby Recovery process
MRP0: Background Managed Standby Recovery process started
Managed Standby Recovery not using Real Time Apply
MRP0: Background Media Recovery terminated with error 1110
MRP0: Background Media Recovery process shutdown
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
RFS[1]: Assigned to RFS process 2148
RFS[1]: Identified database type as 'physical standby'
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
RFS[2]: Assigned to RFS process 2384
RFS[2]: Identified database type as 'physical standby'
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
RFS[3]: Assigned to RFS process 3188
RFS[3]: Identified database type as 'physical standby'
Primary database is in MAXIMUM PERFORMANCE mode
Primary database is in MAXIMUM PERFORMANCE mode
RFS[3]: No standby redo logfiles created
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
RFS[4]: Assigned to RFS process 3168
RFS[4]: Identified database type as 'physical standby'
RFS[4]: No standby redo logfiles created
Primary database is in MAXIMUM PERFORMANCE mode
RFS[3]: No standby redo logfiles created
10. on Physical Standby database
SELECT PROCESS, STATUS, THREAD#, SEQUENCE#, BLOCK#, BLOCKS FROM V$MANAGED_STANDBY;
PROCESS STATUS THREAD# SEQUENCE# BLOCK# BLOCKS
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
RFS IDLE 0 0 0 0
RFS IDLE 0 0 0 0
RFS IDLE 1 9 13664 2
RFS IDLE 0 0 0 0
10) on Primary database:
select message from v$dataguard_status;
MESSAGE
ARC0: Archival started
ARC1: Archival started
ARC2: Archival started
ARC3: Archival started
ARC4: Archival started
ARC5: Archival started
ARC6: Archival started
ARC7: Archival started
ARC8: Archival started
ARC9: Archival started
ARCa: Archival started
ARCb: Archival started
ARCc: Archival started
ARCd: Archival started
ARCe: Archival started
ARCf: Archival started
ARCg: Archival started
ARCh: Archival started
ARCi: Archival started
ARCj: Archival started
ARCk: Archival started
ARCl: Archival started
ARCm: Archival started
ARCn: Archival started
ARCo: Archival started
ARCp: Archival started
ARCq: Archival started
ARCr: Archival started
ARCs: Archival started
ARCt: Archival started
ARCm: Becoming the 'no FAL' ARCH
ARCm: Becoming the 'no SRL' ARCH
ARCd: Becoming the heartbeat ARCH
Error 1034 received logging on to the standby
Error 1034 received logging on to the standby
LGWR: Error 1034 creating archivelog file 'luda'
LNS: Failed to archive log 3 thread 1 sequence 7 (1034)
FAL[server, ARCh]: Error 1034 creating remote archivelog file 'luda'
11)on primary db
select name,sequence#,applied from v$archived_log;
NAME SEQUENCE# APP
C:\ORACLE\PRODUCT\10.2.0\ORADATA\IRINA\ARC00003_0594204176.001 3 NO
C:\ORACLE\PRODUCT\10.2.0\ORADATA\IRINA\ARC00004_0594204176.001 4 NO
Luda 4 NO
Luda 3 NO
C:\ORACLE\PRODUCT\10.2.0\ORADATA\IRINA\ARC00005_0594204176.001 5 NO
Luda 5 NO
C:\ORACLE\PRODUCT\10.2.0\ORADATA\IRINA\ARC00006_0594204176.001 6 NO
Luda 6 NO
C:\ORACLE\PRODUCT\10.2.0\ORADATA\IRINA\ARC00007_0594204176.001 7 NO
Luda 7 NO
C:\ORACLE\PRODUCT\10.2.0\ORADATA\IRINA\ARC00008_0594204176.001 8 NO
Luda 8 NO
12) on standby db
select name,sequence#,applied from v$archived_log;
NAME SEQUENCE# APP
C:\ORACLE\PRODUCT\10.2.0\ORADATA\LUDA\ARC00004_0594204176.001 4 NO
C:\ORACLE\PRODUCT\10.2.0\ORADATA\LUDA\ARC00003_0594204176.001 3 NO
C:\ORACLE\PRODUCT\10.2.0\ORADATA\LUDA\ARC00005_0594204176.001 5 NO
C:\ORACLE\PRODUCT\10.2.0\ORADATA\LUDA\ARC00006_0594204176.001 6 NO
C:\ORACLE\PRODUCT\10.2.0\ORADATA\LUDA\ARC00007_0594204176.001 7 NO
C:\ORACLE\PRODUCT\10.2.0\ORADATA\LUDA\ARC00008_0594204176.001 8 NO
13) my init.ora files
On standby db
irina.__db_cache_size=79691776
irina.__java_pool_size=4194304
irina.__large_pool_size=4194304
irina.__shared_pool_size=75497472
irina.__streams_pool_size=0
*.audit_file_dest='C:\oracle\product\10.2.0\admin\luda\adump'
*.background_dump_dest='C:\oracle\product\10.2.0\admin\luda\bdump'
*.compatible='10.2.0.1.0'
*.control_files='C:\oracle\product\10.2.0\oradata\luda\luda.ctl'
*.core_dump_dest='C:\oracle\product\10.2.0\admin\luda\cdump'
*.db_block_size=8192
*.db_domain=''
*.db_file_multiblock_read_count=16
*.db_file_name_convert='luda','irina'
*.db_name='irina'
*.db_unique_name='luda'
*.db_recovery_file_dest='C:\oracle\product\10.2.0\flash_recovery_area'
*.db_recovery_file_dest_size=2147483648
*.dispatchers='(PROTOCOL=TCP) (SERVICE=irinaXDB)'
*.fal_client='luda'
*.fal_server='irina'
*.job_queue_processes=10
*.log_archive_config='DG_CONFIG=(irina,luda)'
*.log_archive_dest_1='LOCATION=C:/oracle/product/10.2.0/oradata/luda/ VALID_FOR=(ALL_LOGFILES, ALL_ROLES) DB_UNIQUE_NAME=luda'
*.log_archive_dest_2='SERVICE=irina LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES, PRIMARY_ROLE) DB_UNIQUE_NAME=irina'
*.log_archive_dest_state_1='ENABLE'
*.log_archive_dest_state_2='ENABLE'
*.log_archive_max_processes=30
*.log_file_name_convert='C:/oracle/product/10.2.0/oradata/irina/','C:/oracle/product/10.2.0/oradata/luda/'
*.open_cursors=300
*.pga_aggregate_target=16777216
*.processes=150
*.remote_login_passwordfile='EXCLUSIVE'
*.sga_target=167772160
*.standby_file_management='AUTO'
*.undo_management='AUTO'
*.undo_tablespace='UNDOTBS1'
*.user_dump_dest='C:\oracle\product\10.2.0\admin\luda\udump'
On primary db
irina.__db_cache_size=79691776
irina.__java_pool_size=4194304
irina.__large_pool_size=4194304
irina.__shared_pool_size=75497472
irina.__streams_pool_size=0
*.audit_file_dest='C:\oracle\product\10.2.0/admin/irina/adump'
*.background_dump_dest='C:\oracle\product\10.2.0/admin/irina/bdump'
*.compatible='10.2.0.1.0'
*.control_files='C:\oracle\product\10.2.0\oradata\irina\control01.ctl','C:\oracle\product\10.2.0\oradata\irina\control02.ctl','C:\oracle\product\10.2.0\oradata\irina\control03.ctl'
*.core_dump_dest='C:\oracle\product\10.2.0/admin/irina/cdump'
*.db_block_size=8192
*.db_domain=''
*.db_file_multiblock_read_count=16
*.db_file_name_convert='luda','irina'
*.db_name='irina'
*.db_recovery_file_dest='C:\oracle\product\10.2.0/flash_recovery_area'
*.db_recovery_file_dest_size=2147483648
*.dispatchers='(PROTOCOL=TCP) (SERVICE=irinaXDB)'
*.fal_client='irina'
*.fal_server='luda'
*.job_queue_processes=10
*.log_archive_config='DG_CONFIG=(irina,luda)'
*.log_archive_dest_1='LOCATION=C:/oracle/product/10.2.0/oradata/irina/ VALID_FOR=(ALL_LOGFILES, ALL_ROLES) DB_UNIQUE_NAME=irina'
*.log_archive_dest_2='SERVICE=luda LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES, PRIMARY_ROLE) DB_UNIQUE_NAME=luda'
*.log_archive_dest_state_1='ENABLE'
*.log_archive_dest_state_2='ENABLE'
*.log_archive_max_processes=30
*.log_file_name_convert='C:/oracle/product/10.2.0/oradata/luda/','C:/oracle/product/10.2.0/oradata/irina/'
*.open_cursors=300
*.pga_aggregate_target=16777216
*.processes=150
*.remote_login_passwordfile='EXCLUSIVE'
*.sga_target=167772160
*.standby_file_management='AUTO'
*.undo_management='AUTO'
*.undo_tablespace='UNDOTBS1'
*.user_dump_dest='C:\oracle\product\10.2.0/admin/irina/udump'
Please help me!!!!Hi,
After several tries my redo logs are applied now. I think in my case it had to do with the tnsnames.ora. At this moment I have both database in both tnsnames.ora files using the SID and not the SERVICE_NAME.
Now I want to use DGMGRL. Adding a configuration and a stand-by database is working fine, but when I try to enable the configuration DGMGRL gives no feedback and it looks like it is hanging. The log, although says that it succeeded.
In another session 'show configuration' results in the following, confirming that the enable succeeded.
DGMGRL> show configuration
Configuration
Name: avhtest
Enabled: YES
Protection Mode: MaxPerformance
Fast-Start Failover: DISABLED
Databases:
avhtest - Primary database
avhtestls53 - Physical standby database
Current status for "avhtest":
Warning: ORA-16610: command 'ENABLE CONFIGURATION' in progress
It there anybody that experienced the same problem and/or knows the solution to this?
With kind regards,
Martin Schaap -
What is wrong with my Data Guard system?
What is wrong with my Data Guard system(10g10.2.0 on OEL5.0)? What method should I take to diagnose it and repair it?
After shutting down last night, my Data Guard does not run normally today.
On the primary database I issue the following commands:
DGMGRL> show configuration verbose;
Configuration
Name: sdb10g
Enabled: YES
Protection Mode: MaxAvailability
Fast-Start Failover: ENABLED
Databases:
sdb10g - Primary database
stdby10g - Physical standby database
- Fast-Start Failover target
Fast-Start Failover
Threshold: 30 seconds
Observer: hostp
Current status for "sdb10g":
Warning: ORA-16607: one or more databases have failed
DGMGRL> show fast_start failover;
show fast_start failover;
Syntax error before or at "fast_start"
SQL> startup
ORACLE instance started.
Database mounted.
ORA-16649: database will open after Data Guard broker has evaluated Fast-Start
Failover status
On the physical standby database I issue the commands:
SQL> startup mount
ORACLE instance started.
Database mounted.
SQL> recover managed standby database disconnect;
Media recovery complete.
DGMGRL> show configuration verbose;
Configuration
Name: sdb10g
Enabled: YES
Protection Mode: MaxAvailability
Fast-Start Failover: ENABLED
Databases:
sdb10g - Primary database
stdby10g - Physical standby database
- Fast-Start Failover target
Fast-Start Failover
Threshold: 30 seconds
Observer: hostp
Current status for "sdb10g":
Warning: ORA-16607: one or more databases have failed
DGMGRL> disable fast_start failover;
Error: ORA-01034: ORACLE not available
Failed.
Message was edited by:
frank.qian
null
nullThe primary database cannot be opened and the fast_start failover cannot be discabled:
SQL> SQL> ALTER DATABASE open
ERROR at line 1:
ORA-16649: database will open after Data Guard broker has evaluated Fast-Start
Failover status
DGMGRL> disable fast_start failover;
Error: ORA-01034: ORACLE not available
Maybe you are looking for
-
How do i get my songs back if itunes wipes them off?
i plugged my iphone into the laptop to transfer my new songs to my library and its wiped all the songs i've just bought off my phone, how do i get them back?
-
Strange behavior in OM (PI 7.4)
Hi all! I have strange problem with my Operation Mapping in PI 7.4 In this OM i have two mappings. 1. Message Mapping, that sort message 2. Java Mapping, that make structure changes. When i test 1-1 step, copy result of this step and test 2-2 step in
-
has anyone come across an issue with jpg or psd files created in photoshop not being able to be opened by recipients?
-
Oops. Can I read my byte stream files with missing headers?
My fault, I know, but I wrote out an 1D array of numbers to a file using the simple Write File vi, not realising that a header would have been a good idea at the time. Now I can't read them back in because LabVIEW doesn't know what they are, and tryi
-
Blackberry link OSX 1.6 Snow Leopard
Hi, Got my new Z10. I can only download the newest version which requires Mavericks (10.7). Is there a version for 1.6 available? Regards Michael