Messages: J-K-L-M

Listener-thread err = error_number: error_message

Cause:

A listener thread has encountered an error. This message displays the error number and message text.

Action:

For the cause and corrective action, see IBM Informix: Error Messages in at the IBM Informix Online Documentation site at http://www.ibm.com/software/data/informix
/pubs/library/.

Lock table overflow - user id mm session id nn

Cause:

A thread attempted to acquire a lock when no locks were available. The user ID and session ID are displayed.

Action:

Increase the LOCKS configuration parameter, and initialize shared memory.

Logical-log File not found

Cause:

The checkpoint record in the root dbspace reserved page is corrupted.

Action:

Perform a data restore from dbspace backup.

Logical Log nn Complete

Cause:

The logical-log file identified by log-ID number nn is full. The database server automatically switches to the next logical-log file in the sequence.

Action:

None required.

Logical Recovery allocating nn worker threads thread_type.

Cause:

The database server determined the number of worker threads that will be used for parallel recovery. The variable thread_type can assume the values ON_RECVRY_THREADS or OFF_RECVRY_THREADS.

Action:

This status message requires no action. If you want a different number of worker threads allocated for parallel recovery, change the value of the ONCONFIG configuration parameter ON_RECVRY_THREADS or OFF_RECVRY_THREADS.

Logical Recovery Started

Cause:

Logical recovery began.

Action:

This status message requires no action.

Memory allocation error.

Cause:

Not enough main (OS) memory or not enough internal (database server) memory might cause this error.

Action:

See your operating-system documentation for information on how to increase OS memory. Alternatively, increase the virtual-memory size (SHMVIRTSIZE), the size of the added segments, (SHMADD), or your total shared-memory size (SHMTOTAL).

Mirror Chunk chunkname added to space spacename. Perform manual recovery.

Cause:

Fast recovery or full recovery has recovered the add of a mirror chunk. It does not perform automatic mirror recovery, however. The administrator must do this.

Action:

Use the onutil ALTER DBSPACE command to attempt to recover the mirror chunks.

Mixed transaction result. (pid=nn user=userid)

Cause:

You receive this message only when more than one database server is involved in a transaction. This message indicates that a database server, after preparing a transaction for commit, heuristically rolled back the transaction, and the global transaction completed inconsistently. The pid value is the user-process identification number of the coordinator process. The value of user is the user ID associated with the coordinator process.

Action:

See the information on recovering manually from failed two-phase commit in your IBM Informix: Administrator's Guide.

mt_shm_free_pool: pool 0xn has blocks still used (id nn)

Cause:

An internal error occurred during a pool deallocation because blocks are still associated with the pool.

Action:

Contact IBM Technical Support at tsmail@us.ibm.com.

mt_shm_init: can't create resident/virtual segment

Cause:

The causes for the failure to create the resident or virtual segment are as follows: (1) the segment size is less than the minimum segment size; (2) the segment size is larger than the maximum segment size; (3) allocating another segment would exceed the allowable total shared-memory size; or (4) a failure occurred while the database server was trying to allocate the segment.

Action:

If you suspect that this error was generated because of item 1 or 2 in the preceding paragraph, contact IBM Technical Support at tsmail@us.ibm.com. To correct item 3, increase the SHMTOTAL value in your ONCONFIG configuration file. For additional information about errors generated because of item 4, see your logical-log file.

mt_shm_remove: WARNING: may not have removed all/correct segments

Cause:

When the operating system tried to remove the shared-memory segments associated with the database server, the last segment did not equal the last segment registered internally. This situation is probably due to the unexpected failure of the database server.

Action:

Remove any segments that were not cleaned up.