Messages: T-U-V

Table tablename set to resident

Cause:

The indicated table has been made resident by the SET TABLE statement.

Action:

No action is required.

Table tablename and all its indexes set to resident

Cause:

The indicated table and all its indexes have been made resident by the SET TABLE statement.

Action:

No action is required.

The following tables have outstanding old version data pages due to an In-Place Alter Table. Perform UPDATE table-name SET column = column WHERE 1=1; to clear these pages from the following tables.

Cause:

Reversion to a previous version of the database server has been attempted while an in-place ALTER TABLE is in progress. The previous versions of the database server cannot handle tables that have multiple schemas of rows in them.

Action:

Force any in-place alters to complete by updating the rows in the affected tables before you attempt to revert to a previous version of the database server. To do this, create a dummy update in which a column in the table is set to its own value, forcing the row to be updated to the latest schema in the process without actually changing column values. Rows are always altered to the latest schema, so a single pass through the table that updates all rows completes all outstanding in-place alters.

TIMER VP: Could not redirect I/O in initialization, errno = nn

Cause:

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.

Action:

See your operating-system documentation.

Too Many Active Transactions.

Cause:

During a data restore, there were too many active transactions. At some point during the restore, the number of active transactions exceeded 32 kilobytes.

Action:

None.

Transaction Not Found

Cause:

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.

Action:

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

Transaction heuristically rolled back

Cause:

A heuristic decision occurred to roll back a transaction after it completed the first phase of a two-phase commit.

Action:

None required.

Transaction table overflow - user id nn, process id nn

Cause:

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.

Action:

Try again later.

Unable to create output file filename errno = nn

Cause:

The operating system cannot create output file filename. The errno is the number of the operating-system error returned.

Action:

Verify that the directory exists and has write permissions.

Unable to extend nn reserved pages for purpose in root chunk.

Cause:

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.)

Action:

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.

Unable to start SQL engine

Cause:

The database server encountered an out-of-memory condition.

Action:

No action is necessary.

Unable to open tblspace nn, iserrno = nn

Cause:

The database server cannot open the specified tblspace. (The value nn is the hexadecimal representation of the tblspace number.)

Action:

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 http://www.ibm.com/software/data/informix
/pubs/library/.

The value of pagesize pagesize specified in the config file is not a valid pagesize. Use 2048, 4096 or 8192 as the value for PAGESIZE in the onconfig file and restart the server.

Cause:

This message displays upon disk initialization. The value of PAGESIZE that was specified in the ONCONFIG file is not a valid value.

Action:

Restart the database server with a valid PAGESIZE value.

Virtual processor limit exceeded

Cause:

You configured the database server with more than the maximum number of virtual processors allowed (1000).

Action:

To reduce the number of virtual processors, decrease the values of VPCLASS, NUMCPUVPS, NUMAIOVPS, or NETTYPE in your ONCONFIG file.