Default configuration keywords specific to Oracle
Default configuration keywords specific to Oracle
|
| Release 9.3 |
   |
Note:This topic was updated for 9.3.1.
In addition to the default DBTUNE keywords common to all DBMSs for ArcSDE 9 and higher that were listed in the topic DBTUNE configuration keywords, the keywords that are specific to ArcSDE for Oracle and Oracle Spatial are listed below.
The first four default configuration keywords define geometry and raster storage. If you only want to use a different geometry storage type with a few datasets, you can use separate configuration keywords to specify this when the data is created or brought into the database.
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 the 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.
##SDELOB
GEOMETRY_STORAGE "SDELOB"
ATTRIBUTE_BINARY "BLOB"
RASTER_STORAGE "BLOB"
UI_TEXT "User Interface text description for SDELOB"
COMMENT "Any general comment for SDELOB keyword"
END
SDO_GEOMETRY
##SDO_GEOMETRY
GEOMETRY_STORAGE "SDO_GEOMETRY"
ATTRIBUTE_BINARY "BLOB"
RASTER_STORAGE "SDO_GEORASTER"
SDO_COMMIT_INTERVAL 1000
UI_TEXT "User Interface text description for SDO_GEOMETRY"
COMMENT "Any general comment for SDO_GEOMETRY keyword"
END
SDO_GEORASTER
##SDO_GEORASTER
GEOMETRY_STORAGE "SDELOB"
RASTER_STORAGE "SDO_GEORASTER"
ATTRIBUTE_BINARY "BLOB"
RDT_STORAGE "PCTFREE 0 INITRANS 4"
# TABLESPACE <RDT Table tablespace name>
RDT_INDEX_COMPOSITE "PCTFREE 0 INITRANS 4
# TABLESPACE <RDT Composite index tablespace name>
STORAGE ( INITIAL 409600) NOLOGGING"
UI_TEXT "User Interface text description for SDO_GEORASTER"
COMMENT "Any general comment for SDO_GEORASTER keyword"
END
WKB_GEOMETRY
##WKB_GEOMETRY
GEOMETRY_STORAGE "OGCWKB"
UI_TEXT "User Interface text description for OGC WKB"
END
IMS_GAZETTEER—Beginning with ArcSDE 9.1, the IMS_GAZETTEER keyword can be used to control the storage of the XML documents, storing them in line with the sde_xml_doc<n> side table associated with an XML column. You can specify whether an XML column's LOB data is stored in line or out of line using the parameters XML_DOC_LOB_STORAGE and XML_DOC_VAL_LOB_STORAGE. By default, XML documents are stored out of line with the sde_xml_doc<n> table. This is best to support fast searching of large XML documents, such as with an ArcIMS Metadata Service. Use this keyword when an XML column will only store small XML documents. In particular, this keyword is designed to be used when storing data associated with an ArcIMS Gazetteer Metadata Service. For more information about ArcIMS Metadata Services and the gazetteer, refer to the ArcIMS Metadata Service section of the ArcIMS help.
##IMS_GAZETTEER
XML_DOC_LOB_STORAGE "NOCACHE NOLOGGING CHUNK 4K PCTVERSION 5"
XML_DOC_VAL_LOB_STORAGE "NOCACHE NOLOGGING CHUNK 4K PCTVERSION 5"
END
