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

CREATING A TABLESPACE IN A PARTITIONED ENVIRONMENT WITH $[NUMBER]N
PARTITION EXPRESSION FOR STORAGE PATH WILL RESULT IN SQL0294N

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
When we use $[number]N partition expression for storage path in 
a create tablespace statement, we will get SQL0294N as follows: 
 
$ db2 "CREATE TABLESPACE TS1 MANAGED BY DATABASE 
> USING (FILE '/home/db2inst1/filepath/NODE \$4N' 4096) ON 
DBPARTITIONNUM (0 to 2)" 
DB21034E  The command was processed as an SQL statement because 
it was not a 
valid Command Line Processor command.  During SQL processing it 
returned: 
SQL0294N  The container is already in use.  SQLSTATE=42730 
 
This APAR will resolve the above observed issue.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* See SYSROUTE APARs to see where this APAR is addressed       * 
****************************************************************
Local Fix:
use $N instead of $[number]N. 
 
$ db2 "CREATE TABLESPACE TS1 MANAGED BY DATABASE 
> USING (FILE '/home/db2inst1/filepath/NODE000 \$N' 4096) ON 
DBPARTITIONNUM (0 to 2)" 
DB20000I  The SQL command completed successfully.
Solution
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
20.08.2014
09.05.2017
09.05.2017
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.5.0.5 FixList