Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IT01399 Status: Geschlossen

DATABASE IS MARKED BAD DUE TO "NO ACTIVE SAVE POINT" ERROR FOR
MISHANDLING SAVE POINT WHEN THERE IS AN INTERRUPT.

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
"NO ACTIVE SAVE POINT" ERROR DUE TO MISHANDLING OF SAVE POINT 
POINTERS WHEN THERE IS AN INTERRUPT. 
 
Following is the diagnostic in db2diag.log that reported error: 
 
2013-08-27-19.45.24.706136-240 I229406274A927       LEVEL: Error 
PID     : 34734296             TID  : 151024        PROC : 
db2sysc 0 
INSTANCE: inst               NODE : 000         DB   : db 
APPHDL  : 0-2252               APPID:  appid 
AUTHID  : authid 
EDUID   : 151024               EDUNAME: db2agent (db) 0 
FUNCTION: DB2 UDB, relation data serv, sqlrr_rds_common_post, 
probe:1700 
MESSAGE : Severe TERMINATE err at nest lvl 1, in SQL from rtn 
          WMPIS06.HANDLE_SERVICE_MIN_MAX_INSERT: 
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes 
 sqlcaid : SQLCA     sqlcabc: 136   sqlcode: -1224   sqlerrml: 0 
 sqlerrmc: 
 sqlerrp : SQL09085 
 sqlerrd : (1) 0x00000000      (2) 0x00000000      (3) 
0x00000000 
           (4) 0x00000000      (5) 0x00000000      (6) 
0x00000000 
 sqlwarn : (1)      (2)      (3)      (4)        (5)       (6) 
           (7)      (8)      (9)      (10)        (11) 
 sqlstate: 55032 
 
2013-08-27-19.45.24.706673-240 I229407202A506       LEVEL: 
Severe 
PID     : 34734296             TID  : 151024        PROC : 
db2sysc 0 
INSTANCE: db2               NODE : 000         DB   : db 
APPHDL  : 0-2252               APPID: appid 
AUTHID  : authid 
EDUID   : 151024               EDUNAME: db2agent (db) 0 
FUNCTION: DB2 UDB, relation data serv, sqlreesp, probe:400 
RETCODE : ZRC=0x87100020=-2028994528=SQLP_TNSV "No active save 
point" 
          DIA8529C There were no active save points.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2LUW                                                       * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* "NO ACTIVE SAVE POINT" ERROR DUE TO MISHANDLING OF SAVE      * 
* POINT                                                        * 
* POINTERS WHEN THERE IS AN INTERRUPT.                         * 
*                                                              * 
* Following is the diagnostic in db2diag.log that reported     * 
* error:                                                       * 
*                                                              * 
* 2013-08-27-19.45.24.706136-240 I229406274A927       LEVEL:   * 
* Error                                                        * 
* PID     : 34734296             TID  : 151024        PROC :   * 
* db2sysc 0                                                    * 
* INSTANCE: inst               NODE : 000         DB   : db    * 
* APPHDL  : 0-2252               APPID:  appid                 * 
* AUTHID  : authid                                             * 
* EDUID   : 151024               EDUNAME: db2agent (db) 0      * 
* FUNCTION: DB2 UDB, relation data serv,                       * 
* sqlrr_rds_common_post,                                       * 
* probe:1700                                                   * 
* MESSAGE : Severe TERMINATE err at nest lvl 1, in SQL from    * 
* rtn                                                          * 
*           WMPIS06.HANDLE_SERVICE_MIN_MAX_INSERT:             * 
* DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes                * 
*  sqlcaid : SQLCA     sqlcabc: 136   sqlcode: -1224           * 
* sqlerrml: 0                                                  * 
*  sqlerrmc:                                                   * 
*  sqlerrp : SQL09085                                          * 
*  sqlerrd : (1) 0x00000000      (2) 0x00000000      (3)       * 
* 0x00000000                                                   * 
*            (4) 0x00000000      (5) 0x00000000      (6)       * 
* 0x00000000                                                   * 
*  sqlwarn : (1)      (2)      (3)      (4)        (5)         * 
* (6)                                                          * 
*            (7)      (8)      (9)      (10)        (11)       * 
*  sqlstate: 55032                                             * 
*                                                              * 
* 2013-08-27-19.45.24.706673-240 I229407202A506       LEVEL:   * 
* Severe                                                       * 
* PID     : 34734296             TID  : 151024        PROC :   * 
* db2sysc 0                                                    * 
* INSTANCE: db2               NODE : 000         DB   : db     * 
* APPHDL  : 0-2252               APPID: appid                  * 
* AUTHID  : authid                                             * 
* EDUID   : 151024               EDUNAME: db2agent (db) 0      * 
* FUNCTION: DB2 UDB, relation data serv, sqlreesp, probe:400   * 
* RETCODE : ZRC=0x87100020=-2028994528=SQLP_TNSV "No active    * 
* save                                                         * 
* point"                                                       * 
*           DIA8529C There were no active save points.         * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 10.1 Fp4                                      * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Lösung
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
29.04.2014
09.06.2014
09.06.2014
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.4 FixList