Informix Error -9459: Large object Error: (%s).

Reasons / Common Causes

-9459 fires when the database server can't access a large object over a JDBC connection — per the official guidance; this is the general large-object-access error, with a parenthetical problem message.

1. An invalidated JDBC connection, per the official guidance — the most common named cause, consistent with -9455 through -9458.
2. Another problem, named in the accompanying (%s) text, per the official guidance.

Solutions / Resolution

1. Check the problem information contained in the error message, per the official guidance.
2. Make sure the connection from which the large object comes is still valid, per the official guidance.

Examples

N/A

No specific triggering statement is documented; the exact problem text varies.

Diagnostic Checks

1. Read the accompanying (%s) problem text, and check whether the originating JDBC connection is still valid.

Related Errors / Related Topics

• -9455 — "Cannot access large object." A related large-object-access error, on a missing default sbspace specifically.
• -9456 — "Cannot get large object length." A related large-object-access error, on length retrieval specifically.
• -9457 — "Cannot convert large object handle to byte[]." A related large-object-access error, on content retrieval specifically.
• -9458 — "Cannot start large object search." A related large-object-access error, on seek specifically.

A large object couldn't be accessed, usually because its JDBC connection is no longer valid — read the accompanying message and check the connection.