Truncated log file — When you truncate your log file, all existing information in your log file is deleted, and the log file is re-created. Near the top of your log file is the following message:
|
(19219) The database log file was truncated.
|
Your log file is also re-loaded with all your license information, and the primary broker startup parameters with their current values (which could have been changed while the database is online).
Interim archive file — When you specify that you want to archive your log file, an interim archive is created and filled, in anticipation of being archived. When you enable archiving, the interim log file is named,dbname.lg.date-time.n.tmplg, where the date-time is initially the start time, and over time is the time of the previous archive. The interim log file is renamed when archiving occurs, and a new interim log file is created. The interim log file is deleted when the database is shut down or the log file is truncated with PROLOG.
Truncated and archived log file — When you truncate and archive your log file, the log file is first archived, then all existing information in your log file is deleted, and the log file is re-created. The following messages are written to your truncated log file:
|
The database log file was archived to archive-dir/archive-file.
(19219) The database log file was truncated. |
Archived log file — When your archive log file is created, near the end of the archive, are the following lines (written to the log file when preparing to archive):
|
(19233) Preparing to truncate the database .lg file.
(19232) Database .lg file archive in process. |