Help

Log file tables configuration in Oracle

Available with Production Mapping license.

Enterprise geodatabases use log file tables to maintain lists of selected records. Records are written to log file tables for later use by the application whenever a selection of a specific size is made, a reconciliation or post on a versioned database is performed, or a disconnected editing checkout is done in a client application. The log file tables store the ObjectIDs of the selected features so they can be redisplayed. This allows for faster analysis and processing of information.

In ArcGIS, by default, log file tables are used if the selection set contains 100 or more records. This selection threshold of 100 features is set in the registry. It can be changed; however, Esri does not recommend you do so. There is no proven performance reason for changing it, and doing so could cause performance problems.

Log file tables store feature selections in ArcMap that are greater than 100 for each connected geodatabases editor/viewer user. It is recommended that you store the log file tables in a separate tablespace; this can be achieved with the DBTUNE table.

Geodatabases in DB2 use shared log file tables by default, but you can change log file table settings using the Configure Geodatabase Logfile Tables geoprocessing tool.

Creating log file tablespaces

Use the following statement to create log file tablespaces in Oracle.

CREATE SMALLFILE TABLESPACE gdblogfile
DATAFILE 'D:\oracle\ORADATA\PRODLIBDB\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\PRODLIBDB\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 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.

  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.

      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. 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 expand Data Management Tools > Geodatabase Administration.
    2. Double-click 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 enterprise geodatabase you want 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 files tables can be created in ArcMap by performing a large selection.

  1. Grant QUOTA permissions in OEM to the users on GDBLOGFILE and GDBLOGFILEIDX.
    ALTER USER SDE QUOTA UNLIMITED ON "GDBLOGFILE";
ALTER USER SDE QUOTA UNLIMITED ON "GDBLOGFILEIDX";

ALTER USER PRODLIB QUOTA UNLIMITED ON "GDBLOGFILE";
ALTER USER PRODLIB QUOTA UNLIMITED ON "GDBLOGFILEIDX";

ALTER USER PRODLIBUSER QUOTA UNLIMITED ON "GDBLOGFILE";
ALTER USER PRODLIBUSER QUOTA UNLIMITED ON "GDBLOGFILEIDX";
  2. Grant CREATE TABLE permissions for the geodatabase editor/viewer user.
  3. Start ArcMap.
  4. Select more than 100 features.

    This automatically creates the log file tables.

  5. Remove CREATE TABLE permissions as appropriate.

Related topics