Oninit
Talk to an expert →

Informix Error -43276: XBSA Error: (<error-number>) Backup object does not exist in </error-number> Storage Manager.

Cause and resolution

XBSA Error: (<error-number>) Backup object does not exist in </error-number> Storage Manager.

An error occurred in the storage manager application.

Refer to the storage manager message log (or equivalent) for more information. If the cause of the error is still unclear, contact your storage manager technical support. If you are using the Informix Primary Storage Manager, contact IBM Informix Technical Support.

Oninit® Troubleshooting Guidance

Reasons / Common Causes

-43276 fires when the storage manager application reports that a requested backup object doesn't exist — per the official guidance.

  1. An error in the storage manager application, per the official guidance — the direct, only cause; the specific error-number identifies the condition.
Solutions / Resolution
  1. Check the storage manager's message log (or equivalent) for more detail, per the official guidance.
  2. If the cause is still unclear, contact the storage manager's technical support, per the official guidance — or IBM Informix Technical Support if using the Informix Primary Storage Manager.
Examples
N/A

No specific triggering statement is documented beyond a missing backup object.

Diagnostic Checks
  1. Check the storage manager's message log for the underlying error, and escalate to its vendor's support (or IBM's, for the Primary Storage Manager) if unclear.
Related Errors / Related Topics
  • -43258 — "ON-Bar could not get logical log from the Storage Manager." A related missing-backup error, specific to a logical log rather than a general backup object.
  • -43260 — "ON-Bar was unable to get backup record of from storage manager." A related missing-backup error, specific to a dbspace/blobspace.
  • -43283 — "XBSA Error: () This object has not been backed up." A related backup-existence error, where the object exists but was never backed up.

A requested backup object doesn't exist in the storage manager — check its message log and escalate to its technical support if unclear.