Messages: A-B

Aborting Long Transaction: tx 0xn.

Cause:

The transaction spans the log space specified by transaction high-watermark (LTXHWM), and the offending long transaction is rolling back.

Action:

No additional action is needed. The address of the transaction structure in shared memory is displayed as a hexadecimal value.

Affinitied VP mm to phys proc nn.

Cause:

The database server successfully bound a CPU virtual processor to a physical processor.

Action:

None required.

Affinity not enabled for this server.

Cause:

You tried to bind your CPU virtual processors to physical processors, but the database server that you are running does not support process affinity.

Action:

Set AFF_NPROCS to 0, or remove the affinity setting from VPCLASS.

Assert Failed: Error from SBSpace cleanup thread.

Cause:

The sbspace cleanup thread encountered an error while cleaning up stray smart large objects.

Action:

See the action suggested in the message log file.

Most of the time, running onspaces -cl sbspacename on the failed sbspace succeeds in cleaning up any stray smart large objects. If you encounter an unrecoverable error, contact Technical Support.

Assert Failed: Short description of what failed
Who: Description of user/session/thread running at the time
Result: State of the affected database server entity
Action: What action the database administrator should take
See Also: DUMPDIR/af.uniqid containing more diagnostics.

Cause:

This message indicates an internal error.

Action:

The af.uniqid file in the directory specified by the ONCONFIG parameter DUMPDIR contains a copy of the assertion-failure message that was sent to the message log, as well as the contents of the current, relevant structures and/or data buffers. The information included in this message is intended for Technical Support.

Begin re-creating indexes deferred during recovery.

Cause:

During recovery, indexes to be created are deferred until after recovery completes. This message indicates that the database server deferred re-creating indexes and that it is now creating the indexes. During the time that the database server re-creates the indexes, it locks the affected tables with a shared lock.

Action:

None required.

Building 'sysmaster' database requires ~mm pages of logical log. Currently there are nn pages available. Prepare to back up your logs soon.

Cause:

You do not currently have the approximate amount of free log space necessary to complete a build of the sysmaster database.

Action:

Back up your logs.

Building 'sysmaster' database...

Cause:

The database server is building the sysmaster database.

Action:

None required.