ADVM-00100 to ADVM-14107

4 ADVM-00100 to ADVM-14107

ADVM-00100: Enabled: Cause: /*Action single letter option; Action: n/a
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-00505: invalid signature requested: Cause: The command failed to verify the ACFS file system metadata.; Action: Contact Oracle Support Services.
ADVM-00506: Failed to read 'string'.: Cause: An open file could not be read.; Action: The most likely cause is a file permission problem.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-00520: string is not an ADVM volume.: Cause: Volume specified was not an ADVM volume.; Action: Retry the command specifying an ADVM volume.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-00535: insufficient arguments: Cause: The command required additional arguments.; Action: Review the command usage and retry the command providing the needed argument.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-00602: An internal error (BADARG) occurred while trying to determine the Oracle Registry configuration.: Cause: An Oracle internal error.; Action: Contact Oracle.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-00609: End-of-file received.: Cause: An end-of-file was received while waiting for the answer to a question prompt.; Action: None
ADVM-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.
ADVM-00620: This feature is not available for Oracle version string or lower on this platform.: Cause: Informational.; Action: None
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-00999: unexpected assert: "string", string: string: number: Cause: An unexpected situation has occurred.; Action: Contact Oracle Support Services.
ADVM-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.
ADVM-01002: ACFS requires a minimum volume size of numberMB.: Cause: Volume was too small.; Action: Select a larger volume and retry.
ADVM-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.
ADVM-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."
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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
ADVM-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.
ADVM-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.
ADVM-02119: creating administrative network share for mount point string at share name 'string': Cause: Informational; Action: None
ADVM-02120: administrative network share for mount point string already exists at share name 'string': Cause: Informational; Action: None
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-02125: volume 'string' is already in use: Cause: The volume was in use by another file system.; Action: Verify the volume specified.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-03019: Too many options specified: Cause: A command was rejected because too many options were specified.; Action: Retry the command specifying a valid option.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-03036: no mounted ACFS file systems: Cause: The system did not have any mounted ACFS file systems.; Action: None
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-03093: no string tunables for this platform: Cause: Informational.; Action: None
ADVM-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.
ADVM-03095: tunable parameter string not found: Cause: The specified tunable parameter does not exist.; Action: Verify the correctness of the parameter name.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-03119: Incorrect data format in file 'number'.: Cause: The file data was not in the expected format.; Action: Contact Oracle Support Services.
ADVM-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).
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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
ADVM-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.
ADVM-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.
ADVM-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')
ADVM-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')
ADVM-03168: Internal error: string number: Cause: An Oracle internal error.; Action: Contact Oracle Support Services.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-03187: Extent number (mirror number) is not in use.: Cause: Informational; Action: None
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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'
ADVM-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
ADVM-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
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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
ADVM-03275: Updating CRS dependencies for resource 'string'.: Cause: Informational.; Action: None
ADVM-03276: CRS dependencies were updated successfully.: Cause: Informational.; Action: None
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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'
ADVM-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'
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-03310: amount of change since mount: number MB: Cause: Informational; Action: None
ADVM-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.
ADVM-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".
ADVM-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".
ADVM-03316: interval must be a positive integer: Cause: A zero or negative integer was provided.; Action: Provide a positive integer for the statistics interval.
ADVM-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.
ADVM-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.
ADVM-03319: Set tag on file: string: Cause: Informational; Action: None
ADVM-03320: Removing tag(s) on file: string: Cause: Informational; Action: None
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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).
ADVM-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).
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-03511: Deleting string.: Cause: A log file was deleted to satisfy the new configuration.; Action: None. Informational.
ADVM-03512: Renaming string to string.: Cause: A log file was renamed to place it in time modified sequential order.; Action: None. Informational.
ADVM-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'.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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]'.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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
ADVM-03611: Invalid interval specified.: Cause: An invalid interval was specified.; Action: Enter a valid interval between 1 and 3600 seconds.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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"
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-03691: successful update of mount point 'string' to ACFS compatibility level with number.number.number.number.numberstring release stream: Cause: Informational.; Action: None
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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'.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-03920: Creation of volume snapshot string complete.: Cause: Informational; Action: None
ADVM-03921: Deletion of volume snapshot string complete.: Cause: Informational; Action: None
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-03940: Creation of volume snapshot string with backup string complete.: Cause: Informational; Action: None
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-03950: Successful creation of backup string of file system string complete.: Cause: Informational; Action: None
ADVM-03951: Successful creation of backup string of volume snapshot string complete.: Cause: Informational; Action: None
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-04001: Failed to open path string. Verify that string exists.: Cause: Path could not be opened.; Action: Verify the path is accessible before retrying.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-04032: removing administrative network share for mount point string at share name 'string': Cause: Informational; Action: None
ADVM-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'
ADVM-04034: administrative network share for mount point string does not exist at share name 'string': Cause: Informational; Action: None
ADVM-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'
ADVM-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'
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-05007: cannot initialize interrupt signal handler: Cause: The system could not initialize the mechanism to handle interrupts.; Action: Contact Oracle Support Services.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-05023: error checking for file: string: Cause: Informational; Action: None
ADVM-05024: The standby replication site is initialized. ACFS replication will begin.: Cause: Informational; Action: None
ADVM-05025: waiting for the standby replication site to initialize: Cause: Informational; Action: None
ADVM-05026: caught interrupt; ACFS replication initialization is shutting down.: Cause: Informational; Action: None
ADVM-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.
ADVM-05028: cannot obtain current time for events log: Cause: The application failed to get the current time for logging.; Action: Contact Oracle Support Services.
ADVM-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.
ADVM-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.
ADVM-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/.
ADVM-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.
ADVM-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.
ADVM-05034: cannot obtain path for directory: string: Cause: The application failed to locate the specified directory.; Action: Verify that the replication directory is available.
ADVM-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.
ADVM-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.
ADVM-05037: cannot move file string to directory string: Cause: The application failed move the specified file.; Action: Verify that the replication directory is available.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-05044: cannot obtain node name: Cause: Unable to get local node name through CRS.; Action: Verify that CRS is running.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-05049: validating the remote connection: Cause: Informational; Action: None
ADVM-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.
ADVM-05051: remote connection has been established: Cause: Informational; Action: None
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-05059: ACFS replication not initialized: Cause: ACFS replication information cannot be retrieved as replication has not been initialized.; Action: None
ADVM-05060: waiting for ACFS replication to terminate: Cause: Informational; Action: None
ADVM-05061: ACFS replication command interrupted: Cause: Informational; Action: None
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-05066: ACFS replication is already paused: Cause: ACFS replication was paused by a previous call.; Action: None
ADVM-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.
ADVM-05068: ACFS replication has not been paused: Cause: ACFS replication was not paused. Resume operation is not needed.; Action: None
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-05079: waiting for replication update to complete: Cause: Informational; Action: None
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-05159: Last sync time with primary: string: Cause: Informational; Action: None
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-05200: Stopping ACFS replication daemons on string: Cause: Informational; Action: None
ADVM-05201: Starting ACFS replication daemons on string: Cause: Informational; Action: None
ADVM-05202: ACFS replication daemons started successfully on string: Cause: Informational; Action: None
ADVM-05203: ACFS replication daemons stopped successfully on string: Cause: Informational; Action: None
ADVM-05204: Attempting to restart replication daemons on string: Cause: Informational; Action: None
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-05500: ACFS replication error. Contact Oracle Support Services. string: Cause: An ACFS replication operation failed.; Action: Contact Oracle Support Services.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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'.
ADVM-05517: ACFS replication on string: string: Cause: Informational; Action: None
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-05525: File systems have replication enabled from a pre-12.2 release: string: Cause: Informational; Action: None
ADVM-05605: ACFS replication daemon string is exiting due to replication termination. string: Cause: Informational; Action: None
ADVM-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.
ADVM-05701: Comparing first tree (<<<) to second tree (>>>):: Cause: Informational; Action: None
ADVM-05702: Testing for extra files in the second tree.\nSecond tree (<<<) to first tree (>>>):: Cause: Informational; Action: None
ADVM-05703: Results for file comparison of first tree to second tree:: Cause: Informational; Action: None
ADVM-05704: Files successfully compared = number: Cause: Informational; Action: None
ADVM-05705: Files which failed comparison = number: Cause: Informational; Action: None
ADVM-05706: Results for extra files in the second tree:: Cause: Informational; Action: None
ADVM-05707: Total files checked = number: Cause: Informational; Action: None
ADVM-05708: Extra files found = number: Cause: Informational; Action: None
ADVM-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.
ADVM-05710: ACFS tags do not support character devices. Skipping file: string: Cause: Informational; Action: None
ADVM-05711: ACFS tags do not support block devices. Skipping file: string: Cause: Informational; Action: None
ADVM-05712: ACFS tags do not support FIFOs. Skipping file: string: Cause: Informational; Action: None
ADVM-05713: ACFS tags do not support sockets. Skipping file: string: Cause: Informational; Action: None
ADVM-05714: <<< string\n>>> File missing!: Cause: The specified file was not found in the second tree.; Action: None
ADVM-05715: Found: string: Cause: The specified file is an extra file in the second tree.; Action: None
ADVM-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.
ADVM-05717: <<< Extended attribute mismatch for string\n>>> Extended attribute mismatch for string: Cause: Informational; Action: None
ADVM-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.
ADVM-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.
ADVM-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
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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".
ADVM-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.
ADVM-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
ADVM-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.
ADVM-05733: Successfully compared: string string: Cause: Informational.; Action: None
ADVM-05734: Successfully verified existence: string string: Cause: Informational.; Action: None
ADVM-05735: string contents not compared for symlink string: Cause: Informational.; Action: None
ADVM-05736: string symlink contents comparison failed: symlink=string, contents=string: Cause: Informational.; Action: None
ADVM-05737: string file attribute comparison failed: permissions=string, links=number, uid=number, gid=number, bytes=number, file: string: Cause: Informational.; Action: None
ADVM-05738: string file size or file contents comparison failed, file: string: Cause: Informational.; Action: None
ADVM-05739: string security descriptor comparison failed, file: string: Cause: Informational.; Action: None
ADVM-05740: string file type comparison failed, file: string: Cause: Informational.; Action: None
ADVM-05741: string file type comparison failed, directory: string: Cause: Informational.; Action: None
ADVM-05742: string file type comparison failed, soft link: string: Cause: Informational.; Action: None
ADVM-05743: string file type comparison failed, socket: string: Cause: Informational.; Action: None
ADVM-05744: string file type comparison failed, character device: string: Cause: Informational.; Action: None
ADVM-05745: string file type comparison failed, block device: string: Cause: Informational.; Action: None
ADVM-05746: string file type comparison failed, FIFO: string: Cause: Informational.; Action: None
ADVM-05747: Directory 'string' is a nested ACFS reparse point and was not included in the file system comparison.: Cause: Informational.; Action: None
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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
ADVM-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
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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'.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-05903: unable to cleanup old snapshots: Cause: Informational.; Action: None
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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'.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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'.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-05969: unable to get domain-qualified hostname for string: Cause: Internal error.; Action: Contact Oracle Support Services.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-05974: unable to get home directory path for string: Cause: Internal error.; Action: Contact Oracle Support Services.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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).
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-06007: Credentials already exist.: Cause: Informational.; Action: None
ADVM-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.
ADVM-06009: A client with process id number at node string failed to authenticate using certificate number.: Cause: Informational.; Action: None
ADVM-06010: number authentication failure alerts have been suppressed: Cause: Informational.; Action: None
ADVM-06011: An invalid request was received from process number at node string.: Cause: Informational.; Action: None
ADVM-06012: ACFS Replication credentials number were created.: Cause: Informational.; Action: None
ADVM-06013: ACFS Replication credentials number were imported.: Cause: Informational.; Action: None
ADVM-06014: ACFS Replication credentials number were destroyed.: Cause: Informational.; Action: None
ADVM-06015: ACFS Replication credentials number were synced with site string.: Cause: Informational.; Action: None
ADVM-06016: The replication service at node string is online.: Cause: Informational.; Action: None
ADVM-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.
ADVM-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).
ADVM-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).
ADVM-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.
ADVM-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).
ADVM-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.
ADVM-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.
ADVM-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).
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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.
ADVM-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 ACF