Oracle DBTUNE configuration parameters |
|
Release 9.3 |
SQL> connect <user>/<password>
SQL> select default_tablespace from user_users;
SQL> connect system/<password>
SQL> select default_tablespace from dba_users where username = <user>;
SQL> connect <user>/<password>
SQL> select * from user_tablespaces where tablespace_name = <tablespace>;
Parameter name | Description | Values | Notes |
---|---|---|---|
A_INDEX_RASTER | Storage definition for the Adds table raster column index | See your Oracle documentation for CREATE INDEX parameters. | |
A_INDEX_ROWID | Storage definition for the Adds table object ID column index | See your Oracle documentation for CREATE INDEX parameters. | |
A_INDEX_SHAPE | Storage definition for the Adds table spatial column index | See your Oracle documentation for CREATE INDEX parameters. | |
A_INDEX_STATEID | Storage definition for the Adds table sde_state_id column index | See your Oracle documentation for CREATE INDEX parameters. | |
A_INDEX_USER | Defines storage for the Adds table index | See your Oracle documentation for CREATE INDEX parameters. | |
A_INDEX_XML | Storage definition for the Adds table XML column index | See your Oracle documentation for CREATE INDEX parameters. | |
A_STORAGE | Defines the storage of the Adds table | See your Oracle documentation for CREATE TABLE parameters. | |
ATTRIBUTE_BINARY | Indicates storage type for binary attribute (nonspatial) fields) | BLOB or LONGRAW | |
AUX_INDEX_COMPOSITE | Raster AUX table composite column index storage definition | See your Oracle documentation for CREATE INDEX parameters. | |
AUX_STORAGE | Raster AUX table storage definition | See your Oracle documentation for CREATE TABLE parameters. | |
B_INDEX_RASTER | Business table raster column index storage definition | See your Oracle documentation for CREATE INDEX parameters. | |
B_INDEX_ROWID | Business table object ID column index and aster rowid index R<N>_SDE_ROWID_UK storage definition | See your Oracle documentation for CREATE INDEX parameters. | |
B_INDEX_SHAPE | Business table spatial column index storage definition | See your Oracle documentation for CREATE INDEX parameters. | |
B_INDEX_TO_DATE | Storage parameter info for creating the index R<registration_id>_sde_todate, which is used when updating the history table during an archive operation | See your Oracle documentation for CREATE INDEX parameters. | |
B_INDEX_USER | Business table user index storage definition | See your Oracle documentation for CREATE INDEX parameters. | |
B_INDEX_XML | Business table XML column index table storage definition | See your Oracle documentation for CREATE INDEX parameters. | |
B_STORAGE | Business table and raster attribute table storage definition | See your Oracle documentation for CREATE TABLE parameters. | |
BLK_INDEX_COMPOSITE | Raster BLK table composite column index storage definition | See your Oracle documentation for CREATE INDEX parameters. | |
BLK_STORAGE | Raster BLK table storage definition | See your Oracle documentation for CREATE TABLE parameters. | |
BND_INDEX_COMPOSITE | Raster BND table composite column index storage definition | See your Oracle documentation for CREATE INDEX parameters. | |
BND_INDEX_ID | Raster BND table RID column index storage definition | See your Oracle documentation for CREATE INDEX parameters. | |
BND_STORAGE | Raster BND table storage definition | See your Oracle documentation for CREATE TABLE parameters. | |
COMMENT | Line used for comments | Can place any comment up to 8000 characters | |
COMPRESS_ROLLBACK_SEGMENT | Version compression rollback segment (only applies to databases that are using manual undo space management) | Name of a rollback segment | |
D_INDEX_DELETED_AT | Deletes table sde_deleted_at column index storage definition | See your Oracle documentation for CREATE INDEX parameters. | |
D_INDEX_ STATE_ROWID | Deletes table sde_states_id and sde_deletes_row_id column index storage definition | See your Oracle documentation for CREATE INDEX parameters. | |
D_STORAGE | Deletes table storage definition | See your Oracle documentation for CREATE TABLE parameters. | |
F_INDEX_AREA | Feature table area column index storage definition | See your Oracle documentation for CREATE INDEX parameters. | Binary geometry storage only |
F_INDEX_FID | Feature table FID column index storage definition | See your Oracle documentation for CREATE INDEX parameters. | Binary geometry storage only |
F_INDEX_LEN | Feature table length column index storage definition | See your Oracle documentation for CREATE INDEX parameters. | Binary geometry storage only |
F_STORAGE | Feature table storage definition | See your Oracle documentation for CREATE TABLE parameters. | Binary geometry storage only |
GEOMETRY_STORAGE | Indicates storage data type for spatial column | ST_GEOMETRY,SDEBINARY, SDELOB, OGCWKB, or SDO_GEOMETRY | |
LD_INDEX_DATA_ID | SDE_LOGFILE_DATA and SDE_LOGPOOL tables' index storage definition | See your Oracle documentation for CREATE INDEX parameters. | |
LD_INDEX_ROWID | SDE_LOGFILE_DATA and SDE_LOGPOOL tables' SDE_ROWID column index storage definition | See your Oracle documentation for CREATE INDEX parameters. | |
LD_STORAGE | SDE_LOGFILE_DATA and SDE_LOGPOOL_<SDE_ID> tables' storage definition | See your Oracle documentation for CREATE TABLE parameters. | |
LF_INDEXES | SDE_LOGFILES table column indexes storage definition | See your Oracle documentation for CREATE INDEX parameters. | |
LF_STORAGE | SDE_LOGFILES table storage definition | See your Oracle documentation for CREATE TABLE parameters. | |
MVTABLES_MODIFIED_INDEX | MVTABLES_MODIFIED index storage definition | See your Oracle documentation for CREATE INDEX parameters. | |
MVTABLES_MODIFIED_TABLE | MVTABLES_MODIFIED table storage definition | See your Oracle documentation for CREATE TABLE parameters. | |
RAS_INDEX_ID | Raster RAS table RID index storage definition | See your Oracle documentation for CREATE INDEX parameters. | |
RAS_STORAGE | Raster RAS table storage definition | See your Oracle documentation for CREATE TABLE parameters. | |
RASTER_STORAGE | Indicates the storage type used for raster data | BLOB, LONGRAW, or SDO_GEORASTER | |
RDT_INDEX_COMPOSITE | Contains the storage information for the composite index that is created on the SDO_GEORASTER blocks table The index is named SDE_RDT_<N>_PK, where N is the rastercolumn_id value of the raster column. | See your Oracle documentation for CREATE INDEX parameters. | Oracle Spatial only |
RDT_STORAGE | Contains the storage information for the SDO_GEORASTER blocks table The blocks table is named sde_rdt_<N>, where N is the rastercolumn_id value for the raster column. | See your Oracle documentation for CREATE TABLE parameters. | Oracle Spatial only |
S_INDEX_ALL | Spatial index table first index storage definition when using binary geometry storage | See your Oracle documentation for CREATE INDEX parameters. | Binary geometry storage only |
S_INDEX_SP_FID | Spatial index table second index storage definition | See your Oracle documentation for CREATE INDEX parameters. | Binary geometry storage only |
S_STORAGE | Represents the spatial index storage definition | See your Oracle documentation for CREATE TABLE parameters. | |
SDO_COMMIT_INTERVAL | Number of rows inserted into the spatial index table between each database COMMIT. This becomes a parameter in the CREATE INDEX statement. | 1000 Refer to your Oracle Spatial Users Guide for information about all these values. | Oracle Spatial only |
SDO_DIMNAME_1 SDO_DIMNAME_2 SDO_DIMNAME_3 SDO_DIMNAME_4 | The name of each dimension for Oracle Spatial geometry types; corresponding values are: 1 = X 2 = Y 3 = Z 4 = M | The dimension name Refer to your Oracle Spatial Users Guide for information about all these values. | Oracle Spatial only |
SDO_INDEX_SHAPE | The Oracle Spatial geometry types spatial index storage parameters | Various spatial index storage parameters, including <tablespace_name> and sdo_indx_dims=# (default is 2), which specifies how many dimensions should be indexed with an R-tree spatial index Refer to your Oracle Spatial Users Guide for information about all these values. | Oracle Spatial only |
SDO_LB_1 SDO_LB_2 SDO_LB_3 SDO_LB_4 | Lower dimension boundary for Oracle Spatial geometry type; units specified in coordinate system of the data Default values based on extent of data to be loaded; for data with geodetic SRID, SDO_LB_1 must be 180, and SDO_LB_2 must be 90 | a value less than the corresponding SDO_UB values Refer to your Oracle Spatial Users Guide for information about all these values. | Oracle Spatial only |
SDO_SRID | Oracle Spatial coordinate reference identifier assigned to the SDO_GEOMETRY column | If a coordinate reference system is provided during the creation of a feature class, the SDO_SRID parameter is ignored and not written to the Oracle USER_SDO_GEOM_METADATA view. | Oracle Spatial only |
SDO_TOLERANCE_1 SDO_TOLERANCE_2 SDO_TOLERANCE_3 SDO_TOLERANCE_4 |
|
A value greater than 0 Refer to your Oracle Spatial Users Guide for information about all these values. | Oracle Spatial only |
SDO_UB_1 SDO_UB_2 SDO_UB_3 SDO_UB_4 |
|
A value greater than the corresponding SDO_LB values Refer to your Oracle Spatial Users Guide for information about all these values. | Oracle Spatial only |
SESSION_INDEX | ArcSDE session-based and stand-alone log file indexes storage definition | See your Oracle documentation for CREATE INDEX parameters. | |
SESSION_STORAGE | ArcSDE session-based and stand-alone log file tables storage definition | See your Oracle documentation for CREATE TABLE parameters. | |
ST_GEOM_LOB_STORAGE | Controls the storage of the SHAPE.POINTS column for an ST_Geometry object | See your Oracle documentation for CREATE TABLE and the LOB storage clause parameters. | ST_Geometry storage only; for more information on storing LOBs, see BLOB data storage in Oracle geodatabases |
ST_INDEX_PARTITION_LOCAL | Specifies if a partitioned table's sde.st_spatial_index is created as a global or local index FALSE indicates the st_spatial_index will be created as a global index; TRUE specifies the spatial index will be created as a local index. | True or False | Only applies to partitioned business tables containing ST_Geometry columns |
STATES_INDEX | STATES table storage definition | See your Oracle documentation for CREATE INDEX parameters. | |
STATES_LINEAGES_TABLE | STATE_LINEAGES table storage definition | See your Oracle documentation for CREATE TABLE parameters. | |
STATES_TABLE | STATES table storage definition | See your Oracle documentation for CREATE TABLE parameters. | |
UI_NETWORK_TEXT | User interface parameter, which indicates associated configuration keyword will appear in the ArcGIS user interface; contains description of network configuration | Description up to 8000 characters | |
UI_TERRAIN_TEXT | User interface parameter, which indicates associated configuration keyword will appear in the ArcGIS user interface; contains description of terrain configuration | Description up to 8000 characters | |
UI_TEXT | User interface parameter, which indicates associated configuration keyword will appear in the ArcGIS user interface; contains description of associated noncomposite configuration keyword | Description up to 8000 characters | |
UI_TOPOLOGY_TEXT | User interface parameter, which indicates associated configuration keyword will appear in the ArcGIS user interface; contains description of topoology configuration | Description up to 8000 characters | |
UNICODE_STRING | Determines whether Unicode text types will be used or not; If set to TRUE, character fields will be stored in UNICODE compliant data types. For example, if the UNICODE_STRING parameter is set to FALSE, a string data type would be VARCHAR2. If UNICODE_STRING is set to TRUE, the data type of the field would be NVARCHAR2. | TRUE or FALSE | |
VERSIONS_INDEX | VERSIONS table index storage definition | See your Oracle documentation for CREATE INDEX parameters. | |
VERSIONS_TABLE | VERSIONS table storage definition | See your Oracle documentation for CREATE TABLE parameters. | |
XML_DOC_INDEX | Storage clause for xmldoc<n>_pk and xml_doc<n>_ix indexes on the sde_xml_doc<n> table | See your Oracle documentation for CREATE INDEX parameters. | |
XML_DOC_LOB_STORAGE | Storage and access information for XML documents in the xml_doc column of the sde_xml_doc<n> table | See your Oracle documentation for LOB storage clause parameters. | For more information on storing LOBs, see BLOB data storage in Oracle geodatabases. |
XML_DOC_MODE | Storage type for XML documents | COMPRESSED or UNCOMPRESSED | |
XML_DOC_STORAGE | Storage clause for sde_xml_doc<n> table | See your Oracle documentation for CREATE TABLE parameters. | |
XML_DOC_TEXT_TYPE | Data type for document text column | BLOB or LONGRAW | Obsolete after ArcSDE release 9.0 |
XML_DOC_UNCOMPRESSED_TYPE | When the XML_DOC_MODE parameter is set to UNCOMPRESSED, the XML_DOC_UNCOMPRESSED_TYPE parameter determines the storage format for XML documents | Since XML_DOC_MODE is set to COMPRESSED by default, the XML_DOC_UNCOMPRESSED_TYPE parameter is not present by default. Possible values: CLOB or NCLOB | |
XML_DOC_VAL_LOB_STORAGE | Storage and access information for the XML document content in the xml_doc_val column of the sde_xml_doc<n> table | See your Oracle documentation for LOB storage clause parameters. | For more information on storing LOBs, see BLOB data storage in Oracle geodatabases. |
XML_IDX_INDEX_DOUBLE | Storage clause for the xmlix<n>_db index on the double_tag column of the sde_xml_idx<n> table | See your Oracle documentation for CREATE INDEX parameters. | |
XML_IDX_INDEX_ID | Storage clause for the xmlix<n>_id index on the ID column of the xml_idx<n> table | See your Oracle documentation for CREATE INDEX parameters. | |
XML_IDX_INDEX_PK | Storage clause for xmlix<n>_pk index on the xml_key_column identity column of the sde_xml_idx<n> table | See your Oracle documentation for CREATE INDEX parameters. | |
XML_IDX_INDEX_STRING | Storage clause for xmlix<n>_st index on the string_tag column of the sde_xml_idx<n> table | See your Oracle documentation for CREATE INDEX parameters. | |
XML_IDX_INDEX_TAG | Storage clause for the xmlix<n>_tg index on the tag_id column of the sde_xml_idx<n> table | See your Oracle documentation for CREATE INDEX parameters. | |
XML_IDX_INDEX_TEXT | XML index creation parameters (see Oracle Text Reference) | See your Oracle documentation for CREATE INDEX parameters. | |
XML_IDX_STORAGE | Storage clause for sde_xml_idx<n> table (the index table of an XML column) | See your Oracle documentation for CREATE TABLE parameters. | |
XML_IDX_TEXT_TAG_STORAGE | Storage and access information for the contents of the text_tag column in the sde_xml_idx<n> table (the index table of an XML column); if no value is specified (default) or if DISABLE STORAGE IN ROW is not specified, this LOB data is stored in line. | <no value>, ENABLE STORAGE IN ROW,or DISABLE STORAGE IN ROW | |
XML_IDX_TEXT_UPDATE_MEMORY | The amount of memory to use when building and updating the text index, such as "2M" to allocate 2 MB | An integer, greater than 0 but less than the amount of available RAM given in MB (indicated with M); consult your Oracle documentation for recommended settings. | |
XML_IDX_TEXT_UPDATE_METHOD | Oracle Text index change tracking method:
|
NONE, BUFFERED, or IMMEDIATE | |
XML_INDEX_TAGS_INDEX | Storage clause for xml_indextags_pk index of the sde_xml_indexes table | See your Oracle documentation for CREATE INDEX parameters. | |
XML_INDEX_TAGS_TABLE | Storage clause for sde_xml_index_tags table and the xml_indextags_ix1 and xml_indextags_ix2 indexes on the tag_name and tag_alias columns, respectively | See your Oracle documentation for CREATE TABLE parameters. |
NOTE: For the XML parameters, <n> refers to the xml_column_id associated with a specific XML column.
NOTE: ArcSDE registers all tables that it creates. Tables not created by ArcSDE can also be registered with the sdetable or sdelayer commands. The TABLE_REGISTRY system table maintains a list of the currently registered tables.
The B_INDEX_SHAPE parameter holds the storage configuration of the spatial column index that ArcSDE creates when a spatial column is added to a business table. This index is created by the ArcSDE C API function SE_layer_create. This function is called by ArcGIS when it creates a feature class and by the add operation of the sdelayer command. The B_INDEX_RASTER parameter holds the storage configuration of the raster column index that ArcSDE creates when a raster column is added to a business table. This index is created by the ArcSDE C API function SE_rastercolumn_create. This function is called by ArcGIS when it creates a feature class and by the add, copy, and import operations of the sderaster command. The B_INDEX_TO_DATE parameter specifies the storage for the index R<registration_id>_sde_todate. This index is created when archiving is enabled on a business table, and is used when updating the history table during an archive operation.ORA-14016: underlying table of a LOCAL partitioned index must be partitioned
NOTE: It is not recommended you use LONGRAW storage because Oracle has deprecated support for this data type beginning with release 11g.
## DEFAULTS
RASTER_STORAGE "SDO_GEORASTER"
<other parameters>
END
NOTE: If you specify SDO_GEORASTER for the RASTER_STORAGE parameter, you cannot set the GEOMETRY_STORAGE to SDO_GEOMETRY or ST_GEOMETRY.
For more information on raster storage in the geodatabase, see Raster datasets and raster catalogs in a geodatabase stored in Oracle in the "Geodatabase data storage and schema" section of the help. There is an additional type of raster table—the raster attribute table. These tables store attribute values based on cell values in the raster. The B_STORAGE parameter defines the storage of these tables. If you need to define a different storage location for these tables than you do for other feature class business tables, be sure to create a raster keyword you can use when creating raster datasets and raster catalogs that specifies different storage information for the raster attribute tables. To learn more about raster attribute tables, see Raster dataset attribute tables in the "Image and raster data management" section of the help. To learn how to create custom configuration keywords, see DBTUNE configuration keywords.NOTE: Oracle has deprecated the LONG RAW storage type. For this reason, it is recommended you not use SDEBINARY storage for new feature classes. To migrate existing feature classes from LONG RAW to BLOB or ST_GEOMETRY, see Migrating Oracle data from one storage type to another in the "Geodatabase data storage and schema" section of the help.
NOTE: The ArcSDE for Oracle Windows installation includes several versions of the dbtune file; each specifies a different geometry storage in the DEFAULTS keyword. If you are performing a new installation of ArcSDE for Oracle (not upgrading the database), you can use one of the alternate versions of the file to populate your DBTUNE table during the postinstallation setup if you want your default geometry storage to be a type other than ST_GEOMETRY.
NOTE: If you do not use XML columns and XML documents in your geodatabase, you don't need to configure these parameters.
An XML column may have two text indexes associated with it: one for the XML document table and one for the XML index table. To successfully create an XML column, the XML_IDX_INDEX_TEXT parameter must have an appropriate value. This value is used in the PARAMETERS clause when creating the XML column's context text indexes. An appropriate value for the XML_IDX_INDEX_TEXT parameter is not the same as the values that are used for other DBTUNE parameters used to create other types of indexes. The value in the PARAMETERS clause controls the storage parameters for the text indexes, the language of linguistic analysis for indexing and searching text in the XML documents, the schedule with which the text indexes are updated, and other settings that are specific to text indexes. XML documents are stored in as large objects (LOBs) in the XML document table in the XML_DOC and XML_DOC_VAL columns and in the XML index table in the TEXT_TAG column. It is important to configure these columns accurately to achieve the best possible search performance. LOBs are stored in line if the LOB data is stored in the same block as the rest of the data in the row. However, in-line storage is only possible if the LOB data is less than 4 KB in size. With out-of-line storage, the data is stored in the LOB segment and only the LOB locator is stored with the rest of the data in the row. You can specify whether LOB data associated with an XML column is stored in line or out of line using the ArcSDE DBTUNE parameters XML_DOC_LOB_STORAGE and XML_DOC_VAL_LOB_STORAGE and XML_IDX_TEXT_TAG_STORAGE. Append the value "DISABLE STORAGE IN ROW" to store the data out of line, or "ENABLE STORAGE IN ROW" to store the data in line. When LOB data is stored out of line for an XML column, by default, ArcSDE places that data in the same tablespace as the XML document table. The LOB data may be moved to a different tablespace than the one containing the XML document table. A typical XML document that contains metadata describing a GIS resource will be greater than 4 KB in size. Tests show XML columns associated with ArcIMS Metadata Services perform best when the LOB data is stored out of line in a separate tablespace from the XML document table. However, a metadata service may contain gazetteer data instead of typical metadata XML documents. Gazetteer data is very small, typically less than 100 bytes in size. Metadata services containing gazetteer data will perform best when the LOB data is stored in line. See Configuring an Oracle database to support XML columns for information on using XML columns in your geodatabase.NOTE: Prior to ArcSDE 9.2, LONGRAW was the default value for the ATTRIBUTE_BINARY parameter. When you upgrade an existing ArcSDE geodatabase to a 9.2 or later release, this value is not changed in the DBTUNE table. To make BLOB the default data type for binary attribute columns, you need to manually alter the DEFAULTS ATTRIBUTE_BINARY parameter to BLOB. After you make this change, new feature classes created with the DEFAULTS keyword will use BLOB for binary columns. To migrate the attribute columns in existing data from LONG RAW to BLOB, see Migrating Oracle data from one storage type to another in the "Geodatabase data storage and schema" section of the help.
If you are using feature class representations, you must create the feature class with a configuration keyword that has the ATTRIBUTE_BINARY parameter set to BLOB. If you have your DEFAULTS ATTRIBUTE_BINARY value set to LONGRAW, you will need to create another configuration keyword users can specify when they create feature classes that will contain representation classes. For example, you could add the following configuration keyword REPRESENTATIONS as follows:##REPRESENTATIONS
ATTRIBUTE_BINARY BLOB
UI_TEXT "Configuration keyword used to create feature classes
containing representation classes"
END
Unable to create the representation. Underlying DBMS error.
#COMMENT "This keyword is used by ArcSDE to create log file
tables for all users logged in as editor"
SDO_DIMNAME_<n>
SDO_LB_<n>
SDO_UB_<n>
SDO_TOLERANCE_<n>
SDO_SRID
NOTE: If a coordinate reference system is provided during the creation of a feature class, the SDO_SRID parameter is ignored and not written to the USER_SDO_GEOM_METADATA view.
Oracle Spatial permits feature geometries of two, three, or four dimensions in the combinations x/y, x/y/z, x/y/z (measure), or x/y/z/m. Through these storage parameters, ArcSDE allows you to specify metadata for each dimension. The <n> in some parameter names should be replaced by one of the digits 1, 2, 3, or 4, corresponding to the dimension number. If you do not supply these storage parameters, the ArcSDE client application that creates the feature class will determine the name, upper and lower bound (extent), and tolerance of each dimension.CREATE INDEX MY_SP_INDEX ON MY_SP_TABLE(SHAPE)
INDEXTYPE IS MDSYS.SPATIAL_INDEX
PARAMETERS ( <configuration string is inserted here> );
B_STORAGE "TABLESPACE ORSPBIZ PCTFREE 10 INITRANS 4 STORAGE(INITIAL 512000)"
SDO_INDEX_SHAPE "tablespace=ORSPIDX initial=512000"
##SDO_GEOMETRY
GEOMETRY_STORAGE "SDO_GEOMETRY"
SDO_INDEX_SHAPE "sdo_indx_dims=2"
UI_TEXT "Oracle Spatial: default settings"
END
NOTE: For geodetic data, the extents are specified in decimal degrees and the tolerances are specified in meters.
##SDO_GEOMETRY_8307
GEOMETRY_STORAGE "SDO_GEOMETRY"
SDO_INDEX_SHAPE "sdo_indx_dims=2"
SDO_SRID 8307
SDO_DIMNAME_1 "Lon"
SDO_LB_1 -180.000000
SDO_UB_1 180.000000
SDO_TOLERANCE_1 0.001
SDO_DIMNAME_2 "Lat"
SDO_LB_2 -90.000000
SDO_UB_2 90.000000
SDO_TOLERANCE_2 0.001
UI_TEXT "Oracle Spatial: WGS84"
END
##SDO_GEOMETRY_ORSPBIZ
GEOMETRY_STORAGE "SDO_GEOMETRY"
B_STORAGE "TABLESPACE ORSPBIZ"
SDO_INDEX_SHAPE "tablespace=ORSPIDX sdo_indx_dims=2"
UI_TEXT "Tablespace ORSPBIZ / ORSPIDX"
END
NOTE: The parameter sdo_commit_interval is so important that ArcSDE automatically includes it in SQL indexing statements for Oracle Spatial tables even if you do not specify it as part of the SDO_INDEX_SHAPE parameter. It is set to 1,000.
##SDO_GEOMETRY_QT_6
GEOMETRY_STORAGE "SDO_GEOMETRY"
SDO_INDEX_SHAPE "tablespace=ORSPIDX sdo_level=6 sdo_commit_interval=1000"
END