Log file tables configuration for the Production Mapping workspace in Oracle (Production Mapping)
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 Esri Production Mapping, which performs selection sets, uses these log file tables. ArcSDE 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 Production Mapping table.
When working with results in the Production Mapping 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 ArcSDE log file options: shared, session-based, stand-alone, and pools of session-based or stand-alone log files.
The default ArcSDE log file table configuration for Oracle is shared ArcSDE log files.
In most cases, the default ArcSDE 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 sdelogfile DATAFILE 'D:\oracle\ORADATA\PMDB\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\PMDB\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:pmdb
- 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 file through a command line.
sdedbtune -o import -f dbtune_logfile.sde -u sde -p sde -i sde:oracle11g:pmdb
Creating log file tables
The sde log file tables can be created in ArcMap by performing a large selection.
- Grant QUOTA on SDELOGFILE and SDELOGFILEIDX permissions in OEM to the ArcSDE editor/viewer user.
ALTER USER <user_name> QUOTA UNLIMITED ON "SDELOGFILE"; ALTER USER <user_name> 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.