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 logical-log files, Increase LOGFILES.

Cause:

During a data restore, the value of the LOGFILES configuration must always be greater than or equal to the total number of logical-log files. At some point during the restore, the number of logical-log files exceeded the value of LOGFILES.

Action:

Increase the value of LOGFILES in ONCONFIG.

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: Cannot have SINGLE_CPU_VP non-zero and number of CPU VPs greater than 1.

Cause:

The ONCONFIG file contains VPCLASS cpu with a num= value greater than 1 and a nonzero value for SINGLE_CPU_VP. SINGLE_CPU_VP must be 0 (or omitted) when there are more than 1 CPU VPs.

Action:

Correct the ONCONFIG file and restart the database server.

oninit: Cannot have SINGLE_CPU_VP non-zero and user-defined VP classes.

Cause:

The ONCONFIG file contains a user-defined VPCLASS as well as a nonzero value for SINGLE_CPU_VP. SINGLE_CPU_VP must be 0 (or omitted) when the ONCONFIG file contains a user-defined VPCLASS.

Action:

Correct the ONCONFIG file and restart the database server.

oninit: Cannot mix VPCLASS cpu and NUMCPUVPS, AFF_SPROC, AFF_NPROCS, or NOAGE parameters.

Cause:

The ONCONFIG file contains both VPCLASS cpu and one or more of the other listed parameters. It cannot contain both.

Action:

Correct the ONCONFIG file and restart the database server.

oninit: Cannot mix VPCLASS aio and NUMAIOVPS parameters.

Cause:

The ONCONFIG file contains both VPCLASS aio and NUMAIOVPS. It cannot contain both.

Action:

Correct the ONCONFIG file and restart the database server.

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.

oninit: invalid or missing name for Subsystem Staging Blobspace.

Cause:

You set the configuration parameter STAGEBLOB to a blobspace that does not exist.

Action:

Use the -d option of onspaces to create the blobspace specified in STAGEBLOB, and restart the database server.

oninit: Too many VPCLASS parameters specified.

Cause:

Too many VPCLASS parameter lines have been specified in the ONCONFIG file.

Action:

Reduce the number of VPCLASS lines, if possible. If not possible, contact Technical Support.

oninit: VPCLASS classname bad affinity specification.

Cause:

The affinity specification for the VPCLASS line is incorrect. Affinity is specified as a range:

For m, use processor m.

For m to n, use processors in the range m to n inclusive, where m <=n, m >= 0, and n >= 0.

Action:

Correct the VPCLASS parameter in the ONCONFIG file and restart the database server.

oninit: VPCLASS classname duplicate class name.

Cause:

The VPCLASS classname in the ONCONFIG file has a duplicate name. VP class names must be unique.

Action:

Correct the duplicate name and restart the database server.

oninit: VPCLASS classname illegal option.

Cause:

One of the fields in the VPCLASS classname parameter is illegal.

Action:

Correct the parameter in the ONCONFIG file and restart the database server.

oninit: VPCLASS classname maximum number of VPs is out of the range 0-10000.

Cause:

The maximum number of VPs specified by a VPCLASS parameter line must be in the range 1 to 10,000.

Action:

Correct the value and restart the database server.

oninit: VPCLASS classname name is too long. Maximum length is maxlength.

Cause:

The length of the name field in VPCLASS classname is too long.

Action:

Choose a shorter class name, correct the ONCONFIG file, and restart the database server.

oninit: VPCLASS classname number of VPs is greater than the maximum specified.

Cause:

The initial number of VPs specified by a VPCLASS parameter is greater than the maximum specified by the same VPCLASS parameter.

Action:

Correct the VPCLASS parameter and restart the database server.

oninit: VPCLASS classname number of VPs is out of the range 0-10000.

Cause:

The initial number of VPs specified by a VPCLASS parameter line must be in the range 1 to 10,000.

Action:

Correct the value and restart the database server.

onmode: VPCLASS classname name is too long. Maximum length is maxlength.

Cause:

The name of a dynamically added VP class that onmode -p specifies is too long.

Action:

Choose a shorter name, and retry the onmode -p command.

Optical Subsystem is running.

Cause:

You set the value of the STAGEBLOB parameter in the configuration file, and the database server is communicating properly with the optical-storage subsystem.

Action:

No action is required.

Optical Subsystem is not running.

Cause:

You set the value of the STAGEBLOB parameter in the configuration file, but the database server cannot detect the existence of the optical-storage subsystem.

Action:

Check that the optical subsystem is online.

Optical Subsystem STARTUP Error.

Cause:

The database server detects that the optical-storage subsystem is running, but the database server cannot communicate with it properly.

Action:

Check your optical subsystem for errors.

Online Mode.

Cause:

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

Action:

This status message requires no action.

onspaces: unable to reset dataskip.

Cause:

This error message comes from the onspaces utility. For some reason, the utility cannot change the specification of DATASKIP (ON or OFF) across all dbspaces in the database server instance.

Action:

You are unlikely to receive this message. If the error persists after you restart the database server, Contact Technical Support.

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.

Physical recovery complete: number pages examined, number pages restored.

Cause:

This message displays during fast recovery. The number of pages examined indicates the number of page images that exist in the physical log. The number of pages restored indicates the actual number of pages that are restored from the physical log. The number of pages restored is always less than or equal to the number examined.

The database server might physically log a page image multiple times between checkpoints. Physical recovery restores only the first logged page image.

If a page stays in the memory buffer pool, the database server physically logs it once per checkpoint, and stores one page image in the physical log. If the buffer pool is too small, a page that is being updated many times might get forced out of the buffer pool to disk and then brought back into memory for the next update. Each time the page is brought into memory, it is physically logged again, resulting in duplicate page images in the physical log.

Action:

If the number of pages examined is much larger than the number of pages restored, increase the size of the buffer pool to reduce the number of duplicate before-images. For more information, see the IBM Informix Performance Guide.

Physical recovery started at page (chunk:offset).

Cause:

This message displays during fast recovery. Chunk is the number of the chunk that contains the physical log. Offset is the page offset of the start of the physical log entries. Physical recovery begins restoring pages from that point.

Action:

No action required. For information on fast recovery, see the IBM Informix Administrator's Guide.

Portions of partition partnum of table tablename in database dbname were not logged. This partition cannot be rolled forward.

Cause:

Light appends occurred to the operational table since the last backup.

Action:

If you want full access to data in this table, you need to alter the table to raw and then to the desired table type. This alter operation removes inconsistencies in the table that resulted from replaying non-logged operations such as light appends.

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.