Results 1 to 5 of 5

Thread: db2 crash

  1. #1
    Join Date
    Jul 2003
    Posts
    5

    Question Unanswered: db2 crash

    Hi folks!

    I have problems with offline backups. Just after midnight the application disconnects from the DB and starts with backup. After backup is done it waits for few minutes and then connects to the db again. For few minutes everything is OK, but then DB2 disconnects all aplications:

    [SQLSTATE=40003 - [IBM][CLI Driver][DB2/NT] SQL1224N A database agent could not be started to service a request, or was terminated as a result of a database system shutdown or a force command. SQLSTATE=55032 [Native Error=-1224]]

    [SQLSTATE=08003 - [IBM][CLI Driver] CLI0106E Connection is closed. SQLSTATE=08003 [Native Error=-99999]]

    In db2diag.log I have this:

    2003-02-18-03.44.02.312000 InstanceB2 Node:000
    PID:1240(db2syscs.exe) TID:1968 Appid:*LOCAL.DB2.030703094551
    buffer_pool_services sqlbWritePageToContainer Probe:30 Database:PRO_DB

    Obj={pool:2;obj:5;type:1} State=x27 Cont=0 Offset=64017 BlkSize=12

    Data TitleQLB_OBJECT_DESC PID:1240 TID:1968 Node:000
    0200 0500 0200 0500 0100 0000 0073 7347 .............ssG
    ca36 0000 0000 0000 0000 0000 0000 0000 6..............
    0000 0000 0100 0000 2700 0000 0000 0000 ........'.......
    0010 0000 2000 0000 0100 0000 0200 0501 .... ...........
    48b7 7501 3080 c101 Hu.0.

    2003-02-18-03.44.02.593000 InstanceB2 Node:000
    PID:1240(db2syscs.exe) TID:1968 Appid:*LOCAL.DB2.030703094551
    buffer_pool_services sqlbwrpg Probe:1120 Database:PRO_DB
    DIA3811C A locked file was encountered.
    ...
    ... (full of erorrs)
    ...
    2003-02-18-03.44.03.515000 InstanceB2 Node:000
    PID:1172(db2syscs.exe) TID:1968 Appid:*LOCAL.DB2.030218024403
    base_sys_utilities sqledint Probe:0 Database:PRO_DB

    Crash Recovery is needed.

    2003-02-18-03.44.03.625000 InstanceB2 Node:000
    PID:1172(db2syscs.exe) TID:1968 Appid:*LOCAL.DB2.030218024403
    recovery_manager sqlpresr Probe:1 Database:PRO_DB
    DIA3908W Crash recovery has been initiated. Lowtran LSN is "00329E7F000C",
    Minbuff LSN is "00329E7F000C".

    2003-02-18-03.44.03.703000 InstanceB2 Node:000
    PID:1172(db2syscs.exe) TID:1968 Appid:*LOCAL.DB2.030218024403
    recovery_manager sqlprecm Probe:125 Database:PRO_DB

    Using parallel recovery with 3 agents 3 QSets 21 queues and 125 chunks


    2003-02-18-03.44.03.890000 InstanceB2 Node:000
    PID:1172(db2syscs.exe) TID:1968 Appid:*LOCAL.DB2.030218024403
    recovery_manager sqlprecm Probe:400 Database:PRO_DB
    DIA3916W Forward phase of crash recovery has completed. Next LSN is
    "00329E7F070B".

    2003-02-18-03.44.04.078000 InstanceB2 Node:000
    PID:1172(db2syscs.exe) TID:1968 Appid:*LOCAL.DB2.030218024403
    recovery_manager sqlpresr Probe:170 Database:PRO_DB
    DIA3909W Crash recovery completed. Next LSN is "00329E7F08D6".

    On the machine we have: DB2 V7.2.3, WIN2k.

    Thank's in advance

  2. #2
    Join Date
    Aug 2001
    Location
    UK
    Posts
    4,650

    Re: db2 crash

    This is not an unexpected behaviour ...

    If you froce the applications off the database, the next time the database starts , db2 has to do a crash recovery ... this error can be seen even if you do a connect from the command line ...

    So, to avoid this error, terminate the applications 'gracefully' or retry connecting to the database , if this error occurs ..

    Cheers

    Sathyaram

    Originally posted by mariborcan
    Hi folks!

    I have problems with offline backups. Just after midnight the application disconnects from the DB and starts with backup. After backup is done it waits for few minutes and then connects to the db again. For few minutes everything is OK, but then DB2 disconnects all aplications:

    [SQLSTATE=40003 - [IBM][CLI Driver][DB2/NT] SQL1224N A database agent could not be started to service a request, or was terminated as a result of a database system shutdown or a force command. SQLSTATE=55032 [Native Error=-1224]]

    [SQLSTATE=08003 - [IBM][CLI Driver] CLI0106E Connection is closed. SQLSTATE=08003 [Native Error=-99999]]

    In db2diag.log I have this:

    2003-02-18-03.44.02.312000 InstanceB2 Node:000
    PID:1240(db2syscs.exe) TID:1968 Appid:*LOCAL.DB2.030703094551
    buffer_pool_services sqlbWritePageToContainer Probe:30 Database:PRO_DB

    Obj={pool:2;obj:5;type:1} State=x27 Cont=0 Offset=64017 BlkSize=12

    Data TitleQLB_OBJECT_DESC PID:1240 TID:1968 Node:000
    0200 0500 0200 0500 0100 0000 0073 7347 .............ssG
    ca36 0000 0000 0000 0000 0000 0000 0000 6..............
    0000 0000 0100 0000 2700 0000 0000 0000 ........'.......
    0010 0000 2000 0000 0100 0000 0200 0501 .... ...........
    48b7 7501 3080 c101 Hu.0.

    2003-02-18-03.44.02.593000 InstanceB2 Node:000
    PID:1240(db2syscs.exe) TID:1968 Appid:*LOCAL.DB2.030703094551
    buffer_pool_services sqlbwrpg Probe:1120 Database:PRO_DB
    DIA3811C A locked file was encountered.
    ...
    ... (full of erorrs)
    ...
    2003-02-18-03.44.03.515000 InstanceB2 Node:000
    PID:1172(db2syscs.exe) TID:1968 Appid:*LOCAL.DB2.030218024403
    base_sys_utilities sqledint Probe:0 Database:PRO_DB

    Crash Recovery is needed.

    2003-02-18-03.44.03.625000 InstanceB2 Node:000
    PID:1172(db2syscs.exe) TID:1968 Appid:*LOCAL.DB2.030218024403
    recovery_manager sqlpresr Probe:1 Database:PRO_DB
    DIA3908W Crash recovery has been initiated. Lowtran LSN is "00329E7F000C",
    Minbuff LSN is "00329E7F000C".

    2003-02-18-03.44.03.703000 InstanceB2 Node:000
    PID:1172(db2syscs.exe) TID:1968 Appid:*LOCAL.DB2.030218024403
    recovery_manager sqlprecm Probe:125 Database:PRO_DB

    Using parallel recovery with 3 agents 3 QSets 21 queues and 125 chunks


    2003-02-18-03.44.03.890000 InstanceB2 Node:000
    PID:1172(db2syscs.exe) TID:1968 Appid:*LOCAL.DB2.030218024403
    recovery_manager sqlprecm Probe:400 Database:PRO_DB
    DIA3916W Forward phase of crash recovery has completed. Next LSN is
    "00329E7F070B".

    2003-02-18-03.44.04.078000 InstanceB2 Node:000
    PID:1172(db2syscs.exe) TID:1968 Appid:*LOCAL.DB2.030218024403
    recovery_manager sqlpresr Probe:170 Database:PRO_DB
    DIA3909W Crash recovery completed. Next LSN is "00329E7F08D6".

    On the machine we have: DB2 V7.2.3, WIN2k.

    Thank's in advance
    Visit the new-look IDUG Website , register to gain access to the excellent content.

  3. #3
    Join Date
    Jul 2003
    Posts
    5

    Re: db2 crash

    Hi Sathyaram!

    Applications are not forced, they're disconnected 'gracefully'!
    And yes I've already tried to connect again to the database,
    but this is not a solution for me. I would like to know what is
    going on with DB2.

    Cheers

    Mariborcan


    Originally posted by sathyaram_s
    This is not an unexpected behaviour ...

    If you froce the applications off the database, the next time the database starts , db2 has to do a crash recovery ... this error can be seen even if you do a connect from the command line ...

    So, to avoid this error, terminate the applications 'gracefully' or retry connecting to the database , if this error occurs ..

    Cheers

    Sathyaram

  4. #4
    Join Date
    Aug 2001
    Location
    UK
    Posts
    4,650

    Re: db2 crash

    If you can reproduce the error easily, I would suggest that you contact IBM Support .... They might request for a trace ...

    After you 'gracefuly' terminate your applications, and when you are convinced that the database has no connections, before starting backup, can you check the db cfg and see what 'Database is Consistent' flag says. Again before doing the first connection, check the same ... You will be able to narrow down when the error 'creeps' in ...

    HTH

    Sathyaram

    Originally posted by mariborcan
    Hi Sathyaram!

    Applications are not forced, they're disconnected 'gracefully'!
    And yes I've already tried to connect again to the database,
    but this is not a solution for me. I would like to know what is
    going on with DB2.

    Cheers

    Mariborcan
    Visit the new-look IDUG Website , register to gain access to the excellent content.

  5. #5
    Join Date
    Jul 2003
    Posts
    5

    Re: db2 crash

    Hi Sathyaram!

    The problem is that I can't reproduce the error. The error occurs
    2-3 times per week. In other cases everything is OK.

    Thank's and best regards, Mariborcan

    Originally posted by sathyaram_s
    If you can reproduce the error easily, I would suggest that you contact IBM Support .... They might request for a trace ...

    After you 'gracefuly' terminate your applications, and when you are convinced that the database has no connections, before starting backup, can you check the db cfg and see what 'Database is Consistent' flag says. Again before doing the first connection, check the same ... You will be able to narrow down when the error 'creeps' in ...

    HTH

    Sathyaram

Posting Permissions

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