Action: n/a

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.

Action: Verify the ACFS driver is loaded and running.

Action: Review the command usage and retry the command providing valid input.

Action: Review the command usage and retry the command providing valid input.

Action: Contact Oracle Support Services.

Action: The most likely cause is a file permission problem.

Action: Correct the problem indicated by the other message(s). If the solution is not clear, contact Oracle Support Services.

Action: Correct the problem indicated by the other message(s). If the solution is not clear, contact Oracle Support Services.

Action: Correct the problem indicated by the other message(s). If the solution is not clear, contact Oracle Support Services.

Action: Correct the problem indicated by the other message(s). If the solution is not clear, contact Oracle Support Services.

Action: Make sure the file system is unmounted on all cluster nodes before running the file system checking utility.

Action: Ensure that a file system check is not being run on another node or by another user before retrying the command. If a file system check operation had been started and then aborted, use 'fsck -f' to repair the volume and then retry the command.

Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.

Action: Correct the problem indicated by the other message(s). If the solution is not clear, contact Oracle Support Services.

Action: Use the 'acfsdriverstate version' command to obtain additional version information and contact Oracle Support Services.

Action: Correct the problem indicated by the other message(s). If the solution is not clear, contact Oracle Support Services.

Action: Correct the problem indicated by the other message(s). If the solution is not clear, contact Oracle Support Services.

Action: Correct the problem indicated by the other message(s). If the solution is not clear, contact Oracle Support Services.

Action: Review the command usage and retry the command providing the correct number of arguments.

Action: Retry the command specifying an ADVM volume.

Action: Correct the problem indicated by the other message(s). If the solution is not clear, contact Oracle Support Services.

Action: Correct the problem indicated by the other message(s). If the solution is not clear, contact Oracle Support Services.

Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.

Action: Correct the problem indicated by the other message(s). If the solution is not clear, contact Oracle Support Services.

Action: Correct the problem indicated by the other message(s). If the solution is not clear, contact Oracle Support Services.

Action: Correct the problem indicated by the other message(s). If the solution is not clear, contact Oracle Support Services.

Action: Correct the problem indicated by the other message(s). If the solution is not clear, contact Oracle Support Services.

Action: Select a different volume and retry the mount operation.

Action: Correct the problem indicated by the other message(s). If the solution is not clear, contact Oracle Support Services.

Action: Review the command usage and retry the command providing valid options.

Action: Review the command usage and retry the command providing the needed argument.

Action: Review the command usage and retry the command providing valid input.

Action: Review the command usage and retry the command providing the needed argument.

Action: Review the command usage and retry the command providing valid options.

Action: Review the command usage and retry the command providing valid input.

Action: Review the command usage and retry the command providing valid input.

Action: Review the command usage and retry the command providing valid input.

Action: Review the command usage and retry the command providing valid input.

Action: Review the command usage and retry the command providing valid input.

Action: Review the command usage and retry the command providing the desired option.

Action: Review the command usage and retry the command providing the correct option syntax.

Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.

Action: Run fsck (Unix or Linux) or acfschkdsk.exe (Windows) as soon as possible to fix the metadata inconsistency.

Action: Verify the driver is loaded and running. Also, verify that the ASM instance is accessible.

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.

Action: Run the ACFS Fixer to resolve the metadata inconsistency and then retry the operation.

Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.

Action: None

Action: Ensure that the required group exists, then re-run the command.

Action: Correct the problem indicated by the other message(s). If the solution is not clear, contact Oracle Support Services.

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.

Action: Review the command usage and retry the command providing valid options.

Action: Correct the problem indicated by the other message(s). If the cause of the problem is unclear, contact Oracle Support Services.

Action: Run ocrcheck to verify the Oracle Registry is working properly.

Action: Use acfsutil registry to verify the mount key exists in the Oracle Registry.

Action: Run ocrcheck to verify the Oracle Registry is working properly. Report to Oracle Support Services.

Action: Run ocrcheck to verify the Oracle Registry is working properly. Report to Oracle Support Services.

Action: Verify the Oracle Registry is accessible. If it is not accessible and the cause is unclear, report this error to Oracle Support Services.

Action: Report this error to Oracle Support Services.

Action: Use acfsutil registry to ensure the mount entry exists in the Oracle Registry.

Action: View the mount entries in the Oracle Registry using "acfsutil registry" and remove any dependent mount entries before retrying this operation.

Action: Verify the Oracle Registry is accessible and that command is being run from a properly authorized user ID.

Action: Report this error to Oracle Support Services.

Action: Run ocrcheck to verify that Oracle Registry is working properly. If problem persists, report to Oracle Support Services.

Action: Run ocrcheck to verify the Oracle Registry is working properly. If problem persists, report to Oracle Support Services.

Action: Run ocrcheck to verify that Oracle Registry is working properly. If problem persists, report to Oracle Support Services.

Action: Run ocrcheck to verify that Oracle Registry is working properly. If problem persists, report to Oracle Support Services.

Action: Run ocrcheck to verify that Oracle Registry is working properly. If problem persists, report to Oracle Support Services.

Action: Run the ACFS Fixer to resolve the metadata inconsistency and then retry the operation.

Action: Verify the volume exists on this node and that it is accessible.

Action: Run ocrcheck to verify the Oracle Registry is working properly. Examine the appended error message from the Oracle Registry service.

Action: Examine the appended error message from the Oracle Registry.

Action: Examine the appended error message from the Oracle Registry. Run ocrcheck to verify the Oracle Registry is working properly.

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.

Action: Evaluate the attached SCLS error message. Run ocrcheck to verify the Oracle Registry is functioning correctly.

Action: Evaluate the attached error message to determine why the current user name could not obtained from the operating system.

Action: Examine the appended error message from the Oracle Registry. Run ocrcheck to verify the Oracle Registry is working properly.

Action: Examine the appended error message from the Oracle Registry.

Action: Run ocrcheck to verify the registry service is working properly.

Action: Contact Oracle.

Action: Run ocrcheck to verify OCR is working properly.

Action: Run ocrcheck -local to verify the OLR is working properly.

Action: Run ocrcheck to verify the registry is working properly.

Action: Run ocrcheck to verify the Oracle registry service.

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.

Action: Review the command usage and retry the command providing valid options.

Action: None

Action: Use a system with the same Endian as the system which created the file system.

Action: None

Action: Verify the mount point is an ACFS mount point and it is not offline.

Action: Provide an existing mount point on the base site.

Action: Provide an existing mount point with an empty file system on the target site.

Action: Verify the path was entered correctly, or use a different path.

Action: Provide a valid ACFS mount point.

Action: Contact Oracle Support Services.

Action: Select a size that is less than or equal to the volume size and retry the ACFS format command.

Action: Select a larger volume and retry.

Action: Correct the problem indicated by the other messages. If the solution is not clear, contact Oracle Support Services.

Action: This message is accompanied by another error message. Respond as indicated for that message."

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.

Action: Correct the problem indicated by the other message(s). If the cause of the problem is unclear, contact Oracle Support Services.

Action: Correct the problem described in the accompanying messages if possible and retry the command. If the solution is not clear, contact Oracle Support Services.

Action: Verify the volume associated with the file system is enabled and online before retrying.

Action: Correct the problem described in the accompanying messages if possible and retry the command. If the solution is not clear, contact Oracle Support Services.

Action: Verify the intended volume and reissue the format command with the force flag to overwrite the existing ACFS file system.

Action: Verify the intended volume and reissue the format command with the force flag to overwrite the existing ACFS file system.

Action: Correct the problem indicated by the other message(s). If the solution is not clear, contact Oracle Support Services.

Action: Correct the problem described in the accompanying messages if possible and retry the command. If the solution is not clear, contact Oracle Support Services.

Action: Retry the command (mkfs on Unix or Linux or acfsformat.exe on Windows) supplying a name with length less than or equal to the indicated maximum.

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.

Action: Dismount the ACFS file system with acfsdismount and retry the command.

Action: Dismount the non-ACFS file system with 'advmutil dismount' and retry the command.

Action: Retry the command (mkfs on Unix or Linux or acfsformat.exe on Windows) supplying a name with length less than or equal to the indicated maximum.

Action: Correct the problem described in the accompanying messages if possible and retry the command. If the solution is not clear, contact Oracle Support Services.

Action: Correct the problem described in the accompanying messages if possible and retry the command. If the solution is not clear, contact Oracle Support Services.

Action: Retry the command supplying a primary volume and accelerator volume that have the same storage type.

Action: Correct the problem indicated by the other message(s). If the cause of the problem is unclear, contact Oracle Support Services.

Action: Correct the problem indicated by the other message(s). If the cause of the problem is unclear, contact Oracle Support Services.

Action: Correct the problem indicated by the other message(s). If the cause of the problem is unclear, contact Oracle Support Services.

Action: Correct the problem indicated by the other message(s). If the cause of the problem is unclear, contact Oracle Support Services.

Action: Correct the problem indicated by the other message(s). If the cause of the problem is unclear, contact Oracle Support Services.

Action: Correct the problem indicated by the other message(s). If the cause of the problem is unclear, contact Oracle Support Services.

Action: Correct the problem indicated by the other message(s). If the cause of the problem is unclear, contact Oracle Support Services.

Action: Correct the problem indicated by the other message(s). If the cause of the problem is unclear, contact Oracle Support Services.

Action: Correct the problem indicated by the other message(s). If the cause of the problem is unclear, contact Oracle Support Services.

Action: Correct the problem indicated by the other message(s). If the cause of the problem is unclear, contact Oracle Support Services.

Action: Correct the problem indicated by the other message(s). If the cause of the problem is unclear, contact Oracle Support Services.

Action: Correct the problem indicated by the other message(s). If the cause of the problem is unclear, contact Oracle Support Services.

Action: Correct the problem indicated by the other message(s). If the cause of the problem is unclear, contact Oracle Support Services.

Action: Correct the problem indicated by the other message(s). If the cause of the problem is unclear, contact Oracle Support Services.

Action: Correct the problem indicated by the other message(s). If the cause of the problem is unclear, contact Oracle Support Services.

Action: Retry the command with an ADVM volume or, if the volume is a local volume, retry the command with the -l option.

Action: Correct the problem described in the accompanying messages if possible and retry the command. If the solution is not clear, contact Oracle Support Services.

Action: Retry the command (mkfs on Unix or Linux or acfsformat.exe on Windows) supplying a volume path with length less than or equal to the indicated maximum.

Action: Specify a metadata block size of 4096 or take the default. File system creation sets the metadata block size to the primary volume's logical sector size by default.

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.

Action: No action required. A supported block size will be used.

Action: Select an accelerator volume name with length less than or equal to the maximum length displayed in the message and retry the command.

Action: Dismount the ACFS file system with acfsdismount and retry the command.

Action: Dismount the non-ACFS file system with 'advmutil dismount' and retry the command.

Action: Use the Oracle ASM Configuration Assistant (ASMCA) tool or the SQL statement ALTER DISKGROUP to upgrade COMPATIBLE.ADVM attribute.

Action: Choose a different volume for the accelerator and retry the command.

Action: Select a larger accelerator volume and retry the command.

Action: Select an unused device, or use srvctl to modify the association for this device and retry the file system creation.

Action: Select devices that have the same logical sector size for the primary and accelerator volumes or specify the 'i 4096' switch.

Action: Retry the command without the -c option.

Action: Use the Oracle ASM Configuration Assistant (ASMCA) tool or the SQL ALTER DISKGROUP statement to upgrade the disk group compatibility (COMPATIBLE.ADVM attribute) to the specified version and then re-issue the original command. If the disk group compatibility cannot be upgraded, update the ACFS compatibility using the 'acfsutil compat set' command and then re-issue the original command.

Action: Select devices with a 512-byte logical sector size when creating a file system using the 'i 512' format switch. Use the command 'advmutil volstats' to verify that the volume's sector size is 512 bytes before formatting the file system. Alternatively, format the file system without the 'i 512' switch, allowing Oracle ACFS to create a 4096-byte metadata block size format.

Action: Use the Oracle ASM Configuration Assistant (ASMCA) tool or the SQL ALTER DISKGROUP statement to upgrade the disk group compatibility (COMPATIBLE.ADVM attribute) to the specified version and then re-issue the original command. If the disk group compatibility cannot be upgraded, update the ACFS compatibility using the 'acfsutil compat set' command and then re-issue the original command.

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.

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.

Action: Verify the volume exists on this node and that it is accessible.

Action: Verify the mount point and volume both exist and are accessible before retrying the mount command.

Action: Verify the mount point exists and is accessible before retrying the mount command.

Action: Select an unused directory and retry the mount operation.

Action: Verify the ASM instance is operational and the volume is enabled and accessible before retrying the mount command.

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.

Action: Retry the mount operation supplying an option list of length less than or equal to the indicated maximum.

Action: Retry the mount operation supplying a total length less than or equal to the indicated maximum.

Action: Run crs_stat to verify CSS is working properly.

Action: Run crs_stat to verify CSS is working properly.

Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.

Action: Retry the mount on a system that matches the indicated system type.

Action: Use a system with the same endianness as the system which created the file system.

Action: Retry the mount command (acfsmountvol.exe on Windows) supplying a path with length less than or equal to the indicated maximum.

Action: Retry the operation, specifying a valid ACFS mount point.

Action: Retry the mount command (acfsmountvol.exe on Windows) supplying a volume name with length less than or equal to the indicated maximum.

Action: Select a different volume and retry the mount operation.

Action: Run acfschkdsk.exe as soon as possible to fix the metadata inconsistency, and then retry the acfsmountvol.exe command.

Action: Select a different mount point and retry the mount operation.

Action: Examine the system event log for more detail.

Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.

Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.

Action: Verify the ASM instance is operational and the volume is enabled and accessible before retrying.

Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.

Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.

Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.

Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.

Action: Use the 'acfsdriverstate version' command to obtain the version of the loaded ACFS driver and contact Oracle Support Services.

Action: Run acfschkdsk.exe as soon as possible to fix the metadata inconsistency.

Action: Run crs_stat to verify health of CSS.

Action: Run crs_stat to verify health of CSS.

Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.

Action: None

Action: Analyze the error messages that precede this message.

Action: Verify the node listed in the entry is a member of the CSS cluster.

Action: None

Action: None

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.

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.

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.

Action: Correct the error indicated by the accompanying messages.

Action: Verify the volume specified.

Action: Correct the problem indicated by the other messages and retry the mount command.

Action: Correct the problem identified by the other messages. If the cause is unclear, contact Oracle Support Services.

Action: None. This state will not have any repercussions and it will be remedied automatically during the next restart.

Action: Correct the problem by resizing the ADVM volume and then retry the mount command.

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.

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.

Action: Reduce the load activity on the system and retry the mount command.

Action: Run command 'fsck -t acfs' as soon as possible to fix the metadata inconsistency and then retry the mount command.

Action: Use the 'acfsdriverstate version' command to obtain the version of the loaded ACFS driver and contact Oracle Support Services.

Action: Use the 'acfsdriverstate version' command to obtain the version of the loaded ACFS driver and contact Oracle Support Services.

Action: Retry the command with the addition of the -o local option.

Action: Retry the command without the -o local option.

Action: Verify the mount point or file is accessible before retrying.

Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.

Action: Select a size that is smaller than the size of the file system and retry.

Action: Specify a primary volume size of 200MB or more

Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.

Action: Select a primary volume size that is greater than the size indicated in the message and retry the command.

Action: Select a primary volume size that is less than the size indicated in the message and retry the command.

Action: If the file system has been grown four or more times, running the ACFS Fixer may allow future volume expansions.

Action: Try again later. Check the ASM alert log if the issue persists.

Action: Select a volume name with length less than or equal to the indicated maximum length.

Action: Verify the volume is not mounted on any node in the cluster before retrying.

Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.

Action: Retry the command with a valid IP address.

Action: Retry the resize operation when online fsck is not running.

Action: Retry the operation using an ACFS file system that has not been mounted with -o local.

Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.

Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.

Action: Retry the command specifying one of OKS, OFS, and AVD.

Action: Retry the command specifying one of OKS, OFS, and AVD.

Action: Retry the command specifying the debug level or context.

Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.

Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.

Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.

Action: If a file exists by the same name as the file specified, verify that this is a file that can be overwritten.

Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.

Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.

Action: None

Action: Retry the command with a file or directory that is part of an ACFS file system.

Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.

Action: Verify the ACFS driver is loaded and running and retry the command.

Action: Dismount all ACFS file systems and retry the command.

Action: Verify the ACFS driver is loaded and running and retry the command.

Action: Issue the command again using a shorter snapshot name.

Action: Verify the mount point exists and is accessible before retrying the snap command.

Action: Retry the command with an ACFS mount point.

Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.

Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.

Action: Reduce the number of snapshots for the associated file system using 'acfsutil snap delete' and then retry the acfsutil snap command.

Action: Retry the acfsutil snap command specifying a different name.

Action: Retry the acfsutil snap command with the correct name.

Action: Use lsof or a similar tool to find the processes with open files. No files can be open in the snapshot for the snapshot delete operation to succeed.

Action: Run the ACFS Fixer to free the storage.

Action: Retry the acfsutil snap command specifying a valid snapshot name.

Action: Examine the Alert logs on the other nodes, resolve the indicated problems, and then retry the operation.

Action: Retry the command from an account with the required privilege.

Action: Review the command usage and retry the command providing valid input.

Action: Verify the driver is loaded and running.

Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.

Action: None

Action: Verify the correct value of the parameter.

Action: Verify the correctness of the parameter name.

Action: If the configuration file exists, verify the file can be opened.

Action: If the configuration file exists, verify the file is accessible.

Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.

Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.

Action: Retry the command with one set of operations.

Action: Retry the command with one set of operations.

Action: Retry the command with an ADVM volume.

Action: Run ocrcheck to verify the Oracle Registry is working properly. Analyze the appended Oracle Registry service error message.

Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation. If another registration is using this device or mountpoint, remove the existing registration before retrying the operation.

Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.

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.

Action: Run ocrcheck to verify the Oracle Registry service is working properly. If the cause of the problem is unclear, contact Oracle Support Services.

Action: Run crs_stat to verify health of CSS.

Action: Verify that the specified host is a member of this cluster.

Action: Contact Oracle Support Services.

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).

Action: Run ocrcheck to verify the Oracle Registry service is working properly. Verify acfsutil is executed with operating system administrator privileges.

Action: Run ocrcheck to verify the Oracle Registry service is working properly.

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.

Action: Run ocrcheck to verify the Oracle Registry is working properly.

Action: Run ocrcheck to verify the Oracle Registry is working properly.

Action: Run ocrcheck to verify the Oracle Registry is working properly.

Action: Run ocrcheck to verify the Oracle Registry is working properly.

Action: Run ocrcheck to verify the Oracle Registry is working properly.

Action: Check the instance alert log for the maximum size of the ADVM volume and retry the resize operation, specifying a smaller volume size.

Action: If the new device is meant to replace an old device on this mount point, unmount the old device and then retry the command.

Action: Correct the problem identified by the other message(s). If the cause is unclear, contact Oracle Support Services.

Action: Correct the problem indicated by the other message(s). If the cause of the problem is unclear, contact Oracle Support Services.

Action: Verify the mount point is registered with CRS using the 'acfsutil registry device' commands.

Action: Verify the volume is registered with CRS using the 'acfsutil registry device' commands.

Action: Retry acfsutil registry with volume name.

Action: Run ocrcheck to verify the Oracle Registry is working properly.

Action: Run ocrcheck to verify the Oracle Registry is working properly.

Action: Run ocrcheck to verify the Oracle Registry is working properly.

Action: Check the diskgroup is mounted and the specified volume is enabled.

Action: Check the attached error. If not serviceable, contact Oracle.

Action: Run "acfsutil registry" to list out the available ACFS mount points.

Action: Verify the volume exists in the Oracle Registry using the acfsutil registry command.

Action: Re-initializing the ACFS mount point group ownership in the Oracle Registry is not supported.

Action: Re-enter a number other than 0 or -1.

Action: Correct the problem indicated by the other message(s). If the cause of the problem is unclear, contact Oracle Support Services.

Action: Try the command again. If the problem persists, contact Oracle Support Services.

Action: None. There is no pathname associated with this ACFS file identifier.

Action: Verify that the correct ACFS file identifier and mountpoint were specified.

Action: Verify that the correct ACFS file identifier and mountpoint were specified.

Action: Report this error to Oracle Support Services.

Action: The acfsutil info acfs command requires that the input be a mount point.

Action: The acfsutil size command requires that the input be a mount point or a file.

Action: None

Action: Reissue the resize command.

Action: Remove the file system resource from CRS or continue to use CRS to manage the file system.

Action: Verify the ACFS registry state ('crsctl stat res ora.registry.acfs -p')

Action: Verify the ACFS registry state ('crsctl stat res ora.registry.acfs -p')

Action: Contact Oracle Support Services.

Action: Check the log file to see the reason of failure.

Action: Log file size has to be bigger than or equal to the minimum size.

Action: Check the ASM alert logs, address ASM issues if any, and retry the resize. If ASM rebalance is running it may release sufficient space by completion to allow a retry of the resize to succeed. Monitor V$ASM_DISK.FREE_MB view, if desired, to track free storage and retry the resize if sufficient storage becomes available. Otherwise, retry the resize after using ASM commands to increase the free space or retry, specifying a smaller quantity.

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.

Action: Check the ASM alert log.

Action: Use the Oracle ASM Configuration Assistant (ASMCA) tool or the SQL ALTER DISKGROUP statement to upgrade the disk group compatibility (COMPATIBLE.ADVM attribute) to the specified version and then re-issue the original command. If the disk group compatibility cannot be upgraded, update the ACFS compatibility using the 'acfsutil compat set' command and then re-issue the original command.

Action: Retry the command with a log file size that is smaller than the maximum size.

Action: Complete the rolling migration and then delete the snapshot.

Action: Complete the rolling migration and then create the snapshot.

Action: Correct the problem indicated by the other message(s). If the solution is not clear, contact Oracle Support Services.

Action: Verify the correctness of the device name and retry the command.

Action: Correct the problem indicated by the other message(s). If the solution is not clear, contact Oracle Support Services.

Action: Specify a file offset within the actual or allocated size of the file. Use 'acfsutil info file filename' to see those values.

Action: None

Action: To force deletion of the snapshot, re-try the command with the -R option.

Action: To delete the snapshot, re-try the command without the -R option.

Action: Terminate replication and retry the command.

Action: Use a valid 'acfsutil snap' command combination. Valid commands are 'acfsutil snap create', 'acfsutil snap delete', and 'acfsutil snap info'

Action: None

Action: None

Action: Use the Oracle ASM Configuration Assistant (ASMCA) tool or the SQL ALTER DISKGROUP statement to upgrade the disk group compatibility (COMPATIBLE.ADVM attribute) to the specified version and then re-issue the original command. If the disk group compatibility cannot be upgraded, update the ACFS compatibility using the 'acfsutil compat set' command and then re-issue the original command.

Action: Remove either the -r or -w option from the 'acfsutil snap convert' command.

Action: Upgrade operating system to Windows Server 2008 R2 or use the 'acfsutil snap create' command to create a read-only snapshot.

Action: Delete a snapshot before creating a new one.

Action: Delete all snapshots associated with the file system and retry the command.

Action: Use the Oracle ASM Configuration Assistant (ASMCA) tool or the SQL ALTER DISKGROUP statement to upgrade the disk group compatibility (COMPATIBLE.ADVM attribute) to the specified version and then re-issue the original command. If the disk group compatibility cannot be upgraded, update the ACFS compatibility using the 'acfsutil compat set' command and then re-issue the original command.

Action: Use the Oracle ASM Configuration Assistant (ASMCA) tool or the SQL ALTER DISKGROUP statement to upgrade the disk group compatibility (COMPATIBLE.ADVM attribute) to the specified version and then re-issue the original command. If the disk group compatibility cannot be upgraded, update the ACFS compatibility using the 'acfsutil compat set' command and then re-issue the original command.

Action: Correct the problem identified by the other messages. If the cause is unclear, contact Oracle Support Services.

Action: Correct the problem identified by the other messages. If the cause is unclear, contact Oracle Support Services.

Action: Correct the problem identified by the other messages. If the cause is unclear, contact Oracle Support Services.

Action: Retry the command specifying a value between -2^63+1 and 2^63-1. 03245 is obsolete - see 3249.

Action: Correct the problems indicated by the other messages. If the cause of the problems is unclear, contact Oracle Support Services.

Action: Ensure that the primary volume has an associated accelerator volume before attempting replacement.

Action: Ensure that the specified volume is a primary volume with an associated accelerator volume before attempting replacement.

Action: Retry the 'acfsutil accel replace' command specifying a volume at least as large as the volume to be replaced.

Action: Ensure that an accelerator operation is not being run on another node or by another user before attempting to check this file system again. If an accelerator change operation had been started and then aborted, use 'fsck -f' to repair the volume. If the operation was interrupted, run it again with the same arguments.

Action: Use the Oracle ASM Configuration Assistant (ASMCA) tool or the SQL ALTER DISKGROUP statement to upgrade the disk group compatibility (COMPATIBLE.ADVM attribute) to the specified version and then re-issue the original command. If the disk group compatibility cannot be upgraded, update the ACFS compatibility using the 'acfsutil compat set' command and then re-issue the original command.

Action: Address errors in the accompanying error messages and run 'acfsutil accel replace' with the same arguments on to render the primary volume mountable. The accelerator replace operation should then be complete.

Action: The issued 'acfsutil accel replace' command should have finished an incomplete accelerator replace operation if one existed. Otherwise the file system should remain unchanged. No further action is necessary.

Action: Ensure that an accelerator operation is not being run on another node or by another user. If an accelerator operation had been started and then aborted, use 'fsck.acfs -f' to repair the primary volume. If an accelerator operation was interrupted, reissue the command with the same arguments to complete it.

Action: Reissue the request specifying a different volume not containing an existing file system or being used as an accelerator. To use the indicated volume, evidence of its prior use containing a file system or as an accelerator volume must first be removed.

Action: Select a device that has the same logical sector size as the existing accelerator volume and retry the operation.

Action: Use the Oracle ASM Configuration Assistant (ASMCA) tool or the SQL ALTER DISKGROUP statement to upgrade the disk group compatibility (COMPATIBLE.ADVM attribute) to the specified version and then re-issue the original command. If the disk group compatibility cannot be upgraded, update the ACFS compatibility using the 'acfsutil compat set' command and then re-issue the original command.

Action: Reissue the request specifying a different primary volume containing an existing ACFS file system that has an accompanying accelerator volume.

Action: Ensure that an accelerator operation is not being run on another node or by another user before retrying the mount operation. If an accelerator operation had been started and then aborted, use 'fsck.acfs -f' to repair the primary volume. If an accelerator operation was interrupted, reissue the command with the same arguments to complete it.

Action: Use the 'acfsutil snap quota' to set quota for a snapshot created from a file system whose compatibility level is at least 12.2.0.0.0

Action: None

Action: None

Action: Examine the accompanying CRS error messages, address issues reported and retry.

Action: The issued 'acfsutil accel replace' command attempted to complete the specified accelerator replace operation. No further action is necessary if this message is not accompanied by failure messages.

Action: Reissue the request specifying a different primary volume that contains a valid ACFS file system configured with an accompanying accelerator volume. Issue 'fsck' on the primary volume for more detail on its current state.

Action: Retry the operation. Alternatively, issue the following commands on each cluster node: 'acfsutil log -r 500M; acfsutil log -p ofs -l 5' run the workload that caused the problem wait for two or three minutes 'acfsutil log -r 10M; acfsutil log -p ofs -l 2'

Action: Retry the operation. Alternatively, issue the command on each cluster node: 'acfsutil log -r 10M; acfsutil log -p ofs -l 2'

Action: Re-issue the 'acfsutil log' command with only the desired option. With -o, the log files will be generated in the persistent log directory in the form yymmddhhmmss.log. With -f the specified name will be used.

Action: Re-issue the 'acfsutil log' command with only the desired option. With -o, only log file size, log level and product name may be specified.

Action: List the CRS resources to verify that the volume resource for the indicated device exists and is online and retry.

Action: Examine the file system resource attributes, ensure that the primary and accelerator resources are correct and retry.

Action: No action necessary.

Action: Use the ASMCA tool or the SQL ALTER DISKGROUP statement to upgrade the disk group compatibility (COMPATIBLE.ADVM attribute) to the specified version and then re-issue the original 'acfsutil snap link' command. If the disk group compatibility cannot be upgraded, update the ACFS compatibility level using the 'acfsutil compat set' command and then re-issue the original 'acfsutil snap link' command.

Action: Use the 'acfsutil snap info' command to see the existing snapshot link for this snapshot. Before creating a new snapshot link, use the 'acfsutil snap link -d' command to delete the existing link for the snapshot.

Action: Retry the command while logged in as a user with resource ACL access.

Action: Retry the command, specifying only valid options.

Action: Ensure that the Grid Infrastructure has completed an upgrade to the indicated version or higher and then re-issue the command.

Action: Read the accompanying messages, correct the issues identified there, and then retry the operation.

Action: Read the accompanying messages, correct the issues identified there, and then retry the operation.

Action: Complete the rolling migration and then retry the command.

Action: Verify memory or storage resources are sufficient.

Action: Verify memory or storage resources are sufficient.

Action: Change tag name to use valid characters or shorten the tag name.

Action: Remove the -t or -r arguments from the ofsutil tag info command.

Action: Verify that the mount point exists and is accessible before retrying the tag info command.

Action: Verify there is sufficient memory resources available.

Action: Verify the tag name to unset is correct.

Action: Use the Oracle ASM Configuration Assistant (ASMCA) tool or the SQL ALTER DISKGROUP statement to upgrade the disk group compatibility (COMPATIBLE.ADVM attribute) to the specified version and then re-issue the original command. If the disk group compatibility cannot be upgraded, update the ACFS compatibility using the 'acfsutil compat set' command and then re-issue the original command.

Action: Remove the non-ACFS path name from the 'acfsutil tag' command.

Action: None

Action: Verify that the file system is online and that the ADVM/ACFS drivers are loaded and running.

Action: Select an interval that is less than or equal to 2592000 seconds and retry "acfsutil info fs -s".

Action: Select a total count that is less than or equal to 2^63-1 and retry "acfsutil info fs -s".

Action: Provide a positive integer for the statistics interval.

Action: Remove any unused tags on this file and try the command again.

Action: Choose another tag name which is not reserved.

Action: None

Action: None

Action: Use the Oracle ASM Configuration Assistant (ASMCA) tool or the SQL ALTER DISKGROUP statement to upgrade the disk group compatibility (COMPATIBLE.ADVM attribute) to the specified version and then re-issue the original command. If the disk group compatibility cannot be upgraded, update the ACFS compatibility using the 'acfsutil compat set' command and then re-issue the original command.

Action: Use the Oracle ASM Configuration Assistant (ASMCA) tool or the SQL ALTER DISKGROUP statement to upgrade the disk group compatibility (COMPATIBLE.ADVM attribute) to the specified version and then re-issue the original command. If the disk group compatibility cannot be upgraded, update the ACFS compatibility using the 'acfsutil compat set' command and then re-issue the original command.

Action: To use the 'c' option, add the 't' option to specify a tag.

Action: Correct the problem indicated by the other message(s). If the cause of the problem is unclear, contact Oracle Support Services.

Action: Reissue the request specifying a single file system or omitting the repetition interval.

Action: Specify an accelerator volume size of 256MB or more.

Action: Correct the problem identified by the other messages. If the cause is unclear, contact Oracle Support Services.

Action: Reissue the request specifying a single file system or omitting the repetition interval.

Action: Retry the command specifying either the -o option for individual items or the -s or -s and -d for statistics.

Action: Retry the command with both -s and -d options.

Action: Retry the command specifying either the -s option for statistics or the -f option for fragmentation.

Action: Retry the command specifying either the -f option for fragmentation or the -o option for individual items.

Action: Retry the command with both -f and -v options.

Action: Retry the command with a positive integer for the statistics count.

Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation. If the resolution is not clear or the problem persists, contact Oracle Support Services.

Action: The Oracle Kernel Services (OKS) persistent log provides more detailed failure information. Resolve the indicated problems, and then retry the operation. If the resolution is not clear or the problem persists, contact Oracle Support Services.

Action: Review the command usage and retry the command providing valid input.

Action: Respond Y(yes) to proceed or N(no) to cancel.

Action: Respond Y(yes) to proceed or N(no) to cancel.

Action: Retry the operation after removing the target files or correcting the permissions.

Action: Execute the ACFS mount command, followed by the ACFS dismount command on any node of the cluster. After that, retry the add operation. If the cause of the problems is unclear, contact Oracle Support Services.

Action: Correct the problems indicated by the other messages. If the cause of the problems is unclear, contact Oracle Support Services.

Action: Use the Oracle ASM Configuration Assistant (ASMCA) tool or the SQL ALTER DISKGROUP statement to upgrade the disk group compatibility (COMPATIBLE.ADVM attribute) to the indicated version and then re-issue the original command. If the disk group compatibility cannot be upgraded, update the ACFS compatibility using the 'acfsutil compat set' command and then re-issue the original command.

Action: The issued 'acfsutil accel add' command attempted to complete the previous accelerator add operation. No further action is necessary if this message was not accompanied by failure messages.

Action: Address errors in the accompanying error messages and run 'acfsutil accel add' with the same arguments to render the primary volume mountable. The accelerator add operation should then be complete.

Action: Before attempting to add an accelerator volume ensure that the primary does not have one. If the cause of the problem is unclear, contact Oracle Support Services.

Action: Correct the problem indicated by the other messages. If the cause of the problem is unclear, contact Oracle Support Services.

Action: Correct the problem described in the accompanying messages if possible or run fsck (Unix or Linux) or acfschkdsk.exe (Windows).

Action: Correct the problem described in the accompanying messages if possible or run fsck (Unix or Linux) or acfschkdsk.exe (Windows).

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.

Action: Do not use any other options with the 'query' option.

Action: Specify a value equal to or greater than the minimum size and equal to or less than the maximum size.

Action: Enter an interval value equal to or greater than the minimum.

Action: Enter a valid high water level value.

Action: Enter a valid low water level value.

Action: None. Informational.

Action: Enter a value equal to or greater than the minimum or equal to or less than the maximum size.

Action: Specify a value equal to or greater than the minimum and equal to or less than the maximum.

Action: Specify a valid Grid infrastructure home.

Action: None. Informational.

Action: None. Informational.

Action: None. Informational.

Action: Start the log with 'acfsutil plogconfig -d gridhome'.

Action: Specify the directory name in the form of an absolute path. On Windows, the absolute path includes the drive letter.

Action: Correct the problem indicated by the other message(s). If the solution is not clear, contact Oracle Support Services.

Action: None

Action: Do not use any other options with the 'terminate' option.

Action: Retry the acfsutil snap link command with the correct name.

Action: Retry the acfsutil snap link command specifying a valid snapshot link name.

Action: Complete the rolling migration and then retry the command.

Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.

Action: None

Action: Enter an interval value equal to or less than the maximum.

Action: If a symbolic link is desired, delete the link target and its contents and reissue the command.

Action: Enter a node local location for the Oracle Kernel Services (OKS) log.

Action: Start the log with 'acfsutil plogconfig -d [log_dir]'.

Action: Either delete the file or choose another directory name.

Action: Retry the command using a text string shorter than the indicated maximum size.

Action: Check the Oracle Kernel Services (OKS) log for details, correct the error, and retry command.

Action: Retry the acfsutil snap link command after terminating replication.

Action: Retry the acfsutil snap link command with an allowed path.

Action: Retry the acfsutil snap link command with a different path.

Action: First disable the plug-in then retry the command.

Action: Enable the plug-in and then retry the command.

Action: Correct the problem indicated by the other message(s). If the solution is not clear, contact Oracle Support Services.

Action: Enter a valid metric type from the following list: acfsmetric1, acfsmetric2

Action: Enter a valid interval between 1 and 3600 seconds.

Action: Correct the problem indicated by the other message(s). If the solution is not clear, contact Oracle Support Services.

Action: Try the command again. If the problem persists, contact Oracle Support Services.

Action: Enable plug-in with fewer tags.

Action: Try the command again. If the problem persists, contact Oracle Support Services.

Action: Enter a valid metric type from the following list: "acfsmetric1"

Action: Examine the accompanying error messages and respond accordingly. If the solution is not clear, contact Oracle Support Services.

Action: Examine the accompanying error messages and respond accordingly. If the solution is not clear, contact Oracle Support Services.

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.

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.

Action: Examine the log file manually and, if a single line is corrupted, remove that line and re-issue the command. For systemic corruption, log file recovery may not be possible.

Action: Retry the command using a bigger auto-resize increment.

Action: Ensure that your compatible.advm setting allows auto-resize and then re-issue the command.

Action: Specify an auto-resize increment when specifying a maximum.

Action: Run 'acfsutil size' to shrink the file system to the recommended size, or to increase the accelerator volume size to the recommended size.

Action: Attempt to correct the issues indicated by the accompanying messages and retry. If unable to make progress, contact Oracle Support Services.

Action: Specify a valid value for compression unit size with the -c option and retry.

Action: Specify an output directory on an ACFS Volume and retry.

Action: Consult the command inline help or the product documentation for command argument details.

Action: Consult the command inline help or the product documentation for command argument details.

Action: Enable compression on the volume and retry, or use the -u option.

Action: Correct the problem indicated by the other messages. If the cause of the problem is unclear, contact Oracle Support Services.

Action: Correct the problem indicated by the other messages. If the cause of the problem is unclear, contact Oracle Support Services.

Action: Specify a directory for a recursive copy and retry.

Action: Retry the command using only directory or file names on the command line.

Action: Provide the name of an existing directory and retry.

Action: Consult the command inline help or the product documentation for command argument details.

Action: Retry the command without the -c option.

Action: To overwrite an existing file, specify the -f option. Otherwise, specify a file system path that does not exist.

Action: Correct the problems indicated by the other messages. If the cause of the problem is unclear, contact Oracle Support Services.

Action: Specify the path of a regular file to copy.

Action: Specify a file system directory for the last command line argument.

Action: If the copy is intended to be used by the database, it must be compressed with a compression unit size equal to the internal block size. In this case, use the -c option with a value equal to the internal block size and retry the command.

Action: Specify the path name in the form of an absolute path. On Windows, the absolute path includes the drive letter.

Action: None

Action: Select a supported release stream that is higher than the active ACFS compatibility level and retry the 'acfsutil compat set' command.

Action: Correct the problem indicated by the other messages. If the cause of the problem is unclear, contact Oracle Support Services.

Action: If the cluster is in the proces of a rolling upgrade, verify the target version of the upgrade and wait until the upgrade has completed to retry the command. If the cluster is not in the process of a rolling upgrade, the supplied release will not be supported until the cluster has been upgraded to a sufficient release.

Action: Verify that the supplied release follows the Oracle version syntax (For example, 12.2.0.0.0) and retry the command.

Action: Retry the mkfs command with a release passed to the -c option that is equal to or exceeds the required version displayed in the message.

Action: Correct the problem indicated by the other messages. If the cause of the problem is unclear, contact Oracle Support Services.

Action: Ensure that the compatible.advm setting is at least 12.2.0.0.0 and then re-issue the command.

Action: If the invalid entry was required, re-issue the command with the correct value. Otherwise no further action is required.

Action: If the additional entries are required, re-issue the command, specifying a different output file along with the -o arguments that were previously ignored. Otherwise no further action is required.

Action: Ensure that the compatible.advm setting is at least 18.0.0.0.0 for Linux or 19.0.0.0.0 for Aix and then re-issue the command.

Action: Retry the command. If unable to proceed, contact Oracle Support Services.

Action: Delete and re-add the ACFS file system using the command 'acfsutil registry'. Use the node option to specify the nodes on which this file system should run.

Action: Start an Oracle ASM instance and retry the command. If the problem persists, contact Oracle Support Services.

Action: Examine the messages in the OKS persistent log, resolve the indicated problems, and retry the operation.

Action: Retry the operation, specifying a valid 'acfsutil meta' file.

Action: Examine the accompanying messages, resolve the indicated problems, and retry the operation.

Action: Retry the command using a valid scan size.

Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.

Action: Retry the operation, providing a valid value for the sort option. Valid sort option values can be displayed by running the command with the 'h' (help) option.

Action: Contact Oracle Support Services.

Action: Contact Oracle Support Services.

Action: Rerun the command with only one of the specified options.

Action: Rerun the command, providing a positive integer value for the option 't'.

Action: Make sure ACFS has been properly installed. If the solution is not clear, contact Oracle Support Services.

Action: Rerun the command with a compatible set of options.

Action: Correct the problem indicated by the other messages. If the cause of the problem is unclear, contact Oracle Support Services.

Action: Make sure the device is unmounted on all cluster nodes, and then retry the command.

Action: Rerun the command with a compatible set of options.

Action: Rerun the command with a compatible set of options.

Action: Make sure the device is mounted, and then retry the command.

Action: If possible re-run 'acfsutil meta' again to collect all the metadata. If you must use this metadata collection file, just be aware that it may be incomplete.

Action: If possible re-run 'acfsutil meta' without the 'g' option to force a block-by-block file system walk. If you must use this metadata collection file, just be aware that it may be incomplete.

Action: Rerun the command with a compatible set of options.

Action: Rerun the command with a different option 'f' or 'a' file name.

Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.

Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.

Action: Retry the ' acfsutil fshare create' command specifying a different name.

Action: Delete unnecessary files from the file system to free up space, resize the file system using 'acfsutil size', or delete snapshots from the file system if any exist.

Action: Retry the 'acfsutil fshare create' command with the correct name.

Action: Terminate replication by using command 'acfsutil repl term' and then retry.

Action: None

Action: Reissue the command in a writable snapshot.

Action: Reissue the command in a writable mountpoint.

Action: Turn off compression by using command 'acfsutil compression off' and copy the file then retry.

Action: Reissue the command in the same namespace.

Action: Use the Oracle ASM Configuration Assistant (ASMCA) tool or the SQL ALTER DISKGROUP statement to upgrade the disk group compatibility (COMPATIBLE.ADVM attribute) to the specified version and then re-issue the original command. If the disk group compatibility cannot be upgraded, update the ACFS compatibility using the 'acfsutil compat set' command and then re-issue the original command.

Action: Delete a file share before creating a new one.

Action: Reissue the command in the same filesystem.

Action: Issue the command again using a shorter file share name.

Action: Retry the 'acfsutil fshare create' command specifying a valid fshare create name.

Action: Verify the path is accessible before retrying.

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.

Action: Select a different volume and retry the dismount operation.

Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.

Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.

Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.

Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.

Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.

Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.

Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.

Action: Verify the ASM instance is operational and the volume is enabled and accessible before retrying.

Action: Use acfsmountvol to determine if there are any file systems still mounted and reissue 'acfsdismount /all' if necessary.

Action: None

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'

Action: None

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'

Action: Manually remove the administrative network share at the specified share name using 'net share share name /delete'

Action: Correct the error indicated by the accompanying messages.

Action: To force dismount to complete, terminate any processes or applications that are using the file system.

Action: No action required. The unmount will proceed without the option.

Action: Verify the mount point is a valid ACFS file system before retrying the unmount command. If the problem persists, contact Oracle Support Services.

Action: Correct the problem indicated by the other message(s). If the cause of the problem is unclear, contact Oracle Support Services.

Action: At command line, indicate primary or standby for replication command.

Action: Provide Oracle Net alias to connect to the primary replication site.

Action: Provide an existing mount point on the primary site for the file system to be replicated.

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.

Action: See the platform specific Oracle documentation for correct syntax for ACFS tag names.

Action: Verify the specified mount point is an ACFS file system.

Action: Contact Oracle Support Services.

Action: Correct the problem indicated by the other message(s). If the cause of the problem is unclear, contact Oracle Support Services.

Action: Wait for the other initialization on replication site to complete.

Action: Monitor initialization progress with the 'acfsutil repl info' command.

Action: Correct the problem indicated by the other message(s). If the cause of the problem is unclear, contact Oracle Support Services.

Action: Initialization cannot be undone unless replication is terminated or the file system is reformatted.

Action: Correct the problem indicated by the other message(s). If the cause of the problem is unclear, contact Oracle Support Services.

Action: Correct the problem indicated by the other message(s). If the cause of the problem is unclear, contact Oracle Support Services.

Action: Verify user permissions and that the replication directory is available.

Action: Verify that the ADVM/ACFS drivers are loaded and running.

Action: Correct the problem indicated by the other message(s). If the solution is not clear, contact Oracle Support Services.

Action: Verify that the file system is mounted and of type ACFS.

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.

Action: Verify that CRS is running. Check the CRS logs to determine why the replication daemons failed to start.

Action: Verify that CRS is running. Check the CRS logs to determine why the replication daemons failed to stop.

Action: Verify that CRS is running. Check the CRS logs to determine why the replication daemons failed to start.

Action: None

Action: None

Action: None

Action: None

Action: Verify the ASM instance is operational and the state of the file system using 'acfsutil info fs' before retrying the command.

Action: Contact Oracle Support Services.

Action: Correct the problem indicated by the other message(s). If the solution is not clear, contact Oracle Support Services.

Action: Contact Oracle Support Services.

Action: Use an empty standby file system; either reformat the file system or remove all files and directories under standby mount point/.

Action: Correct the problem indicated by the other message(s). Otherwise, report this error to Oracle Support Services.

Action: Provide an existing mount point with an empty file system on the standby replication site.

Action: Verify that the replication directory is available.

Action: Correct the problem indicated by the other message(s). If the solution is not clear, contact Oracle Support Services.

Action: Correct the problem indicated by the other message(s). If the solution is not clear, contact Oracle Support Services.

Action: Verify that the replication directory is available.

Action: Verify the ASM instance is operational and the state of the file system using 'acfsutil info fs' before retrying the command.

Action: Verify the ASM instance is operational and the state of the file system using 'acfsutil info fs' before retrying the command.

Action: Verify that the Oracle Net alias exists and is properly formed.

Action: Reduce the size of the Oracle Net service name being used for replication.

Action: Execute the replication command from a user with administrator access.

Action: Execute the replication command from a user with ASM administrator group access.

Action: Verify that CRS is running.

Action: Verify the syntax of the time interval using 'acfsutil repl info' help flag and retry.

Action: Verify the syntax of the date range using 'acfsutil repl info' help flag and retry.

Action: Verify the time specified is before the current time.

Action: Verify the start time is before the end time.

Action: None

Action: Verify the connection information is correct and the status of the remote site.

Action: None

Action: On the standby replication site, run 'acfsutil repl terminate' and 'acfsutil repl init' before retrying initialization on the the primary replication site.

Action: Review the Oracle Net alias for replication in tnsnames.ora and use a different service name for the replication alias.

Action: Unmount the file system on all but one node on the standby replication site and retry the initialization.

Action: Verify the connection information is correct and the status of the primary replication site.

Action: Verify the connection information is correct and the status of the standby 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.

Action: None

Action: None

Action: None

Action: Verify that CRS is running. Check the CRS logs to determine why the CRS resource is not responding.

Action: Verify that CRS is running. Check the CRS logs to determine why the CRS resource cannot be relocated.

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.

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.

Action: None

Action: Verify that the replication directory is available.

Action: None

Action: Specify at least one replication attribute to be updated.

Action: Execute 'acfsutil repl update' on the primary replication site.

Action: Verify the username and password are correct when connecting to the standby site.

Action: Verify the ASM instance is operational and the state of the file system using 'acfsutil info fs' before retrying the command.

Action: Verify the ASM instance is operational and the state of the file system using 'acfsutil info fs' before retrying the command.

Action: Verify the ASM instance is operational and the state of the file system using 'acfsutil info fs' before retrying the command.

Action: Verify that CRS is running. Check the CRS logs to determine why the CRS user and/or group cannot be determined.

Action: Verify the ASM instance is operational and the state of the file system using 'acfsutil info fs' before retrying the command.

Action: Verify the ASM instance is operational and the state of the file system using 'acfsutil info fs' before retrying the command.

Action: None

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.

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.

Action: If the file system was frozen, run 'acfsutil thaw mount-point' and then retry the operation. Otherwise, migration to newer replication infrastructure must be performed. Refer to the Oracle Product Documentation for more information.

Action: Verify the listener is started on the standby site. Check that the standby alias contains the correct node names.

Action: Change the time range or use an events log that covers the range specified.

Action: Resize the file system to at least the minimum size specified.

Action: Query the replication statistics from the primary site.

Action: Retry the command with a lower interval value.

Action: Use a valid mount path.

Action: Consider resizing the file system to allow for optimal replication performance.

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.

Action: Resize the file system such that free space is at least the minimum size specified.

Action: None

Action: Complete the rolling migration and then initialize replication.

Action: Either complete the rolling migration and then terminate replication, or unmount this file system on the other nodes and then terminate replication.

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.

Action: None

Action: None

Action: None

Action: None

Action: None

Action: If you are sure you want to use the indicated file system as standby, reformat the standby file system and retry the command.

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.

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.

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.

Action: Contact Oracle Support Services.

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.

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.

Action: Contact Oracle Support Services.

Action: Initialize ACFS Security on the standby site by executing the 'acfsutil sec init' command and retry the operation.

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.

Action: Contact Oracle Support Services.

Action: Retry the command after some time.

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.

Action: Verify that the ACFS replication initialization is complete by executing 'acfsutil repl info' and retry.

Action: Initialize ACFS Audit on the standby site by executing the 'acfsutil audit init' command and retry the operation.

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.

Action: Initialize ACFS Audit on the standby site by executing the 'acfsutil audit init' command and retry the operation.

Action: Contact Oracle Support Services.

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.

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.

Action: Initialize ACFS Audit on the standby site by executing the 'acfsutil audit init' command and retry the operation.

Action: Contact Oracle Support Services.

Action: Verify the status of remote site and retry the command.

Action: Verify the status of remote site and retry the command.

Action: Verify the status of remote site and retry the command.

Action: Complete the rolling migration and retry the command.

Action: Complete the rolling migration and retry the command.

Action: Complete the rolling migration and retry the command.

Action: Retry initializing ACFS replication either: 1. specifying a file system (not a snapshot) as the standby site, or 2. after first disabling ACFS security on the primary file system.

Action: Retry initializing ACFS replication either: 1. specifying a file system (not a snapshot) as the standby site, or 2. after first disabling ACFS encryption on the primary file system.

Action: Retry initializing ACFS replication either: 1. specifying a file system (not a snapshot) as the standby site, or 2. after first disabling ACFS audit on the primary file system.

Action: Retry the command after reinitializing replication using a file system (not a snapshot) as the standby site.

Action: Retry the command after reinitializing replication using a file system (not a snapshot) as the standby site.

Action: Retry the command after reinitializing replication using a file system (not a snapshot) as the standby site.

Action: Retry after disabling ACFS Security using 'sec prepare -u' on the file system.

Action: Retry after disabling ACFS Encryption using 'encr set -u' on the file system.

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.

Action: Run 'ocrcheck -local' to verify the OLR is accessible and working properly.

Action: Contact Oracle Support Services.

Action: Correct the problem indicated by the other message(s) immediately. If the cause of the problem is unclear, contact Oracle Support Services.

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.

Action: Correct the problem indicated by the other message(s). If the cause of the problem is unclear, contact Oracle Support Services.

Action: Resize the standby file system or delete snapshots from the standby file system if any exist; otherwise, replication may not proceed.

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.

Action: Make sure the replication transport daemon is running and that proper permissions are set on the replication file systems.

Action: Make sure the replication transport daemon is running and that proper permissions are set on the replication file systems.

Action: Verify the ASM instance is operational and the state of the file system using 'acfsutil info fs' before retrying the command.

Action: Verify the ASM instance is operational and the state of the file system using 'acfsutil info fs' before retrying the command.

Action: Check the ACFS alert logs and 'acfsutil repl info' to determine the cause.

Action: Make sure all replication resources are running using 'acfsutil repl bg info' on both the primary and standby replication sites.

Action: Make sure proper permissions are set on the replication directories and that I/O requests can be processed.

Action: Restart the file system replication resource using 'acfsutil repl bg start'.

Action: None

Action: Retry the command using an ACFS mount point.

Action: Provide the Oracle Net alias to connect to the standby replication site.

Action: Verify that the ADVM/ACFS drivers are loaded and running.

Action: Verify that the ADVM/ACFS drivers are loaded and running.

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.

Action: The new replication infrastructure supports current and future functional and performance improvements. While replication continues to function for the indicated mount point, migration to the new infrastructure must be performed as soon as possible. One option is to terminate and restart replication. The other option is to use the 'acfsutil repl upgrade' suite of commands to migrate this use of replication without disturbing it. Refer to the Oracle product documentation for more information.

Action: The new replication infrastructure supports current and future functional and performance improvements. While replication will function for the relationship just initiated, migration to the new infrastructure must be performed as soon as possible. One option is to terminate and restart replication. The other option is to use the 'acfsutil repl upgrade' suite of commands to migrate this use of replication without disturbing it. Refer to the Oracle product documentation for more information.

Action: None

Action: Use the exact tag names specified during the "acfsutil repl init" operation.

Action: None

Action: None

Action: None

Action: None

Action: None

Action: None

Action: None

Action: None

Action: If possible, ensure the first tree is not changing while the tool is running.

Action: None

Action: None

Action: None

Action: None

Action: None

Action: None

Action: Tag names on files can be displayed with the "acfsutil tag info" command.

Action: None

Action: None. The file was skipped.

Action: None. The file was skipped.

Action: Informational

Action: If possible, do not modify files in the first tree when running this tool.

Action: If possible, do not modify files in the first tree when running this tool.

Action: Ensure the files security attributes can be read using a file manager.

Action: Check the Windows SID is available on this host.

Action: Reissue the 'acfsutil repl init primary' with a matching replication user for the '-p' and '-s' options. This user should also match the replication user specified with the 'acfsutil repl init standby' command using the '-u' option.

Action: Ensure the file system is accessible via "acfsutil info fs".

Action: Disable ACFS tag name comparison by omitting the "-a" option.

Action: None

Action: Use a networked file system to provide access to the second tree on the primary node where the 'acfsutil repl compare' will be performed.

Action: None

Action: None

Action: None

Action: None

Action: None

Action: None

Action: None

Action: None

Action: None

Action: None

Action: None

Action: None

Action: None

Action: None

Action: None

Action: Combine the 's' option with either the 'a' option or 't' option.

Action: Rerun the command specifying unique trees.

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.

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.

Action: Restart replication with a larger primary file system that has free space equal to at least 4GB per active node.

Action: Check that the network connectivity between the primary and standby replication systems is functional.

Action: Check that the network connectivity between the primary and standby replication systems is functional.

Action: None

Action: None

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.

Action: Query the replication apply events from the primary site.

Action: Query the replication transport events from the primary site.

Action: Initialize ACFS replication in an environment that is configured with single or multi-node RAC.

Action: Verify user permissions, that the snapshot directory is available, and then retry the command.

Action: Run 'acfsutil repl terminate' and retry the initialization.

Action: Provide the username and VIP name or hostname to connect to the standby replication site.

Action: Provide the username for connecting and applying changes to the standby replication site using the -u option.

Action: Verify the username is correct when connecting to the standby site.

Action: Resize the primary file system, or delete snapshots from the primary file system if they exist, and retry 'acfsutil repl terminate'.

Action: Pause replication or stop the replication resource and try to update the standby replication site again.

Action: Specify the 'i' option with an integer value greater than zero.

Action: Append a unit from the set W (weeks), D (days), H (hours), M (minutes), S (seconds) to the interval specified.

Action: Append a unit of time from the set W (weeks), D (days), H (hours), M (minutes), S (seconds) to the interval specified.

Action: Provide an interval when the primary is initialized. An interval can be set implicitly through the use of the '-C' option or explicitly through the argument passed to the '-i' option.

Action: Remove some tag names and try the command again.

Action: Convert the snapshot to be read-write and retry.

Action: None

Action: Ensure both systems are Unix or Linux or both systems are Windows.

Action: Run the 'acfsutil snap remaster' command with the snap duplicate backup snapshot for the target file system or snapshot, in order to re-base the target to the backup snapshot contents.

Action: Reestablish connectivity to the system containing the base or primary file system and then retry.

Action: If the indicated ACFS file system was not the intended target for upgrade, reissue the command specifying the correct file system.

Action: Run the 'acfsutil repl upgrade prepare' command to prepare the file system to be upgraded.

Action: Re-create the snapshot as read only and retry the command.

Action: Reverse the order of the two snapshot names or specify a different new or old snapshot and retry the command.

Action: Run the 'acfsutil snap remaster' command with the snap duplicate backup snapshot for the target file system or snapshot, in order to re-base the target to the backup snapshot contents.

Action: Terminate replication on the file system if appropriate by executing the 'acfsutil repl terminate' command and then retry the 'acfsutil snap duplicate' command.

Action: Ensure that the correct host name or IP address was specified for the standby node, and that the standby node is operating normally. Then reissue the 'acfsutil repl init primary' command.

Action: Ensure that the correct user name and address were specified for the standby node, and that the standby cluster is operating normally. If need be, verify network connectivity to the standby cluster, and refer to the product documentation to verify ssh configuration details. Then reissue the 'acfsutil repl init primary' or 'acfsutil repl update' command.

Action: Reissue the 'acfsutil repl compare' command without the '-t ALL' option.

Action: Ensure that the path to the ssh utility is correct and retry.

Action: Ensure that the standby cluster is operating normally. If need be, verify network connectivity to the standby cluster, and refer to the product documentation to verify ssh configuration details.

Action: Ensure that the correct user name and address were specified for the standby node, and run the 'acfsutil repl info -c' command on the standby site to confirm that replication has been initialized there for the mount point named. Then retry the 'acfsutil repl init primary' command.

Action: Check the standby cluster for conditions that would prevent snapshot creation, such as lack of storage or having too many snapshots present. Replication will resume automatically once backup snapshots can again be created.

Action: Retry the command with a supported ssh cipher option.

Action: Rename the problematic files so that their absolute path names are shorter than the limit, and retry the command.

Action: Rename the problematic files so that their absolute path names are shorter than the limit. Once each file has been renamed, the next later replication operation will automatically transfer the file.

Action: Apply an initial snapshot duplication stream to the target using 'acfsutil snapshot duplicate create' without the -i option to create the initial snapshot duplication stream.

Action: Apply all the intermediate incremental data streams in the correct order leading up to failed snap duplication stream and then rerun the apply operation.

Action: Re-apply the correct initial snapshot duplication stream using the -r option of the command 'acfsutil snap duplicate create'.

Action: Generate a snapshot duplication stream using the -r option of the command 'acfsutil snap duplicate create', and apply it.

Action: Resume replication on the primary replication site and try the command again.

Action: Use the Oracle ASM Configuration Assistant (ASMCA) tool or the SQL ALTER DISKGROUP statement to upgrade the disk group compatibility (COMPATIBLE.ADVM) attribute to the specified version and then re-issue the original command. If the disk group compatibility attribute cannot be upgraded, update the ACFS compatibility using the 'acfsutil compat set' command and then re-issue the original command.

Action: Check the alert log for message ACFS-05027 which includes the name of the directory being deleted. Check the standby cluster for conditions that would prevent the directory from being deleted, such as its being in use. Replication will resume automatically once the directory can be removed.

Action: Ensure that the cluster where the standby replication ACFS file system is located is running a version of Clusterware that supports the version of ACFS replication to which upgrade was attempted. Upgrade the standby replication ACFS file system, and then reissue the command to upgrade the primary ACFS replication file system. Refer to Oracle product documentation for details regarding Clusterware and ACFS replication version compatibility.

Action: Terminate the existing replication environment and reconfigure using snapshot-based replication. Refer to Oracle product documentation for details regarding upgrading to ACFS snapshot-based replication.

Action: Ensure that you are using 'acfsutil repl init' as required by the current version of ACFS replication. Refer to the Oracle product documentation for details about running current replication.

Action: Contact Oracle Support Services.

Action: Unmount the ACFS replication primary on all but one node and retry the command.

Action: Reissue the command with the correct snapshot names.

Action: Reissue the command with the correct snapshot names.

Action: Reissue the command with the correct snapshot names.

Action: Reissue the command specifying a writable parent snapshot.

Action: If the indicated ACFS file system was not the intended target for upgrade, reissue the command specifying the correct file system. Otherwise no further action is necessary.

Action: If the indicated Oracle ACFS file system was not the intended target for upgrade, reissue the command specifying the correct file system. Otherwise no further action is necessary.

Action: Run the 'acfsutil repl update' command for the mount point where the intended replication user is not currently configured to ensure that both mount points have the intended user configured.

Action: If the intended replication user was correctly specified, ensure that that user is a member of the necessary groups, as specified in the Oracle documentation, before continuing to initiate replication. If the indicated user is not the intended replication user, then re-initialize the standby using the command 'acfsutil repl terminate standby' and then 'acfsutil repl init standby' naming the intended user.

Action: Reissue the command specifying old and new snapshots with the required relationship.

Action: Upgrade the Oracle Clusterware on the cluster where the standby file system is located to ensure that the cluster is running the same version of Clusterware as the cluster where the primary file system is located.

Action: None

Action: Reissue the command specifying a writable snapshot.

Action: Reissue the command specifying a standby that is not in use.

Action: Ensure that the cluster where the standby replication ACFS file system is located is running a version of Clusterware that supports the version of ACFS replication which was being initialized. Initialize the standby replication ACFS file system, and then reissue the command to initialize the primary ACFS replication file system. Refer to Oracle product documentation for details regarding Clusterware and ACFS replication version compatibility.

Action: Complete the rolling upgrade and then reverse the replication site.

Action: If the command has completed in the meantime, no action is required. Otherwise, if no action is taken, snapshot creation will be retried periodically and complete once the ACFS replication update has completed. To complete the snapshot creation immediately, interrupt the replication update and reissue the command. Terminiate the 'acfsutil snap create', run 'acfsutil repl pause' on the replication primary to pause the update, and then reissue 'acfsutil snap create'. Finally, run 'acfsutil repl resume' on the primary to resume the replication update.

Action: Reverse the replication primary site, then retry the operation.

Action: On the remote replication cluster, verify replication is enabled, the ASM instance is operational and the state of the file system is healthy using 'acfsutil info fs'.

Action: On the remote replication cluster, verify replication is enabled, the ASM instance is operational and the state of the file system is healthy using 'acfsutil info fs' before running 'acfsutil repl terminate' on the remote cluster.

Action: If the replication user configured on the standby is correct, reissue the 'acfsutil repl init primary' command specifying it using the '-s' option. If the replication user configured on the standby is incorrect, run 'acfsutil repl terminate' on the standby, and rerun the 'acfsutil repl init' commands specifying the same user for replication user on both the standby and primary using the '-u' and '-s' options respectively.

Action: Complete the rolling upgrade and then retry the operation.

Action: Determine why the standby was failed over. If appropriate, determine why this site has not failed over.

Action: Determine why the standby was removed from this replication relationship, configure a new standby and then run 'acfsutil repl update -m -s' on this node.

Action: Complete or abort the role reversal and then retry the operation.

Action: Complete the upgrade process and then retry the operation.

Action: Reissue the command with the correct snapshot names.

Action: Reissue the command without the multiple connection option.

Action: Correct the problem described in the accompanying messages if possible and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).

Action: Correct the problem described in the accompanying messages if possible and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).

Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.

Action: Correct the problem described in the accompanying messages if possible and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).

Action: Restore the file system from a backup copy.

Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem.

Action: Correct the problem described in the accompanying messages if possible and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).

Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve 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.

Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve 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.

Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve 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.

Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve 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.

Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve 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.

Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve 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.

Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve 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.

Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve 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.

Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve 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.

Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve 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.

Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve 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.

Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve 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.

Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve 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.

Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve 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.

Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve 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.

Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve 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.

Action: If the ACFS Fixer is currently running, then no further action is needed. The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the ACFS Fixer to resolve 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.