Previous Topic: MDB Installation Log FilesNext Topic: Uninstallation


MDB Upgrades

This release supports the following MDB upgrades:

If the database server is remote, the MDB is upgraded during a DSM manager upgrade with the current release. For Microsoft SQL Server, no user interaction is required because the database details are retrieved from comstore. For Oracle, set the ORACLE_HOME environment variable and enter the Oracle service name, TNS name, and the mdbadmin and sys passwords.

If existing database sessions are found during the upgrade, each session is displayed with the names of the database user, process ID, and host computer. The database sessions are displayed in two lists in a dialog. The first list is for sessions that must be closed before the upgrade is allowed to proceed. This list includes sessions belonging to database users who are members of roles created by the DSM schema. Representative roles are ams_group, ca_itrm_group, ca_itrm_group_ro (Oracle only), ca_itrm_group_ams, upmuser_group, and mdbadmin (Oracle only). CCS roles (for Microsoft SQL Server only), like emadmin, emuser, uniadmin, uniuser, wvadmin and wvuser, are also included in the first list. (The roles are read from a configuration file on the DVD image.)

The second list displays any remaining sessions belonging to other database users. We recommend that you close these sessions also, but this step is not mandatory. You can proceed with the upgrade even with these outstanding open sessions.

Use the Refresh button in this dialog to refresh the lists as you close open database sessions. The Continue button is enabled only if the first list of database sessions is empty.