home clear 64x64
en blue 200x116 de orange 200x116 info letter User
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 IC75281 Status: Closed

ADMIN_COPY_SCHEMA() COMPLETES SUCCESSFULLY BUT THE ERROR TABLE CONTAINS
SQL0901N WITH REASON "UNKNOWN DEPENDENT OBJECT TYPE: B"

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
admin_copy_schema() completes successfully but the error table 
contains sql0901n with Reason "Unknown dependent object type: B" 
 
 
Example: 
 
db2 "call sysproc.admin_copy_schema('DB2INST1', 'DB2INST2', 
'COPY', 'DB2INST2', NULL, NULL, 'DB2INST2', 
'COPY_SCHEMA_ERROR')" 
 
  Value of output parameters 
  -------------------------- 
  Parameter Name  : ERRORTABSCHEMA 
  Parameter Value : DB2INST2 
 
  Parameter Name  : ERRORTABNAME 
  Parameter Value : COPY_SCHEMA_ERROR 
 
  Return Status = 0 
 
 
In this example, all objects are copied successfully from source 
schema DB2INST1 to target scheam DB2INST2, but the error table 
DB2INST2.COPY_SCHEMA_ERROR contains sql0901n with Reason 
"Unknown dependent object type: B". For example: 
 
IBM][CLI Driver][DB2/NT] SQL0901N  The SQL statement failed 
because of a non-severe system error. Subsequent SQL statements 
can be processed.  (Reason "Unknown dependent object type: B".) 
SQLSTATE=58004
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* SQL0901N with reason  "UNKNOWN DEPENDENT OBJECT TYPE: B"     * 
* where "Object type: B" is a trigger                          * 
* Cause is with background process.                            * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 9.7 FP5 or newer                              * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
Problem First Fixed in DB2 Version 9.7 Fix Pack 5   (s111017)
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
25.03.2011
16.12.2011
12.07.2012
Problem solved at the following versions (IBM BugInfos)
9.7.FP5
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.5 FixList