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

ADMIN_MOVE_TABLE MIGHT PRODUCE TRAP OR FAIL IF ORIGINAL TABLE HAS MORE THAN
100 REFERENCES

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
The following call might trap or fail to move the table Origt if 
this table has more than 100 References. The call might fail 
with SQL2104N or SQL0443N instead of producing a trap 
 
db2 "call 
sysproc.admin_move_table('test','Origt','TS_DATA','TS_INDX','TS_ 
LOB_DATA',null,null,null,null,'COPY_USE_LOAD,FORCE,NO_STATS','MO 
VE')" 
 
Trap files generated will contain the following stack: 
 
0        ossDumpStackTraceInternal 
1        ossDumpStackTraceV98 
2        OSSTrapFile::dumpEx 
3        sqlo_trce 
4        sqloEDUCodeTrapHandler 
5        __invoke_dynamic_linker__ 
6        StoredProcedure::execDirect 
7        Otm::dropForeignKeys 
8        Otm::swapOffline 
9        Otm::swap 
10       admin_move_table 
11       admin_move_table_nf1 
12       sqloInvokeFnArgs 
13       sqlriInvokerTrusted 
14       sqlriInvokeInvoker 
15       sqlricall 
16       sqlriSectInvoke 
17       sqlrr_process_execute_request 
18       sqlrr_execute 
19       sqljs_ddm_excsqlstt 
20       sqljsParseRdbAccessed 
21       sqljsParse 
22       sqljsSqlam 
23       sqljsDriveRequests 
24       sqljsDrdaAsInnerDriver 
25       sqljsDrdaAsDriver 
26       sqeAgent::RunEDU 
27       sqzEDUObj::EDUDriver 
28       sqlzRunEDU 
29       sqloEDUEntry 
30       __pthread_manager 
31       clone 
 
Check if the number of references on the table is higher than 
100 with the following query: 
 
SELECT a.constname, a.tabschema, a.tabname, a.deleterule, 
a.updaterule, a.refkeyname,  b.enforced, b.trusted, 
b.enablequeryopt  FROM SYSCAT.REFERENCES a, SYSCAT.TABCONST b 
WHERE a.reftabschema = 'Schema' AND a.reftabname = 'Tablename' 
AND a.constname=b.constname AND a.tabschema=b.tabschema AND 
a.tabname=b.tabname 
 
a.reftabschema = 'Schema' AND a.reftabname = 'Tablename' in the 
example above would be a.reftabschema = 'TEST' AND a.reftabname 
= 'ORIGT' 
 
 
If there is no trap but the procedure fails, run it with TRACE 
option and check for entries like the following ( "Maximum 
String array length exceeded" and later on 
"adminotm_StoredProcedure_execDirect | NULL"): 
 
. . . . (11002)DATA: adminotm_Otm_stringArrayAppend            | 
Maximum String array length exceeded 
. . . . (11006)EXIT: adminotm_Otm_stringArrayAppend 
| 0 
 
........ 
 . . (2432)ENTRY: adminotm_StoredProcedure_execDirect 
| ALTER TABLE "TEST     "."ORIGT" DROP FOREIGN KEY "FK_REF101" | 
1112a9d70 
. . . . (2450)EXIT: adminotm_StoredProcedure_execDirect 
| 0 
. . . . (2432)ENTRY: adminotm_StoredProcedure_execDirect 
| NULL | 1112a9d70 
. . . . . (746)ENTRY: adminotm_fillSqlca                 | 3 | 
65549 | 1112a9d70 
. . . . . . (763)DATA: adminotm_fillSqlca                | 1 | 
CLI0124E  Invalid argument value. SQLSTATE=HY009 
. . . . . (810)EXIT: adminotm_fillSqlca          | -443 
. . . . . (2443)DATA: adminotm_HANDLE_SQLCA              | -443 
. . . . (2450)EXIT: adminotm_StoredProcedure_execDirect 
| -443 
. . . . (14608)DATA: adminotm_HANDLE_SQLCA               | -443 
. . . (14612)EXIT: adminotm_Otm_dropForeignKeys          | -443 
. . . (21420)DATA: adminotm_HANDLE_SQLCA                 | -443
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.5 and Fix Pack 3                   * 
****************************************************************
Local Fix:
Make sure that original table has less than 100 references 
before executing admin_move_table
available fix packs:
DB2 Version 10.5 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows

Solution
Problem was first fixed in DB2 Version 10.5 and Fix Pack 3
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
27.08.2013
27.02.2014
27.02.2014
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.5.0.3 FixList
10.5.0.3 FixList