ACFS-00100 to ACFS-14107

2 ACFS-00100 to ACFS-14107

ACFS-00100: Enabled: Cause: /*Action single letter option; Action: n/a
ACFS-00501: unable to allocate a buffer: Cause: A request for process virtual memory failed. This message is accompanied by other message(s) providing details on the error.; Action: Correct the problem indicated by the other message(s). If possible, change options to reduce required memory and/or take steps to increase memory available to the process. Otherwise, report this error to Oracle Support Services.
ACFS-00502: Failed to communicate with the ACFS driver. Verify the ACFS driver has been loaded.: Cause: The ACFS control device could not be accessed.; Action: Verify the ACFS driver is loaded and running.
ACFS-00503: invalid numeric value specified: string: Cause: The command argument does not support the specified value.; Action: Review the command usage and retry the command providing valid input.
ACFS-00504: Invalid unit specified: string. Valid units are K|M|G|T|P.: Cause: The command does not support the specified unit.; Action: Review the command usage and retry the command providing valid input.
ACFS-00505: invalid signature requested: Cause: The command failed to verify the ACFS file system metadata.; Action: Contact Oracle Support Services.
ACFS-00506: Failed to read 'string'.: Cause: An open file could not be read.; Action: The most likely cause is a file permission problem.
ACFS-00507: Failed to seek to string prior to writing the volume disk header.: Cause: A seek to the volume failed. This message is accompanied by other message(s) providing details on the error.; Action: Correct the problem indicated by the other message(s). If the solution is not clear, contact Oracle Support Services.
ACFS-00508: unable to obtain device major and minor number for volume string: Cause: Failed to obtain volume information. This message is accompanied by other message(s) providing details on the error.; Action: Correct the problem indicated by the other message(s). If the solution is not clear, contact Oracle Support Services.
ACFS-00509: unsupported file type for string, not a block device: Cause: Volume provided was not recognized as a block device. This message is accompanied by other message(s) providing details on the error.; Action: Correct the problem indicated by the other message(s). If the solution is not clear, contact Oracle Support Services.
ACFS-00510: unable to obtain volume id for string: Cause: Volume id was not obtained. This message is accompanied by other message(s) providing details on the error.; Action: Correct the problem indicated by the other message(s). If the solution is not clear, contact Oracle Support Services.
ACFS-00511: string is mounted on at least one node of the cluster.: Cause: Cluster was still using the file system.; Action: Make sure the file system is unmounted on all cluster nodes before running the file system checking utility.
ACFS-00512: A file system check of string is in progress.: Cause: The command failed because metadata showed that a file system check was either in progress or incomplete on the specified volume.; Action: Ensure that a file system check is not being run on another node or by another user before retrying the command. If a file system check operation had been started and then aborted, use 'fsck -f' to repair the volume and then retry the command.
ACFS-00513: unable to obtain ACFS driver version number: Cause: The ACFS driver version number could not be retrieved. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.
ACFS-00514: unable to close handle: Cause: Handle could not be closed. This message is accompanied by other message(s) providing details on the error.; Action: Correct the problem indicated by the other message(s). If the solution is not clear, contact Oracle Support Services.
ACFS-00515: version mismatch: \n string string version \n string ACFS kernel version: Cause: The command failed because of a mismatch between the loaded ACFS driver and the ACFS commands.; Action: Use the 'acfsdriverstate version' command to obtain additional version information and contact Oracle Support Services.
ACFS-00516: stat of string failed: Cause: Stat() failed. This message is accompanied by other message(s) providing details on the error.; Action: Correct the problem indicated by the other message(s). If the solution is not clear, contact Oracle Support Services.
ACFS-00517: unable to obtain block device sector size: Cause: Failed to obtain volume information. This message is accompanied by other message(s) providing details on the error.; Action: Correct the problem indicated by the other message(s). If the solution is not clear, contact Oracle Support Services.
ACFS-00518: unable to obtain volume size in sectors: Cause: Failed to obtain volume information. This message is accompanied by other message(s) providing details on the error.; Action: Correct the problem indicated by the other message(s). If the solution is not clear, contact Oracle Support Services.
ACFS-00519: too many arguments: string: Cause: Too many arguments were entered on the command line.; Action: Review the command usage and retry the command providing the correct number of arguments.
ACFS-00520: string is not an ADVM volume.: Cause: Volume specified was not an ADVM volume.; Action: Retry the command specifying an ADVM volume.
ACFS-00521: Failed to determine file type of string.: Cause: Failed to obtain volume information. This message is accompanied by other message(s) providing details on the error.; Action: Correct the problem indicated by the other message(s). If the solution is not clear, contact Oracle Support Services.
ACFS-00522: unable to get drive structure: Cause: Failed to obtain volume information. This message is accompanied by other message(s) providing details on the error.; Action: Correct the problem indicated by the other message(s). If the solution is not clear, contact Oracle Support Services.
ACFS-00523: string is an unsupported drive type number.: Cause: Failed to obtain volume information. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.
ACFS-00524: unable to obtain partition information: Cause: Failed to obtain volume information. This message is accompanied by other message(s) providing details on the error.; Action: Correct the problem indicated by the other message(s). If the solution is not clear, contact Oracle Support Services.
ACFS-00525: failed to seek to string: Cause: Failed to seek to volume. This message is accompanied by other message(s) providing details on the error.; Action: Correct the problem indicated by the other message(s). If the solution is not clear, contact Oracle Support Services.
ACFS-00526: read of volume disk header failed: Cause: Failed to read volume. This message is accompanied by other message(s) providing details on the error.; Action: Correct the problem indicated by the other message(s). If the solution is not clear, contact Oracle Support Services.
ACFS-00527: unable to dismount volume: Cause: Could not dismount volume. This message is accompanied by other message(s) providing details on the error.; Action: Correct the problem indicated by the other message(s). If the solution is not clear, contact Oracle Support Services.
ACFS-00528: Volume string is already mounted on string.: Cause: The file system could not be mounted because the specified volume was already mounted using a different mount point.; Action: Select a different volume and retry the mount operation.
ACFS-00531: write of volume disk header failed: Cause: Write to volume failed. This message is accompanied by other message(s) providing details on the error.; Action: Correct the problem indicated by the other message(s). If the solution is not clear, contact Oracle Support Services.
ACFS-00532: invalid option: string: Cause: The command does not support the specified option.; Action: Review the command usage and retry the command providing valid options.
ACFS-00533: string requires an argument: Cause: The command did not pass a required argument.; Action: Review the command usage and retry the command providing the needed argument.
ACFS-00534: A valid numeric string is required.: Cause: The command was rejected because the specified value was not a valid numeric string.; Action: Review the command usage and retry the command providing valid input.
ACFS-00535: insufficient arguments: Cause: The command required additional arguments.; Action: Review the command usage and retry the command providing the needed argument.
ACFS-00536: unknown extra argument: string: Cause: The command was rejected because the indicated argument was not a valid argument for this command.; Action: Review the command usage and retry the command providing valid options.
ACFS-00538: invalid command or command is not unique: string: Cause: The command was rejected because the indicated sub-command was not supported.; Action: Review the command usage and retry the command providing valid input.
ACFS-00539: missing arguments: Cause: The command was rejected because additional arguments were required.; Action: Review the command usage and retry the command providing valid input.
ACFS-00540: incorrect number of arguments: Cause: The command was rejected because an incorrect number of arguments were specified.; Action: Review the command usage and retry the command providing valid input.
ACFS-00542: argument is not an integer: Cause: The command was rejected because a string was specified as an argument instead of an integer.; Action: Review the command usage and retry the command providing valid input.
ACFS-00543: invalid command: Cause: The command was rejected because an invalid sub-command was specified.; Action: Review the command usage and retry the command providing valid input.
ACFS-00544: option spelling is not unique: string: Cause: An attempt to execute a command specifying an abbreviated option name was rejected because there were multiple possible options beginning with the specified string.; Action: Review the command usage and retry the command providing the desired option.
ACFS-00545: string does not support a value: string=string: Cause: The command was rejected because an option that does not support a value was specified with a value attached.; Action: Review the command usage and retry the command providing the correct option syntax.
ACFS-00546: failed to change on-disk signature: Cause: The command failed to update ACFS metadata on-disk. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.
ACFS-00547: Both the primary and alternate superblocks are damaged.: Cause: The file system metadata was found to be damaged.; Action: Run fsck (Unix or Linux) or acfschkdsk.exe (Windows) as soon as possible to fix the metadata inconsistency.
ACFS-00548: Failed to communicate with the ACFS driver. Verify that cluster membership has been established.: Cause: The ACFS driver's control device could not be accessed.; Action: Verify the driver is loaded and running. Also, verify that the ASM instance is accessible.
ACFS-00549: mount path string already contains a volume mount point for volume string: Cause: The mount path contained a reparse point that references a a different volume than the mount request.; Action: Verify the path is correct. If it is, the existing volume mount point must be removed before a new one can be created. Use acfsdismount to remove the mount point.
ACFS-00550: checksums for both superblocks are bad: Cause: An attempt to validate the metadata on-disk failed due to a metadata inconsistency found in the file system superblocks.; Action: Run the ACFS Fixer to resolve the metadata inconsistency and then retry the operation.
ACFS-00551: unable to process input from the command line: Cause: A failure occurred opening the stdin stream. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.
ACFS-00552: End-of-file received instead of 'y' or 'n': Cause: An end-of-file was received while waiting for the answer to a question prompt.; Action: None
ACFS-00554: Unable to obtain group name for gid: number: Cause: The command failed because the group name could not be determined using the supplied group id.; Action: Ensure that the required group exists, then re-run the command.
ACFS-00555: unsupported file type for string, not a device file: Cause: Volume provided was not recognized as a device file. This message is accompanied by other message(s) providing details on the error.; Action: Correct the problem indicated by the other message(s). If the solution is not clear, contact Oracle Support Services.
ACFS-00556: invalid vfs name string: Cause: a helper command was called with an unexpected vfs name argument; Action: Verify that ACFS helper commands are installed in the '/sbin/helpers/acfs' directory and that '/etc/vfs' contains the correct information for ACFS. If the solution is not clear, contact Oracle Support Services.
ACFS-00560: Operation not applicable for FSType string: Cause: ACFS did not support the specified option.; Action: Review the command usage and retry the command providing valid options.
ACFS-00561: auto-resize percent must be 0 (to disable) or 5-50 (to enable).: Cause: Invalid percentage specified.; Action: Re-run the command with a percentage within the valid range.
ACFS-00562: An attempt to create Oracle Registry ACFS key string resulted in a registry error. string: Cause: An error was returned by the Oracle Registry service when attempting to create an ACFS key. This message is accompanied by other message(s) that provide details as to the exact cause of the failure.; Action: Correct the problem indicated by the other message(s). If the cause of the problem is unclear, contact Oracle Support Services.
ACFS-00563: Auto-resize is currently configured for file system string. The requested size command may cause the system to re-grow the file system.: Cause: The requested size will shrink the file system and reduce the amount of free space to a level that may cause the system to re-grow the file system.; Action: Run 'acfsutil size' to change the auto-resize parameters if re-growth of the filesystem is not desired.
ACFS-00564: unable to delete Oracle Registry key string while trying to recover from an error string: Cause: Removal of a key from the Oracle Registry failed.; Action: Run ocrcheck to verify the Oracle Registry is working properly.
ACFS-00565: unable to delete Oracle Registry key string string: Cause: Removal of mount key from Oracle Registry failed.; Action: Use acfsutil registry to verify the mount key exists in the Oracle Registry.
ACFS-00566: invalid handle received when attempting to close an ACFS mount key within Oracle Registry: Cause: An error was returned during the closing of a key in the Oracle Registry.; Action: Run ocrcheck to verify the Oracle Registry is working properly. Report to Oracle Support Services.
ACFS-00567: unknown Oracle Registry error encountered closing key: Cause: An error was returned while closing the key from the Oracle Registry.; Action: Run ocrcheck to verify the Oracle Registry is working properly. Report to Oracle Support Services.
ACFS-00568: closing of a key resulted in Oracle Registry error number: Cause: An error was returned during the closing of a key in the Oracle Registry.; Action: Verify the Oracle Registry is accessible. If it is not accessible and the cause is unclear, report this error to Oracle Support Services.
ACFS-00569: invalid handle received when attempting to delete an ACFS mount key within Oracle Registry: Cause: An error was returned while removing a key from the Oracle Registry.; Action: Report this error to Oracle Support Services.
ACFS-00570: The ACFS mount key specified for deletion does not exist within Oracle Registry.: Cause: The mount key could not be located in the Oracle Registry.; Action: Use acfsutil registry to ensure the mount entry exists in the Oracle Registry.
ACFS-00571: The ACFS mount key specified for deletion is not empty.: Cause: The mount key specified for deletion from the Oracle Registry contained dependent subkeys.; Action: View the mount entries in the Oracle Registry using "acfsutil registry" and remove any dependent mount entries before retrying this operation.
ACFS-00572: permission denied to delete the ACFS mount entry from Oracle Registry: Cause: The user permissions were insufficient to remove the key from the Oracle Registry.; Action: Verify the Oracle Registry is accessible and that command is being run from a properly authorized user ID.
ACFS-00573: Oracle Registry error encountered while deleting an ACFS mount key: Cause: An error was returned while removing the key from the Oracle Registry.; Action: Report this error to Oracle Support Services.
ACFS-00575: deletion request of key resulted in Oracle Registry error number: Cause: An error was returned while removing a key from the Oracle Registry.; Action: Run ocrcheck to verify that Oracle Registry is working properly. If problem persists, report to Oracle Support Services.
ACFS-00584: failed to look up ACFS mount points in the Oracle Registry string: Cause: An error was returned while looking up a mount point in the Oracle Registry.; Action: Run ocrcheck to verify the Oracle Registry is working properly. If problem persists, report to Oracle Support Services.
ACFS-00585: null parameter received: Cause: A null parameter was passed to the Oracle Registry.; Action: Run ocrcheck to verify that Oracle Registry is working properly. If problem persists, report to Oracle Support Services.
ACFS-00587: unknown Oracle Registry error encountered during operation on ACFS mount entry: Cause: An error was returned while accessing the key from the Oracle Registry.; Action: Run ocrcheck to verify that Oracle Registry is working properly. If problem persists, report to Oracle Support Services.
ACFS-00589: key operation resulted in Oracle Registry error number: Cause: An error was returned during a key operation with the Oracle Registry.; Action: Run ocrcheck to verify that Oracle Registry is working properly. If problem persists, report to Oracle Support Services.
ACFS-00591: error found in volume disk header: Cause: An attempt to validate the metadata on-disk failed due to a metadata inconsistency found in the volume disk header.; Action: Run the ACFS Fixer to resolve the metadata inconsistency and then retry the operation.
ACFS-00592: Seek to volume failed. Verify the volume exists.: Cause: Seek to a location on the volume failed.; Action: Verify the volume exists on this node and that it is accessible.
ACFS-00593: The Oracle Registry returned the following error while attempting to access ACFS key string string: Cause: Failed to access either the SYSTEM, SYSTEM.ACFS or SYSTEM.ACFS.Mounts keys in Oracle Registry.; Action: Run ocrcheck to verify the Oracle Registry is working properly. Examine the appended error message from the Oracle Registry service.
ACFS-00594: Failed to access ACFS mount information. The Oracle Registry returned the appended error for ACFS key string. string: Cause: Failed to access ACFS mount information from the Oracle Registry.; Action: Examine the appended error message from the Oracle Registry.
ACFS-00595: Failed to access ACFS mount value information. The Oracle Registry returned the appended error for ACFS key string. string: Cause: Failed to access ACFS mount value information from the Oracle Registry. This might be due to Oracle Registry corruption or a sudden loss of the Oracle Registry service.; Action: Examine the appended error message from the Oracle Registry. Run ocrcheck to verify the Oracle Registry is working properly.
ACFS-00596: A failure occurred while accessing the Oracle Registry ACFS key "SYSTEM" for security purposes and follows this message: string: Cause: Failed to retrieve key access rights for the Oracle Registry ACFS key "SYSTEM"; Action: Run ocrcheck to verify the Oracle Registry is working properly. Evaluate the error message returned from the Oracle Registry appended to this message. If necessary, run ocrdump and make sure the "SYSTEM" key exists and is accessible.
ACFS-00597: Failed to initialize the Oracle Registry's SCLS context. The SCLS error is included with this message.: Cause: An operating system initialization failed.; Action: Evaluate the attached SCLS error message. Run ocrcheck to verify the Oracle Registry is functioning correctly.
ACFS-00598: An error occurred while looking up the current user's operating system account name. The error is included with this message.: Cause: ACFS was attempting to add an entry to the Oracle Registry. During this attempt a lookup of the current user's name failed in the operating system failed.; Action: Evaluate the attached error message to determine why the current user name could not obtained from the operating system.
ACFS-00599: The Oracle Registry returned the following error while attempting to close the ACFS key string string: Cause: Possibly due to Oracle Registry corruption or a sudden loss of the Oracle Registry service.; Action: Examine the appended error message from the Oracle Registry. Run ocrcheck to verify the Oracle Registry is working properly.
ACFS-00600: Failed to access ACFS mount subkey information. The Oracle Registry returned the appended error. string: Cause: Failed to access ACFS mount information from the Oracle Registry.; Action: Examine the appended error message from the Oracle Registry.
ACFS-00601: Failed to initialize this utility's access to the Oracle Registry. Verify the registry service has started.: Cause: Either the Oracle Registry service was unavailable or the registry configuration was incomplete/inaccurate.; Action: Run ocrcheck to verify the registry service is working properly.
ACFS-00602: An internal error (BADARG) occurred while trying to determine the Oracle Registry configuration.: Cause: An Oracle internal error.; Action: Contact Oracle.
ACFS-00603: Failed to retrieve the Oracle Cluster Registry, OCR, configuration: Cause: Failed to obtain OCR information.; Action: Run ocrcheck to verify OCR is working properly.
ACFS-00604: Failed to retrieve the Oracle Local Registry, OLR, configuration: Cause: Failed to obtain Oracle Local Registry information.; Action: Run ocrcheck -local to verify the OLR is working properly.
ACFS-00605: Failed to retrieve the Oracle Registry configuration for an unknown reason: Cause: Failed to obtain Oracle Registry information.; Action: Run ocrcheck to verify the registry is working properly.
ACFS-00606: Could not determine if the system is configured for RAC or Oracle Restart environment.: Cause: The Oracle Registry service configuration could not be detected; Action: Run ocrcheck to verify the Oracle registry service.
ACFS-00607: Failed to access or create Oracle Registry keys required for ACFS operation: Cause: Oracle Registry keys required for operation either could not be accessed or created.; Action: Another error message number will follow this message. Analyze its output. Run ocrcheck to verify the Oracle registry is functioning properly. Also, verify acfsutil was invoked with administrative rights when attempting to add the ACFS mount points.
ACFS-00608: Invalid option combination: string conflicts with another option.: Cause: The command did not support the specified option combination.; Action: Review the command usage and retry the command providing valid options.
ACFS-00609: End-of-file received.: Cause: An end-of-file was received while waiting for the answer to a question prompt.; Action: None
ACFS-00619: This is a string computer, but the file system was created on a string string computer.: Cause: The file system was created on a computer which has a different Endian than the current system. Little Endian machines (such as the intel x86 based systems) store the Least Significant bit in the first byte of an integer value. Big Endian machines (such as Solaris SPARC and AIX Power based systems) store the Most Significant bit in the first byte of an integer value.; Action: Use a system with the same Endian as the system which created the file system.
ACFS-00620: This feature is not available for Oracle version string or lower on this platform.: Cause: Informational.; Action: None
ACFS-00621: Unable to determine privileges: Cause: An error occured retrieving the user credentials.; Action: Verify the mount point is an ACFS mount point and it is not offline.
ACFS-00622: must provide a base mount point: Cause: A mount point on the base site was not provided.; Action: Provide an existing mount point on the base site.
ACFS-00623: must provide a target mount point: Cause: A mount point on the target site was not provided.; Action: Provide an existing mount point with an empty file system on the target site.
ACFS-00624: The path specified is too long.: Cause: The path specified exceeded the allowed maximum path length.; Action: Verify the path was entered correctly, or use a different path.
ACFS-00625: string is not a valid ACFS mount point.: Cause: The mount point path specified was not a valid mount point.; Action: Provide a valid ACFS mount point.
ACFS-00634: unsupported operation for read-only volume string: Cause: The requested operation failed because the target was on a read-only volume.; Action: Retry the operation using a writable volume.
ACFS-00999: unexpected assert: "string", string: string: number: Cause: An unexpected situation has occurred.; Action: Contact Oracle Support Services.
ACFS-01001: Size specified cannot exceed size of volume.: Cause: Volume size was smaller than the requested size.; Action: Select a size that is less than or equal to the volume size and retry the ACFS format command.
ACFS-01002: ACFS requires a minimum volume size of numberMB.: Cause: Volume was too small.; Action: Select a larger volume and retry.
ACFS-01003: failed to generate a unique file system ID: Cause: An error occurred during the generation of a unique file system identifier. This message is accompanied by other messages providing details on the error.; Action: Correct the problem indicated by the other messages. If the solution is not clear, contact Oracle Support Services.
ACFS-01004: string was not formatted.: Cause: An error occurred during the formatting of the volume.; Action: This message is accompanied by another error message. Respond as indicated for that message."
ACFS-01005: unable to allocate a buffer: Cause: A request for process virtual memory by the ACFS format command failed. This message is accompanied by other message(s) providing details on the error.; Action: Correct the problem indicated by the other message(s). If possible, change options to reduce required memory and/or take steps to increase memory available to the process. Otherwise, report this error to Oracle Support Services.
ACFS-01006: unable to open volume device 'string': Cause: Volume device could not be opened. This message is accompanied by other message(s) providing details on the error.; Action: Correct the problem indicated by the other message(s). If the cause of the problem is unclear, contact Oracle Support Services.
ACFS-01007: unable to close volume handle: Cause: An attempt to close a volume handle failed. The accompanying messages provide detailed information on the failure.; Action: Correct the problem described in the accompanying messages if possible and retry the command. If the solution is not clear, contact Oracle Support Services.
ACFS-01008: unable to open file system string: Cause: File system was not accessible.; Action: Verify the volume associated with the file system is enabled and online before retrying.
ACFS-01009: unable to close file system handle: Cause: An attempt to close a file system handle failed. The accompanying messages provide detailed information on the failure.; Action: Correct the problem described in the accompanying messages if possible and retry the command. If the solution is not clear, contact Oracle Support Services.
ACFS-01010: Volume already contains an ACFS file system. To reformat the volume, reissue string with the stringf option.: Cause: The on-disk metadata indicated that an ACFS file system is located on the volume.; Action: Verify the intended volume and reissue the format command with the force flag to overwrite the existing ACFS file system.
ACFS-01011: Volume contains an ACFS file system that is being checked. To reformat the volume, reissue string with the stringf option.: Cause: The volume contained a file system that was in the process of being checked by fsck (Unix or Linux) or acfschkdsk.exe (Windows).; Action: Verify the intended volume and reissue the format command with the force flag to overwrite the existing ACFS file system.
ACFS-01014: write of volume label failed: Cause: A write to the volume during file system creation failed. This message is accompanied by other message(s) providing details on the error.; Action: Correct the problem indicated by the other message(s). If the solution is not clear, contact Oracle Support Services.
ACFS-01015: failed to clear the contents of the volume: Cause: An attempt to write to the volume failed. The accompanying messages provide detailed information on the failure.; Action: Correct the problem described in the accompanying messages if possible and retry the command. If the solution is not clear, contact Oracle Support Services.
ACFS-01017: length of file system name exceeds number: Cause: An ACFS file system could not be created because the length of the file system name exceeded the indicated maximum length.; Action: Retry the command (mkfs on Unix or Linux or acfsformat.exe on Windows) supplying a name with length less than or equal to the indicated maximum.
ACFS-01018: failed to allocate a buffer for number bytes: Cause: A request for process virtual memory by the ACFS format command failed. This message is accompanied by other message(s) providing details on the error.; Action: Correct the problem indicated by the other message(s). If possible, change options to reduce required memory and/or take steps to increase memory available to the process. Otherwise, report this error to Oracle Support Services.
ACFS-01019: This volume contains a mounted ACFS file system. The file system must be dismounted with acfsdismount on all nodes.: Cause: The volume was in use by another file system.; Action: Dismount the ACFS file system with acfsdismount and retry the command.
ACFS-01020: This volume contains a mounted non-ACFS file system. The file system must be dismounted with 'advmutil dismount'.: Cause: The volume was in use by another non-ACFS file system.; Action: Dismount the non-ACFS file system with 'advmutil dismount' and retry the command.
ACFS-01021: length of volume name exceeds number: Cause: An ACFS file system could not be created because the length of the volume name exceeded the indicated maximum length.; Action: Retry the command (mkfs on Unix or Linux or acfsformat.exe on Windows) supplying a name with length less than or equal to the indicated maximum.
ACFS-01022: failed to bring ADVM volume string online: Cause: An ACFS file system could not be created because an error occurred while bringing the volume online. This message is accompanied by other messages providing details on the error.; Action: Correct the problem described in the accompanying messages if possible and retry the command. If the solution is not clear, contact Oracle Support Services.
ACFS-01025: failed to generate a file system id: Cause: An ACFS file system could not be created because an error occurred during the generation of a file system identifier. This message is accompanied by other messages providing details on the error.; Action: Correct the problem described in the accompanying messages if possible and retry the command. If the solution is not clear, contact Oracle Support Services.
ACFS-01026: storage type mismatch of primary volume and accelerator volume: Cause: An ACFS file system could not be created because the supplied primary volume and accelerator volume were different storage types. Storage types include ASM, local volumes.; Action: Retry the command supplying a primary volume and accelerator volume that have the same storage type.
ACFS-01028: One volume disk header is corrupt. To reformat the volume, reissue string with the stringf option.: Cause: One of the volume disk headers was corrupt.; Action: Verify the intended volume and reissue the format command with the force flag to overwrite the corrupted ACFS file system.
ACFS-01033: write to volume failed: Cause: A write to the volume during file system creation failed. This message is accompanied by other message(s) providing details on the error.; Action: Correct the problem indicated by the other message(s). If the cause of the problem is unclear, contact Oracle Support Services.
ACFS-01038: write failed during setup of root directory entry: Cause: A write to the volume during file system creation failed. This message is accompanied by other message(s) providing details on the error.; Action: Correct the problem indicated by the other message(s). If the cause of the problem is unclear, contact Oracle Support Services.
ACFS-01041: write of snaps directory entry failed: Cause: A write to the volume during file system creation failed. This message is accompanied by other message(s) providing details on the error.; Action: Correct the problem indicated by the other message(s). If the cause of the problem is unclear, contact Oracle Support Services.
ACFS-01043: write of lost+found directory entry failed: Cause: A write to the volume during file system creation failed. This message is accompanied by other message(s) providing details on the error.; Action: Correct the problem indicated by the other message(s). If the cause of the problem is unclear, contact Oracle Support Services.
ACFS-01044: write of file entry table failed: Cause: A write to the volume during file system creation failed. This message is accompanied by other message(s) providing details on the error.; Action: Correct the problem indicated by the other message(s). If the cause of the problem is unclear, contact Oracle Support Services.
ACFS-01045: write of global bitmap failed: Cause: A write to the volume during file system creation failed. This message is accompanied by other message(s) providing details on the error.; Action: Correct the problem indicated by the other message(s). If the cause of the problem is unclear, contact Oracle Support Services.
ACFS-01046: read of global bitmap file entry failed: Cause: A read of the volume during file system creation failed. This message is accompanied by other message(s) providing details on the error.; Action: Correct the problem indicated by the other message(s). If the cause of the problem is unclear, contact Oracle Support Services.
ACFS-01047: write of global bitmap file entry failed: Cause: A write to the volume during file system creation failed. This message is accompanied by other message(s) providing details on the error.; Action: Correct the problem indicated by the other message(s). If the cause of the problem is unclear, contact Oracle Support Services.
ACFS-01049: seek to snap map header failure: Cause: A seek to the volume during file system creation failed. This message is accompanied by other message(s) providing details on the error.; Action: Correct the problem indicated by the other message(s). If the cause of the problem is unclear, contact Oracle Support Services.
ACFS-01050: write to snap map header failure: Cause: A write to the volume during file system creation failed. This message is accompanied by other message(s) providing details on the error.; Action: Correct the problem indicated by the other message(s). If the cause of the problem is unclear, contact Oracle Support Services.
ACFS-01051: partial write to snap map header failure: Cause: A write to the volume during file system creation failed. This message is accompanied by other message(s) providing details on the error.; Action: Correct the problem indicated by the other message(s). If the cause of the problem is unclear, contact Oracle Support Services.
ACFS-01052: write to snap map info entry failure: Cause: A write to the volume during file system creation failed. This message is accompanied by other message(s) providing details on the error.; Action: Correct the problem indicated by the other message(s). If the cause of the problem is unclear, contact Oracle Support Services.
ACFS-01053: partial write to snap map info entry failure: Cause: A write to the volume during file system creation failed. This message is accompanied by other message(s) providing details on the error.; Action: Correct the problem indicated by the other message(s). If the cause of the problem is unclear, contact Oracle Support Services.
ACFS-01054: write to snap map storage entry failure: Cause: A write to the volume during file system creation failed. This message is accompanied by other message(s) providing details on the error.; Action: Correct the problem indicated by the other message(s). If the cause of the problem is unclear, contact Oracle Support Services.
ACFS-01055: partial write to snap map storage entry failure: Cause: A write to the volume during file system creation failed. This message is accompanied by other message(s) providing details on the error.; Action: Correct the problem indicated by the other message(s). If the cause of the problem is unclear, contact Oracle Support Services.
ACFS-01094: string cannot be formatted with the supplied options: Cause: The file system creation failed because the specified volume was not an ADVM volume. The default set of options requires an ADVM volume. If the specified volume is a local volume, the -l option is required.; Action: Retry the command with an ADVM volume or, if the volume is a local volume, retry the command with the -l option.
ACFS-01095: unable to determine current directory: Cause: An ACFS file system could not be created because an attempt to determine the current directory failed. This message is accompanied by other messages providing details on the error.; Action: Correct the problem described in the accompanying messages if possible and retry the command. If the solution is not clear, contact Oracle Support Services.
ACFS-01096: length of volume path exceeds number: Cause: An ACFS file system could not be created because the length of the volume path exceeded the indicated maximum length.; Action: Retry the command (mkfs on Unix or Linux or acfsformat.exe on Windows) supplying a volume path with length less than or equal to the indicated maximum.
ACFS-01113: Block size string is invalid for metadata.: Cause: An attempt to create a file system was rejected because the requested metadata block size was invalid.; Action: Specify a metadata block size of 4096 or take the default. File system creation sets the metadata block size to the primary volume's logical sector size by default.
ACFS-01150: unable to synchronize in-memory file data to disk: Cause: A request to flush all in-memory copies of buffers associated with the open handle failed. This message is accompanied by other message(s) providing details on the error.; Action: Correct the problem identified by the other message(s). If the problem has been resolved and the file system is unusable, retry the ACFS format command.
ACFS-01151: Ignoring invalid block size number, using number: Cause: An ACFS format command unsupported block size was specified.; Action: No action required. A supported block size will be used.
ACFS-01152: The length of accelerator volume name exceeds number.: Cause: Accelerator volume name length exceeded the maximum length displayed in the message.; Action: Select an accelerator volume name with length less than or equal to the maximum length displayed in the message and retry the command.
ACFS-01154: The accelerator volume contains a mounted ACFS file system. The file system must be dismounted with acfsdismount on each node.: Cause: The specified volume could not be used as an accelerator volume because it was in use by a mounted file system.; Action: Dismount the ACFS file system with acfsdismount and retry the command.
ACFS-01155: The accelerator volume contains a mounted non-ACFS file system. The file system must be dismounted with 'advmutil dismount'.: Cause: The specified volume could not be used as an accelerator volume because it was in use by a mounted non-ACFS file system.; Action: Dismount the non-ACFS file system with 'advmutil dismount' and retry the command.
ACFS-01156: The Oracle ASM Dynamic Volume Manager (Oracle ADVM) compatibility attribute for the disk group is less than the required minimum 12.1.0.2.0.: Cause: An attempt to create a file system with an accelerator volume failed because the ADVM compatibility attribute for the disk group was not set to 12.1.0.2.0 or higher.; Action: Use the Oracle ASM Configuration Assistant (ASMCA) tool or the SQL statement ALTER DISKGROUP to upgrade COMPATIBLE.ADVM attribute.
ACFS-01159: The accelerator volume must be different from the volume containing the file system.: Cause: The file system could not be created because the same volume was specified for both the accelerator and the file system.; Action: Choose a different volume for the accelerator and retry the command.
ACFS-01160: The specified accelerator volume was smaller than the number string required for this file system.: Cause: The file system could not be created because the specified accelerator volume was below the minimum allowed size reported in the message.; Action: Select a larger accelerator volume and retry the command.
ACFS-01164: The specified device 'string' is already in use with a CRS-managed file system.: Cause: The file system could not be created because the specified device was already registered with CRS (Cluster Ready Services).; Action: Select an unused device, or use srvctl to modify the association for this device and retry the file system creation.
ACFS-01170: Accelerator volume sector size = number must match primary volume sector size = number: Cause: An attempt to create a file system was rejected because the logical sector sizes of primary and accelerator volume were different, as shown. The sector sizes of the primary and accelerator volumes must be the same.; Action: Select devices that have the same logical sector size for the primary and accelerator volumes or specify the 'i 4096' switch.
ACFS-01171: string cannot be formatted as a local file system with ACFS compatibility less than the current release: Cause: The file system creation failed because the -l option was specified with a -c option that specified ACFS compatibility for a previous release.; Action: Retry the command without the -c option.
ACFS-01173: The Oracle ASM Dynamic Volume Manager (Oracle ADVM) compatibility attribute for the disk group is less than the required minimum 12.2.0.0.0.: Cause: An attempt to create a file system failed because the ADVM disk group compatibility had not been upgraded to the indicated version for either the primary or accelerator volume, which is required for that command.; Action: Use the Oracle ASM Configuration Assistant (ASMCA) tool or the SQL ALTER DISKGROUP statement to upgrade the disk group compatibility (COMPATIBLE.ADVM attribute) to the specified version and then re-issue the original command. If the disk group compatibility cannot be upgraded, update the ACFS compatibility using the 'acfsutil compat set' command and then re-issue the original command.
ACFS-01176: file system format requires volumes with sector size = number: Cause: An attempt to create a file system was rejected because the logical sector size of the primary or accelerator volumes was too large for the 512-byte metadata block size format.; Action: Select devices with a 512-byte logical sector size when creating a file system using the 'i 512' format switch. Use the command 'advmutil volstats' to verify that the volume's sector size is 512 bytes before formatting the file system. Alternatively, format the file system without the 'i 512' switch, allowing Oracle ACFS to create a 4096-byte metadata block size format.
ACFS-01179: The Oracle ASM Dynamic Volume Manager (Oracle ADVM) compatibility attribute for the disk group is less than the required minimum number.number.number.number.number: Cause: An attempt to create a file system failed because the ADVM disk group compatibility had not been upgraded to the indicated version for either the primary or accelerator volume, which is required for that command.; Action: Use the Oracle ASM Configuration Assistant (ASMCA) tool or the SQL ALTER DISKGROUP statement to upgrade the disk group compatibility (COMPATIBLE.ADVM attribute) to the specified version and then re-issue the original command. If the disk group compatibility cannot be upgraded, update the ACFS compatibility using the 'acfsutil compat set' command and then re-issue the original command.
ACFS-01182: An Oracle ASM Dynamic Volume Manager device is not supported in this configuration.: Cause: An attempt to create a file system failed because ADVM is not supported in the single node ACFS configuration.; Action: Assure the ACFS installation and configuration are correct for the single node ACFS configuration.
ACFS-01211: [-k <kernel rpm package file path | installed kernel rpm package name>]: Cause: Informational *Installed kernel rpm package name The installed kernel rpm package can be found by using the command: "rpm -qf /boot/vmlinuz-<kernel_version>" i.e: "rpm -qf /boot/vmlinuz-4.1.12-124.49.3.1.el7uek.x86_64" kernel-uek-4.1.12-124.49.3.1.el7uek.x86_64 *Kernel rpm package file path If providing a kernel rpm package file path, verify the file path exists, has read permissions, and that the rpm provides kABI symbols. To verify rpm kABI symbols use the following command: "rpm -qip --provides <path_to_rpm_file>" A symbol list should be displayed and look like this: kernel(symbolfoo) = 0xvaluefoo ksym(symbolfoo) = 0xvaluefoo; Action: None
ACFS-02001: unable to allocate a buffer: Cause: A request for process virtual memory by mount command failed. This message is accompanied by other message(s) providing details on the error.; Action: Correct the problem indicated by the other message(s). If possible, change options to reduce required memory and/or take steps to increase memory available to the process. Otherwise, report this error to Oracle Support Services.
ACFS-02006: unable to terminate the Oracle Registry connection: Cause: Either the Oracle Registry service was unavailable or the Oracle Registry configuration was incomplete/inaccurate.; Action: Run crs_stat and ocrcheck to verify CSS and the Oracle Registry are working properly. If they are not accessible and the cause is unclear, report this error to Oracle Support Services.
ACFS-02012: Mount of string failed, volume string does not exist. Verify that string exists on this node.: Cause: Could not mount the file system retrieved from the Oracle Registry.; Action: Verify the volume exists on this node and that it is accessible.
ACFS-02014: Mount of string failed. Error number was returned.: Cause: Mount operation failed.; Action: Verify the mount point and volume both exist and are accessible before retrying the mount command.
ACFS-02015: Failed to open mount point string. Verify the mount point exists.: Cause: Mount point could not be opened.; Action: Verify the mount point exists and is accessible before retrying the mount command.
ACFS-02016: Mount point, string, is in use by another file system.: Cause: The file system could not be mounted because the specified directory was already in use by another file system mount point.; Action: Select an unused directory and retry the mount operation.
ACFS-02017: Failed to open volume string. Verify the volume exists.: Cause: The volume could not be opened.; Action: Verify the ASM instance is operational and the volume is enabled and accessible before retrying the mount command.
ACFS-02018: Volume string contains an ACFS file system that is being checked. Allow the file system check to complete.: Cause: The volume contained a file system that was in the process of being checked by the ACFS checker.; Action: Allow the ACFS checker to complete before retrying the mount. If the ACFS checker is not running on this file system and a file system check was previously interrupted, reissue the ACFS checker.
ACFS-02020: options length exceeds number: Cause: An ACFS file system could not be mounted because the length of the options provided exceeded the indicated maximum length.; Action: Retry the mount operation supplying an option list of length less than or equal to the indicated maximum.
ACFS-02021: mount path paired with volume string exceeds number characters: Cause: An ACFS file system could not be mounted because the total length of the mount path plus the volume path exceeded the indicated maximum character length.; Action: Retry the mount operation supplying a total length less than or equal to the indicated maximum.
ACFS-02026: unable to verify the host names passed in are part of the cluster: Cause: Either CSS was unavailable or the CSS configuration was incomplete/inaccurate.; Action: Run crs_stat to verify CSS is working properly.
ACFS-02027: unable to obtain the local CSS node name: Cause: Either CSS was unavailable or the CSS configuration was incomplete/inaccurate.; Action: Run crs_stat to verify CSS is working properly.
ACFS-02028: unable to retrieve the list of volumes associated with string: Cause: An ACFS file system could not be mounted because an attempt to obtain a list of volumes failed. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.
ACFS-02037: File system not created on a string system. Cannot mount.: Cause: An ACFS file system could not be mounted because it was created on a different type of system than the current system.; Action: Retry the mount on a system that matches the indicated system type.
ACFS-02038: File system created on an incompatible system (endianness). Cannot mount.: Cause: An ACFS file sytem could not be mounted because it was created on a computer which has a different endianness than the current system. Little endianness machines (such as the Intel X86 based systems) store the Least Significant Bit in the first byte of an integer value. Big endianness machines (such as Solaris SPARC and AIX Power based systems) store the Most Significant Bit in the first byte of an integer value.; Action: Use a system with the same endianness as the system which created the file system.
ACFS-02039: length of path exceeds number: Cause: An ACFS file system could not be mounted because the length of the path exceeded the indicated maximum length.; Action: Retry the mount command (acfsmountvol.exe on Windows) supplying a path with length less than or equal to the indicated maximum.
ACFS-02040: Path must be a valid directory or drive letter.: Cause: An ACFS file system could not be mounted because the mount point path specified was not a valid mount point.; Action: Retry the operation, specifying a valid ACFS mount point.
ACFS-02041: length of volume name exceeds number: Cause: An ACFS file system could not be mounted because the length of the volume name exceeded the indicated maximum length.; Action: Retry the mount command (acfsmountvol.exe on Windows) supplying a volume name with length less than or equal to the indicated maximum.
ACFS-02043: volume string in use by a non-ACFS file system: Cause: The file system could not be mounted because the specified volume was already in use by another file system.; Action: Select a different volume and retry the mount operation.
ACFS-02044: string does not contain a valid ACFS file system. Verify volume contents using acfschkdsk.exe.: Cause: The specified file system could not be mounted due to inconsistent file system metadata.; Action: Run acfschkdsk.exe as soon as possible to fix the metadata inconsistency, and then retry the acfsmountvol.exe command.
ACFS-02045: string is in use by another non-ADVM volume: Cause: The file system could not be mounted because the specified mount point was already in use by another file system.; Action: Select a different mount point and retry the mount operation.
ACFS-02046: Volume string cannot be mounted. Examine the system event log for possible causes.: Cause: The volume mount failed. This could be caused by an out of space condition if this is the first mount of a file system on a node.; Action: Examine the system event log for more detail.
ACFS-02048: unable to retrieve full path name for path string: Cause: An ACFS file system could not be mounted because an attempt to determine a full path name failed. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.
ACFS-02049: conversion of reparse data Unicode string to ANSI string failed: Cause: An ACFS file system could not be mounted because an attempt to convert a unicode string to an ANSI string failed. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.
ACFS-02050: unable to set in-memory mount information: Cause: Could not communicate with the mounted file system.; Action: Verify the ASM instance is operational and the volume is enabled and accessible before retrying.
ACFS-02051: failed to create symbolic link with path string: Cause: An ACFS file system could not be mounted because an attempt to create a symbolic link failed. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.
ACFS-02052: broadcast of new symbolic link string failed: Cause: An ACFS file system could not be mounted because a system wide broadcast of the symbolic link failed. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.
ACFS-02053: failed to create mount point on directory string: Cause: An ACFS file system could not be mounted because the supplied directory could not be turned into a reparse point. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.
ACFS-02054: unable to retrieve a list of active ACFS file systems: Cause: An attempt to obtain an active list of ACFS file systems failed. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.
ACFS-02080: Volume string failed to mount due to a version mismatch. Volume version number is not supported by the current driver, which supports a maximum volume version of number.: Cause: The volume mount failed because the loaded ACFS driver did not support the volume version of the indicated volume.; Action: Use the 'acfsdriverstate version' command to obtain the version of the loaded ACFS driver and contact Oracle Support Services.
ACFS-02081: Warning: acfschkdsk.exe should be run on volume string at your earliest convenience: Cause: A flag in the superblock indicates that a metadata inconsistency has been found on this volume.; Action: Run acfschkdsk.exe as soon as possible to fix the metadata inconsistency.
ACFS-02082: unable to verify if the host names provided are part of the cluster: Cause: Could not obtain information about the cluster.; Action: Run crs_stat to verify health of CSS.
ACFS-02083: cannot get the local CSS node name: Cause: Could not obtain local CSS node name.; Action: Run crs_stat to verify health of CSS.
ACFS-02088: failed to unlock the volume: Cause: An attempt to dismount the ACFS file system failed because the volume could not be unlocked. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.
ACFS-02089: Info: failed to change the volume signature, but continuing with dismount anyway. No action required: Cause: An attempt to modify the ACFS file system metadata failed during the dismount. The accompanying messages provide detailed failure information.; Action: None
ACFS-02090: unable to retrieve ACFS mount information from CRS: Cause: Failed to retrieve mount information the CRS.; Action: Analyze the error messages that precede this message.
ACFS-02092: Mount of string failed, node string is not a member of the CSS cluster.: Cause: Could not mount the file system retrieved from the Oracle Registry.; Action: Verify the node listed in the entry is a member of the CSS cluster.
ACFS-02119: creating administrative network share for mount point string at share name 'string': Cause: Informational; Action: None
ACFS-02120: administrative network share for mount point string already exists at share name 'string': Cause: Informational; Action: None
ACFS-02121: administrative network share 'string' already exists, but does not share mount point string: Cause: Attempted to create an administrative network share for the specified ACFS mount point, but the required share name was already in use.; Action: Remove the conflicting network share using 'net share share name /delete'. Remount the ACFS file system to retry creating an administrative network share for the mount point.
ACFS-02122: retrieving information for administrative network share 'string' failed: Cause: While creating an administrative network share for the specified ACFS mount point, failed to retrieve information on any network share that might already exist at the required share name. This message is accompanied by other messages providing details on the error.; Action: Correct the error indicated by the accompanying messages. Remount the ACFS file system to retry creating an administrative network share for the mount point.
ACFS-02123: creating administrative network share for mount point string at share name 'string' failed: Cause: Failed to create an administrative network share for the specified ACFS mount point. This message is accompanied by other messages providing details on the error.; Action: Correct the error indicated by the accompanying messages. Remount the ACFS file system to retry creating an administrative network share for the mount point.
ACFS-02124: could not create administrative network share for mount point string at share name 'string': Cause: Failed to create an administrative network share for the specified ACFS mount point. This message is accompanied by other messages providing details on the error.; Action: Correct the error indicated by the accompanying messages.
ACFS-02125: volume 'string' is already in use: Cause: The volume was in use by another file system.; Action: Verify the volume specified.
ACFS-02126: Volume string cannot be mounted.: Cause: The volume mount failed. This message is accompanied by other messages providing details on the error.; Action: Correct the problem indicated by the other messages and retry the mount command.
ACFS-02127: unable to transfer mount data to the ACFS driver: Cause: The mount failed because the transfer of mount data from the mount command to the ACFS driver failed. This message is accompanied by other messages providing details on the error.; Action: Correct the problem identified by the other messages. If the cause is unclear, contact Oracle Support Services.
ACFS-02128: unable to clean up mount data passed to ACFS driver: Cause: The operation to clean up mount data from a temporary location / failed.; Action: None. This state will not have any repercussions and it will be remedied automatically during the next restart.
ACFS-02129: Volume string cannot be mounted. Volume is out of space.: Cause: The volume mount failed because the volume was out of space.; Action: Correct the problem by resizing the ADVM volume and then retry the mount command.
ACFS-02130: Volume string cannot be mounted. Volume version does not match the ACFS driver version.: Cause: The volume mount failed because the loaded ACFS driver does not support the volume version.; Action: Use 'acfsdriverstate' command to determine the state of the ACFS driver and address any issues that are reported. Retry the mount command after the installed driver has been verified.
ACFS-02131: Volume string cannot be mounted. Cluster membership is not established.: Cause: The volume mount failed because the ACFS driver could not communicate with Oracle Clusterware.; Action: Verify the online state of Oracle Clusterware using command 'crsctl check CRS' and address any issues that are reported. Retry the mount command once Oracle Clusterware is fully operational.
ACFS-02132: Volume string cannot be mounted. Insufficient kernel resources to complete the mount.: Cause: The volume mount failed due to insufficient kernel resources.; Action: Reduce the load activity on the system and retry the mount command.
ACFS-02133: Volume string cannot be mounted. Metadata inconsistency found on-disk.: Cause: The volume mount failed due to a metadata inconsistency found in the volume superblock.; Action: Run command 'fsck -t acfs' as soon as possible to fix the metadata inconsistency and then retry the mount command.
ACFS-02135: Volume string failed to mount due to a version mismatch. Volume version number is not supported by the number.number.number.number.number release.: Cause: The volume mount failed because the loaded ACFS driver did not support the volume version of the indicated volume.; Action: Use the 'acfsdriverstate version' command to obtain the version of the loaded ACFS driver and contact Oracle Support Services.
ACFS-02136: Volume string failed to mount due to a version mismatch. Volume version number requires that the loaded ACFS drivers be from the number.number.number.number.number Oracle Database Appliance release.: Cause: The volume mount failed because the loaded ACFS driver did not support the volume version of the indicated volume.; Action: Use the 'acfsdriverstate version' command to obtain the version of the loaded ACFS driver and contact Oracle Support Services.
ACFS-02139: Volume string failed to mount. Insufficient options to complete the mount.: Cause: The volume mount failed because the -o local option was not specified. This option is required for node local volumes.; Action: Retry the command with the addition of the -o local option.
ACFS-02141: Volume string failed to mount. Invalid option combination.: Cause: The volume mount failed because the -o local option was specified with an ADVM volume.; Action: Retry the command without the -o local option.
ACFS-03001: Failed to open string. Verify that string exists.: Cause: The mount point or file could not be opened.; Action: Verify the mount point or file is accessible before retrying.
ACFS-03002: unable to obtain file system information for string: Cause: An attempt to obtain file system information failed. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.
ACFS-03003: Cannot decrease the volume by this amount.: Cause: Requested size exceeded the size of the file system.; Action: Select a size that is smaller than the size of the file system and retry.
ACFS-03004: cannot reduce primary volume size below 200MB: Cause: A size request specified a primary volume size less than the minimum allowed.; Action: Specify a primary volume size of 200MB or more
ACFS-03005: unable to resize string: Cause: An attempt to resize the file system failed. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.
ACFS-03006: smallest size, without loss of data, is: number (numberMB): Cause: A resize request failed because the specified size would result in data loss.; Action: Select a primary volume size that is greater than the size indicated in the message and retry the command.
ACFS-03007: insufficient storage - largest size is: number (numberMB): Cause: A resize request failed because there was not enough storage to accomodate the specified size.; Action: Select a primary volume size that is less than the size indicated in the message and retry the command.
ACFS-03008: The volume could not be resized. The volume expansion limit has been reached.: Cause: The file system's internal storage bitmap has a five extent limit. Growing the file system may fail if it has already been grown four or more times, using up all available storage bitmap extents.; Action: If the file system has been grown four or more times, running the ACFS Fixer may allow future volume expansions.
ACFS-03009: The volume could not be resized at this time. Try again later.: Cause: ADVM or ASM was unable to resize the volume.; Action: Try again later. Check the ASM alert log if the issue persists.
ACFS-03012: length of volume name exceeds number: Cause: The length of the volume name exceeded the indicated maximum length.; Action: Select a volume name with length less than or equal to the indicated maximum length.
ACFS-03013: unable to open string: Cause: Volume could not be opened to remove the file system.; Action: Verify the volume is not mounted on any node in the cluster before retrying.
ACFS-03014: file system not removed: Cause: Failed to remove the ACFS file system from the volume. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.
ACFS-03015: invalid IP address: string: Cause: An attempted 'acfsutil repl' command failed because the indicated IP address specification was invalid.; Action: Retry the command with a valid IP address.
ACFS-03016: ACFS is busy with online fsck. Try again later.: Cause: An attempt to resize a volume was rejected because ACFS was running online fsck.; Action: Retry the resize operation when online fsck is not running.
ACFS-03018: unsupported operation for local file system string: Cause: The requested operation failed because it is not supported by ACFS file systems that are mounted with -o local.; Action: Retry the operation using an ACFS file system that has not been mounted with -o local.
ACFS-03019: Too many options specified: Cause: A command was rejected because too many options were specified.; Action: Retry the command specifying a valid option.
ACFS-03020: Failed to open ACFS file system string. Verify that directory string can be accessed.: Cause: The ACFS file system mount point directory could not be opened.; Action: Verify that the mount point directory is available before retrying the command.
ACFS-03021: The volume snapshot operation failed. Volume snapshots must be managed from the Oracle Control Plane.: Cause: The requested operation failed because the volume was deployed in the Cloud. Volume snapshots of volumes deployed in cloud must be managed from the Oracle Control Plane.; Action: Retry the volume snapshot operation from the Oracle Control Plane.
ACFS-03022: unsupported operation for read-only file system string on read-only volume: Cause: The requested operation failed because the file system was on a read-only volume.; Action: Retry the operation using an ACFS file system that is not on a read-only volume.
ACFS-03023: The volume could not be resized. The volume must be resized from the Oracle Control Plane.: Cause: The requested operation failed because the volume was deployed in the Cloud. Volumes in this state can only be resized from the Oracle Control Plane.; Action: Retry the resize operation from the Oracle Control Plane.
ACFS-03024: ioctl failed: Cause: An attempted utility operation failed because an error occurred in the underlying ioctl operation. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.
ACFS-03025: ioctl call to panic the system failed: Cause: An attempt to execute the 'acfsutil panic' command failed because the ioctl request to panic the system failed. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.
ACFS-03026: cannot freeze or thaw file system string because the file system is marked read-only: Cause: An 'acfsutil freeze' or 'acfsutil thaw' command was rejected because the file system was mounted with the read-only option.; Action: Retry the operation using a writable ACFS file system.
ACFS-03029: product name requires a debug level or context: Cause: An attempt to execute the 'acfsutil log' command failed because the debug level or context required for the specified product was not provided.; Action: Retry the command specifying the debug level or context.
ACFS-03030: unable to get log buffer size: Cause: An attempt to execute the 'acfsutil log' command failed because the ioctl to retrieve log buffer size failed. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.
ACFS-03031: unable to set debug context or level: Cause: An attempt to execute the 'acfsutil log' command failed because the ioctl to set the debug context or level failed. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.
ACFS-03032: unable to retrieve log: Cause: An attempt to execute the 'acfsutil log' command failed because the ioctl to retrieve the log failed. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.
ACFS-03033: unable to open string: Cause: An attempted utility operation failed because the indicated file could not be created and/or opened.; Action: If a file exists by the same name as the file specified, verify that this is a file that can be overwritten.
ACFS-03034: write of log file failed: Cause: An attempt to write to the log file failed. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.
ACFS-03035: unable to retrieve mount entries: Cause: An attempt to obtain an active list of ACFS file systems failed. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.
ACFS-03036: no mounted ACFS file systems: Cause: The system did not have any mounted ACFS file systems.; Action: None
ACFS-03037: not an ACFS file system: Cause: The specified file or directory was not a part of an ACFS file system.; Action: Retry the command with a file or directory that is part of an ACFS file system.
ACFS-03038: unable to retrieve list of volumes associated with string: Cause: An ACFS informational query failed because an attempt to obtain a list of volumes failed. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.
ACFS-03039: ioctl call to unregister the ACFS driver failed: Cause: An ACFS detach command failed because an attempt to unregister the driver failed.; Action: Verify the ACFS driver is loaded and running and retry the command.
ACFS-03040: Volumes are still mounted. All ACFS file systems must be dismounted before the ACFS driver can be unregistered.: Cause: An ACFS detach command failed to unregister the driver because ACFS file systems were still mounted.; Action: Dismount all ACFS file systems and retry the command.
ACFS-03041: unable to unregister ACFS driver: Cause: An ACFS detach command failed because an attempt to unregister the driver failed.; Action: Verify the ACFS driver is loaded and running and retry the command.
ACFS-03043: name of snapshot cannot exceed number bytes: Cause: At attempt to create a snapshot was rejected because the specified snapshot name was too long.; Action: Issue the command again using a shorter snapshot name.
ACFS-03044: Failed to open mount point string. Verify the mount point exists.: Cause: Mount point could not be opened for snapshot operation.; Action: Verify the mount point exists and is accessible before retrying the snap command.
ACFS-03045: string is not a mount point: Cause: The specified directory was not an ACFS mount point.; Action: Retry the command with an ACFS mount point.
ACFS-03046: unable to perform snapshot operation on string: Cause: An attempt to execute the acfsutil snap command failed. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.
ACFS-03048: Snapshot operation could not complete.: Cause: An attempt to execute the acfsutil snap command failed. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.
ACFS-03049: There are too many snapshots for the file system associated with string. Reduce the number of snapshots before proceeding.: Cause: An attempt to execute the acfsutil snap command failed because there were too many snapshots for the file system.; Action: Reduce the number of snapshots for the associated file system using 'acfsutil snap delete' and then retry the acfsutil snap command.
ACFS-03050: Cannot create snapshot string. It already exists.: Cause: An attempt to create a snapshot failed because a snapshot with the indicated name was found to already exist.; Action: Retry the acfsutil snap command specifying a different name.
ACFS-03051: Snapshot string does not exist.: Cause: An attempt to execute the acfsutil snap command failed because no snapshot could be found with the indicated name.; Action: Retry the acfsutil snap command with the correct name.
ACFS-03052: unable to delete snapshot string due to open files: Cause: An attempt to delete a snapshot failed because there were files open in the snapshot.; Action: Use lsof or a similar tool to find the processes with open files. No files can be open in the snapshot for the snapshot delete operation to succeed.
ACFS-03053: Delete of snapshot string succeeded but some disk storage could not be freed. When convenient, run fsck/acfschkdsk to free the storage.: Cause: A snapshot was successfully deleted but some of the disk storage could not be freed.; Action: Run the ACFS Fixer to free the storage.
ACFS-03054: Snapshot string is not a valid snapshot name.: Cause: The acfsutil snap command failed because the indicated name was not a valid snapshot name. Possible reasons include: 1) The snapshot name exceeded the limit of 255 characters. 2) The snapshot name equaled "." or "..". 3) The snapshot name contained "/" (Unix or Linux). 4) The snapshot name contained "" or ":" (Windows). 5) The snapshot name contained an illegal character for NTFS file names (Windows).; Action: Retry the acfsutil snap command specifying a valid snapshot name.
ACFS-03055: Snapshot operation failed due to an error on another node. Check Alert logs on other nodes for more details.: Cause: An attempt to execute the acfsutil snap command failed because of an error on another node in the cluster.; Action: Examine the Alert logs on the other nodes, resolve the indicated problems, and then retry the operation.
ACFS-03089: permission denied: Cause: The command failed because the user did not have the required ASM Administrator privilege.; Action: Retry the command from an account with the required privilege.
ACFS-03090: string is an invalid string number: Cause: The specified argument value was not a valid numeric value.; Action: Review the command usage and retry the command providing valid input.
ACFS-03091: Failed to open string. This may mean the string driver is not loaded/running: Cause: The driver's control device could not be accessed.; Action: Verify the driver is loaded and running.
ACFS-03092: error reading driver tunables: Cause: An attempt to read the tunable parameters from the ACFS driver failed. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.
ACFS-03093: no string tunables for this platform: Cause: Informational.; Action: None
ACFS-03094: invalid value number for tunable parameter string: Cause: The specified tunable parameter value was out of range.; Action: Verify the correct value of the parameter.
ACFS-03095: tunable parameter string not found: Cause: The specified tunable parameter does not exist.; Action: Verify the correctness of the parameter name.
ACFS-03096: error opening configuration file string: Cause: The configuration file cannot be created and/or opened.; Action: If the configuration file exists, verify the file can be opened.
ACFS-03097: error accessing configuration file string: Cause: Seek to the end of the configuration file failed.; Action: If the configuration file exists, verify the file is accessible.
ACFS-03098: error writing to configuration file string: Cause: An attempt to write to the tunable parameters file failed. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.
ACFS-03099: error updating driver tunables: Cause: An attempt to update the kernel version of the tunable parameters failed. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.
ACFS-03105: Cannot create snapshot string. Previous delete of snapshot string is still in progress.: Cause: An attempt to create a snapshot failed because a snapshot with the indicated name is in the process of being deleted.; Action: Retry the acfsutil snap command specifying a different name.
ACFS-03106: Invalid combination of arguments. stringa was previously specified to add an ACFS mount point to Oracle Registry.: Cause: Invalid option combination.; Action: Retry the command with one set of operations.
ACFS-03107: Invalid combination of arguments. stringd was previously specified to remove an ACFS mount point from the Oracle Registry.: Cause: Invalid option combination.; Action: Retry the command with one set of operations.
ACFS-03108: Neither string nor string is an ADVM volume.: Cause: Volume specified was not an ADVM volume.; Action: Retry the command with an ADVM volume.
ACFS-03110: unable to access the Oracle Registry string: Cause: Either the Oracle Registry service was unavailable or the registry configuration was incomplete/inaccurate.; Action: Run ocrcheck to verify the Oracle Registry is working properly. Analyze the appended Oracle Registry service error message.
ACFS-03111: unable to add ACFS mount string within Oracle Registry: Cause: A request to add the indicated device and mountpoint to the Oracle Registry failed. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation. If another registration is using this device or mountpoint, remove the existing registration before retrying the operation.
ACFS-03112: unable to remove mount point string from Oracle Registry: Cause: A request to delete the indicated device or mountpoint from the Oracle Registry failed. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.
ACFS-03114: unable to allocate a buffer: Cause: A request for process virtual memory by acfsutil registry failed This message is accompanied by other message(s) providing details on the error.; Action: Correct the problem indicated by the other message(s). If possible, change options to reduce required memory and/or take steps to increase memory available to the process. Otherwise, report this error to Oracle Support Services.
ACFS-03115: an error occurred while attempting to disconnect from Oracle Registry: Cause: Either the Oracle Registry service was unavailable or the Oracle Registry configuration was incomplete/inaccurate.; Action: Run ocrcheck to verify the Oracle Registry service is working properly. If the cause of the problem is unclear, contact Oracle Support Services.
ACFS-03117: unable to verify if the hostnames provided are part of the cluster: Cause: Could not obtain information about the cluster.; Action: Run crs_stat to verify health of CSS.
ACFS-03118: cannot obtain the node number of host string via CSS or the Oracle Registry: Cause: Could not determine the node number for the specified host.; Action: Verify that the specified host is a member of this cluster.
ACFS-03119: Incorrect data format in file 'number'.: Cause: The file data was not in the expected format.; Action: Contact Oracle Support Services.
ACFS-03120: Note: Reported snapshot space usage is inaccurate.: Cause: The snapshot storage calculated was not expected.; Action: No action is required. To get a more accurate count, dismount the file system on all nodes and run fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ACFS-03122: failed to create Oracle Registry ACFS key string string: Cause: Failed to create ACFS key(s) SYSTEM.ACFS and/or SYSTEM.ACFS.Mounts in the Oracle Registry.; Action: Run ocrcheck to verify the Oracle Registry service is working properly. Verify acfsutil is executed with operating system administrator privileges.
ACFS-03123: failed to create Oracle Registry ACFS key string because it already exists: Cause: The Oracle Registry ACFS key already exists.; Action: Run ocrcheck to verify the Oracle Registry service is working properly.
ACFS-03124: failed to create Oracle Registry ACFS subkey because it already exists: Cause: The Oracle Registry mounts subkey already exists.; Action: Run ocrcheck to verify the Oracle Registry service is working properly. If the ACFS mount entry is in an inconsistent state delete it, then re-add it using acfsutil with the registry option. If the problem persists, contact Oracle Support Services.
ACFS-03125: error retrieving the volume using Oracle Registry key: string: Cause: Could not retrieve volume information from mount entry in the Oracle Registry.; Action: Run ocrcheck to verify the Oracle Registry is working properly.
ACFS-03126: error retrieving the mount point using Oracle Registry key: string: Cause: Could not retrieve mount point information from mount entry in the Oracle Registry.; Action: Run ocrcheck to verify the Oracle Registry is working properly.
ACFS-03127: error retrieving the mount options using Oracle Registry key: string: Cause: Could not retrieve mount options from mount entry in the Oracle Registry.; Action: Run ocrcheck to verify the Oracle Registry is working properly.
ACFS-03128: error retrieving the version using Oracle Registry key: string: Cause: Could not retrieve the version for mount entry in the Oracle Registry.; Action: Run ocrcheck to verify the Oracle Registry is working properly.
ACFS-03129: error retrieving the nodes list using Oracle Registry key: string: Cause: Could not retrieve the nodes list for mount entry in the Oracle Registry.; Action: Run ocrcheck to verify the Oracle Registry is working properly.
ACFS-03130: Resize request is greater than allowed maximum for ADVM volume.: Cause: An attempt to resize an ADVM volume failed because the size requested was larger than the maximum allowed ADVM volume size.; Action: Check the instance alert log for the maximum size of the ADVM volume and retry the resize operation, specifying a smaller volume size.
ACFS-03132: mount point string already exists in the Oracle Registry as:: Cause: The indicated mount point was in use in the Oracle Registry.; Action: If the new device is meant to replace an old device on this mount point, unmount the old device and then retry the command.
ACFS-03133: The Oracle Registry returned the following error while attempting to access the security attributes of key string: \n string: Cause: Could not access the security information of Oracle Registry. This message is accompanied by other message(s) from the Registry providing details on the error.; Action: Correct the problem identified by the other message(s). If the cause is unclear, contact Oracle Support Services.
ACFS-03134: An error occurred while accessing Oracle Registry for a delete mount point operation. string: Cause: Could not retrieve data from the Oracle Registry. This message is accompanied by other message(s) providing details on the error.; Action: Correct the problem indicated by the other message(s). If the cause of the problem is unclear, contact Oracle Support Services.
ACFS-03135: unable to locate mount point string in Cluster Ready Services: Cause: An attempt to access the ACFS mount point failed because the mount point information could not be retrieved from CRS.; Action: Verify the mount point is registered with CRS using the 'acfsutil registry device' commands.
ACFS-03136: unable to locate volume string in Cluster Ready Services: Cause: An attempt to access the ASM volume failed because the volume information could not be retrieved from CRS.; Action: Verify the volume is registered with CRS using the 'acfsutil registry device' commands.
ACFS-03137: Multiple entries exist for the mount point string. Rerun the command with the volume name.: Cause: Could not locate unique entry for mount point in the Oracle Registry.; Action: Retry acfsutil registry with volume name.
ACFS-03138: failed to create and set Oracle Registry ACFS mount info key string: Cause: Could not create and set a mount info key in the Oracle Registry.; Action: Run ocrcheck to verify the Oracle Registry is working properly.
ACFS-03139: error retrieving the disk group name using Oracle Registry key: string: Cause: Could not retrieve the disk group name from the mount entry in the Oracle Registry.; Action: Run ocrcheck to verify the Oracle Registry is working properly.
ACFS-03140: error retrieving the volume name using Oracle Registry key: string: Cause: Could not retrieve the volume name from the mount entry in the Oracle Registry.; Action: Run ocrcheck to verify the Oracle Registry is working properly.
ACFS-03141: unable to open device string: Cause: The device could not be opened.; Action: Check the diskgroup is mounted and the specified volume is enabled.
ACFS-03142: Failed to retrieve the diskgroup and volume name for device string. See the attached error.: Cause: Possible internal error.; Action: Check the attached error. If not serviceable, contact Oracle.
ACFS-03143: The specified mount point does not exist and therefore cannot be deleted.: Cause: The Oracle Registry has not been configured for ACFS or the specified mount point does not exist.; Action: Run "acfsutil registry" to list out the available ACFS mount points.
ACFS-03145: unable to remove ACFS volume string from Oracle Registry: Cause: Could not remove volume from Oracle Registry.; Action: Verify the volume exists in the Oracle Registry using the acfsutil registry command.
ACFS-03146: Warning: The ACFS mount point group ownership cannot be re-initialized in the Oracle Registry. The registry is initialized from the ACFS control device on first use, and may have changed ownership since then. Current Key Ownership: string: Cause: An attempt was made to re-initialize the ACFS mount point group ownership in the Oracle Registry. This may be because the ACFS control device /dev/ofsctl or /dev/acfsctl has changed owners.; Action: Re-initializing the ACFS mount point group ownership in the Oracle Registry is not supported.
ACFS-03147: invalid ACFS file identifier provided: Cause: The ACFS file identifier provided by the user had an illegal value.; Action: Re-enter a number other than 0 or -1.
ACFS-03148: ioctl call to obtain pathname associated with file id number failed: Cause: An internal ioctl operation to map from an ACFS file identifier to a pathname failed. This message is accompanied by other message(s) providing details on the error.; Action: Correct the problem indicated by the other message(s). If the cause of the problem is unclear, contact Oracle Support Services.
ACFS-03149: constructed path name is longer than system limit of number characters: Cause: The length of the pathname being constructed has exceeded the system limit of %d characters. This may be due to changes in the file system namespace while the command is running.; Action: Try the command again. If the problem persists, contact Oracle Support Services.
ACFS-03151: The ACFS file identifier provided is not associated with a user file or directory.: Cause: The ACFS file identifier, although valid, was not for a user file or directory.; Action: None. There is no pathname associated with this ACFS file identifier.
ACFS-03152: The ACFS file identifier provided is invalid for the mountpoint specified.: Cause: The ACFS file identifier was not a valid identifier for the mountpoint specified.; Action: Verify that the correct ACFS file identifier and mountpoint were specified.
ACFS-03153: The file system name space has changed and a pathname cannot be obtained.: Cause: The ACFS file identifier was valid, but could not be used to obtain a full file pathname.; Action: Verify that the correct ACFS file identifier and mountpoint were specified.
ACFS-03154: Failed to determine the full pathname. Too many directory levels.: Cause: acfsutil has received information from the operating system that it could not process fully.; Action: Report this error to Oracle Support Services.
ACFS-03157: unsupported file type for string, not a mount point: Cause: An invalid entry was passed on the command line.; Action: The acfsutil info acfs command requires that the input be a mount point.
ACFS-03158: unsupported file type for string, not a mount point or a file: Cause: An invalid entry was passed on the command line.; Action: The acfsutil size command requires that the input be a mount point or a file.
ACFS-03161: Device : string : Mount Point : string already exists in the Oracle Registry: Cause: This entry has already been added to the Oracle Registry.; Action: None
ACFS-03162: Warning: The file system was resized, but an error occurred while resizing the underlying volume. File system size now number MB, volume size number MB.: Cause: An error occurred during volume resize.; Action: Reissue the resize command.
ACFS-03165: Unable to add the file system on device string to the ACFS registry. It is currently managed by CRS.: Cause: The file system is currently managed by CRS and a file system cannot be managed by both CRS and the ACFS registry.; Action: Remove the file system resource from CRS or continue to use CRS to manage the file system.
ACFS-03166: Unable to add a STOP_DEPENDENCY to the ACFS registry for device string.: Cause: The ACFS registry resource could not be updated.; Action: Verify the ACFS registry state ('crsctl stat res ora.registry.acfs -p')
ACFS-03167: Unable to remove the STOP_DEPENDENCY for device string from the ACFS registry.: Cause: The ACFS registry resource could not be updated.; Action: Verify the ACFS registry state ('crsctl stat res ora.registry.acfs -p')
ACFS-03168: Internal error: string number: Cause: An Oracle internal error.; Action: Contact Oracle Support Services.
ACFS-03169: Unable to set log file size.: Cause: The ACFS driver was unable to set the log file size.; Action: Check the log file to see the reason of failure.
ACFS-03170: Minimum log file size is number.: Cause: The ACFS driver was unable to set the log file size.; Action: Log file size has to be bigger than or equal to the minimum size.
ACFS-03171: insufficient contiguous free ASM Diskgroup space: Cause: An attempt to resize an ADVM volume failed because ASM did not have enough contiguous free diskgroup storage. This could have been a transient condition if ASM rebalance was running, otherwise the ASM alert logs may provide detailed failure indications.; Action: Check the ASM alert logs, address ASM issues if any, and retry the resize. If ASM rebalance is running it may release sufficient space by completion to allow a retry of the resize to succeed. Monitor V$ASM_DISK.FREE_MB view, if desired, to track free storage and retry the resize if sufficient storage becomes available. Otherwise, retry the resize after using ASM commands to increase the free space or retry, specifying a smaller quantity.
ACFS-03172: ADVM is busy with Mirror recovery. Try again later.: Cause: ADVM could not resize the volume because it is recovering the mirrored volumes.; Action: Try again later. The system console log will contain mirror recovery started and completed messages. For example: [Oracle ADVM] Mirror recovery for volume asm/volume-name started. [Oracle ADVM] Mirror recovery for volume asm/volume-name completed.
ACFS-03173: ADVM or ASM is unable to resize the volume. Check the ASM alert log.: Cause: ADVM or ASM is unable to resize the volume.; Action: Check the ASM alert log.
ACFS-03174: The Oracle ASM Dynamic Volume Manager (Oracle ADVM) compatibility attribute for the disk group is less than 11.2.0.3.0.: Cause: The creation of a read/write snapshot was rejected because the ADVM disk group compatibility had not been upgraded to 11.2.0.3.0 or higher, which is required for that command.; Action: Use the Oracle ASM Configuration Assistant (ASMCA) tool or the SQL ALTER DISKGROUP statement to upgrade the disk group compatibility (COMPATIBLE.ADVM attribute) to the specified version and then re-issue the original command. If the disk group compatibility cannot be upgraded, update the ACFS compatibility using the 'acfsutil compat set' command and then re-issue the original command.
ACFS-03177: maximum log file size cannot exceed number MB: Cause: The ACFS driver was unable to set the log file size.; Action: Retry the command with a log file size that is smaller than the maximum size.
ACFS-03178: unable to delete snapshot string while cluster is in rolling migration: Cause: The cluster was in rolling migration. Snapshot deletions are not allowed during rolling migration.; Action: Complete the rolling migration and then delete the snapshot.
ACFS-03179: unable to create snapshot 'string' while cluster is in rolling migration: Cause: The cluster was in rolling migration. Snapshot creations are not allowed during rolling migration.; Action: Complete the rolling migration and then create the snapshot.
ACFS-03180: Unable to obtain ASM volume device information for 'string': Cause: The operation for retrieval of ASM volume device information failed. This message is accompanied by other message(s) providing details on the error.; Action: Correct the problem indicated by the other message(s). If the solution is not clear, contact Oracle Support Services.
ACFS-03182: Device name 'string' does not exist.: Cause: An attempt to execute the 'advmutil canonical' command failed because no device could be found with the indicated name.; Action: Verify the correctness of the device name and retry the command.
ACFS-03185: Unable to obtain ASM volume extent information for string: Cause: The operation for retrieval of ASM volume extent information failed. This message is accompanied by other message(s) providing details on the error.; Action: Correct the problem indicated by the other message(s). If the solution is not clear, contact Oracle Support Services.
ACFS-03186: Supplied ACFS file offset value exceeded the maximum of the file and allocation sizes of number.: Cause: The supplied file offset value in bytes exceeded both the file size and allocation size.; Action: Specify a file offset within the actual or allocated size of the file. Use 'acfsutil info file filename' to see those values.
ACFS-03187: Extent number (mirror number) is not in use.: Cause: Informational; Action: None
ACFS-03190: Neither string nor string is a supported volume type.: Cause: An attempt to register the filesystem was unsuccessful because the filesystem was not on an ADVM or EXC volume.; Action: Retry the command with a filesystem that is using an ADVM or EDV volume.
ACFS-03191: string is not a supported volume type.: Cause: Volume specified was not an ADVM or EDV volume.; Action: Retry the command specifying an ADVM or EDV volume.
ACFS-03197: unable to delete snapshot string while it is configured for use by ACFS replication: Cause: An attempt to delete a snapshot was rejected because it was configured for use by ACFS replication.; Action: To force deletion of the snapshot, re-try the command with the -R option.
ACFS-03198: unable to delete snapshot string as a component of ACFS replication: Cause: An attempt to delete a snapshot was rejected because it was not; Action: To delete the snapshot, re-try the command without the -R option.
ACFS-03199: unable to convert snapshot string because it is replication-specific: Cause: An attempt was made to convert a replication-specific snapshot while replication was running.; Action: Terminate replication and retry the command.
ACFS-03203: Invalid snap command.: Cause: An invalid entry was passed on the command line.; Action: Use a valid 'acfsutil snap' command combination. Valid commands are 'acfsutil snap create', 'acfsutil snap delete', and 'acfsutil snap info'
ACFS-03204: Snapshot 'string' is already read-only.: Cause: A request was made to convert a snapshot to be read-only but the snapshot was already read-only.; Action: None
ACFS-03205: Snapshot 'string' is already read-write.: Cause: A request was made to convert a snapshot to be read-write but the snapshot was already read-write.; Action: None
ACFS-03206: The ADVM compatibility attribute for the diskgroup was below the required version (string) for the 'acfsutil snap convert' command.: Cause: The 'acfsutil snap convert' command was rejected because the ADVM disk group compatibility had not been upgraded to the indicated version, which is required for that command.; Action: Use the Oracle ASM Configuration Assistant (ASMCA) tool or the SQL ALTER DISKGROUP statement to upgrade the disk group compatibility (COMPATIBLE.ADVM attribute) to the specified version and then re-issue the original command. If the disk group compatibility cannot be upgraded, update the ACFS compatibility using the 'acfsutil compat set' command and then re-issue the original command.
ACFS-03207: invalid combination of options: Cause: The 'acfsutil snap convert' command was passed an invalid option combination which included both the -r and -w options.; Action: Remove either the -r or -w option from the 'acfsutil snap convert' command.
ACFS-03208: The /r option is not supported on this operating system: Cause: The 'acfsutil snap convert /r' option was specified. This functionality requires a minimum operating system version of Windows Server 2008 R2.; Action: Upgrade operating system to Windows Server 2008 R2 or use the 'acfsutil snap create' command to create a read-only snapshot.
ACFS-03212: There are too many snapshots for the file system associated with string. Only number are allowed. Reduce the number of snapshots before proceeding.: Cause: An attempt to create more than the maximum allowed number of active snapshots was rejected.; Action: Delete a snapshot before creating a new one.
ACFS-03213: Creation of a snapshot failed due to presence of snapshots that prevent this functionality.: Cause: A snapshot creation which specified a parent snapshot was not processed because of compatibility issues with existing snapshots. Possible causes include: 1) Snapshots of the file system were found that were created before ADVM compatibility attribute was set to 12.1. 2) Snapshots of the file system were found that were created after ADVM compatibility was set to 12.1 but while 11.2 snapshots existed.; Action: Delete all snapshots associated with the file system and retry the command.
ACFS-03214: The Oracle ASM Dynamic Volume Manager (Oracle ADVM) compatibility attribute for the disk group is less than 12.1.: Cause: The creation of a snapshot with a parent snapshot was rejected because the ADVM disk group compatibility had not been upgraded to version 12.1 or higher, which is required for that command.; Action: Use the Oracle ASM Configuration Assistant (ASMCA) tool or the SQL ALTER DISKGROUP statement to upgrade the disk group compatibility (COMPATIBLE.ADVM attribute) to the specified version and then re-issue the original command. If the disk group compatibility cannot be upgraded, update the ACFS compatibility using the 'acfsutil compat set' command and then re-issue the original command.
ACFS-03216: The ADVM compatibility attribute for the diskgroup was below the required version (string) for unlimited volume expansions.: Cause: A request to resize the ACFS file system failed because the volume expansion limit was reached. This limit was in effect because the ADVM compatibility attribute associated with the disk group had not been upgraded to the indicated version, which is required for that command.; Action: Use the Oracle ASM Configuration Assistant (ASMCA) tool or the SQL ALTER DISKGROUP statement to upgrade the disk group compatibility (COMPATIBLE.ADVM attribute) to the specified version and then re-issue the original command. If the disk group compatibility cannot be upgraded, update the ACFS compatibility using the 'acfsutil compat set' command and then re-issue the original command.
ACFS-03228: unable to retrieve metadata statistics for primary volume associated with mount point string: Cause: An internal ioctl operation to retrieve ACFS metadata statistics failed. This message is accompanied by other messages providing details on the error.; Action: Correct the problem identified by the other messages. If the cause is unclear, contact Oracle Support Services.
ACFS-03229: unable to retrieve metadata statistics for accelerator volume associated with mount point string: Cause: An internal ioctl operation to retrieve ACFS metadata statistics failed. This message is accompanied by other messages providing details on the error.; Action: Correct the problem identified by the other messages. If the cause is unclear, contact Oracle Support Services.
ACFS-03243: failed to write Hang Manager entries to the kernel in-memory and persistent logs: Cause: An internal ioctl operation to write Hang Manager data to the in-memory and persistent logs failed. This message is accompanied by other messages providing details on the error.; Action: Correct the problem identified by the other messages. If the cause is unclear, contact Oracle Support Services.
ACFS-03244: The specified numeric value string is outside the valid range.: Cause: The indicated numeric argument was rejected because it was too long to be converted to a 64-bit internal representation.; Action: Retry the command specifying a value between -2^63+1 and 2^63-1. 03245 is obsolete - see 3249.
ACFS-03255: accelerator volume not replaced: Cause: An attempt to replace the accelerator volume failed. This message is accompanied by other messages providing details on the error.; Action: Correct the problems indicated by the other messages. If the cause of the problems is unclear, contact Oracle Support Services.
ACFS-03256: primary volume has no accelerator volume to replace: Cause: An attempt to replace the accelerator volume was rejected because the specified volume did not have an accelerator volume associated with it.; Action: Ensure that the primary volume has an associated accelerator volume before attempting replacement.
ACFS-03257: the specified primary volume is an accelerator volume. Cannot proceed.: Cause: An attempt to replace an accelerator volume was rejected because the volume specified as the primary volume was not a primary volume.; Action: Ensure that the specified volume is a primary volume with an associated accelerator volume before attempting replacement.
ACFS-03258: the specified replacement accelerator volume must be at least as large as the accelerator volume it is to replace.: Cause: An attempt to replace the accelerator volume was rejected because the specified replacement volume was smaller than the current accelerator volume.; Action: Retry the 'acfsutil accel replace' command specifying a volume at least as large as the volume to be replaced.
ACFS-03263: Volume signature indicates that an accelerator operation is in progress.: Cause: An attempt to perform a filesystem check could not be completed because metadata showed that an accelerator operation was either in progress or incomplete on the specified volume.; Action: Ensure that an accelerator operation is not being run on another node or by another user before attempting to check this file system again. If an accelerator change operation had been started and then aborted, use 'fsck -f' to repair the volume. If the operation was interrupted, run it again with the same arguments.
ACFS-03264: 'acfsutil accel replace' failed due to a version mismatch. The Oracle ASM Dynamic Volume Manager (Oracle ADVM) compatibility attribute for the disk group is less than number.number.number.number.number.: Cause: An attempt to replace an accelerator volume was rejected because the ADVM disk group compatibility had not been upgraded to the release specified in the message or higher, which is required for the operation.; Action: Use the Oracle ASM Configuration Assistant (ASMCA) tool or the SQL ALTER DISKGROUP statement to upgrade the disk group compatibility (COMPATIBLE.ADVM attribute) to the specified version and then re-issue the original command. If the disk group compatibility cannot be upgraded, update the ACFS compatibility using the 'acfsutil compat set' command and then re-issue the original command.
ACFS-03265: 'acfsutil accel replace' interrupted. Ensure primary volume is accessible then run 'acfsutil accel replace' with the same arguments again to complete the operation.: Cause: An event or condition interrupted the execution of the 'acfsutil accel replace' command. This message is accompanied by other messages providing details on the error.; Action: Address errors in the accompanying error messages and run 'acfsutil accel replace' with the same arguments on to render the primary volume mountable. The accelerator replace operation should then be complete.
ACFS-03266: The specified new accelerator volume is already the accelerator volume that corresponds to the specified primary volume.: Cause: The specified new accelerator volume was the same as the accelerator volume it was to replace. This state may occur because another operation instructed 'acfsutil accel replace' be run again with the same arguments to recover from or complete a failed accelerator replacement. This message will also be seen as a result of accidentally rerunning the same command.; Action: The issued 'acfsutil accel replace' command should have finished an incomplete accelerator replace operation if one existed. Otherwise the file system should remain unchanged. No further action is necessary.
ACFS-03267: Volume signature indicates that an accelerator operation is in progress.: Cause: An attempt to format a volume could not be completed because an accelerator operation was either in progress or incomplete on the specified volume.; Action: Ensure that an accelerator operation is not being run on another node or by another user. If an accelerator operation had been started and then aborted, use 'fsck.acfs -f' to repair the primary volume. If an accelerator operation was interrupted, reissue the command with the same arguments to complete it.
ACFS-03268: Cannot use volume string. It contains an existing ACFS file system or is being used as an accelerator.: Cause: An attempt to replace a file system's accelerator volume was rejected because the on-disk metadata of the indicated volume showed that a valid ACFS file system was located on the volume or that it was an existing accelerator.; Action: Reissue the request specifying a different volume not containing an existing file system or being used as an accelerator. To use the indicated volume, evidence of its prior use containing a file system or as an accelerator volume must first be removed.
ACFS-03270: New accelerator volume sector size (number) must match existing accelerator volume sector size (number).: Cause: An attempt to execute 'acfsutil accel replace' was rejected because the logical sector sizes of the existing and specified new accelerator volumes were different, as shown. The sector size of the accelerator volume must remain the same as the sector size of the associated primary volume.; Action: Select a device that has the same logical sector size as the existing accelerator volume and retry the operation.
ACFS-03271: The Oracle ASM Dynamic Volume Manager (Oracle ADVM) compatibility attribute for the diskgroup was below the required version (string) for the 'acfsutil snap quota' command.: Cause: The 'acfsutil snap quota' command was rejected because the ADVM disk group compatibility had not been upgraded to the indicated version, which is required for that command.; Action: Use the Oracle ASM Configuration Assistant (ASMCA) tool or the SQL ALTER DISKGROUP statement to upgrade the disk group compatibility (COMPATIBLE.ADVM attribute) to the specified version and then re-issue the original command. If the disk group compatibility cannot be upgraded, update the ACFS compatibility using the 'acfsutil compat set' command and then re-issue the original command.
ACFS-03272: The specified primary volume string does not appear to contain an ACFS file system.: Cause: An attempt to replace a primary volume's accelerator volume failed because the on-disk metadata of the indicated primary volume did not show that a valid ACFS file system was located on the volume.; Action: Reissue the request specifying a different primary volume containing an existing ACFS file system that has an accompanying accelerator volume.
ACFS-03273: Volume signature indicates that an accelerator operation is in progress.: Cause: An attempt to mount a file system could not be completed because an accelerator operation was either in progress or incomplete on the specified volume.; Action: Ensure that an accelerator operation is not being run on another node or by another user before retrying the mount operation. If an accelerator operation had been started and then aborted, use 'fsck.acfs -f' to repair the primary volume. If an accelerator operation was interrupted, reissue the command with the same arguments to complete it.
ACFS-03274: Snap quota can not be enabled for this snapshot.: Cause: The command 'acfsutil snap quota' was rejected because the snapshot was created from a file system whose compatibility level was less than 12.2.; Action: Use the 'acfsutil snap quota' to set quota for a snapshot created from a file system whose compatibility level is at least 12.2.0.0.0
ACFS-03275: Updating CRS dependencies for resource 'string'.: Cause: Informational.; Action: None
ACFS-03276: CRS dependencies were updated successfully.: Cause: Informational.; Action: None
ACFS-03277: failed to update CRS resource: Cause: An attempt to replace the accelerator failed because an error occurred while updating a resource. The accompanying messages from CRS provide detailed failure information.; Action: Examine the accompanying CRS error messages, address issues reported and retry.
ACFS-03278: restarting replace operation: Cause: The metadata of the supplied volumes indicated that a previous invocation of 'acfsutil accel replace' with the same arguments as this one was interrupted before completion. This invocation attempted to complete the replace operation.; Action: The issued 'acfsutil accel replace' command attempted to complete the specified accelerator replace operation. No further action is necessary if this message is not accompanied by failure messages.
ACFS-03279: The file system on the specified primary volume string is either in use or has been removed.: Cause: An attempt to replace a primary volume's accelerator volume failed because the on-disk metadata of the indicated primary volume showed that the file system was either in use or had been removed.; Action: Reissue the request specifying a different primary volume that contains a valid ACFS file system configured with an accompanying accelerator volume. Issue 'fsck' on the primary volume for more detail on its current state.
ACFS-03280: failed to increase log size and change log level of in-memory log on all nodes: Cause: An attempt to increase log size and change log level on all nodes of the cluster failed because an error occurred while sending the request to every node.; Action: Retry the operation. Alternatively, issue the following commands on each cluster node: 'acfsutil log -r 500M; acfsutil log -p ofs -l 5' run the workload that caused the problem wait for two or three minutes 'acfsutil log -r 10M; acfsutil log -p ofs -l 2'
ACFS-03281: failed to reset log size and log level of in-memory log on all nodes: Cause: An attempt to reset log size and change log level on all nodes of the cluster failed because an error occurred while sending the request to every node.; Action: Retry the operation. Alternatively, issue the command on each cluster node: 'acfsutil log -r 10M; acfsutil log -p ofs -l 2'
ACFS-03283: invalid combination of -o and -f options: Cause: The 'acfsutil log' command was issued with both the -f and -o options. This is a conflict, because the log file names are pre-specified for -o and may not be specified using -f.; Action: Re-issue the 'acfsutil log' command with only the desired option. With -o, the log files will be generated in the persistent log directory in the form yymmddhhmmss.log. With -f the specified name will be used.
ACFS-03284: invalid combination of -o and -n, -T, -c, -s, -q options: Cause: The 'acfsutil log -o' command is incompatible with other options included in the commmand line. The -o option can not be combined with the -n, -T, -c, -s, or -q options.; Action: Re-issue the 'acfsutil log' command with only the desired option. With -o, only log file size, log level and product name may be specified.
ACFS-03286: failed to find volume resource for device string: Cause: An attempt to replace an accelerator volume with the command 'acfsutil accel replace' failed because the volume resource for the indicated device was not found.; Action: List the CRS resources to verify that the volume resource for the indicated device exists and is online and retry.
ACFS-03287: unable to find old accelerator volume resource name: Cause: An attempt to replace an accelerator volume with the command 'acfsutil accel replace' failed because the old accelerator resource could not be found because the file system resource dependencies were not correct.; Action: Examine the file system resource attributes, ensure that the primary and accelerator resources are correct and retry.
ACFS-03288: CRS dependencies already had the requested values.: Cause: A request to update the dependencies for a file system resource was ignored because the dependencies already had the requested values.; Action: No action necessary.
ACFS-03290: The Oracle ADVM compatibility level for the disk group is less than the required version 18.0.0.0.0 for snap link.: Cause: The 'acfsutil snap link' command was rejected because the ADVM disk group compatibility had not been upgraded to the indicated version, which is required for that command.; Action: Use the ASMCA tool or the SQL ALTER DISKGROUP statement to upgrade the disk group compatibility (COMPATIBLE.ADVM attribute) to the specified version and then re-issue the original 'acfsutil snap link' command. If the disk group compatibility cannot be upgraded, update the ACFS compatibility level using the 'acfsutil compat set' command and then re-issue the original 'acfsutil snap link' command.
ACFS-03291: Only one snaphshot link can be created for this snapshot.: Cause: The command 'acfsutil snap link' was rejected because the snapshot already had a snapshot link.; Action: Use the 'acfsutil snap info' command to see the existing snapshot link for this snapshot. Before creating a new snapshot link, use the 'acfsutil snap link -d' command to delete the existing link for the snapshot.
ACFS-03294: Insufficient privileges to perform command. Resource Administrator access is required.: Cause: An attempt to execute an acfsutil command was rejected because the caller did not have sufficient privileges.; Action: Retry the command while logged in as a user with resource ACL access.
ACFS-03295: Invalid freeze or thaw command.: Cause: An 'acfsutil freeze' or 'acfsutil thaw' command was rejected because an invalid option was specified. The 'acfsutil thaw' command does not accept any options. The 'acfsutil freeze' command accepts the '-f' option only.; Action: Retry the command, specifying only valid options.
ACFS-03296: cannot freeze or thaw file system string because the Grid Infrastructure has not been upgraded to string: Cause: An 'acfsutil freeze' or 'acfsutil thaw' command was rejected because the Grid Infrastructure had not been upgraded to the indicated version.; Action: Ensure that the Grid Infrastructure has completed an upgrade to the indicated version or higher and then re-issue the command.
ACFS-03297: unable to freeze file system string: Cause: The file system could not be frozen. The accompanying messages provide detailed failure information.; Action: Read the accompanying messages, correct the issues identified there, and then retry the operation.
ACFS-03298: unable to thaw file system string: Cause: The file system could not be thawed from a frozen state. The accompanying messages provide detailed failure information.; Action: Read the accompanying messages, correct the issues identified there, and then retry the operation.
ACFS-03299: cannot freeze or thaw file system string because the cluster is in rolling migration: Cause: An 'acfsutil freeze' or 'acfsutil thaw' command was rejected because the cluster was in rolling migration. Freezing or thawing a file system during rolling migration was not supported.; Action: Complete the rolling migration and then retry the command.
ACFS-03300: unable to set tag name on file string: Cause: The ACFS driver was unable to complete the request.; Action: Verify memory or storage resources are sufficient.
ACFS-03301: unable to unset tag name on file string: Cause: The ACFS driver was unable to complete the request.; Action: Verify memory or storage resources are sufficient.
ACFS-03302: tag name syntax invalid or length too long: Cause: Tag name contains invalid characters or has too many characters.; Action: Change tag name to use valid characters or shorten the tag name.
ACFS-03303: invalid combination of arguments: Cause: The acfsutil tag info -t or -r arguments work only on file pathnames.; Action: Remove the -t or -r arguments from the ofsutil tag info command.
ACFS-03304: Unable to open mount point string. Verify that the mount point exists.: Cause: Mount point cannot be opened to display tag name information.; Action: Verify that the mount point exists and is accessible before retrying the tag info command.
ACFS-03305: unable to retrieve all tag names for string: Cause: Unable to return the full list of tag names.; Action: Verify there is sufficient memory resources available.
ACFS-03306: tag name does not exist in file string: Cause: Cannot unset a tag name on a file that does not exist.; Action: Verify the tag name to unset is correct.
ACFS-03308: The ADVM compatibility attribute for the diskgroup must be set to version 11.2.0.2.0 to allow the acfsutil repl and tag commands.: Cause: The acfsutil command was rejected because the ADVM disk group compatibility had not been upgraded to 11.2.0.2.0 or higher, which is required for that command.; Action: Use the Oracle ASM Configuration Assistant (ASMCA) tool or the SQL ALTER DISKGROUP statement to upgrade the disk group compatibility (COMPATIBLE.ADVM attribute) to the specified version and then re-issue the original command. If the disk group compatibility cannot be upgraded, update the ACFS compatibility using the 'acfsutil compat set' command and then re-issue the original command.
ACFS-03309: path name string does not resolve to an ACFS file system: Cause: A path name supplied on an 'acfsutil tag' command did not resolve to an ACFS file system.; Action: Remove the non-ACFS path name from the 'acfsutil tag' command.
ACFS-03310: amount of change since mount: number MB: Cause: Informational; Action: None
ACFS-03313: unable to collect ACFS statistics for mount point string: Cause: 'acfsutil info fs -s' was unable to communicate with the ACFS driver.; Action: Verify that the file system is online and that the ADVM/ACFS drivers are loaded and running.
ACFS-03314: interval cannot exceed number seconds: Cause: Statistics interval exceeded maximum number of seconds per interval.; Action: Select an interval that is less than or equal to 2592000 seconds and retry "acfsutil info fs -s".
ACFS-03315: count cannot exceed number: Cause: Number of statistics intervals exceeded maximum number allowed.; Action: Select a total count that is less than or equal to 2^63-1 and retry "acfsutil info fs -s".
ACFS-03316: interval must be a positive integer: Cause: A zero or negative integer was provided.; Action: Provide a positive integer for the statistics interval.
ACFS-03317: unable to set tag on file "string" because its tag name storage is full: Cause: The limit of the file's tag name storage has been reached.; Action: Remove any unused tags on this file and try the command again.
ACFS-03318: unable to set tag name "string" because this name is reserved: Cause: The tag name specified is reserved.; Action: Choose another tag name which is not reserved.
ACFS-03319: Set tag on file: string: Cause: Informational; Action: None
ACFS-03320: Removing tag(s) on file: string: Cause: Informational; Action: None
ACFS-03321: The ADVM compatibility attribute for the diskgroup is below the required version (string) for the 'acfsutil tag' commands.: Cause: The 'acfsutil tag' command was rejected because the ADVM disk group compatibility had not been upgraded to the indicated version, which is required for that command.; Action: Use the Oracle ASM Configuration Assistant (ASMCA) tool or the SQL ALTER DISKGROUP statement to upgrade the disk group compatibility (COMPATIBLE.ADVM attribute) to the specified version and then re-issue the original command. If the disk group compatibility cannot be upgraded, update the ACFS compatibility using the 'acfsutil compat set' command and then re-issue the original command.
ACFS-03322: The ADVM compatibility attribute for the diskgroup is below the required version (string) for the 'acfsutil repl' commands.: Cause: The 'acfsutil repl' command was rejected because the ADVM disk group compatibility had not been upgraded to the indicated version, which is required for that command.; Action: Use the Oracle ASM Configuration Assistant (ASMCA) tool or the SQL ALTER DISKGROUP statement to upgrade the disk group compatibility (COMPATIBLE.ADVM attribute) to the specified version and then re-issue the original command. If the disk group compatibility cannot be upgraded, update the ACFS compatibility using the 'acfsutil compat set' command and then re-issue the original command.
ACFS-03323: stringc option requires the stringt option: Cause: The 'c' option was specified without the 't' option. The 'c' option invokes case insensitive substring matching on the tag names specified using the 't' option.; Action: To use the 'c' option, add the 't' option to specify a tag.
ACFS-03324: Unable to obtain metric data for string: Cause: An internal ioctl operation to access metric data from ACFS file system failed. This message is accompanied by other message(s) providing details on the error.; Action: Correct the problem indicated by the other message(s). If the cause of the problem is unclear, contact Oracle Support Services.
ACFS-03344: Error, strings option with repetition interval applied to multiple file systems.: Cause: A request to report file system statistics periodically was rejected because it applied to multiple file systems. A single file system must be specified explicitly when supplying the 's' option with a time interval.; Action: Reissue the request specifying a single file system or omitting the repetition interval.
ACFS-03345: cannot reduce accelerator volume size below 256MB: Cause: A size request specified an accelerator volume size less than the minimum allowed.; Action: Specify an accelerator volume size of 256MB or more.
ACFS-03346: unable to grow the accelerator volume in support of a request to grow the primary volume: Cause: A size request required growth of the accelerator volume, which failed. This message is accompanied by other messages providing details on the error.; Action: Correct the problem identified by the other messages. If the cause is unclear, contact Oracle Support Services.
ACFS-03347: Error, strings option with repetition interval applied to multiple file systems (string).: Cause: A request to report file system statistics periodically was rejected because it applied to multiple file systems. A single file system must be specified explicitly when supplying the 's' option with a time interval.; Action: Reissue the request specifying a single file system or omitting the repetition interval.
ACFS-03348: cannot display file system statistics and individual items at the same time: Cause: An attempt to display file system statistics was rejected because one or more of the -s or -d options were specified with the -o option. The display of statistics and the display of individual items are mutually exclusive.; Action: Retry the command specifying either the -o option for individual items or the -s or -s and -d for statistics.
ACFS-03349: cannot display detailed file system statistics without specifying the statistics option: Cause: An attempt to display file system statistics was rejected because the -d option was specified without the -s option. The detail option -d augments the -s option and cannot be used alone.; Action: Retry the command with both -s and -d options.
ACFS-03350: cannot display file system statistics and fragmentation at the same time: Cause: An attempt to display file system statistics was rejected because the -s option was specified with the -f option. The display of statistics and the display of fragmentation are mutually exclusive.; Action: Retry the command specifying either the -s option for statistics or the -f option for fragmentation.
ACFS-03351: cannot display file system fragmentation and individual items at the same time: Cause: An attempt to display file system fragmentation was rejected because the -f option was specified with the -o option. The display of fragmentation and the display of individual items are mutually exclusive.; Action: Retry the command specifying either the -f option for fragmentation or the -o option for individual items.
ACFS-03352: cannot display file system fragmentation without specifying the fragmentation option: Cause: An attempt to display file system fragmentation was rejected because the -v option was specified without the -f option. The verbose option -v augments the -f option and cannot be used alone.; Action: Retry the command with both -f and -v options.
ACFS-03353: invalid count value supplied: Cause: An attempt to display file system statistics was rejected because a zero or negative integer was provided for the count argument.; Action: Retry the command with a positive integer for the statistics count.
ACFS-03354: local statistics dump failed: Cause: An attempt to save ACFS file system statistics failed. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation. If the resolution is not clear or the problem persists, contact Oracle Support Services.
ACFS-03355: state dump failed: Cause: An attempt to save ACFS binary log data failed. The accompanying messages provide detailed failure information.; Action: The Oracle Kernel Services (OKS) persistent log provides more detailed failure information. Resolve the indicated problems, and then retry the operation. If the resolution is not clear or the problem persists, contact Oracle Support Services.
ACFS-03357: local lock dump failed: Cause: An attempt to save ACFS file system lock info failed. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation. If the resolution is not clear or the problem persists, contact Oracle Support Services.
ACFS-03372: Resize request is greater than allowed maximum for ADVM volume: numberGB: Cause: An attempt to resize an ADVM volume failed because the size requested was larger than the maximum allowed ADVM volume size reported in the message.; Action: Retry the resize operation specifying a size that is smaller than the maximum allowed ADVM volume size.
ACFS-03400: Invalid repl toggle command.: Cause: The command was rejected because an invalid sub-command was specified.; Action: Review the command usage and retry the command providing valid input.
ACFS-03450: Continue to panic the cluster [y|n] ?: Cause: The 'acfsutil panic' command was issued to panic the cluster.; Action: Respond Y(yes) to proceed or N(no) to cancel.
ACFS-03451: Continue to panic the system [y|n] ?: Cause: The 'acfsutil panic' command was issued to panic the system.; Action: Respond Y(yes) to proceed or N(no) to cancel.
ACFS-03452: failed to move file or directory from string to string: Cause: An attempt to rename a file or directory failed because the target was an existing, populated directory or the user permissions were insufficient to perform the operation.; Action: Retry the operation after removing the target files or correcting the permissions.
ACFS-03461: 'accel add' aborted because one node of the cluster did not unmount properly: Cause: An attempt to add an accelerator volume was aborted because one node of cluster had crashed prior to running 'acfsutil accel add' command.; Action: Execute the ACFS mount command, followed by the ACFS dismount command on any node of the cluster. After that, retry the add operation. If the cause of the problems is unclear, contact Oracle Support Services.
ACFS-03462: accelerator volume not added: Cause: An attempt to add an accelerator volume failed. This message is accompanied by other messages providing details on the error.; Action: Correct the problems indicated by the other messages. If the cause of the problems is unclear, contact Oracle Support Services.
ACFS-03463: 'acfsutil accel add' failed due to a version mismatch. The Oracle ASM Dynamic Volume Manager (Oracle ADVM) compatibility attribute for the disk group is less than number.number.number.number.number.: Cause: An attempt to add an accelerator volume was rejected because the ADVM disk group compatibility had not been upgraded to the release specified in the message or higher, which was required for the operation.; Action: Use the Oracle ASM Configuration Assistant (ASMCA) tool or the SQL ALTER DISKGROUP statement to upgrade the disk group compatibility (COMPATIBLE.ADVM attribute) to the indicated version and then re-issue the original command. If the disk group compatibility cannot be upgraded, update the ACFS compatibility using the 'acfsutil compat set' command and then re-issue the original command.
ACFS-03464: restarting add operation: Cause: The metadata of the specified volumes indicated that a previous invocation of 'acfsutil accel add' with the same arguments had been interrupted before completion. The current invocation attempted to complete the add operation.; Action: The issued 'acfsutil accel add' command attempted to complete the previous accelerator add operation. No further action is necessary if this message was not accompanied by failure messages.
ACFS-03465: 'acfsutil accel add' interrupted. Ensure primary volume is accessible then run 'acfsutil accel add' with the same arguments again to complete the operation.: Cause: An event or condition interrupted the execution of the 'acfsutil accel add' command. This message is accompanied by other messages providing details on the error.; Action: Address errors in the accompanying error messages and run 'acfsutil accel add' with the same arguments to render the primary volume mountable. The accelerator add operation should then be complete.
ACFS-03466: Primary volume has an accelerator volume: Cause: An attempt to an the accelerator volume was aborted because the specified primary volume has already had an accelerator volume.; Action: Before attempting to add an accelerator volume ensure that the primary does not have one. If the cause of the problem is unclear, contact Oracle Support Services.
ACFS-03467: write of Rollback_Log failed: Cause: An attempt to add an accelerator volume failed because of an error in a write operation to the primary volume. The accompanying messages provide additional details on the error.; Action: Correct the problem indicated by the other messages. If the cause of the problem is unclear, contact Oracle Support Services.
ACFS-03468: Unable to roll back the operation of add accelerator.: Cause: An attempt to roll back the add accelerator operation failed. This message is accompanied by other messages providing details on the error.; Action: Correct the problem described in the accompanying messages if possible or run fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ACFS-03469: Write failed at disk offset: string size: number bytes.: Cause: An attempt to write at the indicated disk offset failed. This message is accompanied by other messages providing details on the error.; Action: Correct the problem described in the accompanying messages if possible or run fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ACFS-03500: Unable to access kernel persistent log entries.: Cause: Could not get or set persistent log configuration data.; Action: Make sure that the Oracle kernel drivers are loaded/started (run 'acfsdriverstate loaded'). If loaded/started, make sure that you have root/administrator privileges.
ACFS-03501: The 'query' option may not be used with any other options.: Cause: Additional options to 'query' were specified on the command line.; Action: Do not use any other options with the 'query' option.
ACFS-03502: The specified maximum log file size is less than number MB or is greater than number MB.: Cause: An invalid log file size was entered on the command line.; Action: Specify a value equal to or greater than the minimum size and equal to or less than the maximum size.
ACFS-03503: The specified interval is less than number seconds.: Cause: An invalid interval value was entered on the command line.; Action: Enter an interval value equal to or greater than the minimum.
ACFS-03504: An invalid high water level value (number percent) was specified.: Cause: The high water level must be greater than the low water level and less than 100 percent.; Action: Enter a valid high water level value.
ACFS-03505: An invalid low water level value (number percent) was specified.: Cause: The low water level must be greater than zero and less than the high water level.; Action: Enter a valid low water level value.
ACFS-03506: The selected percentage does not generate an even integer. Changing to number percent.: Cause: The specified percentage of the buffer size generates a remainder.; Action: None. Informational.
ACFS-03507: The specified buffer size is less than number KB or is greater than number KB.: Cause: An invalid buffer size value was entered on the command line."; Action: Enter a value equal to or greater than the minimum or equal to or less than the maximum size.
ACFS-03508: The specified maximum number of log files is less than number or greater than number.: Cause: An invalid maximum number of log files was entered on the command line.; Action: Specify a value equal to or greater than the minimum and equal to or less than the maximum.
ACFS-03509: string is not a Grid infrastructure home.: Cause: An invalid Grid infrastructure home was entered on the command line.; Action: Specify a valid Grid infrastructure home.
ACFS-03510: There are more log files on the system than are being configured. Removing the oldest files.: Cause: A new, lower, maximum number of allowable Oracle Kernel Services (OKS) persistent log files was configured and there are currently more log files on the system. Deleting the oldest files."; Action: None. Informational.
ACFS-03511: Deleting string.: Cause: A log file was deleted to satisfy the new configuration.; Action: None. Informational.
ACFS-03512: Renaming string to string.: Cause: A log file was renamed to place it in time modified sequential order.; Action: None. Informational.
ACFS-03513: The OKS persistent log configuration settings cannot be queried.: Cause: The Oracle Kernel Services (OKS) persistent log was not running.; Action: Start the log with 'acfsutil plogconfig -d gridhome'.
ACFS-03514: The directory 'string' can not be converted to an absolute path.: Cause: A directory name was specified that could not be converted to an absolute path. The name was either an invalid relative path or, on Windows, included an invalid drive letter.; Action: Specify the directory name in the form of an absolute path. On Windows, the absolute path includes the drive letter.
ACFS-03515: The OKS persistent log buffer resize operation failed.: Cause: The Oracle Kernel Services driver could not allocate a log buffer of the requested size. The current buffer size remained unchanged.; Action: This is an internal error. Contact Oracle Support Services.
ACFS-03516: Cannot disable storage interest tracking on a file system with on-disk version less than 50.: Cause: The request to disable storage interest tracking on the specified file system failed. The disablesoap command can only be used on file systems with version 50 or higher on-disk structures.; Action: None. Informational.
ACFS-03528: failed to determine Oracle Base: Cause: The operation to retrieve the Oracle Base location failed. This message is accompanied by other message(s) providing details on the error.; Action: Correct the problem indicated by the other message(s). If the solution is not clear, contact Oracle Support Services.
ACFS-03529: Warning: The 'd' option was specified with an argument, which is no longer used - argument ignored.: Cause: 'acfsutil plogconfig' now gets the log location internally. The specified log location was ignored and the command continued using the internally derived location.; Action: None
ACFS-03530: The 'terminate' option may not be used with any other options.: Cause: Conflicting options were specified on the command line.; Action: Do not use any other options with the 'terminate' option.
ACFS-03531: Snapshot link string does not exist.: Cause: An attempt to execute the acfsutil snap link command failed because no snapshot link could be found with the indicated name.; Action: Retry the acfsutil snap link command with the correct name.
ACFS-03532: The specified string string is not a valid snapshot link name.: Cause: The acfsutil snap link command failed because the indicated name was not a valid snapshot link name. Possible reasons include: 1) The snapshot link name exceeded the limit of 255 characters. 2) The snapshot link name equaled "." or "..". 3) The snapshot link name contained "/" (Unix or Linux). 4) The snapshot link name contained "" or ":" (Windows). 5) The snapshot link name contained an illegal character for NTFS file names (Windows).; Action: Retry the acfsutil snap link command specifying a valid snapshot link name.
ACFS-03533: compression operation failed because the cluster is in rolling migration: Cause: An 'acfsutil compress' command was rejected because the cluster was in rolling migration. Compressing files during rolling migration was not supported.; Action: Complete the rolling migration and then retry the command.
ACFS-03534: cannot read from file: string: Cause: Execution of a requested application failed because it encountered an error in attempting to read from the indicated file. Additional messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.
ACFS-03535: The logs cannot be moved from 'string' to 'string'.: Cause: The command to move the Oracle Kernel Services persistent logs failed. The likely cause is that the destination file system was out of space.; Action: Verify that sufficient space is available at the target destination. If not, choose another location for the logs. Otherwise, contact Oracle Support Services.
ACFS-03536: failed to set ACFS compatibility level for mount point 'string': Cause: The 'acfsutil compat set' command was rejected because the file system is on an ADVM volume.; Action: Use the Oracle ASM Configuration Assistant (ASMCA) tool or the SQL ALTER DISKGROUP statement to upgrade the disk group compatibility (COMPATIBLE.ADVM attribute) to the specified version.
ACFS-03539: Base time stamp not found in log file.: Cause: Informational. The likely cause is that the running Oracle Kernel Services (OKS) driver is an older version that does not support time stamp conversion.; Action: None
ACFS-03540: The specified interval is greater than number seconds.: Cause: An invalid interval value was entered on the command line.; Action: Enter an interval value equal to or less than the maximum.
ACFS-03541: The symbolic link 'string' to 'string' cannot be created.: Cause: An attempt to start Oracle Kernel Services persistent logging was not completely successful. Logging was started, but the indicated symbolic link could not be created. Most likely the link name was non-empty directory.; Action: If a symbolic link is desired, delete the link target and its contents and reissue the command.
ACFS-03542: The specified OKS log directory 'string' is invalid because it is NFS mounted.: Cause: The indicated logging directory was NFS mounted.; Action: Enter a node local location for the Oracle Kernel Services (OKS) log.
ACFS-03543: The OKS persistent log is not active.: Cause: The Oracle Kernel Services (OKS) persistent log was not running.; Action: Start the log with 'acfsutil plogconfig -d [log_dir]'.
ACFS-03544: Directory 'string' exists as a file.: Cause: An Oracle Kernel Services (OKS) persistent log directory could not be created because it exists as a file.; Action: Either delete the file or choose another directory name.
ACFS-03545: The input text is longer than the maximum of number bytes.: Cause: The command failed because input text was too long.; Action: Retry the command using a text string shorter than the indicated maximum size.
ACFS-03546: failed to update the debug levels for the specified binary log: Cause: The 'acfsutil blog' command encountered an error while attempting to update the binary log debug levels.; Action: Check the Oracle Kernel Services (OKS) log for details, correct the error, and retry command.
ACFS-03547: unable to create snapshot link while replication v1 is active: Cause: An attempt to execute the acfsutil snap link command failed because replication v1 is active.; Action: Retry the acfsutil snap link command after terminating replication.
ACFS-03548: snapshot link cannot be created at the specified path: Cause: An attempt to execute the acfsutil snap link command failed because the link is not allowed at the specified path. Possible reasons include: 1) The path is in .ACFS 2) The path is in another snapshot 3) The path is a replication standby; Action: Retry the acfsutil snap link command with an allowed path.
ACFS-03549: snapshot link cannot be created because the specified path already exists: Cause: An attempt to execute the acfsutil snap link command failed because a file already exists at the specified path.; Action: Retry the acfsutil snap link command with a different path.
ACFS-03602: Plug-in is already enabled on 'string': Cause: An attempt was made to enable the plug-in when it is already enabled.; Action: First disable the plug-in then retry the command.
ACFS-03603: Plug-in is not enabled on 'string': Cause: A plug-in command was attempt when the plug-in is not enabled.; Action: Enable the plug-in and then retry the command.
ACFS-03604: Unable to perform plug-in operation on 'string': Cause: The plug-in operation failed. This message is accompanied by other message(s) providing details on the error.; Action: Correct the problem indicated by the other message(s). If the solution is not clear, contact Oracle Support Services.
ACFS-03610: Invalid plug-in metric type: string: Cause: An invalid plug-in metric type was specified.; Action: Enter a valid metric type from the following list: acfsmetric1, acfsmetric2
ACFS-03611: Invalid interval specified.: Cause: An invalid interval was specified.; Action: Enter a valid interval between 1 and 3600 seconds.
ACFS-03612: Unable to retrieve list of plug-in enabled tags.: Cause: ACFS was unable to retrieve the list of tags for which the plug-in is collecting metrics. This message is accompanied by other message(s) providing details on the error.; Action: Correct the problem indicated by the other message(s). If the solution is not clear, contact Oracle Support Services.
ACFS-03613: Unable to write plug-in config file.: Cause: ACFS was unable to write the plug-in config file to disk.; Action: Try the command again. If the problem persists, contact Oracle Support Services.
ACFS-03614: Plug-in cannot be enabled for more than number tags.: Cause: An attempt was made to enable the plug-in for more than the maximum allowed number of tags.; Action: Enable plug-in with fewer tags.
ACFS-03615: An error occured when copying the list of tags.: Cause: This is an internal error.; Action: Try the command again. If the problem persists, contact Oracle Support Services.
ACFS-03621: missing plug-in metric type: Cause: No plug-in metric type was specified.; Action: Enter a valid metric type from the following list: "acfsmetric1"
ACFS-03623: unable to modify the ACFS registration for mount point 'string': Cause: Could not modify the ACFS registration for the specified mount point.; Action: Examine the accompanying error messages and respond accordingly. If the solution is not clear, contact Oracle Support Services.
ACFS-03624: unable to modify registration for ACFS volume 'string': Cause: Could not modify the ACFS registration for the ACFS volume.; Action: Examine the accompanying error messages and respond accordingly. If the solution is not clear, contact Oracle Support Services.
ACFS-03626: invalid combination of -C and -f options: Cause: The 'acfsutil log' command was issued with both the -f and -C options. This is a conflict, because the log file names are pre-specified for -C and may not be specified using -f.; Action: Re-issue the 'acfsutil log' command with only the desired option. With -C, the log files will be generated in the persistent log directory in the form yymmddhhmmss.log. With -f the specified name will be used.
ACFS-03627: logging behavior change specified with cluster option: Cause: The 'acfsutil log' command was issued with both the -C option and and an option that modifies the logging behavior.; Action: Re-issue the 'acfsutil log' command without the -C option to modify the ACFS logging behavior. To create logs on all cluster nodes, issue 'acfsutil log -C' with no other options.
ACFS-03637: corruption detected in log file 'string': Cause: The 'acfsutil logconvert' command detected a corrupted log entry.; Action: Examine the log file manually and, if a single line is corrupted, remove that line and re-issue the command. For systemic corruption, log file recovery may not be possible.
ACFS-03641: auto-resize increment below minimum numberG: Cause: An attempt to update auto-resize settings specified an auto-resize increment less than the minimum allowed.; Action: Retry the command using a bigger auto-resize increment.
ACFS-03643: failed to update auto-resize settings: Cause: The ACFS driver was unable to update the auto-resize settings.; Action: Ensure that your compatible.advm setting allows auto-resize and then re-issue the command.
ACFS-03644: No auto-resize increment is currently configured.: Cause: An attempt was made to set an auto-resize maximum when no auto-resize increment was set.; Action: Specify an auto-resize increment when specifying a maximum.
ACFS-03645: File system of size number string requires an accelerator volume of size number string for best performance, which is larger than the current accelerator volume size number string.: Cause: The file system was resized such that the accelerator volume size was then below the minimum size recommended for best performance.; Action: Run 'acfsutil size' to shrink the file system to the recommended size, or to increase the accelerator volume size to the recommended size.
ACFS-03655: Too many read failures on device string. Exiting.: Cause: An attempt to retrieve the metadata from the indicated device was terminated because there were too many read errors. The accompanying error messages provide additional failure details.; Action: Attempt to correct the issues indicated by the accompanying messages and retry. If unable to make progress, contact Oracle Support Services.
ACFS-03656: invalid compression unit size: number bytes\n Valid compression unit sizes are string bytes.: Cause: An invalid value for compression unit size was provided.; Action: Specify a valid value for compression unit size with the -c option and retry.
ACFS-03657: Directory string is not on an ACFS Volume.: Cause: The specified output directory was not located on an ACFS Volume.; Action: Specify an output directory on an ACFS Volume and retry.
ACFS-03658: Too many file names were specified.: Cause: There were too many file names for the the options being used.; Action: Consult the command inline help or the product documentation for command argument details.
ACFS-03659: No files to copy were specified.: Cause: There were no file names to copy specified.; Action: Consult the command inline help or the product documentation for command argument details.
ACFS-03660: Compression is not enabled on the volume containing directory string.: Cause: The target ACFS volume did not have compression enabled.; Action: Enable compression on the volume and retry, or use the -u option.
ACFS-03662: partial write during copy of file string: Cause: A write to the volume during file copy failed. This message is accompanied by other messages providing details on the error.; Action: Correct the problem indicated by the other messages. If the cause of the problem is unclear, contact Oracle Support Services.
ACFS-03671: failed to set compression information for file string: Cause: An internal ioctl operation to set compression information for a file failed. This message is accompanied by other messages providing details on the error.; Action: Correct the problem indicated by the other messages. If the cause of the problem is unclear, contact Oracle Support Services.
ACFS-03674: Pathname string is not a directory.: Cause: The pathname following the -r option was not a directory.; Action: Specify a directory for a recursive copy and retry.
ACFS-03676: Pathname string is not a directory or a regular file.: Cause: The pathname provided was not a directory or a regular file.; Action: Retry the command using only directory or file names on the command line.
ACFS-03677: no output directory specified: Cause: No output directory was found in the command line.; Action: Provide the name of an existing directory and retry.
ACFS-03678: too many directories specified: Cause: The parameters provided contain more directories than expected for the options used.; Action: Consult the command inline help or the product documentation for command argument details.
ACFS-03679: File string is a file type that cannot be compressed.: Cause: The file specified with the -c option was a type of file that cannot be compressed.; Action: Retry the command without the -c option.
ACFS-03680: File system path string already exists. Compress copy of file string will not execute.: Cause: An attempt to execute the acfsutil compress copy command failed because the indicated destination path name already existed and the forced overwrite option was not specified.; Action: To overwrite an existing file, specify the -f option. Otherwise, specify a file system path that does not exist.
ACFS-03681: No files were copied.\n: Cause: An attempt to execute the acfsutil compress copy command failed because no files could be copied. This message is accompanied by other messages providing detailed failure information.; Action: Correct the problems indicated by the other messages. If the cause of the problem is unclear, contact Oracle Support Services.
ACFS-03682: File system path string is not a regular file.: Cause: The specified path name was not a regular file.; Action: Specify the path of a regular file to copy.
ACFS-03683: File system path string is not a directory.: Cause: The last path name specified was not a directory.; Action: Specify a file system directory for the last command line argument.
ACFS-03684: File string with internal block size string bytes is being compressed with compression unit size string bytes. It will not be usable by the RDBMS.: Cause: The file was copied with a compression unit size that prevents the database from using it.; Action: If the copy is intended to be used by the database, it must be compressed with a compression unit size equal to the internal block size. In this case, use the -c option with a value equal to the internal block size and retry the command.
ACFS-03685: File system path string cannot be converted to an absolute path.: Cause: A path name was specified that could not be converted to an absolute path. The name was either an invalid relative path or, on Windows, included an invalid drive letter.; Action: Specify the path name in the form of an absolute path. On Windows, the absolute path includes the drive letter.
ACFS-03691: successful update of mount point 'string' to ACFS compatibility level with number.number.number.number.numberstring release stream: Cause: Informational.; Action: None
ACFS-03692: Failed to update ACFS compatibility level for mount point 'string'. The active ACFS compatibility level (number.number.number.number.numberstring) is a higher release than the requested release.: Cause: The internal ioctl operation to set ACFS compatibility level for a mounted file system failed because the active ACFS compatibility level is higher than the requested release stream.; Action: Select a supported release stream that is higher than the active ACFS compatibility level and retry the 'acfsutil compat set' command.
ACFS-03693: failed to get ACFS compatibility level for mount point 'string': Cause: An internal ioctl operation to get the ACFS compatibility level for a mounted file system failed. This message is accompanied by other messages providing details on the error.; Action: Correct the problem indicated by the other messages. If the cause of the problem is unclear, contact Oracle Support Services.
ACFS-03695: Invalid release supplied. Requested version of number.number.number.number.number exceeds the active version of the cluster (number.number.number.number.number).: Cause: The release supplied was higher than the active version of the cluster.; Action: If the cluster is in the proces of a rolling upgrade, verify the target version of the upgrade and wait until the upgrade has completed to retry the command. If the cluster is not in the process of a rolling upgrade, the supplied release will not be supported until the cluster has been upgraded to a sufficient release.
ACFS-03696: Invalid release supplied.: Cause: The supplied release was invalid.; Action: Verify that the supplied release follows the Oracle version syntax (For example, 12.2.0.0.0) and retry the command.
ACFS-03697: The ACFS compatibility level must be set to number.number.number.number.number or higher to proceed.: Cause: The specified ACFS compatibility level was too low to support the supplied list of options.; Action: Retry the mkfs command with a release passed to the -c option that is equal to or exceeds the required version displayed in the message.
ACFS-03700: failed to set ACFS compatibility level for mount point 'string': Cause: An internal ioctl operation to set ACFS compatibility level for a mounted file system failed. This message is accompanied by other messages providing details on the error.; Action: Correct the problem indicated by the other messages. If the cause of the problem is unclear, contact Oracle Support Services.
ACFS-03731: The Oracle ADVM compatibility level for the disk group is less than the required version 12.2 for auto-resize.: Cause: An attempt to enable auto-resize was rejected because the ADVM disk group compatibility level had not been upgraded to the indicated version, which is required for that command.; Action: Ensure that the compatible.advm setting is at least 12.2.0.0.0 and then re-issue the command.
ACFS-03732: Skipping invalid or non-numeric -o entry string.: Cause: An attempt to copy an item from the additional offset list (-o) encountered the indicated non-numeric or invalid entry. The indicated invalid entry was skipped.; Action: If the invalid entry was required, re-issue the command with the correct value. Otherwise no further action is required.
ACFS-03733: Too many -o arguments. Ignoring entries beyond number.: Cause: The command 'acfsutil meta' was not executed for all offset list (-o) entries because the number of -o entries exceeded the indicated limit. Entries beyond that limit were ignored.; Action: If the additional entries are required, re-issue the command, specifying a different output file along with the -o arguments that were previously ignored. Otherwise no further action is required.
ACFS-03740: The Oracle ADVM compatibility attribute for the disk group is less than the required version (string) for 'acfsutil size -s' command.: Cause: An attempt to enable auto-shrink was rejected because the ADVM disk group compatibility level had not been upgraded to the indicated version, which is required for that command.; Action: Ensure that the compatible.advm setting is at least 18.0.0.0.0 for Linux or 19.0.0.0.0 for Aix and then re-issue the command.
ACFS-03741: Failed to set auto-shrink: Cause: The ACFS driver was unable to change auto-shrink state.; Action: Retry the command. If unable to proceed, contact Oracle Support Services.
ACFS-03751: Unable to modify the set of nodes where this ACFS file system is running.: Cause: An attempt to modify the set of nodes where this ACFS file system was running was rejected because that operation was not supported by the command 'acfsutil registry'.; Action: Delete and re-add the ACFS file system using the command 'acfsutil registry'. Use the node option to specify the nodes on which this file system should run.
ACFS-03777: no connection to Oracle ASM: Cause: A requested operation that required services from Oracle Automatic Storage Management (ASM) failed because it could not connect to an ASM instance.; Action: Start an Oracle ASM instance and retry the command. If the problem persists, contact Oracle Support Services.
ACFS-03778: unable to perform remote operation 'string' for file string: Cause: An attempt to issue the indicated remote command on the indicated file failed. The Oracle Kernel Services (OKS) persistent log provides more detailed failure information.; Action: Examine the messages in the OKS persistent log, resolve the indicated problems, and retry the operation.
ACFS-03780: 'acfsutil meta' metadata file had an unknown file format:\n string expected\n string found: Cause: An attempt to expand an ACFS metadata file was rejected because the metadata file had an unknown format, possibly because it was not created by the command 'acfsutil meta', or it was created by an incompatible version of that command.; Action: Retry the operation, specifying a valid 'acfsutil meta' file.
ACFS-03783: unable to determine the cluster type: Cause: An 'acfsutil' command failed to determine the type of cluster that contained the local server. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated problems, and retry the operation.
ACFS-03784: Minimum scan size is numberMB.: Cause: An attempt to perform a limited file system scan was rejected because the scan size was smaller than the indicated minimum.; Action: Retry the command using a valid scan size.
ACFS-03802: unable to obtain lock statistics: Cause: An error occurred while fetching lock statistics. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.
ACFS-03804: invalid sort column: 'string': Cause: An attempt to get lock statistics was rejected because an invalid value was provided for the sort option.; Action: Retry the operation, providing a valid value for the sort option. Valid sort option values can be displayed by running the command with the 'h' (help) option.
ACFS-03805: command failed due to an internal error: Cause: An attempt to get lock statistics failed due to an internal error.; Action: Contact Oracle Support Services.
ACFS-03807: unknown sort column: 'number': Cause: An internal sort function was called with an unknown sort column. This was an internal error.; Action: Contact Oracle Support Services.
ACFS-03808: command cannot accept the 'string' and 'string' options simultaneously: Cause: An 'acfsutil lockstats' command was rejected because of an invalid option combination. 'acfsutil lockstats' could not take the specified options simultaneously.; Action: Rerun the command with only one of the specified options.
ACFS-03809: invalid value for option 't': 'string': Cause: An 'acfsutil lockstats' command was rejected because a value that was not a positive integer was provided for the 't' option.; Action: Rerun the command, providing a positive integer value for the option 't'.
ACFS-03813: cannot find the ACFS Checker utility: string: Cause: The 'acfsutil meta' back-end utility (the ACFS Checker) could not be found.; Action: Make sure ACFS has been properly installed. If the solution is not clear, contact Oracle Support Services.
ACFS-03814: stringe stringi stringo stringq options cannot be used with stringg: Cause: The 'acfsutil meta' command cannot use the 'e', 'i', 'o', nor 'q' options simultaneously with the 'g' option.; Action: Rerun the command with a compatible set of options.
ACFS-03815: Cannot determine if string was mounted in the cluster.: Cause: 'acfsutil meta' cannot determine if the specified device is mounted somewhere in the cluster. This message is accompanied by other messages providing details on the error.; Action: Correct the problem indicated by the other messages. If the cause of the problem is unclear, contact Oracle Support Services.
ACFS-03816: 'acfsutil meta stringg' failed because string was mounted in the cluster.: Cause: An attempt to execute the command 'acfsutil meta -g' failed because the specified device is mounted somewhere in the cluster.; Action: Make sure the device is unmounted on all cluster nodes, and then retry the command.
ACFS-03817: The 'acfsutil meta' command was rejected because the stringO, stringC and stringS options can only be used with the stringg option.: Cause: The 'O', 'C' and 'S' options can only be used with the 'acfsutil meta' 'g' option.; Action: Rerun the command with a compatible set of options.
ACFS-03818: The online 'acfsutil meta stringg stringO' command failed because all the stringO, stringC and stringS options were not specified.: Cause: If one of these 'acfsutil meta 'g' options 'O', 'C' and 'S' are specified, they must all be specified.; Action: Rerun the command with a compatible set of options.
ACFS-03819: The online 'acfsutil meta stringg stringO' failed because string was not mounted.: Cause: The online 'acfsutil meta -g -O' command found that the specified device was unmounted.; Action: Make sure the device is mounted, and then retry the command.
ACFS-03820: WARNING: Incomplete: string - Check the log file for errors.: Cause: 'acfsutil meta' failed while collecting the file system metadata and the specified metadata collection file may be incomplete. The metadata collection log file will have the failure reason.; Action: If possible re-run 'acfsutil meta' again to collect all the metadata. If you must use this metadata collection file, just be aware that it may be incomplete.
ACFS-03821: WARNING: ACFS Checker failed. Re-run 'acfsutil meta' without the stringg option.: Cause: ACFS Checker failed while collecting the file system metadata and the specified metadata collection file may be incomplete. The metadata collection log file will have the failure reason.; Action: If possible re-run 'acfsutil meta' without the 'g' option to force a block-by-block file system walk. If you must use this metadata collection file, just be aware that it may be incomplete.
ACFS-03822: stringe and stringi options cannot be used when collecting metadata: Cause: The 'acfsutil meta' command failed because invalid options were supplied. The 'e' and 'i' options cannot be used when collecting metadata.; Action: Rerun the command with a compatible set of options.
ACFS-03823: The stringstring file cannot be the stringstring file.: Cause: The 'acfsutil meta' command failed because the 'f' or 'a' option file was the same as the option 'e' file.; Action: Rerun the command with a different option 'f' or 'a' file name.
ACFS-03824: Fshare operation could not complete.: Cause: An attempt to execute the 'acfsutil fshare create' command failed. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.
ACFS-03825: Unable to perform file share operation on string: Cause: An attempt to execute the 'acfsutil fshare create' command failed. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.
ACFS-03826: Cannot create file share string. It already exists.: Cause: An attempt to create a file share failed because a file share with the indicated name was found to already exist.; Action: Retry the ' acfsutil fshare create' command specifying a different name.
ACFS-03827: Cannot create file share string. The file system is full.: Cause: An attempt to create a file share failed because the file system is out of space.; Action: Delete unnecessary files from the file system to free up space, resize the file system using 'acfsutil size', or delete snapshots from the file system if any exist.
ACFS-03828: File share string does not exist.: Cause: An attempt to execute the 'acfsutil fshare create' command failed because no file could be found with the indicated name.; Action: Retry the 'acfsutil fshare create' command with the correct name.
ACFS-03829: Cannot create file share string as replication V1 is active on this mount point.: Cause: Replication V1 was active on the mount point. ACFS Replication V1 and ACFS file shares cannot co-exist on the same mount point.; Action: Terminate replication by using command 'acfsutil repl term' and then retry.
ACFS-03830: Cannot create file share string as this operation is not allowed on a standby file system.: Cause: An attempt to execute the 'acfsutil fshare create' on a standby file system was attempted.; Action: None
ACFS-03831: Cannot create file share string in a read only snapshot.: Cause: An attempt to create a file share failed because the snapshot is read only.; Action: Reissue the command in a writable snapshot.
ACFS-03832: Cannot create file share string in a read only mountpoint.: Cause: An attempt to create an file share failed because the mountpoint is read only.; Action: Reissue the command in a writable mountpoint.
ACFS-03833: Cannot create file share of string as file is compressed.: Cause: ACFS Compression and ACFS file shares cannot co-exist on the same file.; Action: Turn off compression by using command 'acfsutil compression off' and copy the file then retry.
ACFS-03834: Cannot create file share string as destination file is in different namespace.: Cause: An attempt to create a file share failed because destination is in a different snapshot or filesystem than the source."; Action: Reissue the command in the same namespace.
ACFS-03836: The ADVM compatibility attribute for the diskgroup is below the required version (string) for the 'acfsutil fshare' commands.: Cause: The 'acfsutil fshare command was rejected because the ADVM disk group compatibility had not been upgraded to the indicated version, which is required for that command.; Action: Use the Oracle ASM Configuration Assistant (ASMCA) tool or the SQL ALTER DISKGROUP statement to upgrade the disk group compatibility (COMPATIBLE.ADVM attribute) to the specified version and then re-issue the original command. If the disk group compatibility cannot be upgraded, update the ACFS compatibility using the 'acfsutil compat set' command and then re-issue the original command.
ACFS-03837: There are too many fshares for the file string. Only number are allowed. Reduce the number of fshares before proceeding.: Cause: An attempt to create more than the maximum allowed number of file shares was rejected.; Action: Delete a file share before creating a new one.
ACFS-03839: Cannot create file share string as destination file is in different filesystem.: Cause: An attempt to create a file share failed because destination is in a different filesystem"; Action: Reissue the command in the same filesystem.
ACFS-03840: name of file share cannot exceed number bytes: Cause: At attempt to create a file share was rejected because the specified name was too long.; Action: Issue the command again using a shorter file share name.
ACFS-03841: The specified string string is not a valid fshare create name.: Cause: The 'acfsutil fshare create' command failed because the indicated name was not a valid fshare create name. Possible reasons include: 1) The fshare create name exceeded the limit of 255 characters. 2) The fshare create name equaled "." or "..". 3) The fshare create name contained "/" (Unix or Linux). 4) The fshare create name contained "" or ":" (Windows). 5) The fshare create name contained an illegal character for NTFS file names (Windows).; Action: Retry the 'acfsutil fshare create' command specifying a valid fshare create name.
ACFS-03847: Cannot create file share string as destination directory was not writable.: Cause: The 'acfsutil fshare create' command failed because the destination directory was not writable.; Action: Check the permission of the directory and ensure it has write permission.
ACFS-03904: No auto-resize increment is currently configured.: Cause: An attempt was made to set an auto-resize percentage when no auto-resize increment was set.; Action: Specify an auto-resize increment when specifying a percentage.
ACFS-03906: unable to update UTC offset: Cause: An internal ioctl operation failed to update ACFS's UTC offset. This message is accompanied by other messages providing details on the error.; Action: Correct the problem indicated by the other messages. If the cause of the problem is unclear, contact Oracle Support Services.
ACFS-03912: Failed to delete volume snapshot string.: Cause: The ACFS volume snapshot could not be deleted. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.
ACFS-03913: Failed to create volume snapshot string.: Cause: The ACFS volume snapshot could not be created. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.
ACFS-03914: Volume snapshot string cannot be deleted because it is in use.: Cause: The ACFS volume snapshot could not be deleted because it was in use.; Action: Reissue the command specifying a snapshot that is not in use.
ACFS-03915: name of volume snapshot cannot exceed number bytes in length: Cause: An attempt to create a snapshot was rejected because the specified name of the volume snapshot was too long.; Action: Issue the command again using a shorter snapshot name.
ACFS-03916: Failed to obtain device information about supplied mountpoint string.: Cause: The ACFS primary device name could not be derived. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.
ACFS-03917: Unable to create volume snapshot because generated default name exceeds number bytes in length.: Cause: An attempt to create a snapshot was rejected because the generated name was too long. The default name is generated using the name of the parent volume and the current time: <parent_vol>_YYMMDDHHMMSS.; Action: Issue the command again using the -n option to specify a volume snapshot name.
ACFS-03918: Failed to create volume snapshot as volume device name string already exists.: Cause: The ACFS volume snapshot could not be created because the specified name already exists.; Action: Reissue the command specifying a different snapshot name.
ACFS-03919: Failed to obtain volume attributes for string.: Cause: The volume attributes could not be obtained. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.
ACFS-03920: Creation of volume snapshot string complete.: Cause: Informational; Action: None
ACFS-03921: Deletion of volume snapshot string complete.: Cause: Informational; Action: None
ACFS-03922: Insufficient privileges to create volume snapshot of string.: Cause: An attempt to create a volume snapshot was rejected due to insufficient privileges. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.
ACFS-03923: Operation not supported by the underlying device.: Cause: An attempt to create a volume snapshot was rejected because the operation was not supported. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.
ACFS-03924: Failed to create volume snapshot of string because the ACFS compatibility of the file system is lower than the required minimum of string.: Cause: An attempt to create a volume snapshot was rejected because the ACFS file system had not been upgraded to the indicated ACFS compatibility, which is required for that command.; Action: Update the ACFS compatibility to the required level using the 'acfsutil compat set' command and then reissue the original command.
ACFS-03925: Failed to create volume snapshot of string because the file system could not be frozen.: Cause: An attempt to create a volume snapshot failed because the target file system could not be frozen. The accompanying messages provide detailed failure information.; Action: Read the accompanying messages, correct the issues identified there, and then retry the operation.
ACFS-03926: Failed to create volume snapshot of string because the file system could not be thawed.: Cause: An attempt to create a volume snapshot failed because the target file system could not be thaws from the frozen state. The accompanying messages provide detailed failure information.; Action: Read the accompanying messages, correct the issues identified there, and then retry the operation.
ACFS-03927: Volume snapshot information could not be returned for string.: Cause: An attempt to return volume snapshot information failed. The accompanying messages provide detailed failure information.; Action: Read the accompanying messages, correct the issues identified there, and then retry the operation.
ACFS-03928: Insufficient privileges to open string. Administrator access is required.: Cause: An attempt to execute an acfsutil command was rejected because the caller did not have sufficient privileges.; Action: Retry the command while logged in as a user with Linux root privileges.
ACFS-03929: Volume string is mounted. Reissue command using the mount point.: Cause: An attempt to create a volume snapshot failed because a device was specified and the file system was mounted. Volume snapshot creation must go through the mount point when the file system is mounted.; Action: Reissue the command specifying the mount point.
ACFS-03940: Creation of volume snapshot string with backup string complete.: Cause: Informational; Action: None
ACFS-03941: Failed to create volume snapshot of newly created file system.: Cause: The ACFS volume snapshot could not be created because the file system was never mounted after the mkfs command.; Action: Retry the command after the file system has been mounted on at least one node.
ACFS-03942: invalid combination of options: Cause: The 'acfsutil volsnap create' command was passed an invalid option combination that included both -w and -r options.; Action: Reissue the command specifying a valid option combination.
ACFS-03943: Failed to create volume snapshot due to invalid characters supplied in specified name.: Cause: The 'acfsutil volsnap create' command was passed an invalid set of characters in the backup or volume snapshot name.; Action: Reissue the command specifying valid name.
ACFS-03944: name of volume snapshot cannot exceed number bytes in length: Cause: An attempt to create a volume snapshot was rejected because the specified name of the volume snapshot was too long.; Action: Issue the command again using a shorter volume snapshot name.
ACFS-03945: name of volume backup cannot exceed number bytes in length: Cause: An attempt to create a volume backup was rejected because the specified name of the volume backup was too long.; Action: Issue the command again using a shorter volume backup name.
ACFS-03946: name of volume snapshot must exceed number bytes in length: Cause: An attempt to create a volume snapshot was rejected because the specified name of the volume snapshot was too short.; Action: Issue the command again using a longer volume snapshot name.
ACFS-03947: name of volume backup must exceed number bytes in length: Cause: An attempt to create a volume backup was rejected because the specified name of the volume backup was too short.; Action: Issue the command again using a longer volume backup name.
ACFS-03948: name supplied must exceed number bytes in length: Cause: The name of the volume snapshot or volume backup specified was too short.; Action: Issue the command again using a longer name.
ACFS-03949: Failed to create volume snapshot as specified file system is on read-only volume snapshot 'string'.: Cause: An attempt to create a volume snapshot was rejected because the specified file system was on a read-only volume snapshot.; Action: Issue the command again using a file system on a read-write volume.
ACFS-03950: Successful creation of backup string of file system string complete.: Cause: Informational; Action: None
ACFS-03951: Successful creation of backup string of volume snapshot string complete.: Cause: Informational; Action: None
ACFS-03952: name of volume backup cannot exceed number bytes in length: Cause: At attempt to create a volume backup was rejected because the specified backup name was too long.; Action: Issue the command again using a shorter backup name.
ACFS-03953: Failed to create volume backup due to invalid characters supplied in specified name.: Cause: The 'acfsutil volsnap backup' command was passed an invalid set of characters in the backup name.; Action: Reissue the command specifying valid name.
ACFS-03954: Failed to create volume backup string of volume snapshot string.: Cause: An attempt to create a volume backup was rejected. This message is accompanied by other messages providing details on the error.; Action: Correct the problem indicated by the other messages. If the solution is not clear, contact Oracle Support Services.
ACFS-03955: The volume backup operation failed. Volume backups must be managed from the Oracle Control Plane.: Cause: The requested operation failed because the volume was deployed in the Cloud. Volume backups of volumes deployed in cloud must be managed from the Oracle Control Plane.; Action: Retry the volume backup operation from the Oracle Control Plane.
ACFS-04001: Failed to open path string. Verify that string exists.: Cause: Path could not be opened.; Action: Verify the path is accessible before retrying.
ACFS-04002: unable to allocate a buffer: Cause: A request for process virtual memory by acfsdismount command failed. This message is accompanied by other message(s) providing details on the error.; Action: Correct the problem indicated by the other message(s). If possible, change options to reduce required memory and/or take steps to increase memory available to the process. Otherwise, report this error to Oracle Support Services.
ACFS-04003: volume string in use by a non-ACFS file system: Cause: The file system could not be dismounted because the specified volume was in use by another non-ACFS file system.; Action: Select a different volume and retry the dismount operation.
ACFS-04004: error removing symbolic link for string: Cause: An ACFS file system could not be dismounted because an attempt to remove a symbolic link failed. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.
ACFS-04005: error removing DOS definition for string: Cause: An ACFS file system could not be dismounted because an attempt to remove a DOS definition failed. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.
ACFS-04006: unable to remove the reparse point on string: Cause: An ACFS file system could not be dismounted because an attempt to remove the associated reparse point failed. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.
ACFS-04007: dismount failed due to open files on the volume: Cause: An ACFS file system could not be dismounted because an attempt to lock the associated volume failed. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.
ACFS-04008: failed to unlock the volume: Cause: An ACFS file system could not be dismounted because an attempt to unlock the associated volume failed. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.
ACFS-04009: unable to retrieve the volume name associated with string: Cause: An ACFS file system could not be dismounted because an attempt to retrieve the volume associated with the supplied mount point failed. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.
ACFS-04010: conversion of reparse data Unicode string to ANSI string failed: Cause: An ACFS file system could not be dismounted because an attempt to convert a unicode string to an ANSI string failed. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.
ACFS-04011: Failed to open volume string. Verify that string exists.: Cause: Volume could not be opened.; Action: Verify the ASM instance is operational and the volume is enabled and accessible before retrying.
ACFS-04013: acfsdismount /all operation did not complete. Unable to retrieve a mount point from the list of active ACFS file systems to dismount. It is possible that not all file systems were dismounted.: Cause: Failed to obtain the next file system to dismount.; Action: Use acfsmountvol to determine if there are any file systems still mounted and reissue 'acfsdismount /all' if necessary.
ACFS-04032: removing administrative network share for mount point string at share name 'string': Cause: Informational; Action: None
ACFS-04033: administrative network share 'string' does not share mount point string as expected: Cause: Attempted to remove the administrative network share associated with the specified ACFS mount point, but the network share does not share the specified ACFS mount point as expected.; Action: Examine the network share at the specified share name. If the network share shares an unmounted ACFS file system, manually remove the network share using 'net share share name /delete'
ACFS-04034: administrative network share for mount point string does not exist at share name 'string': Cause: Informational; Action: None
ACFS-04035: retrieving information for administrative network share 'string' failed: Cause: While removing the administrative network share associated with the specified ACFS mount point, failed to retrieve information on the administrative network share. This message is accompanied by other messages providing details on the error.; Action: Check for a network share at the specified share name. If a network share exists at the specified share name and it shares an unmounted ACFS file system, manually remove the network share using 'net share share name /delete'
ACFS-04036: removing administrative network share for mount point string at share name 'string' failed: Cause: Failed to remove the administrative network share associated with the specified ACFS mount point. This message is accompanied by other messages providing details on the error.; Action: Manually remove the administrative network share at the specified share name using 'net share share name /delete'
ACFS-04037: could not remove administrative network share for mount point string at share name 'string': Cause: Failed to remove the administrative network share associated with the specified ACFS mount point. This message is accompanied by other messages providing details on the error.; Action: Correct the error indicated by the accompanying messages.
ACFS-04038: Volume string is still mounted. Dismount will complete as soon as activity ceases on the file system.: Cause: At the conclusion of the file system dismount request, the file system was still mounted. This could be a result of open files on the mount point. The dismount will finish as soon as activity ceases on the file system.; Action: To force dismount to complete, terminate any processes or applications that are using the file system.
ACFS-04039: File string cannot be replicated as an fshare due to compression being enabled on the standby file system. Encryption attributes on the file, if any, were also not replicated.: Cause: Replication of the indicated file to the standby file system did not replicate as an fshare because the standby file system is configured with compression.; Action: If encryption on the primary file system is on, turn off and then turn on the encryption of the standby file system.
ACFS-04058: Ignoring unsupported ACFS command option: 'string': Cause: An unsupported 'umount.acfs' command option was specified.; Action: No action required. The unmount will proceed without the option.
ACFS-04150: unable to retrieve mount point information from the ACFS driver: Cause: During unmount processing, an attempt to retrieve mount point information from the ACFS driver failed.; Action: Verify the mount point is a valid ACFS file system before retrying the unmount command. If the problem persists, contact Oracle Support Services.
ACFS-04151: unmount of mount point string failed: Cause: The file system unmount failed. This message is accompanied by other message(s) providing details on the error.; Action: Correct the problem indicated by the other message(s). If the cause of the problem is unclear, contact Oracle Support Services.
ACFS-05001: must specify 'primary' or 'standby': Cause: Command syntax requires 'primary' or 'standby' argument.; Action: At command line, indicate primary or standby for replication command.
ACFS-05002: must provide an Oracle Net alias to the primary replication site: Cause: The Oracle Net alias to connect to the primary replication site was not specified.; Action: Provide Oracle Net alias to connect to the primary replication site.
ACFS-05003: must provide a primary mount point: Cause: The mount point on the replication primary site for the file system to be replicated was not provided.; Action: Provide an existing mount point on the primary site for the file system to be replicated.
ACFS-05004: cannot allocate a list of tag names: Cause: A request for process virtual memory failed. This message is accompanied by other message(s) providing details on the error.; Action: Correct the problem indicated by the other message(s). If possible, change options to reduce required memory and/or take steps to increase memory available to the process. Otherwise, report this error to Oracle Support Services.
ACFS-05005: invalid tag name: string: Cause: User specified a tag name that has incorrect syntax.; Action: See the platform specific Oracle documentation for correct syntax for ACFS tag names.
ACFS-05006: unable to initialize replication process data structures: Cause: Failed to determine path names for replication directories.; Action: Verify the specified mount point is an ACFS file system.
ACFS-05007: cannot initialize interrupt signal handler: Cause: The system could not initialize the mechanism to handle interrupts.; Action: Contact Oracle Support Services.
ACFS-05008: cannot lock file string to serialize ACFS replication commands: Cause: Failed to open and lock the specified file. This message accompanied by other message(s) providing details on the error.; Action: Correct the problem indicated by the other message(s). If the cause of the problem is unclear, contact Oracle Support Services.
ACFS-05009: ACFS replication initialization is already in progress.: Cause: Initialization was in progress on the replication site.; Action: Wait for the other initialization on replication site to complete.
ACFS-05010: ACFS replication initialization is still in progress.: Cause: The command cannot be run until replication initialization completes.; Action: Monitor initialization progress with the 'acfsutil repl info' command.
ACFS-05011: cannot open directory: string: Cause: Failed to open the specified directory. This message is accompanied by other message(s) providing details on the error.; Action: Correct the problem indicated by the other message(s). If the cause of the problem is unclear, contact Oracle Support Services.
ACFS-05012: ACFS replication is already initialized.: Cause: ACFS replication has already been initialized on this system.; Action: Initialization cannot be undone unless replication is terminated or the file system is reformatted.
ACFS-05013: ACFS replication cannot be initialized.: Cause: This message is accompanied by other message(s) providing details on the error.; Action: Correct the problem indicated by the other message(s). If the cause of the problem is unclear, contact Oracle Support Services.
ACFS-05014: cannot verify replication configuration: Cause: This message is accompanied by other message(s) providing details on the error.; Action: Correct the problem indicated by the other message(s). If the cause of the problem is unclear, contact Oracle Support Services.
ACFS-05015: cannot cleanup replication directories: Cause: The application failed to cleanup from a previous replication instantiation.; Action: Verify user permissions and that the replication directory is available.
ACFS-05016: cannot update replication configuration with new trace level: Cause: The application was unable to communicate with the ACFS driver.; Action: Verify that the ADVM/ACFS drivers are loaded and running.
ACFS-05017: cannot create file: string: Cause: The application failed to create the specified file. This message is accompanied by other message(s) providing details on the error.; Action: Correct the problem indicated by the other message(s). If the solution is not clear, contact Oracle Support Services.
ACFS-05018: cannot get primary ADVM volume information for string: Cause: The application failed to get the ADVM volume path for the mounted ACFS file system.; Action: Verify that the file system is mounted and of type ACFS.
ACFS-05019: cannot allocate space for the ADVM volume path: Cause: A request for process virtual memory failed. This message is accompanied by other message(s) providing details on the error.; Action: Correct the problem indicated by the other message(s). If possible, change options to reduce required memory and/or take steps to increase memory available to the process. Otherwise, report this error to Oracle Support Services.
ACFS-05020: cannot start replication daemons: Cause: CRS has failed to start the replication daemons.; Action: Verify that CRS is running. Check the CRS logs to determine why the replication daemons failed to start.
ACFS-05021: cannot stop replication daemons: Cause: CRS has failed to stop the replication daemons.; Action: Verify that CRS is running. Check the CRS logs to determine why the replication daemons failed to stop.
ACFS-05022: internal CRS error: Cause: The application failed to initialize communication with CRS.; Action: Verify that CRS is running. Check the CRS logs to determine why the replication daemons failed to start.
ACFS-05023: error checking for file: string: Cause: Informational; Action: None
ACFS-05024: The standby replication site is initialized. ACFS replication will begin.: Cause: Informational; Action: None
ACFS-05025: waiting for the standby replication site to initialize: Cause: Informational; Action: None
ACFS-05026: caught interrupt; ACFS replication initialization is shutting down.: Cause: Informational; Action: None
ACFS-05027: cannot remove file: string: Cause: File system was not accessible.; Action: Verify the ASM instance is operational and the state of the file system using 'acfsutil info fs' before retrying the command.
ACFS-05028: cannot obtain current time for events log: Cause: The application failed to get the current time for logging.; Action: Contact Oracle Support Services.
ACFS-05029: cannot write to the events log: Cause: The application failed to write to the specified file. This message is accompanied by other message(s) providing details on the error.; Action: Correct the problem indicated by the other message(s). If the solution is not clear, contact Oracle Support Services.
ACFS-05030: cannot clean up configuration file: Cause: Initialization failed and the configuration file created during failed initialization could not be removed.; Action: Contact Oracle Support Services.
ACFS-05031: standby file system is not empty: Cause: The file system was not empty.; Action: Use an empty standby file system; either reformat the file system or remove all files and directories under standby mount point/.
ACFS-05032: unable to determine user permissions: Cause: An error occurred attempting to acquire the user permissions. This message is accompanied by other message(s) providing details on the error.; Action: Correct the problem indicated by the other message(s). Otherwise, report this error to Oracle Support Services.
ACFS-05033: must provide a standby mount point: Cause: A mount point on the standby replication site was not provided.; Action: Provide an existing mount point with an empty file system on the standby replication site.
ACFS-05034: cannot obtain path for directory: string: Cause: The application failed to locate the specified directory.; Action: Verify that the replication directory is available.
ACFS-05035: cannot open file for write: string: Cause: The application failed to open the specified file. This message is accompanied by other message(s) providing details on the error.; Action: Correct the problem indicated by the other message(s). If the solution is not clear, contact Oracle Support Services.
ACFS-05036: cannot write to file: string: Cause: The application failed to write to the specified file. This message is accompanied by other message(s) providing details on the error.; Action: Correct the problem indicated by the other message(s). If the solution is not clear, contact Oracle Support Services.
ACFS-05037: cannot move file string to directory string: Cause: The application failed move the specified file.; Action: Verify that the replication directory is available.
ACFS-05038: cannot register Oracle Net service name: Cause: Unable to register the Oracle Net service name with the ASM instance.; Action: Verify the ASM instance is operational and the state of the file system using 'acfsutil info fs' before retrying the command.
ACFS-05039: cannot unregister Oracle Net service name: Cause: Unable to unregister the Oracle Net service name from the ASM instance.; Action: Verify the ASM instance is operational and the state of the file system using 'acfsutil info fs' before retrying the command.
ACFS-05040: cannot obtain Oracle Net service name from alias provided: Cause: Unable obtain the Oracle Net service name from the Oracle Net alias provided on the command line.; Action: Verify that the Oracle Net alias exists and is properly formed.
ACFS-05041: Oracle Net service name is greater than number bytes: Cause: The Oracle Net service name specified for replication is greater than the maximum allowed.; Action: Reduce the size of the Oracle Net service name being used for replication.
ACFS-05042: insufficient privileges to perform replication command. Administrator access is required.: Cause: The caller does not have sufficient privileges to perform the replication command.; Action: Execute the replication command from a user with administrator access.
ACFS-05043: insufficient privileges to perform replication command. ASM administrator group access is required.: Cause: The caller does not have sufficient privileges to perform the replication command.; Action: Execute the replication command from a user with ASM administrator group access.
ACFS-05044: cannot obtain node name: Cause: Unable to get local node name through CRS.; Action: Verify that CRS is running.
ACFS-05045: invalid interval specified for replication statistics: Cause: The caller specified an invalid time interval for replication statistics.; Action: Verify the syntax of the time interval using 'acfsutil repl info' help flag and retry.
ACFS-05046: invalid date range specified for replication statistics: Cause: The caller specified an invalid date range for replication statistics.; Action: Verify the syntax of the date range using 'acfsutil repl info' help flag and retry.
ACFS-05047: time specified is in the future: Cause: The caller specified a date in the future.; Action: Verify the time specified is before the current time.
ACFS-05048: start time specified is newer than the end time specified: Cause: The caller specified a date range where the start time was more recent the end time.; Action: Verify the start time is before the end time.
ACFS-05049: validating the remote connection: Cause: Informational; Action: None
ACFS-05050: remote connection cannot be established: Cause: The user name, password, or Oracle Net alias used to connect to the remote site was not correct or the remote site was unreachable.; Action: Verify the connection information is correct and the status of the remote site.
ACFS-05051: remote connection has been established: Cause: Informational; Action: None
ACFS-05052: standby replication site requires reinitialization: Cause: Initialization was unable to complete on the primary replication site and left the standby replication site in an indeterminate state.; Action: On the standby replication site, run 'acfsutil repl terminate' and 'acfsutil repl init' before retrying initialization on the the primary replication site.
ACFS-05053: replication's Oracle Net service name conflicts with the existing ASM service name: Cause: The service name for replication specified in the Oracle Net alias conflicts eith the Oracle Net service name that ASM uses.; Action: Review the Oracle Net alias for replication in tnsnames.ora and use a different service name for the replication alias.
ACFS-05054: standby replication file system is mounted on more than one cluster node: Cause: The standby replication file system was mounted on more than one node in the cluster.; Action: Unmount the file system on all but one node on the standby replication site and retry the initialization.
ACFS-05055: invalid connection string for the primary replication site: Cause: The user name, password, or Oracle Net alias used to connect to the primary replication site was not correct or was unreachable.; Action: Verify the connection information is correct and the status of the primary replication site.
ACFS-05056: invalid connection string for the standby replication site: Cause: The user name, password, or Oracle Net alias used to connect to the standby replication site was not correct or was unreachable.; Action: Verify the connection information is correct and the status of the standby replication site.
ACFS-05058: command issued on the incorrect replication site: Cause: The command was issued on the incorrect replication site.; Action: Verify the command syntax. If issued on the primary file system, reissue on the standby file system. If issued on the standby file system, reissue on the primary file system.
ACFS-05059: ACFS replication not initialized: Cause: ACFS replication information cannot be retrieved as replication has not been initialized.; Action: None
ACFS-05060: waiting for ACFS replication to terminate: Cause: Informational; Action: None
ACFS-05061: ACFS replication command interrupted: Cause: Informational; Action: None
ACFS-05062: cannot query CRS resource: Cause: The application failed to communicate with CRS.; Action: Verify that CRS is running. Check the CRS logs to determine why the CRS resource is not responding.
ACFS-05063: cannot relocate CRS resource: Cause: The application failed to relocate CRS resource.; Action: Verify that CRS is running. Check the CRS logs to determine why the CRS resource cannot be relocated.
ACFS-05064: the service name 'string' is not registered on the standby site: Cause: Possible causes include: 1.) Replication was not initialized on the standby site. 2.) Mismatched service names. If the -c option is not used, the service name specified in the alias for the standby file system did not match the service name specified for the primary file system in the alias on the standby site. 3.) The alias for the standby site referred to the wrong set of nodes.; Action: Possible actions include: 1.) Verify replication is initialized on the standby site. 2.) Verify the service name used to connect to the standby site matches the one registered on the standby site. Run 'lsnrctl status' on the standby site to verify. 3.) Verify that the nodes listed in the standby alias have the standby file system mounted.
ACFS-05065: cannot transfer files to the standby file system 'string': Cause: Possible causes include: 1.) The standby mount point did not exist or was not an ACFS file system. 2.) The standby file system was full.; Action: Possible actions include: 1.) Verify that the standby mount point exists and is an ACFS file system. 2.) Verify that there is free space on the standby file system.
ACFS-05066: ACFS replication is already paused: Cause: ACFS replication was paused by a previous call.; Action: None
ACFS-05067: cannot rename file string to string in directory string: Cause: The application failed to rename the specified file.; Action: Verify that the replication directory is available.
ACFS-05068: ACFS replication has not been paused: Cause: ACFS replication was not paused. Resume operation is not needed.; Action: None
ACFS-05069: ACFS replication update must specify at least one attribute: Cause: The command to update the replication configuration did not specify any attributes to update.; Action: Specify at least one replication attribute to be updated.
ACFS-05070: command must be run on the primary replication site: Cause: 'acfsutil repl update' command was not run on the primary replication site.; Action: Execute 'acfsutil repl update' on the primary replication site.
ACFS-05071: invalid username or password used to connect to the standby site: Cause: The username or password specified on the command line or in the wallet was incorrect.; Action: Verify the username and password are correct when connecting to the standby site.
ACFS-05072: cannot open events file string: Cause: Failed to open events log file.; Action: Verify the ASM instance is operational and the state of the file system using 'acfsutil info fs' before retrying the command.
ACFS-05073: cannot query events log file: Cause: Failed to query events log file.; Action: Verify the ASM instance is operational and the state of the file system using 'acfsutil info fs' before retrying the command.
ACFS-05075: cannot terminate replication: Cause: Failed to terminate replication.; Action: Verify the ASM instance is operational and the state of the file system using 'acfsutil info fs' before retrying the command.
ACFS-05076: unable to determine CRS user/group: Cause: The application failed to determine CRS user and/or group.; Action: Verify that CRS is running. Check the CRS logs to determine why the CRS user and/or group cannot be determined.
ACFS-05077: could not complete replication synchronization: Cause: Failed to complete synchronization of primary and standby replication sites.; Action: Verify the ASM instance is operational and the state of the file system using 'acfsutil info fs' before retrying the command.
ACFS-05078: failed to synchronize primary and standby replication sites: Cause: Failed to synchronize replication sites.; Action: Verify the ASM instance is operational and the state of the file system using 'acfsutil info fs' before retrying the command.
ACFS-05079: waiting for replication update to complete: Cause: Informational; Action: None
ACFS-05083: Initialization of the primary file system could not complete because the standby is already configured for replication.: Cause: The standby file system was not expecting initialization data from this primary. Possible causes include: 1. Stale replication state detected on standby file system from a previous instantiation. 2. An incorrect replication standby site was supplied. 3. An incorrect replication standby file system was supplied.; Action: 1. Run 'acfsutil repl terminate' on the standby site for the standby file system before retrying the initialization of the primary. 2. Verify the correct standby site is used. 3. Verify the correct standby file system is used.
ACFS-05084: The replication standby file system has been newly initialized and is refusing files from the primary. The primary may need to be terminated and newly initialized.: Cause: The standby file system was not expecting any data from the primary except initialization data. A possible cause may be the standby file system was terminated and newly initialized, but the primary was not.; Action: Verify the primary site and primary file system. Run 'acfsutil repl terminate' on the primary site for the primary file system before retrying the initialization of the standby.
ACFS-05085: cannot start replication because incompatible ACFS features already exist: Cause: An attempt to initialize replication was rejected because the file system was in a state incompatible with replication. Possible causes include: 1. The file system was not formatted with 512-byte metadata blocks, the file system was compressed, or the file system contains fshares. 2. The file system was frozen.; Action: If the file system was frozen, run 'acfsutil thaw mount-point' and then retry the operation. Otherwise, migration to newer replication infrastructure must be performed. Refer to the Oracle Product Documentation for more information.
ACFS-05086: listener is not running on the standby site: Cause: The listener was not started on the remote site or an incorrect node name was specified in the standby alias definition.; Action: Verify the listener is started on the standby site. Check that the standby alias contains the correct node names.
ACFS-05087: The event log does not cover the time range specifed.: Cause: The events log did not cover any portion of the time range specified in the command.; Action: Change the time range or use an events log that covers the range specified.
ACFS-05088: replicated file system size is below the minimum of stringG: Cause: An attempt was made to initialize replication on a file system that did not have sufficient space.; Action: Resize the file system to at least the minimum size specified.
ACFS-05089: replication statistics cannot be queried on the standby site: Cause: An attempt was made to query the replication statistics on the standby site.; Action: Query the replication statistics from the primary site.
ACFS-05090: interval is greater than number years: Cause: The interval specified was greater than the maximum allowed.; Action: Retry the command with a lower interval value.
ACFS-05091: The mount path specified exceeds the maximum length allowed on this platform.: Cause: The specified mount path exceeded the maximum length on this platform.; Action: Use a valid mount path.
ACFS-05092: replicated file system free space is near the minimum threshold of numberGB per active node, continuing with initialization: Cause: Initialization of replication was issued on a file system that is near the minimum threshold of free space.; Action: Consider resizing the file system to allow for optimal replication performance.
ACFS-05093: could not retrieve active node count on file system: string, error: number: Cause: Could not get the number of nodes active on the specified file system.; Action: Verify at least one cluster node has the file system mounted, or address the specified operating system dependent error code provided. If the solution is not clear, contact Oracle Support Services.
ACFS-05094: replicated file system free space is below the minimum of numberGB per active node, actual free space left: numberGB: Cause: An attempt was made to initialize replication on a file system that did not have sufficient space.; Action: Resize the file system such that free space is at least the minimum size specified.
ACFS-05159: Last sync time with primary: string: Cause: Informational; Action: None
ACFS-05170: Cannot initialize replication while the cluster is in rolling migration: Cause: An attempt to initialize replication was rejected because the cluster was in rolling migration. Replication initialization is not allowed during rolling migration.; Action: Complete the rolling migration and then initialize replication.
ACFS-05171: Cannot terminate replication while the cluster is in rolling migration: Cause: An attempt to terminate replication was rejected because the cluster was in rolling migration and the file system was mounted on more than one node.; Action: Either complete the rolling migration and then terminate replication, or unmount this file system on the other nodes and then terminate replication.
ACFS-05172: Replication cannot be terminated because background processes are not running.: Cause: Replication background processes were stopped and cannot finish processing replication data.; Action: Run 'acfsutil repl bg start mountpoint' to restart replication background processes and complete the apply of existing replication data, or run 'acfsutil repl terminate standby immediate mountpoint' to terminate replication immediately without applying the remaining replication data.
ACFS-05200: Stopping ACFS replication daemons on string: Cause: Informational; Action: None
ACFS-05201: Starting ACFS replication daemons on string: Cause: Informational; Action: None
ACFS-05202: ACFS replication daemons started successfully on string: Cause: Informational; Action: None
ACFS-05203: ACFS replication daemons stopped successfully on string: Cause: Informational; Action: None
ACFS-05204: Attempting to restart replication daemons on string: Cause: Informational; Action: None
ACFS-05205: Failed to initialize replication because ACFS Security is in use on the standby file system 'string'.: Cause: ACFS replication initialization failed on the standby file system because ACFS Security was in use on the file system.; Action: If you are sure you want to use the indicated file system as standby, reformat the standby file system and retry the command.
ACFS-05206: Failed to initialize replication on ACFS Security enabled file system 'string' because ACFS Security is not initialized on the standby site.: Cause: Replication initialization failed on ACFS Security enabled primary file system because ACFS Security was not initialized on the standby site.; Action: There are two possible options based on user's preference. 1. If ACFS Security is desired on primary and standby file systems, follow the below mentioned steps in sequence: a. Terminate replication on standby file system by executing 'acfsutil repl terminate' command. b. Initialize ACFS Security on standby site by executing 'acfsutil sec init' command. c. Reinitialize replication on standby file system by executing 'acfsutil repl init' command. d. Retry 'acfsutil repl init' command on the primary file system. 2. If ACFS Security is not desired on primary and standby file systems, follow the below mentioned steps in sequence: a. Terminate replication on standby file system by executing 'acfsutil repl terminate' command. b. Remove ACFS Security on primary file system by using 'acfsutil sec prepare' command. c. Reinitialize replication on standby file system by executing 'acfsutil repl init' command. d. Retry 'acfsutil repl init' command on the primary file system.
ACFS-05207: A request to initialize replication failed because the primary replication file system is enabled for ACFS Security and standby site is not initialized for ACFS Security.: Cause: A request to initialize replication failed because the primary replication file system was enabled for ACFS Security and standby site was not initialized for ACFS Security.; Action: There are two possible options based on user's preference. 1. If ACFS Security is desired on primary and standby file systems, follow the below mentioned steps in sequence: a. Terminate replication on standby file system by executing 'acfsutil repl terminate' command. b. Initialize ACFS Security on standby site by executing 'acfsutil sec init' command. c. Reinitialize replication on standby file system by executing 'acfsutil repl init' command. d. Retry 'acfsutil repl init' command on the primary file system. 2. If ACFS Security is not desired on primary and standby file systems, follow below mentioned steps in sequence: a. Terminate replication on standby file system by executing 'acfsutil repl terminate' command. b. Remove ACFS Security on primary file system by using 'acfsutil sec prepare' command. c. Reinitialize replication on standby file system by executing 'acfsutil repl init' command. d. Retry 'acfsutil repl init' command on the primary file system.
ACFS-05208: A request to initialize replication failed because the primary replication file system is enabled for ACFS Encryption and standby site has PKCS wallet.: Cause: Replication initialization failed because the use of PKCS wallet for an ACFS Replication standby site is not supported.; Action: There are two possible options based on user's preference. 1. If ACFS Encryption is desired on primary and standby file systems a. Terminate replication on standby file system by executing 'acfsutil repl terminate' command. b. Convert the PKCS wallet to SSO wallet on standby by executing 'acfsutil keystore migrate' command. c. Reinitialize replication on standby file system by executing 'acfsutil repl init' command. d. Retry 'acfsutil repl init' command on the primary file system. 2. If ACFS Encryption is not desired on primary and standby file systems a. Terminate replication on stanby filesystem by executing 'acfsutil repl terminate' command. b. Remove ACFS Encryption on primary filesystem by using 'acfsutil encr set' command. c. Reinitialize replication on standby file system by executing 'acfsutil repl init' command. d. Retry 'acfsutil repl init' command on the primary file system.
ACFS-05209: A request to initialize replication failed because the primary replication file system is enabled for ACFS Encryption and an error occurred in accessing OCR at standby site.: Cause: Internal error.; Action: Contact Oracle Support Services.
ACFS-05210: Failed to initialize replication because ACFS Encryption is in use on the standby file system 'string'.: Cause: ACFS replication initialization failed on the standby file system because ACFS Encryption was in use on the file system.; Action: If you are sure you want to use the indicated file system as standby, reformat the standby file system to remove encryption and retry the command.
ACFS-05211: Failed to initialize replication on ACFS Encryption enabled file system 'string' because PKCS wallet existed on standby site.: Cause: Replication initialization failed because the use of PKCS wallet for an ACFS Replication standby site is not supported.; Action: There are two possible options based on user's preference. 1. If ACFS Encryption is desired on primary and standby file systems a. Terminate replication on standby file system by executing 'acfsutil repl terminate' command. b. Convert the PKCS wallet to SSO wallet on standby by executing 'acfsutil keystore migrate' command. c. Reinitialize replication on standby file system by executing 'acfsutil repl init' command. d. Retry 'acfsutil repl init' command on the primary file system. 2. If ACFS Encryption is not desired on primary and standby file systems a. Terminate replication on stanby filesystem by executing 'acfsutil repl terminate' command. b. Remove ACFS Encryption on primary filesystem by using 'acfsutil encr set' command. c. Reinitialize replication on standby file system by executing 'acfsutil repl init' command. d. Retry 'acfsutil repl init' command on the primary file system.
ACFS-05212: Failed to initialize replication on ACFS Encryption enabled file system 'string' because an error occurred in accessing the OCR at standby site.: Cause: Internal error.; Action: Contact Oracle Support Services.
ACFS-05214: Failed to prepare ACFS Security on replication enabled file system 'string' because ACFS Security is not initialized on the standby site.: Cause: An attempt to prepare ACFS Security on replication enabled file system failed because ACFS Security was not initialized on the standby site.; Action: Initialize ACFS Security on the standby site by executing the 'acfsutil sec init' command and retry the operation.
ACFS-05216: Failed to set ACFS encryption on a replication enabled file system 'string' because PKCS wallet is not supported as ACFS encryption key store on standby site.: Cause: An attempt to set ACFS encryption on replication enabled file system failed because the standby site was having a PKCS wallet as ACFS encryption key store.; Action: If ACFS encryption is desired on primary and standby file systems follow the steps mentioned below in sequence: a. Convert the PKCS wallet to SSO wallet on standby site by executing the 'acfsutil keystore migrate' command. b. Retry the 'acfsutil encr set' command.
ACFS-05217: Failed to set ACFS Encryption on replication enabled file system 'string' because an error occurred accessing the OCR at standby site.: Cause: Internal error.; Action: Contact Oracle Support Services.
ACFS-05218: Cannot proceed because another conflicting 'acfsutil' command is in progress.: Cause: The command could not proceed because one of the following 'acfsutil' commands was in progress in the cluster. a. 'acfsutil repl init' b. 'acfsutil sec prepare' c. 'acfsutil encr set' d. 'acfsutil audit enable'; Action: Retry the command after some time.
ACFS-05219: Cannot proceed because CRS stack is not up.: Cause: The command could not proceed because CRS stack was not up.; Action: Verify that Cluster Ready Services (CRS) stack is up by executing 'crsctl check crs' and Cluster Synchronization Services (CSS) is running by executing 'crsctl check css'. If the CRS stack is not up or the CSS is not running, check with the CRS administrator to bring it up. If it does not resolve the problem, contact Oracle Support Services.
ACFS-05220: Cannot proceed because ACFS replication initialization is in progress.: Cause: The command could not proceed because ACFS replication initialization was in progress.; Action: Verify that the ACFS replication initialization is complete by executing 'acfsutil repl info' and retry.
ACFS-05221: Failed to prepare ACFS Security on a replication enabled file system 'string' because ACFS audit is not initialized on the standby site.: Cause: An attempt to prepare ACFS Security on a replication enabled file system failed because ACFS Audit was not initialized on the standby site.; Action: Initialize ACFS Audit on the standby site by executing the 'acfsutil audit init' command and retry the operation.
ACFS-05222: Failed to initialize replication on ACFS Audit prepared filesystem string because ACFS Audit is not initialized on the standby site.: Cause: Replication initialization failed on an ACFS Audit prepared primary file system because ACFS Audit was not initialized on the standby site.; Action: If ACFS Audit is desired on primary and the standby file systems, follow the steps mentioned below in sequence: a. Terminate replication on the standby file system by executing 'acfsutil repl terminate' command. b. Initialize ACFS Audit on the standby site by executing 'acfsutil audit init' command. c. Reinitialize replication on the standby file system by executing 'acfsutil repl init' command. d. Retry 'acfsutil repl init' command on the primary file system.
ACFS-05223: Failed to prepare ACFS Audit on replication enabled file system 'string' because ACFS audit is not initialized on the standby site.: Cause: An attempt to prepare ACFS Audit on a replication enabled file system failed because ACFS Audit was not initialized on the standby site.; Action: Initialize ACFS Audit on the standby site by executing the 'acfsutil audit init' command and retry the operation.
ACFS-05224: Failed to prepare ACFS Audit on replication enabled file system 'string' because an error occurred accessing the OCR at standby site.: Cause: Internal error.; Action: Contact Oracle Support Services.
ACFS-05226: Failed to set ACFS Encryption on a replication enabled file system 'string' because ACFS audit is not initialized on the standby site; moreover, PKCS wallet is not supported as ACFS Encryption key store on the standby site.: Cause: In ACFS Audit initialized cluster, an attempt to set ACFS Encryption on replication enabled filesystem failed because standby site is not ACFS audit initailized and PKCS wallet is not supported as ACFS Encryption key store on the standby site.; Action: follow the steps mentioned below in sequence. a. Initialize ACFS Audit on the standby site by executing 'acfsutil audit init' command. b. Convert the PKCS wallet to SSO wallet on standby by executing 'acfsutil keystore migrate' command. c. Retry command 'acfsutil repl init' on the primary site.
ACFS-05227: Failed to set ACFS Security on a replication enabled file system 'string' because ACFS Security is not initialized on the standby site; moreover, ACFS Audit is not initialized on standby site.: Cause: In an ACFS Audit initialized cluster, an attempt to prepare ACFS Security on a replication enabled filesystem failed because the standby site was neither Audit initialized nor Security initialized.; Action: follow the steps mentioned below in sequence. a. Initialize ACFS Audit on the standby site by executing 'acfsutil audit init' command. b. Initialize ACFS Security on the standby site by executing 'acfsutil sec init' command. c. Retry command 'acfsutil repl init' on the primary site.
ACFS-05228: Failed to set ACFS Encryption on a replication enabled file system 'string' because ACFS audit is not initialized on the standby site.: Cause: An attempt to set ACFS Encryption on a replication enabled file system failed because ACFS Audit was not initialized on the standby site.; Action: Initialize ACFS Audit on the standby site by executing the 'acfsutil audit init' command and retry the operation.
ACFS-05229: Failed to prepare ACFS Security on replication enabled file system 'string' because an error occurred accessing the OCR at the standby site.: Cause: Internal error.; Action: Contact Oracle Support Services.
ACFS-05230: Failed to get standby site's encryption state.: Cause: An attempt to get standby site's encryption status failed because standby site was unreachable.; Action: Verify the status of remote site and retry the command.
ACFS-05231: Failed to get standby site's security state.: Cause: An attempt to get standby site's security status failed because standby site was unreachable.; Action: Verify the status of remote site and retry the command.
ACFS-05232: Failed to get standby site's audit state.: Cause: An attempt to get standby site's audit status failed because standby site was unreachable.; Action: Verify the status of remote site and retry the command.
ACFS-05233: Cannot prepare a file system for ACFS Security while the cluster is in rolling migration.: Cause: An attempt to prepare a file system for ACFS Security was rejected because the cluster was in rolling migration. ACFS Security prepare operation is not allowed during rolling migration.; Action: Complete the rolling migration and retry the command.
ACFS-05234: Cannot set ACFS Encryption parameters while the cluster is in rolling migration.: Cause: An attempt to set ACFS Encryption parameters was rejected because the cluster was in rolling migration. ACFS Encryption set operation is not allowed during rolling migration.; Action: Complete the rolling migration and retry the command.
ACFS-05235: Cannot enable ACFS Audit while the cluster is in rolling migration.: Cause: An attempt to enable ACFS Audit was rejected because the cluster was in rolling migration. ACFS Audit enable operation is not allowed during rolling migration.; Action: Complete the rolling migration and retry the command.
ACFS-05236: Snapshot cannot serve as replication standby for primary with security enabled.: Cause: An attempt to initialize ACFS replication was rejected because a snapshot was specified as the replication standby site for a primary file system with ACFS security enabled.; Action: Retry initializing ACFS replication either: 1. specifying a file system (not a snapshot) as the standby site, or 2. after first disabling ACFS security on the primary file system.
ACFS-05237: Snapshot cannot serve as replication standby for primary with encryption enabled.: Cause: An attempt to initialize ACFS replication was rejected because a snapshot was specified as the replication standby site for a primary file system with ACFS encryption enabled.; Action: Retry initializing ACFS replication either: 1. specifying a file system (not a snapshot) as the standby site, or 2. after first disabling ACFS encryption on the primary file system.
ACFS-05238: Snapshot cannot serve as replication standby for primary with audit enabled.: Cause: An attempt to initialize ACFS replication was rejected because a snapshot was specified as the replication standby site for a primary file system with ACFS audit enabled.; Action: Retry initializing ACFS replication either: 1. specifying a file system (not a snapshot) as the standby site, or 2. after first disabling ACFS audit on the primary file system.
ACFS-05239: Failed to prepare ACFS Security on replication enabled file system 'string'.: Cause: An attempt to prepare security on replication enabled file system because ACFS security is not supported on primary file systems when the standby site is a snapshot.; Action: Retry the command after reinitializing replication using a file system (not a snapshot) as the standby site.
ACFS-05240: Failed to set ACFS Encryption on replication enabled file system 'string'.: Cause: An attempt to set encryption on the indicated replication enabled file system because ACFS encryption was not supported where the standby site is a snapshot.; Action: Retry the command after reinitializing replication using a file system (not a snapshot) as the standby site.
ACFS-05241: Failed to enable ACFS Audit on replication enabled file system 'string'.: Cause: An attempt to enable ACFS audit on a replication enabled file system failed because ACFS Audit is not supported when replication is in use.; Action: Retry the command after terminating replication.
ACFS-05242: Snapshot creation failed for file system with ACFS Security enabled.: Cause: An attempt to create a snapshot using the command 'snap dup create' was rejected because the file system had ACFS Security enabled. Snapshots were not supported for file systems with security enabled.; Action: Retry after disabling ACFS Security using 'sec prepare -u' on the file system.
ACFS-05243: Snapshot creation failed for file system with ACFS Encryption enabled.: Cause: An attempt to create a snapshot using the command 'snap dup create' was rejected because the file system had ACFS Encryption enabled. Snapshots were not supported for file systems with encryption enabled.; Action: Retry after disabling ACFS Encryption using 'encr set -u' on the file system.
ACFS-05244: The operation failed because ACFS Security and/or Audit is enabled for the file system.: Cause: An attempt to run the command was rejected because the file system has ACFS Security or ACFS Audit enabled.; Action: If possible, retry after ensuring that ACFS Security and ACFS Audit are disabled for the file system.
ACFS-05245: The operation failed because ACFS Security, Audit or Encryption is enabled for the file system.: Cause: An attempt to run the command was rejected because the file system has ACFS Security, ACFS Audit or ACFS Encryption enabled.; Action: If possible, retry after ensuring that ACFS Security, ACFS Audit and ACFS Encryption are disabled for the file system.
ACFS-05246: cannot start the replication daemon for string: Cause: CRS has failed to start the replication daemon.; Action: Verify that CRS is running. Check the CRS logs to determine why the replication daemon failed to start.
ACFS-05247: cannot stop the replication daemon for string: Cause: CRS has failed to stop the replication daemon.; Action: Verify that CRS is running. Check the CRS logs to determine why the replication daemon failed to stop.
ACFS-05354: Clock difference detected between primary and standby replication sites.: Cause: A difference in the system clocks has been detected between the primary and standby replication sites.; Action: Update the time on the primary and standby replication sites to match, and reissue the 'acfsutil repl info -s' command with a new time interval.
ACFS-05356: The Oracle Local Registry, OLR, cannot be accessed to query the software version.: Cause: The OLR is not accessible or is not configured correctly.; Action: Run 'ocrcheck -local' to verify the OLR is accessible and working properly.
ACFS-05500: ACFS replication error. Contact Oracle Support Services. string: Cause: An ACFS replication operation failed.; Action: Contact Oracle Support Services.
ACFS-05501: ACFS replication error. Customer action required. string: Cause: This message is accompanied by other message(s) providing details on the error.; Action: Correct the problem indicated by the other message(s) immediately. If the cause of the problem is unclear, contact Oracle Support Services.
ACFS-05502: ACFS replication error. System administration needed. string: Cause: This message is accompanied by other message(s) providing details on the error.; Action: The replication daemon(s) will try to correct this situation by moving to another node in the cluster, if available. The problem indicated by the other message(s) should be addressed as soon as possible for replication to continue without further error. If the cause of the problem is unclear, contact Oracle Support Services.
ACFS-05503: ACFS replication string daemon shutting down. string: Cause: This message is accompanied by other message(s) providing details on the error.; Action: Correct the problem indicated by the other message(s). If the cause of the problem is unclear, contact Oracle Support Services.
ACFS-05505: The standby replication file system is full.: Cause: The standby replication file system is out of space.; Action: Resize the standby file system or delete snapshots from the standby file system if any exist; otherwise, replication may not proceed.
ACFS-05506: The primary replication file system is full.: Cause: The primary replication file system is out of space.; Action: Delete unnecessary files from the primary file system to free up space, resize the primary file system, or delete snapshots from the primary if any exist; otherwise, replication may not proceed.
ACFS-05507: The standby replication site failed number times to transport replication files from host string.: Cause: The replication transport mechanism failed to transport files from the standby replication site.; Action: Make sure the replication transport daemon is running and that proper permissions are set on the replication file systems.
ACFS-05508: The primary replication site failed number times to transport replication files from host string.: Cause: The replication transport daemon failed to transfer files from the primary replication site.; Action: Make sure the replication transport daemon is running and that proper permissions are set on the replication file systems.
ACFS-05511: The standby replication site host, string, is experiencing number I/O errors.: Cause: I/O on the standby replication site failed.; Action: Verify the ASM instance is operational and the state of the file system using 'acfsutil info fs' before retrying the command.
ACFS-05512: The primary replication site host, string, has experienced number I/O errors.: Cause: I/O on the primary replication site failed.; Action: Verify the ASM instance is operational and the state of the file system using 'acfsutil info fs' before retrying the command.
ACFS-05513: replication monitor daemon has detected a problem: Cause: An error log file was received.; Action: Check the ACFS alert logs and 'acfsutil repl info' to determine the cause.
ACFS-05514: The replication monitor daemon has not received receipt or error files within the set threshold.: Cause: The time allowed for receiving receipt or error files has surpassed.; Action: Make sure all replication resources are running using 'acfsutil repl bg info' on both the primary and standby replication sites.
ACFS-05515: The replication monitor received an invalid receipt file and will not process it.: Cause: The receipt file that the replication monitor process received is not valid.; Action: Make sure proper permissions are set on the replication directories and that I/O requests can be processed.
ACFS-05516: The apply daemon failed to regenerate an apply file.: Cause: The apply daemon has requested more than the allowed number of regnerations on an apply file.; Action: Restart the file system replication resource using 'acfsutil repl bg start'.
ACFS-05517: ACFS replication on string: string: Cause: Informational; Action: None
ACFS-05518: string is not an ACFS mount point: Cause: The command required an ACFS mount point for execution.; Action: Retry the command using an ACFS mount point.
ACFS-05519: must provide an Oracle Net alias to the standby replication site: Cause: The Oracle Net alias, which is used to connect to the standby replication site, was not specified.; Action: Provide the Oracle Net alias to connect to the standby replication site.
ACFS-05520: cannot update replication configuration: Cause: The application was unable to communicate with the ACFS driver.; Action: Verify that the ADVM/ACFS drivers are loaded and running.
ACFS-05521: cannot initialize replication configuration: Cause: The application was unable to communicate with the ACFS driver.; Action: Verify that the ADVM/ACFS drivers are loaded and running.
ACFS-05522: Cannot terminate replication. Pending operations are unable to complete because the replication standby file system is full.: Cause: The standby replication file system is full and replication could not complete applying data before terminating.; Action: Resize the standby file system, delete snapshots from the standby file system if any exist, or use 'acfsutil repl terminate immediate' to force a terminate on the standby without applying any outstanding replication data. Any outstanding replication data will be lost if 'acfsutil repl terminate immediate' is issued.
ACFS-05523: The replication relationship for mount point 'string' must be restarted or upgraded.: Cause: ACFS replication activity determined that the indicated mount point was using outdated replication infrastructure. Release 12.2 introduced new ACFS replication infrastructure, and migration to the new infrastructure was required.; Action: The new replication infrastructure supports current and future functional and performance improvements. While replication continues to function for the indicated mount point, migration to the new infrastructure must be performed as soon as possible. One option is to terminate and restart replication. The other option is to use the 'acfsutil repl upgrade' suite of commands to migrate this use of replication without disturbing it. Refer to the Oracle product documentation for more information.
ACFS-05524: The replication relationship just initiated must be restarted or upgraded.: Cause: A replication relationship was initiated specifically using an outdated replication infrastructure. Release 12.2 introduced new ACFS replication infrastructure, and migration to the new infrastructure was required.; Action: The new replication infrastructure supports current and future functional and performance improvements. While replication will function for the relationship just initiated, migration to the new infrastructure must be performed as soon as possible. One option is to terminate and restart replication. The other option is to use the 'acfsutil repl upgrade' suite of commands to migrate this use of replication without disturbing it. Refer to the Oracle product documentation for more information.
ACFS-05525: File systems have replication enabled from a pre-12.2 release: string: Cause: Informational; Action: None
ACFS-05605: ACFS replication daemon string is exiting due to replication termination. string: Cause: Informational; Action: None
ACFS-05700: All the tag names specified during the "acfsutil repl init" operation must exactly match those specified on the command line.: Cause: Either at least one tag name was not specified during replication initialization or a specified tag name does not match that used during the "acfsutil repl init" operation.; Action: Use the exact tag names specified during the "acfsutil repl init" operation.
ACFS-05701: Comparing first tree (<<<) to second tree (>>>):: Cause: Informational; Action: None
ACFS-05702: Testing for extra files in the second tree.\nSecond tree (<<<) to first tree (>>>):: Cause: Informational; Action: None
ACFS-05703: Results for file comparison of first tree to second tree:: Cause: Informational; Action: None
ACFS-05704: Files successfully compared = number: Cause: Informational; Action: None
ACFS-05705: Files which failed comparison = number: Cause: Informational; Action: None
ACFS-05706: Results for extra files in the second tree:: Cause: Informational; Action: None
ACFS-05707: Total files checked = number: Cause: Informational; Action: None
ACFS-05708: Extra files found = number: Cause: Informational; Action: None
ACFS-05709: A status check on a file failed. Skipping file: string: Cause: Either the first tree is actively being modified or an internal error occurred.; Action: If possible, ensure the first tree is not changing while the tool is running.
ACFS-05710: ACFS tags do not support character devices. Skipping file: string: Cause: Informational; Action: None
ACFS-05711: ACFS tags do not support block devices. Skipping file: string: Cause: Informational; Action: None
ACFS-05712: ACFS tags do not support FIFOs. Skipping file: string: Cause: Informational; Action: None
ACFS-05713: ACFS tags do not support sockets. Skipping file: string: Cause: Informational; Action: None
ACFS-05714: <<< string\n>>> File missing!: Cause: The specified file was not found in the second tree.; Action: None
ACFS-05715: Found: string: Cause: The specified file is an extra file in the second tree.; Action: None
ACFS-05716: <<< Tag names exist on file string\n>>> No tag names exist on file string: Cause: The file in the first tree has tag names but the file in the second tree has no tag names.; Action: Tag names on files can be displayed with the "acfsutil tag info" command.
ACFS-05717: <<< Extended attribute mismatch for string\n>>> Extended attribute mismatch for string: Cause: Informational; Action: None
ACFS-05718: An unexpected result occurred while comparing the first tree to the second tree. Continuing. Affected files: string string: Cause: An unexpected result occurred while comparing the first tree to the second tree.; Action: None. The file was skipped.
ACFS-05719: An unexpected result occurred while comparing the second tree to the first tree. Continuing. Affected files: string string: Cause: An unexpected result occurred while comparing the second tree to the first tree.; Action: None. The file was skipped.
ACFS-05720: File type was not recognized. Continuing. Affected files "string" and "string": Cause: An unrecognized file type was encountered which will be ignored.; Action: Informational
ACFS-05721: Could not open the file specified for a checksum operation: string: Cause: Either the first tree was modified or an internal error occurred.; Action: If possible, do not modify files in the first tree when running this tool.
ACFS-05722: A file read failed during a checksum operation: string: Cause: Either the first tree was modified or an internal error occurred.; Action: If possible, do not modify files in the first tree when running this tool.
ACFS-05723: Unable to obtain security attributes on file "string": Cause: Check the access rights on the indicated file.; Action: Ensure the files security attributes can be read using a file manager.
ACFS-05724: Unable to convert a security descriptor to a string on file "string": Cause: The Windows security identifier (SID) may not be available on this system.; Action: Check the Windows SID is available on this host.
ACFS-05725: The replication user 'string' specified using the '-p' option does not match the replication user 'string' specified using the '-s' option.: Cause: An attempt to initialize replication on the primary was rejected because the replication user specified using the '-p' option does not match the replication user specified using the '-s' option.; Action: Reissue the 'acfsutil repl init primary' with a matching replication user for the '-p' and '-s' options. This user should also match the replication user specified with the 'acfsutil repl init standby' command using the '-u' option.
ACFS-05728: Failed to retrieve file system status information from a system call for mount point "string.": Cause: A system call for the status of the file system failed.; Action: Ensure the file system is accessible via "acfsutil info fs".
ACFS-05730: Mount point "string" does not support Oracle ACFS tagging.: Cause: The "-a" option was passed on the command line to compare ACFS tags. A file system being checked did not support ACFS tagging.; Action: Disable ACFS tag name comparison by omitting the "-a" option.
ACFS-05731: Mount point "string" does not support extended attributes, therefore, the ACFS tag name portion of the comparisons will not be performed.: Cause: Informational.; Action: None
ACFS-05732: The second tree does not exist: "string" .: Cause: Failed to access the specified second tree.; Action: Use a networked file system to provide access to the second tree on the primary node where the 'acfsutil repl compare' will be performed.
ACFS-05733: Successfully compared: string string: Cause: Informational.; Action: None
ACFS-05734: Successfully verified existence: string string: Cause: Informational.; Action: None
ACFS-05735: string contents not compared for symlink string: Cause: Informational.; Action: None
ACFS-05736: string symlink contents comparison failed: symlink=string, contents=string: Cause: Informational.; Action: None
ACFS-05737: string file attribute comparison failed: permissions=string, links=number, uid=number, gid=number, bytes=number, file: string: Cause: Informational.; Action: None
ACFS-05738: string file size or file contents comparison failed, file: string: Cause: Informational.; Action: None
ACFS-05739: string security descriptor comparison failed, file: string: Cause: Informational.; Action: None
ACFS-05740: string file type comparison failed, file: string: Cause: Informational.; Action: None
ACFS-05741: string file type comparison failed, directory: string: Cause: Informational.; Action: None
ACFS-05742: string file type comparison failed, soft link: string: Cause: Informational.; Action: None
ACFS-05743: string file type comparison failed, socket: string: Cause: Informational.; Action: None
ACFS-05744: string file type comparison failed, character device: string: Cause: Informational.; Action: None
ACFS-05745: string file type comparison failed, block device: string: Cause: Informational.; Action: None
ACFS-05746: string file type comparison failed, FIFO: string: Cause: Informational.; Action: None
ACFS-05747: Directory 'string' is a nested ACFS reparse point and was not included in the file system comparison.: Cause: Informational.; Action: None
ACFS-05748: The 'strings' option requires either the 'stringa' option or 'stringt' option.: Cause: An incorrect combination of options was specified.; Action: Combine the 's' option with either the 'a' option or 't' option.
ACFS-05749: The specified trees are the same and will not be compared.: Cause: The provided first and second trees resolved to the same location.; Action: Rerun the command specifying unique trees.
ACFS-05801: The primary replication file system string is at least number%% full.: Cause: Free space in the primary replication file system fell below a monitored threshold.; Action: Delete unnecessary files from the primary file system to free up space, resize the primary file system, or delete snapshots from the primary if any exist; otherwise, replication may not proceed.
ACFS-05802: The primary replication file system string has numberGB or less space available per active node.: Cause: The primary replication file system was found to be running low on space.; Action: Delete unnecessary files from the primary file system to free up space, resize the primary file system, or delete snapshots from the primary if any exist; otherwise, replication may not proceed.
ACFS-05803: The primary replication file system string has 2GB or less space available per active node. Replication is being terminated.: Cause: The primary replication file system was found to be too low on space in order to run efficiently.; Action: Restart replication with a larger primary file system that has free space equal to at least 4GB per active node.
ACFS-05804: The standby replication file system string is out of sync with the primary by at least number minutes.: Cause: The time period to process changes on the standby file system was exceeded.; Action: Check that the network connectivity between the primary and standby replication systems is functional.
ACFS-05805: The standby replication file system string is out of sync with the primary by at least 60 minutes.: Cause: The standby replication file system finished applying changes from the primary that were made more than 60 minutes ago. The standby is at least 60 minutes out of sync with the primary.; Action: Check that the network connectivity between the primary and standby replication systems is functional.
ACFS-05806: The primary replication file system string has reached an appropriate free space level.: Cause: A previously-reported free space shortage in the primary replication file system was relieved.; Action: None
ACFS-05807: The standby file system string is less than 15 minutes out of sync now.: Cause: A previously-reported out of sync time difference between the standby replication file system and the primary reached an appropriate out of sync time for replication to run efficiently.; Action: None
ACFS-05808: The primary replication file system string had an unrecoverable error and replication has been terminated for that file system.: Cause: The primary file system encountered an unrecoverable error in the kernel that has caused replication for this file system to be terminated. The cause will be in the Oracle Kernel Services (OKS) persistent log.; Action: Replication must be restarted. To do this, terminate replication on the standby file system, run mkfs (Unix or Linux) or acfsformat.exe (Windows) on the volume for the standby file system, remount that volume, and then restart replication for both file systems.
ACFS-05809: invalid query of replication apply events on the standby site: Cause: An attempt was made to query the replication apply events on the standby site which failed because the information is available only on the primary site.; Action: Query the replication apply events from the primary site.
ACFS-05810: invalid query of replication transport events on the standby site: Cause: An attempt was made to query the replication transport events on the standby site which failed because the information is available only on the primary site.; Action: Query the replication transport events from the primary site.
ACFS-05811: ACFS replication initialization failed in Oracle Restart environment.: Cause: Initialization failed because the system was configured with Oracle Restart. ACFS replication is not supported for Oracle Restart configurations.; Action: Initialize ACFS replication in an environment that is configured with single or multi-node RAC.
ACFS-05887: cannot cleanup snapshot directories: Cause: The 'acfsutil repl terminate' command failed to cleanup from a previous replication instantiation.; Action: Verify user permissions, that the snapshot directory is available, and then retry the command.
ACFS-05888: ACFS replication requires reinitialization of mount point string.: Cause: This file system has already been initialized with a different version of ACFS replication.; Action: Run 'acfsutil repl terminate' and retry the initialization.
ACFS-05889: a username and VIP name or username and hostname to the standby replication site was not provided: Cause: The username and VIP name or username and hostname used to connect to the standby replication site were not specified.; Action: Provide the username and VIP name or hostname to connect to the standby replication site.
ACFS-05890: a username for the standby replication site was not provided: Cause: The username on the standby replication site with which the primary replication site will connect and apply changes was not specified.; Action: Provide the username for connecting and applying changes to the standby replication site using the -u option.
ACFS-05891: username string used to connect to the standby site was rejected: Cause: The username specified on the command line was not found in the password database on the standby site.; Action: Verify the username is correct when connecting to the standby site.
ACFS-05892: Cannot terminate replication. Pending operations are unable to complete because the replication primary file system is full.: Cause: The primary replication file system was full and replication could not complete sending data before terminating.; Action: Resize the primary file system, or delete snapshots from the primary file system if they exist, and retry 'acfsutil repl terminate'.
ACFS-05893: cannot update the standby replication site: Cause: An attempt to update the standby replication site failed because an apply operation was in progress.; Action: Pause replication or stop the replication resource and try to update the standby replication site again.
ACFS-05894: invalid zero or negative integer replication interval: Cause: The value specified with the 'i' option was not an integer greater than zero.; Action: Specify the 'i' option with an integer value greater than zero.
ACFS-05895: missing time unit on interval ('stringi') option: Cause: A unit of time was not specified with the interval that was provided with the 'i' option.; Action: Append a unit from the set W (weeks), D (days), H (hours), M (minutes), S (seconds) to the interval specified.
ACFS-05896: invalid time unit in replication interval: Cause: An unrecognized unit was used following the interval length given with the 'i' option.; Action: Append a unit of time from the set W (weeks), D (days), H (hours), M (minutes), S (seconds) to the interval specified.
ACFS-05897: missing interval ('stringi') option: Cause: The 'acfsutil repl init primary' command was incomplete because a replication interval was not specified.; Action: Provide an interval when the primary is initialized. An interval can be set implicitly through the use of the '-C' option or explicitly through the argument passed to the '-i' option.
ACFS-05901: The specified tag name list exceeds the maximum of number characters.: Cause: The specified tag name list was too long.; Action: Remove some tag names and try the command again.
ACFS-05902: Snapshot string is read-only and cannot be modified.: Cause: A request to write to a snapshot was rejected because the snapshot was configured as read-only.; Action: Convert the snapshot to be read-write and retry.
ACFS-05903: unable to cleanup old snapshots: Cause: Informational.; Action: None
ACFS-05904: The base and target operating systems are not compatible.: Cause: An attempt to apply changes from a base file system to a target file system was rejected because one system was Unix or Linux and the other system was Windows.; Action: Ensure both systems are Unix or Linux or both systems are Windows.
ACFS-05905: Target file system or snapshot has been altered since the last 'snap duplicate apply'.: Cause: An attempt to apply changes from a base file system or snapshot to a target file system or snapshot was rejected because the target had previously been modified and was no longer in sync with the base file system or snapshot.; Action: Run the 'acfsutil snap remaster' command with the snap duplicate backup snapshot for the target file system or snapshot, in order to re-base the target to the backup snapshot contents.
ACFS-05906: The system containing the base or primary file system disconnected prematurely.: Cause: An attempt to apply changes from the base or primary file system to the target or standby file system could not be completed because connectivity to the system containing the base or primary file system was lost.; Action: Reestablish connectivity to the system containing the base or primary file system and then retry.
ACFS-05907: The ACFS file system mounted at path string is already running the latest version of replication.: Cause: A request to prepare an ACFS file system for replication upgrade was rejected because the file system is already running the latest version of replication.; Action: If the indicated ACFS file system was not the intended target for upgrade, reissue the command specifying the correct file system.
ACFS-05908: The replication upgrade control file string cannot be opened.: Cause: An attempt to open the replication upgrade control file failed.; Action: Run the 'acfsutil repl upgrade prepare' command to prepare the file system to be upgraded.
ACFS-05909: Snapshot string is not read only.: Cause: An attempt to use the 'snap duplicate create' command failed because the snapshot was writable.; Action: Re-create the snapshot as read only and retry the command.
ACFS-05910: The snapshot specified as the old snapshot by the stringi option is not older than the snapshot specified as the new snapshot.: Cause: An attempt to create a snap duplicate failed because the snapshot specified as the old snapshot by the 'i' option is not older than the snapshot specified as the new snapshot.; Action: Reverse the order of the two snapshot names or specify a different new or old snapshot and retry the command.
ACFS-05911: Target file system or snapshot has been altered since the start of the current 'snap duplicate apply'.: Cause: An attempt to apply changes from a base file system or snapshot to a target file system or snapshot was rejected because the target was modified while the apply attempt was in progress, and was no longer in sync with the base file system or snapshot.; Action: Run the 'acfsutil snap remaster' command with the snap duplicate backup snapshot for the target file system or snapshot, in order to re-base the target to the backup snapshot contents.
ACFS-05912: unable to perform 'snap duplicate' operation because ACFS replication is initialized on the file system: Cause: An attempt to use the 'acfsutil snap duplicate' command was rejected because ACFS replication was initialized on the file system.; Action: Terminate replication on the file system if appropriate by executing the 'acfsutil repl terminate' command and then retry the 'acfsutil snap duplicate' command.
ACFS-05913: unable to contact the standby node string: Cause: An attempt to use the ping utility to contact a standby node failed.; Action: Ensure that the correct host name or IP address was specified for the standby node, and that the standby node is operating normally. Then reissue the 'acfsutil repl init primary' command.
ACFS-05914: user string on node string unable to log in via 'ssh' to node string as user string: Cause: An attempt by an 'acfsutil repl' command to use the ssh utility to log in to a node failed.; Action: Ensure that the correct user name and address were specified for the standby node, and that both the standby and primary clusters are operating normally. If need be, verify network connectivity between the clusters, and refer to the product documentation to verify ssh configuration details. Then reissue the command.
ACFS-05915: invalid use of '-t ALL' option: Cause: An attempt to execute the 'acfsutil repl compare' command was rejected because the '-t ALL' option was specified on the command line, but no tag names had been specified when the primary was initialized.; Action: Reissue the 'acfsutil repl compare' command without the '-t ALL' option.
ACFS-05916: path string not found: Cause: The ssh utility was not found at the indicated path.; Action: Ensure that the path to the ssh utility is correct and retry.
ACFS-05917: user 'root' on node string unable to continue logging in via 'ssh' to the standby node string as user 'string': Cause: A periodic attempt by ACFS replication to use the ssh utility to continue logging in to a standby node failed.; Action: Ensure that the standby cluster is operating normally. If need be, verify network connectivity to the standby cluster, and refer to the product documentation to verify ssh configuration details.
ACFS-05918: Replication initialization on primary site cannot confirm replication initialized on standby mount point 'string'.: Cause: The 'acfsutil repl init primary' command failed on the primary replication site because it could not confirm that replication has been initialized on the standby replication site.; Action: Ensure that the correct user name and address were specified for the standby node, and run the 'acfsutil repl info -c' command on the standby site to confirm that replication has been initialized there for the mount point named. Then retry the 'acfsutil repl init primary' command.
ACFS-05919: Replication failed because it was unable to create a backup snapshot for mount point 'string' on standby node 'string'.: Cause: The 'acfsutil snap dup apply' operation, as used by ACFS replication, was unable to create a backup snapshot at the end of an apply operation on the standby node named. As a result, replication cannot proceed.; Action: Check the standby cluster for conditions that would prevent snapshot creation, such as lack of storage or having too many snapshots present. Replication will resume automatically once backup snapshots can again be created.
ACFS-05920: ssh cipher option "string" is invalid for replication: Cause: An attempt to configure replication on the primary file system was rejected because the indicated value was specified for the 'sshCipher' option. Replication does not support unencrypted ssh connections.; Action: Retry the command with a supported ssh cipher option.
ACFS-05921: One or more files under mount point 'string' was not transferred because its path name exceeded number characters. The first such file was in directory 'string' and had name 'string'.: Cause: The command 'acfsutil snap duplicate create' did not complete correctly because one or more files located under the indicated mount point had an absolute path name longer than the indicated limit. Any files with path names exceeding the limit were not processed by 'acfsutil'. The directory and basename of the first such file found are shown in the message, but there may be many others.; Action: Rename the problematic files so that their absolute path names are shorter than the limit, and retry the command.
ACFS-05922: One or more files under primary mount point 'string' was not replicated because its path name exceeded number characters. The first such file was in directory 'string' and had name 'string'.: Cause: ACFS replication did not replicate the primary correctly because one or more files located under the indicated mount point had an absolute path name longer than the indicated limit. Any files with path names exceeding the limit were not replicated. The directory and basename of the first such file found are shown in the message, but there may be many others.; Action: Rename the problematic files so that their absolute path names are shorter than the limit. Once each file has been renamed, the next later replication operation will automatically transfer the file.
ACFS-05923: unable to apply the incremental snapshot duplication stream because no initial snapshot duplication stream has been applied: Cause: An attempt to apply an incremental snapshot duplication stream failed because no preceding initial snapshot duplication stream has been applied to the snapshot duplication target.; Action: Apply an initial snapshot duplication stream to the target using 'acfsutil snapshot duplicate create' without the -i option to create the initial snapshot duplication stream.
ACFS-05924: unable to apply the incremental snapshot duplication stream because its starting snapshot does not match the final snapshot used to create the most recently applied snapshot duplication stream: Cause: The incremental snapshot duplication stream could not be applied because its starting snapshot did not match the final snapshot of the last stream applied.; Action: Apply all the intermediate incremental data streams in the correct order leading up to failed snap duplication stream and then rerun the apply operation.
ACFS-05925: unable to re-apply the initial snapshot duplication stream because its starting snapshot does not match the snapshot used to create the partially applied duplication stream: Cause: An attempt to apply an initial snapshot duplication stream was interrupted. An attempt was then made to re-apply the initial snapshot duplication stream. The re-apply failed because its starting snapshot did not match the snapshot of the last, partially applied snapshot duplication stream.; Action: Re-apply the correct initial snapshot duplication stream using the -r option of the command 'acfsutil snap duplicate create'.
ACFS-05926: The snapshot duplication stream cannot be applied because a previous duplication stream was interrupted.: Cause: Snapshot duplication failed because a previously interrupted snapshot duplication stream was detected.; Action: Generate a snapshot duplication stream using the -r option of the command 'acfsutil snap duplicate create', and apply it.
ACFS-05927: operation not allowed when replication is paused: Cause: A request to perform a replication command was rejected because the primary replication site was paused.; Action: Resume replication on the primary replication site and try the command again.
ACFS-05928: The ADVM compatibility attribute for the diskgroup is below the required version (string) for the 'acfsutil snap duplicate' commands.: Cause: The command 'acfsutil snap duplicate' was rejected because the ADVM disk group compatibility attribute had not been upgraded to the indicated version, which is required for that command.; Action: Use the Oracle ASM Configuration Assistant (ASMCA) tool or the SQL ALTER DISKGROUP statement to upgrade the disk group compatibility (COMPATIBLE.ADVM) attribute to the specified version and then re-issue the original command. If the disk group compatibility attribute cannot be upgraded, update the ACFS compatibility using the 'acfsutil compat set' command and then re-issue the original command.
ACFS-05929: Replication could not proceed because it was unable to delete a directory in mount point 'string' on standby node 'string'.: Cause: The 'acfsutil snap dup apply' operation, as used by ACFS replication, could not proceed because it was unable to delete a directory in the indicated mount point on the standby replication site shown.; Action: Check the alert log for message ACFS-05027 which includes the name of the directory being deleted. Check the standby cluster for conditions that would prevent the directory from being deleted, such as its being in use. Replication will resume automatically once the directory can be removed.
ACFS-05931: The standby replication ACFS file system mounted at path string at site string is not running a compatible version of replication.: Cause: A request to upgrade a primary replication ACFS file system was rejected because the standby file system is not running a compatible version of replication.; Action: Ensure that the cluster where the standby replication ACFS file system is located is running a version of Clusterware that supports the version of ACFS replication to which upgrade was attempted. Upgrade the standby replication ACFS file system, and then reissue the command to upgrade the primary ACFS replication file system. Refer to Oracle product documentation for details regarding Clusterware and ACFS replication version compatibility.
ACFS-05932: cannot upgrade the existing ACFS replication environment: Cause: A request to upgrade the existing ACFS replication environment to snapshot-based replication was rejected because the existing tag name list exceeded the limit of 4096 characters imposed by snapshot-based replication.; Action: Terminate the existing replication environment and reconfigure using snapshot-based replication. Refer to Oracle product documentation for details regarding upgrading to ACFS snapshot-based replication.
ACFS-05933: invalid, out-of-date option given for 'acfsutil repl init': Cause: An attempt to invoke a 'acfsutil repl init' command was rejected because it specified an option specific to an earlier version of ACFS replication.; Action: Ensure that you are using 'acfsutil repl init' as required by the current version of ACFS replication. Refer to the Oracle product documentation for details about running current replication.
ACFS-05934: ACFS replication could not start an apply operation for mount point 'string' due to an existing apply operation.: Cause: This message may indicate a problem with networking or storage access that is preventing the existing apply operation from making progress. Alternatively, this message may indicate an internal error.; Action: Contact Oracle Support Services.
ACFS-05935: The ACFS replication primary is mounted on more than one node.: Cause: A request to prepare ACFS replication for upgrade was rejected because the file system was mounted on more than one node.; Action: Unmount the ACFS replication primary on all but one node and retry the command.
ACFS-05936: The new snapshot and the old snapshot do not have the same parent.: Cause: An attempt to create a snap duplicate stream failed because the snapshot specified as the old snapshot by the -i option did not have the same parent as the snapshot specified as the new snapshot.; Action: Reissue the command with the correct snapshot names.
ACFS-05937: The new snapshot is not a child of the parent snapshot.: Cause: An attempt to create a snap duplicate stream failed because the snapshot specified as the new snapshot was not a child of the parent snap specified by the -p option.; Action: Reissue the command with the correct snapshot names.
ACFS-05938: The new snapshot is not a child of the mount point.: Cause: An attempt to create a snap duplicate stream failed because the snapshot specified as the new snapshot was not a child of the specified mount point.; Action: Reissue the command with the correct snapshot names.
ACFS-05939: The parent snapshot must be writable.: Cause: An attempt to create a snap duplicate stream failed because the snapshot specified as the parent snapshot by the -p option was not writable.; Action: Reissue the command specifying a writable parent snapshot.
ACFS-05940: The ACFS file system mounted at path string is not prepared for replication upgrade.: Cause: A request to undo replication upgrade preparation on an ACFS file system was rejected because the file system had not been prepared for replication upgrade.; Action: If the indicated ACFS file system was not the intended target for upgrade, reissue the command specifying the correct file system. Otherwise no further action is necessary.
ACFS-05941: The ACFS file system mounted at path string may not be unprepared for replication upgrade.: Cause: A request to undo replication upgrade preparation on an Oracle ACFS file system was rejected because its standby file system had already been upgraded.; Action: If the indicated Oracle ACFS file system was not the intended target for upgrade, reissue the command specifying the correct file system. Otherwise no further action is necessary.
ACFS-05942: unable to apply updates to standby mount point 'string' due to user mismatch: Cause: An apply update operation on the indicated mount point was rejected because the replication user for the primary mount point and the indicated standby mount point did not match. This could occur if the command 'acfsutil repl update' had been used to change the replication user for one mount point and not the other.; Action: Run the 'acfsutil repl update' command for the mount point where the intended replication user is not currently configured to ensure that both mount points have the intended user configured.
ACFS-05943: The replication user 'string' may lack needed privileges -- confirm the user's group memberships.: Cause: The 'acfsutil repl init standby' command completed correctly and registered the indicated user as specified by the -u option. However additional validation by the command determined that the indicated user was not a member of one or more groups presumed necessary for subsequent correct functioning of replication.; Action: If the intended replication user was correctly specified, ensure that that user is a member of the necessary groups, as specified in the Oracle documentation, before continuing to initiate replication. If the indicated user is not the intended replication user, then re-initialize the standby using the command 'acfsutil repl terminate standby' and then 'acfsutil repl init standby' naming the intended user.
ACFS-05944: The old and new snapshots are not properly related.: Cause: An attempt to create a snap duplicate stream failed because the specified new snapshot was not properly related to the old snapshot specified with -i. The new snapshot must either be a child of the old snapshot or be a child of the same parent as the old snapshot.; Action: Reissue the command specifying old and new snapshots with the required relationship.
ACFS-05945: Clusterware at site string must be upgraded to support the standby replication ACFS file system mounted at path string.: Cause: Following an upgrade of the Oracle Clusterware on the cluster where a primary replication ACFS file system was located, an attempt to do an automatic update of the standby failed, because the cluster where the standby replication ACFS file system was located was not running the same version of Clusterware.; Action: Upgrade the Oracle Clusterware on the cluster where the standby file system is located to ensure that the cluster is running the same version of Clusterware as the cluster where the primary file system is located.
ACFS-05946: The replication subcommand (string) is not supported by the version of replication configured on the file system or snapshot.: Cause: An attempt to execute the indicated replication sub-command was rejected because it was not supported by the configured replication version.; Action: None
ACFS-05947: Snapshot string must be writable.: Cause: An attempt to initialize replication on a snapshot failed because the snapshot specified was not writable.; Action: Reissue the command specifying a writable snapshot.
ACFS-05948: The named standby is already in use by a different primary.: Cause: An attempt to initialize replication failed because the standby specified was already paired with a different primary.; Action: Reissue the command specifying a standby that is not in use.
ACFS-05949: The standby replication ACFS file system mounted at path string at site string is not running a compatible version of replication.: Cause: A request to initiate replication of an ACFS file system was rejected because the indicated standby file system was running an incompatible version of replication.; Action: Ensure that the cluster where the standby replication ACFS file system is located is running a version of Clusterware that supports the version of ACFS replication which was being initialized. Initialize the standby replication ACFS file system, and then reissue the command to initialize the primary ACFS replication file system. Refer to Oracle product documentation for details regarding Clusterware and ACFS replication version compatibility.
ACFS-05950: cannot reverse replication during a rolling upgrade: Cause: An attempt to reverse the replication role at a site was rejected because the cluster was in a rolling upgrade. Replication site reversal is not allowed during a rolling upgrade.; Action: Complete the rolling upgrade and then reverse the replication site.
ACFS-05951: snapshot creation is blocked while ACFS replication is updating the standby: Cause: An attempt to create a snapshot could not complete immediately because the replication standby was currently being updated by ACFS replication.; Action: If the command has completed in the meantime, no action is required. Otherwise, if no action is taken, snapshot creation will be retried periodically and complete once the ACFS replication update has completed. To complete the snapshot creation immediately, interrupt the replication update and reissue the command. Terminiate the 'acfsutil snap create', run 'acfsutil repl pause' on the replication primary to pause the update, and then reissue 'acfsutil snap create'. Finally, run 'acfsutil repl resume' on the primary to resume the replication update.
ACFS-05952: A replication standby site cannot be reversed before the primary site is reversed.: Cause: An attempt to reverse a replication standby site was rejected because the corresponding replication primary site had not been reversed before the attempted standby reversal.; Action: Reverse the replication primary site, then retry the operation.
ACFS-05953: Replication on the remote site cannot be terminated from the local site.: Cause: An attempt to terminate replication on the remote site from the local site failed.; Action: On the remote replication cluster, verify replication is enabled, the ASM instance is operational and the state of the file system is healthy using 'acfsutil info fs'.
ACFS-05954: Replication on the remote site cannot be terminated from the local site. Proceeding with local termination.: Cause: An attempt to terminate replication on the remote site from the local site failed.; Action: On the remote replication cluster, verify replication is enabled, the ASM instance is operational and the state of the file system is healthy using 'acfsutil info fs' before running 'acfsutil repl terminate' on the remote cluster.
ACFS-05955: The replication user 'string' specified using the '-s' option does not match the replication user configured on the standby.: Cause: An attempt to initialize replication on the primary was rejected because the replication user specified using the '-s' option does not match the replication user specified with the 'acfsutil repl init standby' command using the '-u' option.; Action: If the replication user configured on the standby is correct, reissue the 'acfsutil repl init primary' command specifying it using the '-s' option. If the replication user configured on the standby is incorrect, run 'acfsutil repl terminate' on the standby, and rerun the 'acfsutil repl init' commands specifying the same user for replication user on both the standby and primary using the '-u' and '-s' options respectively.
ACFS-05956: Operation not allowed during a rolling upgrade.: Cause: An attempt to perform an operation was rejected because the cluster was in a rolling upgrade. Some operations are not allowed during a rolling upgrade.; Action: Complete the rolling upgrade and then retry the operation.
ACFS-05957: Unable to initiate a transfer after failover.: Cause: The replication daemon detected that the standby was failed over and is no longer participating in this replication relationship as a standby. As such, we can no longer replicate to it so the daemon will terminate.; Action: Determine why the standby was failed over. If appropriate, determine why this site has not failed over.
ACFS-05958: Invalid standby configuration.: Cause: The replication daemon detected that the standby is no longer participating in this replication relationship as a standby. As such, it can no longer be replicated to.; Action: Determine why the standby was removed from this replication relationship, configure a new standby and then run 'acfsutil repl update -m -s' on this node.
ACFS-05959: Operation not allowed during role reversal.: Cause: An attempt to perform an operation was rejected because a role reversal is in progress for this replication relationship.; Action: Complete or abort the role reversal and then retry the operation.
ACFS-05960: Operation not allowed during upgrade.: Cause: An attempt to perform an operation was rejected because an upgrade is in progress for this replication relationship.; Action: Complete the upgrade process and then retry the operation.
ACFS-05961: The new snapshot and the old snapshot have the same names.: Cause: An attempt to create a snap duplicate stream failed because the snapshot specified as the old snapshot by the -i option has the same name as the new snapshot.; Action: Reissue the command with the correct snapshot names.
ACFS-05962: Multiple connections are not allowed between snapshot sites.: Cause: An attempt to configure replication failed because multiple connections were specified but the primary or standby site is a snapshot. Replication does not support multiple connections between snapshot sites.; Action: Reissue the command without the multiple connection option.
ACFS-05963: user root on node string unable to log in via 'ssh' to the primary node string as user string: Cause: An attempt by 'acfsutil repl init primary' to use the ssh utility from a standby node to log in to a primary node failed.; Action: Ensure that the intended address has been used for the primary node, specifying a different address if need be with the "-p" option. Ensure that the primary cluster is operating normally. Verify network connectivity to the primary cluster, and refer to the product documentation to verify ssh configuration details. Then reissue the 'acfsutil repl init primary' command.
ACFS-05965: You must be the replication user (string) or 'root' to run this command.: Cause: User was not the replication user specified when replication was initialized.; Action: Only the replication user or 'root' has privilege to execute the replication commands.
ACFS-05966: operation not allowed due to insufficient space in file system: Cause: An attempt to run a replication command failed because the ACFS file system was full.; Action: Make at least 100MB of free space available within the ACFS file system and retry the command.
ACFS-05967: invalid 'ynvalue' specified: string: Cause: The command argument does not support the specified value.; Action: Review the command usage and retry the command providing valid input.
ACFS-05968: unable to get hosts for remote cluster string: Cause: An attempt to use the "acfsutil cluster info" command to get hosts for the remote cluster specified failed.; Action: Ensure that the correct host name or IP address was specified for the '-c remote_cluster' option, and that the remote cluster is operating normally. Then reissue the 'acfsreplssh' command.
ACFS-05969: unable to get domain-qualified hostname for string: Cause: Internal error.; Action: Contact Oracle Support Services.
ACFS-05970: unable to backup directory string to directory string: Cause: An attempt to backup the local ssh directory failed due to an internal error.; Action: Contact Oracle Support Services.
ACFS-05971: unable to confirm backup to string: Cause: An attempt to confirm backup to the local ssh backup directory failed due to an internal error.; Action: Contact Oracle Support Services.
ACFS-05972: unable to create file or directory string: Cause: An attempt to create a file or directory failed due to an internal error.; Action: Contact Oracle Support Services.
ACFS-05973: unable to ssh to string@string using the user name and password provided: Cause: An attempt to use the ssh utility to log in to a remote node failed.; Action: Ensure you are invoking the 'acfsreplssh' command as the replication user, specifying its password correctly, and that the remote node is operating normally. If need be, verify network connectivity to the remote node. Then reissue the 'acfsreplssh' command.
ACFS-05974: unable to get home directory path for string: Cause: Internal error.; Action: Contact Oracle Support Services.
ACFS-05975: unable to determine remote home directory (string): Cause: An attempt to determine the remote home directory failed due to an internal error.; Action: Contact Oracle Support Services.
ACFS-05976: unable to update permissions for string on string (string): Cause: An attempt to update permissions for the remote home directory failed due to an internal error.; Action: Contact Oracle Support Services.
ACFS-05977: unable to remove passwordless ssh from string@string: Cause: An attempt to remove passwordless ssh failed due to an internal error.; Action: Contact Oracle Support Services.
ACFS-05978: unable to confirm existence or permissions (rwx------) of directory string on host string (string): Cause: An attempt to confirm existence or permissions of a directory failed due to an internal error.; Action: Contact Oracle Support Services.
ACFS-05979: invalid public key: string: Cause: An attempt to retrieve the local user public key failed due to an internal error.; Action: Contact Oracle Support Services.
ACFS-05980: failed to configure passwordless ssh to string@string: Cause: An attempt to configure passwordless ssh failed due to an internal error.; Action: Contact Oracle Support Services.
ACFS-05981: The standby replication ACFS file system mounted at path string at site string must be upgraded to a compatible version of replication.: Cause: An attempt to perform replication of an ACFS file system was rejected because the indicated standby file system was running an incompatible version of replication.; Action: Ensure that the cluster where the standby replication ACFS file system is located is running a version of Clusterware that supports the version of ACFS replication that was in use in the primary replication cluster. On Linux, one cause of a version mismatch may be that the primary file system contains a use of extended attributes of the class "trusted" or "security". Refer to Oracle product documentation for further details regarding Clusterware and ACFS replication version compatibility.
ACFS-05982: The replication user 'string' may lack needed privileges -- confirm the user's capabilities.: Cause: An attempt to perform replication of an ACFS file system was rejected with a permissions error.; Action: On Linux, one cause of this error may be that the replication user does not have the capability CAP_SYS_ADMIN, and the primary file system contains a use of extended attributes of the class "trusted" or "security". If this cause does not apply, contact Oracle Support Services.
ACFS-05983: A switchover operation is not possible because status at the primary host 'string' cannot be determined.: Cause: An attempt to perform a replication switchover was rejected. The primary location cannot be accessed.; Action: If the situation with the primary location can be resolved, you may re-try the switchover command. If the primary location status cannot be corrected, you may run the 'acfsutil repl failover' command to force the standby transition to a primary.
ACFS-05984: A failover or switchover operation is not possible because the initial transfer was never completed.: Cause: An attempt to perform a replication failover or switchover operation was rejected because a successful transfer was never completed.; Action: Until at least one successful transfer has completed, a failover or switchover operation is not allowed. If possible, wait until the initial transfer has completed and then retry the command.
ACFS-05985: Replication initialization on primary site cannot confirm replication initialized on standby snapshot storage location 'string@string'.: Cause: The 'acfsutil repl init primary' command failed on the primary replication site because it could not confirm that replication has been initialized on the standby replication site.; Action: Ensure that the correct user name and address were specified for the standby node, and run the 'acfsutil repl info -c' command on the standby site to confirm that replication has been initialized there for the snapshot storage location named. Then retry the 'acfsutil repl init primary' command.
ACFS-05986: A sparse backup cannot be applied to a snapshot.: Cause: An attempt to apply an ACFS sparse backup was rejected because a snapshot was specified.; Action: Retry the apply of a sparse backup to an ACFS file system (not a snapshot).
ACFS-05987: A sparse backup cannot be applied while snapshots exist on the specified file system.: Cause: One or more snapshots existed for the file system when an attempt was made to apply an ACFS sparse backup.; Action: Remove all snapshots from the file system and retry the apply of the sparse backup.
ACFS-05988: ACFS replication for the storage location string at site string does not support the failover or switchover operation.: Cause: The 'acfsutil repl failover' or 'acfsutil repl switchover' operation failed on the standby replication site because it found that the primary site was running a version of replication that does not support these operations.; Action: To enable failover or switchover to the named primary site, upgrade the primary site to run a version of replication that supports the desired operation.
ACFS-06001: No credentials file was found.: Cause: A credentials file was not found at the location specified for pathname.; Action: Ensure that the pathname to the credentials file is correct and retry.
ACFS-06002: No credentials found.: Cause: No credentials were stored in the OCR.; Action: Create credentials using the 'acfsutil repl update' command's sslCreateCredentials option and retry.
ACFS-06003: Credentials file already exists.: Cause: A credentials file was found at the location specified for pathname.; Action: Change the pathname to the credentials file and retry.
ACFS-06004: Authentication failed.: Cause: Authentication failed because no credentials were found.; Action: Create credentials using the 'acfsutil repl update' command's sslCreateCredentials option and retry.
ACFS-06005: Credential sync not permitted at this site.: Cause: Credential sync was not permitted at this site because either the sslPermitCredentialSync option was not specified, or the sslProhibitCredentialSync option was specified.; Action: Retry specifying the sslPermitCredentialSync option.
ACFS-06006: Credential sync not permitted at remote site.: Cause: Credential sync was not permitted at remote site because either the sslPermitCredentialSync option was not specified, or the sslProhibitCredentialSync option was specified.; Action: Retry specifying the sslPermitCredentialSync option.
ACFS-06007: Credentials already exist.: Cause: Informational.; Action: None
ACFS-06008: The connection request to the replication service at node string was refused.: Cause: The node hosting the replication service was inaccessible or not operating normally. The replication service on node was not online or refused the connection request.; Action: Ensure that the node hosting the replication service is operating normally. Ensure network connectivity to the node. Ensure that the replication service is online.
ACFS-06009: A client with process id number at node string failed to authenticate using certificate number.: Cause: Informational.; Action: None
ACFS-06010: number authentication failure alerts have been suppressed: Cause: Informational.; Action: None
ACFS-06011: An invalid request was received from process number at node string.: Cause: Informational.; Action: None
ACFS-06012: ACFS Replication credentials number were created.: Cause: Informational.; Action: None
ACFS-06013: ACFS Replication credentials number were imported.: Cause: Informational.; Action: None
ACFS-06014: ACFS Replication credentials number were destroyed.: Cause: Informational.; Action: None
ACFS-06015: ACFS Replication credentials number were synced with site string.: Cause: Informational.; Action: None
ACFS-06016: The replication service at node string is online.: Cause: Informational.; Action: None
ACFS-06017: cannot start replication service daemon: Cause: CRS has failed to start the replication service daemons.; Action: Verify that CRS is running. Check the CRS logs to determine why the replication daemons failed to start.
ACFS-07016: metadata read failed at disk offset: string size: number bytes: Cause: An attempt to read metadata at the indicated disk offset failed. Refer to the accompanying message(s) for more information on the problem.; Action: Correct the problem described in the accompanying messages if possible and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ACFS-07017: metadata read failed at disk offset: string\n bytes requested: number bytes returned: number: Cause: A metadata read at the indicated offset was incomplete. The amount of data returned did not match the amount requested. Refer to the accompanying message(s) for more information on the problem.; Action: Correct the problem described in the accompanying messages if possible and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ACFS-07018: metadata write failed at disk offset: string size: number bytes: Cause: An attempt to write metadata at the indicated disk offset failed. Refer to the accompanying message(s) for more information on the problem.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07019: metadata write failed at disk offset: string\n bytes requested: number bytes written: number bytes: Cause: A metadata write at the indicated offset was incomplete. The amount of data written did not match the amount requested. Refer to the accompanying message(s) for more information on the problem.; Action: Correct the problem described in the accompanying messages if possible and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ACFS-07021: The File_Entry_Table is corrupt and many of the files in the file system may \nnot be recoverable. It is strongly recommended that the file system be restored \nfrom a backup copy.: Cause: The ACFS Checker/Fixer found an inconsistency with the File_Entry_Table metadata. The File_Entry_Table is a critical system structure that is necessary for a functioning file system.; Action: Restore the file system from a backup copy.
ACFS-07022: I/O request for (disk offset + size): string exceeds primary volume size: string\nfor structure:\nstring: Cause: An I/O request was made for data that exceeded the size of the primary volume.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07023: read failed for metadata structure at disk offset: string size: number bytes\nstructure type: string \nfor structure:\nstring: Cause: An attempt to read a metadata structure from disk failed. Refer to accompanying message(s) for more information on the problem.; Action: Correct the problem described in the accompanying messages if possible and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ACFS-07024: File_Entry_Table entry: string exceeds the maximum value for this file system: string: Cause: An entry was referenced that exceeded the File_Entry_Table limit.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07025: File_Entry_Table entry: string already processed for structure:\nstring: Cause: File_Entry_Table entries must be unique within a file system, but there were multiple references for this specific entry.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07026: file extent exceeds file system size: string\nextent: _FileOffset: string _Length: string _PhysicalDiskOffset: string\nfor file:\nstring: Cause: The extent values of the indicated file referenced data beyond the size of the file system. There are two possible causes: 1. The extent _Length and/or _PhysicalDiskOffset property were incorrect. 2. The file system size value was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07027: metadata structure at disk offset: string contains incorrect or invalid type\n found: string, but expected to find: string or string\nfor structure:\nstring: Cause: The type property of the indicated metadata structure was not valid. The type must be a DATA extent or a HEADER extent.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07028: DATA extent structure has incorrect _granularity value\n found: number, but expected to find: number\nfor structure:\nstring: Cause: The _granularity property of the indicated DATA extent structure was invalid. Its value must be -1.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07029: HEADER extent structure has incorrect _granularity value\n found: number, but expected to find: >= 0\nfor structure:\nstring: Cause: The _granularity property of the indicated HEADER extent structure was invalid. Its value must be greater than or equal to zero.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07030: file has invalid _FE_OsdSecurity value\nfor file:\nstring: Cause: The _FE_OsdSecurity property of the indicated file was invalid.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07031: extent structure has incorrect _ExtentOffset value\n found: string, but expected to find: string\nfor structure:\nstring: Cause: The _ExtentOffset property of the indicated extent structure did not match its disk offset.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07032: extent structure has incorrect _UpHeaderNodePtr value\n found: string, but expected to find: string\nfor structure:\nstring: Cause: The _UpHeaderNodePtr property of the indicated extent structure was incorrect. There are two possible causes: 1. The _UpHeaderNodePtr property did not match its parent. 2. The parent identifier property was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07033: extent structure has incorrect _granularity value\n found: number, but expected to find: number\nfor structure:\nstring: Cause: The _granularity property of the indicated extent structure did not match its calculated depth.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07034: extent structure has incorrect _NextFreeExtent value\n found: number maximum: number\nfor structure:\nstring: Cause: The _NextFreeExtent property of the indicated extent structure was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07035: extent[number] appears to be uninitialized\nfor structure:\nstring: Cause: An extent of the indicated extent structure appeared to be in use, but all of its values were zero.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07036: extent[number] has invalid _Length value\n found: 0, but expected to find: > 0\nfor structure:\nstring: Cause: The _Length property of an extent of the indicated extent structure had a value of zero. _Length values must be greater than zero.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07037: extent[number] has incorrect _SnapIncarnationNumber value\n found: number maximum: number\nfor structure:\nstring: Cause: The _SnapIncarnationNumber property of the indicated extent structure exceeded the maximum value for the file system.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07038: extent[number] has a non-contiguous _FileOffset value\n found: string, but expected to find: string\nfor structure:\nstring: Cause: The _FileOffset property of an extent of the indicated extent structure was not contiguous with the _FileOffset of the previous extent.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07039: extent[number] is not in use but it contains non-zero values:\n _FileOffset: string\n _Length: string\n _PhysicalDiskOffset: string\n _SnapIncarnationNumber: number\nfor structure:\nstring: Cause: An extent of the indicated extent structure was not in use, but it contained non-zero values. There are two possible causes: 1. The extent values were not reset to zero when the extent was freed. 2. The _NextFreeExtent property of the extent structure was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07040: calculated extent structure allocation size (sum of data sizes) does not match expected value\n calculated: string, but expected to find:string\nfor structure:\nstring: Cause: The sum of all valid extents within the indicated extent structure did not match the value of the corresponding extent in the parent extent structure.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07041: DATA extent list not found\nfor file:\nstring: Cause: The list of DATA extent structures of the indicated file did not include the initial DATA extent structure. There are two possible causes: 1. The _LastExtentPointer property of the file was incorrect. 2. The structure identified by the _LastExtentPointer value was not a DATA extent structure.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07042: DATA extent node list missing entry for extent structure:\nstring: Cause: The list of DATA extent structures of the indicated file was incomplete. One or more DATA extent structures was missing. There are three possible causes: 1. The _LastExtentPointer property of the file was incorrect. 2. The structure identified by the _LastExtentPointer value was not a valid DATA extent structure. 3. The _NextDataExtent property of one or more DATA extent structures was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07043: metadata structure has invalid or incorrect type:\n found: string, but expected to find: string\nfor structure:\nstring: Cause: The type property of the indicated metadata structure did not match the type expected for this structure.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07044: DATA extent list has more nodes than expected\n found: number, but expected to find: number\nfor file:\nstring: Cause: The list of DATA extent structures of the indicated file contained more nodes than expected. The _NextDataExtent property of one or more DATA extent structures was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07045: DATA extent list has fewer nodes than expected\n found: number, but expected to find: number\nfor file:\nstring: Cause: The list of DATA extent structures of the indicated file contained fewer nodes than expected. There are two possible causes: 1. One or more of the DATA extent structures did not have a valid structure header. 2. The _NextDataExtent property of one or more DATA extent structures was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07046: file has _LastExtentPointer that does not match calculated value\n calculated: string, but expected to find: string\nfor file:\nstring: Cause: The _LastExtentPointer property of the indicated file did not match the file's last DATA extent structure. There are three possible causes: 1. The _LastExtentPointer value was incorrect. 2. The last DATA extent structure was not found because the The _NextDataExtent property of one or more DATA extent structures was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07047: extent node list missing entry for extent structure:\nstring: Cause: The list of extent structures of the indicated file was incomplete. One or more extent structures was missing. There are three possible causes: 1. The _LastExtentPointer property of the file was incorrect. 2. One or more extent structures did not have a valid structure header. 3. The _LastExtentPointer property of one or more extent structures was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07048: metadata structure has invalid _generation_number value\n found: number, but expected to find: number\nfor structure:\nstring: Cause: The _generation_number property of the indicated metadata structure was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07049: extent list has more nodes than expected\n found: number, but expected to find: number\nfor file:\nstring: Cause: The list extent structures of the indicated file contained more nodes than expected. The _LastExtentPointer property of one or more extent structures was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07050: extent list has fewer nodes than expected\n found: number, but expected to find: number\nfor file:\nstring: Cause: The list of extent structures of the indicated file contained fewer nodes than expected. There are two possible causes: 1. One or more of the extent structures did not have a valid structure header. 2. The _LastExtentPointer property of one or more extent structures was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07051: file has incorrect _LinkCount value\n found: number, but expected to find: number\nfor file:\nstring: Cause: The _LinkCount property of the indicated file did not match the number of hard links found for the file. There are four possible causes: 1. The _LinkCount property was incorrect. 2. One or more directory entries for this file was invalid or was not found. 3. A Directory_Entry structure for this file had an incorrect file identifier. 4. The _LinkCount property of an ACFS Internal File was not equal to one.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07052: file has invalid _ProtectionBits value\n found: number, but expected to find: number\nfor file:\nstring: Cause: The _ProtectionBits property of the indicated files was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07053: file has invalid _ParentID value\n found: string, but expected to find: string\nfor file:\nstring: Cause: The _ParentID property of the indicated file was not correct. There are two possible causes: 1. The _ParentID value did not match the file's parent directory. 2. The _ParentID value did not match any valid directory.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07054: file has invalid _WindowsAttributes value(s)\n found: string\n, but expected to find: 0\nfor file:\nstring: Cause: The _WindowsAttributes property of the indicated file was invalid. The _WindowsAttributes value must be zero since file was not created on a Windows system.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07055: extent[number] is not in use but it contains non-zero values:\n _FileOffset: string\n _Length: string\n _PhysicalDiskOffset: string\nfor file:\nstring: Cause: One of the extents of the indicated file was not in use, but it contained non-zero values. There are two possible causes: 1. The extent values were not reset to zero when the extent was freed. 2. The _NextFreeExtent property of the file was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07057: extent[number] has incorrect _FileOffset\n found: string, but expected to find: 0\nfor file:\nstring: Cause: The _FileOffset property of the initial extent of the indicated file was not zero. The _FileOffset for a file's initial extent must be zero as it identifies the beginning of the file.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07058: file with local extents has invalid _LastExtentPointer value\n found: string, but expected to find: 0\nfor file:\nstring: Cause: The _LastExtentPointer property of the indicated file was not zero which is required for files with local extents.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07060: extent[number] appears to be uninitialized\nfor file:\nstring: Cause: An extent of the indicated file appeared to be in use, but all of its values were zero.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07061: extent[number] has invalid _Length value\n found: 0, but expected to find: > 0\nfor file:\nstring: Cause: The _Length property of an extent of the indicated file had a value of zero. _Length values must be greater than zero.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07062: extent[number] has incorrect _SnapIncarnationNumber value\n found: number maximum: number\nfor file:\nstring: Cause: The _SnapIncarnationNumber property of the indicated file exceeded the maximum value for the file system.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07063: extent[number] has a non-contiguous _FileOffset value\n found: string, but expected to find: string\nfor file:\nstring: Cause: The _FileOffset property of an extent of the indicated file was not contiguous with the _FileOffset of the previous extent.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem
ACFS-07064: file _AllocationSize value not equal to sum of extents\n found: string, but expected to find: string\nfor file:\nstring: Cause: The _AllocationSize property of the indicated file was not equal to the sum of the _Length properties of the file's extents. There are three possible causes: 1. The _AllocationSize value was incorrect. 2. The _Length property of one or more of the file's extents was incorrect. 3. The _NextFreeExtent property of the file was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07065: File_Entry_Table calculated allocation size (sum of data extents) does not match its _FileSize value\n found: string calculated: string\nfor file:\nstring: Cause: The _FileSize property of File_Entry_Table did not match the sum of the file's extent _Length values. There are two possible causes: 1. The _Length property of one or more extents of the File_Entry_Table was incorrect. 2. The _FileSize property of the File_Entry_Table was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07066: extent[number] is not in use but it contains non-zero values:\n _FileOffset: string\n _Length: string\n _PhysicalDiskOffset: string\n _SnapIncarnationNumber: number\nfor file:\nstring: Cause: One of the extents of the indicated file was not in use, but it contained non-zero values. There are two possible causes: 1. The extent values were not reset to zero when the extent was freed. 2. The _NextFreeExtent property of the file was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07073: file has _FileEntry structure with incorrect or invalid _FileEntryType value\n found: string, but expected to find: string\nfor file:\nstring: Cause: The _FileEntryType property of the indicated file did not match its expected value. There are two possible causes: 1. The _FileEntryType value was incorrect for this particular file. 2. The _FileEntryType value was not on the list of valid values.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07074: file has _FileEntry structure with incorrect file identifier\n found: string, but expected to find: string\nfor file:\nstring: Cause: The file identifier property of the indicated file did not match its position within the File_Entry_Table entry.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07075: file has incorrect _FileSize value\n found: string minimum: string\nfor file:\nstring: Cause: The _FileSize property of the indicated file was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07076: file has invalid _AllocationSize value\n found: string minimum: string\nfor file:\nstring: Cause: The _AllocationSize property of the indicated file was invalid. The _AllocationSize value for this file cannot be less than the value described in the message.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07077: Local_Bitmap has incorrect _FileOffset value for Extent[1]\n found: string, but expected to find: 0\nfor file:\nstring: Cause: The _FileOffset property in Extent[1] of the indicated Local_Bitmap was not zero.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07078: Local_Bitmap has incorrect _Length value in Extent[1]\n found: string, but expected to find: string\nfor file:\nstring: Cause: The _Length property in Extent[1] of the indicated Local_Bitmap did not match the file system's allocation unit size.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07079: Local_Bitmap has invalid _PhysicalDiskOffset value for Extent[1]\n found: 0, but expected to find: > 0\nfor file:\nstring: Cause: The _PhysicalDiskOffset property in Extent[1] of the indicated Local_Bitmap was equal to zero. This _PhysicalDiskOffset value must be greater than zero.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07080: Local_Bitmap has incorrect _PhysicalDiskOffset value for Extent[1]\n found: string maximum: string\nfor file:\nstring: Cause: The _PhysicalDiskOffset property in Extent[1] of the indicated Local_Bitmap exceeded the size of the file system.; Action: n/a
ACFS-07081: file has invalid _granularity value\n found: number, but expected to find: number\nfor file:\nstring: Cause: The _granularity property of the indicated system file was incorrect. Many system files require local extents which is indicated by a _granularity value of -1.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07082: Global_BitMap space requirement exceeds _AllocationSize value. Bitmap requires string bytes, allocated space: string bytes\nfor file:\nstring: Cause: The _AllocationSize property of the Global_BitMap was not large enough to store the Global_BitMap data. There are two possible causes: 1. The _AllocationSize value was incorrect. 2. The value used to indicate the number of bits needed to map file system storage was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07083: Global_BitMap has invalid _granularity value\n found: number, but expected to find: number\nfor file:\nstring: Cause: The _granularity property of the indicated Global_BitMap was incorrect. The Global_BitMap file must have a _granularity value of -1 which indicates that the file has local extents.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07084: Snap_Map has mismatch between _FileSize and _AllocationSize values\n _FileSize: string _AllocationSize: string\nfor file:\nstring: Cause: The _FileSize and _AllocationSize properties of the indicated Snap_Map file did not match. The values for these properties must match for a Snap_Map file. One or both values was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07085: file has _FileSize value that exceeds _AllocationSize value\n _FileSize: string _AllocationSize: string\nfor file:\nstring: Cause: The _FileSize property of the indicated file exceeded the amount of storage allocated to the file. The _AllocationSize property describes the amount of storage available for the file. One of of these properties was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07086: file has _AllocationSize value that is invalid for the file system\n found: string, but expected to find: multiple of string\nfor file:\nstring: Cause: The _AllocationSize property of the indicated file was incorrect. Its value must be a multiple of the file system allocation unit size.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07087: file has _AllocationSize value but no extent information\n _AllocationSize: string\nfor file:\nstring: Cause: The _AllocationSize property of the indicated file was greater than 0, but there was no corresponding extent information. There are two possible causes: 1. The _AllocationSize should have been zero. 2. The _NextFreeExtent value was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07088: Map_File has incorrect _FileSize value\n found: string, but expected to find: multiple of number\nfor file:\nstring: Cause: The _FileSize property of the indicated Map_File was incorrect. The _FileSize value for a Map_File must be a multiple of the META_MAP_ENTRY size.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07089: Volume_Log has invalid _FileSize value\n found: string, but expected to find: 0\nfor file:\nstring: Cause: The _FileSize property of the indicated Volume_Log file was not equal to zero. The _FileSize value for a Volume_Log must be zero.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07090: Volume_Log has invalid _granularity value\n found: number, but expected to find: number\nfor file:\nstring: Cause: The _granularity property of the indicated Volume_Log file was incorrect. Volume_Log files must have a _granularity value of -1 which indicates that the file has local extents.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07091: Volume_Log has incorrect _NextFreeExtent value\n found: number, but expected to find: 0 or 1\nfor file:\nstring: Cause: The _NextFreeExtent property of the indicated Volume_Log file was incorrect. A Volume_Log file can have at most one extent.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07092: file has invalid _security_data_offset value\nfor file:\nstring: Cause: The _security_data_offset property of the indicated file did not have a corresponding entry in any Security_Metadata file. There are three possible causes: 1. The _security_data value was incorrect. 2. The Security_Metadata file had incorrect data at the corresponding offset. 3. The Security_Metadata file was not found.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07094: file has invalid _SnapMetaIncarnationNumber value\n found: number maximum: number\nfor file:\nstring: Cause: The _SnapIncarnationNumber property of the indicated file exceeded the maximum _SnapIncarnationNumber value for the file system.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07095: CHARACTER special file has invalid major_device_number value\n found: 0, but expected to find: > 0\nfor file:\nstring: Cause: The major_device_number property of the indicated CHARACTER special file was invalid. major_device_number values must be greater than zero.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07096: file has incorrect _EAOffset value\n found: string, but expected to find: string\nfor file:\nstring: Cause: The _EAOffset property of the indicated file was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07097: file has invalid _TimeofCreation value\n found: string, but expected to find: string\nfor file:\nstring: Cause: The _TimeofCreation property of the indicated file was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07098: file has invalid _TimeLastAccessed value\n found: string, but expected to find: string\nfor file:\nstring: Cause: The _TimeLastAccessed property of the indicated file was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07099: file has invalid _TimeLastModified value\n found: string, but expected to find: string\nfor file:\nstring: Cause: The _TimeLastModified property of the indicated file was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07100: file has invalid _FileSize value\n found: string minimum: string\nfor file:\nstring: Cause: The _FileSize property of the indicated file was invalid. The _FileSize value for this file cannot be less than the value described in the message.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07101: file has invalid _TimeLastChanged value\n found: string, but expected to find: string\nfor file:\nstring: Cause: The _TimeLastChanged property of the indicated file was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07102: file has invalid _TimeofCreation value\n found: 0\nfor file:\nstring: Cause: The _TimeofCreation property of the indicated file was invalid. The _TimeofCreation value must be non-zero.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07103: file has invalid _TimeLastAccessed value\n found: 0\nfor file:\nstring: Cause: The _TimeLastAccessed property of the indicated file was invalid. The _TimeLastAccessed value must be non-zero.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07104: file has invalid _TimeLastModified value\n found: 0\nfor file:\nstring: Cause: The _TimeLastModified property of the indicated file was invalid. The _TimeLastModified value must be non-zero.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07105: file has invalid _TimeLastChanged value\n found: 0\nfor file:\nstring: Cause: The _TimeLastChanged property of the indicated file was invalid. The _TimeLastChanged value must be non-zero.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07106: file has invalid _WindowsAttributes value(s)\n found: string\n valid values: string\nfor file:\nstring: Cause: The _WindowsAttributes property of the indicated file was invalid. One or more of the _WindowsAttributes values were not within the range of valid values. Refer to the corresponding messages for a list of valid values.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07107: file has incorrect _rep_incarnation value\n found: number, but expected to find: number\nfor file:\nstring: Cause: The _repFE_incarnation_number property of the indicated file was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07108: file has incorrect _rep_VFN value\n found: string, but expected to find: string\nfor file:\nstring: Cause: The _rep_VFN property of the indicated file was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07109: file has incorrect _rep_SCN value\n found: string, but expected to find: string\nfor file:\nstring: Cause: The _rep_SCN property of the indicated file was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07110: file has incorrect _EncrMetaOffset value\n found: string, but expected to find: string\nfor file:\nstring: Cause: The _EncrMetaOffset property of the indicated file was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07111: file has incorrect _Vault_MetaOffset value\n found: string, but expected to find: string\nfor file:\nstring: Cause: The _Vault_MetaOffset property of the indicated file was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07112: file has incorrect _EncrSecFlags value\n found: string, but expected to find: string\nfor file:\nstring: Cause: The _EncrSecFlags property of the indicated file was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07113: file has incorrect _EA_ContainerUnits value\n found: number, but expected to find: number\nfor file:\nstring: Cause: The _EA_ContainerUnits property of the indicated file was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07115: Local_Bitmap has incorrect _FileSize value\n found: string, but expected to find: 0\nfor file:\nstring: Cause: The _FileSize property of the indicated Local_Bitmap was invalid. The _FileSize value for a Local_Bitmap must be zero.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07116: BLOCK special file has invalid major_device_number value\n found: 0, but expected to find: > 0\nfor file:\nstring: Cause: The major_device_number property of the indicated BLOCK special file was invalid. major_device_number values must be greater than zero.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07117: Directory_Entry structure has invalid file identifier value:\n found: string maximum: string\nfor structure:\nstring: Cause: The file identifier property of the indicated Directory_Entry structure exceeded the maximum file identifier for the file system.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07118: System metadata file is corrupt and cannot be repaired\nfor file:\nstring: Cause: The ACFS Checker/Fixer found an inconsistency with the indicated system metadata file. This metadata file cannot be repaired due to the nature of the corruption.; Action: Restore the file system from a backup copy.
ACFS-07119: _Locator structure has incorrect _global_dir_blk value\n found: string, but expected to find: string\nfor structure:\nstring: Cause: The _global_dir_blk property of the indicated structure was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07120: _Locator structure has invalid node identifier for entry number in _node_number array\n found: number maximum: number\nfor structure:\nstring: Cause: A node identifier in the _node_number array of the indicated structure that exceeded the maximum value for the file system.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07121: _Locator structure has invalid file identifier for entry number in _local_dir_blk array\n found: string maximum: string\nfor structure:\nstring: Cause: A file identifier for a Local_Metadata_Directory in the _local_dir_blk array of the indicated _Locator structure exceeded the maximum file identifier for the file system.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07122: _Locator structure has incorrect _local_dir_blk_disk_offset for entry number in _local_dir_blk_disk_offset array\n found: string, but expected to find: string\nfor structure:\nstring: Cause: The disk offset for a Local_Metadata_Directory in the _local_dir_blk_disk_offset array of the indicated _Locator structure was incorrect. There are two possible causes: 1. The _local_dir_blk_disk_offset value was incorrect. 2. The structure at the _local_dir_blk_disk_offset was not a Local_Metadata_Directory structure.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07123: _Locator structure has duplicate entries for node number\nfor structure:\nstring: Cause: There was more than one entry for the same node within the _Locator structure(s). Node identifies must be unique.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07124: _Locator structure has duplicate entries for Local_Metadata_Directory: string\nfor structure:\nstring: Cause: There was more than one entry for the same Local_Metadata_Directory within the _Locator structure(s). Local_Metadata_Directory file identifiers must be unique.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07125: _Locator structure has incorrect _node_count value\n found: number, but expected to find: number\nfor structure:\nstring: Cause: The _node_count property of the indicated _Locator structure did not match the number of valid nodes found.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07126: _Locator structure has incorrect _next_locator_blk_disk_offset value\n found: string\nfor structure:\nstring: Cause: The _next_locator_blk_disk_offset property of the indicated _Locator structure was incorrect. There are two possible causes: 1. The _next_locator_blk_disk_offset was incorrect. 2. The structure at the _next_locator_blk_disk_offset was not a _Locator structure.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07127: Global_Virtual_FileID_Pool structure has incorrect _repFreeVFNGroup value\n found: string, but expected to find: string\nfor structure:\nstring: Cause: The _repFreeVFNGroup property of the indicated Global_Virtual_FileID_Pool structure was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07128: Global_Virtual_FileID_Pool structure has incorrect _repFreeVFNIncarnNum value\n found: string, but expected to find: string\nfor structure:\nstring: Cause: The _repFreeVFNIncarnNum property of the indicated Global_Virtual_FileID_Pool structure was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07129: Replication_Log_Initiator structure has incorrect _initiator_node_id value\n found: number, but expected to find: number\nfor structure:\nstring: Cause: The _initiator_node_id property of the indicated Replication_Log_Initiator structure was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07130: Replication_Log_Initiator structure has incorrect _new_rlog_recovered value\n found: number, but expected to find: number\nfor structure:\nstring: Cause: The _it_rep_logs_processed property of the indicated Replication_Log_Initiator structure was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07131: Replication_Log_Initiator structure has incorrect _next_cord_id value\n found: string, but expected to find: string\nfor structure:\nstring: Cause: The _next_cord_id property of the indicated Replication_Log_Initiator structure was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07132: Replication_Log_Initiator structure has incorrect _next_segment_id value\n found: string, but expected to find: string\nfor structure:\nstring: Cause: The _next_segment_id property of the indicated Replication_Log_Initiator structure was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07133: Local_Bitmap has incorrect _AllocationSize value\n found: string, but expected to find: string\nfor file:\nstring: Cause: The _AllocationSize property of the indicated Local_Bitmap did not match the _Length value of its first extent.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07134: invalid global_dir_fileid value\n found: string, but expected to find: string: Cause: The ACFS Checker/Fixer found an inconsistency within the file system.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07135: Global_Metadata_Directory structure has incorrect _node_number value\n found: number, but expected to find: number\nfor structure:\nstring: Cause: The _node_number property of the indicated Global_Metadata_Directory structure was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07136: Global_Metadata_Directory structure has incorrect _global_free_blk_list value\n found: string, but expected to find: string\nfor structure:\nstring: Cause: The _global_free_blk_list property of the indicated Global_Metadata_Directory structure was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07137: Global_Metadata_Directory structure has incorrect _global_bitmap_fileid value\n found: string, but expected to find: string\nfor structure:\nstring: Cause: The _global_bitmap_fileid property of the indicated Global_Metadata_Directory structure was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07138: Global_Metadata_Directory structure has incorrect _SuperBlock_fileid value\n found: string, but expected to find: string\nfor structure:\nstring: Cause: The _SuperBlock_fileid property of the indicated Global_Metadata_Directory structure was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07139: Global_Metadata_Directory structure has incorrect _gdrfl_fileid value\n found: string, but expected to find: string\nfor structure:\nstring: Cause: The _gdrfl_fileid property of the indicated Global_Metadata_Directory structure was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07140: Global_Metadata_Directory structure has incorrect _dotofs_dir_fileid value\n found: string, but expected to find: string\nfor structure:\nstring: Cause: The _dotofs_dir_fileid property of the indicated Global_Metadata_Directory structure was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07141: Global_Metadata_Directory structure has incorrect _ready_dir_fileid value\n found: string, but expected to find: string\nfor structure:\nstring: Cause: The _ready_dir_fileid property of the indicated Global_Metadata_Directory structure was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07142: Global_Metadata_Directory structure has incorrect _repl_config_fileid value\n found: string, but expected to find: string\nfor structure:\nstring: Cause: The _repl_config_fileid property of the indicated Global_Metadata_Directory structure was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07143: Global_Metadata_Directory structure has incorrect _mmap_log_fileid value\n found: string, but expected to find: string\nfor structure:\nstring: Cause: The _mmap_log_fileid property of the indicated Global_Metadata_Directory structure was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07144: Global_Metadata_Directory structure has incorrect _repGlobalVFNPool_fileid value\n found: string, but expected to find: string\nfor structure:\nstring: Cause: The _repGlobalVFNPool_fileid property of the indicated Global_Metadata_Directory structure was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07145: Global_Metadata_Directory structure has incorrect _repl_config_tbl_fileid value\n found: string, but expected to find: string\nfor structure:\nstring: Cause: The _repl_config_tbl_fileid property of the indicated Global_Metadata_Directory structure was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07146: Global_Metadata_Directory structure has incorrect _repLogCutInitiatorBlock_fileid value\n found: string, but expected to find: string\nfor structure:\nstring: Cause: The _repLogCutInitiatorBlock_fileid property of the indicated Global_Metadata_Directory structure was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07147: Global_Metadata_Directory structure has incorrect _repLogCutInitiatorBlock_offset value\n found: string, but expected to find: string\nfor structure:\nstring: Cause: The _repLogCutInitiatorBlock_offset property of the indicated Global_Metadata_Directory structure was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07148: Global_Metadata_Directory structure has incorrect _snap_map_fileid value\n found: string, but expected to find: string\nfor structure:\nstring: Cause: The _snap_map_fileid property of the indicated Global_Metadata_Directory structure was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07149: Global_Metadata_Directory structure has incorrect _snaps_dir_fileid value\n found: string, but expected to find: string\nfor structure:\nstring: Cause: The _snaps_dir_fileid property of the indicated Global_Metadata_Directory structure was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07150: Global_Metadata_Directory structure has incorrect _global_tagdir_fileid value\n found: string, but expected to find: string\nfor structure:\nstring: Cause: The _global_tagdir_fileid property of the indicated Global_Metadata_Directory structure was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07151: Global_Metadata_Directory structure has incorrect _ea_change_fileid\n found: string, but expected to find: string\nfor structure:\nstring: Cause: The _ea_change_fileid property of the indicated Global_Metadata_Directory structure was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07152: orphan directory 'string' (file identifier: string) \nadded to 'lost+found' directory: Cause: The indicated directory did not have a valid entry in any parent directory. The ACFS Fixer move the file to the 'lost+found' directory.; Action: No further action is needed.
ACFS-07154: An attempt to create a low-fragmentation memory heap failed.\nstring will attempt to continue with the standard memory heap but may run out of memory.: Cause: A call to the Windows HeapCreate function failed. Refer to the accompanying message(s) for more information on the error.; Action: No further action is required unless there is an error using the standard memory heap. If there is an error using the standard memory heap then refer to the accompanying message(s) for information to resolve the problem.
ACFS-07155: An attempt to initialize a low-fragmentation memory heap failed.\nstring will attempt to continue with the standard memory heap but may run out of memory.: Cause: A call to the Windows HeapSetInformation function failed. Refer to the accompanying message(s) for more information on the error.; Action: The program will automatically attempt to continue with the standard memory heap but could run out of memory. No further action is required unless there is an error using the standard memory heap. To use low-fragmentation heaps, refer to Microsoft documentation on GlobalFlags values for executables that are not compatible with low-fragmentation heaps. Then use the regedit utility to unset those flags on the executable.
ACFS-07156: Local_Metadata_Directory structure has incorrect _map_file_disk_offset value\n found: string, but expected to find: string\nfor structure:\nstring: Cause: The _map_file_disk_offset property of the indicated Local_Metadata_Directory structure was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07157: Local_Metadata_Directory structure has incorrect _vol_log_disk_offset value\n found: string, but expected to find: string\nfor structure:\nstring: Cause: The _vol_log_disk_offset property of the indicated Local_Metadata_Directory structure was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07158: unable to create Security_Metadata file offset list\nfor file:\nstring: Cause: The ACFS Checker could not create the Security_Metadata file offset list. Refer to the accompanying message(s) for more information on the problem.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07159: Local_Metadata_Directory structure has incorrect _smf_fileid value \n found: string, but expected to find: string\nfor structure:\nstring: Cause: The _smf_fileid property of the indicated Local_Metadata_Directory structure was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07160: Local_Metadata_Directory structure has incorrect _it_rlog_fileid value\n found: string, but expected to find: string\nfor structure:\nstring: Cause: The _it_rlog_fileid property of the indicated Local_Metadata_Directory structure was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07161: Local_Metadata_Directory structure has incorrect _rlog_fileid value\n found: string, but expected to find: string\nfor structure:\nstring: Cause: The _rlog_fileid property of the indicated Local_Metadata_Directory structure was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07162: Local_Metadata_Directory structure has incorrect _it_rmap_file_fileid value\n found: string, but expected to find: string\nfor structure:\nstring: Cause: The _it_rmap_file_fileid property of the indicated Local_Metadata_Directory structure was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07163: Local_Metadata_Directory structure has incorrect _rmap_file_fileid value\n found: string, but expected to find: string\nfor structure:\nstring: Cause: The _rmap_file_fileid property of the indicated Local_Metadata_Directory structure was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07164: Local_Metadata_Directory structure has incorrect _repLocalVFNPool_fileid value\n found: string, but expected to find: string\nfor structure:\nstring: Cause: The _repLocalVFNPool_fileid property of the indicated Local_Metadata_Directory structure was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07165: invalid file identifier: string: Cause: The file identifier enetered must be a valid numeric value, greater than or equal to 0, and less than the maximum file identifier value for the file system.; Action: Re-enter a valid file identifier value.
ACFS-07167: Functionality may be limited due to problems accessing the accelerator volume: string.: Cause: An attempt to open the accelerator volume failed. Refer to the accompanying messages for more information on the problem.; Action: Correct the problems described in the accompanying messages if possible and rerun the command.
ACFS-07168: Global_BitMap has incorrect value for bitmap size\n found: string, but expected to find: string\nfor file:\nstring: Cause: The bitmap size property of the indicated Global_BitMap file was incorrect. Its value did not the bitmap size that was calculated for the file system.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07169: Global_BitMap has incorrect _AllocationSize value\n found: string, but expected to find: string\nfor file:\nstring: Cause: The _AllocationSize property of the indicated Global_BitMap file was incorrect. The _AllocationSize value was not large enough to store the Global_BitMap data as determined by the ACFS Checker.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07170: Global_BitMap has incorrect values for Extent[0]\n found: _FileOffset: string _Length: string _PhysicalDiskOffset: string\n, but expected to find: _FileOffset: string _Length: string _PhysicalDiskOffset: string\nfor file:\nstring: Cause: The _PhysicalDiskOffset property of the first extent of the indicated Global_BitMap file was incorrect. The Global_BitMap data must begin at the disk offset described in the message.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07171: attempt to read SuperBlock FileEntry failed\nfor file:\nstring: Cause: An attempt to read SuperBlock metadata failed. Refer to the accompanying message(s) for more information on the problem.; Action: Correct the problem described in the accompanying messages if possible and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ACFS-07172: file has incorrect values for Extent[number] \n found: _FileOffset: string _Length: string _PhysicalDiskOffset: string \n, but expected to find: _FileOffset: string _Length: string _PhysicalDiskOffset: string \nfor file:\nstring: Cause: One or more values of an extent of the indicated file was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07175: file has incorrect values for Extent[number]\n found: _FileOffset: string _Length: string \n, but expected to find: _FileOffset: string _Length: string\nfor file: \nstring: Cause: One or more values of an extent of the indicated file was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07176: file has invalid _AllocationSize value\n found: string, but expected to find: string\nfor file:\nstring: Cause: The _AllocationSize property of the indicated file was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07177: file has incorrect _FileSize value\n found: string, but expected to find: string\nfor file:\nstring: Cause: The _FileSize property of the indicated file was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07178: file has incorrect _granularity value\n found: number, but expected to find: number\nfor file:\nstring: Cause: The _granularity property of the indicated file was incorrect. Some ACFS internal files must have a _granularity value equal to -1 which indicates that the file has local extents.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07179: file has incorrect _NextFreeExtent value\n found: number, but expected to find: number\nfor file:\nstring: Cause: The _NextFreeExtent property of the indicated file was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07180: There is an inconsistency between the ACFS Map_File and the ACFS Log_File.: Cause: An inconsistency was found between the ACFS Map and Log Files which prevented the processing of transaction data.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07184: Log_File not processed for node number\nfor file:\nstring: Cause: A Log_File was found but not processed. Unprocessed Log_Files could result in false errors being reported because transaction data was not applied to the file system.; Action: There are two actions possible: 1. Run the ACFS Fixer which will automatically process all valid Log_Files. 2. Run the ACFS Checker and respond yes to any question pertaining to Log_File processing.
ACFS-07185: The ACFS Map _FileSize: number indicates that there is transaction data \nto be processed, but the ACFS Log _AllocationSize: number indicates that \nthere is no data available. \nACFS Map_File:\nstring \nACFS Log_File: \nfor file: \nstring: Cause: An inconsistency was found between the ACFS Map and Log Files which prevented the processing of transaction data.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07188: Map_File has entry with incorrect _Length value\n found: number\nfor file:\nstring: Cause: There are two possible causes: 1. The Map_File entry's _Length was equal to zero. 2. The Map_File entry's _Length was not a multiple of the volume's sector size as detailed in the message.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07189: Map_File has entry with incorrect _ActualDiskOffset value\n found: string minimum: string\nfor file:\nstring: Cause: The _ActualDiskOffset property for an entry in the indicated Map_File was incorrect. The _ActualDiskOffset value in a Map_File entry must be greater than the previous entry's _ActualDiskOffset.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07190: Map_File has an entry with invalid _LogDiskOffset value\n found: string minimum: string maximum: string\nfor file:\nstring: Cause: The _LogDiskOffset property for an entry in the indicated Map_File was incorrect. The _LogDiskOffset value in a Map_File entry must be within the corresponding Log_File data.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07191: Map_File has duplicate entries for _ActualDiskOffset:string\nfor file:\nstring: Cause: The indicated Map_File contained more than one entry for the same disk offset. _ActualDiskOffset values must be unique within a Map File.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07192: Map_File has incorrect Map_Entry _Length for the Volume_Disk_Header\n found: number, but expected to find: number\nfor file:\nstring: Cause: The _Length property for an entry in the indicated Map_File was incorrect. The entry was for a Volume_Disk_Header structure, but its _Length value did not match the size of a Volume_Disk_Header structure.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07193: Map_File entry with an invalid _ActualDiskOffset value\n found: string maximum: string\nfor file:\nstring: Cause: The _ActualDiskOffset property for an entry in the indicated Map_File was incorrect. The _ActualDiskOffset value that exceeded the size of this file system.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07195: metadata write failed while processing Volume_Log transaction data at disk offset: string\nfor file:\nstring: Cause: An error occurred while writing Volume_Log transaction data to the file system. Refer to the accompanying message(s) for more information.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07196: write failed for Map_File metadata structure at disk offset: string size: number bytes\nstructure type: string \nfor file:\nstring: Cause: An attempt to write a metadata structure to disk failed. Refer to accompanying message(s) for more information on the problem.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07197: discarding Volume_Log and Map_File contents on node number due to processing error: Cause: An error occurred while processing file system transaction data. Refer to the accompanying message(s) for more information on the problem.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07199: write failed for Volume_Log metadata structure at disk offset: string size: number bytes\nstructure type: string \nfor file:\nstring: Cause: An attempt to update a metadata structure of the indicated Volume_Log file failed. Refer to accompanying message(s) for more information on the problem.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07200: duplicate _SnapFetaFenum: string found for the following snapshots:\n: Cause: The _SnapFetaFenum property of the indicated snapshots had the same value. _SnapFetaFenum values must be unique.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer will resolve the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07201: Global_Free_Block list is corrupt: Cause: A metadata inconsistency was found within the Global_Free_Block list for the file system.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07202: Free_Block_List has incorrect _free_blk_count value\n found: number, but expected to find: number\nfor structure:\nstring: Cause: The _free_blk_count property of the indicated Free_Block_List was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07203: results for Snap_Map data may be limited or incorrect due to inconsistencies with Snap_Map metadata: Cause: The acfsdbg utility has identified the metadata inconsistency reported in the accompanying message.; Action: Run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07204: write failed for Global_BitMap metadata structure at disk offset: string size: number bytes\nstructure type: string \nfor file:\nstring: Cause: An attempt to update a metadata structure of the indicated Global_BitMap file failed. Refer to accompanying message(s) for more information on the problem.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07205: functionality may be limited due to File_Entry_Table metadata inconsistency: Cause: The acfsdbg utility has identified the metadata inconsistency reported in the accompanying message.; Action: Run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07206: read failed for Local_BitMap metadata structure at disk offset: string size: number bytes\nstructure type: string \nfor file:\nstring: Cause: An attempt to read a metadata structure of the indicated Local_BitMap file failed. Refer to accompanying message(s) for more information on the problem.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem
ACFS-07207: functionality related to snapshots disabled due to problems accessing Snap_Map file: Cause: The acfsdbg utility has identified the metadata inconsistency reported in the accompanying message.; Action: Run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07208: Local_BitMap (file identifier: string) has incorrect size\n found: string, but expected to find: string \nfor file:\nstring: Cause: The size property of the indicated Local_BitMap was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07209: Local_BitMap (file identifier: string) has incorrect Global_BitMap file offset: string or incorrect disk offset: string \nfor file:\nstring: Cause: The Global_BitMap offset property of the indicated Local_BitMap was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07211: mismatch between Local_BitMap (file identifier: string) and temporary Global_BitMap for disk offset: string: Cause: The bitmap data of the indicated Local_BitMap did not match the corresponding bitmap data of the temporary Global_BitMap for the described disk offset.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07212: temporary Global_BitMap bit set for disk offset: string exceeds maximum offset: string: Cause: The bitmap data of the temporary Global_BitMap referenced storage that is beyond the size of this file system.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07215: Volume_Disk_Header has invalid _VolSignature value\n found: 'string',\n but expected to find: string, string, string, string or string\nfor structure:\nstring: Cause: The _VolSignature property of the indicated Volume_Disk_Header was not a valid ACFS volume signature.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07216: Volume_Disk_Header has incorrect _Checksum value\n found: string, but expected to find: string\nfor structure:\nstring: Cause: The _Checksum property of the indicated Volume_Disk_Header did not match its calculated value.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07217: Volume_Disk_Header version does not match string version\n found: number.number, but expected to find: number.number\nfor structure:\nstring: Cause: The _MajorVersionNumber and _MinorVersionNumber properties of the indicated Volume_Disk_Header did not match the version of the ACFS Checker/Fixer or ACFS debug utility that was being used. The ACFS Checker/Fixer or ACFS debug utility was not compatible with this file system. There are two possible causes: 1. The version information in the Volume_Disk_Header structure was not correct. 2. The ACFS Checker/Fixer or ACFS debug utility was not the correct version for the file system.; Action: There are two possible actions: 1. If the file system version displayed in the message is valid then run a compatible version of the ACFS Checker/Fixer or ACFS debug utility. 2. If the file system version displayed in the message is not valid then restore the file system from backup.
ACFS-07218: Volume_Disk_Header has incorrect _VolVolumeSize value\n found: string maximum: string\nfor structure:\nstring: Cause: The _VolVolumeSize property of the indicated Volume_Disk_Header exceeded the size of the volume. The ACFS Checker temporarily assumed the maximum volume size during processing.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07219: Volume_Disk_Header has incorrect _VolVolumeSize value\n found: string minimum: string\nfor structure:\nstring: Cause: The _VolVolumeSize property of the indicated Volume_Disk_Header was less than the minimum supported volume size as detailed in the message. The ACFS Checker temporarily assumed the maximum volume size during processing.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07220: Volume_Disk_Header has incorrect _VolClusterSize value\n found: string, but expected to find: string\n- assuming default size: string\nfor structure:\nstring: Cause: The _VolClusterSize property of the indicated Volume_Disk_Header was incorrect. The ACFS Checker temporarily assumed the default value during processing.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07221: Volume_Disk_Header has incorrect _VolFETALPosition value\n found: string, but expected to find: string\nfor structure:\nstring: Cause: The _VolFETALPosition property of the indicated Volume_Disk_Header was incorrect. The ACFS Checker temporarily assumed the default File_Entry_Table offset during processing.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07222: Volume_Disk_Header has incorrect _VolOrigVolumeSize value\n found: string must be aligned on a string byte boundary\nfor structure:\nstring: Cause: The ACFS Checker/Fixer found an inconsistency within the file system.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07223: Volume_Disk_Header has incorrect _VolExtentHeaderSize value\n found: string, but expected to find: string\n- assuming default value: string\nfor structure:\nstring: Cause: The _VolExtentHeaderSize property of the indicated Volume_Disk_Header was incorrect. The ACFS Checker temporarily assumed the default value during processing.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07224: cannot process command due to Snap_Map File metadata inconsistency: Cause: An acfsdbg command was not executed due to a metadata inconsistency.; Action: Run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07225: Volume_Disk_Header has invalid _VolFileSystemEndian value\n found: character, but expected to find: character\nfor structure:\nstring: Cause: The _VolFileSystemEndian property of the indicated Volume_Disk_Header was invalid.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07226: Volume_Disk_Header has invalid _VolStateFlag values.\n found: string\n, but expected to find: string or string\nfor structure:\nstring: Cause: The _VolStateFlag property of the indicated Volume_Disk_Header contained one or more invalid values.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07227: missing snapshot name or identifier: Cause: A snapshot name or identifier was not entered as required for this command.; Action: Re-enter the command with a valid snapshot name or snapshot identifier.
ACFS-07228: cannot determine disk geometry for volume: string: Cause: The program was unable to determine the geometry of the indicated volume. Refer to the accompanying message(s) for more information on the problem.; Action: Correct the problem described in the accompanying messages if possible and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ACFS-07229: volume: string has invalid sector size\n found: number, but expected to find: number\n- assuming default value: number: Cause: The sector size of the indicated volume was invalid. The ACFS Checker temporarily assumed the default sector size during processing.; Action: Correct the problem described in the accompanying messages if possible and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ACFS-07230: cannot determine volume size for: string: Cause: The program was unable to determine the size of the indicated volume. Refer to the accompanying message(s) for more information on the problem.; Action: Correct the problem described in the accompanying messages if possible and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ACFS-07231: seek to end of volume failed for volume: string offset: string: Cause: The program was unable to seek to the end of the indicated volume. Refer to the accompanying message(s) for more information on the problem.; Action: Correct the problem described in the accompanying messages if possible and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ACFS-07232: seek to end of volume failed for volume: string\n requested offset: string returned offset: string: Cause: The request to seek to the end of the indicated volume failed. The offset set returned did not match the offset requested. Refer to the accompanying message(s) for more information on the problem.; Action: Correct the problem described in the accompanying messages if possible and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ACFS-07233: read failed for Primary Volume_Disk_Header at disk offset: string: Cause: An attempt to read the Primary Volume_Disk_Header at the indicated disk offset failed. Refer to the accompanying message(s) for more information on the problem.; Action: Correct the problem described in the accompanying messages if possible and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ACFS-07234: read failed for Alternate Volume_Disk_Header at disk offset: string: Cause: An attempt to read the Alternate Volume_Disk_Header at the indicated disk offset failed. Refer to the accompanying message(s) for more information on the problem. problem.; Action: Correct the problem described in the accompanying messages if possible and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ACFS-07235: extent[number] has invalid _PhysicalDiskOffset value\n found: 0, but expected to find: greater than 0\nfor file:\nstring: Cause: The _PhysicalDiskOffset property of an extent structure of the indicated file had a value of zero. _PhysicalDiskOffset values must be greater than zero.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07236: extent[number] has invalid _PhysicalDiskOffset value\n found: 0, but expected to find: greater than 0\nfor structure:\nstring: Cause: The _PhysicalDiskOffset property of an extent of the indicated extent structure had a value of zero. _PhysicalDiskOffset values must be greater than zero.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07237: read failed for File_Entry_Table extent metadata structure at disk offset: string\nfor file:\nstring: Cause: An attempt to read an extent metadata structure of the indicated file failed. Refer to the accompanying message(s) for more information on the problem.; Action: Correct the problem described in the accompanying messages if possible and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ACFS-07239: File_Entry_Table count incorrect\n found: number, but expected to find: number\nfor file:\nstring: Cause: The number of entries found in the File_Entry_Table file did not match the expected number of entries. One or more of the extent structures was invalid.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07240: Invalid Security_Metadata_File: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer will resolve the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07241: Security_Metadata file has invalid _security_descriptor record\nfor file:\nstring: Cause: A _security_descriptor record of the indicated Security_Metadata file was invalid.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07243: Security_Metadata file has no valid _security_data records\nfor file:\nstring: Cause: The indicated Security_Metadata file did not contain any valid valid _security_data records.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07245: Security_Metadata file contains invalid _security_descriptor data\nfor file:\nstring: Cause: The indicated Security_Metadata file contained at least one invalid _security_data record. Refer to the accompanying message(s) for more information on the problem.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07246: Security_Metadata file _Private structure is invalid for:\nfor file:\nstring: Cause: The _Private structure of the indicated Security_Metadata file was invalid. Refer to the accompanying message(s) for more information on the problem.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07247: Security_Metadata file has invalid Hash_Table data\nfor file:\nstring: Cause: The Hash_Table of the indicated Security_Metadata file contained inconsistent data. Refer to the accompanying message(s) for more information on the problem.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07250: Security_Metadata file _Private structure has invalid _maxFree value\n found: number minimum: number\nfor structure:\nstring: Cause: The _maxFree property of the indicated _Private metadata structure was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07251: Security_Metadata file _Private structure has invalid _freeDataListTail value\n found: number minimum: number\nfor structure:\nstring: Cause: The _freeDataListTail property of the indicated _Private metadata structure was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07252: Security_Metadata file node not on _freeDataList\nfor file:\nstring: Cause: One or more of the _security_data nodes of the indicated Security_Metadata file was not found on the free data node list. The _next property for one or more of the _security_data nodes was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07254: Security_Metadata file has invalid _security_record for _Administrator default\nfor file:\nstring: Cause: The default _Administrator _security_record of the indicated Security_Metadata file was invalid.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07256: file has unexpected _ProtectionBits value\n found: number, but expected to find: number\nfor file:\nstring: Cause: The _ProtectionBits property of the indicated files was not expected.; Action: No action is needed if the protection bits were intentionally set differently from the default.
ACFS-07257: unable to process request for volume string; volume is not open: Cause: An attempt to read metadata failed because the volume was not open. Refer to the accompanying messages for more information on the problem.; Action: Correct the problem described in the accompanying messages if possible and rerun the acfsdbg utility.
ACFS-07258: unable to reset context to snapshot string due to File_Entry_Table metadata inconsistency: Cause: The acfsdbg utility has identified the metadata inconsistency reported in the accompanying message.; Action: Run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services. Services.
ACFS-07259: file system does not contain a valid Local_Metadata_Directory: Cause: There was no valid Local_Metadata_Directory in the file system. At least one Local_Metadata_Directory is required.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07260: Volume_Disk_Header has incorrect _VolNumOFSNodes value\n found: number, but expected to find: number\nfor structure:\nstring: Cause: The _VolNumOFSNodes property of the indicated Volume_Disk_Header structure was incorrect. Its value did not match the number of valid ACFS nodes found.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07261: unable to reset context to snapshot string due to Snap_Map file metadata inconsistency: Cause: The acfsdbg utility has identified the metadata inconsistency reported in the accompanying message.; Action: Run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07262: unable to reset context to snapshot string because it no longer exists: Cause: The identified snapshot no longer exists due to on-disk metadata changes that are allowed whenever the acfsdbg utility is operating in read-only mode.; Action: Enter the 'primary' or 'snap snapshot name' command to set context.
ACFS-07263: Free_Block_List has incorrect _first_free_group value\n found: number, but expected to find: number\nfor structure:\nstring: Cause: The _first_free_group property of the indicated Free_Block_List structure was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07264: Free_Block_List has incorrect _last_free_blk value\n found: number, but expected to find: number\nfor structure:\nstring: Cause: The _last_free_blk property of the indicated Free_Block_List structure was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07265: write failed for Free_Block metadata structure at disk offset: string size: number bytes\nfor structure:\nstring: Cause: An attempt to write a Free_Block metadata structure to disk failed. Refer to accompanying message(s) for more information on the problem.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07266: write failed for Free_Block_List metadata structure at disk offset: string size: number bytes\nfor structure:\nstring: Cause: An attempt to write a Free_Block_List metadata structure to disk failed. Refer to accompanying message(s) for more information on the problem.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07267: file marked for deletion (file identifier: string, disk offset: string) cannot be removed due to inconsistent file metadata: Cause: Inconsistent metadata was found for the indicated file that was marked for deletion. The file could not be deleted.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07268: file marked for deletion (file identifier: string, disk offset: string) has invalid _LinkCount value\n found: number, but expected to find: 0: Cause: The indicated file was marked for deletion, but its _LinkCount property was not zero. Files to be deleted must have a _LinkCount value of zero. The file could not be deleted.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07271: orphan file : string (file identifier: string) added to 'lost+found' directory: Cause: The indicated file did not have a valid entry in any parent directory. The ACFS Fixer move the file to the 'lost+found' directory.; Action: No further action is needed.
ACFS-07272: read failed for extent metadata structure at disk offset: string\nfor file:\nstring: Cause: An attempt to read an extent metadata structure for the indicated file failed. Refer to the accompanying message(s) for more information on the problem.; Action: Correct the problem described in the accompanying messages if possible and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ACFS-07274: missing or invalid snapshot name: Cause: No snapshot name was provided or the name entered was not valid.; Action: Re-enter the command with a valid snapshot name.
ACFS-07275: cannot read File_Entry_Table _FileEntry metadata structure\n- file system validation cannot continue: Cause: An attempt to read the _FileEntry metadata structure of the File_Entry_Table failed. The File_Entry_Table is a critical ACFS metadata structure that is required for file system validation or repairs. The ACFS Checker/Fixer could not process the file system. NOTE: It is also possible that there was no ACFS file system on this volume.; Action: Correct the problem indicated by the accompanying messages if possible and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows). If the problem cannot be resolved then restore the file system from a backup copy.
ACFS-07276: File_Entry_Table _FileEntry metadata structure is invalid\n- file system validation cannot continue: Cause: The File_Entry_Table's _FileEntry metadata structure is either corrupt or is missing critical information. NOTE: It is also possible that there is no ACFS file system on the volume.; Action: Restore the file system from a backup copy.
ACFS-07280: checking File_Entry_Table entry: string at disk offset: string: Cause: The ACFS Checker found a File_Entry_Table entry that has not been processed. This entry was an orphan file or an orphan internal metadata structure.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07282: read failed for File_Entry_Table entry: string at disk offset string: Cause: An attempt to read a File_Entry_Table entry failed. Refer to the accompanying message(s) for more information on the problem.; Action: Correct the problem described in the accompanying messages if possible and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ACFS-07283: orphan File_Entry_Table metadata structure found for\n identifier: string at disk offset: string\n structure type: string: Cause: A File_Entry_Table entry was found that had not been processed. This entry was an orphan file or an invalid internal metadata structure.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07284: orphan system file found for file identifier: string at disk offset:string: Cause: The indicated system file did not have a valid parent directory.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07285: snapshot: string (identifier: number) has invalid File_Entry_Table identifier: string that exceeds the maximum value for this file system: string: Cause: The acfsdbg utility has identified the metadata inconsistency reported in the accompanying message.; Action: Run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07286: orphan file found for file identifier: string at disk offset: string: Cause: The indicated file did not have a valid parent directory.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07287: orphan Free_Block metadata structure found for file identifier: string at disk offset: string: Cause: The indicated Free_Block metadata structure was not found on any free block list.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07288: orphan file 'string' (file identifier: string) \nadded to 'lost+found' directory: Cause: The indicated file did not have a valid entry in any directory which meant that the file did not have a valid file name. The file was given the generic name described in the message and moved to the 'lost+found' directory.; Action: No further action is needed.
ACFS-07289: orphan Local_Metadata_Directory metadata structure found for file identifier: string at disk offset: string: Cause: The indicated Local_Metadata_Directory metadata structure was not found on any _Locator list for Local_Metadata_Directory structures.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07290: orphan Free_List_Header metadata structure found for file identifier: string at disk offset: string: Cause: The indicated Free_List_Header metadata structure was not found on any valid Local_Metadata_Directory structure.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07291: orphan _Locator metadata structure found for file identifier: string at disk offset: string: Cause: The indicated _Locator metadata structure was not found in any list of valid _Locator structures.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07292: orphan Global_Metadata_Directory metadata structure found for file identifier: string at disk offset: string: Cause: The File_Entry_Table contained a duplicate Global_Metadata_Directory metadata structure. Global_Metadata_Directory structures must be unique.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07294: orphan Global_Virtual_FileID_Pool metadata structure found for identifier: string at disk offset: string: Cause: The File_Entry_Table contained a duplicate entry for the Global_Virtual_FileID_Pool metadata structure. Global_Virtual_FileID_Pool structures must be unique.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07295: orphan Local_Virtual_FileID_Pool metadata structure found for identifier: string at disk offset: string: Cause: The indicated Local_Virtual_FileID_Pool metadata structure was not found on any valid Local_Metadata_Directory structure.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07296: orphan Replication_Log_Initiator metadata structure found for identifier: string at disk offset: string: Cause: The File_Entry_Table contained a duplicate entry for a Replication_Log_Initiator metadata structure. Replication_Log_Initiator structures must be unique.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07297: File_Entry_Table entry: string at disk offset: string is not a valid metadata structure: Cause: The indicated entry in the File_Entry_Table was not a metadata structure recognized by ACFS.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07298: cannot convert file identifier: 'string' to numeric value: Cause: The format entered for the file identifier was invalid.; Action: Use the acfsdbg utility help (-h) option for a list of commands and format options for entering data.
ACFS-07300: directory Hash_Table contains duplicate entries for offset: string\nfor file:\nstring: Cause: The Hash_Table of the indicated directory file had duplicate entries for the offset described in the message. Hash_Table entries must map to unique offsets.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07301: directory _hash_key: string for offset: string has no corresponding file entry\nfor file:\nstring: Cause: The _hash_key property of the indicated directory file was invalid. Its value did not reference a valid file entry.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07302: directory _hash_key for offset: string is incorrect\n found: string, but expected to find: string\nfor file:\nstring: Cause: The _hash_key property of the indicated directory file was incorrect. Its value did not match the hash value calculated for the corresponding file entry.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07303: Security_Metadata file Hash_Table contains multiple entries for offset: string\nfor file:\nstring: Cause: The Hash_Table of the indicated Security_Metadata file had duplicate entries for the offset described in the message. Hash_Table entries must map to unique offsets.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07304: Security_Metadata file _hash_key: string for offset: string has no corresponding entry\nfor file:\nstring: Cause: The _hash_key property of the indicated Security_Metadata file was invalid. Its value did not reference a valid entry.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07305: Security_Metadata file _hash_key for offset: string is incorrect\n found: string, but expected to find: string\nfor file:\nstring: Cause: The _hash_key property of the indicated Security_Metadata file was incorrect. Its value did not match the hash value calculated for the corresponding entry.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07306: Hash_Table _hash_key order is incorrect\nfor file:\nstring: Cause: The _hash_key properties of the Hash_Table of the indicated file were not ordered correctly.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07308: Hash_File_Index structure for block number at disk offset: string already processed\nfor file:\nstring: Cause: The Hash_File node list of the indicated file was invalid. One or more of the Hash_File structures had an invalid _next property.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07309: cannot access Hash_File_Index node metadata structure at disk offset: string\nfor file:\nstring: Cause: An attempt to access the indicated Hash_File_Index metadata structure failed. Refer to the accompanying message(s) for more information on the problem.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07310: Hash_File_Index node has incorrect _next value\n found: string, but expected to find: string\nfor file:\nstring: Cause: The _next property of the indicated Hash_File_Index structure was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07311: Hash_Bucket for block number at disk offset: string already processed\nfor structure:\nstring: Cause: The Hash_Bucket structure of the indicated file has already been processed. One or more of the Hash_File structures had an invalid _next property.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07312: cannot access Hash_Bucket metadata structure at disk offset: string\nfor file:\nstring: Cause: An attempt to access the indicated Hash_Bucket metadata structure failed. Refer to the accompanying message(s) for more information on the problem.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07313: Hash_Bucket has incorrect _controlling_bkt value\n found: number, but expected to find: number\nfor structure:\nstring: Cause: The _controlling_bkt property of the indicated Hash_Bucket structure was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07314: Hash_Bucket has incorrect _split_count value\n found: number, but expected to find: number\nfor file:\nstring: Cause: The _split_count property of the indicated Hash_Bucket structure was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07315: Hash_Bucket has incorrect _next value\n found: number, but expected to find: number\nfor file:\nstring: Cause: The _next property of the indicated Hash_Bucket structure was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07316: cannot access Hash_File_Master_Block metadata structure at disk offset: string\nfor file:\nstring: Cause: An attempt to access the indicated Hash_File_Master_Block metadata structure failed. Refer to the accompanying message(s) for more information on the problem.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07317: Hash_File metadata structure for block:number at disk offset: string already processed\nfor file:\nstring: Cause: The list of nodes of the indicated Hash_File file was invalid. One or more of the Hash_File structures had an invalid _next property.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07318: Hash_File_Master_Block structure has incorrect _initial_bkt_count value\n found: number, but expected to find: number\nfor structure:\nstring: Cause: The _initial_bkt_count property of the indicated Hash_File_Master_Block structure was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07319: Hash_File_Master_Block structure has incorrect _double_count value\n found: number, but expected to find: number\nfor file:\nstring: Cause: The _double_count property of the indicated Hash_File_Master_Block structure was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07320: Hash_File_Master_Block structure has incorrect value for entry number in _hash_bucket_group array\n found: number, but expected to find: number\nfor structure:\nstring: Cause: The entry in _hash_bucket_group array of the indicated Hash_File_Master_Block was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07321: _hash_entry number has no corresponding entry\nfor file:\nstring: Cause: The _hash_entry property in the Hash_Table of the indicated file did not have a valid entry associated with it.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07322: metadata read failed at disk offset: string size: number bytes\nfor file:\nstring: Cause: An attempt to read metadata of the indicated file failed. Refer to the accompanying message(s) for more information on the problem.; Action: Correct the problem described in the accompanying messages if possible and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ACFS-07326: metadata read failed at disk offset: string\n bytes requested: number bytes returned: number\nfor file:\nstring: Cause: An attempt to read metadata of the indicated file failed. The amount of data returned did not match the amount requested. Refer to the accompanying message(s) for more information on the problem.; Action: Correct the problem described in the accompanying messages if possible and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ACFS-07327: metadata write failed at disk offset: string size: number bytes\nfor file:\nstring: Cause: An attempt to write metadata of the indicated file failed. Refer to accompanying message(s) for more information on the problem.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07331: metadata write failed at disk offset: string\n bytes requested: number bytes written: number\nfor file:\nstring: Cause: An attempt to write metadata of the indicated file failed. The amount of data written did not match the amount requested. Refer to the accompanying message(s) for more information on the problem.; Action: Correct the problem described in the accompanying messages if possible and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ACFS-07332: cannot convert snapshot identifier: 'string' to numeric value: Cause: The format entered for the snapshot identifier was invalid.; Action: Use the acfsdbg utility help (-h) option for a list of commands and format options for entering data.
ACFS-07333: invalid snapshot identifier entered: string\n minimum: 1 maximum: number: Cause: The snapshot identifier entered was not within the valid range for this file system.; Action: Re-enter the command with a snapshot identifier that is within the valid range described in the message.
ACFS-07334: invalid snapshot name 'string' entered: Cause: The snapshot name entered did not exist.; Action: Re-enter the command with the name or identifier of a valid snapshot.
ACFS-07335: Directory_Node has invalid _dir_entry_free_list_tail value\n found: number maximum: number\nfor structure:\nstring: Cause: The _dir_entry_free_list_tail property of the indicated Directory_Node structure was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07336: Directory_Node structure has invalid _next_free_dirnode value\n found: number maximum: number\nfor structure:\nstring: Cause: The _next_free_dirnode property of the indicated Directory_Node structure was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07337: Directory_Entry structure has incorrect file identifier for file 'string'\n found: string, but expected to find: string\nfor structure:\nstring: Cause: The file identifier property of the indicated Directory_Entry structure did not match the file identifier of the corresponding file.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07338: Directory_Entry structure has incorrect _rec_len value for file 'string'\n found: number, but expected to find: number\nfor structure:\nstring: Cause: The _rec_len property of the indicated Directory_Entry structure was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07339: Directory_Entry structure has incorrect _name_len value for file 'string'\n found: number, but expected to find: number\nfor structure:\nstring: Cause: The _name_len property of the indicated Directory_Entry structure was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07340: Directory_Entry structure has invalid or incorrect _attributes for file 'string'\n found: string\n, but expected to find: string\nfor structure:\nstring: Cause: The _attributes property of the indicated Directory_Entry structure did not match the _attributes property of the corresponding file.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07341: starting disk offset string exceeds ending disk offset string: Cause: The starting storage map offset was greater than the ending offset.; Action: Re-enter the command with valid disk offsets.
ACFS-07342: Directory_Entry structure has incorrect filename for file\n found: 'string', but expected to find: 'string'\nfor structure:\nstring: Cause: The filename property of the indicated Directory_Entry structure did not match the name of the file.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07343: unused Directory_Entry structure has incorrect _name_len value\n found: number, but expected to find: number\nfor structure:\nstring: Cause: The _name_len property of the indicated Directory_Entry structure was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07344: Directory_Entry structure has incorrect _rec_len value for file 'string'\n found: number maximum: number\nfor structure:\nstring: Cause: The _rec_len property of the indicated Directory_Entry structure was greater than the maximum value.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07345: Directory_Entry structure has incorrect _rec_len value for file 'string'\n found: number minimum: number\nfor structure:\nstring: Cause: The _rec_len property of the indicated Directory_Entry structure was less than the minimum value.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07346: Directory_Entry structure has invalid _name_len value\n found: number operating system maximum: number\nfor structure:\nstring: Cause: The _name_len property of the indicated Directory_Entry structure was greater than the maximum value for this operating system.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07347: Directory_Entry structure has incorrect _name_len value\n found: number maximum: number\nfor structure:\nstring: Cause: The _name_len property of the indicated Directory_Entry structure was greater than the maximum value for this entry.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07350: command disabled due to lack of File_Entry_Table context; enter 'primary' or 'snap' to set context: Cause: The acfsdbg utility could not process the request because the File_Entry_Table context was not set. The acfsdbg utility requires a valid File_Entry_Table context to locate on-disk metadata structures.; Action: Enter 'primary' or 'snap snapshot name' command to set context.
ACFS-07351: requested Snap_Info_Entry structure not available due to inconsistencies with Snap_Map metadata: Cause: The acfsdbg utility has identified the metadata inconsistency reported in the accompanying message.; Action: Run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07352: snapshot directory contains files with incorrect attributes; attempting to continue processing: Cause: The _attributes property for a file in the indicated snapshot directory was incorrect. The _attributes value indicated that the file was not a directory. All files in a snapshot directory must be directories.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07354: file has incorrect or invalid _attributes value\n found: string\n, but expected to find: string\nfor file:\nstring: Cause: The _attributes property of the indicated file was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07355: Cannot fix orphaned files because the lost+found directory is damaged.: Cause: Fsck could not move the orphan files because there was an inconsistency with the lost+found directory. Files that do not have a valid parent directory are considered to be orphan files and are moved to the lost+found directory.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07356: file is a symbolic link but has no storage for the target name \nfor file:\nstring: Cause: The indicated file was a symbolic link but did have a target. The target of a symbolic link must have storage.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07360: deleting file due to invalid _attributes: string\nfile:\nstring: Cause: The _attributes property of the indicated file was invalid. The file must be deleted in order to preserve the integrity of the file system.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07361: truncating file 'string' to number bytes\nfor file:\nstring: Cause: The indicated file was truncated in order to preserve file system integrity.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07363: Volume_Disk_Header has invalid _VolFeatureFlag values.\n found: string\n, but expected to find: string or string\nfor structure:\nstring: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer will resolve the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07364: file has incorrect values for Extent[number]\n found: _Length: string _PhysicalDiskOffset: string\n, but expected to find: _Length: string _PhysicalDiskOffset: string\nfor file:\nstring: Cause: One or more or the extent properties of the indicated file was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07365: extent metadata structure has incorrect values for Extent[number]\n found: _FileOffset: string _Length: string _PhysicalDiskOffset: string \n, but expected to find: _FileOffset: string _Length: string _PhysicalDiskOffset: string \nfor structure:\nstring: Cause: One or more properties of the indicated extent metadata structure was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07366: directory has incorrect _attributes value\n found: string\n, but expected to find: string\nfor file:\nstring: Cause: The _attributes property of the indicated directory file was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07367: Volume_Disk_Header has invalid _VolStateFlag values for accelerator volume: string\n found: string,\n but expected to find: string \nfor structure:\nstring: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer will resolve the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07369: directory has invalid _FileSize value\n found: number minimum: number\nfor file:\nstring: Cause: The _FileSize property of the indicated directory file was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07370: directory has invalid _FileSize: string _AllocationSize: string values\nfor file:\nstring: Cause: The _FileSize and _AllocationSize properties of the indicated directory file were incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07374: cannot access directory _Private structure for block number at disk offset: string\nfor file:\nstring: Cause: An attempt to access the indicated directory _Private metadata structure failed. Refer to the accompanying message(s) for more information on the problem.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07375: directory _Private structure at disk offset: string contains invalid data\nfor file:\nstring: Cause: The _Private structure of the indicated directory file contained invalid data. Refer to the accompanying message(s) for more information on the problem.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07376: directory _Private structure has incorrect header type at disk offset: string, this file may not be a directory\n found: string, but expected to find: string\nfor file:\nstring: Cause: The indicated file did not contain a _Private directory metadata structure as required for directory files. It appeared that the file was incorrectly identified as being a directory.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07377: directory has invalid node list\nfor file:\nstring: Cause: The node list of the indicated directory file was invalid. There are three possible causes: 1. One or more of the file's directory structures had an invalid structure header. 2. The _next_dirnode property of one or more of the file's directory structures was incorrect. 3. The _first_dirnode property of the _Private directory structure was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07378: directory _Private structure has incorrect _last_dirnode value\n found: number, but expected to find: number\nfor file:\nstring: Cause: The _last_dirnode property of the indicated _Private directory structure was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07379: directory has invalid free block list\nfor file:\nstring: Cause: The free block list of the indicated directory file was invalid. There are three possible causes: 1. One or more of the file's directory structures had an invalid structure header. 2. The _next_free_dirnode property of one or more of the file's directory structures was incorrect. 3. The _dir_entry_free_list_head property of the _Private directory structure was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07381: directory _Private structure has incorrect _dir_entry_free_list_tail value\n found: number, but expected to find: number\nfor file:\nstring: Cause: The _ dir_entry_free_list_tail property of the indicated _Private directory structure was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07382: directory has invalid hash block free list; invalid reference for free hash block\n found: number maximum: number\nfor file:\nstring: Cause: The hash block free list of the indicated directory file was invalid. There are two possible causes: 1. The _hash_blk_free_list property of the _Private directory structure referenced a block that exceeded the directory's size. 2. The _next_free_blk property of a directory free block referenced a block that exceeded the directory's size.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07383: directory has invalid hash block free list\nfor file:\nstring: Cause: The free hash block list of the indicated directory file was invalid. There are three possible causes: 1. One or more of the file's directory structures had an invalid structure header. 2. The next_free_blk property of one or more of the file's directory structures was incorrect. 3. The hash_blk_free_list property of the _Private directory structure was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07384: snapshot: string (identifier: number) has invalid _SnapIncarnationNumber\n found: 0, but expected to find: > 0\nfor structure:\nstring: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer will resolve the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07385: directory has orphan Directory_Node metadata structure for block number at disk offset: string\nfor file:\nstring: Cause: The indicated directory file had a Directory_Node metadata structure that was not found on any directory node list.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07386: directory has incorrect _FileSize value\n found: string, but expected to find: string\nfor file:\nstring: Cause: The _FileSize property of the indicated directory file was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07388: directory contains invalid _Private structure for block number at disk offset: string\nfor file:\nstring: Cause: A _Private metadata structure of the indicated directory file was found in the wrong block. _Private metadata structures must be located at block one of a directory's metadata.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07389: directory has orphan free block number at disk offset: string\nfor file:\nstring: Cause: The indicated directory file had a free block that was not found on the directory's free list.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07391: directory has invalid metadata structure string type for block number at disk offset: string\nfor file:\nstring: Cause: The structure found at the block of the indicated directory file was not a valid directory metadata structure.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07392: Directory_Entry has incorrect or invalid _attributes value\n found: string\n, but expected to find: string\nfor file:\nstring: Cause: The _attributes property of the indicated Directory_Entry was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07395: directory has incorrect or invalid _attributes values\n found: string\n, but expected to find: string\nfor file:\nstring: Cause: The _attributes property of the indicated directory file was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07396: directory has incorrect Hash_Table data\nfor file:\nstring: Cause: The Hash_Table of the indicated directory file contained inconsistent data. Refer to the accompanying message(s) for more information on the problem.; Action: Correct the problem described in the accompanying messages if possible and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ACFS-07399: directory has incorrect _LinkCount value\n found: number, but expected to find: number\nfor file:\nstring: Cause: The _LinkCount property of the indicated directory file was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07400: mismatch between _NOLSTXPTR feature and _NOUPHDRPTR feature\n _NOLSTXPTR: string _NOUPHDRPTR: string\nfor file:\nstring: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer will resolve the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07402: Deferred_Delete_Storage_List structure has invalid delete list pointers: _PrevDeferredListLink: string _NextDeferredListLink: string\nfor structure:\nstring: Cause: The _PrevDeferredListLink or _NextDeferredListLink property of of the indicated structure were incorrect. Both values must be zero or non-zero.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07407: Snap_Map_Header contains invalid _SnapCreatePending field\nfound: 0, but expected to find: > 0\nfor structure:\nstring: Cause: The acfsdbg utility has identified the metadata inconsistency reported in the accompanying message.; Action: Run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07408: Snap_Map_Header contains invalid _SnapDeletePending field\nfound: 0, but expected to find: > 0\nfor structure:\nstring: Cause: The acfsdbg utility has identified the metadata inconsistency reported in the accompanying message.; Action: Run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07411: snapshot metadata checking will be limited due to an error reading snapshot metadata: Cause: An attempt to read snapshot metadata failed. Snapshot validation was limited since not all snapshot metadata was not available.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07412: Accelerator Volume_Disk_Header has invalid _VolSignature value\n found: 'string'\n, expected: string\nfor structure: \nstring: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer will resolve the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07413: unable to create internal structure needed for processing: Cause: Refer to the accompanying message(s) for more information on the problem.; Action: Correct the problem described in the accompanying messages if possible and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ACFS-07414: snapshot: string (identifier: number) has invalid snap_map_tuples for file:\nstring: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer will resolve the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07415: invalid snap_map_tuple: ( string, string ) for disk offset: string: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer will resolve the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07416: file has invalid _FileSize value\n found: string minimum: string\nfor file:\nstring: Cause: The _FileSize property of the indicated file was invalid.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07417: Snap_Map_Header structure has invalid _snap_incarnation values; _SnapHighestActiveIncarnNumber: number must be less than _SnapNextIncarnationNumber: number\nfor structure:\nstring: Cause: One or both of the _SnapHighestActiveIncarnNumber and _SnapNextIncarnationNumber properties of the indicated Snap_Map_Header metadata structure was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07418: Snap_Map_Header structure has invalid _SnapCreatePending value\n found: number, but expected to find: number or < number\nfor structure:\nstring: Cause: The _SnapCreatePending property of the indicated Snap_Map_Header metadata structure was incorrect. The _SnapCreatePending value must be zero or less than the value indicated in the message.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07419: Snap_Map_Header structure has invalid _SnapDeletePending value\n found: number, but expected to find: number or < number\nfor structure:\nstring: Cause: The _SnapDeletePending property of the indicated Snap_Map_Header metadata structure was incorrect. The _SnapDeletePending value must be zero or less than the value indicated in the message.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07420: found partially created snapshot for snapshot: 'string': Cause: Initialization of the indicated snapshot did not complete. There are two possible causes: 1. The volume went offline while the snapshot was being created. 2. The process creating the snapshot was unexpectedly terminated do to a shutdown of the system.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem. The ACFS Fixer will remove this snapshot.
ACFS-07421: found partially deleted snapshot: Cause: A snapshot was not completely deleted. There are several possible causes: 1. The volume was unmounted before the asynchronous phase of snapshot deletion had completed. 2. The volume went offline while the snapshot was being deleted. 3. The process deleting the snapshot was unexpectedly terminated do to a shutdown of the system.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem. The ACFS Fixer will remove this snapshot.
ACFS-07423: snapshot 'string' has invalid file identifier\n found: string maximum: string\nfor structure:\nstring: Cause: The file identifier property of the indicated snapshot was invalid. Its value exceeded the maximum value for the file system.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07424: snapshot 'string' has invalid _SnapIncarnationNumber value\n found: number maximum: number\nfor structure:\nstring: Cause: The _SnapIncarnationNumber property of the indicated snapshot was invalid.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07425: snapshot (_snapid value: string) has invalid name: 'string'\nfor structure:\nstring: Cause: The name of indicated snapshot contained invalid characters.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07426: snapshot 'string' has invalid _SnapVisibility value\n found: number, but expected to find: number or number\nfor structure:\nstring: Cause: The _SnapVisibility property of the indicated snapshot was invalid.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07427: duplicate _SnapIncarnationNumber: number found for snapshots 'string' and 'string': Cause: The _SnapIncarnationNumber property of the indicated snapshots had the same value. _SnapIncarnationNumber values must be unique across all snapshots.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem. The ACFS Fixer will delete the second snapshot.
ACFS-07429: Snap_Map_Header structure has incorrect _SnapCount value\n found: number, but expected to find: number\nfor structure:\nstring: Cause: The _SnapCount property of the indicated Snap_Map_Header metadata structure was incorrect. The _SnapCount value did not match the number of valid snapshots found.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07430: cannot determine free space for volume associated with directory 'string'; attempting to continue with current directory 'string': Cause: A temporary file is needed to store information during processing. This file was targeted for the indicated directory. The ACFS Checker was unable to determine the mount of space available for the volume associated with the directory. Refer to the accompanying message(s) for more information on the problem.; Action: No further action is needed. The ACFS Checker/Fixer will attempt to continue processing with the current directory.
ACFS-07431: cannot determine free space for volume associated with current directory 'string': Cause: A temporary file is needed to store information during processing. This file was targeted for the current directory. The ACFS Checker was unable to determine the mount of space available for the volume associated with the directory. Refer to the accompanying message(s) for more information on the problem.; Action: Correct the problem described in the accompanying messages if possible and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ACFS-07432: insufficient space available to store temporary file in\ndirectory 'string' or directory 'string'\nspace needed: number bytes\n- unable to continue: Cause: A temporary file is needed to store information during processing but there was not enough space to store the file in either of the The size of this file is dependent on the size of the file system. indicated directories.; Action: Provide sufficient space as described in the message to store the the temporary file in either of the indicated directories. Rerun the ACFS Checker/Fixer once there is sufficient storage to store the temporary file.
ACFS-07435: invalid path name length for temporary file\n length: number minimum: number maximum: number: Cause: The path name for a temporary file does not exist or its length exceeds the maximum for this system. Refer to the accompanying message(s) for more information on the problem.; Action: Correct the problem described in the accompanying messages if possible and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ACFS-07436: string has encountered an internal error: invalid parameter passed to fb_create: Cause: The ACFS Checker/Fixer or ACFS Debug utility has encountered an unexpected, internal error.; Action: Contact Oracle Support Services.
ACFS-07437: string has encountered an internal error: invalid parameter passed to fb_ref\n disk offset: string size: string fbSize: string fbCacheSize: string: Cause: The ACFS Checker/Fixer or ACFS Debug utility has encountered an unexpected, internal error.; Action: Contact Oracle Support Services.
ACFS-07438: file has storage allocated to it that is also allocated to another file\nfor file:\nstring: Cause: Storage allocated to the indicated file was also allocated to at least one other file. Storage can only be allocated to a single file. Storage can never be allocated to multiple files.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07439: Snapshot_BitMap conflicts with the Global_BitMap for disk offset: string: Cause: One or more snapshot bitmaps claimed storage that was also claimed by the Global_BitMap.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem. The ACFS Fixer will remove all snapshots whose bitmap conflicts with the Global_BitMap.
ACFS-07440: Snapshot_BitMap has bit set for non-existing snapshot for disk offset: string: Cause: One or more bitmaps reserved for unused snapshot incorrectly claimed storage. Bitmaps for snapshots that are not in use cannot claim any storage.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07441: Snapshot_BitMap has bits set for storage at disk offset: string that is beyond the file system size: Cause: One or more snapshot bitmaps incorrectly claimed storage that exceeded the size of the file system.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07443: Global_BitMap has invalid value for number of bits set\n found: string maximum: string\nfor file:\nstring: Cause: The Global_BitMap property that indicates the number of bits set exceeded the size of the bitmap.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07444: Global_BitMap has invalid value for number of bits set.\n found: string, but expected to find: string\nfor file:\nstring: Cause: The Global_BitMap property that indicates the number of bits set did not match the amount of storage allocated to all valid files.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07445: Global_BitMap has invalid value for next offset to search\n found: string maximum: string\nfor file:\nstring: Cause: The Global_BitMap property that indicates the next offset to search for available bits to allocate exceeded the size of the bitmap.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07446: mismatch between temporary Global_BitMap and on-disk Global_BitMap: Cause: The temporary Global_BitMap that was populated by traversing all valid file system data did not match the on-disk copy of the Global_BitMap.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07447: invalid snap_map_tuple for disk offset: string\n found: ( 0, 0 ), but expected non-zero values\nfor file:\nstring: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer will resolve the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07448: invalid snap_map_tuple for disk offset: string\n found: ( 0, 0 ), but expected non-zero values: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer will resolve the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07449: snapshot 'string' storage bitmap is incorrectly set for disk offset: string: Cause: The bitmap of the indicated snapshot claimed storage that was allocated to allocated file. Storage can only be allocated to a single file. Storage can never be allocated to multiple files.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem. The ACFS Fixer will remove this snapshot.
ACFS-07450: snapshot 'string' storage bitmap is not set for disk offset: string: Cause: The bitmap of the indicated snapshot did not claim storage that was allocated to one of its files. A snapshot's bitmap must claim all storage allocated to its files.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem. The ACFS Fixer will remove this snapshot.
ACFS-07451: snapshot 'string' storage bitmap is incorrectly set for disk offset: string with no corresponding file data: Cause: The bitmap of the indicated snapshot claimed storage but the storage was not allocated to any file.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07452: unable to locate directory for snapshot 'string' (id: number)\n processing will continue for other snapshots: Cause: The directory of the indicated snapshot was not found. This snapshot could not be processed.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07453: Snap_Root_Directory file identifier for snapshot 'string' was incorrect\n found: string, but expected to find: string\nfor structure:\nstring: Cause: The Snap_Root_Directory file identifier property of the indicated snapshot was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07455: unable to open file: string: Cause: An attempt to open a file failed. Refer to the accompanying message(s) for more information on the error.; Action: Correct the problem described in the accompanying messages if possible and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ACFS-07456: Global_Metadata_Directory structure has incorrect _accelerator_GBM_fileid value\n found: string, but expected to find: string\nfor structure:\nstring: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer will resolve the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07458: The request to cancel string was incomplete because volume string was not accessible. The file system cannot be mounted in this state.\nRerun string once the volume is accessible to enable file system mounts.: Cause: The ACFS Checker/Fixer could not reset the volume to allow for file system mounts because the volume was not accessible. Refer to the accompanying message(s) for more information on the error.; Action: Rerun the ACFS Checker/Fixer once the volume is accessible to enable file system mounts.
ACFS-07459: Volume_Label metadata structure has invalid _VolLabelLength value\n found: number maximum: number\nfor structure:\nstring: Cause: The _VolLabelLength property of the indicated Volume_Label metadata structure exceeded the maximum value.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07460: Volume_Label metadata structure has invalid _VolIDLength value\n found: number maximum: number\nfor structure:\nstring: Cause: The _VolIDLength property of the indicated Volume_Label metadata structure exceeded the maximum value.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07461: Volume_Label metadata structure has invalid _ClusterNameLength value\n found: number maximum: number\nfor structure:\nstring: Cause: The _ClusterNameLength property of the indicated Volume_Label metadata structure exceeded the maximum value.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07462: file has incorrect or invalid _attributes values\n found: string\n valid values: string\nfor file:\nstring: Cause: The _attributes property of the indicated file contained invalid and/or incorrect values.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07463: Global_Metadata_Directory structure has incorrect _accelerator_snap_map_fileid value\n found: string, but expected to find: string\nfor structure:\nstring: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer will resolve the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07464: file has invalid _attributes value\n found: string\nfor file:\nstring: Cause: The _attributes property of the indicated file contained invalid values. These values are not supported on Windows systems.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07465: file has _attributes set that are mutually exclusive\n found: string\nfor file:\nstring: Cause: The _attributes property of the indicated file describe more than one type of file. File types are mutually exclusive.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07466: file has no _attributes value\nfor file:\nstring: Cause: The _attributes property of the indicated file did not describe a file type. The _attributes property must describe a valid file type.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07467: metadata structure has a non-zero value for field: string\nfor structure:\nstring: Cause: The indicated ACFS metadata structure had a reserved or unused field that contained a non-zero value. The field was overwritten or was not initialized correctly.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07468: file has invalid _SynchFlags value\n found: string\n expected: string\nfor file:\nstring: Cause: The _SynchFlags property of the indicated file contained values that were not within the range of valid values.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07469: file cannot be modified; _SynchFlag value:\n found: string\nfor file:\nstring: Cause: The indicated file had an internal inconsistency that prevented it from being modified.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07470: file cannot be accessed; _SynchFlag value:\n found: string\nfor file:\nstring: Cause: The indicated file had an internal inconsistency that prevented it from being accessed.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07471: file incorrectly marked for deletion with _SynchFlag value:\n found: string\nfor file:\nstring: Cause: The _SynchFlag property of the indicated file incorrectly identified the file as marked for deletion while it was still part of a valid directory.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07474: invalid program name\n found: string, but expected to find: string or string: Cause: The ACFS Checker/Fixer or Debug utility has been renamed to a value that is not recognized.; Action: Rename the program to the corresponding value listed in the message and rerun the program.
ACFS-07475: attempting to continue with standard memory heap: Cause: The file system checker was unable to use the more efficient memory allocation facility, so the file system checker attempted to continue with the standard memory allocation facility.; Action: None
ACFS-07481: An I/O error occurred while reading ACFS metadata, some snapshot metadata checks will not be performed.: Cause: The I/O error prevented full snapshot checking because required ACFS metadata was not available. Refer to the accompanying message(s) for more information on the error.; Action: Correct the problem described in the accompanying messages if possible and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ACFS-07482: snapshot string with _snapid value: string has invalid parent snapshot with _snapid value: string: Cause: The indicated snapshot does not have a valid parent.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07483: snapshot with _snapid value: string has invalid ancestor snapshot: Cause: The indicated snapshot has an invalid ancestor snapshot.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07484: valid ACFS volume path name required: Cause: A valid volume path name was not entered.; Action: Rerun the ACFS Checker/Fixer or Debug utility with a valid ACFS volume path name as the final argument.
ACFS-07485: unable to determine temporary directory: Cause: An attempt to determine the system's temporary directory failed. For UNIX systems this directory is either "/usr/tmp" or "/tmp". For Windows systems this directory is the system's temporary folder. Refer to the accompanying message(s) for more information on the error.; Action: Correct the problem described in the accompanying messages if possible and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ACFS-07486: unable to determine current directory: Cause: An attempt to determine the current directory failed. Refer to the accompanying message(s) for more information on the error.; Action: Correct the problem described in the accompanying messages if possible and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ACFS-07487: unable to open volume: string: Cause: An attempt to open a volume failed. Refer to the accompanying message(s) for more information on the error.; Action: Correct the problem described in the accompanying messages if possible and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ACFS-07488: This volume is now in a mountable state. \nThe file system was not checked before changing the volume's state. \nUse of this file system may encounter serious errors since it has \nnot been checked.: Cause: The volume was forced into a mountable state without checking the integrity of the file system. The file system may contain incorrect or invalid data.; Action: Run the ACFS Checker/Fixer before attempting to mount the file system.
ACFS-07489: maximum number of passes: number exceeded, program terminating: Cause: There are two possible causes: 1. There is a problem with the file system that the ACFS Fixer cannot repair. 2. The ACFS Fixer has encountered an internal problem.; Action: Contact Oracle Support Services.
ACFS-07490: Metadata structure has non-zero values for various fields\nfor structure:\nstring: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer will resolve the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07498: extent[number] has invalid _Length value\n found: string, but expected to find multiple of: string\nfor file:\nstring: Cause: The _Length property of an extent structure of the indicated file was invalid. _Length values must be a multiple of the file system allocation unit size.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07499: extent[number] has invalid _Length value\n found: string, but expected to find multiple of: string\nfor structure:\nstring: Cause: The _Length property of an extent of the indicated extent structure was invalid. _Length values must be a multiple of the file system allocation unit size.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07500: extent[number] has invalid _FileOffset value\n found: string, but expected to find multiple of: string\nfor file:\nstring: Cause: The _FileOffset property of an extent structure of the indicated file was invalid. _FileOffset values must be a multiple of the file system allocation unit size.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07501: extent[number] has invalid _FileOffset value\n found: string, but expected to find multiple of: string\nfor structure:\nstring: Cause: The _FileOffset property of an extent of the indicated extent structure was invalid. _FileOffset values must be a multiple of the file system allocation unit size.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07502: extent[number] has invalid _PhysicalDiskOffset value\n found: string, but expected to find multiple of: string\nfor file:\nstring: Cause: The _PhysicalDiskOffset property of an extent structure of the indicated file was invalid. _PhysicalDiskOffset values must be a multiple of the file system allocation unit size.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07503: extent[number] has invalid _PhysicalDiskOffset value\n found: string, but expected to find multiple of: string\nfor structure:\nstring: Cause: The _PhysicalDiskOffset property of an extent of the indicated extent structure was invalid. _PhysicalDiskOffset values must be a multiple of the file system allocation unit size.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07504: snapshot with _snapid value: string has invalid ancestor snapshot (_cycle): Cause: The indicated snapshot has an invalid ancestor snapshot.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07505: metadata structure read failed at disk offset: string for structure: string: Cause: An attempt to read the indicated metadata structure at the described disk offset failed. Refer to the accompanying message(s) for more information on the problem.; Action: Correct the problem described in the accompanying messages if possible and rerun the program.
ACFS-07519: Snap_Map_Header structure has invalid _SnapConvertPending value\n found: number, but expected to find: less than number\nfor structure:\nstring: Cause: The _SnapConvertPending property of the indicated Snap_Map_Header metadata structure was incorrect. The _SnapConvertPending value must be zero or less than the value indicated in the message.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07520: Snap_Map_Info structure has invalid _SnapInfoFlags value\n found: string\nfor structure:\nstring: Cause: The _SnapInfoFlags property of the indicated Snap_Map_Info metadata structure was invalid.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07521: Snap_Map_Info structure has invalid _SnapAncestorIncarn value\n found: string\nfor structure:\nstring: Cause: The _SnapAncestorIncarn property of the indicated Snap_Map_Info metadata structure was invalid.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07522: snapshot: string (identifier: number) has invalid _SnapParentId: number, parent snapshot does not exist: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer will resolve the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07523: snapshot: string (identifier: number) has invalid _SnapParentId value\n found: number, but expected to find: 0\nfor structure:\nstring: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer will resolve the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07524: snapshot: string (identifier: number) has invalid _SnapAncestorIncarn value\n found: number, but expected to find: 0\nfor structure:\nstring: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer will resolve the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07525: snapshot: string (identifier: number) has invalid _SnapAncestorIncarn value\n found: number, must be less than _SnapIncarnationNumber: number\nfor structure:\nstring: Cause: The _SnapAncestorIncarn property of the indicated Snap_Map_Info metadata structure was invalid.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07526: Volume_Disk_Header has invalid _VolStateFlag values.\n found: string,\n but expected to find: string \nfor structure:\nstring: Cause: The _VolStateFlag property of the indicated Volume_Disk_Header contained one or more invalid values.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07527: Volume Disk Header has invalid VolFeatureFlag values \n found: string \nstring but expected to find: string \nstringfor structure:\nstring: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer will resolve the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07528: found partially created snapshot: string (identifier: number): Cause: Initialization of the indicated snapshot did not complete. There are two possible causes: 1. The volume went offline while the snapshot was being created. 2. The process creating the snapshot was unexpectedly terminated do to a shutdown of the system.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem. The ACFS Fixer will remove this snapshot.
ACFS-07529: found partially deleted snapshot: string (identifier: number): Cause: A snapshot was not completely deleted. There are several possible causes: 1. The volume was unmounted before the asynchronous phase of snapshot deletion had completed. 2. The volume went offline while the snapshot was being deleted. 3. The process deleting the snapshot was unexpectedly terminated do to a shutdown of the system.; Action: n/a
ACFS-07530: snapshot: string (identifier: number) has invalid file identifier\n found: string maximum: string\nfor structure:\nstring: Cause: The file identifier property of the indicated snapshot was invalid. Its value exceeded the maximum value for the file system.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07531: snapshot: (identifier: number) has invalid name: 'string'\nfor structure:\nstring: Cause: The name of indicated snapshot contained invalid characters.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07532: snapshot: string (identifier: number) has invalid _SnapVisibility value found: number, but expected to find: number, number or number\for structure:\nstring: Cause: The _SnapVisibility property of the indicated snapshot was invalid.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07533: duplicate _SnapIncarnationNumber: number found for the following snapshots:\n: Cause: The _SnapIncarnationNumber property of the indicated snapshots had the same value. _SnapIncarnationNumber values must be unique.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer will resolve the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07534: request for disk offset: string exceeds the size for this file system: string: Cause: A request was made for a disk offset that exceeded the size of the file system.; Action: Reenter the command with a disk offset that is within the limits of the file system.
ACFS-07536: snapshot: string (identifier: number) has invalid parent snapshot identifier: number, maximum: number\nstructure:\nstring: Cause: The indicated snapshot does not have a valid parent.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07537: snapshot: string (identifier: number) has invalid ancestor snapshot: string (identifier: number): Cause: The indicated snapshot has an invalid ancestor snapshot.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07538: snapshot: string (identifier: number) has invalid ancestor snapshot (_cycle): Cause: The indicated snapshot has an invalid ancestor snapshot.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07539: Snap_Map_Info structure has invalid _SnapAncestorIncarn value\n found: number\nfor structure:\nstring: Cause: The _SnapAncestorIncarn property of the indicated Snap_Map_Info metadata structure was invalid.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07540: deleting snapshot: string (identifier: number) to maintain file system integrity: Cause: The ACFS Fixer had to delete a snapshot to maintain the integrity of the file system. Refer to the corresponding message(s) for more information on the problem(s) associated with the snapshot.; Action: No further action is needed.
ACFS-07541: Snap_Map_header has invalid value for SnapMapFlags\n found: string\n string\n but expected to find: string\n string\nfor structure: string: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer will resolve the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07542: Snapshot string (identifier number) has invalid _SnapStorageCount value found: number, but expected to find: number, for structure: \nstring: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer has resolved the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07543: snapshot string (identifier number) has invalid _SnapStorageCount value found: number, but it should not be greater than the total amount of the storage all snapshots have number, for structure: \nstring: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer has resolved the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07544: Compressed file:\nstring\n has an incorrect value number\nfor the _compression_unit_size_index property of the _FileEntry\nand cannot be used.: Cause: The _FileEntry indicated that compression was enabled but the _compression_unit_size_index property was not set to a valid value.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will delete this file. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07545: Compressed file:\nstring\nhas an incorrect value number\nfor the compression algorithm and cannot be used.: Cause: The file entry indicated that compression was enabled but the compression algorithm was not set to a valid value.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will delete this file. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07546: extent[number] has invalid _FileOffset value\n found: string, but expected to find multiple of: string\nfor compressed file:\nstring: Cause: The _FileOffset property of an extent of the indicated extent structure was invalid. _FileOffset values must be a multiple of the file's compression unit size, for compressed files.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07547: Compressed file has extents that overlap.\n_FileOffset: string and\n_FileOffset: string\nfor file:\nstring: Cause: Two file extents with the _FileOffset values shown, were found to use the same disk storage incorrectly.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07548: Compressed file extent is in an inconsistent state.\n_FileOffset: string\nfor file:\nstring: Cause: A file extent with the _FileOffset value shown was found to be using disk storage incorrectly.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07549: File has _attributes value indicating compression but this is inconsistent with the volume header.\n found: string\nFile:\nstring\nshould not be compressed: Cause: The volume header indicated that compression was never enabled but a file entry indicating compression was found.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07550: default compression algorithm value is invalid\n found: string expected: string\nfor structure:\nstring: Cause: The volume header indicated that compression was enabled but the default compression algorithm was not set as expected.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07551: The Volume_Disk_Header indicates that this file system has an accelerator volume, but the Global_Metadata_Directory structure does not contain an accelerator volume name.: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the file system has an accelerator volume associated with it then this problem may not be recoverable. The file system will have to be restored from a backup copy if the the problem cannot be resolved.
ACFS-07552: Global_Metadata_Directory structure has no value for _accelerator_device, but contains a non-zero value for _accelerator_GBM_fileid or _accelerator_snap_map_fileid\n _accelerator_GBM_fileid: string\n _accelerator_snap_map_fileid: string\nfor structure:\nstring: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer will resolve the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07554: unable to close volume: string: Cause: An attempt to close a volume failed. Refer to the accompanying messages for more information on the error.; Action: Correct the problem described in the accompanying messages if possible and rerun the command.
ACFS-07555: unable to close file: string: Cause: An attempt to close a file failed. Refer to the accompanying messages for more information on the error.; Action: Correct the problem described in the accompanying messages if possible and rerun the command
ACFS-07556: I/O request for (disk offset + size): string exceeds accelerator volume size: string\nfor structure:\nstring: Cause: An I/O request was made for data that exceeded the size of the accelerator volume.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer will resolve the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07557: found accelerator volume: string associated with this file system,\nbut accelerator volumes are not supported on this operating system: string: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer will resolve the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07558: unable to process SnapMap metadata on the accelerator volume due to a problem with the primary volume's SnapMap metadata: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer will resolve the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07559: The _FileEntry metadata structure for the accelerator volume storage SnapMap is invalid.: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer will resolve the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07560: \nextent[number] is not in use but it contains non-zero values:\n _FileOffset: string\n _Length: string\n _PhysicalDiskOffset: string\n _SnapIncarnationNumber: number\n _VolId: string\n _ExtFlags: string: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer will resolve the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07563: volume: string had an unsupported logical sector size\n found: number, but only number or number are supported\n: Cause: File system check has identified the metadata inconsistency reported in the message.; Action: Copy the file system to a volume with a supported sector size of 512 or 4096 and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ACFS-07564: Snap_Clone_ID structure has an invalid Version value\n found: string\nfor structure:\nstring: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer has resolved the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07565: Snap_Clone_ID structure has an invalid Flags value\n found: string\nfor structure:\nstring: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer has resolved the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07566: extent[number] at _FileOffset value string has invalid _PhysicalDiskOffset value \n found: string, but expected to find multiple of: string\nfor structure:\nstring: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer has resolved the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07567: extent[number] at _FileOffset value string has invalid _PhysicalDiskOffset value \n found: string, but expected to find multiple of: string\nfor compressed file:\nstring: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer has resolved the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07568: Volume_Disk_Header has incorrect metadata size value\n found: string, but expected to find: string\nfor structure:\nstring: Cause: The MetadataSize property of the indicated Volume_Disk_Header did not match supported values.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer will resolve the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07570: snap_map_tuple for disk offset: string conflicts with primary file system\n found: ( string, string )\n expected: ( 0, 0 ): Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer will resolve the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07571: snap_map_tuple for disk offset: string not set in Global BitMap\n snap_map_tuple: ( string, string ): Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer will resolve the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07572: invalid snap_map_tuple found for for disk offset string,\nfirst value must be less than or equal to second value\n snap_map_tuple: ( string, string ): Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer will resolve the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07573: orphan snap_map_tuple found for for disk offset string\n snap_map_tuple: ( string, string ): Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer will resolve the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07574: snapshot marked for delete: string (identifier: number) was still present: Cause: File system checking has identified the metadata inconsistency reported in the message. A snapshot was marked for delete, but did not get deleted due to open files in the snapshot. There are two possible causes why the snapshot was not deleted. 1. The volume went offline while there were still open files in the snapshot. 2. The system was unexpectedly shutdown while there were still open files in the snapshot.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer has resolved the problem. If the message was generated by the ACFS Checker, then run the Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07575: command takes no arguments: Cause: The command entered does not take any arguments.; Action: Reenter the command with no arguments.
ACFS-07576: Compressed file:\nstring\nhas an incorrect value number\nfor the _range_size value and cannot be used.: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer has resolved the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07577: extent structure has incorrect _NextDataExtent value\n found: string, but expected to find: string\nfor structure:\nstring: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer has resolved the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07578: extent structure has incorrect _NextDataExtentVolId value\n found: string, but expected to find: string\nfor structure:\nstring: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer has resolved the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07579: HEADER extent structure found in _NextDataExtent list for file that does not support range locking\nfor file:\nstring: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer has resolved the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07580: Remap_Bitmap has an invalid volume offset beyond the current volume size (EAOffset)\n found: string, but expected: string\nfor structure: \n string: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer has resolved the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07581: disk storage used string greater than sum of extents allocation size string\nfor file:\nstring: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer has resolved the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07582: file _DiskUsage value not equal to disk storage used by DATA extents\n found: string, but expected to find: string\nfor file:\nstring: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer has resolved the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07583: invalid file entry number found in deferred release file at offset: string: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer has resolved the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07584: found a number in the Remap_Bitmap for offset string where a number was expected: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer has resolved the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07585: unable to set File_Entry_Table context: Cause: The ACFS Debug utility was not able to set the File_Entry_Table context. Lookups by file identifier were disabled. Refer to the accompanying message(s) for more information on the problem.; Action: Correct the problem described in the accompanying messages if possible by rerunning the ACFS Fixer.
ACFS-07586: Do you want to continue [y|n] ?: Cause: The ACFS Checker/Fixer or Debug utility detected a situation that could leave the file system in an inconsistent or unusable state. Refer to the corresponding error message for more information.; Action: Respond Y(yes) to proceed or N(no) to cancel.
ACFS-07588: Metadata read of size string bytes failed at disk offset: string.\n Can not read beyond end of primary volume, size: string.: Cause: An attempt to read metadata failed because the data requested was beyond the size of the primary volume for this file system.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer will resolve the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07590: Metadata write of size string bytes failed at disk offset: string.\n Can not write beyond end of primary volume, size: string.: Cause: An attempt to write metadata failed because the write location was beyond the size of size of the primary volume for this file system.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer will resolve the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07592: metadata structure has incorrect header for:\nstring: Cause: One or more properties of the header of the indicated metadata structure contained invalid or incorrect values. Refer to accompanying messages for more information on the error.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07598: Metadata read of size string bytes failed at disk offset: string.\n Can not read beyond end of accelerator volume, size: string.: Cause: An attempt to read metadata failed because the data requested was beyond the size of the accelerator volume for this file system.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer will resolve the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07600: Metadata write of size string bytes failed at disk offset: string.\n Can not write beyond end of accelerator volume, size: string.: Cause: An attempt to write metadata failed because the write location was beyond the size of size of the accelerator volume for this file system.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer will resolve the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07601: unable to determine size of file: string: Cause: An attempt to determine the size of the indicated file failed. Refer to the accompanying message(s) for more information on the problem.; Action: Correct the problem described in the accompanying messages if possible and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ACFS-07602: failed to create temporary paging file 'string': Cause: An attempt to create the indicated temporary paging file failed. Refer to the accompanying message(s) for more information on the problem.; Action: Correct the problem described in the accompanying messages if possible and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ACFS-07603: write failed at position: string for temporary paging file 'string': Cause: An attempt to write to the indicated temporary paging file failed. Refer to the accompanying message(s) for more information on the problem.; Action: Correct the problem described in the accompanying messages if possible and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ACFS-07604: seek failed at position: string for temporary paging file 'string': Cause: An attempt to seek within the indicated temporary paging file failed. Refer to the accompanying message(s) for more information on the problem.; Action: Correct the problem described in the accompanying messages if possible and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ACFS-07606: read failed at position: string for temporary paging file 'string': Cause: An attempt to read the indicated temporary paging file failed. Refer to the accompanying message(s) for more information on the problem.; Action: Correct the problem described in the accompanying messages if possible and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ACFS-07607: metadata read failed at disk offset: string\n bytes requested: number bytes returned: number: Cause: An attempt to read metadata at the indicated offset was incomplete. The amount of data read did not match the amount requested. Refer to the accompanying message(s) for more information on the problem.; Action: Correct the problem described in the accompanying messages if possible and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ACFS-07608: found number incorrectly set bits in the Remap_Bitmap: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer has resolved the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07609: found number incorrectly unset bits in the Remap_Bitmap: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer has resolved the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07610: Volume_Disk_Header has incorrect _VolVolumeSize value\n found: string, but expected to find: string\nfor structure:\nstring: Cause: The _VolVolumeSize property of the indicated Volume_Disk_Header metadata structure was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07611: Global_BitMap has bits incorrectly set for storage beyond the file system size\nfor file:\nstring: Cause: The Global_BitMap had bits set in an area reserved for future expansion. All of these storage bits must be zero. There is no valid storage associated with these bits.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07612: file has invalid _NextFreeExtent value:\n found: number minimum: number\nfor file:\nstring: Cause: The _NextFreeExtent property of the indicated file was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07613: file has invalid _NextFreeExtent value:\n found: number maximum: number\nfor file:\nstring: Cause: The _NextFreeExtent property of the indicated file was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07614: Global_BitMap's first extent is not located at the expected disk offset\n found: string, but expected to find: string\nfor file:\nstring: Cause: The first extent of the indicated Global_BitMap was not located at the correct disk offset. The Global_BitMap's first extent must be located at the disk offset described in the message.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07615: Global_BitMap file has extents that overlap\n Extent[number] _Length: string _PhysicalDiskOffset: string\n Extent[number] _Length: string _PhysicalDiskOffset: string\nfor file:\nstring: Cause: The extents of the indicated Global_BitMap mapped some or all of the same storage. All extents within a file must map storage that is mutually exclusive.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07616: string has encountered an internal error: could not post error to ACFS Fixer: Cause: The ACFS Checker/Fixer or ACFS Debug utility has encountered an unexpected, internal error. Refer to the accompanying message(s) for more information on the problem.; Action: Contact Oracle Support Services.
ACFS-07619: truncating file from number bytes to number bytes to ensure metadata consistency; file content following file offset: number has been lost\nfor file:\nstring: Cause: The ACFS Fixer was not able to fully repair the indicated file due to an inconsistency within its metadata. The file had to be truncated to maintain the integrity of the file system.; Action: Restore the file from a backup copy.
ACFS-07622: resetting _security_descriptor to administrator default value for:\nfor file:\nstring: Cause: The _security_descriptor the indicated file was invalid or incorrect. It was reset to the default administrator value.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will reset the _security_descriptor to the administrator default value for the file.
ACFS-07623: unable to repair problem with file _attributes; deleting file to maintain file system integrity\nfor file:\nstring: Cause: The ACFS Fixer was not able to resolve a problem with the _attributes property of the indicated file. The file had to be deleted to maintain the integrity of the file system.; Action: Restore the file from a backup copy.
ACFS-07624: file cannot be repaired; deleting file to maintain file system integrity\nfor file:\nstring: Cause: The ACFS Fixer was not able to repair a problem with the indicated file. The file had to be deleted to maintain file system integrity.; Action: Restore the file from a backup copy.
ACFS-07625: failed to create system directory\nfor file:\nstring: Cause: The ACFS Fixer was not able to create a directory for the indicated internal system file. Refer to the accompanying message(s) for more information on the problem.; Action: Correct the problem described in the accompanying messages if possible and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ACFS-07628: invalid snapshot name 'string' entered: Cause: The snapshot entered did not exist.; Action: Enter the name of a valid snapshot to continue.
ACFS-07629: numeric argument too large: number: Cause: The numeric value entered as an argument exceeded the largest possible value for this type of argument.; Action: Enter a value that is within the valid range of values for the type of argument.
ACFS-07630: file has invalid _oracle_file_type value\n found: number\nfor file:\nstring: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer has resolved the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07631: extent[number] has invalid _Length value\n found: string, but expected to find multiple of: string\nfor structure:\nstring: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer has resolved the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07632: extent[number] has invalid _PhysicalDiskOffset value\n found: string, but expected to find multiple of: string\nfor structure:\nstring: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer has resolved the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07633: extent[number] has invalid _Length value\n found: string, but expected to find multiple of: string\nfor file:\nstring: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer has resolved the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07634: extent[number] has invalid _PhysicalDiskOffset value\n found: string, but expected to find multiple of: string\nfor file:\nstring: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer has resolved the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07635: extent[number] has invalid _Length value\n found: string, but expected to find: string\nfor structure:\nstring: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer has resolved the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07636: extent[number] has invalid _Length value\n found: string, but expected to find: string\nfor file:\nstring: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer has resolved the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07637: extent[number] has invalid _Length value\n found: string, but expected to find less than: string\nfor structure:\nstring: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer has resolved the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07638: extent[number] has invalid _Length value\n found: string, but expected to find less than: string\nfor file:\nstring: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer has resolved the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07641: Remap_Bitmap has number bits set without corresponding offsets: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer has resolved the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07642: Storage referenced directly at disk offset: string is also referenced via remapping from disk offset: string: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer has resolved the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07643: primary and duplicate Volume_Disk_Header structures do not match for string: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer has resolved the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07644: _VolStateFlag property of a Volume_Disk_Header structure for device 'string' indicates that this is an accelerator volume\n _VolStateFlag: string\nfor structure:\nstring: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer has resolved the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07645: extent[number] is a sparse extent which is not supported for this type of file\nfor file: \nstring: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer has resolved the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07646: Volume_Disk_Header has incorrect _VolVolumeSize value\n found: string expected: string\nfor structure:\nstring: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer has resolved the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07647: local extent limit reached for extending files; indirect extents not supported for extending files\nfor file:\nstring: Cause: The ACFS Fixer was not able to create an indirect extent to extend the indicated file.; Action: Restore the file from a backup copy.
ACFS-07648: cannot set Global_BitMap bits for offset: string for number bytes\nfor file:\nstring: Cause: The ACFS Fixer was unable to set the range of bits described in the message. Refer to the accompanying message(s) for more information on the problem.; Action: Correct the problem described in the accompanying messages if possible and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ACFS-07649: deleting snapshot to maintain file system integrity: Cause: The ACFS Fixer had to delete a snapshot to maintain the integrity of the file system. Refer to the corresponding message(s) for more information on the problem(s) associated with the snapshot.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07650: unable to repair _VolStateFlag value in Volume_Disk_Header: Cause: The ACFS Fixer was unable to update the _VolStateFlag in the Volume_Disk_Header. Refer to the accompanying message(s) for more information on the problem.; Action: Correct the problem described in the accompanying messages if possible and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ACFS-07651: Remap_Storage_Table is corrupt and may result in files being truncated\nRemap_Storage_Table:\nstring: Cause: The ACFS Checker/Fixer found an inconsistency with the Remap_Storage_Table metadata. The Remap_Storage_Table is a critical system structure that is necessary for a functioning file system.; Action: If the Fixer reports that files have been truncated, restore them from a backup copy.
ACFS-07652: Volume_Disk_Header has invalid _VolOSCreatedOn value\n found: number string, but expected to find: number string\nfor structure:\nstring: Cause: The _VolOSCreatedOn property of the indicated Volume_Disk_Header was incorrect. Its value must be one of the values listed in the message.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07653: Security_Metadata file _Private structure has invalid _freeDataListTail value\n found: 0, but expected to find: > 0\nfor structure:\nstring: Cause: The _freeDataListTail property of the indicated Security_Metadata _Private metadata structure was invalid. The value must be greater than zero.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07655: This file system had been removed. It has now been restored.: Cause: This file system was removed via the acfsutil rmfs utility. It has now been restored by the ACFS Fixer.; Action: The ACFS Fixer has restored the file system. No further action is required.
ACFS-07656: unable to continue: Cause: The ACFS Checker/Fixer or Debug utility has encountered a fatal error and cannot continue. Refer to the accompanying message(s) for more information on the error.; Action: Correct the problem described in the accompanying messages if possible and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ACFS-07658: Ensure that volume string is not mounted on this node. \nNote that data displayed may not be current if volume string is mounted on any other node due to file system caching: Cause: The volume cannot be mounted on this node while running the acfsdbg utility in read-only mode. This restriction is limited to Windows systems. The acfsdbg utility reads metadata directly from disk and data may not be current if the file system is mount on any other nodes due file system caching.; Action: Check to determine if the volume is mounted on any node. The volume must be unmounted on this node before continuing. The volume should also be unmounted on all others node if possible. If the volume cannot be unmounted on other nodes, then reenter any request if the metadata values displayed appear to be stale. Note: You may have to reenter the request several times to retrieve the latest metadata.
ACFS-07659: command is disabled in read-only mode: Cause: The command entered attempted to modify file system metadata while running in read-only mode. Modifications to file system metadata are not allowed when running the ACFS Debug utility in read-only mode.; Action: Rerun the acfsdbg utility in write mode to modify metadata.
ACFS-07660: unable to modify metadata for volume string; volume is not open: Cause: An attempt to modify metadata failed because the volume was not open. Refer to the accompanying message(s) for more information on the problem.; Action: Correct the problem described in the accompanying messages if possible and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ACFS-07661: metadata lookup by file identifier is disabled due to lack of File_Entry_Table context; enter 'primary' or 'snap snapshot name' to set the context: Cause: The acfsdbg utility could not process the request because there was no File_Entry_Table context. The acfsdbg utility requires a valid File_Entry_Table context for lookups by file identifier since the same file identifier may appear in multiple snapshots.; Action: Enter the 'primary' or 'snap snapshot name' command to set context.
ACFS-07662: unable to set snapshot context due to Snap_Map file metadata inconsistency: Cause: An attempt to set the metadata lookup context to a snapshot failed because there was a problem accessing the SnapMap metadata. Refer to the accompanying message(s) for more information on the problem.; Action: Correct the problem described in the accompanying messages if possible and rerun the ACFS debug utility.
ACFS-07663: disk offset request: string is not aligned on a sector: number bytes; results may be inconsistent: Cause: The disk offset entered was not sector aligned. All ACFS metadata structures are sector aligned.; Action: Reenter the offset so that is properly aligned as described in the corresponding message.
ACFS-07664: read failed for metadata structure at disk offset: string for number bytes: Cause: An attempt to read a metadata structure at the indicted disk offset failed. Refer to accompanying message(s) for more information on the problem.; Action: Correct the problem described in the accompanying messages if possible and rerun the ACFS debug utility.
ACFS-07665: Remap_Storage_Table has invalid RTFE_VolVolumeSize which exceeds the physical volume size\n found: string maximum: string\nfor file:\n string: Cause: The ACFS Checker/Fixer found an inconsistency with the Remap_Storage_Table metadata. The Remap_Storage_Table is a critical system structure that is necessary for a functioning file system.; Action: Restore the file system from a backup copy.
ACFS-07666: unrecognized metadata found at disk offset: string: Cause: The data found at the indicated disk offset did not contain a valid ACFS metadata structure type. There are two possible causes: 1. The data at the disk offset was not an ACFS metadata structure. 2. The metadata structure at the disk offset was in an inconsistent state.; Action: If the data at the disk offset should be an ACFS metadata structure, then run the ACFS Fixer to resolve the problem.
ACFS-07667: request for file identifier: string exceeds the maximum value for this file system: string: Cause: A request was made for a file identifier that exceeded the maximum for the file system.; Action: Reenter the command with a file identifier that is within the limits of the file system.
ACFS-07669: metadata lookup by file identifier is disabled due to File_Entry_Table metadata inconsistency: Cause: The acfsdbg utility has identified the metadata inconsistency reported in the accompanying message.; Action: Run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07670: extent[number] references an accelerator volume but there is no accelerator volume available for this file system\nfor structure:\nstring: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer has resolved the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07671: extent[number] references an accelerator volume that does not support this type of file\n file type: string\nfor file:\nstring: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer has resolved the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07672: extent[number] has invalid volume identified\n found: string but expected string or string\nfor structure:\nstring: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer has resolved the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07673: ACFS system file must have at least one valid extent\nfor file:\n%(1): Cause: The ACFS Checker/Fixer found an inconsistency with the Remap_Storage_Table metadata. The Remap_Storage_Table is a critical system structure that is necessary for a functioning file system.; Action: Restore the file system from a backup copy.
ACFS-07674: Global_BitMap has incorrect value for bitmap size\n found: string maximum: string\nfor file:\nstring: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer has resolved the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07675: Remap_Storage_Table has invalid RTFE_VolVolumeSize value\n found: string maximum: string\nfor file:\n string: Cause: The ACFS Checker/Fixer found an inconsistency with the Remap_Storage_Table metadata. The Remap_Storage_Table is a critical system structure that is necessary for a functioning file system.; Action: Restore the file system from a backup copy.
ACFS-07676: Remap_Storage_Table has invalid RTFE_VolVolumeSize value\n found: string must be aligned on a number byte boundary\nfor file:\n string: Cause: The ACFS Checker/Fixer found an inconsistency with the Remap_Storage_Table metadata. The Remap_Storage_Table is a critical system structure that is necessary for a functioning file system.; Action: Restore the file system from a backup copy.
ACFS-07677: Local_BitMap has invalid value for Global_disk_offset\n found: string maximum: string\nfor file:\nstring: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer has resolved the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07678: Snap Map Info structure has invalid SnapGenumBase value\n found: number, but expected to find: number\nfor structure:\nstring: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer will resolve the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07679: Estimated progress for current pass: number%% (string remaining): Cause: Informational.; Action: None
ACFS-07680: Storage interest tracking map has incorrect size.\nfound: string but expected to find: string\nfor structure:\nstring: Cause: The _AllocationSize property of the indicated file was incorrect.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer will resolve the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07681: Storage interest tracking map has incorrect row size.\nfound: string but expected to find: string\nfor structure:\nstring: Cause: The _row_size property of the indicated file was incorrect.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer will resolve the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07682: file system check has been cancelled: Cause: File system checking was terminated because a signal was received, such as Control-C.; Action: None
ACFS-07683: found incorrect size string for the Remap_Bitmap: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer has resolved the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07684: The Accelerator Volume string is corrupt and cannot be be repaired.\nRestore the file system from a backup copy.: Cause: The ACFS Checker/Fixer found an inconsistency with the Accelerator Volume metadata that cannot be repaired.; Action: Restore the file system from a backup copy.
ACFS-07685: string is unable to detect the ACFS driver on this system. \nProceeding could leave the file system in an inconsistent and possibly \nunusable state if the file system is mounted or being fixed on another system.: Cause: The ACFS Checker/Fixer or Debug utility issued a system call to the ACFS driver that failed. It appeared that the ACFS driver was not loaded on this system.; Action: The ACFS driver should be loaded on all nodes if possible. Verify that the file system is not mounted or being fixed on any node. Rerun the ACFS Checker/Fixer or Debug utility once these steps are complete.
ACFS-07686: found bit set for non-existent or read-only optimized snapshot string\nat disk offset string\nin string: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer has resolved the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07687: found string bits set for in-use storage\nfor snapshot string at disk offset string\nin string: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer has resolved the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07688: found string rows with bits set for free storage\nat disk offset string\nin string: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer has resolved the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07689: Shrink of string failed due to unmovable metadata\nfor node string.: Cause: ACFS metadata files prevented the shrink from succeeding.; Action: Execute the following commands on the specified node to cause its metadata to be recreated at a lower disk offset for the specified mountpoint: 1. acfsutil size -r mountpoint 2. Unmount the file system from mountpoint 3. Mount the file system again on mountpoint Then try the shrink operation again.
ACFS-07690: data displayed may not be current if volume string is mounted on any node due to file system caching: Cause: The acfsdbg utility reads metadata directly from disk. Metadata updates to disk may be delayed due standard file system caching.; Action: Check to determine if the volume is mounted on any node. Unmount the volume on all nodes if possible. If the volume cannot be unmounted from all nodes, then reenter any request if the metadata values displayed appear to be stale. Note: You may have to reenter a request several times to retrieve the latest metadata.
ACFS-07691: command entered: 'string' is invalid or not unique: Cause: There are two possible causes: 1. The command entered was not recognized by the acfsdbg utility. 2. A partial command name was entered and there was more than one command that matched the characters entered.; Action: Use the acfsdbg utility help (-h) option for a list of valid commands. Renter the command, ensuring that enough of the command name is entered to make it unique.
ACFS-07692: cannot convert disk offset as specified: string: Cause: The format entered for the disk offset was invalid.; Action: Use the acfsdbg utility help (-h) option for a list of commands and format options for entering data.
ACFS-07693: Volume_Disk_Header has invalid _VolVolumeSize value\n found: string must be aligned on a number byte boundary\nfor structure:\nstring: Cause: The _VolVolumeSize property of the Volume_Disk_Header was invalid. Its value must be aligned on the byte boundary described in the message.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07694: too many arguments for string: Cause: Too many arguments were supplied for the string option. The string option takes one argument.; Action: Reenter the command with only one argument for the string option.
ACFS-07695: The ACFS driver should be loaded on all nodes for a safe check of this file system.: Cause: The ACFS Checker/Fixer or Debug utility issued a system call to the ACFS driver that failed. It appeared that the ACFS driver was not loaded on this system.; Action: The ACFS driver should be loaded on all nodes if possible. Verify that the file system is not mounted or being checked on any node. Rerun the ACFS Checker/Fixer or Debug utility once these steps are complete.
ACFS-07696: The file system on volume string is currently in the string state. This state indicates that a file system check is currently in progress.: Cause: There are two possible causes: 1. The file system on this volume was being checked on this system or another system in the cluster. 2. The ACFS Checker/Fixer was unexpectedly terminated leaving the file system state incorrectly set.; Action: Verify that the file system is not being checked on any node. There are a two possible options if the file system is not being checked on any node: 1. Respond Y(yes) when prompted to run the ACFS Checker/Fixer. 2. Run the ACFS Fixer with the [f] option to reset the file system state to allow the file system to be mounted. NOTE: Use caution with this option as file system repairs from a previous run of the ACFS Checker/Fixer may be incomplete.
ACFS-07697: unable to determine program name: Cause: The ACFS Checker/Fixer or Debug utility was invoked in a non-standard way such that the program name could not be determined.; Action: Run the ACFS Checker/Fixer or Debug utility using a standard method.
ACFS-07698: orphan directory found for file identifier: string at disk offset: string: Cause: No parent directory entry was found for the indicated directory file. 1. The directory file had no corresponding parent directory entry. 2. The directory file had a parent directory entry, but there was a problem with corresponding parent directory file.; Action: If the ACFS Fixer is currently running, then no further action is needed. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem. The ACFS Fixer will attempt to repair any directories that are in an inconsistent state first. Any directory file that does not have a valid parent directory entry following directory repairs will be moved to the 'lost+found' directory with all of its files.
ACFS-07699: string unused bytes in the\nFile Entry Table may be reclaimed by running the Fixer.: Cause: File system checking has identified unused storage in the File Entry Table which may be reclaimed by running the ACFS Fixer.; Action: No action is needed. If desired, the ACFS Fixer can be run to reclaim the unused storage.
ACFS-07700: string unused bytes in the\nFile Entry Table were reclaimed.: Cause: Unused storage in the File Entry Table was reclaimed by the ACFS Fixer.; Action: No action is needed. The message is informational only.
ACFS-07701: There are metadata transaction log file(s) that have not been processed. Failure \nto process these transaction logs may result in metadata inconsistencies. \nDo you want to process the transaction log(s)? [y|n]: Cause: Transaction Log files contain updates to the file system's metadata. The ACFS Checker found at least one transaction log that was not completely processed. This indicates that metadata updates were not completed which could leave the file system in an inconsistent state.; Action: Respond yes to process metadata transaction log(s).
ACFS-07702: Attention: As a side effect of the reclaiming of unused bytes\nin the File Entry Table, the summary below reports File System Errors,\nall of which are Fixed. The file system metadata is consistent\nand the file system may safely be mounted.\n: Cause: Reclaiming of unused storage in the File Entry Table can cause metadata inconsistencies which the ACFS Fixer will fix.; Action: No action is needed. The ACFS Fixer has reclaimed the unused storage and has fixed the resulting inconsistencies.
ACFS-07708: unable to read File_Entry_Table entry: string at disk offset: string: Cause: An attempt to read the File_Entry_Table for the indicated entry failed. Refer to the accompanying message(s) for more information on the problem.; Action: Correct the problem described in the accompanying messages if possible and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ACFS-07709: orphan file (file identifier: string, disk offset: string) marked for deletion not on delete list: Cause: The indicated file was marked for deletion but it was not found on any of the delete file lists.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07710: orphan file found for file identifier: string at disk offset: string: Cause: No directory entry was found for the indicated file. There are two possible causes: 1. The file had no corresponding directory entry. 2. The file had a directory entry, but there was a problem with corresponding directory file.; Action: If the ACFS Fixer is currently running, then no further action is needed. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem. The ACFS Fixer will attempt to repair any directories that are in an inconsistent state first. Any file that does not have a valid directory entry following directory repairs will be moved to the 'lost+found' directory.
ACFS-07711: orphan metadata structure (type: string) found for file identifier: string at disk offset: string: Cause: The indicated metadata structure was found but had no corresponding parent metadata structure.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will move the structure to the free list. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07712: Device 'string' is a read only file system and cannot be modified by fsck. Any file system metadata inconsistencies discovered by fsck will not be resolved.: Cause: The device name specified is a Read-Only file system which prevents fsck from changing any data.; Action: Allow fsck to continue as it will report any metadata inconsistencies if found.
ACFS-07713: One or more log files cannot be processed because this is a read only file system. Any metadata inconsistencies found will not be resolved.: Cause: Log files cannot be process because updates are not allowed on a read only file system; Action: Allow the process to continue and make note of any metadata inconsistencies reported.
ACFS-07714: The '-f' option is not supported on a read only file system.: Cause: The '-f' option forces a file system into a mountable state which is not allowed on a read only file system.; Action: Refrain from using the '-f' option on a read only file system.
ACFS-07715: extent[number] has invalid _PhysicalDiskOffset value\n found: string, but expected to find:\n greater than or equal to string for file:\n string: Cause: The _PhysicalDiskOffset property of an extent structure of the indicated file had a value less than the offset of the Super Block. _PhysicalDiskOffset values must be greater or equal to the offset of the Super Block.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07716: extent[number] has invalid _PhysicalDiskOffset value\n found: string, but expected to find:\n greater than or equal to string for structure:\n string: Cause: The _PhysicalDiskOffset property of an extent of the indicated extent structure had a value less than the offset of the Super Block. _PhysicalDiskOffset values must be greater or equal to the offset of the Super Block.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07718: Adding number bytes of zero-filled storage to NI Map:\nstring: Cause: The NI Map metadata file was identified as truncated. The ACFS Fixer will rebuild the extents of the truncated file.; Action: No action is needed. The message is informational only.
ACFS-07719: Success: Unmount string to cause new metadata creation at next mount.: Cause: The command succeeded.; Action: Unmount the specified file system to cause new metadata creation at the next mount.
ACFS-07720: new allocation size is invalid\n found: number, but expected to find multiple of: number\nfor file:\nstring: Cause: The new allocation size property of the indicated file was incorrect. Its value must be a multiple of the file system allocation unit size.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07721: file has invalid _NextFreeExtent value\n found: number maximum: number\nfor file:\nstring: Cause: The _NextFreeExtent property of the indicated file was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07722: file has invalid _NextFreeExtent value:\n found: number minimum: 1\nfor file:\nstring: Cause: The ACFS Checker/Fixer found an inconsistency within the file system.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07723: could not clear temporary Global_BitMap bits at offset: string for number bits: Cause: The ACFS Fixer was unable to free the indicated storage on the temporary Global_BitMap.; Action: See the preceding error message, and take corrective action.
ACFS-07724: unable to set temporary Global_BitMap bits at offset: string for number bits: Cause: The ACFS Fixer was unable to reserve the indicated storage on the temporary Global_BitMap.; Action: See the preceding error message, and take corrective action.
ACFS-07725: unable to allocate storage; file system has no free space: Cause: The ACFS Fixer was unable to allocate storage because there was no free storage available.; Action: There are two options: 1. Free up some storage by deleting some files. 2. Add available storage by increasing the size of the file system via the 'acfsutil size' command.
ACFS-07726: could not find sufficient free storage to rebuild Global_BitMap extent\n found: string requested: string\nfor file:\nstring: Cause: The ACFS Fixer could not find enough contiguous storage to rebuild the Global_BitMap file's extent map.; Action: There are two options: 1. Free up some storage by deleting some files. 2. Add available storage by increasing the size of the file system via the 'acfsutil size' command.
ACFS-07727: could not rewrite Global_Bitmap data for file:\nstring: Cause: The ACFS Fixer could not update the file system's storage bitmap. Refer to the accompanying message(s) for more information on the problem.; Action: Correct the problem described in the accompanying messages if possible and rerun the ACFS Fixer.
ACFS-07728: The Global_BitMap file has reached the maximum number of extents (number). The file system can no longer be expanded. Running string in fixer mode will attempt to consolidate the storage bitmap into fewer extents which would allow for file system expansion via the 'acfsutil size' command.: Cause: The ACFS Checker found the file system's storage bitmap was using its maximum number of extents.; Action: Running the ACFS Checker/Fixer in Fixer mode will attempt to consolidate the file system's storage bitmap into two extents allowing future file system expansion using 'acfsutil size', assuming additional storage is available.
ACFS-07729: The Global_Bitmap file has been\n consolidated into number extents.\nThis may allow for file system expansion via the 'acfsutil size' command.: Cause: The Global_Bitmap file was using the maximum number of extents supported. The ACFS Fixer has consolidated the Global_Bitmap file into fewer extents thus allowing future file system growth using the 'acfsutil size' command if unused storage is available.; Action: No Action Needed.
ACFS-07733: directory _Private structure has invalid _first_dirnode value\n found: number maximum: number\nfor structure:\nstring: Cause: The _first_dirnode property of the indicated _Private directory structure was invalid. Its value exceeded the maximum value for the directory.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07734: directory _Private structure has invalid _last_dirnode value\n found: number maximum: number\nfor structure:\nstring: Cause: The _last_dirnode property of the indicated _Private directory structure was invalid. Its value exceeded the maximum value for the directory.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07735: directory _Private structure has invalid _hash_blk_free_list value\n found: number maximum: number\nfor structure:\nstring: Cause: The _hash_blk_free_list property of the indicated _Private directory structure was invalid. Its value exceeded the maximum value for the directory.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07736: directory _Private structure has invalid _dir_entry_free_list_head value\n found: string maximum: string\nfor structure:\nstring: Cause: The _dir_entry_free_list_head property of the indicated _Private directory structure was invalid. Its value exceeded the maximum value for the directory.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07737: directory _Private structure has invalid _dir_entry_free_list_tail value\n found: string maximum: string\nfor structure:\nstring: Cause: The _dir_entry_free_list_tail property of the indicated _Private directory structure was invalid. Its value exceeded the maximum value for the directory.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07740: Could not consolidate the file system's temporary\n storage bitmap to less than number extents. Need\n at least number bytes free contiguous storage.: Cause: The file system's internal storage bitmap could not be consolidated to less than five extents because there was insufficient free contiguous storage.; Action: Deleting some files larger than the amount of contiguous storage needed may free up sufficient contiguous storage so consolidation of the file system's internal storage bitmap may occur. The 'acfsutil info file filename' command may be used to examine a candidate file's contiguous extents.
ACFS-07741: could not rebuild file system storage bitmap\n free contiguous bytes found: number\n contiguous bytes requested: number\nfor file: string: Cause: The ACFS Fixer could not find enough contiguous free storage to rebuild the file system's storage bitmap.; Action: Deleting some files larger than the amount of contiguous storage needed may free up sufficient contiguous storage so consolidation of the file system's internal storage bitmap may occur. The 'acfsutil info file filename' command may be used to examine a candidate file's contiguous extents.
ACFS-07742: _ustEAContainerEntry property has an invalid value\n found: number for structure:\nstring: Cause: The _ustEAContainerEntry property of the indicated _ustEAContainer structure was not within the range of valid offset values.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem. The ACFS Fixer reconstructs the structure to retain as much valid information as possible and may eliminate inaccessible information.
ACFS-07743: _ustEAEntryHdrFlags property has an invalid value\n found: string for _ustEAContainerEntry at offset: number for structure:\nstring: Cause: The _ustEAEntryHdrFlags property of the indicated _ustEAContainer structure contained one or more invalid values.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07744: _ustEAEntryHdrNextFreeOffset property has an invalid value\n found: number, but expected to find: number for _ustEAContainerEntry at offset: number for structure:\nstring: Cause: The _ustEAEntryHdrNextFreeOffset property of the indicated _ustEAContainer structure was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07745: _ustEAEntryHdrNameLen property has an invalid value\n found: number, but expected to find no greater than: number\n for _ustEAContainerEntry at offset: number for structure:\nstring: Cause: The _ustEAEntryHdrNameLen property of the indicated _ustEAEntryHdr property at the _ustEAContainerEntry offset for the indicated _ustEAContainer structure was invalid. Its value exceeded the maximum length for an extended attribute name or ACFS tag name.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem. The ACFS Fixer reconstructs the structure to retain as much valid information as possible and may eliminate inaccessible or invalid information.
ACFS-07746: ACFS tag name contains invalid syntax\n found: string for _ustEAContainerEntry at offset: number for structure:\nstring: Cause: The _ustEAEntryName property of the indicated _ustEAContainerEntry property in the _ustEAContainer structure contained invalid syntax for an ACFS tag name.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem. The ACFS Fixer reconstructs the structure to retain as much valid information as possible and may eliminate inaccessible or invalid information.
ACFS-07747: _ustEAEntryValueLen property has an invalid value\n found: number, but expected to find: number\n for _ustEAEntry offset: number for structure:\nstring: Cause: The _ustEAEntryValueLen property of the indicated _ustEAEntry property in the _ustEAEntryContainer structure contained an invalid value length.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem. The ACFS Fixer reconstructs the structure to retain as much valid information as possible and may eliminate inaccessible or invalid information.
ACFS-07748: _ustEAEntryValue property has an invalid value\n found: string, but expected to find: string\n for _ustEAEntry offset: number for structure:\nstring: Cause: The _ustEAEntryValue property of the indicated _ustEAEntry property in the _ustEAEntryContainer structure contained an invalid value string for an ACFS tag name.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07749: _ustEAContainerHdrNextContainer property has an invalid value\n found: string for structure:\nstring: Cause: The _ustEAContainerHdrNextContainer property of the indicated _ustEAContainer structure contained an invalid offset value.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem. The ACFS Fixer reconstructs the structure to retain as much valid information as possible and may eliminate inaccessible or invalid information.
ACFS-07750: _ustEAContainerHdrNumEAEntries property has an invalid value\n found: number, but expected to find: number for structure:\nstring: Cause: The _ustEAContainerHdrNumEAEntries property of the indicated _ustEAContainer structure contained an incorrect count of valid entries.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07751: Inconsistent amount of available space\n found: number, but expected to find: number\n for structure:\nstring: Cause: The _ustEAContainer structure had an incorrect amount of free space.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem. The ACFS Fixer reconstructs the structure to retain as much valid information as possible and may eliminate inaccessible or invalid information.
ACFS-07752: _LocalTags property has invalid characters for _FileEntry:\nstring: Cause: The _LocalTags property of the indicted _FileEntry structure contained invalid characters for ACFS tag names.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem. The ACFS Fixer reconstructs the structure to retain as much valid information as possible and may eliminate inaccessible or invalid information.
ACFS-07753: _ustEAEntry property offset: number is marked free\n but is missing from the free list for structure:\nstring: Cause: The _ustEAContainer structure had an incorrect amount of free space.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem. The ACFS Fixer reconstructs the structure to retain as much valid information as possible and may eliminate inaccessible or invalid information.
ACFS-07754: _ustEAContainer property has inconsistent\n total free and assigned _ustEAContainerEntry property space\n found: number, but expected to find: number for structure:\nstring: Cause: The _ustEAContainer structure contained free and active _ustEAContainerEntry property entries that indicate its total space exceeded the size of a _ustEAContainer structure.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem. The ACFS Fixer reconstructs the structure to retain as much valid information as possible and may eliminate inaccessible or invalid information.
ACFS-07755: _ustEAContainerHdrNextFreeOffset property has an invalid value\n found: number, but expected to find less than: number for structure:\nstring: Cause: The ustEAContainerHdrNextFreeOffset property of the indicated _ustEAContainer structure was not within the range of valid offset values.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem. The ACFS Fixer reconstructs the structure to retain as much valid information as possible and may eliminate inaccessible information.
ACFS-07756: _ustEAEntryHeader.ustEAEntryHdrNextFreeEAOffset property has an invalid value\n found: number, but expected to find less than: number for _ustEAContainerEntry at offset: number for structure:\nstring: Cause: The _ustEAEntryHeader.ustEAEntryHdrNextFreeEAOffset property of the indicated _ustEAContainerEntry property for the _ustEAContainer structure was not within the range of valid offset values.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem. The ACFS Fixer reconstructs the structure to retain as much valid information as possible and may eliminate inaccessible information.
ACFS-07757: file extended attribute container structure exceeds file system size: string\n _Length: string\nfor structure:\nstring: Cause: The extended attribute container structure of the indicated file referenced meta data beyond the size of the file system. There are two possible causes: 1. The extended attribute container structure disk offset was incorrect. 2. The file system size value was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07758: _ustEAEntryHdrNameLen property has an invalid value\n found: number, but expected non-zero value\n for _ustEAContainerEntry at offset: number for structure:\nstring: Cause: The _ustEAEntryHdrNameLen property of the indicated _ustEAEntryHdr property at the _ustEAContainerEntry offset for the indicated _ustEAContainer structure was invalid. Its value was zero but must be non-zero for an extended attribute name entry.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem. The ACFS Fixer reconstructs the structure to retain as much valid information as possible and may eliminate inaccessible or invalid information.
ACFS-07759: _ustEAEntryValueLen property has an invalid value\n found: number, but expected to find less than: number\n for _ustEAEntry offset: number for structure:\nstring: Cause: The _ustEAEntryValueLen property of the indicated _ustEAEntry property in the _ustEAEntryContainer structure contained an invalid value length that was larger than expected for this structure.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem. The ACFS Fixer reconstructs the structure to retain as much valid information as possible and may eliminate inaccessible or invalid information.
ACFS-07760: _ustEAContainerHdrNextFreeOffset property has an invalid value\n found: number, but expected to find: number for structure:\nstring: Cause: The _ustEAContainerHdrNextFreeOffset property of the indicated _ustEAContainer structure was not within the range of valid offset values.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem. The ACFS Fixer reconstructs the structure to retain as much valid information as possible and may eliminate inaccessible information.
ACFS-07761: directory _Private structure has invalid _dir_bitmap_start value\n found: string maximum: string\nfor structure:\nstring: Cause: The _dir_bitmap_start property of the indicated _Private directory structure was invalid. Its value exceeded the maximum value for the directory.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07762: Directory contains invalid bitmap block number at disk offset: string\nfor file:\nstring: Cause: A bitmap block of the indicated directory file was found in the wrong location. Directory bitmap blocks must be located contiguously after the first bitmap block.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07763: Directory bitmap is not contiguous from block number to block number at disk offset: string\nfor file:\nstring: Cause: A discontinuity was seen in the directory bitmap. Directory bitmap blocks must be located contiguously after the first bitmap block.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07764: Directory bitmap has incorrect last block\n found: number expected: number\nfor file:\nstring: Cause: The directory bitmap does not end where expected.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07765: Version 11.2.0.3 or earlier directory contains bitmap block number at disk offset: string\nfor file:\nstring: Cause: The directory _Private structure indicates that the directory does not have a bitmap, yet a bitmap block was found in the directory.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07766: Directory bitmap does not match state of block number\n bitmap: string block: string\nfor file:\nstring: Cause: The directory bitmap indicates an incorrect state for the directory block.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07767: Directory bitmap contains non-zero value for bit number mapping beyond end of directory:\nstring: Cause: The directory bitmap contains a non-zero bit in the range mapping blocks beyond the end of the directory.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07768: Directory _Private structure has invalid _dir_bitmap_size value\n found: string minimum: string\nfor structure:\nstring: Cause: The _dir_bitmap_size property of the indicated _Private directory structure was invalid. Its value did not meet the minimum value for the directory.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07769: Number of bitmap blocks found does not match value of _dir_bitmap_size in directory _Private structure\n found: string expected: string\nfor structure:\nstring: Cause: The number of bitmap blocks in the directory does not match the number of blocks that were expected.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07770: System directory _Private structure has invalid on-disk version\n found: string expected: string\nfor structure:\nstring: Cause: The on-disk version of the indicated _Private directory structure was invalid.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07771: directory _Private structure has invalid directory bitmap end value\n found: string maximum: string\nfor structure:\nstring: Cause: The calculated end of the directory bitmap of the indicated _Private directory structure was invalid. Its value exceeded the maximum value for the directory.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07772: snapshot 'string' has invalid _SnapLinkParentFenum value\n found: number maximum: number\nfor structure:\nstring: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer has resolved the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07773: snapshot link to non-existent snapshot: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer has resolved the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07774: Global_Metadata_Directory structure has incorrect _remap_table_fileid value\n found: string, but expected to find: string\nfor structure:\nstring: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer will resolve the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07775: Global_Metadata_Directory structure has incorrect _remap_bitmap_fileid value\n found: string, but expected to find: string\nfor structure:\nstring: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer will resolve the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07776: Global_Metadata_Directory structure has incorrect _accelerator_remap_table_fileid value\n found: string, but expected to find: string\nfor structure:\nstring: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer will resolve the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07777: Global_Metadata_Directory structure has incorrect _accelerator_remap_bitmap_fileid value\n found: string, but expected to find: string\nfor structure:\nstring: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer will resolve the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07778: read failed for File_Entry_Table metadata file at VolFETALPosition offset: string\n- assuming default File Entry Table offset: string\nfor structure:\n string: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer will resolve the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07779: could not locate File_Entry_Table metadata file at VolFETALPosition offset: string\n- assuming default File Entry Table offset: string\nfor structure:\nstring: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer will resolve the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07864: A request to cancel string was made \nwhile the file system was being repaired. This could leave the file system \nin an inconsistent state. It is strongly recommended that string \nbe rerun to complete file system repairs.: Cause: The ACFS fixer was cancelled before all file system repairs were completed.; Action: Rerun the ACFS fixer to complete file system repairs.
ACFS-07900: Security_Metadata file _Private structure has invalid _freeDataList value\n found: number maximum: number\nfor structure:\nstring: Cause: The _freeDataList property of the _Private structure of the indicated Security_Metadata file was incorrect. The _freeDataList value exceeded the maximum value for this Security_Metadata file.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07901: Hash_Bucket metadata structure has incorrect _controlling_bkt value\n found: string maximum: string\nfor structure:\nstring: Cause: The _controlling_bkt property of the indicated Hash_Bucket structure was incorrect. Its value exceeded the maximum value for the hash table.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07902: Hash_File_Master_Block metadata structure has incorrect value for entry number in _hash_bucket_group array\n found: number minimum: number\nfor structure:\nstring: Cause: The entry in _hash_bucket_group array of the indicated Hash_File_Master_Block structure was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07903: Hash_Bucket metadata structure has invalid data; expected all zeros\nfor structure:\nstring: Cause: The ACFS Checker/Fixer found an inconsistency within the file system.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07907: directory file has no storage allocated to it\nfor file:\nstring: Cause: The ACFS Checker/Fixer found an inconsistency within the file system.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07908: Root_Directory cannot be repaired\nfile:\nstring: Cause: The ACFS Checker/Fixer found an inconsistency with the Root_Directory metadata.; Action: The Root_Directory is a critical system file that is necessary for a functioning file system. Restore the file system from a backup copy.
ACFS-07909: System metadata was truncated, possibly resulting in the deletion of files.: Cause: The ACFS Checker/Fixer found an inconsistency within the file system.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07924: Snap_Map_header has invalid value for RW snap storage not in map\n found: string, but expected to find: string\nfor file:\nstring: Cause: The Snap_Map_header property that indicates the amount of RW snap storage not recorded in the Snap_Map file is incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07925: Snap_Map_header has invalid value for snap storage in map\n found: string, but expected to find: string\nfor file:\nstring: Cause: The Snap_Map_header property that indicates the amount of snap storage recorded in the Snap_Map file is incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07926: Snap_Map_header has invalid value for snap map flags\n found: string\nfor file:\nstring: Cause: The Snap_Map_header flags field is invalid.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07928: Plug-in configuration file has invalid _FileSize value\n found: string, but expected to find: string\nfor file:\nstring: Cause: The _FileSize property of the indicated plug-in configuration file was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-07929: The string command is unable to open the storage accelerator volume string that is associated with this file system.: Cause: fsck (Unix or Linux) or acfschkdsk.exe (Windows) could not open the specified storage accelerator volume. This could be because the ASM disk group containing the storage accelerator volume is not mounted.; Action: Verify that the ASM disk group containing the storage accelerator volume is mounted. Then rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ACFS-07930: Continuing will result in the storage accelerator volume being removed from the file system, which could leave the file system in an inconsistent and possibly unusable state if critical system metadata is stored on the storage accelerator volume.: Cause: fsck (Unix or Linux) or acfschkdsk.exe (Windows) could not open the specified storage accelerator volume. This could be because the ASM disk group containing the storage accelerator volume is not mounted.; Action: If the accelerator volume has no known problems, verify that the ASM disk group containing the storage accelerator volume is mounted. Then rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows). Or, if the accelerator volume is known to have problems such as disk corruption and you wish to have fsck (Unix of Linux) or acfschkdsk.exe (Windows) disassociate the accelerator volume from the file system, allow it to continue.
ACFS-07932: Volume string does not contain a valid ACFS storage accelerator.: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer will resolve the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07933: Accelerator volume string is associated with a different file system.: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer will resolve the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07934: The file identifier for the accelerator volume storage bitmap is invalid.\n found: string maximum: string: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer will resolve the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07935: The _FileEntry metadata structure for the accelerator volume storage bitmap is invalid.: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer will resolve the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07936: Extent structure has incorrect _VolId value.\n found: string\nfor structure:\nstring: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer will resolve the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07937: File extent exceeds accelerator volume size.\n string\nextent: _FileOffset: string _Length: string _PhysicalDiskOffset: string\nfor file:\nstring: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer will resolve the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07938: Accelerator Global_BitMap has invalid value for number of bits set.\n found: string maximum: string\nfor file:\nstring: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer will resolve the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07939: Accelerator Global_BitMap has invalid value for number of bits set.\n found: string, but expected to find: string\nfor file:\nstring: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer will resolve the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07940: Accelerator Global_BitMap has invalid value for next offset to search.\n found: string maximum: string\nfor file:\nstring: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer will resolve the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07941: mismatch between temporary Global_BitMap and on-disk accelerator Global_BitMap: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer will resolve the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07942: Accelerator Global_BitMap has bits incorrectly set for storage beyond the file system size for file:\nstring: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer will resolve the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07943: The specified volume is an accelerator volume. Cannot proceed.: Cause: The volume specified on the command line was an accelerator volume. The command requires the primary file system volume.; Action: Rerun the command specifying the primary file system volume.
ACFS-07944: could not set up _VolDiskHdr STRUCT_INFO: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer will resolve the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07945: found _DirNode in block: number at disk offset: string\nfor directory:\nstring: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer will resolve the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07946: string has an invalid extent node at disk offset string: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer will resolve the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07947: Mount point directory 'string' was specified when device name expected.: Cause: The ACFS Checker rejected the mount point because a file system device name was expected.; Action: Specify the device containing the file system.
ACFS-07950: File has _range_size value which does not match extent metadata.\n found: string expected: string\nfor structure:\nstring: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer will resolve the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07951: signal number received: Cause: The ACFS Checker received the indicated interrupt signal.; Action: If this was not an operator-initiated abort of the ACFS Checker, then correct the problem indicated by the accompanying error messages. If the solution is not clear, contact Oracle Support Services.
ACFS-07952: File has _SynchFlags value indicating range locking which is not supported on this file system.\n found: string\nFile:\nstring: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer will resolve the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07953: File has invalid _range_size value.\n found: number expected: number\nFile:\nstring: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer will resolve the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07954: The specified volume is an accelerator volume so cannot be made mountable.: Cause: An attempt to force a volume into a mountable state using 'fsck.acfs -f' was rejected because the supplied volume was an accelerator. An accelerator can only be used in conjunction with its primary volume.; Action: Reissue the 'fsck.acfs -f' command with the primary volume that corresponds to the supplied accelerator volume. If the primary volume no longer exists, the accelerator volume cannot be made usable.
ACFS-07955: read of global directory file entry failed: Cause: A read of the volume metadata during an invocation of 'fsck.acfs -f' failed. Accompanying messages provide failure details.; Action: Correct the problem indicated by the other messages. If the cause of the problem is unclear, contact Oracle Support Services.
ACFS-07956: accelerator volume found and restored: Cause: During an invocation of 'fsck.acfs -f', the supplied primary volume's metadata showed that it had made use of an accelerator volume. Both the primary and accelerator volumes have been restored, but the metadata has not been verified.; Action: The ACFS Fixer has restored the file system, but its metadata must be verified using 'fsck.acfs' before attempting to mount it. If the accelerator had been repurposed, the file system associated with the primary volume cannot be mounted, which will be reported by 'fsck.acfs'.
ACFS-07957: unable to mount removed file system string: Cause: An attempt to mount the indicated file system was rejected because it had been removed via the acfsutil rmfs utility.; Action: To render this file system mountable, run 'fsck.acfs -f'.
ACFS-07960: acfsdbg cannot find the ACFS storage accelerator volume: Cause: An attempt to locate the ACFS storage accelartor volume failed. Either: - the file system did not have an ACFS storage accelerator, or - the metadata for locating the ACFS storage accelerator was corrupt, or - the 'acfsdbg' command was being used to analyze the output of the 'acfsutil meta' command, and the sparse copy of the ACFS storage accelerator volume was not provided.; Action: Retry the 'acfsdbg' command using the '-x' option to specify the location of the ACFS storage accelerator volume.
ACFS-07961: GBM Lookup Table is corrupt and must be removed.: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer has resolved the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07962: GBM Lookup Table has the wrong size.\n found: number expected: number: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer has resolved the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07963: GBM Lookup Table is not a multiple of the block size.\n found: number expected: number: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer has resolved the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07964: mismatch between GBM Lookup Table block and temporary GBM Lookup Table block for disk offset: string: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer has resolved the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07965: Global_Metadata_Directory structure has incorrect _glut_fenum value\n found: string, but expected to find: string\nfor structure:\nstring: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer has resolved the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07966: GBM Lookup Table file entry is not initialized.: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer has resolved the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07967: 'acfsutil meta' files and ACFS file system devices cannot be processed at the same time: string: Cause: An ACFS Checker attempt was rejected because a mix of 'acfsutil meta' metadata collector files and physical ACFS file system devices were specified on the command line.; Action: Either specify the physical ACFS file system device or the the primary and accelerator 'acfsutil meta' files on the command line.
ACFS-07968: Remap_BitMap bit set for disk offset string has no corresponding remapped offset.: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer has resolved the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07969: Remap_Table has incorrect _VolVolumeSize value.\n found: string, but expected to find: string\nfor structure:\nstring: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer has resolved the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-07970: communication error with ACFS kernel driver encountered during setup for online fsck: Cause: An attempt to run online fsck failed due to a communication error with the ACFS kernel driver. The accompanying messages provide detailed failure information.; Action: Correct the problems indicated by the accompanying messages and retry the online fsck operation. If the solution is not clear, contact Oracle Support Services.
ACFS-07971: communication error with ACFS kernel driver encountered during cleanup for online fsck: Cause: An execution of online fsck did not completely correctly because a communication error with the ACFS kernel driver occurred during cleanup processing. The accompanying messages provided detailed failure information. As a result, cleanup of online fsck may be incomplete, which may cause failures in other ACFS operations. Manual cleanup of online fsck should undertaken as soon as possible to ensure continued correct operation.; Action: Correct the problems indicated by the accompanying messages, then unmount and remount the ACFS file system on all nodes. This will enable the cluster to complete cleanup of online fsck.
ACFS-07972: unable to unlink online fsck Copy-On-Write (COW) file: string: Cause: An execution of online fsck did not complete correctly because unlinking the online fsck COW file failed. The accompanying messages provide detailed failure information.; Action: Manually unlink the indicated online fsck COW file to reclaim file system storage and make the online fsck COW file path available to subsequent online fsck operations.
ACFS-07973: online fsck Copy-On-Write (COW) file string not accessible on all nodes: Cause: An attempt to run online fsck for an ACFS file system failed because one or more nodes with the ACFS file system mounted were unable to access the indicated online fsck COW file.; Action: Retry the online fsck operation after verifying that all nodes with the ACFS file system mounted can access the indicated online fsck COW file.
ACFS-07974: online fsck already active on the specified ACFS file system: Cause: An attempt to run online fsck for an ACFS file system was rejected because it appeared an instance of online fsck was already active on the ACFS file system.; Action: Retry the online fsck operation after waiting for the other instance of online fsck to complete. If there was no other instance of online fsck active on the ACFS file system, the ACFS file system should be unmounted and remounted on all nodes to clear this state.
ACFS-07975: online fsck already active on another ACFS file system: Cause: An attempt to run online fsck for an ACFS file system was rejected because it appeared an instance of online fsck was already active on another ACFS file system within the same cluster. More than one instance of online fsck is not allowed within the same cluster.; Action: Retry the online fsck operation after waiting for the other instance of online fsck to complete. If there was no other instance of online fsck active within the cluster, the prior ACFS file system checked by online fsck should be unmounted and remounted on all nodes to clear this state.
ACFS-07976: network communication error encountered during setup for online fsck: Cause: An attempt to run online fsck for an ACFS file system failed because a network communication error was encountered between the nodes that have the ACFS file system mounted.; Action: Examine the alert logs and Oracle Kernel Services (OKS) persistent logs on all nodes for network and membership errors and correct any errors. Then retry the online fsck operation after verifying that network connectivity exists between all nodes that have the ACFS file system mounted and that the ACFS file system is online on all of those nodes.
ACFS-07977: network communication error encountered during cleanup for online fsck: Cause: An execution of online fsck did not complete correctly because a network communication error occurred during cleanup processing between the nodes that have the ACFS file system mounted. As a result, cleanup of online fsck may be incomplete, which may cause failures in other ACFS operations. Manual cleanup of online fsck should be undertaken as soon as possible to ensure continued correct operation.; Action: Examine the alert logs and Oracle Kernel Services (OKS) persistent logs on all nodes for network and membership errors and correct any errors. Verify that network connectivity exists between all nodes that have the ACFS file system mounted, then unmount and remount the ACFS file system on all nodes. This will enable the cluster to complete cleanup of online fsck.
ACFS-07978: I/O error encountered accessing online fsck Copy-On-Write (COW) file: Cause: An attempt to run online fsck for an ACFS file system was aborted because online fsck encountered an I/O error while accessing the online fsck COW file.; Action: Ensure that the ACFS file system containing the online fsck COW file is mounted and online on exactly those nodes on which the ACFS file system specified for online fsck is mounted. Examine the Oracle Kernel Services (OKS) persistent logs on all nodes for errors, correct any errors, and then retry the online fsck operation.
ACFS-07979: unexpected error number from ACFS kernel driver encountered during setup for online fsck: Cause: An attempt to run online fsck for an ACFS file system failed because of an unexpected error reported from the ACFS kernel driver.; Action: Examine the alert logs and Oracle Kernel Services (OKS) persistent logs on all nodes for errors, correct any errors if possible, and then retry the online fsck operation. If the solution is not clear, contact Oracle Support Services.
ACFS-07980: unexpected error number from ACFS kernel driver encountered during cleanup for online fsck: Cause: An execution of online fsck did not complete correctly because an unexpected error during cleanup processing was reported from the ACFS kernel driver. As a result, cleanup of online fsck may be incomplete, which may cause failures in other ACFS operations. Manual cleanup of online fsck should be undertaken as soon as soon as possible to ensure continued correct operation.; Action: Examine the alert logs and Oracle Kernel Services (OKS) persistent logs on all nodes for errors and correct any errors. Unmount and remount the ACFS file system on all nodes. This will enable the cluster to complete cleanup of online fsck.
ACFS-07981: failed to copy global ACFS metadata to online fsck Copy-On-Write (COW) file: Cause: An attempt to run online fsck for an ACFS file system failed because online fsck could not copy global ACFS metadata to the online fsck COW file.; Action: Examine the Oracle Kernel Services (OKS) persistent logs on all nodes. If metadata validation errors are seen in the OKS persistent logs, it may not be possible to run online fsck on the specified ACFS file system, offline fsck may be required instead. If metadata validation errors are not seen in the OKS persistent logs, resolve any errors indicated in the OKS persistent logs, and then retry the online fsck operation.
ACFS-07982: incorrect kernel state number for online fsck encountered during setup for online fsck: Cause: An attempt to run online fsck for an ACFS file system failed because the state data for online fsck maintained in the ACFS kernel driver was inconsistent. This is an internal error.; Action: Contact Oracle Support Services.
ACFS-07983: incorrect kernel state number for online fsck encountered during cleanup for online fsck: Cause: An execution of online fsck did not complete correctly because the state data for online fsck maintained in the ACFS kernel driver was inconsistent during cleanup processing. This is an internal error.; Action: Contact Oracle Support Services.
ACFS-07984: online fsck aborted because file system mounted on a new node: Cause: An attempt to run online fsck for an ACFS file system was aborted because the ACFS file system was mounted on a new node while online fsck was running.; Action: Retry the online fsck operation.
ACFS-07985: communication error with ACFS kernel driver encountered while querying runtime status for online fsck: Cause: An attempt to run online fsck for an ACFS file system was aborted because a query to the ACFS kernel driver for the runtime status for online fsck encountered a communcation error. The accompanying messages provide detailed failure information.; Action: Correct the problems indicated by the accompanying messages and retry the online fsck operation. If the solution is not clear, contact Oracle Support Services.
ACFS-07986: online fsck Copy-On-Write (COW) file is full: Cause: An attempt to run online fsck for an ACFS file system was aborted because the online fsck COW file ran out of space.; Action: Retry the online fsck operation with a larger COW file size.
ACFS-07987: unknown runtime error number encountered during online fsck: Cause: An attempt to run online fsck for an ACFS file system was aborted because an unknown runtime error was encountered.; Action: Examine the alert logs and Oracle Kernel Services (OKS) persistent logs on all nodes for online fsck errors. These online fsck errors will indicate whether further action is required. Then retry the online fsck operation. If the error persists, contact Oracle Support Services.
ACFS-07988: network communication error encountered during online fsck: Cause: An attempt to run online fsck for an ACFS file system was aborted because a network communication error was encountered between the nodes that have ACFS file ssytem mounted.; Action: Examine the alert logs and Oracle Kernel Services (OKS) persistent logs on all nodes for network and membership errors and correct any errors. Then retry the online fsck operation after verifying that network connectivity exists between all nodes that have the ACFS file system mounted and that the ACFS file system is online on all of those nodes.
ACFS-07990: unexpected non-empty volume logs encountered during online fsck: Cause: An attempt to run online fsck for an ACFS file system was aborted because non-empty volume logs were encountered unexpectedly.; Action: Retry the online fsck operation. If the error persists, contact Oracle Support Services.
ACFS-07991: The length of the online fsck Copy-On-Write (COW) file path exceeds number.: Cause: An attempt to run online fsck was rejected because the specified online fsck COW file path exceeded the maximum length displayed in the message.; Action: Retry the online fsck operation specifying a COW file whose path name is less than the maximum length displayed in the message.
ACFS-07999: unexpected ACFS Checker/Fixer assert: "string", string: string: number: Cause: An unexpected situation has occurred.; Action: Contact Oracle Support Services.
ACFS-08000: unable to create online fsck Copy-On-Write (COW) file: string: Cause: An attempt to run online fsck was rejected because an error occurred while creating the indicated COW file. The accompanying messages provide detailed failure information.; Action: Correct the problems indicated by the accompanying messages and retry the online fsck operation. If the solution is not clear, contact Oracle Support Services.
ACFS-08001: online fsck Copy-On-Write (COW) file path is not on an ACFS file system: Cause: An attempt to run online fsck was rejected because the specified online fsck COW file path is not on an ACFS file system.; Action: Retry the online fsck operation specifying a COW file path that is on an ACFS file system.
ACFS-08002: _NextDeferredListLink on Deferred_Delete_Storage_List references a snapshot that is not valid\n _NextDeferredListLink: string\n snapshot: string (identifier: number)\nfor structure:\nstring: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer has resolved the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-08003: Deferred_Delete_Storage_List has invalid file identifier for _PrevDeferredListLink:\n found: string expected: string\nfor structure:\n string: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer has resolved the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-08004: unable to process Deferred_Delete_Storage_List data for structure:\n%(1): Cause: File system checking has identified metadata inconsistencies. The accompanying messages provide further details.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer has resolved the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-08005: Deferred_Delete_Storage_List incorrectly contains an entry for a read only snapshot:\n file identifier: string\n snapshot: string (identifier: number)\nfor structure:\nstring: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer has resolved the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-08006: _NextDeferredListLink on Deferred_Delete_Storage_List references a file identifier that exceeds the maximum value supported for this file system\n _NextDeferredListLink: string\n file identifier: string maximum: string\nfor structure:\nstring: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer has resolved the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-08007: string has determined that there is a loop within a Deferred_Delete_Storage_List\nfor file:\nstring: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer has resolved the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-08008: Deferred_Delete_Storage_List structure for accelerator volume has invalid values:\n _PrevDeferredListLink: string\n _NextDeferredListLink: string\nfor structure:\nstring: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer has resolved the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-08009: Deferred_Delete_Storage_List for snapshot: string (identifier: number) incorrectly contains an entry for a File_Entry_Table: string\nfor structure:\nstring: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer has resolved the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-08010: Deferred_Delete_Storage_List entry contains an invalid _DRSLSequenceNumber\n found: string\n maximum: string\nfor file:\nstring: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer has resolved the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-08011: _NextDeferredListLink on Deferred_Delete_Storage_List references a snapshot that does not exist\n _NextDeferredListLink: string\n snapshot identifier: number\nfor structure:\nstring: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer has resolved the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-08012: Deferred_Delete_Storage_List has invalid file identifier for_NextDeferredListLink: string\n snapshot identifier: number\n found: string minimum: string\nfor structure:\nstring: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer has resolved the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-08013: Deferred_Delete_Storage_List contains an entry that was previously referenced by a directory or other ACFS structure\n _NextDeferredListLink: string\n file identifier: string\nfor structure:\nstring: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer has resolved the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-08016: multiple invalid snap_map_tuples found; number found: number: Cause: File system checking has identified the metadata inconsistency reported in the message. The number of instances is indicated here in lieu of flooding the output by displaying message ACFS-07414 for each occurrence.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer has resolved the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-08017: multiple snap_map_tuples with (0,0) found where a non-zero value was expected; number found: number: Cause: File system checking has identified the metadata inconsistency reported in the message. The number of instances is indicated here in lieu of flooding the output by displaying message ACFS-07448 for each occurrence.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer has resolved the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-08018: allocated but unused storage of string found: Cause: File system checking has identified unreferenced snapshot storage that could be freed.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer has resolved the problem and freed the indicated storage. If the message was generated by the ACFS Checker, then run the ACFS Fixer to free the storage.
ACFS-08019: online fsck already active on the local node: Cause: An attempt to run online fsck for an ACFS file system was rejected because it appeared an instance of online fsck was already active on the local node.; Action: Retry the online fsck operation after waiting for the other instance of online fsck to complete. If another instance of online fsck was not active on the local node, all ACFS file systems on the local node should be unmounted and remounted to clear this state.
ACFS-08020: size of the online fsck Copy-On-Write (COW) file must be at least number megabytes: Cause: An attempt to run online fsck was rejected because the specified online fsck COW file size was smaller than the minimum size displayed in the message.; Action: Retry the online fsck operation specifying a COW file size that is larger than the minimum size displayed in the message.
ACFS-08021: online fsck flags string must all be specified together: Cause: An attempt to run online fsck was rejected because insufficient online fsck flags were specified.; Action: Retry the online fsck operation while specifying all of the online fsck flags indicated in the message.
ACFS-08022: failed to create online fsck Copy-On-Write (COW) file due to insufficient free storage: Cause: An attempt to run online fsck for an ACFS file system was aborted because the ACFS file system containing the online fsck COW file did not have sufficient free storage for the full online fsck COW file.; Action: Retry the online fsck operation specifying a smaller online fsck COW file size or another ACFS file system for the online fsck COW file that has more free storage.
ACFS-08023: failed to create online fsck Copy-On-Write (COW) file: Cause: An attempt to run online fsck for an ACFS file system was aborted because the online fsck Copy-On-Write (COW) file could not be created successfully.; Action: Correct the problems indicated by the accompanying messages and retry online fsck operation. If the solution is not clear, contact Oracle Support Services.
ACFS-08024: online fsck is unsupported by the loaded ACFS driver version: Cause: An attempt to run online fsck for an ACFS file system was rejected because the loaded ACFS driver version does not support online fsck.; Action: Load an ACFS driver version (>= 12.1.0.2) that supports online fsck and retry online fsck operation.
ACFS-08025: online fsck could not read on-disk superblocks: Cause: An attempt to run online fsck for an ACFS file system failed because the on-disk superblocks could not be read.; Action: Ensure that the ACFS file system undergoing online fsck is mounted and online. Examine the Oracle Kernel Services (OKS) persistent logs for errors, correct any errors, and then retry the online fsck operation.
ACFS-08026: online fsck found invalid on-disk superblocks: Cause: An attempt to run online fsck for an ACFS file system failed because the on-disk superblocks were found to be invalid.; Action: Unmount the filesystem and run fsck (Unix or Linux) or acfschkdsk.exe (Windows) as soon as possible to fix the metadata inconsistency.
ACFS-08027: online fsck Copy-On-Write (COW) file cannot be within the ACFS file system undergoing online fsck: Cause: An attempt to run online fsck for an ACFS file system was rejected because the online fsck Copy-On-Write (COW) file was placed on the ACFS file system undergoing online fsck.; Action: Retry the online fsck operation specifying a location for the online fsck COW file that is not on the ACFS file system undergoing online fsck.
ACFS-08028: online fsck encountered unexpected partial read: Cause: An attempt to run online fsck for an ACFS file system failed due to an unexpected read error.; Action: Ensure that the ACFS file system containing the online fsck Copy-On-Write (COW) file is mounted and online on exactly those nodes on which the ACFS file system specified for online fsck is mounted. Examine the Oracle Kernel Services (OKS) persistent logs on all nodes for errors, correct any errors, and then retry the online fsck operation.
ACFS-08029: The ACFS Checker failed because it was supplied an unexpanded acfsutil meta output file.\n The file needs to be expanded using\n acfsutil meta -e string -f string.expanded: Cause: The ACFS Checker did not know how to read an unexpanded acfsutil meta output file.; Action: Expand the 'acfsutil meta' metadata collection file using: acfsutil meta -e <meta.file> -f <meta.file.expanded> then use the ACFS Checker against the expanded file.
ACFS-08030: Failed to write metadata collector record header (Flags:0xnumber, VolID:number, Offset:number, Size:number)\n Write size:number\n Actual written:number: Cause: The ACFS Checker failed to write a record header to the metadata collector file.; Action: Correct the problem described in the accompanying messages if possible and rerun 'acfsutil meta' metadata collector.
ACFS-08031: Failed to write metadata collector record body (Flags:0xnumber, VolID:number, Offset:number, Size:number)\n Write size:number\n Actual written:number: Cause: The ACFS Checker failed to write a record body to the metadata collector file.; Action: Correct the problem described in the accompanying messages if possible and rerun 'acfsutil meta' metadata collector.
ACFS-08032: could not disable compression for online fsck Copy-On-Write (COW) file: Cause: An attempt to run online fsck for an ACFS file system failed because compression could not be disabled for the online fsck Copy-On-Write (COW) file.; Action: Retry the online fsck operation. If the online fsck operation continues to fail, contact Oracle Support Services.
ACFS-08033: online fsck aborted to avoid file system deadlock: Cause: An attempt to run online fsck for an ACFS file system was aborted to avoid a deadlock within the file system.; Action: Retry the online fsck operation. If the online fsck operation continues to fail, contact Oracle Support Services.
ACFS-08034: online fsck failed to fix metadata due to communication error with ACFS kernel driver: Cause: An attempt by online fsck to fix file system metadata failed due to a communication error with the ACFS kernel driver. The accompanying messages provide detailed failure information.; Action: Correct the problems indicated by the accompanying messages and retry the online fsck operation. If the solution is not clear, contact Oracle Support Services.
ACFS-08035: unexpected error number from ACFS kernel driver encountered while fixing metadata via online fsck: Cause: An attempt by online fsck to fix file system metadata failed due to an unexpected error reported from the ACFS kernel driver.; Action: Examine the alert logs and Oracle Kernel Services (OKS) persistent logs on the node where online fsck was running for errors, correct any errors, and retry the online fsck operation. If the issue persists, contact Oracle Support Services.
ACFS-08036: unable to stop online fsck: Cause: An unmount operation was unable to stop an online fsck operation that had been using the unmounting filesystem to store a Copy-On-Write (COW) file.; Action: No action needed to complete the unmount. If the online fsck operation that had been using the unmounting filesystem to store a Copy-On-Write (COW) file reports any errors, ignore the errors and retry the online fsck operation.
ACFS-08037: online fsck aborted because the file system containing the Copy-On-Write (COW) file was unmounted on one or more nodes: Cause: An attempt to run online fsck for an ACFS file system was aborted because the ACFS file system containing the Copy-On-Write (COW) file was unmounted on one or more nodes.; Action: Ensure that the ACFS file system containing the online fsck Copy-On-Write (COW) file is mounted on all of the same nodes as the ACFS file system undergoing online fsck, then retry online fsck operation.
ACFS-08038: online fsck could not start due to insufficient space in file system: Cause: An attempt to run online fsck for an ACFS file system failed because the ACFS file system is full.; Action: Make at least 16K of free space available within the ACFS file system and retry the online fsck operation.
ACFS-08039: online fsck could not start due to insufficient memory: Cause: An attempt to run online fsck for an ACFS file system failed because there was insufficient memory on one of the nodes with the ACFS file system mounted.; Action: Examine the Oracle Kernel Services (OKS) persistent logs on all nodes with the ACFS file system mounted for messages concerning insufficient memory. Ensure that all nodes with the ACFS file system mounted have available memory and retry the online fsck operation.
ACFS-08040: online fsck could not clean up due to insufficient memory: Cause: An execution of online fsck for an ACFS file system did not complete correctly because there was insufficient memory on one of the nodes with the ACFS file system mounted.; Action: Unmount and remount the ACFS file system on all nodes. This will enable the cluster the complete cleanup of online fsck.
ACFS-08041: online fsck failed to create internal structures: Cause: An attempt to run online fsck for an ACFS file system failed due to errors while creating internal structures.; Action: Examine the alert logs and Oracle Kernel Services (OKS) persistent logs on all nodes for errors, correct any errors if possible, and then retry the online fsck operation. If the solution is not clear, contact Oracle Support Services.
ACFS-08043: Could not determine the file size for: string: Cause: The ACFS Checker failed to get the specified file's size.; Action: Correct the problem described in the accompanying messages if possible and rerun 'acfsutil meta' metadata collector.
ACFS-08044: Failed to write metadata collector log message to string: Cause: The ACFS Checker failed to write the log message to the specified log file.; Action: Correct the problem described in the accompanying messages if possible and rerun 'acfsutil meta' metadata collector. This message is accompanied by other messages providing details on the error.
ACFS-08045: online fsck could not create special work directory: Cause: An attempt to run online fsck for an ACFS file system failed because it could not create a special work directory required for online fsck execution.; Action: Examine the alert log and Oracle Kernel Services (OKS) persistent log on the affected node, correct any errors, and then retry the online fsck operation.
ACFS-08046: allocated but unused storage of number MB found: Cause: File system checking has identified unreferenced fshare storage that could be freed.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer has resolved the problem and freed the indicated storage. If the message was generated by the ACFS Checker, then run the ACFS Fixer to free the storage.
ACFS-08047: RefCnt Table has an invalid counts for number of entries: string: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer will resolve the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-08048: unable to determine default location for online fsck Copy-On-Write (COW) file because the cluster is in rolling migration: Cause: Due to rolling upgrade from older kernel versions, the location for the online fsck Copy-On-Write (COW) file must be specified and must be placed in a separate ACFS file system from the ACFS file system undergoing online fsck.; Action: Complete the rolling upgrade or specify a location for the COW file that is in a separate ACFS file system from the ACFS file system undergoing online fsck.
ACFS-08049: A valid ACFS mount point is required: Cause: A valid ACFS mount point was not entered.; Action: Rerun the ACFS Checker/Fixer with a valid ACFS mount point as the final argument.
ACFS-08050: acfsdbg command line had 2 conflicting Volume IDs: string vs string: Cause: The user specified acfsdbg command has 2 different Volume IDs.; Action: The command should be specified with just 1 Volume ID, or the command should use the default Volume ID as specified by the 'volume' command.
ACFS-08051: acfsdbg command field does not support a Volume ID prefix: string: Cause: The user specified acfsdbg command field does not allow a Volume ID prefix.; Action: The command should be specified without a Volume ID prefix.
ACFS-08052: Global_Metadata_Directory structure has incorrect _nimap_fenum value\n found zero but expected to find non-zero value\nfor structure:\nstring: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer has resolved the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-08053: Global_Metadata_Directory structure has incorrect _accel_nimap_fenum value\n found zero but expected to find non-zero value\nfor structure:\nstring: Cause: File system checking has identified the metadata inconsistency reported in the message.; Action: If the message was generated by the ACFS Fixer, then no further action is needed. The ACFS Fixer has resolved the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ACFS-08054: failed to create FETA file access structure for file ID string: Cause: The acfsdbg utility failed to complete because it could not allocate sufficient memory for the operation.; Action: Correct the problem indicated by the other messages. If the solution is not clear, contact Oracle Support Services.
ACFS-08055: failed to create a file access structure for file ID string: Cause: The acfsdbg utility failed to complete because it could not allocate sufficient memory for the operation.; Action: Correct the problem indicated by the other messages. If the solution is not clear, contact Oracle Support Services.
ACFS-08056: failed to read the on-disk file entry for file ID string: Cause: The acfsdbg utility failed to read the file entry for the indicated file ID. Refer to accompanying messages for more information on the problem.; Action: Correct the problem indicated by the other messages. If the solution is not clear, contact Oracle Support Services.
ACFS-08057: failed to read directory contents for file ID string: Cause: An acfsdbg command was not executed due to a metadata inconsistency or a physical I/O failure reported in the accompanying message.; Action: Correct the problem indicated by the other messages. If the solution is not clear, contact Oracle Support Services.
ACFS-08058: Unknown directory entry OfsOdsType: string\n File ID: string: Cause: The acfsdbg utility has identified the metadata inconsistency reported in the accompanying message. information on the problem.; Action: Run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case contact Oracle Support Services.
ACFS-08059: This can occur when snapshots are deleted from the middle of the snapshot tree.: Cause: Informational.; Action: None
ACFS-08060: No Such File: string/string: Cause: The acfsdbg utility could not find the specified file. Refer to accompanying messages for more information on the problem.; Action: Correct the problem indicated by the other messages. If the solution is not clear, contact Oracle Support Services.
ACFS-08061: Name longer than number: string\n string: Cause: The acfsdbg utility has found that the specified file or directory name was too long. Refer to accompanying messages for more information on the problem.; Action: Correct the problem indicated by the other messages. If the solution is not clear, contact Oracle Support Services.
ACFS-08062: The snapshot prefixed path did not start with string@/...: Cause: The acfsdbg utility found that the snapshot path specifications did not start with the snapshot root directory. Refer to accompanying messages for more information on the problem.; Action: Correct the problem indicated by the other messages. If the solution is not clear, contact Oracle Support Services.
ACFS-08063: Snapshot name longer than number: string: Cause: The acfsdbg utility found that the specified snapshot name was too long. Refer to accompanying messages for more information on the problem.; Action: Correct the problem indicated by the other messages. If the solution is not clear, contact Oracle Support Services.
ACFS-08064: FSCK read cache failed to init, running without it: Cause: FSCK read cache failed to start, due to insufficient memory.; Action: None
ACFS-08066: Attempt to write stringstringstring length number at string exceeded the end of the metadata structure string.: Cause: The acfsdbg utility was asked to modify an on-disk metadata structure, and then re-checksum the structure, but the offset would place the value past the end of the metadata structure.; Action: Specify a metadata structure field offset that is within the metadata structure.
ACFS-08067: File has incorrect _fshare_src_fenum value, found:number/number.: Cause: The _fshare_src_fenum property of the indicated file name has an invalid value.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-08068: Attempt to read structure length number at string exceeds the end of the buffer string.: Cause: The acfsdbg utility was asked to display an on-disk structure where the buffer offset plus the structure length exceeds the end of the metadata buffer.; Action: Specify a valid on-disk offset for the structure.
ACFS-08069: Attempt to read number byte aligned structure at the unaligned offset string.: Cause: The acfsdbg utility was asked to display an on-disk structure where the offset alignment did not match the structure alignment.; Action: Specify a properly aligned on-disk offset for the structure.
ACFS-08070: End of number metadata block exceeded.: Cause: The acfsdbg utility was asked to display multiple on-disk structures where the repeat count exceeds the end of the current metadata block.; Action: Specify a new on-disk offset in the next metadata structure.
ACFS-08071: Attempt to lock string failed. Process number has the lock.: Cause: A node local lock could not be obtained on the specified device.; Action: Re-issue the command after the specified process has finished.
ACFS-08072: End of file has invalid sparse extent\n for file:\nstring: Cause: fsck found an invalid hole at the end of a sparse file.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-09004: CreateProcess of acfsmountvol failed, string: Cause: The 'advmutil mount' command failed because a required process could not be created. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.
ACFS-09005: Error running string: Cause: The 'advmutil mount' command failed because a required process could not be executed. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.
ACFS-09006: Error opening volume string: Cause: The advmutil command failed because the indicated file could not be created. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.
ACFS-09009: Error closing volume string: Cause: The 'advmutil mount' or 'advmutil list' command encountered an error; Action: None. The command completed successfully. The indicated file was closed by the operating system.
ACFS-09010: Error locking volume string: Cause: The 'advmutil dismount' command failed while attempting to lock the indicated volume. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.
ACFS-09011: Error dismounting file system on volume string: Cause: The 'advmutil dismount' command failed. The accompanying messages provide detailed failure information.; Action: Ensure that the indicated file system is not in use. Examine the accompanying messages, resolve the indicated problems, and then retry the operation.
ACFS-09012: Error opening the Windows Registry: Cause: The 'advmutil list' command failed while opening the Windows Registry. This is an internal error.; Action: Contact Oracle Support Services.
ACFS-09013: Error reading the Windows Registry: Cause: The 'advmutil list' command failed while reading the Windows Registry. This is an internal error.; Action: Contact Oracle Support Services.
ACFS-09015: The volume string was not found. Verify the diskgroup is mounted and the volume is enabled.: Cause: The 'advmutil mount' command failed because the indicated ADVM volume was not found.; Action: Run the command 'asmcmd volinfo --all'. If the indicated volume is listed as 'DISABLED', run the command 'asmcmd volenable' and then retry the mount operation. If the indicated volume is not listed, verify the ASM setup, and then create and mount the ADVM volume.
ACFS-09016: Error mounting volume string on drive string: Cause: The 'advmutil mount' command failed to mount the specified volume. The accompanying messages provide detailed failure information.; Action: Ensure that the user issuing the mount command has write permissions on the drive. Examine the accompanying messages, resolve the indicated problems, and then retry the operation. Examine the accompanying messages, resolve the indicated problems, and then retry the operation.
ACFS-09018: Error broadcasting mount of volume string on drive string: Cause: The 'advmutil mount' command failed because it was unable to broadcast device change information to other devices in the system. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.
ACFS-09019: Error opening volume on string: Cause: The 'advmutil dismount' command failed to open the indicated file. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.
ACFS-09020: Error dismounting string: Cause: An 'advmutil dismount' operation failed to remove a symbolic link. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.
ACFS-09021: Error broadcasting dismount of string: Cause: The 'advmutil dismount' command failed because it was unable to broadcast device change information to other devices in the system. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.
ACFS-09025: Failed to update the Windows Registry for volume string on drive string: Cause: An attempt to store data in the Windows registry failed. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.
ACFS-09027: Error deleting the drive letter assignment string: Cause: An 'advmutil dismount' command failed because the specified drive letter could not be removed from a volume assignment. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.
ACFS-09028: Assignment for drive letter string not found: Cause: An 'advmutil dismount' command failed because the indicated drive letter could not be found.; Action: Retry the 'advmutil dismount' command specifying the correct drive letter.
ACFS-09030: Error unassigning drive letter string from volume string: Cause: An advmutil dismount failed because it could not unassign a drive letter. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.
ACFS-09034: Error taking string offline: Cause: An 'advmutil dismount' command failed to offline the specified mount point.; Action: Verify that the mount point is online via the 'asmcmd volinfo' command. If it is, contact Oracle Support Services. If the mount point is already offline, no further action is required.
ACFS-09035: Error unlocking string: Cause: An 'advmutil dismount' command failed because it could not unlock the specified file system. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.
ACFS-09036: Error bringing string online: Cause: An 'advmutil mount' command failed because it could not bring the specified file system online. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.
ACFS-09037: Error reading reparse point string: Cause: An 'advmutil dismount' command failed because it could not read the specified reparse point. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.
ACFS-09093: No volume managers are running on this system.: Cause: No volume managers (ADVM, or EDV on Exascale) were running.; Action: Start the Oracle stack.
ACFS-09100: Creating volume 'string' in diskgroup 'string'.: Cause: Informational; Action: None
ACFS-09101: Failed to create volume 'string' in diskgroup 'string'.: Cause: The volume was unable to be created in the diskgroup. Possible Causes: 1) ASM is not running. 2) User is not part of the ASMADMIN group. 3) An ASM specific error occurred.; Action: 1) Verify that ASM is running ('srvctl status asm') 2) Verify that the user is part of the ASMADMIN group. 3) Check the ASM logs and output for an ASM specific error.
ACFS-09102: Unable to verify creation of ACFS Oracle database Home.: Cause: A command was given to ASM to create the specified volume and no errors were detected. However, post creation checks failed to find that the volume that was created and/or enabled.; Action: Run sqlplus (or asmcmd) to manually create the volume.
ACFS-09103: Enabling volume 'string' on diskgroup 'string'.: Cause: Informational; Action: None
ACFS-09104: Enable of volume 'string' failed.: Cause: ASM was instructed to enable the specified volume and failed.; Action: Attempt a manual enable via sqlplus or asmcmd.
ACFS-09105: Volume 'string' not found in 'string'.: Cause: The specified volume does not exist.; Action: Create volume via sqlplus or asmcmd.
ACFS-09106: Diskgroup 'string' not found.: Cause: The specified diskgroup does not exist.; Action: Create diskgroup via sqlplus or asmcmd.
ACFS-09107: ASM mounting diskgroup 'string'.: Cause: Informational; Action: None
ACFS-09108: ASM mount of diskgroup 'string' failed.: Cause: ASM found the specified diskgroup but could not mount it.; Action: Try mounting the diskgroup manually via sqlplus. If the mount fails, check ASM logs for errors related to the diskgroup, clear errors, and try again.
ACFS-09109: string driver failed to load.: Cause: The driver failed to load.; Action: View the system specific OS kernel log (for instance, /var/log/messages on Linux, Event Log on Windows). If the drivers have not previously been unloaded ('crsctl stop crs', 'acfsload stop', 'acfsroot uninstall'), it is not possible to reload them. If a specific error has occurred, than clear the error condition and try again. If the OS and\or architecture is not supported by the drivers, than contact Oracle Support Services for an updated driver package.
ACFS-09110: Offline mount point 'string' was dismounted for recovery.: Cause: Informational. The mount point referenced was fenced due to an underlying volume failure. In this case, the mount point was successfully dismounted for recovery.; Action: None
ACFS-09111: Offline mount point 'string' was recovered.: Cause: Informational - the mount point referenced was fenced due to an underlying volume failure. In this case, the mount point was successfully remounted, which has renabled IO to the file system.; Action: None
ACFS-09112: The following process IDs have open references on mount point 'string':: Cause: During shutdown of the CRS stack, it was determined that a process had files open on the mount point in the process of being dismounted. This prevents the dismount from succeeding.; Action: Terminate any process\applications that are using files on the mount point that is being dismounted before stopping the CRS stack.
ACFS-09113: These processes will now be terminated.: Cause: Informational; Action: None
ACFS-09114: completed: Cause: Informational; Action: None
ACFS-09115: The command 'string' returned an unexpected value.: Cause: This is an internal error.; Action: An internal error occurred during the installation process. Restart the installation process.
ACFS-09116: Offline mount point 'string' was not recovered.: Cause: An inaccessible mount point could not be restored to working condition.; Action: Manual intervention is required to clear the offline mount point. Dismount the mount point and remount it manually to restore access to the mount point.
ACFS-09117: Manual intervention is required.: Cause: Informational, from previous errors.; Action: Clear previous errors and retry.
ACFS-09118: Driver string in use - cannot unload.: Cause: This may be seen during 'crsctl stop crs', 'acfsload stop', or 'acfsroot uninstall'. Applications (possibly ASM) have open references on the driver.; Action: Terminate applications, including ASM, that may be using the driver and retry.
ACFS-09119: Driver string failed to unload.: Cause: An unknown error has occurred when trying to unload the driver.; Action: Check system specific logs (/var/log/messages on Linux, Event Log on Windows) and clear any error conditions that are preventing the unload.
ACFS-09120: The 'string' machine architecture not supported.: Cause: ADVM/ACFS device drivers have not yet been ported to this CPU type or OS. This occurs when the customer manually tries to load the drivers on an architecture or system OS type that ACFS is not supported, such as VMS.; Action: Contact Oracle Support Services to determine if an updated driver is available for this OS and architecture, or install ACFS on a supported architecture and OS.
ACFS-09121: Failed to detect control device 'string'.: Cause: ADVM/ACFS device drivers have been started but the devices that should have been created have not been.; Action: Try 'acfsload stop' followed by 'acfsload start' or restarting the crs stack - 'crsctl stop crs', 'crsctl start crs'. If the control devices still do not exist, contact Oracle Support Services.
ACFS-09122: ADVM device not determined from mount point 'string'.: Cause: This is an internal error.; Action: Contact Oracle Support Services.
ACFS-09123: 'string' command not found.: Cause: A required component of ACFS is missing. This could be an incomplete install, removal of files from the system after install, or an unknown cause.; Action: Re-install by running 'acfsroot install'. If that does not work, than contact Oracle Support Services. In the event that handle.exe // is not found, than please install handle from sysinternals.com or another site, and make sure that the PATH environment variable contains the install location. Retry the operation.
ACFS-09124: string driver failed to detach from the system driver stack.: Cause: The ACFS driver is being used by one or more mounted file systems.; Action: Unmount all ACFS file systems and retry the operation.
ACFS-09125: ADVM/ACFS is not supported on this OS: 'string': Cause: ADVM/ACFS device drivers have not been ported to this OS.; Action: None
ACFS-09126: Attempting to terminate the program 'string' with OS process ID 'string'.: Cause: The process was using an ACFS file system, which was being forcibly unmounted. A kill signal was sent to allow the unmount to proceed.; Action: This message is informational.
ACFS-09127: Not all ADVM/ACFS drivers have been loaded.: Cause: ADVM/ACFS device drivers have been started but not all of them are detected as running.; Action: Try 'acfsload stop' followed by 'acfsload start'. If that does not start all drivers, than contact Oracle Support Services.
ACFS-09128: unknown query type 'string': Cause: This is an internal error.; Action: Contact Oracle Support Services.
ACFS-09129: ADVM/ACFS not installed: Cause: No ADVM/ACFS drivers or commands have been found on the system. All ADVM and ACFS actions will be disabled.; Action: Install components using 'acfsroot install options'. No ACFS file systems or ADVM volume devices will be available until ADVM/ACFS has been installed.
ACFS-09130: Root access required: Cause: The user this command is executing as does not have sufficient privileges to run this command.; Action: Run this command as a user with administrative privileges.
ACFS-09135: string installation aborted.: Cause: Informational; Action: See preceding error message for more information.
ACFS-09136: PID string could not be killed.: Cause: Failed to kill a Process ID during a force unmount of a file system.; Action: Manually kill the process and retry the unmount.
ACFS-09137: Failed to set group on directory 'string'.: Cause: The group of the directory could not be changed.; Action: Make sure the user has permission to do so.
ACFS-09138: command 'string' completed with an error: string: Cause: 'acfsutil' did not successfully run.; Action: Correct the problem described in the accompanying error message from 'acfsutil'. If this error was returned within the context of a CRS resource execution, retry the CRS action after the problem is resolved.
ACFS-09139: Attempting recovery of offline mount point 'string': Cause: An ACFS mount point reported by the 'acfsutil' command was not accessible.; Action: This message is informational. CRS will attempt to recover the mount point.
ACFS-09140: Unable to determine the correct drivers for this version of Windows: ID:string Major:string Minor:string Product Type:string: Cause: Error. ACFS is not supported on this Windows Version.; Action: Report this message to Oracle Support Services to determine if an update to ACFS is available.
ACFS-09149: unable to determine device mount status - unsupported OS name 'string': Cause: The standard method to determine mount state of a device was unavailable. It is possible that ADVM/ACFS is not supported on the OS.; Action: Report the value of OS to Oracle Support Services.
ACFS-09150: Unexpected output from 'acfsutil info fs': 'string'.: Cause: Informational; Action: None
ACFS-09151: Ignoring request to mount due to existence of "oracle_nomounts" file: string: Cause: "An "oracle_nomounts" file was present, causing file system mount processing to be skipped during a CRS resource operation."; Action: Normal mount operations can be resumed by removing the "oracle_nomounts" file.
ACFS-09152: Program 'string' with OS process ID 'string' will not be terminated.: Cause: The process is using an ACFS file system which is being forcibly unmounted but it will not be terminated because it is a system critical process.; Action: Manual intervention may be required.
ACFS-09153: Program 'string' with OS process ID 'string' is using mount point 'string'.: Cause: The process is using the mount point.; Action: None - Informational.
ACFS-09154: Loading 'string' driver.: Cause: Informational.; Action: None
ACFS-09155: Checking for existing 'string' driver installation.: Cause: Informational.; Action: None
ACFS-09156: Detecting control device 'string'.: Cause: Informational.; Action: None
ACFS-09157: Detecting driver 'string'.: Cause: Informational.; Action: None
ACFS-09158: Configuration file 'string' in the /boot directory does not exist.: Cause: A populated /boot directory, which contains static files required to install kernel modules, was not detected on the system.; Action: After restoring the /boot directory and the kernel configuration files, re-run "acfsroot install".
ACFS-09160: Can not use the silent and verbose options at the same time.: Cause: The -s and -v options were used in the command. These options are mutually exclusive.; Action: Re-execute the command with one of the options or neither.
ACFS-09161: acfsroot install: Install ADVM/ACFS components.: Cause: Informational.; Action: None
ACFS-09162: acfsroot uninstall: Uninstall ADVM/ACFS components.: Cause: Informational.; Action: None
ACFS-09163: acfsroot version_check: Check ADVM/ACFS version.: Cause: Informational.; Action: None
ACFS-09164: acfsroot enable: Enable ADVM/ACFS CRS resources.: Cause: Informational.; Action: None
ACFS-09165: acfsroot disable: Disable ADVM/ACFS CRS resources.: Cause: Informational.; Action: None
ACFS-09166: string [-h] [-s | -v]: Cause: Syntax error or help [-h] option was passed.; Action: Use syntax as specified in the 'Usage' message.
ACFS-09167: ADVM/ACFS is not installed or loaded. Run 'acfsroot install'.: Cause: An operation was requested that requires ADVM/ACFS to be running.; Action: Run 'acfsroot install' and then run the requested operation.
ACFS-09168: The CRS query "string" cannot be parsed.: Cause: This is an internal error.; Action: Contact Oracle Support Services.
ACFS-09169: The CRS attribute value specification "string" is invalid.: Cause: This is an internal error.; Action: Contact Oracle Support Services.
ACFS-09170: The file system's CRS resource name "string" is invalid.: Cause: This is an internal error.; Action: Contact Oracle Support Services.
ACFS-09171: The CRS resource for the file system on device string cannot be retrieved: Cause: Informational; Action: Analyze the error messages that precede this message.
ACFS-09172: The CRS resource for the file system on device string cannot be registered: Cause: Informational; Action: Analyze the error messages that precede this message.
ACFS-09173: The srvctl command line "string" failed to execute. (number): Cause: This is an internal error.; Action: Contact Oracle Support Services.
ACFS-09174: unable to communicate with CRS: Cause: The application failed to communicate with CRS.; Action: Verify that CRS is running. Check the CRS logs to determine why the CRS resource is not responding.
ACFS-09175: Invalid trace level. Valid values for trace level are 0, 1 or 2.: Cause: An invalid trace level was provided.; Action: Use a supported trace level: 0, 1, or 2.
ACFS-09176: Entering 'string': Cause: Informational.; Action: None
ACFS-09177: Return from 'string': Cause: Informational.; Action: None
ACFS-09178: Return code = string: Cause: Informational.; Action: None
ACFS-09179: Command executed: 'string', output = 'string': Cause: Informational.; Action: None
ACFS-09180: Sub-command is 'string': Cause: Informational.; Action: None
ACFS-09181: Kernel version is 'string': Cause: Informational.; Action: None
ACFS-09182: Variable 'string' has value 'string': Cause: Informational.; Action: None
ACFS-09183: Query = 'string': Cause: Informational.; Action: None
ACFS-09184: string [-h] [-s | -v | -t <0,1,2>]: Cause: Either a syntax error or unknown option was specified, or the help (-h) option was specified.; Action: Use syntax as specified in the 'Usage' message.
ACFS-09185: string [-h] [-s | -v | -t <0,1,2>] [-l directory]: Cause: Either a syntax error or unknown option was specified, or the help (-h) option was specified.; Action: Use syntax as specified in the 'Usage' message.
ACFS-09186: Usage: acfsroot uninstall [-h] [-s | -v | -t <0,1,2>]: Cause: Either a syntax error or unknown option was specified, or the help (-h) option was specified.; Action: Use syntax as specified in the 'Usage' message.
ACFS-09187: Usage: acfsroot version_check [-h] [-t <0,1,2>] [-l location]: Cause: Either a syntax error or unknown option was specified, or the help (-h) option was specified.; Action: Use syntax as specified in the 'Usage' message.
ACFS-09188: cannot use the trace option with the silent or verbose options: Cause: Conflicting options were specified.; Action: Specify only one of -s, -v, and -t.
ACFS-09189: [-t <0,1,2> ] - trace level: Cause: Either a syntax error or unknown option was specified, or the help (-h) option was specified.; Action: Use syntax as specified in the 'Usage' message.
ACFS-09190: User group 'string' does not exist.: Cause: The group name is required to create ADVM/ACFS devices with the correct attributes. The group name could not be found in the /etc/group file nor in the various remote services like LDAP, AD, NIS/Yellow Pages, DNS, etc.; Action: Ensure that the required group exists, then re-run the command.
ACFS-09191: Usage: acfsroot version_check [-h] [-t <0,1,2>]: Cause: Either a syntax error or unknown option was specified, or the help (-h) option was specified.; Action: Use syntax as specified in the 'Usage' message.
ACFS-09192: unknown installation mode: string: Cause: An attempt to execute the 'acfsroot install' command failed because an unknown mode was specified.; Action: Consult the documentation and reissue the command specifying a supported installation mode.
ACFS-09193: Use of the -m flag is not supported in this OS.: Cause: An attempt was made to install ACFS with the -m flag in an operating system that did not support Oracle Database Appliance modes.; Action: Installation of ACFS cannot proceed with the -m flag in the current operating system. Reissue the command without the -m flag.
ACFS-09194: unable to query the WMI service to identify the Windows OS Version: Cause: A requested management operation failed because an attempt to obtain the current Windows OS version from the Windows Managment Instrumentation (WMI) Service in order to determine whether ACFS/ADVM drivers were supported was not successful.; Action: Use the Windows Task Manager to verify the status of the WMI service (winmgmt). After the WMI service is verified to be enabled and running, retry the command.
ACFS-09195: Unable to access the specified Cluster Manifest File: string: Cause: An attempt to access the specified Cluster Manifest File failed.; Action: Verify that the specified Cluster Manifest File exists and is accessible by root. If necessary, run 'crsctl create member_cluster_configuration' in a Domain Services Cluster. Once the Cluster Manifest File has been verified to exist, retry the installation.
ACFS-09196: Exit code = string: Cause: Informational.; Action: None
ACFS-09197: string RPM package was not found in directory 'string'.: Cause: The RPM package was not found in the specified path.; Action: Contact Oracle Support Services.
ACFS-09198: File 'string' has an invalid size: 'string'.: Cause: The size of the specified file was invalid.; Action: Contact Oracle Support Services.
ACFS-09200: Supported: Cause: ADVM/ACFS device drivers have been ported to this OS or CPU type.; Action: None - Informational.
ACFS-09201: Not Supported: Cause: ADVM/ACFS device drivers have not yet been ported to this OS or CPU type.; Action: None
ACFS-09202: RPM query failed: string,exit code: string: Cause: RPM database was throwing an error.; Action: Perform action based on the error returned.
ACFS-09203: true: Cause: ADVM/ACFS device drivers were installed/loaded.; Action: None
ACFS-09204: false: Cause: ADVM/ACFS device drivers were not installed/loaded.; Action: None
ACFS-09205: usage: string [-h] [-orahome <home_path>] {installed | loaded | version | supported | validate} [-s]: Cause: Syntax error or help [-h] option was passed.; Action: Use syntax as specified in the 'Usage' message.
ACFS-09206: usage: string [-orahome <ORACLE_HOME>] {installed | loaded | version | supported} [-s]: Cause: Syntax error.; Action: Use syntax as specified in the 'Usage' message.
ACFS-09207: The user this command is executing as does not have permission to execute Perl in 'string'.: Cause: Perl permissions are read/write/execute owner (0700). The user this command is executing as is not the owner of the perl binary.; Action: Enter the db home as an argument to -orahome. Ensure that the user executing the command has execute permission on the perl binary in that db home.
ACFS-09208: Enter the location of the db home for this database to '-orahome'.: Cause: Perl permissions are read/write/execute owner (0700). The user this command is executing as is not the owner of the perl binary.; Action: Enter the db home as an argument to -orahome. Ensure that the user executing the command has execute permission on the perl binary in that db home.
ACFS-09210: The ADVM/ACFS drivers are supported but have not been verified on this Operating System version.: Cause: The drivers have not been explicitly tested on this operating system version but are expected to work properly.; Action: This message is informational.
ACFS-09211: usage: string [-h] [-orahome <home_path>] {installed | loaded | version [-v]| supported [-v]} [-s]: Cause: Syntax error or help [-h] option was passed.; Action: Use syntax as specified in the 'Usage' message.
ACFS-09213: Configuration file 'string' in the /boot directory does not exist or cannot be read.: Cause: An attempt to check for compatible kernel was unable to read required /boot configuration data.; Action: Verify user permissions, that the configuration file is accessible, and then retry the command.
ACFS-09215: System console log level set to: string.: Cause: System console log level has been set to specified value.; Action: None - Informational.
ACFS-09216: System console log level set back to: string.: Cause: System console log level has been set back to a previous known value.; Action: None - Informational.
ACFS-09217: Current system console log level is: string.: Cause: Informational.; Action: None
ACFS-09218: Failed to set system console log level.: Cause: Failed to set system console log level to a known value.; Action: Contact system administrator.
ACFS-09219: No write access to trace directory 'string'.: Cause: The user did not have write access to the indicated directory. This did not affect command completion but no trace file was created.; Action: As a privileged user, set the group of the indicated directory to that of the ASM/database administrator and set group write access.
ACFS-09220: Partially Installed: Cause: ADVM/ACFS device drivers are partially installed/loaded.; Action: None
ACFS-09221: Unable to find kernel rpm 'string': Cause: The kernel rpm path name or the installed kernel rpm name was incorrect or the kernel rpm name did not exist in rpmdb.; Action: If providing a kernel rpm file path, verify the file path exists, has read permissions, and that the rpm provides kABI symbols. See command help for more information.
ACFS-09222: Unable to find Kernel 'string' in rpmdb: Cause: The specified kernel rpm name was not installed.; Action: Install the specified kernel rpm version, or reissue the command with the path to the kernel rpm file as an argument.
ACFS-09225: Failed to start OKS persistent logging.: Cause: The drivers were successfully loaded but Oracle Kernel Services (OKS) persistent logging failed to start.; Action: run "acfsutil plogconfig -d GridHome" to perform a manual start.
ACFS-09226: ADVM/ACFS drivers not correct for this OS - cannot load.: Cause: The device drivers installed are not compatible with the currently running operating system; Action: run "acfsroot install options" to install the correct drivers.
ACFS-09229: precheck:: Cause: One or more ACFS drivers (oracleoks, oracleadvm, or oracleacfs) was in use and could not unload. The operation ("acfsroot uninstall" or "acfsload stop") returned without making any system modifications. Driver use information follows.; Action: Determine the reason a driver was in use (example: a mounted ACFS file system) and retry the operation after correcting the problem.
ACFS-09230: unload:: Cause: One or more ACFS drivers (oracleoks, oracleadvm, or oracleacfs) was in use. The operation ("acfsroot uninstall" or "acfsload stop") did not complete. One or more drivers may have been unloaded. This error occurs after the system verified that the drivers were in the correct state to be unloaded. This means that another process referenced a driver after the verification but before the actual unload was attempted. Driver use information follows.; Action: Determine the reason a driver could not be unloaded. Retry the operation after correcting the problem.
ACFS-09250: Unable to get the ASM administrator user name from the ASM process.: Cause: ASM processes have not been found running on this system. This will prevent the requested action from being completed.; Action: Start ASM ('srvctl start asm') and retry the operation.
ACFS-09251: Mount point 'string' unmounted.: Cause: Informational.; Action: None
ACFS-09252: The following process IDs have open references on mount point 'string':: Cause: Informational.; Action: None
ACFS-09253: Failed to unmount mount point 'string'. Mount point likely in use.: Cause: Other processes have outstanding open references on the mount point.; Action: Terminate applications using files on the mountpoint than retry the // operation (' crsctl stop crs' ).
ACFS-09254: Manual intervention is required.: Cause: Follow up message to ACFS-9253.; Action: None - Informational.
ACFS-09255: Creating 'string' mount point.: Cause: Informational.; Action: None
ACFS-09256: Failed to create mountpoint 'string'.: Cause: The mount point may already exist, the user executing the command may have insufficient permission, or a system specific error may have occurred.; Action: Choose another mount point, execute the action from an account with the required permissions, or resolve the specified error shown before this message.
ACFS-09257: Mounting device 'string' on mount point 'string'.: Cause: Informational.; Action: None
ACFS-09258: Failed to mount device 'string' on mount point 'string'.: Cause: The mount point may be in use, the user executing this command may have insufficient permissions, or another system specific error may have occurred.; Action: Make sure that the mount point is available, ensure the user executing the command has the correct permissions, or resolve any system error shown before this message.
ACFS-09259: Mount point 'string' already has a device mounted on it.: Cause: There is already a device mounted on this mount point.; Action: If the new device is meant to replace the old device on this mount point, unmount the old one first and retry the operation. Otherwise this error may be ignored.
ACFS-09260: Failed to connect to the ASM instance.: Cause: ASM connection attempt failed.; Action: Ensure that the ORACLE_SID environment variable is correctly set to // the value of the ASM instance. In addition, verify that ASM is running ('srvctl status asm').
ACFS-09261: Invalid _ORA_NAME format.: Cause: This is an internal error.; Action: Report this to Oracle Support Services.
ACFS-09262: Invalid sub-command 'string'.: Cause: This is an internal error or the user attempted to run the script manually with an incorrect sub-command.; Action: Contact Oracle Support Services or use a correct sub-command.
ACFS-09263: Valid sub-commands are 'start', 'stop', 'check', and 'clean'.: Cause: This results in an incorrect usage of the command.; Action: Run the command with an option (command) that is supported, such as 'start', 'stop', 'check', or 'clean'.
ACFS-09264: Mount point 'string' is not mounted.: Cause: Informational.; Action: None
ACFS-09274: Resource 'string' is not online.: Cause: Informational.; Action: None
ACFS-09275: The clean failed to unmount the required mountpoint(s) - re-trying.: Cause: Informational. A file system could not be unmounted. This could be due to new process being started just before the unmount.; Action: None
ACFS-09289: string not set in environment.: Cause: The referenced environment variable was not set. This makes it impossible to continue with the requested action.; Action: Ensure that the referenced variable is set and retry the operation.
ACFS-09290: Waiting for ASM to shutdown.: Cause: The resource cannot be terminated while ASM is running.; Action: Wait for ASM to stop. Stop it manually if that does not happen.
ACFS-09291: Waiting for the Windows 'sc stop string' command to complete.: Cause: Informational. System activity is preventing the driver from stopping.; Action: If the driver does not unload, a node reboot may be necessary
ACFS-09292: Warning: A newer version of ACFS software is available in Oracle home string.: Cause: A version check prompted by user request or a maintenance operation determined that updated software is available in the indicated Oracle home.; Action: To ensure the benefits of the latest fixes and performance improvements, the available drivers should be installed at the next maintenance opportunity. Use the command 'rootcrs.pl -updatedriver' to update all drivers on the system.
ACFS-09293: Kernel and command versions do not match.: Cause: A requested version check or a system monitor has found that the installed tools are out of sync with the installed kernel modules. This may cause interoperability issues.; Action: To ensure the benefits of the latest fixes and performance improvements, and to remove potential interoperability issues, the installed software should be updated as soon as possible. Use the command 'rootcrs.pl -updatedriver' to update all driver software on the system, or use 'acfsroot install' to update just ACFS.
ACFS-09295: failed to open file string: Cause: A requested action failed to complete because the indicated file could not be opened.; Action: Verify the file exists and is accessible by the current user, examine previous error messages, address issues, and retry the command.
ACFS-09296: New drivers have been detected for the kernel update, updating drivers from string to string.: Cause: The kernel was updated, triggering a driver update.; Action: None
ACFS-09300: ADVM/ACFS distribution files found.: Cause: Informational.; Action: None
ACFS-09301: ADVM/ACFS installation cannot proceed:: Cause: Previous errors have caused the installation to reach a point where it cannot continue.; Action: Fix previous errors.
ACFS-09303: No installation files found for OS kernel version string.: Cause: If '-l' (distribution directory) was specified, the directory may not be valid.; Action: Choose a proper distribution location version.
ACFS-09304: Installation cannot proceed: Failed to unload ADVM/ACFS drivers.: Cause: Applications (possibly ASM) have open references on the drivers.; Action: Terminate applications and ASM that may be using the drivers, and retry the installation.
ACFS-09305: ADVM/ACFS installation cannot proceed:: Cause: Informational.; Action: Clear previous error and retry.
ACFS-09306: Failed to uninstall previous installation.: Cause: Could not remove ADVM/ACFS commands and or drivers.; Action: Commands and/or drivers are likely in use. Wait for operations to finish, unload the drivers, and retry the installation.
ACFS-09307: Installing requested ADVM/ACFS software.: Cause: Informational.; Action: None
ACFS-09308: Loading installed ADVM/ACFS drivers.: Cause: Informational.; Action: None
ACFS-09309: ADVM/ACFS installation correctness verified.: Cause: Informational.; Action: None
ACFS-09310: ADVM/ACFS installation failed.: Cause: A previous error caused this installation to fail.; Action: Correct previous error and retry the installation.
ACFS-09311: not all components were detected after the installation.: Cause: ADVM/ACFS commands and drivers were found in the installation area but did not get placed in their assigned locations.; Action: Re-install using 'acfsroot install -l options'. If necessary, contact Oracle Support Services.
ACFS-09312: Existing ADVM/ACFS installation detected.: Cause: Informational.; Action: None
ACFS-09313: No ADVM/ACFS installation detected.: Cause: An attempt was made to un-install ADVM/ACFS components that did not exist on the system.; Action: None - there is no problem.
ACFS-09314: Removing previous ADVM/ACFS installation.: Cause: Informational.; Action: None
ACFS-09315: Previous ADVM/ACFS components successfully removed.: Cause: Informational.; Action: None
ACFS-09316: Valid ADVM/ACFS distribution media detected at: 'string': Cause: Informational.; Action: None
ACFS-09317: No ADVM/ACFS distribution media detected at location: 'string': Cause: If -l (location) is used, the directory specified may be invalid.; Action: Use the correct directory.
ACFS-09318: ORACLE_HOME is not set.: Cause: This is an internal error.; Action: Report this to Oracle Support Services.
ACFS-09319: Unknown OS kernel version 'string' detected.: Cause: This is an internal error.; Action: Contact Oracle Support Services.
ACFS-09320: Missing file: 'string'.: Cause: A required command or driver is not found on the installation media (pre install) or system (post install).; Action: If post install, try running acfsroot again. Otherwise, contact Oracle Support Services.
ACFS-09321: Creating udev for ADVM/ACFS.: Cause: Informational.; Action: None
ACFS-09322: completed: Cause: Informational.; Action: None
ACFS-09323: Creating module dependencies - this may take some time.: Cause: Informational.; Action: None
ACFS-09324: Alternate drivers installed.: Cause: Informational.; Action: None
ACFS-09327: Verifying ADVM/ACFS devices.: Cause: Informational.; Action: None
ACFS-09328: unknown query type 'string'.: Cause: This is an internal error.; Action: Contact Oracle Support Services.
ACFS-09329: Failed to uninstall driver: 'string'.: Cause: Acfsinstall failed to uninstall the driver.; Action: Drivers may be in use. Correct previously reported errors and retry uninstall. If that fails, contact Oracle Support Services.
ACFS-09330: Binary 'string' not installed.: Cause: A component that should have been installed was not installed.; Action: Rerun 'acfsroot install'.
ACFS-09339: The environment variable ORACLE_HOME is not set.: Cause: This is an internal error.; Action: Contact Oracle Support Services.
ACFS-09340: failed to install string driver.: Cause: Acfsinstall failed to install the driver.; Action: Run acfsinstall manually to see reported errors, resolve them, and retry.
ACFS-09341: Binary 'string' not found.: Cause: One of the binaries that make up the ACFS package is missing.; Action: Reinstall the ACFS package and retry the operation.
ACFS-09343: Unable to retrieve OS kernel version from module string.: Cause: Running modinfo against the usm driver failed.; Action: None - the current OS kernel version will be used instead.
ACFS-09344: Missing directory: 'string'.: Cause: A required directory is not found on the system.; Action: Contact Oracle Support Services.
ACFS-09345: Unable to create directory: 'string'.: Cause: Creation of a required directory failed.; Action: Contact Oracle Support Services.
ACFS-09346: Unable to install file: 'string'.: Cause: Copying to the given destination failed.; Action: Rerun acfsroot after correcting the OS error.
ACFS-09347: Unable to set permission bits (string) on: 'string'.: Cause: Setting the given permission bits failed.; Action: Manually set the permissions to the required level.
ACFS-09348: Unable to remove 'string'.: Cause: A previously installed file was unable to be removed.; Action: Attempt to manually remove the file.
ACFS-09349: Unable to configure driver 'string'.: Cause: A driver was installed but add_drv failed to write a configuration file.; Action: Correct the OS error and re-run acfsroot install.
ACFS-09350: Failed to create a symbolic link from 'string' to 'string'.: Cause: Creating a symbolic link failed.; Action: Rerun acfsroot after correcting the OS error.
ACFS-09351: Unable to remove devlink entry for 'string'.: Cause: An entry for the driver was found in /etc/devlink.tab but it was not possible to remove the entry.; Action: Manually remove the entry from /etc/devlink.tab and re-run acfsroot uninstall
ACFS-09352: Unable to write to 'string'.: Cause: A file required modifications but it was not possible to write to it.; Action: Check the file permissions.
ACFS-09353: Unable to unconfigure string.: Cause: A call to rem_drv failed.; Action: Correct the OS error and re-run acfsroot uninstall.
ACFS-09354: Unable to create symlink: 'string'.: Cause: Ensure that a file with the same name does not already exist and the user has permission.; Action: Remove the existing file and make sure the user has the required permission.
ACFS-09355: Performing AIX setup failed with error code 'string'.: Cause: Running AIX initial setup has failed.; Action: Correct the error and re-run the root install script.
ACFS-09356: Saving the AIX ODM changes for 'string' failed with error code 'string'.: Cause: Running the AIX savebase command failed.; Action: Correct the error and re-run the root install script.
ACFS-09357: Getting the ASMADMIN group failed with error code 'string'.: Cause: Previous installation steps may have failed.; Action: Correct the preceding error and re-run the root install script.
ACFS-09358: Adding the AIX ODM entry for 'string' failed with error code 'string'.: Cause: Running the AIX odmadd command failed.; Action: Correct the error and re-run the root install script.
ACFS-09360: The command aixsetup failed with error code 'string'.: Cause: Running the aixsetup script failed.; Action: Correct the error and re-run the root install script.
ACFS-09361: Removing device 'string' failed with error code 'string'.: Cause: Running the device's undefine method failed.; Action: Correct the error and re-run the root uninstall script.
ACFS-09362: Warning: deleting the AIX ODM entry for 'string' failed with error code 'string'.: Cause: Running the odmdelete command failed.; Action: Manually remove the entry or ignore the message.
ACFS-09363: Opening the file /etc/vfs for read failed.: Cause: The /etc/vfs file is not readable.; Action: Check the permission of the file and ensure it has read permission.
ACFS-09364: Opening the file /etc/vfs for append failed.: Cause: The /etc/vfs file is not writable.; Action: Check the permission of the file and ensure it has write permission.
ACFS-09365: The directory 'string' is not being removed.: Cause: The directory was scheduled to be uninstalled, but it contained files that were not installed by acfsroot.; Action: Manually remove the directory.
ACFS-09366: Relative path for mount point 'string' is not supported.: Cause: Mount point was provided as a relative path.; Action: Specify the mount point in the form of an absolute path.
ACFS-09381: Modification of ADVM/ACFS drivers resource failed.: Cause: An attempt to modify the ACFS drivers resource resulted in an error.; Action: Contact Oracle Support Services.
ACFS-09382: Modification of ADVM/ACFS drivers resource succeeded.: Cause: Informational.; Action: None
ACFS-09383: ADVM/ACFS uninstall cannot proceed: Cause: ADVM/ACFS uninstall cannot proceed due to an error. This message is accompanied by other message(s) providing details on the error.; Action: Correct the problem indicated in the other messages.
ACFS-09384: Invalid OS kernel variation 'string'.: Cause: The command found an OS kernel variation (e.g., "el5", etc) that it did not recognize as a valid ADVM/ACFS supported kernel.; Action: Boot a supported kernel
ACFS-09385: Usage: acfsroot version_check [-h] [-l location]: Cause: Syntax error or help [-h] option was passed.; Action: Use syntax as specified in the 'Usage' message.
ACFS-09388: An absolute path name must be specified for the alternate location.: Cause: A relative path name to the distribution files was specified.; Action: Enter the absolute path name instead.
ACFS-09389: ORACLE_HOME is not set to the location of the Grid Infrastructure home.: Cause: The ORACLE_HOME environment variable was not set correctly.; Action: Make sure that the ORACLE_HOME environment variable is set to the location of the Grid Infrastructure home and that it is properly exported.
ACFS-09390: The command 'string' returned unexpected output that may be important for system configuration:: Cause: One of the operating system commands used to configure the system returned an unexpected error. This message is accompanied by other message(s) providing details of the error.; Action: See the operating system documentation for the specific command for more information on this error.
ACFS-09391: Checking for existing ADVM/ACFS installation.: Cause: Informational.; Action: None
ACFS-09392: Validating ADVM/ACFS installation files for operating system.: Cause: Informational.; Action: None
ACFS-09393: Verifying ASM Administrator setup.: Cause: Informational.; Action: None
ACFS-09394: The installed driver string has a build date of string which does not match the loaded kernel module build date of string.: Cause: The most likely cause is that an upgrade or patch procedure failed to unload the kernel module.; Action: Reboot the system before attempting to use ACFS.
ACFS-09395: Environment variable ODMDIR is not set, unable to proceed with system configuration.: Cause: Environment variable ODMDIR was not set.; Action: Ensure that the ODMDIR environment variable is set to the location of a valid AIX ODM device configuration database.
ACFS-09396: Environment variable ODMDIR specifies a nonexistent path, unable to proceed with system configuration.: Cause: Environment variable ODMDIR specified a nonexistent path.; Action: Ensure that the ODMDIR environment variable is set to the location of a valid AIX ODM device configuration database.
ACFS-09397: Modification of ADVM/ACFS registry resource failed.: Cause: An attempt to modify the ACFS registry resource resulted in an error.; Action: Contact Oracle Support Services.
ACFS-09398: Modification of ADVM/ACFS registry resource succeeded.: Cause: Informational.; Action: None
ACFS-09399: Calling 'acfsroot install' to install compatible ADVM/ACFS drivers.: Cause: Informational.; Action: None
ACFS-09400: Could not open the Service Control Manager.: Cause: You do not have administrator access.; Action: Log onto a user account with administrator privileges and retry.
ACFS-09401: Failed to install the driver.: Cause: The specified driver could not be installed.; Action: Respond based on the accompanying error message.
ACFS-09402: The driver file path is too long.: Cause: The path to the driver exceeded system limits.; Action: Move the driver to a shorter path or create a shorter link.
ACFS-09403: The driver can be either installed or removed, not both.: Cause: The /i and the /u switches are mutually exclusive.; Action: Use either /i to install or /u to uninstall the driver.
ACFS-09404: Specify either /i (install) or /u (uninstall).: Cause: Either /i to install or /u to uninstall the driver is required.; Action: The /i or the /u switch must be specified.
ACFS-09405: Only one driver can be installed at a time.: Cause: Multiple drivers were specified with the /i option.; Action: Enter only one driver on the command line.
ACFS-09406: Specify either /a (ADVM) or /o (ACFS) or /l (OKS).: Cause: The driver to be installed or uninstalled was not specified.; Action: Enter the driver option on the command line.
ACFS-09407: Could not find driver "string" in the current directory.: Cause: The driver could not be found in the directory specified.; Action: Verify and enter the correct driver path name.
ACFS-09408: The current directory is %"s".: Cause: Informational.; Action: None
ACFS-09409: CreateService failed (ERROR_SERVICE_EXISTS).: Cause: The driver service already exists.; Action: None. The service is active.
ACFS-09410: CreateService failed.: Cause: The driver service could not be created.; Action: Correct the problem indicated by the accompanying error message and retry the operation.
ACFS-09411: CreateService succeeded.: Cause: Informational.; Action: None
ACFS-09412: The driver was installed successfully.: Cause: Informational.; Action: None
ACFS-09413: RegCreateKeyEx failed.: Cause: Failed to create a Windows registry key.; Action: Correct the problem indicated by the accompanying error message and retry the operation.
ACFS-09414: RegSetValueEx (TypesSupported) failed.: Cause: Failed to set the Windows registry key.; Action: Correct the problem indicated by the accompanying error message and retry the operation.
ACFS-09415: RegSetValueEx (EventMessageFile) failed.: Cause: Failed to set the Windows registry key.; Action: Correct the problem indicated by the accompanying error message and retry the operation.
ACFS-09416: OpenService failed.: Cause: Could not start the driver.; Action: Correct the problem indicated by the accompanying error message and retry the operation.
ACFS-09417: The driver was started successfully.: Cause: Informational.; Action: None
ACFS-09418: StartService failed (SERVICE_ALREADY_RUNNING).: Cause: Informational.; Action: None. The driver is already running.
ACFS-09419: StartService failed.: Cause: The driver failed to start.; Action: Correct the problem indicated by the accompanying error message and retry the operation.
ACFS-09420: The driver is not currently installed on this node.: Cause: The driver is not installed to start.; Action: Install the driver using the '/i' option.
ACFS-09421: The driver is already installed on this node.: Cause: An attempt was made to install a driver that is already installed.; Action: None
ACFS-09422: The driver was removed successfully.: Cause: Informational.; Action: None
ACFS-09423: Failure trying to remove the driver, DeleteService failed.\n The driver service is pending deletion or is in an invalid state.: Cause: The driver could not be removed.; Action: Make sure that all references to the driver have been removed and, if the driver is "oracleacfs.sys", that "acfsutil detach" has been run. Verify that the driver is in the STOPPED state and then retry the operation. If the driver removal still fails, you probably need to reboot the node."
ACFS-09424: The driver was stopped successfully.: Cause: Informational.; Action: None
ACFS-09425: The driver could not be stopped: StopService failed.: Cause: The driver could not be stopped.; Action: Correct the problem indicated by the accompanying error message and retry the operation.
ACFS-09426: Unable to set the file attributes for file string.: Cause: The file attributes for the oject file could not be set.; Action: Reset the attributes with "attrib -r <file_name>" and then retry the operation.
ACFS-09427: Failed to unload ADVM/ACFS drivers. A system reboot is recommended.: Cause: An attempt to unload the ADVM/ACFS drivers was unsuccessful due to an unanticipated condition or configuration. The operating system state did not allow the driver to be unloaded successfully.; Action: Reboot the system to reestablish the operating system environment.
ACFS-09428: Failed to load ADVM/ACFS drivers. A system reboot is recommended.: Cause: An attempt to unload the ADVM/ACFS drivers was unsuccessful due to an unanticipated condition or configuration. The operating system state did not allow the driver to be unloaded successfully.; Action: Reboot the system to reestablish the operating system environment.
ACFS-09429: Failed to install ADVM/ACFS files.: Cause: An unexpected condition has been detected. The files were previously verified to exist.; Action: Check the file permissions. Contact Oracle Support if the problem cannot be resolved.
ACFS-09430: ADVM/ACFS is not supported on this OS configuration: 'string': Cause: Attempting to install or configure ADVM/ACFS failed because ADVM/ACFS device drivers have not been ported to this OS configuration.; Action: For supported configurations, refer to MOS note (Doc ID 1369107.1): ACFS Support On OS Platforms (Certification Matrix).
ACFS-09441: /i Install the driver: Cause: Syntax error.; Action: Use syntax as specified in the 'Usage' message.
ACFS-09442: /u Uninstall the driver: Cause: Syntax error.; Action: Use syntax as specified in the 'Usage' message.
ACFS-09443: /a Perform the operation for the ADVM driver: Cause: Syntax error.; Action: Use syntax as specified in the 'Usage' message.
ACFS-09444: /o Perform the operation for the ACFS driver: Cause: Syntax error.; Action: Use syntax as specified in the 'Usage' message.
ACFS-09445: /l Perform the operation for the Oracle Kernel Services (OKS) driver: Cause: Syntax error.; Action: Use syntax as specified in the 'Usage' message.
ACFS-09446: path Path to the driver. If not specified,\n defaults to oracleadvm.sys, oracleacfs.sys, or\n oracleoks.sys in the current directory\n: Cause: Syntax error.; Action: Use syntax as specified in the 'Usage' message.
ACFS-09450: Examples:: Cause: Informational.; Action: None
ACFS-09451: string /i /a (Install the ADVM driver from the current directory): Cause: Informational.; Action: None
ACFS-09452: string /u /o (Uninstall the ACFS driver): Cause: Informational.; Action: None
ACFS-09453: string /i /o c:\drivers\oracleacfs.sys (Install ACFS with the specified file): Cause: Informational.; Action: None
ACFS-09454: Unable to delete the driver file string after stopping driver.: Cause: A call to the Windows DeleteFile function to delete the driver file failed.; Action: Manually delete the specified driver file using Windows Explorer. If you were installing the driver please retry after deletion.
ACFS-09455: Unable to copy driver file string to the path string.: Cause: Could not copy the driver file to the specified directory because the Windows CopyFile function failed.; Action: Manually delete any previous driver file from the specified directory using Windows Explorer and retry the install.
ACFS-09456: An attempt to stop the driver string failed.: Cause: The driver could not be properly stopped; it is in an invalid state.; Action: Reboot system.
ACFS-09457: The driver file does not match the driver chosen to install.: Cause: The driver file is not consistent with the driver option used.; Action: Specify a path to oracleoks.sys when using the /l option. path to oracleacfs.sys with the /o option and path to oracleadvm.sys with the /a option.
ACFS-09458: The Windows 'string' service is in an invalid state. The new driver cannot be installed.: Cause: An attempt to install the new driver failed because the existing service could not be stopped properly.; Action: Reboot system and then retry the install.
ACFS-09459: ADVM/ACFS is not supported on this OS version: 'string': Cause: Attempting to install or configure ADVM/ACFS failed because ADVM/ACFS device drivers have not been ported to this OS version.; Action: For supported versions, refer to MOS note (Doc ID 1369107.1) ACFS Support On OS Platforms (Certification Matrix).
ACFS-09460: Missing symbols: 'string': Cause: Informational.; Action: None
ACFS-09461: ACFS is not supported on secure boot enabled OS.: Cause: Attempting to install or configure ADVM/ACFS failed because this hardware and software combination is not supported.; Action: For supported versions, refer to MOS note (Doc ID 1369107.1) ACFS Support On OS Platforms (Certification Matrix).
ACFS-09462: The string RPM is not compatible with kernel string.: Cause: The RPM package with kernel modules requires kernel symbols not provided by the running kernel.; Action: For supported versions, refer to MOS note (Doc ID 1369107.1) ACFS Support On OS Platforms (Certification Matrix). If the listed patches are installed, contact Oracle Support Services.
ACFS-09463: The string RPM is compatible with kernel string.: Cause: The running kernel provides all the symbols required to install the RPM package.; Action: Informative message. No actions are needed.
ACFS-09464: Symbol string.: Cause: Informational message for symbols dump.; Action: Informational message. No actions are needed.
ACFS-09465: Kernel: 'string', RPM: 'string': Cause: Informational message for symbols dump.; Action: Informational message. No actions are needed.
ACFS-09466: *********************** SYMBOLS SUMMARY ***********************: Cause: Informational header for symbols dump.; Action: Informational message. No actions are needed.
ACFS-09500: Location of Oracle Home is 'string' as determined from the internal configuration data: Cause: Informational.; Action: None
ACFS-09501: Location of Oracle Home is 'string' as determined from the ORACLE_HOME environment variable: Cause: Informational.; Action: None
ACFS-09502: Location of Oracle Home is 'string' as determined from the location of the Oracle library files: Cause: Informational.; Action: None
ACFS-09503: ADVM and ACFS driver media location is 'string': Cause: Informational.; Action: None
ACFS-09504: Copying file 'string' to the path 'string': Cause: Informational.; Action: None
ACFS-09505: Using acfsutil executable from location: 'string': Cause: Informational.; Action: None
ACFS-09506: The files 'string' and 'string' are the same, not copying.: Cause: Informational. The file was not copied because the target and source point to the same file.; Action: None
ACFS-09507: Searching the alternative location: 'string': Cause: Informational. The installation files were not found in the specified location. A likely path containing that location will be searched.; Action: None
ACFS-09508: ACFS installation aborted (component string).: Cause: Installation was aborted due to an error.; Action: See preceding error message for more information.
ACFS-09509: ORACLE_BASE is not set.: Cause: This is an internal error.; Action: Contact Oracle Support Services.
ACFS-09522: invalid compression operation string: Cause: An attempted compression operation was rejected because the specified command syntax was invalid.; Action: Refer to the command usage displayed with the message and resissue the command with correct syntax.
ACFS-09523: Invalid compression algorithm specified. The only valid choice is 'lzo'.: Cause: An attempted compression operation was rejected because the specification of the compression algorithm was invalid. The only algorithm currently supported is 'lzo'.; Action: Retry the command specifying the compression algorithm 'lzo'.
ACFS-09524: unable to modify volume compression configuration on the local node: Cause: A request to modify the compression configuration of the volume failed. This message is accompanied by other messages providing details on the error.; Action: Examine the accompanying messages, correct the indicated problems and retry. If unable to proceed, contact Oracle Support Services.
ACFS-09525: Only regular files may be compressed.: Cause: An attempted compression operation was rejected because the specified pathname did not specify a regular file.; Action: Retry the command specifying the pathname of a regular file.
ACFS-09526: unable to obtain file compression information: Cause: An attempt to read the compression information for the file failed. This message is accompanied by other messages providing details on the error.; Action: Examine the accompanying messages, correct the indicated problems and retry. If unable to proceed, contact Oracle Support Services.
ACFS-09535: The requested compression configuration operation failed on a remote node.: Cause: An attempt to change the compression configuration for the volume failed on a remote node in the cluster. The probable cause is a lack of necessary OS resources.; Action: Retry the command. If unable to proceed, contact Oracle Support Services.
ACFS-09536: The Oracle ADVM compatibility attribute for the disk group is less than the required version 12.2 for 'acfsutil compress' commands.: Cause: The 'acfsutil compress' command was rejected because the ADVM disk group compatibility had not been upgraded to the indicated version, which is required for that command.; Action: Ensure that your compatible.advm setting is at least 12.2.0.0.0 and then re-issue the command.
ACFS-09539: 'acfsutil compress' commands are not supported on this OS configuration: 'string': Cause: The 'acfsutil compress' command was rejected because the current version of the OS does not support compression.; Action: For supported versions, refer to MOS note (Doc ID 1369107.1) ACFS Support On OS Platforms (Certification Matrix).
ACFS-09542: The command was not attempted because asynchronous compression is very active on file 'string' .: Cause: The 'acfsutil defrag file' command was unable to make progress because the file was busy being modified by the asynchronous compression mechanism.; Action: Wait until the file is no longer being modified by the asynchronous compression mechanism and re-issue the command. Use 'acfsutil compress info' to see if asynchronous compression is active on a compressed file.
ACFS-09544: Invalid files or directories found: 'string': Cause: During verification of the directory from which ACFS installs kernel modules (usm), unexpected files or directories were found.; Action: Remove the invalid files or directories, and then retry the operation.
ACFS-09545: Verification error: kernel module 'string' is incompatible with the installed kernel version 'string'. It is compatible with kernel version 'string'.: Cause: An attempted command failed because of kernel module incompatibility. The version of the indicated kernel module is not compatible with the installed kernel.; Action: Revert any manual modifications to the usm install directories, and then retry the operation. If a problem is still reported, re-install any applied patches or the base software.
ACFS-09546: Incorrect permissions for file 'string'. Expected: (user=string, group=string, mode=string), Found: (user=string, group=string, mode=string): Cause: An attempt to install ACFS drivers failed because the indicated permissions were incorrect on the indicated file.; Action: Correct the permissions as indicated and retry the operation.
ACFS-09550: An error occurred while retrieving the kernel and command versions.: Cause: An attempt to retrieve the ACFS driver version information failed because an error occurred when acfsdriverstate command invoked the command 'acfsutil version -v'.; Action: Execute the command 'acfsutil version -v' on its own, and if it succeeds, retry the command 'acfsdriverstate version -v'.
ACFS-09551: Command file '/sbin/weak-modules' does not exist or it is not an executable.: Cause: An attempt to check Kernel Application Binary Interface (KABI) compatibility failed because the command '/sbin/weak-modules' could not be found, or the current user did not have permission to execute it. This indicates a problem with the Linux installation.; Action: Resolve the Linux installation problem, ensuring that the command '/sbin/weak-modules' is installed, and that the file has the appropriate permissions, and then retry the operation.
ACFS-09552: Command '/sbin/weak-modules' returned a potential compatibility issue. For more details execute the command 'string'.: Cause: The command '/sbin/weak-modules' found incompatibilities between the running kernel and the ACFS/ADVM drivers.; Action: Run the indicated command for details. Contact Oracle Support Services to determine whether updated ACFS/ADVM drivers are available for the current operating system and architecture.
ACFS-09553: Operating System: string: Cause: Informational.; Action: None
ACFS-09554: Machine Architecture: string: Cause: Informational.; Action: None
ACFS-09555: Operating system name and information: string: Cause: Informational.; Action: None
ACFS-09556: Release package: string: Cause: Informational.; Action: None
ACFS-09557: Version: string: Cause: Informational.; Action: None
ACFS-09558: Variable _ORA_USM_NOT_SUPPORTED is defined: string: Cause: Informational.; Action: None
ACFS-09559: Running in a local container: string: Cause: Informational.; Action: None
ACFS-09560: Configuration file string in the /boot directory is accessible.: Cause: Informational.; Action: None
ACFS-09561: USM Drivers are KABI Compatible.: Cause: Informational.; Action: None
ACFS-09562: Install Path: string: Cause: Informational.; Action: None
ACFS-09563: storage interest tracking: Enabled: Cause: Informational.; Action: None
ACFS-09564: storage interest tracking: Disabled: Cause: Informational.; Action: None
ACFS-09565: storage interest tracking: Enabled: Cause: Informational.; Action: None
ACFS-09566: storage interest tracking: Disabled: Cause: Informational.; Action: None
ACFS-09567: System is not running a compatible version of the Kmod package. A minimum of version of kmod-20-21.el7.x86_64 is required.: Cause: Informational.; Action: None
ACFS-09568: Kmod package version below required minimum of kmod-20-21.el7.x86_64. Current kmod package version: 'string'.: Cause: An attempt to check Kernel Application Binary Interface (KABI) compatibility failed because the system is not running a compatible version of the Kmod package. A minimum of version of kmod-20-21.el7.x86_64 is required to complete this operation.; Action: Update kmod and its associated kmod-libraries packages. Please consult your OS documentation for more information on updating packages on the system.
ACFS-09569: Fast deploy mode enabled.: Cause: Informational.; Action: None
ACFS-09570: Fast deploy mode supported: string: Cause: Informational.; Action: None
ACFS-09571: Uncompress tool used: string: Cause: Informational.; Action: None
ACFS-09572: Drivers were uncompressed.: Cause: Informational.; Action: None
ACFS-09573: Drivers were NOT uncompressed.: Cause: Informational.; Action: None
ACFS-09574: Is an Exadata machine: string: Cause: Informational.; Action: None
ACFS-09575: Exadata domain: string: Cause: Informational.; Action: None
ACFS-09576: Exadata domain: Not defined: Cause: Informational. The domain could not be determined in exadata machine.; Action: None
ACFS-09577: Kabi Method: string: Cause: Informational.; Action: None
ACFS-09578: Directory string has write and read permissions.: Cause: Informational.; Action: None
ACFS-09579: Directory string does NOT have write and read permissions.: Cause: An attempt to verify the path found that the indicated path did not have write and read permissions.; Action: Check and validate that the indicated path has write and read permissions.
ACFS-09580: INFO original driver file string was not deleted.: Cause: Informational.; Action: None
ACFS-09581: ADVM/ACFS drivers are not supported on Solaris Exadata string domain.: Cause: Informational.; Action: None
ACFS-09582: Add/Start resource on other nodes of the cluster if not already done.: Cause: Informational. The operations to add and start a resource are node-local. The resource must be manually started on all nodes in the cluster for correct behavior.; Action: Add/Start resource ('crsctl add/start res') on other nodes of the cluster if not already done.
ACFS-09583: Unable to retrieve OS name from module string.: Cause: An attempt to obtain OS name information about the specified module failed.; Action: Contact Oracle Support Services.
ACFS-09600: Usage: string [-h] {-nfsv4lock} {-volume <enabled_volume_device>} [-force]: Cause: Informational.; Action: None
ACFS-09601: Usage: string [-h] {-nfsv4lock}: Cause: Informational.; Action: None
ACFS-09602: Installation cannot proceed: path 'string' is mounted or it is a symlink.: Cause: An attempt to validate the path found that the indicated path was mounted or was a symlink.; Action: Unmount the file system or remove the symlink.
ACFS-09603: The script will do the following actions:: Cause: Informational.; Action: None
ACFS-09604: - Update the operating system startup procedure so that NFS does not automatically start.: Cause: Informational.; Action: None
ACFS-09605: Management of the NFS daemons will be moved to Oracle Clusterware.: Cause: Informational.; Action: None
ACFS-09606: - Format the volume: string.: Cause: Informational.; Action: None
ACFS-09607: - Create an ACFS resource for the file system.: Cause: Informational.; Action: None
ACFS-09608: - Mount the ACFS file system on 'string'.: Cause: Informational.; Action: None
ACFS-09609: Continue the installation? [1=yes,2=no]:: Cause: Informational.; Action: None
ACFS-09610: Error - the ACFS resource for the specified file system is already in use.: Cause: An attempt to use the specified volume found that it was in use by an ACFS file system resource.; Action: Specify a volume that is not in use, or remove the conflicting ACFS resource.
ACFS-09611: Starting NFS Service.: Cause: Informational.; Action: None
ACFS-09612: Stopping NFS Service.: Cause: Informational.; Action: None
ACFS-09613: Restarting NFS Service.: Cause: Informational.; Action: None
ACFS-09614: Formatting the volume device.: Cause: Informational.; Action: None
ACFS-09615: NFS_PATH is not supported.: Cause: Informational.; Action: None
ACFS-09620: 'acfsutil scrub' is not implemented.: Cause: An attempt to invoke the command 'acfsutil scrub' was rejected because the version of acfsutil that was used did not include 'scrub' functionality.; Action: Upgrade the Grid Infrastructure software to a version that supports the ACFS scrubber, and retry the operation.
ACFS-09660: Data has been lost in the filesystem.: Cause: The ACFS Scrubber determined that data has been lost in one or more files in the file system being scrubbed. This may result in ACFS data needing to be restored from backup. This could be the result of a storage problem, a configuration issue or a software bug.; Action: Check the alert log for the result of the recovery attempt. Run fsck to verify the file system state. If unsuccessful, contact Oracle Support Services with the incident information.
ACFS-09670: Failure to initialize the ACFS Scrubber.: Cause: An attempt to initialize the ACFS scrubber resulted in an internal error.; Action: Contact Oracle Support Services.
ACFS-09671: Invalid trace value specified. Must be between number (terse) and number (verbose).: Cause: An attempt to initialize the trace level failed because an invalid value was specified.; Action: Retry the command using a value within the range indicated.
ACFS-09672: Invalid I/O load specified. Must be between number (lowest) and number (highest).: Cause: An attempt to initialize the I/O load failed because an invalid value was specified.; Action: Retry the command using a value within the range indicated.
ACFS-09673: Invalid file extent logging value specified. Must be between 0 and 3.: Cause: An attempt to initialize the file extent logging level failed because an invalid value was specified.; Action: Retry the command using a value within the range specified.
ACFS-09674: The filesystem is offline.: Cause: An attempt to scrub the contents of the filesystem was unsuccessful because the filesystem was offline.; Action: Retry the command when the filesystem is online.
ACFS-09675: The ACFS Scrubber was interrupted.: Cause: An interrupt signal was received by the Scrubber to abort scrubbing.; Action: None
ACFS-09676: | NO DATA |: Cause: No data is being printed in this field because the ACFS Scrubber is running as a background job.; Action: None
ACFS-09677: operation not supported by volume: Cause: An attempt to scrub the contents of the filesystem was unsuccessful because the filesystem was not on an ADVM or EXC volume.; Action: Retry the command on a filesystem that is using an ADVM or EDV volume.
ACFS-09801: Failure to access Oracle Cluster Registry (OCR).: Cause: An attempt to access the Oracle Cluster Registry encountered an internal error.; Action: Contact Oracle Support Services.
ACFS-09802: Failure to initialize the credentials context.: Cause: An attempt to initialize the Oracle Cluster Registry credentials context encountered an internal error.; Action: Contact Oracle Support Services.
ACFS-09803: Failure to initialize the credentials domain for the 'string' cluster.: Cause: An attempt to create the Oracle Cluster Registry credentials domain for the indicated cluster encountered an internal error.; Action: Contact Oracle Support Services.
ACFS-09804: Failure to create the credentials for the 'string' cluster.: Cause: An attempt to create the credentials for the indicated cluster encountered an internal error.; Action: Contact Oracle Support Services.
ACFS-09805: Failure to export the credentials for the 'string' cluster.: Cause: Unable to export the credentials for the indicated cluster to the specified Cluster Manifest File.; Action: Ensure that the current user has write permissions to the specified Cluster Manifest File, and retry the operation.
ACFS-09807: Could not find the 'string' credential domain.: Cause: The ACFSREMOTE credential domain was not found in the Oracle Cluster Registry (OCR).; Action: Verify ACFSREMOTE credentials already exist in the Oracle Cluster Registry (OCR). Run the 'acfsutil cluster credential -s Grid Infrastructure User' command if the ACFSREMOTE credentials domain is not present.
ACFS-09809: No Member Clusters have been registered.: Cause: An attempt to list the registered clusters returned no results because no Member Clusters have been registered.; Action: None
ACFS-09810: No credentials were found for the 'string' cluster name.: Cause: An attempt to list the credentials for the indicated cluster failed as it does not exist in the ACFSREMOTE domain.; Action: Verify the indicated cluster name is already registered. If necessary, register it using the 'acfsutil cluster credential -g cluster name -o Cluster Manifest File' command.
ACFS-09812: Unable to obtain the credential set for the 'string' cluster.: Cause: At attempt to get the credential set for the specified cluster encountered an internal error.; Action: Contact Oracle Support Services.
ACFS-09813: Unable to add a new credential pair to the credential set of the 'string' cluster.: Cause: An attempt to add the new credentials for the specified cluster encountered an internal error.; Action: Contact Oracle Support Services.
ACFS-09814: Unable to set the member cluster version.: Cause: An attempt to write the cluster version to the Oracle Cluster Registry (OCR) encountered an internal error.; Action: Contact Oracle Support Services.
ACFS-09816: Unable to determine the version of member cluster 'string'.: Cause: An attempt to read the cluster version for the indicated cluster from the Oracle Cluster Registry (OCR) encountered an internal error.; Action: Contact Oracle Support Services.
ACFS-09821: Unable to access the specified Cluster Manifest File.: Cause: An attempt to read the Cluster Manifest File provided failed. ACFS Remote Member Cluster registration requires a Cluster Manifest File with valid ASM credentials.; Action: Make sure the specified Cluster Manifest File has read and write permissions. Verify the input Cluster Manifest file was generated via 'asmcmd mkcc --asm' (or a flagless 'asmcmd mkcc'). If the Member Cluster has already been registed for ASM use, execute 'asmcmd mkcc --acfs' with the Cluster Manifest File previously generated.
ACFS-09822: The provided cluster name 'string' does not match the name of the Cluster Manifest File's cluster source 'string'.: Cause: There was a mismatch in the name provided and the name of the cluster in the Cluster Manifest File.; Action: Make sure you spelled the name correctly or register the specified cluster as a new one.
ACFS-09823: Unable to find the ASM attributes section in the provided Cluster Manifest File.: Cause: The ASM_attributes section was not found in the Cluster Manifest File provided.; Action: Provide the Cluster Manifest File generated during execution of 'asmcmd mkcc options' command.
ACFS-09824: Unable to find the cluster global unique ID in the provided Cluster Manifest File.: Cause: The cluster global unique ID for the specified cluster was not found in the Cluster Manifest File provided.; Action: Provide the Cluster Manifest File generated during execution of 'asmcmd mkcc options' command.
ACFS-09825: Unable to find the cluster name in the provided Cluster Manifest File.: Cause: The cluster name for the specified cluster was not found in the Cluster Manifest File provided.; Action: Provide the Cluster Manifest File generated during execution of 'asmcmd mkcc options' command.
ACFS-09826: Unable to import the credentials from the specified file.: Cause: An attempt to import the credentials from the Member Cluster Data File failed.; Action: Provide the Cluster Manifest File generated during execution of 'asmcmd mkcc options' command.
ACFS-09827: ACFS Remote credentials were not found in the provided Cluster Manifest File.: Cause: The ACFS Remote section was not found in the provided Cluster Manifest File.; Action: Retry the Member Cluster registration command 'asmcmd mkcc cluster name Cluster Manifest File options', appending '--acfs' to the options specified.
ACFS-09828: Command not permitted on cluster class 'string'.: Cause: An attempt to execute the command 'acfsutil cluster credential' with the specified options was rejected because the local cluster was of the indicated class. With the options specified this command may be executed only from a node in a Domain Services Cluster.; Action: Retry the command on a member node of the Domain Services Cluster.
ACFS-09829: unable to retrieve the current cluster class: Cause: An attempt to execute 'acfsutil cluster credential' failed because the cluster class could not be obtained from the OCR. Possibly the OCR is unavailable or this may be an internal error.; Action: Verify the OCR is available and retry. If retry does not succeed, contact Oracle Support Services.
ACFS-09830: The version string provided is invalid.: Cause: The expected version string input was not of a valid format.; Action: Retry the command with a valid version format. The expected format is X.X[.X.X.X] where the 2 first numbers are mandatory and the last 3 are optional.
ACFS-09831: Creation of ACFS Remote credentials is not supported for cluster version string. The minimum version is string: Cause: The ACFS Remote credentials could not be created because this functionality requires a minimum cluster version of 12.2.0.2.0.; Action: Upgrade the cluster version to 12.2.0.2.0 or higher and then retry the command.
ACFS-09849: Configuration error: iscsid.service is not running.: Cause: 'systemctl status iscsid' returned inactive.; Action: Run 'systemctl start iscsid' as root to start the iscsid service and retry the command.
ACFS-09890: Unable to delete Oracle Cluster Registry subkey 'string' error: string: Cause: An attempt to delete an advmutil transport or session failed because an attempt to delete the indicated Oracle Cluster Registry subkey failed with the indicated error.; Action: Contact Oracle Support Services.
ACFS-09891: Unable to open Oracle Cluster Registry subkey 'string' error: string: Cause: An attempt to open an advmutil transport or session failed because an attempt to open the indicated Oracle Cluster Registry subkey failed with the indicated error.; Action: Contact Oracle Support Services.
ACFS-09892: Unable to set Oracle Cluster Registry subkey 'string' in 'string' error: string: Cause: An attempt to set an advmutil transport or session failed because an attempt to set the indicated Oracle Cluster Registry subkey failed with the indicated error.; Action: Contact Oracle Support Services.
ACFS-09893: Unable to enumerate Oracle Cluster Registry subkey 'string' error: string: Cause: An attempt to enumerate an advmutil transport or session failed because an attempt to enumerate the indicated Oracle Cluster Registry subkey failed with the indicated error.; Action: Contact Oracle Support Services.
ACFS-09894: Invalid Oracle Cluster Registry subkey 'string' in path 'string. error: string': Cause: An attempt to access an advmutil transport or session failed because an attempt to access the indicated Oracle Cluster Registry subkey failed with the indicated error.; Action: Contact Oracle support service.
ACFS-09895: Unable to create Oracle Cluster Registry subkey 'string' error: string: Cause: An attempt to create an advmutil transport or session failed because an attempt to create the indicated Oracle Cluster Registry subkey failed with the indicated error.; Action: Contact Oracle Support Services.
ACFS-09896: Unable to retrieve Oracle Cluster Registry subkey value 'string' error: string: Cause: An attempt to retrieve an advmutil transport or session failed because an attempt to retrieve the indicated Oracle Cluster Registry subkey failed with the indicated error.; Action: Contact Oracle Support Services.
ACFS-09897: unable to retrieve the ASM Administrator name: Cause: An attempt to retrieve the ASM Administrator name from the ADVM control device failed.; Action: Verify that the Oracle stack is up and that ADVM driver is loaded. If not, bring up the Oracle stack, ensure that the ADVM driver is loaded, and retry the command.
ACFS-10101: Authentication failed.: Cause: The specified ACFS Security administrator password was wrong.; Action: Re execute the command and provide the correct ACFS Security administrator password at the prompt.
ACFS-10102: File systems prepared for ACFS auditing: string: Cause: Informational; Action: None
ACFS-10103: File systems with ACFS security enabled: string: Cause: Informational; Action: None
ACFS-10104: ACFS auditing is not present: Cause: Informational; Action: None
ACFS-10105: ACFS security is not enabled: Cause: Informational; Action: None
ACFS-10120: ACFS Encryption not initialized.: Cause: ACFS Encryption was not initialized.; Action: Run 'acfsutil encr init [-p]' as system administrator to initialize encryption.
ACFS-10121: Invalid ACFS encryption argument combination.: Cause: 'acfsutil keystore migration' command was rejected because an invalid option combination was specified.; Action: Retry the command specifying a valid option combination.
ACFS-10122: Unsupported keystore migration request.: Cause: The keystore for an ACFS file system could not be migrated because the request was to migrate the keystore from type OCR to type OKV. This functionality is currently not supported.; Action: The supported keystore migration is 'acfsutil keystore migrate' that migrates the OCR PKCS keystore to OCR SSO keystore, and 'acfsutil keystore migrate -p' that migrates the OCR SSO keystore to OCR PKCS keystore.
ACFS-10123: unable to obtain cluster information to initialize ACFS Encryption: Cause: ACFS Encryption failed to initialize because information about the cluster could not be obtained. ACFS Encryption is dependent on Cluster Ready Services (CRS) for operation.; Action: Verify that Cluster Ready Services(CRS) stack is up by executing 'crsctl check crs' and Cluster Synchronization Services(CSS) is running by executing 'crsctl check css'. If the CRS stack is not up, check with the CRS administrator to bring it up. If it does not resolve the problem contact Oracle Support Services.
ACFS-10124: unable to obtain cluster information for keystore migration: Cause: The 'acfsutil keystore migrate' request failed because information about the cluster could not be obtained. ACFS Encryption is dependent on Cluster Ready Services (CRS) for operation.; Action: Verify that Cluster Ready Services(CRS) stack is up by executing 'crsctl check crs' and Cluster Synchronization Services(CSS) is running by executing 'crsctl check css'. If the CRS stack is not up, check with the CRS administrator to bring it up. If it does not resolve the problem contact Oracle Support Services.
ACFS-10125: unable to obtain cluster information needed to manage encryption passwords: Cause: The 'acfsutil encr passwd' request failed because information about the cluster could not be obtained. ACFS Encryption is dependent on Cluster Ready Services (CRS) for operation.; Action: Verify that Cluster Ready Services(CRS) stack is up by executing 'crsctl check crs' and Cluster Synchronization Services(CSS) is running by executing 'crsctl check css'. If the CRS stack is not up, check with the CRS administrator to bring it up. If it does not resolve the problem contact Oracle Support Services.
ACFS-10126: unable to obtain cluster information needed to query keystore: Cause: The 'acfsutil encr info' request failed because information about the cluster could not be obtained. ACFS Encryption is dependent on Cluster Ready Services (CRS) for operation.; Action: Verify that Cluster Ready Services(CRS) stack is up by executing 'crsctl check crs' and Cluster Synchronization Services(CSS) is running by executing 'crsctl check css'. If the CRS stack is not up, check with the CRS administrator to bring it up. If it does not resolve the problem contact Oracle Support Services.
ACFS-10127: Migrating keystore from OCR to OKV is not supported on a replication-initialized file system.: Cause: The keystore for an ACFS file system could not be migrated because the request was to migrate the keystore from type OCR to type OKV on a file system that has replication initialized. This functionality is currently not supported.; Action: Terminate replication and rerun the command.
ACFS-10149: Realm description cannot exceed number characters: Cause: Realm description cannot exceed 1023 characters; Action: Select a shorter realm name and retry.
ACFS-10150: Realm description not specified within double quotation marks: Cause: Invalid description specified for realm.; Action: Enclose the realm description within double quotation marks.
ACFS-10151: Unmatched single quote or double quote.: Cause: Matching quote was not found.; Action: Add a matching quote and retry.
ACFS-10152: Realm name cannot exceed number characters.: Cause: Realm name length exceeded 255 characters.; Action: Select a shorter realm name and retry.
ACFS-10153: Realm 'string' not found on mount point 'string'.: Cause: Realm was not found on mount point.; Action: Ensure that the realm exists using the command 'acfsutil sec info -m <mount_point> -n'.
ACFS-10154: Failed to create realm 'string' on mount point 'string'.: Cause: Internal error.; Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ACFS-10155: Realm 'string' created.: Cause: Realm was created.; Action: None
ACFS-10156: Failed to destroy realm 'string' on mount point 'string'.: Cause: Internal error.; Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ACFS-10157: Realm 'string' destroyed.: Cause: Realm was destroyed.; Action: None
ACFS-10158: Improper value specified for -l option.: Cause: Invalid argument format was specified for -l option.; Action: Specify the argument in the format 'commandrule:ruleset'. A comma separated list can also be specified as 'cmd1:rs1,cmd2:rs2,cmd2:rs3'. For example: * - acfsutil sec realm add r1 -m /mnt -l READ:rs1 * - acfsutil sec realm add r1 -m /mnt -l READ:rs1,MKDIR:rs2
ACFS-10159: The command requires at least one of the options -u, -G, -l, -f, or -e.: Cause: None of the options -u, -G, -l, -f, or -e were specified with this command.; Action: Specify at least one of the options -u, -G, -l, -f, or -e with this command.
ACFS-10160: Failed to add user 'string' to the realm 'string'.: Cause: Internal error.; Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ACFS-10161: Added user 'string' to realm 'string'.: Cause: User was added to realm.; Action: None
ACFS-10162: Failed to add group 'string' to realm 'string'.: Cause: Internal error.; Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ACFS-10163: Added group 'string' to the realm 'string'.: Cause: Group was added to the realm.; Action: None
ACFS-10164: Failed to add filter 'string:string' to the realm 'string'.: Cause: Internal error.; Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ACFS-10165: Added filter 'string:string' to the realm 'string'.: Cause: Filter was added to the realm.; Action: None
ACFS-10166: Failed to add 'string' to the realm 'string'.: Cause: Internal error.; Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ACFS-10167: Added 'string' to the realm 'string'.: Cause: Pathname was added to the realm.; Action: None
ACFS-10168: Failed to turn encryption ON for realm 'string'.: Cause: Internal error.; Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ACFS-10169: Encryption turned ON for realm 'string'.: Cause: Encryption was turned ON for realm.; Action: None
ACFS-10170: Failed to delete user 'string' from realm 'string'.: Cause: Internal error.; Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ACFS-10171: Deleted user 'string' from realm 'string'.: Cause: User was deleted from realm.; Action: None
ACFS-10172: Failed to delete group 'string' from the realm 'string'.: Cause: Internal error.; Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ACFS-10173: Deleted group 'string' from realm 'string'.: Cause: Group was deleted from realm.; Action: None
ACFS-10174: Failed to delete filter 'string:string' from the realm 'string'.: Cause: Internal error.; Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ACFS-10175: Deleted filter 'string:string' from realm 'string'.: Cause: Filter was deleted from realm.; Action: None
ACFS-10176: Failed to delete 'string' from realm 'string'.: Cause: Internal error.; Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ACFS-10177: Deleted 'string' from realm 'string'.: Cause: Pathname was deleted from realm.; Action: None
ACFS-10178: Failed to turn encryption OFF for realm 'string'.: Cause: Internal error.; Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ACFS-10179: Encryption turned OFF for realm 'string'.: Cause: Encryption was turned OFF for realm.; Action: None
ACFS-10180: Failed to get realm files or directories for realm 'string'.: Cause: Internal error.; Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ACFS-10181: Failed to get groups for realm 'string'.: Cause: Internal error.; Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ACFS-10182: Failed to get users for realm 'string'.: Cause: Internal error.; Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ACFS-10183: Failed to get filters for realm 'string'.: Cause: Internal error.; Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ACFS-10184: Failed to get realm encryption attributes of realm 'string'.: Cause: Internal error.; Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ACFS-10185: '-e' requires both '-a' and '-k'.: Cause: At least one of the options -a or -k is missing with -e option.; Action: Specify both '-a' and '-k' with '-e' and retry.
ACFS-10186: Realm 'string' already exists on mount point 'string'.: Cause: Realm was already found on mount point.; Action: Specify another realm name and retry.
ACFS-10187: Failed to get all realms on mount point 'string'.: Cause: Internal error.; Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ACFS-10188: Attributes of realm 'string' retrieved.: Cause: Realm attributes were retrieved.; Action: None
ACFS-10189: Failed to update attributes of realm 'string'.: Cause: Internal error.; Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ACFS-10190: Updated attributes of realm 'string'.: Cause: Updated realm attributes.; Action: None
ACFS-10195: None of the options -a, -d, are specified with the edit command.: Cause: An attempt to execute the command 'ruleset edit' was rejected because specifying one of -a or -d was mandatory.; Action: Retry the operation, specifying either -a or -d.
ACFS-10204: The rule 'string' will not be added or deleted.: Cause: An attempt to execute the command 'ruleset edit' was rejected because the indicated rule name was specified with both the -a and the -d option.; Action: Retry the command, specifying the indicated rule name in either the -a or the -d option, but not both.
ACFS-10205: The option -f should be specified at the end after all other options.: Cause: An attempt to edit the realm was rejected because -f was not supplied as the last argument of the command.; Action: Retry the command, specifying -f as the last argument.
ACFS-10206: File or directory 'string' does not belong to an ACFS file system: Cause: A File or directory specified in 'acfsutil sec realm add/delete' command did not belong to an ACFS file system.; Action: Specify only ACFS file or directory in the command 'acfsutil sec realm add/delete'.
ACFS-10221: Rule name cannot exceed number characters.: Cause: Rule name length exceeded 255 characters.; Action: Select a rule name that is smaller than 255 characters and retry.
ACFS-10223: Invalid rule type is specified.: Cause: Invalid rule type was provided on the command line with '-t'.; Action: Provide one of the following with '-t': * - username <user_name> * - application <application_name> * - time <start_time>,<end_time> * - hostname <host_name>
ACFS-10224: Rule type 'username', 'application' or 'hostname' must have only one rule value.: Cause: An incorrect number of arguments were provided with rule type 'username', 'application' or 'hostname'.; Action: Provide only one argument after the rule type 'username', 'application' or 'hostname'. * For example, '-t username alice' * '-t application 'c:\programs\mozilla.exe' * '-t application '/sbin/cat' * '-t hostname myhost.domain.com'
ACFS-10225: Rule type 'time' must have both start time and end time separated by a comma.: Cause: Either the start time or end time was not provided.; Action: Specify both start time and end time (comma separated) after rule type time. * For example, '-t time 10:10:40,23:01:12'
ACFS-10226: '-o' requires either 'ALLOW' or 'DENY'.: Cause: A valid rule option was not provided.; Action: Specify either 'ALLOW' or 'DENY' as rule the option.
ACFS-10227: Failed to perform rule create operation on 'string'.: Cause: Internal error.; Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ACFS-10228: Rule 'string' is created.: Cause: Rule was created.; Action: None
ACFS-10229: Rule 'string' not found.: Cause: Rule was not found.; Action: Ensure that the rule exists by executing 'acfsutil sec info -m mnt -l rule-name'.
ACFS-10230: Failed to perform rule edit operation on 'string'.: Cause: Internal error.; Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ACFS-10231: Rule 'string' updated.: Cause: Rule was updated.; Action: None
ACFS-10232: Failed to destroy rule 'string'.: Cause: Internal error; Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ACFS-10233: Rule 'string' destroyed.: Cause: Rule was destroyed.; Action: None
ACFS-10234: Failed to get rule 'string' information.: Cause: Internal error.; Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ACFS-10235: Rule 'string' already exists.: Cause: Rule was already found on mount point.; Action: Specify another rule name and retry.
ACFS-10236: Time format string must be HH:MM:SS.: Cause: The time format provided was not formatted as 'HH:MM: SS', where HH translates to hours, MM to minutes and SS to seconds.; Action: Specify the time in correct format and retry.
ACFS-10237: Rule type 'string' specified does not match the actual type 'string' of rule 'string': Cause: The rule type specified did not match the actual rule typed.; Action: Specify the actual rule type to update the rule value and retry.
ACFS-10238: Failed to get all rules on mount point 'string'.: Cause: Internal error.; Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ACFS-10239: Failed to get information for rule 'string'.: Cause: Internal error.; Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ACFS-10240: Cannot destroy rule 'string'. The rule is in use by one or more rule sets.: Cause: The rule was being used in one or more rule set(s) in the file system.; Action: Remove the rule from the rule set(s) and retry.
ACFS-10241: Rule set name cannot exceed number characters.: Cause: Rule set name length exceeded 255 characters.; Action: Select a shorter rule set name and retry.
ACFS-10242: '-o' requires either ALL_TRUE or ANY_TRUE.: Cause: The rule set option was not set to either ALL_TRUE or ANY_TRUE.; Action: Specify either ALL_TRUE or ANY_TRUE with the rule set option '-o'.
ACFS-10243: Failed to create rule set 'string' on mount point 'string'.: Cause: Internal error; Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ACFS-10244: Rule set 'string' is created.: Cause: Rule set was created.; Action: None
ACFS-10245: Rule set 'string' not found on mount point 'string'.: Cause: Rule set was not found on mount point.; Action: None
ACFS-10246: Failed to add rule 'string' to the rule set 'string'.: Cause: Internal error.; Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ACFS-10247: Added rule 'string' to the rule set 'string'.: Cause: Rule was added to the rule set.; Action: None
ACFS-10248: Failed to delete rule 'string' from the rule set 'string'.: Cause: Internal error.; Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ACFS-10249: Deleted rule 'string' from rule set 'string'.: Cause: Rule was deleted from the rule set.; Action: None
ACFS-10250: Failed to destroy rule set 'string' on mount point 'string'.: Cause: Internal error.; Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ACFS-10251: Rule set 'string' destroyed.: Cause: Rule set was destroyed.; Action: None
ACFS-10252: Failed to get rules for rule set 'string'.: Cause: Internal error.; Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ACFS-10253: Failed to get list of command rules.: Cause: Internal error.; Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ACFS-10254: Rule set 'string' already exists.: Cause: Rule set was already found on mount point.; Action: Specify another rule set name and retry.
ACFS-10255: Rule 'string' already exists in rule set 'string'.: Cause: Rule was already part of rule set.; Action: None
ACFS-10256: Rule 'string' is not found in rule set 'string'.: Cause: Rule was not found in the rule set.; Action: Ensure that the realm exists using the command 'acfsutil sec info -m -s ruleset-name'.
ACFS-10257: Failed to get all rule sets on mount point 'string'.: Cause: Internal error.; Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ACFS-10258: Failed to get information for rule set 'string'.: Cause: Internal error.; Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ACFS-10259: Invalid command rule 'string'.: Cause: Invalid command rule was specified.; Action: Execute 'acfsutil sec info -m <mount_point> -c' to get all the valid command rules. * Re-execute the command with valid command rule.
ACFS-10260: File object 'string' and the realm 'string' should be in the same file system.: Cause: File object was not in the same file system as that of the realm.; Action: Specify file objects from the same file system as that of the realm.
ACFS-10261: Cannot destroy rule set 'string'. The rule set is in use by one or more realms.: Cause: The rule set is being used in filter(s) that are part of one or more realms in the file system.; Action: Remove the filter(s) from the realms that are using this rule set and retry.
ACFS-10262: Application path name for rule type 'application' cannot exceed 'number' characters.: Cause: Application path name for rule type 'application' exceeded 511 characters; Action: Select a shorter application path name for rule type 'application' and retry.
ACFS-10263: Host name for rule type 'hostname' cannot exceed 'number' characters.: Cause: Host name for rule type 'hostname' exceeded 255 characters.; Action: Select a shorter host name for rule type 'hostname' and retry.
ACFS-10264: Invalid value for rule type 'string' as the given path name 'string' is a symbolic link: Cause: Path name provided for rule type 'application' was a symbolic link. Symbolic links are not supported for rule type 'application'.; Action: Specify a path name which is not a symbolic link and re-execute the command.
ACFS-10271: Encryption algorithm can be only 'AES'.: Cause: The encryption algorithm provided was not 'AES'.; Action: Specify 'AES' as the algorithm with '-a' and retry.
ACFS-10272: Key length must be either 128, 192, or 256.: Cause: The key length specified with '-k' was not 128, 192 or 256.; Action: Specify either 128, 192, or 256 with '-k' and retry.
ACFS-10273: Failed to set the encryption parameter on realm 'string'.: Cause: Internal error.; Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ACFS-10274: Failed to update rule set option.: Cause: Internal error.; Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ACFS-10275: Failed to get rule sets for mount point 'string'.: Cause: Internal error.; Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ACFS-10276: Rule set 'string' option updated to 'string'.: Cause: Rule set option updated.; Action: None
ACFS-10277: '-e' requires either ON or OFF.: Cause: The realm encryption status specified with '-e' was not 'on' or 'off'; Action: Specify either 'on' or 'off' with -e and retry.
ACFS-10278: Encryption parameters are not set on the file system, realm encryption is unavailable.: Cause: The encryption parameters were not set on the file system.; Action: A system administrator must execute an 'encr set' command
ACFS-10284: Failed to get security information for 'string'.: Cause: Internal error.; Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ACFS-10285: Pathname 'string' does not exist.: Cause: Specified pathname was not found.; Action: Specify a valid pathname.
ACFS-10286: User 'string' does not exist.: Cause: User was not found.; Action: Specify a valid user.
ACFS-10287: Group 'string' does not exist.: Cause: Group was not found; Action: Specify a valid group.
ACFS-10288: User 'string' already added to the realm 'string'.: Cause: User was already added to the realm.; Action: None
ACFS-10289: Group 'string' already added to the realm 'string'.: Cause: Group was already added to the realm; Action: None
ACFS-10290: Realm filter 'string' already added to the realm 'string'.: Cause: Filter was already added to the realm.; Action: None
ACFS-10291: Pathname 'string' already added to the realm 'string'.: Cause: Pathname was already added to the realm.; Action: None
ACFS-10292: User 'string' is not part of the realm 'string'.: Cause: User was not part of the realm.; Action: None
ACFS-10293: Group 'string' is not part of the realm 'string'.: Cause: Group was not part of the realm.; Action: None
ACFS-10294: Pathname 'string' is not part of the realm 'string'.: Cause: Pathname was not part of the realm.; Action: None
ACFS-10295: Realm filter 'string' is not part of the realm 'string'.: Cause: Filter was not part of the realm.; Action: None
ACFS-10296: Realm filter 'string:string' could not be added to the realm 'string'.: Cause: The filter was not added because the filter with command rule 'ALL' was already part of the realm.; Action: Either add the command rules individually or add 'ALL' if all of the command rules are desired. Individual command rules cannot be added when 'ALL' is already present.
ACFS-10297: Realm filter 'ALL' could not be added since another filter exists in realm 'string'.: Cause: Filter 'ALL' was not added because another filter existed in the realm .; Action: Either add the command rules individually or add 'ALL' if all of the command rules are desired. 'ALL' command rule cannot be added when individual command rules are already present.
ACFS-10298: User name cannot exceed number characters.: Cause: User name length exceeded 64 characters.; Action: Select a shorter user name and retry.
ACFS-10299: Group name cannot exceed number characters.: Cause: Group name length exceeded 64 characters.; Action: Select a shorter group name and retry.
ACFS-10322: System realm 'SYSTEM_SecurityMetadata' created.: Cause: System realm 'SYSTEM_SecurityMetadata' was created.; Action: None
ACFS-10323: System realm 'SYSTEM_Logs' created.: Cause: System realm 'SYSTEM_Logs' was created.; Action: None
ACFS-10324: Rulesets cannot be cloned before cloning rules on mount point 'string'.: Cause: Rule sets were not cloned because some rules were not present on mount point.; Action: Clone rules first using command 'acfsutil sec rule clone' and then clone rule sets.
ACFS-10342: System realm 'SYSTEM_BackupOperators' created.: Cause: System realm 'SYSTEM_BackupOperators' was created.; Action: None
ACFS-10350: Incorrect password was entered in all attempts to open the encryption key store. Encrypted files will not be available.: Cause: Incorrect password was entered in all attempts to open the encryption key store during the mount command.; Action: Unmount the file system and remount it, providing the correct password. Encrypted files will not be available until the file system is unmounted and remounted with the correct password.
ACFS-10355: System realm 'SYSTEM_Antivirus' created.: Cause: System realm 'SYSTEM_Antivirus' was created.; Action: None
ACFS-10356: waiting for the operation to complete...: Cause: Informational.; Action: None
ACFS-10357: System realm 'SYSTEM_Audit' created.: Cause: Informational.; Action: None
ACFS-10359: Failed to create system realm 'string': Cause: An attempt to create a realm with the specified name was rejected because the specified name was a system realm name. System realms get created as the result of some ACFS Security operations and cannot be explicitly created by the ACFS Security Administrator.; Action: Rerun the command with a different realm name.
ACFS-10360: Failed to create system ruleset 'string': Cause: An attempt to create a ruleset with the specified name was rejected because the specified name was a system ruleset name. System rulesets get created as the result of some ACFS Security operations and cannot be explicitly created by the ACFS Security Administrator.; Action: Rerun the command with a different ruleset name.
ACFS-10361: Failed to create system rule 'string': Cause: An attempt to create a rule with the specified name was rejected because the specified name was a system rule name. System rules get created as the result of some ACFS Security operations and cannot be explicitly created by the ACFS Security Administrator.; Action: Rerun the command with a different rule name.
ACFS-10364: Incorrect password for local OKV endpoint.: Cause: An incorrect password was entered while opening the local OKV endpoint.; Action: Retry the command and enter the correct password.
ACFS-10400: Encryption is set on mount point 'string'.: Cause: Encryption was set on mount point.; Action: None
ACFS-10401: Failed to set encryption parameters on mount point 'string'.: Cause: Internal error.; Action: Refer to encryption log in '<mount_point>/.Security/encryption/logs/encr-<host_name>.log'.
ACFS-10402: Encryption turned 'string' on 'string'.: Cause: Encryption was turned either ON or OFF on the pathname.; Action: None
ACFS-10403: Failed to turn encryption 'string' on 'string'.: Cause: Internal error.; Action: Refer to encryption log in '<mount_point>/.Security/encryption/logs/encr-<host_name>.log'.
ACFS-10405: Failed to get encryption information on 'string'.: Cause: Internal error.; Action: Refer to encryption log in '<mount_point>/.Security/encryption/logs/encr-<host_name>.log'.
ACFS-10406: Re-key operation is complete on 'string'.: Cause: Re-key operation was complete on the pathname.; Action: None
ACFS-10407: Failed to perform re-key operation on 'string'.: Cause: Internal error.; Action: Refer to encryption log in '<mount_point>/.Security/encryption/logs/encr-<host_name>.log'.
ACFS-10410: encryption is already disabled on the file system: Cause: Encryption was already disabled on the file system.; Action: None, encryption is already disabled.
ACFS-10411: encryption is already enabled on the file system: Cause: Encryption was already enabled on the file system.; Action: None, encryption is already enabled.
ACFS-10412: Encryption parameters were not provided, using default algorithm (string) and key length (number).: Cause: Encryption parameters were not provided.; Action: None, default values have been used.
ACFS-10413: The ADVM compatibility attribute for the diskgroup must be set to version 11.2.0.2.0 to allow the acfsutil encryption and security commands.: Cause: The ADVM compatibility attribute has not been upgraded to version 11.2.0.2.0 or beyond.; Action: Use the ASMCA tool or the SQL ALTER DISKGROUP statement to upgrade COMPATIBLE.ADVM attribute.
ACFS-10414: Encryption has been initialized for the cluster.: Cause: An administrator initialized encryption for the cluster.; Action: None
ACFS-10415: File system level encryption is on, file level encryption operations are not allowed: Cause: A file level encryption operation was attempted while file system level encryption was enabled. File level encryption operations are not allowed when file system level encryption is turned on.; Action: None
ACFS-10416: File is realm secured\n: Cause: An encryption operation was attempted on a realm secured file and no action was performed. A realm secured file can only be encrypted and decrypted by changing the encryption parameters of containing realm(s) or by deleting the file from all realms.; Action: If changing the encryption status of this file is required, contact a Security Administrator to modify the encryption parameters of the containing realm(s).
ACFS-10419: Skipping directory 'string' because it does not belong to the file system mounted on 'string': Cause: The directory does not belong to the specified mounted ACFS file system.; Action: None
ACFS-10420: Encryption parameters specified for realm 'string' match existing settings.: Cause: An attempt to set encryption parameters for a realm specified values the same as those already set.; Action: None
ACFS-10421: The ADVM compatibility attribute for the diskgroup must be set to version 'string' to allow acfsutil encryption commands.: Cause: An adminstrator attempted an encryption set or volume level rekey operation, but the ADVM compatibility attribute had not been upgraded to a supported version.; Action: Use the ASMCA tool or the SQL ALTER DISKGROUP statement to upgrade COMPATIBLE.ADVM attribute.
ACFS-10422: The ADVM compatibility attribute for the diskgroup must be set to version 'string' to allow 'acfsutil sec' commands.: Cause: A security adminstrator attempted an ACFS Security operation, but the ADVM compatibility attribute had not been upgraded to a supported version.; Action: Use the ASMCA tool or the SQL ALTER DISKGROUP statement to upgrade COMPATIBLE.ADVM attribute and retry the operation.
ACFS-10423: This encryption operation is not allowed on a standby file system.: Cause: An encryption operation that is not allowed on a standby file system was attempted. The following acfsutil encryption commands are not allowed on a standby file system: 'encr set', 'encr on', 'encr off', and 'encr rekey'.; Action: None
ACFS-10424: This ACFS Security operation is not allowed on a standby file system.: Cause: An ACFS Security operation that is not allowed on a standby file system was attempted. The following acfsutil security commands are not allowed on a standby file system: 'sec prepare', 'sec save/load/enable/disable', 'sec realm create/destroy/clone/add/delete', 'sec rule create/destroy/clone/edit', and 'sec ruleset create/destroy/clone/edit'; Action: None
ACFS-10426: This ACFS Security operation is not allowed when replication is in use.: Cause: ACFS security operations are not supported on a file system when replication is in use.; Action: None
ACFS-10450: Unauthorized encryption operation attempted on 'string'.: Cause: A user attempted an encryption operation on the given file and the operation was denied.; Action: None
ACFS-10451: File level encryption operation attempted on realm secured file 'string'.: Cause: A user attempted to perform a file level encryption command on a realm secured file and the operation was denied.; Action: None
ACFS-10452: Failed to decrypt 'string'.: Cause: Internal error.; Action: Contact Oracle Support Services.
ACFS-10453: Unable to get encryption parameters for the file system mounted on 'string'.: Cause: Internal error.; Action: Contact Oracle Support Services.
ACFS-10454: File system level encryption turned on for mount point 'string'.: Cause: A system administrator enabled file system level encryption.; Action: None
ACFS-10455: New volume encryption key generated for mount point 'string'.: Cause: A system administrator updated the volume encryption key for the mount point. The file encryption keys for all encrypted files on the file system were re-encrypted using the new volume encryption key.; Action: None
ACFS-10456: New file encryption key generated for file 'string'.: Cause: A system administrator updated the volume encryption key for the file. The data in the file was re-encrypted using the new key.; Action: None
ACFS-10457: New file encryption keys generated for all files in directory 'string'.: Cause: A system administrator updated the volume encryption key for the files in the given directory. The file contents were re-encrypted using the new key.; Action: None
ACFS-10458: Encryption turned off for path 'string'.: Cause: A user successfully decrypted a file or directory.; Action: None
ACFS-10459: Encryption turned off for directory 'string' and its contents.: Cause: A user successfully decrypted a directory and its contents.; Action: None
ACFS-10460: File system level encryption turned off for mount point 'string'.: Cause: A system administrator disabled file system level encryption.; Action: None
ACFS-10461: Encryption turned on for path 'string'.: Cause: A user successfully encrypted a file or directory.; Action: None
ACFS-10462: Encryption turned on for directory 'string' and its contents.: Cause: A user successfully encrypted a directory and its contents.; Action: None
ACFS-10463: Skipping file 'string' because it does not belong to the file system mounted on 'string': Cause: The file does not belong to the specified mounted ACFS file system.; Action: None
ACFS-10464: ACFS Encryption operations are not allowed on files of this type.: Cause: An attempt was made to encrypt, decrypt, or rekey a file of one of the following Oracle file types: data, control, online redo log, archive log, backup, incremental backup, or flashback.; Action: None
ACFS-10465: FS-level encryption parameters have been set to:: Cause: Informational.; Action: None
ACFS-10466: Using user-provided parameters: algorithm string, key length number bytes: Cause: Informational.; Action: None
ACFS-10467: Using FS-level parameters: algorithm string, key length number bytes: Cause: Informational.; Action: None
ACFS-10468: Encryption has been enabled on mount point 'string'.: Cause: Informational.; Action: None
ACFS-10469: Rekeying file/directory 'string'...: Cause: Informational.; Action: None
ACFS-10470: Encrypting file/directory 'string'...: Cause: Informational.; Action: None
ACFS-10471: Path: string: Cause: Informational.; Action: None
ACFS-10472: Re-encrypting FEK for mount point 'string'...: Cause: Informational.; Action: None
ACFS-10473: Re-encrypting FEK for file/directory 'string'...: Cause: Informational.; Action: None
ACFS-10475: Failed to rekey file/directory 'string'.: Cause: An unexpected error occured while attempting to rekey the indicated file. This is an internal error.; Action: Contact Oracle Support Services.
ACFS-10476: Algorithm AES number-bit, Key length number bytes: Cause: Informational.; Action: None
ACFS-10477: Decrypting file/directory 'string'...: Cause: Informational.; Action: None
ACFS-10478: Encryption has been disabled on mount point 'string'.: Cause: Informational.; Action: None
ACFS-10479: File is larger than 128M, cannot encrypt, decrypt or rekey.: Cause: An attempt was made to encrypt, decrypt or rekey a file larger than 128M in size.; Action: If an encryption operation was attempted, create a new file of size zero, encrypt it using desired encryption parameters, and copy the original file into the newly created file. Then rename the newly created file to the original file name if required. If a decryption operation was attempted, create an unencrypted new file of size zero, and copy the original encrypted file into the new file. Then rename the newly created file to the original file name if required. If a rekey operation was attempted, create a new file of size zero, encrypt it using desired (after rekey) encryption parameters, and copy the original file into the newly created file. Then rename the newly created file to the original file name if required.
ACFS-10500: Pathname cannot exceed number characters.: Cause: Pathname length exceeds 255 characters.; Action: Select a name that is smaller than %d characters and retry.
ACFS-10541: Wallet 'string' creation failed [error : number string].: Cause: An attempt to create the indicated wallet failed with the indicated error. This is an internal error.; Action: Contact Oracle Support Services.
ACFS-10542: Wallet 'string' save failed [error : number string].: Cause: An attempt to save the indicated wallet failed with the indicated error. This is an internal error.; Action: Contact Oracle Support Services.
ACFS-10543: Wallet 'string' open failed [error : number string].: Cause: An attempt to open the indicated wallet failed with the indicated error. This is an internal error.; Action: Contact Oracle Support Services.
ACFS-10548: Wallet initialization failed [error : number string].: Cause: An attempt to initialize the wallet failed with the indicated error. This is an internal error.; Action: Contact Oracle Support Services.
ACFS-10549: Wallet termination failed [error : number string].: Cause: An attempt to terminate the wallet failed with the indicated error. This is an internal error.; Action: Contact Oracle Support Services.
ACFS-10550: Security wallet created.: Cause: Security wallet was created.; Action: None
ACFS-10551: Security wallet creation failed.: Cause: An attempt to create the security wallet failed with the indicated error. This is an internal error.; Action: Contact Oracle Support Services.
ACFS-10552: Security wallet save failed.: Cause: An attempt to save the security wallet failed with the indicated error. This is an internal error.; Action: Contact Oracle Support Services.
ACFS-10553: Security wallet open failed.: Cause: An attempt to open the security wallet failed with the indicated error. This is an internal error.; Action: Contact Oracle Support Services.
ACFS-10557: Security wallet could not be owned by 'string'.: Cause: An attempt to change the ownership of the security wallet failed. This is an internal error.; Action: Contact Oracle Support Services.
ACFS-10559: Insufficient privileges to switch to %0!s '%1!s'.: Cause: An attempt to change the user or group membership privilege for a process failed because the user who was executing the command did not have sufficient privileges.; Action: Retry the command as a system administrator.
ACFS-10564: Incorrect password for encryption key store.: Cause: An incorrect password was entered while opening the encryption key store.; Action: Retry the command and enter the correct password.
ACFS-10565: Encryption key store created.: Cause: Encryption key store was created.; Action: None
ACFS-10566: Encryption key store creation failed.: Cause: An attempt to create the encryption key store failed with the indicated error. This is an internal error.; Action: Refer to encryption log in '<mount_point>/.Security/encryption/logs/encr-<host_name>.log'.
ACFS-10567: Encryption key store save failed.: Cause: An attempt to save the encryption key store failed. This is an internal error.; Action: Contact Oracle Support Services.
ACFS-10568: Encryption key store open failed.: Cause: An attempt to open the encryption key store failed. This is an internal error.; Action: Contact Oracle Support Services.
ACFS-10569: Encryption key store delete succeeded.: Cause: Encryption key store was deleted.; Action: None
ACFS-10573: Encryption key store not found.: Cause: Encryption key store did not exist.; Action: Run 'acfsutil encr init' command and retry.
ACFS-10574: ACFS encryption already initialized, cannot reinitialize.: Cause: 'acfsutil encr init'can has already been executed and the encryption key store already existed.; Action: None
ACFS-10575: Incorrect encryption key store.: Cause: The encryption key store may have been deleted and re-created.; Action: Recover the correct key store from a backup and retry.
ACFS-10576: Incorrect encryption key, new volume encryption key not created.: Cause: The encryption key store may have been deleted and re-created.; Action: Recover the correct key store from a backup and retry.
ACFS-10577: Encryption parameters not set.: Cause: A command that requires encryption parameters to be set first was run before encryption parameters were set on the file system.; Action: Run 'acfsutil encr set' and retry.
ACFS-10578: Unable to communicate new encryption settings to cluster members.: Cause: Internal error.; Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ACFS-10579: Key store is not valid for encryption.: Cause: The encryption key store was either not created using 'acfsutil encr init' or it was corrupted.; Action: Restore the encryption key store from a backup and retry.
ACFS-10580: Internal API error : [number : string].: Cause: Internal error occurred.; Action: Contact Oracle Support Services.
ACFS-10581: Internal API error : [string].: Cause: Internal error occurred.; Action: Contact Oracle Support Services.
ACFS-10582: Internal API error : [number : string string].: Cause: Internal error occurred.; Action: Contact Oracle Support Services.
ACFS-10583: Internal API error : [string, number].: Cause: Internal error occurred.; Action: Contact Oracle support service.
ACFS-10585: Ioctl 'string' failed in 'string' with error number.: Cause: Internal error occurred.; Action: Contact Oracle Support Services.
ACFS-10586: Internal error.: Cause: Internal error occurred.; Action: Contact Oracle support service.
ACFS-10588: Internal error : WLT number.: Cause: Internal error occurred.; Action: Contact Oracle support service.
ACFS-10589: Internal error : BSF number.: Cause: Internal error occurred.; Action: Contact Oracle support service.
ACFS-10590: Internal error : XML number.: Cause: Internal error occurred.; Action: Contact Oracle support service.
ACFS-10591: Internal error : TSP number.: Cause: Internal error occurred.; Action: Contact Oracle support service.
ACFS-10592: Internal error : IOC number.: Cause: Internal error occurred.; Action: Contact Oracle support service.
ACFS-10593: Internal error : UGP number.: Cause: Internal error occurred.; Action: Contact Oracle support service.
ACFS-10594: Internal error : OCR number : string.: Cause: Internal error occurred.; Action: Contact Oracle support service.
ACFS-10596: Unable to get the hostname for the current node.: Cause: The current user does not have access to the requested information.; Action: Contact Oracle Support Services.
ACFS-10597: The user 'string' and the group 'string' do not belong to the same domain.: Cause: The user and the group were not part of the same domain.; Action: Use 'net user' command to verify and retry with user and group that belong to the same domain.
ACFS-10598: Unable to retrieve domain name information for 'string'.: Cause: Unable to retrieve domain name information.; Action: Make sure the node is part of proper domain.
ACFS-10599: Current user does not have system administrative privileges to initialize ACFS security.: Cause: The user was not part of system administrators group.; Action: Run 'acfsutil sec init' with administrative privileges.
ACFS-10600: Failed to store first security administrator 'string' in wallet.: Cause: Internal error.; Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ACFS-10601: Failed to update first security administrator 'string' information.: Cause: Internal error.; Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ACFS-10602: Passwords do not match.: Cause: Verification of the password did not succeed.; Action: Re-execute and provide the same password on both the prompts.
ACFS-10603: Security administrator group already set in wallet.: Cause: Security administrator group was already set in wallet.; Action: None
ACFS-10604: Security administrator group not set in wallet.: Cause: Internal error.; Action: Contact Oracle Support Service.
ACFS-10606: User 'string' is not a security administrator.: Cause: User was not a security administrator.; Action: Only a security administrator has privilege to execute the security commands. Add the user to security administrator list by executing 'acfsutil sec admin add' and retry.
ACFS-10607: User 'string' is not member of security administrator group.: Cause: User was not a member of security administrator's group.; Action: Add the user to the security administrator's group.
ACFS-10609: Administrator update in driver failed.: Cause: Internal error; Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ACFS-10610: Failed to get current user information.: Cause: Internal error.; Action: Contact Oracle Support Service.
ACFS-10611: Failed to assign user 'string' as security administrator.: Cause: Internal error; Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ACFS-10612: Failed to remove user 'string' from security administrator(s) list.: Cause: Internal error; Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ACFS-10613: Failed to change ACFS Security administrator password for current user.: Cause: Internal error; Action: Contact Oracle Support Services.
ACFS-10614: Security administrator 'string' already added.: Cause: User was already a security administrator.; Action: None
ACFS-10615: User 'string' is not a security administrator.: Cause: User was not a security administrator.; Action: None
ACFS-10616: Incorrect ACFS Security administrator password.: Cause: The password supplied was incorrect.; Action: Re-execute and provide the correct ACFS Security administrator password for the current user.
ACFS-10617: Password cannot exceed number characters.: Cause: The password entered exceeded the maximum allowed characters.; Action: Enter the password within the specified number of characters.
ACFS-10618: Security administrator 'string' could not be added.: Cause: Security administrator was not added.; Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ACFS-10619: Security administrator 'string' added.: Cause: Security administrator was added.; Action: None
ACFS-10620: Security administrator 'string' could not be removed.: Cause: Security administrator was not removed.; Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ACFS-10621: Removal of the last security administrator 'string' is not allowed.: Cause: The security administrator was not removed being the only security administrator in this system.; Action: Add another security administrator to remove the intended security administrator.
ACFS-10622: Security administrator 'string' removed.: Cause: Security administrator was removed.; Action: None
ACFS-10623: ACFS security already initialized, cannot reinitialize.: Cause: ACFS security was already initialized and could not be reinitialized.; Action: None
ACFS-10624: User 'string' is not member of the group 'string'.: Cause: The user was not member of the group.; Action: Add the user to the group and retry.
ACFS-10625: Failed to prepare file system for security operations on mount point 'string'.: Cause: Internal error.; Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ACFS-10626: Mount point 'string' is already prepared for security.: Cause: Mount point was already prepared for security. Prepare should be executed only once for an ACFS formatted file system that is mounted.; Action: None
ACFS-10627: Mount point 'string' is now prepared for security operations.: Cause: " Mount point was prepared for security operations.; Action: None
ACFS-10629: Failed to enable security on mount point 'string'.: Cause: Internal error.; Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ACFS-10630: Security is already enabled on mount point 'string'.: Cause: Security was already enabled on mount point.; Action: None
ACFS-10631: Security is now enabled on mount point 'string'.: Cause: Security was enabled on mount point.; Action: None
ACFS-10632: Security is already disabled on mount point 'string'.: Cause: Security was already disabled on mount point.; Action: None
ACFS-10633: Security is now disabled on mount point 'string'.: Cause: Security was disabled on mount point.; Action: None
ACFS-10634: Failed to disable security on mount point 'string'.: Cause: Internal error.; Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ACFS-10635: Failed to get security administrator group.: Cause: Internal error.; Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ACFS-10636: Security administrator group retrieved.: Cause: Security administrators group was retrieved.; Action: None
ACFS-10637: File system is not prepared for ACFS security on mount point 'string'.: Cause: File system was not prepared for security operations on mount point.; Action: Execute 'acfsutil sec prepare' to prepare security operation on mount point.
ACFS-10638: Backup and log directories created.: Cause: Backup and log directories were created.; Action: None
ACFS-10639: Failed to create directory 'string' on mount point 'string'.: Cause: Internal error.; Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ACFS-10640: Failed to create log directory on mount point 'string'.: Cause: Internal error.; Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ACFS-10641: Failed to create backup directory on mount point 'string'.: Cause: Internal error.; Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ACFS-10643: Security is already enabled on realm 'string'.: Cause: Security was already enabled on realm.; Action: None
ACFS-10644: Security is already disabled on realm 'string'.: Cause: Security was already disabled on realm.; Action: None
ACFS-10645: Failed to set owner of file 'string' to 'string'.: Cause: Current user is not owner of the file.; Action: Login as the file owner and re-run the command.
ACFS-10646: Failed to create secbackup.xml file on mount point 'string'.: Cause: Internal error.; Action: Contact Oracle Support Services.
ACFS-10647: Current user does not have system administrative privileges to initialize ACFS encryption.: Cause: The user was not part of system administrators group.; Action: Run 'acfsutil encr init' with administrative privileges.
ACFS-10648: ACFS security already initialized, recovery failed.: Cause: Previous execution of 'acfsutil sec init' had failed. Recovery actions also failed in the subsequent execution of 'acfsutil sec init'.; Action: Contact Oracle support services.
ACFS-10649: ACFS encryption already initialized, recovery failed.: Cause: Previous execution of 'acfsutil encr init' had failed. Recovery actions also failed in the subsequent execution of 'acfsutil encr init'.; Action: Contact Oracle support services.
ACFS-10650: Invalid file name 'string' for ACFS security metadata.: Cause: The file was invalid for saving or loading ACFS security metadata.; Action: Specify a valid file.
ACFS-10651: Failed to save ACFS security metadata of mount point 'string'.: Cause: Internal error; Action: Contact Oracle Support Services.
ACFS-10652: Saved ACFS security metadata of mount point 'string'.: Cause: ACFS security metadata of mount point '%s' was saved.; Action: None
ACFS-10653: Failed to save ACFS security string metadata of mount point 'string'.: Cause: Internal error.; Action: Contact Oracle Support Services.
ACFS-10654: Directory '.Security' does not exist on mount point 'string'.: Cause: Mount point was not prepared for ACFS security.; Action: Execute 'acfsutil sec prepare' on the mount point.
ACFS-10655: Failed to get hostname.: Cause: Internal error.; Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ACFS-10656: Failed to get timestamp.: Cause: Internal error.; Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ACFS-10657: Absolute and relative pathnames are not allowed with '-p' option.: Cause: Filename was provided with absolute or relative path.; Action: Specify only name of the file with '-p' option and retry.
ACFS-10658: ACFS Security has been initialized on the cluster with user 'string' as the initial Security Administrator and 'string' as the Security Administrator group.: Cause: An administrator initialized ACFS Security on the cluster.; Action: None
ACFS-10659: Cannot destroy realm 'string' because it is a system-created realm.: Cause: A request to destroy a system-created realm was denied because that operation is not allowed.; Action: None
ACFS-10660: Current user does not have required OS privileges to set ACFS encryption parameters.: Cause: Current user does not have root or administrator privileges to run 'acfsutil encr set'.; Action: Run 'acfsutil encr set' as a user who has root or administrator privileges.
ACFS-10661: Current user does not have required OS privileges to rekey the ACFS encryption parameters.: Cause: Current user does not have root or administrator privileges to run 'acfsutil encr rekey'.; Action: Run 'acfsutil encr rekey' as a user who has root or administrator privileges.
ACFS-10662: Current user 'string' does not have security administrator privileges.: Cause: A command requiring Security Administrator privileges was issued but the user is not in the Security Administrators group.; Action: Add current user to the Security Administrators group or log on as a user who has the required privileges, then retry the command.
ACFS-10663: User name 'string' is not a fully qualified name.: Cause: Fully qualified name was not specified. The supplied user name was not prefixed with a Windows Server Domain name.; Action: Specify a domain user name prefixed with Windows Server Domain name. For example, HOSPITAL-ADMIN\Alice where HOSPITAL-ADMIN is a Windows Server Domain name and Alice is the user name.
ACFS-10664: Group name 'string' is not a fully qualified name.: Cause: Fully qualified name was not specified.The supplied group name was not prefixed with a Windows Server Domain name.; Action: Specify domain group name prefixed with Windows Server Domain name. For example: HOSPITAL-ADMIN\Doctors where HOSPITAL-ADMIN is a Windows Server Domain name and Doctors is the group name.
ACFS-10665: Group 'string' is a local group and not a Windows Server Domain group.: Cause: Specified group was not a Windows Server Domain group.; Action: Specify a domain group name prefixed with Windows Server Domain name. For example, HOSPITAL-ADMIN\Doctors, where HOSPITAL-ADMIN is a Windows Server Domain name and Doctors is the group name.
ACFS-10666: User 'string' is a local user and not a Windows Server Domain user.: Cause: Specified user was not a Windows Server Domain user.; Action: Specify a domain user name prefixed with Windows Server Domain name. For example, HOSPITAL-ADMIN\Alice where HOSPITAL-ADMIN is a Windows Server Domain name and Alice is the user name.
ACFS-10667: Windows Server Domain 'string' does not exist.: Cause: Failed to get Windows Server Domain controller for the domain either because of not access to domain or domain does not exist.; Action: Specify the name of an existing Windows Server Domain.
ACFS-10675: Failed to load ACFS security metadata on mount point 'string'.: Cause: Internal error.; Action: Contact Oracle Support Services.
ACFS-10676: Loaded ACFS security metadata on mount point 'string'.: Cause: ACFS security metadata was loaded on mount point.; Action: None
ACFS-10677: Failed to load string on mount point 'string'.: Cause: Internal error.; Action: Contact Oracle Support Services.
ACFS-10679: Unable to resolve the user id 'string'.: Cause: The user was not found on the system.; Action: None
ACFS-10680: XDK version not compatible.: Cause: Oracle XDK version was incompatible.; Action: Install the correct Oracle XDK version and retry.
ACFS-10681: ACFS kernel version is not compatible. The kernel version on the system is 'string' while the expected kernel version is 'string' or above.: Cause: ACFS kernel version was incompatible.; Action: Install the correct version and retry.
ACFS-10682: Kernel major version is not compatible.: Cause: Kernel major version was incompatible.; Action: Install the correct version and retry.
ACFS-10683: Kernel release version is not compatible.: Cause: Kernel release version was incompatible.; Action: Install the correct version and retry.
ACFS-10684: Kernel update version is not compatible.: Cause: Kernel update version was incompatible.; Action: Install the correct version and retry.
ACFS-10685: Kernel port update version is not compatible.: Cause: Kernel port version was incompatible.; Action: Install the correct version and retry.
ACFS-10686: Kernel patch version is not compatible.: Cause: Kernel patch version was incompatible.; Action: Install the correct version and retry.
ACFS-10687: Kernel one off version is not compatible.: Cause: Kernel one off version was incompatible.; Action: Install the correct version and retry.
ACFS-10688: Unable to resolve the group id 'string'.: Cause: The OS group ID could not be resolved to a name. Usually this occurs because the OS group has been removed.; Action: None
ACFS-10689: Failed to update security administrators information in the driver, some of the subsequent commands may fail.: Cause: Updating driver security administrator data failed during mount. The mount completes, but subsequent security commands may be affected. This is an internal error.; Action: Contact Oracle Support Services.
ACFS-10690: Cannot edit groups in realm 'string'.: Cause: No changes were made to the groups in the realm as the operation is not allowed.; Action: None
ACFS-10691: Changed ACFS Security administrator password for current user.: Cause: Informational.; Action: None
ACFS-10700: Failed to store volume encryption key.: Cause: Internal error.; Action: Refer to encryption log in '<mount_point>/.Security/encryption/logs/encr-<host_name>.log'.
ACFS-10701: Failed to get volume encryption key.: Cause: Internal error.; Action: Refer to encryption log in '<mount_point>/.Security/encryption/logs/encr-<host_name>.log'.
ACFS-10702: Snapshots exist for the file system mounted on 'string'. New encryption parameters will not apply to files in these snapshots.: Cause: One or more snapshots existed for the file system when this encryption operation was done. The new encryption parameters set by this command will apply only to new files created in the file system and not to existing files in any snapshots. Note that none of the encryption commands affect files in any snapshots. Any snapshots created after the command was run will use the new encryption parameters.; Action: None
ACFS-10703: Snapshots exist for the file system mounted on 'string'. Encryption status of files in these snapshots will not change.: Cause: One or more snapshots existed for the file system when this encryption operation was done. The operation did not modify file data in any snapshots on the file system, so this data may still be available on disk unencrypted. Note that none of the encryption commands affect files in any snapshots.; Action: If you plan to use snapshots and encryption together, it is recommended that any snapshots be created after encrypting data on the file system. If the data on the file system was encrypted when some snapshots already existed, you may delete existing snapshots to ensure that data is not available in unencrypted form via any files in these snapshots.
ACFS-10704: Snapshots exist for the file system mounted on 'string'. Encryption keys of files in these snapshots will not be rekeyed.: Cause: One or more snapshots existed for the file system when this encryption operation was done. The operation did not rekey FEKs of files in any snapshots of the file system, so the FEKs of these files will continue to remain encrypted with the old parameters. Note that none of the encryption commands affect files in any snapshots.; Action: To ensure that all FEKs, including those of files in any snapshots, are encrypted with the new encryption parameters, this command should be run when the file system has no snapshots. If the command was run when some snapshots existed you may delete these snapshots. Any snapshots created after the command was run will use the new encryption parameters.
ACFS-10705: Cannot perform encryption operation because volume encryption keys for the file system mounted at 'string' are not available.: Cause: The encryption operation failed because the required volume encryption keys for the file system were not available to the ACFS file system driver. This could happen because an incorrect key store password was supplied during mount or because of some other error during mount.; Action: Remount the file system, providing the correct password during the mount operation if required. Address any other errors reported during mount. If the issue persists, contact Oracle Support Services.
ACFS-10706: Cannot perform encryption operation because an encryption undo operation is in progress.: Cause: The encryption operation failed because the system administrator was running encryption undo ('acfsutil encr set -u') on the file system. It is also possible that a previous encryption undo operation had not completed cleanly.; Action: There is no action to be taken by users who are not system administrators. If this message is seen by a system administrator and an encryption undo operation is not in progress, then a previous encryption operation did not complete properly. Run the 'acfsutil encr set -u' command again to complete the operation.
ACFS-10707: Cannot perform encryption undo operation because file system level encryption is on.: Cause: The encryption undo operation failed because file system level encryption was on.; Action: Turn file system level encryption off and retry the operation.
ACFS-10708: An earlier key store migrate operation did not complete. Provide the same password as the one used in the previous attempt.: Cause: An earlier run of 'acfsutil keystore migrate' command did not complete.; Action: When prompted for a password (ACFS-10349), provide the same password as the one used in the previous attempt.
ACFS-10709: Existing ACFS encryption key store is already password-protected.: Cause: Informational.; Action: None
ACFS-10710: Existing ACFS encryption key store is already not password-protected.: Cause: Informational.; Action: None
ACFS-10711: Recovery of ACFS encryption key store completed successfully.: Cause: Informational.; Action: None
ACFS-10712: ACFS encryption key store migration to password-protected key store completed successfully.: Cause: Informational.; Action: None
ACFS-10713: ACFS encryption key store migration to password-free key store completed successfully.: Cause: Informational.; Action: None
ACFS-10714: The environment variable OKV_HOME is not set.: Cause: The attempt to access the Oracle key vault server to obtain the volume encryption keys failed because the OKV_HOME environment variable was not set.; Action: Set the environment variable OKV_HOME and retry the command.
ACFS-10715: failed to find the PKCS library in path 'string': Cause: The attempt to access the Oracle key vault server to obtain the volume encryption keys failed because the PKCS library was not found in '$OKV_HOME/lib'.; Action: Ensure that the OKV_HOME environment variable is set to point to the path that contains OKV client data, including the PKCS library. If not, set OKV_HOME and retry the command. If the problem persists, contact Oracle Support Services.
ACFS-10716: failed to load the PKCS library: Cause: The attempt to access the Oracle key vault server to obtain the volume encryption keys failed because the OKV PKCS library could not be loaded from '$OKV_HOME/lib'.; Action: Ensure that the OKV_HOME environment variable is set to point to the path that contains OKV client data, including the PKCS library. If not, set OKV_HOME and retry the command. If the problem persists, contact Oracle Support Services.
ACFS-10717: failed to find Oracle Key Vault (OKV) client configuration file: Cause: The attempt to access the Oracle key vault server to obtain the volume encryption keys failed because the OKV client configuration file, okvclient.ora, was not found in '$OKV_HOME/conf'.; Action: Ensure that the OKV_HOME environment variable is set to point to the path that contains OKV client data, including the OKV client configuration file, okvclient.ora. If not, set OKV_HOME and retry the command. If the problem persists, contact Oracle Support Services.
ACFS-10718: failed to login to OKV server: Cause: A login attempt to Oracle Key Vault (OKV) server failed.; Action: Ensure that correct password is provided, verify okvclient.ora file entries for servers, verify both the servers are still running, and then retry. If the problem persists, contact Oracle Support Services.
ACFS-10719: failed to store encryption keys in file system wallet: Cause: Internal error.; Action: Contact Oracle Support Services.
ACFS-10720: Key store must be either SSO, PKCS, or OKV.: Cause: An attempt to store an encryption key was rejected because the specified key store was not one of: SSO, PKCS or OKV.; Action: Retry the command specifying either SSO, PKCS, or OKV as the key store.
ACFS-10721: failed to save encryption keys, file system wallet already exists in directory 'string': Cause: An attempt to create a new wallet and save encryption keys in it failed because the wallet already existed in the said location.; Action: Delete or move the wallet and retry the command.
ACFS-10722: Current user does not have system administrative privileges to change password for ACFS encryption key store.: Cause: The user was not part of system administrators group.; Action: Run 'acfsutil encr passwd' with administrative privileges.
ACFS-10723: Password for ACFS encryption key store has been changed.: Cause: Informational.; Action: None
ACFS-10724: ACFS encryption key store does not yet have a password, must first migrate key store from SSO to PKCS via 'acfsutil keystore migrate': Cause: An attempt to change the password for the ACFS encryption key store was rejected because the ACFS encryption key store does not currently have a password.; Action: Migrate the ACFS encryption key store from SSO to PKCS via 'acfsutil keystore migrate', which will add a password to the ACFS encryption key store.
ACFS-10725: Failed to start encryption logging on mount point 'string'.: Cause: Internal error.; Action: Contact Oracle Support Services.
ACFS-10726: Failed to start security logging on mount point 'string'.: Cause: Internal error.; Action: Contact Oracle Support Services.
ACFS-10727: Failed to start global security and encryption logging.: Cause: Global security and encryption logging services could not be started. The log file for this node will not be updated.; Action: n/a
ACFS-10728: ACFS encryption logging directory not found on mount point 'string'.: Cause: The ACFS encryption logging directory '<mount_point>/.Security/encryption/logs/' could not be opened.; Action: Ensure the logging directory exists and the system administrator can open and create files in this directory, then unmount the file system and remount it manually to restore logging functionality.
ACFS-10729: ACFS security logging directory not found on mount point 'string'.: Cause: The ACFS security logging directory '<mount_point>/.Security/realm/logs/' could not be opened.; Action: Ensure the logging directory exists and the security administrator can open and create files in this directory, then unmount the file system and remount it manually to restore logging functionality.
ACFS-10730: ACFS security and encryption logging directory not found in CRS_HOME.: Cause: The ACFS security and encryption logging directory '<CRS_HOME>/log/<host_name>/acfssec' could not be opened.; Action: Ensure the logging directory exists and the system administrator can open and create files in this directory.
ACFS-10731: Could not get local host name, ACFS encryption logging will not be available on mount point 'string'.: Cause: The local host name could not be determined, ACFS encryption logs for this host in '<mount_point>/.Security/encryption/logs/' will not be written.; Action: Ensure the operating system host name is set correctly and the system administrator can read this value, then unmount the file system and remount it manually to restore logging functionality.
ACFS-10732: Could not get local host name, ACFS security logging will not be available on mount point 'string'.: Cause: The local host name could not be determined, ACFS security logs for this host in '<mount_point>/.Security/realm/logs/' will not be written.; Action: Ensure the operating system host name is set correctly and the security administrator can read this value, then unmount the file system and remount it manually to restore logging functionality.
ACFS-10733: Could not get local host name, ACFS security and encryption logging will not be available for this host: Cause: The local host name could not be determined, ACFS security and encryption logs for this host in '<CRS_HOME>/log/<host_name>/acfssec' will not be written.; Action: Ensure the operating system host name is set correctly and the system administrator can read this value.
ACFS-10734: OKV autologin wallet create failed.: Cause: An attempt to create the OKV autologin wallet failed. This is an internal error.; Action: Contact Oracle Support Services.
ACFS-10735: OKV autologin wallet save failed.: Cause: An attempt to save the OKV autologin wallet failed. This is an internal error.; Action: Contact Oracle Support Services.
ACFS-10736: OKV autologin wallet open failed.: Cause: An attempt to open the OKV autologin wallet failed. This is an internal error.; Action: Contact Oracle Support Services.
ACFS-10737: OKV autologin wallet permissions could not be set.: Cause: An attempt to set permissions on the OKV autologin wallet failed. This is an internal error.; Action: Contact Oracle Support Services.
ACFS-10738: OKV password not yet stored in OKV autologin wallet.: Cause: An attempt to change the OKV password stored in the OKV autologin wallet failed because no OKV password has yet been stored.; Action: Store an OKV password in the OKV autologin wallet via 'acfsutil encr init -o'
ACFS-10739: OKV password stored in OKV autologin wallet must be updated.: Cause: The OKV password stored in the OKV autologin wallet must be updated.; Action: Update the OKV password in the OKV autologin wallet via 'acfsutil encr init -o' or 'acfsutil encr passwd -o'
ACFS-10740: The environment variable ORACLE_HOME is not set.: Cause: The attempt to access the Oracle key vault server failed because the ORACLE_HOME environment variable was not set.; Action: Set the environment variable ORACLE_HOME and retry the command.
ACFS-10741: The environment variable ORACLE_SID is not set.: Cause: The attempt to access the Oracle key vault server failed because the ORACLE_SID environment variable was not set.; Action: Set the environment variable ORACLE_SID and retry the command.
ACFS-10742: Environment variable string could not be set.: Cause: An attempt to set the specified environment variable failed. This is an internal error.; Action: Contact Oracle Support Services.
ACFS-10751: Realm_Metadata file has invalid realm record\nfor file:\nstring: Cause: A realm record of the indicated Realm_Metadata file was invalid.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-10753: Realm_Metadata file has no valid realm records\nfor file:\nstring: Cause: The indicated Realm_Metadata file did not contain any valid valid realm records.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-10755: Realm_Metadata file contains invalid realm record data\nfor file:\nstring: Cause: The indicated Realm_Metadata file contained at least one invalid realm record. Refer to the accompanying message(s) for more information on the problem.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-10756: Realm_Metadata file _Private structure is invalid for:\nfor file:\nstring: Cause: The _Private structure of the indicated Realm_Metadata file was invalid. Refer to the accompanying message(s) for more information on the problem.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-10757: Realm_Metadata file has invalid Hash_Table data\nfor file:\nstring: Cause: The Hash_Table of the indicated Realm_Metadata file contained inconsistent data. Refer to the accompanying message(s) for more information on the problem.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-10760: Realm_Metadata file _Private structure has invalid _maxFree value\n found: number minimum: number\nfor structure:\nstring: Cause: The _maxFree property of the indicated _Private metadata structure was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-10761: Realm_Metadata file _Private structure has invalid _freeDataListTail value\n found: number minimum: number\nfor structure:\nstring: Cause: The _freeDataListTail property of the indicated _Private metadata structure was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-10762: Realm_Metadata file node not on _freeDataList\nfor file:\nstring: Cause: One or more of the _security_data nodes of the indicated Realm_Metadata file was not found on the free data node list. The _next property for one or more of the _security_data nodes was incorrect.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-10764: Realm_Metadata file has invalid _security_record for _Administrator default\nfor file:\nstring: Cause: The default _Administrator _security_record of the indicated Security_Metadata file was invalid.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-10766: Realm_Metadata file has no valid realm data records\nfor file:\nstring: Cause: The indicated Realm_Metadata file did not contain any valid valid realm data records.; Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ACFS-10767: Realm_Metadata File Private structure has invalid _freeDataList value\n found: number maximum: number\nfor file:\nstring: Cause: The _freeDataList property of the _Private structure of the indicated Realm_Metadata file was incorrect. The _freeDataList value exceeded the maximum value for this Realm_Metadata file.; Action: If the ACFS Fixer was running, the problem would have been resolved. If only the ACFS Checker was running, then run the ACFS Fixer to resolve the problem.
ACFS-10768: Number of realms created on mount point 'string' has reached the limit number.: Cause: A request to create a realm was denied because the number of realms created on the mount point has reached the limit.; Action: Destroy any of the unused realms and retry the command.
ACFS-10769: Number of rulesets created on mount point 'string' has reached the limit number.: Cause: A request to create a ruleset was denied because the number of rulesets created on the mount point has reached the limit.; Action: Destroy any of the unused rulesets and retry the command.
ACFS-10770: Number of rules created on mount point 'string' has reached the limit number.: Cause: A request to create a rule was denied because the number of rules created on the mount point has reached the limit.; Action: Destroy any of the unused rules and retry the command.
ACFS-10771: Number of realms that file 'string' is part of has reached the limit number.: Cause: A request to add the file to a realm was denied because the number of realms that the file is part of has reached the limit.; Action: Remove the file from one or more realms and retry the command.
ACFS-10772: Security at the realm level will not be in effect until file system-level security is enabled.: Cause: Security is disabled at the file system level. When file system-level security is disabled, enabling realm-level security does not enable the authorization checks provided by the realm.; Action: Enable Security at file system level.
ACFS-10773: Unable to lock ACFS Security wallet.: Cause: The ACFS Security wallet lock was not acquired.; Action: Verify that Cluster Ready Services(CRS) stack is up by executing 'crsctl check crs' and Cluster Synchronization Services(CSS) is running by executing 'crsctl check css'. If the CRS stack is not up, check with the CRS administrator to bring it up. If it does not resolve the problem contact Oracle Support Services.
ACFS-10774: Unable to unlock ACFS Security wallet.: Cause: The ACFS Security wallet lock was not released.; Action: Verify that Cluster Ready Services(CRS) stack is up by executing 'crsctl check crs' and Cluster Synchronization Services(CSS) is running by executing 'crsctl check css'. If the CRS stack is not up, check with the CRS administrator to bring it up. If it does not resolve the problem contact Oracle Support Services.
ACFS-10775: Cannot proceed as another instance of 'acfsutil' command is updating the security administrator information.: Cause: ACFS Security wallet is locked by another instance of 'acfsutil' command.; Action: Retry the command after some time.
ACFS-10776: Invalid 'acfsutil' version 'string': Cause: Internal error.; Action: Contact Oracle Support Services.
ACFS-10777: Unable to lock ACFS encryption key store.: Cause: The ACFS encryption key store lock could not be acquired.; Action: Verify that Cluster Ready Services(CRS) stack is up by executing 'crsctl check crs' and Cluster Synchronization Services(CSS) is running by executing 'crsctl check css'. If the CRS stack is not up, check with the CRS administrator to bring it up. If it does not resolve the problem contact Oracle Support Services.
ACFS-10778: Unable to unlock ACFS encryption key store.: Cause: The ACFS encryption key store lock was not released.; Action: Verify that Cluster Ready Services(CRS) stack is up by executing 'crsctl check crs' and Cluster Synchronization Services(CSS) is running by executing 'crsctl check css'. If the CRS stack is not up, check with the CRS administrator to bring it up. If it does not resolve the problem contact Oracle Support Services.
ACFS-10779: Cannot proceed as another instance of 'acfsutil' command is updating the encryption key store.: Cause: An acfsutil encryption request found the ACFS encryption key store locked by another instance of the acfsutil command.; Action: Retry the command after some time.
ACFS-10780: The file system mounted on 'string' has been prepared for ACFS Security, undo ACFS Security first.: Cause: ACFS Encryption cannot be undone when the file system has been prepared for ACFS Security.; Action: Undo ACFS Security prepare on the mount point by executing 'acfsutil sec prepare -m <mount_point> -u' as security administrator and retry.
ACFS-10781: could not undo ACFS security or encryption for the file system mounted on path 'string' because of existing snapshots: Cause: An attempt to undo ACFS security or encryption for the indicated file system failed because there were existing snapshots (created by user or created as part of replication V2 being active) for the file system. ACFS security and encryption can only be undone for a file system with no snapshots. This message may be displayed before or after all files have been decrypted using the command 'acfsutil encr set -u'. In either case, the file system retains its encryption 'prepared' state and files can be encrypted without running 'acfsutil encr set' again.; Action: Remove all snapshots by executing 'acfsutil snap delete', and also check if replication V2 is active, terminate replication on the file system and retry.
ACFS-10782: The file system mounted on 'string' has not been prepared for ACFS Security, nothing to be undone.: Cause: The file system was not prepared for ACFS Security.; Action: None
ACFS-10783: ACFS Encryption is not set on the file system mounted on 'string', nothing to be undone.: Cause: ACFS Encryption was not set on the file system.; Action: None
ACFS-10784: Could not destroy all realms, unable to undo ACFS Security.: Cause: All realms were not destroyed.; Action: Re-execute the command.
ACFS-10785: Could not destroy all rules, unable to undo ACFS Security.: Cause: All rules were not destroyed.; Action: Re-execute the command.
ACFS-10786: Could not destroy all rulesets, unable to undo ACFS Security.: Cause: All rulesets were not destroyed; Action: Re-execute the command.
ACFS-10787: Failed to prepare ACFS Security on mount point 'string' as replication is active on this mount point.: Cause: Replication was active on the mount point. ACFS Replication and ACFS Security cannot co-exist on the same mount point.; Action: Terminate replication by using command 'acfsutil repl term' and then retry.
ACFS-10788: ACFS Security undo operation on mount point 'string' completed.: Cause: ACFS Security undo operation on the mount point was completed.; Action: None
ACFS-10789: Failed to undo ACFS Security on mount point 'string'.: Cause: Internal error.; Action: Contact Oracle Support Services.
ACFS-10790: Failed to set ACFS Encryption on mount point 'string' as replication is active on this mount point.: Cause: Replication was active on the mount point. ACFS Replication and ACFS Encryption cannot co-exist on the same mount point.; Action: Terminate replication by using command 'acfsutil repl term' and then retry.
ACFS-10791: Failed to undo ACFS encryption on mount point 'string'.: Cause: Internal error.; Action: Contact Oracle Support Services.
ACFS-10792: Cannot add filter 'string:string' to the cloned realm as the rule set 'string' does not exist on the mount point 'string'.: Cause: Filters could not be added to cloned realm because rule sets were not present on mount point.; Action: Clone rules and rule sets first and then add command rules to the cloned realm using 'sec realm add' command.
ACFS-10793: File objects cannot be added to cloned realm as file objects do not exist on destination mount point.: Cause: File objects could not be added to cloned realm because file objects were not present on destination mount point.; Action: Copy File objects to destination mount point and then add file objects to the cloned realm using 'sec realm add' command.
ACFS-10794: File 'string' does not exist on mount point 'string'.: Cause: Information of file could not be obtained, because either file name specified is not correct or file does not exist on given mount point.; Action: Specify the correct file name or specify the mount point where the file exists.
ACFS-10795: Cannot load ACFS security meta data because the destination mount point 'string' already has some user-created rules, rule sets or realms.: Cause: ACFS security load was not done as the destination mount point had some user created rules, rule sets or realms.; Action: Run 'acfsutil sec prepare -u' followed by 'acfsutil sec prepare' on the destination mount point and then retry the command, or use a file system with no security objects (like realms, rules and rule sets) except system realms.
ACFS-10796: A prior failed encryption initialization cannot be recovered for this request because the prior initialization specified a password-protected key store.: Cause: A prior failed encryption initialization was not recovered for this request because the prior initialization specified a password-protected key store.; Action: Execute the command 'acfsutil encr init' with option 'p'.
ACFS-10797: A prior failed encryption initialization cannot be recovered for this request because the prior initialization specified a non-password-protected key store.: Cause: A prior failed encryption initialization was not recovered for this request because the prior initialization specified a non-password-protected key store.; Action: Execute the command "acfsutil encr init' without option 'p'.
ACFS-10798: ACFS Encryption undo operation on mount point 'string' completed.: Cause: ACFS Encryption undo operation on the mount point was completed.; Action: None
ACFS-10799: For cloning realms with 'string' option, destination mount point must be same as source mount point.: Cause: Cloning of file system objects is not supported if destination mount point is different from source mount point.; Action: Run 'acfsutil sec realm clone' without -f option, copy file objects to the destination mount point, and then add files using 'acfsutil sec realm add' command.
ACFS-10800: Failed to complete ACFS Security undo operation on mount point 'string'.: Cause: ACFS Security undo operation did not complete because some rules, rulesets, or realms exist for the given file system.; Action: Retry the operation after making sure that no other 'acfsutil sec' commands are running for the given file system.
ACFS-10801: failed to acquire a lock on ACFS security wallet: Cause: The ACFS security wallet could not be initialized because the lock on the wallet could not be obtained.; Action: Verify that Cluster Ready Services(CRS) stack is up by executing 'crsctl check crs' and Cluster Synchronization Services(CSS) is running by executing 'crsctl check css'. If the CRS stack is not up, check with the CRS administrator to bring it up. If this does not resolve the problem contact Oracle Support Services.
ACFS-10802: unable to release the lock being held on the ACFS security wallet: Cause: After security initialization, the lock on ACFS security wallet could not be released.; Action: Verify that Cluster Ready Services(CRS) stack is up by executing 'crsctl check crs' and Cluster Synchronization Services(CSS) is running by executing 'crsctl check css'. If the CRS stack is not up, check with the CRS administrator to bring it up. If this does not resolve the problem contact Oracle Support Services.
ACFS-10803: cannot proceed because another instance of 'acfsutil' command is updating the ACFS security wallet: Cause: An attempt to update the ACFS security wallet failed because the ACFS security wallet was locked by another instance of the acfsutil command.; Action: Retry the command later.
ACFS-10804: ACFS Encryption is not supported.: Cause: ACFS Encryption is not supported.; Action: None
ACFS-10805: Unexpectedly found both PKCS and SSO wallets for the encrypted file system.: Cause: Both PKCS and SSO wallets exist for the encrypted file system.; Action: Contact Oracle Support Services.
ACFS-10806: Neither PKCS nor SSO wallet was found for the encrypted file system.: Cause: Encryption wallet could not be found for the encrypted file system.; Action: Contact Oracle Support Services.
ACFS-10807: Error initializing Oracle Cluster Registry context.: Cause: The Oracle Cluster Registry could not be accessed.; Action: Run ocrcheck to verify the Oracle Cluster Registry is functioning properly.
ACFS-10808: Oracle Cluster Registry keys required for this operation could not be accessed.: Cause: Oracle Cluster Registry keys required for this operation could not be accessed.; Action: Run ocrcheck to verify the Oracle Cluster Registry is functioning properly.
ACFS-10809: ACFS Encryption is not supported for path string.: Cause: ACFS Encryption is not supported for special paths.; Action: None
ACFS-10810: Failed to process supplied password input.: Cause: An attempt to process the password input failed. This could be due to a premature disconnection from the console or input file.; Action: Retry the operation or contact Oracle Support Services.
ACFS-10811: Oracle Cluster Registry keys required for this operation could not be set.: Cause: An attempt to set the Oracle Cluster Registry keys failed which is required to perform this operation.; Action: Retry the operation or contact Oracle Support Services.
ACFS-10812: Failed to create wallet ID for a new encryption wallet.: Cause: A wallet ID could not be created for a new encryption wallet.; Action: Retry the operation or contact Oracle Support Services.
ACFS-10813: Migration of filesystem to Oracle Key Vault failed to remove all volume encryption keys from OCR keystore.: Cause: Failed to remove the volume encryption keys from OCR keystore after the file system was migrated to Oracle Key Vault.; Action: Retry the operation or contact Oracle Support Services.
ACFS-10814: Migration of filesystem to Oracle Key Vault failed to clear OCR wallet information.: Cause: Failed to clear the OCR wallet information in the filesystem metadata when the encryption keys for the specified file system were migrated from Oracle Cluster Registry to Oracle Key Vault. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated problems, and retry the operation or contact Oracle Support Services.
ACFS-10815: Successfully migrated filesystem from OCR keystore to Oracle Key Vault.: Cause: The filesystem has been successfully migrated from OCR keystore to Oracle Key Vault.; Action: No action needed.
ACFS-10850: Password must have at least number characters.: Cause: The password was not long enough.; Action: Provide the password with number of characters greater than minimum required length.
ACFS-10851: Password must have at least one digit and letter in it.: Cause: The password did not have either a digit or a letter in it.; Action: Provide a password containing at least one digit and letter.
ACFS-10901: Failed to add the read-only snapshot file 'string' to realm 'string'.: Cause: A file specified for addition to a security realm was a read-only snapshot file.; Action: None
ACFS-10902: Failed to add the read-write snapshot file 'string' to realm 'string'.: Cause: A file specified for addition to a security realm was a read-write snapshot file.; Action: None
ACFS-10903: Snapshot 'string' of mount point 'string' is not prepared for ACFS Security.: Cause: Snapshot was not prepared for security operations on mount point.; Action: None
ACFS-10914: Security is already enabled in snapshot 'string' of mount point 'string'.: Cause: Security was already enabled in snasphot of mount point.; Action: None
ACFS-10915: Security is already enabled on realm 'string' in snapshot 'string' of mount point 'string': Cause: Security was already enabled on realm in snapshot.; Action: None
ACFS-10916: Security is now enabled in snapshot 'string' of mount point 'string'.: Cause: Security was enabled in snapshot of mount point.; Action: None
ACFS-10917: Failed to enable security in snapshot 'string' of mount point 'string'.: Cause: Internal error.; Action: Contact Oracle Support Services.
ACFS-10918: Security is already disabled in snapshot 'string' of mount point 'string'.: Cause: Security was already disabled in snapshot of mount point.; Action: None
ACFS-10919: Security is already disabled on realm 'string' in snapshot 'string' of mount point 'string'.: Cause: Security was already disabled on realm in snapshot.; Action: None
ACFS-10920: Failed to disable security in snapshot 'string' of mount point 'string'.: Cause: Internal error.; Action: Contact Oracle Support Services.
ACFS-10921: Realm 'string' not found in snapshot 'string' of mount point 'string'.: Cause: Realm was not found in snapshot of mount point.; Action: Ensure that the realm exists using the command 'acfsutil sec info -m <mount_point> -S <snapshot_name> -n'.
ACFS-10922: Failed to get security related information of snapshot 'string' of mount point 'string'.: Cause: Internal error.; Action: Contact Oracle Support Services.
ACFS-10923: Failed to get users for realm 'string' in snapshot 'string' of mount point 'string'.: Cause: Internal error.; Action: Contact Oracle Support Services.
ACFS-10924: Failed to get groups for realm 'string' in snapshot 'string' of mount point 'string'.: Cause: Internal error.; Action: Contact Oracle Support Services.
ACFS-10925: Failed to get realm encryption attributes of realm 'string' in snapshot 'string' of mount point 'string'.: Cause: Internal error.; Action: Contact Oracle Support Services.
ACFS-10926: Attributes of realm 'string' in snapshot 'string' of mount point 'string' retrieved.: Cause: Attributes of realm in snapshot were retrieved.; Action: None
ACFS-10927: Failed to get all rules in snapshot 'string' of mount point 'string'.: Cause: Internal error.; Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ACFS-10928: Failed to get information of rule 'string' in snapshot 'string' of mount point 'string'.: Cause: Internal error.; Action: Contact Oracle Support Services.
ACFS-10929: Rule 'string' not found in snapshot 'string' of mount point 'string'.: Cause: Rule was not found in the snapshot.; Action: Ensure that the rule exists by executing 'acfsutil sec info -m <mount_point> -S <snapshot_name> -l'.
ACFS-10930: Failed to get all rule sets in snapshot 'string' of mount point 'string'.: Cause: Internal error.; Action: Contact Oracle Support Services.
ACFS-10931: Failed to get rules for rule set 'string' in snapshot 'string' of mount point 'string'.: Cause: Internal error.; Action: Contact Oracle Support Services.
ACFS-10932: Rule set 'string' not found in snapshot 'string' of mount point 'string'.: Cause: Rule set was not found in snapshot of mount point.; Action: Ensure that the rule set exists by executing 'acfsutil sec info -m <mount_point> -S <snapshot_name> -s'.
ACFS-10933: Failed to delete the read-only snapshot file 'string' from realm 'string'.: Cause: Security operations cannot be performed on a read-only snapshot file.; Action: None
ACFS-10934: Failed to delete the read-write snapshot file 'string' from realm 'string'.: Cause: Security operations cannot be performed on a read-write snapshot file.; Action: None
ACFS-10935: ACFS Security cannot be enabled or disabled because 'string' is a read-only snapshot: Cause: A request to enable or disable ACFS Security specified a read-only snapshot.; Action: None
ACFS-10936: ACFS Security is now disabled in snapshot 'string' of mount point 'string'.: Cause: Informational.; Action: None
ACFS-10937: ACFS Security is now enabled on realm 'string' in snapshot 'string' of mount point 'string'.: Cause: Informational.; Action: None
ACFS-10938: ACFS Security is now disabled on realm 'string' in snapshot 'string' of mount point 'string'.: Cause: Informational.; Action: None
ACFS-10939: ACFS Security is now enabled on realm 'string' in mount point 'string'.: Cause: Informational.; Action: None
ACFS-10940: ACFS Security is now disabled on realm 'string' in mount point 'string'.: Cause: Informational.; Action: None
ACFS-10941: Failed to create 'string' file on mount point 'string': Cause: An attempt to create a file on the indicated mount point failed, most likely because the user lacked the requisite permission.; Action: Ensure that the user has the required permission and retry. Otherwise, contact Oracle Support Services.
ACFS-10942: Insufficient disk space on mount point 'string': Cause: The requested operation failed because the file system was full.; Action: Resize the file system and retry.
ACFS-10945: ACFS Auditing source 'string' is already enabled on mount point 'string'.: Cause: Informational.; Action: None
ACFS-10946: ACFS Auditing source 'string' is already disabled on mount point 'string'.: Cause: Informational.; Action: None
ACFS-10947: Audit trail on mount point 'string' is marked as read.: Cause: Informational.; Action: None
ACFS-10948: Audit trail on mount point 'string' is archived.: Cause: Informational.; Action: None
ACFS-10949: ACFS Auditing has been initialized on the cluster with 'string' as the Oracle ACFS auditor OS group and 'string' as the Oracle ACFS audit manager OS group.: Cause: Informational.; Action: None
ACFS-10950: Audit trail archive for mount point 'string' is purged.: Cause: Informational.; Action: None
ACFS-10951: Current user does not have system administrative privileges to initialize auditing.: Cause: The user was not part of system administrators group.; Action: Run 'acfsutil audit init' as an OS user with administrative privileges.
ACFS-10952: Auditing already initialized; cannot reinitialize.: Cause: An attempt was made to initialize auditing after it was already initialized.; Action: None
ACFS-10953: Auditing is not initialized.: Cause: A command was issued which requires auditing to be intialized for the cluster, but auditing has not been initialized.; Action: Initialize auditing by reissuing 'acfsutil audit init' command.
ACFS-10954: Failed to enable auditing on mount point 'string'.: Cause: Internal error.; Action: Refer to audit log '<mount_point>/.Security/audit/audit-<host_name>.log'.
ACFS-10955: Failed to disable auditing on mount point 'string'.: Cause: Internal error.; Action: Refer to audit log '<mount_point>/.Security/audit/audit-<host_name>.log'.
ACFS-10956: Failed to enable auditing for realm 'string' on mount point 'string'.: Cause: Internal error.; Action: Refer to audit log '<mount_point>/.Security/audit/audit-<host_name>.log'.
ACFS-10957: Failed to disable auditing for realm 'string' on mount point 'string'.: Cause: Internal error.; Action: Refer to audit log '<mount_point>/.Security/audit/audit-<host_name>.log'.
ACFS-10958: Current user does not have privileges to run audit commands.: Cause: An attempt to execute an audit command was rejected because the attempting user was not a member of the audit managers group or the auditors group.; Action: Retry the command as a user who is part of the audit managers group (for all audit commands except 'audit read') or the auditors group (for 'audit read').
ACFS-10960: Failed to get audit information for the mount point 'string'.: Cause: Internal error.; Action: Contact Oracle Support Services.
ACFS-10961: Failed to get audit manager OS group.: Cause: Internal error.; Action: Contact Oracle Support Services.
ACFS-10962: Failed to get auditor OS group.: Cause: Internal error.; Action: Contact Oracle Support Services.
ACFS-10963: Auditing is not enabled on mount point 'string'.: Cause: A command was issued that requires auditing to be enabled at the file system level, but it is not enabled.; Action: Run 'acfsutil audit enable', and retry the command.
ACFS-10964: Failed to archive audit trail on mount point 'string'.: Cause: Internal error.; Action: Contact Oracle Support Services.
ACFS-10965: Failed to mark audit trail on mount point 'string' as read: Cause: Internal error.; Action: Contact Oracle Support Services.
ACFS-10966: Audit trail on mount point 'string' is already marked as read.: Cause: Audit trail was already marked as read on mount point.; Action: None
ACFS-10967: Audit trail on mount point 'string' not found.: Cause: An 'acfsutil audit' command was issued but auditing has not been initialized.; Action: Run 'acfsutil audit init' as an OS user with administrative privileges, then reissue the original command.
ACFS-10968: Failed to create audit trail XML file 'string' for mount point string.: Cause: Internal error.; Action: Contact Oracle Support Services.
ACFS-10969: Failed to purge audit trail archive file for mount point 'string'.: Cause: Internal error.; Action: Contact Oracle Support Services.
ACFS-10970: Failed to purge audit trail archive because it is not marked 'read' for mount point 'string'.: Cause: Audit trail was not yet marked as 'read' on mount point.; Action: Run 'acfsutil audit read' and retry the command.
ACFS-10971: Current user does not have privileges to run this audit command.: Cause: Command was executed as user who is not part of audit manager OS group.; Action: Run command as user who is part of audit manager OS group.
ACFS-10972: Failed to update audit managers and auditors group information in the driver; some of the subsequent audit related commands may fail.: Cause: Audit Managers and Auditors information was not communicated to the ACFS driver during mount. The mount command was successful but the subsequent audit commands will not work on this host until the problem is corrected.; Action: Contact Oracle Support Services.
ACFS-10973: The ADVM compatibility attribute for the diskgroup must be set to version 'string' to enable auditing on mount point 'string'.: Cause: A security adminstrator or audit manager or administrator attempted to enable auditing, but the 'COMPATIBLE.ADVM' attribute for the disk group had not been upgraded to a supported version.; Action: Use the ASMCA tool or the SQL ALTER DISKGROUP statement to upgrade the COMPATIBLE.ADVM attribute and enable auditing using the 'acfsutil audit enable' command.
ACFS-10974: Auditing cannot be enabled on mount point 'string', because ADVM compatibility is lower than 'string'.: Cause: A security adminstrator or system administrator attempted to enable auditing as part of 'acfsutil sec prepare' or 'acfsutil encr set' which was successful, but auditing could not be enabled because the 'compatible.advm attribute had not been upgraded to a supported version.; Action: Use the ASMCA tool or the SQL ALTER DISKGROUP statement to upgrade the COMPATIBLE.ADVM attribute and enable auditing using the 'acfsutil audit enable' command.
ACFS-10975: Failed to get audit information for realm 'string' on mount point 'string'.: Cause: Internal error.; Action: Contact Oracle Support Services.
ACFS-10976: Failed to create audit trail XML file because the old audit trail XML file exists for mount point 'string'.: Cause: A request to archive the audit trail found an existing audit trail XML file.; Action: Run 'acfsutil audit purge' and retry the command.
ACFS-10977: Auditing is enabled for realm 'string' on mount point 'string'.: Cause: Informational.; Action: None
ACFS-10978: Auditing is disabled for realm 'string' on mount point 'string'.: Cause: Informational.; Action: None
ACFS-10979: Cannot proceed because file system is not prepared for ACFS Security.: Cause: An attempt to enable or disable audit on Security source failed because the file system was not prepare for ACFS Security.; Action: Execute 'acfsutil sec prepare' to prepare ACFS Security on the file system and retry 'acfsutil audit' command.
ACFS-10980: Cannot proceed because file system is not set for ACFS Encryption.: Cause: An attempt to enable or disable audit on Encryption source failed because the file system was not set for ACFS Encryption.; Action: Execute 'acfsutil encr set' to set ACFS Encryption on the file system and retry 'acfsutil audit' command.
ACFS-10998: ACFS Audit not initialized: Cause: ACFS Audit was not initilized.; Action: Run 'acfsutil audit init' command.
ACFS-10999: Audit trail archive file on mount point 'string' was not found.: Cause: An 'acfsutil audit read' command was issued but the audit trail backup file did not exist.; Action: Run 'acfsutil audit archive' as an OS user with Audit Manager privileges, then reissue the original command.
ACFS-11000: ACFS Auditing is already initialized with different Audit Managers and Auditors group.: Cause: Values provided on the command line did not match those with which ACFS Auditing was initialized earlier.; Action: Run 'acfsutil audit init' command with the Audit Managers and Auditors group provided for the previous initialization.
ACFS-11001: Error in parsing command line arguments.: Cause: There was a syntax error is the command line arguments.; Action: Check the command line syntax and re-run the command again.
ACFS-11002: Error: a device name must be supplied with the -l option.: Cause: Either the -l option was not present in the command line or it had no argument.; Action: Make sure you run the command with the '-l device-name' option.
ACFS-11003: AIX ODM initialization failed, odmerr number: Cause: AIX ODM internal operation error.; Action: Internal error - contact Oracle Customer Support.
ACFS-11004: failed to lock AIX ODM database, odmerr number: Cause: The method could not lock the AIX ODM database.; Action: Check to see what other method has locked it.
ACFS-11005: failed to look up AIX ODM PdDv object class, odmerr number: Cause: The user may lack required permission or the entry may not exist.; Action: Ensure that the object exists and that the user has the required permission; otherwise, contact Oracle Customer Support.
ACFS-11006: failed to open AIX ODM CuDv object class, odmerr number: Cause: The user may lack required permission or the entry may not exist.; Action: Ensure that the object exists and that the user has the required permission; otherwise, contact Oracle Customer Support.
ACFS-11007: failed to add to AIX ODM CuDv object class, odmerr number: Cause: An attempt to add the device's entry to the ODM CuDv object class failed.; Action: Ensure the user has the required permission.
ACFS-11008: failed to close the AIX ODM CuDv object class, odmerr number: Cause: AIX ODM internal operation error.; Action: Contact Oracle Customer Support.
ACFS-11010: failed to look up AIX ODM CuDv object class, odmerr number: Cause: The user may lack required permission or the entry may not exist.; Action: Ensure that the object exists and that the user has the required permission; otherwise, contact Oracle Customer Support.
ACFS-11015: failed to load kernel extension string, errno number (string): Cause: Loading the kernel extension into the kernel failed.; Action: Check the error message and resolve the error.
ACFS-11017: failed to configure kernel extension string, errno number (string): Cause: Could not configure the device's driver in the kernel.; Action: Internal error - contact Oracle Customer Support.
ACFS-11018: failed to get a major number for device string: Cause: The method could not get a major number for the device.; Action: Internal error - contact Oracle Customer Support.
ACFS-11019: failed to get a minor number for device string: Cause: The method could not get a minor number for the device.; Action: Internal error - contact Oracle Customer Support.
ACFS-11022: failed to configure device string, errno number (string): Cause: Attempt to configure the device's driver in the kernel got an error.; Action: Internal error - contact Oracle Customer Support.
ACFS-11024: failed to remove the old device file string, errno number (string): Cause: The method failed to remove the device file.; Action: Ensure that the user has permission and no other application is still using the device.
ACFS-11026: failed to create new device file string, errno number (string): Cause: The user may not have permission or a file with the same name already exists.; Action: Ensure that the file does not already exist and that the user has the required permission to create it.
ACFS-11028: failed to set permission of the new device file string, errno number (string): Cause: The method failed to set permission of the device special file.; Action: Ensure the user has the required privilege.
ACFS-11030: failed to set group of the new device file string, errno number (string): Cause: The method failed to set the owning group of the device special file.; Action: Ensure the user has the required privilege.
ACFS-11031: failed to open the ASMADMIN group file, errno number (string): Cause: The method could not open the file containing the group to own the device.; Action: Ensure the installation completed successfully.
ACFS-11032: failed to read from the ASMADMIN group file, errno number (string): Cause: The method could not read the file containing the group to own the device.; Action: Ensure the installation completed successfully.
ACFS-11034: failed to set device state to AVAILABLE, odmerr number: Cause: The method could not change the device's state.; Action: AIX ODM internal error - contact Oracle Customer Support.
ACFS-11036: No operation was performed because device state is string instead of DEFINED.: Cause: The method expected a DEFINED device state.; Action: AIX ODM internal error - contact Oracle Customer Support.
ACFS-11038: failed to unconfigure kernel extension string, errno number (string): Cause: The method could not unconfigure the kernel extension.; Action: Internal error - contact Oracle Customer Support.
ACFS-11040: failed to unload kernel extension string, errno number (string): Cause: The method could not unload the extension from kernel.; Action: Internal error - contact Oracle Customer Support.
ACFS-11044: no minor number was returned for device string: Cause: The operating system did not return a device minor number as requested.; Action: Internal error - contact Oracle Customer Support.
ACFS-11046: failed to set device state to DEFINED, odmerr number: Cause: The method failed to change the device's state.; Action: Contact Oracle Customer Support.
ACFS-11050: failed to delete attributes of device string, odmerr number: Cause: The method failed to remove the device's attributes from the AIX ODM CuAt object class.; Action: Internal AIX ODM error - contact Oracle Customer Support.
ACFS-11052: failed to delete customized object of device string, odmerr number: Cause: The method failed to remove the device's entry from the AIX ODM CuDv object class.; Action: Internal AIX ODM error - contact Oracle Customer Support.
ACFS-11053: failed to release major number for device string: Cause: The method failed to release the device's major number.; Action: Internal error - contact Oracle Customer Support.
ACFS-11055: failed to remove device special file string, errno number (string): Cause: The method failed to remove the device special file.; Action: Check the error message and resolve it.
ACFS-11060: failed to unload kernel extension string: Cause: Could not unload the extension from kernel.; Action: Internal error - contact Oracle Customer Support.
ACFS-11061: failed to look up the group id for group string: Cause: The named group probably does not exist.; Action: Make sure the group exists in the /etc/group file.
ACFS-11062: failed to create directory string, errno number (string): Cause: The directory could not be created.; Action: Check the permission of the base directory to make sure it is writeable.
ACFS-11063: failed to set permission on directory string, errno number (string): Cause: The permission of the directory could not be changed.; Action: Make sure the user has permission to do so.
ACFS-11064: failed to set group on directory string, errno number (string): Cause: The group of the directory could not be changed.; Action: Make sure the user has permission to do so.
ACFS-11065: invalid device minor number number: Cause: The device minor number being used is out of range.; Action: Contact Oracle Customer Support.
ACFS-11066: the ADVM driver is not loaded: Cause: The ADVM driver is expected to exist in the kernel but it does not.; Action: Load the ADVM driver and then try it again.
ACFS-11067: directory /dev/asm does not exist or is not accessible, errno number (string): Cause: The ADVM driver probably has not been successfully loaded.; Action: Load the ADVM driver and then try it again.
ACFS-11068: The state of device string is unknown. No operation was performed.: Cause: Unknown.; Action: Contact Oracle Customer Support.
ACFS-11069: Error: device name is too long, exceeding 255 characters.: Cause: The chosen device name exceeds the limit of 255 characters.; Action: Use a device name that is shorter than the limit.
ACFS-11078: unable to obtain cluster information for local node: Cause: An internal ioctl operation to access cluster information failed. This message is accompanied by other messages providing details on the error.; Action: Correct the problem indicated by the other messages. If the cause of the problem is unclear, contact Oracle Support Services.
ACFS-11083: insufficient OS kernel resources to defragment file string: Cause: An attempted defragment operation failed due to insufficient kernel resources.; Action: Reduce the load activity on the system and retry the defragment.
ACFS-11084: no space left on the file system: Cause: A defragment request failed because the file system was full.; Action: Delete unnecessary files from the file system to free up space, resize the file system, or delete snapshots from the file system if any exist.
ACFS-11085: insufficient privileges to defragment file string: Cause: The caller does not have sufficient privileges to perform the defragment command on the indicated file. Write access is required for 'acfsutil defrag file'. Read access is required for 'acfsutil defrag file -i'.; Action: Obtain the required access rights for the indicated file.
ACFS-11086: The specified path string is not a regular file.: Cause: An attempted defragment operation was rejected because the specified pathname was not a regular file.; Action: Retry the command specifying the pathname of a regular file.
ACFS-11087: The specified path string is not a directory.: Cause: An attempted defragment operation was rejected because the specified pathname was not a directory.; Action: Retry the command specifying a directory path.
ACFS-11088: caught interrupt; stop defragmenting file string: Cause: Informational.; Action: None
ACFS-11089: failed to read from or write to file string: Cause: During defragmentation processing for the indicated file, an attempt to read or write data to disk failed.; Action: Verify that the file system is online and retry the command. If the command still fails, run fsck (Unix or Linux) or acfschkdsk.exe (Windows), before retrying the command.
ACFS-11090: failed to defragment file string: Cause: During defragmentation processing for the indicated file, an internal ioctl request failed. This message is accompanied by other messages providing details on the error.; Action: Correct the problem indicated by the other messages. If the cause of the problem is unclear, contact Oracle Support Services.
ACFS-11091: unable to rename snapshot string because it is replication-specific: Cause: An attempt to rename a snapshot failed because it specified a replication-specific snapshot.; Action: Reconsider the need for the request, or specifiy a snapshot that is not associated with replication.
ACFS-11092: Snapshot name string already exists.: Cause: The snapshot rename operation failed because the newly designated snapshot name was in use by another snapshot.; Action: Rename or delete the conflicting snapshot and then re-issue the original 'acfsutil snap rename' command.
ACFS-11095: 'acfsutil defrag' command is not supported for the current ADVM compatibility version. Version string is required.: Cause: The 'acfsutil defrag' command was rejected because the ADVM disk group compatibility had not been upgraded to the indicated version, which is required for that command.; Action: Use the ASMCA tool or the SQL ALTER DISKGROUP statement to upgrade the disk group compatibility (COMPATIBLE.ADVM attribute) to the specified version and then re-issue the original 'acfsutil defrag' command. If the disk group compatibility cannot be upgraded, update the ACFS compatibility level using the 'acfsutil compat set' command and then re-issue the original 'acfsutil defrag' command.
ACFS-11104: insufficient OS kernel resources to perform the command string: Cause: An attempt to execute the command 'acfsutil volstate' failed due to insufficient kernel resources.; Action: Reduce the load on the system and retry the command.
ACFS-11105: insufficient privileges to perform the command string: Cause: The caller does not have sufficient privileges to perform the command on the indicated mountpoint. Write access is required for 'acfsutil volstate -s'. Write access is required for 'acfsutil volstate -c'.; Action: Obtain the required access rights for the indicated mountpoint and retry the command.
ACFS-11106: failed to perform the command string: Cause: While accessing the volume, an internal ioctl request failed. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.
ACFS-11108: Local node is running Oracle SIHA stack.\n: Cause: Informational.; Action: None
ACFS-11109: Local node is not a member of an ACFS cluster.\n: Cause: Informational.; Action: None
ACFS-11111: string: Cause: None; Action: None
ACFS-12002: reclaiming snap remaster released storage: Cause: The 'acfsutil snap remaster' command has replaced the master file system with the remastered snapshot, releasing all the master's unique storage. In addition, any other snapshots that existed on the volume have also been removed, releasing all their unique storage. This storage was being marked as available in the Global_BitMap.; Action: None
ACFS-12003: 'snap remaster' phase: number\n: Cause: The indicated 'snap remaster' conversion phase has started.; Action: None
ACFS-12004: \ninvoking ACFS Checker, which will check the remastered snapshot file system, and ACFS Fixer, which will reclaim released storage\n: Cause: The ACFS Checker and the ACFS Fixer were reclaiming the storage released when the original master file system and other snapshots were deleted.; Action: None
ACFS-12005: \nSnapshot 'string' has been remastered as the master file system.\n: Cause: The specified snapshot has been remastered as the master file system. The original master file system and all the other snapshots have been deleted.; Action: None
ACFS-12006: Not enough free space to encrypt/decrypt/rekey file 'string': Cause: An attempt was made to encrypt, decrypt or rekey a file larger than the amount of free space remaining in the file system.; Action: Free more space in the file system, then retry the operation.
ACFS-12200: missing required snapshot name: Cause: A 'snap remaster' command was issued without a required argument.; Action: Specify the name of the snapshot to remaster.
ACFS-12201: Volume signature 'string' is invalid for snap remastering.: Cause: The volume signature indicated the volume was not in a state where 'snap remaster' can be performed.; Action: Make sure the volume is unmounted and that ACFS Checker has run successfully.
ACFS-12202: Volume signature indicates 'snap remaster' in progress.\n Signature: 'string'\n Use 'acfsutil snap remaster stringc string'\n to complete the 'snap remaster'.: Cause: The volume signature indicated that 'snap remaster' was being run on this volume.; Action: Make sure 'snap remaster' is not being run on another node or by another user. If 'snap remaster' was started and then aborted, use the 'acfsutil snap remaster -c device' command to continue interrupted snapshot remastering.
ACFS-12203: Volume signature 'string' indicates 'snap remaster' can be performed.\n However, on-disk 'snap remaster' phase (number) indicates 'snap remaster' is in progress.: Cause: The requested 'snap remaster' failed to run because the on-disk information indicated that another 'snap remaster' was in progress.; Action: Make sure 'snap remaster' is not being run on another node or by another user. If 'snap remaster' was started and then aborted, use the ACFS Fixer to restore the file system to a good starting point.
ACFS-12204: The snap remastering phase 'number' is invalid.\n Valid phase range from number to number.: Cause: The on-disk snap remastering conversion phase had an invalid value.; Action: Use the ACFS Fixer to restore the file system to a good starting point. Report this error to Oracle Support Services.
ACFS-12205: Snap remaster request for snapshot 'string' declined.\n\n: Cause: The user responded negatively when prompted to confirm the snapshot remastering.; Action: None
ACFS-12206: failed to fetch the ACFS Global metadata directory: Cause: Snap remaster failed to read the file system's ACFS Global metadata directory. Refer to accompanying messages for more information on the problem.; Action: Correct the problem indicated by the other messages. If the solution is not clear, contact Oracle Support Services.
ACFS-12207: failed to access the remastered snapshot 'string' File Entry Table: Cause: The File Entry Table for the snapshot being remastered could not be read. Refer to accompanying messages for more information on the problem.; Action: Correct the problem indicated by the other messages. If the solution is not clear, contact Oracle Support Services.
ACFS-12208: failed to copy the current 'string' file entry into the remastered snapshot 'string' File Entry Table: Cause: Snap remaster failed to copy the indicated file entry into the remastered snapshot File Entry Table. Refer to accompanying messages for more information on the problem.; Action: Correct the problem indicated by the other messages. If the solution is not clear, contact Oracle Support Services.
ACFS-12209: failed to access on-disk structure 'string': Cause: Snap remaster failed to access the indicated on-disk structure. Refer to accompanying messages for more information on the problem.; Action: Correct the problem indicated by the other messages. If the solution is not clear, contact Oracle Support Services.
ACFS-12210: failed to copy remastered snapshot 'string' current File Entry Table file entry to the beginning of the remastered snapshot File Entry Table: Cause: Snap remaster failed to copy the snapshot to be remastered's file entry into the snapshots File Entry Table. Refer to accompanying messages for more information on the problem.; Action: Correct the problem indicated by the other messages. If the solution is not clear, contact Oracle Support Services.
ACFS-12211: failed to snapshot metadata from the snapshot information table: Cause: Snap remaster failed to zero the snapshot metadata for all the other snapshots from the snapshot information table. Refer to accompanying messages for more information on the problem.; Action: Correct the problem indicated by the other messages. If the solution is not clear, contact Oracle Support Services.
ACFS-12212: failed to reset the snapshot map header to indicate number active snapshots: Cause: Snap remaster failed to set the snapshot map header to the indicated number of active snapshots. Refer to accompanying messages for more information on the problem.; Action: Correct the problem indicated by the other messages. If the solution is not clear, contact Oracle Support Services.
ACFS-12213: failed to erase the snapshot entries from the '.ACFSstringsnapsstring' directory: Cause: Snap remaster failed to remove the deleted snapshot names from the indicated directory. Refer to accompanying messages for more information on the problem.; Action: Correct the problem indicated by the other messages. If the solution is not clear, contact Oracle Support Services.
ACFS-12214: failed to remove the remastered snapshot metadata from the snapshot information table: Cause: Snap remaster failed to snapsnot information table metadata for the snapshot being remastered. Refer to accompanying messages for more information on the problem.; Action: Correct the problem indicated by the other messages. If the solution is not clear, contact Oracle Support Services.
ACFS-12215: failed to clear the snapshot storage allocation map: Cause: Snap remaster failed to remove the storage allocations for the deleted snapshots. Refer to accompanying messages for more information on the problem.; Action: Correct the problem indicated by the other messages. If the solution is not clear, contact Oracle Support Services.
ACFS-12216: failed to save the current per-node local directory metadata entries for reuse: Cause: Snap remaster failed to obtain the local directory metadata entries for each cluster node, so that this information could be used in the remastered snapshot. Refer to accompanying messages for more information on the problem.; Action: Correct the problem indicated by the other messages. If the solution is not clear, contact Oracle Support Services.
ACFS-12217: failed to initialize the locator block metadata and local directory block metadata inside the remastered snapshot: Cause: Snap remaster failed to initialize the remastered snapshot locator block metadata and the local directory block metadata using data from the original master. Refer to accompanying messages for more information on the problem.; Action: Correct the problem indicated by the other messages. If the solution is not clear, contact Oracle Support Services.
ACFS-12218: failed to initialize the global directory block inside the remastered snapshot: Cause: Snap remaster failed to initialize the remastered snapshot global directory block for the remastered snapshot. Refer to accompanying messages for more information on the problem.; Action: Correct the problem indicated by the other messages. If the solution is not clear, contact Oracle Support Services.
ACFS-12219: remastering snapshot 'string' failed: Cause: A 'snap remaster' command failed. Refer to accompanying messages for more information on the problem.; Action: Correct the problem indicated by the other messages. If the solution is not clear, contact Oracle Support Services.
ACFS-12220: The continue option failed because there was no incomplete remastered snapshot.: Cause: The snapshot remastering continue option was specified for a file system that was not an interrupted snapshot remastering.; Action: None
ACFS-12221: failed to allocate a number byte 'string' buffer: Cause: There was insufficient memory to allocate working structures.; Action: Contact Oracle Support Services.
ACFS-12222: failed to read 'string' from disk\n offset string size number: Cause: Snap remaster failed to read the indicated data structure from the file system. Refer to accompanying messages for more information on the problem.; Action: Correct the problem indicated by the other messages. If the solution is not clear, contact Oracle Support Services.
ACFS-12223: failed to read 'string' file entry number from disk\n offset string size number: Cause: Snap remaster failed to read the indicated file entry metadata from the file system. Refer to accompanying messages for more information on the problem.; Action: Correct the problem indicated by the other messages. If the solution is not clear, contact Oracle Support Services.
ACFS-12224: Failed to change the on-disk File Entry Table starting location (_VolFETALPosition).: Cause: Snap remaster failed to write the new File Entry Table starting offset to the remastered file system. Refer to accompanying messages for more information on the problem.; Action: Correct the problem indicated by the other messages. If the solution is not clear, contact Oracle Support Services.
ACFS-12225: failed to initialize extent 'Up Header' offsets and mark deleted snapshot file entries as free: Cause: Snap remaster failed to change the file extent 'Up Header' offsets so they are pointing to the remastered File Entry Table and to change the state of deleted snapshot file entries to available for allocation as new files. Refer to accompanying messages for more information on the problem.; Action: Correct the problem indicated by the other messages. If the solution is not clear, contact Oracle Support Services.
ACFS-12226: failed to read the file entry for the master file system File Entry Table: Cause: Snap remaster failed to read the file entry for the master File Entry Table. Refer to accompanying messages for more information on the problem.; Action: Correct the problem indicated by the other messages. If the solution is not clear, contact Oracle Support Services.
ACFS-12227: unexpected mode string in string: Cause: The reported function detected the wrong mode.; Action: Contact Oracle Support Services.
ACFS-12228: The Oracle ASM Dynamic Volume Manager (Oracle ADVM) compatibility attribute for the disk group is less than number.number.: Cause: The snapshot remaster operation was rejected because the ADVM disk group compatibility had not been upgraded to the indicated version, which is required for that command.; Action: Use the Oracle ASM Configuration Assistant (ASMCA) tool or the SQL ALTER DISKGROUP statement to upgrade the disk group compatibility (COMPATIBLE.ADVM attribute) to the specified version and then re-issue the original command. If the disk group compatibility cannot be upgraded, update the ACFS compatibility using the 'acfsutil compat set' command and then re-issue the original command.
ACFS-12229: Replication must be terminated before the volume can be remastered.: Cause: A 'snap remaster' command was issued for a volume that was being replicated.; Action: 'snap remaster' cannot be performed on a file system that is being replicated. If appropriate, terminate replication on this file system with the command 'acfsutil repl terminate primary mountpoint'.
ACFS-12230: failed to find the snapshot 'string': Cause: The specified snapshot was not found.; Action: Make sure the snapshot name is correct.
ACFS-12231: failed to initialize file ID number for access: Cause: Snap remaster failed to initialize data structures allowing access to the indicated file ID.; Action: Run the ACFS Fixer.
ACFS-12232: failed to create a file access structure for file ID number: Cause: Snap remaster failed to create a structure for accessing the indicated file ID. Refer to accompanying messages for more information on the problem.; Action: Correct the problem indicated by the other messages. If the solution is not clear, contact Oracle Support Services.
ACFS-12233: failed to access the remastered File Entry Table using file ID number: Cause: Snap remaster failed to read the File Entry Table for the remastered snapshot. Refer to accompanying messages for more information on the problem.; Action: Correct the problem indicated by the other messages. If the solution is not clear, contact Oracle Support Services.
ACFS-12234: failed to access the Snap Map file entry at file ID: number: Cause: Snap remaster failed to read the file entry for the Snap Map using the indicated file ID. Refer to accompanying messages for more information on the problem.; Action: Correct the problem indicated by the other messages. If the solution is not clear, contact Oracle Support Services.
ACFS-12235: failed to access the 'string' file entry at file ID: number: Cause: Snap remaster failed read the file entry for the indicated metadata using the indicated file ID. Refer to accompanying messages for more information on the problem.; Action: Correct the problem indicated by the other messages. If the solution is not clear, contact Oracle Support Services.
ACFS-12236: failed to access the Global BitMap file entry at file ID: number: Cause: Snap remaster failed to read the file entry for the Global BitMap using the indicated file ID. Refer to accompanying messages for more information on the problem.; Action: Correct the problem indicated by the other messages. If the solution is not clear, contact Oracle Support Services.
ACFS-12237: failed to read the file extent map for file ID number: Cause: Snap remaster failed to read file storage allocation information for the file ID indicated file. Refer to accompanying messages for more information on the problem.; Action: Correct the problem indicated by the other messages. If the solution is not clear, contact Oracle Support Services.
ACFS-12238: metadata write failed\n offset string size number file ID number: Cause: An attempt to write metadata of the indicated file ID failed. Refer to accompanying messages for more information on the problem.; Action: Correct the problem indicated by the other messages. If the solution is not clear, contact Oracle Support Services.
ACFS-12239: metadata copy failed\n file offset string size number file ID number: Cause: An attempt to write copied metadata to the indicated file ID failed. Refer to accompanying messages for more information on the problem.; Action: Correct the problem indicated by the other messages. If the solution is not clear, contact Oracle Support Services.
ACFS-12240: initializing metadata failed\n file offset string size number file ID number: Cause: An attempt to write initialized metadata to the indicated file ID failed. Refer to accompanying messages for more information on the problem.; Action: Correct the problem indicated by the other messages. If the solution is not clear, contact Oracle Support Services.
ACFS-12241: updating metadata failed\n file offset string size number file ID number: Cause: An attempt to write updated metadata to the indicated file ID failed. Refer to accompanying messages for more information on the problem.; Action: Correct the problem indicated by the other messages. If the solution is not clear, contact Oracle Support Services.
ACFS-12242: failed to update the extent headers with the new file ID number for the moved file entry: Cause: An error occurred while attempting to update the file extent headers with the new file ID after the file's file entry was moved to the remastered File Entry Table. Refer to accompanying messages for more information on the problem.; Action: Correct the problem indicated by the other messages. If the solution is not clear, contact Oracle Support Services.
ACFS-12243: failed to access the Accelerator Global BitMap file entry at file ID: number: Cause: Snap remaster failed to read the indicated file entry for the Accelerator Global BitMap. Refer to accompanying messages for more information on the problem.; Action: Correct the problem indicated by the other messages. If the solution is not clear, contact Oracle Support Services.
ACFS-12244: failed to read the snap map using file ID number: Cause: Snap remaster failed to initialize the snap entry table with snap map entries from the indicated file ID. Refer to accompanying messages for more information on the problem.; Action: Correct the problem indicated by the other messages. If the solution is not clear, contact Oracle Support Services.
ACFS-12245: failed to update the file extent parent pointers for file ID: number: Cause: An error occurred while attempting to update the file extent parent pointer after the file's file entry was moved to the remastered File Entry Table. Refer to accompanying messages for more information on the problem.; Action: Correct the problem indicated by the other messages. If the solution is not clear, contact Oracle Support Services.
ACFS-12246: failed to release file ID number file entry: Cause: An error occurred while releasing the indicated file entry. Refer to accompanying messages for more information on the problem.; Action: Correct the problem indicated by the other messages. If the solution is not clear, contact Oracle Support Services.
ACFS-12247: failed to fetch the remastered snapshot Global directory metadata: file ID number: Cause: Snap remaster failed to read the Global directory metadata using the indicated file ID from the remastered File Entry Table. Refer to accompanying messages for more information on the problem.; Action: Correct the problem indicated by the other messages. If the solution is not clear, contact Oracle Support Services.
ACFS-12248: failed to rebuild directory 'string': file ID number: Cause: Snap remaster failed to reconstruct the indicated file system directory after deleted files were removed. Refer to accompanying messages for more information on the problem.; Action: Correct the problem indicated by the other messages. If the solution is not clear, contact Oracle Support Services.
ACFS-12249: failed to allocate storage from the Global BitMap file ID: number: Cause: Snap remaster failed to find free storage in the Global BitMap. Refer to accompanying messages for more information on the problem.; Action: Correct the problem indicated by the other messages. If the solution is not clear, contact Oracle Support Services.
ACFS-12250: failed to find an expected string data structure on an in-memory linked list: Cause: Snap remaster failed to find the indicated data structure.; Action: Contact Oracle Support Services.
ACFS-12251: failed to add file ID number to the File Entry Table free list: Cause: Snap remaster failed to add the indicated file ID to the remastered File Entry Table list of available for reuse file entries. Refer to accompanying messages for more information on the problem.; Action: Correct the problem indicated by the other messages. If the solution is not clear, contact Oracle Support Services.
ACFS-12252: failed to add file ID number to the in-memory file entry cache: Cause: Snap remaster failed to read the indicated file ID and add it to the file entry cache for reuse in the remastered snapshot. Refer to accompanying messages for more information on the problem.; Action: Correct the problem indicated by the other messages. If the solution is not clear, contact Oracle Support Services.
ACFS-12253: failed to update file ID number storage: Cause: An error occurred while updating the indicated file entry's storage. Refer to accompanying messages for more information on the problem.; Action: Correct the problem indicated by the other messages. If the solution is not clear, contact Oracle Support Services.
ACFS-12254: failed to remove the file ID number storage: Cause: An error occurred while removing the indicated file entry's storage. Refer to accompanying messages for more information on the problem.; Action: Correct the problem indicated by the other messages. If the solution is not clear, contact Oracle Support Services.
ACFS-12255: failed to delete file names from directory 'string': Cause: Snap remaster failed to delete the files in the indicated directory. Refer to accompanying messages for more information on the problem.; Action: Correct the problem indicated by the other messages. If the solution is not clear, contact Oracle Support Services.
ACFS-12256: failed to delete all the .ACFSstringreplstring subdirectories: Cause: Snap remaster failed to delete all the subdirectories in the indicated directory. Refer to accompanying messages for more information on the problem.; Action: Correct the problem indicated by the other messages. If the solution is not clear, contact Oracle Support Services.
ACFS-12257: Snapshot 'string' replication must be terminated before the volume can be remastered.: Cause: A 'snap remaster' command was issued for a volume that was was replicating snapshots.; Action: 'snap remaster' cannot be performed on a file system that is being replicated. Terminate replication on this file system with the command 'acfsutil repl terminate primary mountpoint'.
ACFS-12258: cannot find the ACFS Checker and Fixer utility: string: Cause: The 'snap remaster' back-end utility (the ACFS Checker and Fixer) could not be found.; Action: Make sure ACFS has been properly installed. If the solution is not clear, contact Oracle Support Services.
ACFS-12259: ACFS Checker and Fixer returned an error.: Cause: The 'snap remaster' back-end utility (ACFS Checker and Fixer) returned an error. Refer to accompanying messages for more information on the problem.; Action: Correct the problem indicated by the other messages. If the solution is not clear, contact Oracle Support Services.
ACFS-12260: ACFS Checker and Fixer failed to perform the 'snap remaster'\n command: string: Cause: The indicated ACFS Checker and Fixer command failed.; Action: Correct the problem indicated by the other messages. If the solution is not clear, contact Oracle Support Services.
ACFS-12261: Volume signature indicates 'snap remaster' was in progress.\n Signature: 'string'\n Use\n 'acfsutil snap remaster stringc string'\n to complete the 'snap remaster'.\n Or to reformat the volume, reissue string with the stringf option.: Cause: The volume signature indicates that 'snap remaster' was being run on this volume.; Action: Make sure 'snap remaster' is not being run on another node or by another user. If 'snap remaster' had been started and then aborted, use the 'acfsutil snap remaster -c device' command to continue the interrupted snapshot remastering.
ACFS-12262: 'snap remaster' rejected because this file system uses an accelerator volume.: Cause: 'snap remaster' command was issued for a file system with an accelerator volume.; Action: None
ACFS-12263: ACFS Plugins must be disabled before the file system can be remastered.: Cause: An 'acfsutil snap remaster' command was rejected because the specified file system had Oracle ACFS plug-ins enabled.; Action: If appropriate, disable ACFS Plug-ins with the command 'acfsutil plugin disable mountpoint' and retry the operation.
ACFS-12264: ACFS Plugins are enabled on node: string.: Cause: An 'acfsutil snap remaster' command was rejected because the specified file system had Oracle ACFS plug-ins enabled on the indicated node.; Action: If appropriate, disable ACFS Plug-ins with the command 'acfsutil plugin disable mountpoint' and retry the operation.
ACFS-12265: 'snap remaster' cannot be used on a file system with ACFS security.: Cause: An 'acfsutil snap remaster' command was rejected because the specified file system had Oracle ACFS security enabled.; Action: None
ACFS-12266: 'snap remaster' cannot be used on a file system with ACFS encryption.: Cause: An 'acfsutil snap remaster' command was rejected because the specified file system had Oracle ACFS encryption enabled.; Action: None
ACFS-12267: failed to clean the .ACFS directory tree: Cause: An attempt to remaster an Oracle ACFS snapshot failed to clean the .ACFS directory tree. The accompanying messages provide detailed failure information.; Action: Correct the problem indicated by the other error messages. Use the 'acfsutil snap remaster -c device' command to continue the interrupted snapshot remastering.
ACFS-12268: failed to copy the .ACFS directory tree to the snapshot: Cause: An attempt to remaster an Oracle ACFS snapshot failed to copy the .ACFS directory tree to the snapshot. The accompanying messages provide detailed failure information.; Action: Correct the problem indicated by the other error messages. Use the 'acfsutil snap remaster -c device' command to continue the interrupted snapshot remastering.
ACFS-12269: failed to update directory string: Cause: An attempt to remaster an Oracle ACFS snapshot failed to update the indicated directory. The accompanying messages provide detailed failure information.; Action: Correct the problem indicated by the other error messages. Use the 'acfsutil snap remaster -c device' command to continue the interrupted snapshot remastering.
ACFS-12270: failed due to remapped metadata files from a prior file system shrink: Cause: An attempt to remaster an Oracle ACFS snapshot failed because the specified snapshot contains metadata files that were remapped as part of a prior file system shrink. Such files would prevent the remastered file system from mounting.; Action: Retry the operation, selecting a different snapshot to remaster.
ACFS-12271: Unable to obtain ftrace information for mount point 'string'.: Cause: An attempt to obtain ftrace information failed. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.
ACFS-12274: failed to clear the snapshot storage interest tracking map: Cause: Snap remaster failed to remove the storage interest tracking Map for the deleted snapshots. Refer to accompanying messages for more information on the problem.; Action: Correct the problem indicated by the other messages. If the solution is not clear, contact Oracle Support Services.
ACFS-12275: failed to access the storage interest tracking map file entry for the string volume: Cause: Snap remaster failed to read the file entry for the storage interest tracking map on the indicated volume. Refer to accompanying messages for more information on the problem.; Action: Correct the problem indicated by the other messages. If the solution is not clear, contact Oracle Support Services.
ACFS-13000: unable to determine the cluster type: Cause: An 'advmutil' command failed to determine the type of cluster that contained the local server. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated problems, and retry the operation.
ACFS-13001: insufficient privileges - ASM administrator group access required: Cause: A requested 'advmutil' command failed because the user did not have the required ASM Administrator privilege.; Action: Retry the command from an account with the required privilege.
ACFS-13002: Command is not supported on a cluster of the current type.: Cause: A requested 'advmutil export' or 'advmutil transport' command failed because the command could only be run on a Domain Services Cluster.; Action: Verify that this command is the correct command to execute, and if so, retry the command on a Domain Services Cluster.
ACFS-13016: A failure occurred while updating the currently active export list for cluster 'string'.: Cause: An 'advmutil export create' or 'advmutil export mapping' command failed because an error occurred when attempting to modify the currently active configuration for the indicated cluster. Accompanying messages provide further failure details.; Action: Examine the accompanying messages, address any issues raised and retry the original request.
ACFS-13017: The update of active exports for cluster 'string' succeeded.: Cause: Informational.; Action: None
ACFS-13032: invalid combination of 'fileSize' and 'force' options: Cause: The 'advmutil export create' command was rejected because the 'fileSize' and 'force' options were both used on the command line.; Action: To create an export where the backing store does not exist, execute the 'advmutil export create' command specifying the required 'fileSize' option, which will create the backing store. To reuse an existing backing store, execute the 'export create' with the 'force' option.
ACFS-13033: The 'force' option cannot be used if the backing store does not exist.: Cause: The 'advmutil export create' command was rejected because the 'force' option was specified and the backing store did not exist.; Action: To create an export where the backing store does not exist, execute the 'advmutil export create' command specifying the required 'fileSize' option to create the backing store at the same time.
ACFS-13034: insufficient file space - requested: string available: string: Cause: An 'advmutil export' or 'advmutil resize' command failed because writing the file required the indicated additional space when only the indicated space was available.; Action: Use a requested file size that fits in the storage repository's free space, or create additional space within the storage repository.
ACFS-13035: missing exportName: Cause: An 'advmutil export' command was rejected because the exportName argument was not specified.; Action: Reissue the command, specifying the exportName on the command line.
ACFS-13036: The location 'string' exists but is not a directory.: Cause: An advmutil export command failed because the indicated location for the storage repository existed on disk and was not a directory.; Action: To use the indicated location, remove the conflicting object and retry the command. Otherwise, retry the command specifying a location that was a directory or that does not exist.
ACFS-13037: missing storageRepo: Cause: An advmutil export command was rejected because the storageRepo argument was not specified.; Action: Reissue the command, specifying the storageRepo on the command line.
ACFS-13038: The specified 'exportName' is longer than the maximum length number.: Cause: An advmutil export command was rejected because the exportName exceeded the indicated maximum length.; Action: Retry the command, specifying an exportName with a length less than or equal to the indicated maximum length.
ACFS-13039: The storageRepo/exportName 'string' exists but is not a file.: Cause: An 'advmutil export create' or advmutil transport create' command failed because it expected the location pointed to by the specified storageRepo and exportName to be a file or not to exist. The path pointed to an existing, on-disk, object that was not a file.; Action: To use the indicated location, remove the conflicting object and retry the command. Otherwise, retry the command specifying a location that is a file or that does not exist.
ACFS-13040: missing clusterName: Cause: An 'advmutil export', 'advmutil transport', or 'advmutil resize' command was rejected because the clusterName was not specified.; Action: Retry the command, specifying the clusterName on the command line.
ACFS-13041: The export 'string' for cluster 'string' already exists as file path 'string'.: Cause: An 'advmutil export create' command failed because a file already existed on disk at the indicated location.; Action: To continue using this file, rerun the advmutil export create command with the [-f force] option. Otherwise, remove the existing export using the command 'advmutil export delete' and retry the command 'advmutil export create' using the specified name.
ACFS-13042: unable to create file 'string': Cause: An 'advmutil export create' or 'advmutil export resize' command failed to create or resize the indicated file in the specified storage repository.; Action: Examine the accompanying messages, address issues, and retry.
ACFS-13043: missing size option: Cause: An 'advmutil export create' or 'advmutil export resize' command was rejected because the size argument was not specified.; Action: Reissue the command, specifying the size on the command line.
ACFS-13044: Unable to determine the GUID for cluster 'string'.: Cause: The requested advmutil command failed because it was unable to determine the Globally Unique Identifier (GUID) for the indicated cluster name. The accompanying messages provide further failure details.; Action: Examine the accompanying messages, address any issues raised and retry the original request.
ACFS-13047: Invalid file size string is smaller than the minimum supported file size string.: Cause: An 'advmutil export create' or 'advmutil export resize' was rejected because the indicated size is smaller than the indicated supported minimum file size.; Action: Retry the command, specifying a file size larger than the indicated minimum.
ACFS-13048: The file path for export name 'string' is longer than the maximum allowed 'number' characters.: Cause: An 'advmutil export create' command was rejected because the provided arguments for storageRepo, clusterName, and exportName resulted in a file path storageRepo/clusterGUID/exportName that was longer than the indicated maximum path length.; Action: Retry the command, specifying a smaller storageRepo and exportName so that the combined length is less than the indicated maximum.
ACFS-13049: The location 'string' is not a mounted ACFS file system.: Cause: An 'advmutil export create' command failed because the indicated location, specified as storageRepo, was not an ACFS file system.; Action: Retry the command, ensuring that the location specified for storageRepo is an ACFS file system.
ACFS-13050: File 'string' does not exist.: Cause: An 'advmutil export resize' or 'advmutil transport create' command failed because the indicated file did not exist.; Action: Retry the command, ensuring the arguments specifying fileName, clusterName, and storageRepo used to create the path name are correct.
ACFS-13052: Failed to create export 'string' for cluster 'string'.: Cause: An 'advmutil export create' command failed because the specified export could not be created. The accompanying messages provide further failure details.; Action: Examine the accompanying messages, address any issues raised and retry the original request.
ACFS-13054: The specified export already exists in the Oracle Cluster Registry (OCR).: Cause: An 'advmutil export create' was rejected because the export already existed in the Oracle Cluster Registry (OCR).; Action: To recreate an existing export with a new File Backed Volume, first remove the export using 'advmutil export remove' and retry the 'advmutil export create' command. Otherwise, use the existing export or create a new one using a different name.
ACFS-13061: missing exportName or storageRepo: Cause: An 'advmutil export remove' command was rejected because both exportName and storageRepo must be specified on the command line, and one of them was not specified.; Action: Retry the command specifying storageRepo and exportName.
ACFS-13062: File 'string' does not exist.: Cause: An 'advmutil export remove' or 'advmutil export list' command expected to find the indicated file, which did not exist.; Action: None. The command will complete normally.
ACFS-13067: Unable to remove export 'string' from cluster 'string'.: Cause: An 'advmutil export remove' command failed because it could not remove the indicated export from the indicated cluster. The accompanying messages provide further failure details.; Action: Examine the accompanying messages, address any issues raised and retry the original request.
ACFS-13068: unable to clear ACFS remote usage attribute for file 'string': Cause: An attempt to remove the indicated file from usage in a specified storage repository failed because the ACFS Remote attribute could not be cleared. If the ACFS remote usage attribute is set, the file will not be deleted and its storage will not be removed as part of the export remove.; Action: Check that the indicated file exists and if so, use 'acfsutil remote clear' to clear the ACFS remote attribute explicitly before manually deleting the file. If unable to delete the indicated file, then contact Oracle Support Services.
ACFS-13069: unable to open backing store file 'string': Cause: An attempt to remove the indicated ACFS remote backing storage file from usage in a specified storage repository failed because the file could not be opened to clear the ACFS remote attribute. Additional messages provide detailed failure information.; Action: Check that the file exists and if so, use 'acfsutil remote clear' to clear the ACFS remote attribute explicitly before manually deleting the file. If unable to delete the existing file, contact Oracle Support Services.
ACFS-13076: Invalid options 'string' specified. Valid options are 'string'.: Cause: An 'advmutil export list' command was rejected because the indicated option was not valid.; Action: Retry the command specifying a list of valid, comma-separated options.
ACFS-13077: invalid group type 'string' specified: Cause: An 'advmutil export list' command was rejected because the specified group type was not a valid group type. Valid groups are 'clusterName', 'clusterGUID', and 'storageRepo'.; Action: Retry the command specifying a valid group type.
ACFS-13078: unable to find the cluster name for the GUID 'string': Cause: An 'advmutil export list' command failed because it was unable to determine the cluster name from the Globally Unique Identifier (GUID). The accompanying messages provide further failure details.; Action: Examine the accompanying messages, address any issues raised and retry the original request.
ACFS-13079: more options specified than the maximum allowed: number: Cause: An 'advmutil export list command' was rejected because more options were specified than the indicated maximum.; Action: Retry command specifying fewer options than the indicated maximum.
ACFS-13081: Export list failed.: Cause: An advmutil export list' command failed because the system call to retrieve the export information failed. The accompanying messages provide further failure details.; Action: Examine the accompanying messages, address any issues raised and retry the original request.
ACFS-13083: unable to mark file 'string' for ACFS remote usage: Cause: An operation to mark the indicated file for ACFS Remote usage in a specified storage repository failed. This will not affect normal usage as a ACFS remote backing store, however with the ACFS remote attribute not set the file will not be protected from local modification.; Action: The export will be created and operate normally. Run 'acfsutil remote set' on the indicated file to mark the indicated file for ACFS remote usage.
ACFS-13092: invalid file size or file size increment specified: Cause: An 'advmutil export size' command was rejected because an invalid file size or file size increment was specified.; Action: Retry the command, specifying a file size greater than the current file size or a file size increment equal to or greater than 1MB. Shrinking File Backed Volume (FBV) files can only be done on a Member Cluster using the command 'acfsutil size'.
ACFS-13107: no available sequence number: Cause: An 'advmutil transport create' command failed because all of the available transport sequence numbers for the specified transport type were in use.; Action: Use the 'advmutil transport remove' command to delete an existing transport that is not in use. Then retry the 'advmutil transport create' command.
ACFS-13109: Transport resource 'string' is in use by other transports.: Cause: An 'advmutil transport create' command was rejected because the indicated resource existed and was in use by other transports.; Action: To reuse an existing transport resource, retry the command, specifying the 'resourceID' option for that resource. The 'resourceID' is the resource name minus the leading 'ora.' and the trailing '.transport_vip'.
ACFS-13110: Transport 'string' already exists on cluster 'string'.: Cause: An 'advmutil export create' command was rejected because the indicated transport already existed on the indicated cluster.; Action: Retry the command, specifying a different resourceID.
ACFS-13115: missing transportID: Cause: An 'advmutil transport remove' command was rejected because the transportID argument was not specified."; Action: Retry the command, specifying the transportID on the command line.
ACFS-13116: invalid transport ID 'string': Cause: An 'advmutil transport remove' command was rejected because the indicated transport identifier was not specified in the form 'transportType.sequenceNumber'.; Action: Retry the command, specifying the transportID using the correct format.
ACFS-13117: The transport 'string.string' does not exist for cluster 'string'.: Cause: An 'advmutil transport remove' command failed because the transport did not exist for the indicated cluster name.; Action: Verify the available transportIDs for this cluster by using the 'advmutil transport list' command. Retry the command, specifying a valid transportID. Alternatively, retry the command specifying a different cluster name for which the specified transportID is valid.
ACFS-13119: No eligible exports were found.: Cause: No exports existed for the specified input criteria.; Action: Informational.
ACFS-13130: Both clusterName and clusterGUID were specified on the command line.: Cause: An 'advmutil transport list' command was rejected because both the clusterName and the clusterGUID were specified on the command line.; Action: Retry the command, specifying either a clusterName, a clusterGUID, or neither.
ACFS-13131: missing clusterName or clusterGUID: Cause: An 'advmutil transport list' command was rejected because a transportID was specified without also specifying a clusterGUID or a clusterName on the command line.; Action: Retry the command, specifying either a clusterName or a clusterGUID when specifying a transportID.
ACFS-13132: missing transportID argument: Cause: An 'advmutil transport list' command was rejected because the verbose option was specified without specifying a transportID.; Action: Retry the command, specify either a transportID and the verbose option, or removing the verbose option.
ACFS-13133: No eligible transports were found.: Cause: No transports existed for the specified input criteria.; Action: Informational
ACFS-13150: unknown system call failure - 'ASDO_E_FAILURE': Cause: The requested operation failed because of an unhandled kernel ioctl error. The accompanying messages provide further failure details.; Action: Contact Oracle Support Services.
ACFS-13151: invalid user address passed to the 'oracleadvm' driver -'ASDO_E_FAULT': Cause: The requested operation failed because the oracleadvm driver attempted to access an invalid user memory address.; Action: Contact Oracle Support Services.
ACFS-13152: GUID for the cluster name not found - 'ASDO_E_GUID_NOT_FOUND': Cause: The requested operation failed because it could not determine the Globally Unique IDentifier. Additional messages may accompany this to provide further failure details.; Action: Examine any additional messages, address any issues raised, and retry the original command. Additionally, verify the cluster name is valid, and retry the command specifying a valid cluster name. Finally, contact Oracle Support Services.
ACFS-13153: invalid argument - 'ASDO_E_INVAL_ARG': Cause: The requested operation failed because an invalid argument was passed to a system call.; Action: Contact Oracle Support Services.
ACFS-13154: invalid system call opcode - 'ASDO_E_INVAL_TYPE': Cause: The requested operation failed because an invalid opcode was passed to a system call.; Action: Contact Oracle Support Services.
ACFS-13155: specified storage repository not mounted - 'ASDO_E_REPOMOUNT_NOT_FOUND': Cause: The requested operation failed because the storage repository was not mounted.; Action: Verify that the specified storage repository is a valid ACFS file system. Use 'advmutil export list' to determine if the storage repository is listed as a valid storage repository. Retry the command, specifying a valid storage repository.
ACFS-13156: required file path not found - 'ASDO_E_PATH_NOT_FOUND': Cause: The requested operation failed because the kernel could not find the required path.; Action: Contact Oracle Support Services.
ACFS-13157: repository directory not found - 'ASDO_E_REPOPATH_NOT_FOUND': Cause: The requested operation failed because the required repository directory was not found.; Action: Contact Oracle Support Services.
ACFS-13158: insufficient memory - 'ASDO_E_NOMEM': Cause: The operation failed because the 'oracleadvm' driver could not allocate sufficient kernel memory to perform the operation.; Action: Terminate un-needed processes that may be consuming kernel memory. Retry the command.
ACFS-13159: device special file not found- 'ASDO_E_DSF_NOT_FOUND': Cause: The operation failed because the 'oracleadvm' driver could not find the specified device special file in /dev/acfsr.; Action: Retry the command specifying the correct device special file on the command line.
ACFS-13170: export lsof ioctl failed: Cause: An 'advmutil export lsof' command failed because the system call to retrieve the export information failed. The accompanying messages provide further failure details.; Action: Examine the accompanying messages, address any issues raised and retry the original request.
ACFS-13171: getCurNumExports ioctl failed: Cause: An 'advmutil export lsof' command failed because the system call to retrieve the export information failed. The accompanying messages provide detailed failure information.; Action: Contact Oracle Support Services.
ACFS-13190: Command is not supported on a cluster of the current type.: Cause: An 'advmutil session list' command failed because the command could only be run on a Member Cluster.; Action: Verify that this command is the correct command to execute, and if so, retry the command on a Member Cluster.
ACFS-13192: invalid sequence number number: Cause: An 'advmutil session list' command was rejected because the indicated sequence number was out-of-range.; Action: Retry the command, specifying a sequence number between 0 - 999 (inclusive).
ACFS-13193: Node 'string' does not exist on this cluster.: Cause: An 'advmutil session list' command failed because the specified node was not a member of this cluster.; Action: Retry the command, specifying a node that is a member of this cluster.
ACFS-13194: invalid transport type 'string' specified: Cause: An 'advmutil session list' command was rejected because the indicated transport type specified on the command line was invalid.; Action: Refer to the documentation for valid transport types. Retry the command, specifying a valid transport type.
ACFS-13195: No eligible sessions were found.: Cause: No sessions exist for the specified input criteria.; Action: Informational.
ACFS-13250: The resource name 'string' specified by resource id 'string' does not exist.: Cause: An 'advmutil transport create' command was rejected because the indicated resource identifier did not resolve to an existing transport resource.; Action: If the intent is to re-use an existing transport resource, reissue the 'advmutil transport create' command, specifying the resource identifier of an existing resource.
ACFS-13251: Resource ID may not be specified together with network number or host binding.: Cause: An 'advmutil transport create' command was rejected because the resource ID option was specified with the network number or host binding option (or both) on the command line.; Action: If the intent is to reuse an existing transport resource, reissue the 'advmutil transport create' command specifying the the resource ID of an existing resource and omitting the options for network number or host binding.
ACFS-13252: cannot create a CRS resource ('string') that already exists: Cause: An 'advmutil transport create' command failed because the command attempted to create a Cluster Ready Services (CRS) resource that already existed. This is an internal error.; Action: Contact Oracle Support Services.
ACFS-13253: The 'bind' option must be specified on the command line.: Cause: An 'advmutil transport create' command was rejected because the 'bind' option was not specified on the command line.; Action: Retry the 'advmutil transport create' command, specifying a valid 'bind' option.
ACFS-13254: The binding VIP 'string' does not exist in the Domain Name System (DNS).: Cause: An 'advmutil transport create' command was rejected because the indicated binding VIP (host name or network address) was unknown.; Action: Retry the 'advmutil transport create' command specifying a DNS resolveable host name or network address.
ACFS-13255: The supplied network number 'string' is invalid.: Cause: An 'advmutil transport create' command was rejected because the specified network number was not a positive digit.; Action: Retry the 'advmutil transport create' command, specifying a valid network number.
ACFS-13256: Entries specified on the command line already exist in the OCR.: Cause: An 'advmutil transport create' command was rejected because the bind host name or network address are already in the Oracle Cluster Registry (OCR).; Action: Retry the 'advmutil transport create' command specifying an unused host name or network address. Alternatively, use the 'force' option on the command line to allow the re-use of this binding.
ACFS-13257: The specified network number 'string' does not exist in the Oracle Cluster Ready Services (CRS).: Cause: An 'advmutil transport create' command was rejected because an invalid network number was specified on the command line.; Action: Retry the 'advmutil transport create' command using a valid network number.
ACFS-13258: Failed to retrieve 'string' for resource 'string': error number: Cause: An 'advmutil transport create' command failed because it could not retrieve the indicated item from the indicated resource. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation. If unable to resolve the issues, contact Oracle Support Services.
ACFS-13259: Waiting for competing advmutil process to finish.: Cause: The file /tmp/advmutil.lock was locked by a running advmutil process.; Action: Wait for the other advmutil processes to finish and retry the command.
ACFS-13300: Cannot query Cluster Ready Services (CRS) resource 'string'.: Cause: An 'advmutil transport' or 'advmutil export' command failed because it could not query the indicated resource. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.
ACFS-13301: Invalid CRS attribute format detected in resource 'string'.: Cause: An Cluster Ready Services (CRS) resource start or stop dependency format error was detected. This is an internal error.; Action: Contact Oracle Support Services.
ACFS-13302: Failed to get ACFS mount points from Cluster Ready Services (CRS).: Cause: An 'advmutil export create' or 'advmutil export remove' command failed because it could not query ACFS mount points. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.
ACFS-13303: The Cluster Ready Services (CRS) cannot be initialized.: Cause: An 'advmutil transport' or 'advmutil export' command failed because the initialization of the Cluster Ready Services (CRS) failed. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.
ACFS-13304: The bind host name or network address 'string' is already in use in the network.: Cause: An 'advmutil transport create' command was rejected because the indicated host name or network address specified on the command line was in use in the network and was therefore not generally available for the transport.; Action: Retry the 'advmutil transport create', specifying a host name or network address that is DNS resolvable but not in use. Alternatively, use the 'force' option on the command line to allow the re-use of the specified host name or network address.
ACFS-13305: Failed to start Cluster Ready Services (CRS) resource 'string'.: Cause: "An 'advmutil transport create' failed because the indicated Cluster Ready Services (CRS) resource failed to start. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.
ACFS-13306: The Cluster Ready Services (CRS) resource 'string' cannot be updated.: Cause: An 'advmutil transport create' command failed because it was unable to update the indicated resource. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.
ACFS-13307: Failed to retrieve the resource 'string' error 'number'.: Cause: An 'advmutil transport create' failed to cause it could not retrieve the indicated resource. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.
ACFS-13308: Failed to retrieve the start/stop dependencies or state for resource 'string': error number: Cause: An 'advmutil transport create', 'advmutil export create', or 'advmutil export remove' command failed because it could not retrieve the current start or stop dependency or the resource state for the indicated resource. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation. If unable to resolve the issues, contact Oracle Support Services.
ACFS-13309: Failed to set the 'string' resource attribute for resource 'string': error number: Cause: An 'advmutil transport create' failed because it could not set the start and stop dependencies for the indicated resource. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.
ACFS-13310: Failed to stop Oracle Ready Services (CRS) resource 'string'.: Cause: An 'advmutil transport remove' command failed because the indicated resource could not be stopped. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.
ACFS-13311: Failed to delete Oracle Ready Services (CRS) resource 'string'.: Cause: An 'advmutil transport remove' command failed because the indicated resource could not be deleted. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.
ACFS-13312: The Cluster Ready Services (CRS) resource 'string' does not exist.: Cause: An 'advmutil transport remove' command detected that an expected CRS resource did not exist.; Action: None. This is a warning only. The command completed normally.
ACFS-13313: The transport identifier 'string' was not found in the Oracle Cluster Registry (OCR).: Cause: An 'advmutil export create' command failed because it could not find a transport identifier in the Oracle Cluster Registry (OCR).; Action: Contact Oracle Support Services.
ACFS-13314: Failed to add start and stop dependencies to Cluster Ready Services (CRS) resource 'string'.: Cause: An 'advmutil transport create' command failed because it could not add start and stop dependencies to the indicated resource. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.
ACFS-13315: failed to remove Cluster Ready Services (CRS) resource 'string': Cause: An 'advmutil export remove' command failed to remove the indicated start and stop dependency from the applicable transport resource. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.
ACFS-13316: failed to add cluster Ready Services (CRS) resource 'string': Cause: An 'advmutil export create' command failed to add the indicated resource to the Cluster Ready Resources (CRS). The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.
ACFS-13317: Failed to create Cluster Ready Services (CRS) resource 'string': error 'number'.: Cause: An 'advmutil transport create' command failed to create the indicated resource. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.
ACFS-13318: failed to find the file system resource name for the storage repository mount point 'string' for cluster 'string': Cause: An 'advmutil export create' command failed because it could not find the resource name for the mount point of the indicated storage repository for the indicated cluster.; Action: Examine the ACFS file system resources (ora.acfs.type). Ensure that The ACFS file system for the storage repository is listed and is ONLINE for the cluster in Cluster Ready Services (CRS).
ACFS-13319: Warning: Verify Cluster Ready Services (CRS) resource 'string' is started on all nodes: Cause: An 'advmutil export create' failed to start the indicated filesystem resource on all the cluster nodes.; Action: Examine the accompanying messages, start filesystem resource on all nodes.
ACFS-13375: The export name 'string' contains non-alphanumeric characters.: Cause: An advmutil export command was rejected because the indicated export name contained non-alphanumeric characters.; Action: Retry the command, specifying an export name containing only alphanumeric characters.
ACFS-13376: invalid size specification 'string': Cause: An 'advmutil export create' or 'advmutil export resize' command was rejected because the indicated size specification was invalid. A valid size consists of a numeric value followed by 'K', 'M', 'G', 'T', 'P', or 'E'.; Action: Retry the command, specifying a valid size specification.
ACFS-13377: The storage repository 'string' is compressed or has compressed files.: Cause: An 'advmutil export create' command was rejected because the indicated storage repository was compressed or contained compressed files.; Action: Retry the command, specifying an uncompressed storage repository.
ACFS-13378: Specified network 'string' uses address family 'string', which is incompatible with the address family 'string' of the specified binding 'string'.: Cause: An 'advmutil transport create' was rejected because the address family of the indicated network (e.g., IPv4) did not match that of the indicated binding.; Action: Retry the advmutil command ensuring that the network family of the indicated 'binding' matches that of the indicated network number.
ACFS-14100: operating system function: string failed with error data: string: Cause: A call to an Operating System dependent service or function returned an error indication. The message includes the name of the function and the returned error data. The latter varies by platform but typically is numeric; on most platforms it is the value of C "errno" after the failing call.; Action: This error normally is accompanied by other (higher-level) messages describing the operation that is affected by the failure. It may also include one or more of messages 14101, 14103, and 14104 providing additional error details. All of the messages should be examined to assess the error, which may have a very ordinary cause and correction, such as an input file failing to open because the supplied name was misspelled.
ACFS-14101: operating system error message: string: Cause: This message accompanies message 14100 above when the Operating System dependent error data can be converted into a text message. On most Oracle platforms the message is a text representation of the C "errno" value reported in message 14100.; Action: See message 14100.
ACFS-14102: operating system interface detected an error: Cause: This message is issued instead of messages 14100-14101 when a "logical" error condition (rather than failure of an Operating System function call) is detected at an Operating System specific interface. The error condition is further described by accompanying message(s), including 14103 and 14104.; Action: This error normally is accompanied by other (higher-level) messages describing the operation that is affected by the failure. In most cases it will also include messages 14103 and 14104, providing additional details about the error. All of the messages should be examined to assess the error, which may have a very ordinary cause and correction, such as a missing required environment variable.
ACFS-14103: error location: string: Cause: This message accompanies message 14100, 14102, or 14105 and identifies a location in Oracle program code that encountered the error.; Action: See message 14100, 14102, or 14105. This information normally is useful only when reporting the error condition to Oracle as a potential code bug.
ACFS-14104: additional error information: string: Cause: This message accompanies message 14100, 14102, or 14105 and supplies additional information related to the error condition. A single error may include multiple lines of additional information.; Action: See message 14100, 14102, or 14105.
ACFS-14105: operating system interface has reported an internal failure: Cause: This message indicates that an Operating System dependent interface within Oracle code has detected internal corruption or some other evidence of internal program failure.; Action: This message may be accompanied by other (higher-level) messages indicating the product operation that was affected by the failure. It may also be accompanied by either or both of messages 14103 and 14104. All situations reporting this condition should be referred to Oracle Support for resolution.
ACFS-14106: An improper operating system error display was attempted: Cause: During processing of an error condition, an attempt was made to format or display Operating System dependent error data, but the error data structure was found to indicate "no error".; Action: This error should be reported to Oracle Support for resolution.
ACFS-14107: operating system function: string; failed with error data: string; at location: string: Cause: A call to an operating system-dependent service or function returned an error. The message includes the name of the function, the returned error data, and error location. Error data varies by platform but typically is numeric. On most platforms, it is the value of C "errno" after the failing call.; Action: This error is normally accompanied by other (higher-level) messages describing the operation that is affected by the failure. It can also include one or more of messages 14101 and 14104 providing additional error details. All of the messages should be examined to assess the error, which may have a very ordinary cause and correction, such as an input file failing to open because the supplied name was misspelled.