IBM Support

Error SQL2216N SQL error "-668" occurred while reorganizing a database table or its indexes {Reason Code 1 (RC=1) on REORG}

Troubleshooting


Problem

Customer is performing a command to REORG a table like below: REORG TABLE DB2INST1.EMPLOYEE ALLOW READ ACCESS ...and then receive the following error.... SQL2216N SQL error "-668" occurred while reorganizing a database table or its indexes.

Symptom

SQL2216N SQL error "-668" occurred while reorganizing a database table or its indexes.

The db2diag.log would have an entry similar to below:


2016-07-22-10.17.24.256308-300 E26178635A1106     LEVEL: Error
PID     : 7602310              TID  : 15167       PROC : db2sysc 0
INSTANCE: db2inst              NODE : 000         DB   : SAMPLE
APPHDL  : 0-38674              APPID: *LOCAL.db2inst.160728172241
AUTHID  : DB2INST
EDUID   : 15177                EDUNAME: db2agent (SAMPLE) 0
FUNCTION: DB2 UDB, buffer pool services, sqlbAllocateExtent, probe:840
MESSAGE : ADM6044E  The DMS table space "TABLESPACE1" (ID "57") is full.  If this
          is an autoresize or automatic storage DMS tablespace, the maximum
          table space size may have been reached or the existing containers or
          storage paths cannot grow any more. Additional space can be added to
          the table space by either adding new containers or extending existing
          ones using the ALTER TABLESPACE SQL statement. If this is an
          autoresize or automatic storage DMS table space, additional space can
          be added by adding containers to an autoresize table space or by
          adding new storage paths to an automatic storage database.

Cause

DMS Table Space is not set to auto resize or the storage space on disk is low.

Diagnosing The Problem

Below shows a truncated output from the db2pd command that shows the table space information.


Tablespace Configuration:
Address            Id    Type Content PageSz ExtentSz Auto Prefetch BufID BufIDDisk FSC NumCntrs MaxStripe  LastConsecPg Name
...
0x07000000815D67A0 4     DMS  Regular 4096   32       No   64       1     1         On  1        0          31           MYTABLESPACE

Tablespace Autoresize Statistics:
Address            Id    AS  AR  InitSize    IncSize     IIP MaxSize     LastResize                 LRF
...
0x07000000815D67A0 4     No  No  0           0                    No  0                    None                       No  

Containers:
Address            TspId ContainNum Type    TotalPgs   UseablePgs PathID     StripeSet  Container
...
0x07000000815D7CE0 4     0          File    128000     127968     -          0          /data/largedisk/BIGFILE.LRG

Database Partition 0 -- Database TRAP01 -- Active -- Up 0 days 16:58:40 -- Date 2016-07-29-09.47.18.716163

Tablespace Configuration:
Address            Id    Type Content PageSz ExtentSz Auto Prefetch BufID BufIDDisk FSC NumCntrs MaxStripe  LastConsecPg Name
...
0x0770000030859380 3     DMS  Regular 4096   32       No   64       1     1         On  1        0          31           MYTABLESPACE

Resolving The Problem

You could possibly try doing a classic REORG to see if you can reclaim any space.
Another option if there's disk space is increasing the table space sizes.

See the related URLs which provide examples on the use of these commands.

[{"Product":{"code":"SSEPGG","label":"Db2 for Linux, UNIX and Windows"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Component":"Database Objects\/Config - Tablespaces","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"10.1;10.5;11.1;9.7;9.8","Edition":"Advanced Enterprise Server;Advanced Workgroup Server;Enterprise Server;Express;Express-C;Personal;Workgroup Server","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
16 June 2018

UID

swg21989073