The user tried to add, drop, or modify a column in a table that has a violations table associated with it.

Do not change the columns in the user table.

The user issued a START VIOLATIONS TABLE statement for a target table. The database server cannot create the violations table for this target table. Any of the following situations might be the reason for this failure:

• The target table already has a violations table.
• You specified an invalid name for the violations table in the START VIOLATIONS TABLE statement. For example, if you omit the USING clause from the statement and if the number of characters in the target table plus four characters is longer than the maximum identifier length, the generated names of the violations table exceed the maximum identifier length.
• You specified a name for the violations table in the START VIOLATIONS TABLE statement that match the names of existing tables in the database.
• The target table contains columns with the names informix_tupleid, informix_optype, or informix_recowner. Because these column names duplicate the informix_tupleid, informix_optype, or informix_recowner columns in the violations table, the database server cannot create the violations table.
• The target table is a temporary table.
• The target table is serving as a violations table for some other table.
• The target table is a system catalog table.

To resolve this error, perform one of the following actions:

• If the violations table name was invalid, specify a unique name for the violations table in the USING clause of the START VIOLATIONS TABLE statement.
• If the target table contains columns with the names informix_tupleid, informix_optype, or informix_recowner, rename them to something else.
• Choose a permanent target table that is not a system catalog table or a violations table for some other table.

The user has issued a statement that attempts to insert rows from the violations table into the target table. For example, the user enters the following invalid statement:

INSERT INTO mytable SELECT * FROM 
mytable_vio;

Also, if the target table has filtering-mode constraints, you receive this error. Extended Parallel Server does not support filtering-mode constraints.

To recover from this error, perform the following actions:

• Do not use filtering constraints.
• Stop the violations table.
• Insert rows from the violations table into a temporary table, and then insert rows from the temporary table into the target table.

The user has tried to alter or drop a table that is serving as a violations table for another table.

Do not alter or drop the violations table.

This error gets returned when you attempt to start a violations table when constraints are in deferred mode.

Note: No error is returned if you start a violations table and then later set the constraints to deferred. However, the violations get undone immediately rather than written into the deferred constraint buffer. For more information, see the IBM Informix: Extended Parallel Server Administrator's Guide and the IBM Informix: Guide to SQL Syntax.

If you would like to start a violations table, you must either change the constraint mode to immediate or commit the transaction.

The number of violations in the diagnostics table exceeds the limit that is specified in the MAX VIOLATIONS clause of the START VIOLATIONS TABLE statement. When a single statement on the target table (such as an INSERT or UPDATE statement) inserts more records into the violations table than the limit that is specified by the MAX VIOLATIONS clause, this error is returned to the user who issued the statement on the target table.

This MAX VIOLATIONS limit applies to each coserver. For example, if you reach the MAX VIOLATIONS limit on coserver 2, you can continue to issue statements that violate rows on other coservers until you reach the MAX VIOLATIONS limit.

To resolve this error, perform one of the following actions:

• Omit the MAX VIOLATIONS clause in the START VIOLATIONS TABLE statement when you start a violations table. Here, you are specifying no limit to the number of rows in the violations table.
• Set MAX VIOLATIONS to a high value.

If you issue a STOP VIOLATIONS TABLE statement for which no violations table is started, you receive this message.

To recover from this error, you must start a violations table for the target table.

This message is recorded in the logmessage table in the sysmaster database when the revtestviolations.sh script has completed successfully (no open violations tables were found).

Action: No action is necessary. For more information on revtestviolations.sh, see the IBM Informix: Migration Guide.

When the database server finds an open violations table, it reports errors 16992 and 16993 in the logmessage table in the sysmaster database and aborts the reversion process.

When this message appears, you must issue the STOP VIOLATIONS TABLE FOR table_name command for each open violations table. After you close all open violations tables, you can restart the reversion process.

This message is recorded in the logmessage table in the sysmaster database when the revtestviolations.sh script is executed.

No action is necessary. For more information on revtestviolations.sh, see the IBM Informix: Migration Guide.

This message is recorded in the logmessage table in the sysmaster database when an open violations table is found.

When this message appears, you must issue the STOP VIOLATIONS TABLE FOR table_name command for each open violations table. After you close all open violations tables, you can restart the reversion process.