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                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               

Similar Messages

  • 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.

  • 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 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

  • New standby not applying archive log

    I have just created standby database....but its not applying archive log...
    when I checked the alerlog file of standby....
    ora-19527 physical standby redo log must be renamed

    yes, I have created at onlien redo logs at standby database..
    what is test and test?
    i saw one command like this...
    log_file_name_convert= ((''/u01/oradata/prod'', ''/u01/oradata/standby''),(''/u02/oradata/prod'', ''/u02/oradata/standby''))
    My Primary DB name is OraclePM
    My Standby DB name is OracleDR
    I have placed all redo logs in direcrtory (D:\oracle\product\logs\ ) the directory structure for both databases is same... I have created 3 additionals redo logs at standby database...
    How can I edit my standby init file...

  • 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

  • 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

  • 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.

  • Standby Not Applying After Outage

    We have a 11r2 primary and standby running on RHEL 5. The primary lost network connectivity for a time and VMWare locked up. The VM admin restarted the primary VM (it was a hard-boot). This all happened while I was gone and when I came into work, the primary database appeared to be working. I decided to dig deeper and check out the standby.
    On the standby...
    SQL> select * from v$archive_gap;
    Thread#: 1
    low_sequence: 123120
    high_sequence: 123120
    DGMGRL> show configuration
    Configuration - prodDB
         Protection Mode: MaxPerformance
         Databases:
              prodDB - Primary database
              prodDB2 - Physical standby database
    Fast-Start Failover: DISABLED
    Configuration Status:
    SUCCESS
    SQL> select count(*) from v$archived_log where applied='NO';
    Count(*): 107
    SQL> select process, client_process, thread#, sequence#, block#, status from v$managed_standby where process='MRP0' or client_process='LGWR';
    Process: MRP0
    Client_Process: N/A
    Thread#: 1
    Sequence#: 123120
    Block#: 0
    Status: WAIT_FOR_LOG
    Process: RFS
    Client_Process: LGWR
    Thread#: 1
    Sequence#: 128315
    Block#: 4686
    Status: IDLE
    DGMGRL> show database prodDB2;
    Role: PHYSICAL STANDBY
    Intended State: APPLY-ON
    Transport Lag: 2 days 3 minutes 53 seconds
    Apply Lag: 2 days 3 minutes 53 seconds
    Real Time Query: OFF
    Instance(s): prodDB
    It appears all is well (just very far behind) but when I run the last code block (show database prodDB2;) again ...
    DGMGRL> show database prodDB2;
    Role: PHYSICAL STANDBY
    Intended State: APPLY-ON
    Transport Lag: 2 days 1 hour(s) 42 minutes 37 seconds
    Apply Lag: 2 days 1 hour(s) 42 minutes 37 seconds
    Real Time Query: OFF
    Instance(s): prodDB
    ...it looks as if the massive backlog is just increasing. How can I confirm that everything that things are going well? I am still learning Data Guard.
    Thank you

    Hello;
    It shows 9851 logs behind. If you created the standby more than once then the query could be giving incorrect information. If this is the case then check from the standby. For example
    PRIMARY SIDE
    /home/oracle:PRIMARY >sqlplus "/ as sysdba"
    SQL*Plus: Release 11.2.0.3.0 Production on Thu Sep 5 16:14:06 2013
    Copyright (c) 1982, 2011, Oracle. All rights reserved.
    Connected to:
    Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
    SQL> select max(sequence#) from v$archived_log where NEXT_TIME > sysdate -1;
    MAX(SEQUENCE#)
      766
    SQL>
    STANDBY SIDE
    /home/oracle:STANDBY >sqlplus "/ as sysdba"
    SQL*Plus: Release 11.2.0.3.0 Production on Thu Sep 5 16:14:40 2013
    Copyright (c) 1982, 2011, Oracle. All rights reserved.
    Connected to:
    Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
    SQL> select max(sequence#) from v$archived_log where NEXT_TIME > sysdate -1;
    MAX(SEQUENCE#)
      766
    If you do this is the difference  really 9851?
    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;

  • 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

  • Redo log files are not applying to standby database

    Hi everyone!!
    I have created standby database on same server ( windows XP) and using oracle 11g . I want to synchronize my standby database with primary database . So I tried to apply redo logs from primary to standby database as follow .
    My standby database is open and Primary database is not started (instance not started) because only one database can run in Exclusive Mode as DB_NAME is same for both database.  I run the following command on the standby database.
                SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION;
    It returns "Database altered" . But when I checked the last archive log on primary database, its sequence is 189 while on standby database it is 177. That mean archived redo logs are not applied on standby database.
    The tnsnames.ora file contains entry for both service primary & standby database and same service has been used to transmit and receive redo logs.
    1. How to resolve this issue ?
    2.Is it compulsory to have Primary database open ?
    3. I have created standby  control file by using  command
              SQL> ALTER DATABASE CREATE STANDBY CONTROLFILE AS ‘D:\APP\ORACLE\ORADATA\TESTCAT\CONTROLFILE\CONTROL_STAND1.CTL‘;
    So database name in the standby control file is same as primary database name (PRIM). And hence init.ora file of standby database also contains DB_NAME = 'PRIM' parameter. I can't change it because it returns error of mismatch database name on startup. Should  I have different database name for both or existing one is correct ?
    Can anybody help me to come out from this stuck ?
    Thanks & Regards
    Tushar Lapani

    Thank you Girish. It solved  my redo apply problem. I set log_archive_dest parameter again and then I checked archive redo log sequence number. It was same for both primary and standby database. But still table on standby database is not being refresh.
    I did following scenario.
    1.  Inserted 200000 rows in emp table of Scott user on Primary database and commit changes.
    2. Then I synchronized standby database by using Alter database command. And I also verify that archive log sequence number is same for both database. It mean archived logs from primary database has been applied to standby database.
    3. But when I count number of rows in emp table of scott user on standby database, it returns only 14 rows even of redo log has been applied.
    So my question is why changes made to primary database is not reflected on standby database although redo logs has been applied ?
    Thanks

  • Archive log registered,but showing as not applied in standby db + oracle 9i

    Hi all,
    In my standby database some of the archive log files are not applied.found through the following command
    SQL > select sequence#,applied from v$archived_log where applied='NO';
    sequence# APP FIRST_TIME
    18425 NO 05-FEB-10
    but when try to register manually
    SQL > alter database register logfile '/disk12/arch/A00123000018425.arc';
    ERROR at line 1
    ORA-16089:archive log has already been registered.
    "recover standby database" also asking for the new archive file. how will i apply that?
    any solutions?

    user11919409 wrote:
    I have did that so many times from 05-feb-10 onwards.
    even then only one archive gap???
    or only one is not applied? if yes may be archive file which exist at standby may be corrupt try to restore it from backup and recover.
    also check for some clues at logs at standby and primary.. what actually happen. if archive gap is huge and you have all archvies then you may have to do manual recovery then keep it back to auto recovery mode.
    Hope that may help you.
    Anil Malkai

  • Logs not applying on Standby Database

    I am afraid I am back.
    I now have a primary database and a standby database and logs are being shipped but not applied. Done some research and I have got to the point where in my alert log I find the following when I try to start MRP:
    Fri Jun 29 15:03:40 2012
    alter database recover managed standby database disconnect from session
    Attempt to start background Managed Standby Recovery process (SAPDS)
    Fri Jun 29 15:03:40 2012
    MRP0 started with pid=29, OS id=23272
    MRP0: Background Managed Standby Recovery process started (SAPDS)
    started logmerger process
    Fri Jun 29 15:03:45 2012
    Managed Standby Recovery not using Real Time Apply
    Read of datafile '/var/hpsrp/drforp03/oradata/u04/SAPDS/DRFSAPDS/sysaux01.dbf' (fno 2) header failed with ORA-01206
    Rereading datafile 2 header failed with ORA-01206
    MRP0: Background Media Recovery terminated with error 1110
    Errors in file /var/hpsrp/drforp03/oradata/u04/SAPDS/admin/diag/rdbms/drfsapds/SAPDS/trace/SAPDS_pr00_23308.trc:
    ORA-01110: data file 2: '/var/hpsrp/drforp03/oradata/u04/SAPDS/DRFSAPDS/sysaux01.dbf'
    ORA-01122: database file 2 failed verification check
    ORA-01110: data file 2: '/var/hpsrp/drforp03/oradata/u04/SAPDS/DRFSAPDS/sysaux01.dbf'
    ORA-01206: file is not part of this database - wrong database id
    Recovery Slave PR00 previously exited with exception 1110
    Errors in file /var/hpsrp/drforp03/oradata/u04/SAPDS/admin/diag/rdbms/drfsapds/SAPDS/trace/SAPDS_mrp0_23272.trc:
    ORA-01110: data file 2: '/var/hpsrp/drforp03/oradata/u04/SAPDS/DRFSAPDS/sysaux01.dbf'
    ORA-01122: database file 2 failed verification check
    ORA-01110: data file 2: '/var/hpsrp/drforp03/oradata/u04/SAPDS/DRFSAPDS/sysaux01.dbf'
    ORA-01206: file is not part of this database - wrong database id
    MRP0: Background Media Recovery process shutdown (SAPDS)
    Completed: alter database recover managed standby database disconnect from session
    My question therefore is how can I get out of this and get my logs to apply on standby?

    Hello again;
    Do you think if I tried to repeat the duplicate?
    Yes I think you should do this.
    Give me a few minutes and I will review my Word document and provide a step by step overview here as insurance.
    I always cleanup the standby before trying another dup
    OVERVIEW
    Step 1 - Password file fro standby - Copy from primary and rename
    Step 2 - Directory Structure on the remote server - Make sure noting is missing
    Step 3 - Oracle Net Setup - entry for the CLONE in your TNSNAMES.ORA on both servers
    Step 4 - SID_LIST_LISTENER addition ( assumes listener named LISTENER )
    Step 5 - Timeouts set in listener.ora and sqlnet.ora Both Servers
    Step 6 - Initialization Parameter File for the Auxiliary Instance
    Step 7 - Set SID for Auxiliary Instance
    Step 8 - Create an SPFILE for the new database by using a pfile with the INIT settings
    Step 9 - Shutdown and startup nomount on new Spfile ( Auxiliary Instance )
    Step 10 - Start RMAN and run the DUPLICATE Command
    SID_LIST_LISTENER Example from mine
    SID_LIST_LISTENER =
       (SID_LIST =
           (SID_DESC =
           (SID_NAME = PLSExtProc)
           (ORACLE_HOME = /u01/app/oracle/product/11.2.0.2)
           (PROGRAM = extproc)
           (SID_DESC =
           (global_dbname = CLONE.hostname)
           (ORACLE_HOME = /u01/app/oracle/product/11.2.0.2)
           (sid_name = CLONE)
    Prevent Timeouts
    Add these to both servers
    To listener.ora
    INBOUND_CONNECT_TIMEOUT_ = 120
    To sqlnet.ora
    SQLNET.INBOUND_CONNECT_TIMEOUT = 120
    Then stop and start the listener.
    RMAN
    $ORACLE_HOME/bin/rman target=sys/@primary auxiliary=sys/@standby
    Connect should return something like this
    connected to target database: RECOVER9 (DBID=3806912436)
    connected to auxiliary database: CLONE (not mounted)RMAN>duplicate target database for standby from active database NOFILENAMECHECK;
    INIT Extras
    To avoid ORA-09925 make sure the PFILE has audit_file_dest and core_dump_dest set
    Best Regards
    mseberg
    Edited by: mseberg on Jun 29, 2012 11:12 AM

  • All logs received but not applied | Physical Standby Database

    All,
    Need your help....
    We have physical standby database setup as below
    Primary : 2 node RAC
    Stdby : Standalone physical standby database.
    When I verify the stdby database status, I could see all the logs are received from primary but still not applied many.. Could any one please help me what is the issue and how to resolve it ...?
    Primary :
    =====
    SQL> SELECT THREAD# "Thread",SEQUENCE# "Last Sequence Generated"
    FROM V$ARCHIVED_LOG
    WHERE (THREAD#,FIRST_TIME ) IN (SELECT THREAD#,MAX(FIRST_TIME) FROM V$ARCHIVED_LOG GROUP BY THREAD#)
    ORDER BY 1 2 3 4 ;
    Thread Last Sequence Generated
    1 8073
    1 8073
    2 4521
    2 4521
    stdby:
    ====
    SQL> SELECT ARCH.THREAD# "Thread",
    2 ARCH.SEQUENCE# "Last Sequence Received",
    3 APPL.SEQUENCE# "Last Sequence Applied",
    4 (ARCH.SEQUENCE# - APPL.SEQUENCE#) "Difference"
    5 FROM
    6 (SELECT THREAD# ,SEQUENCE# FROM V$ARCHIVED_LOG WHERE (THREAD#,FIRST_TIME ) IN
    7 (SELECT THREAD#,MAX(FIRST_TIME) FROM V$ARCHIVED_LOG GROUP BY THREAD#)) ARCH,
    8 (SELECT THREAD# ,SEQUENCE# FROM V$LOG_HISTORY WHERE (THREAD#,FIRST_TIME ) IN
    (SELECT THREAD#,MAX(FIRST_TIME) FROM V$LOG_HISTORY GROUP BY THREAD#)) APPL
    9 10 WHERE ARCH.THREAD# = APPL.THREAD# ORDER BY 1;
    Thread Last Sequence Received Last Sequence Applied Difference
    1 8073 8055 18
    2 4521 4510 11
    --Below are tailed messages from standby alert log:
    Fri Nov 04 10:45:15 2011
    ARCH: Archival stopped, error occurred. Will continue retrying
    ORACLE Instance BWFCCSTD - Archival Error
    ORA-16014: log 6 sequence# 8058 not archived, no available destinations
    ORA-00312: online log 6 thread 1: '+ASM_DATA01/bwfccstd/onlinelog/group_6.418.766235259'
    ORA-00312: online log 6 thread 1: '+ASM_FRA01/bwfccstd/onlinelog/group_6.307.766235263'
    Fri Nov 04 10:50:15 2011
    Archiver process freed from errors. No longer stopped
    Fri Nov 04 10:50:15 2011
    ARCH: Archival stopped, error occurred. Will continue retrying
    ORACLE Instance BWFCCSTD - Archival Error
    ORA-16014: log 6 sequence# 8058 not archived, no available destinations
    ORA-00312: online log 6 thread 1: '+ASM_DATA01/bwfccstd/onlinelog/group_6.418.766235259'
    ORA-00312: online log 6 thread 1: '+ASM_FRA01/bwfccstd/onlinelog/group_6.307.766235263'
    Fri Nov 04 10:50:15 2011
    Archiver process freed from errors. No longer stopped
    Fri Nov 04 10:55:15 2011
    ARCH: Archival stopped, error occurred. Will continue retrying
    ORACLE Instance BWFCCSTD - Archival Error
    ORA-16014: log 6 sequence# 8058 not archived, no available destinations
    ORA-00312: online log 6 thread 1: '+ASM_DATA01/bwfccstd/onlinelog/group_6.418.766235259'
    ORA-00312: online log 6 thread 1: '+ASM_FRA01/bwfccstd/onlinelog/group_6.307.766235263'
    Fri Nov 04 11:00:15 2011
    Archiver process freed from errors. No longer stopped
    Fri Nov 04 11:00:15 2011
    ARCH: Archival stopped, error occurred. Will continue retrying
    ORACLE Instance BWFCCSTD - Archival Error
    ORA-16014: log 6 sequence# 8058 not archived, no available destinations
    ORA-00312: online log 6 thread 1: '+ASM_DATA01/bwfccstd/onlinelog/group_6.418.766235259'
    ORA-00312: online log 6 thread 1: '+ASM_FRA01/bwfccstd/onlinelog/group_6.307.766235263'
    Fri Nov 04 11:00:15 2011
    Archiver process freed from errors. No longer stopped
    Fri Nov 04 11:05:16 2011
    ARCH: Archival stopped, error occurred. Will continue retrying
    ORACLE Instance BWFCCSTD - Archival Error
    ORA-16014: log 6 sequence# 8058 not archived, no available destinations
    ORA-00312: online log 6 thread 1: '+ASM_DATA01/bwfccstd/onlinelog/group_6.418.766235259'
    ORA-00312: online log 6 thread 1: '+ASM_FRA01/bwfccstd/onlinelog/group_6.307.766235263'
    Fri Nov 04 11:05:16 2011
    Archiver process freed from errors. No longer stopped

    Primary:
    =====
    SQL> archive log list;
    Database log mode Archive Mode
    Automatic archival Enabled
    Archive destination +ASM_FRA01
    Oldest online log sequence 8073
    Next log sequence to archive 8074
    Current log sequence 8074
    SQL>
    Stdby:
    =====
    SQL> archive log list;
    Database log mode Archive Mode
    Automatic archival Enabled
    Archive destination ?/dbs/arch
    Oldest online log sequence 8074
    Next log sequence to archive 0
    Current log sequence 8074
    Enough space is available :
    =================
    SQL> set lines 180 pages 50000;
    SQL> set lines 100
    col name format a60
    select name
    , floor(space_limit / 1024 / 1024) "Size MB"
    , ceil(space_used / 1024 / 1024) "Used MB"
    from v$recovery_file_dest
    order by nameSQL> SQL> 2 3 4 5 ;
    NAME Size MB Used MB
    +ASM_FRA01                                                        70000        531
    Edited by: 889828 on 2011/11/04 2:26 AM

Maybe you are looking for

  • Tabbed Panel - prevent page content being pushed down

    What is the setting to prevent an open tab from pushing content down that is below it. Rather, just have the tabbed content be presented above the content on the page. In other words, have it behave like a menu bar with drop down boxes. Thanks for an

  • Email on Idoc Failure with Status 56 64 68 69 70

    We have standard inbound idoc processing for Basic Type : DELVRY01 and Message Type : DESADV using the function module IDOC_INPUT_DESADV1. We currently have a requirement to send an email, when any of these type of Idocs fail with status 56, 64, 68,

  • Forms in a document

    Hi, I want to use the form I developed in a book, it is a Travel Log sheet. THe forms data will be exported to a spreadsheet. I Want to also go the other way and use some data from the spreadsheet into the form, the date. Unless acrobat can populate

  • Distributed Cache gets are very time consuming!!!!!

    We have an application that uses Coherence as a distributed partitioned cache server. Our problem is that the access to the near cache is very fast but the access to the remote servers is very cpu consuming (maybe for the deserialization of the objec

  • Command or utility to archive files unmodified in over 730 days

    Hi, I need to find a way to archive files that are over 2 years old, ideally on a weekly basis, and have them moved to an archive volume, maintaining folder structure. I'm not good at writing scripts, and beyond that, even once i locate all of the fi