DB2 FOR LUW / DB2FORLUW / B10 - DB2

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

****************************************************************
* USERS AFFECTED:                                              *
* All Users.                                                   *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to latest fix pack.                                  *
****************************************************************

Move databases into separate instances.

not known / see Local fix

forerunner  : 
follow-up : IT30797 

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

22.04.2019
31.10.2019
31.10.2019