Dataguard - Primary not applying logs to Standby

Having an issue applying logs to the standby, seemingly it's not setup correctly. I am sure I'm missing something simple here, but would love any input or help. Thanks in advance.
Background:
Primary: CDPMTSB (Single Stand alone)
Standby: CDPMT (RAC)
Error Message on Primary (Alert Log):
Errors in file /data/oracle/app/oracle/diag/rdbms/cdpmtsb/CDPMTSB/trace/CDPMTSB_arc6_9571.trc:
ORA-16014: log 3 sequence# 4071 not archived, no available destinations
ORA-00312: online log 3 thread 2: '+FRA_DG_01/cdpmtsb/onlinelog/group_3.291.799379949'
ARCH: Archival error occurred on a closed thread. Archiver continuing
ORACLE Instance CDPMTSB - Archival Error. Archiver continuing.
Mon Nov 19 19:54:24 2012
Changing destination 4 from remote to local during archival of log#: 3 sequence#: 4071 thread#: 2
Changing destination 4 from remote to local during archival of log#: 3 sequence#: 4071 thread#: 2
ARC6: LGWR is actively archiving destination LOG_ARCHIVE_DEST_2
ARC6: Archive log rejected (thread 2 sequence 4071) at host 'CDPMT'
Errors in file /data/oracle/app/oracle/diag/rdbms/cdpmtsb/CDPMTSB/trace/CDPMTSB_arc6_9571.trc:
ORA-16401: archivelog rejected by RFS
Errors in file /data/oracle/app/oracle/diag/rdbms/cdpmtsb/CDPMTSB/trace/CDPMTSB_arc6_9571.trc:
ORA-16014: log 3 sequence# 4071 not archived, no available destinations
ORA-00312: online log 3 thread 2: '+FRA_DG_01/cdpmtsb/onlinelog/group_3.291.799379949'
ARCH: Archival error occurred on a closed thread. Archiver continuing
ORACLE Instance CDPMTSB - Archival Error. Archiver continuing.
Mon Nov 19 19:59:24 2012
Changing destination 4 from remote to local during archival of log#: 3 sequence#: 4071 thread#: 2
Changing destination 4 from remote to local during archival of log#: 3 sequence#: 4071 thread#: 2
ARC6: LGWR is actively archiving destination LOG_ARCHIVE_DEST_2
ARC6: Archive log rejected (thread 2 sequence 4071) at host 'CDPMT'
Errors in file /data/oracle/app/oracle/diag/rdbms/cdpmtsb/CDPMTSB/trace/CDPMTSB_arc6_9571.trc:
ORA-16401: archivelog rejected by RFS
Errors in file /data/oracle/app/oracle/diag/rdbms/cdpmtsb/CDPMTSB/trace/CDPMTSB_arc6_9571.trc:
ORA-16014: log 3 sequence# 4071 not archived, no available destinations
ORA-00312: online log 3 thread 2: '+FRA_DG_01/cdpmtsb/onlinelog/group_3.291.799379949'
ARCH: Archival error occurred on a closed thread. Archiver continuing
ORACLE Instance CDPMTSB - Archival Error. Archiver continuing.
Mon Nov 19 20:00:00 2012
Errors in file /data/oracle/app/oracle/diag/rdbms/cdpmtsb/CDPMTSB/trace/CDPMTSB_j001_17473.trc:
ORA-12012: error on auto execute of job 72620
ORA-06502: PL/SQL: numeric or value error: character to number conversion error
ORA-06512: at "CD_ADMIN.UTDCD_SURVEY_PKG", line 4926
Standby Alert Log:
ORA-16401: archivelog rejected by RFS
Mon Nov 19 19:32:15 2012
RFS[6]: Assigned to RFS process 4248
RFS[6]: Identified database type as 'physical standby': Client is ARCH pid 9561
Mon Nov 19 19:32:22 2012
RFS[1]: Selected log 6 for thread 1 sequence 4073 dbid 1629723947 branch 769881773
Mon Nov 19 19:32:22 2012
Archived Log entry 1097 added for thread 1 sequence 4072 ID 0x62e7f5cf dest 1:
Archived Log entry 1098 added for thread 1 sequence 4072 ID 0x62e7f5cf dest 3:
Mon Nov 19 19:34:23 2012
Errors in file /opt/app/oracle/diag/rdbms/cdpmt/CDPMT1/trace/CDPMT1_rfs_24994.trc:
ORA-16401: archivelog rejected by RFS
Mon Nov 19 19:38:12 2012
RFS[1]: Selected log 5 for thread 1 sequence 4074 dbid 1629723947 branch 769881773
Mon Nov 19 19:38:12 2012
Archived Log entry 1099 added for thread 1 sequence 4073 ID 0x62e7f5cf dest 1:
Archived Log entry 1100 added for thread 1 sequence 4073 ID 0x62e7f5cf dest 3:
Mon Nov 19 19:39:23 2012
Errors in file /opt/app/oracle/diag/rdbms/cdpmt/CDPMT1/trace/CDPMT1_rfs_24994.trc:
ORA-16401: archivelog rejected by RFS
Mon Nov 19 19:44:24 2012
Errors in file /opt/app/oracle/diag/rdbms/cdpmt/CDPMT1/trace/CDPMT1_rfs_24994.trc:
ORA-16401: archivelog rejected by RFS
Mon Nov 19 19:49:24 2012
Errors in file /opt/app/oracle/diag/rdbms/cdpmt/CDPMT1/trace/CDPMT1_rfs_24994.trc:
ORA-16401: archivelog rejected by RFS
Mon Nov 19 19:54:24 2012
Errors in file /opt/app/oracle/diag/rdbms/cdpmt/CDPMT1/trace/CDPMT1_rfs_24994.trc:
ORA-16401: archivelog rejected by RFS
Mon Nov 19 19:59:24 2012
Errors in file /opt/app/oracle/diag/rdbms/cdpmt/CDPMT1/trace/CDPMT1_rfs_24994.trc:
ORA-16401: archivelog rejected by RFS
Primary Parameters:
NAME TYPE VALUE
log_archive_config string DG_CONFIG=(CDPMT,CDPMTSB)
log_archive_dest string
log_archive_dest_1 string LOCATION=USE_DB_RECOVERY_FILE_
DEST VALID_FOR=(ONLINE_LOGFIL
ES,ALL_ROLES) DB_UNIQUE_NAME=C
DPMTSB
log_archive_dest_10 string
log_archive_dest_2 string SERVICE=CDPMT VALID_FOR=(ONLIN
E_LOGFILES,PRIMARY_ROLE) DB_UN
IQUE_NAME=CDPMT
log_archive_dest_3 string location="+FRA_DG_01/cdpmtsb/s
tandbylog", valid_for=(STANDB
Y_LOGFILE,STANDBY_ROLE)
log_archive_dest_4 string
log_archive_dest_5 string
log_archive_dest_6 string
log_archive_dest_7 string
log_archive_dest_8 string
log_archive_dest_9 string
log_archive_dest_state_1 string enable
log_archive_dest_state_10 string enable
log_archive_dest_state_2 string ENABLE
log_archive_dest_state_3 string ENABLE
log_archive_dest_state_4 string defer
log_archive_dest_state_5 string enable
log_archive_dest_state_6 string enable
log_archive_dest_state_7 string enable
log_archive_dest_state_8 string enable
log_archive_dest_state_9 string enable
log_archive_duplex_dest string
log_archive_format string %t_%s_%r.dbf
log_archive_local_first boolean TRUE
log_archive_max_processes integer 7
log_archive_min_succeed_dest integer 2
log_archive_start boolean FALSE
log_archive_trace integer 0
Standby Parameters:
NAME TYPE VALUE
log_archive_config string dg_config=(CDPMT,CD PMTSB)
log_archive_dest string
log_archive_dest_1 string location="USE_DB_RE COVERY_FILE
_DEST", valid_for= (ALL_LOGFIL
ES,ALL_ROLES)
log_archive_dest_10 string
log_archive_dest_2 string SERVICE=cdpmtsb LGW R ASYNC VAL
ID_FOR=(ONLINE_LOGF ILES,PRIMAR
Y_ROLE) DB_UNIQUE_N AME=cdpmtsb
log_archive_dest_3 string LOCATION=+FRA_DG_01 /CDPMT/STAN
DBYLOG VALID_FOR=( STANDBY_LOG
NAME TYPE VALUE
FILES,STANDBY_ROLE) DB_UNIQUE_
NAME=CDPMT
log_archive_dest_4 string
log_archive_dest_5 string
log_archive_dest_6 string
log_archive_dest_7 string
log_archive_dest_8 string
log_archive_dest_9 string
log_archive_dest_state_1 string ENABLE
log_archive_dest_state_10 string enable
log_archive_dest_state_2 string ENABLE
NAME TYPE VALUE
log_archive_dest_state_3 string enable
log_archive_dest_state_4 string enable
log_archive_dest_state_5 string enable
log_archive_dest_state_6 string enable
log_archive_dest_state_7 string enable
log_archive_dest_state_8 string enable
log_archive_dest_state_9 string enable
log_archive_duplex_dest string
log_archive_format string %t_%s_%r.dbf
log_archive_local_first boolean TRUE
log_archive_max_processes integer 30
NAME TYPE VALUE
log_archive_min_succeed_dest integer 1
log_archive_start boolean FALSE
log_archive_trace integer 0
SQL> show parameter log_ar
NAME TYPE VALUE
log_archive_config string dg_config=(CDPMT,CDPMTSB)
log_archive_dest string
log_archive_dest_1 string location="USE_DB_RECOVERY_FILE
_DEST", valid_for=(ALL_LOGFIL
ES,ALL_ROLES)
log_archive_dest_10 string
log_archive_dest_2 string SERVICE=cdpmtsb LGWR ASYNC VAL
ID_FOR=(ONLINE_LOGFILES,PRIMAR
Y_ROLE) DB_UNIQUE_NAME=cdpmtsb
log_archive_dest_3 string LOCATION=+FRA_DG_01/CDPMT/STAN
DBYLOG VALID_FOR=(STANDBY_LOG
NAME TYPE VALUE
FILES,STANDBY_ROLE) DB_UNIQUE_
NAME=CDPMT
log_archive_dest_4 string
log_archive_dest_5 string
log_archive_dest_6 string
log_archive_dest_7 string
log_archive_dest_8 string
log_archive_dest_9 string
log_archive_dest_state_1 string ENABLE
log_archive_dest_state_10 string enable
log_archive_dest_state_2 string ENABLE
NAME TYPE VALUE
log_archive_dest_state_3 string enable
log_archive_dest_state_4 string enable
log_archive_dest_state_5 string enable
log_archive_dest_state_6 string enable
log_archive_dest_state_7 string enable
log_archive_dest_state_8 string enable
log_archive_dest_state_9 string enable
log_archive_duplex_dest string
log_archive_format string %t_%s_%r.dbf
log_archive_local_first boolean TRUE
log_archive_max_processes integer 30
NAME TYPE VALUE
log_archive_min_succeed_dest integer 1
log_archive_start boolean FALSE
log_archive_trace integer 0
SQL>
DGMGRL> show configuration verbose;
Configuration
Name: cdpmtqa
Enabled: YES
Protection Mode: MaxPerformance
Databases:
cdpmtsb - Primary database
cdpmt - Physical standby database
Fast-Start Failover: DISABLED
Current status for "cdpmtqa":
Warning: ORA-16608: one or more databases have warnings
DGMGRL> show database verbose CDPMT
Database
Name: cdpmt
Role: PHYSICAL STANDBY
Enabled: YES
Intended State: APPLY-ON
Instance(s):
CDPMT1
CDPMT2 (apply instance)
Properties:
DGConnectIdentifier = 'cdpmt'
ObserverConnectIdentifier = ''
LogXptMode = 'ASYNC'
DelayMins = '0'
Binding = 'OPTIONAL'
MaxFailure = '0'
MaxConnections = '1'
ReopenSecs = '300'
NetTimeout = '30'
RedoCompression = 'DISABLE'
LogShipping = 'ON'
PreferredApplyInstance = ''
ApplyInstanceTimeout = '0'
ApplyParallel = 'AUTO'
StandbyFileManagement = 'AUTO'
ArchiveLagTarget = '0'
LogArchiveMaxProcesses = '4'
LogArchiveMinSucceedDest = '1'
DbFileNameConvert = ''
LogFileNameConvert = ''
FastStartFailoverTarget = ''
StatusReport = '(monitor)'
InconsistentProperties = '(monitor)'
InconsistentLogXptProps = '(monitor)'
SendQEntries = '(monitor)'
LogXptStatus = '(monitor)'
RecvQEntries = '(monitor)'
HostName(*)
SidName(*)
StaticConnectIdentifier(*)
StandbyArchiveLocation(*)
AlternateLocation(*)
LogArchiveTrace(*)
LogArchiveFormat(*)
LatestLog(*)
TopWaitEvents(*)
(*) - Please check specific instance for the property value
Current status for "cdpmt":
Warning: ORA-16809: multiple warnings detected for the database
Any help would be really appreciated. Thanks!
Edited by: 972075 on Nov 19, 2012 3:09 PM

Thanks MSEBERG,
Here's what I found. FRA seems to have enough space on ASM and there are other logs there, not sure what the issue is:
14:31:58 SYS: CDPMTSB> show parameter db_recovery
NAME TYPE VALUE
db_recovery_file_dest string +FRA_DG_01
db_recovery_file_dest_size big integer 60G
DGMGRL> show database CDPMTSB logxptstatus;
LOG TRANSPORT STATUS
PRIMARY_INSTANCE_NAME STANDBY_DATABASE_NAME STATUS
CDPMTSB cdpmt
DGMGRL> SHOW DATABASE CDPMTSB InconsistentProperties;
INCONSISTENT PROPERTIES
INSTANCE_NAME PROPERTY_NAME MEMORY_VALUE SPFILE_VALUE BROKER_VALUE
DGMGRL> show database CDPMTSB InconsistentLogXptProps;
INCONSISTENT LOG TRANSPORT PROPERTIES
INSTANCE_NAME STANDBY_NAME PROPERTY_NAME MEMORY_VALUE BROKER_VALUE
DGMGRL> show database CDPMT logxptstatus;
Error: ORA-16757: unable to get this property's value
DGMGRL> SHOW DATABASE CDPMT InconsistentProperties;
INCONSISTENT PROPERTIES
INSTANCE_NAME PROPERTY_NAME MEMORY_VALUE SPFILE_VALUE BROKER_VALUE
CDPMT2 DbFileNameConvert DG_01/cdpmtsb, DG_01/cdpmt
CDPMT2 LogFileNameConvert FRA_DG_01/cdpmtsb, FRA_DG_01/cdpmt, DG_01/cdpmtsb, DG_01/cdpmt
CDPMT1 LogArchiveMaxProcesses 4 30 4
CDPMT1 DbFileNameConvert DG_01/cdpmtsb, DG_01/cdpmt DG_01/cdpmtsb,DG_01/cdpmt
CDPMT1 LogFileNameConvert FRA_DG_01/cdpmtsb, FRA_DG_01/cdpmt, DG_01/cdpmtsb, DG_01/cdpmt FRA_DG_01/cdpmtsb,FRA_DG_01/cdpmt,+DG_01/cdpmtsb,+DG_01/cdpmt
DGMGRL> show database CDPMT InconsistentLogXptProps;
Error: ORA-16757: unable to get this property's value
Errors in the Alert (from Primary):
ARCH: Archival error occurred on a closed thread. Archiver continuing
ORACLE Instance CDPMTSB - Archival Error. Archiver continuing.
Tue Nov 20 14:34:43 2012
Changing destination 4 from remote to local during archival of log#: 3 sequence#: 4071 thread#: 2
Changing destination 4 from remote to local during archival of log#: 3 sequence#: 4071 thread#: 2
ARC6: LGWR is actively archiving destination LOG_ARCHIVE_DEST_2
ARC6: Archive log rejected (thread 2 sequence 4071) at host 'cdpmt'
Errors in file /data/oracle/app/oracle/diag/rdbms/cdpmtsb/CDPMTSB/trace/CDPMTSB_arc6_9571.trc:
ORA-16401: archivelog rejected by RFS
Errors in file /data/oracle/app/oracle/diag/rdbms/cdpmtsb/CDPMTSB/trace/CDPMTSB_arc6_9571.trc:
ORA-16014: log 3 sequence# 4071 not archived, no available destinations
ORA-00312: online log 3 thread 2: '+FRA_DG_01/cdpmtsb/onlinelog/group_3.291.799379949'
ARCH: Archival error occurred on a closed thread. Archiver continuing
ORACLE Instance CDPMTSB - Archival Error. Archiver continuing.
DGMGRL> DGMGRL> show database verbose CDPMT
Database
Name: cdpmt
Role: PHYSICAL STANDBY
Enabled: YES
Intended State: APPLY-ON
Instance(s):
CDPMT1
CDPMT2 (apply instance)
Properties:
DGConnectIdentifier = 'cdpmt'
ObserverConnectIdentifier = ''
LogXptMode = 'ASYNC'
DelayMins = '0'
Binding = 'OPTIONAL'
MaxFailure = '0'
MaxConnections = '1'
ReopenSecs = '300'
NetTimeout = '30'
RedoCompression = 'DISABLE'
LogShipping = 'ON'
PreferredApplyInstance = ''
ApplyInstanceTimeout = '0'
ApplyParallel = 'AUTO'
StandbyFileManagement = 'AUTO'
ArchiveLagTarget = '0'
LogArchiveMaxProcesses = '4'
LogArchiveMinSucceedDest = '1'
DbFileNameConvert = ''
LogFileNameConvert = ''
FastStartFailoverTarget = ''
StatusReport = '(monitor)'
InconsistentProperties = '(monitor)'
InconsistentLogXptProps = '(monitor)'
SendQEntries = '(monitor)'
LogXptStatus = '(monitor)'
RecvQEntries = '(monitor)'
HostName(*)
SidName(*)
StaticConnectIdentifier(*)
StandbyArchiveLocation(*)
AlternateLocation(*)
LogArchiveTrace(*)
LogArchiveFormat(*)
LatestLog(*)
TopWaitEvents(*)
(*) - Please check specific instance for the property value
Current status for "cdpmt":
Warning: ORA-16809: multiple warnings detected for the database
DGMGRL> show database verbose CDPMTSB
Database
Name: cdpmtsb
OEM Name: CDPMTSB_devdb40.utd.com
Role: PRIMARY
Enabled: YES
Intended State: TRANSPORT-ON
Instance(s):
CDPMTSB
Properties:
DGConnectIdentifier = 'cdpmtsb'
ObserverConnectIdentifier = ''
LogXptMode = 'ASYNC'
DelayMins = '0'
Binding = 'OPTIONAL'
MaxFailure = '0'
MaxConnections = '1'
ReopenSecs = '300'
NetTimeout = '30'
RedoCompression = 'DISABLE'
LogShipping = 'ON'
PreferredApplyInstance = ''
ApplyInstanceTimeout = '0'
ApplyParallel = 'AUTO'
StandbyFileManagement = 'AUTO'
ArchiveLagTarget = '0'
LogArchiveMaxProcesses = '7'
LogArchiveMinSucceedDest = '2'
DbFileNameConvert = '+DG_01/cdpmt, +DG_01/cdpmtsb'
LogFileNameConvert = '+FRA_DG_01/cdpmt, FRA_DG_01/cdpmtsb, DG_01/cdpmt, +DG_01/cdpmtsb'
FastStartFailoverTarget = ''
StatusReport = '(monitor)'
InconsistentProperties = '(monitor)'
InconsistentLogXptProps = '(monitor)'
SendQEntries = '(monitor)'
LogXptStatus = '(monitor)'
RecvQEntries = '(monitor)'
HostName = 'devdb40.utd.com'
SidName = 'CDPMTSB'
StaticConnectIdentifier = '(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=devdb40.utd.com)(PORT=1521))(CONNECT_DATA=(SERVICE_NAME=CDPMTSB_DGMGRL)(INSTANCE_NAME=CDPMTSB)(SERVER=DEDICATED)))'
StandbyArchiveLocation = '+FRA_DG_01/cdpmtsb/standbylog'
AlternateLocation = ''
LogArchiveTrace = '0'
LogArchiveFormat = '%t_%s_%r.dbf'
LatestLog = '(monitor)'
TopWaitEvents = '(monitor)'
Current status for "cdpmtsb":
SUCCESS
Thanks for your help btw, I'm really at a loss here as to what is going on with this.

Similar Messages

  • My Active dataguard is not applying archives.

    Dears,
    Following is my setup
    =====================
    Primary:
    prod on RAC with 2 nodes
    Database : Oracle 11.2.0.3
    OS OEL 5.7
    storage : ASM
    +DATADG
    +FLASHDG
    Standby:
    sync on single node
    Database : Oracle 11.2.0.3
    storage : ASM
    +DATADG
    +FLASHDG
    I've configured Active dataguard successfully and was able to apply archivelogs successfully instantly.
    Archive log locations are +FLASHDG/prod/ARCHIVELOG/ AND /u02/arch  --- on primary
    Archive log locations are +FLASHDG/stby/ARCHIVELOG/ AND /u02/arch  --- on standby
    On Standby
    ===========
    SQL> select 'Using Active Data Guard' ADG from v$managed_standby m,v$database d where m.process like 'MRP%' ;
    ADG
    Using Active Data Guard
    SQL> select open_mode,database_role,PROTECTION_MODE,PROTECTION_LEVEL from v$database;
    OPEN_MODE DATABASE_ROLE PROTECTION_MODE PROTECTION_LEVEL
    READ ONLY WITH APPLY PHYSICAL STANDBY MAXIMUM PERFORMANCE MAXIMUM PERFORMANCE
    SQL>
    Upto now everything is ok, means same data is sync on primary and standby. As my archive location was getting full, i've used this SQL query to clean them
    SELECT 'alter diskgroup '||dg.name||' drop file
    ''+'||dg.name||''||SYS_CONNECT_BY_PATH(al.name,'/')||''';'
    FROM v$asm_alias al, v$asm_file fi, v$asm_diskgroup dg
    WHERE al.file_number = fi.file_number(+)
    AND al.group_number = dg.group_number
    AND fi.type = 'ARCHIVELOG'
    START WITH alias_index = 0
    CONNECT BY PRIOR al.reference_index = al.parent_index;
    SELECT 'alter diskgroup '||dg.name||' drop file
    ''+'||dg.name||''||SYS_CONNECT_BY_PATH(al.name,'/')||''';'
    FROM v$asm_alias al, v$asm_file fi, v$asm_diskgroup dg
    WHERE al.file_number = fi.file_number(+)
    AND al.group_number = dg.group_number
    AND fi.type = 'BACKUPSET'
    START WITH alias_index = 0
    CONNECT BY PRIOR al.reference_index = al.parent_index;
    In order to delete ARCHIVE logs which are stored in ASM FLASHDG, which will have a type of "ARCHIVELOG" and "BACKUPSET" i've used this above two queries.
    After performing this steps , my Active dataguard is not applying archives.
    On the primary server, check the latest archived redo log
    SELECT sequence#, first_time, next_time
    FROM v$archived_log
    ORDER BY sequence#;
    2809 16-APR-13 16-APR-13
    2809 16-APR-13 16-APR-13
    2809 16-APR-13 16-APR-13
    2810 16-APR-13 16-APR-13
    2810 16-APR-13 16-APR-13
    2810 16-APR-13 16-APR-13
    2811 16-APR-13 16-APR-13
    2811 16-APR-13 16-APR-13
    2811 16-APR-13 16-APR-13
    2812 16-APR-13 16-APR-13
    2812 16-APR-13 16-APR-13
    2812 16-APR-13 16-APR-13
    2813 16-APR-13 16-APR-13
    2813 16-APR-13 16-APR-13
    2814 16-APR-13 16-APR-13
    2814 16-APR-13 16-APR-13
    2815 16-APR-13 16-APR-13
    2815 16-APR-13 16-APR-13
    2816 16-APR-13 16-APR-13
    2816 16-APR-13 16-APR-13
    2817 16-APR-13 16-APR-13
    2817 16-APR-13 16-APR-13
    2818 16-APR-13 16-APR-13
    2818 16-APR-13 16-APR-13
    2819 16-APR-13 16-APR-13
    2819 16-APR-13 16-APR-13
    2820 16-APR-13 16-APR-13
    2820 16-APR-13 16-APR-13
    2821 16-APR-13 16-APR-13
    2821 16-APR-13 16-APR-13
    2822 16-APR-13 16-APR-13
    2822 16-APR-13 16-APR-13
    2823 16-APR-13 16-APR-13
    2823 16-APR-13 16-APR-13
    2824 16-APR-13 16-APR-13
    2824 16-APR-13 16-APR-13
    2825 16-APR-13 16-APR-13
    2825 16-APR-13 16-APR-13
    2826 16-APR-13 16-APR-13
    2826 16-APR-13 16-APR-13
    2827 16-APR-13 16-APR-13
    2827 16-APR-13 16-APR-13
    2828 16-APR-13 16-APR-13
    2828 16-APR-13 16-APR-13
    2829 16-APR-13 16-APR-13
    2829 16-APR-13 16-APR-13
    2830 16-APR-13 16-APR-13
    2830 16-APR-13 16-APR-13
    2831 16-APR-13 16-APR-13
    2831 16-APR-13 16-APR-13
    2832 16-APR-13 16-APR-13
    2832 16-APR-13 16-APR-13
    2833 16-APR-13 16-APR-13
    2833 16-APR-13 16-APR-13
    2834 16-APR-13 16-APR-13
    2834 16-APR-13 16-APR-13
    2835 16-APR-13 16-APR-13
    2835 16-APR-13 16-APR-13
    2836 16-APR-13 16-APR-13
    2836 16-APR-13 16-APR-13
    2837 16-APR-13 16-APR-13
    2837 16-APR-13 16-APR-13
    2838 16-APR-13 16-APR-13
    2838 16-APR-13 16-APR-13
    2839 16-APR-13 16-APR-13
    2839 16-APR-13 16-APR-13
    2840 16-APR-13 16-APR-13
    2840 16-APR-13 16-APR-13
    2841 16-APR-13 16-APR-13
    2841 16-APR-13 16-APR-13
    2842 16-APR-13 16-APR-13
    2842 16-APR-13 16-APR-13
    2843 16-APR-13 16-APR-13
    2843 16-APR-13 16-APR-13
    2844 16-APR-13 16-APR-13
    2844 16-APR-13 16-APR-13
    2845 16-APR-13 16-APR-13
    2845 16-APR-13 16-APR-13
    2846 16-APR-13 16-APR-13
    2846 16-APR-13 16-APR-13
    Check the new archived redo log has arrived at the standby server and been applied.
    SELECT sequence#, first_time, next_time, applied
    FROM v$archived_log
    ORDER BY sequence#;
    2801 15-APR-13 15-APR-13 YES
    2801 15-APR-13 15-APR-13 YES
    2802 15-APR-13 15-APR-13 YES
    2802 15-APR-13 15-APR-13 YES
    2803 15-APR-13 15-APR-13 YES
    2803 15-APR-13 15-APR-13 YES
    2804 15-APR-13 15-APR-13 YES
    2804 15-APR-13 15-APR-13 YES
    2805 15-APR-13 15-APR-13 YES
    2805 15-APR-13 15-APR-13 YES
    2806 15-APR-13 15-APR-13 YES
    2806 15-APR-13 15-APR-13 YES
    2807 15-APR-13 15-APR-13 YES
    2807 15-APR-13 15-APR-13 YES
    2808 15-APR-13 16-APR-13 YES
    2808 15-APR-13 16-APR-13 YES
    2809 16-APR-13 16-APR-13 YES
    2809 16-APR-13 16-APR-13 YES
    2810 16-APR-13 16-APR-13 YES
    2810 16-APR-13 16-APR-13 YES
    2811 16-APR-13 16-APR-13 YES
    2811 16-APR-13 16-APR-13 YES
    2812 16-APR-13 16-APR-13 IN-MEMORY
    2812 16-APR-13 16-APR-13 YES
    So could anyone help me to resolve this issue. Anticipating your response at the earliest.
    Regards,
    VIKHAR
    Edited by: VIKHARAHMED on Apr 16, 2013 9:38 AM

    Here is the alert log file
    Media Recovery Log +FLASHDG/stby/archivelog/2013_04_16/thread_2_seq_1476.1987.812900733
    Tue Apr 16 18:56:42 2013
    Primary database is in MAXIMUM PERFORMANCE mode
    RFS[1]: Assigned to RFS process 16803
    RFS[1]: Selected log 12 for thread 2 sequence 1485 dbid 220323208 branch 808484882
    Tue Apr 16 18:56:42 2013
    RFS[2]: Assigned to RFS process 16807
    RFS[2]: Opened log for thread 2 sequence 1484 dbid 220323208 branch 808484882
    Archived Log entry 6324 added for thread 2 sequence 1484 rlc 808484882 ID 0xd21a288 dest 10:
    Tue Apr 16 19:09:02 2013
    RFS[1]: Selected log 11 for thread 2 sequence 1486 dbid 220323208 branch 808484882
    Tue Apr 16 19:09:02 2013
    Archived Log entry 6325 added for thread 2 sequence 1485 ID 0xd21a288 dest 1:
    Archived Log entry 6326 added for thread 2 sequence 1485 ID 0xd21a288 dest 2:
    Tue Apr 16 19:12:23 2013
    RFS[1]: Selected log 12 for thread 2 sequence 1487 dbid 220323208 branch 808484882
    Tue Apr 16 19:12:23 2013
    Archived Log entry 6327 added for thread 2 sequence 1486 ID 0xd21a288 dest 1:
    Archived Log entry 6328 added for thread 2 sequence 1486 ID 0xd21a288 dest 2:
    Tue Apr 16 19:14:41 2013
    "alert_stby.log" 845L, 33990C 782,1 94%
    Tue Apr 16 19:17:27 2013
    Archived Log entry 6331 added for thread 2 sequence 1488 ID 0xd21a288 dest 1:
    Archived Log entry 6332 added for thread 2 sequence 1488 ID 0xd21a288 dest 2:
    Tue Apr 16 19:25:51 2013
    RFS[1]: Selected log 11 for thread 2 sequence 1490 dbid 220323208 branch 808484882
    Tue Apr 16 19:25:51 2013
    Archived Log entry 6333 added for thread 2 sequence 1489 ID 0xd21a288 dest 1:
    Archived Log entry 6334 added for thread 2 sequence 1489 ID 0xd21a288 dest 2:
    Tue Apr 16 19:51:02 2013
    RFS[1]: Selected log 12 for thread 2 sequence 1491 dbid 220323208 branch 808484882
    Tue Apr 16 19:51:02 2013
    Archived Log entry 6335 added for thread 2 sequence 1490 ID 0xd21a288 dest 1:
    Archived Log entry 6336 added for thread 2 sequence 1490 ID 0xd21a288 dest 2:
    Tue Apr 16 20:37:12 2013
    RFS[1]: Selected log 11 for thread 2 sequence 1492 dbid 220323208 branch 808484882
    Tue Apr 16 20:37:12 2013
    Archived Log entry 6337 added for thread 2 sequence 1491 ID 0xd21a288 dest 1:
    Archived Log entry 6338 added for thread 2 sequence 1491 ID 0xd21a288 dest 2:
    Tue Apr 16 21:08:23 2013
    RFS[1]: Selected log 12 for thread 2 sequence 1493 dbid 220323208 branch 808484882
    Tue Apr 16 21:08:23 2013
    Archived Log entry 6339 added for thread 2 sequence 1492 ID 0xd21a288 dest 1:
    Archived Log entry 6340 added for thread 2 sequence 1492 ID 0xd21a288 dest 2:
    Tue Apr 16 22:16:06 2013
    RFS[1]: Selected log 11 for thread 2 sequence 1494 dbid 220323208 branch 808484882
    Tue Apr 16 22:16:06 2013
    Archived Log entry 6341 added for thread 2 sequence 1493 ID 0xd21a288 dest 1:
    Archived Log entry 6342 added for thread 2 sequence 1493 ID 0xd21a288 dest 2:
    Tue Apr 16 22:31:46 2013
    RFS[1]: Selected log 12 for thread 2 sequence 1495 dbid 220323208 branch 808484882
    Tue Apr 16 22:31:46 2013
    Archived Log entry 6343 added for thread 2 sequence 1494 ID 0xd21a288 dest 1:
    Archived Log entry 6344 added for thread 2 sequence 1494 ID 0xd21a288 dest 2:
    Wed Apr 17 09:31:59 2013
    RFS[1]: Selected log 11 for thread 2 sequence 1496 dbid 220323208 branch 808484882
    Wed Apr 17 09:32:00 2013
    Archived Log entry 6345 added for thread 2 sequence 1495 ID 0xd21a288 dest 1:
    Archived Log entry 6346 added for thread 2 sequence 1495 ID 0xd21a288 dest 2:

  • Standy database MRP0 is not applying logs

    Hi all,
    i am using oracle 11.1.0.7.0 database on linux
    standby database is receving archives but not applying to to standby.
    CTED 0 0 0 0
    ARCH ARCH CONNECTED 0 0 0 0
    PROCESS CLIENT_P STATUS THREAD# SEQUENCE# BLOCK# BLOCKS
    ARCH ARCH CONNECTED 0 0 0 0
    ARCH ARCH CONNECTED 0 0 0 0
    ARCH ARCH CONNECTED 0 0 0 0
    ARCH ARCH CONNECTED 0 0 0 0
    ARCH ARCH CONNECTED 0 0 0 0
    ARCH ARCH CONNECTED 0 0 0 0
    ARCH ARCH CONNECTED 0 0 0 0
    ARCH ARCH CONNECTED 0 0 0 0
    RFS LGWR RECEIVING 1 66141 33298 2
    RFS UNKNOWN IDLE 0 0 0 0
    MRP0 N/A WAIT_FOR_GAP 1 66003 0 0
    PROCESS CLIENT_P STATUS THREAD# SEQUENCE# BLOCK# BLOCKS
    RFS UNKNOWN IDLE 0 0 0 0
    34 rows selected.
    please help to fix this
    thank you

    check whether there is any gap using the V$ARCHIVE_GAP view or using the V$ARCHIVED_log on the primary.. Appears that there is a gap...
    Thanks,
    Vishnu

  • Standby not applying log - DATAGUARD

    Hi pros and gurus,
    I have encountered a problem which is i don't know how to solve it is since every single log working just fine. I already done creating RMAN files and instantiate it later. But after i bring up standy for receiving logs from primary and apply it, nothing is happening. At the end of instantiate standby database, i got this error:
    RMAN 03015 error occurred in stored script Memory Script
    RMAN 06136 ORACLE error from auxiliary database
    ora-01180 cannot create data file 1
    ora-01110 data file 1 '.../system_1.dbf
    is this error affecting my replication? Please help me.

    syns wrote:
    Hi pros and gurus,
    I have encountered a problem which is i don't know how to solve it is since every single log working just fine. I already done creating RMAN files and instantiate it later. But after i bring up standy for receiving logs from primary and apply it, nothing is happening. At the end of instantiate standby database, i got this error:
    RMAN 03015 error occurred in stored script Memory Script
    RMAN 06136 ORACLE error from auxiliary database
    ora-01180 cannot create data file 1
    ora-01110 data file 1 '.../system_1.dbf
    is this error affecting my replication? Please help me.Can u paste the command which you are running on rman prompt with error message?
    Check alert log file ?
    Post the steps u are following ...
    --neeraj                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               

  • ORA-326/ORA-334 Physical Standby DB - Not applying logs

    Hi, all, I have a Dataguard, the primary db is a RAC with three nodes, the standby db is a physical standby. the dataguard are all oracle 10.2.0.3 on solaris 9 sparc system
    Now, my standby db did not apply the archivelogs,there are some errors in standby alert log :
    Thu Jan 8 15:44:31 2009
    Errors in file /oracle/admin/xxxx/bdump/whut_mrp0_12863.trc:
    ORA-00326:log begins at change 2984028173, need earlier change 2984013192
    ORA-00334:archived log '+DGARCH/whut/3_22648_611942629.dbf'
    Managed Standby Recovery not using Real Time Apply
    Recovery interrupted!
    Thu Jan 8 15:44:34 2009
    Errors in file /export/home/oracle/admin/whut/bdump/whut_mrp0_12863.trc:
    ORA-00326:log begins at change 2984028173, need earlier change 2984013192
    ORA-00334:archived log '+DGARCH/whut/3_22648_611942629.dbf'
    Thu Jan 8 15:44:34 2009
    MRP0: Background Media Recovery process shutdown (whut)
    and the archivelogs on the standby db like this :
    NAME APP DEL
    +DGARCH/whut/3_22651_611942629.dbf                           NO  NO
    +DGARCH/whut/3_22650_611942629.dbf                           NO  NO
    +DGARCH/whut/3_22649_611942629.dbf                           NO  NO
    +DGARCH/whut/3_22648_611942629.dbf                           NO  NO
    +DGARCH/whut/3_22648_611942629.dbf                           NO  NO
    +DGARCH/whut/3_22648_611942629.dbf                           NO  YES
    +DGARCH/whut/3_22291_611942629.dbf                           YES YES
    +DGARCH/whut/2_62553_611942629.dbf                           NO  NO
    +DGARCH/whut/2_62552_611942629.dbf                           NO  NO
    +DGARCH/whut/2_62551_611942629.dbf                           NO  NO
    +DGARCH/whut/2_62550_611942629.dbf                           NO  NO
    query the first_change# on the standby db like this :
    SEQUENCE# FIRST_CHANGE# APP ARC
    22646 2983721221 NO YES
    22647 2983911304 NO YES
    22648 2984028173 NO YES
    23813 2984013365 NO YES
    23814 2984118027 NO YES
    62546 2984027708 NO YES
    SEQUENCE# FIRST_CHANGE# APP ARC
    62547 2984163823 NO YES
    23815 2984132128 NO YES
    23816 2984312713 NO YES
    62548 2984255538 NO YES
    62549 2984312692 NO YES
    22649 2984028196 NO YES
    23817 2984351070 NO YES
    then ,how to fix the dataguard and apply the archivelog on standby db ?
    why I can found 2984028173 with 22648,but can not found 2984013192 ??
    and why there have three 22648 with different applied status and deleted status on standby db ???
    Thanks all.

    Thank you for your reply.
    the trc file like this:
    /oracle/admin/xxx/bdump/xxx_mrp0_12863.trc
    Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - 64bit Production
    With the Partitioning, OLAP and Data Mining options
    ORACLE_HOME = /oracle/product/10.2.0/database
    System name:     SunOS
    Node name:     stdb
    Release:     5.9
    Version:     Generic_122300-25
    Machine:     sun4u
    Instance name: xxx
    Redo thread mounted by this instance: 1
    Oracle process number: 27
    Unix process pid: 12863, image: oracle@stdb (MRP0)
    *** SERVICE NAME:() 2009-01-08 15:44:24.179
    *** SESSION ID:(197.3) 2009-01-08 15:44:24.179
    ARCH: Connecting to console port...
    *** 2009-01-08 15:44:24.180 61287 kcrr.c
    MRP0: Background Managed Standby Recovery process started
    *** 2009-01-08 15:44:29.191 1103 krsm.c
    Managed Recovery: Initialization posted.
    *** 2009-01-08 15:44:29.192 61287 kcrr.c
    Managed Standby Recovery starting Real Time Apply
    Recovery target incarnation = 5, activation ID = 721050634
    Influx buffer limit = 152383 (50% x 304766)
    Successfully allocated 3 recovery slaves
    Using 367 overflow buffers per recovery slave
    Start recovery at thread 3 ckpt scn 2984013192 logseq 22648 block 2
    *** 2009-01-08 15:44:31.181
    Media Recovery add redo thread 3
    *** 2009-01-08 15:44:31.181
    Media Recovery add redo thread 1
    *** 2009-01-08 15:44:31.182
    Media Recovery add redo thread 2
    *** 2009-01-08 15:44:31.184 1103 krsm.c
    Managed Recovery: Active posted.
    *** 2009-01-08 15:44:31.838
    Media Recovery Log +DGARCH/whut/3_22648_611942629.dbf
    *** 2009-01-08 15:44:31.851 61287 kcrr.c
    MRP0: Background Media Recovery terminated with error 326
    ORA-00326: log begin at 2984028173, need earlier 2984013192
    ORA-00334: archivelog: '+DGARCH/whut/3_22648_611942629.dbf'
    *** 2009-01-08 15:44:31.851 61287 kcrr.c
    Managed Standby Recovery not using Real Time Apply
    *** 2009-01-08 15:44:31.851
    Media Recovery drop redo thread 3
    *** 2009-01-08 15:44:31.851
    Media Recovery drop redo thread 1
    *** 2009-01-08 15:44:31.851
    Media Recovery drop redo thread 2
    *** 2009-01-08 15:44:34.269 1103 krsm.c
    Managed Recovery: Not Active posted.
    ORA-00326: log begin at 2984028173,need earlier 2984013192
    ORA-00334: archivelog: '+DGARCH/whut/3_22648_611942629.dbf'
    ARCH: Connecting to console port...
    *** 2009-01-08 15:44:34.359 61287 kcrr.c
    MRP0: Background Media Recovery process shutdown
    *** 2009-01-08 15:44:34.359 1103 krsm.c

  • Standby DB not applying logs

    Hi,
    i opened my primary DB using "alter database open resetlogs" after recovering from a power failure crash.
    this caused the log sequence number to reset to 1.
    when i check the standby DB for maximum log sequence applied, it is showing the last log applied before the crash whereas the primary DB has since the recovery, produced over 200 logs.
    how can i get the standby DB to start applying the new log sequence?
    regards,
    Michael

    If you had opened the Primary with a RESETLOGS to a point earlier than the highest log applied on the standby and you cannot flashback the standby, you have to rebuild the standby.
    For example, the Standby has applied Sequence#1411 but the Primary was opened with RECOVER upto Sequence#1409 and RESETLOGS. The Primary has diverged from the Standby so the standby has to be rebuilt.
    If however, the last redo applied to the Standby was lower than the RECOVER and RESETLOGS point on the primary, the Standby should be automatically able to continue. In your case, you say that the Standby hasn't continued. Therefore, I suspect the former (Primary RECOVER and RESETLOGS to a lower SCN/SEQUENCE#).
    See "9.4 Recovering Through the OPEN RESETLOGS Statement" at http://docs.oracle.com/cd/E11882_01/server.112/e25608/manage_ps.htm#i1026480
    Hemant K Chitale

  • Redo data not applied on logical standby database 10g

    after a network problem within the primary and the logical standby database. The redo data is not applied on the logical standby even if all the archived log are sent to it.
    The below is the output from v$archive_gap and DBA_LOGSTDBY_LOG
    SQL> select * from v$archive_gap;
    no rows selected
    SQL> SELECT SEQUENCE#, FIRST_TIME, APPLIED
    FROM DBA_LOGSTDBY_LOG
    ORDER BY SEQUENCE#; 2 3
    SEQUENCE# FIRST_TIME APPLIED
    3937 24-FEB-10 01:48:23 CURRENT
    3938 24-FEB-10 10:31:22 NO
    3939 24-FEB-10 10:31:29 NO
    3940 24-FEB-10 10:31:31 NO
    3941 24-FEB-10 10:33:44 NO
    3942 24-FEB-10 11:54:17 NO
    3943 24-FEB-10 12:05:30 NO
    Any help?
    Thanks

    ORA-00600: internal error code, arguments: [krvxgirp], [], [], [], [], [], [], []
    LOGSTDBY Analyzer process P003 pid=48 OS id=8659 stopped
    Wed Feb 24 16:49:04 2010
    Errors in file /oracle/product/10.2.0/admin/umarket/bdump/oradb_lsp0_8651.trc:
    ORA-12801: error signaled in parallel query server P003
    ORA-00600: internal error code, arguments: [krvxgirp], [], [], [], [], [], [], []
    and below an Warning: Apply error received: ORA-26714: User error encountered while applying. Clearing. from oradb_lsp0_8651.trc
    Thanks

  • Archives are not applying on 2nd standby

    Hi,
    i have one primary and two standby DBs in different servers.
    archives are applying to one standby only,not appling to another.
    what are the things i need to check? please guide me

    Hi,
    archives are not applying that are received from primary
    on standby DB:
    SQL>select SEQUENCE#,APPLIED from v$archived_log;
    UENCE# APP
    393 NO
    387 NO
    388 NO
    389 NO
    on standby ihaven't seen MRP process,but i have given sql comd like
    SQL> alter database recover managed standby database disconnect from session;
    on standby it's displying
    SQL> select PROCESS,STATUS from v$managed_standby;
    PROCESS STATUS
    ARCH CLOSING
    ARCH CLOSING
    RFS WRITING
    RFS RECEIVING
    RFS RECEIVING
    here there is no MRP process,plz tell me where is the mistake.

  • 10gR2 Logical Standby database not applying logs

    No errors are appearing in the logs and I've started the apply process :ALTER DATABASE START LOGICAL STANDBY APPLY but when I query dba_logstdby_log, none of the logs for the last 4 days shows as applied and the first SCN is still listed as current. Any thoughts on where I should start looking?
    the latest event in DBA_LOGSTDBY_EVENTS is the startup of the log mining and apply.
    I do not have standby redo logs so I cannot do real time apply, though I am looking to implementing this. Obviously, this is pretty new to me.

    Sorry I didn't mention this before, the logs are being transferred, I verified their location on the os and it matches the location in the dba_logstdby_log view.

  • Archive logs are being shipped, but are not applied

    Hi everyone,
    Some strange things are happening when I try to configure an Oracle Data Guard setup. Currently I am at the point where the configuration has been completed, and I just need to sync the standby database to the primary one. I can see in the log files that the archive logs are being shipped, but they are not applied on the standby system.
    If I run "recover standby database;" manually in sqlplus I can see that it is trying to apply an archive log which is way too old (ORA-00279: change 9656498443 generated at 04/29/2008 08:45:08 needed for thread 1).
    In the alert log I can also see this error: Warning: Recovery target destination is in a sibling branch of the controlfile checkpoint. Recovery will only recover changes to datafiles.
    At this point I was thinking that the standby database might be on a different incarnation compared to the primary, but this is not the case, they are both in incarnation 6:
    6       6       MVF      4023175798       CURRENT 48493546257 13-06-21
    Does anyone have an idea how this could happen, and how I could fix this issue?
    Thanks, JM.

    The restore did not cause any errors to be displayed, so I assumed everything was ok.
    That's fair enough. 
    One thing I think might cause this behaviour is that the backup on the primary database is incremental,
    Yes...that may be an issue.  Best bet is to re-run your standby creation.....as you are doing.
    With version 11gR2 you also have the option of duplicate from active database which negates the need to copy your backupsets over to do the restore:  I find it a much simpler process than the rman backup, copy files over, restore and then recover process.
    http://www.oracle-base.com/articles/11g/data-guard-setup-11gr2.php
    Something worth considering.

  • 7.5 Standby apply log issue - Cold backup of standby

    We are in the process of migrating to 7.8 from 7.5 and have a 7.5 standby. Needed to test the time is takes to backup from the standby once we go-live on the 7.8 64bit server. Logs have been applied to the 7.5 standby for more than a month just fine prior to doing a "cold" backup test on the standby. Now the logs will not apply to the standby.
    ERR 20039 Log 
    Logrecovery is not allowed, because state of log volume is 'HistoryLost' (log must be cleared)
    2014-05-04 10:02:16 
    0xF28 WRN 20026 Admin
    Initialization of log for 'restore log' failed with 'LogAndDataIncompatible'
    First - backing up the standby in ADMIN mode / cold backup on the standby database, right?  The source and target (standby) have different server names.
    Is it possible to clear the log area or some other process to fix the issue?

    Hi Mike,
    You may need to restore the database with re-intialization and clear the logs
    Refer to the copy steps described in the thread
    Error while recover logs
    Hope this helps.
    Regards,
    Deepak Kori

  • In standby db, can't find sequence number of Last Applied Log.

    Hello,
    Standby database is behind the primary database for over 200 hours, to repaire this, we are using a incremental backup from primary database and a restored control file.
    after starting up standby database, in Grid Control (OEM), can't find "last applied log" sequence number,
    go to that standby, do
    standby> select max(sequence#) from v$archived_log where applied='YES';
    MAX(SEQUENCE#)
    go to primary,
    do
    SQL> select max(sequence#) from v$archived_log where applied='YES';
    MAX(SEQUENCE#)
    83833
    then using OEM grid control, to Verify checks various standby database settings.
    Initializing
    Connected to instance standby_server:standby
    Starting alert log monitor...
    Updating Data Guard link on database homepage...
    Skipping verification of fast-start failover static services check.
    Data Protection Settings:
    Protection mode : Maximum Performance
    Redo Transport Mode settings:
    primary.com: ASYNC
    standby.com: ASYNC
    Checking standby redo log files.....OK
    Checking Data Guard status
    primary.com : Normal
    standby.com : Normal
    Checking inconsistent properties
    Checking agent status
    Checking applied log on standby........WARNING:
    Timed out after 60 seconds waiting for log to be applied.
    Processing completed.
    so how to fix this?
    thanks you very much.
    Edited by: 951932 on Oct 18, 2012 7:44 AM

    Hello;
    Probably nothing to fix. This is a common warning message.
    It even occurs in this example :
    http://www.databasejournal.com/features/oracle/article.php/10893_3826706_2/Oracle-11g-Data-Guard-Grid-Control-Management.htm
    Best Regards
    mseberg

  • Dataguard logs not applied

    Hi,
    We have dataguard on Oracle 10g. The logs are shipped from primary to physical stand by but when I look at "Last Applied Log" under EM on the primary db, I see 0. The logs are shipping but not applied to physical stand by.
    I restarted the standby to mount stage.
    I can tnsping both the database from other servers
    ***** on primary *****
    SELECT name, value FROM gv$parameter WHERE name = 'log_archive_dest_state_1';
    NAME
    VALUE
    log_archive_dest_state_1
    enable
    SELECT name, value FROM gv$parameter WHERE name = 'log_archive_dest_state_2';
    NAME
    VALUE
    log_archive_dest_state_2
    ENABLE
    SELECT name, value FROM gv$parameter WHERE name = 'standby_archive_dest';
    NAME
    VALUE
    standby_archive_dest
    select status, error from v$archive_dest where dest_id=2;
    STATUS ERROR
    VALID
    select switchover_status from v$database;
    SWITCHOVER_STATUS
    SESSIONS ACTIVE
    select protection_mode, protection_level, database_role from v$database;
    PROTECTION_MODE PROTECTION_LEVEL DATABASE_ROLE
    MAXIMUM PERFORMANCE MAXIMUM PERFORMANCE PRIMARY
    SELECT MAX(SEQUENCE#), THREAD# FROM V$ARCHIVED_LOG GROUP BY THREAD#;
    MAX(SEQUENCE#) THREAD#
    4483 1
    SELECT dest_id, valid_type, valid_role, valid_now FROM gv$archive_dest;
    DEST_ID VALID_TYPE VALID_ROLE VALID_NOW
    1 ONLINE_LOGFILE ALL_ROLES YES
    2 ONLINE_LOGFILE PRIMARY_ROLE YES
    ***** on physical stand by *****
    select protection_mode, protection_level, database_role from v$database;
    PROTECTION_MODE PROTECTION_LEVEL DATABASE_ROLE
    MAXIMUM PERFORMANCE MAXIMUM PERFORMANCE PHYSICAL STANDBY
    SELECT MAX(SEQUENCE#), THREAD# FROM V$ARCHIVED_LOG GROUP BY THREAD#;
    MAX(SEQUENCE#) THREAD#
    4483 1
    Can anyone advise what can I check and how can I get the logs to apply on the standy by. The stand by is in mount stage. Thanks

    The alert log for primary does not show any errors:
    LNS: Standby redo logfile selected for thread 1 sequence 4520 for destination LOG_ARCHIVE_DEST_2
    This is in the alert log for standby
    Primary database is in MAXIMUM PERFORMANCE mode
    RFS[11]: Successfully opened standby log 5: '/u02/oradata/prd1/stby_redo_g5_m1.dbf'
    On standby I have the MRP process running:
    $ ps -ef|grep mrp
    oracle 10957 1 0 15:26:48 ? 0:01 ora_mrp0_prd1
    SELECT RECOVERY_MODE FROM V$ARCHIVE_DEST_STATUS WHERE DEST_ID=2 ;
    RECOVERY_MODE
    MANAGED REAL TIME APPLY
    This is from v$dataguard_status
    Remote File Server Warning 0 167 0 NO 20-DEC-07
    RFS[11]: Successfully opened standby log 5: '/u02/oradata/prd1/stby_redo_g5_m1.dbf'
    should I try this as first suggested ?
    alter database recover managed standby database parallel 2 using current logfile disconnect;

  • Standby not applying the online redo logs

    Hi,
    The redo apply process does not seem to apply the current logs to the standby database.
    The output from the query
    Select last_change#, sequence# from v$standby_log;
    LAST_CHANGE# GROUP# SEQUENCE#
    4 0
    10120537 5 8586
    6 0
    7 0
    gives me the current SCN as that of the primary.
    But the CURRENT_SCN from v$database on the standby lags from that of the output above.
    Select CURRENT_SCN from v$database;
    CURRENT_SCN
    10119641
    The STATUS and PROCESS information from the v$managed_standby show the following:
    PROCESS STATUS SEQUENCE#
    ARCH CONNECTED 0
    ARCH CONNECTED 0
    ARCH CONNECTED 0
    ARCH CONNECTED 0
    RFS IDLE 0
    RFS IDLE 0
    RFS IDLE 8586
    RFS IDLE 0
    RFS IDLE 0
    RFS IDLE 0
    RFS IDLE 0
    PROCESS STATUS SEQUENCE#
    MRP0 APPLYING_LOG 8586
    Any thoughts on why the standby has not applied the recived logs from the primary?
    I am currently using version Oracle 11.2.0.2 for Active dataguard setup. I currently have a primary server and one standy server.
    Thanks

    I had sent the output of the queries in the earlier post. Here it is again
    The output for the query
    select thread#, max(sequence#) from v$archived_log group by thread#; (on primary)
    THREAD# MAX(SEQUENCE#)
    1 8585
    The output for
    select thread#, max(sequence#) from v$archived_log where applied = 'YES' group by thread#; (on standby)
    THREAD# MAX(SEQUENCE#)
    1 8585
    Also the query
    select LAST_CHANGE#, STATUS from V$STANDBY_LOG;
    gives me the current scn generated at the primary.
    LAST_CHANGE# STATUS
    10149990 ACTIVE
    10146538 ACTIVE
    10150844 ACTIVE
    But the current_scn from v$database is lagging.
    select current_scn from v$database;
    CURRENT_SCN
    10146535
    Also the query
    select  THREAD#, LOW_SEQUENCE#, HIGH_SEQUENCE# from v$archive_gap;
    returns no rows. So there are no archive logs missing on the standby either.
    So I beleive that the RFS has recieved the logs from the primary but the logs have not been applied at the standby.
    Thanks

  • Dataguard ,redo log not applied

    hi
    i am using oracle dataguard 10g .
    everything was quit fine . but some days later a problem occured . after sequence 128 log is not applied .
    i am using realtime log appled.
    can anybody help me .
    Thanks in advance
    munir .

    Hi,
    Is your standby database a physical or a logical standby ???
    Is the standby database in recover mode?
    What is the current log sequence number on your primary database?
    Place your standby database in recovery mode (if it is not) and restore arhcive logs on the standby database generated after log seq. 128
    Regards
    Asif Momen
    http://momendba.blogspot.com

Maybe you are looking for

  • Additional instruments won't download

    I have Lion (10.7.3) and the latest Garage Band (6.0.5). I've had Garage Band installed for a long time. I went to try it out today, and would like to install the software instruments that (apparently) aren't included on the DVD anymore. When I click

  • Download iTunes 11 screwed my pc up

    I just downloaded iTunes 11 onto my pc (win7) and it screwed it up ie.  error message-  missing msvcr80.dll   Now I can't access any of my music.  Just in case it was just a coincidence I upgraded my laptop to iTunes 11 with the same results.  I'm mi

  • Approach of Java Bean Model: What is the best way?

    Hi Experts, In our project, we are trying to connect Oracle Database and display the tables and information in it on Web Dynpro View. For this I'm following 4 step procedure broadly: 1. Java DC: a) Create Class files --> one for connecting Database (

  • Showing headers in portal for MSS

    hi       when i login to portal , i have MSS role  , and when i click on the MSS role , i need overview, team  as the header , i dont want Budgets and plannings as part of header and  also when i click the team  or overview  , there related  services

  • Adobe Encore AC3 question

    Does anyone have any experience with Adobe's AC3 encoder - is it comparable to Apcak in terms of normalizing and mastering audio tracks...thanks.