Adding a configuration keyword to the geodatabase in Oracle for the Reviewer workspace

Available with Data Reviewer license.

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.

Note:

Copying and pasting the examples may cause syntax errors.

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

      Tip:

      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_rev.txt.
3. Using a file-based editor, modify the ##DEFAULTS keyword and paste it at the end of the file named dbtune_rev.sde.
4. Rename it ##REVIEWER and change the tablespace name for the appropriate parameters.

   Note:

   If your database only stores the Reviewer repository, the dbtune_rev.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_rev.txt
   ##DEFAULTS
   A_INDEX_RASTER	"PCTFREE 0 INITRANS 4 TABLESPACE REV_AINDEX NOLOGGING"
   A_INDEX_ROWID	"PCTFREE 0 INITRANS 4 TABLESPACE REV_AINDEX STORAGE (INITIAL 409600) NOLOGGING" 
   A_INDEX_SHAPE	"PCTFREE 0 INITRANS 4 TABLESPACE REV_AINDEX STORAGE (INITIAL 409600) NOLOGGING" 
   A_INDEX_STATEID	"PCTFREE 0 INITRANS 4 TABLESPACE REV_AINDEX STORAGE (INITIAL 409600) NOLOGGING" 
   A_INDEX_USER	"PCTFREE 0 INITRANS 4 TABLESPACE REV_AINDEX STORAGE (INITIAL 409600) NOLOGGING" 
   A_INDEX_XML	"PCTFREE 0 INITRANS 4 TABLESPACE REV_AINDEX NOLOGGING"
   A_STORAGE	"PCTFREE 0 INITRANS 4 TABLESPACE REV_ADATA STORAGE (INITIAL 409600)" 
   B_INDEX_RASTER	"PCTFREE 0 INITRANS 4 TABLESPACE REV_BINDEX NOLOGGING"
   B_INDEX_ROWID	"PCTFREE 0 INITRANS 4 TABLESPACE REV_BINDEX STORAGE (INITIAL 409600) NOLOGGING" 
   B_INDEX_SHAPE	"PCTFREE 0 INITRANS 4 TABLESPACE REV_BINDEX NOLOGGING"
   B_INDEX_TO_DATE	"PCTFREE 0 INITRANS 4 TABLESPACE REV_BINDEX NOLOGGING"
   B_INDEX_USER	"PCTFREE 0 INITRANS 4 TABLESPACE REV_BINDEX STORAGE (INITIAL 409600) NOLOGGING" 
   B_INDEX_XML	"PCTFREE 0 INITRANS 4 TABLESPACE REV_BINDEX NOLOGGING"
   B_STORAGE	"PCTFREE 0 INITRANS 4 TABLESPACE REV_BDATA STORAGE (INITIAL 409600)" 
   D_INDEX_DELETED_AT	"PCTFREE 0 INITRANS 4 TABLESPACE REV_DINDEX STORAGE (INITIAL 409600) NOLOGGING" 
   D_INDEX_STATE_ROWID	"PCTFREE 0 INITRANS 4 TABLESPACE REV_DINDEX STORAGE (INITIAL 409600) NOLOGGING" 
   D_STORAGE	"PCTFREE 0 INITRANS 4 TABLESPACE REV_DDATA STORAGE (INITIAL 409600)" 
   F_INDEX_AREA	"PCTFREE 0 INITRANS 4 TABLESPACE REV_FINDEX NOLOGGING"
   F_INDEX_FID	"PCTFREE 0 INITRANS 4 TABLESPACE REV_FINDEX NOLOGGING"
   F_INDEX_LEN	"PCTFREE 0 INITRANS 4 TABLESPACE REV_FINDEX NOLOGGING"
   F_STORAGE	"PCTFREE 0 INITRANS 4 TABLESPACE REV_FDATA"
   GEOMETRY_STORAGE	"ST_GEOMETRY"
   S_INDEX_ALL	"PCTFREE 0 INITRANS 4 TABLESPACE REV_SINDEX STORAGE (INITIAL 409600) NOLOGGING" 
   S_INDEX_SP_FID	"PCTFREE 0 INITRANS 4 TABLESPACE REV_SINDEX NOLOGGING"
   S_STORAGE	"PCTFREE 0 INITRANS 4 TABLESPACE REV_SDATA STORAGE (INITIAL 409600)" 
   ST_GEOM_LOB_STORAGE	 "STORE AS (TABLESPACE REV_FDATA ENABLE STORAGE IN ROW CHUNK 8K RETENTION CACHE INDEX (TABLESPACE REV_FINDEX) )" 
   END
   

5. Import the modified dbtune_rev.txt file using ArcCatalog or ArcMap.
   1. In the ArcToolbox window, expand Data Management Tools > Geodatabase Administration.
   2. Double-click the Import Geodatabase Configuration Keywords tool.

      The Import Geodatabase Configuration Keywords dialog box appears.

   3. Click the browse folder next to the Input Database Connection parameter and browse to the connection file for the enterprise geodatabase from which to import.
   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_rev.txt and click Open.
   6. Click OK on the Import Geodatabase Configuration Keywords dialog box.