Archive logs not applied on logical database.

I have 10.2.04 oracle logical dataguard on windows:
The logs are trasported smoothly from primary to stanby;
But they are not applied to the logical standby;
There are no GAPS.
This is the message i got from DG broker wehn i ran verify configuration
Initializing
Connected to instance I-AG1101:tito
Starting alert log monitor...
Updating Data Guard link on database homepage...
Data Protection Settings:
Protection mode : Maximum Performance
Redo Transport Mode settings:
hclistg: ASYNC
hclidg: ASYNC
Checking standby redo log files.....OK
Checking Data Guard status
hclistg : Normal
hclidg : Normal
Checking Inconsistent Properties
Checking agent status
hclistg ... OK
hclidg ... WARNING: No credentials available for target. I-SAG1151
Attempting agent ping ... OK
Switching log file 420.Done
Checking applied log on hclidg.......WARNING:
Timed out after 60 seconds waiting for log to be applied.
Processing completed.
This is the results of query: SELECT SEQUENCE#, FIRST_TIME, APPLIED
FROM DBA_LOGSTDBY_LOG
ORDER BY SEQUENCE#;
SEQUENCE#|FIRST_TIME|APPLIED
391|3/31/2010 1:08:27 PM|CURRENT
392|3/31/2010 3:10:19 PM|NO
393|3/31/2010 3:47:05 PM|NO
394|3/31/2010 3:47:13 PM|NO
395|3/31/2010 3:47:40 PM|NO
396|3/31/2010 3:47:46 PM|NO
397|3/31/2010 3:50:14 PM|NO
398|3/31/2010 3:50:20 PM|NO
399|3/31/2010 3:54:01 PM|NO
400|3/31/2010 3:54:36 PM|NO
401|3/31/2010 3:54:43 PM|NO
402|3/31/2010 3:56:24 PM|NO
403|3/31/2010 3:56:30 PM|NO
404|3/31/2010 4:00:46 PM|NO
405|3/31/2010 4:34:03 PM|NO
406|3/31/2010 4:35:31 PM|NO
407|3/31/2010 5:38:57 PM|NO
408|4/1/2010 7:30:25 AM|NO
409|4/1/2010 11:45:23 AM|NO
410|4/1/2010 11:47:06 AM|NO
411|4/1/2010 2:26:25 PM|NO
412|4/1/2010 2:26:43 PM|NO
413|4/1/2010 2:26:44 PM|NO
414|4/1/2010 2:28:13 PM|NO
415|4/1/2010 5:08:12 PM|NO
416|4/1/2010 5:08:19 PM|NO
417|4/1/2010 5:08:52 PM|NO
418|4/2/2010 10:31:19 AM|NO
419|4/2/2010 10:35:06 AM|NO
420|4/2/2010 11:24:27 AM|NO
Please help,,,

i am getting this error when i run alter database mount standby database
SQL> shutdown immediate;
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup nomount;
ORACLE instance started.
Total System Global Area 1610612736 bytes
Fixed Size 1299288 bytes
Variable Size 545262760 bytes
Database Buffers 1056964608 bytes
Redo Buffers 7086080 bytes
SQL> alter database mount standby database;
alter database mount standby database
ERROR at line 1:
ORA-01665: control file is not a standby control file
I configured my logical DG using Grid control

Similar Messages

  • Archive Logs NOT APPLIED but transferred

    Hi Gurus,
    I have configured Primary & Standby databases in same Oracle Home. OS version is OEL 5. Database version is 10.2.0.1. I could get the archive logs in the standby site but they are not getting applied in the standby database. I don't have OLAP installed in my database version. Would this create this issue? However I attached my primary alert log details below for your reference:
    Thu Aug 30 23:55:37 2012
    Starting ORACLE instance (normal)
    Cannot determine all dependent dynamic libraries for /proc/self/exe
    Unable to find dynamic library libocr10.so in search paths
    RPATH = /ade/aime1_build2101/oracle/has/lib/:/ade/aime1_build2101/oracle/lib/:/ade/aime1_build2101/oracle/has/lib/:
    LD_LIBRARY_PATH is not set!
    The default library directories are /lib and /usr/lib
    Unable to find dynamic library libocrb10.so in search paths
    Unable to find dynamic library libocrutl10.so in search paths
    Unable to find dynamic library libocrutl10.so in search paths
    LICENSE_MAX_SESSION = 0
    LICENSE_SESSIONS_WARNING = 0
    Picked latch-free SCN scheme 2
    Autotune of undo retention is turned on.
    IMODE=BR
    ILAT =18
    LICENSE_MAX_USERS = 0
    SYS auditing is disabled
    ksdpec: called for event 13740 prior to event group initialization
    Starting up ORACLE RDBMS Version: 10.2.0.1.0.
    System parameters with non-default values:
    processes = 150
    sga_target = 289406976
    control_files = /home/oracle/oracle/product/10.2.0/db_1/oradata/newprim/control01.ctl, /home/oracle/oracle/product/10.2.0/db_1/oradata/newprim/control02.ctl, /home/oracle/oracle/product/10.2.0/db_1/oradata/newprim/control03.ctl
    db_file_name_convert = /home/oracle/oracle/product/10.2.0/db_1/oradata/newstand, /home/oracle/oracle/product/10.2.0/db_1/oradata/newprim
    log_file_name_convert = /home/oracle/oracle/product/10.2.0/db_1/oradata/newstand, /home/oracle/oracle/product/10.2.0/db_1/oradata/newprim, /home/oracle/oracle/product/10.2.0/db_1/flash_recovery_area/NEWSTAND/onlinelog, /home/oracle/oracle/product/10.2.0/db_1/flash_recovery_area/NEWPRIM/onlinelog
    db_block_size = 8192
    compatible = 10.2.0.1.0
    log_archive_config = DG_CONFIG=(newprim,newstand)
    log_archive_dest_1 = LOCATION=/home/oracle/oracle/product/10.2.0/db_1/oradata/newprim/arch/
    VALID_FOR=(ALL_LOGFILES,ALL_ROLES)
    DB_UNIQUE_NAME=newprim
    log_archive_dest_2 = SERVICE=newstand LGWR ASYNC VALID_FOR=(online_logfiles,primary_role) DB_UNIQUE_NAME=newstand
    log_archive_dest_state_1 = enable
    log_archive_dest_state_2 = enable
    log_archive_max_processes= 30
    log_archive_format = %t_%s_%r.dbf
    fal_client = newprim
    fal_server = newstand
    db_file_multiblock_read_count= 16
    db_recovery_file_dest = /home/oracle/oracle/product/10.2.0/db_1/flash_recovery_area
    db_recovery_file_dest_size= 2147483648
    standby_file_management = AUTO
    undo_management = AUTO
    undo_tablespace = UNDOTBS1
    remote_login_passwordfile= EXCLUSIVE
    db_domain =
    dispatchers = (PROTOCOL=TCP) (SERVICE=newprimXDB)
    job_queue_processes = 10
    background_dump_dest = /home/oracle/oracle/product/10.2.0/db_1/admin/newprim/bdump
    user_dump_dest = /home/oracle/oracle/product/10.2.0/db_1/admin/newprim/udump
    core_dump_dest = /home/oracle/oracle/product/10.2.0/db_1/admin/newprim/cdump
    audit_file_dest = /home/oracle/oracle/product/10.2.0/db_1/admin/newprim/adump
    db_name = newprim
    db_unique_name = newprim
    open_cursors = 300
    pga_aggregate_target = 95420416
    PMON started with pid=2, OS id=28091
    PSP0 started with pid=3, OS id=28093
    MMAN started with pid=4, OS id=28095
    DBW0 started with pid=5, OS id=28097
    LGWR started with pid=6, OS id=28100
    CKPT started with pid=7, OS id=28102
    SMON started with pid=8, OS id=28104
    RECO started with pid=9, OS id=28106
    CJQ0 started with pid=10, OS id=28108
    MMON started with pid=11, OS id=28110
    MMNL started with pid=12, OS id=28112
    Thu Aug 30 23:55:38 2012
    starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
    starting up 1 shared server(s) ...
    Thu Aug 30 23:55:38 2012
    ALTER DATABASE MOUNT
    Thu Aug 30 23:55:42 2012
    Setting recovery target incarnation to 2
    Thu Aug 30 23:55:43 2012
    Successful mount of redo thread 1, with mount id 1090395834
    Thu Aug 30 23:55:43 2012
    Database mounted in Exclusive Mode
    Completed: ALTER DATABASE MOUNT
    Thu Aug 30 23:55:43 2012
    ALTER DATABASE OPEN
    Thu Aug 30 23:55:43 2012
    LGWR: STARTING ARCH PROCESSES
    ARC0 started with pid=16, OS id=28122
    ARC1 started with pid=17, OS id=28124
    ARC2 started with pid=18, OS id=28126
    ARC3 started with pid=19, OS id=28128
    ARC4 started with pid=20, OS id=28133
    ARC5 started with pid=21, OS id=28135
    ARC6 started with pid=22, OS id=28137
    ARC7 started with pid=23, OS id=28139
    ARC8 started with pid=24, OS id=28141
    ARC9 started with pid=25, OS id=28143
    ARCa started with pid=26, OS id=28145
    ARCb started with pid=27, OS id=28147
    ARCc started with pid=28, OS id=28149
    ARCd started with pid=29, OS id=28151
    ARCe started with pid=30, OS id=28153
    ARCf started with pid=31, OS id=28155
    ARCg started with pid=32, OS id=28157
    ARCh started with pid=33, OS id=28159
    ARCi started with pid=34, OS id=28161
    ARCj started with pid=35, OS id=28163
    ARCk started with pid=36, OS id=28165
    ARCl started with pid=37, OS id=28167
    ARCm started with pid=38, OS id=28169
    ARCn started with pid=39, OS id=28171
    ARCo started with pid=40, OS id=28173
    ARCp started with pid=41, OS id=28175
    ARCq started with pid=42, OS id=28177
    ARCr started with pid=43, OS id=28179
    ARCs started with pid=44, OS id=28181
    Thu Aug 30 23:55:44 2012
    ARC0: Archival started
    ARC1: Archival started
    ARC2: Archival started
    ARC3: Archival started
    ARC4: Archival started
    ARC5: Archival started
    ARC6: Archival started
    ARC7: Archival started
    ARC8: Archival started
    ARC9: Archival started
    ARCa: Archival started
    ARCb: Archival started
    ARCc: Archival started
    ARCd: Archival started
    ARCe: Archival started
    ARCf: Archival started
    ARCg: Archival started
    ARCh: Archival started
    ARCi: Archival started
    ARCj: Archival started
    ARCk: Archival started
    ARCl: Archival started
    ARCm: Archival started
    ARCn: Archival started
    ARCo: Archival started
    ARCp: Archival started
    ARCq: Archival started
    ARCr: Archival started
    ARCs: Archival started
    ARCt: Archival started
    LGWR: STARTING ARCH PROCESSES COMPLETE
    ARCt started with pid=45, OS id=28183
    LNS1 started with pid=46, OS id=28185
    Thu Aug 30 23:55:48 2012
    Thread 1 advanced to log sequence 68
    Thu Aug 30 23:55:48 2012
    ARCo: Becoming the 'no FAL' ARCH
    ARCo: Becoming the 'no SRL' ARCH
    Thu Aug 30 23:55:48 2012
    ARCp: Becoming the heartbeat ARCH
    Thu Aug 30 23:55:48 2012
    Thread 1 opened at log sequence 68
    Current log# 1 seq# 68 mem# 0: /home/oracle/oracle/product/10.2.0/db_1/oradata/newprim/redo01.log
    Successful open of redo thread 1
    Thu Aug 30 23:55:48 2012
    MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
    Thu Aug 30 23:55:48 2012
    SMON: enabling cache recovery
    Thu Aug 30 23:55:48 2012
    Successfully onlined Undo Tablespace 1.
    Thu Aug 30 23:55:48 2012
    SMON: enabling tx recovery
    Thu Aug 30 23:55:49 2012
    Database Characterset is WE8ISO8859P1
    replication_dependency_tracking turned off (no async multimaster replication found)
    Starting background process QMNC
    QMNC started with pid=47, OS id=28205
    Thu Aug 30 23:55:49 2012
    Error 1034 received logging on to the standby
    Thu Aug 30 23:55:49 2012
    Errors in file /home/oracle/oracle/product/10.2.0/db_1/admin/newprim/bdump/newprim_arc1_28124.trc:
    ORA-01034: ORACLE not available
    FAL[server, ARC1]: Error 1034 creating remote archivelog file 'newstand'
    FAL[server, ARC1]: FAL archive failed, see trace file.
    Thu Aug 30 23:55:49 2012
    Errors in file /home/oracle/oracle/product/10.2.0/db_1/admin/newprim/bdump/newprim_arc1_28124.trc:
    ORA-16055: FAL request rejected
    ARCH: FAL archive failed. Archiver continuing
    Thu Aug 30 23:55:49 2012
    ORACLE Instance newprim - Archival Error. Archiver continuing.
    Thu Aug 30 23:55:49 2012
    db_recovery_file_dest_size of 2048 MB is 9.77% used. This is a
    user-specified limit on the amount of space that will be used by this
    database for recovery-related files, and does not reflect the amount of
    space available in the underlying filesystem or ASM diskgroup.
    Thu Aug 30 23:55:50 2012
    Errors in file /home/oracle/oracle/product/10.2.0/db_1/admin/newprim/udump/newprim_ora_28120.trc:
    ORA-00604: error occurred at recursive SQL level 1
    ORA-12663: Services required by client not available on the server
    ORA-36961: Oracle OLAP is not available.
    ORA-06512: at "SYS.OLAPIHISTORYRETENTION", line 1
    ORA-06512: at line 15
    Thu Aug 30 23:55:50 2012
    Completed: ALTER DATABASE OPEN
    Thu Aug 30 23:56:33 2012
    FAL[server]: Fail to queue the whole FAL gap
    GAP - thread 1 sequence 1-33
    DBID 1090398314 branch 792689455
    Kindly, guide me please..
    -Vimal.

    CKPT: The trace file details are added below for your reference;
    /home/oracle/oracle/product/10.2.0/db_1/admin/newprim/bdump/newprim_arc1_28124.trc
    Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
    With the Partitioning and Data Mining options
    ORACLE_HOME = /home/oracle/oracle/product/10.2.0/db_1
    System name:     Linux
    Node name:     localhost.localdomain
    Release:     2.6.18-8.el5PAE
    Version:     #1 SMP Tue Jun 5 23:39:57 EDT 2007
    Machine:     i686
    Instance name: newprim
    Redo thread mounted by this instance: 1
    Oracle process number: 17
    Unix process pid: 28124, image: [email protected] (ARC1)
    *** SERVICE NAME:() 2012-08-30 23:55:48.314
    *** SESSION ID:(155.1) 2012-08-30 23:55:48.314
    kcrrwkx: nothing to do (start)
    Redo shipping client performing standby login
    OCISessionBegin failed -1
    .. Detailed OCI error val is 1034 and errmsg is 'ORA-01034: ORACLE not available
    *** 2012-08-30 23:55:49.723 60679 kcrr.c
    Error 1034 received logging on to the standby
    Error 1034 connecting to destination LOG_ARCHIVE_DEST_2 standby host 'newstand'
    Error 1034 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'newstand'
    ORA-01034: ORACLE not available
    *** 2012-08-30 23:55:49.723 58941 kcrr.c
    kcrrfail: dest:2 err:1034 force:0 blast:1
    kcrrwkx: unknown error:1034
    ORA-16055: FAL request rejected
    ARCH: Connecting to console port...
    ARCH: Connecting to console port...
    kcrrwkx: nothing to do (end)
    *** 2012-08-31 00:00:43.417
    kcrrwkx: nothing to do (start)
    *** 2012-08-31 00:05:43.348
    kcrrwkx: nothing to do (start)
    *** 2012-08-31 00:10:43.280
    kcrrwkx: nothing to do (start)
    *** 2012-08-31 00:15:43.217
    kcrrwkx: nothing to do (start)
    *** 2012-08-31 00:20:43.160
    kcrrwkx: nothing to do (start)
    *** 2012-08-31 00:25:43.092
    kcrrwkx: nothing to do (start)
    *** 2012-08-31 00:30:43.031
    kcrrwkx: nothing to do (start)
    *** 2012-08-31 00:35:42.961
    kcrrwkx: nothing to do (start)
    *** 2012-08-31 00:40:42.890
    kcrrwkx: nothing to do (start)
    *** 2012-08-31 00:45:42.820
    kcrrwkx: nothing to do (start)
    *** 2012-08-31 00:50:42.755
    kcrrwkx: nothing to do (start)
    *** 2012-08-31 00:55:42.686
    kcrrwkx: nothing to do (start)
    *** 2012-08-31 01:00:42.631
    kcrrwkx: nothing to do (start)
    *** 2012-08-31 01:05:42.565
    kcrrwkx: nothing to do (start)
    *** 2012-08-31 01:10:42.496
    kcrrwkx: nothing to do (start)
    Mahir: Yes I have my 4 standby redo logs!
    I created the standby manually without using RMAN.
    Hemant: if it asks for even first thread, then obviously it shows nothing is applied on Standby. By the way so it is not called a 'GAP', I think..!
    Thanks.

  • Archived log not applying

    archived logs are not apllying in DR
    SQL> select max(sequence#) from v$archived_log where applied='YES';
    MAX(SEQUENCE#)
    SQL>
    SQL> select process,status,sequence# from v$managed_standby;
    PROCESS   STATUS        SEQUENCE#
    ARCH      CONNECTED             0
    ARCH      CONNECTED             0
    ARCH      CONNECTED             0
    ARCH      CONNECTED             0
    RFS       IDLE                  0
    RFS       IDLE                  0
    RFS       IDLE              34473
    MRP0      WAIT_FOR_GAP      31753
    RFS       IDLE                  0
    RFS       IDLE                  0
    RFS       IDLE                  0
    11 rows selected.

    Hello,
    As previously posted, you have a GAP. So, you may have to investigate why the Archived logs cannot be applied.
    To do so, you may check for the File System if any Archive destination is FULL. Also, you may have to verify the parameters on the PRIMARY and STANDBY site:
    sqlplus "/ as sysdba"
    show parameter fal
    show parameter dest
    show parameter config
    show parameter broker
    Check also the Alert log on both Primary and Standby.
    If the DATAGUARD BROKER is enabled you may also execute this
    dgmgrl
    show configuration verbose
    Also try to "tnsping" the services used in the Archive Destination from both site.
    When you are sure that everything is correct then, verify if any Archived logs is missing and try to restore it if possible.
    Else if everything is broken, and there's no way to get back the missing Archived logs, you 'll have to "rebuild" the Standby from a new Backup of the PRIMARY.
    Hope this help.
    Best regards,
    Jean-Valentin Lubiez

  • 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

  • Archive logs not applied on standby!!

    Hi Guys,
    I am trying to set up physical standby on windows 2003 server. I am using oracle 10.2.0.4.0. I get the following error in my alert file on standby
    Failed to request gap sequence
    Following is the results of some queries :
    SQL> SELECT PROCESS, STATUS, THREAD#, SEQUENCE#, BLOCK#, BLOCKS FROM V$MANAGED_STANDBY;
    PROCESS STATUS THREAD# SEQUENCE# BLOCK# BLOCKS
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    MR(fg) WAIT_FOR_GAP 1 10004 0 0
    SQL> select * from v$archive_gap;
    no rows selected
    SQL> select message from v$dataguard_status;
    MESSAGE
    ARC0: Archival started
    ARC1: Archival started
    ARC2: Archival started
    ARC3: Archival started
    ARC4: Archival started
    ARC5: Archival started
    ARC6: Archival started
    ARC7: Archival started
    ARC8: Archival started
    ARC9: Archival started
    ARC0: Becoming the 'no FAL' ARCH
    MESSAGE
    ARC0: Becoming the 'no SRL' ARCH
    ARC1: Becoming the heartbeat ARCH
    Attempt to start background Managed Standby Recovery process
    MRP0: Background Managed Standby Recovery process started
    Managed Standby Recovery not using Real Time Apply
    Media Recovery Waiting for thread 1 sequence 10004
    Fetching gap sequence in thread 1, gap sequence 10004-10017
    FAL[client]: Failed to request gap sequence
    GAP - thread 1 sequence 10004-10017
    DBID 2422302575 branch 670594799
    FAL[client]: All defined FAL servers have been attempted.
    MESSAGE
    MRP0: Background Media Recovery cancelled with status 16037
    MRP0: Background Media Recovery process shutdown
    Managed Standby Recovery Canceled
    Media Recovery Start: Managed Standby Recovery
    Managed Standby Recovery not using Real Time Apply
    Media Recovery Waiting for thread 1 sequence 10004
    Fetching gap sequence in thread 1, gap sequence 10004-10017
    FAL[client]: Failed to request gap sequence
    GAP - thread 1 sequence 10004-10017
    DBID 2422302575 branch 670594799
    FAL[client]: All defined FAL servers have been attempted.
    SQL>SELECT THREAD#, SEQUENCE#, APPLIED FROM V$ARCHIVED_LOG
    where applied= 'YES'
    no rows selected
    ##Modification to primary##
    *.log_archive_dest_2='SERVICE=STANDBY'
    *.fal_client='STUTEST'
    *.fal_server='STUSTANDBY'
    *.log_archive_config='DG_CONFIG=(STUTEST,STUSTANDBY)'
    ##Modification to standby##
    *.db_unique_name='STANDBY'
    *.log_archive_dest_2='SERVICE=STANDBY'
    *.log_archive_dest_state_2='ENABLE'
    *.Fal_server=STUTEST
    *.Fal_client=STUSTANDBY
    *.db_file_name_convert='H:\ORACLE\ORADATA\STUTEST\','I:\ORACLE\ORADATA\STUTEST\s_'
    *.log_file_name_convert='D:\oracle\oradata\STUTEST\','D:\oracle\oradata\STUTEST\s_'
    Nore: I used RMAN to create the standby database. The following are brief steps
    Below are the steps to accomplish the task :
    Step 1: Backup the database that includes backup of datafiles, archivelogs and controlfile for standby
    backup current controlfile for standby;
    Step 2: Move the backups to the standby server and restore control file from backup
    Step 3: Make changes in the parameter files of both primary and standby database
    Step 4: Do the restore and recover on standby database
    Step 5: Put the standby database in recover managed mode
    Thanks for help guys!!!!!

    Hi sb92075
    Alert log on standby
    alter database mount standby database
    Mon Jul 26 14:10:40 2010
    Setting recovery target incarnation to 1
    ARCH: STARTING ARCH PROCESSES
    ARC0 started with pid=21, OS id=6708
    ARC1 started with pid=22, OS id=3892
    ARC2 started with pid=23, OS id=4380
    ARC3 started with pid=24, OS id=4896
    ARC4 started with pid=25, OS id=6348
    ARC5 started with pid=26, OS id=5868
    ARC6 started with pid=27, OS id=6904
    ARC7 started with pid=28, OS id=4428
    ARC8 started with pid=29, OS id=5008
    Mon Jul 26 14:10:40 2010
    ARC0: Archival started
    ARC9 started with pid=30, OS id=5804
    Mon Jul 26 14:10:41 2010
    ARC1: Archival started
    ARC2: Archival started
    ARC3: Archival started
    ARC4: Archival started
    ARC5: Archival started
    ARC6: Archival started
    ARC7: Archival started
    ARC8: Archival started
    ARC9: Archival started
    ARCH: STARTING ARCH PROCESSES COMPLETE
    Mon Jul 26 14:10:41 2010
    ARC0: Becoming the 'no FAL' ARCH
    ARC0: Becoming the 'no SRL' ARCH
    ARC0: Thread not mounted
    Mon Jul 26 14:10:41 2010
    Successful mount of redo thread 1, with mount id 2477113436
    Mon Jul 26 14:10:41 2010
    Physical Standby Database mounted.
    Mon Jul 26 14:10:42 2010
    ARC1: Becoming the heartbeat ARCH
    Completed: alter database mount standby database
    Mon Jul 26 14:10:42 2010
    Errors in file c:\oracle\admin\stustandby\udump\stustandby_ora_6604.trc:
    Mon Jul 26 14:11:41 2010
    alter database recover managed standby database disconnect from session
    MRP0 started with pid=19, OS id=3696
    Managed Standby Recovery not using Real Time Apply
    parallel recovery started with 7 processes
    Mon Jul 26 14:11:46 2010
    Waiting for all non-current ORLs to be archived...
    Media Recovery Waiting for thread 1 sequence 10004
    Fetching gap sequence in thread 1, gap sequence 10004-10017
    Mon Jul 26 14:11:47 2010
    Completed: alter database recover managed standby database disconnect from session
    Mon Jul 26 14:12:16 2010
    *FAL[client]: Failed to request gap sequence*
    GAP - thread 1 sequence 10004-10017
    DBID 2422302575 branch 670594799
    *FAL[client]: All defined FAL servers have been attempted.*
    Alert log on primary
    Mon Jul 26 13:50:11 2010
    db_recovery_file_dest_size of 40960 MB is 49.73% used. This is a
    user-specified limit on the amount of space that will be used by this
    database for recovery-related files, and does not reflect the amount of
    space available in the underlying filesystem or ASM diskgroup.
    Mon Jul 26 13:50:12 2010
    Successfully onlined Undo Tablespace 19.
    Mon Jul 26 13:50:12 2010
    SMON: enabling tx recovery
    Mon Jul 26 13:50:12 2010
    Database Characterset is WE8ISO8859P1
    Opening with internal Resource Manager plan
    where NUMA PG = 1, CPUs = 8
    replication_dependency_tracking turned off (no async multimaster replication found)
    Starting background process QMNC
    QMNC started with pid=38, OS id=3776
    Mon Jul 26 13:50:14 2010
    Completed: ALTER DATABASE OPEN
    Mon Jul 26 13:51:10 2010
    Shutting down archive processes
    Mon Jul 26 13:51:15 2010
    ARCH shutting down
    ARCa: Archival stopped
    Mon Jul 26 14:11:47 2010
    Redo Shipping Client Connected as PUBLIC
    -- Connected User is Valid
    *FAL[server]: DGID from FAL client not in Data Guard configuration*
    *FAL[server]: FAL request for destination STUSTANDBY was:*
    GAP - thread 1 sequence 10004-10017
    DBID 2422302575 branch 670594799
    Mon Jul 26 15:04:10 2010
    Redo Shipping Client Connected as PUBLIC
    -- Connected User is Valid
    *FAL[server]: DGID from FAL client not in Data Guard configuration*
    *FAL[server]: FAL request for destination STUSTANDBY was:*
    GAP - thread 1 sequence 10004-10017 DBID 2422302575 branch 670594799

  • Archive not applying on dr database

    Hi All,
    Archive log are transferring from primary db to standby db.but archive are not applying on dr database.
    Below alert log of dr database
    ORA-16037: user requested cancel of managed recovery operation
    Fri Jan 14 17:05:40 2011
    MRP0: Background Media Recovery process shutdown (QMSSTB)
    Fri Jan 14 17:05:41 2011
    Managed Standby Recovery Canceled (QMSSTB)
    Fri Jan 14 17:05:41 2011
    Completed: alter database recover managed standby database cancel
    Fri Jan 14 17:07:56 2011
    alter database recover managed standby database disconnect from session
    Fri Jan 14 17:07:56 2011
    Attempt to start background Managed Standby Recovery process (QMSSTB)
    MRP0 started with pid=19, OS id=823510
    Fri Jan 14 17:07:56 2011
    MRP0: Background Managed Standby Recovery process started (QMSSTB)
    Managed Standby Recovery not using Real Time Apply
    parallel recovery started with 2 processes
    Fri Jan 14 17:08:01 2011
    Waiting for all non-current ORLs to be archived...
    Clearing online redo logfile 1 /oradb/oradata/QMSPROD/redo01.log
    Clearing online log 1 of thread 1 sequence number 3401
    Fri Jan 14 17:08:01 2011
    Errors in file /oradb/oradata/QMSPROD/bdump/qmsstb_mrp0_823510.trc:
    ORA-19527: physical standby redo log must be renamed
    ORA-00312: online log 1 thread 1: '/oradb/oradata/QMSPROD/redo01.log'
    Clearing online redo logfile 1 complete
    Media Recovery Waiting for thread 1 sequence 3401 (in transit)
    Fri Jan 14 17:08:02 2011
    Completed: alter database recover managed standby database disconnect from session

    Hi all,
    Dr database query
    SQL> select sequence#,applied from v$archived_log order by 1;
    SEQUENCE# APP
    3401 NO
    3401 NO
    3402 NO
    3403 NO
    3404 NO
    3405 NO
    3406 NO
    3407 NO
    3408 NO
    3409 NO
    3410 NO
    SEQUENCE# APP
    3411 NO
    3412 NO
    3413 NO
    3414 NO
    3415 NO
    3416 NO
    3417 NO
    3418 NO
    3419 NO
    3420 NO
    3421 NO
    SEQUENCE# APP
    3422 NO
    3423 NO
    3424 NO
    SQL> select process,status,sequence# from v$managed_standby
    2 ;
    PROCESS STATUS SEQUENCE#
    ARCH CONNECTED 0
    ARCH CONNECTED 0
    MRP0 WAIT_FOR_LOG 3401
    RFS IDLE 3401
    RFS RECEIVING 0
    RFS RECEIVING 0

  • 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

  • RMAN-08120: WARNING: archived log not deleted, not yet applied by standby

    i get RMAN-08120: WARNING: archived log not deleted, not yet applied by standby on primary
    but when i run below query i get the same result from primary and standby
    SQL> select max(sequence#) from v$archived_log;
    MAX(SEQUENCE#)
    44051
    SQL>
    standby is one log switch behind only!

    i get RMAN-08120: WARNING: archived log not deleted, not yet applied by standby on primary You already have answer by post of Mseberg.
    but when i run below query i get the same result from primary and standby
    SQL> select max(sequence#) from v$archived_log;
    MAX(SEQUENCE#)
    44051
    SQL>
    standby is one log switch behind only!this is wrong query used on primary & standby. even if any one of archive gap available lets suppose sequence *44020* , this archive not transported to standby due to some network problem and so on. later if archives from *44021* all the archives transported on standby upto *44051* , then it shows the maximum sequence transferred to standby, It wont shows applied sequence.
    Check the below queries.
    Primary:-
    SQL> select thread#,max(sequence#) from v$archived_log group by thread#;
    Standby:-
    SQL> select thread#,max(sequence#) from v$archived_log where applied='YES' group by thread#;
    HTH.

  • How do I setup RMAN not to delete archive log files on the source database so GoldenGate can process DDL/DML changes?

    I want to setup RMAN not to delete any archive log files that will be used by GoldenGate.   Once GoldenGate is completed with the archive log file, the archive log file can be backup and deleted by RMAN.   It's my understanding that I can issue the following command "REGISTER EXTRACT <ext_name>, LOGRETENTION" to enable to functionally.   Is this the only thing I need to do to execute to enable this functionally?

    Hello,
    Yes this is the rigth way  using clasic capture.
    Using the command : REGISTER EXTRACT Extract_name LOGRETENTION.
    Create a Oracle Streams Group Capture (Artificial)  that prevent RMAN archive deletion if these are pending to process for Golden Gate capture process.
    You can see this integration doing a SELECT * FROM DBA_CAPTURE; after execute the register command.
    Then, when RMAN try to delete a archive file pending to process for GG this warning appear AT RMAN logs:
    Error:     RMAN 8317 (RMAN-08317 RMAN-8317)
    Text:     WARNING: archived log not deleted, needed for standby or upstream capture process.
    Then , this is a good manageability feature. I think is a 11.1 GG new feature.
    Tip. To avoid RMAN backup multiples times a archive pending to process, there is a option called BACKUP archivelog not backed 1 times.
    If you remove a Capture process that is registered with the database you need to use this comand to remove the streams capture group:
    unREGISTER EXTRACT extract_name LOGRETENTION;
    Then if you query dba_capture, the artificial Streams group is deleted.
    I hope help.
    Regards
    Arturo

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

  • WARNING: archive log not deleted as it is still needed

    Our Oralce Database is a single node database of version 10.1.0.
    Dataguard/Standby is not configured.....we are executing the following command for archivelog backup
    run
    allocate channel c1 device type sbt;
    backup archivelog all delete input;
    This script is successfull in backingup all the archvied log files however it is not deleteing the input files. Instead it gives the warning....
    "WARNING: archive log not deleted as it is still needed"
    What could be the problem?

    If you do a Metalink seach on "WARNING: archive log not deleted as it is still needed." you'll find a couple of documents that explain the issue.
    The short answer is that RMAN has backed up logs which have not yet shipped to standby, so it won't delete them, cause they're still needed till they're successfully shipped to standby.
    -Mark

  • Archive log not found

    Hi,
    I want to run the RMAN backup, but I lost some of the archivers. How to take the backup excluding those lost archivers?
    Thanks,
    GK

    Only as note: You are faced to the error RMAN-06059.
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of backup command at 03/05/2006 12:43:42
    RMAN-06059: expected archived log not found, lost of archived log compromises recoverability
    ORA-19625: errore nell'identificare il file C:\ORACLE\DB\TEST\ARCHIVE\1_36.DBF
    ORA-27041: impossibile aprire file
    OSD-04002: impossibile aprire il file
    O/S-Error: (OS 2) Impossibile trovare il file specificato.

  • Archive log shipping error in Logical standby database

    Hi,
    We have Primay and logical database configuration both in RAC in Production. both database are in 10.2.0.4.
    Everyday we having issue of some archivelog not transfered to logical server around 2AM. I am having good exposure in Logical/Log minor/Goldgendate and can say fal server/client server configuration is correct.
    Can you guys please give some input of what can cause this.
    Yes we take RMAN backup of both database around 1:30 using control file instead of recovery catalog and I doubt this put lock on control file and cause this issue.
    I would be glad of you could help me out in this.
    Thanks a lot!
    Pradeep
    Below is the configuration of archive/fal on both database.
    PIP1REP2 is logical database(instance 2) where apply process is running/configured.
    Primary server configuration on (PIP11) (same are on other instances).
    SQL> sho parameter fal
    NAME TYPE VALUE
    fal_client string PIP1REP2
    fal_server string PIP11
    SQL> sho parameter archive
    NAME TYPE VALUE
    log_archive_dest_1 string LOCATION=+ARCH01
    log_archive_dest_2 string SERVICE=pip1rep2 lgwr async
    log_archive_dest_state_1 string enable
    log_archive_dest_state_2 string ENABLE
    llog_archive_local_first boolean TRUE
    log_archive_max_processes integer 10
    log_archive_min_succeed_dest integer 1
    log_archive_start boolean FALSE
    log_archive_trace integer 0
    remote_archive_enable string true
    Logical server configuration
    SQL> sho parameter fal
    NAME TYPE VALUE
    fal_client string PIP1REP
    fal_server string pip11, pip12, pip13, pip14, pi
    p15
    SQL> sho parameter archive
    NAME TYPE VALUE
    alog_archive_dest_1 string LOCATION=+ARCH01/PIP1REP valid
    for=(onlinelogfiles, all_rol
    es) db_unique_name=pip1rep
    log_archive_dest_2 string LOCATION=+ARCH01/PIP1REP/ARCH_
    DEST2_STANDBY_LOGS VALID_FOR=(
    STANDBY_LOGFILES,STANDBY_ROLE)
    db_unique_name=pip1rep
    log_archive_dest_state_1 string enable
    log_archive_dest_state_2 string enable
    log_archive_local_first boolean TRUE
    log_archive_max_processes integer 20
    log_archive_min_succeed_dest integer 1
    log_archive_trace integer 0
    remote_archive_enable string true
    standby_archive_dest string +ARCH01                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   

    Do you think creating recovery catalog will resolve it?
    Yes, I do. (But I do not know for sure)
    If it helps when I got to this part I decided to backup either the Primary or the Standby, but not both.
    I decided Primary only and documented how to recreate my standby without downtime.
    I hope this helps.
    regards.

  • 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

  • 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