Help

Log file tables configuration for the BIS workspace in Oracle

In ArcGIS, by default, log file tables are used if the selection set contains 100 or more records. ArcMap, or any application that runs on top of ArcMap, such as ArcGIS for Maritime: Bathymetry, which performs selection sets, uses these log file tables. The geodatabase keeps track of large selections using the log file tables instead of the records being held in memory. The same applies when sorting, selecting, or updating records in the BIS tables.

When working with results in the Bathymetry Information System (BIS) workspace, it is best to understand the log file table configuration options so that you can choose the right option for your database needs. There are four different geodatabase log file options: shared, session-based, stand-alone, and pools of session-based or stand-alone log files.

The default geodatabase log file table configuration for Oracle is shared geodatabase log files.

In most cases, the default geodatabase log file table configuration for your database management system (DBMS) should be sufficient and is the recommended setting.

It is recommended that you store the log file tables in a separate tablespace. This can be achieved by setting specific parameters in the SERVER_CONFIG and DBTUNE tables.

Creating log file tablespaces

Use the following statement to create log file tablespaces in Oracle SQL Plus or Oracle SQL Developer.

CREATE SMALLFILE TABLESPACE gdblogfile
DATAFILE 'D:\oracle\ORADATA\BISDB\GDB\gdblogfile01.dbf' SIZE 10M AUTOEXTEND ON NEXT 1M MAXSIZE 100M
LOGGING EXTENT MANAGEMENT LOCAL UNIFORM SIZE 512K 
SEGMENT SPACE MANAGEMENT AUTO
DEFAULT COMPRESS FOR OLTP STORAGE ( ENCRYPT ) ENCRYPTION USING 'AES256';

CREATE SMALLFILE TABLESPACE gdblogfileidx
DATAFILE 'D:\oracle\ORADATA\BISDB\GDB\gdblogfileidx01.dbf' SIZE 10M AUTOEXTEND ON NEXT 1M MAXSIZE 100M
LOGGING EXTENT MANAGEMENT LOCAL UNIFORM SIZE 512K 
SEGMENT SPACE MANAGEMENT AUTO
DEFAULT COMPRESS FOR OLTP STORAGE ( ENCRYPT ) ENCRYPTION USING 'AES256';

Changing DBTUNE log file parameters

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 under 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.

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

    2. Click the ArcToolbox button ArcToolbox on the Standard toolbar.
    3. Expand Data Management Tools > Geodatabase Administration.
    4. Double-click Export Geodatabase Configuration Keywords.
    5. Click the browse folder for the Input Database Connection parameter and browse to the connection file for the enterprise geodatabase from which 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_logfile.txt and click Save.
    8. Click OK on the Export Geodatabase Configuration Keywords dialog box.
  2. Modify the dbtune_logfile.txt ##LOGFILE_DEFAULTS configuration keyword in a text editor.
    ##LOGFILE_DEFAULTS
LD_INDEX_DATA_ID	"PCTFREE 0 INITRANS 4 TABLESPACE GDBLOGFILEIDX NOLOGGING "
LF_INDEXES	"PCTFREE 0 INITRANS 4 TABLESPACE GDBLOGFILEIDX NOLOGGING "
LF_STORAGE	"PCTFREE 0 INITRANS 4 TABLESPACE GDBLOGFILE"
SESSION_INDEX	"PCTFREE 0 INITRANS 4 TABLESPACE GDBLOGFILEIDX NOLOGGING "
SESSION_TEMP_TABLE	0
SESSION_STORAGE	"PCTFREE 0 INITRANS 4 TABLESPACE GDBLOGFILE"
LD_STORAGE	"PCTFREE 0 INITRANS 4 TABLESPACE GDBLOGFILE "
LD_INDEX_ROWID	"PCTFREE 0 INITRANS 4 TABLE PACE GDBLOGFILEIDX NOLOGGING "
END
  3. Import the modified dbtune_logfile.txt file using ArcCatalog or ArcMap.
    1. In the ArcToolbox window, expand Data Management Tools > Geodatabase Administration.
    2. Double-click Import Geodatabase Configuration Keywords.
    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_logfile.txt and click Open.
    6. Click OK on the Import Geodatabase Configuration Keywords dialog box.

Creating log file tables

The geodatabase log file tables can be created in ArcMap by performing a large selection.

  1. Grant QUOTA on GDBLOGFILE and GDBLOGFILEIDX permissions in OEM to the geodatabase editor/viewer user.
    ALTER USER <user_name> QUOTA UNLIMITED ON "GDBLOGFILE";
ALTER USER <user_name> QUOTA UNLIMITED ON "GDBLOGFILEIDX";
  2. Grant CREATE TABLE permission for the geodatabase editor/viewer user.
  3. Start ArcMap.
  4. Select more than 100 features.

    This automatically creates the log file tables.

  5. Right-click the feature class in the Table Of Contents window, and click Remove to remove the feature class from the map.
  6. Remove CREATE TABLE permissions as appropriate.

Your BIS workspace is now ready to store data and products and be accessed by other users.

Related Topics

Feedback on this topic?