Transaction log file is very large – LX_LANSA.log

Date: Archived
Product/Release: LANSA for Windows and Adaptive Server Anywhere
Abstract: The LANSA for Windows transaction log file is very LARGE
Submitted By: LANSA Technical Support

(Applicable only when using Adaptive Server Anywhere)

Note: The log file name reflects the database. In this example, the database name is LX_LANSA.db (default name) so the log file is called LX_LANSA.log

DISCLAIMER: This information is intended as a guide only and if you intend to follow these procedures then you are totally responsible and totally liable for any effect it has on the integrity, usability, security, maintainability or portability of any LANSA generated applications on your system(s).

In simple terms, the log file acts like a journal for transactions which have been processed for the database. It is used to recover information put into the database since the last full backup.

The naming convention for these files is "databasename.db" and "databasename.log". The defaulted names are LX_LANSA.db and LX_LANSA.log.

The LX_LANSA.DB and LX_LANSA.LOG files exist together and the LX_LANSA.log file is referenced to the LX_LANSA.db file when it is first created.

Consequently, both of these files should always be backed up, thus allowing the restore of the system database to the latest transactions.

But, in large application systems, the LX_LANSA.log file can become very large, taking up a large amount of hard disk memory.

The LOG file can be deleted and when LANSA is next started a new LOG file will be created. Prior to deleting the log file, a full backup of both the log and database files should be taken.

To delete the LOG file:

  1. Stop using the database
  2. Backup the existing log and database files first
  3. Then delete the LX_LANSA.log file

Note: We strongly recommend that the subject of Backup and Data Recovery in the Adaptive Server Anywhere User Guide be read and thoroughly understood before going ahead with the deletion of the log file.