The database server attempted to initialize shared memory with a physical-log size that exceeds the amount of contiguous space available in the dbspace (specified as PHYSDBS in ONCONFIG). Both quantities of space, wanted and available, are expressed as kilobytes.

You must either reduce the size of the physical log (specified as PHYSFILE in ONCONFIG) or change the location of the physical log to a dbspace that contains adequate contiguous space to accommodate the physical log.

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.

Some error during fast or full recovery has prevented the system from changing to online or quiescent mode.

See previous messages in the log file for information.

Transactions that drop tables or indexes do not perform the drop until a COMMIT statement is processed (with a few exceptions). In these cases, a beginning commit log record is written, followed by the usual commit log record. If the database server fails in between the two, the fast recovery process attempts to complete the commit the next time that you initialize the database server.

If this completion of the commit fails, the database server generates the preceding message.

To determine if you need to take action, examine the logical log as described in Interpreting Logical-Log Records.

SINGLE_CPU_VP is set to nonzero, and onmode was used to create a user-defined VP class.

If user-defined VP classes are necessary, stop the database server, change SINGLE_CPU_VP to zero, and restart the database server.

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.

The database server is unable to access the specified dbspace. This message indicates a problem opening the tblspace or corruption in the initial chunk of the dbspace.

Verify that the device or devices that make up the chunks of this dbspace are functioning properly and that you assigned them the correct operating-system permissions (rw-rw----). You might be required to perform a data restore.

The database server is unable to access the logical-log files. Because the database server cannot operate without access to the logical log, you must resolve this problem.

Verify that the chunk device where the logical-log files reside is functioning and has the correct operating-system permissions (rw-rw----).

The database server cannot open the mirrored chunk of a mirrored pair. The chunk pathname and the operating-system error are returned.

For more information about corrective actions, see your operating-system documentation.

The primary chunk of a mirrored pair cannot be opened. The chunk pathname and the operating-system error are returned.

For more information about corrective actions, see your operating-system documentation.

The initial chunk of the dbspace cannot be opened.

Verify that the chunk device is running properly and has the correct operating-system permissions (rw-rw----).

An error occurred when the database server opened the sysams system table.

Note the error number and contact Technical Support.

An error occurred when the database server accessed the sysdistrib system table.

Note the error number and contact Technical Support.

An error occurred when the database server opened the specified system table.

Note the error number and contact Technical Support.

An error occurred when the database server accessed the systrigbody system table.

Note the error number and contact Technical Support.

An error occurred when the database server accessed the systriggers system table.

Note the error number and contact Technical Support.

An error occurred while accessing the sysxtdtypes system table.

Note the error number and contact Technical Support.

A thread that is attempting to restore a mirrored chunk has requested a checkpoint, but the checkpoint cannot be performed.

Shut down the database server.

The database server is unable to recover the physical log and thus unable to perform fast recovery.

If the database server does not come online, perform a data restore from dbspace backup.

Within the fast-recovery or data-restore procedure, the logical-log records are first rolled forward. Then, open transactions that have not committed are rolled back. An open transaction could fail during the rollback, leaving some of the modifications from the open transaction in place. This error does not prevent the database server from moving to quiescent or online mode, but it might indicate an inconsistent database.

To determine if any action is needed, use the onlog utility to examine the logical log.

A failure occurred while the database server was trying to rewrite a reserved page during the reversion process.

See previous messages in the log file for information, or contact Technical Support.

An internal error occurred while inserting data into the syscasts system table.

Contact Technical Support..

The database server supports process affinity, but the system call to bind the virtual processor to a physical processor failed.

See your operating-system documentation.

This informational message occurs when you issue the following command:

onspaces -ch sbspace -Df "MIN_EXT_SIZE=value1" -y

None. For more information, see Change Sbspace Default Specifications.

A dbspace has gone down during a checkpoint interval. The database server is configured to wait for an override when this situation occurs.

Either shut down the database server or issue an onmode -O command to override the down dbspace. For more information on the onmode utility, see In This Chapter.

A checkpoint completed successfully.

None required.

The database server detected an error in an attempt to write checkpoint information to disk.

For additional assistance in resolving this situation, contact Technical Support.

The logical log or the chunk that contains the logical log is corrupted. The database server cannot initialize.

Perform a data restore from dbspace backup.

The variables in this message have the following values:

chunkname

is the name of the chunk that the database server administrator is adding.

spacename

is the name of the storage space to which the database server administrator is adding the chunk.

None required.

The database server administrator dropped chunk chunkname from space spacename.

None required.

The indicated chunk in a mirrored pair has been marked with status D and taken offline. The other chunk in the mirrored pair is operating successfully.

Take steps now to repair the chunk device and restore the chunk. The chunk number and chunk device pathname are displayed.

The indicated chunk in a mirrored pair has been recovered and is online (marked with status O). The chunk number and chunk device pathname are displayed.

None required.

The chunk pathnamedoes not have the correct owner and group permissions.

Make sure that you assigned the correct permissions
(-rw-rw---) to the device on which the chunk is located.

The chunk chunkname does not have the correct owner and group ID.

Make sure the device on which the chunk is located has the ownership. On UNIX, both owner and group should be informix. On Windows, the owner must be a member of the Informix-Admin group.

The chunk pathname does not fit in the space that you specified.

Choose a smaller size for the chunk, or free space where the chunk is to be created.

The database server administrator is running onspaces -cl sbspacename.

None required.

The database server finished re-creating the deferred indexes.

None required.

The database server administrator increased the number of chunks to the specified value by changing CONFIGSIZE or setting MAX_CHUNKS to a higher value.

None required. The change was successful.

The database server administrator increased the number of dbslices to the specified value by changing CONFIGSIZE or setting MAX_DBSLICES to a higher value.

None required. The change was successful.

The database server administrator increased the number of dbspaces to the specified value by changing CONFIGSIZE or setting MAX_DBSPACES to a higher value.

None required. The change was successful.

The logical log has filled beyond the long-transaction high-watermark (LTXHWM), but the offending long transaction is in the process of committing. In this case, the transaction is permitted to continue writing to the logical log and is not rolled back. The address of the transaction structure in shared memory is displayed as hexadecimal value tx 0xn.

None required.

An operating-system call failed while it was trying to disable priority aging for the CPU virtual processor. The system error number associated with the failure is returned.

See your operating-system documentation.

The fork of a virtual processor failed. The database server returns the operating-system error number associated with the failure.

For information on determining the maximum number of processes available per user and for the system as a whole, refer to your operating-system documentation.

The database server cannot allocate new shared memory.

The database server administrator must make more shared memory available. This situation might require increasing SHMTOTAL or reconfiguring the operating system. This message is usually accompanied by other messages that give additional information.