Index architectures are classified as clustered or non-clustered. How to alter an index on DB2. After deciding column and entering all fields and data types for your DB2 create table, go to option 15, it can differ in your product, you might not get option 15 directly, you might have option DB2 and inside that DB2 you might have option DB2 V10. More accurately, the PIECESIZE clause specifies the largest data set size for a non-partitioned index. db2 alter table
Viewed 6k times 3. Clustered and non-clustered indexes. And it then defines the table space to use 32kb data page.
In Object Explorer, expand the database that contains the table on which you want to create a nonclustered index. Expand the Tables folder.
PIECESIZE can be specified in kilobytes, megabytes, or gigabytes. 1 - Check how many indexes your table has and what they are. The table is fairly big. db2 describe indexes for table
Thanks and Best Regards, Hien Nguyen The behavior seems like a bug according to my reading of the help for create index … check, drop and create. Clustered indexes are indexes whose order of the rows in the data pages correspond to the order of the rows in the index. It has about 890,000 rows. On the Table Designer menu, click Indexes/Keys. Right-click the table on which you want to create a nonclustered index and select Design. To create a nonclustered index by using the Table Designer. I found our DB2 server configs all the index into one table space. DB2: Is it good to create the index table space to use 32 KB data page. Using db2 9.1 FP9 on windows … A create index statement is creating an exclusive lock on a table. Subject: [DB2-L] Create index on Declared Temporary Table fails with-551 I searched the ListServ archives, Google and the SQL Reference manual but cannot figure this out for the life of me. "Our System Landscape IS : DEV -> QAS -> Production and DataBase server : db2 9.07 , SAP ECC 6.0, windows server 2008. If you create a table without a PK, then create a unique index, then alter the table to create a PK on the same columns as the unique index, DB2 will tell you that it is using the existing unique index for the primary key (this is a warning message only). This is why only one clustered index can exist in a given table, whereas, many non-clustered indexes can exist in the table. It is therefore recommended to create a new index on table. So, please check your product properly.