Informix Error -394

Reasons / Common Causes

-394 fires when DROP VIEW (or another statement referencing a view by name) names a view that doesn't exist in the current database.

1. A misspelled view name — the most common cause.
2. The view was already dropped (by another session, or an earlier step in the same script).
3. Wrong database connected — the view exists, but in a different database than the one the session is currently attached to.
4. The name actually refers to a table, not a view, or vice versa — a naming or object-type confusion.

Solutions / Resolution

1. Query the system catalog for existing views, per the official guidance:

   SELECT tabname FROM systables WHERE tabtype = 'V';
   

2. Verify the exact view name's spelling against that list.
3. Confirm the correct database is connected if the name looks right but still isn't found.
4. For repeatable scripts, check for the view's existence before attempting DROP VIEW, rather than assuming it's always present.

Examples

Listing existing views before dropping

SELECT tabname FROM systables WHERE tabtype = 'V';

Checking existence before a repeatable drop

SELECT tabname FROM systables WHERE tabname = 'active_customers' AND tabtype = 'V';
-- only DROP VIEW if this returns a row

Diagnostic Checks

1. Query systables filtered to tabtype = 'V' to confirm the view's exact name and existence.
2. Confirm the currently connected database matches the one the view was created in.

Related Errors / Related Topics

• -296 — "Referenced table table-name not available." A related object-not-found error, at the table level rather than the view level.
• -310 — "Table table-name already exists in database." A related object-naming error, on the opposite side (something unexpectedly present rather than unexpectedly missing).

Query systables with tabtype = 'V' first — it's the fastest way to confirm the view's exact name and whether it exists in the current database at all.