Some messages are considered to be at the Severe level because the condition may impact all applications access to the database. The messages generated when the DB2 database encounters a bad page is an example of a severe level message. This condition causes the DB2 database to be stopped. This will alert the DBA to this condition which may limited to one table, but could possibly effect more objects in the database.

Examples of these messages are:

APPHDL : 0-16                      APPID: *LOCAL.INST4.050308164025
FUNCTION: DB2 UDB, data management, sqldLoadTCB, probe:4512
RETCODE : ZRC=0x86020019=-2046689255=SQLB_CSUM "Bad Page, Checksum Error"
            DIA8426C A invalid page checksum was found for page "".
2005-03-08-11.40.27.504000-300 I383755H457               LEVEL: Severe
PID       : 2644                   TID : 3524            PROC : db2syscs.exe
INSTANCE: INST4                    NODE : 000            DB    : TP1
2005-03-08-11.40.27.504000-300 I383287H466               LEVEL: Severe

PID       : 2644                   TID : 3524            PROC : db2syscs.exe
INSTANCE: INST4                    NODE : 000            DB    : TP1APPHDL : 0-16                      APPID: *LOCAL.INST4.050308164025
FUNCTION: DB2 UDB, data management, sqldLoadTCB, probe:4512
MESSAGE : Error loading TCB. tcbFlags =
DATA #1 : Hexdump, 4 bytes
0x081E6F2C : 2400 0000                                          $...

2005-03-08-11.40.27.514000-300 I384214H354               LEVEL: Severe
PID      : 2644                    TID : 3524            PROC : db2syscs.exe
INSTANCE: INST4                    NODE : 000            DB    : TP1
APPHDL : 0-16                      APPID: *LOCAL.INST4.050308164025
MESSAGE : SQLD_TCB:
DATA #1 : String, 39 bytes
Perm Table(11:2)=TBSPACEID=11.TABLEID=2

2005-03-08-11.40.27.514000-300 I384570H162               LEVEL: Severe
PID:2644 TID:3524 NODE:000 Title: SQLD_TCB
Dump File:C:\PROGRA~1\IBM\SQLLIB\INST4\26443524.000

The messages indicate the type of error found and also the tablespace ID (11) and table ID (2) where the bad page was found. The DB2 catalog view SYSCAT.TABLES can be used to locate the table schema and table name based on the tablespace and table IDs.

The db2dart utility could be used offline to scan the table space. The INSPECT command can be used online to scan the database, table space, or table to look for additional internal damage.

Notice that one message indicates that a dump file '26443524.000' was created based on this severe error in the database.
A database or table space restore may be required to allow the applications to resume normal access to the effected tables. Access to other table spaces should not be effected.

The INSPECT command could be used online to search a table space or table after a bad page is encountered.

The following is an example of the report generated from running Inspect:

db2 inspect check database begin TBSPACEID 11 OBJECTID 2 results checkts.out

DATABASE: TP1
VERSION : SQL08020
2005-03-08-11.40.27.444000
Action: CHECK DATABASE
Tablespace ID: 11
Result file name: insp1.txt
Database phase start.
  Tablespace phase start. Tablespace ID: 11
   Tablespace name: TESTTS
   Tablespace Type: SMS - System Managed Space; Extent size: 16; Page size: 4096; Number of containers: 1
   Container name: C:\TP1\test01
    Table phase start (ID Signed: 2, Unsigned: 2; Tablespace ID: 11) :
      Data phase start. Object: 2  Tablespace: 11

             Warning: Object is known to be in error state x200.
            Warning: Object is in corruption detected state.
             Warning: Object is not scanned.
             Data phase end.
           Table phase end.
         Tablespace phase end.
       Database phase end.
       Warning(s) identified during processing.
       Processing has completed. 2005-03-08-11.40.27.524000