Log 1 sequence# 638 cannot be archived

Hello,
I've this error when i start my OAS script and i found nothing about these error.
Could you help me to correct this error please ?
ORA-16038: log 1 sequence# 638 cannot be archived
ORA-19809: limit exceeded for recovery files
ORA-00312: online log 1 thread 1: '/home/oracle/oradata/orcl/redo01.log'
Then, after that:
opmnctl: starting opmn and all managed processes...
and after a long time to wait opmnctl...I obtain that :
opmnctl: starting opmn and all managed processes...
================================================================================
opmn id=rd-srv-oas:6200
1 of 2 processes started.
ias-instance id=infra.rd-srv-oas
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
ias-component/process-type/process-set:
OC4J/OC4J_SECURITY/default_island
Error
--> Process (pid=1522)
time out while waiting for a managed process to start
Log:
/home/oracle/infra/opmn/logs/OC4J~OC4J_SECURITY~default_island~1
TZ set to Europe/Paris
Oracle Enterprise Manager 10g Application Server Control Release 10.1.2.0.0
Copyright (c) 1996, 2004 Oracle Corporation. All rights reserved.
http://rd-srv-oas:1810/emd/console/aboutApplication
Starting Oracle Enterprise Manager 10g Application Server Control ...... started successfully.
opmnctl: starting opmn and all managed processes...
================================================================================
opmn id=rd-srv-oas:6201
3 of 6 processes started.
ias-instance id=portal.rd-srv-oas
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
ias-component/process-type/process-set:
OC4J/home/default_island
Error
--> Process (pid=3334)
time out while waiting for a managed process to start
Log:
/home/oracle/portal/opmn/logs/OC4J~home~default_island~1
ias-component/process-type/process-set:
OC4J/OC4J_Portal/default_island
Error
--> Process (pid=3335)
time out while waiting for a managed process to start
Log:
/home/oracle/portal/opmn/logs/OC4J~OC4J_Portal~default_island~1
ias-component/process-type/process-set:
OC4J/TestWeb/default_island
Error
--> Process (pid=3336)
time out while waiting for a managed process to start
Log:
/home/oracle/portal/opmn/logs/OC4J~TestWeb~default_island~1
TZ set to Europe/Paris
Oracle Enterprise Manager 10g Application Server Control Release 10.1.2.0.0
Copyright (c) 1996, 2004 Oracle Corporation. All rights reserved.
http://rd-srv-oas:1814/emd/console/aboutApplication
Starting Oracle Enterprise Manager 10g Application Server Control ...... started successfully.
Thanks a lot !!!
M.
Message was edited by:
Manu

[demo oracle test10]$ oerr ora 19809
19809, 00000, "limit exceeded for recovery files"
//*Cause: The limit for recovery files specified by the
//        DB_RECOVERY_FILE_DEST_SIZE was exceeded.
//*Action:The error is accompanied by 19804. See message 19804 for further
//        details.
[demo oracle test10]$ oerr ora 19804
19804, 00000, "cannot reclaim %s bytes disk space from %s limit"
// *Cause: Oracle cannot reclaim disk space of specified bytes from the
//         DB_RECOVERY_FILE_DEST_SIZE limit.
// *Action: There are five possible solutions:
//          1) Take frequent backup of recovery area using RMAN.
//          2) Consider changing RMAN retention policy.
//          3) Consider changing RMAN archivelog deletion policy.
//          4) Add disk space and increase DB_RECOVERY_FILE_DEST_SIZE.
//          5) Delete files from recovery area using RMAN.
[demo oracle test10]$Your DB is not able to archive a logfile, because of no more space in FLASHBACK area. If you have enough space on disk you can increase the value of DB_RECOVERY_FILE_DEST_SIZE parameter, if not you should take one of other actions above to reduce occupied space in directory identified by DB_RECOVERY_FILE_DEST parameter.
Anyway, you should periodically clean up the flashback area in some way.
Paul

Similar Messages

  • ORA-16038: log 1 sequence# 1292 cannot be archived ORA-19809: limit exceede

    I am getting this error when starting the database 10g
    ORA-16038: log 1 sequence# 1292 cannot be archived
    ORA-19809: limit exceeded for recovery files
    ORA-00312: online log 1 thread 1:
    '/usr/lib/oracle/xe/app/oracle/flash_recovery_area/XE/onlinelog/o1_mf_1_45ngtrx0_.log'
    Can someone help me, it is very urgent.
    Zulqarnain

    It is resolved when I tried
    ALTER SYSTEM SET DB_RECOVERY_FILE_DEST_SIZE = 15G SCOPE=BOTH

  • ORA-16038: log 1 sequence# 607 cannot be archived Error..

    hi I Have a Problem to Start my Database.
    My Database is Not in Archive Mode..
    to know the detail error message is Given..
    SQL> alter database open;
    alter database open
    ERROR at line 1:
    ORA-16038: log 1 sequence# 607 cannot be archived
    ORA-19809: limit exceeded for recovery files
    ORA-00312: online log 1 thread 1:
    'C:\ORACLE\PRODUCT\10.1.0\ORADATA\ORCL\REDO01.LOG'
    I cam not recover My Database..
    SQL> recover database;
    ORA-00283: recovery session canceled due to errors
    ORA-00264: no recovery required
    I think recovery nolonger needed..
    pls any one help me..

    Hi
    ORA-19809: limit exceeded for recovery filesYou have two options now. First is to set the db_recovery_file_dest_size to a bigger size (if you have disk space available ie) and second to use RMAN to delete the archivelogs.
    Rgds
    Adnan

  • ~ORA-16038: log 2 sequence# 140 cannot be archived~ORA-19809: limit exceede

    ~ORA-16038: log 2 sequence# 140 cannot be archived~ORA-19809: limit exceeded for recovery files~ORA-00312: online log 2 thread 1: '/u02/oradata/PROD/redo02.log'
    but my /u02/oradata/PROD/ is empty, mod is set to 777
    What possible happened?
    Thanks.

    09:37:29 SQL> startup
    ORA-32004: obsolete and/or deprecated parameter(s) specified
    ORACLE instance started.
    see my init.ora, last three line is added by me,
    is it obsolete and/or deprecated parameter(s)?
    *.remote_login_passwordfile='EXCLUSIVE'
    *.sga_target=838860800
    *.undo_management='AUTO'
    *.undo_tablespace='UNDOTBS1'
    *.user_dump_dest='/u01/app/oracle/admin/PROD/udump'
    LOG_ARCHIVE_START=TRUE
    LOG_ARCHIVE_DEST=/u02/archive/PROD
    LOG_ARCHIVE_FORMAT=arc%s.arc

  • ORA 16038 log 1 sequence# 158249 cannot be archived

    hi im getting this error on my database when opening
    ORA-16038: log 1 sequence# 158249 cannot be archived
    ORA-19809: limit exceeded for recovery files
    ORA-00312: online log 1 thread 1: '/bill01/app/oracle/oradata/billing/redo01.log
    i have tried to free the space but still getting the same error
    this are the setting on the init file
    *.db_recovery_file_dest='/bill01/oracle/archive/BILLING'
    *.db_recovery_file_dest_size=21021851648
    on /bill01 ...... i have 131 GB free
    any idea

    SQL> alter system set db_recovery_file_dest_size=30G;
    System altered.
    SQL> alter database open;
    alter database open
    ERROR at line 1:
    ORA-16014: log 1 sequence# 158249 not archived, no available destinations
    ORA-00312: online log 1 thread 1:
    '/bill01/app/oracle/oradata/billing/redo01.log'
    ======================
    *.db_recovery_file_dest='/bill01/oracle/archive/BILLING'
    set on init

  • Database is not opening due to ORA-16038: log 1 sequence# 16 cannot be arch

    Dear All,
    I am using oracle database 10g release2 on linux platform............
    I am just moving logsegment type object from one tablespace to another tablespace.
    But due to low space for redo log file my alter query was hanged on and not completed sucessfully. and the directory is showing full.
    then i abort the query by shutdown database by using shutdown immediate command.
    After that when i m trying to startup my databse in normal mode i am getting following error....
    ERROR at line 1:
    ORA-16038: log 1 sequence# 16 cannot be archived
    ORA-19502: write error on file "", blockno (blocksize=)
    ORA-00312: online log 1 thread 1:
    '/var/oracle/oradata/clone/redofiles/REDO_RLOG_01a.dbf'
    ORA-00312: online log 1 thread 1:
    '/var/oracle/oradata/clone/redofiles/REDO_RLOG_03b.dbf'
    so pls suggest me the solution to resolve this problem.

    Check your Archive log location capacity , used & free.
    If archive mount point/FRA is full , then either take backup archive with delete option into another mount point'
    or
    as part of emergency you can move those archives into different mount point.
    Once there is enough free space, bring database back again. Post if any errors again

  • Next log sequence to archive is different

    Hi,
    I have doubt on standby (DR) concept.
    I can see that in my standby database next log sequence to archive shows 0.
    Is this ok or something is wrong?
    PRODUCTION
    SQL> archive log list;
    Database log mode Archive Mode
    Automatic archival Enabled
    Archive destination /u006/app/archive/XXPROD/arch
    Oldest online log sequence 2627
    Next log sequence to archive 2631
    Current log sequence 2631
    STANDBY
    SQL> archive log list;
    Database log mode Archive Mode
    Automatic archival Enabled
    Archive destination /u006/app/archive/XXPROD/arch
    Oldest online log sequence 2627
    Next log sequence to archive 0
    Current log sequence 2631

    Hello;
    Short answer no nothing is wrong.
    Its the same on mine :
    SQL> archive log list;
    Database log mode              Archive Mode
    Automatic archival             Enabled
    Archive destination            USE_DB_RECOVERY_FILE_DEST
    Oldest online log sequence     5069
    Next log sequence to archive   0
    Current log sequence           5071
    SQL> I use v$archived_log to check mine standby :
    SELECT  name as STANDBY, SEQUENCE#, applied, completion_time from v$archived_log WHERE  DEST_ID = 2 AND NEXT_TIME > SYSDATE -1;Against my Primary I get the last log :
    select max(sequence#) from v$archived_log where NEXT_TIME > sysdate -1;Data Guard has a set of v$ views to check results, 8archive log list8 isn't so good since with Data Guard you have two copies of the same database in different roles.
    Another query I like is : (Run on the standby)
    select process, status, sequence#, block# from v$managed_standby;The Oracle doc E10700-02 has several example in chapter 9 "Monitoring Primary, Physical Standby, and Snapshot Standby Databases"
    Also section "3.2.7 Verify the Physical Standby Database Is Performing Properly"
    Best Regards
    mseberg

  • In Noarchivelog mode "Thread 1 cannot allocate new log, sequence 3298"

    Hi,My database mode is noarchivelog but i see my alert.log "Thread 1 cannot allocate new log, sequence 3298"
    what it`s mean?
    I have enough disk space.

    This is very similar to the your still open thread cannot allocate new log, sequence
    Better protocol would surely be to acknowledge the references given then, and why you think they do or do not apply.
    Please get one of these threads marked as answered and continue on the other.
    Please also indicate:
    1) is your database hung.
    2) Output form this query:
    select log_mode from v$database;
    3) Database Version:
    4) Are there any other messages in alert log.
    5) In sqlplus connected as SYSDBA show output from
    archive log list
    Rgds - bigdelboy.

  • Thread 1 cannot allocate new log, sequence in Alert log

    Could someone help, I am getting the below message in my alert log
    System: AIX6.1 - Oracle 11r2
    GROUP#     THREAD#     MEMBER                                  ARCHIVED     STATUS             MB
    1     1     +DATA01/mydb/redolog_group1_member1     NO         INACTIVE             1536
    1     1     +DATA01/mydb/redolog_group1_member2     NO         INACTIVE             1536
    2     1     +DATA01/mydb/redolog_group2_member2     NO         CURRENT          1536
    2     1     +DATA01/mydb/redolog_group2_member1     NO         CURRENT          1536
    3     1     +DATA01/mydb/redolog_group3_member2     NO         INACTIVE             1536
    3     1     +DATA01/mydb/redolog_group3_member1     NO         INACTIVE             1536
    Tue Jul 10 18:37:48 2012
    Thread 1 advanced to log sequence 28831 (LGWR switch)
      Current log# 1 seq# 28831 mem# 0: +DATA01/mydb/redolog_group1_member1
      Current log# 1 seq# 28831 mem# 1: +DATA01/mydb/redolog_group1_member2
    Tue Jul 10 19:12:01 2012
    Thread 1 advanced to log sequence 28832 (LGWR switch)
      Current log# 2 seq# 28832 mem# 0: +DATA01/mydb/redolog_group2_member1
      Current log# 2 seq# 28832 mem# 1: +DATA01/mydb/redolog_group2_member2
    Tue Jul 10 19:39:00 2012
    Thread 1 cannot allocate new log, sequence 28833
    Private strand flush not complete
    Tue Jul 10 19:39:18 2012
      Current log# 2 seq# 28832 mem# 0: +DATA01/mydb/redolog_group2_member1
      Current log# 2 seq# 28832 mem# 1: +DATA01/mydb/redolog_group2_member2
    Tue Jul 10 19:41:21 2012
    Thread 1 advanced to log sequence 28833 (LGWR switch)
      Current log# 3 seq# 28833 mem# 0: +DATA01/mydb/redolog_group3_member1
      Current log# 3 seq# 28833 mem# 1: +DATA01/mydb/redolog_group3_member2
    Tue Jul 10 20:15:28 2012
    Thread 1 cannot allocate new log, sequence 28834
    Private strand flush not complete
      Current log# 3 seq# 28833 mem# 0: +DATA01/mydb/redolog_group3_member1
      Current log# 3 seq# 28833 mem# 1: +DATA01/mydb/redolog_group3_member2
    Tue Jul 10 20:16:21 2012Could an increase on the redo log file sizes solve this problem? Unfortunately I do not have a test platform, where I could have tested this.

    mseberg wrote:
    It just a warning. I would read these two notes:
    I suspect the OP is more worried about the apparent two minute gap between the "cannot switch" and the "advanced" at     19:39:18 and 19:41:12 respectively. Did the switch really have to wait for that two minutes, or is this a spurious threat caused by an anomaly in the writing of the alert log.
    As a cross check, I would examine v$event_histogram (or an AWR/Statspack for the interval) for time spent in the event "log file switch (private strand flush incomplete)". In prinicple I wouldn't expect to see waits longer than a few (less than 10) milliseconds; if the histogram shows long waits consistent with the alert log reports than I'd contact Oracle because something odd is happening.
    (Footnote - it's possible that the event times out after a limited interval, log file sync used to time out after 1 second and has recently changed to something shorter and adjustable, so 2 seconds may (for example) appear as 20 x 0.1 seconds.)
    Regards
    Jonathan Lewis

  • Thread ... cannot allocate new log, sequence ...

    I have an error in alert.log:
    Thread 1 cannot allocate new log, sequence ...
    Private strand flush not completeIs it dangerous?
    What does it mean?
    What can I do this mistake will disappear?

    select * from v$log;
    GROUP#,THREAD#,SEQUENCE#,BYTES,MEMBERS,ARCHIVED,STATUS,FIRST_CHANGE#,FIRST_TIME
    1,1,25921,1073741824,1,YES,INACTIVE,4582390708,16.05.2013 13:00:02
    2,1,25922,1073741824,1,YES,INACTIVE,4582566850,16.05.2013 13:27:17
    5,1,25923,1073741824,1,YES,INACTIVE,4582748298,16.05.2013 14:00:02
    4,1,25925,1073741824,1,NO,CURRENT,4582990596,16.05.2013 15:00:03
    3,1,25924,1073741824,1,NO,ACTIVE,4582954136,16.05.2013 14:54:42
    GROUP#,STATUS,TYPE,MEMBER,IS_RECOVERY_DEST_FILE
    1,,ONLINE,/opt/oracle/oradata/prod/redo01.log,NO
    2,,ONLINE,/opt/oracle/oradata/prod/redo02.log,NO
    3,,ONLINE,/opt/oracle/oradata/prod/redo03.log,NO
    4,,ONLINE,/opt/oracle/oradata/prod/redo04.log,NO
    5,,ONLINE,/opt/oracle/oradata/prod/redo05.log,NO
    SELECT optimal_logfile_size FROM   v$instance_recovery
    empty
    The last query result is:
    DAY,00,01,02,03,04,05,06,07,08,09,10,11,12,13,14,15,16,17,18,19,20,21,22,23,Total Switch
    05/01,   0,   0,   0,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   0,   0,   0,   0,17
    05/02,   0,   0,   0,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   0,   0,   0,   0,17
    05/03,   0,   1,   1,   1,   1,   1,   0,   0,   0,   0,   5,   3,   2,   0,   0,   1,   0,   0,   0,   0,   0,   0,   0,   2,18
    05/04,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   2,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   2,26
    05/05,   1,   1,   2,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,25
    05/06,   0,   1,   1,   1,   1,   1,   1,   1,   1,   2,   5,   2,   1,   1,   2,   6,   1,   1,   1,   1,   1,   1,   1,   2,36
    05/07,   0,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   3,   1,   1,   3,   2,   1,   1,   2,   1,   1,   1,   2,30
    05/08,   1,   2,   1,   1,   1,   1,   1,   1,   3,   5,   1,   1,   1,   1,   1,   1,   1,   1,   1,   2,   1,   1,   1,   2,33
    05/09,   1,   2,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   2,26
    05/10,   1,   1,   1,   1,   1,   1,   2,   1,   1,   2,   1,   1,   1,   1,   1,   1,   1,   1,   1,   2,   1,   1,   1,   2,28
    05/11,   1,   1,   1,   1,   2,   1,   1,   1,   1,   1,   2,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   2,27
    05/12,   1,   1,   1,   1,   1,   2,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   2,   1,   1,   1,   1,   0,25
    05/13,   0,   0,   0,   0,   0,   0,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,18
    05/14,   0,   0,   0,   0,   0,   0,   1,   1,   2,   1,   4,   4,   2,   4,   1,   4,   1,   4,   1,   2,   1,   1,   1,   1,36
    05/15,   1,   0,   0,   0,   0,   0,   1,   1,   1,   1,   1,   3,   2,   1,   1,   1,   1,   1,   1,   6,   1,   1,   1,   1,27
    05/16,   0,   0,   0,   0,   0,   0,   1,   1,   3,   3,   2,   2,   1,   2,   2,   0,   0,   0,   0,   0,   0,   0,   0,   0,17

  • Very Urgent: Thread 1 cannot allocate new log, sequence 6 : Script stuck

    I am running one script, it is stuck with log file showing:
    Thread 1 cannot allocate new log, sequence 6
    All online logs needed archiving
    Current log# 7 seq# 5 mem# 0: /u13/sjmarte/oradata/redo7a.log
    I have checked the database: it is in archivelog mode
    Checked the archvie dest: we have space in TB's
    And almost 24GB's occupied by log files each of 6GB's.
    ====================================
    Can any one please help us how to get rid of this issue

    Sorry I m new to this forum.
    We dont have a seperate FRA in this case.
    This is the log file information:
    Wed May 18 13:28:23 2011
    Thread 1 advanced to log sequence 5 (LGWR switch)
    Current log# 7 seq# 5 mem# 0: /u13/sjmarte/oradata/redo7a.log
    Current log# 7 seq# 5 mem# 1: /u14/sjmarte/oradata/redo7b.log
    Wed May 18 13:31:58 2011
    ORACLE Instance sjmarte - Can not allocate log, archival required
    Wed May 18 13:31:58 2011
    Thread 1 cannot allocate new log, sequence 6
    All online logs needed archiving
    Current log# 7 seq# 5 mem# 0: /u13/sjmarte/oradata/redo7a.log
    Current log# 7 seq# 5 mem# 1: /u14/sjmarte/oradata/redo7b.log
    Here is archive log list
    SQL> archive log list
    Database log mode Archive Mode
    Automatic archival Enabled
    Archive destination /backup/oracle/sjmarte/archive
    Oldest online log sequence 2
    Next log sequence to archive 2
    Current log sequence 5
    Edited by: 784786 on May 18, 2011 11:35 AM

  • Thread 1 cannot allocate new log, sequence 1258

    Hello buddies,
    I am receiving this message and not sure on how to fix it.
    Please guide me.
    Fri Jul 30 22:00:17 2010
    Thread 1 advanced to log sequence 1256 (LGWR switch)
    Current log# 2 seq# 1256 mem# 0: F:\maindb\LOG_02.DBF
    Fri Jul 30 22:00:36 2010
    Thread 1 advanced to log sequence 1257 (LGWR switch)
    Current log# 3 seq# 1257 mem# 0: F:\maindb\LOG_03.DBF
    Fri Jul 30 22:00:51 2010
    Thread 1 cannot allocate new log, sequence 1258
    Checkpoint not complete
    Current log# 3 seq# 1257 mem# 0: F:\maindb\LOG_03.DBF
    Fri Jul 30 22:00:53 2010
    Thread 1 advanced to log sequence 1258 (LGWR switch)
    Current log# 1 seq# 1258 mem# 0: F:\maindb\LOG_01.DBF
    Fri Jul 30 22:01:09 2010
    Thread 1 cannot allocate new log, sequence 1259
    Checkpoint not complete
    Current log# 1 seq# 1258 mem# 0: F:\maindb\LOG_01.DBF
    Fri Jul 30 22:01:11 2010
    Thread 1 advanced to log sequence 1259 (LGWR switch)
    Current log# 2 seq# 1259 mem# 0: F:\maindb\LOG_02.DBF
    Fri Jul 30 22:01:23 2010
    Thread 1 cannot allocate new log, sequence 1260
    Checkpoint not complete
    Current log# 2 seq# 1259 mem# 0: F:\maindb\LOG_02.DBF
    Fri Jul 30 22:01:26 2010
    Thread 1 advanced to log sequence 1260 (LGWR switch)
    Current log# 3 seq# 1260 mem# 0: F:\maindb\LOG_03.DBF
    Sat Jul 31 00:06:03 2010
    Thread 1 cannot allocate new log, sequence 1261
    Checkpoint not complete
    Current log# 3 seq# 1260 mem# 0: F:\maindb\LOG_03.DBF
    Sat Jul 31 00:06:05 2010
    Thread 1 advanced to log sequence 1261 (LGWR switch)
    Current log# 1 seq# 1261 mem# 0: F:\maindb\LOG_01.DBF
    Sat Jul 31 01:00:00 2010
    Thread 1 cannot allocate new log, sequence 1262
    Checkpoint not complete
    Current log# 1 seq# 1261 mem# 0: F:\maindb\LOG_01.DBF
    Sat Jul 31 01:00:02 2010
    Thread 1 advanced to log sequence 1262 (LGWR switch)
    Current log# 2 seq# 1262 mem# 0: F:\maindb\LOG_02.DBF
    Sat Jul 31 01:00:02 2010
    ALTER SYSTEM ARCHIVE LOG
    Sat Jul 31 01:00:02 2010
    Thread 1 cannot allocate new log, sequence 1263
    Checkpoint not complete
    Current log# 2 seq# 1262 mem# 0: F:\maindb\LOG_02.DBF
    Sat Jul 31 01:00:08 2010
    Thread 1 advanced to log sequence 1263 (LGWR switch)
    Current log# 3 seq# 1263 mem# 0: F:\maindb\LOG_03.DBF
    Sat Jul 31 01:00:11 2010
    ALTER SYSTEM ARCHIVE LOG
    Sat Jul 31 01:00:11 2010
    Thread 1 cannot allocate new log, sequence 1264
    Checkpoint not complete
    Current log# 3 seq# 1263 mem# 0: F:\maindb\LOG_03.DBF
    Sat Jul 31 01:00:14 2010
    Thread 1 advanced to log sequence 1264 (LGWR switch)
    Current log# 1 seq# 1264 mem# 0: F:\maindb\LOG_01.DBF
    Sat Jul 31 01:02:22 2010
    ALTER SYSTEM ARCHIVE LOG
    Sat Jul 31 01:02:22 2010
    Thread 1 advanced to log sequence 1265 (LGWR switch)
    Current log# 2 seq# 1265 mem# 0: F:\maindb\LOG_02.DBF
    Sat Jul 31 06:00:12 2010
    Thread 1 advanced to log sequence 1266 (LGWR switch)
    Current log# 3 seq# 1266 mem# 0: F:\maindb\LOG_03.DBF
    Sat Jul 31 06:00:24 2010
    Thread 1 advanced to log sequence 1267 (LGWR switch)
    Current log# 1 seq# 1267 mem# 0: F:\maindb\LOG_01.DBF
    Sat Jul 31 06:00:43 2010
    Thread 1 cannot allocate new log, sequence 1268
    Checkpoint not complete
    Current log# 1 seq# 1267 mem# 0: F:\maindb\LOG_01.DBF
    Sat Jul 31 06:00:44 2010
    Thread 1 advanced to log sequence 1268 (LGWR switch)
    Current log# 2 seq# 1268 mem# 0: F:\maindb\LOG_02.DBF
    I checked the size of the redo log: and its 10mb:
    spool F:\admin\maindb/create/create.log
    startup nomount
    create database maindb
        maxinstances 1
        datafile 'F:/data/maindb/system_01.dbf' size 250m
        sysaux datafile 'F:/data/maindb/sysaux_01.dbf' size 100m
        extent management local
        undo tablespace undo
                datafile 'F:/data/maindb/undo_01.dbf' size 40m
        default temporary tablespace temp
                tempfile 'F:/data/maindb/temp_01.dbf' size 40m
                extent management local uniform size 1m
        logfile 'F:/data/maindb/log_01.dbf' size 10m,
                'F:/data/maindb/log_02.dbf' size 10m,
                'F:/data/maindb/log_03.dbf' size 10m
        user sys identified by "abc"
        user system identified by "abc";
    whenever sqlerror continue
    @F:\10g/rdbms/admin/catalog
    @F:\10g/rdbms/admin/catproc
    @F:\10g/rdbms/admin/catblock
    @F:\10g/rdbms/admin/caths
    @F:\10g/rdbms/admin/dbmspool
    @F:\10g/rdbms/admin/dbmsrand
    @F:\10g/rdbms/admin/otrcsvr
    connect system/abc
    @F:\10g/sqlplus/admin/pupbld
    spool offSome parameters from my init file: log_archive_max_processes=15
    processes = 200
    log_checkpoint_timeout = 0
    log_checkpoint_interval = 0
    fast_start_mttr_target = 0
    Please help me.
    Thanking in advance.
    Nith

    Dear sb92075,
    I have increased the size of the redo log files to 15M to see how things work.
    select * from v$logfile;
    select group#, sequence#, bytes, archived, members, status
    from v$log;
    alter database drop logfile group 1;
    alter database
    add logfile group 1 ('F:\MAINDB\LOG_01.log') SIZE 15M;
    alter system switch logfile;
    alter database drop logfile group 2;
    alter database
    add logfile group 2 ('F:\MAINDB\LOG_02.LOG') SIZE 15M;
    ALTER SYSTEM CHECKPOINT GLOBAL;
    alter database drop logfile group 3;
    alter database
    add logfile group 3 ('F:\MAINDB\LOG_03.LOG') SIZE 15M;So, all I have to do now is just wait and see how things go after this, right?
    When these statements were being executed, I noticed some errors also but I think I should ignore them for now.
    Some sample messages are:
    Completed: alter database drop logfile group 3
    Sat Jul 31 11:06:40 2010
    alter database
    add logfile group 3 ('F:\MAINDB\LOG_03.LOG') SIZE 15M
    Sat Jul 31 11:06:40 2010
    Completed: alter database
    add logfile group 3 ('F:\MAINDB\LOG_03.LOG') SIZE 15M
    Sat Jul 31 11:08:54 2010
    ALTER SYSTEM ARCHIVE LOG
    Sat Jul 31 11:08:55 2010
    Thread 1 advanced to log sequence 1274 (LGWR switch)
    Sat Jul 31 11:08:55 2010
      Current log# 2 seq# 1274 mem# 0:F:\MAINDB\LOG_02.LOG
    Sat Jul 31 11:08:55 2010
    Thread 1 advanced to log sequence 1275 (LGWR switch)
      Current log# 3 seq# 1275 mem# 0: F:\MAINDB\LOG_03.LOG
    Sat Jul 31 11:09:03 2010
    ALTER SYSTEM ARCHIVE LOG
    Sat Jul 31 11:09:03 2010
    Thread 1 cannot allocate new log, sequence 1276
    Checkpoint not complete
      Current log# 3 seq# 1275 mem# 0: F:\MAINDB\LOG_03.LOG
    Sat Jul 31 11:09:06 2010
    Thread 1 advanced to log sequence 1276 (LGWR switch)
      Current log# 1 seq# 1276 mem# 0: F:\MAINDB\LOG_01.LOG
    Sat Jul 31 11:11:13 2010
    ALTER SYSTEM ARCHIVE LOG
    Sat Jul 31 11:11:13 2010
    Thread 1 advanced to log sequence 1277 (LGWR switch)
      Current log# 2 seq# 1277 mem# 0: F:\MAINDB\LOG_02.LOGPlease comment.

  • Thread 1 cannot allocate new log, sequence 80064 - Checkpoint not complete

    Hi,
    from few days we have sometimes this message into alert. I've just try to increase the size of redo log file but without success, have you got any idea?
    Thank you.
    Wed Jul 30 00:08:05 2014
    Beginning log switch checkpoint up to RBA [0x138bd.2.10], SCN: 4473445936
    Thread 1 advanced to log sequence 80061 (LGWR switch)
      Current log# 1 seq# 80061 mem# 0: F:\ORACLE\PRD\ORIGLOGA\LOG_G11M1.DBF
      Current log# 1 seq# 80061 mem# 1: F:\ORACLE\PRD\MIRRLOGA\LOG_G11M2.DBF
    Beginning log switch checkpoint up to RBA [0x138be.2.10], SCN: 4473445939
    Thread 1 advanced to log sequence 80062 (LGWR switch)
      Current log# 2 seq# 80062 mem# 0: F:\ORACLE\PRD\ORIGLOGB\LOG_G12M1.DBF
      Current log# 2 seq# 80062 mem# 1: F:\ORACLE\PRD\MIRRLOGB\LOG_G12M2.DBF
    Beginning log switch checkpoint up to RBA [0x138bf.2.10], SCN: 4473445942
    Thread 1 advanced to log sequence 80063 (LGWR switch)
      Current log# 3 seq# 80063 mem# 0: F:\ORACLE\PRD\ORIGLOGA\LOG_G13M1.DBF
      Current log# 3 seq# 80063 mem# 1: F:\ORACLE\PRD\MIRRLOGA\LOG_G13M2.DBF
    Wed Jul 30 00:08:06 2014
    Archived Log entry 80064 added for thread 1 sequence 80061 ID 0x70061a1e dest 1:
    Thread 1 cannot allocate new log, sequence 80064
    Checkpoint not complete
    Wed Jul 30 00:08:06 2014
    Archived Log entry 80065 added for thread 1 sequence 80062 ID 0x70061a1e dest 1:
      Current log# 3 seq# 80063 mem# 0: F:\ORACLE\PRD\ORIGLOGA\LOG_G13M1.DBF
      Current log# 3 seq# 80063 mem# 1: F:\ORACLE\PRD\MIRRLOGA\LOG_G13M2.DBF
    Wed Jul 30 00:08:08 2014
    Archived Log entry 80066 added for thread 1 sequence 80060 ID 0x70061a1e dest 1:
    Wed Jul 30 00:08:09 2014
    Completed checkpoint up to RBA [0x138bd.2.10], SCN: 4473445936
    Beginning log switch checkpoint up to RBA [0x138c0.2.10], SCN: 4473445946
    Thread 1 advanced to log sequence 80064 (LGWR switch)
      Current log# 4 seq# 80064 mem# 0: F:\ORACLE\PRD\ORIGLOGB\LOG_G14M1.DBF
    Completed checkpoint up to RBA [0x138c0.2.10], SCN: 4473445946
      Current log# 4 seq# 80064 mem# 1: F:\ORACLE\PRD\MIRRLOGB\LOG_G14M2.DBF
    Archived Log entry 80067 added for thread 1 sequence 80063 ID 0x70061a1e dest 1:
    Completed checkpoint up to RBA [0x138bf.2.10], SCN: 4473445942
    Completed checkpoint up to RBA [0x138be.2.10], SCN: 4473445939

    ========================================================
    GENERIC OPATCH VERSION - FOR USE IN SAP ENVIRONMENT ONLY
    ========================================================
    Oracle Installer di patch provvisorie versione 11.2.0.3.1
    Copyright (c) 2012, Oracle Corporation. Tutti i diritti riservati.
    Oracle Home       : I:\oracle\PRD\11203
    Central Inventory : C:\Program Files\Oracle\Inventory
       from           : n/a
    OPatch version    : 11.2.0.3.1
    OUI version       : 11.2.0.3.0
    Log file location : I:\oracle\PRD\11203\cfgtoollogs\opatch\opatch2014-07-30_00-4
    7-57AM_1.log
    Lsinventory Output file location : I:\oracle\PRD\11203\cfgtoollogs\opatch\lsinv\
    lsinventory2014-07-30_00-47-57AM.txt
    Prodotti di livello superiore installati (1):
    Oracle Database 11g                                                  11.2.0.3.0
    Ci sono 1 prodotti installati in questa Oracle home.
    Patch provvisorie (6) :
    Patch  16167942     : applied on Sat May 18 11:50:42 CEST 2013
    Unique Patch ID:  15646955
    Patch description:  "ORACLE 11G 11.2.0.3 PATCH 15 BUG FOR WINDOWS (64-BIT AMD64
    AND INTEL EM64)"
       Created on 01 Feb 2013, 00:06:51 hrs PST8PDT
       Bugs fixed:
         16167942, 15841373, 14252187, 13877007, 14249514, 13891981, 12637294
         14511876, 14309075, 13736413, 12862170, 13901201, 12819999, 16019955
         15996520, 14775679, 13902963, 15924589, 14525739, 14744263, 12838063
         15910002, 14751895, 14107475, 13262857, 14641969, 15938047, 15982436
         13924173, 14761411, 16042648, 13337530, 14810890, 13605675, 7335665
         12686027, 16011871, 13729351, 13923995, 12813641, 12985237, 14600776
         14565062, 13066936, 14510516, 14192781, 14164191, 14505752, 15834269
         13559463, 14702500, 12345305, 14467027, 14807785, 14590564, 13849733
         13916549, 14755945, 15869211, 13365021, 13972394, 14193629, 14808639
         14189694, 13848402, 14226599, 13621258, 13827380, 14762511, 14064573
         13777449, 15848120, 14546673, 14546638, 14546575, 14469008, 14263073
         14263036, 14258925, 14205448, 14023636, 14035825, 13685544, 14040433
         13593999, 13026410, 12964067, 12873183, 12857027, 12345082, 14589750
         14668670, 13791678, 13769577, 13658087, 14230270, 13890080, 13810393
         13551402, 14644185, 13686047, 12583611, 14488943, 14176879, 13727644
         13517951, 13361350, 14373728, 13602883, 13580513, 10219624, 14645769
         14007968, 14827344, 9153183, 15853081, 14138130, 14168099, 14810093
         13845120, 14277586, 14271305, 13879428, 13938166, 12558569, 10260842
         14569263, 14100232, 13912373, 13653178, 14242977, 14102704, 14001941
         13993634, 13634583, 14828076, 13645875, 14398795, 13879553, 12940620
         14663556, 12327035, 14207902, 12557401, 14653598, 14587310, 14224606
         14577426, 14386985, 13783957, 12656350, 11836374, 14485163, 14624988
         14582487, 14332938, 14166276, 14479390, 14372670, 14038163, 13535104
         13744724, 14245087, 14305767, 14731193, 14313519, 14500723, 12928700
         12571916, 14245825, 13642044, 9706792, 13693929, 13903046, 14581922
         14142884, 14393900, 9778542, 13115786, 13427062, 14164849, 13399711
         11686700, 14175146, 14499293, 13615767, 14625969, 14513934, 14320472
         14613223, 13040943, 12812148, 14360965, 13911821, 14140535, 14204172
         13949042, 14367567, 9949330, 14467202, 14323857, 13834065, 13632653
         14110275, 13549808, 14196818, 13819727, 9751365, 10029609, 11846912
         12646510, 12766337, 12826115, 12860701, 12865360, 12973529, 13031176
         13040909, 13061085, 13066239, 13071375, 13111783, 13114306, 13345188
         13376866, 13393115, 13406688, 13408107, 13433178, 13459147, 13531801
         13553502, 13603792, 13608532, 13622539, 13622968, 13738130, 13961338
         14054189, 13851432, 14063422, 13973307, 14119388, 14282903, 14517263
         13716797, 14465787, 14613900, 14304758, 14251904, 14214257, 14153867
         14009845, 13889047, 13888719, 13820621, 13697828, 12663376, 11675721
         12889329, 13410987, 13965075, 13869978, 13843080, 13825231, 13582411
         13550689, 13023609, 13000491, 10418841, 10317921, 13523527, 13498267
         14096743, 14010695, 13947200, 14259185, 14280458, 14276345, 14543814
         13804294, 13718279, 13612575, 13430938, 13384182, 13377816, 13250244
         12794305, 12693626, 12352406, 12879628, 13534412, 13524698, 13743987
         14207317, 13918644, 14198511, 14088346, 12791981, 13011409, 13038684
         12865902, 12768840, 14076523, 13632809, 14458246, 13359289, 12794025
         9952132, 13780816, 12950694, 14162791, 13093358, 14255600, 13936424
         14301592, 14050233, 13528725, 14500052, 10146616, 14409183, 14324057
         14313389, 5918695, 12430142, 13399435, 13913630, 13732226, 10084752
         13591624, 14237793, 14013094, 10229475, 13078786, 14052474, 13637058
         12646746, 13000553, 14254795, 14215010, 13922729, 13942694, 12898637
         14309390, 13958038, 10214323, 13710236, 14115858, 14240544, 14158332
         13073613, 11074304, 13868705, 12723295, 13853654, 14074606, 13784384
         14386810, 14223718, 14018752, 13258936, 13723052, 12898020, 10625145
         14052871, 13076238, 13992002, 13242070, 12955701, 12693573, 14026888
         13984965, 13366199, 13843286, 13616375, 12839247, 8547978, 13714926
         13023854, 13910420, 11837095, 12842909, 12959852, 13632140, 13780035
         13860201, 13711083, 13628002, 13397104, 12358083, 13743357, 13945708
         10384051, 13591484, 13051250, 13727853, 12959627, 14095820, 5144934
         13657605, 13582702, 12966665, 13463131, 13773133, 12918738, 13099577
         13690409, 13645917, 11708510, 14042380, 13627489, 13652437, 12733042
         13907462, 13608299, 13624984, 9095696, 12794090, 9706532, 13469158
         13947480, 13555112, 13399236, 12910565, 13790109, 12552578, 13896848
         13737746, 13080778, 13458016, 13873885, 12312133, 12731940, 12672969
         13355095, 13981051, 13467683, 13457582, 13370330, 13340388, 12976376
         12797420, 12658411, 10133521, 9761357, 13827394, 13729832, 13851978
         13559770, 13592937, 13592919, 13478856, 13559540, 13641696, 13729808
         13632530, 14100237, 11071989, 13786142, 13839641, 13041324, 13857364
         13853089, 13806545, 13726162, 13657366, 13617861, 13604057, 13483672
         12959140, 12914722, 12910033, 12771830, 13776758, 13339443, 12680491
         10114953, 12966774, 13965211, 12424121, 13478060, 13786778, 13579992
         13705338, 13603613, 13476583, 12745662, 9190186, 13530646, 13520452
         9019231, 13610777, 12905053, 10263668, 13550185, 13385346, 13448206
         12772404, 13911711, 11072246, 13104881, 13863326, 12889054, 13775960
         13777823, 13464002, 11824898, 13535622, 13916709, 12880299, 12918338
         12529945, 13811209, 14058362, 13724808, 13885389, 13649031, 13350245
         13553883, 13388104, 13635347, 13404129, 13031118, 12530140, 13023541
         13767921, 13787482, 13641076, 13807411, 13724992, 12965899, 13791443
         12879027, 13584130, 13495307, 12594032, 13709220, 13247965, 13243072
         13683125, 13652493, 12957127, 10215977, 13014128, 13040331, 12857222
         12977501, 12664456, 12405931, 13525554, 13492863, 13573521, 13873471
         13366268, 13352423, 13460353, 12709476, 13652088, 13886023, 13942723
         12919564, 12894807, 12829021, 12612118, 11063191, 13503598, 13482688
         13354082, 13484963, 13395403, 13542159, 12983611, 13718476, 12846562
         9659614, 13326736, 11846902, 11665727, 13257247, 13588248, 13544396
         13566938, 13615517, 13425727, 13037709, 12730342, 12349553, 13502441
         13258062, 13251796, 13247273, 12659561, 12639013, 12594616, 11772838
         13570057, 12403721, 12585543, 12784549, 12834800, 12975771, 13040171
         13058950, 13063120, 13077335, 13365700, 13382280, 13384397, 13440516
         13454210, 13457537, 13477790, 13496250, 13501787, 13505390, 13506110
         13524899, 13572659, 13594712, 13617627, 13326289, 13555974, 13035360
         13420224, 13419660, 13036331, 13332439, 13420174, 12583826, 13358781
         11883969, 13524237, 12867713, 13328193, 13516727, 11865420, 13502183
         13259364, 13371153, 12998795, 13413168, 12897902, 13044108, 12971242
         12834027, 12620823, 13420516, 12849377, 12975811, 12646784, 12829429
         12538907, 12950823, 12848480, 12823838, 13366202, 13002015, 12834777
         13001901, 13017428, 13082238, 12965049, 11840910, 12656535, 12617123
         13073340, 12925041, 12938841, 13023632, 13066371, 12942119, 11877623
         12810890, 12995950, 12765467, 12934171, 13070939, 12535346, 12985184
         13103913, 12765868, 12622441, 12876314, 12820045, 13038806, 13090686
         12923168, 13362079, 12591252, 12718090, 12873909, 10350832, 12795861
         13039908, 12976590, 13017584, 12627504, 13263435, 12847466, 12797765
         12758736, 12878750, 12861463, 13024624, 12764337, 12662040, 13068077
         12914824, 13074261, 12668341, 12597906, 12932852, 13045518, 12897651
         12960925, 12728585, 13019958, 12902661, 12886827, 12913474, 3522216
         12678920, 12885323, 13334158, 12947871, 12896850, 13001955, 12784559
         12827166, 9703627, 12772345, 12905058, 13345868, 10357727, 12827493
         13004894, 12780983, 12842804, 13146719, 12655301, 12960302, 13085732
         12979199, 12638117, 13357509, 12401111, 12857064, 8631856, 13035804
         13355963, 12845115, 12695029, 12990582, 12971775, 12867511, 12917230
         12582664, 12849688, 12950644, 12588744, 13011520, 12899169, 12823042
    Patch  14658090     : applied on Sat May 18 11:40:34 CEST 2013
    Unique Patch ID:  15859799.1
       Created on 27 Jan 2013, 08:31:45 hrs PST8PDT
       Bugs fixed:
         14658090
    Patch  13575265     : applied on Sat May 18 11:40:14 CEST 2013
    Unique Patch ID:  14606745
       Created on 27 Feb 2012, 02:10:47 hrs PST8PDT
       Bugs fixed:
         13575265
    Patch  13508485     : applied on Sat May 18 11:39:34 CEST 2013
    Unique Patch ID:  14395138
       Created on 21 Dec 2011, 13:23:38 hrs PST8PDT
       Bugs fixed:
         13508485
    Patch  12325243     : applied on Sat May 18 11:38:51 CEST 2013
    Unique Patch ID:  14243031
       Created on 7 Nov 2011, 11:57:40 hrs PST8PDT
       Bugs fixed:
         12325243
    Patch  9584028      : applied on Sat May 18 11:38:31 CEST 2013
       Created on 22 Jun 2012, 11:39:40 hrs CEST
       Bugs fixed:
         9584028
    OPatch succeeded.

  • ORA-00308: cannot open archived log, ORA-27041

    hi All,
    here I am making DR server and I copied  SAP Data file1,2,3,4 from PRD to DR server and created control file. when I try to run following command for applied archives which i copy from PRD then getting below error.
    SQL>Startup
    Database mounted.
    ORA-01589: must use RESETLOGS or NORESETLOGS option for database open
    SQL> recover database using backup controlfile;
    ORA-00279: change 1209554452 generated at 02/09/2012 17:02:57 needed for thre
    1
    ORA-00289: suggestion : F:\ORACLE\PRD\ORAARCH\PRDARCH1_59501_657865393.DBF
    ORA-00280: change 1209554452 for thread 1 is in sequence #59501
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    auto
    ORA-00308: cannot open archived log
    'F:\ORACLE\PRD\ORAARCH\PRDARCH1_59501_657865393.DBF'
    ORA-27041: unable to open file
    OSD-04002: unable to open file
    O/S-Error: (OS 2) The system cannot find the file specified.
    ORA-00308: cannot open archived log
    'F:\ORACLE\PRD\ORAARCH\PRDARCH1_59501_657865393.DBF'
    ORA-27041: unable to open file
    OSD-04002: unable to open file
    O/S-Error: (OS 2) The system cannot find the file specified.
    here required PRDARCH1_59501_657865393.DBF while PRD server have PRDARCHARC59501_0657865393.001
    I did change the LOG_ARCHIVE_DEST parameter in initSID.ora of DR server and not in PRD.
    please tell that, how can i apply PRD's archive (.001 extension) on DR.
    Regards,

    hi all,
    after recommendation , now parameter values on DR server is :
    *.log_archive_dest_1='LOCATION=F:\oracle\PRD\oraarch\PRDarch'
    *.log_archive_format='%t_%s_%r.001'
    when i try to apply
    SQL> recover database using backup controlfile;
    ORA-00279: change 1211443555 generated at 02/10/2012 23:36:05 needed for thread
    1
    ORA-00289: suggestion : F:\ORACLE\PRD\ORAARCH\PRDARCH\1_59557_657865393.001
    ORA-00280: change 1211443555 for thread 1 is in sequence #59557
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    auto
    ORA-00308: cannot open archived log
    'F:\ORACLE\PRD\ORAARCH\PRDARCH\1_59557_657865393.001'
    ORA-27041: unable to open file
    OSD-04002: unable to open file
    O/S-Error: (OS 2) The system cannot find the file specified.
    if you see that the required archive is:       1_59557_657865393.001
    while copied archive exist with this name: PRDARCHARC59557_0657865393.001
    I tried to change in Format parameter to make required format but
    Exp:
    %t_%s_%r.001
    1_59557_657865393.001
    ARC%s%r%t.001
    ARC595576578653931.001'
    ARC%s_%r%t.001
    ARC59557_6578653931.001
    ARC%s_%r.%t
    ARC59557_657865393.1
    PRDARCHARC%s_%r.%t
    PRDARCHARC59557_657865393.1
    Required Format: PRDARCHARC59540_0657865393.001
    how can i resolve this different name issue? please suggest me required format.
    Regards,

  • ORA-00308: cannot open archived log '+DATA'

    Hello all,
    I created new physical standby but I facing problem with shipping archived file between primary and standby.
    Primary : RAC (4 nodes)
    Standby : single node with ASM
    when I run :
    alter database recover managed standby database disconnect from session;
    in alert log file :
    Managed Standby Recovery not using Real Time Apply
    Parallel Media Recovery started with 24 slaves
    Waiting for all non-current ORLs to be archived...
    All non-current ORLs have been archived.
    Media Recovery Waiting for thread 1 sequence 25738
    Tue Mar 03 12:21:13 2015
    Completed: alter database recover managed standby database disconnect from session
    and when i checked archived files by
    select max(sequence#)  from v$archivanded_log;
    It was null.
    I understand thatno shipping between primary and standby till this point i deiced to use manual recovery by :
    alter database recover automatic standby database;
    But i get this error in alert log file :
    alter database recover automatic standby database
    Media Recovery Start
    started logmerger process
    Tue Mar 03 12:38:38 2015
    Managed Standby Recovery not using Real Time Apply
    Parallel Media Recovery started with 24 slaves
    Media Recovery Log +DATA
    Errors with log +DATA
    Errors in file /u01/app/oracle/diag/rdbms/oracledrs/oracledrs/trace/oracledrs_pr00_4989.trc:
    ORA-00308: cannot open archived log '+DATA'
    ORA-17503: ksfdopn:2 Failed to open file +DATA
    ORA-15045: ASM file name '+DATA' is not in reference form
    ORA-279 signalled during: alter database recover automatic standby database..
    when i opened oracledrs_pr00_4989.trc: file i find :
    *** 2015-03-03 12:38:39.478
    Media Recovery add redo thread 4
    ORA-00308: cannot open archived log '+DATA'
    ORA-17503: ksfdopn:2 Failed to open file +DATA
    ORA-15045: ASM file name '+DATA' is not in reference form
    When I created i set these parameter in duplicate command:
    set db_file_name_convert='+ASM_ORADATA/oracle','+DATA/oracledrs'
    set log_file_name_convert='+ASM_ARCHIVE/oracle','+DATA/oracledrs','+ASM_ORADATA/oracle','+DATA/oracledrs'
    set control_files='+DATA'
    set db_create_file_dest='+DATA'
    set db_recovery_file_dest='+DATA'
    What please the mistake here
    Thanks in advance,

    Yes I have datafiles under +DATA
    ASMCMD> cd +DATA/ORACLEDRS/DATAFILE
    ASMCMD> ls
    ASD.282.873258045
    CATALOG.288.873258217
    DEVTS.283.873258091
    EXAMPLE.281.873258043
    FEED.260.873227069
    FEED.279.873257713
    INDX.272.873251345
    INDX.273.873252239
    INDX.278.873257337
    SYSAUX.262.873227071
    SYSTEM.277.873256531
    SYSTEM_2.280.873257849
    TB_WEBSITE.284.873258135
    TB_WEBSITE.285.873258135
    TB_WEBSITE.286.873258181
    TB_WEBSITE.287.873258183
    UNDOTBS1.275.873253421
    UNDOTBS2.276.873255247
    UNDOTBS3.261.873227069
    UNDOTBS4.271.873245967
    USERS.263.873227071
    USERS.264.873235507
    USERS.265.873235893
    USERS.266.873237079
    USERS.267.873238225
    USERS.268.873243661
    USERS.269.873244307
    USERS.270.873244931
    USERS.274.873252585
    asd01.dbf
    catalog01
    dev01.dbf
    example.dbf
    feed01.dbf
    feed02.dbf
    indx01.dbf
    indx02.dbf
    indx03.dbf
    sysaux01.dbf
    system01.dbf
    system02.dbf
    undotbs01.dbf
    undotbs02.dbf
    undotbs03.dbf
    undotbs04.dbf
    user1.dbf
    users01.dbf
    users02.dbf
    users03.dbf
    users04.dbf
    users05.dbf
    users06.dbf
    users07.dbf
    users08.dbf
    website01.dbf
    website02.dbf
    website03.dbf
    website04.dbf
    ASMCMD>
    Standby :
    [root@oracledrs ~]# id oracle
    uid=54321(oracle) gid=54321(oinstall) groups=54321(oinstall),54322(dba)
    Primary :
    [root@dbn-prod-1 disks]# id oracle
    uid=54321(oracle) gid=54321(oinstall) groups=54321(oinstall),54322(dba)
    1- yes i have needed archived files at my primary
    2-  select inst_id,thread#,group# from gv$log;
    Primary :
    INST_ID,THREAD#,GROUP#
    1,1,1
    1,1,2
    1,2,3
    1,2,4
    1,3,5
    1,3,6
    1,4,7
    1,4,8
    1,1,9
    1,2,10
    1,3,11
    1,4,12
    3,1,1
    3,1,2
    3,2,3
    3,2,4
    3,3,5
    3,3,6
    3,4,7
    3,4,8
    3,1,9
    3,2,10
    3,3,11
    3,4,12
    2,1,1
    2,1,2
    2,2,3
    2,2,4
    2,3,5
    2,3,6
    2,4,7
    2,4,8
    2,1,9
    2,2,10
    2,3,11
    2,4,12
    4,1,1
    4,1,2
    4,2,3
    4,2,4
    4,3,5
    4,3,6
    4,4,7
    4,4,8
    4,1,9
    4,2,10
    4,3,11
    4,4,12
    Standby :
    INST_ID,THREAD#,GROUP#
    1,1,9
    1,1,2
    1,1,1
    1,2,3
    1,2,4
    1,2,10
    1,3,5
    1,3,6
    1,3,11
    1,4,12
    1,4,7
    1,4,8
    3- That's sample from alert log since i started the standby (for standby and primary)
    Standby :
    alter database mount standby database
    NOTE: Loaded library: /opt/oracle/extapi/64/asm/orcl/1/libasm.so
    NOTE: Loaded library: System
    SUCCESS: diskgroup DATA was mounted
    ERROR: failed to establish dependency between database oracledrs and diskgroup resource ora.DATA.dg
    ARCH: STARTING ARCH PROCESSES
    Tue Mar 03 18:38:16 2015
    ARC0 started with pid=128, OS id=4461
    ARC0: Archival started
    ARCH: STARTING ARCH PROCESSES COMPLETE
    ARC0: STARTING ARCH PROCESSES
    Tue Mar 03 18:38:17 2015
    Successful mount of redo thread 1, with mount id 1746490068
    Physical Standby Database mounted.
    Lost write protection disabled
    Tue Mar 03 18:38:17 2015
    ARC1 started with pid=129, OS id=4464
    Tue Mar 03 18:38:17 2015
    ARC2 started with pid=130, OS id=4466
    Tue Mar 03 18:38:17 2015
    ARC3 started with pid=131, OS id=4468
    Tue Mar 03 18:38:17 2015
    ARC4 started with pid=132, OS id=4470
    Tue Mar 03 18:38:17 2015
    ARC5 started with pid=133, OS id=4472
    Tue Mar 03 18:38:17 2015
    ARC6 started with pid=134, OS id=4474
    Tue Mar 03 18:38:17 2015
    ARC7 started with pid=135, OS id=4476
    Completed: alter database mount standby database
    Tue Mar 03 18:38:17 2015
    ARC8 started with pid=136, OS id=4478
    Tue Mar 03 18:38:17 2015
    ARC9 started with pid=137, OS id=4480
    ARC1: Archival started
    ARC2: Archival started
    ARC3: Archival started
    ARC4: Archival started
    ARC5: Archival started
    ARC6: Archival started
    ARC7: Archival started
    ARC8: Archival started
    ARC8: Becoming the 'no FAL' ARCH
    ARC2: Becoming the heartbeat ARCH
    ARC2: Becoming the active heartbeat ARCH
    Tue Mar 03 18:38:18 2015
    Starting Data Guard Broker (DMON)
    ARC9: Archival started
    ARC0: STARTING ARCH PROCESSES COMPLETE
    Tue Mar 03 18:38:23 2015
    INSV started with pid=141, OS id=4494
    Tue Mar 03 18:39:11 2015
    alter database recover managed standby database disconnect from session
    Attempt to start background Managed Standby Recovery process (oracledrs)
    Tue Mar 03 18:39:11 2015
    MRP0 started with pid=142, OS id=4498
    MRP0: Background Managed Standby Recovery process started (oracledrs)
    started logmerger process
    Tue Mar 03 18:39:16 2015
    Managed Standby Recovery not using Real Time Apply
    Parallel Media Recovery started with 24 slaves
    Waiting for all non-current ORLs to be archived...
    All non-current ORLs have been archived.
    Media Recovery Waiting for thread 1 sequence 25738
    Completed: alter database recover managed standby database disconnect from session
    Tue Mar 03 18:41:17 2015
    WARN: ARCH: Terminating pid 4476 hung on an I/O operation
    Killing 1 processes with pids 4476 (Process by index) in order to remove hung processes. Requested by OS process 4224
    ARCH: Detected ARCH process failure
    Tue Mar 03 18:45:17 2015
    ARC2: STARTING ARCH PROCESSES
    Tue Mar 03 18:45:17 2015
    ARC7 started with pid=127, OS id=4586
    Tue Mar 03 18:45:18 2015
    Fatal NI connect error 12170.
      VERSION INFORMATION:
            TNS for Linux: Version 11.2.0.4.0 - Production
            Oracle Bequeath NT Protocol Adapter for Linux: Version 11.2.0.4.0 - Production
            TCP/IP NT Protocol Adapter for Linux: Version 11.2.0.4.0 - Production
      Time: 03-MAR-2015 18:45:18
      Tracing not turned on.
      Tns error struct:
        ns main err code: 12535
    TNS-12535: TNS:operation timed out
        ns secondary err code: 12560
        nt main err code: 505
    TNS-00505: Operation timed out
        nt secondary err code: 0
        nt OS err code: 0
      Client address: <unknown>
    ARC7: Archival started
    ARC2: STARTING ARCH PROCESSES COMPLETE
    Tue Mar 03 18:47:14 2015
    alter database recover managed standby database cancel
    Tue Mar 03 18:48:18 2015
    Fatal NI connect error 12170.
      VERSION INFORMATION:
            TNS for Linux: Version 11.2.0.4.0 - Production
            Oracle Bequeath NT Protocol Adapter for Linux: Version 11.2.0.4.0 - Production
            TCP/IP NT Protocol Adapter for Linux: Version 11.2.0.4.0 - Production
      Time: 03-MAR-2015 18:48:18
      Tracing not turned on.
      Tns error struct:
        ns main err code: 12535
    TNS-12535: TNS:operation timed out
        ns secondary err code: 12560
        nt main err code: 505
    TNS-00505: Operation timed out
        nt secondary err code: 0
        nt OS err code: 0
      Client address: <unknown>
    Tue Mar 03 18:51:18 2015
    Fatal NI connect error 12170.
      VERSION INFORMATION:
            TNS for Linux: Version 11.2.0.4.0 - Production
            Oracle Bequeath NT Protocol Adapter for Linux: Version 11.2.0.4.0 - Production
            TCP/IP NT Protocol Adapter for Linux: Version 11.2.0.4.0 - Production
      Time: 03-MAR-2015 18:51:18
      Tracing not turned on.
      Tns error struct:
        ns main err code: 12535
    TNS-12535: TNS:operation timed out
        ns secondary err code: 12560
        nt main err code: 505
    TNS-00505: Operation timed out
        nt secondary err code: 0
        nt OS err code: 0
      Client address: <unknown>
    Error 12170 received logging on to the standby
    FAL[client, USER]: Error 12170 connecting to oracle for fetching gap sequence
    MRP0: Background Media Recovery cancelled with status 16037
    Errors in file /u01/app/oracle/diag/rdbms/oracledrs/oracledrs/trace/oracledrs_pr00_4500.trc:
    ORA-16037: user requested cancel of managed recovery operation
    Recovery interrupted!
    Tue Mar 03 18:51:18 2015
    MRP0: Background Media Recovery process shutdown (oracledrs)
    Tue Mar 03 18:51:19 2015
    Managed Standby Recovery Canceled (oracledrs)
    Completed: alter database recover managed standby database cancel
    Tue Mar 03 18:51:56 2015
    alter database recover automatic standby database
    Media Recovery Start
    started logmerger process
    Tue Mar 03 18:51:56 2015
    Managed Standby Recovery not using Real Time Apply
    Parallel Media Recovery started with 24 slaves
    Media Recovery Log +DATA
    Errors with log +DATA
    Errors in file /u01/app/oracle/diag/rdbms/oracledrs/oracledrs/trace/oracledrs_pr00_4617.trc:
    ORA-00308: cannot open archived log '+DATA'
    ORA-17503: ksfdopn:2 Failed to open file +DATA
    ORA-15045: ASM file name '+DATA' is not in reference form
    ORA-279 signalled during: alter database recover automatic standby database...
    Tue Mar 03 18:53:06 2015
    db_recovery_file_dest_size of 512000 MB is 0.13% 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.
    Primary :
    Tue Mar 03 17:13:43 2015
    Thread 1 advanced to log sequence 26005 (LGWR switch)
      Current log# 1 seq# 26005 mem# 0: +ASM_ORADATA/oracle/onlinelog/group_1.271.849356883
    Tue Mar 03 17:13:44 2015
    Archived Log entry 87387 added for thread 1 sequence 26004 ID 0x66aa5a0d dest 1:
    Tue Mar 03 18:00:18 2015
    Thread 1 advanced to log sequence 26006 (LGWR switch)
      Current log# 2 seq# 26006 mem# 0: +ASM_ORADATA/oracle/onlinelog/group_2.270.849356883
    Tue Mar 03 18:00:18 2015
    Archived Log entry 87392 added for thread 1 sequence 26005 ID 0x66aa5a0d dest 1:
    Tue Mar 03 18:55:33 2015
    Thread 1 advanced to log sequence 26007 (LGWR switch)
      Current log# 9 seq# 26007 mem# 0: +ASM_ORADATA/oracle/onlinelog/group_9.295.853755983
      Current log# 9 seq# 26007 mem# 1: +ASM_ARCHIVE/oracle/onlinelog/group_9.10902.853755985
    Tue Mar 03 18:55:33 2015
    Archived Log entry 87395 added for thread 1 sequence 26006 ID 0x66aa5a0d dest 1:
    Tue Mar 03 19:14:22 2015
    Dumping diagnostic data in directory=[cdmp_20150303191422], requested by (instance=4, osid=10234), summary=[incident=1692472].
    Dumping diagnostic data in directory=[cdmp_20150303191425], requested by (instance=4, osid=10234), summary=[incident=1692473].
    Tue Mar 03 20:00:06 2015
    Thread 1 advanced to log sequence 26008 (LGWR switch)
      Current log# 1 seq# 26008 mem# 0: +ASM_ORADATA/oracle/onlinelog/group_1.271.849356883
    Tue Mar 03 20:00:07 2015
    Archived Log entry 87401 added for thread 1 sequence 26007 ID 0x66aa5a0d dest 1:
    Tue Mar 03 21:00:02 2015
    Thread 1 advanced to log sequence 26009 (LGWR switch)
      Current log# 2 seq# 26009 mem# 0: +ASM_ORADATA/oracle/onlinelog/group_2.270.849356883
    Tue Mar 03 21:00:03 2015
    Archived Log entry 87403 added for thread 1 sequence 26008 ID 0x66aa5a0d dest 1:
    Thread 1 advanced to log sequence 26010 (LGWR switch)
      Current log# 9 seq# 26010 mem# 0: +ASM_ORADATA/oracle/onlinelog/group_9.295.853755983
      Current log# 9 seq# 26010 mem# 1: +ASM_ARCHIVE/oracle/onlinelog/group_9.10902.853755985
    Tue Mar 03 21:00:06 2015
    Archived Log entry 87404 added for thread 1 sequence 26009 ID 0x66aa5a0d dest 1:
    Tue Mar 03 22:00:00 2015
    Setting Resource Manager plan SCHEDULER[0x32DA]:DEFAULT_MAINTENANCE_PLAN via scheduler window
    Setting Resource Manager plan DEFAULT_MAINTENANCE_PLAN via parameter
    Tue Mar 03 22:00:00 2015
    Starting background process VKRM
    Tue Mar 03 22:00:00 2015
    VKRM started with pid=184, OS id=4838
    Tue Mar 03 22:00:07 2015
    Begin automatic SQL Tuning Advisor run for special tuning task  "SYS_AUTO_SQL_TUNING_TASK"
    Tue Mar 03 22:00:25 2015
    Thread 1 advanced to log sequence 26011 (LGWR switch)
      Current log# 1 seq# 26011 mem# 0: +ASM_ORADATA/oracle/onlinelog/group_1.271.849356883
    Tue Mar 03 22:00:26 2015
    Archived Log entry 87408 added for thread 1 sequence 26010 ID 0x66aa5a0d dest 1:
    Tue Mar 03 22:00:58 2015
    Thread 1 advanced to log sequence 26012 (LGWR switch)
      Current log# 2 seq# 26012 mem# 0: +ASM_ORADATA/oracle/onlinelog/group_2.270.849356883
    Tue Mar 03 22:01:00 2015
    Archived Log entry 87412 added for thread 1 sequence 26011 ID 0x66aa5a0d dest 1:
    Tue Mar 03 22:02:37 2015
    Thread 1 cannot allocate new log, sequence 26013
    Checkpoint not complete
      Current log# 2 seq# 26012 mem# 0: +ASM_ORADATA/oracle/onlinelog/group_2.270.849356883
    Thread 1 advanced to log sequence 26013 (LGWR switch)
      Current log# 9 seq# 26013 mem# 0: +ASM_ORADATA/oracle/onlinelog/group_9.295.853755983
      Current log# 9 seq# 26013 mem# 1: +ASM_ARCHIVE/oracle/onlinelog/group_9.10902.853755985
    Tue Mar 03 22:02:41 2015
    Archived Log entry 87415 added for thread 1 sequence 26012 ID 0x66aa5a0d dest 1:
    Tue Mar 03 22:03:26 2015
    Thread 1 cannot allocate new log, sequence 26014
    Checkpoint not complete
      Current log# 9 seq# 26013 mem# 0: +ASM_ORADATA/oracle/onlinelog/group_9.295.853755983
      Current log# 9 seq# 26013 mem# 1: +ASM_ARCHIVE/oracle/onlinelog/group_9.10902.853755985
    Thread 1 advanced to log sequence 26014 (LGWR switch)
      Current log# 1 seq# 26014 mem# 0: +ASM_ORADATA/oracle/onlinelog/group_1.271.849356883
    Tue Mar 03 22:03:29 2015
    Archived Log entry 87416 added for thread 1 sequence 26013 ID 0x66aa5a0d dest 1:
    Tue Mar 03 22:05:50 2015
    Thread 1 cannot allocate new log, sequence 26015
    Checkpoint not complete
      Current log# 1 seq# 26014 mem# 0: +ASM_ORADATA/oracle/onlinelog/group_1.271.849356883
    Tue Mar 03 22:05:52 2015
    End automatic SQL Tuning Advisor run for special tuning task  "SYS_AUTO_SQL_TUNING_TASK"
    Thread 1 advanced to log sequence 26015 (LGWR switch)
      Current log# 2 seq# 26015 mem# 0: +ASM_ORADATA/oracle/onlinelog/group_2.270.849356883
    Tue Mar 03 22:05:54 2015
    Archived Log entry 87418 added for thread 1 sequence 26014 ID 0x66aa5a0d dest 1:
    Tue Mar 03 22:07:29 2015
    Thread 1 cannot allocate new log, sequence 26016
    Checkpoint not complete
      Current log# 2 seq# 26015 mem# 0: +ASM_ORADATA/oracle/onlinelog/group_2.270.849356883
    Thread 1 advanced to log sequence 26016 (LGWR switch)
      Current log# 9 seq# 26016 mem# 0: +ASM_ORADATA/oracle/onlinelog/group_9.295.853755983
      Current log# 9 seq# 26016 mem# 1: +ASM_ARCHIVE/oracle/onlinelog/group_9.10902.853755985
    Tue Mar 03 22:07:33 2015
    Archived Log entry 87421 added for thread 1 sequence 26015 ID 0x66aa5a0d dest 1:
    Thread 1 cannot allocate new log, sequence 26017
    Checkpoint not complete
      Current log# 9 seq# 26016 mem# 0: +ASM_ORADATA/oracle/onlinelog/group_9.295.853755983
      Current log# 9 seq# 26016 mem# 1: +ASM_ARCHIVE/oracle/onlinelog/group_9.10902.853755985
    Thread 1 advanced to log sequence 26017 (LGWR switch)
      Current log# 1 seq# 26017 mem# 0: +ASM_ORADATA/oracle/onlinelog/group_1.271.849356883
    Tue Mar 03 22:07:39 2015
    Archived Log entry 87422 added for thread 1 sequence 26016 ID 0x66aa5a0d dest 1:
    Tue Mar 03 22:16:36 2015
    Thread 1 advanced to log sequence 26018 (LGWR switch)
      Current log# 2 seq# 26018 mem# 0: +ASM_ORADATA/oracle/onlinelog/group_2.270.849356883
    Tue Mar 03 22:16:37 2015
    Archived Log entry 87424 added for thread 1 sequence 26017 ID 0x66aa5a0d dest 1:
    Tue Mar 03 22:30:06 2015
    Thread 1 advanced to log sequence 26019 (LGWR switch)
      Current log# 9 seq# 26019 mem# 0: +ASM_ORADATA/oracle/onlinelog/group_9.295.853755983
      Current log# 9 seq# 26019 mem# 1: +ASM_ARCHIVE/oracle/onlinelog/group_9.10902.853755985
    Tue Mar 03 22:30:07 2015
    Archived Log entry 87427 added for thread 1 sequence 26018 ID 0x66aa5a0d dest 1:
    Tue Mar 03 22:30:18 2015
    Thread 1 advanced to log sequence 26020 (LGWR switch)
      Current log# 1 seq# 26020 mem# 0: +ASM_ORADATA/oracle/onlinelog/group_1.271.849356883
    Tue Mar 03 22:30:19 2015
    Archived Log entry 87428 added for thread 1 sequence 26019 ID 0x66aa5a0d dest 1:
    Tue Mar 03 23:07:27 2015
    Dumping diagnostic data in directory=[cdmp_20150303230727], requested by (instance=4, osid=25140), summary=[incident=1692496].
    Dumping diagnostic data in directory=[cdmp_20150303230730], requested by (instance=4, osid=25140), summary=[incident=1692497].
    Thanks in advance sir ,

Maybe you are looking for

  • Dependencies visible in Web UI for Data Cleansing

    Hi All, My client is using the functionality Data Cleansing and we are implementing CRM 2007. As of CRM 2007 we now have two variants in BUSWU02 - CLEARING and CLEAR_REP. The dependencies(objects) defined in CLEARING are visible in the web UI. and ob

  • Capture Media and running Task Sequence gets error 0x80004005 and TSMBAutorun.log error

    Hi All, I've been stuck on this for a while now, trying to figure out why I am getting the following error in the  TSMBAutorun.log file <![LOG[TSMBAutoRun started]LOG]!><time=13:0:0 date=0-1-1970 component="TSMBautorun" context="" type="1"> <![LOG[Un

  • Kindle single-folio apps?

    Is it still not possible to build single-folio apps for Kindle? (And Android in general?) I'm assuming that hasn't changed but haven't paid attention. If not possible, is it on the horizon? (Is it a Kindle Store issue, or a viewer builder issue? Assu

  • IPad 1 Website connection problems

    I have an original iPad and it keeps throwing me out or not connecting to certain web sites. Is this because it's only iOS 5.1. There is no further software update available from apple.

  • Transferring data between matrices

    I am new to this stuff; so I would like to say hello.  I will probably need to come here often with questions and hopefully later with some answers. I need sample code that shows how to transfer data into a matrix on the current form from a matrix on