Results 1 to 4 of 4
  1. #1
    Join Date
    Aug 2007
    Location
    Chennai, India
    Posts
    3

    Unanswered: Database archive log file sequnce change.

    Hi Friends,

    I have got one issue with DB2 database in archive logging. The archive logs naming generated as regularly in sequence number and suddenly it got changed. Since I don’t have DB2 database admin exposure, not able to find the root cause of this change.
    Currently database is working normally.

    Please see below for more information.

    -rw------- 1 db2admin ses 102408192 Mar 29 01:38 S0000545.LOG
    -rw------- 1 db2admin ses 102408192 Mar 29 14:22 S0000546.LOG
    -rw------- 1 db2admin ses 102408192 Mar 30 01:00 S0000547.LOG
    -rw------- 1 db2admin ses 102408192 Mar 30 01:38 S0000548.LOG
    -rw------- 1 db2admin ses 102408192 Mar 30 14:43 S0000549.LOG
    -rw------- 1 db2admin ses 102408192 Mar 30 17:38 S0000550.LOG
    -rw------- 1 db2admin ses 102408192 Mar 31 01:38 S0000551.LOG
    -rw------- 1 db2admin ses 102408192 Mar 31 12:43 S0000452.LOG
    -rw------- 1 db2admin ses 102408192 Mar 31 16:12 S0000552.LOG
    -rw------- 1 db2admin ses 96952320 Apr 1 01:01 S0000453.LOG
    -rw------- 1 db2admin ses 102408192 Apr 1 01:38 S0000553.LOG
    -rw------- 1 db2admin ses 102408192 Apr 1 12:43 S0000454.LOG
    -rw------- 1 db2admin ses 102408192 Apr 1 14:42 S0000554.LOG

    Really appreciates for all suggestions to find the root cause of this issue.

    Thank you,
    Pratheep

  2. #2
    Join Date
    Jan 2009
    Location
    Zoetermeer, Holland
    Posts
    746
    Check your db2diag.log very thouroughly for that period. Computers do not play april-fools so something happened. db2diag should be able to tell.

  3. #3
    Join Date
    Aug 2007
    Location
    Chennai, India
    Posts
    3
    Hi dr_te_z,
    Thanks for your suggestion. I have fully verified the db2diag.log file and during that period
    and didnt find any errors.
    Is anyother way is there to find the root cause. \
    Regards,
    Pratheep

  4. #4
    Join Date
    Nov 2005
    Location
    IL
    Posts
    557
    You had a transaction that was using S0000453.LOG still out there mid flight. Then at 01:01 on April 1st it finished or finally issued a commit. That is why your log now mixed in with a newer logs.

    This timestamp is not when record was created, but rather when last transaction was committed.
    --
    IBM Certified DBA on DB2 for Linux, UNIX, and Windows

    DB2 v9.7.0.6 os 6.1.0.0

Tags for this Thread

Posting Permissions

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