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 IT28880 Status: Geschlossen

EXTENT MOVEMENT RETURNS SQL1523N REASON CODE "15" WHEN EXTENT MOVEMENT NOT
RUNNING

Produkt:
DB2 FOR LUW / DB2FORLUW / B10 - DB2
Problembeschreibung:
Starting extent movement on a table space that does not have an
extent movement running can return SQL1523N reason code "15" if
two databases exist on under the same instance with the same
database seed.

The database seed is used to generate a unique task ID for the
extent movement process so databases with the same database seed
will generate the same task ID for the same table space ID on
two different databases. This will prevent one of the extent
movement processes from starting.

There will also be a message in db2diag.log that looks similar
to the following message:

EDUID   : 5712                 EDUNAME: db2agent (XXXXXQA1) 0
FUNCTION: DB2 UDB, buffer pool services,
sqlbSpawnExtentMovementIcoord, probe:7098
MESSAGE : ZRC=0x8002045E=-2147351458=SQLB_EM_NOT_ALLOWED
          "Extent movement is not allowed due to incompatible
tablespace state."
DATA #1 : String, 32 bytes
Failed to spawn extent movement.
DATA #2 : unsigned integer, 2 bytes
11
Problem-Zusammenfassung:
****************************************************************
* USERS AFFECTED:                                              *
* All Users.                                                   *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to latest fix pack.                                  *
****************************************************************
Local-Fix:
Move databases into separate instances.
Lösung
Workaround
keiner bekannt / siehe Local-Fix
Bug-Verfolgung
Vorgänger  : 
Nachfolger : IT30797 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
22.04.2019
31.10.2019
31.10.2019
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version