Informix Error -504

Reasons / Common Causes

-504 fires when a LOCK TABLE statement names a view rather than a real, storage-backed table — views have no rows of their own to lock, so the operation is rejected outright.

1. LOCK TABLE viewname issued directly against a view, per the official guidance — the direct, only cause.
2. Generated or templated SQL that locks tables by name from a list, where the list wasn't filtered to exclude views before the lock statements were built.
3. Confusion between a view and the base table it's built on, especially when both share a similar or identical name in different naming conventions.

Solutions / Resolution

1. Roll back the current transaction, per the official guidance.
2. Redesign the operation to work against the view's underlying real tables, per the official guidance, locking those directly instead:

   LOCK TABLE base_table_name IN EXCLUSIVE MODE;
   

3. Or open the database in exclusive mode, per the official guidance, if the operation needs broader protection than locking the specific base tables provides.
4. Confirm which underlying tables a view depends on before writing the lock statements, so the correct base-table names are used from the start.

Examples

The disallowed attempt

LOCK TABLE active_orders_view IN SHARE MODE;
-- -504: Cannot lock a view.

Locking the real table instead

LOCK TABLE orders IN SHARE MODE;

Diagnostic Checks

1. Query sysviews/systables to confirm whether a name refers to a view or a base table before issuing a LOCK TABLE statement against it:

   SELECT tabname, tabtype FROM systables WHERE tabname = 'active_orders_view';
   

   tabtype = 'V' indicates a view.

Related Errors / Related Topics

No closely related error codes are cross-referenced for -504 in this set yet.

Views can't be locked directly — lock the base table(s) the view is built on instead.