Release 8.0.4
A58312-01
 Library |
 Product |
 Contents |
 Index |
| Oracle8 Error Messages Release 8.0.4 A58312-01 |
|
Cause: This program requires that a voltab file be specified.
Action: Rerun the program and specify the voltab file using the appropriate command line option.
Cause: An internal error occurred while trying to verify the volume information on the disk.
Action: Contact Oracle customer support.
Cause: Cannot open or access the voltab file.
Action: Verify that the voltab file exists and its access permissions allow the program to read it.
Cause: The process failed to open and initialize the indicated disk for the reasons above.
Action: Check to see if the disk or disk driver has failed. If no hardware or operating system problems are found, contact Oracle customer support.
Cause: MDS failed to mount all volumes.
Action: See the log for related error messages.
Cause: The number of disks in the volume must be a multiple of the raid width, which is indicated in the "width" parameter in the voltab file.
Action: Fix the voltab file by modifying the raid width or the number of disks that comprise the volume.
Cause: An internal error occurred while seeking within the indicated file.
Action: Contact Oracle customer support.
Cause: All disks in a volume must have the same size.
Action: Check that all disks within the volume have the same size. Replace the odd-sized disk(s).
Cause: All disks in a volume must have the same size.
Action: Check that all disks within the volume have the same size. Replace the odd-sized disk(s).
Cause: The indicated disk name does not have the proper format.
Action: Fix the syntax error which occurred, most likely in the voltab file or on the command line.
Cause: This server cannot access the indicated volume because the version of the server is incompatible with the version of the volume. This volume was probably created by a newer version of MDS whose format is not recognized by older versions of MDS.
Action: Use a more current version of MDS.
Cause: The process received the signal indicated.
Action: No action required. The log may contain errors from failures related to receipt of this signal.
Cause: An internal error occurred while reading within the indicated file.
Action: Contact Oracle customer support.
Cause: An internal error occurred while writing within the indicated file.
Action: Contact Oracle customer support.
Cause: The MDS server failed to read the table of contents for the indicated volume.
Action: Check the log for related error messages concerning disk I/O.
Cause: The stripe size indicated by "width" in the voltab file is not a legal value.
Action: Modify the voltab file to use a legal stripe size.
Cause: A syntax error was found in the voltab file.
Action: Fix the syntax error in the voltab file by using the format specified in the documentation.
Cause: None of the disks are responding to queries about their disk size.
Action: See the log for related error messages.
Cause: Internal error.
Action: Contact Oracle customer support.
Cause: Internal error.
Action: Contact Oracle customer support.
Cause: The indicated volume was not mounted.
Action: See the log for related error messages.
Cause: The indicated volume needs to be converted to a different format in order to be compatible with MDS. The conversion can only occur if the volume is mounted in read-write mode.
Action: Remount the volume in read-write mode.
Cause: The table of contents is full.
Action: Remove unused files from the volume.
Cause: The volume is full.
Action: Remove unused files from the volume.
Cause: Internal error.
Action: Contact Oracle customer support.
Cause: An internal error occurred while copying files.
Action: Contact Oracle customer support.
Cause: MDS lost a message.
Action: No action required. The log may contain errors from failures related to the lost message.
Cause: This process is an MDS client and is unable to locate the MDS server.
Action: Verify that an MDS server is running and accessible to the client.
Cause: The indicated voltab filename contains a syntax error.
Action: Rerun the program using a voltab filename with legal syntax.
Cause: Internal error.
Action: Contact Oracle customer support.
Cause: A write to the indicated disk failed for the reasons given.
Action: Check to see if the disk or disk driver has failed. If no hardware or operating system problems are found, contact Oracle customer support.
Cause: A flush to the indicated disk failed for the reasons given.
Action: Check to see if the disk or disk driver has failed. If no hardware or operating system problems are found, contact Oracle customer support.
Cause: An internal error occurred while reading within the indicated file.
Action: Contact Oracle customer support.
Cause: An internal error occurred while writing within the indicated file.
Action: Contact Oracle customer support.
Cause: A read to the indicated disk failed for the reasons given.
Action: Check to see if the disk or disk driver has failed. If no hardware or operating system problems are found, contact Oracle customer support.
Cause: The system-dependent error indicated occurred while waiting for disk I/O to complete.
Action: See your operating system documentation.
Cause: The voltab specification includes more disks per volume than allowed.
Action: Modify the voltab file to use fewer disks.
Cause: The indicated I/O operation failed because too many errors occurred.
Action: See the log for related error messages.
Cause: This program requires that the indicated argument be a legal filename.
Action: Rerun the program with a valid target filename.
Cause: An error occurred while verifying the volume's attributes.
Action: See the log for related error messages.
Cause: Internal error.
Action: Contact Oracle customer support.
Cause: The process cannot allocate memory for the I/O operation.
Action: Contact Oracle customer support.
Cause: Internal error.
Action: Contact Oracle customer support.
Cause: An error occurred while modifying the table of contents.
Action: See the log for related error messages.
Cause: The table of contents is full.
Action: Remove unused files from the volume.
Cause: The volume is full.
Action: Remove unused files from the volume.
Cause: MDS failed to mount the indicated volume.
Action: See the log for related error messages.
Cause: Internal error.
Action: Contact Oracle customer support.
Cause: An error occurred during rebuild.
Action: See the log for related error messages.
Cause: Internal error.
Action: Contact Oracle customer support.
Cause: The indicated disk is not responding to queries about its disk size.
Action: Check to see if the disk or disk driver has failed. If no hardware or operating system problems are found, contact Oracle customer support.
Cause: The server does not have as much bandwidth as the client requested in the indicated volume.
Action: Be prepared to encounter out-of-bandwidth errors. No immediate action required.
Cause: The server does not have enough bandwidth for the client in the indicated volume.
Action: Wait for other processes to free up bandwidth.
Cause: An I/O did not complete because it timed-out.
Action: See the log for related error messages.
Cause: A request to the MDS server did not complete because it timed-out.
Action: See the log for related error messages.
Cause: The number or size of the input files have changed since the program was run.
Action: Rerun the program.
Cause: The indicated input file has changed since the program was run.
Action: Rerun the program.
Cause: The process failed to open the indicated disk.
Action: Contact Oracle customer support.
Cause: The read operation indicated failed.
Action: Check to see if the disk or disk driver has failed. If no hardware or operating system problems are found, contact Oracle customer support.
Cause: The write operation indicated failed.
Action: Check to see if the disk or disk driver has failed. If no hardware or operating system problems are found, contact Oracle customer support.
Cause: The read operation indicated failed.
Action: Check to see if the disk or disk driver has failed. If no hardware or operating system problems are found, contact Oracle customer support.
Cause: The write operation indicated failed.
Action: Check to see if the disk or disk driver has failed. If no hardware or operating system problems are found, contact Oracle customer support.
Cause: Internal error.
Action: Contact Oracle customer support.
Cause: A volume can only be rebuilt if it is mounted in read-only or read-write mode.
Action: Remount volume in read-only or read-write mode.
Cause: The TOC of a volume can only be initialized if it is mounted in read-write mode.
Action: Remount volume in read-write mode.
Cause: The disk indicated needs to be rebuilt.
Action: Run mdsrebuild immediately.
Cause: The disks above both need to be rebuilt. However, since the failures are within the same raid stripe, they cannot both be rebuilt.
Action: Contact Oracle customer support.
Cause: An I/O error occurred on the disk indicated.
Action: Determine if the disk is broken. If it is, bring up MDS and specify the disk as a broken disk. Replace the disk with a working one and rebuild it immediately.
Cause: An I/O error occurred on the disk indicated.
Action: Determine if the disk is broken. If it is, bring up MDS and specify the disk as a broken disk. Replace the disk with a working one and rebuild it immediately.
Cause: The volume attributes on disk do not match the input voltab for any of the disks. The volume probably has not been initialized via mdsinit.
Action: If this is the case, run mdsinit to initialize the volume attributes.
Cause: Each volume or volume set can only support one outstanding disk rebuild at any time.
Action: Wait until the conflicting rebuild has completed before starting this disk rebuild.
Cause: Cannot read the volume attributes or mode from the indicated disk. In addition, the disk cannot be rebuilt because the volume does not contain parity information.
Action: Contact Oracle customer support.
Cause: Internal error.
Action: Contact Oracle customer support.
Cause: Internal error.
Action: Contact Oracle customer support.
Cause: Internal error.
Action: Contact Oracle customer support.
Cause: Internal error.
Action: Contact Oracle customer support.
Cause: The volume indicated cannot be mounted because the volume it is supposed to share bandwidth with is not mounted.
Action: Mount the volume with its own bandwidth resources or mount the volume whose bandwidth is to be shared first.
Cause: A volume must have a bandwidth capacity specified in order to be mounted.
Action: Specify the bandwidth capacity for the volume when mounting it.
Cause: The address is either negative or exceeds the size of the file.
Action: Rerun the program with a legal input address.
Cause: The start address must be smaller than the end address.
Action: Rerun the program with a legal start address.
Cause: The input voltab must correspond to the volume containing the disk being rebuilt.
Action: Rerun the program with the correct voltab or initialize the disk directly.
Cause: Internal error.
Action: Contact Oracle customer support.
Cause: Internal error.
Action: Contact Oracle customer support.
Cause: Internal error.
Action: Contact Oracle customer support.
Cause: Internal error.
Action: Contact Oracle customer support.
Cause: The file indicated cannot be opened.
Action: Verify that the file exists and that its access permission allow the desired type of access.
Cause: The host file operation indicated failed.
Action: Verify that the file exists and that its access permission allow the desired type of access.
Cause: The server cannot be created for reasons provided above.
Action: If the name server already contains an entry for MDS, restart the system. Otherwise, contact Oracle customer support.
Cause: The server cannot be registered for reasons provided above.
Action: If the name server already contains an entry for MDS, restart the system. Otherwise, contact Oracle customer support.
Cause: Another MDS server or utility is holding the lock to the global lock manager.
Action: If this process is still hung, contact Oracle customer support.
Cause: The rebuild process cannot open a file that needs to be rebuilt.
Action: See the log for related error messages.
Cause: A volume must be mounted in read-write mode in order to be converted to a version compatible with this server.
Action: Remount the volume in read-write mode.
Cause: Internal error.
Action: Contact Oracle customer support.
Cause: The host file indicated cannot be created.
Action: Verify that the filename is legal and the directory's access permissions.
Cause: The host file indicated cannot be closed.
Action: Verify that the file exists.
Cause: The file indicated is being written by another MDS client.
Action: Wait for that process to close the file.
Cause: The defragmentation slaves could not be launched.
Action: Verify that the defragger was started up as indicated in the documentation. If the problem persists, contact Oracle customer support.
Cause: Internal error.
Action: Contact Oracle customer support.
Cause: A previous error occurred.
Action: See the log for related error messages.
Cause: A previous error occurred.
Action: See the log for related error messages. The indicated file must be reloaded since its image on disk may have been corrupted.
Cause: Internal error.
Action: Contact Oracle customer support.
Cause: Internal error.
Action: Contact Oracle customer support.
Cause: Internal error.
Action: Contact Oracle customer support.
Cause: The indicated process is not exiting due to a previous error.
Action: Inform Oracle customer support. No immediate action required.
Cause: The indicated process is not exiting due to a previous error.
Action: Inform Oracle customer support. No immediate action required.
Cause: The volume indicated cannot be mounted because of the mount status of another MDS server.
Action: Remount the volume in a mode that does not conflict with the other MDS server(s).
Cause: The read operation indicated failed.
Action: Check to see if the disk or disk driver has failed. If no hardware or operating system problems are found, contact Oracle customer support.
Cause: The write operation indicated failed.
Action: Check to see if the disk or disk driver has failed. If no hardware or operating system problems are found, contact Oracle customer support.
Cause: The disk cannot be set to normal mode.
Action: Check to see if the disk or disk driver has failed. If no hardware or operating system problems are found, contact Oracle customer support.
Cause: The disk cannot be set to rebuild mode.
Action: Check to see if the disk or disk driver has failed. If no hardware or operating system problems are found, contact Oracle customer support.
Cause: The address is either negative or exceeds the size of the file.
Action: Rerun the program with a legal input address.
Cause: Internal error.
Action: Contact Oracle customer support.
Cause: A volume must have a bandwidth capacity specified in order to be mounted.
Action: Specify the bandwidth capacity for the volume.
Cause: A volume cannot be unmounted if MDS clients are actively reading and writing files in that volume.
Action: Wait for all MDS clients to close the files in that volume before unmounting it.
Cause: A volume cannot be remounted if MDS clients are writing to files in that volume.
Action: Wait until all MDS clients have finished writing to the volume.
Cause: Internal error.
Action: Contact Oracle customer support.
Cause: The volume indicated was not unmounted.
Action: See the log for related error messages.
Cause: The volume indicated was not remounted.
Action: See the log for related error messages.
Cause: The errors encountered while trying to remount the indicated volume are fatal.
Action: See log fore related error messages. Contact Oracle customer support.
Cause: A volume cannot be remounted with less bandwidth capacity.
Action: Remount the volume with at least the same amount of bandwidth capacity.
Cause: To mount a volume, the voltab must be specified.
Action: Remount the volume and specify the voltab.
Cause: Internal error.
Action: Contact Oracle customer support.
Cause: Internal error.
Action: Contact Oracle customer support.
Cause: Internal error.
Action: Contact Oracle customer support.
Cause: Internal error.
Action: Contact Oracle customer support.
Cause: Files that have been deleted cannot be modified.
Action: If you really want to write to the deleted file, recover the file first by undeleting it.
Cause: The volume's table of contents is larger than the volume.
Action: Verify that the volume hasn't inadvertently shrunk. If not, then decrease the TOC size by specifying a smaller value in the voltab.
Cause: The size of the volume's TOC has probably been recently increased. The new TOC is occupying disk space also occupied by the indicated file.
Action: If the size of the volume's TOC has indeed been recently increased, then revert back to the original TOC size. Remove the conflicting files before increasing the TOC size.
Cause: The user has specified the same filename for both the source and destination file for an operation that requires the source filename to be different than the destination. Example: mdscp, mdsconcat.
Action: Use different files for src and dst; be aware that wildcarding or links may cause different filenames to refer to the same file.
Cause: The user has specified incompatible resources. A common cause is specifying incompatible arguments to a process, such as both length_in_bytes and end_address for mdssum.
Action: Consult the documentation for the correct usage.
Cause: The user has specified a relative filename and the resource mds.cwd is not set. Mds does not know where the file may reside.
Action: Specify an absolute pathname (beginning with /mds), or set the mds.cwd resource, i.e. setenv MDS_CWD /mds/int1
Cause: The TOC of the volume appears to be corrupt. This is usually caused by having run mdsvolinit on the volume to change the spec of the TOC, and using a modified voltab file with a different raidsize or stripe width.
Action: If the cause is as described above, rerun mdsvolinit with the correct voltab information. If not, contact WWS.
Cause: The indicated volume is currently being mounted by another MDS server and has not yet been rebuilt. Consequently, the disk mode cannot be set to normal.
Action: Rebuild the indicated disk as soon as possible.
Cause: The volume attributes on this disk do not correspond with the volume's.
Action: Check the voltab information and verify that it is correct. If the disk should be rebuilt or spared, follow the procedure as documented.
Cause: An attempt to read volume information for the indicated disk failed. MDS expects this disk to be up and readable because either the volume doesn't have parity or another disk disk within the same raid stripe has already failed.
Action: Check the voltab information and verify that it is correct. Check that the disk is on-line and operating correctly. If the error still occurs, contact Oracle customer support.
Cause: MDS expects all of the volumes that exist on the indicated disk to be listed in the input voltabs.
Action: Check that all volumes that exist on the indicated disk are on one of the input voltabs and that the input voltabs are correct.
Cause: MDS is unable to read or find the disk status information for the indicated volume.
Action: Check that the voltab information is correct. Verify that all disks in the volumes are in the correct mode. Verify that all disks in the volume are on-line and operating correctly. If the error still occurs, contact Oracle customer support.
Cause: Another MDS process has exclusively control of the MDS lock.
Action: Wait for a few seconds and rerun mdsrebuild.
Cause: Internal error.
Action: Contact Oracle customer support.
Cause: If a disk is in use a spare, another disk cannot be spared to it.
Action: Either: choose another disk to spare to or unspare the spare disk.
Cause: Spare disks depend on parity protection to rebuild missing info. Without parity, you cannot spare a disk.
Action: None possible other than a complete redo of volume with parity.
Cause: Mds believes that the disk is potentially in use by another server. As such, it cannot safely return the disk to normal mode until all known and in-use partitions on the disk have been rebuilt.
Action: Run mdsrebuild within the other servers to rebuild the other partitions of the new disk. When the disk is completely rebuilt, use mdsdiskmode to return the disk to normal mode.
Cause: The volume was created with a spare disk that is no longer specified or does not match the name of the spare that was originally used.
Action: Correct the voltab to list the original spare disk name, or run "mdsvolinit -s" to change the spare disk name on the other disks.
Cause: You cannot spare an operating disk to another operating disk. You can only spare a normal operating disk to a specified spare.
Action: Make sure you are sparing a normal disk in the volume to one of the specified spares for that volume.
Cause: The disk (or possibly simulated disk, i.e. a file) is too small.
Action: Acquire bigger disks.
Cause: The segment length and offset are invalid. This could either be an internal error, or tar is encountering filenames with incorrect segment information.
Action: Check the segmented filenames carefully to see if they are properly formed. If they are, contact WWS.
Cause: The TAR header appears to be corrupt.
Action: Obtain a new copy of the TAR archive.
Cause: mdstar was unable to open the archive (usually a physical device).
Action: Check the device or archive name for legality and the correct permissions. Check for hardware connectivity problems.
Cause: mdstar was unable to close the archive (usually a physical device). May be caused by premature shutdown or loss of archive device.
Action: None. However this warning may indicate that the TAR archive may be incomplete.
Cause: The TAR archive appears to be corrupt. Tar must always read block multiples of 512 bytes.
Action: Obtain a new copy of the TAR archive.
Cause: The TAR archive appears to be corrupt. Tar must always read block multiples of 512 bytes.
Action: Obtain a new copy of the TAR archive.
Cause: The TAR archive appears to be corrupt. mdstar expected a TAR archive header and found a bad checksum within the header.
Action: Obtain a new copy of the TAR archive.
Cause: The segment length and offset are invalid. This could either be an internal error, or tar is encountering filenames with incorrect segment information.
Action: Check the segmented filenames carefully to see if they are properly formed. If they are, contact WWS.
Cause: Missing a segment. This could either be an internal error, or tar is encountering filenames with incorrect segment information.
Action: Check the segmented filenames carefully to see if they are properly formed and complete. If they are, contact WWS.
Cause: Failed to parse the next segment name. This could either be an internal error, or tar is encountering filenames with incorrect segment information.
Action: Check the segmented filenames carefully to see if they are properly formed. If they are, contact WWS.
Cause: Unexpected write error probably caused by read-only volume, or having a locked file with the same name present in Mds.
Action: Bring up Mds in read/write mode, or remove the locked file.
Cause: Unexpected read error. Probably caused by disk unavailability.
Action: None. By default mdstar will try several times to read/write in the face of intermittent errors. Check possible physical problems and for interference from other disk intensive processes.
Cause: An expected resource was not set or was set incorrectly.
Action: Check to see that the resource is set properly, usually via the command line.
Cause: mdstar must either extract, create, or list archives.
Action: Specify an action via the command line.
Cause: mdstar has reached the end of the archive. Reading a multi-volume archive or creating an archive that is larger than a physical tape will cause mdstar to assume that the archive is spread across multiple tapes.
Action: Insert the next tape and hit return.
Cause: The specified disk is not part of any of the volumes currently mounted by the MDS server. A disk rebuild can only occur if the volumes on that disk are mounted.
Action: Verify that the disk name is correct. If it is, start up the MDS server with the associated volumes mounted.
Action: Specify only one of the options: -I, -R, -W.
Action: Specify the volume with only one of the options: -i, -r, -w.
