RTView Enterprise 5.3

1.

If you are upgrading from a previous release that sent SNMP notifications, you need to update the MIB in your SNMP receiver. The MIB definition in rtvapm\common\lib\SL-RTVIEW-EM-MIB.txt has changed to include a new field for this.

2.

To support the service diagrams, two new columns were added to the RTVCMDB database: DisplayName and Children. You must update the table structure of the RTVCMDB table by executing the following alter table SQL sentences in your selected database administrative tool:

•

DB2:

ALTER TABLE "RTVCMDB" ADD "DisplayName" VARCHAR(15);

ALTER TABLE "RTVCMDB" ADD "Children" VARCHAR(2000);

•

SQL Server:

ALTER TABLE [RTVCMDB] ADD [DisplayName] VARCHAR(15);

ALTER TABLE [RTVCMDB] ADD [Children] VARCHAR(2000);

•

MySQL:

ALTER TABLE "RTVCMDB" ADD "DisplayName" VARCHAR(15);

ALTER TABLE "RTVCMDB" ADD "Children" VARCHAR(2000);

•

Oracle:

ALTER TABLE "RTVCMDB" ADD ("DisplayName" VARCHAR(15), "Children" VARCHAR(2000));

The DisplayName and Children columns were also added to the RTViewCmdbCITable cache. The cache source (.rtv) files that are included in the distribution to populate the CMDB have been modified to add these columns if they are not included in the incoming CMDB data. If you have created your own cache source .rtv file that calls a Store Table In Cache function, or if you have developed an application to modify the RtvCmdbCITable cache or RTVCMDB database, you need to add these two columns. Contact SL Technical Support for more information.

3.

If you use the Solution Package for Solace, remove alerts that are no longer in the monitors from the Alert Administration display. Remove all entries for the SolMsgRouterMsgEgressUtilHigh, SolMsgRouterMsgIngressUtilHigh, SolMsgRouterByteEgressUtilHigh and SolMsgRouterByteIngressUtilHigh alerts from the ALERTDEFS ALERTLEVELS database table. You can configure thresholds and overrides for the new alerts in the Alert Administration display.

4.

If you use the Solution Package for Solace and you enabled alert persistence, remove SolMsgRouterMsgEgressUtilHigh and SolMsgRouterMsgIngressUtilHigh from the ALERT_PERSIST_TABLE and ALERT_PERSIST_TABLE_CENTRAL or you will see errors about these alerts in the log file at startup.

Also note that if you have stored alert history, the old alert will be in the alert history. It is up to user discretion whether to keep the old alerts in history or not.