Avoid salvaging logical logs

The onbar -r command automatically salvages the logical logs. However, avoid salvaging logical logs in some situations.

Use the onbar -r -p and onbar -r -l commands to skip log salvage.

If you set the LTAPEDEV configuration parameter to /dev/null on UNIX™ or to NUL on Windows™, the logical logs are not salvaged in any ON-Bar restore (onbar -r or onbar -r -w, for example).

Avoid salvaging the logical logs in the following situations:
  • When you perform an imported restore

    Salvage the logical logs on the source database server but not on the target database server.

  • If you reinitialize the database server (oninit -i) before you perform a cold restore

    Reinitialization creates new logical logs that do not contain the data that you want to restore.

  • If you install a new disk for the dbspace that contains the logical logs

    Salvage the logs from the old disk, but not from the new disk.