Database Error Messages

The MERGE INTO syntax did not support a security policy on the destination table, because the policy's statement types did not include INSERT, UPDATE and DELETE or the policy had a security-relevant column.

If you do not have the privilege to modify the security policy, then instead of MERGE INTO, use the INSERT, UPDATE, and DELETE DML statements on the table with a security policy defined. If you have the privilege to modify the security policy, then redefine the policy so that statement types include all of the DML statement types (INSERT, UPDATE and DELETE) or ensure that the policy does not have a security-relevant column.

The MERGE INTO syntax did not support a security policy on the destination table, because the policy's statement_types did not include each of INSERT, UPDATE and DELETE or the policy had security-relevant column.

If you do not have the privilege to modify the security policy, then instead of MERGE INTO, use the INSERT, UPDATE and DELETE DML statements on the table that has a security policy defined on it. If you have the privilege to modify the security policy, then redefine it in such a way that statement_types includes all of the DML statement types (INSERT, UPDATE and DELETE) or ensure that the policy does not have a security-relevant column.

The MERGE INTO syntax did not support a security policy on the destination table, because the policy's statement_types did not include each of INSERT, UPDATE and DELETE or the policy had security-relevant column.

If you do not have the privilege to modify the security policy, then instead of MERGE INTO, use the INSERT, UPDATE and DELETE DML statements on the table that has a security policy defined on it. If you have the privilege to modify the security policy, then redefine it in such a way that statement_types includes all of the DML statement types (INSERT, UPDATE and DELETE) or ensure that the policy does not have a security-relevant column.