Upgrading to 6.0.1

Alerts / Self Service Alerts

Customers using the Alert Action Audit Table and/or the Self Service Audit Table will need to do the following:

•

Modify table schemas so that the TIME_STAMP column uses the correct timestamp type for their database.

For example, in MySQL the following SQL statement will modify the TIME_STAMP column:

ALTER TABLE AUDIT_TABLE ALTER TIME_STAMP DATETIME

•

Update database to contain the ALERT_NAME (string) and ALERT_INDEX (string) columns.

Alert Persistence

The alert persistence feature has been enhanced for easier configuration. Customers persisting alert data will need to do the following:

•

In your existing persistence table, rename the AlertEngineName column to AgentName, or delete the table and select the Create Database Table If Not Found option on the Alerts>Alert Persistence tab of the Application Options dialog.

•

On the Alerts>Alert Persistence tab of the Application Options dialog, fill in the Alert Engine Name with the same value previously used for Agent Name.

•

If you are only using the Historian to persist alerts, you no longer need to run the Historian.

•

Add the Row Update Time column to the alert persistence database table. The database schemas in RTV\dbconfig\alert_persist have been updated to include this column. See Viewing Alerts and Alert Persistence for more information.

CMDB

Customers using the CMDB from a previous release need to do the following:

•

Create a Relationship Table.

•

For each row in the Container Table and Metric Source Table where a parent value is listed, add a row to the Relationship Table where ID1 is the value in the Parent column and ID2 is the value in the Name column.

•

Remove the Parent column from the Container Table and Metric Source Table.

•

Specify the name of the Relationship Table in the Application Options dialog on the CMDB Tables Tab.