Oninit
Talk to an expert →

Informix Error -16330: Cannot open file filename for reading.

Cause and resolution

Cannot open file filename for reading.

Make sure that you specified the correct filename in your READ or VIEW command, or after the -F option when you invoked the Debugger from the command line. If the name was correct, the file might be damaged or read protected. If you do not have permission to read it, refer to the discussion of access privileges in your operating-system documentation, or contact your system administrator.

Oninit® Troubleshooting Guidance

Reasons / Common Causes

-16330 fires when the Debugger can't open a named file for reading — per the official guidance.

  1. An incorrect filename in a READ/VIEW command or after -F, per the official guidance — the first named cause.
  2. A damaged or read-protected file, per the official guidance — the second named cause, if the name is correct.
Solutions / Resolution
  1. Confirm the filename is correct, per the official guidance.
  2. If the name is correct, check whether the file is damaged or read-protected, per the official guidance, referring to the operating system's access-privilege documentation or the system administrator if needed.
Examples
Checking file permissions
$ ls -l myfile.4db
Diagnostic Checks
  1. Confirm the filename's spelling and the file's read permissions.
Related Errors / Related Topics
  • -16327 — "Cannot locate file filename." A related file-access error, about the file not being found at all rather than found but unopenable for reading.
  • -16328 — "Cannot read initialization file filename." The same open-for-reading failure, specific to a -F initialization file.

The Debugger couldn't open the named file for reading — check its spelling and read permissions.