suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IT30578 Status: Closed

IN DPF ENVIRONMENT THE RESTART DATABASE COMMAND MAY FAIL WITH SQL10003C IF
TABLESPACE(S) ARE IN AN ABNORMAL STATE

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
The error can be encountered if a database crashes while
transactions are indoubt and during the subsequent crash
recovery a storage error is encountered on a tablespace
which makes the tablespace inaccessible.  After completing
crash recovery, Db2 will detect the presence of indoubt
transactions and will attempt to resolve it.  If the indoubt
transaction made changes to the tablespace that is no
longer accessible, SQL10003C error is returned and the
database is shut down.

$ db2 restart db sample
SQL10003C  There are not enough system resources to process the
request.  The request cannot be processed.  SQLSTATE=57011


The following messages can be found in db2diag.log.

2019-10-09-02.16.00.686210-420 I28689E515            LEVEL: Info
PID     : 3015                 TID : 140427164378880 PROC :
db2sysc 2
INSTANCE: db2v1058             NODE : 002            DB   :
SAMPLE
APPHDL  : 2-57                 APPID: *N2.db2v1058.191009091600
AUTHID  : DB2V1058             HOSTNAME: TURING11
EDUID   : 67                   EDUNAME: db2agent (SAMPLE) 2
FUNCTION: DB2 UDB, recovery manager, sqlpresr, probe:3170
DATA #1 : 
Crash recovery completed. Next LSN is 0000000000001969.

2019-10-09-02.16.00.686538-420 I29205E539            LEVEL:
Warning
PID     : 3015                 TID : 140427164378880 PROC :
db2sysc 2
INSTANCE: db2v1058             NODE : 002            DB   :
SAMPLE
APPHDL  : 2-57                 APPID: *N2.db2v1058.191009091600
AUTHID  : DB2V1058             HOSTNAME: TURING11
EDUID   : 67                   EDUNAME: db2agent (SAMPLE) 2
FUNCTION: DB2 UDB, recovery manager, sqlpresr, probe:3280
DATA #1 : 
In-doubt transaction(s) exists at the end of crash recovery on
log stream 2.

2019-10-09-02.16.00.686951-420 E29745E495            LEVEL:
Warning
PID     : 3015                 TID : 140427164378880 PROC :
db2sysc 2
INSTANCE: db2v1058             NODE : 002            DB   :
SAMPLE
APPHDL  : 2-57                 APPID: *N2.db2v1058.191009091600
AUTHID  : DB2V1058             HOSTNAME: TURING11
EDUID   : 67                   EDUNAME: db2agent (SAMPLE) 2
FUNCTION: DB2 UDB, recovery manager, sqlpssdw, probe:100
MESSAGE : Resolving indoubt transactions with other nodes.

2019-10-09-02.16.00.918253-420 I30241E622            LEVEL:
Severe
PID     : 3015                 TID : 140427097270016 PROC :
db2sysc 2
INSTANCE: db2v1058             NODE : 002            DB   :
SAMPLE
APPHDL  : 2-57                 APPID: *N2.db2v1058.191009091600
AUTHID  : DB2V1058             HOSTNAME: TURING11
EDUID   : 108                  EDUNAME: db2agnsc (SAMPLE) 2
FUNCTION: DB2 UDB, data management, sqldmund, probe:1184
MESSAGE :
ZRC=0x80020033=-2147352525=SQLB_NOT_ALLOWED_ROLLFORWARD_P
          "Access not allowed. Tblspc RF Pending."
DATA #1 : 
Error during UNDO of LSN: 0000000000001965

2019-10-09-02.16.00.918622-420 I30864E554            LEVEL:
Severe
PID     : 3015                 TID : 140427097270016 PROC :
db2sysc 2
INSTANCE: db2v1058             NODE : 002            DB   :
SAMPLE
APPHDL  : 2-57                 APPID: *N2.db2v1058.191009091600
AUTHID  : DB2V1058             HOSTNAME: TURING11
EDUID   : 108                  EDUNAME: db2agnsc (SAMPLE) 2
FUNCTION: DB2 UDB, data management, sqldmund, probe:1184
RETCODE :
ZRC=0x80020033=-2147352525=SQLB_NOT_ALLOWED_ROLLFORWARD_P
          "Access not allowed. Tblspc RF Pending."

2019-10-09-02.16.00.918823-420 I31419E739            LEVEL:
Severe
PID     : 3015                 TID : 140427097270016 PROC :
db2sysc 2
INSTANCE: db2v1058             NODE : 002            DB   :
SAMPLE
APPHDL  : 2-57                 APPID: *N2.db2v1058.191009091600
AUTHID  : DB2V1058             HOSTNAME: TURING11
EDUID   : 108                  EDUNAME: db2agnsc (SAMPLE) 2
FUNCTION: DB2 UDB, data management, sqldmund, probe:1184
MESSAGE : Error during UNDO of log record:
DATA #1 : Hexdump, 38 bytes
0x00007FB7BB3FC2E0 : 01A2 0200 1400 0000 1200 F41A 0700 0000
................
0x00007FB7BB3FC2F0 : 0000 041B 0000 1200 0100 0A00 0800 0000
................
0x00007FB7BB3FC300 : 0008 0000 0000
......
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* Server can't bring up due to indoubt transaction and  rfd    *
* pending tblspace                                             *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to Db2 v11.1.4.6                                     *
****************************************************************
Local Fix:
Solution
Workaround
****************************************************************
* USERS AFFECTED:                                              *
* Server can't bring up due to indoubt transaction and  rfd    *
* pending tblspace                                             *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to Db2 v11.1.4.6                                     *
****************************************************************
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
11.10.2019
04.11.2019
04.11.2019
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)