This error is returned when you attempt to start a violations table and 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 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.
Adding a logical-log file to a blobspace or sbspace is not allowed.
Add the logical-log file to a dbspace. For more information, see Add a Logical-Log File.
The operating system could not open the null device or duplicate the file descriptor associated with the opening of that device. The system error number is returned.
See your operating-system documentation.
During a data restore, there were too many active transactions. At some point during the restore, the number of active transactions exceeded 32 kilobytes.
None.
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:
The logical log is corrupt. This situation can occur when a new transaction is started, but the first logical-log record for the transaction is not a BEGWORK record.
Contact Technical Support.
A heuristic decision occurred to roll back a transaction after it completed the first phase of a two-phase commit.
None required.
A thread attempted to allocate an entry in the transaction table when no entries in the shared-memory table were available. The user ID and process ID of the requesting thread are displayed.
Try again later.
The operating system cannot create output file filename. The errno is the number of the operating-system error returned.
Verify that the directory exists and has write permissions.
The operating system cannot extend to nn reserved pages for purpose in root chunk. (The value purpose can be either Checkpoint/Log, DBSpace, Chunk, or Mirror Chunk.)
Reduce the ONCONFIG parameter for the resource cited; bring the database server up and free some space in the primary root chunk. Then reattempt the same operation.
The optical driver supplied by the optical-drive vendor has indicated that the drive is not accessible.
Check driver installation and cabling between the computer and the drive.
The database server encountered an out-of-memory condition.
No action is necessary.
The database server cannot open the specified tblspace. (The value nn is the hexadecimal representation of the tblspace number.)
See the ISAM error message number nn, which should explain why the tblspace cannot be accessed. The error message appears in IBM Informix Error Messages at the IBM Informix Online Documentation site at: www.ibm.com/software/data/ developer/informix.
This message displays upon disk initialization. The value of PAGESIZE that was specified in the ONCONFIG file is not a valid 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).
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.
You configured the database server with more than the maximum number of virtual processors allowed (1000).
To reduce the number of virtual processors, decrease the values of VPCLASS, NUMCPUVPS, NUMAIOVPS, or NETTYPE in your ONCONFIG file.
This message indicates an internal error.
Contact Technical Support.
This message indicates an internal error.
Contact Technical Support.
The physical processors in the affinity specification for the VP class classname do not exist or are offline. The problem might be with the VPCLASS parameter for cpu class VPs or with the AFF_SPROC and AFF_NPROCS parameters.
Make sure the named processors are online. Correct the affinity specification for the named VP class. Restart the database server.