Can not allocate log, archival required
DBAsupport.com Forums - Powered by vBulletin
Results 1 to 6 of 6

Thread: Can not allocate log, archival required

Hybrid View

  1. #1

    Can not allocate log, archival required

    Hi all,

    For some reason, I got oracle error message about archive. Below is the actual error message:

    .....................
    Tue Jan 14 10:14:06 2003
    ORACLE Instance P - Can not allocate log, archival required
    ARCH: Connecting to console port...
    Thread 1 cannot allocate new log, sequence 13746
    All online logs needed archiving
    Current log# 1 seq# 13745 mem# 0: /env1/oraredo/P/log1P.dbf
    Tue Jan 14 10:14:55 2003
    Thread 1 advanced to log sequence 13746
    Current log# 2 seq# 13746 mem# 0: /env1/oraredo/P/log2P.dbf
    Tue Jan 14 10:15:04 2003
    ORACLE Instance P - Can not allocate log, archival required
    ARCH: Connecting to console port...
    Thread 1 cannot allocate new log, sequence 13747
    All online logs needed archiving
    .....................

    Am I going to lose all the data that suppose to be archived? Anybody who had experience regarding above error could give me some explanation why I got this error message?

    Oracle: 8.0.6
    OS: UNIX
    Redolog size : 32 MB
    NO. of redolog: 4

    Thank you in advance.

    regards,
    feroz

  2. #2
    Join Date
    Jan 2002
    Location
    Up s**t creek
    Posts
    1,525
    Either add more redo logs or make the existing ones bigger

    Regards
    Jim
    Oracle Certified Professional
    "Build your reputation by helping other people build theirs."

    "Sarcasm may be the lowest form of wit but its still funny"

    Click HERE to vist my website!

  3. #3
    Join Date
    Dec 2000
    Location
    Ljubljana, Slovenia
    Posts
    4,439
    I assume you have automatic archiving enabled for your database.

    Have you checked the disk space on your archlog destination? It might be full. If so, make some room in it and archiving will continue.

    If this isn't the case or if emptying the archlog destination doesn't help, try the following:

    ALTER SYSTEM ARCHIVE LOG STOP;
    ALTER SYSTEM ARCHIVE LOG START;

    In any case, you won't loose any data becouse of this error. In fact, this error actually prevents you from potentialy loosing data in case media recovery will be needed in the future....
    Last edited by jmodic; 01-14-2003 at 06:04 AM.
    Jurij Modic
    ASCII a stupid question, get a stupid ANSI
    24 hours in a day .... 24 beer in a case .... coincidence?

  4. #4
    Hi again,

    Thank you for replying. Space is not a problem. I might increase the redolog size and restart the archive process.

    regards,
    feroz

  5. #5
    Join Date
    Sep 2001
    Location
    Düsseldorf, Germany.
    Posts
    588
    Then, did anybody stopped ARCH process in between? Check If you get any record for "Archive Log Stop" in near-by time in alert.log

  6. #6
    Hi,

    I've checked the alertlog file. Nobody issue ARCH process stop. Could it be heavy usage on the database?

    regards,
    Feroz

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