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

DATABASE RESTORE HITS ADM6091W ON TABLESPACE MAXSIZE

product:
DB2 FOR LUW / DB2FORLUW / B10 - DB2
Problem description:
Redirected DB restore of an autostorage database failed
on target system. The restore failed because the MAXSIZE and
USED
tablespace space was close, and the restore failed with below
error
while converting tablespace to automatic storage. Had to
increase
the max size on source and retake the backup to resolve.

TS                 ID    DP_CT TYPE    CONTENT    STATE
TRACKMOD_STATE BUFFERPOOL           EXT   PFSZ   PGSZ
MAX_MB

TOTAL_MB    USED_MB     FREE_MB     %FREE  UNRD_PFPG
  ------------------ ----- ----- ------- ---------- ----------
-------------- -------------------- ----- ------ -----------
-----------

----------- ----------- ----------- ------ --------------------

  TS10                 27.    1. DMS(AR) ANY        NORMAL
UNAVAILABLE    DATA_16K               32.   192.       16384
16384

   10240       10239           0     0.

2016/09/30 Continuing with the restore
------------------------------
restore database PROD continue

SQL2025N  An I/O error occurred.  Error code: "2231500833".
Media on
which this error occurred: "TS10".

 The db2diag.log recorded:

2016-09-30-15.57.34.307249-240 E910964E1193          LEVEL:
Warning
PID     : 15941                TID : 46914426889984  PROC :
db2sysc 0
INSTANCE: db2inst1             NODE : 000            DB   : PROD
HOSTNAME: xxxxx.yyy
EDUID   : 2287                 EDUNAME: db2pfchr (PROD) 0
FUNCTION: DB2 UDB, buffer pool services,
sqlbPrepareToGrowLastRange, probe:140
MESSAGE : ADM6091W  An attempt was made to automatically
increase the
    size of auto-resize table space "TS10" (ID "27") but the
table
    space's maximum size ("10737418240" bytes) has been reached.
Note
    that this value may be lower than expected due to
uncommitted ALTER
    TABLESPACE statements. Also, because DB2 attempts to extend
containers
    at the same rate and extending must occur in a multiple of
extents,
    it may not actually be possible to reach the maximum size
exactly.
    In this case, the current size ("10737418240" bytes) will
have a
    smaller value than the maximum size. The MAXSIZE clause of
the ALTER
    TABLESPACE statement can be used to increase the maximum
size
    for this table space.

2016-09-30-15.57.34.309296-240 I912158E1099          LEVEL:
Severe
PID     : 15941                TID : 46914426889984  PROC :
db2sysc 0
INSTANCE: db2inst1             NODE : 000            DB   : PROD
HOSTNAME: xxxxx.yyy
EDUID   : 2287                 EDUNAME: db2pfchr (PROD) 0
FUNCTION: DB2 UDB, buffer pool services, sqlbDMSDirectWrite,
probe:823
MESSAGE : ZRC=0x85020021=-2063466463=SQLB_END_OF_CONTAINER
          "DMS Container space full"
DATA #1 : Direct write control block,
PD_TYPE_SQLB_DIRECT_WRITE_CB, 96
bytes
  obj:            0x00002aae01aff048
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* ALL                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to Db2 11.1 Mod 2 Fix Pack 2 or higher               *
****************************************************************
Local Fix:
Increase the max size on source and retake the backup.
Solution
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : IT17746 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
02.10.2017
24.10.2017
24.10.2017
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)