Blank parsed reports appear after upgrading TIBCO LogLogic LMI
book
Article ID: KB0077368
calendar_today
Updated On:
Products
Versions
TIBCO LogLogic Log Management Intelligence
all versions
Description
After upgrading to any LMI version your parsed reports may include only data captured afterward the upgrade.Nothing before the upgrade is being included. This is normal behavior after upgrading when the post upgrade script hasn't been executed. Each upgrade may make changes to the database schemas for tables containing parsed data. The existing data in the tables prior to the upgrade is quarantined in a separate non-production database. The data must be imported into the production tables containing the new schema changes and may need converted on-the-fly during this process to conform to the new changes. The post upgrade script handles all this. Follow the procedure below to migrate your old data to the production database. Afterward you can execute your parsed reports and they will contain all your data previously collected prior to the upgrade.
Issue/Introduction
This article explains why parsed reports can be empty or only contain data for events that were collected after the most recent upgrade. A resolution is also provided.
Resolution
1. SSH to the appliance and login as ”toor”. 2. Execute the postupgrade script: $ /loglogic/scripts/postupgrade
Note in modern LMI versions the command to execute is rundbm rather than postupgrade. Refer to the LMI ConfigureUpgrade guide for more information.
The following will appear:
Select option 2) from the Configuration Menu. Data Summary Table The following table shows the amount of data that hasn't been converted yet along with the approximate time it will take to convert the data set for the specified number of days. You can adjust the parameters below to only convert certain data sets and also specify the number of days of data you are interested in converting for each. Action - Y (marked for conversion), N (do nothing), D (marked for deletion) Days - total number of days to convert Please wait while preparing configuration... Data Set Action Days Size (MB) Estimated Time ============================================== ASA Y 7 0 0 hr 0 min 0 sec DBAUDIT Y 7 0 0 hr 0 min 0 sec ALERTHISTORY Y 7 0 0 hr 0 min 0 sec AUTH Y 7 0 0 hr 0 min 0 sec ============================================== total Start time : 2009-02-11 09:05:08 End time : 2009-02-11 09:05:08 Total disk space required : 0 MB Current total disk space available: 1174 MB Current disk space used : 232491 (warning messages) Configuration Menu: 1) Modify the above configuration 2) Start the Post Upgrade Process 3) Help 4) Exit the Post Upgrade Process Enter choice: 2
Note: If your retention period is set for any value other than 7 days then you'll need to choose option 1 first to adjust the values.