DBAsupport.com Forums - Powered by vBulletin
Results 1 to 4 of 4

Thread: archive log

  1. #1
    Join Date
    Nov 2000
    ARC0: Beginning to archive log# 5 seq# 395
    ARC0: Failed to archive log# 5 seq# 395
    ARC0: Beginning to archive log# 6 seq# 396

    what does that mean, i have that 3 or 4 times in my oracle alert file.

  2. #2
    Join Date
    Apr 2000
    Edison, NJ
    Check to see if the arch dest is full or not.

  3. #3
    Join Date
    Jun 2000
    Toronto, ON, Canada
    I guess this info is from alert file. Check to see how many archive processes you have. If you have two or more, the missing archived file should be in the other archive process log(BACKGROUND_DUMP_DEST). Check to see if the archived log is really missing. I don't think so.

  4. #4
    Join Date
    May 2000
    This could happen due to the following:

    1 All Members of the redo log are in the same disk.

    2 You might have configured Hardware Level Disk Mirroring and duplexing of redo log files.

    Basically when a redo log gets filled up, Oracle informs the ARCH process to do archiving the completed redo log file. Then the ARCH process tries to read other member of the redo log group, but it was not filled, because OS still writing the data into redo log file (2nd member).

    How to eliminate:
    1 If hardware level mirroring done, then you do not need duplexing of redo log files. You can drop the 2nd member in each group.

    2 If you still need software level mirroing of redo log files, place them in the internal disk.

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

We have made updates to our Privacy Policy to reflect the implementation of the General Data Protection Regulation.