Modifying geodatabase configuration keywords in Oracle

Mit der Production Mapping-Lizenz verfügbar.

After creating the data files, modify the DBTUNE table to include a new configuration keyword. Based on this new keyword, the data and database objects will be stored in the tablespaces location that was previously defined. The DBTUNE table is stored in the geodatabase in Oracle. To modify the DBTUNE table, it's necessary to export the DBTUNE table into a text file and make modifications in the text file. After the updates to the text file are made, import the new DBTUNE table from the text file.

Hinweis:

Copying and pasting the examples may cause syntax errors.

1. Export the dbtune file before making any modifications.
   1. Start ArcCatalog.

      Tipp:

      You can also export using ArcMap.

   2. Click the ArcToolbox button on the Standard toolbar.
   3. Expand Data Management Tools > Geodatabase Administration..
   4. Double-click Export Geodatabase Configuration Keywords.

      The Export Geodatabase Configuration Keywords dialog box appears.

   5. Click the browse folder for the Input Database Connection parameter and browse to the connection file for the enterprise geodatabase you want to export.
   6. Click the browse folder for the Output File parameter and browse to the path where the file will be exported.
   7. Name the file dbtune_exp.txt and click Save.
   8. Click OK on the Export Geodatabase Configuration Keywords dialog box.
2. Copy dbtune_exp.txt to dbtune_<Database Name>.txt.
3. Modify the ##DEFAULTS configuration keywords to control which tablespaces the tables and indexes will be created in.

   Hinweis:

   If your geodatabase only stores the product library workspace, the dbtune_<Database Name>.txt file can be opened in a text editor where you can manually edit the ##DEFAULTS configuration keyword; otherwise, create a new configuration keyword using the following example.

   dbtune_prodlib.txt
   ##DEFAULTS
   A_INDEX_RASTER	"PCTFREE 0 INITRANS 4 TABLESPACE PRODLIB_AINDEX NOLOGGING"
   A_INDEX_ROWID	"PCTFREE 0 INITRANS 4 TABLESPACE PRODLIB_AINDEX STORAGE (INITIAL 409600) NOLOGGING" 
   A_INDEX_SHAPE	"PCTFREE 0 INITRANS 4 TABLESPACE PRODLIB_AINDEX STORAGE (INITIAL 409600) NOLOGGING" 
   A_INDEX_STATEID	"PCTFREE 0 INITRANS 4 TABLESPACE PRODLIB_AINDEX STORAGE (INITIAL 409600) NOLOGGING" 
   A_INDEX_USER	"PCTFREE 0 INITRANS 4 TABLESPACE PRODLIB_AINDEX STORAGE (INITIAL 409600) NOLOGGING" 
   A_INDEX_XML	"PCTFREE 0 INITRANS 4 TABLESPACE PRODLIB_AINDEX NOLOGGING"
   A_STORAGE	"PCTFREE 0 INITRANS 4 TABLESPACE PRODLIB_ADATA STORAGE (INITIAL 409600)" 
   B_INDEX_RASTER	"PCTFREE 0 INITRANS 4 TABLESPACE PRODLIB_BINDEX NOLOGGING"
   B_INDEX_ROWID	"PCTFREE 0 INITRANS 4 TABLESPACE PRODLIB_BINDEX STORAGE (INITIAL 409600) NOLOGGING" 
   B_INDEX_SHAPE	"PCTFREE 0 INITRANS 4 TABLESPACE PRODLIB_BINDEX NOLOGGING"
   B_INDEX_TO_DATE	"PCTFREE 0 INITRANS 4 TABLESPACE PRODLIB_BINDEX NOLOGGING"
   B_INDEX_USER	"PCTFREE 0 INITRANS 4 TABLESPACE PRODLIB_BINDEX STORAGE (INITIAL 409600) NOLOGGING" 
   B_INDEX_XML	"PCTFREE 0 INITRANS 4 TABLESPACE PRODLIB_BINDEX NOLOGGING"
   B_STORAGE	"PCTFREE 0 INITRANS 4 TABLESPACE PRODLIB_BDATA STORAGE (INITIAL 409600)" 
   D_INDEX_DELETED_AT	"PCTFREE 0 INITRANS 4 TABLESPACE PRODLIB_DINDEX STORAGE (INITIAL 409600) NOLOGGING" 
   D_INDEX_STATE_ROWID	"PCTFREE 0 INITRANS 4 TABLESPACE PRODLIB_DINDEX STORAGE (INITIAL 409600) NOLOGGING" 
   D_STORAGE	"PCTFREE 0 INITRANS 4 TABLESPACE PRODLIB_DDATA STORAGE (INITIAL 409600)" 
   F_INDEX_AREA	"PCTFREE 0 INITRANS 4 TABLESPACE PRODLIB_FINDEX NOLOGGING"
   F_INDEX_FID	"PCTFREE 0 INITRANS 4 TABLESPACE PRODLIB_FINDEX NOLOGGING"
   F_INDEX_LEN	"PCTFREE 0 INITRANS 4 TABLESPACE PRODLIB_FINDEX NOLOGGING"
   F_STORAGE	"PCTFREE 0 INITRANS 4 TABLESPACE PRODLIB_FDATA"
   GEOMETRY_STORAGE	"ST_GEOMETRY"
   S_INDEX_ALL	"PCTFREE 0 INITRANS 4 TABLESPACE PRODLIB_SINDEX STORAGE (INITIAL 409600) NOLOGGING" 
   S_INDEX_SP_FID	"PCTFREE 0 INITRANS 4 TABLESPACE PRODLIB_SINDEX NOLOGGING"
   S_STORAGE	"PCTFREE 0 INITRANS 4 TABLESPACE PRODLIB_SDATA STORAGE (INITIAL 409600)" 
   ST_GEOM_LOB_STORAGE	 "STORE AS (TABLESPACE PRODLIB_FDATA ENABLE STORAGE IN ROW CHUNK 8K RETENTION CACHE INDEX (TABLESPACE PRODLIB_FINDEX) )" 
   END
   

4. Import the modified dbtune_<Database Name>.txt file using ArcCatalog or ArcMap.
   1. In the ArcToolbox window, expand Data Management Tools > Geodatabase Administration.
   2. Double-click Import Geodatabase Configuration Keywords. The Import Geodatabase Configuration Keywords dialog box appears.
   3. Click the browse folder next to the Input Database Connection parameter, and browse to the path where the file will be imported.
   4. Click the browse folder for the Input File parameter, and browse to the path where the file will be imported.
   5. Name the file dbtune_<Database Name>.txt, and click Open.
   6. Click OK on the Import Geodatabase Configuration Keywords dialog box.