DB2 - Problembeschreibung
Problem IC70019 | Status: Geschlossen |
ADMIN_MOVE_TABLE WITH TRACE OPTION GETS PDTRACESP WAS UNABLE TO SET UP FILE IN THE DIAGPATH IF TABLE HAS "/" IN THE NAME | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 980 - DB2 | |
Problembeschreibung: | |
When using the option TRACE or TRACEDIR with ADMIN_MOVE_TABLE procedure, the trace file will be setup with the schema and name of the table. If there is a "/" in the schema or name of the table, the INIT will fail (although Return status =0) and subsequent calls to start for other operations will also fail with -2104. Example: db2 call SYSPROC.ADMIN_MOVE_TABLE('TESTS','/NAM/TABLE1','ORIGSPACE','','' ,'','','','','COPY_WITH_INDEXES','INIT,TRACE') Return Status = 0 The db2diag.log will show an entry like: 2010-07-13-13.56.00.484000+120 E94513H375 LEVEL: Error PID : 6540 TID : 5632 PROC : db2fmp.exe INSTANCE: DB2_01 NODE : 000 EDUID : 5632 FUNCTION: DB2 UDB, database application extension for utili, adminotm_online_table_move, probe:18090 DATA #1 : String, 51 bytes pdTraceSP was unable to set up file in the DIAGPATH db2 "call SYSPROC.ADMIN_MOVE_TABLE('TESTS','/NAM/TABLE1','','','','','','' ,'','COPY_WITH_INDEXES','COPY')" SQL2104N The ADMIN_MOVE_TABLE procedure could not be completed at this time by this user. Reason code: "8". SQLSTATE=5UA0M | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * ADMIN_MOVE_TABLE WITH TRACE OPTION GETS PDTRACESP WAS UNABLE * * TO SET UP FILE IN THE DIAGPATH IF TABLE HAS "/" IN THE NAME * * When using the option TRACE or TRACEDIR with * * ADMIN_MOVE_TABLE * * procedure, the trace file will be setup with the schema and * * name * * of the table. * * * * If there is a "/" in the schema or name of the table, the * * INIT * * will fail (although Return status =0) and subsequent calls * * to * * start for other operations will also fail with -2104. * * * * * * * * * * * * Example: * * * * db2 call * * * * SYSPROC.ADMIN_MOVE_TABLE('TESTS','/NAM/TABLE1','ORIGSPACE','', * ,'','','','','COPY_WITH_INDEXES','INIT,TRACE') * * * * Return Status = 0 * * * * * * * * The db2diag.log will show an entry like: * * * * * * * * 2010-07-13-13.56.00.484000+120 E94513H375 LEVEL: * * Error * * PID : 6540 TID : 5632 PROC : * * * * db2fmp.exe * * * * INSTANCE: DB2_01 NODE : 000 * * * * EDUID : 5632 * * * * FUNCTION: DB2 UDB, database application extension for utili, * * * * adminotm_online_table_move, probe:18090 * * * * DATA #1 : String, 51 bytes * * * * pdTraceSP was unable to set up file in the DIAGPATH * * * * * * * * * * * * db2 "call * * * * SYSPROC.ADMIN_MOVE_TABLE('TESTS','/NAM/TABLE1','','','','','', * ,'','COPY_WITH_INDEXES','COPY')" * * * * * * * * SQL2104N The ADMIN_MOVE_TABLE procedure could not be * * completed * * at this time by this user. Reason code: "8". * * SQLSTATE=5UA0M * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 9.7 and Fickpack 0 * **************************************************************** | |
Local-Fix: | |
Lösung | |
Problem was first fixed in DB2 Version 9.8 and Fickpack 0 | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 19.07.2010 19.05.2011 19.05.2011 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.7., 9.8. | |
Problem behoben lt. FixList in der Version |