Informix Error -8239: The table <table-name> already has a security policy. </table-name>
Cause and resolution
The table <table-name> already has a security policy. </table-name>
A table can have at most one security policy attached to it. Do not try to associate another security policy with the table before you have dropped the association of the table with its current security policy.
Oninit® Troubleshooting Guidance
Reasons / Common Causes
-8239 fires when a security policy is added to a table that already has one — per the official guidance, a table can have at most one security policy.
- A security policy added to a table that already has one associated, per the official guidance — the direct, only cause.
Solutions / Resolution
- Drop the association with the current security policy first, per the official guidance, before associating a different one.
Examples
N/A
No specific triggering statement is documented beyond adding a second security policy to the table.
Diagnostic Checks
- Check the table's current security policy, and drop that association before adding a different policy.
Related Errors / Related Topics
- -8240 — "The table
is not protected with a security policy." The complementary condition — no policy present, rather than one already present.
A table already has a security policy — drop its current association before adding another.