|
Problem IC87838
|
Status: Closed |
AFTER REDIRECTED RESTORE TERMINATED WITH ERROR "-1704" WITH TOKENS "17" SUBSEQUENT DROP FAILING TO CLEAN THE CONTAINERS |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
Error is a consequence of incorrect cleaning. When error occurs,
the database drop command finishes dirty with leftover table
space containers. Sequence of events:
1. Redirected restore
2. Redirected restore terminates with Error "-1704" with tokens
"17" - unable to allocate pages in SYSCAT . You can see in
db2diag.log:
2012-03-28-06.06.57.349698-240 E371364A1119 LEVEL: Error
PID : 37617714 TID : 1819 PROC : db2sysc
INSTANCE: db2inst1 NODE : 000 DB :
redirectedDB
APPHDL : 0-10 APPID:
*LOCAL.db2inst1.120328100613
AUTHID : db2inst1
EDUID : 1819 EDUNAME: db2agent (redirectedDB )
FUNCTION: DB2 UDB, buffer pool services, sqlbAllocateExtent,
probe:840
MESSAGE : ADM6044E The DMS table space "SYSCATSPACE" (ID "0")
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.
3 Subsequent database drop failing to clean the currently
assigned containers. You can see in the console error similar to
the following:
SET TABLESPACE CONTAINERS FOR 0 USING (FILE
'/home/db2inst1/originalDB/cat' 140000)
SQL0299N Container is already assigned to the table space.
SQLSTATE=42731
Customer Impact: customer unable to perform a redirected restore
of a downlevel backup image. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 version 10.1 fixpack 2 *
**************************************************************** |
| Local Fix: |
Manual file system cleanup of previous table space containers is
needed. |
| available fix packs: |
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Solution |
Problem was first fixed in DB2 version 10.1 fixpack 2 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 04.11.2012
18.12.2012
18.12.2012 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.2
|
 |
| 10.5.0.2
|
|
