ArcMap

Log file table configuration in Oracle

Disponible avec une licence Production Mapping.

Les géodatabases d'enterprise utilisent des tables de fichiers journaux pour maintenir des listes d'enregistrements sélectionnés. Les enregistrements sont écrits dans les tables de fichiers journaux pour être utilisés ultérieurement par l'application à chaque sélection d'une taille spécifique, lors d'une réconciliation ou d'une réinjection dans une base de données versionnée ou encore lors d'une extraction de mise à jour en mode déconnecté dans une application cliente. Les tables de fichiers journaux stockent les identifiants ObjectID des entités sélectionnées pour qu'ils puissent être réaffichés. Ceci permet une analyse et un traitement plus rapides des informations.

Dans ArcGIS, par défaut, les tables de fichiers journaux sont utilisées si l'ensemble de sélection contient 100 enregistrements ou plus. Cette limite de sélection de 100 entités est définie dans le registre. Vous pouvez modifier cette limite, mais cela n'est pas recommandé. Rien ne prouve que cela améliore les performances et cela risquerait d'entraîner des problèmes de performances.

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 Oracle use shared log file tables by default. If the connecting user does not have privileges to create tables or sequences in the database, the log file table will be created as a global temporary table owned by the geodatabase administrator. In most cases, this should be sufficient, but you can change log file table settings using the Configure Geodatabase Log File 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 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 button next to the Input Database Connection parameter and browse to the enterprise geodatabase you want to import.
    4. Click the browse button 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 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. Learn more about altering log files
  5. Remove CREATE TABLE permissions as appropriate.

See the following Technical Support articles to learn more about how to create the ArcSDE log file tables as global temporary tables in Oracle and about log file table options for geodatabases in Oracle.

Rubriques connexes