DB2 DATA DICTIONARY keyword
DB2 DATA DICTIONARY keyword
|
| Release 9.3 |
   |
Note:This topic was updated for 9.3.1.
As mentioned in The DATA_DICTIONARY keyword, you should alter the DATA_DICTIONARY parameters in the dbtune.sde file prior to creating a geodatabase. The following is a sample of the default entries in the dbtune.sde file for the DATA_DICTIONARY keyword in a DB2 for Linux, UNIX, or Windows database.
##DATA_DICTIONARY
B_INDEX_ROWID ""
B_INDEX_USER ""
#B_STORAGE "IN <TABLESPACE> INDEX IN <TABLESPACE> LONG IN <TABLESPACE>"
#STATES_TABLE "IN <TABLESPACE> INDEX IN <TABLESPACE>"
STATES_INDEX ""
#STATE_LINEAGES_TABLE "IN <TABLESPACE> INDEX IN <TABLESPACE>"
#VERSIONS_TABLE "IN <TABLESPACE> INDEX IN <TABLESPACE>"
VERSIONS_INDEX ""
#MVTABLES_MODIFIED_TABLE "IN <TABLESPACE> INDEX IN <TABLESPACE>"
MVTABLES_MODIFIED_INDEX ""
#XML_INDEX_TAGS_TABLE "IN <TABLESPACE> INDEX IN <TABLESPACE>"
END
Uncomment the B_STORAGE, STATES_TABLE, STATE_LINEAGES_TABLE, VERSIONS_TABLE, MVTABLES_MODIFIED_TABLE, and XML_INDEX_TAGS_TABLE lines by removing the pound sign (#). Replace <TABLESPACE> in each of those lines with the name of the tablespaces in which you want the specific table and index to be stored. An altered DATA_DICTIONARY entry might look like the example below:
##DATA_DICTIONARY
B_INDEX_ROWID ""
B_INDEX_USER ""
B_STORAGE "IN SDE INDEX IN SDEIDX LONG IN SDELOBS"
#STATES_TABLE "IN EDITS INDEX IN EDITSIDX"
STATES_INDEX ""
#STATE_LINEAGES_TABLE "IN EDITS INDEX IN EDITSIDX"
#VERSIONS_TABLE "IN EDITS INDEX IN EDITSIDX"
VERSIONS_INDEX ""
#MVTABLES_MODIFIED_TABLE "IN EDITS INDEX IN EDITSIDX"
MVTABLES_MODIFIED_INDEX ""
#XML_INDEX_TAGS_TABLE "IN SDE INDEX IN SDEIDX"
END
The following is a sample of the default entries in the dbtune.sde.zos file for the DATA_DICTIONARY keyword in a DB2 for z/OS database.
##DATA_DICTIONARY
B_INDEX_ROWID ""
B_INDEX_USER ""
#B_STORAGE "IN DATABASE <REPOSITORY DATABASE NAME>"
#STATES_TABLE "IN DATABASE <REPOSITORY DATABASE NAME>"
STATES_INDEX ""
#STATE_LINEAGES_TABLE "IN DATABASE <REPOSITORY DATABASE NAME>"
#VERSIONS_TABLE "IN DATABASE <REPOSITORY DATABASE NAME>"
VERSIONS_INDEX ""
#MVTABLES_MODIFIED_TABLE "IN DATABASE <REPOSITORY DATABASE NAME>"
MVTABLES_MODIFIED_INDEX ""
#XML_INDEX_TAGS_TABLE "IN DATABASE <REPOSITORY DATABASE NAME>"
XML_INDEX_TAGS_INDEX ""
END
Uncomment the B_STORAGE, STATES_TABLE, STATE_LINEAGES_TABLE, VERSIONS_TABLE, MVTABLES_MODIFIED_TABLE, and XML_INDEX_TAGS_TABLE lines by removing the pound sign (#). Replace <REPOSITORY DATABASE NAME> in each of those lines with the name of the database in which you want the ArcSDE geodatabase system tables and indexes to be stored. An altered DATA_DICTIONARY entry might look like the example below:
##DATA_DICTIONARY
B_INDEX_ROWID ""
B_INDEX_USER "IN DATABASE SDEREP"
B_STORAGE "IN DATABASE SDEREP"
STATES_TABLE "IN DATABASE SDEREP"
STATES_INDEX "IN DATABASE SDEREP"
STATE_LINEAGES_TABLE "IN DATABASE SDEREP"
VERSIONS_TABLE "IN DATABASE SDEREP"
VERSIONS_INDEX "IN DATABASE SDEREP"
MVTABLES_MODIFIED_TABLE "IN DATABASE SDEREP"
MVTABLES_MODIFIED_INDEX "IN DATABASE SDEREP"
#XML_INDEX_TAGS_TABLE "IN DATABASE <REPOSITORY DATABASE NAME>"
XML_INDEX_TAGS_INDEX ""
END
NOTE: XML parameters do not affect geodatabases on DB2 for z/OS, since XML is not supported for these geodatabases at this time.
