Log file tables configuration in Oracle (Production Mapping)
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.
Log file options are set using specific parameters in the SERVER_CONFIG and DBTUNE tables.
Creating log file tablespaces
Use the following statement to create log file tablespaces in Oracle.
CREATE SMALLFILE TABLESPACE sdelogfile DATAFILE 'D:\oracle\ORADATA\PRODLIBDB\SDE\sdelogfile01.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 sdelogfileidx DATAFILE 'D:\oracle\ORADATA\PRODLIBDB\SDE\sdelogfileidx01.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.
If you only use direct connections at your site, you may not have installed ArcSDE. You need to install ArcSDE, if you haven't already, to get the sdedbtune and sdeconfig tools.
- Export the DBTUNE table through a command line.
sdedbtune -o export -f dbtune_logfile.sde -u sde -p sde -i sde:oracle11g:prolibdb
- Modify the dbtune_logfile.sde ##LOGFILE_DEFAULTS configuration keyword in a text editor.
##LOGFILE_DEFAULTS LD_INDEX_DATA_ID "PCTFREE 0 INITRANS 4 TABLESPACE SDELOGFILEIDX NOLOGGING " LF_INDEXES "PCTFREE 0 INITRANS 4 TABLESPACE SDELOGFILEIDX NOLOGGING " LF_STORAGE "PCTFREE 0 INITRANS 4 TABLESPACE SDELOGFILE" SESSION_INDEX "PCTFREE 0 INITRANS 4 TABLESPACE SDELOGFILEIDX NOLOGGING " SESSION_TEMP_TABLE 0 SESSION_STORAGE "PCTFREE 0 INITRANS 4 TABLESPACE SDELOGFILE" LD_STORAGE "PCTFREE 0 INITRANS 4 TABLESPACE SDELOGFILE " LD_INDEX_ROWID "PCTFREE 0 INITRANS 4 TABLE PACE SDELOGFILEIDX NOLOGGING " END
- Import the modified dbtune_logfile.sde through a command line.
sdedbtune -o import -f dbtune_logfile.sde -u sde -p sde -i sde:oracle11g:prodlibdb
Creating log file tables
The sde log files tables can be created in ArcMap by performing a large selection.
- Grant QUOTA permissions in OEM to the users on SDELOGFILE and SDELOGFILEIDX.
ALTER USER SDE QUOTA UNLIMITED ON "SDELOGFILE"; ALTER USER SDE QUOTA UNLIMITED ON "SDELOGFILEIDX"; ALTER USER PRODLIB QUOTA UNLIMITED ON "SDELOGFILE"; ALTER USER PRODLIB QUOTA UNLIMITED ON "SDELOGFILEIDX"; ALTER USER PRODLIBUSER QUOTA UNLIMITED ON "SDELOGFILE"; ALTER USER PRODLIBUSER QUOTA UNLIMITED ON "SDELOGFILEIDX";
- Grant CREATE TABLE permissions for the ArcSDE editor/viewer user.
- Start ArcMap.
- Select more than 100 features.
This automatically creates the log file tables.
- Remove CREATE TABLE permissions as appropriate.