Informix Error -43168: ON-Bar suspended the logical restore on log <value-1> </value-1> (expected to restore to <value-2>).

Cause and resolution

ON-Bar suspended the logical restore on log <value-1> </value-1> (expected to restore to <value-2>).

ON-Bar was able to restore up through log file x.

To restore all data, however, you also need to restore log files x + 1 through y. Query your storage manager to find out if the backups of these log files exist and if they are restorable. If the log files are not restorable or you do not want to restore them, issue the following commands to force the logical restore to end:

onmode -k; oninit

Otherwise, issue onbar -r -l to resume the logical restore.

</value-2>

Oninit® Troubleshooting Guidance

Reasons / Common Causes

-43168 fires when ON-Bar suspends a logical restore partway through — per the official guidance, it restored up through the reported log but still needs the logs between it and the expected target log.

Log files between the reached log and the expected target log not yet backed up (or not accessible/restorable) via the storage manager, per the official guidance — the direct, only cause.

Solutions / Resolution

Query the storage manager to check whether the needed log files exist and are restorable, per the official guidance.
If they aren't restorable, or aren't wanted, force the logical restore to end with onmode -k; oninit, per the official guidance.
Otherwise, resume the logical restore with onbar -r -l, per the official guidance.

Examples

Forcing the logical restore to end

$ onmode -k
$ oninit

Resuming the logical restore

$ onbar -r -l

Diagnostic Checks

Check the storage manager for the log files between the reached and expected target logs, and choose to force-end or resume the restore accordingly.

Related Errors / Related Topics

-43140 — "Due to the previous error, logical restore will not be attempted." A related restore-suspension message, on a physical-restore error blocking logical restore entirely rather than a logical restore stalling partway through.

The logical restore is suspended, missing log files between the reached and expected target logs — check the storage manager, then force-end or resume with onbar -r -l.