Messages: Q-R-S

Quiescent Mode.

Cause:

The database server has entered quiescent mode from some other state. On UNIX, only users logged in as informix or as root can interact with the database server. On Windows, only members of the Informix-Admin group can interact with the database server. No user can access a database.

Action:

None required.

Read failed. Table name, Database name, iserrno = number

Cause:

An error occurred reading the specified system table.

Action:

Note the error number and contact Technical Support.

Recovery Mode.

Cause:

The database server entered the recovery mode. No user can access a database until recovery is complete.

Action:

None required.

Recreating index: 'dbsname:"owner".tabname-idxname'.

Cause:

This message indicates which index is currently being re-created.

Action:

None required.

Rollforward of log record failed, iserrno = nn.

Cause:

The message appears if, during fast recovery or a data restore, the database server cannot roll forward a specific logical-log record. The database server might be able to change to quiescent or online mode, but some inconsistency could result. For further information, see the message that immediately precedes this one. The iserrno value is the error number.

Action:

Contact IBM Informix Technical Support.

Root chunk is full and no additional pages could be allocated to chunk descriptor page.

Cause:

The root chunk is full.

Action:

To free space in the root chunk, take one of the following actions:

Drop and re-create the sysmaster database.
Move user tables from the root dbspace to another dbspace.
Refragment tables.

scan_logundo: subsys ss, type tt, iserrno ee.

Cause:

A log undo failed because log type tt is corrupt.

The variables in this message have the following values:

ss: Is the subsystem name.
tt: Is the logical-log record type.
ee: Is the iserror number.

Action:

Examine the logical log with the onlog utility to determine if any action is needed. Contact Technical Support.

Session completed abnormally. Committing tx id 0xm, flags 0xn.

Cause:

Abnormal session completion occurs only when the database server is attempting to commit a transaction that has no current owner, and the transaction develops into a long transaction. The database server forked a thread to complete the commit.

Action:

None required.

Session completed abnormally. Rolling back tx id 0xm, flags 0xn.

Cause:

Abnormal session completion occurs only when the database server is attempting to commit a distributed transaction that has no current owner, and the transaction develops into a long transaction. The database server forked a thread that rolled back the transaction.

Action:

None required.

semctl: errno = nn.

Cause:

When the database server initialized a semaphore, an error occurred. The operating-system error is returned.

Action:

See your operating-system documentation.

semget: errno = nn.

Cause:

An allocation of a semaphore set failed. The operating-system error is returned.

Action:

See your operating-system documentation.

shmat: some_string os_errno: os_err_text.

Cause:

An attempt to attach to a shared-memory segment failed. The system error number and the suggested corrective action are returned.

Action:

Review the corrective action (if given), and determine if it is reasonable to try. For more information, refer to your operating-system documentation.

shmctl: errno = nn.

Cause:

An error occurred while the database server tried to remove or lock a shared-memory segment. The operating-system error number is returned.

Action:

See your operating-system documentation.

shmdt: errno = nn.

Cause:

An error occurred while the database server was trying to detach from a shared-memory segment. The operating-system error number is returned.

Action:

See your operating-system documentation.

shmem sent to filename.

Cause:

The database server wrote a copy of shared memory to the specified file as a consequence of an assertion failure.

Action:

None.

shmget: some_str os_errno: key shmkey: some_string.

Cause:

Either the creation of a shared-memory segment failed, or an attempt to get the shared-memory ID associated with a certain key failed. The system error number and the suggested corrective action are returned.

Action:

Consult your operating-system documentation.

Shutdown (onmode -k) or override (onmode -O).

Cause:

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

When the checkpoint actually happens, the following message appears: Checkpoint blocked by down space, waiting for override or shutdown.

Action:

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.

Shutdown Mode.

Cause:

The database server is in the process of moving from online mode to quiescent mode.

Action:

None required.

Space spacename added.

Cause:

The database server administrator added a new storage space spacename to the database server.

Action:

None required.

Space spacename dropped.

Cause:

The database server administrator dropped a storage space spacename from the database server.

Action:

None required.

Space spacename -- Recovery Begins(addr).

Cause:

This informational message indicates that the database server is attempting to recover the storage space.

The variables in this message have the following values:

spacename: Is the name of the storage space that the database server is recovering.
addr: Is the address of the control block.

Action:

None required.

Space spacename -- Recovery Complete(addr).

Cause:

This informational message indicates that the database server recovered the storage space.

The variables in this message have the following values:

spacename: Is the name of the storage space that the database server has recovered.
addr: Is the address of the control block.

Action:

None required.

Space spacename -- Recovery Failed(addr).

Cause:

This informational message indicates that the database server was unable to recover the storage space.

The variables in this message have the following values:

spacename: Is the name of the storage space that the database server failed to recover.
addr: Is the address of the control block.

Action:

None required.

sysmaster database built successfully.

Cause:

The database server successfully built the sysmaster database.

Action:

None required.

Successfully extend physical log space

Cause:

The physical log space was successfully extended to the file plog_extend.servernum under the designated path.

Action:

None required.