Description of the post upgrade script in TIBCO LogLogic LMI

Description of the post upgrade script in TIBCO LogLogic LMI

book

Article ID: KB0077507

calendar_today

Updated On:

Products Versions
TIBCO LogLogic Log Management Intelligence all versions

Description

The post upgrade script (the binary is called rundbm) enables you to update "legacy" data on your LogLogic appliance for the purpose of compatibility with the LogLogic software version to which you just upgraded. "Legacy" is defined as all data on the appliance prior to performing an upgrade. "Data" is defined as being only the parsed event data (or statistical data such as the CPU and message stats) originating from the LX parser engine processing the raw data. Raw data and index data does not get processed in any way by the post upgrade script.

 After performing an upgrade the legacy data on your appliance is moved to a temporary location in a non-production database within MySQL therefore the data is inaccessible from LMI so it's effectively quarantined. The data remains in this state until you convert the data set to comply with the new database schemas. Example schema changes are data types for fields changing, columns added or removed from a table's index definition, etc.) You can choose to delete the legacy data from the appliance, convert it, or when the data reaches the retention settings, it is removed automatically.

 If you choose to run the post upgrade script on your data then you will regain access to the legacy data because it is migrated from the non-production database instance to the respective production database (i.e. ll_auth_logs, ll_misc_logs, etc.).

Note 1: The more data there is to migrate the longer the process will take.
Note 2: Only data from the previously installed LMI version can be migrated with the post upgrade script. For example, if you have version 5.7.0 installed then upgrade to 6.1.0 then upgrade a few months later to 6.2.0 but you choose to execute rundbm only after upgrading to 6.2.0 then only the data collected since upgrading to 6.1.0 will be available for migrating. Any data from that had been available for migration after upgrading to 6.1.0 (collected by the 5.7.0 version) would have been removed as part of the installation process of 6.2.0.

Issue/Introduction

This article describes the purpose of the post upgrade script in LogLogic LMI.