Results 1 to 6 of 6
  1. #1
    Join Date
    Jul 2004
    Posts
    306

    Unanswered: Missing log file (but it has been archived)

    DB2 9.7 in Linux

    Hey all I've got a DB giving:
    SQL1036C An I/O error occurred while accessing the database. SQLSTATE=58030

    On inspection the diaglog indicates
    Code:
    2013-01-18-11.17.19.504688+660 I3350180E388        LEVEL: Error
    PID     : 10306                TID  : 47672870299968PROC : db2sysc
    INSTANCE: db2dev               NODE : 000          DB   : SLADM
    EDUID   : 16415                EDUNAME: db2loggr (SLADM)
    FUNCTION: DB2 UDB, data protection services, sqlpgInitRecoverable, probe:1370
    DATA #1 : <preformatted>
    Log file S0111648.LOG not found.
    
    2013-01-18-11.17.19.504885+660 I3350569E437        LEVEL: Error
    PID     : 10306                TID  : 47672870299968PROC : db2sysc
    INSTANCE: db2dev               NODE : 000          DB   : SLADM
    EDUID   : 16415                EDUNAME: db2loggr (SLADM)
    FUNCTION: DB2 UDB, data protection services, sqlpgLoggrInit, probe:430
    RETCODE : ZRC=0x860F000A=-2045837302=SQLO_FNEX "File not found."
              DIA8411C A file "" could not be found.
    
    2013-01-18-11.17.19.505072+660 I3351007E184       LEVEL: Error
    PID:10306 TID:47672870299968 NODE:000 Title: SQLP_DBCB
    Dump File:/db2home/db2dev/sqllib/db2dump/10306.16415.000.dump.bin
    
    2013-01-18-11.17.19.506893+660 I3351192E371        LEVEL: Severe
    PID     : 10306                TID  : 47672870299968PROC : db2sysc
    INSTANCE: db2dev               NODE : 000          DB   : SLADM
    EDUID   : 16415                EDUNAME: db2loggr (SLADM)
    FUNCTION: DB2 UDB, data protection services, sqlpgasn, probe:4000
    MESSAGE : Logging can not continue due to an error.
    
    2013-01-18-11.17.19.507042+660 I3351564E517        LEVEL: Severe
    PID     : 10306                TID  : 47672819968320PROC : db2sysc
    INSTANCE: db2dev               NODE : 000          DB   : SLADM
    APPHDL  : 0-20086              APPID: *LOCAL.db2dev.130118001719
    AUTHID  : DB2DEV
    EDUID   : 14892                EDUNAME: db2agent (SLADM)
    FUNCTION: DB2 UDB, data protection services, sqlpgint, probe:9030
    RETCODE : ZRC=0x860F000A=-2045837302=SQLO_FNEX "File not found."
              DIA8411C A file "" could not be found.
    The log in question was archived 9 days ago and subsequently deleted (this is a non-prod DB).

    Any ideas why DB2 is looking for an old archive log? Or what might have caused this?

    Cheers,
    Last edited by meehange; 01-18-13 at 00:40.

  2. #2
    Join Date
    Jun 2003
    Location
    Toronto, Canada
    Posts
    5,516
    Provided Answers: 1
    How do you archive logs and how do you decide when to delete them?
    ---
    "It does not work" is not a valid problem statement.

  3. #3
    Join Date
    Jul 2004
    Posts
    306
    They are just archived to local disk, then a cron job deletes them regularly.
    This is a Dev environment so recoverability is not paramount, but I'd really like to figure out what went wrong in case it comes up on a more important environment.
    Last edited by meehange; 01-17-13 at 23:35.

  4. #4
    Join Date
    Jun 2003
    Location
    Toronto, Canada
    Posts
    5,516
    Provided Answers: 1
    Quote Originally Posted by meehange View Post
    They are just archived to local disk, then a cron job deletes them regularly.
    Sure. But you didn't answer either of my questions.

    There have been a few discussions about log management on this board, see if they give you a better view of what's happening.
    ---
    "It does not work" is not a valid problem statement.

  5. #5
    Join Date
    Jul 2004
    Posts
    306
    Quote Originally Posted by n_i View Post
    Sure. But you didn't answer either of my questions.

    There have been a few discussions about log management on this board, see if they give you a better view of what's happening.
    Not sure I follow.. they are archived using LOGARCHMETH1 = DISK:/Localfilesystem/bla

    They are deleted from the archive directory at regular time intervals.

    Under what circumstance would db2 need to refer back to a closed, archived log from weeks gone by? (Other than Restore/Rolforward or HADR, neither of which is the case here)

  6. #6
    Join Date
    Jun 2003
    Location
    Toronto, Canada
    Posts
    5,516
    Provided Answers: 1
    http://www.dbforums.com/db2/1685645-...ctive-log.html
    http://www.dbforums.com/db2/1688772-...secondary.html

    If you have the currently committed semantics enabled, that might be another reason for DB2 to access the log file.
    ---
    "It does not work" is not a valid problem statement.

Posting Permissions

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