Upgrade Warnings

Update will issue warning messages instead of error messages for errors that can be ignored.

Related Topics
Upgrade Analysis
Running the Upgrade
Upgrading the Database after Installing a New Version of ENOVIA Live Collaboration

Upgrade may encounter errors on existing tables due to rollbacks (such as tablespace and other admin related issues). While it is difficult to catch all possible errors and roll back up to the last successful SQL command, upgrade can look for certain expected error messages that need to be ignored (and does so). If the error is one of the following, upgrade issues warnings (and does not error) and updates the mxSchema table:


  • ORACLE
    • ORA-00955 (Name is already used by an existing object)
    • ORA-00275 (Such a referential constraint already exists)
    • ORA-02260 (Table can have only one primary key)
  • DB2
    • SQLSTATE=42710 (Object already exists)
    • SQLSTATE=01550 (Index already exists)
    • SQLSTATE=42889 (Cannot have more than one primary key)

However, if the error is something other than these valid error messages, upgrade will error and the mxSchema will not get updated. The DBA needs to correct it on his/her own and then re-run upgrade.