Upgrading the Database after Installing a New Version of ENOVIA Live Collaboration

When you upgrade to a new version of ENOVIA Live Collaboration, it may or may not require a database (schema) upgrade. Refer to the Program Directory for the given release for details.

Important: Upgrading to V6R2012x or later from any version earlier than V6R2012x requires a schema upgrade. For details, see the Database Migration Guide in the Program Directory.

Related Topics
Upgrade Analysis
Oracle Configuration
Upgrade Postprocessing

If a database upgrade is required, the following factors should be evaluated to determine the scope of the upgrade project:


  • The type of upgrade.

    You can perform an upgrade analysis to determine what changes will be made to the database when the upgrade is performed. When extensive changes will be made during an upgrade and you are using Oracle, some Oracle configuration may be required before a successful upgrade can be accomplished. The Program Directory may also provide insight as to the extent of an upgrade.

  • The size of the database.

    Very large databases generally require database tuning before an upgrade is performed.

Note: When a database is linked to another database via a loose coupling, you should remove the remote (LCD) vault before running an upgrade or you will receive an error. Once the pgrade is complete, you can restore the remote vaults.

Note: When an upgrade is required, always refer to the specific procedures provided in the Program Directory for the new ENOVIA Live Collaboration release.