ARCHIVE LOG ERROR
DBAsupport.com Forums - Powered by vBulletin
Results 1 to 3 of 3

Thread: ARCHIVE LOG ERROR

  1. #1
    Join Date
    Sep 2001
    Posts
    200
    Hi All,
    I have an interesting/ scary scenario here. Take a look at the series of ORA-s this alert file.
    Questions:
    What was going on?
    How do I prevent this?
    NB note that the log (48276) eventually succeeded to be archived. And followed by message "Archiver process freed from errors. No longer stopped."
    Thanks
    Tony.

    Thread 1 advanced to log sequence 48274
    Current log# 3 seq# 48274 mem# 0: /dev/rprod_0016_009
    Current log# 3 seq# 48274 mem# 1: /dev/rprod_0016_010
    Current log# 3 seq# 48274 mem# 2: /dev/rprod_0016_011
    Fri Apr 5 18:40:26 2002
    ARC1: Beginning to archive log# 2 seq# 48273
    ARC1: Completed archiving log# 2 seq# 48273
    Fri Apr 5 18:48:44 2002
    Thread 1 advanced to log sequence 48275
    Current log# 1 seq# 48275 mem# 0: /dev/rprod_0016_003
    Current log# 1 seq# 48275 mem# 1: /dev/rprod_0016_004
    Current log# 1 seq# 48275 mem# 2: /dev/rprod_0016_005
    Fri Apr 5 18:48:44 2002
    ARC0: Beginning to archive log# 3 seq# 48274
    ARC0: Completed archiving log# 3 seq# 48274
    Fri Apr 5 18:58:04 2002
    Thread 1 advanced to log sequence 48276
    Current log# 2 seq# 48276 mem# 0: /dev/rprod_0016_006
    Current log# 2 seq# 48276 mem# 1: /dev/rprod_0016_007
    Current log# 2 seq# 48276 mem# 2: /dev/rprod_0016_008
    Fri Apr 5 18:58:05 2002
    ARC2: Beginning to archive log# 1 seq# 48275
    ARC2: Completed archiving log# 1 seq# 48275
    Fri Apr 5 19:00:04 2002
    Thread 1 advanced to log sequence 48277
    Current log# 3 seq# 48277 mem# 0: /dev/rprod_0016_009
    Current log# 3 seq# 48277 mem# 1: /dev/rprod_0016_010
    Current log# 3 seq# 48277 mem# 2: /dev/rprod_0016_011
    Fri Apr 5 19:08:15 2002
    ARC1: Beginning to archive log# 2 seq# 48276
    ARC1: Error 19504 creating archivelog file '/u02/oracle/admin/prod/arch/prod1/re
    do1_48276.arc'
    ARC1: Archiving not possible: error count exceeded
    ARC1: Failed to archive log# 2 seq# 48276
    ARCH: Archival stopped, error occurred. Will continue retrying
    Fri Apr 5 19:08:16 2002
    ORACLE Instance prod1 - Archival Error
    ARCH: Connecting to console port...
    Fri Apr 5 19:08:16 2002
    ORA-16014: log 2 sequence# 48276 not archived, no available destinations
    ORA-00312: online log 2 thread 1: '/dev/rprod_0016_006'
    ORA-00312: online log 2 thread 1: '/dev/rprod_0016_007'
    ORA-00312: online log 2 thread 1: '/dev/rprod_0016_008'
    ARCH: Connecting to console port...
    ARCH:
    ORA-16014: log 2 sequence# 48276 not archived, no available destinations
    ORA-00312: online log 2 thread 1: '/dev/rprod_0016_006'
    ORA-00312: online log 2 thread 1: '/dev/rprod_0016_007'
    ORA-00312: online log 2 thread 1: '/dev/rprod_0016_008'
    Thread 1 advanced to log sequence 48278
    Current log# 1 seq# 48278 mem# 0: /dev/rprod_0016_003
    Current log# 1 seq# 48278 mem# 1: /dev/rprod_0016_004
    Current log# 1 seq# 48278 mem# 2: /dev/rprod_0016_005
    Fri Apr 5 19:19:38 2002
    ARC2: Beginning to archive log# 2 seq# 48276
    ARC2: Completed archiving log# 2 seq# 48276
    Archiver process freed from errors. No longer stopped.
    Fri Apr 5 19:19:42 2002
    ARC0: Beginning to archive log# 3 seq# 48277
    ARC0: Completed archiving log# 3 seq# 48277
    Fri Apr 5 19:23:15 2002
    Life is what is happening today while you were planning tomorrow.

  2. #2
    Join Date
    Mar 2000
    Location
    CA
    Posts
    317
    Probably your archive drive might have been full and you could have cleared it later. When I was full, it gave that error. And and when you freed up, it said started archiving again.
    Thanks
    Kishore Kumar

  3. #3
    Join Date
    Mar 2002
    Posts
    60
    16014, 00000, "log %s sequence# %s not archived, no available destinations"
    // *Cause: An attempt was made to archive the named log, but the archive was unsuccessful. The archive failed because there were no archivelog destinations specified or all destinations experienced debilitating errors.

    // *Action: Verify that archivelog destinations are being specified and/or take the necessary step to correct any errors that may have occurred.

    Looks like the archive destination was not availaible or it was full...as soon as Oracle saw it....ARC background process was freed from errors.

    You need to make sure your archive destination directory has enough space to accomodate the archive files ..
    In this scenario when your archiver is not able to write files...
    ur database is in a hung state meaning nobody can login and no transactions can be processed.
    thanks



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