98 ADVM-00501 to ADVM-11069

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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-01033: write to volume failed
Cause: of the problem is unclear, contact Oracle Support Services.
Action: Correct the problem indicated by the other message(s). If the
ADVM-01038: write failed during setup of root directory entry
Cause: of the problem is unclear, contact Oracle Support Services.
Action: Correct the problem indicated by the other message(s). If the
ADVM-01041: write of snaps directory entry failed
Cause: of the problem is unclear, contact Oracle Support Services.
Action: Correct the problem indicated by the other message(s). If the
ADVM-01043: write of lost+found directory entry failed
Cause: of the problem is unclear, contact Oracle Support Services.
Action: Correct the problem indicated by the other message(s). If the
ADVM-01044: write of file entry table failed
Cause: of the problem is unclear, contact Oracle Support Services.
Action: Correct the problem indicated by the other message(s). If the
ADVM-01045: write of global bitmap failed
Cause: of the problem is unclear, contact Oracle Support Services.
Action: Correct the problem indicated by the other message(s). If the
ADVM-01046: read of global bitmap file entry failed
Cause: of the problem is unclear, contact Oracle Support Services.
Action: Correct the problem indicated by the other message(s). If the
ADVM-01047: write of global bitmap file entry failed
Cause: of the problem is unclear, contact Oracle Support Services.
Action: Correct the problem indicated by the other message(s). If the
ADVM-01049: seek to snap map header failure
Cause: of the problem is unclear, contact Oracle Support Services.
Action: Correct the problem indicated by the other message(s). If the
ADVM-01050: write to snap map header failure
Cause: of the problem is unclear, contact Oracle Support Services.
Action: Correct the problem indicated by the other message(s). If the
ADVM-01051: partial write to snap map header failure
Cause: of the problem is unclear, contact Oracle Support Services.
Action: Correct the problem indicated by the other message(s). If the
ADVM-01052: write to snap map info entry failure
Cause: of the problem is unclear, contact Oracle Support Services.
Action: Correct the problem indicated by the other message(s). If the
ADVM-01053: partial write to snap map info entry failure
Cause: of the problem is unclear, contact Oracle Support Services.
Action: Correct the problem indicated by the other message(s). If the
ADVM-01054: write to snap map storage entry failure
Cause: of the problem is unclear, contact Oracle Support Services.
Action: Correct the problem indicated by the other message(s). If the
ADVM-01055: partial write to snap map storage entry failure
Cause: of the problem is unclear, contact Oracle Support Services.
Action: Correct the problem indicated by the other message(s). If the
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 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 numberMB.
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-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-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-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-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-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-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-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: is unclear, contact Oracle Support Services.
Action: Correct the problem identified by the other messages. If the
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-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-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 volume size below 200 MB.
Cause: Requested size was below the minimum volume size of 200MB."
Action: Select a volume that is 200MB or larger."
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-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-03033: unable to open string
Cause: The log file specified could not be created and/or opened.
Action: If a file exists by the same name as the log file specified, verify that this is a file that can be overwritten.
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-03052: unable to delete snapshot string due to open files
Cause: There are files open in the snapshot.
Action: Use lsof or 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-03054: snapshot string is not a valid snapshot name
Cause: statement.
Action: Verify that the snapshot name meets the criteria listed in the
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-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-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-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-03133: The Oracle Registry returned the following error while attempting to access the security attributes of key string: string
Cause: is unclear, contact Oracle Support Services.
Action: Correct the problem identified by the other message(s). If the
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 pathname is too large
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 ADVM volume. File system size now number MB, volume size number MB.
Cause: An error occurred during ADVM 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. Check the ASM alert log.
Cause: ADVM could not resize the volume because ASM did not have enough contiguous free diskgroup storage.
Action: Increase the free space in the diskgroup. Check the ASM alert log.
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 ADVM compatibility attribute for the disk group was not set to version 11.2.0.3.0 or higher to allow the creation of a read/write snapshot.
Action: Use the Oracle ASM Configuration Assistant (ASMCA) tool or the SQL statement ALTER DISKGROUP to upgrade COMPATIBLE.ADVM attribute.
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-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 is greater than the file allocation size of number
Cause: The supplied file offset value in bytes supplied must be smaller than the file allocation size.
Action: 'acfsutil file info filename' provides the file allocation size. Choose a smaller value.
ADVM-03187: Extent number (mirror number) is not in use.
Cause: Informational
Action: None
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 ADVM compatibility attribute has not been upgraded to a version that supports the 'acfsutil snap convert' command.
Action: Use the ASMCA tool or the SQL ALTER DISKGROUP statement to upgrade COMPATIBLE.ADVM attribute to the specified version.
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 ADVM compatibility attribute for the disk group was not set to version 12.1 or higher to allow the creation of a snapshot with a parent snapshot.
Action: Use the Oracle ASM Configuration Assistant (ASMCA) tool or the SQL statement ALTER DISKGROUP to upgrade COMPATIBLE.ADVM attribute.
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 hit because the ADVM compatibility attribute associated with the diskgroup was too low.
Action: Use the ASMCA tool or the SQL ALTER DISKGROUP statement to upgrade the COMPATIBLE.ADVM attribute to the specified version.
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 ADVM compatibility attribute has not been upgraded to version 11.2.0.2.0 or beyond.
Action: Use the ASMCA tool or the SQL ALTER DISKGROUP statement to upgrade COMPATIBLE.ADVM attribute.
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 ADVM compatibility attribute has not been upgraded to a version that supports tagging.
Action: Use the ASMCA tool or the SQL ALTER DISKGROUP statement to upgrade COMPATIBLE.ADVM attribute to the specified version.
ADVM-03322: The ADVM compatibility attribute for the diskgroup is below the required version (string) for the 'acfsutil repl' commands.
Cause: The ADVM compatibility attribute has not been upgraded to a version that supports replication.
Action: Use the ASMCA tool or the SQL ALTER DISKGROUP statement to upgrade COMPATIBLE.ADVM attribute to the specified version.
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-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-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 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 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-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-03539: Base time stamp not found in log file.
Cause: Informational. The likely cause is that the running 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: Likely, the link name was a non-empty directory. OKS persistent logging was started but no symbolic was created to the target 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 specified logging directory was NFS mounted.
Action: Enter a node local location for the OKS log.
ADVM-03543: The OKS persistent log is not active.
Cause: The 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 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-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"
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-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-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-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: of the problem is unclear, contact Oracle Support Services.
Action: Correct the problem indicated by the other message(s). If the
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: of the problem is unclear, contact Oracle Support Services.
Action: Correct the problem indicated by the other message(s). If the
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: of the problem is unclear, contact Oracle Support Services.
Action: Correct the problem indicated by the other message(s). If the
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: of the problem is unclear, contact Oracle Support Services.
Action: Correct the problem indicated by the other message(s). If the
ADVM-05014: cannot verify replication configuration
Cause: of the problem is unclear, contact Oracle Support Services.
Action: Correct the problem indicated by the other message(s). If the
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 string 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: Failed to start replication: Either security or encryption or both is enabled on the file system.
Action: Undo security or encryption or both, then try to initialize replication again. To undo encryption and security respectively: acfsutil encr set -m <mount-point> -u acfsutil sec prepare -m <mount-point> -u
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 string 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 stringGB 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: string
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 stringGB per active node, actual free space left: stringGB
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-05158: Replication background processes are not running
Cause: Replication background processes were stopped.
Action: Run 'acfsutil repl bg start <mountpoint>' to restart replication background processes.
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-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. 05600-05604 reserved for replication exceptions
ADVM-05605: ACFS replication daemon string is exiting due to replication termination. string
Cause: Informational
Action: None 05606-05625 reserved for replication exceptions
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 primary mount point (<<<) to standby mount point (>>>):
Cause: Informational
Action: None
ADVM-05702: Testing for extra files on standby. Standby mount point (<<<) to primary mount point (>>>):
Cause: Informational
Action: None
ADVM-05703: Results for file comparison of primary to standby mount points:
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 on standby test:
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 primary file system is actively being modified or an internal error occurred.
Action: If possible, ensure the primary file system 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 >>> File missing!
Cause: The specified file was not replicated to the standby file system.
Action: None
ADVM-05715: Found: string
Cause: The specified file is an extra file on the standby file system.
Action: None
ADVM-05716: <<< Tag names exist on file string >>> No tag names exist on file string
Cause: The file on the primary file system has tag names but the file on the standby file system 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 >>> Extended attribute mismatch for string
Cause: Informational
Action: None
ADVM-05718: An unexpected result occurred during primary to standby comparison. Continuing. Affected files: string string
Cause: An unexpected result occurred when comparing the primary to the standby.
Action: None. The file was skipped.
ADVM-05719: An unexpected result occurred during standby to primary comparison. Continuing. Affected files: string string
Cause: An unexpected result occurred when comparing the standby to the primary.
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 primary file system was modified or an internal error occurred.
Action: If possible, do not modify files on the primary file system when running this tool.
ADVM-05722: A file read failed during a checksum operation: string
Cause: Either the primary file system was modified or an internal error occurred.
Action: If possible, do not modify files on the primary file system 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-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 specified standby mount point does not exist: "string" .
Cause: Failed to access the specified standby mount point.
Action: Use a networked file system to provide access to the standby file system on the primary node where the 'acfsutil repl compare' will be preformed.
ADVM-05733: Successfully compared: string string
Cause: Informational.
Action: None
ADVM-05734: Successfully verified existence: string 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 primary and standby mount points are the same path and will not be compared.
Cause: The provided primary and standby mount point paths resolved to the same location.
Action: Rerun the command specifying the unique mount point paths for the primary file system and the standby file system.
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 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-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 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 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 not be recoverable. It is strongly recommended that the file system be restored from 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 file system size: string for structure: string
Cause: An I/O request was made for data that exceeded the size of the file system."
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07023: read failed for metadata structure at disk offset: string size: number bytes structure type: string for structure: string
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: string
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 extent: _FileOffset: string _Length: string _PhysicalDiskOffset: string for file: string
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 found: string, but expected to find: string or string for structure: string
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 found: number, but expected to find: number for structure: string
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 found: number, but expected to find: >= 0 for structure: string
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 for file: string
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 found: string, but expected to find: string for structure: string
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 found: string, but expected to find: string for structure: string
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 found: number, but expected to find: number for structure: string
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 found: number maximum: number for structure: string
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 for structure: string
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 found: 0, but expected to find: > 0 for structure: string
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 found: number maximum: number for structure: string
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 found: string, but expected to find: string for structure: string
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: _FileOffset: string _Length: string _PhysicalDiskOffset: string _SnapIncarnationNumber: number for structure: string
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 calculated: string, but expected to find:string for structure: string
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 for file: string
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: string
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: found: string, but expected to find: string for structure: string
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 found: number, but expected to find: number for file: string
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 found: number, but expected to find: number for file: string
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 calculated: string, but expected to find: string for file: string
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: string
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 found: number, but expected to find: number for structure: string
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 found: number, but expected to find: number for file: string
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 found: number, but expected to find: number for file: string
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 found: number, but expected to find: number for file: string
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 found: number, but expected to find: number for file: string
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 found: string, but expected to find: string for file: string
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) found: string , but expected to find: 0 for file: string
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: _FileOffset: string _Length: string _PhysicalDiskOffset: string for file: string
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 found: string, but expected to find: 0 for file: string
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 found: string, but expected to find: 0 for file: string
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 for file: string
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 found: 0, but expected to find: > 0 for file: string
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 found: number maximum: number for file: string
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 found: string, but expected to find: string for file: string
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 found: string, but expected to find: string for file: string
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 found: string calculated: string for file: string
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: _FileOffset: string _Length: string _PhysicalDiskOffset: string _SnapIncarnationNumber: number for file: string
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 found: string, but expected to find: string for file: string
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 found: string, but expected to find: string for file: string
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 found: string minimum: string for file: string
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 found: string minimum: string for file: string
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] found: string, but expected to find: 0 for file: string
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] found: string, but expected to find: string for file: string
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] found: 0, but expected to find: > 0 for file: string
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] found: string maximum: string for file: string
Cause: The _PhysicalDiskOffset property in Extent[1] of the indicated Local_Bitmap exceeded the size of the file system.
Action: None
ADVM-07081: file has invalid _granularity value found: number, but expected to find: number for file: string
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 for file: string
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 found: number, but expected to find: number for file: string
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 _FileSize: string _AllocationSize: string for file: string
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 _FileSize: string _AllocationSize: string for file: string
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 found: string, but expected to find: multiple of string for file: string
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 _AllocationSize: string for file: string
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 found: string, but expected to find: multiple of number for file: string
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 found: string, but expected to find: 0 for file: string
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 found: number, but expected to find: number for file: string
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 found: number, but expected to find: 0 or 1 for file: string
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 for file: string
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 found: number maximum: number for file: string
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 found: 0, but expected to find: > 0 for file: string
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 found: string, but expected to find: string for file: string
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 found: string, but expected to find: string for file: string
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 found: string, but expected to find: string for file: string
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 found: string, but expected to find: string for file: string
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 found: string minimum: string for file: string
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 found: string, but expected to find: string for file: string
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 found: 0 for file: string
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 found: 0 for file: string
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 found: 0 for file: string
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 found: 0 for file: string
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) found: string valid values: string for file: string
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 found: number, but expected to find: number for file: string
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 found: string, but expected to find: string for file: string
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 found: string, but expected to find: string for file: string
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 found: string, but expected to find: string for file: string
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 found: string, but expected to find: string for file: string
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 found: string, but expected to find: string for file: string
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 found: number, but expected to find: number for file: string
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 found: string, but expected to find: 0 for file: string
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 found: 0, but expected to find: > 0 for file: string
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: found: string maximum: string for structure: string
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 for file: string
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 found: string, but expected to find: string for structure: string
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 found: number maximum: number for structure: string
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 found: string maximum: string for structure: string
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 found: string, but expected to find: string for structure: string
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 for structure: string
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 for structure: string
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 found: number, but expected to find: number for structure: string
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 found: string for structure: string
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 found: string, but expected to find: string for structure: string
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 found: string, but expected to find: string for structure: string
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 found: number, but expected to find: number for structure: string
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 found: number, but expected to find: number for structure: string
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 found: string, but expected to find: string for structure: string
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 found: string, but expected to find: string for structure: string
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 found: string, but expected to find: string for file: string
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 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 found: number, but expected to find: number for structure: string
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 found: string, but expected to find: string for structure: string
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 found: string, but expected to find: string for structure: string
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 found: string, but expected to find: string for structure: string
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 found: string, but expected to find: string for structure: string
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 found: string, but expected to find: string for structure: string
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 found: string, but expected to find: string for structure: string
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 found: string, but expected to find: string for structure: string
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 found: string, but expected to find: string for structure: string
Cause: The _mmap_log_fileid property of the indicated Global_Metadata_Directory structure was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07144: Global_Metadata_Directory structure has incorrect _repGlobalVFNPool_fileid value found: string, but expected to find: string for structure: string
Cause: The _repGlobalVFNPool_fileid property of the indicated Global_Metadata_Directory structure was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07145: Global_Metadata_Directory structure has incorrect _repl_config_tbl_fileid value found: string, but expected to find: string for structure: string
Cause: The _repl_config_tbl_fileid property of the indicated Global_Metadata_Directory structure was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07146: Global_Metadata_Directory structure has incorrect _repLogCutInitiatorBlock_fileid value found: string, but expected to find: string for structure: string
Cause: The _repLogCutInitiatorBlock_fileid property of the indicated Global_Metadata_Directory structure was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07147: Global_Metadata_Directory structure has incorrect _repLogCutInitiatorBlock_offset value found: string, but expected to find: string for structure: string
Cause: The _repLogCutInitiatorBlock_offset property of the indicated Global_Metadata_Directory structure was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07148: Global_Metadata_Directory structure has incorrect _snap_map_fileid value found: string, but expected to find: string for structure: string
Cause: The _snap_map_fileid property of the indicated Global_Metadata_Directory structure was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07149: Global_Metadata_Directory structure has incorrect _snaps_dir_fileid value found: string, but expected to find: string for structure: string
Cause: The _snaps_dir_fileid property of the indicated Global_Metadata_Directory structure was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07150: Global_Metadata_Directory structure has incorrect _global_tagdir_fileid value found: string, but expected to find: string for structure: string
Cause: The _global_tagdir_fileid property of the indicated Global_Metadata_Directory structure was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07151: Global_Metadata_Directory structure has incorrect _ea_change_fileid found: string, but expected to find: string for structure: string
Cause: The _ea_change_fileid property of the indicated Global_Metadata_Directory structure was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07152: orphan directory 'string' (file identifier: string) added to 'lost+found' directory
Cause: The indicated directory did not have a valid entry in any parent directory. The ACFS Fixer move the file to the 'lost+found' directory.
Action: No further action is needed.
ADVM-07154: An attempt to create a low-fragmentation memory heap failed. string will attempt to continue with the standard memory heap but may run out of memory.
Cause: A call to the Windows HeapCreate function failed. Refer to the accompanying message(s) for more information on the error.
Action: No further action is required unless there is an error using the standard memory heap. If there is an error using the standard memory heap then refer to the accompanying message(s) for information to resolve the problem.
ADVM-07155: An attempt to initialize a low-fragmentation memory heap failed. string will attempt to continue with the standard memory heap but may run out of memory.
Cause: A call to the Windows HeapSetInformation function failed. Refer to the accompanying message(s) for more information on the error.
Action: is required unless there is an error using the standard memory heap. To use low-fragmentation heaps, refer to Microsoft documentation on GlobalFlags values for executables that are not compatible with low-fragmentation heaps. Then use the regedit utility to unset those flags on the executable.
ADVM-07156: Local_Metadata_Directory structure has incorrect _map_file_disk_offset value found: string, but expected to find: string for structure: string
Cause: The _map_file_disk_offset property of the indicated Local_Metadata_Directory structure was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07157: Local_Metadata_Directory structure has incorrect _vol_log_disk_offset value found: string, but expected to find: string for structure: string
Cause: The _vol_log_disk_offset property of the indicated Local_Metadata_Directory structure was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07158: unable to create Security_Metadata file offset list for file: string
Cause: The ACFS Checker could not create the Security_Metadata file offset list. Refer to the accompanying message(s) for more information on the problem.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07159: Local_Metadata_Directory structure has incorrect _smf_fileid value found: string, but expected to find: string for structure: string
Cause: The _smf_fileid property of the indicated Local_Metadata_Directory structure was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07160: Local_Metadata_Directory structure has incorrect _it_rlog_fileid value found: string, but expected to find: string for structure: string
Cause: The _it_rlog_fileid property of the indicated Local_Metadata_Directory structure was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07161: Local_Metadata_Directory structure has incorrect _rlog_fileid value found: string, but expected to find: string for structure: string
Cause: The _rlog_fileid property of the indicated Local_Metadata_Directory structure was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07162: Local_Metadata_Directory structure has incorrect _it_rmap_file_fileid value found: string, but expected to find: string for structure: string
Cause: The _it_rmap_file_fileid property of the indicated Local_Metadata_Directory structure was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07163: Local_Metadata_Directory structure has incorrect _rmap_file_fileid value found: string, but expected to find: string for structure: string
Cause: The _rmap_file_fileid property of the indicated Local_Metadata_Directory structure was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07164: Local_Metadata_Directory structure has incorrect _repLocalVFNPool_fileid value found: string, but expected to find: string for structure: string
Cause: The _repLocalVFNPool_fileid property of the indicated Local_Metadata_Directory structure was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07165: invalid file identifier: string
Cause: The file identifier enetered must be a valid numeric value, greater than or equal to 0, and less than the maximum file identifier value for the file system.
Action: Re-enter a valid file identifier value.
ADVM-07168: Global_BitMap has incorrect value for bitmap size found: string, but expected to find: string for file: string
Cause: The bitmap size property of the indicated Global_BitMap file was incorrect. Its value did not the bitmap size that was calculated for the file system.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07169: Global_BitMap has incorrect _AllocationSize value found: string, but expected to find: string for file: string
Cause: The _AllocationSize property of the indicated Global_BitMap file was incorrect. The _AllocationSize value was not large enough to store the Global_BitMap data as determined by the ACFS Checker.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07170: Global_BitMap has incorrect values for Extent[0] found: _FileOffset: string _Length: string _PhysicalDiskOffset: string , but expected to find: _FileOffset: string _Length: string _PhysicalDiskOffset: string for file: string
Cause: The _PhysicalDiskOffset property of the first extent of the indicated Global_BitMap file was incorrect. The Global_BitMap data must begin at the disk offset described in the message.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07171: attempt to read SuperBlock FileEntry failed for file: string
Cause: An attempt to read SuperBlock metadata failed. Refer to the accompanying message(s) for more information on the problem.
Action: Correct the problem described in the accompanying messages if possible and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ADVM-07172: file has incorrect values for Extent[number] found: _FileOffset: string _Length: string _PhysicalDiskOffset: string , but expected to find: _FileOffset: string _Length: string _PhysicalDiskOffset: string for file: string
Cause: One or more values of an extent of the indicated file was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07175: file has incorrect values for Extent[number] found: _FileOffset: string _Length: string , but expected to find: _FileOffset: string _Length: string for file: string
Cause: One or more values of an extent of the indicated file was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07176: file has invalid _AllocationSize value found: string, but expected to find: string for file: string
Cause: The _AllocationSize property of the indicated file was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07177: file has incorrect _FileSize value found: string, but expected to find: string for file: string
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-07178: file has incorrect _granularity value found: number, but expected to find: number for file: string
Cause: The _granularity property of the indicated file was incorrect. Some ACFS internal files must have a _granularity value equal to -1 which indicates that the file has local extents.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07179: file has incorrect _NextFreeExtent value found: number, but expected to find: number for file: string
Cause: The _NextFreeExtent property of the indicated file was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07180: There is an inconsistency between the ACFS Map_File and the ACFS Log_File.
Cause: An inconsistency was found between the ACFS Map and Log Files which prevented the processing of transaction data.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07184: Log_File not processed for node number for file: string
Cause: A Log_File was found but not processed. Unprocessed Log_Files could result in false errors being reported because transaction data was not applied to the file system.
Action: There are two actions possible:

1. Run the ACFS Fixer which will automatically process all valid Log_Files.

2. Run the ACFS Checker and respond yes to any question pertaining to Log_File processing.

ADVM-07185: The ACFS Map _FileSize: number indicates that there is transaction data to be processed, but the ACFS Log _AllocationSize: number indicates that there is no data available. ACFS Map_File: string ACFS Log_File: for file: string
Cause: An inconsistency was found between the ACFS Map and Log Files which prevented the processing of transaction data.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07188: Map_File has entry with incorrect _Length value found: number for file: string
Cause: There are two possible causes:

1. The Map_File entry's _Length was equal to zero.

2. The Map_File entry's _Length was not a multiple of the volume's sector size as detailed in the message.

Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07189: Map_File has entry with incorrect _ActualDiskOffset value found: string minimum: string for file: string
Cause: The _ActualDiskOffset property for an entry in the indicated Map_File was incorrect. The _ActualDiskOffset value in a Map_File entry must be greater than the previous entry's _ActualDiskOffset.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07190: Map_File has an entry with invalid _LogDiskOffset value found: string minimum: string maximum: string for file: string
Cause: The _LogDiskOffset property for an entry in the indicated Map_File was incorrect. The _LogDiskOffset value in a Map_File entry must be within the corresponding Log_File data.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07191: Map_File has duplicate entries for _ActualDiskOffset:string for file: string
Cause: The indicated Map_File contained more than one entry for the same disk offset. _ActualDiskOffset values must be unique within a Map File.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07192: Map_File has incorrect Map_Entry _Length for the Volume_Disk_Header found: number, but expected to find: number for file: string
Cause: The _Length property for an entry in the indicated Map_File was incorrect. The entry was for a Volume_Disk_Header structure, but its _Length value did not match the size of a Volume_Disk_Header structure.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07193: Map_File entry with an invalid _ActualDiskOffset value found: string maximum: string for file: string
Cause: The _ActualDiskOffset property for an entry in the indicated Map_File was incorrect. The _ActualDiskOffset value that exceeded the size of this file system.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07195: metadata write failed while processing Volume_Log transaction data at disk offset: string for file: string
Cause: An error occurred while writing Volume_Log transaction data to the file system. Refer to the accompanying message(s) for more information.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07196: write failed for Map_File metadata structure at disk offset: string size: number bytes structure type: string for file: string
Cause: An attempt to write a metadata structure to disk failed. Refer to accompanying message(s) for more information on the problem.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07197: discarding Volume_Log and Map_File contents on node number due to processing error
Cause: An error occurred while processing file system transaction data. Refer to the accompanying message(s) for more information on the problem.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07199: write failed for Volume_Log metadata structure at disk offset: string size: number bytes structure type: string for file: string
Cause: An attempt to update a metadata structure of the indicated Volume_Log file failed. Refer to accompanying message(s) for more information on the problem.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07200: duplicate _SnapFetaFenum: string found for the following snapshots:
Cause: The _SnapFetaFenum property of the indicated snapshots had the same value. _SnapFetaFenum values must be unique.
Action: is needed. The ACFS Fixer will resolve the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ADVM-07201: Global_Free_Block list is corrupt
Cause: A metadata inconsistency was found within the Global_Free_Block list for the file system.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07202: Free_Block_List has incorrect _free_blk_count value found: string, but expected to find: string for structure: string
Cause: The _free_blk_count property of the indicated Free_Block_List was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07203: results for Snap_Map data may be limited or incorrect due to inconsistencies with Snap_Map metadata
Cause: The acfsdbg utility has identified the metadata inconsistency reported in the accompanying message.
Action: Run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ADVM-07204: write failed for Global_BitMap metadata structure at disk offset: string size: number bytes structure type: string for file: string
Cause: An attempt to update a metadata structure of the indicated Global_BitMap file failed. Refer to accompanying message(s) for more information on the problem.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07205: functionality may be limited due to File_Entry_Table metadata inconsistency
Cause: The acfsdbg utility has identified the metadata inconsistency reported in the accompanying message.
Action: Run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ADVM-07206: read failed for Local_BitMap metadata structure at disk offset: string size: number bytes structure type: string for file: string
Cause: An attempt to read a metadata structure of the indicated Local_BitMap file failed. Refer to accompanying message(s) for more information on the problem.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem
ADVM-07207: functionality related to snapshots disabled due to problems accessing Snap_Map file
Cause: The acfsdbg utility has identified the metadata inconsistency reported in the accompanying message.
Action: Run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ADVM-07208: Local_BitMap (file identifier: string) has incorrect size found: string, but expected to find: string for file: string
Cause: The size property of the indicated Local_BitMap was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07209: Local_BitMap (file identifier: string) has incorrect Global_BitMap file offset: string or incorrect disk offset: string for file: string
Cause: The Global_BitMap offset property of the indicated Local_BitMap was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07211: mismatch between Local_BitMap (file identifier: string) and temporary Global_BitMap for disk offset: string
Cause: The bitmap data of the indicated Local_BitMap did not match the corresponding bitmap data of the temporary Global_BitMap for the described disk offset.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07212: temporary Global_BitMap bit set for disk offset: string exceeds maximum offset: string
Cause: The bitmap data of the temporary Global_BitMap referenced storage that is beyond the size of this file system.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07215: Volume_Disk_Header has invalid _VolSignature value found: 'string' , but expected to find: string, string, string, or string for structure: string
Cause: The _VolSignature property of the indicated Volume_Disk_Header was not a valid ACFS volume signature.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07216: Volume_Disk_Header has incorrect _Checksum value found: string, but expected to find: string for structure: string
Cause: The _Checksum property of the indicated Volume_Disk_Header did not match its calculated value.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07217: Volume_Disk_Header version does not match string version found: number.number, but expected to find: number.number for structure: string
Cause: The _MajorVersionNumber and _MinorVersionNumber properties of the indicated Volume_Disk_Header did not match the version of the ACFS Checker/Fixer or ACFS debug utility that was being used. The ACFS Checker/Fixer or ACFS debug utility was not compatible with this file system. There are two possible causes:

1. The version information in the Volume_Disk_Header structure was not correct.

2. The ACFS Checker/Fixer or ACFS debug utility was not the correct version for the file system.

Action: There are two possible actions:

1. If the file system version displayed in the message is valid then run a compatible version of the ACFS Checker/Fixer or ACFS debug utility.

2. If the file system version displayed in the message is not valid then restore the file system from backup.

ADVM-07218: Volume_Disk_Header has incorrect _VolVolumeSize value found: string maximum: string - temporarily assuming Volume Size: string for structure: string
Cause: The _VolVolumeSize property of the indicated Volume_Disk_Header exceeded the size of the volume. The ACFS Checker temporarily assumed the maximum volume size during processing.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07219: Volume_Disk_Header has incorrect _VolVolumeSize value found: string minimum: string - temporarily assuming Volume Size: string for structure: string
Cause: The _VolVolumeSize property of the indicated Volume_Disk_Header was less than the minimum supported volume size as detailed in the message. The ACFS Checker temporarily assumed the maximum volume size during processing.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07220: Volume_Disk_Header has incorrect _VolClusterSize value found: string, but expected to find: string - assuming default size: string for structure: string
Cause: The _VolClusterSize property of the indicated Volume_Disk_Header was incorrect. The ACFS Checker temporarily assumed the default value during processing.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07221: Volume_Disk_Header has incorrect _VolFETALPosition value found: string, but expected to find: string - assuming default File_Entry_Table offset: string for structure: string
Cause: The _VolFETALPosition property of the indicated Volume_Disk_Header was incorrect. The ACFS Checker temporarily assumed the default File_Entry_Table offset during processing.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07222: Volume_Disk_Header has incorrect _VolOrigVolumeSize value found: string must be aligned on a string byte boundary for structure: 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-07223: Volume_Disk_Header has incorrect _VolExtentHeaderSize value found: string, but expected to find: string - assuming default value: string for structure: string
Cause: The _VolExtentHeaderSize property of the indicated Volume_Disk_Header was incorrect. The ACFS Checker temporarily assumed the default value during processing.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07224: cannot process command due to Snap_Map File metadata inconsistency
Cause: An acfsdbg command was not executed due to a metadata inconsistency.
Action: Run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ADVM-07225: Volume_Disk_Header has invalid _VolFileSystemEndian value found: character, but expected to find: string or string for structure: string
Cause: The _VolFileSystemEndian property of the indicated Volume_Disk_Header was invalid.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07226: Volume_Disk_Header has invalid _VolStateFlag values. found: string , but expected to find: string or string for structure: string
Cause: The _VolStateFlag property of the indicated Volume_Disk_Header contained one or more invalid values.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07227: missing snapshot name or identifier
Cause: A snapshot name or identifier was not entered as required for this command.
Action: Re-enter the command with a valid snapshot name or snapshot identifier.
ADVM-07228: cannot determine disk geometry for volume: string
Cause: The program was unable to determine the geometry of the indicated volume. Refer to the accompanying message(s) for more information on the problem.
Action: Correct the problem described in the accompanying messages if possible and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ADVM-07229: volume: string has invalid sector size found: number, but expected to find: number - assuming default value: number
Cause: The sector size of the indicated volume was invalid. The ACFS Checker temporarily assumed the default sector size during processing.
Action: Correct the problem described in the accompanying messages if possible and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ADVM-07230: cannot determine size for volume: string
Cause: The program was unable to determine the size of the indicated volume. Refer to the accompanying message(s) for more information on the problem.
Action: Correct the problem described in the accompanying messages if possible and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ADVM-07231: seek to end of volume failed for volume: string offset: string
Cause: The program was unable to seek to the end of the indicated volume. Refer to the accompanying message(s) for more information on the problem.
Action: Correct the problem described in the accompanying messages if possible and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ADVM-07232: seek to end of volume failed for volume: string requested offset: string returned offset: string
Cause: The request to seek to the end of the indicated volume failed. The offset set returned did not match the offset requested. Refer to the accompanying message(s) for more information on the problem.
Action: Correct the problem described in the accompanying messages if possible and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ADVM-07233: read failed for Primary Volume_Disk_Header at disk offset: string
Cause: An attempt to read the Primary Volume_Disk_Header at the indicated disk offset failed. Refer to the accompanying message(s) for more information on the problem.
Action: Correct the problem described in the accompanying messages if possible and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ADVM-07234: read failed for Alternate Volume_Disk_Header at disk offset: string
Cause: An attempt to read the Alternate Volume_Disk_Header at the indicated disk offset failed. Refer to the accompanying message(s) for more information on the problem. problem.
Action: Correct the problem described in the accompanying messages if possible and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ADVM-07235: extent[number] has invalid _PhysicalDiskOffset value found: 0, but expected to find: greater than 0 for file: string
Cause: The _PhysicalDiskOffset property of an extent structure of the indicated file had a value of zero. _PhysicalDiskOffset values must be greater than zero.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07236: extent[number] has invalid _PhysicalDiskOffset value found: 0, but expected to find: greater than 0 for structure: string
Cause: The _PhysicalDiskOffset property of an extent of the indicated extent structure had a value of zero. _PhysicalDiskOffset values must be greater than zero.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07237: read failed for File_Entry_Table extent metadata structure at disk offset: string for file: string
Cause: An attempt to read an extent metadata structure of the indicated file failed. Refer to the accompanying message(s) for more information on the problem.
Action: Correct the problem described in the accompanying messages if possible and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ADVM-07239: File_Entry_Table count incorrect found: number, but expected to find: number for file: string
Cause: The number of entries found in the File_Entry_Table file did not match the expected number of entries. One or more of the extent structures was invalid.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07240: Invalid Security_Metadata_File
Cause: File system checking has identified the metadata inconsistency reported in the message.
Action: is needed. The ACFS Fixer will resolve the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ADVM-07241: Security_Metadata file has invalid _security_descriptor record for file: string
Cause: A _security_descriptor record of the indicated Security_Metadata file was invalid.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07243: Security_Metadata file has no valid _security_data records for file: string
Cause: The indicated Security_Metadata file did not contain any valid valid _security_data records.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07245: Security_Metadata file contains invalid _security_descriptor data for file: string
Cause: The indicated Security_Metadata file contained at least one invalid _security_data record. Refer to the accompanying message(s) for more information on the problem.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07246: Security_Metadata file _Private structure is invalid for: for file: string
Cause: The _Private structure of the indicated Security_Metadata file was invalid. Refer to the accompanying message(s) for more information on the problem.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07247: Security_Metadata file has invalid Hash_Table data for file: string
Cause: The Hash_Table of the indicated Security_Metadata file contained inconsistent data. Refer to the accompanying message(s) for more information on the problem.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07250: Security_Metadata file _Private structure has invalid _maxFree value found: number minimum: number for structure: string
Cause: The _maxFree property of the indicated _Private metadata structure was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07251: Security_Metadata file _Private structure has invalid _freeDataListTail value found: number minimum: number for structure: string
Cause: The _freeDataListTail property of the indicated _Private metadata structure was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07252: Security_Metadata file node not on _freeDataList for file: string
Cause: One or more of the _security_data nodes of the indicated Security_Metadata file was not found on the free data node list. The _next property for one or more of the _security_data nodes was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07254: Security_Metadata file has invalid _security_record for _Administrator default for file: string
Cause: The default _Administrator _security_record of the indicated Security_Metadata file was invalid.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07256: file has unexpected _ProtectionBits value found: number, but expected to find: number for file: string
Cause: The _ProtectionBits property of the indicated files was not expected.
Action: No action is needed if the protection bits were intentionally set differently from the default.
ADVM-07257: unable to process request for volume string; volume is not open
Cause: An attempt to read metadata failed because the volume was not open. Refer to the accompanying messages for more information on the problem.
Action: Correct the problem described in the accompanying messages if possible and rerun the acfsdbg utility.
ADVM-07258: unable to reset context to snapshot string due to File_Entry_Table metadata inconsistency
Cause: The acfsdbg utility has identified the metadata inconsistency reported in the accompanying message.
Action: Run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services. Services.
ADVM-07259: file system does not contain a valid Local_Metadata_Directory
Cause: There was no valid Local_Metadata_Directory in the file system. At least one Local_Metadata_Directory is required.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07260: Volume_Disk_Header has incorrect _VolNumOFSNodes value found: number, but expected to find: number for structure: string
Cause: The _VolNumOFSNodes property of the indicated Volume_Disk_Header structure was incorrect. Its value did not match the number of valid ACFS nodes found.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07261: unable to reset context to snapshot string due to Snap_Map file metadata inconsistency
Cause: The acfsdbg utility has identified the metadata inconsistency reported in the accompanying message.
Action: Run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ADVM-07262: unable to reset context to snapshot %(1) because it no longer exists
Cause: The identified snapshot no longer exists due to on-disk metadata changes that are allowed whenever the acfsdbg utility is operating in read-only mode.
Action: Enter the 'primary' or 'snap <snapshot name>' command to set context.
ADVM-07263: Free_Block_List has incorrect _first_free_group value found: number, but expected to find: number for structure: string
Cause: The _first_free_group property of the indicated Free_Block_List structure was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07264: Free_Block_List has incorrect _last_free_blk value found: number, but expected to find: number for structure: string
Cause: The _last_free_blk property of the indicated Free_Block_List structure was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07265: write failed for Free_Block metadata structure at disk offset: string size: number bytes for structure: string
Cause: An attempt to write a Free_Block metadata structure to disk failed. Refer to accompanying message(s) for more information on the problem.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07266: write failed for Free_Block_List metadata structure at disk offset: string size: number bytes for structure: string
Cause: An attempt to write a Free_Block_List metadata structure to disk failed. Refer to accompanying message(s) for more information on the problem.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07267: file marked for deletion (file identifier: string, disk offset: string) cannot be removed due to inconsistent file metadata
Cause: Inconsistent metadata was found for the indicated file that was marked for deletion. The file could not be deleted.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07268: file marked for deletion (file identifier: string, disk offset: string) has invalid _LinkCount value found: number, but expected to find: 0
Cause: The indicated file was marked for deletion, but its _LinkCount property was not zero. Files to be deleted must have a _LinkCount value of zero. The file could not be deleted.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07269: file marked for deletion (file identifier: string, disk offset: string) has invalid _SynchFlag value found: string , but expected to find: string
Cause: The _SynchFlag property of the indicated file was incorrect. The file was marked for deletion but its _SynchFlag did not have the appropriate value. The file could not be deleted.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07271: orphan file : string (file identifier: string) added to 'lost+found' directory
Cause: The indicated file did not have a valid entry in any parent directory. The ACFS Fixer move the file to the 'lost+found' directory.
Action: No further action is needed.
ADVM-07272: read failed for extent metadata structure at disk offset: string for file: string
Cause: An attempt to read an extent metadata structure for the indicated file failed. Refer to the accompanying message(s) for more information on the problem.
Action: Correct the problem described in the accompanying messages if possible and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ADVM-07274: missing or invalid snapshot name
Cause: No snapshot name was provided or the name entered was not valid.
Action: Re-enter the command with a valid snapshot name.
ADVM-07275: cannot read File_Entry_Table _FileEntry metadata structure - file system validation cannot continue
Cause: An attempt to read the _FileEntry metadata structure of the File_Entry_Table failed. The File_Entry_Table is a critical ACFS metadata structure that is required for file system validation or repairs. The ACFS Checker/Fixer could not process the file system. NOTE: It is also possible that there was no ACFS file system on this volume.
Action: Correct the problem indicated by the accompanying messages if possible and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows). If the problem cannot be resolved then restore the file system from a backup copy.
ADVM-07276: File_Entry_Table _FileEntry metadata structure is invalid - file system validation cannot continue
Cause: The File_Entry_Table's _FileEntry metadata structure is either corrupt or is missing critical information. NOTE: It is also possible that there is no ACFS file system on the volume.
Action: Restore the file system from a backup copy.
ADVM-07280: checking File_Entry_Table entry: string at disk offset: string
Cause: The ACFS Checker found a File_Entry_Table entry that has not been processed. This entry was an orphan file or an orphan internal metadata structure.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07282: read failed for File_Entry_Table entry: string at disk offset string
Cause: An attempt to read a File_Entry_Table entry failed. Refer to the accompanying message(s) for more information on the problem.
Action: Correct the problem described in the accompanying messages if possible and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ADVM-07283: orphan File_Entry_Table metadata structure found for identifier: string at disk offset: string structure type: string
Cause: A File_Entry_Table entry was found that had not been processed. This entry was an orphan file or an invalid internal metadata structure.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07284: orphan system file found for file identifier: string at disk offset:string
Cause: The indicated system file did not have a valid parent directory.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07285: snapshot: string (identifier: number) has invalid File_Entry_Table identifier: string that exceeds the maximum value for this file system: string
Cause: The acfsdbg utility has identified the metadata inconsistency reported in the accompanying message.
Action: Run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ADVM-07286: orphan file found for file identifier: string at disk offset: string
Cause: The indicated file did not have a valid parent directory.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07287: orphan Free_Block metadata structure found for file identifier: string at disk offset: string
Cause: The indicated Free_Block metadata structure was not found on any free block list.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07288: orphan file 'string' (file identifier: string) added to 'lost+found' directory
Cause: The indicated file did not have a valid entry in any directory which meant that the file did not have a valid file name. The file was given the generic name described in the message and moved to the 'lost+found' directory.
Action: No further action is needed.
ADVM-07289: orphan Local_Metadata_Directory metadata structure found for file identifier: string at disk offset: string
Cause: The indicated Local_Metadata_Directory metadata structure was not found on any _Locator list for Local_Metadata_Directory structures.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07290: orphan Free_List_Header metadata structure found for file identifier: string at disk offset: string
Cause: The indicated Free_List_Header metadata structure was not found on any valid Local_Metadata_Directory structure.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07291: orphan _Locator metadata structure found for file identifier: string at disk offset: string
Cause: The indicated _Locator metadata structure was not found in any list of valid _Locator structures.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07292: orphan Global_Metadata_Directory metadata structure found for file identifier: string at disk offset: string
Cause: The File_Entry_Table contained a duplicate Global_Metadata_Directory metadata structure. Global_Metadata_Directory structures must be unique.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07294: orphan Global_Virtual_FileID_Pool metadata structure found for identifier: string at disk offset: string
Cause: The File_Entry_Table contained a duplicate entry for the Global_Virtual_FileID_Pool metadata structure. Global_Virtual_FileID_Pool structures must be unique.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07295: orphan Local_Virtual_FileID_Pool metadata structure found for identifier: string at disk offset: string
Cause: The indicated Local_Virtual_FileID_Pool metadata structure was not found on any valid Local_Metadata_Directory structure.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07296: orphan Replication_Log_Initiator metadata structure found for identifier: string at disk offset: string
Cause: The File_Entry_Table contained a duplicate entry for a Replication_Log_Initiator metadata structure. Replication_Log_Initiator structures must be unique.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07297: File_Entry_Table entry: string at disk offset: string is not a valid metadata structure
Cause: The indicated entry in the File_Entry_Table was not a metadata structure recognized by ACFS.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07298: cannot convert file identifier: 'string' to numeric value
Cause: The format entered for the file identifier was invalid.
Action: Use the acfsdbg utility help (-h) option for a list of commands and format options for entering data.
ADVM-07300: directory Hash_Table contains duplicate entries for offset: string for file: string
Cause: The Hash_Table of the indicated directory file had duplicate entries for the offset described in the message. Hash_Table entries must map to unique offsets.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07301: directory _hash_key: string for offset: string has no corresponding file entry for file: string
Cause: The _hash_key property of the indicated directory file was invalid. Its value did not reference a valid file entry.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07302: directory _hash_key for offset: string is incorrect found: string, but expected to find: string for file: string
Cause: The _hash_key property of the indicated directory file was incorrect. Its value did not match the hash value calculated for the corresponding file entry.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07303: Security_Metadata file Hash_Table contains multiple entries for offset: string for file: string
Cause: The Hash_Table of the indicated Security_Metadata file had duplicate entries for the offset described in the message. Hash_Table entries must map to unique offsets.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07304: Security_Metadata file _hash_key: string for offset: string has no corresponding entry for file: string
Cause: The _hash_key property of the indicated Security_Metadata file was invalid. Its value did not reference a valid entry.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07305: Security_Metadata file _hash_key for offset: string is incorrect found: string, but expected to find: string for file: string
Cause: The _hash_key property of the indicated Security_Metadata file was incorrect. Its value did not match the hash value calculated for the corresponding entry.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07306: Hash_Table _hash_key order is incorrect for file: string
Cause: The _hash_key properties of the Hash_Table of the indicated file were not ordered correctly.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07308: Hash_File_Index structure for block number at disk offset: string already processed for file: string
Cause: The Hash_File node list of the indicated file was invalid. One or more of the Hash_File structures had an invalid _next property.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07309: cannot access Hash_File_Index node metadata structure at disk offset: string for file: string
Cause: An attempt to access the indicated Hash_File_Index metadata structure failed. Refer to the accompanying message(s) for more information on the problem.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07310: Hash_File_Index node has incorrect _next value found: string, but expected to find: string for file: string
Cause: The _next property of the indicated Hash_File_Index structure was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07311: Hash_Bucket for block number at disk offset: string already processed for structure: string
Cause: The Hash_Bucket structure of the indicated file has already been processed. One or more of the Hash_File structures had an invalid _next property.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07312: cannot access Hash_Bucket metadata structure at disk offset: string for file: string
Cause: An attempt to access the indicated Hash_Bucket metadata structure failed. Refer to the accompanying message(s) for more information on the problem.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07313: Hash_Bucket has incorrect _controlling_bkt value found: number, but expected to find: number for structure: string
Cause: The _controlling_bkt property of the indicated Hash_Bucket structure was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07314: Hash_Bucket has incorrect _split_count value found: number, but expected to find: number for file: string
Cause: The _split_count property of the indicated Hash_Bucket structure was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07315: Hash_Bucket has incorrect _next value found: number, but expected to find: number for file: string
Cause: The _next property of the indicated Hash_Bucket structure was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07316: cannot access Hash_File_Master_Block metadata structure at disk offset: string for file: string
Cause: An attempt to access the indicated Hash_File_Master_Block metadata structure failed. Refer to the accompanying message(s) for more information on the problem.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07317: Hash_File metadata structure for block:number at disk offset: string already processed for file: string
Cause: The list of nodes of the indicated Hash_File file was invalid. One or more of the Hash_File structures had an invalid _next property.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07318: Hash_File_Master_Block structure has incorrect _initial_bkt_count value found: number, but expected to find: number for structure: string
Cause: The _initial_bkt_count property of the indicated Hash_File_Master_Block structure was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07319: Hash_File_Master_Block structure has incorrect _double_count value found: number, but expected to find: number for file: string
Cause: The _double_count property of the indicated Hash_File_Master_Block structure was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07320: Hash_File_Master_Block structure has incorrect value for entry number in _hash_bucket_group array found: number, but expected to find: number for structure: string
Cause: The entry in _hash_bucket_group array of the indicated Hash_File_Master_Block was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07321: _hash_entry number has no corresponding entry for file: string
Cause: The _hash_entry property in the Hash_Table of the indicated file did not have a valid entry associated with it.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07322: metadata read failed at disk offset: string size: number bytes for file: string
Cause: An attempt to read metadata of the indicated file failed. Refer to the accompanying message(s) for more information on the problem.
Action: Correct the problem described in the accompanying messages if possible and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ADVM-07326: metadata read failed at disk offset: string bytes requested: number bytes returned: number for file: string
Cause: An attempt to read metadata of the indicated file failed. The amount of data returned did not match the amount requested. Refer to the accompanying message(s) for more information on the problem.
Action: Correct the problem described in the accompanying messages if possible and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ADVM-07327: metadata write failed at disk offset: string size: number bytes for file: string
Cause: An attempt to write metadata of the indicated file failed. Refer to accompanying message(s) for more information on the problem.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07331: metadata write failed at disk offset: string bytes requested: number bytes written: number for file: string
Cause: An attempt to write metadata of the indicated file failed. The amount of data written did not match the amount requested. Refer to the accompanying message(s) for more information on the problem.
Action: Correct the problem described in the accompanying messages if possible and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ADVM-07332: cannot convert snapshot identifier: 'string' to numeric value
Cause: The format entered for the snapshot identifier was invalid.
Action: Use the acfsdbg utility help (-h) option for a list of commands and format options for entering data.
ADVM-07333: invalid snapshot identifier entered: string minimum: 1 maximum: number
Cause: The snapshot identifier entered was not within the valid range for this file system.
Action: Re-enter the command with a snapshot identifier that is within the valid range described in the message.
ADVM-07334: invalid snapshot name 'string' entered
Cause: The snapshot name entered did not exist.
Action: Re-enter the command with the name or identifier of a valid snapshot.
ADVM-07335: Directory_Node has invalid _dir_entry_free_list_tail value found: number maximum: number for structure: string
Cause: The _dir_entry_free_list_tail property of the indicated Directory_Node structure was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07336: Directory_Node structure has invalid _next_free_dirnode value found: number maximum: number for structure: string
Cause: The _next_free_dirnode property of the indicated Directory_Node structure was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07337: Directory_Entry structure has incorrect file identifier for file 'string' found: string, but expected to find: string for structure: string
Cause: The file identifier property of the indicated Directory_Entry structure did not match the file identifier of the corresponding file.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07338: Directory_Entry structure has incorrect _rec_len value for file 'string' found: number, but expected to find: number for structure: string
Cause: The _rec_len property of the indicated Directory_Entry structure was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07339: Directory_Entry structure has incorrect _name_len value for file 'string' found: number, but expected to find: number for structure: string
Cause: The _name_len property of the indicated Directory_Entry structure was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07340: Directory_Entry structure has invalid or incorrect _attributes for file 'string' found: string , but expected to find: string for structure: string
Cause: The _attributes property of the indicated Directory_Entry structure did not match the _attributes property of the corresponding file.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07341: starting disk offset string exceeds ending disk offset string
Cause: The starting storage map offset was greater than the ending offset.
Action: Re-enter the command with valid disk offsets.
ADVM-07342: Directory_Entry structure has incorrect filename for file found: 'string', but expected to find: 'string' for structure: string
Cause: The filename property of the indicated Directory_Entry structure did not match the name of the file.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07343: unused Directory_Entry structure has incorrect _name_len value found: number, but expected to find: number for structure: string
Cause: The _name_len property of the indicated Directory_Entry structure was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07344: Directory_Entry structure has incorrect _rec_len value for file 'string' found: number maximum: number for structure: string
Cause: The _rec_len property of the indicated Directory_Entry structure was greater than the maximum value.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07345: Directory_Entry structure has incorrect _rec_len value for file 'string' found: number minimum: number for structure: string
Cause: The _rec_len property of the indicated Directory_Entry structure was less than the minimum value.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07346: Directory_Entry structure has invalid _name_len value found: number operating system maximum: number for structure: string
Cause: The _name_len property of the indicated Directory_Entry structure was greater than the maximum value for this operating system.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07347: Directory_Entry structure has incorrect _name_len value found: number maximum: number for structure: string
Cause: The _name_len property of the indicated Directory_Entry structure was greater than the maximum value for this entry.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07350: command disabled due to lack of File_Entry_Table context; enter 'primary' or 'snap' to set context
Cause: The acfsdbg utility could not process the request because the File_Entry_Table context was not set. The acfsdbg utility requires a valid File_Entry_Table context to locate on-disk metadata structures.
Action: Enter 'primary' or 'snap <snapshot name>' command to set context.
ADVM-07351: requested Snap_Info_Entry structure not available due to inconsistencies with Snap_Map metadata
Cause: The acfsdbg utility has identified the metadata inconsistency reported in the accompanying message.
Action: Run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ADVM-07352: snapshot directory contains files with incorrect attributes; attempting to continue processing
Cause: The _attributes property for a file in the indicated snapshot directory was incorrect. The _attributes value indicated that the file was not a directory. All files in a snapshot directory must be directories.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07354: file has incorrect or invalid _attributes value found: string , but expected to find: string for file: string
Cause: The _attributes property of the indicated file was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07355: Cannot fix orphaned files because the lost+found directory is damaged.
Cause: Fsck could not move the orphan files because there was an inconsistency with the lost+found directory. Files that do not have a valid parent directory are considered to be orphan files and are moved to the lost+found directory.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07356: file is a symbolic link but has no storage for the target name for file: string
Cause: The indicated file was a symbolic link but did have a target. The target of a symbolic link must have storage.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07360: deleting file due to invalid _attributes: string file: string
Cause: The _attributes property of the indicated file was invalid. The file must be deleted in order to preserve the integrity of the file system.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07361: truncating file 'string' to number bytes for file: string
Cause: The indicated file was truncated in order to preserve file system integrity.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07363: Volume_Disk_Header has invalid _VolFeatureFlag values. found: string , but expected to find: string or string for structure: string
Cause: File system checking has identified the metadata inconsistency reported in the message.
Action: is needed. The ACFS Fixer will resolve the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ADVM-07364: file has incorrect values for Extent[number] found: _Length: string _PhysicalDiskOffset: string , but expected to find: _Length: string _PhysicalDiskOffset: string for file: string
Cause: One or more or the extent properties of the indicated file was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07365: extent metadata structure has incorrect values for Extent[number] found: _FileOffset: string _Length: string _PhysicalDiskOffset: string , but expected to find: _FileOffset: string _Length: string _PhysicalDiskOffset: string for structure: string
Cause: One or more properties of the indicated extent metadata structure was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07366: directory has incorrect _attributes value found: string , but expected to find: string for file: string
Cause: The _attributes property of the indicated directory file was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07369: directory has invalid _FileSize value found: number minimum: number for file: string
Cause: The _FileSize property of the indicated directory file was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07370: directory has invalid _FileSize: string _AllocationSize: string values for file: string
Cause: The _FileSize and _AllocationSize properties of the indicated directory file were incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07374: cannot access directory _Private structure for block number at disk offset: string for file: string
Cause: An attempt to access the indicated directory _Private metadata structure failed. Refer to the accompanying message(s) for more information on the problem.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07375: directory _Private structure at disk offset: string contains invalid data for file: string
Cause: The _Private structure of the indicated directory file contained invalid data. Refer to the accompanying message(s) for more information on the problem.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07376: directory _Private structure has incorrect header type at disk offset: string, this file may not be a directory found: string, but expected to find: string for file: string
Cause: The indicated file did not contain a _Private directory metadata structure as required for directory files. It appeared that the file was incorrectly identified as being a directory.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07377: directory has invalid node list for file: string
Cause: The node list of the indicated directory file was invalid. There are three possible causes:

1. One or more of the file's directory structures had an invalid structure header.

2. The _next_dirnode property of one or more of the file's directory structures was incorrect.

3. The _first_dirnode property of the _Private directory structure was incorrect.

Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07378: directory _Private structure has incorrect _last_dirnode value found: number, but expected to find: number for file: string
Cause: The _last_dirnode property of the indicated _Private directory structure was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07379: directory has invalid free block list for file: string
Cause: The free block list of the indicated directory file was invalid. There are three possible causes:

1. One or more of the file's directory structures had an invalid structure header.

2. The _next_free_dirnode property of one or more of the file's directory structures was incorrect.

3. The _dir_entry_free_list_head property of the _Private directory structure was incorrect.

Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07381: directory _Private structure has incorrect _dir_entry_free_list_tail value found: number, but expected to find: number for file: string
Cause: The _ dir_entry_free_list_tail property of the indicated _Private directory structure was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07382: directory has invalid hash block free list; invalid reference for free hash block found: number maximum: number for file: string
Cause: The hash block free list of the indicated directory file was invalid. There are two possible causes:

1. The _hash_blk_free_list property of the _Private directory structure referenced a block that exceeded the directory's size.

2. The _next_free_blk property of a directory free block referenced a block that exceeded the directory's size.

Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07383: directory has invalid hash block free list for file: string
Cause: The free hash block list of the indicated directory file was invalid. There are three possible causes:

1. One or more of the file's directory structures had an invalid structure header.

2. The next_free_blk property of one or more of the file's directory structures was incorrect.

3. The hash_blk_free_list property of the _Private directory structure was incorrect.

Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07384: snapshot: string (identifier: number) has invalid _SnapIncarnationNumber found: 0, but expected to find: > 0 for structure: string
Cause: File system checking has identified the metadata inconsistency reported in the message.
Action: is needed. The ACFS Fixer will resolve the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ADVM-07385: directory has orphan Directory_Node metadata structure for block number at disk offset: string for file: string
Cause: The indicated directory file had a Directory_Node metadata structure that was not found on any directory node list.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07386: directory has incorrect _FileSize value found: string, but expected to find: string for file: string
Cause: The _FileSize property of the indicated directory file was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07388: directory contains invalid _Private structure for block number at disk offset: string for file: string
Cause: A _Private metadata structure of the indicated directory file was found in the wrong block. _Private metadata structures must be located at block one of a directory's metadata.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07389: directory has orphan free block number at disk offset: string for file: string
Cause: The indicated directory file had a free block that was not found on the directory's free list.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07391: directory has invalid metadata structure string type for block number at disk offset: string for file: string
Cause: The structure found at the block of the indicated directory file was not a valid directory metadata structure.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07392: Directory_Entry has incorrect or invalid _attributes value found: string , but expected to find: string for file: string
Cause: The _attributes property of the indicated Directory_Entry was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07395: directory has incorrect or invalid _attributes values found: string , but expected to find: string for file: string
Cause: The _attributes property of the indicated directory file was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07396: directory has incorrect Hash_Table data for file: string
Cause: The Hash_Table of the indicated directory file contained inconsistent data. Refer to the accompanying message(s) for more information on the problem.
Action: Correct the problem described in the accompanying messages if possible and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ADVM-07399: directory has incorrect _LinkCount value found: number, but expected to find: number for file: string
Cause: The _LinkCount property of the indicated directory file was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07400: mismatch between _NOLSTXPTR feature and _NOUPHDRPTR feature _NOLSTXPTR: string _NOUPHDRPTR: string for file: string
Cause: File system checking has identified the metadata inconsistency reported in the message.
Action: is needed. The ACFS Fixer will resolve the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ADVM-07401: write failed for Deferred_Remove_File_List metadata structure at disk offset: string size: number bytes structure type: string for file: string
Cause: An attempt to write metadata on the indicated file failed. Refer to accompanying message(s) for more information on the problem.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07402: Deferred_Delete_Storage_List structure has invalid delete list pointers: _PrevDeferredListLink: string _NextDeferredListLink: string for structure: string
Cause: The _PrevDeferredListLink or _NextDeferredListLink property of of the indicated structure were incorrect. Both values must be zero or non-zero.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07403: write failed for Deferred_Remove_Storage_List metadata structure at disk offset: string size: number bytes structure type: string for file: string
Cause: An attempt to write metadata of the indicated failed. Refer to accompanying message(s) for more information on the problem.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07407: Snap_Map_Header contains invalid _SnapCreatePending field found: 0, but expected to find: > 0 for structure: string
Cause: The acfsdbg utility has identified the metadata inconsistency reported in the accompanying message.
Action: Run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ADVM-07408: Snap_Map_Header contains invalid _SnapDeletePending field found: 0, but expected to find: > 0 for structure: string
Cause: The acfsdbg utility has identified the metadata inconsistency reported in the accompanying message.
Action: Run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ADVM-07411: snapshot metadata checking will be limited due to an error reading snapshot metadata
Cause: An attempt to read snapshot metadata failed. Snapshot validation was limited since not all snapshot metadata was not available.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07413: unable to create internal structure needed for processing
Cause: Refer to the accompanying message(s) for more information on the problem.
Action: Correct the problem described in the accompanying messages if possible and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ADVM-07414: snapshot: string (identifier: number) has invalid snap_map_tuples for file: string
Cause: File system checking has identified the metadata inconsistency reported in the message.
Action: is needed. The ACFS Fixer will resolve the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ADVM-07415: invalid snap_map_tuple: ( string, string ) for disk offset: string
Cause: File system checking has identified the metadata inconsistency reported in the message.
Action: is needed. The ACFS Fixer will resolve the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ADVM-07416: file has invalid _FileSize value found: string minimum: string for file: string
Cause: The _FileSize property of the indicated file was invalid.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07417: Snap_Map_Header structure has invalid _snap_incarnation values; _SnapHighestActiveIncarnNumber: number must be less than _SnapNextIncarnationNumber: number for structure: string
Cause: One or both of the _SnapHighestActiveIncarnNumber and _SnapNextIncarnationNumber properties of the indicated Snap_Map_Header metadata structure was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07418: Snap_Map_Header structure has invalid _SnapCreatePending value found: number, but expected to find: number or < number for structure: string
Cause: The _SnapCreatePending property of the indicated Snap_Map_Header metadata structure was incorrect. The _SnapCreatePending value must be zero or less than the value indicated in the message.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07419: Snap_Map_Header structure has invalid _SnapDeletePending value found: number, but expected to find: number or < number for structure: string
Cause: The _SnapDeletePending property of the indicated Snap_Map_Header metadata structure was incorrect. The _SnapDeletePending value must be zero or less than the value indicated in the message.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07420: found partially created snapshot for snapshot: 'string'
Cause: Initialization of the indicated snapshot did not complete. There are two possible causes:

1. The volume went offline while the snapshot was being created.

2. The process creating the snapshot was unexpectedly terminated do to a shutdown of the system.

Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem. The ACFS Fixer will remove this snapshot.
ADVM-07421: found partially deleted snapshot
Cause: A snapshot was not completely deleted. There are several possible causes:

1. The volume was unmounted before the asynchronous phase of snapshot deletion had completed.

2. The volume went offline while the snapshot was being deleted.

3. The process deleting the snapshot was unexpectedly terminated do to a shutdown of the system.

Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem. The ACFS Fixer will remove this snapshot.
ADVM-07423: snapshot 'string' has invalid file identifier found: string maximum: string for structure: string
Cause: The file identifier property of the indicated snapshot was invalid. Its value exceeded the maximum value for the file system.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07424: snapshot 'string' has invalid _SnapIncarnationNumber value found: number maximum: number for structure: string
Cause: The _SnapIncarnationNumber property of the indicated snapshot was invalid.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07425: snapshot (_snapid value: string) has invalid name: 'string' for structure: string
Cause: The name of indicated snapshot contained invalid characters.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07426: snapshot 'string' has invalid _SnapVisibility value found: number, but expected to find: number or number for structure: string
Cause: The _SnapVisibility property of the indicated snapshot was invalid.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07427: duplicate _SnapIncarnationNumber: number found for snapshots 'string' and 'string'
Cause: The _SnapIncarnationNumber property of the indicated snapshots had the same value. _SnapIncarnationNumber values must be unique across all snapshots.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem. The ACFS Fixer will delete the second snapshot.
ADVM-07429: Snap_Map_Header structure has incorrect _SnapCount value found: number, but expected to find: number for structure: string
Cause: The _SnapCount property of the indicated Snap_Map_Header metadata structure was incorrect. The _SnapCount value did not match the number of valid snapshots found.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07430: cannot determine free space for volume associated with directory 'string'; attempting to continue with current directory 'string'
Cause: A temporary file is needed to store information during processing. This file was targeted for the indicated directory. The ACFS Checker was unable to determine the mount of space available for the volume associated with the directory. Refer to the accompanying message(s) for more information on the problem.
Action: No further action is needed. The ACFS Checker/Fixer will attempt to continue processing with the current directory.
ADVM-07431: cannot determine free space for volume associated with current directory 'string'
Cause: A temporary file is needed to store information during processing. This file was targeted for the current directory. The ACFS Checker was unable to determine the mount of space available for the volume associated with the directory. Refer to the accompanying message(s) for more information on the problem.
Action: Correct the problem described in the accompanying messages if possible and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ADVM-07432: insufficient space available to store temporary file in directory 'string' or directory 'string' space needed: number bytes - unable to continue
Cause: A temporary file is needed to store information during processing but there was not enough space to store the file in either of the The size of this file is dependent on the size of the file system. indicated directories.
Action: Provide sufficient space as described in the message to store the the temporary file in either of the indicated directories. Rerun the ACFS Checker/Fixer once there is sufficient storage to store the temporary file.
ADVM-07435: invalid path name length for temporary file length: number minimum: number maximum: number
Cause: The path name for a temporary file does not exist or its length exceeds the maximum for this system. Refer to the accompanying message(s) for more information on the problem.
Action: Correct the problem described in the accompanying messages if possible and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ADVM-07436: string has encountered an internal error: invalid parameter passed to fb_create
Cause: The ACFS Checker/Fixer or ACFS Debug utility has encountered an unexpected, internal error.
Action: Contact Oracle Support Services.
ADVM-07437: string has encountered an internal error: invalid parameter passed to fb_ref disk offset: string size: string fbSize: string fbCacheSize: string
Cause: The ACFS Checker/Fixer or ACFS Debug utility has encountered an unexpected, internal error.
Action: Contact Oracle Support Services.
ADVM-07438: file has storage allocated to it that is also allocated to another file for file: string
Cause: Storage allocated to the indicated file was also allocated to at least one other file. Storage can only be allocated to a single file. Storage can never be allocated to multiple files.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07439: Snapshot_BitMap conflicts with the Global_BitMap for disk offset: string
Cause: One or more snapshot bitmaps claimed storage that was also claimed by the Global_BitMap.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem. The ACFS Fixer will remove all snapshots whose bitmap conflicts with the Global_BitMap.
ADVM-07440: Snapshot_BitMap has bit set for non-existing snapshot for disk offset: string
Cause: One or more bitmaps reserved for unused snapshot incorrectly claimed storage. Bitmaps for snapshots that are not in use cannot claim any storage.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07441: Snapshot_BitMap has bits set for storage at disk offset: string that is beyond the file system size
Cause: One or more snapshot bitmaps incorrectly claimed storage that exceeded the size of the file system.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07443: Global_BitMap has invalid value for number of bits set found: string maximum: string for file: string
Cause: The Global_BitMap property that indicates the number of bits set exceeded the size of the bitmap.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07444: Global_BitMap has invalid value for number of bits set. found: string, but expected to find: string for file: string
Cause: The Global_BitMap property that indicates the number of bits set did not match the amount of storage allocated to all valid files.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07445: Global_BitMap has invalid value for next offset to search found: string maximum: string for file: string
Cause: The Global_BitMap property that indicates the next offset to search for available bits to allocate exceeded the size of the bitmap.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07446: mismatch between temporary Global_BitMap and on-disk Global_BitMap
Cause: The temporary Global_BitMap that was populated by traversing all valid file system data did not match the on-disk copy of the Global_BitMap.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07447: invalid snap_map_tuple for disk offset: string found: ( 0, 0 ), but expected non-zero values for file: string
Cause: File system checking has identified the metadata inconsistency reported in the message.
Action: is needed. The ACFS Fixer will resolve the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ADVM-07448: invalid snap_map_tuple for disk offset: string found: ( 0, 0 ), but expected non-zero values
Cause: File system checking has identified the metadata inconsistency reported in the message.
Action: is needed. The ACFS Fixer will resolve the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ADVM-07449: snapshot 'string' storage bitmap is incorrectly set for disk offset: string
Cause: The bitmap of the indicated snapshot claimed storage that was allocated to allocated file. Storage can only be allocated to a single file. Storage can never be allocated to multiple files.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem. The ACFS Fixer will remove this snapshot.
ADVM-07450: snapshot 'string' storage bitmap is not set for disk offset: string
Cause: The bitmap of the indicated snapshot did not claim storage that was allocated to one of its files. A snapshot's bitmap must claim all storage allocated to its files.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem. The ACFS Fixer will remove this snapshot.
ADVM-07451: snapshot 'string' storage bitmap is incorrectly set for disk offset: string with no corresponding file data
Cause: The bitmap of the indicated snapshot claimed storage but the storage was not allocated to any file.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07452: unable to locate directory for snapshot 'string' (id: number) processing will continue for other snapshots
Cause: The directory of the indicated snapshot was not found. This snapshot could not be processed.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07453: Snap_Root_Directory file identifier for snapshot 'string' was incorrect found: string, but expected to find: string for structure: string
Cause: The Snap_Root_Directory file identifier property of the indicated snapshot was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07455: unable to open file: string
Cause: An attempt to open a file failed. Refer to the accompanying message(s) for more information on the error.
Action: Correct the problem described in the accompanying messages if possible and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ADVM-07458: The request to cancel string was incomplete because volume string was not accessible. The file system cannot be mounted in this state. Rerun string once the volume is accessible to enable file system mounts.
Cause: The ACFS Checker/Fixer could not reset the volume to allow for file system mounts because the volume was not accessible. Refer to the accompanying message(s) for more information on the error.
Action: Rerun the ACFS Checker/Fixer once the volume is accessible to enable file system mounts.
ADVM-07459: Volume_Label metadata structure has invalid _VolLabelLength value found: number maximum: number for structure: string
Cause: The _VolLabelLength property of the indicated Volume_Label metadata structure exceeded the maximum value.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07460: Volume_Label metadata structure has invalid _VolIDLength value found: number maximum: number for structure: string
Cause: The _VolIDLength property of the indicated Volume_Label metadata structure exceeded the maximum value.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07461: Volume_Label metadata structure has invalid _ClusterNameLength value found: number maximum: number for structure: string
Cause: The _ClusterNameLength property of the indicated Volume_Label metadata structure exceeded the maximum value.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07462: file has incorrect or invalid _attributes values found: string valid values: string for file: string
Cause: The _attributes property of the indicated file contained invalid and/or incorrect values.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07464: file has invalid _attributes value found: string for file: string
Cause: The _attributes property of the indicated file contained invalid values. These values are not supported on Windows systems.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07465: file has _attributes set that are mutually exclusive found: string for file: string
Cause: The _attributes property of the indicated file describe more than one type of file. File types are mutually exclusive.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07466: file has no _attributes value for file: string
Cause: The _attributes property of the indicated file did not describe a file type. The _attributes property must describe a valid file type.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07467: metadata structure has a non-zero value for field: string for structure: string
Cause: The indicated ACFS metadata structure had a reserved or unused field that contained a non-zero value. The field was overwritten or was not initialized correctly.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07468: file has invalid _SynchFlags value found: string for file: string
Cause: The _SynchFlags property of the indicated file contained values that were not within the range of valid values.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07469: file cannot be modified; _SynchFlag value: found: string for file: string
Cause: The indicated file had an internal inconsistency that prevented it from being modified.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07470: file cannot be accessed; _SynchFlag value: found: string for file: string
Cause: The indicated file had an internal inconsistency that prevented it from being accessed.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07471: file incorrectly marked for deletion with _SynchFlag value: found: string for file: string
Cause: The _SynchFlag property of the indicated file incorrectly identified the file as marked for deletion while it was still part of a valid directory.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07474: invalid program name found: string, but expected to find: string or string
Cause: The ACFS Checker/Fixer or Debug utility has been renamed to a value that is not recognized.
Action: Rename the program to the corresponding value listed in the message and rerun the program.
ADVM-07481: An I/O error occurred while reading ACFS metadata, some snapshot metadata checks will not be performed.
Cause: The I/O error prevented full snapshot checking because required ACFS metadata was not available. Refer to the accompanying message(s) for more information on the error.
Action: Correct the problem described in the accompanying messages if possible and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ADVM-07482: snapshot string with _snapid value: string has invalid parent snapshot with _snapid value: string
Cause: The indicated snapshot does not have a valid parent.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07483: snapshot with _snapid value: string has invalid ancestor snapshot
Cause: The indicated snapshot has an invalid ancestor snapshot.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07484: valid ACFS volume path name required
Cause: A valid volume path name was not entered.
Action: Rerun the ACFS Checker/Fixer or Debug utility with a valid ACFS volume path name as the final argument.
ADVM-07485: unable to determine temporary directory
Cause: An attempt to determine the system's temporary directory failed. For UNIX systems this directory is either "/usr/tmp" or "/tmp". For Windows systems this directory is the system's temporary folder. Refer to the accompanying message(s) for more information on the error.
Action: Correct the problem described in the accompanying messages if possible and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ADVM-07486: unable to determine current directory
Cause: An attempt to determine the current directory failed. Refer to the accompanying message(s) for more information on the error.
Action: Correct the problem described in the accompanying messages if possible and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ADVM-07487: unable to open volume: string
Cause: An attempt to open a volume failed. Refer to the accompanying message(s) for more information on the error.
Action: Correct the problem described in the accompanying messages if possible and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ADVM-07488: This volume is now in a mountable state. The file system was not checked before changing the volume's state. Use of this file system may encounter serious errors since it has not been checked.
Cause: The volume was forced into a mountable state without checking the integrity of the file system. The file system may contain incorrect or invalid data.
Action: Run the ACFS Checker/Fixer before attempting to mount the file system.
ADVM-07489: maximum number of passes: number exceeded, program terminating
Cause: There are two possible causes:

1. There is a problem with the file system that the ACFS Fixer cannot repair.

2. The ACFS Fixer has encountered an internal problem.

Action: Contact Oracle Support Services.
ADVM-07498: extent[number] has invalid _Length value found: string, but expected to find multiple of: string for file: string
Cause: The _Length property of an extent structure of the indicated file was invalid. _Length values must be a multiple of the file system allocation unit size.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07499: extent[number] has invalid _Length value found: string, but expected to find multiple of: string for structure: string
Cause: The _Length property of an extent of the indicated extent structure was invalid. _Length values must be a multiple of the file system allocation unit size.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07500: extent[number] has invalid _FileOffset value found: string, but expected to find multiple of: string for file: string
Cause: The _FileOffset property of an extent structure of the indicated file was invalid. _FileOffset values must be a multiple of the file system allocation unit size.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07501: extent[number] has invalid _FileOffset value found: string, but expected to find multiple of: string for structure: string
Cause: The _FileOffset property of an extent of the indicated extent structure was invalid. _FileOffset values must be a multiple of the file system allocation unit size.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07502: extent[number] has invalid _PhysicalDiskOffset value found: string, but expected to find multiple of: string for file: string
Cause: The _PhysicalDiskOffset property of an extent structure of the indicated file was invalid. _PhysicalDiskOffset values must be a multiple of the file system allocation unit size.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07503: extent[number] has invalid _PhysicalDiskOffset value found: string, but expected to find multiple of: string for structure: string
Cause: The _PhysicalDiskOffset property of an extent of the indicated extent structure was invalid. _PhysicalDiskOffset values must be a multiple of the file system allocation unit size.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07504: snapshot with _snapid value: string has invalid ancestor snapshot (_cycle)
Cause: The indicated snapshot has an invalid ancestor snapshot.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07505: metadata structure read failed at disk offset: string for structure: string
Cause: An attempt to read the indicated metadata structure at the described disk offset failed. Refer to the accompanying message(s) for more information on the problem.
Action: Correct the problem described in the accompanying messages if possible and rerun the program.
ADVM-07519: Snap_Map_Header structure has invalid _SnapConvertPending value found: number, but expected to find: less than number for structure: string
Cause: The _SnapConvertPending property of the indicated Snap_Map_Header metadata structure was incorrect. The _SnapConvertPending value must be zero or less than the value indicated in the message.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07520: Snap_Map_Info structure has invalid _SnapInfoFlags value found: string for structure: string
Cause: The _SnapInfoFlags property of the indicated Snap_Map_Info metadata structure was invalid.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07521: Snap_Map_Info structure has invalid _SnapAncestorIncarn value found: string for structure: string
Cause: The _SnapAncestorIncarn property of the indicated Snap_Map_Info metadata structure was invalid.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07522: snapshot: string (identifier: number) has invalid _SnapParentId: number, parent snapshot does not exist
Cause: File system checking has identified the metadata inconsistency reported in the message.
Action: is needed. The ACFS Fixer will resolve the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ADVM-07523: snapshot: string (identifier: number) has invalid _SnapParentId value found: number, but expected to find: 0 for structure: string
Cause: File system checking has identified the metadata inconsistency reported in the message.
Action: is needed. The ACFS Fixer will resolve the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ADVM-07524: snapshot: string (identifier: number) has invalid _SnapAncestorIncarn value found: number, but expected to find: 0 for structure: string
Cause: File system checking has identified the metadata inconsistency reported in the message.
Action: is needed. The ACFS Fixer will resolve the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ADVM-07525: snapshot: string (identifier: number) has invalid _SnapAncestorIncarn value found: number, must be less than _SnapIncarnationNumber: number for structure: string
Cause: The _SnapAncestorIncarn property of the indicated Snap_Map_Info metadata structure was invalid.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07526: Volume_Disk_Header has invalid _VolStateFlag values. found: string, but expected to find: string for structure: string
Cause: The _VolStateFlag property of the indicated Volume_Disk_Header contained one or more invalid values.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07527: Volume Disk Header has invalid VolFeatureFlag values found: string string but expected to find: string string for structure: string
Cause: File system checking has identified the metadata inconsistency reported in the message.
Action: is needed. The ACFS Fixer will resolve the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ADVM-07528: found partially created snapshot: string (identifier: number)
Cause: Initialization of the indicated snapshot did not complete. There are two possible causes:

1. The volume went offline while the snapshot was being created.

2. The process creating the snapshot was unexpectedly terminated do to a shutdown of the system.

Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem. The ACFS Fixer will remove this snapshot.
ADVM-07529: found partially deleted snapshot: string (identifier: number)
Cause: A snapshot was not completely deleted. There are several possible causes:

1. The volume was unmounted before the asynchronous phase of snapshot deletion had completed.

2. The volume went offline while the snapshot was being deleted.

3. The process deleting the snapshot was unexpectedly terminated do to a shutdown of the system.

Action: None
ADVM-07530: snapshot: string (identifier: number) has invalid file identifier found: string maximum: string for structure: string
Cause: The file identifier property of the indicated snapshot was invalid. Its value exceeded the maximum value for the file system.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07531: snapshot: (identifier: number) has invalid name: 'string' for structure: string
Cause: The name of indicated snapshot contained invalid characters.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07532: snapshot: string (identifier: number) has invalid _SnapVisibility value found: number, but expected to find: number, number or number\for structure: string
Cause: The _SnapVisibility property of the indicated snapshot was invalid.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07533: duplicate _SnapIncarnationNumber: number found for the following snapshots:
Cause: The _SnapIncarnationNumber property of the indicated snapshots had the same value. _SnapIncarnationNumber values must be unique.
Action: is needed. The ACFS Fixer will resolve the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ADVM-07534: request for disk offset: string exceeds the size for this file system: string
Cause: A request was made for a disk offset that exceeded the size of the file system.
Action: Reenter the command with a disk offset that is within the limits of the file system.
ADVM-07536: snapshot: string (identifier: number) has invalid parent snapshot identifier: number, maximum: number structure: string
Cause: The indicated snapshot does not have a valid parent.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07537: snapshot: string (identifier: number) has invalid ancestor snapshot: string (identifier: number)
Cause: The indicated snapshot has an invalid ancestor snapshot.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07538: snapshot: string (identifier: number) has invalid ancestor snapshot (_cycle)
Cause: The indicated snapshot has an invalid ancestor snapshot.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07539: Snap_Map_Info structure has invalid _SnapAncestorIncarn value found: number for structure: string
Cause: The _SnapAncestorIncarn property of the indicated Snap_Map_Info metadata structure was invalid.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07540: deleting snapshot: string (identifier: number) to maintain file system integrity
Cause: The ACFS Fixer had to delete a snapshot to maintain the integrity of the file system. Refer to the corresponding message(s) for more information on the problem(s) associated with the snapshot.
Action: No further action is needed.
ADVM-07541: Snap_Map_header has invalid value for SnapMapFlags found: string string but expected to find: string string for structure: string
Cause: File system checking has identified the metadata inconsistency reported in the message.
Action: is needed. The ACFS Fixer will resolve the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ADVM-07570: snap_map_tuple for disk offset: string conflicts with primary file system found: ( string, string ) expected: ( 0, 0 )
Cause: File system checking has identified the metadata inconsistency reported in the message.
Action: is needed. The ACFS Fixer will resolve the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ADVM-07571: snap_map_tuple for disk offset: string not set in Global BitMap snap_map_tuple: ( string, string )
Cause: File system checking has identified the metadata inconsistency reported in the message.
Action: is needed. The ACFS Fixer will resolve the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ADVM-07572: invalid snap_map_tuple found for for disk offset string, first value must be less than or equal to second value snap_map_tuple: ( string, string )
Cause: File system checking has identified the metadata inconsistency reported in the message.
Action: is needed. The ACFS Fixer will resolve the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ADVM-07573: orphan snap_map_tuple found for for disk offset string snap_map_tuple: ( string, string )
Cause: File system checking has identified the metadata inconsistency reported in the message.
Action: is needed. The ACFS Fixer will resolve the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ADVM-07575: command takes no arguments
Cause: The command entered does not take any arguments.
Action: Reenter the command with no arguments.
ADVM-07585: unable to set File_Entry_Table context
Cause: The ACFS Debug utility was not able to set the File_Entry_Table context. Lookups by file identifier were disabled. Refer to the accompanying message(s) for more information on the problem.
Action: Correct the problem described in the accompanying messages if possible by rerunning the ACFS Fixer.
ADVM-07586: Do you want to continue [y|n] ?
Cause: The ACFS Checker/Fixer or Debug utility detected a situation that could leave the file system in an inconsistent or unusable state. Refer to the corresponding error message for more information.
Action: Respond Y(yes) to proceed or N(no) to cancel.
ADVM-07588: metadata read failed at disk offset: string size: string bytes - cannot read beyond file system size: string
Cause: An attempt to read metadata failed because the data requested was beyond the size of the file system.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07590: metadata write failed at disk offset: string size: string bytes - cannot write beyond file system size: string
Cause: An attempt to write metadata failed because the write location was beyond the size of the file system.
Action: The ACFS Fixer will resolve the problem. No further action is needed.
ADVM-07592: metadata structure has incorrect header for: string
Cause: One or more properties of the header of the indicated metadata structure contained invalid or incorrect values. Refer to accompanying messages for more information on the error.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07601: unable to determine size of file: string
Cause: An attempt to determine the size of the indicated file failed. Refer to the accompanying message(s) for more information on the problem.
Action: Correct the problem described in the accompanying messages if possible and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ADVM-07602: failed to create temporary paging file 'string'
Cause: An attempt to create the indicated temporary paging file failed. Refer to the accompanying message(s) for more information on the problem.
Action: Correct the problem described in the accompanying messages if possible and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ADVM-07603: write failed at position: string for temporary paging file 'string'
Cause: An attempt to write to the indicated temporary paging file failed. Refer to the accompanying message(s) for more information on the problem.
Action: Correct the problem described in the accompanying messages if possible and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ADVM-07604: seek failed at position: string for temporary paging file 'string'
Cause: An attempt to seek within the indicated temporary paging file failed. Refer to the accompanying message(s) for more information on the problem.
Action: Correct the problem described in the accompanying messages if possible and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ADVM-07606: read failed at position: string for temporary paging file 'string'
Cause: An attempt to read the indicated temporary paging file failed. Refer to the accompanying message(s) for more information on the problem.
Action: Correct the problem described in the accompanying messages if possible and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ADVM-07607: metadata read failed at disk offset: string bytes requested: number bytes returned: number
Cause: An attempt to read metadata at the indicated offset was incomplete. The amount of data read did not match the amount requested. Refer to the accompanying message(s) for more information on the problem.
Action: Correct the problem described in the accompanying messages if possible and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ADVM-07610: Volume_Disk_Header has incorrect _VolVolumeSize value found: string, but expected to find: string for structure: string
Cause: The _VolVolumeSize property of the indicated Volume_Disk_Header metadata structure was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07611: Global_BitMap has bits incorrectly set for storage beyond the file system size for file: string
Cause: The Global_BitMap had bits set in an area reserved for future expansion. All of these storage bits must be zero. There is no valid storage associated with these bits.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07612: file has invalid _NextFreeExtent value: found: number minimum: number for file: string
Cause: The _NextFreeExtent property of the indicated file was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07613: file has invalid _NextFreeExtent value: found: number maximum: number for file: string
Cause: The _NextFreeExtent property of the indicated file was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07614: Global_BitMap's first extent is not located at the expected disk offset found: string, but expected to find: string for file: string
Cause: The first extent of the indicated Global_BitMap was not located at the correct disk offset. The Global_BitMap's first extent must be located at the disk offset described in the message.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07615: Global_BitMap file has extents that overlap Extent[number] _Length: string _PhysicalDiskOffset: string Extent[number] _Length: string _PhysicalDiskOffset: string for file: string
Cause: The extents of the indicated Global_BitMap mapped some or all of the same storage. All extents within a file must map storage that is mutually exclusive.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07616: string has encountered an internal error: could not post error to ACFS Fixer
Cause: The ACFS Checker/Fixer or ACFS Debug utility has encountered an unexpected, internal error. Refer to the accompanying message(s) for more information on the problem.
Action: Contact Oracle Support Services.
ADVM-07619: truncating file from number bytes to number bytes to ensure metadata consistency; file content following file offset: number has been lost for file: string
Cause: The ACFS Fixer was not able to fully repair the indicated file due to an inconsistency within its metadata. The file had to be truncated to maintain the integrity of the file system.
Action: Restore the file from a backup copy.
ADVM-07622: resetting _security_descriptor to administrator default value for: for file: string
Cause: The _security_descriptor the indicated file was invalid or incorrect. It was reset to the default administrator value.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will reset the _security_descriptor to the administrator default value for the file.
ADVM-07623: unable to repair problem with file _attributes; deleting file to maintain file system integrity for file: string
Cause: The ACFS Fixer was not able to resolve a problem with the _attributes property of the indicated file. The file had to be deleted to maintain the integrity of the file system.
Action: Restore the file from a backup copy.
ADVM-07624: file cannot be repaired; deleting file to maintain file system integrity for file: string
Cause: The ACFS Fixer was not able to repair a problem with the indicated file. The file had to be deleted to maintain file system integrity.
Action: Restore the file from a backup copy.
ADVM-07625: failed to create system directory for file: string
Cause: The ACFS Fixer was not able to create a directory for the indicated internal system file. Refer to the accompanying message(s) for more information on the problem.
Action: Correct the problem described in the accompanying messages if possible and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ADVM-07628: invalid snapshot name 'string' entered
Cause: The snapshot entered did not exist.
Action: Enter the name of a valid snapshot to continue.
ADVM-07629: numeric argument too large: number
Cause: The numeric value entered as an argument exceeded the largest possible value for this type of argument.
Action: Enter a value that is within the valid range of values for the type of argument.
ADVM-07647: local extent limit reached for extending files; indirect extents not supported for extending files for file: string
Cause: The ACFS Fixer was not able to create an indirect extent to extend the indicated file.
Action: Restore the file from a backup copy.
ADVM-07648: cannot set Global_BitMap bits for offset: string for number bytes for file: string
Cause: The ACFS Fixer was unable to set the range of bits described in the message. Refer to the accompanying message(s) for more information on the problem.
Action: Correct the problem described in the accompanying messages if possible and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ADVM-07649: deleting snapshot to maintain file system integrity
Cause: The ACFS Fixer had to delete a snapshot to maintain the integrity of the file system. Refer to the corresponding message(s) for more information on the problem(s) associated with the snapshot.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07650: unable to repair _VolStateFlag value in Volume_Disk_Header
Cause: The ACFS Fixer was unable to update the _VolStateFlag in the Volume_Disk_Header. Refer to the accompanying message(s) for more information on the problem.
Action: Correct the problem described in the accompanying messages if possible and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ADVM-07652: Volume_Disk_Header has invalid _VolOSCreatedOn value found: number, but expected to find: 1 (Windows_XP), 2 (Linux), 3 (Solaris), or 4 (AIX) for structure: string
Cause: The _VolOSCreatedOn property of the indicated Volume_Disk_Header was incorrect. Its value must be one of the values listed in the message.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07653: Security_Metadata file _Private structure has invalid _freeDataListTail value found: 0, but expected to find: > 0 for structure: string
Cause: The _freeDataListTail property of the indicated Security_Metadata _Private metadata structure was invalid. The value must be greater than zero.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07655: This file system had been removed. It has now been restored.
Cause: This file system was removed via the acfsutil rmfs utility. It has now been restored by the ACFS Fixer.
Action: The ACFS Fixer has restored the file system. No further action is required.
ADVM-07656: unable to continue
Cause: The ACFS Checker/Fixer or Debug utility has encountered a fatal error and cannot continue. Refer to the accompanying message(s) for more information on the error.
Action: Correct the problem described in the accompanying messages if possible and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ADVM-07658: Ensure that volume string is not mounted on this node. Note that data displayed may not be current if volume string is mounted on any other node due to file system caching
Cause: The volume cannot be mounted on this node while running the acfsdbg utility in read-only mode. This restriction is limited to Windows systems. The acfsdbg utility reads metadata directly from disk and data may not be current if the file system is mount on any other nodes due file system caching.
Action: Check to determine if the volume is mounted on any node. The volume must be unmounted on this node before continuing. The volume should also be unmounted on all others node if possible. If the volume cannot be unmounted on other nodes, then reenter any request if the metadata values displayed appear to be stale. Note: You may have to reenter the request several times to retrieve the latest metadata.
ADVM-07659: command is disabled in read-only mode
Cause: The command entered attempted to modify file system metadata while running in read-only mode. Modifications to file system metadata are not allowed when running the ACFS Debug utility in read-only mode.
Action: Rerun the acfsdbg utility in write mode to modify metadata.
ADVM-07660: unable to modify metadata for volume string; volume is not open
Cause: An attempt to modify metadata failed because the volume was not open. Refer to the accompanying message(s) for more information on the problem.
Action: Correct the problem described in the accompanying messages if possible and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ADVM-07661: metadata lookup by file identifier is disabled due to lack of File_Entry_Table context; enter 'primary' or 'snap <snapshot name>' to set the context
Cause: The acfsdbg utility could not process the request because there was no File_Entry_Table context. The acfsdbg utility requires a valid File_Entry_Table context for lookups by file identifier since the same file identifier may appear in multiple snapshots.
Action: Enter the 'primary' or 'snap <snapshot name>' command to set context.
ADVM-07662: unable to set snapshot context due to Snap_Map file metadata inconsistency
Cause: An attempt to set the metadata lookup context to a snapshot failed because there was a problem accessing the SnapMap metadata. Refer to the accompanying message(s) for more information on the problem.
Action: Correct the problem described in the accompanying messages if possible and rerun the ACFS debug utility.
ADVM-07663: disk offset request: string is not aligned on a sector: number bytes; results may be inconsistent
Cause: The disk offset entered was not sector aligned. All ACFS metadata structures are sector aligned.
Action: Reenter the offset so that is properly aligned as described in the corresponding message.
ADVM-07664: read failed for metadata structure at disk offset: string for number bytes
Cause: An attempt to read a metadata structure at the indicted disk offset failed. Refer to accompanying message(s) for more information on the problem.
Action: Correct the problem described in the accompanying messages if possible and rerun the ACFS debug utility.
ADVM-07666: unrecognized metadata found at disk offset: string
Cause: The data found at the indicated disk offset did not contain a valid ACFS metadata structure type. There are two possible causes:

1. The data at the disk offset was not an ACFS metadata structure.

2. The metadata structure at the disk offset was in an inconsistent state.

Action: If the data at the disk offset should be an ACFS metadata structure, then run the ACFS Fixer to resolve the problem.
ADVM-07667: request for file identifier: string exceeds the maximum value for this file system: string
Cause: A request was made for a file identifier that exceeded the maximum for the file system.
Action: Reenter the command with a file identifier that is within the limits of the file system.
ADVM-07669: metadata lookup by file identifier is disabled due to File_Entry_Table metadata inconsistency
Cause: The acfsdbg utility has identified the metadata inconsistency reported in the accompanying message.
Action: Run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ADVM-07685: string is unable to detect the ACFS driver on this system. Proceeding could leave the file system in an inconsistent and possibly unusable state if the file system is mounted or being fixed on another system.
Cause: The ACFS Checker/Fixer or Debug utility issued a system call to the ACFS driver that failed. It appeared that the ACFS driver was not loaded on this system.
Action: The ACFS driver should be loaded on all nodes if possible. Verify that the file system is not mounted or being fixed on any node. Rerun the ACFS Checker/Fixer or Debug utility once these steps are complete.
ADVM-07690: data displayed may not be current if volume string is mounted on any node due to file system caching
Cause: The acfsdbg utility reads metadata directly from disk. Metadata updates to disk may be delayed due standard file system caching.
Action: Check to determine if the volume is mounted on any node. Unmount the volume on all nodes if possible. If the volume cannot be unmounted from all nodes, then reenter any request if the metadata values displayed appear to be stale. Note: You may have to reenter a request several times to retrieve the latest metadata.
ADVM-07691: command entered: 'string' is invalid or not unique
Cause: There are two possible causes:

1. The command entered was not recognized by the acfsdbg utility.

2. A partial command name was entered and there was more than one command that matched the characters entered.

Action: Use the acfsdbg utility help (-h) option for a list of valid commands. Renter the command, ensuring that enough of the command name is entered to make it unique.
ADVM-07692: cannot convert disk offset as specified: string
Cause: The format entered for the disk offset was invalid.
Action: Use the acfsdbg utility help (-h) option for a list of commands and format options for entering data.
ADVM-07693: Volume_Disk_Header has invalid _VolVolumeSize value found: string must be aligned on a number byte boundary for structure: string
Cause: The _VolVolumeSize property of the Volume_Disk_Header was invalid. Its value must be aligned on the byte boundary described in the message.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07694: too many arguments for string
Cause: Too many arguments were supplied for the string option. The string option takes one argument.
Action: Reenter the command with only one argument for the string option.
ADVM-07695: The ACFS driver should be loaded on all nodes for a safe check of this file system.
Cause: The ACFS Checker/Fixer or Debug utility issued a system call to the ACFS driver that failed. It appeared that the ACFS driver was not loaded on this system.
Action: The ACFS driver should be loaded on all nodes if possible. Verify that the file system is not mounted or being checked on any node. Rerun the ACFS Checker/Fixer or Debug utility once these steps are complete.
ADVM-07696: The file system on volume string is currently in the string state. This state indicates that a file system check is currently in progress.
Cause: There are two possible causes:

1. The file system on this volume was being checked on this system or another system in the cluster.

2. The ACFS Checker/Fixer was unexpectedly terminated leaving the file system state incorrectly set.

Action: Verify that the file system is not being checked on any node. There are a two possible options if the file system is not being checked on any node:

1. Respond Y(yes) when prompted to run the ACFS Checker/Fixer.

2. Run the ACFS Fixer with the [f] option to reset the file system state to allow the file system to be mounted. NOTE: Use caution with this option as file system repairs from a previous run of the ACFS Checker/Fixer may be incomplete.

ADVM-07697: unable to determine program name
Cause: The ACFS Checker/Fixer or Debug utility was invoked in a non-standard way such that the program name could not be determined.
Action: Run the ACFS Checker/Fixer or Debug utility using a standard method.
ADVM-07698: orphan directory found for file identifier: string at disk offset: string
Cause: No parent directory entry was found for the indicated directory file.

1. The directory file had no corresponding parent directory entry.

2. The directory file had a parent directory entry, but there was a problem with corresponding parent directory file.

Action: If the ACFS Fixer is currently running, then no further action is needed. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem. The ACFS Fixer will attempt to repair any directories that are in an inconsistent state first. Any directory file that does not have a valid parent directory entry following directory repairs will be moved to the 'lost+found' directory with all of its files.
ADVM-07701: There are metadata transaction log file(s) that have not been processed. Failure to process these transaction logs may result in metadata inconsistencies. Do you want to process the transaction log(s)? [y|n]
Cause: Transaction Log files contain updates to the file system's metadata. The ACFS Checker found at least one transaction log that was not completely processed. This indicates that metadata updates were not completed which could leave the file system in an inconsistent state.
Action: Respond yes to process metadata transaction log(s).
ADVM-07705: There are files marked for deletion that have not been removed from the file system. Failure to remove these files could result in false errors being reported. Do you want to remove files that are marked for deletion? [y|n]
Cause: The ACFS Checker found files that were marked for deletion but had not been removed from the file system. False errors may be reported due to the presence of there files.
Action: Respond yes to remove these files.
ADVM-07708: unable to read File_Entry_Table entry: string at disk offset: string
Cause: An attempt to read the File_Entry_Table for the indicated entry failed. Refer to the accompanying message(s) for more information on the problem.
Action: Correct the problem described in the accompanying messages if possible and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ADVM-07709: orphan file (file identifier: string, disk offset: string) marked for deletion not on delete list
Cause: The indicated file was marked for deletion but it was not found on any of the delete file lists.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07710: orphan file found for file identifier: string at disk offset: string
Cause: No directory entry was found for the indicated file. There are two possible causes:

1. The file had no corresponding directory entry.

2. The file had a directory entry, but there was a problem with corresponding directory file.

Action: If the ACFS Fixer is currently running, then no further action is needed. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem. The ACFS Fixer will attempt to repair any directories that are in an inconsistent state first. Any file that does not have a valid directory entry following directory repairs will be moved to the 'lost+found' directory.
ADVM-07711: orphan metadata structure (type: string) found for file identifier: string at disk offset: string
Cause: The indicated metadata structure was found but had no corresponding parent metadata structure.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will move the structure to the free list. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07720: new allocation size is invalid found: number, but expected to find multiple of: number for file: string
Cause: The new allocation size property of the indicated file was incorrect. Its value must be a multiple of the file system allocation unit size.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07721: file has invalid _NextFreeExtent value found: number maximum: number for file: string
Cause: The _NextFreeExtent property of the indicated file was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07722: file has invalid _NextFreeExtent value: found: number minimum: 1 for file: 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-07723: could not clear temporary Global_BitMap bits at offset: string for number bits
Cause: The ACFS Fixer was unable to free the indicated storage on the temporary Global_BitMap.
Action: See the preceding error message, and take corrective action.
ADVM-07724: unable to set temporary Global_BitMap bits at offset: string for number bits
Cause: The ACFS Fixer was unable to reserve the indicated storage on the temporary Global_BitMap.
Action: See the preceding error message, and take corrective action.
ADVM-07725: unable to allocate storage; file system has no free space
Cause: The ACFS Fixer was unable to allocate storage because there was no free storage available.
Action: There are two options:

1. Free up some storage by deleting some files.

2. Add available storage by increasing the size of the file system via the 'acfsutil size' command.

ADVM-07726: could not find sufficient free storage to rebuild Global_BitMap extent found: string requested: string for file: string
Cause: The ACFS Fixer could not find enough contiguous storage to rebuild the Global_BitMap file's extent map.
Action: There are two options:

1. Free up some storage by deleting some files.

2. Add available storage by increasing the size of the file system via the 'acfsutil size' command.

ADVM-07727: could not rewrite Global_Bitmap data for file: string
Cause: The ACFS Fixer could not update the file system's storage bitmap. Refer to the accompanying message(s) for more information on the problem.
Action: Correct the problem described in the accompanying messages if possible and rerun the ACFS Fixer.
ADVM-07728: The Global_BitMap file has reached the maximum number of extents (number). The file system can no longer be expanded. Running string in fixer mode will attempt to consolidate the storage bitmap into fewer extents which would allow for file system expansion via the 'acfsutil size' command.
Cause: The ACFS Checker found the file system's storage bitmap was using its maximum number of extents.
Action: Running the ACFS Checker/Fixer in Fixer mode will attempt to consolidate the file system's storage bitmap into two extents allowing future file system expansion using 'acfsutil size', assuming additional storage is available.
ADVM-07729: The Global_Bitmap file has been consolidated into number extents. This may allow for file system expansion via the 'acfsutil size' command.
Cause: The Global_Bitmap file was using the maximum number of extents supported. The ACFS Fixer has consolidated the Global_Bitmap file into fewer extents thus allowing future file system growth using the 'acfsutil size' command if unused storage is available.
Action: No Action Needed.
ADVM-07733: directory _Private structure has invalid _first_dirnode value found: number maximum: number for structure: string
Cause: The _first_dirnode property of the indicated _Private directory structure was invalid. Its value exceeded the maximum value for the directory.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07734: directory _Private structure has invalid _last_dirnode value found: number maximum: number for structure: string
Cause: The _last_dirnode property of the indicated _Private directory structure was invalid. Its value exceeded the maximum value for the directory.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07735: directory _Private structure has invalid _hash_blk_free_list value found: number maximum: number for structure: string
Cause: The _hash_blk_free_list property of the indicated _Private directory structure was invalid. Its value exceeded the maximum value for the directory.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07736: directory _Private structure has invalid _dir_entry_free_list_head value found: number maximum: number for structure: string
Cause: The _dir_entry_free_list_head property of the indicated _Private directory structure was invalid. Its value exceeded the maximum value for the directory.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07737: directory _Private structure has invalid _dir_entry_free_list_tail value found: number maximum: number for structure: string
Cause: The _dir_entry_free_list_tail property of the indicated _Private directory structure was invalid. Its value exceeded the maximum value for the directory.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07740: Could not consolidate the file system's temporary storage bitmap to less than number extents. Need at least number bytes free contiguous storage.
Cause: The file system's internal storage bitmap could not be consolidated to less than five extents because there was insufficient free contiguous storage.
Action: Deleting some files larger than the amount of contiguous storage needed may free up sufficient contiguous storage so consolidation of the file system's internal storage bitmap may occur. The 'acfsutil info file filename' command may be used to examine a candidate file's contiguous extents.
ADVM-07741: could not rebuild file system storage bitmap free contiguous bytes found: number contiguous bytes requested: number for file: string
Cause: The ACFS Fixer could not find enough contiguous free storage to rebuild the file system's storage bitmap.
Action: Deleting some files larger than the amount of contiguous storage needed may free up sufficient contiguous storage so consolidation of the file system's internal storage bitmap may occur. The 'acfsutil info file filename' command may be used to examine a candidate file's contiguous extents.
ADVM-07742: _ustEAContainerEntry property has an invalid value found: number for structure: string
Cause: The _ustEAContainerEntry property of the indicated _ustEAContainer structure was not within the range of valid offset values.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem. The ACFS Fixer reconstructs the structure to retain as much valid information as possible and may eliminate inaccessible information.
ADVM-07743: _ustEAEntryHdrFlags property has an invalid value found: string for _ustEAContainerEntry at offset: string for structure: string
Cause: The _ustEAEntryHdrFlags property of the indicated _ustEAContainer structure contained one or more invalid values.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07744: _ustEAEntryHdrNextFreeOffset property has an invalid value found: number, but expected to find: number for _ustEAContainerEntry at offset: number for structure: string
Cause: The _ustEAEntryHdrNextFreeOffset property of the indicated _ustEAContainer structure was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07745: _ustEAEntryHdrNameLen property has an invalid value found: number, but expected to find no greater than: number for _ustEAContainerEntry at offset: string for structure: string
Cause: The _ustEAEntryHdrNameLen property of the indicated _ustEAEntryHdr property at the _ustEAContainerEntry offset for the indicated _ustEAContainer structure was invalid. Its value exceeded the maximum length for an extended attribute name or ACFS tag name.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem. The ACFS Fixer reconstructs the structure to retain as much valid information as possible and may eliminate inaccessible or invalid information.
ADVM-07746: ACFS tag name contains invalid syntax found: string for _ustEAContainerEntry at offset: string for structure: string
Cause: The _ustEAEntryName property of the indicated _ustEAContainerEntry property in the _ustEAContainer structure contained invalid syntax for an ACFS tag name.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem. The ACFS Fixer reconstructs the structure to retain as much valid information as possible and may eliminate inaccessible or invalid information.
ADVM-07747: _ustEAEntryValueLen property has an invalid value found: number, but expected to find: number for _ustEAEntry offset: string for structure: string
Cause: The _ustEAEntryValueLen property of the indicated _ustEAEntry property in the _ustEAEntryContainer structure contained an invalid value length.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem. The ACFS Fixer reconstructs the structure to retain as much valid information as possible and may eliminate inaccessible or invalid information.
ADVM-07748: _ustEAEntryValue property has an invalid value found: string, but expected to find: string for _ustEAEntry offset: string for structure: string
Cause: The _ustEAEntryValue property of the indicated _ustEAEntry property in the _ustEAEntryContainer structure contained an invalid value string for an ACFS tag name.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07749: _ustEAContainerHdrNextContainer property has an invalid value found: string for structure: string
Cause: The _ustEAContainerHdrNextContainer property of the indicated _ustEAContainer structure contained an invalid offset value.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem. The ACFS Fixer reconstructs the structure to retain as much valid information as possible and may eliminate inaccessible or invalid information.
ADVM-07750: _ustEAContainerHdrNumEAEntries property has an invalid value found: number, but expected to find: number for structure: string
Cause: The _ustEAContainerHdrNumEAEntries property of the indicated _ustEAContainer structure contained an incorrect count of valid entries.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07751: Inconsistent amount of available space found: number, but expected to find: number for structure: string
Cause: The _ustEAContainer structure had an incorrect amount of free space.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem. The ACFS Fixer reconstructs the structure to retain as much valid information as possible and may eliminate inaccessible or invalid information.
ADVM-07752: _LocalTags property has invalid characters for _FileEntry: string
Cause: The _LocalTags property of the indicted _FileEntry structure contained invalid characters for ACFS tag names.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem. The ACFS Fixer reconstructs the structure to retain as much valid information as possible and may eliminate inaccessible or invalid information.
ADVM-07753: _ustEAEntry property offset: number is marked free but is missing from the free list for structure: string
Cause: The _ustEAContainer structure had an incorrect amount of free space.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem. The ACFS Fixer reconstructs the structure to retain as much valid information as possible and may eliminate inaccessible or invalid information.
ADVM-07754: _ustEAContainer property has inconsistent total free and assigned _ustEAContainerEntry property space found: number, but expected to find: number for structure: string
Cause: The _ustEAContainer structure contained free and active _ustEAContainerEntry property entries that indicate its total space exceeded the size of a _ustEAContainer structure.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem. The ACFS Fixer reconstructs the structure to retain as much valid information as possible and may eliminate inaccessible or invalid information.
ADVM-07755: _ustEAContainerHdrNextFreeOffset property has an invalid value found: number, but expected to find less than: number for structure: string
Cause: The ustEAContainerHdrNextFreeOffset property of the indicated _ustEAContainer structure was not within the range of valid offset values.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem. The ACFS Fixer reconstructs the structure to retain as much valid information as possible and may eliminate inaccessible information.
ADVM-07756: _ustEAEntryHeader.ustEAEntryHdrNextFreeEAOffset property has an invalid value found: number, but expected to find less than: number for _ustEAContainerEntry at offset: number for structure: string
Cause: The _ustEAEntryHeader.ustEAEntryHdrNextFreeEAOffset property of the indicated _ustEAContainerEntry property for the _ustEAContainer structure was not within the range of valid offset values.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem. The ACFS Fixer reconstructs the structure to retain as much valid information as possible and may eliminate inaccessible information.
ADVM-07757: file extended attribute container structure exceeds file system size: string _Length: string for structure: string
Cause: The extended attribute container structure of the indicated file referenced meta data beyond the size of the file system. There are two possible causes:

1. The extended attribute container structure disk offset was incorrect.

2. The file system size value was incorrect.

Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07758: _ustEAEntryHdrNameLen property has an invalid value found: number, but expected non-zero value for _ustEAContainerEntry at offset: string for structure: string
Cause: The _ustEAEntryHdrNameLen property of the indicated _ustEAEntryHdr property at the _ustEAContainerEntry offset for the indicated _ustEAContainer structure was invalid. Its value was zero but must be non-zero for an extended attribute name entry.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem. The ACFS Fixer reconstructs the structure to retain as much valid information as possible and may eliminate inaccessible or invalid information.
ADVM-07759: _ustEAEntryValueLen property has an invalid value found: number, but expected to find less than: number for _ustEAEntry offset: string for structure: string
Cause: The _ustEAEntryValueLen property of the indicated _ustEAEntry property in the _ustEAEntryContainer structure contained an invalid value length that was larger than expected for this structure.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem. The ACFS Fixer reconstructs the structure to retain as much valid information as possible and may eliminate inaccessible or invalid information.
ADVM-07760: _ustEAContainerHdrNextFreeOffset property has an invalid value found: number, but expected to find: number for structure: string
Cause: The _ustEAContainerHdrNextFreeOffset property of the indicated _ustEAContainer structure was not within the range of valid offset values.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem. The ACFS Fixer reconstructs the structure to retain as much valid information as possible and may eliminate inaccessible information.
ADVM-07761: directory _Private structure has invalid _dir_bitmap_start value found: number maximum: number for structure: string
Cause: The _dir_bitmap_start property of the indicated _Private directory structure was invalid. Its value exceeded the maximum value for the directory.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07762: Directory contains invalid bitmap block number at disk offset: string for file: string
Cause: A bitmap block of the indicated directory file was found in the wrong location. Directory bitmap blocks must be located contiguously after the first bitmap block.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07763: Directory bitmap is not contiguous from block number to block number at disk offset: string for file: string
Cause: A discontinuity was seen in the directory bitmap. Directory bitmap blocks must be located contiguously after the first bitmap block.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07764: Directory bitmap has incorrect last block found: number expected: number for file: string
Cause: The directory bitmap does not end where expected.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07765: Version 11.2.0.3 or earlier directory contains bitmap block number at disk offset: string for file: string
Cause: The directory _Private structure indicates that the directory does not have a bitmap, yet a bitmap block was found in the directory.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07766: Directory bitmap does not match state of block number bitmap: string block: string for file: string
Cause: The directory bitmap indicates an incorrect state for the directory block.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07767: Directory bitmap contains non-zero value for bit number mapping beyond end of directory: string
Cause: The directory bitmap contains a non-zero bit in the range mapping blocks beyond the end of the directory.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07768: Directory _Private structure has invalid _dir_bitmap_size value found: string minimum: string for structure: string
Cause: The _dir_bitmap_size property of the indicated _Private directory structure was invalid. Its value did not meet the minimum value for the directory.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07769: Number of bitmap blocks found does not match value of _dir_bitmap_size in directory _Private structure found: number expected: number for structure: string
Cause: The number of bitmap blocks in the directory does not match the number of blocks that were expected.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07770: System directory _Private structure has invalid on-disk version found: string expected: string for structure: string
Cause: The on-disk version of the indicated _Private directory structure was invalid.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07771: directory _Private structure has invalid directory bitmap end value found: number maximum: number for structure: string
Cause: The calculated end of the directory bitmap of the indicated _Private directory structure was invalid. Its value exceeded the maximum value for the directory.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07864: A request to cancel string was made while the file system was being repaired. This could leave the file system in an inconsistent state. It is strongly recommended that string be rerun to complete file system repairs.
Cause: The ACFS fixer was cancelled before all file system repairs were completed.
Action: Rerun the ACFS fixer to complete file system repairs.
ADVM-07900: Security_Metadata file _Private structure has invalid _freeDataList value found: number maximum: number for structure: string
Cause: The _freeDataList property of the _Private structure of the indicated Security_Metadata file was incorrect. The _freeDataList value exceeded the maximum value for this Security_Metadata file.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07901: Hash_Bucket metadata structure has incorrect _controlling_bkt value found: string maximum: string for structure: string
Cause: The _controlling_bkt property of the indicated Hash_Bucket structure was incorrect. Its value exceeded the maximum value for the hash table.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07902: Hash_File_Master_Block metadata structure has incorrect value for entry number in _hash_bucket_group array found: number minimum: number for structure: string
Cause: The entry in _hash_bucket_group array of the indicated Hash_File_Master_Block structure was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07903: Hash_Bucket metadata structure has invalid data; expected all zeros for structure: 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-07907: directory file has no storage allocated to it for file: 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-07908: Root_Directory cannot be repaired file: string
Cause: The ACFS Checker/Fixer found an inconsistency with the Root_Directory metadata.
Action: The Root_Directory is a critical system file that is necessary for a functioning file system. Restore the file system from a backup copy.
ADVM-07909: System metadata was truncated, possibly resulting in the deletion of files.
Cause: The ACFS Checker/Fixer found an inconsistency within the file system.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07924: Snap_Map_header has invalid value for RW snap storage not in map found: string, but expected to find: string for file: string
Cause: The Snap_Map_header property that indicates the amount of RW snap storage not recorded in the Snap_Map file is incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07925: Snap_Map_header has invalid value for snap storage in map found: string, but expected to find: string for file: string
Cause: The Snap_Map_header property that indicates the amount of snap storage recorded in the Snap_Map file is incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07926: Snap_Map_header has invalid value for snap map flags found: string for file: string
Cause: The Snap_Map_header flags field is invalid.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07928: Plug-in configuration file has invalid _FileSize value found: string, but expected to find: string for file: string
Cause: The _FileSize property of the indicated plug-in configuration file was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-07929: The string command is unable to open the storage accelerator volume string that is associated with this file system.
Cause: fsck (Unix or Linux) or acfschkdsk.exe (Windows) could not open the specified storage accelerator volume. This could be because the ASM disk group containing the storage accelerator volume is not mounted.
Action: Verify that the ASM disk group containing the storage accelerator volume is mounted. Then rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ADVM-07930: Continuing will result in the storage accelerator volume being removed from the file system, which could leave the file system in an inconsistent and possibly unusable state if critical system metadata is stored on the storage accelerator volume.
Cause: fsck (Unix or Linux) or acfschkdsk.exe (Windows) could not open the specified storage accelerator volume. This could be because the ASM disk group containing the storage accelerator volume is not mounted.
Action: If the accelerator volume has no known problems, verify that the ASM disk group containing the storage accelerator volume is mounted. Then rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows). Or, if the accelerator volume is known to have problems such as disk corruption and you wish to have fsck (Unix of Linux) or acfschkdsk.exe (Windows) disassociate the accelerator volume from the file system, allow it to continue.
ADVM-07932: Volume string does not contain a valid ACFS storage accelerator.
Cause: File system checking has identified the metadata inconsistency reported in the message.
Action: is needed. The ACFS Fixer will resolve the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ADVM-07933: Accelerator volume string is associated with a different file system.
Cause: File system checking has identified the metadata inconsistency reported in the message.
Action: is needed. The ACFS Fixer will resolve the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ADVM-07934: The file identifier for the accelerator volume storage bitmap is invalid. found: string maximum: string
Cause: File system checking has identified the metadata inconsistency reported in the message.
Action: is needed. The ACFS Fixer will resolve the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ADVM-07935: The _FileEntry metadata structure for the accelerator volume storage bitmap is invalid.
Cause: File system checking has identified the metadata inconsistency reported in the message.
Action: is needed. The ACFS Fixer will resolve the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ADVM-07936: Extent structure has incorrect _VolId value. found: string for structure: string
Cause: File system checking has identified the metadata inconsistency reported in the message.
Action: is needed. The ACFS Fixer will resolve the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ADVM-07937: File extent exceeds accelerator volume size. string extent: _FileOffset: string _Length: string _PhysicalDiskOffset: string for file: string
Cause: File system checking has identified the metadata inconsistency reported in the message.
Action: is needed. The ACFS Fixer will resolve the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ADVM-07938: Accelerator Global_BitMap has invalid value for number of bits set. found: string maximum: string for file: string
Cause: File system checking has identified the metadata inconsistency reported in the message.
Action: is needed. The ACFS Fixer will resolve the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ADVM-07939: Accelerator Global_BitMap has invalid value for number of bits set. found: string, but expected to find: string for file: string
Cause: File system checking has identified the metadata inconsistency reported in the message.
Action: is needed. The ACFS Fixer will resolve the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ADVM-07940: Accelerator Global_BitMap has invalid value for next offset to search. found: string maximum: string for file: string
Cause: File system checking has identified the metadata inconsistency reported in the message.
Action: is needed. The ACFS Fixer will resolve the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ADVM-07941: mismatch between temporary Global_BitMap and on-disk accelerator Global_BitMap
Cause: File system checking has identified the metadata inconsistency reported in the message.
Action: is needed. The ACFS Fixer will resolve the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ADVM-07942: Accelerator Global_BitMap has bits incorrectly set for storage beyond the file system size for file: string
Cause: File system checking has identified the metadata inconsistency reported in the message.
Action: is needed. The ACFS Fixer will resolve the problem. If the message was generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent metadata inconsistencies may point to internal errors. In this case, contact Oracle Support Services.
ADVM-07943: The specified volume is an accelerator volume. Cannot proceed.
Cause: The volume specified on the command line was an accelerator volume. The command requires the primary file system volume.
Action: Rerun the command specifying the primary file system volume.
ADVM-09025: Failed to update the Windows Registry for volume string.
Cause: An attempt to store data in the Windows registry failed. 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 accompanying messages and retry the operation.
ADVM-09100: Creating volume 'string' in diskgroup 'string'.
Cause: Informational
Action: None
ADVM-09101: Failed to create volume 'string' in diskgroup 'string'.
Cause: The volume was unable to be created in the diskgroup. Possible Causes: 1) ASM is not running. 2) User is not part of the ASMADMIN group. 3) An ASM specific error occurred.
Action: 1) Verify that ASM is running ('srvctl status asm') 2) Verify that the user is part of the ASMADMIN group. 3) Check the ASM logs and output for an ASM specific error.
ADVM-09102: Unable to verify creation of ACFS Oracle database Home.
Cause: A command was given to ASM to create the specified volume and no errors were detected. However, post creation checks failed to find that the volume that was created and/or enabled.
Action: Run sqlplus (or asmcmd) to manually create the volume.
ADVM-09103: Enabling volume 'string' on diskgroup 'string'.
Cause: Informational
Action: None
ADVM-09104: Enable of volume 'string' failed.
Cause: ASM was instructed to enable the specified volume and failed.
Action: Attempt a manual enable via sqlplus or asmcmd.
ADVM-09105: Volume 'string' not found in 'string'.
Cause: The specified volume does not exist.
Action: Create volume via sqlplus or asmcmd.
ADVM-09106: Diskgroup 'string' not found.
Cause: The specified diskgroup does not exist.
Action: Create diskgroup via sqlplus or asmcmd.
ADVM-09107: ASM mounting diskgroup 'string'.
Cause: Informational
Action: None
ADVM-09108: ASM mount of diskgroup 'string' failed.
Cause: ASM found the specified diskgroup but could not mount it.
Action: Try mounting the diskgroup manually via sqlplus. If the mount fails, check ASM logs for errors related to the diskgroup, clear errors, and try again.
ADVM-09109: string driver failed to load.
Cause: The driver failed to load.
Action: View the system specific OS kernel log (for instance, /var/log/messages on Linux, Event Log on Windows). If the drivers have not previously been unloaded ('crsctl stop crs', 'acfsload stop', 'acfsroot uninstall'), it is not possible to reload them. If a specific error has occurred, than clear the error condition and try again. If the OS and\or architecture is not supported by the drivers, than contact Oracle Support Services for an updated driver package.
ADVM-09110: Offline mount point 'string' was dismounted for recovery.
Cause: Informational. The mount point referenced was fenced due to an underlying volume failure. In this case, the mount point was successfully dismounted for recovery.
Action: None
ADVM-09111: Offline mount point 'string' was recovered.
Cause: Informational - the mount point referenced was fenced due to an underlying volume failure. In this case, the mount point was successfully remounted, which has renabled IO to the file system.
Action: None
ADVM-09112: The following process IDs have open references on mount point 'string':
Cause: During shutdown of the CRS stack, it was determined that a process had files open on the mount point in the process of being dismounted. This prevents the dismount from succeeding.
Action: Terminate any process\applications that are using files on the mount point that is being dismounted before stopping the CRS stack.
ADVM-09113: These processes will now be terminated.
Cause: Informational
Action: None
ADVM-09114: completed
Cause: Informational
Action: None
ADVM-09115: The command 'string' returned an unexpected value.
Cause: This is an internal error.
Action: An internal error occurred during the installation process. Restart the installation process.
ADVM-09116: Offline mount point 'string' was not recovered.
Cause: An inaccessible mount point could not be restored to working condition.
Action: Manual intervention is required to clear the offline mount point. Dismount the mount point and remount it manually to restore access to the mount point.
ADVM-09117: Manual intervention is required.
Cause: Informational, from previous errors.
Action: Clear previous errors and retry.
ADVM-09118: string driver in use - cannot unload.
Cause: This may be seen during 'crsctl stop crs', 'acfsload stop', or 'acfsroot uninstall'. Applications (possibly ASM) have open references on the driver.
Action: Terminate applications, including ASM, that may be using the driver and retry.
ADVM-09119: string driver failed to unload.
Cause: An unknown error has occurred when trying to unload the driver.
Action: Check system specific logs (/var/adm/messages on Linux, Event Log on Windows) and clear any error conditions that are preventing the unload.
ADVM-09120: The 'string' machine architecture not supported.
Cause: ADVM/ACFS device drivers have not yet been ported to this CPU type or OS. This occurs when the customer manually tries to load the drivers on an architecture or system OS type that ACFS is not supported, such as VMS.
Action: Contact Oracle Support Services to determine if an updated driver is available for this OS and architecture, or install ACFS on a supported architecture and OS.
ADVM-09121: Failed to detect control device 'string'.
Cause: ADVM/ACFS device drivers have been started but the devices that should have been created have not been.
Action: Try 'acfsload stop' followed by 'acfsload start' or restarting the crs stack - 'crsctl stop crs', 'crsctl start crs'. If the control devices still do not exist, contact Oracle Support Services.
ADVM-09122: ADVM device not determined from mount point 'string'.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
ADVM-09123: 'string' command not found.
Cause: A required component of ACFS is missing. This could be an incomplete install, removal of files from the system after install, or an unknown cause.
Action: Re-install by running 'acfsroot install'. If that does not work, than contact Oracle Support Services. In the event that handle.exe // is not found, than please install handle from sysinternals.com or another site, and make sure that the PATH environment variable contains the install location. Retry the operation.
ADVM-09124: string driver failed to detach from the system driver stack.
Cause: The ACFS driver is being used by one or more mounted file systems.
Action: Unmount all ACFS file systems and retry the operation.
ADVM-09125: ADVM/ACFS is not supported on this OS: 'string'
Cause: ADVM/ACFS device drivers have not been ported to this OS.
Action: None
ADVM-09126: Attempting to terminate the program 'string' with OS process ID 'string'.
Cause: The process was using an ACFS file system, which was being forcibly unmounted. A kill signal was sent to allow the unmount to proceed.
Action: This message is informational.
ADVM-09127: Not all ADVM/ACFS drivers have been loaded.
Cause: ADVM/ACFS device drivers have been started but not all of them are detected as running.
Action: Try 'acfsload stop' followed by 'acfsload start'. If that does not start all drivers, than contact Oracle Support Services.
ADVM-09128: unknown query type 'string'
Cause: This is an internal error.
Action: Contact Oracle Support Services.
ADVM-09129: ADVM/ACFS not installed
Cause: No ADVM/ACFS drivers or commands have been found on the system. All ADVM and ACFS actions will be disabled.
Action: Install components using 'acfsroot install <options>'. No ACFS file systems or ADVM volume devices will be available until ADVM/ACFS has been installed.
ADVM-09130: Root access required
Cause: The user this command is executing as does not have sufficient privileges to run this command.
Action: Run this command as a user with administrative privileges.
ADVM-09135: string installation aborted.
Cause: Informational
Action: See preceding error message for more information.
ADVM-09136: PID string could not be killed.
Cause: Failed to kill a Process ID during a force unmount of a file system.
Action: Manually kill the process and retry the unmount.
ADVM-09137: Failed to set group on directory 'string'.
Cause: The group of the directory could not be changed.
Action: Make sure the user has permission to do so.
ADVM-09138: command 'string' completed with an error: string
Cause: 'acfsutil' did not successfully run.
Action: Correct the problem described in the accompanying error message from 'acfsutil'. If this error was returned within the context of a CRS resource execution, retry the CRS action after the problem is resolved.
ADVM-09139: Attempting recovery of offline mount point 'string'
Cause: An ACFS mount point reported by the 'acfsutil' command was not accessible.
Action: This message is informational. CRS will attempt to recover the mount point.
ADVM-09140: Unable to determine the correct drivers for this version of Windows: ID:string Major:string Minor:string Product Type:string
Cause: Error. ACFS is not supported on this Windows Version.
Action: Report this message to Oracle Support Services to determine if an update to ACFS is available.
ADVM-09149: unable to determine device mount status - unsupported OS name 'string'
Cause: The standard method to determine mount state of a device was unavailable. It is possible that ADVM/ACFS is not supported on the OS.
Action: Report the value of OS to Oracle Support Services.
ADVM-09150: Unexpected output from 'acfsutil info fs': 'string'.
Cause: Informational
Action: None
ADVM-09151: Ignoring request to mount due to existence of "oracle_nomounts" file: string
Cause: "An "oracle_nomounts" file was present, causing file system mount processing to be skipped during a CRS resource operation."
Action: Normal mount operations can be resumed by removing the "oracle_nomounts" file.
ADVM-09152: Program 'string' with OS process ID 'string' will not be terminated.
Cause: The process is using an ACFS file system which is being forcibly unmounted but it will not be terminated because it is a system critical process.
Action: Manual intervention may be required.
ADVM-09153: Program 'string' with OS process ID 'string' is using mount point 'string'.
Cause: The process is using the mount point.
Action: None - Informational.
ADVM-09154: Loading 'string' driver.
Cause: Informational.
Action: None
ADVM-09155: Checking for existing 'string' driver installation.
Cause: Informational.
Action: None
ADVM-09156: Detecting control device 'string'.
Cause: Informational.
Action: None
ADVM-09157: Detecting driver 'string'.
Cause: Informational.
Action: None
ADVM-09158: Configuration file 'string' in the /boot directory is not accessible.
Cause: A populated /boot directory, which contains static files required to install kernel modules, was not detected on the system.
Action: After restoring the /boot directory and the kernel configuration files, re-run "acfsroot install".
ADVM-09160: Can not use the silent and verbose options at the same time.
Cause: The -s and -v options were used in the command. These options are mutually exclusive.
Action: Re-execute the command with one of the options or neither.
ADVM-09161: acfsroot install: Install ADVM/ACFS components.
Cause: Informational.
Action: None
ADVM-09162: acfsroot uninstall: Uninstall ADVM/ACFS components.
Cause: Informational.
Action: None
ADVM-09163: acfsroot version_check: Check ADVM/ACFS version.
Cause: Informational.
Action: None
ADVM-09164: acfsroot enable: Enable ADVM/ACFS CRS resources.
Cause: Informational.
Action: None
ADVM-09165: acfsroot disable: Disable ADVM/ACFS CRS resources.
Cause: Informational.
Action: None
ADVM-09166: string [-h] [-s | -v]
Cause: Syntax error or help [-h] option was passed.
Action: Use syntax as specified in the 'Usage' message.
ADVM-09167: ADVM/ACFS is not installed or loaded. Run 'acfsroot install'.
Cause: An operation was requested that requires ADVM/ACFS to be running.
Action: Run 'acfsroot install' and then run the requested operation.
ADVM-09168: The CRS query "string" cannot be parsed.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
ADVM-09169: The CRS attribute value specification "string" is invalid.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
ADVM-09170: The file system's CRS resource name "string" is invalid.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
ADVM-09171: The CRS resource for the file system on device string cannot be retrieved
Cause: Informational
Action: Analyze the error messages that precede this message.
ADVM-09172: The CRS resource for the file system on device string cannot be registered
Cause: Informational
Action: Analyze the error messages that precede this message.
ADVM-09173: The srvctl command line "string" failed to execute. (number)
Cause: This is an internal error.
Action: Contact Oracle Support Services.
ADVM-09174: unable to communicate with CRS
Cause: The application failed to communicate with CRS.
Action: Verify that CRS is running. Check the CRS logs to determine why the CRS resource is not responding.
ADVM-09175: Invalid trace level. Valid values for trace level are 0, 1 or 2.
Cause: An invalid trace level was provided.
Action: Use a supported trace level: 0, 1, or 2.
ADVM-09176: Entering 'string'
Cause: Informational.
Action: None
ADVM-09177: Return from 'string'
Cause: Informational.
Action: None
ADVM-09178: Return code = string
Cause: Informational.
Action: None
ADVM-09179: Command executed: 'string', output = 'string'
Cause: Informational.
Action: None
ADVM-09180: Sub-command is 'string'
Cause: Informational.
Action: None
ADVM-09181: Kernel version is 'string'
Cause: Informational.
Action: None
ADVM-09182: Variable 'string' has value 'string'
Cause: Informational.
Action: None
ADVM-09183: Query = 'string'
Cause: Informational.
Action: None
ADVM-09184: string [-h] [-s | -v | -t <0,1,2>]
Cause: Either a syntax error or unknown option was specified, or the help (-h) option was specified.
Action: Use syntax as specified in the 'Usage' message.
ADVM-09185: string [-h] [-s | -v | -t <0,1,2>] [-l <directory>]
Cause: Either a syntax error or unknown option was specified, or the help (-h) option was specified.
Action: Use syntax as specified in the 'Usage' message.
ADVM-09186: Usage: acfsroot uninstall [-h] [-s | -v | -t <0,1,2>]
Cause: Either a syntax error or unknown option was specified, or the help (-h) option was specified.
Action: Use syntax as specified in the 'Usage' message.
ADVM-09187: Usage: acfsroot version_check [-h] [-t <0,1,2>] [-l <location>]
Cause: Either a syntax error or unknown option was specified, or the help (-h) option was specified.
Action: Use syntax as specified in the 'Usage' message.
ADVM-09188: cannot use the trace option with the silent or verbose options
Cause: Conflicting options were specified.
Action: Specify only one of -s, -v, and -t.
ADVM-09189: [-t <0,1,2> ] - trace level
Cause: Either a syntax error or unknown option was specified, or the help (-h) option was specified.
Action: Use syntax as specified in the 'Usage' message.
ADVM-09190: User group 'string' does not exist.
Cause: The group name is required to create ADVM/ACFS devices with the correct attributes. The group name could not be found in the /etc/group file nor in the various remote services like LDAP, AD, NIS/Yellow Pages, DNS, etc.
Action: Ensure that the required group exists, then re-run the command.
ADVM-09191: Usage: acfsroot version_check [-h] [-t <0,1,2>]
Cause: Either a syntax error or unknown option was specified, or the help (-h) option was specified.
Action: Use syntax as specified in the 'Usage' message.
ADVM-09200: Supported
Cause: ADVM/ACFS device drivers have been ported to this OS or CPU type.
Action: None - Informational.
ADVM-09201: Not Supported
Cause: ADVM/ACFS device drivers have not yet been ported to this OS or CPU type.
Action: None
ADVM-09203: true
Cause: ADVM/ACFS device drivers were installed/loaded.
Action: None
ADVM-09204: false
Cause: ADVM/ACFS device drivers were not installed/loaded.
Action: None
ADVM-09205: usage: string [-h] [-orahome <home_path>] {installed | loaded | version | supported | validate} [-s]
Cause: Syntax error or help [-h] option was passed.
Action: Use syntax as specified in the 'Usage' message.
ADVM-09206: usage: string [-orahome <ORACLE_HOME>] {installed | loaded | version | supported} [-s]
Cause: Syntax error.
Action: Use syntax as specified in the 'Usage' message.
ADVM-09207: The user this command is executing as does not have permission to execute Perl in 'string'.
Cause: Perl permissions are read/write/execute owner (0700). The user this command is executing as is not the owner of the perl binary.
Action: Enter the db home as an argument to -orahome. Ensure that the user executing the command has execute permission on the perl binary in that db home.
ADVM-09208: Enter the location of the db home for this database to '-orahome'.
Cause: Perl permissions are read/write/execute owner (0700). The user this command is executing as is not the owner of the perl binary.
Action: Enter the db home as an argument to -orahome. Ensure that the user executing the command has execute permission on the perl binary in that db home.
ADVM-09210: The ADVM/ACFS drivers are supported but have not been verified on this Operating System version.
Cause: The drivers have not been explicitly tested on this operating system version but are expected to work properly.
Action: This message is informational.
ADVM-09211: usage: string [-h] [-orahome <home_path>] {installed | loaded | version | supported} [-s]
Cause: Syntax error or help [-h] option was passed.
Action: Use syntax as specified in the 'Usage' message.
ADVM-09225: Failed to start OKS persistent logging.
Cause: The drivers were successfully loaded but OKS persistent logging failed to start.
Action: run "acfsutil plogconfig -d <GridHome>" to perform a manual start.
ADVM-09226: ADVM/ACFS drivers not correct for this OS - cannot load.
Cause: The device drivers installed are not compatible with the currently running operating system
Action: run "acfsroot install <options>" to install the correct drivers.
ADVM-09250: Unable to get the ASM administrator user name from the ASM process.
Cause: ASM processes have not been found running on this system. This will prevent the requested action from being completed.
Action: Start ASM ('srvctl start asm') and retry the operation.
ADVM-09251: Mount point 'string' unmounted.
Cause: Informational.
Action: None
ADVM-09252: The following process IDs have open references on mount point 'string':
Cause: Informational.
Action: None
ADVM-09253: Failed to unmount mount point 'string'. Mount point likely in use.
Cause: Other processes have outstanding open references on the mount point.
Action: Terminate applications using files on the mountpoint than retry the // operation (' crsctl stop crs' ).
ADVM-09254: Manual intervention is required.
Cause: Follow up message to ACFS-9253.
Action: None - Informational.
ADVM-09255: Creating 'string' mount point.
Cause: Informational.
Action: None
ADVM-09256: Failed to create mountpoint 'string'.
Cause: The mount point may already exist, the user executing the command may have insufficient permission, or a system specific error may have occurred.
Action: Choose another mount point, execute the action from an account with the required permissions, or resolve the specified error shown before this message.
ADVM-09257: Mounting device 'string' on mount point 'string'.
Cause: Informational.
Action: None
ADVM-09258: Failed to mount device 'string' on mount point 'string'.
Cause: The mount point may be in use, the user executing this command may have insufficient permissions, or another system specific error may have occurred.
Action: Make sure that the mount point is available, ensure the user executing the command has the correct permissions, or resolve any system error shown before this message.
ADVM-09259: Mount point 'string' already has a device mounted on it.
Cause: There is already a device mounted on this mount point.
Action: If the new device is meant to replace the old device on this mount point, unmount the old one first and retry the operation. Otherwise this error may be ignored.
ADVM-09260: Failed to connect to the ASM instance.
Cause: ASM connection attempt failed.
Action: Ensure that the ORACLE_SID environment variable is correctly set to // the value of the ASM instance. In addition, verify that ASM is running ('srvctl status asm').
ADVM-09261: Invalid _ORA_NAME format.
Cause: This is an internal error.
Action: Report this to Oracle Support Services.
ADVM-09262: Invalid sub-command 'string'.
Cause: This is an internal error or the user attempted to run the script manually with an incorrect sub-command.
Action: Contact Oracle Support Services or use a correct sub-command.
ADVM-09263: Valid sub-commands are 'start', 'stop', 'check', and 'clean'.
Cause: This results in an incorrect usage of the command.
Action: Run the command with an option (command) that is supported, such as 'start', 'stop', 'check', or 'clean'.
ADVM-09264: Mount point 'string' is not mounted.
Cause: Informational.
Action: None
ADVM-09274: Resource 'string' is not online.
Cause: Informational.
Action: None
ADVM-09275: The clean failed to unmount the required mountpoint(s) - re-trying.
Cause: Informational. A file system could not be unmounted. This could be due to new process being started just before the unmount.
Action: None. 9276 - 9288 UNUSED
ADVM-09289: string not set in environment.
Cause: The referenced environment variable was not set. This makes it impossible to continue with the requested action.
Action: Ensure that the referenced variable is set and retry the operation.
ADVM-09290: Waiting for ASM to shutdown.
Cause: The resource cannot be terminated while ASM is running.
Action: Wait for ASM to stop. Stop it manually if that does not happen.
ADVM-09291: Waiting for the Windows 'sc stop string' command to complete.
Cause: Informational. System activity is preventing the driver from stopping.
Action: If the driver does not unload, a node reboot may be necessary
ADVM-09300: ADVM/ACFS distribution files found.
Cause: Informational.
Action: None
ADVM-09301: ADVM/ACFS installation cannot proceed:
Cause: Previous errors have caused the installation to reach a point where it cannot continue.
Action: Fix previous errors.
ADVM-09303: No installation files found for OS kernel version string.
Cause: If '-l' (distribution directory) was specified, the directory may not be valid.
Action: Choose a proper distribution location version.
ADVM-09304: Installation cannot proceed: Failed to unload ADVM/ACFS drivers.
Cause: Applications (possibly ASM) have open references on the drivers.
Action: Terminate applications and ASM that may be using the drivers, and retry the installation.
ADVM-09305: ADVM/ACFS installation cannot proceed:
Cause: Informational.
Action: Clear previous error and retry.
ADVM-09306: Failed to uninstall previous installation.
Cause: Could not remove ADVM/ACFS commands and or drivers.
Action: Commands and/or drivers are likely in use. Wait for operations to finish, unload the drivers, and retry the installation.
ADVM-09307: Installing requested ADVM/ACFS software.
Cause: Informational.
Action: None
ADVM-09308: Loading installed ADVM/ACFS drivers.
Cause: Informational.
Action: None
ADVM-09309: ADVM/ACFS installation correctness verified.
Cause: Informational.
Action: None
ADVM-09310: ADVM/ACFS installation failed.
Cause: A previous error caused this installation to fail.
Action: Correct previous error and retry the installation.
ADVM-09311: not all components were detected after the installation.
Cause: ADVM/ACFS commands and drivers were found in the installation area but did not get placed in their assigned locations.
Action: Re-install using 'acfsroot install -l <options>'. If necessary, contact Oracle Support Services.
ADVM-09312: Existing ADVM/ACFS installation detected.
Cause: Informational.
Action: None
ADVM-09313: No ADVM/ACFS installation detected.
Cause: An attempt was made to un-install ADVM/ACFS components that did not exist on the system.
Action: None - there is no problem.
ADVM-09314: Removing previous ADVM/ACFS installation.
Cause: Informational.
Action: None
ADVM-09315: Previous ADVM/ACFS components successfully removed.
Cause: Informational.
Action: None
ADVM-09316: Valid ADVM/ACFS distribution media detected at: 'string'
Cause: Informational.
Action: None
ADVM-09317: No ADVM/ACFS distribution media detected at location: 'string'
Cause: If -l (location) is used, the directory specified may be invalid.
Action: Use the correct directory.
ADVM-09318: ORACLE_HOME is not set.
Cause: This is an internal error.
Action: Report this to Oracle Support Services.
ADVM-09319: Unknown OS kernel version 'string' detected.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
ADVM-09320: Missing file: 'string'.
Cause: A required command or driver is not found on the installation media (pre install) or system (post install).
Action: If post install, try running acfsroot again. Otherwise, contact Oracle Support Services.
ADVM-09321: Creating udev for ADVM/ACFS.
Cause: Informational.
Action: None
ADVM-09322: completed
Cause: Informational.
Action: None
ADVM-09323: Creating module dependencies - this may take some time.
Cause: Informational.
Action: None
ADVM-09324: Alternate drivers installed.
Cause: Informational.
Action: None
ADVM-09327: Verifying ADVM/ACFS devices.
Cause: Informational.
Action: None
ADVM-09328: unknown query type 'string'.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
ADVM-09329: Failed to uninstall driver: 'string'.
Cause: Acfsinstall failed to uninstall the driver.
Action: Drivers may be in use. Correct previously reported errors and retry uninstall. If that fails, contact Oracle Support Services.
ADVM-09330: Binary 'string' not installed.
Cause: A component that should have been installed was not installed.
Action: Rerun 'acfsroot install'.
ADVM-09339: The environment variable ORACLE_HOME is not set.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
ADVM-09340: failed to install string driver.
Cause: Acfsinstall failed to install the driver.
Action: Run acfsinstall manually to see reported errors, resolve them, and retry.
ADVM-09341: Binary 'string' not found.
Cause: One of the binaries that make up the ACFS package is missing.
Action: Reinstall the ACFS package and retry the operation.
ADVM-09343: Unable to retrieve OS kernel version from module string.
Cause: Running modinfo against the usm driver failed.
Action: None - the current OS kernel version will be used instead.
ADVM-09344: Missing directory: 'string'.
Cause: A required directory is not found on the system.
Action: Contact Oracle Support Services.
ADVM-09345: Unable to create directory: 'string'.
Cause: Creation of a required directory failed.
Action: Contact Oracle Support Services.
ADVM-09346: Unable to install file: 'string'.
Cause: Copying to the given destination failed.
Action: Rerun acfsroot after correcting the OS error.
ADVM-09347: Unable to set permission bits (string) on: 'string'.
Cause: Setting the given permission bits failed.
Action: Manually set the permissions to the required level.
ADVM-09348: Unable to remove 'string'.
Cause: A previously installed file was unable to be removed.
Action: Attempt to manually remove the file.
ADVM-09349: Unable to configure driver 'string'.
Cause: A driver was installed but add_drv failed to write a configuration file.
Action: Correct the OS error and re-run acfsroot install.
ADVM-09350: Failed to create a symbolic link from 'string' to 'string'.
Cause: Creating a symbolic link failed.
Action: Rerun acfsroot after correcting the OS error.
ADVM-09351: Unable to remove devlink entry for 'string'.
Cause: An entry for the driver was found in /etc/devlink.tab but it was not possible to remove the entry.
Action: Manually remove the entry from /etc/devlink.tab and re-run acfsroot uninstall
ADVM-09352: Unable to write to 'string'.
Cause: A file required modifications but it was not possible to write to it.
Action: Check the file permissions.
ADVM-09353: Unable to unconfigure string.
Cause: A call to rem_drv failed.
Action: Correct the OS error and re-run acfsroot uninstall.
ADVM-09354: Unable to create symlink: 'string'.
Cause: Ensure that a file with the same name does not already exist and the user has permission.
Action: Remove the existing file and make sure the user has the required permission.
ADVM-09355: Performing AIX setup failed with error code 'string'.
Cause: Running AIX initial setup has failed.
Action: Correct the error and re-run the root install script.
ADVM-09356: Saving the AIX ODM changes for 'string' failed with error code 'string'.
Cause: Running the AIX savebase command failed.
Action: Correct the error and re-run the root install script.
ADVM-09357: Getting the ASMADMIN group failed with error code 'string'.
Cause: Previous installation steps may have failed.
Action: Correct the preceding error and re-run the root install script.
ADVM-09358: Adding the AIX ODM entry for 'string' failed with error code 'string'.
Cause: Running the AIX odmadd command failed.
Action: Correct the error and re-run the root install script.
ADVM-09360: The command aixsetup failed with error code 'string'.
Cause: Running the aixsetup script failed.
Action: Correct the error and re-run the root install script.
ADVM-09361: Removing device 'string' failed with error code 'string'.
Cause: Running the device's undefine method failed.
Action: Correct the error and re-run the root uninstall script.
ADVM-09362: Warning: deleting the AIX ODM entry for 'string' failed with error code 'string'.
Cause: Running the odmdelete command failed.
Action: Manually remove the entry or ignore the message.
ADVM-09363: Opening the file /etc/vfs for read failed.
Cause: The /etc/vfs file is not readable.
Action: Check the permission of the file and ensure it has read permission.
ADVM-09364: Opening the file /etc/vfs for append failed.
Cause: The /etc/vfs file is not writable.
Action: Check the permission of the file and ensure it has write permission.
ADVM-09365: The directory 'string' is not being removed.
Cause: The directory was scheduled to be uninstalled, but it contained files that were not installed by acfsroot.
Action: Manually remove the directory.
ADVM-09366: Relative path for mount point 'string' is not supported.
Cause: Mount point was provided as a relative path.
Action: Specify the mount point in the form of an absolute path.
ADVM-09381: Modification of ADVM/ACFS drivers resource failed.
Cause: An attempt to modify the ACFS drivers resource resulted in an error.
Action: Contact Oracle Support Services.
ADVM-09382: Modification of ADVM/ACFS drivers resource succeeded.
Cause: Informational.
Action: None
ADVM-09383: ADVM/ACFS uninstall cannot proceed
Cause: ADVM/ACFS uninstall cannot proceed due to an error. This message is accompanied by other message(s) providing details on the error.
Action: Correct the problem indicated in the other messages.
ADVM-09384: Invalid OS kernel variation 'string'.
Cause: The command found an OS kernel variation (e.g., "el5", etc) that it did not recognize as a valid ADVM/ACFS supported kernel.
Action: Boot a supported kernel
ADVM-09385: Usage: acfsroot version_check [-h] [-l <location>]
Cause: Syntax error or help [-h] option was passed.
Action: Use syntax as specified in the 'Usage' message.
ADVM-09388: An absolute path name must be specified for the alternate location.
Cause: A relative path name to the distribution files was specified.
Action: Enter the absolute path name instead.
ADVM-09389: ORACLE_HOME is not set to the location of the Grid Infrastructure home.
Cause: The ORACLE_HOME environment variable was not set correctly.
Action: Make sure that the ORACLE_HOME environment variable is set to the location of the Grid Infrastructure home and that it is properly exported.
ADVM-09390: The command 'string' returned unexpected output that may be important for system configuration:
Cause: One of the operating system commands used to configure the system returned an unexpected error. This message is accompanied by other message(s) providing details of the error.
Action: See the operating system documentation for the specific command for more information on this error.
ADVM-09391: Checking for existing ADVM/ACFS installation.
Cause: Informational.
Action: None
ADVM-09392: Validating ADVM/ACFS installation files for operating system.
Cause: Informational.
Action: None
ADVM-09393: Verifying ASM Administrator setup.
Cause: Informational.
Action: None
ADVM-09394: The installed driver string has a build date of string which does not match the loaded kernel module build date of string.
Cause: The most likely cause is that an upgrade or patch procedure failed to unload the kernel module.
Action: Reboot the system before attempting to use ACFS.
ADVM-09395: Environment variable ODMDIR is not set, unable to proceed with system configuration.
Cause: Environment variable ODMDIR was not set.
Action: Ensure that the ODMDIR environment variable is set to the location of a valid AIX ODM device configuration database.
ADVM-09396: Environment variable ODMDIR specifies a nonexistent path, unable to proceed with system configuration.
Cause: Environment variable ODMDIR specified a nonexistent path.
Action: Ensure that the ODMDIR environment variable is set to the location of a valid AIX ODM device configuration database.
ADVM-09397: Modification of ADVM/ACFS registry resource failed.
Cause: An attempt to modify the ACFS registry resource resulted in an error.
Action: Contact Oracle Support Services.
ADVM-09398: Modification of ADVM/ACFS registry resource succeeded.
Cause: Informational.
Action: None
ADVM-09399: Calling 'acfsroot install' to install compatible ADVM/ACFS drivers.
Cause: Informational.
Action: None
ADVM-09400: Could not open the Service Control Manager.
Cause: You do not have administrator access.
Action: Log onto a user account with administrator privileges and retry.
ADVM-09401: Failed to install the driver.
Cause: The specified driver could not be installed.
Action: Respond based on the accompanying error message.
ADVM-09402: The driver file path is too long.
Cause: The path to the driver exceeded system limits.
Action: Move the driver to a shorter path or create a shorter link.
ADVM-09403: The driver can be either installed or removed, not both.
Cause: The /i and the /u switches are mutually exclusive.
Action: Use either /i to install or /u to uninstall the driver.
ADVM-09404: Specify either /i (install) or /u (uninstall).
Cause: Either /i to install or /u to uninstall the driver is required.
Action: The /i or the /u switch must be specified.
ADVM-09405: Only one driver can be installed at a time.
Cause: Multiple drivers were specified with the /i option.
Action: Enter only one driver on the command line.
ADVM-09406: Specify either /a (ADVM) or /o (ACFS) or /l (OKS).
Cause: The driver to be installed or uninstalled was not specified.
Action: Enter the driver option on the command line.
ADVM-09407: Could not find driver "string" in the current directory.
Cause: The driver could not be found in the directory specified.
Action: Verify and enter the correct driver path name.
ADVM-09408: The current directory is %"s".
Cause: Informational.
Action: None
ADVM-09409: CreateService failed (ERROR_SERVICE_EXISTS).
Cause: The driver service already exists.
Action: None. The service is active.
ADVM-09410: CreateService failed.
Cause: The driver service could not be created.
Action: Correct the problem indicated by the accompanying error message and retry the operation.
ADVM-09411: CreateService succeeded.
Cause: Informational.
Action: None
ADVM-09412: The driver was installed successfully.
Cause: Informational.
Action: None
ADVM-09413: RegCreateKeyEx failed.
Cause: Failed to create a Windows registry key.
Action: Correct the problem indicated by the accompanying error message and retry the operation.
ADVM-09414: RegSetValueEx (TypesSupported) failed.
Cause: Failed to set the Windows registry key.
Action: Correct the problem indicated by the accompanying error message and retry the operation.
ADVM-09415: RegSetValueEx (EventMessageFile) failed.
Cause: Failed to set the Windows registry key.
Action: Correct the problem indicated by the accompanying error message and retry the operation.
ADVM-09416: OpenService failed.
Cause: Could not start the driver.
Action: Correct the problem indicated by the accompanying error message and retry the operation.
ADVM-09417: The driver was started successfully.
Cause: Informational.
Action: None
ADVM-09418: StartService failed (SERVICE_ALREADY_RUNNING).
Cause: Informational.
Action: None. The driver is already running.
ADVM-09419: StartService failed.
Cause: The driver failed to start.
Action: Correct the problem indicated by the accompanying error message and retry the operation.
ADVM-09420: The driver is not currently installed on this node.
Cause: The driver is not installed to start.
Action: Install the driver using the '/i' option.
ADVM-09421: The driver is already installed on this node.
Cause: An attempt was made to install a driver that is already installed.
Action: None
ADVM-09422: The driver was removed successfully.
Cause: Informational.
Action: None
ADVM-09423: Failure trying to remove the driver, DeleteService failed. The driver service is pending deletion or is in an invalid state.
Cause: The driver could not be removed.
Action: Make sure that all references to the driver have been removed and, if the driver is "oracleacfs.sys", that "acfsutil detach" has been run. Verify that the driver is in the STOPPED state and then retry the operation. If the driver removal still fails, you probably need to reboot the node."
ADVM-09424: The driver was stopped successfully.
Cause: Informational.
Action: None
ADVM-09425: The driver could not be stopped: StopService failed.
Cause: The driver could not be stopped.
Action: Correct the problem indicated by the accompanying error message and retry the operation.
ADVM-09426: Unable to set the file attributes for file string.
Cause: The file attributes for the oject file could not be set.
Action: Reset the attributes with "attrib -r <file_name>" and then retry the operation.
ADVM-09427: Failed to unload ADVM/ACFS drivers. A system reboot is recommended.
Cause: An attempt to unload the ADVM/ACFS drivers was unsuccessful due to an unanticipated condition or configuration. The operating system state did not allow the driver to be unloaded successfully.
Action: Reboot the system to reestablish the operating system environment.
ADVM-09428: Failed to load ADVM/ACFS drivers. A system reboot is recommended.
Cause: An attempt to unload the ADVM/ACFS drivers was unsuccessful due to an unanticipated condition or configuration. The operating system state did not allow the driver to be unloaded successfully.
Action: Reboot the system to reestablish the operating system environment.
ADVM-09429: Failed to install ADVM/ACFS files.
Cause: An unexpected condition has been detected. The files were previously verified to exist.
Action: Check the file permissions. Contact Oracle Support if the problem cannot be resolved.
ADVM-09441: /i Install the driver
Cause: Syntax error.
Action: Use syntax as specified in the 'Usage' message.
ADVM-09442: /u Uninstall the driver
Cause: Syntax error.
Action: Use syntax as specified in the 'Usage' message.
ADVM-09443: /a Perform the operation for the ADVM driver
Cause: Syntax error.
Action: Use syntax as specified in the 'Usage' message.
ADVM-09444: /o Perform the operation for the ACFS driver
Cause: Syntax error.
Action: Use syntax as specified in the 'Usage' message.
ADVM-09445: /l Perform the operation for the OKS driver
Cause: Syntax error.
Action: Use syntax as specified in the 'Usage' message.
ADVM-09446: <path> Path to the driver. If not specified, defaults to oracleadvm.sys, oracleacfs.sys, or oracleoks.sys in the current directory
Cause: Syntax error.
Action: Use syntax as specified in the 'Usage' message.
ADVM-09450: Examples:
Cause: Informational.
Action: None
ADVM-09451: string /i /a (Install the ADVM driver from the current directory)
Cause: Informational.
Action: None
ADVM-09452: string /u /o (Uninstall the ACFS driver)
Cause: Informational.
Action: None
ADVM-09453: string /i /o c:\drivers\oracleacfs.sys (Install ACFS with the specified file)
Cause: Informational.
Action: None
ADVM-09454: Unable to delete the driver file string after stopping driver.
Cause: A call to the Windows DeleteFile function to delete the driver file failed.
Action: Manually delete the specified driver file using Windows Explorer. If you were installing the driver please retry after deletion.
ADVM-09455: Unable to copy driver file string to the path string.
Cause: Could not copy the driver file to the specified directory because the Windows CopyFile function failed.
Action: Manually delete any previous driver file from the specified directory using Windows Explorer and retry the install.
ADVM-09456: An attempt to stop the driver string failed.
Cause: The driver could not be properly stopped; it is in an invalid state.
Action: Reboot system.
ADVM-09457: The driver file does not match the driver chosen to install.
Cause: The driver file is not consistent with the driver option used.
Action: Specify a path to oracleoks.sys when using the /l option. path to oracleacfs.sys with the /o option and path to oracleadvm.sys with the /a option.
ADVM-09458: The Windows 'string' service is in an invalid state. The new driver cannot be installed.
Cause: An attempt to install the new driver failed because the existing service could not be stopped properly.
Action: Reboot system and then retry the install.
ADVM-09459: ADVM/ACFS is not supported on this OS version: 'string'
Cause: ADVM/ACFS device drivers have not been ported to this OS version.
Action: None
ADVM-09500: Location of Oracle Home is 'string' as determined from the internal configuration data
Cause: Informational.
Action: None
ADVM-09501: Location of Oracle Home is 'string' as determined from the ORACLE_HOME environment variable
Cause: Informational.
Action: None
ADVM-09502: Location of Oracle Home is 'string' as determined from the location of the Oracle library files
Cause: Informational.
Action: None
ADVM-09503: ADVM and ACFS driver media location is 'string'
Cause: Informational.
Action: None
ADVM-09504: Copying file 'string' to the path 'string'
Cause: Informational.
Action: None
ADVM-09505: Using acfsutil executable from location: 'string'
Cause: Informational.
Action: None
ADVM-09506: The files 'string' and 'string' are the same, not copying.
Cause: Informational. The file was not copied because the target and source point to the same file.
Action: None
ADVM-09507: Searching the alternative location: 'string'
Cause: Informational. The installation files were not found in the specified location. A likely path containing that location will be searched.
Action: None
ADVM-09508: ACFS installation aborted (component string).
Cause: Installation was aborted due to an error.
Action: See preceding error message for more information.
ADVM-10101: Authentication failed.
Cause: The specified ACFS Security administrator password was wrong.
Action: Re execute the command and provide the correct ACFS Security administrator password at the prompt.
ADVM-10120: ACFS Encryption not initialized.
Cause: ACFS Encryption was not initialized.
Action: Run 'acfsutil encr init [-p]' as system administrator to initialize encryption.
ADVM-10149: Realm description cannot exceed number characters
Cause: Realm description cannot exceed 1023 characters
Action: Select a shorter realm name and retry.
ADVM-10150: Realm description not specified within double quotation marks
Cause: Invalid description specified for realm.
Action: Enclose the realm description within double quotation marks.
ADVM-10151: Unmatched single quote or double quote.
Cause: Matching quote was not found.
Action: Add a matching quote and retry.
ADVM-10152: Realm name cannot exceed number characters.
Cause: Realm name length exceeded 255 characters.
Action: Select a shorter realm name and retry.
ADVM-10153: Realm 'string' not found on mount point 'string'.
Cause: Realm was not found on mount point.
Action: Ensure that the realm exists using the command 'acfsutil sec info -m <mount_point> -n'.
ADVM-10154: Failed to create realm 'string' on mount point 'string'.
Cause: Internal error.
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ADVM-10155: Realm 'string' created.
Cause: Realm was created.
Action: None
ADVM-10156: Failed to destroy realm 'string' on mount point 'string'.
Cause: Internal error.
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ADVM-10157: Realm 'string' destroyed.
Cause: Realm was destroyed.
Action: None
ADVM-10158: Improper value specified for -l option.
Cause: Invalid argument format was specified for -l option.
Action: Specify the argument in the format 'commandrule:ruleset'. A comma separated list can also be specified as 'cmd1:rs1,cmd2:rs2,cmd2:rs3'. For example:

* - acfsutil sec realm add r1 -m /mnt -l READ:rs1

* - acfsutil sec realm add r1 -m /mnt -l READ:rs1,MKDIR:rs2

ADVM-10159: The command requires at least one of the options -u, -G, -l, -f, or -e.
Cause: None of the options -u, -G, -l, -f, or -e were specified with this command.
Action: Specify at least one of the options -u, -G, -l, -f, or -e with this command.
ADVM-10160: Failed to add user 'string' to the realm 'string'.
Cause: Internal error.
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ADVM-10161: Added user 'string' to realm 'string'.
Cause: User was added to realm.
Action: None
ADVM-10162: Failed to add group 'string' to realm 'string'.
Cause: Internal error.
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ADVM-10163: Added group 'string' to the realm 'string'.
Cause: Group was added to the realm.
Action: None
ADVM-10164: Failed to add filter 'string:string' to the realm 'string'.
Cause: Internal error.
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ADVM-10165: Added filter 'string:string' to the realm 'string'.
Cause: Filter was added to the realm.
Action: None
ADVM-10166: Failed to add 'string' to the realm 'string'.
Cause: Internal error.
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ADVM-10167: Added 'string' to the realm 'string'.
Cause: Pathname was added to the realm.
Action: None
ADVM-10168: Failed to turn encryption ON for realm 'string'.
Cause: Internal error.
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ADVM-10169: Encryption turned ON for realm 'string'.
Cause: Encryption was turned ON for realm.
Action: None
ADVM-10170: Failed to delete user 'string' from realm 'string'.
Cause: Internal error.
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ADVM-10171: Deleted user 'string' from realm 'string'.
Cause: User was deleted from realm.
Action: None
ADVM-10172: Failed to delete group 'string' from the realm 'string'.
Cause: Internal error.
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ADVM-10173: Deleted group 'string' from realm 'string'.
Cause: Group was deleted from realm.
Action: None
ADVM-10174: Failed to delete filter 'string:string' from the realm 'string'.
Cause: Internal error.
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ADVM-10175: Deleted filter 'string:string' from realm 'string'.
Cause: Filter was deleted from realm.
Action: None
ADVM-10176: Failed to delete 'string' from realm 'string'.
Cause: Internal error.
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ADVM-10177: Deleted 'string' from realm 'string'.
Cause: Pathname was deleted from realm.
Action: None
ADVM-10178: Failed to turn encryption OFF for realm 'string'.
Cause: Internal error.
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ADVM-10179: Encryption turned OFF for realm 'string'.
Cause: Encryption was turned OFF for realm.
Action: None
ADVM-10180: Failed to get realm files or directories for realm 'string'.
Cause: Internal error.
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ADVM-10181: Failed to get groups for realm 'string'.
Cause: Internal error.
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ADVM-10182: Failed to get users for realm 'string'.
Cause: Internal error.
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ADVM-10183: Failed to get filters for realm 'string'.
Cause: Internal error.
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ADVM-10184: Failed to get realm encryption attributes of realm 'string'.
Cause: Internal error.
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ADVM-10185: '-e' requires both '-a' and '-k'.
Cause: At least one of the options -a or -k is missing with -e option.
Action: Specify both '-a' and '-k' with '-e' and retry.
ADVM-10186: Realm 'string' already exists on mount point 'string'.
Cause: Realm was already found on mount point.
Action: Specify another realm name and retry.
ADVM-10187: Failed to get all realms on mount point 'string'.
Cause: Internal error.
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ADVM-10188: Attributes of realm 'string' retrieved.
Cause: Realm attributes were retrieved.
Action: None
ADVM-10189: Failed to update attributes of realm 'string'.
Cause: Internal error.
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ADVM-10190: Updated attributes of realm 'string'.
Cause: Updated realm attributes.
Action: None
ADVM-10206: File or directory 'string' does not belong to an ACFS file system
Cause: A File or directory specified in 'acfsutil sec realm add/delete' command did not belong to an ACFS file system.
Action: Specify only ACFS file or directory in the command 'acfsutil sec realm add/delete'.
ADVM-10221: Rule name cannot exceed number characters.
Cause: Rule name length exceeded 255 characters.
Action: Select a rule name that is smaller than 255 characters and retry.
ADVM-10223: Invalid rule type is specified.
Cause: Invalid rule type was provided on the command line with '-t'.
Action: Provide one of the following with '-t':

* - username <user_name>

* - application <application_name>

* - time <start_time>,<end_time>

* - hostname <host_name>

ADVM-10224: Rule type 'username', 'application' or 'hostname' must have only one rule value.
Cause: An incorrect number of arguments were provided with rule type 'username', 'application' or 'hostname'.
Action: Provide only one argument after the rule type 'username', 'application' or 'hostname'.

* For example, '-t username alice'

* '-t application 'c:\programs\mozilla.exe'

* '-t application '/sbin/cat'

* '-t hostname myhost.domain.com'

ADVM-10225: Rule type 'time' must have both start time and end time separated by a comma.
Cause: Either the start time or end time was not provided.
Action: Specify both start time and end time (comma separated) after rule type time.

* For example, '-t time 10:10:40,23:01:12'

ADVM-10226: '-o' requires either 'ALLOW' or 'DENY'.
Cause: A valid rule option was not provided.
Action: Specify either 'ALLOW' or 'DENY' as rule the option.
ADVM-10227: Failed to perform rule create operation on 'string'.
Cause: Internal error.
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ADVM-10228: Rule 'string' is created.
Cause: Rule was created.
Action: None
ADVM-10229: Rule 'string' not found.
Cause: Rule was not found.
Action: Ensure that the rule exists by executing 'acfsutil sec info -m <mnt> -l <rule-name>'.
ADVM-10230: Failed to perform rule edit operation on 'string'.
Cause: Internal error.
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ADVM-10231: Rule 'string' updated.
Cause: Rule was updated.
Action: None
ADVM-10232: Failed to destroy rule 'string'.
Cause: Internal error
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ADVM-10233: Rule 'string' destroyed.
Cause: Rule was destroyed.
Action: None
ADVM-10234: Failed to get rule 'string' information.
Cause: Internal error.
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ADVM-10235: Rule 'string' already exists.
Cause: Rule was already found on mount point.
Action: Specify another rule name and retry.
ADVM-10236: Time format string must be HH:MM:SS.
Cause: The time format provided was not formatted as 'HH:MM: SS', where HH translates to hours, MM to minutes and SS to seconds.
Action: Specify the time in correct format and retry.
ADVM-10237: Rule type 'string' specified does not match the actual type 'string' of rule 'string'
Cause: The rule type specified did not match the actual rule typed.
Action: Specify the actual rule type to update the rule value and retry.
ADVM-10238: Failed to get all rules on mount point 'string'.
Cause: Internal error.
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ADVM-10239: Failed to get information for rule 'string'.
Cause: Internal error.
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ADVM-10240: Cannot destroy rule 'string'. The rule is in use by one or more rule sets.
Cause: The rule was being used in one or more rule set(s) in the file system.
Action: Remove the rule from the rule set(s) and retry.
ADVM-10241: Rule set name cannot exceed number characters.
Cause: Rule set name length exceeded 255 characters.
Action: Select a shorter rule set name and retry.
ADVM-10242: '-o' requires either ALL_TRUE or ANY_TRUE.
Cause: The rule set option was not set to either ALL_TRUE or ANY_TRUE.
Action: Specify either ALL_TRUE or ANY_TRUE with the rule set option '-o'.
ADVM-10243: Failed to create rule set 'string' on mount point 'string'.
Cause: Internal error
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ADVM-10244: Rule set 'string' is created.
Cause: Rule set was created.
Action: None
ADVM-10245: Rule set 'string' not found on mount point 'string'.
Cause: Rule set was not found on mount point.
Action: None
ADVM-10246: Failed to add rule 'string' to the rule set 'string'.
Cause: Internal error.
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ADVM-10247: Added rule 'string' to the rule set 'string'.
Cause: Rule was added to the rule set.
Action: None
ADVM-10248: Failed to delete rule 'string' from the rule set 'string'.
Cause: Internal error.
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ADVM-10249: Deleted rule 'string' from rule set 'string'.
Cause: Rule was deleted from the rule set.
Action: None
ADVM-10250: Failed to destroy rule set 'string' on mount point 'string'.
Cause: Internal error.
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ADVM-10251: Rule set 'string' destroyed.
Cause: Rule set was destroyed.
Action: None
ADVM-10252: Failed to get rules for rule set 'string'.
Cause: Internal error.
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ADVM-10253: Failed to get list of command rules.
Cause: Internal error.
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ADVM-10254: Rule set 'string' already exists.
Cause: Rule set was already found on mount point.
Action: Specify another rule set name and retry.
ADVM-10255: Rule 'string' already exists in rule set 'string'.
Cause: Rule was already part of rule set.
Action: None
ADVM-10256: Rule 'string' is not found in rule set 'string'.
Cause: Rule was not found in the rule set.
Action: Ensure that the realm exists using the command 'acfsutil sec info -m <> -s <ruleset-name>'.
ADVM-10257: Failed to get all rule sets on mount point 'string'.
Cause: Internal error.
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ADVM-10258: Failed to get information for rule set 'string'.
Cause: Internal error.
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ADVM-10259: Invalid command rule 'string'.
Cause: Invalid command rule was specified.
Action: Execute 'acfsutil sec info -m <mount_point> -c' to get all the valid command rules.

* Re-execute the command with valid command rule.

ADVM-10260: File object 'string' and the realm 'string' should be in the same file system.
Cause: File object was not in the same file system as that of the realm.
Action: Specify file objects from the same file system as that of the realm.
ADVM-10261: Cannot destroy rule set 'string'. The rule set is in use by one or more realms.
Cause: The rule set is being used in filter(s) that are part of one or more realms in the file system.
Action: Remove the filter(s) from the realms that are using this rule set and retry.
ADVM-10262: Application path name for rule type 'application' cannot exceed 'number' characters.
Cause: Application path name for rule type 'application' exceeded 511 characters
Action: Select a shorter application path name for rule type 'application' and retry.
ADVM-10263: Host name for rule type 'hostname' cannot exceed 'number' characters.
Cause: Host name for rule type 'hostname' exceeded 255 characters.
Action: Select a shorter host name for rule type 'hostname' and retry.
ADVM-10264: Invalid value for rule type 'string' as the given path name 'string' is a symbolic link
Cause: Path name provided for rule type 'application' was a symbolic link. Symbolic links are not supported for rule type 'application'.
Action: Specify a path name which is not a symbolic link and re-execute the command.
ADVM-10271: Encryption algorithm can be only 'AES'.
Cause: The encryption algorithm provided was not 'AES'.
Action: Specify 'AES' as the algorithm with '-a' and retry.
ADVM-10272: Key length must be either 128, 192, or 256.
Cause: The key length specified with '-k' was not 128, 192 or 256.
Action: Specify either 128, 192, or 256 with '-k' and retry.
ADVM-10273: Failed to set the encryption parameter on realm 'string'.
Cause: Internal error.
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ADVM-10274: Failed to update rule set option.
Cause: Internal error.
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ADVM-10275: Failed to get rule sets for mount point 'string'.
Cause: Internal error.
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ADVM-10276: Rule set 'string' option updated to 'string'.
Cause: Rule set option updated.
Action: None
ADVM-10277: '-e' requires either ON or OFF.
Cause: The realm encryption status specified with '-e' was not 'on' or 'off'
Action: Specify either 'on' or 'off' with -e and retry.
ADVM-10278: Encryption parameters are not set on the file system, realm encryption is unavailable.
Cause: The encryption parameters were not set on the file system.
Action: A system administrator must execute an 'encr set' command
ADVM-10284: Failed to get security information for 'string'.
Cause: Internal error.
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ADVM-10285: Pathname 'string' does not exist.
Cause: Specified pathname was not found.
Action: Specify a valid pathname.
ADVM-10286: User 'string' does not exist.
Cause: User was not found.
Action: Specify a valid user.
ADVM-10287: Group 'string' does not exist.
Cause: Group was not found
Action: Specify a valid group.
ADVM-10288: User 'string' already added to the realm 'string'.
Cause: User was already added to the realm.
Action: None
ADVM-10289: Group 'string' already added to the realm 'string'.
Cause: Group was already added to the realm
Action: None
ADVM-10290: Realm filter 'string' already added to the realm 'string'.
Cause: Filter was already added to the realm.
Action: None
ADVM-10291: Pathname 'string' already added to the realm 'string'.
Cause: Pathname was already added to the realm.
Action: None
ADVM-10292: User 'string' is not part of the realm 'string'.
Cause: User was not part of the realm.
Action: None
ADVM-10293: Group 'string' is not part of the realm 'string'.
Cause: Group was not part of the realm.
Action: None
ADVM-10294: Pathname 'string' is not part of the realm 'string'.
Cause: Pathname was not part of the realm.
Action: None
ADVM-10295: Realm filter 'string' is not part of the realm 'string'.
Cause: Filter was not part of the realm.
Action: None
ADVM-10296: Realm filter 'string:string' could not be added to the realm 'string'.
Cause: The filter was not added because the filter with command rule 'ALL' was already part of the realm.
Action: Either add the command rules individually or add 'ALL' if all of the command rules are desired. Individual command rules cannot be added when 'ALL' is already present.
ADVM-10297: Realm filter 'ALL' could not be added since another filter exists in realm 'string'.
Cause: Filter 'ALL' was not added because another filter existed in the realm .
Action: Either add the command rules individually or add 'ALL' if all of the command rules are desired. 'ALL' command rule cannot be added when individual command rules are already present.
ADVM-10298: User name cannot exceed number characters.
Cause: User name length exceeded 64 characters.
Action: Select a shorter user name and retry.
ADVM-10299: Group name cannot exceed number characters.
Cause: Group name length exceeded 64 characters.
Action: Select a shorter group name and retry.
ADVM-10322: System realm 'SYSTEM_SecurityMetadata' created.
Cause: System realm 'SYSTEM_SecurityMetadata' was created.
Action: None
ADVM-10323: System realm 'SYSTEM_Logs' created.
Cause: System realm 'SYSTEM_Logs' was created.
Action: None
ADVM-10324: Rulesets cannot be cloned before cloning rules on mount point 'string'.
Cause: Rule sets were not cloned because some rules were not present on mount point.
Action: Clone rules first using command 'acfsutil sec rule clone' and then clone rule sets.
ADVM-10342: System realm 'SYSTEM_BackupOperators' created.
Cause: System realm 'SYSTEM_BackupOperators' was created.
Action: None
ADVM-10350: Incorrect password was entered in all attempts to open the encryption key store. Encrypted files will not be available.
Cause: Incorrect password was entered in all attempts to open the encryption key store during the mount command.
Action: Unmount the file system and remount it, providing the correct password. Encrypted files will not be available until the file system is unmounted and remounted with the correct password.
ADVM-10355: System realm 'SYSTEM_Antivirus' created.
Cause: System realm 'SYSTEM_Antivirus' was created.
Action: None
ADVM-10356: waiting for the operation to complete...
Cause: Informational.
Action: None
ADVM-10357: System realm 'SYSTEM_Audit' created.
Cause: Informational.
Action: None
ADVM-10400: Encryption is set on mount point 'string'.
Cause: Encryption was set on mount point.
Action: None
ADVM-10401: Failed to set encryption parameters on mount point 'string'.
Cause: Internal error.
Action: Refer to encryption log in '<mount_point>/.Security/encryption/logs/encr-<host_name>.log'.
ADVM-10402: Encryption turned 'string' on 'string'.
Cause: Encryption was turned either ON or OFF on the pathname.
Action: None
ADVM-10403: Failed to turn encryption 'string' on 'string'.
Cause: Internal error.
Action: Refer to encryption log in '<mount_point>/.Security/encryption/logs/encr-<host_name>.log'.
ADVM-10405: Failed to get encryption information on 'string'.
Cause: Internal error.
Action: Refer to encryption log in '<mount_point>/.Security/encryption/logs/encr-<host_name>.log'.
ADVM-10406: Re-key operation is complete on 'string'.
Cause: Re-key operation was complete on the pathname.
Action: None
ADVM-10407: Failed to perform re-key operation on 'string'.
Cause: Internal error.
Action: Refer to encryption log in '<mount_point>/.Security/encryption/logs/encr-<host_name>.log'.
ADVM-10410: encryption is already disabled on the file system
Cause: Encryption was already disabled on the file system.
Action: None, encryption is already disabled.
ADVM-10411: encryption is already enabled on the file system
Cause: Encryption was already enabled on the file system.
Action: None, encryption is already enabled.
ADVM-10412: Encryption parameters were not provided, using default algorithm (string) and key length (number).
Cause: Encryption parameters were not provided.
Action: None, default values have been used.
ADVM-10413: The ADVM compatibility attribute for the diskgroup must be set to version 11.2.0.2.0 to allow the acfsutil encryption and security commands.
Cause: The ADVM compatibility attribute has not been upgraded to version 11.2.0.2.0 or beyond.
Action: Use the ASMCA tool or the SQL ALTER DISKGROUP statement to upgrade COMPATIBLE.ADVM attribute.
ADVM-10414: Encryption has been initialized for the cluster.
Cause: An administrator initialized encryption for the cluster.
Action: None
ADVM-10415: File system level encryption is on, file level encryption operations are not allowed
Cause: A file level encryption operation was attempted while file system level encryption was enabled. File level encryption operations are not allowed when file system level encryption is turned on.
Action: None
ADVM-10416: File is realm secured
Cause: An encryption operation was attempted on a realm secured file and no action was performed. A realm secured file can only be encrypted and decrypted by changing the encryption parameters of containing realm(s) or by deleting the file from all realms.
Action: If changing the encryption status of this file is required, contact a Security Administrator to modify the encryption parameters of the containing realm(s).
ADVM-10419: Skipping directory 'string' because it does not belong to the file system mounted on 'string'
Cause: The directory does not belong to the specified mounted ACFS file system.
Action: None
ADVM-10420: Encryption parameters specified for realm 'string' match existing settings.
Cause: An attempt to set encryption parameters for a realm specified values the same as those already set.
Action: None
ADVM-10421: The ADVM compatibility attribute for the diskgroup must be set to version 'string' to allow acfsutil encryption commands.
Cause: An adminstrator attempted an encryption set or volume level rekey operation, but the ADVM compatibility attribute had not been upgraded to a supported version.
Action: Use the ASMCA tool or the SQL ALTER DISKGROUP statement to upgrade COMPATIBLE.ADVM attribute.
ADVM-10422: The ADVM compatibility attribute for the diskgroup must be set to version 'string' to allow 'acfsutil sec' commands.
Cause: A security adminstrator attempted an ACFS Security operation, but the ADVM compatibility attribute had not been upgraded to a supported version.
Action: Use the ASMCA tool or the SQL ALTER DISKGROUP statement to upgrade COMPATIBLE.ADVM attribute and retry the operation.
ADVM-10423: This encryption operation is not allowed on a standby file system.
Cause: An encryption operation that is not allowed on a standby file system was attempted. The following acfsutil encryption commands are not allowed on a standby file system: 'encr set', 'encr on', 'encr off', and 'encr rekey'.
Action: None
ADVM-10424: This ACFS Security operation is not allowed on a standby file system.
Cause: An ACFS Security operation that is not allowed on a standby file system was attempted. The following acfsutil security commands are not allowed on a standby file system: 'sec prepare', 'sec save/load/enable/disable', 'sec realm create/destroy/clone/add/delete', 'sec rule create/destroy/clone/edit', and 'sec ruleset create/destroy/clone/edit'
Action: None
ADVM-10450: Unauthorized encryption operation attempted on 'string'.
Cause: A user attempted an encryption operation on the given file and the operation was denied.
Action: None
ADVM-10451: File level encryption operation attempted on realm secured file 'string'.
Cause: A user attempted to perform a file level encryption command on a realm secured file and the operation was denied.
Action: None
ADVM-10452: Failed to decrypt 'string'.
Cause: Internal error.
Action: Contact Oracle Support Services.
ADVM-10453: Unable to get encryption parameters for the file system mounted on 'string'.
Cause: Internal error.
Action: Contact Oracle Support Services.
ADVM-10454: File system level encryption turned on for mount point 'string'.
Cause: A system administrator enabled file system level encryption.
Action: None
ADVM-10455: New volume encryption key generated for mount point 'string'.
Cause: A system administrator updated the volume encryption key for the mount point. The file encryption keys for all encrypted files on the file system were re-encrypted using the new volume encryption key.
Action: None
ADVM-10456: New file encryption key generated for file 'string'.
Cause: A system administrator updated the volume encryption key for the file. The data in the file was re-encrypted using the new key.
Action: None
ADVM-10457: New file encryption keys generated for all files in directory 'string'.
Cause: A system administrator updated the volume encryption key for the files in the given directory. The file contents were re-encrypted using the new key.
Action: None
ADVM-10458: Encryption turned off for path 'string'.
Cause: A user successfully decrypted a file or directory.
Action: None
ADVM-10459: Encryption turned off for directory 'string' and its contents.
Cause: A user successfully decrypted a directory and its contents.
Action: None
ADVM-10460: File system level encryption turned off for mount point 'string'.
Cause: A system administrator disabled file system level encryption.
Action: None
ADVM-10461: Encryption turned on for path 'string'.
Cause: A user successfully encrypted a file or directory.
Action: None
ADVM-10462: Encryption turned on for directory 'string' and its contents.
Cause: A user successfully encrypted a directory and its contents.
Action: None
ADVM-10463: Skipping file 'string' because it does not belong to the file system mounted on 'string'
Cause: The file does not belong to the specified mounted ACFS file system.
Action: None
ADVM-10464: ACFS Encryption operations are not allowed on files of this type.
Cause: An attempt was made to encrypt, decrypt, or rekey a file of one of the following Oracle file types: data, control, online redo log, archive log, backup, incremental backup, or flashback.
Action: None
ADVM-10500: Pathname cannot exceed number characters.
Cause: Pathname length exceeds 255 characters.
Action: Select a name that is smaller than %d characters and retry.
ADVM-10550: Security wallet created.
Cause: Security wallet was created.
Action: None
ADVM-10551: Security wallet creation failed.
Cause: Internal error.
Action: Contact Oracle Support Services.
ADVM-10564: Incorrect password for encryption key store.
Cause: An incorrect password was entered while opening the encryption key store.
Action: Retry the command and enter the correct password.
ADVM-10565: Encryption key store created.
Cause: Encryption key store was created.
Action: None
ADVM-10566: Encryption key store creation failed.
Cause: Internal error.
Action: Refer to encryption log in '<mount_point>/.Security/encryption/logs/encr-<host_name>.log'.
ADVM-10573: Encryption key store not found.
Cause: Encryption key store did not exist.
Action: Run 'acfsutil encr init' command and retry.
ADVM-10574: ACFS encryption already initialized, cannot reinitialize.
Cause: 'acfsutil encr init'can has already been executed and the encryption key store already existed.
Action: None
ADVM-10575: Incorrect encryption key store.
Cause: The encryption key store may have been deleted and re-created.
Action: Recover the correct key store from a backup and retry.
ADVM-10576: Incorrect encryption key, new volume encryption key not created.
Cause: The encryption key store may have been deleted and re-created.
Action: Recover the correct key store from a backup and retry.
ADVM-10577: Encryption parameters not set.
Cause: A command that requires encryption parameters to be set first was run before encryption parameters were set on the file system.
Action: Run 'acfsutil encr set' and retry.
ADVM-10578: Unable to communicate new encryption settings to cluster members.
Cause: Internal error.
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ADVM-10579: Key store is not valid for encryption.
Cause: The encryption key store was either not created using 'acfsutil encr init' or it was corrupted.
Action: Restore the encryption key store from a backup and retry.
ADVM-10586: Internal error.
Cause: Internal error occurred.
Action: Contact Oracle support service.
ADVM-10588: Internal error : WLT number.
Cause: Internal error occurred.
Action: Contact Oracle support service.
ADVM-10589: Internal error : BSF number.
Cause: Internal error occurred.
Action: Contact Oracle support service.
ADVM-10590: Internal error : XML number.
Cause: Internal error occurred.
Action: Contact Oracle support service.
ADVM-10591: Internal error : TSP number.
Cause: Internal error occurred.
Action: Contact Oracle support service.
ADVM-10592: Internal error : IOC number.
Cause: Internal error occurred.
Action: Contact Oracle support service.
ADVM-10593: Internal error : UGP number.
Cause: Internal error occurred.
Action: Contact Oracle support service.
ADVM-10594: Internal error : OCR number : string.
Cause: Internal error occurred.
Action: Contact Oracle support service.
ADVM-10596: Unable to get the hostname for the current node.
Cause: The current user does not have access to the requested information.
Action: Contact Oracle Support Services.
ADVM-10597: The user 'string' and the group 'string' do not belong to the same domain.
Cause: The user and the group were not part of the same domain.
Action: Use 'net user' command to verify and retry with user and group that belong to the same domain.
ADVM-10598: Unable to retrieve domain name information for 'string'.
Cause: Unable to retrieve domain name information.
Action: Make sure the node is part of proper domain.
ADVM-10599: Current user does not have system administrative privileges to initialize ACFS security.
Cause: The user was not part of system administrators group.
Action: Run 'acfsutil sec init' with administrative privileges.
ADVM-10600: Failed to store first security administrator 'string' in wallet.
Cause: Internal error.
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ADVM-10601: Failed to update first security administrator 'string' information.
Cause: Internal error.
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ADVM-10602: Passwords do not match.
Cause: Verification of the password did not succeed.
Action: Re-execute and provide the same password on both the prompts.
ADVM-10603: Security administrator group already set in wallet.
Cause: Security administrator group was already set in wallet.
Action: None
ADVM-10604: Security administrator group not set in wallet.
Cause: Internal error.
Action: Contact Oracle Support Service.
ADVM-10606: User 'string' is not a security administrator.
Cause: User was not a security administrator.
Action: Only a security administrator has privilege to execute the security commands. Add the user to security administrator list by executing 'acfsutil sec admin add' and retry.
ADVM-10607: User 'string' is not member of security administrator group.
Cause: User was not a member of security administrator's group.
Action: Add the user to the security administrator's group.
ADVM-10609: Administrator update in driver failed.
Cause: Internal error
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ADVM-10610: Failed to get current user information.
Cause: Internal error.
Action: Contact Oracle Support Service.
ADVM-10611: Failed to assign user 'string' as security administrator.
Cause: Internal error
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ADVM-10612: Failed to remove user 'string' from security administrator(s) list.
Cause: Internal error
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ADVM-10613: Failed to change ACFS Security administrator password for current user.
Cause: Internal error
Action: Contact Oracle Support Services.
ADVM-10614: Security administrator 'string' already added.
Cause: User was already a security administrator.
Action: None
ADVM-10615: User 'string' is not a security administrator.
Cause: User was not a security administrator.
Action: None
ADVM-10616: Incorrect ACFS Security administrator password.
Cause: The password supplied was incorrect.
Action: Re-execute and provide the correct ACFS Security administrator password for the current user.
ADVM-10617: Password cannot exceed number characters.
Cause: The password entered exceeded the maximum allowed characters.
Action: Enter the password within the specified number of characters.
ADVM-10618: Security administrator 'string' could not be added.
Cause: Security administrator was not added.
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ADVM-10619: Security administrator 'string' added.
Cause: Security administrator was added.
Action: None
ADVM-10620: Security administrator 'string' could not be removed.
Cause: Security administrator was not removed.
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ADVM-10621: Removal of the last security administrator 'string' is not allowed.
Cause: The security administrator was not removed being the only security administrator in this system.
Action: Add another security administrator to remove the intended security administrator.
ADVM-10622: Security administrator 'string' removed.
Cause: Security administrator was removed.
Action: None
ADVM-10623: ACFS security already initialized, cannot reinitialize.
Cause: ACFS security was already initialized and could not be reinitialized.
Action: None
ADVM-10624: User 'string' is not member of the group 'string'.
Cause: The user was not member of the group.
Action: Add the user to the group and retry.
ADVM-10625: Failed to prepare file system for security operations on mount point 'string'.
Cause: Internal error.
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ADVM-10626: Mount point 'string' is already prepared for security.
Cause: Mount point was already prepared for security. Prepare should be executed only once for an ACFS formatted file system that is mounted.
Action: None
ADVM-10627: Mount point 'string' is now prepared for security operations.
Cause: " Mount point was prepared for security operations.
Action: None
ADVM-10629: Failed to enable security on mount point 'string'.
Cause: Internal error.
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ADVM-10630: Security is already enabled on mount point 'string'.
Cause: Security was already enabled on mount point.
Action: None
ADVM-10631: Security is now enabled on mount point 'string'.
Cause: Security was enabled on mount point.
Action: None
ADVM-10632: Security is already disabled on mount point 'string'.
Cause: Security was already disabled on mount point.
Action: None
ADVM-10633: Security is now disabled on mount point 'string'.
Cause: Security was disabled on mount point.
Action: None
ADVM-10634: Failed to disable security on mount point 'string'.
Cause: Internal error.
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ADVM-10635: Failed to get security administrator group.
Cause: Internal error.
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ADVM-10636: Security administrator group retrieved.
Cause: Security administrators group was retrieved.
Action: None
ADVM-10637: File system is not prepared for ACFS security on mount point 'string'.
Cause: File system was not prepared for security operations on mount point.
Action: Execute 'acfsutil sec prepare' to prepare security operation on mount point.
ADVM-10638: Backup and log directories created.
Cause: Backup and log directories were created.
Action: None
ADVM-10639: Failed to create directory 'string' on mount point 'string'.
Cause: Internal error.
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ADVM-10640: Failed to create log directory on mount point 'string'.
Cause: Internal error.
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ADVM-10641: Failed to create backup directory on mount point 'string'.
Cause: Internal error.
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ADVM-10643: Security is already enabled on realm 'string'.
Cause: Security was already enabled on realm.
Action: None
ADVM-10644: Security is already disabled on realm 'string'.
Cause: Security was already disabled on realm.
Action: None
ADVM-10645: Failed to set owner of file 'string' to 'string'.
Cause: Current user is not owner of the file.
Action: Login as the file owner and re-run the command.
ADVM-10646: Failed to create secbackup.xml file on mount point 'string'.
Cause: Internal error.
Action: Contact Oracle Support Services.
ADVM-10647: Current user does not have system administrative privileges to initialize ACFS encryption.
Cause: The user was not part of system administrators group.
Action: Run 'acfsutil encr init' with administrative privileges.
ADVM-10648: ACFS security already initialized, recovery failed.
Cause: Previous execution of 'acfsutil sec init' had failed. Recovery actions also failed in the subsequent execution of 'acfsutil sec init'.
Action: Contact Oracle support services.
ADVM-10649: ACFS encryption already initialized, recovery failed.
Cause: Previous execution of 'acfsutil encr init' had failed. Recovery actions also failed in the subsequent execution of 'acfsutil encr init'.
Action: Contact Oracle support services.
ADVM-10650: Invalid file name 'string' for ACFS security metadata.
Cause: The file was invalid for saving or loading ACFS security metadata.
Action: Specify a valid file.
ADVM-10651: Failed to save ACFS security metadata of mount point 'string'.
Cause: Internal error
Action: Contact Oracle Support Services.
ADVM-10652: Saved ACFS security metadata of mount point 'string'.
Cause: ACFS security metadata of mount point '%s' was saved.
Action: None
ADVM-10653: Failed to save ACFS security string metadata of mount point 'string'.
Cause: Internal error.
Action: Contact Oracle Support Services.
ADVM-10654: Directory '.Security' does not exist on mount point 'string'.
Cause: Mount point was not prepared for ACFS security.
Action: Execute 'acfsutil sec prepare' on the mount point.
ADVM-10655: Failed to get hostname.
Cause: Internal error.
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ADVM-10656: Failed to get timestamp.
Cause: Internal error.
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ADVM-10657: Absolute and relative pathnames are not allowed with '-p' option.
Cause: Filename was provided with absolute or relative path.
Action: Specify only name of the file with '-p' option and retry.
ADVM-10658: ACFS Security has been initialized on the cluster with user 'string' as the initial Security Administrator and 'string' as the Security Administrator group.
Cause: An administrator initialized ACFS Security on the cluster.
Action: None
ADVM-10659: Cannot destroy realm 'string' because it is a system-created realm.
Cause: A request to destroy a system-created realm was denied because that operation is not allowed.
Action: None
ADVM-10660: Current user does not have required OS privileges to set ACFS encryption parameters.
Cause: Current user does not have root or administrator privileges to run 'acfsutil encr set'.
Action: Run 'acfsutil encr set' as a user who has root or administrator privileges.
ADVM-10661: Current user does not have required OS privileges to rekey the ACFS encryption parameters.
Cause: Current user does not have root or administrator privileges to run 'acfsutil encr rekey'.
Action: Run 'acfsutil encr rekey' as a user who has root or administrator privileges.
ADVM-10662: Current user 'string' does not have security administrator privileges.
Cause: A command requiring Security Administrator privileges was issued but the user is not in the Security Administrators group.
Action: Add current user to the Security Administrators group or log on as a user who has the required privileges, then retry the command.
ADVM-10663: User name 'string' is not a fully qualified name.
Cause: Fully qualified name was not specified. The supplied user name was not prefixed with a Windows Server Domain name.
Action: Specify a domain user name prefixed with Windows Server Domain name. For example, HOSPITAL-ADMIN\Alice where HOSPITAL-ADMIN is a Windows Server Domain name and Alice is the user name.
ADVM-10664: Group name 'string' is not a fully qualified name.
Cause: Fully qualified name was not specified.The supplied group name was not prefixed with a Windows Server Domain name.
Action: Specify domain group name prefixed with Windows Server Domain name. For example: HOSPITAL-ADMIN\Doctors where HOSPITAL-ADMIN is a Windows Server Domain name and Doctors is the group name.
ADVM-10665: Group 'string' is a local group and not a Windows Server Domain group.
Cause: Specified group was not a Windows Server Domain group.
Action: Specify a domain group name prefixed with Windows Server Domain name. For example, HOSPITAL-ADMIN\Doctors, where HOSPITAL-ADMIN is a Windows Server Domain name and Doctors is the group name.
ADVM-10666: User 'string' is a local user and not a Windows Server Domain user.
Cause: Specified user was not a Windows Server Domain user.
Action: Specify a domain user name prefixed with Windows Server Domain name. For example, HOSPITAL-ADMIN\Alice where HOSPITAL-ADMIN is a Windows Server Domain name and Alice is the user name.
ADVM-10667: Windows Server Domain 'string' does not exist.
Cause: Failed to get Windows Server Domain controller for the domain either because of not access to domain or domain does not exist.
Action: Specify the name of an existing Windows Server Domain.
ADVM-10675: Failed to load ACFS security metadata on mount point 'string'.
Cause: Internal error.
Action: Contact Oracle Support Services.
ADVM-10676: Loaded ACFS security metadata on mount point 'string'.
Cause: ACFS security metadata was loaded on mount point.
Action: None
ADVM-10677: Failed to load string on mount point 'string'.
Cause: Internal error.
Action: Contact Oracle Support Services.
ADVM-10679: Unable to resolve the user id 'string'.
Cause: The user was not found on the system.
Action: None
ADVM-10680: XDK version not compatible.
Cause: Oracle XDK version was incompatible.
Action: Install the correct Oracle XDK version and retry.
ADVM-10681: ACFS kernel version is not compatible. The kernel version on the system is 'string' while the expected kernel version is 'string' or above.
Cause: ACFS kernel version was incompatible.
Action: Install the correct version and retry.
ADVM-10682: Kernel major version is not compatible.
Cause: Kernel major version was incompatible.
Action: Install the correct version and retry.
ADVM-10683: Kernel release version is not compatible.
Cause: Kernel release version was incompatible.
Action: Install the correct version and retry.
ADVM-10684: Kernel update version is not compatible.
Cause: Kernel update version was incompatible.
Action: Install the correct version and retry.
ADVM-10685: Kernel port update version is not compatible.
Cause: Kernel port version was incompatible.
Action: Install the correct version and retry.
ADVM-10686: Kernel patch version is not compatible.
Cause: Kernel patch version was incompatible.
Action: Install the correct version and retry.
ADVM-10687: Kernel one off version is not compatible.
Cause: Kernel one off version was incompatible.
Action: Install the correct version and retry.
ADVM-10688: Unable to resolve the group id 'string'.
Cause: The OS group ID could not be resolved to a name. Usually this occurs because the OS group has been removed.
Action: None
ADVM-10689: Failed to update security administrators information in the driver, some of the subsequent commands may fail.
Cause: Updating driver security administrator data failed during mount. The mount completes, but subsequent security commands may be affected. This is an internal error.
Action: Contact Oracle Support Services.
ADVM-10690: Cannot edit groups in realm 'string'.
Cause: No changes were made to the groups in the realm as the operation is not allowed.
Action: None
ADVM-10691: Changed ACFS Security administrator password for current user.
Cause: Informational.
Action: None
ADVM-10700: Failed to store volume encryption key.
Cause: Internal error.
Action: Refer to encryption log in '<mount_point>/.Security/encryption/logs/encr-<host_name>.log'.
ADVM-10701: Failed to get volume encryption key.
Cause: Internal error.
Action: Refer to encryption log in '<mount_point>/.Security/encryption/logs/encr-<host_name>.log'.
ADVM-10702: Snapshots exist for the file system mounted on 'string'. New encryption parameters will not apply to files in these snapshots.
Cause: One or more snapshots existed for the file system when this encryption operation was done. The new encryption parameters set by this command will apply only to new files created in the file system and not to existing files in any snapshots. Note that none of the encryption commands affect files in any snapshots. Any snapshots created after the command was run will use the new encryption parameters.
Action: None
ADVM-10703: Snapshots exist for the file system mounted on 'string'. Encryption status of files in these snapshots will not change.
Cause: One or more snapshots existed for the file system when this encryption operation was done. The operation did not modify file data in any snapshots on the file system, so this data may still be available on disk unencrypted. Note that none of the encryption commands affect files in any snapshots.
Action: If you plan to use snapshots and encryption together, it is recommended that any snapshots be created after encrypting data on the file system. If the data on the file system was encrypted when some snapshots already existed, you may delete existing snapshots to ensure that data is not available in unencrypted form via any files in these snapshots.
ADVM-10704: Snapshots exist for the file system mounted on 'string'. Encryption keys of files in these snapshots will not be rekeyed.
Cause: One or more snapshots existed for the file system when this encryption operation was done. The operation did not rekey FEKs of files in any snapshots of the file system, so the FEKs of these files will continue to remain encrypted with the old parameters. Note that none of the encryption commands affect files in any snapshots.
Action: To ensure that all FEKs, including those of files in any snapshots, are encrypted with the new encryption parameters, this command should be run when the file system has no snapshots. If the command was run when some snapshots existed you may delete these snapshots. Any snapshots created after the command was run will use the new encryption parameters.
ADVM-10705: Cannot perform encryption operation because volume encryption keys for the file system mounted at 'string' are not available.
Cause: The encryption operation failed because the required volume encryption keys for the file system were not available to the ACFS file system driver. This could happen because an incorrect key store password was supplied during mount or because of some other error during mount.
Action: Remount the file system, providing the correct password during the mount operation if required. Address any other errors reported during mount. If the issue persists, contact Oracle Support Services.
ADVM-10706: Cannot perform encryption operation because an encryption undo operation is in progress.
Cause: The encryption operation failed because the system administrator was running encryption undo ('acfsutil encr set -u') on the file system. It is also possible that a previous encryption undo operation had not completed cleanly.
Action: There is no action to be taken by users who are not system administrators. If this message is seen by a system administrator and an encryption undo operation is not in progress, then a previous encryption operation did not complete properly. Run the 'acfsutil encr set -u' command again to complete the operation.
ADVM-10707: Cannot perform encryption undo operation because file system level encryption is on.
Cause: The encryption undo operation failed because file system level encryption was on.
Action: Turn file system level encryption off and retry the operation.
ADVM-10708: An earlier key store migrate operation did not complete. Provide the same password as the one used in the previous attempt.
Cause: An earlier run of 'acfsutil keystore migrate' command did not complete.
Action: When prompted for a password (ACFS-10349), provide the same password as the one used in the previous attempt.
ADVM-10709: Existing ACFS encryption key store is already password-protected.
Cause: Informational.
Action: None
ADVM-10710: Existing ACFS encryption key store is already not password-protected.
Cause: Informational.
Action: None
ADVM-10711: Recovery of ACFS encryption key store completed successfully.
Cause: Informational.
Action: None
ADVM-10712: ACFS encryption key store migration to password-protected key store completed successfully.
Cause: Informational.
Action: None
ADVM-10713: ACFS encryption key store migration to password-free key store completed successfully.
Cause: Informational.
Action: None
ADVM-10714: The environment variable OKV_HOME is not set.
Cause: The attempt to access the Oracle key vault server to obtain the volume encryption keys failed because the OKV_HOME environment variable was not set.
Action: Set the environment variable OKV_HOME and retry the command.
ADVM-10715: failed to find the PKCS library in path 'string'
Cause: The attempt to access the Oracle key vault server to obtain the volume encryption keys failed because the PKCS library was not found in '$OKV_HOME/lib'.
Action: Ensure that the OKV_HOME environment variable is set to point to the path that contains OKV client data, including the PKCS library. If not, set OKV_HOME and retry the command. If the problem persists, contact Oracle Support Services.
ADVM-10716: failed to load the PKCS library
Cause: The attempt to access the Oracle key vault server to obtain the volume encryption keys failed because the OKV PKCS library could not be loaded from '$OKV_HOME/lib'.
Action: Ensure that the OKV_HOME environment variable is set to point to the path that contains OKV client data, including the PKCS library. If not, set OKV_HOME and retry the command. If the problem persists, contact Oracle Support Services.
ADVM-10717: failed to find Oracle Key Vault (OKV) client configuration file
Cause: The attempt to access the Oracle key vault server to obtain the volume encryption keys failed because the OKV client configuration file, okvclient.ora, was not found in '$OKV_HOME/conf'.
Action: Ensure that the OKV_HOME environment variable is set to point to the path that contains OKV client data, including the OKV client configuration file, okvclient.ora. If not, set OKV_HOME and retry the command. If the problem persists, contact Oracle Support Services.
ADVM-10718: failed to login to OKV server
Cause: A login attempt to Oracle Key Vault (OKV) server failed.
Action: Ensure that correct password is provided, verify okvclient.ora file entries for servers, verify both the servers are still running, and then retry. If the problem persists, contact Oracle Support Services.
ADVM-10719: failed to store encryption keys in file system wallet
Cause: Internal error.
Action: Contact Oracle Support Services.
ADVM-10720: Key store must be either SSO, PKCS, or OKV.
Cause: An attempt to store an encryption key was rejected because the specified key store was not one of: SSO, PKCS or OKV.
Action: Retry the command specifying either SSO, PKCS, or OKV as the key store.
ADVM-10721: failed to save encryption keys, file system wallet already exists in directory 'string'
Cause: An attempt to create a new wallet and save encryption keys in it failed because the wallet already existed in the said location.
Action: Delete or move the wallet and retry the command.
ADVM-10725: Failed to start encryption logging on mount point 'string'.
Cause: Internal error.
Action: Contact Oracle Support Services.
ADVM-10726: Failed to start security logging on mount point 'string'.
Cause: Internal error.
Action: Contact Oracle Support Services.
ADVM-10727: Failed to start global security and encryption logging.
Cause: Global security and encryption logging services could not be started. The log file for this node will not be updated.
Action: None
ADVM-10728: ACFS encryption logging directory not found on mount point 'string'.
Cause: The ACFS encryption logging directory '<mount_point>/.Security/encryption/logs/' could not be opened.
Action: Ensure the logging directory exists and the system administrator can open and create files in this directory, then unmount the file system and remount it manually to restore logging functionality.
ADVM-10729: ACFS security logging directory not found on mount point 'string'.
Cause: The ACFS security logging directory '<mount_point>/.Security/realm/logs/' could not be opened.
Action: Ensure the logging directory exists and the security administrator can open and create files in this directory, then unmount the file system and remount it manually to restore logging functionality.
ADVM-10730: ACFS security and encryption logging directory not found in CRS_HOME.
Cause: The ACFS security and encryption logging directory '<CRS_HOME>/log/<host_name>/acfssec' could not be opened.
Action: Ensure the logging directory exists and the system administrator can open and create files in this directory.
ADVM-10731: Could not get local host name, ACFS encryption logging will not be available on mount point 'string'.
Cause: The local host name could not be determined, ACFS encryption logs for this host in '<mount_point>/.Security/encryption/logs/' will not be written.
Action: Ensure the operating system host name is set correctly and the system administrator can read this value, then unmount the file system and remount it manually to restore logging functionality.
ADVM-10732: Could not get local host name, ACFS security logging will not be available on mount point 'string'.
Cause: The local host name could not be determined, ACFS security logs for this host in '<mount_point>/.Security/realm/logs/' will not be written.
Action: Ensure the operating system host name is set correctly and the security administrator can read this value, then unmount the file system and remount it manually to restore logging functionality.
ADVM-10733: Could not get local host name, ACFS security and encryption logging will not be available for this host
Cause: The local host name could not be determined, ACFS security and encryption logs for this host in '<CRS_HOME>/log/<host_name>/acfssec' will not be written.
Action: Ensure the operating system host name is set correctly and the system administrator can read this value.
ADVM-10751: Realm_Metadata file has invalid realm record for file: string
Cause: A realm record of the indicated Realm_Metadata file was invalid.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-10753: Realm_Metadata file has no valid realm records for file: string
Cause: The indicated Realm_Metadata file did not contain any valid valid realm records.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-10755: Realm_Metadata file contains invalid realm record data for file: string
Cause: The indicated Realm_Metadata file contained at least one invalid realm record. Refer to the accompanying message(s) for more information on the problem.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-10756: Realm_Metadata file _Private structure is invalid for: for file: string
Cause: The _Private structure of the indicated Realm_Metadata file was invalid. Refer to the accompanying message(s) for more information on the problem.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-10757: Realm_Metadata file has invalid Hash_Table data for file: string
Cause: The Hash_Table of the indicated Realm_Metadata file contained inconsistent data. Refer to the accompanying message(s) for more information on the problem.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-10760: Realm_Metadata file _Private structure has invalid _maxFree value found: number minimum: number for structure: string
Cause: The _maxFree property of the indicated _Private metadata structure was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-10761: Realm_Metadata file _Private structure has invalid _freeDataListTail value found: number minimum: number for structure: string
Cause: The _freeDataListTail property of the indicated _Private metadata structure was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-10762: Realm_Metadata file node not on _freeDataList for file: string
Cause: One or more of the _security_data nodes of the indicated Realm_Metadata file was not found on the free data node list. The _next property for one or more of the _security_data nodes was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-10764: Realm_Metadata file has invalid _security_record for _Administrator default for file: string
Cause: The default _Administrator _security_record of the indicated Security_Metadata file was invalid.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-10766: Realm_Metadata file has no valid realm data records for file: string
Cause: The indicated Realm_Metadata file did not contain any valid valid realm data records.
Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.
ADVM-10768: Number of realms created on mount point 'string' has reached the limit number.
Cause: A request to create a realm was denied because the number of realms created on the mount point has reached the limit.
Action: Destroy any of the unused realms and retry the command.
ADVM-10769: Number of rulesets created on mount point 'string' has reached the limit number.
Cause: A request to create a ruleset was denied because the number of rulesets created on the mount point has reached the limit.
Action: Destroy any of the unused rulesets and retry the command.
ADVM-10770: Number of rules created on mount point 'string' has reached the limit number.
Cause: A request to create a rule was denied because the number of rules created on the mount point has reached the limit.
Action: Destroy any of the unused rules and retry the command.
ADVM-10771: Number of realms that file 'string' is part of has reached the limit number.
Cause: A request to add the file to a realm was denied because the number of realms that the file is part of has reached the limit.
Action: Remove the file from one or more realms and retry the command.
ADVM-10772: Security at the realm level will not be in effect until file system-level security is enabled.
Cause: Security is disabled at the file system level. When file system-level security is disabled, enabling realm-level security does not enable the authorization checks provided by the realm.
Action: Enable Security at file system level.
ADVM-10773: Unable to lock ACFS Security wallet.
Cause: The ACFS Security wallet lock was not acquired.
Action: Verify that Cluster Ready Services(CRS) stack is up by executing 'crsctl check crs' and Cluster Synchronization Services(CSS) is running by executing 'crsctl check css'. If the CRS stack is not up, check with the CRS administrator to bring it up. If it does not resolve the problem contact Oracle Support Services.
ADVM-10774: Unable to unlock ACFS Security wallet.
Cause: The ACFS Security wallet lock was not released.
Action: Verify that Cluster Ready Services(CRS) stack is up by executing 'crsctl check crs' and Cluster Synchronization Services(CSS) is running by executing 'crsctl check css'. If the CRS stack is not up, check with the CRS administrator to bring it up. If it does not resolve the problem contact Oracle Support Services.
ADVM-10775: Cannot proceed as another instance of 'acfsutil' command is updating the security administrator information.
Cause: ACFS Security wallet is locked by another instance of 'acfsutil' command.
Action: Retry the command after some time.
ADVM-10776: Invalid 'acfsutil' version 'string'
Cause: Internal error.
Action: Contact Oracle Support Services.
ADVM-10777: Unable to lock ACFS encryption key store.
Cause: The ACFS encryption key store lock could not be acquired.
Action: Verify that Cluster Ready Services(CRS) stack is up by executing 'crsctl check crs' and Cluster Synchronization Services(CSS) is running by executing 'crsctl check css'. If the CRS stack is not up, check with the CRS administrator to bring it up. If it does not resolve the problem contact Oracle Support Services.
ADVM-10778: Unable to unlock ACFS encryption key store.
Cause: The ACFS encryption key store lock was not released.
Action: Verify that Cluster Ready Services(CRS) stack is up by executing 'crsctl check crs' and Cluster Synchronization Services(CSS) is running by executing 'crsctl check css'. If the CRS stack is not up, check with the CRS administrator to bring it up. If it does not resolve the problem contact Oracle Support Services.
ADVM-10779: Cannot proceed as another instance of 'acfsutil' command is updating the encryption key store.
Cause: An acfsutil encryption request found the ACFS encryption key store locked by another instance of the acfsutil command.
Action: Retry the command after some time.
ADVM-10780: The file system mounted on 'string' has been prepared for ACFS Security, undo ACFS Security first.
Cause: ACFS Encryption cannot be undone when the file system has been prepared for ACFS Security.
Action: Undo ACFS Security prepare on the mount point by executing 'acfsutil sec prepare -m <mount_point> -u' as security administrator and retry.
ADVM-10781: existing snapshots preclude undoing ACFS security or encryption for the file system mounted on 'string'
Cause: An attempt to undo ACFS security or encryption for the indicated file system failed because there were existing snapshots for the file system. ACFS security and encryption can only be undone for a file system with no snapshots. This message may be displayed before or after all files have been decrypted by the 'acfsutil encr set -u' command. In both cases, the file system retains its encryption 'prepared' state and files can be encrypted without running 'acfsutil encr set' again.
Action: Remove all snapshots by executing 'acfsutil snap delete' and retry.
ADVM-10782: The file system mounted on 'string' has not been prepared for ACFS Security, nothing to be undone.
Cause: The file system was not prepared for ACFS Security.
Action: None
ADVM-10783: ACFS Encryption is not set on the file system mounted on 'string', nothing to be undone.
Cause: ACFS Encryption was not set on the file system.
Action: None
ADVM-10784: Could not destroy all realms, unable to undo ACFS Security.
Cause: All realms were not destroyed.
Action: Re-execute the command.
ADVM-10785: Could not destroy all rules, unable to undo ACFS Security.
Cause: All rules were not destroyed.
Action: Re-execute the command.
ADVM-10786: Could not destroy all rulesets, unable to undo ACFS Security.
Cause: All rulesets were not destroyed
Action: Re-execute the command.
ADVM-10787: Failed to prepare ACFS Security on mount point 'string' as replication is active on this mount point.
Cause: Replication was active on the mount point. ACFS Replication and ACFS Security cannot co-exist on the same mount point.
Action: Terminate replication by using command 'acfsutil repl term' and then retry.
ADVM-10788: ACFS Security undo operation on mount point 'string' completed.
Cause: ACFS Security undo operation on the mount point was completed.
Action: None
ADVM-10789: Failed to undo ACFS Security on mount point 'string'.
Cause: Internal error.
Action: Contact Oracle Support Services.
ADVM-10790: Failed to set ACFS Encryption on mount point 'string' as replication is active on this mount point.
Cause: Replication was active on the mount point. ACFS Replication and ACFS Encryption cannot co-exist on the same mount point.
Action: Terminate replication by using command 'acfsutil repl term' and then retry.
ADVM-10791: Failed to undo ACFS encryption on mount point 'string'.
Cause: Internal error.
Action: Contact Oracle Support Services.
ADVM-10792: Cannot add filter 'string:string' to the cloned realm as the rule set 'string' does not exist on the mount point 'string'.
Cause: Filters could not be added to cloned realm because rule sets were not present on mount point.
Action: Clone rules and rule sets first and then add command rules to the cloned realm using 'sec realm add' command.
ADVM-10793: File objects cannot be added to cloned realm as file objects do not exist on destination mount point.
Cause: File objects could not be added to cloned realm because file objects were not present on destination mount point.
Action: Copy File objects to destination mount point and then add file objects to the cloned realm using 'sec realm add' command.
ADVM-10794: File 'string' does not exist on mount point 'string'.
Cause: Information of file could not be obtained, because either file name specified is not correct or file does not exist on given mount point.
Action: Specify the correct file name or specify the mount point where the file exists.
ADVM-10795: Cannot load ACFS security meta data because the destination mount point 'string' already has some user-created rules, rule sets or realms.
Cause: ACFS security load was not done as the destination mount point had some user created rules, rule sets or realms.
Action: Run 'acfsutil sec prepare -u' followed by 'acfsutil sec prepare' on the destination mount point and then retry the command, or use a file system with no security objects (like realms, rules and rule sets) except system realms.
ADVM-10796: A prior failed encryption initialization cannot be recovered for this request because the prior initialization specified a password-protected key store.
Cause: A prior failed encryption initialization was not recovered for this request because the prior initialization specified a password-protected key store.
Action: Execute the command 'acfsutil encr init' with option 'p'.
ADVM-10797: A prior failed encryption initialization cannot be recovered for this request because the prior initialization specified a non-password-protected key store.
Cause: A prior failed encryption initialization was not recovered for this request because the prior initialization specified a non-password-protected key store.
Action: Execute the command "acfsutil encr init' without option 'p'.
ADVM-10798: ACFS Encryption undo operation on mount point 'string' completed.
Cause: ACFS Encryption undo operation on the mount point was completed.
Action: None
ADVM-10799: For cloning realms with 'string' option, destination mount point must be same as source mount point.
Cause: Cloning of file system objects is not supported if destination mount point is different from source mount point.
Action: Run 'acfsutil sec realm clone' without -f option, copy file objects to the destination mount point, and then add files using 'acfsutil sec realm add' command.
ADVM-10800: Failed to complete ACFS Security undo operation on mount point 'string'.
Cause: ACFS Security undo operation did not complete because some rules, rulesets, or realms exist for the given file system.
Action: Retry the operation after making sure that no other 'acfsutil sec' commands are running for the given file system.
ADVM-10801: failed to acquire a lock on ACFS security wallet
Cause: The ACFS security wallet could not be initialized because the lock on the wallet could not be obtained.
Action: Verify that Cluster Ready Services(CRS) stack is up by executing 'crsctl check crs' and Cluster Synchronization Services(CSS) is running by executing 'crsctl check css'. If the CRS stack is not up, check with the CRS administrator to bring it up. If this does not resolve the problem contact Oracle Support Services.
ADVM-10802: unable to release the lock being held on the ACFS security wallet
Cause: After security initialization, the lock on ACFS security wallet could not be released.
Action: Verify that Cluster Ready Services(CRS) stack is up by executing 'crsctl check crs' and Cluster Synchronization Services(CSS) is running by executing 'crsctl check css'. If the CRS stack is not up, check with the CRS administrator to bring it up. If this does not resolve the problem contact Oracle Support Services.
ADVM-10803: cannot proceed because another instance of 'acfsutil' command is updating the ACFS security wallet
Cause: An attempt to update the ACFS security wallet failed because the ACFS security wallet was locked by another instance of the acfsutil command.
Action: Retry the command later.
ADVM-10850: Password must have at least number characters.
Cause: The password was not long enough.
Action: Provide the password with number of characters greater than minimum required length.
ADVM-10851: Password must have at least one digit and letter in it.
Cause: The password did not have either a digit or a letter in it.
Action: Provide a password containing at least one digit and letter.
ADVM-10901: Failed to add the read-only snapshot file 'string' to realm 'string'.
Cause: A file specified for addition to a security realm was a read-only snapshot file.
Action: None
ADVM-10902: Failed to add the read-write snapshot file 'string' to realm 'string'.
Cause: A file specified for addition to a security realm was a read-write snapshot file.
Action: None
ADVM-10903: Snapshot 'string' of mount point 'string' is not prepared for ACFS Security.
Cause: Snapshot was not prepared for security operations on mount point.
Action: None
ADVM-10914: Security is already enabled in snapshot 'string' of mount point 'string'.
Cause: Security was already enabled in snasphot of mount point.
Action: None
ADVM-10915: Security is already enabled on realm 'string' in snapshot 'string' of mount point 'string'
Cause: Security was already enabled on realm in snapshot.
Action: None
ADVM-10916: Security is now enabled in snapshot 'string' of mount point 'string'.
Cause: Security was enabled in snapshot of mount point.
Action: None
ADVM-10917: Failed to enable security in snapshot 'string' of mount point 'string'.
Cause: Internal error.
Action: Contact Oracle Support Services.
ADVM-10918: Security is already disabled in snapshot 'string' of mount point 'string'.
Cause: Security was already disabled in snapshot of mount point.
Action: None
ADVM-10919: Security is already disabled on realm 'string' in snapshot 'string' of mount point 'string'.
Cause: Security was already disabled on realm in snapshot.
Action: None
ADVM-10920: Failed to disable security in snapshot 'string' of mount point 'string'.
Cause: Internal error.
Action: Contact Oracle Support Services.
ADVM-10921: Realm 'string' not found in snapshot 'string' of mount point 'string'.
Cause: Realm was not found in snapshot of mount point.
Action: Ensure that the realm exists using the command 'acfsutil sec info -m <mount_point> -S <snapshot_name> -n'.
ADVM-10922: Failed to get security related information of snapshot 'string' of mount point 'string'.
Cause: Internal error.
Action: Contact Oracle Support Services.
ADVM-10923: Failed to get users for realm 'string' in snapshot 'string' of mount point 'string'.
Cause: Internal error.
Action: Contact Oracle Support Services.
ADVM-10924: Failed to get groups for realm 'string' in snapshot 'string' of mount point 'string'.
Cause: Internal error.
Action: Contact Oracle Support Services.
ADVM-10925: Failed to get realm encryption attributes of realm 'string' in snapshot 'string' of mount point 'string'.
Cause: Internal error.
Action: Contact Oracle Support Services.
ADVM-10926: Attributes of realm 'string' in snapshot 'string' of mount point 'string' retrieved.
Cause: Attributes of realm in snapshot were retrieved.
Action: None
ADVM-10927: Failed to get all rules in snapshot 'string' of mount point 'string'.
Cause: Internal error.
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
ADVM-10928: Failed to get information of rule 'string' in snapshot 'string' of mount point 'string'.
Cause: Internal error.
Action: Contact Oracle Support Services.
ADVM-10929: Rule 'string' not found in snapshot 'string' of mount point 'string'.
Cause: Rule was not found in the snapshot.
Action: Ensure that the rule exists by executing 'acfsutil sec info -m <mount_point> -S <snapshot_name> -l'.
ADVM-10930: Failed to get all rule sets in snapshot 'string' of mount point 'string'.
Cause: Internal error.
Action: Contact Oracle Support Services.
ADVM-10931: Failed to get rules for rule set 'string' in snapshot 'string' of mount point 'string'.
Cause: Internal error.
Action: Contact Oracle Support Services.
ADVM-10932: Rule set 'string' not found in snapshot 'string' of mount point 'string'.
Cause: Rule set was not found in snapshot of mount point.
Action: Ensure that the rule set exists by executing 'acfsutil sec info -m <mount_point> -S <snapshot_name> -s'.
ADVM-10933: Failed to delete the read-only snapshot file 'string' from realm 'string'.
Cause: Security operations cannot be performed on a read-only snapshot file.
Action: None
ADVM-10934: Failed to delete the read-write snapshot file 'string' from realm 'string'.
Cause: Security operations cannot be performed on a read-write snapshot file.
Action: None
ADVM-10935: ACFS Security cannot be enabled or disabled because 'string' is a read-only snapshot
Cause: A request to enable or disable ACFS Security specified a read-only snapshot.
Action: None
ADVM-10936: ACFS Security is now disabled in snapshot 'string' of mount point 'string'.
Cause: Informational.
Action: None
ADVM-10937: ACFS Security is now enabled on realm 'string' in snapshot 'string' of mount point 'string'.
Cause: Informational.
Action: None
ADVM-10938: ACFS Security is now disabled on realm 'string' in snapshot 'string' of mount point 'string'.
Cause: Informational.
Action: None
ADVM-10939: ACFS Security is now enabled on realm 'string' in mount point 'string'.
Cause: Informational.
Action: None
ADVM-10940: ACFS Security is now disabled on realm 'string' in mount point 'string'.
Cause: Informational.
Action: None
ADVM-10941: Failed to create 'string' file on mount point 'string'
Cause: An attempt to create a file on the indicated mount point failed, most likely because the user lacked the requisite permission.
Action: Ensure that the user has the required permission and retry. Otherwise, contact Oracle Support Services.
ADVM-10942: Insufficient disk space on mount point 'string'
Cause: The requested operation failed because the file system was full.
Action: Resize the file system and retry.
ADVM-10945: ACFS Auditing source 'string' is already enabled on mount point 'string'.
Cause: Informational.
Action: None
ADVM-10946: ACFS Auditing source 'string' is already disabled on mount point 'string'.
Cause: Informational.
Action: None
ADVM-10947: Audit trail on mount point 'string' is marked as read.
Cause: Informational.
Action: None
ADVM-10948: Audit trail on mount point 'string' is archived.
Cause: Informational.
Action: None
ADVM-10949: ACFS Auditing has been initialized on the cluster with 'string' as the Oracle ACFS auditor OS group and 'string' as the Oracle ACFS audit manager OS group.
Cause: Informational.
Action: None
ADVM-10950: Audit trail archive for mount point 'string' is purged.
Cause: Informational.
Action: None
ADVM-10951: Current user does not have system administrative privileges to initialize auditing.
Cause: The user was not part of system administrators group.
Action: Run 'acfsutil audit init' as an OS user with administrative privileges.
ADVM-10952: Auditing already initialized; cannot reinitialize.
Cause: An attempt was made to initialize auditing after it was already initialized.
Action: None
ADVM-10953: Auditing is not initialized.
Cause: A command was issued which requires auditing to be intialized for the cluster, but auditing has not been initialized.
Action: Initialize auditing by reissuing 'acfsutil audit init' command.
ADVM-10954: Failed to enable auditing on mount point 'string'.
Cause: Internal error.
Action: Refer to audit log '<mount_point>/.Security/audit/audit-<host_name>.log'.
ADVM-10955: Failed to disable auditing on mount point 'string'.
Cause: Internal error.
Action: Refer to audit log '<mount_point>/.Security/audit/audit-<host_name>.log'.
ADVM-10956: Failed to enable auditing for realm 'string' on mount point 'string'.
Cause: Internal error.
Action: Refer to audit log '<mount_point>/.Security/audit/audit-<host_name>.log'.
ADVM-10957: Failed to disable auditing for realm 'string' on mount point 'string'.
Cause: Internal error.
Action: Refer to audit log '<mount_point>/.Security/audit/audit-<host_name>.log'.
ADVM-10958: Current user does not have privileges to run audit commands.
Cause: Command was executed as user who is not part of audit manager OS group or auditors OS group.
Action: Run command as user who is part of audit manager OS group or auditors OS group.
ADVM-10960: Failed to get audit information for the mount point 'string'.
Cause: Internal error.
Action: Contact Oracle Support Services.
ADVM-10961: Failed to get audit manager OS group.
Cause: Internal error.
Action: Contact Oracle Support Services.
ADVM-10962: Failed to get auditor OS group.
Cause: Internal error.
Action: Contact Oracle Support Services.
ADVM-10963: Auditing is not enabled on mount point 'string'.
Cause: A command was issued that requires auditing to be enabled at the file system level, but it is not enabled.
Action: Run 'acfsutil audit enable', and retry the command.
ADVM-10964: Failed to archive audit trail on mount point 'string'.
Cause: Internal error.
Action: Contact Oracle Support Services.
ADVM-10965: Failed to mark audit trail on mount point 'string' as read
Cause: Internal error.
Action: Contact Oracle Support Services.
ADVM-10966: Audit trail on mount point 'string' is already marked as read.
Cause: Audit trail was already marked as read on mount point.
Action: None
ADVM-10967: Audit trail on mount point 'string' not found.
Cause: An 'acfsutil audit' command was issued but auditing has not been initialized.
Action: Run 'acfsutil audit init' as an OS user with administrative privileges, then reissue the original command.
ADVM-10968: Failed to create audit trail XML file 'string' for mount point string.
Cause: Internal error.
Action: Contact Oracle Support Services.
ADVM-10969: Failed to purge audit trail archive file for mount point 'string'.
Cause: Internal error.
Action: Contact Oracle Support Services.
ADVM-10970: Failed to purge audit trail archive because it is not marked 'read' for mount point 'string'.
Cause: Audit trail was not yet marked as 'read' on mount point.
Action: Run 'acfsutil audit read' and retry the command.
ADVM-10971: Current user does not have privileges to run this audit command.
Cause: Command was executed as user who is not part of audit manager OS group.
Action: Run command as user who is part of audit manager OS group.
ADVM-10972: Failed to update audit managers and auditors group information in the driver; some of the subsequent audit related commands may fail.
Cause: Audit Managers and Auditors information was not communicated to the ACFS driver during mount. The mount command was successful but the subsequent audit commands will not work on this host until the problem is corrected.
Action: Contact Oracle Support Services.
ADVM-10973: The ADVM compatibility attribute for the diskgroup must be set to version 'string' to enable auditing on mount point 'string'.
Cause: A security adminstrator or audit manager or administrator attempted to enable auditing, but the 'COMPATIBLE.ADVM' attribute for the disk group had not been upgraded to a supported version.
Action: Use the ASMCA tool or the SQL ALTER DISKGROUP statement to upgrade the COMPATIBLE.ADVM attribute and enable auditing using the 'acfsutil audit enable' command.
ADVM-10974: Auditing cannot be enabled on mount point 'string', because ADVM compatibility is lower than 'string'.
Cause: A security adminstrator or system administrator attempted to enable auditing as part of 'acfsutil sec prepare' or 'acfsutil encr set' which was successful, but auditing could not be enabled because the 'compatible.advm attribute had not been upgraded to a supported version.
Action: Use the ASMCA tool or the SQL ALTER DISKGROUP statement to upgrade the COMPATIBLE.ADVM attribute and enable auditing using the 'acfsutil audit enable' command.
ADVM-10975: Failed to get audit information for realm 'string' on mount point 'string'.
Cause: Internal error.
Action: Contact Oracle Support Services.
ADVM-10976: Failed to create audit trail XML file because the old audit trail XML file exists for mount point 'string'.
Cause: A request to archive the audit trail found an existing audit trail XML file.
Action: Run 'acfsutil audit purge' and retry the command.
ADVM-10977: Auditing is enabled for realm 'string' on mount point 'string'.
Cause: Informational.
Action: None
ADVM-10978: Auditing is disabled for realm 'string' on mount point 'string'.
Cause: Informational.
Action: None
ADVM-10979: Cannot proceed because file system is not prepared for ACFS Security.
Cause: An attempt to enable or disable audit on Security source failed because the file system was not prepare for ACFS Security.
Action: Execute 'acfsutil sec prepare' to prepare ACFS Security on the file system and retry 'acfsutil audit' command.
ADVM-10980: Cannot proceed because file system is not set for ACFS Encryption.
Cause: An attempt to enable or disable audit on Encryption source failed because the file system was not set for ACFS Encryption.
Action: Execute 'acfsutil encr set' to set ACFS Encryption on the file system and retry 'acfsutil audit' command.
ADVM-10998: ACFS Audit not initialized
Cause: ACFS Audit was not initilized.
Action: Run 'acfsutil audit init' command.
ADVM-10999: Audit trail archive file on mount point 'string' was not found.
Cause: An 'acfsutil audit read' command was issued but the audit trail backup file did not exist.
Action: Run 'acfsutil audit archive' as an OS user with Audit Manager privileges, then reissue the original command.
ADVM-11000: ACFS Auditing is already initialized with different Audit Managers and Auditors group.
Cause: Values provided on the command line did not match those with which ACFS Auditing was initialized earlier.
Action: Run 'acfsutil audit init' command with the Audit Managers and Auditors group provided for the previous initialization.
ADVM-11001: Error in parsing command line arguments.
Cause: There was a syntax error is the command line arguments.
Action: Check the command line syntax and re-run the command again.
ADVM-11002: Error: a device name must be supplied with the -l option.
Cause: Either the -l option was not present in the command line or it had no argument.
Action: Make sure you run the command with the '-l device-name' option.
ADVM-11003: AIX ODM initialization failed, odmerr number
Cause: AIX ODM internal operation error.
Action: Internal error - contact Oracle Customer Support.
ADVM-11004: failed to lock AIX ODM database, odmerr number
Cause: The method could not lock the AIX ODM database.
Action: Check to see what other method has locked it.
ADVM-11005: failed to look up AIX ODM PdDv object class, odmerr number
Cause: The user may lack required permission or the entry may not exist.
Action: Ensure that the object exists and that the user has the required permission; otherwise, contact Oracle Customer Support.
ADVM-11006: failed to open AIX ODM CuDv object class, odmerr number
Cause: The user may lack required permission or the entry may not exist.
Action: Ensure that the object exists and that the user has the required permission; otherwise, contact Oracle Customer Support.
ADVM-11007: failed to add to AIX ODM CuDv object class, odmerr number
Cause: An attempt to add the device's entry to the ODM CuDv object class failed.
Action: Ensure the user has the required permission.
ADVM-11008: failed to close the AIX ODM CuDv object class, odmerr number
Cause: AIX ODM internal operation error.
Action: Contact Oracle Customer Support.
ADVM-11010: failed to look up AIX ODM CuDv object class, odmerr number
Cause: The user may lack required permission or the entry may not exist.
Action: Ensure that the object exists and that the user has the required permission; otherwise, contact Oracle Customer Support.
ADVM-11015: failed to load kernel extension string, errno number (string)
Cause: Loading the kernel extension into the kernel failed.
Action: Check the error message and resolve the error.
ADVM-11017: failed to configure kernel extension string, errno number (string)
Cause: Could not configure the device's driver in the kernel.
Action: Internal error - contact Oracle Customer Support.
ADVM-11018: failed to get a major number for device string
Cause: The method could not get a major number for the device.
Action: Internal error - contact Oracle Customer Support.
ADVM-11019: failed to get a minor number for device string
Cause: The method could not get a minor number for the device.
Action: Internal error - contact Oracle Customer Support.
ADVM-11022: failed to configure device string, errno number (string)
Cause: Attempt to configure the device's driver in the kernel got an error.
Action: Internal error - contact Oracle Customer Support.
ADVM-11024: failed to remove the old device file string, errno number (string)
Cause: The method failed to remove the device file.
Action: Ensure that the user has permission and no other application is still using the device.
ADVM-11026: failed to create new device file string, errno number (string)
Cause: The user may not have permission or a file with the same name already exists.
Action: Ensure that the file does not already exist and that the user has the required permission to create it.
ADVM-11028: failed to set permission of the new device file string, errno number (string)
Cause: The method failed to set permission of the device special file.
Action: Ensure the user has the required privilege.
ADVM-11030: failed to set group of the new device file string, errno number (string)
Cause: The method failed to set the owning group of the device special file.
Action: Ensure the user has the required privilege.
ADVM-11031: failed to open the ASMADMIN group file, errno number (string)
Cause: The method could not open the file containing the group to own the device.
Action: Ensure the installation completed successfully.
ADVM-11032: failed to read from the ASMADMIN group file, errno number (string)
Cause: The method could not read the file containing the group to own the device.
Action: Ensure the installation completed successfully.
ADVM-11034: failed to set device state to AVAILABLE, odmerr number
Cause: The method could not change the device's state.
Action: AIX ODM internal error - contact Oracle Customer Support.
ADVM-11036: No operation was performed because device state is string instead of DEFINED.
Cause: The method expected a DEFINED device state.
Action: AIX ODM internal error - contact Oracle Customer Support.
ADVM-11038: failed to unconfigure kernel extension string, errno number (string)
Cause: The method could not unconfigure the kernel extension.
Action: Internal error - contact Oracle Customer Support.
ADVM-11040: failed to unload kernel extension string, errno number (string)
Cause: The method could not unload the extension from kernel.
Action: Internal error - contact Oracle Customer Support.
ADVM-11044: no minor number was returned for device string
Cause: The operating system did not return a device minor number as requested.
Action: Internal error - contact Oracle Customer Support.
ADVM-11046: failed to set device state to DEFINED, odmerr number
Cause: The method failed to change the device's state.
Action: Contact Oracle Customer Support.
ADVM-11050: failed to delete attributes of device string, odmerr number
Cause: The method failed to remove the device's attributes from the AIX ODM CuAt object class.
Action: Internal AIX ODM error - contact Oracle Customer Support.
ADVM-11052: failed to delete customized object of device string, odmerr number
Cause: The method failed to remove the device's entry from the AIX ODM CuDv object class.
Action: Internal AIX ODM error - contact Oracle Customer Support.
ADVM-11053: failed to release major number for device string
Cause: The method failed to release the device's major number.
Action: Internal error - contact Oracle Customer Support.
ADVM-11055: failed to remove device special file string, errno number (string)
Cause: The method failed to remove the device special file.
Action: Check the error message and resolve it.
ADVM-11060: failed to unload kernel extension string
Cause: Could not unload the extension from kernel.
Action: Internal error - contact Oracle Customer Support.
ADVM-11061: failed to look up the group id for group string
Cause: The named group probably does not exist.
Action: Make sure the group exists in the /etc/group file.
ADVM-11062: failed to create directory string, errno number (string)
Cause: The directory could not be created.
Action: Check the permission of the base directory to make sure it is writeable.
ADVM-11063: failed to set permission on directory string, errno number (string)
Cause: The permission of the directory could not be changed.
Action: Make sure the user has permission to do so.
ADVM-11064: failed to set group on directory string, errno number (string)
Cause: The group of the directory could not be changed.
Action: Make sure the user has permission to do so.
ADVM-11065: invalid device minor number number
Cause: The device minor number being used is out of range.
Action: Contact Oracle Customer Support.
ADVM-11066: the ADVM driver is not loaded
Cause: The ADVM driver is expected to exist in the kernel but it does not.
Action: Load the ADVM driver and then try it again.
ADVM-11067: directory /dev/asm does not exist or is not accessible, errno number (string)
Cause: The ADVM driver probably has not been successfully loaded.
Action: Load the ADVM driver and then try it again.
ADVM-11068: The state of device string is unknown. No operation was performed.
Cause: Unknown.
Action: Contact Oracle Customer Support.
ADVM-11069: Error: device name is too long, exceeding 255 characters.
Cause: The chosen device name exceeds the limit of 255 characters.
Action: Use a device name that is shorter than the limit.