home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC77357 Status: Geschlossen

ADMIN_MOVE_TABLE WILL GIVE WRONG ERROR SQL2102N RC=12, WHEN IT FAILS TO
ACQUIRE SEMAPHORE

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
Due to many DDL operations in INIT and SWAP phase, 
admin_move_table may fail if executed in parallel. 
 
If ADMIN_MOVE_TABLE fails to acquire semaphore for a table, it 
will give incorrect error: 
 
SQL2102N The ADMIN_MOVE_TABLE procedure could not be completed 
because of an internal failure during the execution of the 
procedure. Reason code: "12". 
   Reason Code 12 An unexpected internal error has occurred. 
 
correct error would be this: 
 
SQL2102N The ADMIN_MOVE_TABLE procedure could not be completed 
because of an internal failure during the execution of the 
procedure. Reason code: "33". 
 
Reason Code 33 
The maximum number of retries was exceeded when trying to 
acquire a semaphore. 
 
User response: 
33 
  Wait until the conflicting move operation that is currently in 
progress releases the semaphore. 
 
 
To determine  which table currently holds the semaphore run the 
below query: 
 
SELECT TABSCHEMA, TABNAME from SYSTOOLS.OTM_SEMAPHORE_TABLE 
where VALUE = 'SEM_LOCK' AND SEM_NAME = 'SEM_0'
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users of ADMIN_MOVE_TABLE                                    * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Due to many DDL operations in INIT and SWAP phase,           * 
*                                                              * 
* admin_move_table may fail if executed in parallel.           * 
*                                                              * 
*                                                              * 
*                                                              * 
* If ADMIN_MOVE_TABLE fails to acquire semaphore for a table,  * 
* it                                                           * 
* will give below incorrect error:                             * 
*                                                              * 
*                                                              * 
*                                                              * 
* SQL2102N The ADMIN_MOVE_TABLE procedure could not be         * 
* completed                                                    * 
* because of an internal failure during the execution of the   * 
*                                                              * 
* procedure. Reason code: "12".                                * 
*                                                              * 
*   Reason Code 12 An unexpected internal error has occurred.  * 
*                                                              * 
*                                                              * 
*                                                              * 
* correct error would be this:                                 * 
*                                                              * 
*                                                              * 
*                                                              * 
* SQL2102N The ADMIN_MOVE_TABLE procedure could not be         * 
* completed                                                    * 
* because of an internal failure during the execution of the   * 
*                                                              * 
* procedure. Reason code: "33".                                * 
*                                                              * 
*                                                              * 
*                                                              * 
* Reason Code 33                                               * 
*                                                              * 
* The maximum number of retries was exceeded when trying to    * 
*                                                              * 
* acquire a semaphore.                                         * 
*                                                              * 
*                                                              * 
*                                                              * 
* User response:                                               * 
*                                                              * 
* 33                                                           * 
*                                                              * 
*   Wait until the conflicting move operation that is          * 
* currently in                                                 * 
* progress releases the semaphore.                             * 
*                                                              * 
*                                                              * 
*                                                              * 
*                                                              * 
*                                                              * 
* To determine  which table currently holds the semaphore run  * 
* the                                                          * 
* below query:                                                 * 
*                                                              * 
*                                                              * 
*                                                              * 
* SELECT TABSCHEMA, TABNAME from SYSTOOLS.OTM_SEMAPHORE_TABLE  * 
*                                                              * 
* where VALUE = 'SEM_LOCK' AND SEM_NAME = 'SEM_0'              * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.7 Fix Pack 5                        * 
****************************************************************
Local-Fix:
Run admin_move_table after the conflicting move operation has 
completed.
verfügbare FixPacks:
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

Lösung
Problem was first fixed in DB2 Version 9.7 Fix Pack 5
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
06.07.2011
07.12.2011
07.12.2011
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP5
Problem behoben lt. FixList in der Version
9.7.0.5 FixList