Error Occurs During File Open; Error Occurs During Read/Write Activity - HP Guardian Errors Manual

Error Occurs During File Open

Cause The file you attempted to open is marked as corrupt. A utility command such as FUP DUP,
FUP LOAD, SQLCI DUP, SQLCI LOAD, or RESTORE has not finished.
Effect The procedure sets the error code and returns without performing the requested operation.
The file or table cannot be opened.
Recovery Wait until the utility operation finished before attempting to open the file. If the file is not
currently open, then the utility abended before finishing; purge the file or table.

Error Occurs During Read/Write Activity

Cause The structured file or table has an inconsistent structure.
Effect The procedure sets the error code and returns without performing the requested operation.
The portion of the file or table with the inconsistent structure cannot be accessed or updated.
Recovery Examine the EMS event logs for BAD FILE DETECTED events. Run the FILCHECK utility to
determine whether the file is broken. If FILCHECK reports a broken file or table, use the TMF
subsystem or the RESTORE program to recover the data. If TMF or RESTORE recovery is not
available, and recovery is required, contact your service provider for assistance.
60
Cause This error can occur for the following reasons:
The specified file resides on a volume that has been removed from the system or on a device
that was brought down after the file was opened.
The file is a device or process on a remote system whose link has gone down.
If a server returned this error, the server received a message from a process that it does not
recognize as its opener. This can happen if a FILE_OPEN_ procedure was used to open a file
but the file name did not include the optional sequence number.
Certain sequences of DDL and DML operations can result in an error 60 (lost open). Refer to
the NonStop SQL/MP Reference Manual for more information on opening SQL files.
Effect The procedure sets the error code and returns without performing the requested operation.
Recovery Ensure that the device (if any) is up, close the file and reopen it, then try again. If that is
not successful, abort the operation and start over.
61
Cause The number of open files on this volume reached the maximum allowed, or the system
operator used a PUP STOPOPENS command (on D-series systems) or SCF STOPOPENS (on G-series
systems) to stop any more files from being opened on the volume.
Effect The procedure sets the error code and returns without performing the requested operation.
Recovery Retry when files can be opened.
62
(%74) The file resides on a removed volume,
the device is downed or not open,
or a server has failed and a process has
been replaced by a different process with
the same name since the server was opened.
(device type: any except 1 and 2)
(%75) No more file opens are permitted on this
volume or device; the system operator issued
a STOPOPENS command or the number of open files
reached the maximum allowed. (device type: 3)
(%76) The volume was mounted but no mount
order was given, so the file open is
not permitted. (device type: 3)
Error Code Descriptions 35