1.
If DB2 table is having composite primary key,can one OF THE key column among them be NULLABLE?

2.
The table controlled partition is applied using PARTITION BY keyword while creating tables,
while index controlled partion is implemented using part values.
In index controlled partions,only one partioned index cab exists, but in table controlled partitions any number of partitioned index can exists.
I.E if we does not creates the table with partitions by clause and creates partitioned index with part by values.If again we tried to create partitioned index, will it give error?
If yes then what type of error?
Can we create partitioned index only in partitioned tablesspace? not simple tablespace?

3.
Can anyone pass good documents on alter and rotate partition,what are the various states the last or any partition will be while altering or rotating partitions?

4.
While loading data into table,if load job failed then at what pending state table will be?
and how to resolve that pending state?

Thanks.

1. No. The SQL standard requires that columns in a primary key must not be nullable.

2. There is a difference between "partitioning" indexes and "partitioned" indexes. The former defines the partitioning of a table while the latter just states that the index itself is partitioned (but does not define the partitioning of the rows in the table) - completely different concept despite the similar name.

3. Have a look at the DB2 manual. It documents those commands and how they work.

Hi Stolze,

Thanks for reply.
Can you please answer 4th question also.

Thanks.

4. It depends:

If the problem occurred while you load data into the tablespace, the tablespace will most probably by in "recover pending". If the problem occurred during index build, the index spaces are in "rebuild pending". Additionally, the tablespace may be in check pending if RI constraints are involved and need to be verified in case the LOAD abended before the check could be done.

IBM DB2 9.5 Information Center for Linux, UNIX, and Windows