Oracle Configuration

ENOVIA Live Collaboration is a client to the database. For Oracle environments, all upgrades involve adding or deleting tables, indexes, and constraints of one Oracle user only. Sometimes the upgrade adds a column to a table or modifies the field contents of a column. Each of these actions is bounded by a transaction across all vaults.

Adding or deleting tables does not require a lot of system resources. However, applying indexes and constraints impact rollback segments, redo logs, and the Temp tablespace. And modifying field content data can impact rollback segments and redo logs very significantly.

Related Topics
Upgrade Warnings
Running the Upgrade
Upgrade Postprocessing

When upgrading all databases, always follow these generic rules:


  • Always have a complete backup before upgrading.

    Always run upgrade with SQL tracing on. Use the following:

    trace type sql filename sqlupgrade.log;
  • For upgrades that involve major data modifications, use the following additional guidelines. When upgrading a small database (less than 25,000 business objects) observing these rules should be sufficient:
    • Assign 3 large, online rollback segments and ensure that rollback tablespaces can auto-extend, also ensuring that sufficient disk space is available. Turn off all other rollback segments except system.
    • Ensure that Temp tablespace and datafiles can auto-extend.
    • Always use a minimum of 4 redo logs with a minimum of 10MB per redo log.
    • Modify init<SID>.ora, setting the Log_buffer to at least 16MB and log_checkpoint_interval to a very large number (suggestion: 4096000) for the upgrade only.
  • It is recommended that you first upgrade a test database in order to benchmark success and elapsed time.

Note: For major upgrades of large databases, also follow additional procedures provided in the Program Directory included with the new ENOVIA Live Collaboration release.

Note: The dynamic relationship feature adds an additional requirement for database definition with Oracle installations: the Oracle user (i.e., database) must have CREATE VIEW privileges. Run the following command to add this privilege:

SQL> grant connect, resource, create view to USER; 
Grant succeeded. 
SQL> commit; 
Commit complete.

where USER is the V6 Oracle user.

For information on dynamic relationships, see the MQL Guide > Working with Metadata > Relationships > Dynamic Relationships.