Messages: N-O-P

Newly specified value of value for the pagesize in the configuration file does not match older value of value. Using the older value.

Cause:

This message displays upon database server restart. The PAGESIZE value changed in the ONCONFIG file after the database server was initialized.

Action:

The database server uses the older PAGESIZE value.

Not enough main memory

Cause:

The database server detected an error in an attempt to acquire more memory space from the operating system.

Action:

For more information about shared-memory configuration and management, refer to your operating-system documentation.

Not enough physical procs for affinity

Cause:

The ONCONFIG parameters AFF_NPROCS and AFF_SPROC are not correctly set. AFF_SPROC plus AFF_NPROCS is greater than the number of physical processors on your computer or node.

Action:

Reset AFF_NPROCS and AFF_SPROC, such that the value AFF_SPROC plus value of AFF_NPROCS is less than or equal to the number of physical processors.

The number of configured CPU poll threads exceeds NUMCPUVPS.

Cause:

The number of in-line poll threads that you specified in the ONCONFIG configuration file exceeds the number of CPU virtual processors.

Action:

Reduce the number of in-line poll threads to be less than or equal to the number of CPU virtual processors.

onconfig parameter parameter modified from old_value to new_value

Cause:

When the database server shared memory is reinitialized, this message documents any changes that occurred since the last initialization.

Action:

None required.

oninit: Fatal error in initializing ASF with 'ASF_INIT_DATA' flags asfcode = '25507'

Cause:

The nettype value specified in the sqlhosts file or registry for the database server is invalid or unsupported, or the servicename specified in the sqlhosts file or registry for the database server is invalid.

Action:

Check the nettype and servicename values in the sqlhosts file or registry for each DBSERVERNAME and for the DBSERVERALIASES. Check the nettype value in each NETTYPE parameter in the ONCONFIG file.

Online Mode.

Cause:

The database server is in online mode. Users can access all databases

Action:

This status message requires no action.

Open transaction detected when changing log versions.

Cause:

The database server detected an open transaction while it was trying to convert the data from a previous version of the database server.

Action:

Conversion is not allowed unless the last record in the log is a checkpoint. You must restore the previous version of the database server, force a checkpoint, and then retry conversion.

Out of message shared memory

Cause:

The database server could not allocate more memory for the specified segment.

Action:

For additional information, see the log file.

out of resident shared memory

Cause:

The database server could not allocate more memory for the specified segment.

Action:

For additional information, see the log file.

out of virtual shared memory

Cause:

The database server could not allocate more memory for the specified segment.

Action:

For additional information, see the log file.

PANIC: Attempting to bring system down

Cause:

A fatal database server error occurred.

Action:

See the error that caused the panic and attempt the corrective action suggested by the error message. For additional information that might explain the failure, refer also to other messages in the message-log file.

Participant site database_server heuristically rolled back

Cause:

A remote site rolled back a transaction after it reached the prepared-for-commit phase.

Action:

You might need to roll back the transaction on other sites and then restart it.

Possible mixed transaction result.

Cause:

This message indicates that error -716 has been returned. Associated with this message is a list of the database servers where the result of a transaction is unknown.

Action:

For information on determining if a transaction was implemented inconsistently, see the IBM Informix: Administrator's Guide.

Prepared participant site server_name did not respond

Cause:

Too many attempts were made to contact remote site server_name. After several timeout intervals were met, the site was determined to be down.

Action:

Verify that the remote site is online and that it is correctly configured for distributed transactions. Once the remote site is ready, reinitiate the transaction.

Prepared participant site server_name not responding

Cause:

The database server is attempting to contact remote site server_name. For some unknown reason, the database server cannot contact the remote site.

Action:

Verify that the remote site is online and that it is correctly configured for distributed transactions.