Objectivity/DB - upgrading 5.1.x to 5.2

Upgrading to Objectivity/DB V5.2

Before upgrading to Objectivity/DB V5.2, read the section "Upgrading to this release" in the Release Notes.

The release notes describe changes regarding:

• Running ooschemaupgrade
• Changes to ooCleanup
• Use of exceptions in an application defined error handler

V5.1.x and V5.2 Compability

• In general, federations and databases are compatible (see above section).
• However:
  • You cannot mix V5.1.x clients with V5.2 servers and vice versa.
  • You must rebuild applications and restart servers.

Upgrade of federation and databases

• Kill Lockserver and AMS for Objectivity/DB 5.1.x.
• Restart Lockserver and AMS with Objectivity/DB 5.2.

Upgrade of federation, databases and programs

• Kill Lockserver and AMS for Objectivity/DB 5.1.x.
• Restart Lockserver and AMS with Objectivity/DB 5.2.
• Remove compiled files with V5.1.x.
• Compile program files with V5.2.
• Check if everything works correctly.

The following testing procedure was done:

• Lockserver and AMS started on Linux, IBM, HP, Sun with Objectivity/DB V5.1.2.
• A testing program compiled with V5.1.2 on Linux.
• Databases created with a script on Linux, IBM, HP, Sun.
• Objects created in databases.
• Objects were visible with ootoolmgr V5.1.2.
• Lockserver and AMS V5.1.2 processes killed. As Lockserver and AMS are on diffrent ports for V5.1.2 and V5.2 is possible to run both of them. This is however not advised.
• Compiled files with V5.1.2 removed.
• Lockserver and AMS restarted on Linux, IBM, HP, Sun with Objectivity/DB V5.2.
• The testing program recompiled with Objectivity/DB V5.2.
• Objects were visible with ootoolmgr V5.2.
• Objects added to databases.
• Objects were visible with ootoolmgr V5.2.