|
DBTUNE configuration keywords |
|
| Release 9.3 |    |
NOTE: Applies to geodatabases created with an ArcGIS Server Enterprise license only
The following sections are covered in this topic:NOTE: To make a configuration keyword available on the ArcGIS Desktop dialog boxes, specific user interface parameters need to be present under that configuration keyword. See Making configuration keywords available in ArcGIS for more information.
One configuration keyword—DATA_DICTIONARY—is used when the geodatabase is created because it defines the storage of certain ArcSDE geodatabase system tables. If you want to customize the storage of these system tables and their indexes, you must alter the values for the parameters grouped under the DATA_DICTIONARY keyword in the dbtune.sde filebefore you create your geodatabase. You would never specify this keyword when creating datasets.##RASTER
AUX_INDEX_COMPOSITE "TABLESPACE RASTER_DATA PCTFREE 10 INITRANS 4"
AUX_STORAGE "TABLESPACE RASTER_DATA PCTFREE 10 INITRANS 4"
BLK_INDEX_COMPOSITE "TABLESPACE RASTER_DATA PCTFREE 10 INITRANS 4"
<other parameters>
ENDNOTE: As mentioned in the previous section, configuration keywords are limited to 32 characters. The appended _ARCHIVE counts toward the 32 characters.
For any given keyword, if the corresponding archive keyword is not found, ArcSDE will use the same keyword as was used for the original dataset. In the example above, it will use the DEFAULTS keyword, which means the history tables and indexes will be stored in the same logical storage spaces as the feature class that was enabled for archiving. If the <keyword>_ARCHIVE is present but missing a given parameter, the value of the parameter found in the DEFAULTS keyword will be used. See the topic Geodatabase archiving in the "Data management workflows, transactions, and versioning" section of the help.NOTE: If you create an archive keyword, there is no need to include a UI_TEXT parameter. You would not specify the *_ARCHIVE keyword when the data is created; rather, the system will search for the keyword that matches the archiving table's configuration keyword.
NOTE: Datasets that participate in the same topology should be stored in the same geometry storage type. If they are not, you may experience some topology errors due to slight variations in the way the data is stored for different storage types. These variations are extremely small (a matter of millimeters, for instance) but could cause a violation of one of your topology rules. For example, if you have polygon feature class A stored in SDO_GEOMETRY and polygon feature class B stored in ArcSDE compressed binary (Long Raw), and you place them in a topology and specify the topology rule feature class A Must not overlap with feature class B, slight differences in the way the features are rendered could cause adjacent features from A and B to cross, thus violating this topology rule.
As mentioned in the topic The DEFAULTS keyword, if you specify a keyword that only has a few parameters, the rest of the parameters are read from the DEFAULTS configuration keyword. Therefore, if you specify SDELOB when you create a feature class in a geodatabase in Oracle, the software uses the values for GEOMETRY_STORAGE, ATTRIBUTE_BINARY, and RASTER_STORAGE parameters from the SDELOB keyword, then goes to the DEFAULTS keyword for values for all the other parameters such as B_STORAGE and UNICODE_STRING. If you want to create a topology, terrain, or network that uses a geometry storage type other than what is stored under the DEFAULTS keyword, you need to create custom keywords that contain the desired geometry storage. For example, if you create a roads feature class in an Oracle database using SDO_GEOMETRY, when you create a network that involves that roads feature class, you want the network to also use SDO_GEOMETRY. For that, you need to create a set of NETWORK composite keywords that specify SDO_GEOMETRY storage. See Composite configuration keywords for details on creating these custom keywords. To see the configuration keywords provided for using a data type different from the default to store data in each DBMS, see the following topics: Geometry and raster keywords for OracleGeometry keywords for PostgreSQLGeometry keywords for SQL Server