Database Considerations

This topic provides specific examples of database settings you may want to change before running the LargeDBSchemaUpdate.tcl preprocessing script.

The appropriate settings depend on your database size, configuration, and system resources, so consult with ENOVIA Customer Support and your Database Administrator for the appropriate changes for your system. These changes are temporary and are needed only when running commands with large-scale transaction boundaries. They should be changed back after running the script.

Related Topics
Installation Overview
About the Preprocessing Script
Running the Preprocessing Script

Redo Logs

Disable logging at the tablespace level, and then turn it back on after running the script.

Alternatively, create more and larger logs because they will fill up quickly. Should an existing database have four 10m redo logs, you could drop them one by one, replacing each one with a 200m redo log. Then create two additional logs.

More on Redo Log activity

Increase the log_buffer size, but always keep the log_buffer size to no more than 5% of the sum of the redo logs. For example, for 5 * 200m redo logs, set log_buffer = 50m.

Disable LOG_CHECKPOINT_INTERVAL and LOG_CHECKPOINT_TIMEOUT. For example, set them to a very high number such as 18000000 or 10000000, respectively.

Disable ARCHIVE LOG operations.

Sort_Area_Size and TEMP tablespace

The goal is to avoid sorting to disk.

An installation with sort_area_size set to 2097152 or 2m might change it to 200m, depending on how much RAM is available on the box.

For the TEMP tablespace, the extent sizing calculation is usually:

N * sort_area_size + db_block_size

For a 2048k (2097152 byte) sort_area_size and an 8k db_block_size, the extent sizing would be 2056k. So before running the tcl script, you should change the TEMP extent to 200m + 8k or 204808k.

Buffer, Cache, and Pool Size

Oracle 8i: DB_BLOCK_BUFFERS
Oracle 9i: DB_CACHE_SIZE
Oracle 8i and 9i: SHARED_POOL_SIZE

Set all values high. For a single Oracle instance on a database server, assign up to 50% physical memory. If the database server has more than one instance or other applications, assign the largest amount of physical memory possible without causing the system to go to swap. Settings of 1g and higher for Oracle 32-bit software and yet higher for Oracle 64-bit software have been noted at large installations for such large operations. This is entirely dependent on system RAM and size of the database.