|
Problem IC77513
|
Status: Closed |
CREATE TABLESPACE SHOULD FAIL WITH SQL1524N WHEN NEW PARTITION IS JUST ADDED & ALL OTHER PARTITIONS ARE NOT RECOGNIZED IT YET. |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
CREATE TABLESPACE should fail with SQL1524N when new partition
is just added and all other partitions are not recognized this
new partition:
The issue can be recreated as following (alter/drop
tablesapce, in step 7 & 8, failed with SQL1524N, but create
tablespace, in step 6, is successful):
1. db2sampl
2. $ cat tbspace_crt_dpf.clp
create regular tablespace testts1 managed by database using
(FILE '/data2/shenh/pmr85282/ts1 $N' 300000) EXTENTSIZE 16
PREFETCHSIZE 16;
db2 -tvf tbspace_crt_dpf.clp
3. db2 "CREATE DATABASE PARTITION GROUP sxh_group1 ON
DBPARTITIONNUM (0,1)"
4. $ cat tbspace_crt_dpf.clp1
create regular tablespace testts4 in DATABASE PARTITION GROUP
sxh_group1 managed by database using (FILE
'/data2/shenh/pmr85282/ts4 $N' 300000) EXTENTSIZE 16
PREFETCHSIZE 16;
db2 -tvf tbspace_crt_dpf.clp1
5. db2 "START DBM DBPARTITIONNUM 2 ADD DBPARTITIONNUM HOSTNAME
db2debug port 2"
6. $ cat tbspace_crt_dpf.clp2
create regular tablespace testts7 in DATABASE PARTITION GROUP
sxh_group1 managed by database using (FILE
'/data2/shenh/pmr85282/ts7 $N' 300000) EXTENTSIZE 16
PREFETCHSIZE 16;
db2 -tvf tbspace_crt_dpf.clp2
7. db2 "ALTER TABLESPACE testts4 (or testtst1,testtst7)
AUTORESIZE YES INCREASESIZE 5 Percent MAXSIZE NONE"
DB21034E The command was processed as an SQL statement because
it was not a
valid Command Line Processor command. During SQL processing it
returned:
SQL1524N The request cannot occur until all applications in the
instance are
aware of the new database partition server. SQLSTATE=55077
8. $ db2 drop tablespace testtst4
DB21034E The command was processed as an SQL statement because
it was not a
valid Command Line Processor command. During SQL processing it
returned:
SQL1524N The request cannot occur until all applications in the
instance are
aware of the new database partition server. SQLSTATE=55077 |
| Problem Summary: |
Users Effected:
All users
Problem Description:
CREATE TABLESPACE SHOULD FAIL WITH SQL1524N WHEN NEW PARTITION
IS JUST ADDED & ALL OTHER PARTITIONS ARE NOT RECOGNIZED IT YET.
Problem Summary:
CREATE TABLESPACE should fail with SQL1524N when new partition
is just added and all other partitions are not recognized this
new partition:
The issue can be recreated as following (alter/drop
tablesapce, in step 7 & 8, failed with SQL1524N, but create
tablespace, in step 6, is successful):
1. db2sampl
2. $ cat tbspace_crt_dpf.clp
create regular tablespace testts1 managed by database using
(FILE '/data2/shenh/pmr85282/ts1 $N' 300000) EXTENTSIZE 16
PREFETCHSIZE 16;
db2 -tvf tbspace_crt_dpf.clp
3. db2 "CREATE DATABASE PARTITION GROUP sxh_group1 ON
DBPARTITIONNUM (0,1)"
4. $ cat tbspace_crt_dpf.clp1
create regular tablespace testts4 in DATABASE PARTITION GROUP
sxh_group1 managed by database using (FILE
'/data2/shenh/pmr85282/ts4 $N' 300000) EXTENTSIZE 16
PREFETCHSIZE 16;
db2 -tvf tbspace_crt_dpf.clp1
5. db2 "START DBM DBPARTITIONNUM 2 ADD DBPARTITIONNUM HOSTNAME
db2debug port 2"
6. $ cat tbspace_crt_dpf.clp2
create regular tablespace testts7 in DATABASE PARTITION GROUP
sxh_group1 managed by database using (FILE
'/data2/shenh/pmr85282/ts7 $N' 300000) EXTENTSIZE 16
PREFETCHSIZE 16;
db2 -tvf tbspace_crt_dpf.clp2
7. db2 "ALTER TABLESPACE testts4 (or testtst1,testtst7)
AUTORESIZE YES INCREASESIZE 5 Percent MAXSIZE NONE"
DB21034E The command was processed as an SQL statement because
it was not a
valid Command Line Processor command. During SQL processing it
returned:
SQL1524N The request cannot occur until all applications in the
instance are
aware of the new database partition server. SQLSTATE=55077
8. $ db2 drop tablespace testtst4
DB21034E The command was processed as an SQL statement because
it was not a
valid Command Line Processor command. During SQL processing it
returned:
SQL1524N The request cannot occur until all applications in the
instance are
aware of the new database partition server. SQLSTATE=55077 |
| Local Fix: |
|
| available fix packs: |
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
defect wsdbu00873881
CSD First fixed in DB2 UDB Version 9.7, FixPak 5
module engn_sqnq |
| Workaround |
Upgrade to DB2 Version Version 9.7, FixPak 5 |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 13.07.2011
07.12.2011
07.12.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.5
|
 |
