Use /dev/null when you do not need to recover
When you decide that you do not need to recover transactions
or administrative database activities between backups, you can set
the database server configuration parameter LTAPEDEV to /dev/null.
Important: When you set LTAPEDEV to /dev/null,
it has the following implications:
- You can only restore the data that your database server manages up to the point of your most recent backup and any previously backed-up logical-log files.
- When you perform a recovery, you must always perform a full-system restore. (See Full-system restore.) You cannot perform partial restores or restore when the database server is online.
When you set LTAPEDEV to /dev/null, the database server marks a logical-log file as backed up (status B) as soon as it becomes full. The database server can then reuse that logical-log file without waiting for you to back it up. As a result, the database server does not preserve any logical-log records.
Fast recovery and rolling back transactions are not impaired when you use /dev/null as your log-file backup device. For a description of fast recovery, see your HCL OneDB™ Administrator's Guide. For information about rolling back transactions, see the ROLLBACK WORK statement in the HCL OneDB Guide to SQL: Syntax.