Data collection failing after upgrade to OpsCenter 8.3

Problem

After upgrading an OpsCenter server to version 8.3, data collection stops.

However, note that data collection is being performed, but the data is not visible in the OpsCenter web GUI.

After the upgrade, all master servers would show in Monitor > Hosts > Masters. After data collection is re-enabled, they would disappear from Monitor > Hosts > Masters as their entitytype was changing.

Error Message

Cause

This issue was caused by a regression of VMWare Aliasing related changes to the 8.3 code base.

Solution

Veritas is aware of this issue and is working on integrating the solution into an upcoming release. Until then, the following steps may be performed.

1. Make a copy of the OpsCenter database using the dbbackup command (just in case!).

2. Disable OpsCenter data collection for all masters.

3. Run the following SQL script (see below note Running SQL scripts for more information):

update domain_Entity set entityType = 14 where id in (select id from domain_MasterServer); commit;

4. Run the following SQL script (see below note Running SQL scripts for more information):

delete from nb_VirtualMachines where clientId in (select id from domain_MasterServer); commit;

5. Restart OpsCenter Services

6. Enable OpsCenter data collection and verify proper operation.

Note: Running SQL scripts

You may use any of the following methods:

• Sybase Central
• dbisql
• loadsql

Note that loadsql (.bat for Windows, .sh for Linux) requires that the scripts shown should be written to a file with a .sql or .txt extension.

Sybase Central is a free download, but customers may not allow additional software such as this to be installed, whereas loadsql and dbisql are included with the OpsCenter installation. See relevant documentation on the use of these tools.

If you do not feel confident performing these steps, please contact Veritas Support Services and/or open a support case for assistance.