SQL statements allowed on the catalog
Certain SQL statements can be used to change the value of certain options for existing catalog indexes, sequences, and table spaces, or to add indexes to any of the catalog tables.
SQL statement | Index | Allowable clauses and usage notes | ||||
---|---|---|---|---|---|---|
ALTER INDEX | IBM®-defined | Only these clauses are allowed:
You cannot alter the GBPCACHE value for indexes DSNDXX01, DSNDXX02, and DSNDXX03, which are on catalog table SYSIBM.SYSINDEXES. |
||||
ALTER INDEX | User-created | All clauses are allowed, except for the following:
|
||||
ALTER SEQUENCE | The only clause allowed is MAXVALUE. You can only change the MAXVALUE value of the catalog sequence DSNSEQ_IMPLICITDB. The only value specific must be an integer in the range 1–60000, inclusive. |
|||||
ALTER TABLE |
Only these clauses are allowed:
The ADD VERSIONING, DROP VERSIONING, and ADD PERIOD clauses can be specified on only the following tables:
|
|||||
ALTER TABLESPACE | Only these clauses are allowed:
For DSNDB06.SYSSEQ, MAXROW can be specified only with a value of 1. You can specify the LOCKSIZE keyword on the ALTER TABLESPACE statement for any catalog table spaces that are not LOB table spaces. You cannot alter the GBPCACHE or MAXROWS value of some catalog table spaces. Do not specify GBPCACHE for the following table spaces:
|
|||||
CREATE INDEX | User-created | All clauses are allowed, except for:
The USING clause is ignored. Indexes that are created with key-expressions are not allowed on the catalog. The only value allowed for BUFFERPOOL is BP0. You can create up to 500 indexes on the catalog. |
||||
DROP INDEX | User-created | The statement has no clauses. |