Cause No space is available in the revive pool to allocate a new buffer.
Effect The procedure sets the error code and returns without performing the requested operation.
Recovery Wait for a few minutes, and then retry. If the problem persists, contact your service
provider.
765 (%1375) Unable to allocate space from the SQL
data area pool (MX buffer space).
(device type: 3)
Cause No space is available in the SQL data area pool to allocate a new buffer or reuse an existing
buffer. There are too many SQL/MX session requests for buffer space.
Effect The procedure sets the error code and returns without performing the requested operation.
Recovery Reduce the number of concurrent SQL/MX sessions for the disk volume. If the problem
persists, consider increasing the SQLMXBuffer size by issuing the SCF command ALTER DISK
$disk-name, SQLMXBUFFER size in MB. If the problem persists, contact your service provider.
NOTE: Increasing the SQL/MX buffer space reduces the memory available for cache. This can
degrade performance.
766 (%1376) The maximum number of opens for a single
file or partition has been reached.
(device type: 3)
Cause A file or partition open request exceeds the maximum number of opens for a single file or
partition on a volume.
Effect The procedure sets the error code and returns without performing the requested operation.
Recovery Wait for a few minutes, and then retry. Check the system for processes that are requesting
too many opens of a single file or partition. If the problem persists, contact your service provider.
899 (%1603) FENOSWITCH - An attempt to switch
CPUs with a PUP or SCF command failed.
Cause The primary or backup DP2 process is not running.
Effect The operation fails.
Recovery Ensure that both the primary and backup DP2 processes are running.
1091 (%2103) The file or table cannot be purged
until the NOPURGEUNTIL date.
Cause An attempt was made to purge a file for which the specified expiration date has not been
reached. The expiration date is set by using item code 57 of the FILE_CREATELIST_ procedure or
by using the NOPURGEUNTIL option of the FUP ALTER command.
Effect On a purge operation, if the NOPURGEUNTIL option is specified, the expiration date (a
four-word GMT timestamp) is checked against the current time. If the timestamp is less than the
current time, the file is not purged. All Enscribe files existing before C10 are assumed to have a
zero expiration date.
Recovery The expiration date of a file can be set or changed with a call to the C-series ALTER
procedure or a call to the D-series FILE_ALTERLIST_ procedure.
80 File-System Errors
To Next Page
Loading...
