Main -> Documentation -> OCLC SiteSearch Record Builder -> Record Builder Journal Files |
Contents Introduction
The Record Builder application included with OCLC Database Builder creates a journal file every time a Record Builder user successfully submits a transaction to a local database. Transactions include adding a new record, modifying an existing record, or deleting a record. This document provides information about the location, contents, and naming conventions of journal files, and their role in database recovery.
For databases that
you build and maintain with Record Builder, you specify the location of
the database Within a database's directory for storing journal files, Record Builder assigns a unique file name to each journal file using the following naming conventions:
where:
For example:
contains the transaction applied to the database on January 4, 2000 at 4:35:04 pm. After Record Builder successfully completes a transaction, it creates a journal file containing the transaction. Each journal file contains a record in BER format, including the BER tag that indicates whether the record is to be added to the database, replace an existing record, or be deleted. You can use the SiteSearch ber2txt utility to view the contents of a journal file. Role of Journal Files in Database Recovery Since each journal file contains a transaction applied to the database, you can use journal files and a database backup to recover a corrupted database by restoring the backup and then using the SiteSearch Database Operations Tool (SSDOT) to apply journal files to the database backup. See Recovering a Corrupted Record Builder Database for recovery procedures. See Also Database
Configuration Files - Sections and Variables |
[Main][Documentation][Support][Technical
Reference][Community][Glossary][Search]
|