User's Manual

13-2 ILS Open Plus 3.0 Installation Manual
Transaction Database Maintenance
The transaction database size cannot exceed 1 GB. If 1 GB maximum limit is reached, no
new data will be written to the database, the application server will log errors
continuously, and database behavior becomes unpredictable. In fact, if the transaction
database is allowed to reach a size of 500 MB, system performance suffers. To avoid this
constraint, you can purge the transaction database. However, there are a number of
preliminary and subsequent steps included in the task of purging the transaction database,
including:
1 Synchronize offline transactions, if this feature is enabled. Offline processing allows
you to continue check-in and checkout tasks, even if the Library Management System
(LMS) is offline. You perform this task first so that offline transactions are included in
the transaction database. See “Synchronize Offline Transactions” on page 13-3.
2 Make a copy of the transaction database, so that you have an archive of the
transactions, in case the purge process fails or is interrupted. See “Backup Transaction
Database” on page 13-4.
3 Purge the transaction database. You use the Purge function to mark transaction
database records for deletion. This function does not remove rows from the database,
so physical disk space is still allocated and used. Perform this function only during
non-circulation hours. See “Purge the Transaction Database” on page 13-5.
4 Compact the transaction database. To physically remove the deleted records and
reduce the size of the database, you must compact the database. Perform this function
only during non-circulation hours. See “Compact the Transaction Database” on
page 13-7.
5 Checkpoint Systems recommends that you then reboot the Intelligent Library
Controller. See “Reboot the Application Server” on page 13-8.