The Optical Subsystem Message File

Under certain exceptional conditions, the Optical Subsystem API writes messages to the message file. In general, the messages indicate that the Optical Subsystem made a request of the optical-storage subsystem and the optical-storage subsystem was unable to accomplish it. For the content of these messages and an appropriate action or response, if one is required, see the documentation from your optical-storage subsystem vendor. A message consists of two error numbers. The first error number is Informix specific, and the second is generated by the vendor's subsystem log file. The MSGPATH parameter in the ONCONFIG file specifies the UNIX pathname of the system message log file. For more information about the message log file, refer to the IBM Informix: Administrator's Reference.

The database server writes the following messages concerning the Optical Subsystem to the message log file:

oninit: invalid or missing name for Subsystem Staging Blobspace

Cause:

The STAGEBLOB configuration parameter specifies a blobspace, but the named blobspace does not exist. This message is normal the first time oninit is started with the Optical Subsystem. Check to see if you have accidentally created the STAGEBLOB as a dbspace instead of a blobspace.

Action:

Use onspaces with the -b option to create the blobspace.

Optical Subsystem is running

Cause:

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

Action:

None required.

Optical Subsystem is not running

Cause:

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

Or on UNIX, the /usr/lib/iosm10a.so link is not linked to the optical library.

Action:

Check that the optical-storage subsystem is online.

Optical Subsystem STARTUP Error

Cause:

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

Action:

Check your optical-storage subsystem for errors.

Unable to initiate communication with the Optical Subsystem

Cause:

The optical driver that the optical-drive vendor supplies indicates that the drive is not accessible.

Action:

Check the driver installation and the cabling between the computer and the drive.