|
Problem IC97143
|
Status: Closed |
DATABASE UPGRADE FAILS WITH SQL20481N |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
Though db2ckupgrade become successful, a database upgrade
fails with SQL20481N
Messages similar to following might be visible in db2diag.log
2013-10-07-10.30.46.270534-300 I389948A348 LEVEL:
Warning
PID : 18089 TID : 2199075095856 PROC : db2bp
INSTANCE: db2inst1 NODE : 000 DB :
TESTDB
APPID : *LOCAL.db2inst1.131007152115
HOSTNAME: host1
FUNCTION: DB2 UDB, base sys utilities, sqlemgdb, probe:556
MESSAGE : Begin db2spcat
2013-10-07-10.30.49.049785-300 I390297A1914 LEVEL: Error
PID : 9709 TID : 2199421708560 PROC :
db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB :
TESTDB
APPHDL : 0-18 APPID:
*LOCAL.db2inst1.131007152115
AUTHID : DB2INST1 HOSTNAME: host1
EDUID : 23 EDUNAME: db2agent (TESTDB) 0
FUNCTION: DB2 UDB, base sys utilities, sys_views, probe:1486
MESSAGE : ZRC=0xFFFFAFFF=-20481
SQL20481N The creation or revalidation of object ""
would result in
an invalid direct or indirect self-reference. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Users trying to upgrade database in V10.1 *
****************************************************************
* PROBLEM DESCRIPTION: *
* Please see Error Description to find the details *
****************************************************************
* RECOMMENDATION: *
* Users can upgrade to DB2 Version 10.1 fix pack 4 or higher *
* to avoid this defect *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Solution |
First fixed in DB2 Version 10.1 fix pack 4 |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC99212
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 23.10.2013
16.06.2014
16.06.2014 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.4
|
 |
