TLTMaint checks the stability of the Canister and its files. When a corruption is detected in any of the Canister data files, an attempt is made to correct the condition by rebuilding the corrupted table. If stability of the Canister cannot be maintained, TLTMaint does not allow the Canister services to start.
TLTMaint command-line options
TLTMaint is normally started by the Experience Analytics Canister Server program but can also be run manually at the command line. The command-line options are:
-CheckOnlyPerforms check on tables without fixing anything.
-NoserverRecovers files without datastore (Canister/Archive) services running.
TLTMaint publishes its processing to the Windows™
application log. It also stores log files in the
When services start, TLTMaint performs several configuration checks. The configuration checks include:
- Locates the installation path of Experience Analytics by checking the Registry.
- Checks for the
- Loads its own CFG file (
- Creates Canister spacer file. TLTMaint calculates spacer file size by reading the Max Ctree Bytes size from the Registry. Every time that it starts, it can modify the spacer file size that is based on these settings.
- Checks Canister size and files to index.
- Checks database version.
- Begins checking tables that are defined in the
TLTMaint.cfg. If you want to skip the check of these tables, you can comment these tables out in
TLTMaint.cfg. On bad Canister shutdowns, data files might be corrupted. An attempt is made to salvage the data file.
- Runs CanTrim. Checks the CanTrim setting to see whether it is the right time and day to start.
Note: CanTrim is enabled through TMS.