Informix Error -8270: Row security label for a protected table cannot be null.

Cause and resolution

Row security label for a protected table cannot be null.

To insert data into a row protected table either user should have LBAC security label or the user has to explicitly specify a row security label.

Oninit® Troubleshooting Guidance

Reasons / Common Causes

-8270 fires when inserting into a row-protected table without a row security label — per the official guidance.

The user has no LBAC security label, and none was explicitly specified for the insert, per the official guidance — the direct, only cause.

Solutions / Resolution

Ensure the user has an LBAC security label, or explicitly specify a row security label for the insert, per the official guidance.

Examples

An insert with no row security label

INSERT INTO orders (order_id, seclabel) VALUES (1001, NULL);
-- -8270: row security label cannot be null for a protected table

Corrected

INSERT INTO orders (order_id, seclabel) VALUES (1001, 'confidential');

Diagnostic Checks

Check whether the inserting user has an LBAC security label, and if not, explicitly specify a valid row security label in the insert.

Related Errors / Related Topics

-8244 — "The value provided for row security label column is invalid." A related row-security-label error, about an invalid (but non-null) value rather than a null one.

Inserting into a row-protected table requires a non-null row security label — supply one explicitly, or ensure the user has one.