Results 1 to 11 of 11
  1. #1
    Join Date
    Jul 2007
    Posts
    6

    Unanswered: db2stop force hang

    When I ran 'db2stop force', it hang. I get the following messages in db2diag.log. Pls help me!
    2007-07-02-12.22.42.666825+480 I32543726A297 LEVEL: Warning
    PID : 524484 TID : 1 PROC : db2loggr (ABSTEST) 0
    INSTANCE: db2inst1 NODE : 000
    FUNCTION: DB2 UDB, data protection, sqlpghck, probe:1780
    MESSAGE : DB2 is waiting for log files to be archived.

    2007-07-02-12.23.42.667245+480 I32544024A402 LEVEL: Warning
    PID : 524484 TID : 1 PROC : db2loggr (ABSTEST) 0
    INSTANCE: db2inst1 NODE : 000
    FUNCTION: DB2 UDB, data protection, sqlpghck, probe:1800
    DATA #1 : String, 131 bytes
    DB2 was unable to confirm logs were archived.
    Return code -2029059911, FirstArchNum 274, FirstArchNum2 4294967295, HeadExtentID 296

    2007-07-02-12.28.44.681513+480 I32544427A383 LEVEL: Warning
    PID : 921672 TID : 1 PROC : db2agent (idle) 0
    INSTANCE: db2inst1 NODE : 000 DB : ABSTEST
    APPHDL : 0-50 APPID: *LOCAL.db2inst1.070628165841
    FUNCTION: DB2 UDB, data protection, sqlpterm, probe:2330
    MESSAGE : Some daemon is taking too long to shut down

  2. #2
    Join Date
    Jun 2006
    Posts
    471
    (same entry as in ittools)
    are you using userexit or tsm or any other product to archive the log ?
    do you have problems with regular archive of log ?
    maybe the library manager (tsm) is busy or no tape drive is free
    archive to tape or disk ?
    Best Regards, Guy Przytula
    DB2 UDB LUW certified V6/7/8

  3. #3
    Join Date
    Jul 2007
    Posts
    6
    Quote Originally Posted by guyprzytula
    (same entry as in ittools)
    are you using userexit or tsm or any other product to archive the log ?
    aix5L+db2+tsm+hacmp logretain=on


    do you have problems with regular archive of log ?
    no

    maybe the library manager (tsm) is busy or no tape drive is free
    there are two database in my instance
    there is only one tape drive in my tap lib

    archive to tape or disk ?
    don't do it

  4. #4
    Join Date
    Jul 2007
    Posts
    6
    how can I confirm archive logs have being completed before I ran 'db2stop force'

  5. #5
    Join Date
    Jun 2006
    Posts
    471
    try the command
    db2 archive log for db dbname
    do you archive to tape/disk/tsm ?
    Best Regards, Guy Przytula
    DB2 UDB LUW certified V6/7/8

  6. #6
    Join Date
    Jul 2007
    Posts
    6
    archive to TSM.

    I don't use the following command before
    db2 archive log for db dbname

    I don't kown if this command is asynchronous, so it will return immediately. I can't comfiirm if log archive have been performed.

    or this command is synchronous,it will not return before log archive operation have been performed completely.

    Do anyone have the experience using this command? please help me

    My machine is a product system, I can't test this command in it.

  7. #7
    Join Date
    Jun 2006
    Posts
    471
    if you use tsm there is a file ARCHIVE.LOG that will keep history about archived files with return code
    there is also an entry in db2diag.log whenever a file is archived
    Best Regards, Guy Przytula
    DB2 UDB LUW certified V6/7/8

  8. #8
    Join Date
    Jul 2007
    Posts
    6
    We assume that there are three active log files and two of them are full before I stop DB2.
    I will stop all applications that connect to db2 before I ran "db2stop force".
    In that time, two full log will be closed and beginning to archive.
    I can confirm the two log archive have been performed through looking at db2diag.log or ARCHIVE.LOG. I can ran " db2stop force"

    BUT how can I confirm how many active full logs are there before I stop db2

    I can kown the first active log file through looking at "db cfg"

  9. #9
    Join Date
    Jun 2006
    Posts
    471
    whenever an active log file is full, it will be archived immediatly and another log file will be requested
    Best Regards, Guy Przytula
    DB2 UDB LUW certified V6/7/8

  10. #10
    Join Date
    Jul 2007
    Posts
    6
    Dear guyprzytula !

    One active log file witch is full will be archived until all tranctions in it are commited or rollbacked

  11. #11
    Join Date
    Jun 2006
    Posts
    471
    according the doc
    When archiving, a log file is passed to the user exit when it is full, even if the log file is still active and is needed for normal processing. This allows copies of the data to be moved away from volatile media as quickly as possible. The log file passed to the user exit is retained in the log path directory until it is no longer needed for normal processing. At this point, the disk space is reused.
    Best Regards, Guy Przytula
    DB2 UDB LUW certified V6/7/8

Posting Permissions

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