Submit a ticketCall us

Systems Monitoring for Dummies
Our new eBook will teach you the fundamentals and help you create monitors and alerts that are effective, meaningful, and actionable. Monitoring is more than a checkbox on your to-do list. This free eBook will give you practical advice to help you succeed in all aspects of monitoring – discovery, alerting, remediation, and troubleshooting. Don’t miss out on this indispensable resource for newbies, experienced IT pros, and everyone in between. Register Now.

Home > Success Center > Kiwi CatTools > Reduce Kiwi CatTools database size

Reduce Kiwi CatTools database size

Table of contents
Created by Norsolihati Selamat, last modified by Caroline Juszczak on Oct 09, 2017

Views: 40 Votes: 0 Revisions: 4

Overview

Every time an activity is run, the ActivityLog table in the database is updated with the Run status of the activity.

This can cause the database to grow to a large size over time and can affect loading Manager interface. Refreshing the Manager interface also takes a while.

In extreme circumstances, if the 2GB file size limit has been reached, the file may become corrupted, requiring intervention before CatTools can run.

Environment

All Kiwi CatTools versions

Steps

1. Squeeze:

To keep the database at its optimum size, perform a regular (suggested: once a week) 'squeeze' of the database.

This will compress the database to its smallest size.

To perform the database squeeze:

a. Select the following item from the menu: File > Database > Squeeze current database. 

b. Stop the Timer before this menu item is made available as it requires exclusive access on the database to run the squeeze.

See: http://www.kiwisyslog.com/help/cattools/mnu_filedbsqueezecurrent.htm for more information.

 

2. Compact Using MS Access:

If you have MSAccess installed (and assuming you have a default install on an x86 Windows O/S), you could try running the command line (Use: START button > RUN dialog):
   msaccess "C:\Program Files (x86)\CatTools3\KiwiDB-CatTools.kdb" /compact

 

You may need to change the filename or path in the above to suit your installation. Create a backup of the file before attempting to run a compact. You must rename the file again after the compact.

 

3. If the file is corrupted, or the above steps did not work:

Before using a third party tool to make any changes, make sure to create a backup of the file before attempting to run compact, or the Jetcomp.exe at a command line. You will also have to ensure that the CatTools Manager UI and CatTools Service are not running.

a. Open the database file in Microsoft Access, and delete data manually from the CatTools database ActivityLog table. Once this is complete, run a compact of the database as above.
b. The Jetcomp.exe utility can help. See Microsoft KB on Jet Compact Utility (© 2016 Microsoft, available at www.microsoft.com, obtained on September 1, 2016.) for more information. 

 

 

 

Last modified

Tags

Classifications

Public