Perform the following steps to compete the upgrade:
After upgrading, clean up the upgraded installation directory by removing the following files without causing harm to the system:
Client, Server, Experience Manager, and Event Manager (Eve) patch directories are renamed and retained upon upgrade.
You can delete any of these renamed directories without affecting anything other than the ability to rollback to a prior version of Operations Center.
Files in the /database/notconverted directory.
This directory exists after you start the Operations Center server the first time. Review these files before deleting them to ensure that everything that should have been converted during upgrade was converted cleanly.
To set purge dates on existing data in the Service Warehouse, type the following command at the command prompt from the /install/bin directory.
mosdbpurge BSWname
If BSWname contains multiple words, wrap the name in quotation marks.
As of version 4.7, purge dates are set for each data point rather than performing a look up during the purge process. The mosdbpurge command sets purge dates for existing data based on warehouse profile settings. If upgrading for several versions, this process only needs to be run once after all upgrades are complete.
If mosdbpurge is run more than once, data will be unaffected and purge dates remain unchanged. Note that version 4.5 Aug 2009 patch bundle set purge dates at 90 days and if this patch was already applied, you do not need to run mosdbpurge again.
Manually edit the hierarchy XML files for existing Data Integrator adapter definitions or other adapters to point to the Novell DTD web site at http://www.Novell.com/dtds/hierarchy_2.0.dtd.
XML files for Data Integrator definitions are located in /OperationsCenter_install_path/bdi/adapter_name/data/adapter_nameHierarchy.xml.
XML files for adapter definitions are located in /OperationsCenter_install_path/database/examples. To verify the XML file used for an adapter, check the adapter’s property settings.
If upgrading to 5.0 September 2011 Patch Release or later, recreate any links to existing EMC SMARTS objects from the Services hierarchy or in BSCM definitions.
The DName structure for EMC SMARTS adapter elements has been modified for the support of multiple domains.
(Optional) You may want to disable the Java version check on console launch. This will turn off the warning message to users that the version has changed. For instructions, see Section 3.3, Disabling Java Version Warnings on Console Launch.