ArcMap

Log file table configuration for the Workflow Manager (Classic) workspace in Oracle

Available with Workflow Manager license.

In ArcGIS, log file tables are used by default if the selection set contains 100 or more records. ArcMap and applications that run on top of it, such as Workflow Manager (Classic), which performs selection sets, use these log file tables. The geodatabase keeps track of large selections using the log file tables instead of the records held in memory. The same applies when sorting, selecting, or updating records in the Workflow Manager (Classic) table.

When working with results in the Workflow Manager (Classic) workspace, it is best to understand the log file table configuration options so 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\WMXDB\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\WMXDB\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. Open the ArcToolbox window.
    3. Open the Geodatabase Administration toolset in the Data Management Tools toolbox.
    4. Double-click the Export Geodatabase Configuration Keywords tool.
    5. Browse to the enterprise database connection from which the file will be exported for Input Database Connection.
    6. Specify dbtune_logfile.txt for Output File.
    7. Click OK.
  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.
    1. Start ArcCatalog.
    2. Open the ArcToolbox window.
    3. Open the Geodatabase Administration toolset in the Data Management Tools toolbox.
    4. Double-click the Import Geodatabase Configuration Keywords tool.
    5. Browse to the enterprise database connection into which the file will be imported for Input Database Connection.
    6. Browse to the dbtune_logfile.txt file for Input File.
    7. Click OK.

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 tablespaces to the geodatabase editor or viewer user.

    ALTER USER <user_name> QUOTA UNLIMITED ON "GDBLOGFILE";
ALTER USER <user_name> 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.

For more information, see How To: Create the ArcSDE log file tables as global temporary tables in Oracle and Log file table options for geodatabases in Oracle.