Informix Error -957

Reasons / Common Causes

-957 is flagged by the official text as an internal error specific to a database located on an NFS-mounted filesystem, with no documented application-level trigger beyond that context.

1. A genuine internal engine condition interacting with the NFS-mounted filesystem, per the official guidance's framing, with no other documented application-level cause.
2. An NFS-level problem (mount instability, permission issues, stale file handles) affecting the underlying filesystem, the same general category of NFS-related issue as -916's mount table error, though not explicitly named by this error's own sparse official text.

Solutions / Resolution

1. Note the specifics of your system when this internal error occurred, and contact IBM Informix Technical Support, per the official guidance — this is the documented, only resolution path.
2. Check basic NFS mount health as a practical first step, given the error's specific NFS-mount framing, before escalating:

   mount | grep nfs
   df -h
   

Examples

Checking NFS mount status

$ mount | grep nfs
$ df -h

Confirm the NFS mount holding the database is actually mounted and responsive.

Diagnostic Checks

1. Check basic NFS mount health (mounted, responsive, not stale) for the filesystem holding the database.
2. Capture full system specifics for escalation to IBM Informix Technical Support, per the official guidance.

Related Errors / Related Topics

• -916 — "NFS mount table error." A related NFS-specific error, about reading the mount table file itself rather than creating/accessing a database on an NFS mount.

An internal error specific to NFS-mounted databases — check basic mount health first, then escalate to IBM Informix Technical Support with full system specifics.