Archival Error, no source redo log file
DBAsupport.com Forums - Powered by vBulletin
Page 1 of 2 12 LastLast
Results 1 to 10 of 12

Thread: Archival Error, no source redo log file

  1. #1
    Join Date
    Jan 2005
    Posts
    10

    Question Archival Error, no source redo log file

    Dear all,

    I just start to be an Oracle DBA. When I checked the alert log file this morning, I found the following error message in the alert log file. Could you please give me some clue to solve the issue? I do appreciate.

    My understanding is: in my primary database, no redo log file /u05/arch/1_3907.dbf exists, so there is no way for standby database to archive the log file. Am I right? What should I do?


    **********************************************************************

    Tue Jan 25 16:51:22 2005
    Errors in file /u05/bdump/ladb_arc0_17043.trc:
    ORA-16055: FAL request rejected
    ARC0: Begin FAL archive (thread 1 sequence 3904 destination tr_db_standby)
    Tue Jan 25 16:51:22 2005
    ARC1: Begin FAL archive (thread 1 sequence 3905 destination tr_db_standby)
    Tue Jan 25 16:51:22 2005
    ARC0: FAL archive, source redo log file not found: /u05/arch/1_3904.dbf
    Tue Jan 25 16:51:22 2005
    ARC1: FAL archive, source redo log file not found: /u05/arch/1_3905.dbf
    Tue Jan 25 16:51:22 2005
    Errors in file /u05/bdump/ladb_arc0_17043.trc:
    ORA-19505: failed to identify file "/u05/arch/1_3904.dbf"
    ORA-27037: unable to obtain file status
    Linux Error: 2: No such file or directory
    Additional information: 3
    Tue Jan 25 16:51:22 2005
    Errors in file /u05/bdump/ladb_arc1_17045.trc:
    ORA-19505: failed to identify file "/u05/arch/1_3905.dbf"
    ORA-27037: unable to obtain file status
    Linux Error: 2: No such file or directory
    Additional information: 3
    Tue Jan 25 16:51:22 2005
    ARC0: FAL archive failed, see trace file.
    Tue Jan 25 16:51:22 2005
    ARC1: FAL archive failed, see trace file.
    Tue Jan 25 16:51:22 2005
    ARCH: FAL archive failed. Archiver continuing
    Tue Jan 25 16:51:22 2005
    ARCH: FAL archive failed. Archiver continuing
    Tue Jan 25 16:51:22 2005
    ORACLE Instance ladb - Archival Error. Archiver continuing.
    Tue Jan 25 16:51:22 2005
    ORACLE Instance ladb - Archival Error. Archiver continuing.
    Tue Jan 25 16:51:22 2005
    ARCH: Connecting to console port...
    Tue Jan 25 16:51:22 2005
    ARCH: Connecting to console port...
    Tue Jan 25 16:51:22 2005
    ORA-16055: FAL request rejected
    Tue Jan 25 16:51:22 2005
    ORA-16055: FAL request rejected
    Tue Jan 25 16:51:22 2005
    ARCH: Connecting to console port...
    Tue Jan 25 16:51:22 2005
    ARCH: Connecting to console port...
    Tue Jan 25 16:51:22 2005
    Errors in file /u05/bdump/ladb_arc0_17043.trc:
    ORA-16055: FAL request rejected
    Tue Jan 25 16:51:22 2005
    Errors in file /u05/bdump/ladb_arc1_17045.trc:
    ORA-16055: FAL request rejected
    Tue Jan 25 16:51:22 2005
    ARC0: Begin FAL archive (thread 1 sequence 3907 destination tr_db_standby)
    ARC0: FAL archive, source redo log file not found: /u05/arch/1_3907.dbf
    Tue Jan 25 16:51:22 2005
    Errors in file /u05/bdump/ladb_arc0_17043.trc:
    ORA-19505: failed to identify file "/u05/arch/1_3907.dbf"
    ORA-27037: unable to obtain file status
    Linux Error: 2: No such file or directory
    Additional information: 3
    ARC0: FAL archive failed, see trace file.
    ARCH: FAL archive failed. Archiver continuing
    Tue Jan 25 16:51:22 2005
    ORACLE Instance ladb - Archival Error. Archiver continuing.
    ARCH: Connecting to console port...
    Tue Jan 25 16:51:22 2005
    ORA-16055: FAL request rejected
    ARCH: Connecting to console port...

    **************************************************************

    thanks a lot,

    Jian

  2. #2
    Join Date
    Aug 2002
    Location
    Atlanta
    Posts
    1,187

    Re: Archival Error, no source redo log file

    Originally posted by jwu1023
    Dear all,

    I just start to be an Oracle DBA. When I checked the alert log file this morning, I found the following error message in the alert log file. Could you please give me some clue to solve the issue? I do appreciate.

    My understanding is: in my primary database, no redo log file /u05/arch/1_3907.dbf exists, so there is no way for standby database to archive the log file. Am I right? What should I do?


    **********************************************************************

    Tue Jan 25 16:51:22 2005
    Errors in file /u05/bdump/ladb_arc0_17043.trc:
    ORA-16055: FAL request rejected
    ARC0: Begin FAL archive (thread 1 sequence 3904 destination tr_db_standby)
    Tue Jan 25 16:51:22 2005
    ARC1: Begin FAL archive (thread 1 sequence 3905 destination tr_db_standby)
    Tue Jan 25 16:51:22 2005
    ARC0: FAL archive, source redo log file not found: /u05/arch/1_3904.dbf
    Tue Jan 25 16:51:22 2005
    ARC1: FAL archive, source redo log file not found: /u05/arch/1_3905.dbf
    Tue Jan 25 16:51:22 2005
    Errors in file /u05/bdump/ladb_arc0_17043.trc:
    ORA-19505: failed to identify file "/u05/arch/1_3904.dbf"
    ORA-27037: unable to obtain file status
    Linux Error: 2: No such file or directory
    Additional information: 3
    Tue Jan 25 16:51:22 2005
    Errors in file /u05/bdump/ladb_arc1_17045.trc:
    ORA-19505: failed to identify file "/u05/arch/1_3905.dbf"
    ORA-27037: unable to obtain file status
    Linux Error: 2: No such file or directory
    Additional information: 3
    Tue Jan 25 16:51:22 2005
    ARC0: FAL archive failed, see trace file.
    Tue Jan 25 16:51:22 2005
    ARC1: FAL archive failed, see trace file.
    Tue Jan 25 16:51:22 2005
    ARCH: FAL archive failed. Archiver continuing
    Tue Jan 25 16:51:22 2005
    ARCH: FAL archive failed. Archiver continuing
    Tue Jan 25 16:51:22 2005
    ORACLE Instance ladb - Archival Error. Archiver continuing.
    Tue Jan 25 16:51:22 2005
    ORACLE Instance ladb - Archival Error. Archiver continuing.
    Tue Jan 25 16:51:22 2005
    ARCH: Connecting to console port...
    Tue Jan 25 16:51:22 2005
    ARCH: Connecting to console port...
    Tue Jan 25 16:51:22 2005
    ORA-16055: FAL request rejected
    Tue Jan 25 16:51:22 2005
    ORA-16055: FAL request rejected
    Tue Jan 25 16:51:22 2005
    ARCH: Connecting to console port...
    Tue Jan 25 16:51:22 2005
    ARCH: Connecting to console port...
    Tue Jan 25 16:51:22 2005
    Errors in file /u05/bdump/ladb_arc0_17043.trc:
    ORA-16055: FAL request rejected
    Tue Jan 25 16:51:22 2005
    Errors in file /u05/bdump/ladb_arc1_17045.trc:
    ORA-16055: FAL request rejected
    Tue Jan 25 16:51:22 2005
    ARC0: Begin FAL archive (thread 1 sequence 3907 destination tr_db_standby)
    ARC0: FAL archive, source redo log file not found: /u05/arch/1_3907.dbf
    Tue Jan 25 16:51:22 2005
    Errors in file /u05/bdump/ladb_arc0_17043.trc:
    ORA-19505: failed to identify file "/u05/arch/1_3907.dbf"
    ORA-27037: unable to obtain file status
    Linux Error: 2: No such file or directory
    Additional information: 3
    ARC0: FAL archive failed, see trace file.
    ARCH: FAL archive failed. Archiver continuing
    Tue Jan 25 16:51:22 2005
    ORACLE Instance ladb - Archival Error. Archiver continuing.
    ARCH: Connecting to console port...
    Tue Jan 25 16:51:22 2005
    ORA-16055: FAL request rejected
    ARCH: Connecting to console port...

    **************************************************************

    thanks a lot,

    Jian
    you have a standby database and the standby needs a log that likely you already removed where it thinks it should be /u05/arch/
    I'm stmontgo and I approve of this message

  3. #3
    Join Date
    Jan 2005
    Posts
    10
    Thanks for your help, stmontgo.

    Another new "DBA" like me deleted all the files in dicrectory /u05/arch on the standby. So does that mean I have to create a log file with the same name? If so, could you tell me the steps of creating a log file? I do appreciate your help.

    Jian

  4. #4
    Join Date
    Aug 2002
    Location
    Atlanta
    Posts
    1,187
    Originally posted by jwu1023
    Thanks for your help, stmontgo.

    Another new "DBA" like me deleted all the files in dicrectory /u05/arch on the standby. So does that mean I have to create a log file with the same name? If so, could you tell me the steps of creating a log file? I do appreciate your help.

    Jian
    Well the thing is there was a gap detected in the sequence of archive logs to applied at the standby - namely among others /u05/arch/1_3904.dbf. The standby is not being kept current and will not be until you can retrieve the missing logs. If you cannot retrieve the missing logs you need to recerate the standby with a new backup from production.
    I'm stmontgo and I approve of this message

  5. #5
    Join Date
    Jan 2005
    Posts
    10
    Hi stmontgo,

    May be this is stupid question, can I retrieve the miss log from the back up tape? If so, how could I reach the tape drive in Linux?

    And if I couldn't find the miss log, is there any drawback to create a new standby?

    Thanks for your patience and time.

    Jian

  6. #6
    Join Date
    Sep 2002
    Location
    England
    Posts
    7,331
    ask you SA as they probably control your backup software

    no downside to recreating the standby, apart from the hassle of doing it if you have no experience

  7. #7
    Join Date
    Nov 2002
    Location
    Geneva Switzerland
    Posts
    3,142
    Originally posted by davey23uk
    no downside to recreating the standby, apart from the hassle of doing it if you have no experience
    You are going to need to have this "under your belt" anyway, since recreation is needed if ever you restore & partially recover the primary or when you test the activation of the standby. Whoever first created the standby should have left instruction on how to do it.

  8. #8
    Join Date
    Jan 2005
    Posts
    10
    Hi DaPi and davey23uk,

    Thank you all so much for the helpful input. I will ask our SA for instruction. You all have a nice afternoon

    Jian

  9. #9
    Join Date
    Jan 2005
    Posts
    10
    Dear all,

    Another junior DBA suggested me to solve the issue in this way:

    1. shut down the primary database and clean all the logs.

    2. shut down the standby database and clean all the logs.

    3. start and mount the primary database and standby database.

    Could anybody tell me whether it is a good way? Is there any risk? After the above steps, should we create the log on both databases and how could we create the log file matched on both database? Thank you for your help in advance.

    Jian

  10. #10
    Join Date
    Sep 2002
    Location
    England
    Posts
    7,331
    no, your standby needs to be be in sync with the primary with missing lpgs it cannot do that.

    Do this.

    Shutdown primary and standby

    remove current standby

    backup and restore primary onto standby machine

    open up standy in standby mode.

    Can't invent logs which it needs

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  



Click Here to Expand Forum to Full Width