Messages: D-E-F

dataskip is OFF for all dbspaces

Cause:

Informational.

Action:

None required.

dataskip is ON for all dbspaces

Cause:

Informational.

Action:

None required.

dataskip is ON for dbspaces: <dbspacelist>.

Cause:

Informational; DATASKIP is ON for the specified dbspaces.

Action:

None required.

dataskip will be turned {ON|OFF} for <dbspacename>.

Cause:

Informational; DATASKIP is ON or OFF for the specified dbspace.

Action:

None required.

DBSPACETEMP internal list not initialized, using default

Cause:

An error occurred while initializing a user-specified DBSPACETEMP list. Typically this condition is due to a memory-allocation failure.

Action:

Check for accompanying error messages.

The DBspace/BLOBspace spacename is now mirrored.

Cause:

You successfully added mirroring to the indicated storage space.

Action:

None required.

The DBspace/BLOBspace spacename is no longer mirrored.

Cause:

You have ended mirroring for the indicated storage space.

Action:

None required.

Dbspace dbspacename for Physical-log File not found

Cause:

The dbspace dbspacename specified by the PHYSDBS configuration parameter does not exist. As a consequence, the database server cannot complete initialization.

Action:

Use a dbspace known to exist.

devname: write failed, file system is full.

Cause:

Because the file system devname is full, the write failed.

Action:

Free some space in devname.

Dropping temporary tblspace 0xn, recovering nn pages.

Cause:

During shared-memory initialization, the database server routinely searches for temporary tables that are left without proper cleanup. If the database server finds a temporary table, it drops the table and recovers the space. The database server located the specified temporary tblspace and dropped it. The value 0xn is the hexadecimal representation of the tblspace number.

Action:

None required.

Dynamically allocated new shared memory segment (size nnnn)

Cause:

This status message informs you that the database server successfully allocated a new shared-memory segment of size nnnn.

Action:

None required.

ERROR: NO "waitfor" locks in Critical Section.

Cause:

The database server does not permit a thread to own locks that might have to wait while that thread is within a critical section. Any such lock request is denied, and an ISAM error message is returned to the user.

Action:

The error reported is an internal error. Contact IBM Technical Support at tsmail@us.ibm.com.

Error building sysmaster database. See outfile

Cause:

Errors were encountered in building the sysmaster database. The file outfile contains the result of running the script buildsmi.

Action:

See the file outfile.

Error writing pathname errno = nn

Cause:

The operating system cannot write to pathname. The number nn is the number of the operating-system error that was returned.

Action:

Investigate the cause of the operating-system error. Usually it means that no space is available for the file. It might also mean that the directory does not exist or that no write permissions exist.

Error writing shmem to file filename (error)
Unable to create output file filename errno=mm
Error writing filename errno=nn

Cause:

The database server detected an error in an attempt to write shared memory to filename. The first message is followed by one of the next two. Either the attempt failed because the output file could not be created or because the contents of shared memory could not be written. The error refers to the operating-system error that prompted the attempted write of shared memory to a file. The value of nn is the operating-system error.

Action:

See your operating-system documentation.

Fatal error initializing CWD string.
Check permissions on current working directory. Group groupname must have at least execute permission on '.'.

Cause:

Group groupname does not have execute permission for the current working directory.

Action:

Check permissions on the current working directory. You or the system administrator must give your group execute permission on the current working directory. After your group has been given permission, retry the operation that generated this message.

Fragments dbspacename1 dbspacename2 of table tablename set to non-resident.

Cause:

The specified fragments of tablename either have been set to nonresident by the SET TABLE statement.

Action:

None required.

Forced-resident shared memory not available

Cause:

The database server port for your computer does not support forced-resident shared memory.

Action:

None required.

Freed mm shared-memory segment(s) nn bytes

Cause:

The database server sends this message to the message log after you run the -F option of the onmode utility to free unused memory. The message informs you of the number of segments and bytes that the database server successfully freed.

Action:

None required.