Informix Error -1331: A row could not be fetched from a temporary report table.
Cause and resolution
A row could not be fetched from a temporary report table.
Within the report definition, 4GL generated SQL statements to select rows from a temporary table. The table was built successfully but now an error occurred while rows were being retrieved from it. Almost the only possible cause is a hardware failure or an error in the database server. Check for operating-system messages that might give more details.
Oninit® Troubleshooting Guidance
Reasons / Common Causes
-1331 fires when 4GL-generated SQL fails to retrieve a row from a report's temporary table that was successfully built — per the official guidance, the table build succeeded, but the fetch itself failed, most likely due to hardware failure or a database server error.
- Hardware failure, per the official guidance's named primary cause.
- A database server error, per the official guidance's other named primary cause.
Solutions / Resolution
- Check operating-system messages for additional diagnostic details, per the official guidance.
- Escalate as a potential hardware/server-level issue if the OS messages don't point to an obvious application-level cause, given the official guidance's framing.
Examples
N/A
No specific triggering statement is documented — the temp table build succeeded, but a subsequent fetch from it failed.
Diagnostic Checks
- Check operating-system messages around the time of the failure for hardware or server-level errors.
Related Errors / Related Topics
- -1328 — "A temporary table needed for a report could not be created in the selected database." A related report-generation error, about the temp table's creation, which -1331 presupposes succeeded.
- -1330 — "A row could not be inserted into a temporary report table." A related report-generation error, about insertion rather than a later fetch.
A fetch from the (already successfully built) report temp table failed, likely hardware or server-level — check OS messages.