Messages: G-H-I

gcore pid; mv core.pid dir/core.pid.ABORT.

Cause:

This status message during a database server failure provides the name and place of each core file associated with the virtual processors.

Action:

None required.

I/O function chunk mm, pagenum nn, pagecnt aa --> errno = bb.

Cause:

An operating-system error occurred during an attempt to access data from disk space. The operating-system function that failed is defined by function. The chunk number and physical address of the page where the error occurred are displayed as integers. The pagecnt value refers to the number of pages that the thread was attempting to read or write. If an errno value is displayed, it is the number of the operating-system error and might explain the failure. If function is specified as bad request, some unexpected event caused the I/O attempt on an invalid chunk or page.

Action:

If the chunk status changes to D, or down, restore the chunk from its mirror or repair the chunk. Otherwise, perform a data restore.

I/O error, primary/mirror Chunk pathname -- Offline (sanity).

Cause:

The database server detected an I/O error on a primary or mirror chunk with pathname. The chunk was taken offline.

Action:

Check that the device on which the chunk was stored is functioning as intended.

Deleted Indexes idx1 and idx 2 error message

Informix database_server Initialized - Complete Disk Initialized.

Cause:

Disk space and shared memory have been initialized. Any databases that existed on the disk before the initialization are now inaccessible.

Action:

None required.

Informix database_server Initialized - Shared Memory Initialized.

Cause:

Shared memory has been initialized.

Action:

None required.

Informix database_server Stopped.

Cause:

The database server has moved from quiescent mode to offline mode. The database server is offline.

Action:

None required.

ERROR: Insufficient available disk in the root dbspace to increase the entire Configuration save area.

Cause:

The user attempted to increase the number of storage objects to a specific value by changing CONFIGSIZE or setting MAX_DBSPACES, MAX_DBSLICES, or MAX_CHUNKS to a higher value, but the database server did not have enough rootspace for the increased number of storage objects. A storage object might be a dbspace, dbslice, or chunk.

Action:

Increase the size of the root dbspace or reset CONFIGSIZE, MAX_DBSPACES, MAX_DBSLICES, or MAX_DBSLICES to a lower value and restart the database server. For example, if you set MAX_CHUNKS to 32,768, but the root dbspace did not have enough space, set MAX_CHUNKS to a lower value.

Insufficient available disk in the root dbspace for the CM save area. Increase the size of the root dbspace in the ONCONFIG file and reinitialize the server.

Cause:

The cause might be one of the following:

The user attempted to increase the number of storage objects to a specific value by changing CONFIGSIZE or setting MAX_DBSPACES, MAX_DBSLICES, or MAX_CHUNKS to a higher value, but the database server did not have enough rootspace for the increased number of storage objects. A storage object might be a dbspace, dbslice, or chunk.
The user converted to a database server version that requires slightly more rootspace, but it is not available (this case is unlikely).

Action:

Take one of the following actions:

Increase the size of the root dbspace or reset CONFIGSIZE, MAX_DBSPACES, MAX_DBSLICES, or MAX_DBSLICES to a lower value and restart the database server. For example, if you set MAX_DBSPACES to 32,768 but the root dbspace did not have enough space, set MAX_DBSPACES to a lower value.
Increase the size of the root dbspace and reinitialize the database server.

Internal overflow of shmid's, increase system max shared memory segment size.

Cause:

The database server was initializing shared memory when it ran out of internal storage for the shared-memory IDs associated with this segment.

Action:

Increase the value of your maximum kernel shared-memory segment size, usually SHMMAX. For more information, see your operating-system documentation.