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 IT39796 Status: Closed

DB2 UPGRADE DB MAY TRAP or FAIL WITH SQL1704N IF THE DB CONTAINSA TYPE
WITH (SCHEMA+NAME) LENGTH OVER 56 CHARACTERS

product:
DB2 FOR LUW / DB2FORLUW / B50 - DB2
Problem description:
DB migration may trap or fail with SQL1704N if there is a
created type with length more than 56 schema+name combined.

Trap during restore upgrade:

$  db2 restore db testdb
SQL2519N  The database was restored but the restored database
was not upgraded
to the current release.  Error "-1224" with tokens "-2097151964
* * * *
SEMAPHORE WAIT                            " is returned.

Failure during normal upgrade
$ db2 upgrade db testdb
   SQL1704N  Database upgrade failed.  Reason code "2".

On AIX, the FODC trap.txt file will show a stack similar to the
following:

sqlrlm_catalogFixup
sqlrlm_catalog_parallel_migrate
sqlrlm_catalog_migrate
sqlefmig
sqlemigr
AppLocalStart

db2diag.log leading up to the trap:
2020-10-16-17.45.39.835593-240 I972328E606           LEVEL:
Severe
PID     : 24164                TID : 140243160262400 PROC :
db2sysc
INSTANCE: db2inst1           NODE : 000            DB   : TESTDB
APPHDL  : 0-11                APPID:
*LOCAL.username.201016214522
AUTHID  : authid              HOSTNAME: hostname
EDUID   : 391                  EDUNAME: db2agent (TESTDB)
FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_ffdc,
probe:550
RETCODE : ZRC=0x87120007=-2028863481=SQLR_SEVERE_PGM_ERROR
          "Severe programming error"
          DIA8516C A severe internal processing error has
occurred.
...
2020-10-16-17.45.40.027818-240 E1007602E1606         LEVEL:
Severe
PID     : 24164                TID : 140243160262400 PROC :
db2sysc
INSTANCE: db2inst1         NODE : 000            DB   : TESTDB
APPHDL  : 0-11                APPID:
*LOCAL.username.201016214522
AUTHID  : authid              HOSTNAME: hostname
EDUID   : 391                  EDUNAME: db2agent (TESTDB)
FUNCTION: DB2 UDB, oper system services, sqloEDUCodeTrapHandler,
probe:90
MESSAGE : ADM14011C  A critical failure has caused the following
type of error:
          "Trap". The database manager cannot recover from the
failure. First
          Occurrence Data Capture (FODC) was invoked in the
following mode:
          "Automatic". FODC diagnostic information is located in
the following
          directory:

"/home/username/sqllib/db2dump/FODC_Trap_2020-10-16-17.45.27.651
181_000
          0/".

For LINUXAMD64, db2diag.log may show:

MESSAGE : Stack analysis failed, which implies stack corruption
or failed to do 'stack walk'.

with the trap.txt showing a partial stack

 _ZN6migLog7logTimeEPKcjP10SQLD_VALUEm + 0x04a9
(/home/username/sqllib/lib64/libdb2e.so.1)

        0x00007F94F3F9B319 : C3B809000000E924
Problem Summary:
The problem is first fixed on Db2 v11.5.5.0
Local Fix:
Drop the long created type before upgrade.
Solution
Workaround
The problem is first fixed on Db2 v11.5.5.0
Comment
Upgrade to Db2 v11.5.5.0.
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
29.01.2022
29.01.2022
29.03.2022
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)