This discussion is archived
5 Replies Latest reply: Dec 5, 2012 11:41 PM by Osama_Mustafa RSS

Checkpoint Not complete in alert log

PVOWUSU Newbie
Currently Being Moderated
Hello Gurus,

Alert log keeps displaying the following message:

Current log# 3 seq# 80148 mem# 0: /UBSUNDO/ghadb_redo03b.log
Current log# 3 seq# 80148 mem# 1: /UBSTEMP/ghadb_redo03a.log
Thu Dec 06 01:33:20 GMT 2012
Thread 1 advanced to log sequence 80149 (LGWR switch)
Current log# 1 seq# 80149 mem# 0: /UBSUNDO/ghadb_redo01b.log
Current log# 1 seq# 80149 mem# 1: /UBSTEMP/ghadb_redo01a.log
Thu Dec 06 01:34:06 GMT 2012
Thread 1 cannot allocate new log, sequence 80150
Checkpoint not complete
Current log# 1 seq# 80149 mem# 0: /UBSUNDO/ghadb_redo01b.log
Current log# 1 seq# 80149 mem# 1: /UBSTEMP/ghadb_redo01a.log
Thu Dec 06 01:34:14 GMT 2012
Thread 1 advanced to log sequence 80150 (LGWR switch)
Current log# 2 seq# 80150 mem# 0: /UBSUNDO/ghadb_redo02b.log
Current log# 2 seq# 80150 mem# 1: /UBSTEMP/ghadb_redo02a.log


Kindly advice on how to resolve this issue. Database is up for now but i donot want to bounce DB because of this archiving problem.

Thank you.
  • 1. Re: Checkpoint Not complete in alert log
    sb92075 Guru
    Currently Being Moderated
    PVOWUSU wrote:
    Hello Gurus,

    Alert log keeps displaying the following message:

    Current log# 3 seq# 80148 mem# 0: /UBSUNDO/ghadb_redo03b.log
    Current log# 3 seq# 80148 mem# 1: /UBSTEMP/ghadb_redo03a.log
    Thu Dec 06 01:33:20 GMT 2012
    Thread 1 advanced to log sequence 80149 (LGWR switch)
    Current log# 1 seq# 80149 mem# 0: /UBSUNDO/ghadb_redo01b.log
    Current log# 1 seq# 80149 mem# 1: /UBSTEMP/ghadb_redo01a.log
    Thu Dec 06 01:34:06 GMT 2012
    Thread 1 cannot allocate new log, sequence 80150
    Checkpoint not complete
    Current log# 1 seq# 80149 mem# 0: /UBSUNDO/ghadb_redo01b.log
    Current log# 1 seq# 80149 mem# 1: /UBSTEMP/ghadb_redo01a.log
    Thu Dec 06 01:34:14 GMT 2012
    Thread 1 advanced to log sequence 80150 (LGWR switch)
    Current log# 2 seq# 80150 mem# 0: /UBSUNDO/ghadb_redo02b.log
    Current log# 2 seq# 80150 mem# 1: /UBSTEMP/ghadb_redo02a.log


    Kindly advice on how to resolve this issue. Database is up for now but i donot want to bounce DB because of this archiving problem.

    Thank you.
    Those lines are just informational.
    no error exists
  • 2. Re: Checkpoint Not complete in alert log
    SHANOJ Newbie
    Currently Being Moderated
    http://asktom.oracle.com/pls/asktom/f?p=100:11:0::::P11_QUESTION_ID:69012348056

    http://www.inthebasis.com/solve-checkpoint-complete/
  • 3. Re: Checkpoint Not complete in alert log
    PVOWUSU Newbie
    Currently Being Moderated
    Thanks for your swift response.

    These information were not appearing in the alert log previously. Ever since it started some application processes are failing with error:

    USER MSG : Inside pr_start_sms_log
    USER MSG : current branch : 009
    USER MSG : FailedORA-01115: IO error reading block from file 25 (block # 214503)
    ORA-01110: data file 25: '/UBSDATA/ghadb_users_007.dbf'
    ORA-27091: unable to queue I/O
    ORA-27072: File I/O error
    Linux-x86_64 Error: 11: Resource temporarily unavailable
    Additional info
  • 4. Re: Checkpoint Not complete in alert log
    sb92075 Guru
    Currently Being Moderated
    PVOWUSU wrote:
    Thanks for your swift response.

    These information were not appearing in the alert log previously. Ever since it started some application processes are failing with error:

    USER MSG : Inside pr_start_sms_log
    USER MSG : current branch : 009
    USER MSG : FailedORA-01115: IO error reading block from file 25 (block # 214503)
    ORA-01110: data file 25: '/UBSDATA/ghadb_users_007.dbf'
    ORA-27091: unable to queue I/O
    ORA-27072: File I/O error
    Linux-x86_64 Error: 11: Resource temporarily unavailable
    Additional info
    OS/hardware failure
    Oracle is victim; not the culprit
    check OS "messages" file for details
  • 5. Re: Checkpoint Not complete in alert log
    Osama_Mustafa Oracle ACE
    Currently Being Moderated
    Check MOS Notes :
    Checkpoint Not Complete In Alert.log Due To Setting Of Archive_lag_target [ID 435780.1]

Legend

  • Correct Answers - 10 points
  • Helpful Answers - 5 points