ADVM-00565: unable to delete Oracle Registry key string string
Cause: Removal of mount key from Oracle Registry failed.
Action: Use acfsutil registry to verify the mount key exists in the Oracle Registry.
ADVM-00566: invalid handle received when attempting to close an ACFS mount
key within Oracle Registry
Cause: An error was returned during the closing of a key in the Oracle Registry.
Action: Run ocrcheck to verify the Oracle Registry is working properly. Report to
Oracle Support Services.
ADVM-00567: unknown Oracle Registry error encountered closing key
Cause: An error was returned while closing the key from the Oracle Registry.
Action: Run ocrcheck to verify the Oracle Registry is working properly. Report to
Oracle Support Services.
ADVM-00568: closing of a key resulted in Oracle Registry error number
Cause: An error was returned during the closing of a key in the Oracle Registry.
Action: Verify the Oracle Registry is accessible. If it is not accessible and the cause
is unclear, report this error to Oracle Support Services.
ADVM-00569: invalid handle received when attempting to delete an ACFS mount
key within Oracle Registry
Cause: An error was returned while removing a key from the Oracle Registry.
Action: Report this error to Oracle Support Services.
ADVM-00570: The ACFS mount key specified for deletion does not exist within
Oracle Registry.
Cause: The mount key could not be located in the Oracle Registry.
Action: Use acfsutil registry to ensure the mount entry exists in the Oracle
Registry.
ADVM-00571: The ACFS mount key specified for deletion is not empty.
Cause: The mount key specified for deletion from the Oracle Registry contained
dependent subkeys.
Action: View the mount entries in the Oracle Registry using "acfsutil registry" and
remove any dependent mount entries before retrying this operation.
ADVM-00572: permission denied to delete the ACFS mount entry from Oracle
Registry
Cause: The user permissions were insufficient to remove the key from the Oracle
Registry.
Action: Verify the Oracle Registry is accessible and that command is being run
from a properly authorized user ID.
ADVM-00573: Oracle Registry error encountered while deleting an ACFS mount
key
Cause: An error was returned while removing the key from the Oracle Registry.
ADVM-00501 to ADVM-11069 98-5
Action: Report this error to Oracle Support Services.
ADVM-00575: deletion request of key resulted in Oracle Registry error number
Cause: An error was returned while removing a key from the Oracle Registry.
Action: Run ocrcheck to verify that Oracle Registry is working properly. If
problem persists, report to Oracle Support Services.
ADVM-00584: failed to look up ACFS mount points in the Oracle Registry string
Cause: An error was returned while looking up a mount point in the Oracle
Registry.
Action: Run ocrcheck to verify the Oracle Registry is working properly. If problem
persists, report to Oracle Support Services.
ADVM-00585: null parameter received
Cause: A null parameter was passed to the Oracle Registry.
Action: Run ocrcheck to verify that Oracle Registry is working properly. If
problem persists, report to Oracle Support Services.
ADVM-00587: unknown Oracle Registry error encountered during operation on
ACFS mount entry
Cause: An error was returned while accessing the key from the Oracle Registry.
Action: Run ocrcheck to verify that Oracle Registry is working properly. If
problem persists, report to Oracle Support Services.
ADVM-00589: key operation resulted in Oracle Registry error number
Cause: An error was returned during a key operation with the Oracle Registry.
Action: Run ocrcheck to verify that Oracle Registry is working properly. If
problem persists, report to Oracle Support Services.
ADVM-00592: Seek to volume failed. Verify the volume exists.
Cause: Seek to a location on the volume failed.
Action: Verify the volume exists on this node and that it is accessible.
ADVM-00593: The Oracle Registry returned the following error while attempting
to access ACFS key string string
Cause: Failed to access either the SYSTEM, SYSTEM.ACFS or
SYSTEM.ACFS.Mounts keys in Oracle Registry.
Action: Run ocrcheck to verify the Oracle Registry is working properly. Examine
the appended error message from the Oracle Registry service.
ADVM-00594: Failed to access ACFS mount information. The Oracle Registry
returned the appended error for ACFS key string. string
Cause: Failed to access ACFS mount information from the Oracle Registry.
Action: Examine the appended error message from the Oracle Registry.
ADVM-00595: Failed to access ACFS mount value information. The Oracle Registry
returned the appended error for ACFS key string. string
Cause: Failed to access ACFS mount value information from the Oracle Registry.
This might be due to Oracle Registry corruption or a sudden loss of the Oracle
Registry service.
Action: Examine the appended error message from the Oracle Registry. Run
ocrcheck to verify the Oracle Registry is working properly.
98-6 Oracle Database Error Messages
ADVM-00596: A failure occurred while accessing the Oracle Registry ACFS key
"SYSTEM" for security purposes and follows this message: string
Cause: Failed to retrieve key access rights for the Oracle Registry ACFS key
"SYSTEM"
Action: Run ocrcheck to verify the Oracle Registry is working properly. Evaluate
the error message returned from the Oracle Registry appended to this message. If
necessary, run ocrdump and make sure the "SYSTEM" key exists and is accessible.
ADVM-00597: Failed to initialize the Oracle Registry's SCLS context. The SCLS
error is included with this message.
Cause: An operating system initialization failed.
Action: Evaluate the attached SCLS error message. Run ocrcheck to verify the
Oracle Registry is functioning correctly.
ADVM-00598: An error occurred while looking up the current user's operating
system account name. The error is included with this message.
Cause: ACFS was attempting to add an entry to the Oracle Registry. During this
attempt a lookup of the current user's name failed in the operating system failed.
Action: Evaluate the attached error message to determine why the current user
name could not obtained from the operating system.
ADVM-00599: The Oracle Registry returned the following error while attempting
to close the ACFS key string string
Cause: Possibly due to Oracle Registry corruption or a sudden loss of the Oracle
Registry service.
Action: Examine the appended error message from the Oracle Registry. Run
ocrcheck to verify the Oracle Registry is working properly.
ADVM-00600: Failed to access ACFS mount subkey information. The Oracle
Registry returned the appended error. string
Cause: Failed to access ACFS mount information from the Oracle Registry.
Action: Examine the appended error message from the Oracle Registry.
ADVM-00601: Failed to initialize this utility's access to the Oracle Registry. Verify
the registry service has started.
Cause: Either the Oracle Registry service was unavailable or the registry
configuration was incomplete/inaccurate.
Action: Run ocrcheck to verify the registry service is working properly.
ADVM-00602: An internal error (BADARG) occurred while trying to determine the
Oracle Registry configuration.
Cause: An Oracle internal error.
Action: Contact Oracle.
ADVM-00603: Failed to retrieve the Oracle Cluster Registry, OCR, configuration
Cause: Failed to obtain OCR information.
Action: Run ocrcheck to verify OCR is working properly.
ADVM-00604: Failed to retrieve the Oracle Local Registry, OLR, configuration
Cause: Failed to obtain Oracle Local Registry information.
Action: Run ocrcheck -local to verify the OLR is working properly.
ADVM-00501 to ADVM-11069 98-7
ADVM-00605: Failed to retrieve the Oracle Registry configuration for an unknown
reason
Cause: Failed to obtain Oracle Registry information.
Action: Run ocrcheck to verify the registry is working properly.
ADVM-00606: Could not determine if the system is configured for RAC or Oracle
Restart environment.
Cause: The Oracle Registry service configuration could not be detected
Action: Run ocrcheck to verify the Oracle registry service.
ADVM-00607: Failed to access or create Oracle Registry keys required for ACFS
operation
Cause: Oracle Registry keys required for operation either could not be accessed or
created.
Action: Another error message number will follow this message. Analyze its
output. Run ocrcheck to verify the Oracle registry is functioning properly. Also,
verify acfsutil was invoked with administrative rights when attempting to add the
ACFS mount points.
ADVM-00619: This is a string computer, but the file system was created on a string
string computer.
Cause: The file system was created on a computer which has a different Endian
than the current system. Little Endian machines (such as the intel x86 based
systems) store the Least Significant bit in the first byte of an integer value. Big
Endian machines (such as Solaris SPARC and AIX Power based systems) store the
Most Significant bit in the first byte of an integer value.
Action: Use a system with the same Endian as the system which created the file
system.
ADVM-00620: This feature is not available for Oracle version string or lower on
this platform.
Cause: Informational.
Action: None
ADVM-00621: Unable to determine privileges
Cause: An error occured retrieving the user credentials.
Action: Verify the mount point is an ACFS mount point and it is not offline.
ADVM-00622: must provide a base mount point
Cause: A mount point on the base site was not provided.
Action: Provide an existing mount point on the base site.
ADVM-00623: must provide a target mount point
Cause: A mount point on the target site was not provided.
Action: Provide an existing mount point with an empty file system on the target
site.
ADVM-00624: The path specified is too long.
Cause: The path specified exceeded the allowed maximum path length.
Action: Verify the path was entered correctly, or use a different path.
ADVM-00625: string is not a valid ACFS mount point.
98-8 Oracle Database Error Messages
Cause: The mount point path specified was not a valid mount point.
Action: Provide a valid ACFS mount point.
ADVM-01001: Size specified cannot exceed size of volume.
Cause: Volume size was smaller than the requested size.
Action: Select a size that is less than or equal to the volume size and retry the
ACFS format command.
ADVM-01002: ACFS requires a minimum volume size of numberMB.
Cause: Volume was too small.
Action: Select a larger volume and retry.
ADVM-01004: string was not formatted.
Cause: An error occurred during the formatting of the volume.
Action: This message is accompanied by another error message. Respond as
indicated for that message."
ADVM-01005: unable to allocate a buffer
Cause: A request for process virtual memory by the ACFS format command
failed. This message is accompanied by other message(s) providing details on the
error.
Action: Correct the problem indicated by the other message(s). If possible, change
options to reduce required memory and/or take steps to increase memory
available to the process. Otherwise, report this error to Oracle Support Services.
ADVM-01006: unable to open volume device 'string'
Cause: Volume device could not be opened. This message is accompanied by
other message(s) providing details on the error.
Action: Correct the problem indicated by the other message(s). If the cause of the
problem is unclear, contact Oracle Support Services.
ADVM-01008: unable to open file system string
Cause: File system was not accessible.
Action: Verify the volume associated with the file system is enabled and online
before retrying.
ADVM-01010: Volume already contains an ACFS file system. To reformat the
volume, reissue string with the stringf option.
Cause: The on-disk metadata indicated that an ACFS file system is located on the
volume.
Action: Verify the intended volume and reissue the format command with the
force flag to overwrite the existing ACFS file system.
ADVM-01011: Volume contains an ACFS file system that is being checked. To
reformat the volume, reissue string with the stringf option.
Cause: The volume contained a file system that was in the process of being
checked by fsck (Unix or Linux) or acfschkdsk.exe (Windows).
Action: Verify the intended volume and reissue the format command with the
force flag to overwrite the existing ACFS file system.
ADVM-01014: write of volume label failed
ADVM-00501 to ADVM-11069 98-9
Cause: A write to the volume during file system creation failed. This message is
accompanied by other message(s) providing details on the error.
Action: Correct the problem indicated by the other message(s). If the solution is
not clear, contact Oracle Support Services.
ADVM-01018: failed to allocate a buffer for number bytes
Cause: A request for process virtual memory by the ACFS format command
failed. This message is accompanied by other message(s) providing details on the
error.
Action: Correct the problem indicated by the other message(s). If possible, change
options to reduce required memory and/or take steps to increase memory
available to the process. Otherwise, report this error to Oracle Support Services.
ADVM-01019: This volume contains a mounted ACFS file system. The file system
must be dismounted with acfsdismount on all nodes.
Cause: The volume was in use by another file system.
Action: Dismount the ACFS file system with acfsdismount and retry the
command.
ADVM-01020: This volume contains a mounted non-ACFS file system. The file
system must be dismounted with 'advmutil dismount'.
Cause: The volume was in use by another non-ACFS file system.
Action: Dismount the non-ACFS file system with 'advmutil dismount' and retry
the command.
ADVM-01033: write to volume failed
Cause: of the problem is unclear, contact Oracle Support Services.
Action: Correct the problem indicated by the other message(s). If the
ADVM-01038: write failed during setup of root directory entry
Cause: of the problem is unclear, contact Oracle Support Services.
Action: Correct the problem indicated by the other message(s). If the
ADVM-01041: write of snaps directory entry failed
Cause: of the problem is unclear, contact Oracle Support Services.
Action: Correct the problem indicated by the other message(s). If the
ADVM-01043: write of lost+found directory entry failed
Cause: of the problem is unclear, contact Oracle Support Services.
Action: Correct the problem indicated by the other message(s). If the
ADVM-01044: write of file entry table failed
Cause: of the problem is unclear, contact Oracle Support Services.
Action: Correct the problem indicated by the other message(s). If the
ADVM-01045: write of global bitmap failed
Cause: of the problem is unclear, contact Oracle Support Services.
Action: Correct the problem indicated by the other message(s). If the
ADVM-01046: read of global bitmap file entry failed
Cause: of the problem is unclear, contact Oracle Support Services.
Action: Correct the problem indicated by the other message(s). If the
98-10 Oracle Database Error Messages
ADVM-01047: write of global bitmap file entry failed
Cause: of the problem is unclear, contact Oracle Support Services.
Action: Correct the problem indicated by the other message(s). If the
ADVM-01049: seek to snap map header failure
Cause: of the problem is unclear, contact Oracle Support Services.
Action: Correct the problem indicated by the other message(s). If the
ADVM-01050: write to snap map header failure
Cause: of the problem is unclear, contact Oracle Support Services.
Action: Correct the problem indicated by the other message(s). If the
ADVM-01051: partial write to snap map header failure
Cause: of the problem is unclear, contact Oracle Support Services.
Action: Correct the problem indicated by the other message(s). If the
ADVM-01052: write to snap map info entry failure
Cause: of the problem is unclear, contact Oracle Support Services.
Action: Correct the problem indicated by the other message(s). If the
ADVM-01053: partial write to snap map info entry failure
Cause: of the problem is unclear, contact Oracle Support Services.
Action: Correct the problem indicated by the other message(s). If the
ADVM-01054: write to snap map storage entry failure
Cause: of the problem is unclear, contact Oracle Support Services.
Action: Correct the problem indicated by the other message(s). If the
ADVM-01055: partial write to snap map storage entry failure
Cause: of the problem is unclear, contact Oracle Support Services.
Action: Correct the problem indicated by the other message(s). If the
ADVM-01150: unable to synchronize in-memory file data to disk
Cause: A request to flush all in-memory copies of buffers associated with the
open handle failed. This message is accompanied by other message(s) providing
details on the error.
Action: Correct the problem identified by the other message(s). If the problem has
been resolved and the file system is unusable, retry the ACFS format command.
ADVM-01151: Ignoring invalid block size number, using number
Cause: An ACFS format command unsupported block size was specified.
Action: No action required. A supported block size will be used.
ADVM-01152: The length of accelerator volume name exceeds number.
Cause: Accelerator volume name length exceeded the maximum length displayed
in the message.
Action: Select an accelerator volume name with length less than or equal to the
maximum length displayed in the message and retry the command.
ADVM-01154: The accelerator volume contains a mounted ACFS file system. The
file system must be dismounted with acfsdismount on each node.
ADVM-00501 to ADVM-11069 98-11
Cause: The specified volume could not be used as an accelerator volume because
it was in use by a mounted file system.
Action: Dismount the ACFS file system with acfsdismount and retry the
command.
ADVM-01155: The accelerator volume contains a mounted non-ACFS file system.
The file system must be dismounted with 'advmutil dismount'.
Cause: The specified volume could not be used as an accelerator volume because
it was in use by a mounted non-ACFS file system.
Action: Dismount the non-ACFS file system with 'advmutil dismount' and retry
the command.
ADVM-01156: The Oracle ASM Dynamic Volume Manager (Oracle ADVM)
compatibility attribute for the disk group is less than 12.1.0.2.0.
Cause: An attempt to create a file system with an accelerator volume failed
because the ADVM compatibility attribute for the disk group was not set to
12.1.0.2.0 or higher.
Action: Use the Oracle ASM Configuration Assistant (ASMCA) tool or the SQL
statement ALTER DISKGROUP to upgrade COMPATIBLE.ADVM attribute.
ADVM-01159: The accelerator volume must be different from the volume
containing the file system.
Cause: The file system could not be created because the same volume was
specified for both the accelerator and the file system.
Action: Choose a different volume for the accelerator and retry the command.
ADVM-01160: The specified accelerator volume was smaller than numberMB.
Cause: The file system could not be created because the specified accelerator
volume was below the minimum allowed size reported in the message.
Action: Select a larger accelerator volume and retry the command.
ADVM-01164: The specified device 'string' is already in use with a CRS-managed
file system.
Cause: The file system could not be created because the specified device was
already registered with CRS (Cluster Ready Services).
Action: Select an unused device, or use srvctl to modify the association for this
device and retry the file system creation.
ADVM-02001: unable to allocate a buffer
Cause: A request for process virtual memory by mount command failed. This
message is accompanied by other message(s) providing details on the error.
Action: Correct the problem indicated by the other message(s). If possible, change
options to reduce required memory and/or take steps to increase memory
available to the process. Otherwise, report this error to Oracle Support Services.
ADVM-02006: unable to terminate the Oracle Registry connection
Cause: Either the Oracle Registry service was unavailable or the Oracle Registry
configuration was incomplete/inaccurate.
Action: Run crs_stat and ocrcheck to verify CSS and the Oracle Registry are
working properly. If they are not accessible and the cause is unclear, report this
error to Oracle Support Services.
98-12 Oracle Database Error Messages
ADVM-02012: Mount of string failed, volume string does not exist. Verify that
string exists on this node.
Cause: Could not mount the file system retrieved from the Oracle Registry.
Action: Verify the volume exists on this node and that it is accessible.
ADVM-02014: Mount of string failed. Error number was returned.
Cause: Mount operation failed.
Action: Verify the mount point and volume both exist and are accessible before
retrying the mount command.
ADVM-02015: Failed to open mount point string. Verify the mount point exists.
Cause: Mount point could not be opened.
Action: Verify the mount point exists and is accessible before retrying the mount
command.
ADVM-02017: Failed to open volume string. Verify the volume exists.
Cause: The volume could not be opened.
Action: Verify the ASM instance is operational and the volume is enabled and
accessible before retrying the mount command.
ADVM-02018: Volume string contains an ACFS file system that is being checked.
Allow the file system check to complete.
Cause: The volume contained a file system that was in the process of being
checked by the ACFS checker.
Action: Allow the ACFS checker to complete before retrying the mount. If the
ACFS checker is not running on this file system and a file system check was
previously interrupted, reissue the ACFS checker.
ADVM-02026: unable to verify the host names passed in are part of the cluster
Cause: Either CSS was unavailable or the CSS configuration was
incomplete/inaccurate.
Action: Run crs_stat to verify CSS is working properly.
ADVM-02027: unable to obtain the local CSS node name
Cause: Either CSS was unavailable or the CSS configuration was
incomplete/inaccurate.
Action: Run crs_stat to verify CSS is working properly.
ADVM-02046: Volume string cannot be mounted. Examine the system event log for
possible causes.
Cause: The volume mount failed. This could be caused by an out of space
condition if this is the first mount of a file system on a node.
Action: Examine the system event log for more detail.
ADVM-02050: unable to set in-memory mount information
Cause: Could not communicate with the mounted file system.
Action: Verify the ASM instance is operational and the volume is enabled and
accessible before retrying.
ADVM-02081: Warning: acfschkdsk.exe should be run on volume string at your
earliest convenience
ADVM-00501 to ADVM-11069 98-13
Cause: A flag in the superblock indicates that a metadata inconsistency has been
found on this volume.
Action: Run acfschkdsk.exe as soon as possible to fix the metadata inconsistency.
ADVM-02082: unable to verify if the host names provided are part of the cluster
Cause: Could not obtain information about the cluster.
Action: Run crs_stat to verify health of CSS.
ADVM-02083: cannot get the local CSS node name
Cause: Could not obtain local CSS node name.
Action: Run crs_stat to verify health of CSS.
ADVM-02090: unable to retrieve ACFS mount information from CRS
Cause: Failed to retrieve mount information the CRS.
Action: Analyze the error messages that precede this message.
ADVM-02092: Mount of string failed, node string is not a member of the CSS
cluster.
Cause: Could not mount the file system retrieved from the Oracle Registry.
Action: Verify the node listed in the entry is a member of the CSS cluster.
ADVM-02119: creating administrative network share for mount point string at
share name 'string'
Cause: Informational
Action: None
ADVM-02120: administrative network share for mount point string already exists at
share name 'string'
Cause: Informational
Action: None
ADVM-02121: administrative network share 'string' already exists, but does not
share mount point string
Cause: Attempted to create an administrative network share for the specified
ACFS mount point, but the required share name was already in use.
Action: Remove the conflicting network share using 'net share <share name>
/delete'. Remount the ACFS file system to retry creating an administrative
network share for the mount point.
ADVM-02122: retrieving information for administrative network share 'string'
failed
Cause: While creating an administrative network share for the specified ACFS
mount point, failed to retrieve information on any network share that might
already exist at the required share name. This message is accompanied by other
messages providing details on the error.
Action: Correct the error indicated by the accompanying messages. Remount the
ACFS file system to retry creating an administrative network share for the mount
point.
ADVM-02123: creating administrative network share for mount point string at
share name 'string' failed
98-14 Oracle Database Error Messages
Cause: Failed to create an administrative network share for the specified ACFS
mount point. This message is accompanied by other messages providing details on
the error.
Action: Correct the error indicated by the accompanying messages. Remount the
ACFS file system to retry creating an administrative network share for the mount
point.
ADVM-02124: could not create administrative network share for mount point string
at share name 'string'
Cause: Failed to create an administrative network share for the specified ACFS
mount point. This message is accompanied by other messages providing details on
the error.
Action: Correct the error indicated by the accompanying messages.
ADVM-02125: volume 'string' is already in use
Cause: The volume was in use by another file system.
Action: Verify the volume specified.
ADVM-02126: Volume string cannot be mounted.
Cause: The volume mount failed. This message is accompanied by other messages
providing details on the error.
Action: Correct the problem indicated by the other messages and retry the mount
command.
ADVM-02127: unable to transfer mount data to the ACFS driver
Cause: is unclear, contact Oracle Support Services.
Action: Correct the problem identified by the other messages. If the
ADVM-02128: unable to clean up mount data passed to ACFS driver
Cause: The operation to clean up mount data from a temporary location / failed.
Action: None. This state will not have any repercussions and it will be remedied
automatically during the next restart.
ADVM-02129: Volume string cannot be mounted. Volume is out of space.
Cause: The volume mount failed because the volume was out of space.
Action: Correct the problem by resizing the ADVM volume and then retry the
mount command.
ADVM-02130: Volume string cannot be mounted. Volume version does not match
the ACFS driver version.
Cause: The volume mount failed because the loaded ACFS driver does not
support the volume version.
Action: Use 'acfsdriverstate' command to determine the state of the ACFS driver
and address any issues that are reported. Retry the mount command after the
installed driver has been verified.
ADVM-02131: Volume string cannot be mounted. Cluster membership is not
established.
Cause: The volume mount failed because the ACFS driver could not communicate
with Oracle Clusterware.
ADVM-00501 to ADVM-11069 98-15
Action: Verify the online state of Oracle Clusterware using command 'crsctl check
CRS' and address any issues that are reported. Retry the mount command once
Oracle Clusterware is fully operational.
ADVM-02132: Volume string cannot be mounted. Insufficient kernel resources to
complete the mount.
Cause: The volume mount failed due to insufficient kernel resources.
Action: Reduce the load activity on the system and retry the mount command.
ADVM-02133: Volume string cannot be mounted. Metadata inconsistency found
on-disk.
Cause: The volume mount failed due to a metadata inconsistency found in the
volume superblock.
Action: Run command 'fsck -t acfs' as soon as possible to fix the metadata
inconsistency and then retry the mount command.
ADVM-03001: Failed to open string. Verify that string exists.
Cause: The mount point or file could not be opened.
Action: Verify the mount point or file is accessible before retrying.
ADVM-03003: Cannot decrease the volume by this amount.
Cause: Requested size exceeded the size of the file system.
Action: Select a size that is smaller than the size of the file system and retry.
ADVM-03004: Cannot reduce volume size below 200 MB.
Cause: Requested size was below the minimum volume size of 200MB."
Action: Select a volume that is 200MB or larger."
ADVM-03008: The volume could not be resized. The volume expansion limit has
been reached.
Cause: The file system's internal storage bitmap has a five extent limit. Growing
the file system may fail if it has already been grown four or more times, using up
all available storage bitmap extents.
Action: If the file system has been grown four or more times, running the ACFS
Fixer may allow future volume expansions.
ADVM-03013: unable to open string
Cause: Volume could not be opened to remove the file system.
Action: Verify the volume is not mounted on any node in the cluster before
retrying.
ADVM-03033: unable to open string
Cause: The log file specified could not be created and/or opened.
Action: If a file exists by the same name as the log file specified, verify that this is
a file that can be overwritten.
ADVM-03044: Failed to open mount point string. Verify the mount point exists.
Cause: Mount point could not be opened for snapshot operation.
Action: Verify the mount point exists and is accessible before retrying the snap
command.
ADVM-03052: unable to delete snapshot string due to open files
98-16 Oracle Database Error Messages
Cause: There are files open in the snapshot.
Action: Use lsof or similar tool to find the processes with open files. No files can
be open in the snapshot for the snapshot delete operation to succeed.
ADVM-03054: snapshot string is not a valid snapshot name
Cause: statement.
Action: Verify that the snapshot name meets the criteria listed in the
ADVM-03091: Failed to open string. This may mean the string driver is not
loaded/running
Cause: The driver's control device could not be accessed.
Action: Verify the driver is loaded and running.
ADVM-03096: error opening configuration file string
Cause: The configuration file cannot be created and/or opened.
Action: If the configuration file exists, verify the file can be opened.
ADVM-03097: error accessing configuration file string
Cause: Seek to the end of the configuration file failed.
Action: If the configuration file exists, verify the file is accessible.
ADVM-03106: Invalid combination of arguments. stringa was previously specified
to add an ACFS mount point to Oracle Registry.
Cause: Invalid option combination.
Action: Retry the command with one set of operations.
ADVM-03107: Invalid combination of arguments. stringd was previously specified
to remove an ACFS mount point from the Oracle Registry.
Cause: Invalid option combination.
Action: Retry the command with one set of operations.
ADVM-03108: Neither string nor string is an ADVM volume.
Cause: Volume specified was not an ADVM volume.
Action: Retry the command with an ADVM volume.
ADVM-03110: unable to access the Oracle Registry string
Cause: Either the Oracle Registry service was unavailable or the registry
configuration was incomplete/inaccurate.
Action: Run ocrcheck to verify the Oracle Registry is working properly. Analyze
the appended Oracle Registry service error message.
ADVM-03114: unable to allocate a buffer
Cause: A request for process virtual memory by acfsutil registry failed This
message is accompanied by other message(s) providing details on the error.
Action: Correct the problem indicated by the other message(s). If possible, change
options to reduce required memory and/or take steps to increase memory
available to the process. Otherwise, report this error to Oracle Support Services.
ADVM-03115: an error occurred while attempting to disconnect from Oracle
Registry
Cause: Either the Oracle Registry service was unavailable or the Oracle Registry
configuration was incomplete/inaccurate.
ADVM-00501 to ADVM-11069 98-17
Action: Run ocrcheck to verify the Oracle Registry service is working properly. If
the cause of the problem is unclear, contact Oracle Support Services.
ADVM-03117: unable to verify if the hostnames provided are part of the cluster
Cause: Could not obtain information about the cluster.
Action: Run crs_stat to verify health of CSS.
ADVM-03118: cannot obtain the node number of host string via CSS or the Oracle
Registry
Cause: Could not determine the node number for the specified host.
Action: Verify that the specified host is a member of this cluster.
ADVM-03119: Incorrect data format in file 'number'.
Cause: The file data was not in the expected format.
Action: Contact Oracle Support Services.
ADVM-03120: Note: Reported snapshot space usage is inaccurate.
Cause: The snapshot storage calculated was not expected.
Action: No action is required. To get a more accurate count, dismount the file
system on all nodes and run fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ADVM-03122: failed to create Oracle Registry ACFS key string string
Cause: Failed to create ACFS key(s) SYSTEM.ACFS and/or
SYSTEM.ACFS.Mounts in the Oracle Registry.
Action: Run ocrcheck to verify the Oracle Registry service is working properly.
Verify acfsutil is executed with operating system administrator privileges.
ADVM-03123: failed to create Oracle Registry ACFS key string because it already
exists
Cause: The Oracle Registry ACFS key already exists.
Action: Run ocrcheck to verify the Oracle Registry service is working properly.
ADVM-03124: failed to create Oracle Registry ACFS subkey because it already
exists
Cause: The Oracle Registry mounts subkey already exists.
Action: Run ocrcheck to verify the Oracle Registry service is working properly. If
the ACFS mount entry is in an inconsistent state delete it, then re-add it using
acfsutil with the registry option. If the problem persists, contact Oracle Support
Services.
ADVM-03125: error retrieving the volume using Oracle Registry key: string
Cause: Could not retrieve volume information from mount entry in the Oracle
Registry.
Action: Run ocrcheck to verify the Oracle Registry is working properly.
ADVM-03126: error retrieving the mount point using Oracle Registry key: string
Cause: Could not retrieve mount point information from mount entry in the
Oracle Registry.
Action: Run ocrcheck to verify the Oracle Registry is working properly.
ADVM-03127: error retrieving the mount options using Oracle Registry key: string
Cause: Could not retrieve mount options from mount entry in the Oracle Registry.
98-18 Oracle Database Error Messages
Action: Run ocrcheck to verify the Oracle Registry is working properly.
ADVM-03128: error retrieving the version using Oracle Registry key: string
Cause: Could not retrieve the version for mount entry in the Oracle Registry.
Action: Run ocrcheck to verify the Oracle Registry is working properly.
ADVM-03129: error retrieving the nodes list using Oracle Registry key: string
Cause: Could not retrieve the nodes list for mount entry in the Oracle Registry.
Action: Run ocrcheck to verify the Oracle Registry is working properly.
ADVM-03133: The Oracle Registry returned the following error while attempting
to access the security attributes of key string: string
Cause: is unclear, contact Oracle Support Services.
Action: Correct the problem identified by the other message(s). If the
ADVM-03134: An error occurred while accessing Oracle Registry for a delete mount
point operation. string
Cause: Could not retrieve data from the Oracle Registry. This message is
accompanied by other message(s) providing details on the error.
Action: Correct the problem indicated by the other message(s). If the cause of the
problem is unclear, contact Oracle Support Services.
ADVM-03135: unable to locate mount point string in Cluster Ready Services
Cause: An attempt to access the ACFS mount point failed because the mount
point information could not be retrieved from CRS.
Action: Verify the mount point is registered with CRS using the 'acfsutil registry
<device>' commands.
ADVM-03136: unable to locate volume string in Cluster Ready Services
Cause: An attempt to access the ASM volume failed because the volume
information could not be retrieved from CRS.
Action: Verify the volume is registered with CRS using the 'acfsutil registry
<device>' commands.
ADVM-03137: Multiple entries exist for the mount point string. Rerun the
command with the volume name.
Cause: Could not locate unique entry for mount point in the Oracle Registry.
Action: Retry acfsutil registry with volume name.
ADVM-03138: failed to create and set Oracle Registry ACFS mount info key string
Cause: Could not create and set a mount info key in the Oracle Registry.
Action: Run ocrcheck to verify the Oracle Registry is working properly.
ADVM-03139: error retrieving the disk group name using Oracle Registry key:
string
Cause: Could not retrieve the disk group name from the mount entry in the
Oracle Registry.
Action: Run ocrcheck to verify the Oracle Registry is working properly.
ADVM-03140: error retrieving the volume name using Oracle Registry key: string
Cause: Could not retrieve the volume name from the mount entry in the Oracle
Registry.
ADVM-00501 to ADVM-11069 98-19
Action: Run ocrcheck to verify the Oracle Registry is working properly.
ADVM-03141: unable to open device string
Cause: The device could not be opened.
Action: Check the diskgroup is mounted and the specified volume is enabled.
ADVM-03142: Failed to retrieve the diskgroup and volume name for device string.
See the attached error.
Cause: Possible internal error.
Action: Check the attached error. If not serviceable, contact Oracle.
ADVM-03143: The specified mount point does not exist and therefore cannot be
deleted.
Cause: The Oracle Registry has not been configured for ACFS or the specified
mount point does not exist.
Action: Run "acfsutil registry" to list out the available ACFS mount points.
ADVM-03145: unable to remove ACFS volume string from Oracle Registry
Cause: Could not remove volume from Oracle Registry.
Action: Verify the volume exists in the Oracle Registry using the acfsutil registry
command.
ADVM-03146: Warning: The ACFS mount point group ownership cannot be
re-initialized in the Oracle Registry. The registry is initialized from the ACFS
control device on first use, and may have changed ownership since then.
Current Key Ownership: string
Cause: An attempt was made to re-initialize the ACFS mount point group
ownership in the Oracle Registry. This may be because the ACFS control device
/dev/ofsctl or /dev/acfsctl has changed owners.
Action: Re-initializing the ACFS mount point group ownership in the Oracle
Registry is not supported.
ADVM-03147: invalid ACFS file identifier provided
Cause: The ACFS file identifier provided by the user had an illegal value.
Action: Re-enter a number other than 0 or -1.
ADVM-03148: ioctl call to obtain pathname associated with file id number failed
Cause: An internal ioctl operation to map from an ACFS file identifier to a
pathname failed. This message is accompanied by other message(s) providing
details on the error.
Action: Correct the problem indicated by the other message(s). If the cause of the
problem is unclear, contact Oracle Support Services.
ADVM-03149: constructed pathname is too large
Cause: The length of the pathname being constructed has exceeded the system
limit of %d characters. This may be due to changes in the file system namespace
while the command is running.
Action: Try the command again. If the problem persists, contact Oracle Support
Services.
ADVM-03151: The ACFS file identifier provided is not associated with a user file
or directory.
Cause: The ACFS file identifier, although valid, was not for a user file or directory.
98-20 Oracle Database Error Messages
Action: None. There is no pathname associated with this ACFS file identifier.
ADVM-03152: The ACFS file identifier provided is invalid for the mountpoint
specified.
Cause: The ACFS file identifier was not a valid identifier for the mountpoint
specified.
Action: Verify that the correct ACFS file identifier and mountpoint were specified.
ADVM-03153: The file system name space has changed and a pathname cannot be
obtained.
Cause: The ACFS file identifier was valid, but could not be used to obtain a full
file pathname.
Action: Verify that the correct ACFS file identifier and mountpoint were specified.
ADVM-03154: Failed to determine the full pathname. Too many directory levels.
Cause: acfsutil has received information from the operating system that it could
not process fully.
Action: Report this error to Oracle Support Services.
ADVM-03157: unsupported file type for string, not a mount point
Cause: An invalid entry was passed on the command line.
Action: The acfsutil info acfs command requires that the input be a mount point.
ADVM-03158: unsupported file type for string, not a mount point or a file
Cause: An invalid entry was passed on the command line.
Action: The acfsutil size command requires that the input be a mount point or a
file.
ADVM-03161: Device : string : Mount Point : string already exists in the Oracle
Registry
Cause: This entry has already been added to the Oracle Registry.
Action: None
ADVM-03162: Warning: The file system was resized, but an error occurred while
resizing the ADVM volume. File system size now number MB, volume size
number MB.
Cause: An error occurred during ADVM volume resize.
Action: Reissue the resize command.
ADVM-03165: Unable to add the file system on device string to the ACFS registry.
It is currently managed by CRS.
Cause: The file system is currently managed by CRS and a file system cannot be
managed by both CRS and the ACFS registry.
Action: Remove the file system resource from CRS or continue to use CRS to
manage the file system.
ADVM-03166: Unable to add a STOP_DEPENDENCY to the ACFS registry for
device string.
Cause: The ACFS registry resource could not be updated.
Action: Verify the ACFS registry state ('crsctl stat res ora.registry.acfs -p')
ADVM-00501 to ADVM-11069 98-21
ADVM-03167: Unable to remove the STOP_DEPENDENCY for device string from
the ACFS registry.
Cause: The ACFS registry resource could not be updated.
Action: Verify the ACFS registry state ('crsctl stat res ora.registry.acfs -p')
ADVM-03168: Internal error: string number
Cause: An Oracle internal error.
Action: Contact Oracle Support Services.
ADVM-03169: Unable to set log file size.
Cause: The ACFS driver was unable to set the log file size.
Action: Check the log file to see the reason of failure.
ADVM-03170: Minimum log file size is number.
Cause: The ACFS driver was unable to set the log file size.
Action: Log file size has to be bigger than or equal to the minimum size.
ADVM-03171: Insufficient contiguous free ASM Diskgroup space. Check the ASM
alert log.
Cause: ADVM could not resize the volume because ASM did not have enough
contiguous free diskgroup storage.
Action: Increase the free space in the diskgroup. Check the ASM alert log.
ADVM-03172: ADVM is busy with Mirror recovery. Try again later.
Cause: ADVM could not resize the volume because it is recovering the mirrored
volumes.
Action: Try again later. The system console log will contain mirror recovery
started and completed messages. For example: [Oracle ADVM] Mirror recovery
for volume asm/volume-name started. [Oracle ADVM] Mirror recovery for
volume asm/volume-name completed.
ADVM-03173: ADVM or ASM is unable to resize the volume. Check the ASM alert
log.
Cause: ADVM or ASM is unable to resize the volume.
Action: Check the ASM alert log.
ADVM-03174: The Oracle ASM Dynamic Volume Manager (Oracle ADVM)
compatibility attribute for the disk group is less than 11.2.0.3.0.
Cause: The ADVM compatibility attribute for the disk group was not set to
version 11.2.0.3.0 or higher to allow the creation of a read/write snapshot.
Action: Use the Oracle ASM Configuration Assistant (ASMCA) tool or the SQL
statement ALTER DISKGROUP to upgrade COMPATIBLE.ADVM attribute.
ADVM-03177: maximum log file size cannot exceed number MB
Cause: The ACFS driver was unable to set the log file size.
Action: Retry the command with a log file size that is smaller than the maximum
size.
ADVM-03178: unable to delete snapshot string while cluster is in rolling migration
Cause: The cluster was in rolling migration. Snapshot deletions are not allowed
during rolling migration.
Action: Complete the rolling migration and then delete the snapshot.
98-22 Oracle Database Error Messages
ADVM-03179: unable to create snapshot 'string' while cluster is in rolling migration
Cause: The cluster was in rolling migration. Snapshot creations are not allowed
during rolling migration.
Action: Complete the rolling migration and then create the snapshot.
ADVM-03180: Unable to obtain ASM volume device information for 'string'
Cause: The operation for retrieval of ASM volume device information failed. This
message is accompanied by other message(s) providing details on the error.
Action: Correct the problem indicated by the other message(s). If the solution is
not clear, contact Oracle Support Services.
ADVM-03185: Unable to obtain ASM volume extent information for string
Cause: The operation for retrieval of ASM volume extent information failed. This
message is accompanied by other message(s) providing details on the error.
Action: Correct the problem indicated by the other message(s). If the solution is
not clear, contact Oracle Support Services.
ADVM-03186: Supplied ACFS file offset value is greater than the file allocation
size of number
Cause: The supplied file offset value in bytes supplied must be smaller than the
file allocation size.
Action: 'acfsutil file info filename' provides the file allocation size. Choose a
smaller value.
ADVM-03187: Extent number (mirror number) is not in use.
Cause: Informational
Action: None
ADVM-03203: Invalid snap command.
Cause: An invalid entry was passed on the command line.
Action: Use a valid 'acfsutil snap' command combination. Valid commands are
'acfsutil snap create', 'acfsutil snap delete', and 'acfsutil snap info'
ADVM-03204: Snapshot 'string' is already read-only.
Cause: A request was made to convert a snapshot to be read-only but the
snapshot was already read-only.
Action: None
ADVM-03205: Snapshot 'string' is already read-write.
Cause: A request was made to convert a snapshot to be read-write but the
snapshot was already read-write.
Action: None
ADVM-03206: The ADVM compatibility attribute for the diskgroup was below the
required version (string) for the 'acfsutil snap convert' command.
Cause: The ADVM compatibility attribute has not been upgraded to a version
that supports the 'acfsutil snap convert' command.
Action: Use the ASMCA tool or the SQL ALTER DISKGROUP statement to
upgrade COMPATIBLE.ADVM attribute to the specified version.
ADVM-03207: invalid combination of options
ADVM-00501 to ADVM-11069 98-23
Cause: The 'acfsutil snap convert' command was passed an invalid option
combination which included both the -r and -w options.
Action: Remove either the -r or -w option from the 'acfsutil snap convert'
command.
ADVM-03208: The /r option is not supported on this operating system
Cause: The 'acfsutil snap convert /r' option was specified. This functionality
requires a minimum operating system version of Windows Server 2008 R2.
Action: Upgrade operating system to Windows Server 2008 R2 or use the 'acfsutil
snap create' command to create a read-only snapshot.
ADVM-03212: There are too many snapshots for the file system associated with
string. Only number are allowed. Reduce the number of snapshots before
proceeding.
Cause: An attempt to create more than the maximum allowed number of active
snapshots was rejected.
Action: Delete a snapshot before creating a new one.
ADVM-03213: Creation of a snapshot failed due to presence of snapshots that
prevent this functionality.
Cause: A snapshot creation which specified a parent snapshot was not processed
because of compatibility issues with existing snapshots. Possible causes include: 1)
Snapshots of the file system were found that were created before ADVM
compatibility attribute was set to 12.1. 2) Snapshots of the file system were found
that were created after ADVM compatibility was set to 12.1 but while 11.2
snapshots existed.
Action: Delete all snapshots associated with the file system and retry the
command.
ADVM-03214: The Oracle ASM Dynamic Volume Manager (Oracle ADVM)
compatibility attribute for the disk group is less than 12.1.
Cause: The ADVM compatibility attribute for the disk group was not set to
version 12.1 or higher to allow the creation of a snapshot with a parent snapshot.
Action: Use the Oracle ASM Configuration Assistant (ASMCA) tool or the SQL
statement ALTER DISKGROUP to upgrade COMPATIBLE.ADVM attribute.
ADVM-03216: The ADVM compatibility attribute for the diskgroup was below the
required version (string) for unlimited volume expansions.
Cause: A request to resize the ACFS file system failed because the volume
expansion limit was reached. This limit was hit because the ADVM compatibility
attribute associated with the diskgroup was too low.
Action: Use the ASMCA tool or the SQL ALTER DISKGROUP statement to
upgrade the COMPATIBLE.ADVM attribute to the specified version.
ADVM-03300: unable to set tag name on file string
Cause: The ACFS driver was unable to complete the request.
Action: Verify memory or storage resources are sufficient.
ADVM-03301: unable to unset tag name on file string
Cause: The ACFS driver was unable to complete the request.
Action: Verify memory or storage resources are sufficient.
ADVM-03302: tag name syntax invalid or length too long
98-24 Oracle Database Error Messages
Cause: Tag name contains invalid characters or has too many characters.
Action: Change tag name to use valid characters or shorten the tag name.
ADVM-03303: invalid combination of arguments
Cause: The acfsutil tag info -t or -r arguments work only on file pathnames.
Action: Remove the -t or -r arguments from the ofsutil tag info command.
ADVM-03304: Unable to open mount point string. Verify that the mount point
exists.
Cause: Mount point cannot be opened to display tag name information.
Action: Verify that the mount point exists and is accessible before retrying the tag
info command.
ADVM-03305: unable to retrieve all tag names for string
Cause: Unable to return the full list of tag names.
Action: Verify there is sufficient memory resources available.
ADVM-03306: tag name does not exist in file string
Cause: Cannot unset a tag name on a file that does not exist.
Action: Verify the tag name to unset is correct.
ADVM-03308: The ADVM compatibility attribute for the diskgroup must be set to
version 11.2.0.2.0 to allow the acfsutil repl and tag commands.
Cause: The ADVM compatibility attribute has not been upgraded to version
11.2.0.2.0 or beyond.
Action: Use the ASMCA tool or the SQL ALTER DISKGROUP statement to
upgrade COMPATIBLE.ADVM attribute.
ADVM-03309: path name string does not resolve to an ACFS file system
Cause: A path name supplied on an 'acfsutil tag' command did not resolve to an
ACFS file system.
Action: Remove the non-ACFS path name from the 'acfsutil tag' command.
ADVM-03310: amount of change since mount: number MB
Cause: Informational
Action: None
ADVM-03313: unable to collect ACFS statistics for mount point string
Cause: 'acfsutil info fs -s' was unable to communicate with the ACFS driver.
Action: Verify that the file system is online and that the ADVM/ACFS drivers are
loaded and running.
ADVM-03314: interval cannot exceed number seconds
Cause: Statistics interval exceeded maximum number of seconds per interval.
Action: Select an interval that is less than or equal to 2592000 seconds and retry
"acfsutil info fs -s".
ADVM-03315: count cannot exceed number
Cause: Number of statistics intervals exceeded maximum number allowed.
Action: Select a total count that is less than or equal to 2^63-1 and retry "acfsutil
info fs -s".
ADVM-00501 to ADVM-11069 98-25
ADVM-03316: interval must be a positive integer
Cause: A zero or negative integer was provided.
Action: Provide a positive integer for the statistics interval.
ADVM-03317: unable to set tag on file "string" because its tag name storage is full
Cause: The limit of the file's tag name storage has been reached.
Action: Remove any unused tags on this file and try the command again.
ADVM-03318: unable to set tag name "string" because this name is reserved
Cause: The tag name specified is reserved.
Action: Choose another tag name which is not reserved.
ADVM-03319: Set tag on file: string
Cause: Informational
Action: None
ADVM-03320: Removing tag(s) on file: string
Cause: Informational
Action: None
ADVM-03321: The ADVM compatibility attribute for the diskgroup is below the
required version (string) for the 'acfsutil tag' commands.
Cause: The ADVM compatibility attribute has not been upgraded to a version
that supports tagging.
Action: Use the ASMCA tool or the SQL ALTER DISKGROUP statement to
upgrade COMPATIBLE.ADVM attribute to the specified version.
ADVM-03322: The ADVM compatibility attribute for the diskgroup is below the
required version (string) for the 'acfsutil repl' commands.
Cause: The ADVM compatibility attribute has not been upgraded to a version
that supports replication.
Action: Use the ASMCA tool or the SQL ALTER DISKGROUP statement to
upgrade COMPATIBLE.ADVM attribute to the specified version.
ADVM-03323: stringc option requires the stringt option
Cause: The 'c' option was specified without the 't' option. The 'c' option invokes
case insensitive substring matching on the tag names specified using the 't' option.
Action: To use the 'c' option, add the 't' option to specify a tag.
ADVM-03324: Unable to obtain metric data for string
Cause: An internal ioctl operation to access metric data from ACFS file system
failed. This message is accompanied by other message(s) providing details on the
error.
Action: Correct the problem indicated by the other message(s). If the cause of the
problem is unclear, contact Oracle Support Services.
ADVM-03344: Error, strings option with repetition interval applied to multiple file
systems.
Cause: A request to report file system statistics periodically was rejected because
it applied to multiple file systems. A single file system must be specified explicitly
when supplying the 's' option with a time interval.
98-26 Oracle Database Error Messages
Action: Reissue the request specifying a single file system or omitting the
repetition interval.
ADVM-03450: Continue to panic the cluster [y|n] ?
Cause: The 'acfsutil panic' command was issued to panic the cluster.
Action: Respond Y(yes) to proceed or N(no) to cancel.
ADVM-03451: Continue to panic the system [y|n] ?
Cause: The 'acfsutil panic' command was issued to panic the system.
Action: Respond Y(yes) to proceed or N(no) to cancel.
ADVM-03452: failed to move file or directory from string to string
Cause: An attempt to rename a file or directory failed because the target was an
existing, populated directory or the user permissions were insufficient to perform
the operation.
Action: Retry the operation after removing the target files or correcting the
permissions.
ADVM-03500: Unable to access kernel persistent log entries.
Cause: Could not get or set persistent log configuration data.
Action: Make sure that the Oracle kernel drivers are loaded/started (run
'acfsdriverstate loaded'). If loaded/started, make sure that you have
root/administrator privileges.
ADVM-03501: The 'query' option may not be used with any other options.
Cause: Additional options to 'query' were specified on the command line.
Action: Do not use any other options with the 'query' option.
ADVM-03502: The specified maximum log file size is less than number MB or is
greater than number MB.
Cause: An invalid log file size was entered on the command line.
Action: Specify a value equal to or greater than the minimum size and equal to or
less than the maximum size.
ADVM-03503: The specified interval is less than number seconds.
Cause: An invalid interval value was entered on the command line.
Action: Enter an interval value equal to or greater than the minimum.
ADVM-03504: An invalid high water level value (number percent) was specified.
Cause: The high water level must be greater than the low water level and less
than 100 percent.
Action: Enter a valid high water level value.
ADVM-03505: An invalid low water level value (number percent) was specified.
Cause: The low water level must be greater than zero and less than the high water
level.
Action: Enter a valid low water level value.
ADVM-03506: The selected percentage does not generate an even integer. Changing
to number percent.
Cause: The specified percentage of the buffer size generates a remainder.
Action: None. Informational.
ADVM-00501 to ADVM-11069 98-27
ADVM-03507: The specified buffer size is less than number KB or is greater than
number KB.
Cause: An invalid buffer size value was entered on the command line."
Action: Enter a value equal to or greater than the minimum or equal to or less
than the maximum size.
ADVM-03508: The specified maximum number of log files is less than number or
greater than number.
Cause: An invalid maximum number of log files was entered on the command
line.
Action: Specify a value equal to or greater than the minimum and equal to or less
than the maximum.
ADVM-03509: string is not a Grid infrastructure home.
Cause: An invalid Grid infrastructure home was entered on the command line.
Action: Specify a valid Grid infrastructure home.
ADVM-03510: There are more log files on the system than are being configured.
Removing the oldest files.
Cause: A new, lower, maximum number of allowable OKS persistent log files was
configured and there are currently more log files on the system. Deleting the oldest
files."
Action: None. Informational.
ADVM-03511: Deleting string.
Cause: A log file was deleted to satisfy the new configuration.
Action: None. Informational.
ADVM-03512: Renaming string to string.
Cause: A log file was renamed to place it in time modified sequential order.
Action: None. Informational.
ADVM-03513: The OKS persistent log configuration settings cannot be queried.
Cause: The OKS persistent log was not running.
Action: Start the log with 'acfsutil plogconfig -d <gridhome>'.
ADVM-03514: The directory 'string' can not be converted to an absolute path.
Cause: A directory name was specified that could not be converted to an absolute
path. The name was either an invalid relative path or, on Windows, included an
invalid drive letter.
Action: Specify the directory name in the form of an absolute path. On Windows,
the absolute path includes the drive letter.
ADVM-03528: failed to determine Oracle Base
Cause: The operation to retrieve the Oracle Base location failed. This message is
accompanied by other message(s) providing details on the error.
Action: Correct the problem indicated by the other message(s). If the solution is
not clear, contact Oracle Support Services.
ADVM-03529: Warning: The 'd' option was specified with an argument, which is no
longer used - argument ignored.
98-28 Oracle Database Error Messages
Cause: 'acfsutil plogconfig' now gets the log location internally. The specified log
location was ignored and the command continued using the internally derived
location.
Action: None
ADVM-03530: The 'terminate' option may not be used with any other options.
Cause: Conflicting options were specified on the command line.
Action: Do not use any other options with the 'terminate' option.
ADVM-03539: Base time stamp not found in log file.
Cause: Informational. The likely cause is that the running OKS driver is an older
version that does not support time stamp conversion.
Action: None
ADVM-03540: The specified interval is greater than number seconds.
Cause: An invalid interval value was entered on the command line.
Action: Enter an interval value equal to or less than the maximum.
ADVM-03541: The symbolic link 'string' to 'string' cannot be created.
Cause: Likely, the link name was a non-empty directory. OKS persistent logging
was started but no symbolic was created to the target directory.
Action: If a symbolic link is desired, delete the link target and its contents and
reissue the command.
ADVM-03542: The specified OKS log directory 'string' is invalid because it is NFS
mounted.
Cause: The specified logging directory was NFS mounted.
Action: Enter a node local location for the OKS log.
ADVM-03543: The OKS persistent log is not active.
Cause: The OKS persistent log was not running.
Action: Start the log with 'acfsutil plogconfig -d [log_dir]'.
ADVM-03544: Directory 'string' exists as a file.
Cause: An OKS persistent log directory could not be created because it exists as a
file.
Action: Either delete the file or choose another directory name.
ADVM-03602: Plug-in is already enabled on 'string'
Cause: An attempt was made to enable the plug-in when it is already enabled.
Action: First disable the plug-in then retry the command.
ADVM-03603: Plug-in is not enabled on 'string'
Cause: A plug-in command was attempt when the plug-in is not enabled.
Action: Enable the plug-in and then retry the command.
ADVM-03604: Unable to perform plug-in operation on 'string'
Cause: The plug-in operation failed. This message is accompanied by other
message(s) providing details on the error.
Action: Correct the problem indicated by the other message(s). If the solution is
not clear, contact Oracle Support Services.
ADVM-00501 to ADVM-11069 98-29
ADVM-03610: Invalid plug-in metric type: string
Cause: An invalid plug-in metric type was specified.
Action: Enter a valid metric type from the following list: "acfsmetric1"
ADVM-03611: Invalid interval specified.
Cause: An invalid interval was specified.
Action: Enter a valid interval between 1 and 3600 seconds.
ADVM-03612: Unable to retrieve list of plug-in enabled tags.
Cause: ACFS was unable to retrieve the list of tags for which the plug-in is
collecting metrics. This message is accompanied by other message(s) providing
details on the error.
Action: Correct the problem indicated by the other message(s). If the solution is
not clear, contact Oracle Support Services.
ADVM-03613: Unable to write plug-in config file.
Cause: ACFS was unable to write the plug-in config file to disk.
Action: Try the command again. If the problem persists, contact Oracle Support
Services.
ADVM-03614: Plug-in cannot be enabled for more than number tags.
Cause: An attempt was made to enable the plug-in for more than the maximum
allowed number of tags.
Action: Enable plug-in with fewer tags.
ADVM-03615: An error occured when copying the list of tags.
Cause: This is an internal error.
Action: Try the command again. If the problem persists, contact Oracle Support
Services.
ADVM-03621: missing plug-in metric type
Cause: No plug-in metric type was specified.
Action: Enter a valid metric type from the following list: "acfsmetric1"
ADVM-03623: unable to modify the ACFS registration for mount point 'string'
Cause: Could not modify the ACFS registration for the specified mount point.
Action: Examine the accompanying error messages and respond accordingly. If
the solution is not clear, contact Oracle Support Services.
ADVM-03624: unable to modify registration for ACFS volume 'string'
Cause: Could not modify the ACFS registration for the ACFS volume.
Action: Examine the accompanying error messages and respond accordingly. If
the solution is not clear, contact Oracle Support Services.
ADVM-03626: invalid combination of -C and -f options
Cause: The 'acfsutil log' command was issued with both the -f and -C options.
This is a conflict, because the log file names are pre-specified for -C and may not
be specified using -f.
Action: Re-issue the 'acfsutil log' command with only the desired option. With -C,
the log files will be generated in the persistent log directory in the form
yymmddhhmmss.log. With -f the specified name will be used.
98-30 Oracle Database Error Messages
ADVM-03627: logging behavior change specified with cluster option
Cause: The 'acfsutil log' command was issued with both the -C option and and an
option that modifies the logging behavior.
Action: Re-issue the 'acfsutil log' command without the -C option to modify the
ACFS logging behavior. To create logs on all cluster nodes, issue 'acfsutil log -C'
with no other options.
ADVM-04001: Failed to open path string. Verify that string exists.
Cause: Path could not be opened.
Action: Verify the path is accessible before retrying.
ADVM-04002: unable to allocate a buffer
Cause: A request for process virtual memory by acfsdismount command failed.
This message is accompanied by other message(s) providing details on the error.
Action: Correct the problem indicated by the other message(s). If possible, change
options to reduce required memory and/or take steps to increase memory
available to the process. Otherwise, report this error to Oracle Support Services.
ADVM-04011: Failed to open volume string. Verify that string exists.
Cause: Volume could not be opened.
Action: Verify the ASM instance is operational and the volume is enabled and
accessible before retrying.
ADVM-04013: acfsdismount /all operation did not complete. Unable to retrieve a
mount point from the list of active ACFS file systems to dismount. It is possible
that not all file systems were dismounted.
Cause: Failed to obtain the next file system to dismount.
Action: Use acfsmountvol to determine if there are any file systems still mounted
and reissue 'acfsdismount /all' if necessary.
ADVM-04032: removing administrative network share for mount point string at
share name 'string'
Cause: Informational
Action: None
ADVM-04033: administrative network share 'string' does not share mount point
string as expected
Cause: Attempted to remove the administrative network share associated with
the specified ACFS mount point, but the network share does not share the
specified ACFS mount point as expected.
Action: Examine the network share at the specified share name. If the network
share shares an unmounted ACFS file system, manually remove the network share
using 'net share <share name> /delete'
ADVM-04034: administrative network share for mount point string does not exist at
share name 'string'
Cause: Informational
Action: None
ADVM-04035: retrieving information for administrative network share 'string'
failed
ADVM-00501 to ADVM-11069 98-31
Cause: While removing the administrative network share associated with the
specified ACFS mount point, failed to retrieve information on the administrative
network share. This message is accompanied by other messages providing details
on the error.
Action: Check for a network share at the specified share name. If a network share
exists at the specified share name and it shares an unmounted ACFS file system,
manually remove the network share using 'net share <share name> /delete'
ADVM-04036: removing administrative network share for mount point string at
share name 'string' failed
Cause: Failed to remove the administrative network share associated with the
specified ACFS mount point. This message is accompanied by other messages
providing details on the error.
Action: Manually remove the administrative network share at the specified share
name using 'net share <share name> /delete'
ADVM-04037: could not remove administrative network share for mount point
string at share name 'string'
Cause: Failed to remove the administrative network share associated with the
specified ACFS mount point. This message is accompanied by other messages
providing details on the error.
Action: Correct the error indicated by the accompanying messages.
ADVM-04038: Volume string is still mounted. Dismount will complete as soon as
activity ceases on the file system.
Cause: At the conclusion of the file system dismount request, the file system was
still mounted. This could be a result of open files on the mount point. The
dismount will finish as soon as activity ceases on the file system.
Action: To force dismount to complete, terminate any processes or applications
that are using the file system.
ADVM-04058: Ignoring unsupported ACFS command option: 'string'
Cause: An unsupported 'umount.acfs' command option was specified.
Action: No action required. The unmount will proceed without the option.
ADVM-04150: unable to retrieve mount point information from the ACFS driver
Cause: During unmount processing, an attempt to retrieve mount point
information from the ACFS driver failed.
Action: Verify the mount point is a valid ACFS file system before retrying the
unmount command. If the problem persists, contact Oracle Support Services.
ADVM-04151: unmount of mount point string failed
Cause: of the problem is unclear, contact Oracle Support Services.
Action: Correct the problem indicated by the other message(s). If the
ADVM-05001: must specify 'primary' or 'standby'
Cause: Command syntax requires 'primary' or 'standby' argument.
Action: At command line, indicate primary or standby for replication command.
ADVM-05002: must provide an Oracle Net alias to the primary replication site
Cause: The Oracle Net alias to connect to the primary replication site was not
specified.
98-32 Oracle Database Error Messages
Action: Provide Oracle Net alias to connect to the primary replication site.
ADVM-05003: must provide a primary mount point
Cause: The mount point on the replication primary site for the file system to be
replicated was not provided.
Action: Provide an existing mount point on the primary site for the file system to
be replicated.
ADVM-05004: cannot allocate a list of tag names
Cause: A request for process virtual memory failed. This message is accompanied
by other message(s) providing details on the error.
Action: Correct the problem indicated by the other message(s). If possible, change
options to reduce required memory and/or take steps to increase memory
available to the process. Otherwise, report this error to Oracle Support Services.
ADVM-05005: invalid tag name: string
Cause: User specified a tag name that has incorrect syntax.
Action: See the platform specific Oracle documentation for correct syntax for
ACFS tag names.
ADVM-05006: unable to initialize replication process data structures
Cause: Failed to determine path names for replication directories.
Action: Verify the specified mount point is an ACFS file system.
ADVM-05007: cannot initialize interrupt signal handler
Cause: The system could not initialize the mechanism to handle interrupts.
Action: Contact Oracle Support Services.
ADVM-05008: cannot lock file string to serialize ACFS replication commands
Cause: of the problem is unclear, contact Oracle Support Services.
Action: Correct the problem indicated by the other message(s). If the
ADVM-05009: ACFS replication initialization is already in progress.
Cause: Initialization was in progress on the replication site.
Action: Wait for the other initialization on replication site to complete.
ADVM-05010: ACFS replication initialization is still in progress.
Cause: The command cannot be run until replication initialization completes.
Action: Monitor initialization progress with the 'acfsutil repl info' command.
ADVM-05011: cannot open directory: string
Cause: of the problem is unclear, contact Oracle Support Services.
Action: Correct the problem indicated by the other message(s). If the
ADVM-05012: ACFS replication is already initialized.
Cause: ACFS replication has already been initialized on this system.
Action: Initialization cannot be undone unless replication is terminated or the file
system is reformatted.
ADVM-05013: ACFS replication cannot be initialized.
Cause: of the problem is unclear, contact Oracle Support Services.
Action: Correct the problem indicated by the other message(s). If the
ADVM-00501 to ADVM-11069 98-33
ADVM-05014: cannot verify replication configuration
Cause: of the problem is unclear, contact Oracle Support Services.
Action: Correct the problem indicated by the other message(s). If the
ADVM-05015: cannot cleanup replication directories
Cause: The application failed to cleanup from a previous replication instantiation.
Action: Verify user permissions and that the replication directory is available.
ADVM-05016: cannot update replication configuration with new trace level
Cause: The application was unable to communicate with the ACFS driver.
Action: Verify that the ADVM/ACFS drivers are loaded and running.
ADVM-05017: cannot create file: string
Cause: The application failed to create the specified file. This message is
accompanied by other message(s) providing details on the error.
Action: Correct the problem indicated by the other message(s). If the solution is
not clear, contact Oracle Support Services.
ADVM-05018: cannot get primary ADVM volume information for string
Cause: The application failed to get the ADVM volume path for the mounted
ACFS file system.
Action: Verify that the file system is mounted and of type ACFS.
ADVM-05019: cannot allocate space for the ADVM volume path
Cause: A request for process virtual memory failed. This message is accompanied
by other message(s) providing details on the error.
Action: Correct the problem indicated by the other message(s). If possible, change
options to reduce required memory and/or take steps to increase memory
available to the process. Otherwise, report this error to Oracle Support Services.
ADVM-05020: cannot start replication daemons
Cause: CRS has failed to start the replication daemons.
Action: Verify that CRS is running. Check the CRS logs to determine why the
replication daemons failed to start.
ADVM-05021: cannot stop replication daemons
Cause: CRS has failed to stop the replication daemons.
Action: Verify that CRS is running. Check the CRS logs to determine why the
replication daemons failed to stop.
ADVM-05022: internal CRS error
Cause: The application failed to initialize communication with CRS.
Action: Verify that CRS is running. Check the CRS logs to determine why the
replication daemons failed to start.
ADVM-05023: error checking for file: string
Cause: Informational
Action: None
ADVM-05024: The standby replication site is initialized. ACFS replication will
begin.
Cause: Informational
98-34 Oracle Database Error Messages
Action: None
ADVM-05025: waiting for the standby replication site to initialize
Cause: Informational
Action: None
ADVM-05026: caught interrupt; ACFS replication initialization is shutting down.
Cause: Informational
Action: None
ADVM-05027: cannot remove file: string
Cause: File system was not accessible.
Action: Verify the ASM instance is operational and the state of the file system
using 'acfsutil info fs' before retrying the command.
ADVM-05028: cannot obtain current time for events log
Cause: The application failed to get the current time for logging.
Action: Contact Oracle Support Services.
ADVM-05029: cannot write to the events log
Cause: The application failed to write to the specified file. This message is
accompanied by other message(s) providing details on the error.
Action: Correct the problem indicated by the other message(s). If the solution is
not clear, contact Oracle Support Services.
ADVM-05030: cannot clean up configuration file
Cause: Initialization failed and the configuration file created during failed
initialization could not be removed.
Action: Contact Oracle Support Services.
ADVM-05031: standby file system is not empty
Cause: The file system was not empty.
Action: Use an empty standby file system; either reformat the file system or
remove all files and directories under <standby mount point>/.
ADVM-05032: unable to determine user permissions
Cause: An error occurred attempting to acquire the user permissions. This
message is accompanied by other message(s) providing details on the error.
Action: Correct the problem indicated by the other message(s). Otherwise, report
this error to Oracle Support Services.
ADVM-05033: must provide a standby mount point
Cause: A mount point on the standby replication site was not provided.
Action: Provide an existing mount point with an empty file system on the
standby replication site.
ADVM-05034: cannot obtain path for directory: string
Cause: The application failed to locate the specified directory.
Action: Verify that the replication directory is available.
ADVM-05035: cannot open file for write: string
ADVM-00501 to ADVM-11069 98-35
Cause: The application failed to open the specified file. This message is
accompanied by other message(s) providing details on the error.
Action: Correct the problem indicated by the other message(s). If the solution is
not clear, contact Oracle Support Services.
ADVM-05036: cannot write to file: string
Cause: The application failed to write to the specified file. This message is
accompanied by other message(s) providing details on the error.
Action: Correct the problem indicated by the other message(s). If the solution is
not clear, contact Oracle Support Services.
ADVM-05037: cannot move file string to directory string
Cause: The application failed move the specified file.
Action: Verify that the replication directory is available.
ADVM-05038: cannot register Oracle Net service name
Cause: Unable to register the Oracle Net service name with the ASM instance.
Action: Verify the ASM instance is operational and the state of the file system
using 'acfsutil info fs' before retrying the command.
ADVM-05039: cannot unregister Oracle Net service name
Cause: Unable to unregister the Oracle Net service name from the ASM instance.
Action: Verify the ASM instance is operational and the state of the file system
using 'acfsutil info fs' before retrying the command.
ADVM-05040: cannot obtain Oracle Net service name from alias provided
Cause: Unable obtain the Oracle Net service name from the Oracle Net alias
provided on the command line.
Action: Verify that the Oracle Net alias exists and is properly formed.
ADVM-05041: Oracle Net service name is greater than string bytes
Cause: The Oracle Net service name specified for replication is greater than the
maximum allowed.
Action: Reduce the size of the Oracle Net service name being used for replication.
ADVM-05042: insufficient privileges to perform replication command.
Administrator access is required.
Cause: The caller does not have sufficient privileges to perform the replication
command.
Action: Execute the replication command from a user with administrator access.
ADVM-05043: insufficient privileges to perform replication command. ASM
administrator group access is required.
Cause: The caller does not have sufficient privileges to perform the replication
command.
Action: Execute the replication command from a user with ASM administrator
group access.
ADVM-05044: cannot obtain node name
Cause: Unable to get local node name through CRS.
Action: Verify that CRS is running.
98-36 Oracle Database Error Messages
ADVM-05045: invalid interval specified for replication statistics
Cause: The caller specified an invalid time interval for replication statistics.
Action: Verify the syntax of the time interval using 'acfsutil repl info' help flag and
retry.
ADVM-05046: invalid date range specified for replication statistics
Cause: The caller specified an invalid date range for replication statistics.
Action: Verify the syntax of the date range using 'acfsutil repl info' help flag and
retry.
ADVM-05047: time specified is in the future
Cause: The caller specified a date in the future.
Action: Verify the time specified is before the current time.
ADVM-05048: start time specified is newer than the end time specified
Cause: The caller specified a date range where the start time was more recent the
end time.
Action: Verify the start time is before the end time.
ADVM-05049: validating the remote connection
Cause: Informational
Action: None
ADVM-05050: remote connection cannot be established
Cause: The user name, password, or Oracle Net alias used to connect to the
remote site was not correct or the remote site was unreachable.
Action: Verify the connection information is correct and the status of the remote
site.
ADVM-05051: remote connection has been established
Cause: Informational
Action: None
ADVM-05052: standby replication site requires reinitialization
Cause: Initialization was unable to complete on the primary replication site and
left the standby replication site in an indeterminate state.
Action: On the standby replication site, run 'acfsutil repl terminate' and 'acfsutil
repl init' before retrying initialization on the the primary replication site.
ADVM-05053: replication's Oracle Net service name conflicts with the existing
ASM service name
Cause: The service name for replication specified in the Oracle Net alias conflicts
eith the Oracle Net service name that ASM uses.
Action: Review the Oracle Net alias for replication in tnsnames.ora and use a
different service name for the replication alias.
ADVM-05054: standby replication file system is mounted on more than one cluster
node
Cause: The standby replication file system was mounted on more than one node
in the cluster.
Action: Unmount the file system on all but one node on the standby replication
site and retry the initialization.
ADVM-00501 to ADVM-11069 98-37
ADVM-05055: invalid connection string for the primary replication site
Cause: The user name, password, or Oracle Net alias used to connect to the
primary replication site was not correct or was unreachable.
Action: Verify the connection information is correct and the status of the primary
replication site.
ADVM-05056: invalid connection string for the standby replication site
Cause: The user name, password, or Oracle Net alias used to connect to the
standby replication site was not correct or was unreachable.
Action: Verify the connection information is correct and the status of the standby
replication site.
ADVM-05058: command issued on the incorrect replication site
Cause: The command was issued on the incorrect replication site.
Action: Verify the command syntax. If issued on the primary file system, reissue
on the standby file system. If issued on the standby file system, reissue on the
primary file system.
ADVM-05059: ACFS replication not initialized
Cause: ACFS replication information cannot be retrieved as replication has not
been initialized.
Action: None
ADVM-05060: waiting for ACFS replication to terminate
Cause: Informational
Action: None
ADVM-05061: ACFS replication command interrupted
Cause: Informational
Action: None
ADVM-05062: cannot query CRS resource
Cause: The application failed to communicate with CRS.
Action: Verify that CRS is running. Check the CRS logs to determine why the CRS
resource is not responding.
ADVM-05063: cannot relocate CRS resource
Cause: The application failed to relocate CRS resource.
Action: Verify that CRS is running. Check the CRS logs to determine why the CRS
resource cannot be relocated.
ADVM-05064: the service name 'string' is not registered on the standby site
Cause: Possible causes include: 1.) Replication was not initialized on the standby
site. 2.) Mismatched service names. If the -c option is not used, the service name
specified in the alias for the standby file system did not match the service name
specified for the primary file system in the alias on the standby site. 3.) The alias
for the standby site referred to the wrong set of nodes.
Action: Possible actions include: 1.) Verify replication is initialized on the standby
site. 2.) Verify the service name used to connect to the standby site matches the one
registered on the standby site. Run 'lsnrctl status' on the standby site to verify. 3.)
Verify that the nodes listed in the standby alias have the standby file system
mounted.
98-38 Oracle Database Error Messages
ADVM-05065: cannot transfer files to the standby file system 'string'
Cause: Possible causes include: 1.) The standby mount point did not exist or was
not an ACFS file system. 2.) The standby file system was full.
Action: Possible actions include: 1.) Verify that the standby mount point exists
and is an ACFS file system. 2.) Verify that there is free space on the standby file
system.
ADVM-05066: ACFS replication is already paused
Cause: ACFS replication was paused by a previous call.
Action: None
ADVM-05067: cannot rename file string to string in directory string
Cause: The application failed to rename the specified file.
Action: Verify that the replication directory is available.
ADVM-05068: ACFS replication has not been paused
Cause: ACFS replication was not paused. Resume operation is not needed.
Action: None
ADVM-05069: ACFS replication update must specify at least one attribute
Cause: The command to update the replication configuration did not specify any
attributes to update.
Action: Specify at least one replication attribute to be updated.
ADVM-05070: command must be run on the primary replication site
Cause: 'acfsutil repl update' command was not run on the primary replication
site.
Action: Execute 'acfsutil repl update' on the primary replication site.
ADVM-05071: invalid username or password used to connect to the standby site
Cause: The username or password specified on the command line or in the wallet
was incorrect.
Action: Verify the username and password are correct when connecting to the
standby site.
ADVM-05072: cannot open events file string
Cause: Failed to open events log file.
Action: Verify the ASM instance is operational and the state of the file system
using 'acfsutil info fs' before retrying the command.
ADVM-05073: cannot query events log file
Cause: Failed to query events log file.
Action: Verify the ASM instance is operational and the state of the file system
using 'acfsutil info fs' before retrying the command.
ADVM-05075: cannot terminate replication
Cause: Failed to terminate replication.
Action: Verify the ASM instance is operational and the state of the file system
using 'acfsutil info fs' before retrying the command.
ADVM-05076: unable to determine CRS user/group
Cause: The application failed to determine CRS user and/or group.
ADVM-00501 to ADVM-11069 98-39
Action: Verify that CRS is running. Check the CRS logs to determine why the CRS
user and/or group cannot be determined.
ADVM-05077: could not complete replication synchronization
Cause: Failed to complete synchronization of primary and standby replication
sites.
Action: Verify the ASM instance is operational and the state of the file system
using 'acfsutil info fs' before retrying the command.
ADVM-05078: failed to synchronize primary and standby replication sites
Cause: Failed to synchronize replication sites.
Action: Verify the ASM instance is operational and the state of the file system
using 'acfsutil info fs' before retrying the command.
ADVM-05079: waiting for replication update to complete
Cause: Informational
Action: None
ADVM-05083: Initialization of the primary file system could not complete because
the standby is already configured for replication.
Cause: The standby file system was not expecting initialization data from this
primary. Possible causes include:
1. Stale replication state detected on standby file system from a previous
instantiation.
2. An incorrect replication standby site was supplied.
3. An incorrect replication standby file system was supplied.
Action: 1. Run 'acfsutil repl terminate' on the standby site for the standby file
system before retrying the initialization of the primary.
2. Verify the correct standby site is used.
3. Verify the correct standby file system is used.
ADVM-05084: The replication standby file system has been newly initialized and is
refusing files from the primary. The primary may need to be terminated and
newly initialized.
Cause: The standby file system was not expecting any data from the primary
except initialization data. A possible cause may be the standby file system was
terminated and newly initialized, but the primary was not.
Action: Verify the primary site and primary file system. Run 'acfsutil repl
terminate' on the primary site for the primary file system before retrying the
initialization of the standby.
ADVM-05085: cannot start replication because incompatible ACFS features already
exist
Cause: Failed to start replication: Either security or encryption or both is enabled
on the file system.
Action: Undo security or encryption or both, then try to initialize replication
again. To undo encryption and security respectively: acfsutil encr set -m
<mount-point> -u acfsutil sec prepare -m <mount-point> -u
ADVM-05086: listener is not running on the standby site
98-40 Oracle Database Error Messages
Cause: The listener was not started on the remote site or an incorrect node name
was specified in the standby alias definition.
Action: Verify the listener is started on the standby site. Check that the standby
alias contains the correct node names.
ADVM-05087: The event log does not cover the time range specifed.
Cause: The events log did not cover any portion of the time range specified in the
command.
Action: Change the time range or use an events log that covers the range
specified.
ADVM-05088: replicated file system size is below the minimum of stringG
Cause: An attempt was made to initialize replication on a file system that did not
have sufficient space.
Action: Resize the file system to at least the minimum size specified.
ADVM-05089: replication statistics cannot be queried on the standby site
Cause: An attempt was made to query the replication statistics on the standby
site.
Action: Query the replication statistics from the primary site.
ADVM-05090: interval is greater than string years
Cause: The interval specified was greater than the maximum allowed.
Action: Retry the command with a lower interval value.
ADVM-05091: The mount path specified exceeds the maximum length allowed on
this platform.
Cause: The specified mount path exceeded the maximum length on this platform.
Action: Use a valid mount path.
ADVM-05092: replicated file system free space is near the minimum threshold of
stringGB per active node, continuing with initialization
Cause: Initialization of replication was issued on a file system that is near the
minimum threshold of free space.
Action: Consider resizing the file system to allow for optimal replication
performance.
ADVM-05093: could not retrieve active node count on file system: string, error:
string
Cause: Could not get the number of nodes active on the specified file system.
Action: Verify at least one cluster node has the file system mounted, or address
the specified operating system dependent error code provided. If the solution is
not clear, contact Oracle Support Services.
ADVM-05094: replicated file system free space is below the minimum of stringGB
per active node, actual free space left: stringGB
Cause: An attempt was made to initialize replication on a file system that did not
have sufficient space.
Action: Resize the file system such that free space is at least the minimum size
specified.
ADVM-05158: Replication background processes are not running
ADVM-00501 to ADVM-11069 98-41
Cause: Replication background processes were stopped.
Action: Run 'acfsutil repl bg start <mountpoint>' to restart replication background
processes.
ADVM-05159: Last sync time with primary: string
Cause: Informational
Action: None
ADVM-05170: Cannot initialize replication while the cluster is in rolling migration
Cause: An attempt to initialize replication was rejected because the cluster was in
rolling migration. Replication initialization is not allowed during rolling
migration.
Action: Complete the rolling migration and then initialize replication.
ADVM-05171: Cannot terminate replication while the cluster is in rolling migration
Cause: An attempt to terminate replication was rejected because the cluster was in
rolling migration and the file system was mounted on more than one node.
Action: Either complete the rolling migration and then terminate replication, or
unmount this file system on the other nodes and then terminate replication.
ADVM-05172: Replication cannot be terminated because background processes are
not running.
Cause: Replication background processes were stopped and cannot finish
processing replication data.
Action: Run 'acfsutil repl bg start <mountpoint>' to restart replication background
processes and complete the apply of existing replication data, or run 'acfsutil repl
terminate standby immediate <mountpoint>' to terminate replication immediately
without applying the remaining replication data.
ADVM-05200: Stopping ACFS replication daemons on string
Cause: Informational
Action: None
ADVM-05201: Starting ACFS replication daemons on string
Cause: Informational
Action: None
ADVM-05202: ACFS replication daemons started successfully on string
Cause: Informational
Action: None
ADVM-05203: ACFS replication daemons stopped successfully on string
Cause: Informational
Action: None
ADVM-05204: Attempting to restart replication daemons on string
Cause: Informational
Action: None
ADVM-05205: Failed to initialize replication because A
Cause: Removal of mount key from Oracle Registry failed.
Action: Use acfsutil registry to verify the mount key exists in the Oracle Registry.
ADVM-00566: invalid handle received when attempting to close an ACFS mount
key within Oracle Registry
Cause: An error was returned during the closing of a key in the Oracle Registry.
Action: Run ocrcheck to verify the Oracle Registry is working properly. Report to
Oracle Support Services.
ADVM-00567: unknown Oracle Registry error encountered closing key
Cause: An error was returned while closing the key from the Oracle Registry.
Action: Run ocrcheck to verify the Oracle Registry is working properly. Report to
Oracle Support Services.
ADVM-00568: closing of a key resulted in Oracle Registry error number
Cause: An error was returned during the closing of a key in the Oracle Registry.
Action: Verify the Oracle Registry is accessible. If it is not accessible and the cause
is unclear, report this error to Oracle Support Services.
ADVM-00569: invalid handle received when attempting to delete an ACFS mount
key within Oracle Registry
Cause: An error was returned while removing a key from the Oracle Registry.
Action: Report this error to Oracle Support Services.
ADVM-00570: The ACFS mount key specified for deletion does not exist within
Oracle Registry.
Cause: The mount key could not be located in the Oracle Registry.
Action: Use acfsutil registry to ensure the mount entry exists in the Oracle
Registry.
ADVM-00571: The ACFS mount key specified for deletion is not empty.
Cause: The mount key specified for deletion from the Oracle Registry contained
dependent subkeys.
Action: View the mount entries in the Oracle Registry using "acfsutil registry" and
remove any dependent mount entries before retrying this operation.
ADVM-00572: permission denied to delete the ACFS mount entry from Oracle
Registry
Cause: The user permissions were insufficient to remove the key from the Oracle
Registry.
Action: Verify the Oracle Registry is accessible and that command is being run
from a properly authorized user ID.
ADVM-00573: Oracle Registry error encountered while deleting an ACFS mount
key
Cause: An error was returned while removing the key from the Oracle Registry.
ADVM-00501 to ADVM-11069 98-5
Action: Report this error to Oracle Support Services.
ADVM-00575: deletion request of key resulted in Oracle Registry error number
Cause: An error was returned while removing a key from the Oracle Registry.
Action: Run ocrcheck to verify that Oracle Registry is working properly. If
problem persists, report to Oracle Support Services.
ADVM-00584: failed to look up ACFS mount points in the Oracle Registry string
Cause: An error was returned while looking up a mount point in the Oracle
Registry.
Action: Run ocrcheck to verify the Oracle Registry is working properly. If problem
persists, report to Oracle Support Services.
ADVM-00585: null parameter received
Cause: A null parameter was passed to the Oracle Registry.
Action: Run ocrcheck to verify that Oracle Registry is working properly. If
problem persists, report to Oracle Support Services.
ADVM-00587: unknown Oracle Registry error encountered during operation on
ACFS mount entry
Cause: An error was returned while accessing the key from the Oracle Registry.
Action: Run ocrcheck to verify that Oracle Registry is working properly. If
problem persists, report to Oracle Support Services.
ADVM-00589: key operation resulted in Oracle Registry error number
Cause: An error was returned during a key operation with the Oracle Registry.
Action: Run ocrcheck to verify that Oracle Registry is working properly. If
problem persists, report to Oracle Support Services.
ADVM-00592: Seek to volume failed. Verify the volume exists.
Cause: Seek to a location on the volume failed.
Action: Verify the volume exists on this node and that it is accessible.
ADVM-00593: The Oracle Registry returned the following error while attempting
to access ACFS key string string
Cause: Failed to access either the SYSTEM, SYSTEM.ACFS or
SYSTEM.ACFS.Mounts keys in Oracle Registry.
Action: Run ocrcheck to verify the Oracle Registry is working properly. Examine
the appended error message from the Oracle Registry service.
ADVM-00594: Failed to access ACFS mount information. The Oracle Registry
returned the appended error for ACFS key string. string
Cause: Failed to access ACFS mount information from the Oracle Registry.
Action: Examine the appended error message from the Oracle Registry.
ADVM-00595: Failed to access ACFS mount value information. The Oracle Registry
returned the appended error for ACFS key string. string
Cause: Failed to access ACFS mount value information from the Oracle Registry.
This might be due to Oracle Registry corruption or a sudden loss of the Oracle
Registry service.
Action: Examine the appended error message from the Oracle Registry. Run
ocrcheck to verify the Oracle Registry is working properly.
98-6 Oracle Database Error Messages
ADVM-00596: A failure occurred while accessing the Oracle Registry ACFS key
"SYSTEM" for security purposes and follows this message: string
Cause: Failed to retrieve key access rights for the Oracle Registry ACFS key
"SYSTEM"
Action: Run ocrcheck to verify the Oracle Registry is working properly. Evaluate
the error message returned from the Oracle Registry appended to this message. If
necessary, run ocrdump and make sure the "SYSTEM" key exists and is accessible.
ADVM-00597: Failed to initialize the Oracle Registry's SCLS context. The SCLS
error is included with this message.
Cause: An operating system initialization failed.
Action: Evaluate the attached SCLS error message. Run ocrcheck to verify the
Oracle Registry is functioning correctly.
ADVM-00598: An error occurred while looking up the current user's operating
system account name. The error is included with this message.
Cause: ACFS was attempting to add an entry to the Oracle Registry. During this
attempt a lookup of the current user's name failed in the operating system failed.
Action: Evaluate the attached error message to determine why the current user
name could not obtained from the operating system.
ADVM-00599: The Oracle Registry returned the following error while attempting
to close the ACFS key string string
Cause: Possibly due to Oracle Registry corruption or a sudden loss of the Oracle
Registry service.
Action: Examine the appended error message from the Oracle Registry. Run
ocrcheck to verify the Oracle Registry is working properly.
ADVM-00600: Failed to access ACFS mount subkey information. The Oracle
Registry returned the appended error. string
Cause: Failed to access ACFS mount information from the Oracle Registry.
Action: Examine the appended error message from the Oracle Registry.
ADVM-00601: Failed to initialize this utility's access to the Oracle Registry. Verify
the registry service has started.
Cause: Either the Oracle Registry service was unavailable or the registry
configuration was incomplete/inaccurate.
Action: Run ocrcheck to verify the registry service is working properly.
ADVM-00602: An internal error (BADARG) occurred while trying to determine the
Oracle Registry configuration.
Cause: An Oracle internal error.
Action: Contact Oracle.
ADVM-00603: Failed to retrieve the Oracle Cluster Registry, OCR, configuration
Cause: Failed to obtain OCR information.
Action: Run ocrcheck to verify OCR is working properly.
ADVM-00604: Failed to retrieve the Oracle Local Registry, OLR, configuration
Cause: Failed to obtain Oracle Local Registry information.
Action: Run ocrcheck -local to verify the OLR is working properly.
ADVM-00501 to ADVM-11069 98-7
ADVM-00605: Failed to retrieve the Oracle Registry configuration for an unknown
reason
Cause: Failed to obtain Oracle Registry information.
Action: Run ocrcheck to verify the registry is working properly.
ADVM-00606: Could not determine if the system is configured for RAC or Oracle
Restart environment.
Cause: The Oracle Registry service configuration could not be detected
Action: Run ocrcheck to verify the Oracle registry service.
ADVM-00607: Failed to access or create Oracle Registry keys required for ACFS
operation
Cause: Oracle Registry keys required for operation either could not be accessed or
created.
Action: Another error message number will follow this message. Analyze its
output. Run ocrcheck to verify the Oracle registry is functioning properly. Also,
verify acfsutil was invoked with administrative rights when attempting to add the
ACFS mount points.
ADVM-00619: This is a string computer, but the file system was created on a string
string computer.
Cause: The file system was created on a computer which has a different Endian
than the current system. Little Endian machines (such as the intel x86 based
systems) store the Least Significant bit in the first byte of an integer value. Big
Endian machines (such as Solaris SPARC and AIX Power based systems) store the
Most Significant bit in the first byte of an integer value.
Action: Use a system with the same Endian as the system which created the file
system.
ADVM-00620: This feature is not available for Oracle version string or lower on
this platform.
Cause: Informational.
Action: None
ADVM-00621: Unable to determine privileges
Cause: An error occured retrieving the user credentials.
Action: Verify the mount point is an ACFS mount point and it is not offline.
ADVM-00622: must provide a base mount point
Cause: A mount point on the base site was not provided.
Action: Provide an existing mount point on the base site.
ADVM-00623: must provide a target mount point
Cause: A mount point on the target site was not provided.
Action: Provide an existing mount point with an empty file system on the target
site.
ADVM-00624: The path specified is too long.
Cause: The path specified exceeded the allowed maximum path length.
Action: Verify the path was entered correctly, or use a different path.
ADVM-00625: string is not a valid ACFS mount point.
98-8 Oracle Database Error Messages
Cause: The mount point path specified was not a valid mount point.
Action: Provide a valid ACFS mount point.
ADVM-01001: Size specified cannot exceed size of volume.
Cause: Volume size was smaller than the requested size.
Action: Select a size that is less than or equal to the volume size and retry the
ACFS format command.
ADVM-01002: ACFS requires a minimum volume size of numberMB.
Cause: Volume was too small.
Action: Select a larger volume and retry.
ADVM-01004: string was not formatted.
Cause: An error occurred during the formatting of the volume.
Action: This message is accompanied by another error message. Respond as
indicated for that message."
ADVM-01005: unable to allocate a buffer
Cause: A request for process virtual memory by the ACFS format command
failed. This message is accompanied by other message(s) providing details on the
error.
Action: Correct the problem indicated by the other message(s). If possible, change
options to reduce required memory and/or take steps to increase memory
available to the process. Otherwise, report this error to Oracle Support Services.
ADVM-01006: unable to open volume device 'string'
Cause: Volume device could not be opened. This message is accompanied by
other message(s) providing details on the error.
Action: Correct the problem indicated by the other message(s). If the cause of the
problem is unclear, contact Oracle Support Services.
ADVM-01008: unable to open file system string
Cause: File system was not accessible.
Action: Verify the volume associated with the file system is enabled and online
before retrying.
ADVM-01010: Volume already contains an ACFS file system. To reformat the
volume, reissue string with the stringf option.
Cause: The on-disk metadata indicated that an ACFS file system is located on the
volume.
Action: Verify the intended volume and reissue the format command with the
force flag to overwrite the existing ACFS file system.
ADVM-01011: Volume contains an ACFS file system that is being checked. To
reformat the volume, reissue string with the stringf option.
Cause: The volume contained a file system that was in the process of being
checked by fsck (Unix or Linux) or acfschkdsk.exe (Windows).
Action: Verify the intended volume and reissue the format command with the
force flag to overwrite the existing ACFS file system.
ADVM-01014: write of volume label failed
ADVM-00501 to ADVM-11069 98-9
Cause: A write to the volume during file system creation failed. This message is
accompanied by other message(s) providing details on the error.
Action: Correct the problem indicated by the other message(s). If the solution is
not clear, contact Oracle Support Services.
ADVM-01018: failed to allocate a buffer for number bytes
Cause: A request for process virtual memory by the ACFS format command
failed. This message is accompanied by other message(s) providing details on the
error.
Action: Correct the problem indicated by the other message(s). If possible, change
options to reduce required memory and/or take steps to increase memory
available to the process. Otherwise, report this error to Oracle Support Services.
ADVM-01019: This volume contains a mounted ACFS file system. The file system
must be dismounted with acfsdismount on all nodes.
Cause: The volume was in use by another file system.
Action: Dismount the ACFS file system with acfsdismount and retry the
command.
ADVM-01020: This volume contains a mounted non-ACFS file system. The file
system must be dismounted with 'advmutil dismount'.
Cause: The volume was in use by another non-ACFS file system.
Action: Dismount the non-ACFS file system with 'advmutil dismount' and retry
the command.
ADVM-01033: write to volume failed
Cause: of the problem is unclear, contact Oracle Support Services.
Action: Correct the problem indicated by the other message(s). If the
ADVM-01038: write failed during setup of root directory entry
Cause: of the problem is unclear, contact Oracle Support Services.
Action: Correct the problem indicated by the other message(s). If the
ADVM-01041: write of snaps directory entry failed
Cause: of the problem is unclear, contact Oracle Support Services.
Action: Correct the problem indicated by the other message(s). If the
ADVM-01043: write of lost+found directory entry failed
Cause: of the problem is unclear, contact Oracle Support Services.
Action: Correct the problem indicated by the other message(s). If the
ADVM-01044: write of file entry table failed
Cause: of the problem is unclear, contact Oracle Support Services.
Action: Correct the problem indicated by the other message(s). If the
ADVM-01045: write of global bitmap failed
Cause: of the problem is unclear, contact Oracle Support Services.
Action: Correct the problem indicated by the other message(s). If the
ADVM-01046: read of global bitmap file entry failed
Cause: of the problem is unclear, contact Oracle Support Services.
Action: Correct the problem indicated by the other message(s). If the
98-10 Oracle Database Error Messages
ADVM-01047: write of global bitmap file entry failed
Cause: of the problem is unclear, contact Oracle Support Services.
Action: Correct the problem indicated by the other message(s). If the
ADVM-01049: seek to snap map header failure
Cause: of the problem is unclear, contact Oracle Support Services.
Action: Correct the problem indicated by the other message(s). If the
ADVM-01050: write to snap map header failure
Cause: of the problem is unclear, contact Oracle Support Services.
Action: Correct the problem indicated by the other message(s). If the
ADVM-01051: partial write to snap map header failure
Cause: of the problem is unclear, contact Oracle Support Services.
Action: Correct the problem indicated by the other message(s). If the
ADVM-01052: write to snap map info entry failure
Cause: of the problem is unclear, contact Oracle Support Services.
Action: Correct the problem indicated by the other message(s). If the
ADVM-01053: partial write to snap map info entry failure
Cause: of the problem is unclear, contact Oracle Support Services.
Action: Correct the problem indicated by the other message(s). If the
ADVM-01054: write to snap map storage entry failure
Cause: of the problem is unclear, contact Oracle Support Services.
Action: Correct the problem indicated by the other message(s). If the
ADVM-01055: partial write to snap map storage entry failure
Cause: of the problem is unclear, contact Oracle Support Services.
Action: Correct the problem indicated by the other message(s). If the
ADVM-01150: unable to synchronize in-memory file data to disk
Cause: A request to flush all in-memory copies of buffers associated with the
open handle failed. This message is accompanied by other message(s) providing
details on the error.
Action: Correct the problem identified by the other message(s). If the problem has
been resolved and the file system is unusable, retry the ACFS format command.
ADVM-01151: Ignoring invalid block size number, using number
Cause: An ACFS format command unsupported block size was specified.
Action: No action required. A supported block size will be used.
ADVM-01152: The length of accelerator volume name exceeds number.
Cause: Accelerator volume name length exceeded the maximum length displayed
in the message.
Action: Select an accelerator volume name with length less than or equal to the
maximum length displayed in the message and retry the command.
ADVM-01154: The accelerator volume contains a mounted ACFS file system. The
file system must be dismounted with acfsdismount on each node.
ADVM-00501 to ADVM-11069 98-11
Cause: The specified volume could not be used as an accelerator volume because
it was in use by a mounted file system.
Action: Dismount the ACFS file system with acfsdismount and retry the
command.
ADVM-01155: The accelerator volume contains a mounted non-ACFS file system.
The file system must be dismounted with 'advmutil dismount'.
Cause: The specified volume could not be used as an accelerator volume because
it was in use by a mounted non-ACFS file system.
Action: Dismount the non-ACFS file system with 'advmutil dismount' and retry
the command.
ADVM-01156: The Oracle ASM Dynamic Volume Manager (Oracle ADVM)
compatibility attribute for the disk group is less than 12.1.0.2.0.
Cause: An attempt to create a file system with an accelerator volume failed
because the ADVM compatibility attribute for the disk group was not set to
12.1.0.2.0 or higher.
Action: Use the Oracle ASM Configuration Assistant (ASMCA) tool or the SQL
statement ALTER DISKGROUP to upgrade COMPATIBLE.ADVM attribute.
ADVM-01159: The accelerator volume must be different from the volume
containing the file system.
Cause: The file system could not be created because the same volume was
specified for both the accelerator and the file system.
Action: Choose a different volume for the accelerator and retry the command.
ADVM-01160: The specified accelerator volume was smaller than numberMB.
Cause: The file system could not be created because the specified accelerator
volume was below the minimum allowed size reported in the message.
Action: Select a larger accelerator volume and retry the command.
ADVM-01164: The specified device 'string' is already in use with a CRS-managed
file system.
Cause: The file system could not be created because the specified device was
already registered with CRS (Cluster Ready Services).
Action: Select an unused device, or use srvctl to modify the association for this
device and retry the file system creation.
ADVM-02001: unable to allocate a buffer
Cause: A request for process virtual memory by mount command failed. This
message is accompanied by other message(s) providing details on the error.
Action: Correct the problem indicated by the other message(s). If possible, change
options to reduce required memory and/or take steps to increase memory
available to the process. Otherwise, report this error to Oracle Support Services.
ADVM-02006: unable to terminate the Oracle Registry connection
Cause: Either the Oracle Registry service was unavailable or the Oracle Registry
configuration was incomplete/inaccurate.
Action: Run crs_stat and ocrcheck to verify CSS and the Oracle Registry are
working properly. If they are not accessible and the cause is unclear, report this
error to Oracle Support Services.
98-12 Oracle Database Error Messages
ADVM-02012: Mount of string failed, volume string does not exist. Verify that
string exists on this node.
Cause: Could not mount the file system retrieved from the Oracle Registry.
Action: Verify the volume exists on this node and that it is accessible.
ADVM-02014: Mount of string failed. Error number was returned.
Cause: Mount operation failed.
Action: Verify the mount point and volume both exist and are accessible before
retrying the mount command.
ADVM-02015: Failed to open mount point string. Verify the mount point exists.
Cause: Mount point could not be opened.
Action: Verify the mount point exists and is accessible before retrying the mount
command.
ADVM-02017: Failed to open volume string. Verify the volume exists.
Cause: The volume could not be opened.
Action: Verify the ASM instance is operational and the volume is enabled and
accessible before retrying the mount command.
ADVM-02018: Volume string contains an ACFS file system that is being checked.
Allow the file system check to complete.
Cause: The volume contained a file system that was in the process of being
checked by the ACFS checker.
Action: Allow the ACFS checker to complete before retrying the mount. If the
ACFS checker is not running on this file system and a file system check was
previously interrupted, reissue the ACFS checker.
ADVM-02026: unable to verify the host names passed in are part of the cluster
Cause: Either CSS was unavailable or the CSS configuration was
incomplete/inaccurate.
Action: Run crs_stat to verify CSS is working properly.
ADVM-02027: unable to obtain the local CSS node name
Cause: Either CSS was unavailable or the CSS configuration was
incomplete/inaccurate.
Action: Run crs_stat to verify CSS is working properly.
ADVM-02046: Volume string cannot be mounted. Examine the system event log for
possible causes.
Cause: The volume mount failed. This could be caused by an out of space
condition if this is the first mount of a file system on a node.
Action: Examine the system event log for more detail.
ADVM-02050: unable to set in-memory mount information
Cause: Could not communicate with the mounted file system.
Action: Verify the ASM instance is operational and the volume is enabled and
accessible before retrying.
ADVM-02081: Warning: acfschkdsk.exe should be run on volume string at your
earliest convenience
ADVM-00501 to ADVM-11069 98-13
Cause: A flag in the superblock indicates that a metadata inconsistency has been
found on this volume.
Action: Run acfschkdsk.exe as soon as possible to fix the metadata inconsistency.
ADVM-02082: unable to verify if the host names provided are part of the cluster
Cause: Could not obtain information about the cluster.
Action: Run crs_stat to verify health of CSS.
ADVM-02083: cannot get the local CSS node name
Cause: Could not obtain local CSS node name.
Action: Run crs_stat to verify health of CSS.
ADVM-02090: unable to retrieve ACFS mount information from CRS
Cause: Failed to retrieve mount information the CRS.
Action: Analyze the error messages that precede this message.
ADVM-02092: Mount of string failed, node string is not a member of the CSS
cluster.
Cause: Could not mount the file system retrieved from the Oracle Registry.
Action: Verify the node listed in the entry is a member of the CSS cluster.
ADVM-02119: creating administrative network share for mount point string at
share name 'string'
Cause: Informational
Action: None
ADVM-02120: administrative network share for mount point string already exists at
share name 'string'
Cause: Informational
Action: None
ADVM-02121: administrative network share 'string' already exists, but does not
share mount point string
Cause: Attempted to create an administrative network share for the specified
ACFS mount point, but the required share name was already in use.
Action: Remove the conflicting network share using 'net share <share name>
/delete'. Remount the ACFS file system to retry creating an administrative
network share for the mount point.
ADVM-02122: retrieving information for administrative network share 'string'
failed
Cause: While creating an administrative network share for the specified ACFS
mount point, failed to retrieve information on any network share that might
already exist at the required share name. This message is accompanied by other
messages providing details on the error.
Action: Correct the error indicated by the accompanying messages. Remount the
ACFS file system to retry creating an administrative network share for the mount
point.
ADVM-02123: creating administrative network share for mount point string at
share name 'string' failed
98-14 Oracle Database Error Messages
Cause: Failed to create an administrative network share for the specified ACFS
mount point. This message is accompanied by other messages providing details on
the error.
Action: Correct the error indicated by the accompanying messages. Remount the
ACFS file system to retry creating an administrative network share for the mount
point.
ADVM-02124: could not create administrative network share for mount point string
at share name 'string'
Cause: Failed to create an administrative network share for the specified ACFS
mount point. This message is accompanied by other messages providing details on
the error.
Action: Correct the error indicated by the accompanying messages.
ADVM-02125: volume 'string' is already in use
Cause: The volume was in use by another file system.
Action: Verify the volume specified.
ADVM-02126: Volume string cannot be mounted.
Cause: The volume mount failed. This message is accompanied by other messages
providing details on the error.
Action: Correct the problem indicated by the other messages and retry the mount
command.
ADVM-02127: unable to transfer mount data to the ACFS driver
Cause: is unclear, contact Oracle Support Services.
Action: Correct the problem identified by the other messages. If the
ADVM-02128: unable to clean up mount data passed to ACFS driver
Cause: The operation to clean up mount data from a temporary location / failed.
Action: None. This state will not have any repercussions and it will be remedied
automatically during the next restart.
ADVM-02129: Volume string cannot be mounted. Volume is out of space.
Cause: The volume mount failed because the volume was out of space.
Action: Correct the problem by resizing the ADVM volume and then retry the
mount command.
ADVM-02130: Volume string cannot be mounted. Volume version does not match
the ACFS driver version.
Cause: The volume mount failed because the loaded ACFS driver does not
support the volume version.
Action: Use 'acfsdriverstate' command to determine the state of the ACFS driver
and address any issues that are reported. Retry the mount command after the
installed driver has been verified.
ADVM-02131: Volume string cannot be mounted. Cluster membership is not
established.
Cause: The volume mount failed because the ACFS driver could not communicate
with Oracle Clusterware.
ADVM-00501 to ADVM-11069 98-15
Action: Verify the online state of Oracle Clusterware using command 'crsctl check
CRS' and address any issues that are reported. Retry the mount command once
Oracle Clusterware is fully operational.
ADVM-02132: Volume string cannot be mounted. Insufficient kernel resources to
complete the mount.
Cause: The volume mount failed due to insufficient kernel resources.
Action: Reduce the load activity on the system and retry the mount command.
ADVM-02133: Volume string cannot be mounted. Metadata inconsistency found
on-disk.
Cause: The volume mount failed due to a metadata inconsistency found in the
volume superblock.
Action: Run command 'fsck -t acfs' as soon as possible to fix the metadata
inconsistency and then retry the mount command.
ADVM-03001: Failed to open string. Verify that string exists.
Cause: The mount point or file could not be opened.
Action: Verify the mount point or file is accessible before retrying.
ADVM-03003: Cannot decrease the volume by this amount.
Cause: Requested size exceeded the size of the file system.
Action: Select a size that is smaller than the size of the file system and retry.
ADVM-03004: Cannot reduce volume size below 200 MB.
Cause: Requested size was below the minimum volume size of 200MB."
Action: Select a volume that is 200MB or larger."
ADVM-03008: The volume could not be resized. The volume expansion limit has
been reached.
Cause: The file system's internal storage bitmap has a five extent limit. Growing
the file system may fail if it has already been grown four or more times, using up
all available storage bitmap extents.
Action: If the file system has been grown four or more times, running the ACFS
Fixer may allow future volume expansions.
ADVM-03013: unable to open string
Cause: Volume could not be opened to remove the file system.
Action: Verify the volume is not mounted on any node in the cluster before
retrying.
ADVM-03033: unable to open string
Cause: The log file specified could not be created and/or opened.
Action: If a file exists by the same name as the log file specified, verify that this is
a file that can be overwritten.
ADVM-03044: Failed to open mount point string. Verify the mount point exists.
Cause: Mount point could not be opened for snapshot operation.
Action: Verify the mount point exists and is accessible before retrying the snap
command.
ADVM-03052: unable to delete snapshot string due to open files
98-16 Oracle Database Error Messages
Cause: There are files open in the snapshot.
Action: Use lsof or similar tool to find the processes with open files. No files can
be open in the snapshot for the snapshot delete operation to succeed.
ADVM-03054: snapshot string is not a valid snapshot name
Cause: statement.
Action: Verify that the snapshot name meets the criteria listed in the
ADVM-03091: Failed to open string. This may mean the string driver is not
loaded/running
Cause: The driver's control device could not be accessed.
Action: Verify the driver is loaded and running.
ADVM-03096: error opening configuration file string
Cause: The configuration file cannot be created and/or opened.
Action: If the configuration file exists, verify the file can be opened.
ADVM-03097: error accessing configuration file string
Cause: Seek to the end of the configuration file failed.
Action: If the configuration file exists, verify the file is accessible.
ADVM-03106: Invalid combination of arguments. stringa was previously specified
to add an ACFS mount point to Oracle Registry.
Cause: Invalid option combination.
Action: Retry the command with one set of operations.
ADVM-03107: Invalid combination of arguments. stringd was previously specified
to remove an ACFS mount point from the Oracle Registry.
Cause: Invalid option combination.
Action: Retry the command with one set of operations.
ADVM-03108: Neither string nor string is an ADVM volume.
Cause: Volume specified was not an ADVM volume.
Action: Retry the command with an ADVM volume.
ADVM-03110: unable to access the Oracle Registry string
Cause: Either the Oracle Registry service was unavailable or the registry
configuration was incomplete/inaccurate.
Action: Run ocrcheck to verify the Oracle Registry is working properly. Analyze
the appended Oracle Registry service error message.
ADVM-03114: unable to allocate a buffer
Cause: A request for process virtual memory by acfsutil registry failed This
message is accompanied by other message(s) providing details on the error.
Action: Correct the problem indicated by the other message(s). If possible, change
options to reduce required memory and/or take steps to increase memory
available to the process. Otherwise, report this error to Oracle Support Services.
ADVM-03115: an error occurred while attempting to disconnect from Oracle
Registry
Cause: Either the Oracle Registry service was unavailable or the Oracle Registry
configuration was incomplete/inaccurate.
ADVM-00501 to ADVM-11069 98-17
Action: Run ocrcheck to verify the Oracle Registry service is working properly. If
the cause of the problem is unclear, contact Oracle Support Services.
ADVM-03117: unable to verify if the hostnames provided are part of the cluster
Cause: Could not obtain information about the cluster.
Action: Run crs_stat to verify health of CSS.
ADVM-03118: cannot obtain the node number of host string via CSS or the Oracle
Registry
Cause: Could not determine the node number for the specified host.
Action: Verify that the specified host is a member of this cluster.
ADVM-03119: Incorrect data format in file 'number'.
Cause: The file data was not in the expected format.
Action: Contact Oracle Support Services.
ADVM-03120: Note: Reported snapshot space usage is inaccurate.
Cause: The snapshot storage calculated was not expected.
Action: No action is required. To get a more accurate count, dismount the file
system on all nodes and run fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ADVM-03122: failed to create Oracle Registry ACFS key string string
Cause: Failed to create ACFS key(s) SYSTEM.ACFS and/or
SYSTEM.ACFS.Mounts in the Oracle Registry.
Action: Run ocrcheck to verify the Oracle Registry service is working properly.
Verify acfsutil is executed with operating system administrator privileges.
ADVM-03123: failed to create Oracle Registry ACFS key string because it already
exists
Cause: The Oracle Registry ACFS key already exists.
Action: Run ocrcheck to verify the Oracle Registry service is working properly.
ADVM-03124: failed to create Oracle Registry ACFS subkey because it already
exists
Cause: The Oracle Registry mounts subkey already exists.
Action: Run ocrcheck to verify the Oracle Registry service is working properly. If
the ACFS mount entry is in an inconsistent state delete it, then re-add it using
acfsutil with the registry option. If the problem persists, contact Oracle Support
Services.
ADVM-03125: error retrieving the volume using Oracle Registry key: string
Cause: Could not retrieve volume information from mount entry in the Oracle
Registry.
Action: Run ocrcheck to verify the Oracle Registry is working properly.
ADVM-03126: error retrieving the mount point using Oracle Registry key: string
Cause: Could not retrieve mount point information from mount entry in the
Oracle Registry.
Action: Run ocrcheck to verify the Oracle Registry is working properly.
ADVM-03127: error retrieving the mount options using Oracle Registry key: string
Cause: Could not retrieve mount options from mount entry in the Oracle Registry.
98-18 Oracle Database Error Messages
Action: Run ocrcheck to verify the Oracle Registry is working properly.
ADVM-03128: error retrieving the version using Oracle Registry key: string
Cause: Could not retrieve the version for mount entry in the Oracle Registry.
Action: Run ocrcheck to verify the Oracle Registry is working properly.
ADVM-03129: error retrieving the nodes list using Oracle Registry key: string
Cause: Could not retrieve the nodes list for mount entry in the Oracle Registry.
Action: Run ocrcheck to verify the Oracle Registry is working properly.
ADVM-03133: The Oracle Registry returned the following error while attempting
to access the security attributes of key string: string
Cause: is unclear, contact Oracle Support Services.
Action: Correct the problem identified by the other message(s). If the
ADVM-03134: An error occurred while accessing Oracle Registry for a delete mount
point operation. string
Cause: Could not retrieve data from the Oracle Registry. This message is
accompanied by other message(s) providing details on the error.
Action: Correct the problem indicated by the other message(s). If the cause of the
problem is unclear, contact Oracle Support Services.
ADVM-03135: unable to locate mount point string in Cluster Ready Services
Cause: An attempt to access the ACFS mount point failed because the mount
point information could not be retrieved from CRS.
Action: Verify the mount point is registered with CRS using the 'acfsutil registry
<device>' commands.
ADVM-03136: unable to locate volume string in Cluster Ready Services
Cause: An attempt to access the ASM volume failed because the volume
information could not be retrieved from CRS.
Action: Verify the volume is registered with CRS using the 'acfsutil registry
<device>' commands.
ADVM-03137: Multiple entries exist for the mount point string. Rerun the
command with the volume name.
Cause: Could not locate unique entry for mount point in the Oracle Registry.
Action: Retry acfsutil registry with volume name.
ADVM-03138: failed to create and set Oracle Registry ACFS mount info key string
Cause: Could not create and set a mount info key in the Oracle Registry.
Action: Run ocrcheck to verify the Oracle Registry is working properly.
ADVM-03139: error retrieving the disk group name using Oracle Registry key:
string
Cause: Could not retrieve the disk group name from the mount entry in the
Oracle Registry.
Action: Run ocrcheck to verify the Oracle Registry is working properly.
ADVM-03140: error retrieving the volume name using Oracle Registry key: string
Cause: Could not retrieve the volume name from the mount entry in the Oracle
Registry.
ADVM-00501 to ADVM-11069 98-19
Action: Run ocrcheck to verify the Oracle Registry is working properly.
ADVM-03141: unable to open device string
Cause: The device could not be opened.
Action: Check the diskgroup is mounted and the specified volume is enabled.
ADVM-03142: Failed to retrieve the diskgroup and volume name for device string.
See the attached error.
Cause: Possible internal error.
Action: Check the attached error. If not serviceable, contact Oracle.
ADVM-03143: The specified mount point does not exist and therefore cannot be
deleted.
Cause: The Oracle Registry has not been configured for ACFS or the specified
mount point does not exist.
Action: Run "acfsutil registry" to list out the available ACFS mount points.
ADVM-03145: unable to remove ACFS volume string from Oracle Registry
Cause: Could not remove volume from Oracle Registry.
Action: Verify the volume exists in the Oracle Registry using the acfsutil registry
command.
ADVM-03146: Warning: The ACFS mount point group ownership cannot be
re-initialized in the Oracle Registry. The registry is initialized from the ACFS
control device on first use, and may have changed ownership since then.
Current Key Ownership: string
Cause: An attempt was made to re-initialize the ACFS mount point group
ownership in the Oracle Registry. This may be because the ACFS control device
/dev/ofsctl or /dev/acfsctl has changed owners.
Action: Re-initializing the ACFS mount point group ownership in the Oracle
Registry is not supported.
ADVM-03147: invalid ACFS file identifier provided
Cause: The ACFS file identifier provided by the user had an illegal value.
Action: Re-enter a number other than 0 or -1.
ADVM-03148: ioctl call to obtain pathname associated with file id number failed
Cause: An internal ioctl operation to map from an ACFS file identifier to a
pathname failed. This message is accompanied by other message(s) providing
details on the error.
Action: Correct the problem indicated by the other message(s). If the cause of the
problem is unclear, contact Oracle Support Services.
ADVM-03149: constructed pathname is too large
Cause: The length of the pathname being constructed has exceeded the system
limit of %d characters. This may be due to changes in the file system namespace
while the command is running.
Action: Try the command again. If the problem persists, contact Oracle Support
Services.
ADVM-03151: The ACFS file identifier provided is not associated with a user file
or directory.
Cause: The ACFS file identifier, although valid, was not for a user file or directory.
98-20 Oracle Database Error Messages
Action: None. There is no pathname associated with this ACFS file identifier.
ADVM-03152: The ACFS file identifier provided is invalid for the mountpoint
specified.
Cause: The ACFS file identifier was not a valid identifier for the mountpoint
specified.
Action: Verify that the correct ACFS file identifier and mountpoint were specified.
ADVM-03153: The file system name space has changed and a pathname cannot be
obtained.
Cause: The ACFS file identifier was valid, but could not be used to obtain a full
file pathname.
Action: Verify that the correct ACFS file identifier and mountpoint were specified.
ADVM-03154: Failed to determine the full pathname. Too many directory levels.
Cause: acfsutil has received information from the operating system that it could
not process fully.
Action: Report this error to Oracle Support Services.
ADVM-03157: unsupported file type for string, not a mount point
Cause: An invalid entry was passed on the command line.
Action: The acfsutil info acfs command requires that the input be a mount point.
ADVM-03158: unsupported file type for string, not a mount point or a file
Cause: An invalid entry was passed on the command line.
Action: The acfsutil size command requires that the input be a mount point or a
file.
ADVM-03161: Device : string : Mount Point : string already exists in the Oracle
Registry
Cause: This entry has already been added to the Oracle Registry.
Action: None
ADVM-03162: Warning: The file system was resized, but an error occurred while
resizing the ADVM volume. File system size now number MB, volume size
number MB.
Cause: An error occurred during ADVM volume resize.
Action: Reissue the resize command.
ADVM-03165: Unable to add the file system on device string to the ACFS registry.
It is currently managed by CRS.
Cause: The file system is currently managed by CRS and a file system cannot be
managed by both CRS and the ACFS registry.
Action: Remove the file system resource from CRS or continue to use CRS to
manage the file system.
ADVM-03166: Unable to add a STOP_DEPENDENCY to the ACFS registry for
device string.
Cause: The ACFS registry resource could not be updated.
Action: Verify the ACFS registry state ('crsctl stat res ora.registry.acfs -p')
ADVM-00501 to ADVM-11069 98-21
ADVM-03167: Unable to remove the STOP_DEPENDENCY for device string from
the ACFS registry.
Cause: The ACFS registry resource could not be updated.
Action: Verify the ACFS registry state ('crsctl stat res ora.registry.acfs -p')
ADVM-03168: Internal error: string number
Cause: An Oracle internal error.
Action: Contact Oracle Support Services.
ADVM-03169: Unable to set log file size.
Cause: The ACFS driver was unable to set the log file size.
Action: Check the log file to see the reason of failure.
ADVM-03170: Minimum log file size is number.
Cause: The ACFS driver was unable to set the log file size.
Action: Log file size has to be bigger than or equal to the minimum size.
ADVM-03171: Insufficient contiguous free ASM Diskgroup space. Check the ASM
alert log.
Cause: ADVM could not resize the volume because ASM did not have enough
contiguous free diskgroup storage.
Action: Increase the free space in the diskgroup. Check the ASM alert log.
ADVM-03172: ADVM is busy with Mirror recovery. Try again later.
Cause: ADVM could not resize the volume because it is recovering the mirrored
volumes.
Action: Try again later. The system console log will contain mirror recovery
started and completed messages. For example: [Oracle ADVM] Mirror recovery
for volume asm/volume-name started. [Oracle ADVM] Mirror recovery for
volume asm/volume-name completed.
ADVM-03173: ADVM or ASM is unable to resize the volume. Check the ASM alert
log.
Cause: ADVM or ASM is unable to resize the volume.
Action: Check the ASM alert log.
ADVM-03174: The Oracle ASM Dynamic Volume Manager (Oracle ADVM)
compatibility attribute for the disk group is less than 11.2.0.3.0.
Cause: The ADVM compatibility attribute for the disk group was not set to
version 11.2.0.3.0 or higher to allow the creation of a read/write snapshot.
Action: Use the Oracle ASM Configuration Assistant (ASMCA) tool or the SQL
statement ALTER DISKGROUP to upgrade COMPATIBLE.ADVM attribute.
ADVM-03177: maximum log file size cannot exceed number MB
Cause: The ACFS driver was unable to set the log file size.
Action: Retry the command with a log file size that is smaller than the maximum
size.
ADVM-03178: unable to delete snapshot string while cluster is in rolling migration
Cause: The cluster was in rolling migration. Snapshot deletions are not allowed
during rolling migration.
Action: Complete the rolling migration and then delete the snapshot.
98-22 Oracle Database Error Messages
ADVM-03179: unable to create snapshot 'string' while cluster is in rolling migration
Cause: The cluster was in rolling migration. Snapshot creations are not allowed
during rolling migration.
Action: Complete the rolling migration and then create the snapshot.
ADVM-03180: Unable to obtain ASM volume device information for 'string'
Cause: The operation for retrieval of ASM volume device information failed. This
message is accompanied by other message(s) providing details on the error.
Action: Correct the problem indicated by the other message(s). If the solution is
not clear, contact Oracle Support Services.
ADVM-03185: Unable to obtain ASM volume extent information for string
Cause: The operation for retrieval of ASM volume extent information failed. This
message is accompanied by other message(s) providing details on the error.
Action: Correct the problem indicated by the other message(s). If the solution is
not clear, contact Oracle Support Services.
ADVM-03186: Supplied ACFS file offset value is greater than the file allocation
size of number
Cause: The supplied file offset value in bytes supplied must be smaller than the
file allocation size.
Action: 'acfsutil file info filename' provides the file allocation size. Choose a
smaller value.
ADVM-03187: Extent number (mirror number) is not in use.
Cause: Informational
Action: None
ADVM-03203: Invalid snap command.
Cause: An invalid entry was passed on the command line.
Action: Use a valid 'acfsutil snap' command combination. Valid commands are
'acfsutil snap create', 'acfsutil snap delete', and 'acfsutil snap info'
ADVM-03204: Snapshot 'string' is already read-only.
Cause: A request was made to convert a snapshot to be read-only but the
snapshot was already read-only.
Action: None
ADVM-03205: Snapshot 'string' is already read-write.
Cause: A request was made to convert a snapshot to be read-write but the
snapshot was already read-write.
Action: None
ADVM-03206: The ADVM compatibility attribute for the diskgroup was below the
required version (string) for the 'acfsutil snap convert' command.
Cause: The ADVM compatibility attribute has not been upgraded to a version
that supports the 'acfsutil snap convert' command.
Action: Use the ASMCA tool or the SQL ALTER DISKGROUP statement to
upgrade COMPATIBLE.ADVM attribute to the specified version.
ADVM-03207: invalid combination of options
ADVM-00501 to ADVM-11069 98-23
Cause: The 'acfsutil snap convert' command was passed an invalid option
combination which included both the -r and -w options.
Action: Remove either the -r or -w option from the 'acfsutil snap convert'
command.
ADVM-03208: The /r option is not supported on this operating system
Cause: The 'acfsutil snap convert /r' option was specified. This functionality
requires a minimum operating system version of Windows Server 2008 R2.
Action: Upgrade operating system to Windows Server 2008 R2 or use the 'acfsutil
snap create' command to create a read-only snapshot.
ADVM-03212: There are too many snapshots for the file system associated with
string. Only number are allowed. Reduce the number of snapshots before
proceeding.
Cause: An attempt to create more than the maximum allowed number of active
snapshots was rejected.
Action: Delete a snapshot before creating a new one.
ADVM-03213: Creation of a snapshot failed due to presence of snapshots that
prevent this functionality.
Cause: A snapshot creation which specified a parent snapshot was not processed
because of compatibility issues with existing snapshots. Possible causes include: 1)
Snapshots of the file system were found that were created before ADVM
compatibility attribute was set to 12.1. 2) Snapshots of the file system were found
that were created after ADVM compatibility was set to 12.1 but while 11.2
snapshots existed.
Action: Delete all snapshots associated with the file system and retry the
command.
ADVM-03214: The Oracle ASM Dynamic Volume Manager (Oracle ADVM)
compatibility attribute for the disk group is less than 12.1.
Cause: The ADVM compatibility attribute for the disk group was not set to
version 12.1 or higher to allow the creation of a snapshot with a parent snapshot.
Action: Use the Oracle ASM Configuration Assistant (ASMCA) tool or the SQL
statement ALTER DISKGROUP to upgrade COMPATIBLE.ADVM attribute.
ADVM-03216: The ADVM compatibility attribute for the diskgroup was below the
required version (string) for unlimited volume expansions.
Cause: A request to resize the ACFS file system failed because the volume
expansion limit was reached. This limit was hit because the ADVM compatibility
attribute associated with the diskgroup was too low.
Action: Use the ASMCA tool or the SQL ALTER DISKGROUP statement to
upgrade the COMPATIBLE.ADVM attribute to the specified version.
ADVM-03300: unable to set tag name on file string
Cause: The ACFS driver was unable to complete the request.
Action: Verify memory or storage resources are sufficient.
ADVM-03301: unable to unset tag name on file string
Cause: The ACFS driver was unable to complete the request.
Action: Verify memory or storage resources are sufficient.
ADVM-03302: tag name syntax invalid or length too long
98-24 Oracle Database Error Messages
Cause: Tag name contains invalid characters or has too many characters.
Action: Change tag name to use valid characters or shorten the tag name.
ADVM-03303: invalid combination of arguments
Cause: The acfsutil tag info -t or -r arguments work only on file pathnames.
Action: Remove the -t or -r arguments from the ofsutil tag info command.
ADVM-03304: Unable to open mount point string. Verify that the mount point
exists.
Cause: Mount point cannot be opened to display tag name information.
Action: Verify that the mount point exists and is accessible before retrying the tag
info command.
ADVM-03305: unable to retrieve all tag names for string
Cause: Unable to return the full list of tag names.
Action: Verify there is sufficient memory resources available.
ADVM-03306: tag name does not exist in file string
Cause: Cannot unset a tag name on a file that does not exist.
Action: Verify the tag name to unset is correct.
ADVM-03308: The ADVM compatibility attribute for the diskgroup must be set to
version 11.2.0.2.0 to allow the acfsutil repl and tag commands.
Cause: The ADVM compatibility attribute has not been upgraded to version
11.2.0.2.0 or beyond.
Action: Use the ASMCA tool or the SQL ALTER DISKGROUP statement to
upgrade COMPATIBLE.ADVM attribute.
ADVM-03309: path name string does not resolve to an ACFS file system
Cause: A path name supplied on an 'acfsutil tag' command did not resolve to an
ACFS file system.
Action: Remove the non-ACFS path name from the 'acfsutil tag' command.
ADVM-03310: amount of change since mount: number MB
Cause: Informational
Action: None
ADVM-03313: unable to collect ACFS statistics for mount point string
Cause: 'acfsutil info fs -s' was unable to communicate with the ACFS driver.
Action: Verify that the file system is online and that the ADVM/ACFS drivers are
loaded and running.
ADVM-03314: interval cannot exceed number seconds
Cause: Statistics interval exceeded maximum number of seconds per interval.
Action: Select an interval that is less than or equal to 2592000 seconds and retry
"acfsutil info fs -s".
ADVM-03315: count cannot exceed number
Cause: Number of statistics intervals exceeded maximum number allowed.
Action: Select a total count that is less than or equal to 2^63-1 and retry "acfsutil
info fs -s".
ADVM-00501 to ADVM-11069 98-25
ADVM-03316: interval must be a positive integer
Cause: A zero or negative integer was provided.
Action: Provide a positive integer for the statistics interval.
ADVM-03317: unable to set tag on file "string" because its tag name storage is full
Cause: The limit of the file's tag name storage has been reached.
Action: Remove any unused tags on this file and try the command again.
ADVM-03318: unable to set tag name "string" because this name is reserved
Cause: The tag name specified is reserved.
Action: Choose another tag name which is not reserved.
ADVM-03319: Set tag on file: string
Cause: Informational
Action: None
ADVM-03320: Removing tag(s) on file: string
Cause: Informational
Action: None
ADVM-03321: The ADVM compatibility attribute for the diskgroup is below the
required version (string) for the 'acfsutil tag' commands.
Cause: The ADVM compatibility attribute has not been upgraded to a version
that supports tagging.
Action: Use the ASMCA tool or the SQL ALTER DISKGROUP statement to
upgrade COMPATIBLE.ADVM attribute to the specified version.
ADVM-03322: The ADVM compatibility attribute for the diskgroup is below the
required version (string) for the 'acfsutil repl' commands.
Cause: The ADVM compatibility attribute has not been upgraded to a version
that supports replication.
Action: Use the ASMCA tool or the SQL ALTER DISKGROUP statement to
upgrade COMPATIBLE.ADVM attribute to the specified version.
ADVM-03323: stringc option requires the stringt option
Cause: The 'c' option was specified without the 't' option. The 'c' option invokes
case insensitive substring matching on the tag names specified using the 't' option.
Action: To use the 'c' option, add the 't' option to specify a tag.
ADVM-03324: Unable to obtain metric data for string
Cause: An internal ioctl operation to access metric data from ACFS file system
failed. This message is accompanied by other message(s) providing details on the
error.
Action: Correct the problem indicated by the other message(s). If the cause of the
problem is unclear, contact Oracle Support Services.
ADVM-03344: Error, strings option with repetition interval applied to multiple file
systems.
Cause: A request to report file system statistics periodically was rejected because
it applied to multiple file systems. A single file system must be specified explicitly
when supplying the 's' option with a time interval.
98-26 Oracle Database Error Messages
Action: Reissue the request specifying a single file system or omitting the
repetition interval.
ADVM-03450: Continue to panic the cluster [y|n] ?
Cause: The 'acfsutil panic' command was issued to panic the cluster.
Action: Respond Y(yes) to proceed or N(no) to cancel.
ADVM-03451: Continue to panic the system [y|n] ?
Cause: The 'acfsutil panic' command was issued to panic the system.
Action: Respond Y(yes) to proceed or N(no) to cancel.
ADVM-03452: failed to move file or directory from string to string
Cause: An attempt to rename a file or directory failed because the target was an
existing, populated directory or the user permissions were insufficient to perform
the operation.
Action: Retry the operation after removing the target files or correcting the
permissions.
ADVM-03500: Unable to access kernel persistent log entries.
Cause: Could not get or set persistent log configuration data.
Action: Make sure that the Oracle kernel drivers are loaded/started (run
'acfsdriverstate loaded'). If loaded/started, make sure that you have
root/administrator privileges.
ADVM-03501: The 'query' option may not be used with any other options.
Cause: Additional options to 'query' were specified on the command line.
Action: Do not use any other options with the 'query' option.
ADVM-03502: The specified maximum log file size is less than number MB or is
greater than number MB.
Cause: An invalid log file size was entered on the command line.
Action: Specify a value equal to or greater than the minimum size and equal to or
less than the maximum size.
ADVM-03503: The specified interval is less than number seconds.
Cause: An invalid interval value was entered on the command line.
Action: Enter an interval value equal to or greater than the minimum.
ADVM-03504: An invalid high water level value (number percent) was specified.
Cause: The high water level must be greater than the low water level and less
than 100 percent.
Action: Enter a valid high water level value.
ADVM-03505: An invalid low water level value (number percent) was specified.
Cause: The low water level must be greater than zero and less than the high water
level.
Action: Enter a valid low water level value.
ADVM-03506: The selected percentage does not generate an even integer. Changing
to number percent.
Cause: The specified percentage of the buffer size generates a remainder.
Action: None. Informational.
ADVM-00501 to ADVM-11069 98-27
ADVM-03507: The specified buffer size is less than number KB or is greater than
number KB.
Cause: An invalid buffer size value was entered on the command line."
Action: Enter a value equal to or greater than the minimum or equal to or less
than the maximum size.
ADVM-03508: The specified maximum number of log files is less than number or
greater than number.
Cause: An invalid maximum number of log files was entered on the command
line.
Action: Specify a value equal to or greater than the minimum and equal to or less
than the maximum.
ADVM-03509: string is not a Grid infrastructure home.
Cause: An invalid Grid infrastructure home was entered on the command line.
Action: Specify a valid Grid infrastructure home.
ADVM-03510: There are more log files on the system than are being configured.
Removing the oldest files.
Cause: A new, lower, maximum number of allowable OKS persistent log files was
configured and there are currently more log files on the system. Deleting the oldest
files."
Action: None. Informational.
ADVM-03511: Deleting string.
Cause: A log file was deleted to satisfy the new configuration.
Action: None. Informational.
ADVM-03512: Renaming string to string.
Cause: A log file was renamed to place it in time modified sequential order.
Action: None. Informational.
ADVM-03513: The OKS persistent log configuration settings cannot be queried.
Cause: The OKS persistent log was not running.
Action: Start the log with 'acfsutil plogconfig -d <gridhome>'.
ADVM-03514: The directory 'string' can not be converted to an absolute path.
Cause: A directory name was specified that could not be converted to an absolute
path. The name was either an invalid relative path or, on Windows, included an
invalid drive letter.
Action: Specify the directory name in the form of an absolute path. On Windows,
the absolute path includes the drive letter.
ADVM-03528: failed to determine Oracle Base
Cause: The operation to retrieve the Oracle Base location failed. This message is
accompanied by other message(s) providing details on the error.
Action: Correct the problem indicated by the other message(s). If the solution is
not clear, contact Oracle Support Services.
ADVM-03529: Warning: The 'd' option was specified with an argument, which is no
longer used - argument ignored.
98-28 Oracle Database Error Messages
Cause: 'acfsutil plogconfig' now gets the log location internally. The specified log
location was ignored and the command continued using the internally derived
location.
Action: None
ADVM-03530: The 'terminate' option may not be used with any other options.
Cause: Conflicting options were specified on the command line.
Action: Do not use any other options with the 'terminate' option.
ADVM-03539: Base time stamp not found in log file.
Cause: Informational. The likely cause is that the running OKS driver is an older
version that does not support time stamp conversion.
Action: None
ADVM-03540: The specified interval is greater than number seconds.
Cause: An invalid interval value was entered on the command line.
Action: Enter an interval value equal to or less than the maximum.
ADVM-03541: The symbolic link 'string' to 'string' cannot be created.
Cause: Likely, the link name was a non-empty directory. OKS persistent logging
was started but no symbolic was created to the target directory.
Action: If a symbolic link is desired, delete the link target and its contents and
reissue the command.
ADVM-03542: The specified OKS log directory 'string' is invalid because it is NFS
mounted.
Cause: The specified logging directory was NFS mounted.
Action: Enter a node local location for the OKS log.
ADVM-03543: The OKS persistent log is not active.
Cause: The OKS persistent log was not running.
Action: Start the log with 'acfsutil plogconfig -d [log_dir]'.
ADVM-03544: Directory 'string' exists as a file.
Cause: An OKS persistent log directory could not be created because it exists as a
file.
Action: Either delete the file or choose another directory name.
ADVM-03602: Plug-in is already enabled on 'string'
Cause: An attempt was made to enable the plug-in when it is already enabled.
Action: First disable the plug-in then retry the command.
ADVM-03603: Plug-in is not enabled on 'string'
Cause: A plug-in command was attempt when the plug-in is not enabled.
Action: Enable the plug-in and then retry the command.
ADVM-03604: Unable to perform plug-in operation on 'string'
Cause: The plug-in operation failed. This message is accompanied by other
message(s) providing details on the error.
Action: Correct the problem indicated by the other message(s). If the solution is
not clear, contact Oracle Support Services.
ADVM-00501 to ADVM-11069 98-29
ADVM-03610: Invalid plug-in metric type: string
Cause: An invalid plug-in metric type was specified.
Action: Enter a valid metric type from the following list: "acfsmetric1"
ADVM-03611: Invalid interval specified.
Cause: An invalid interval was specified.
Action: Enter a valid interval between 1 and 3600 seconds.
ADVM-03612: Unable to retrieve list of plug-in enabled tags.
Cause: ACFS was unable to retrieve the list of tags for which the plug-in is
collecting metrics. This message is accompanied by other message(s) providing
details on the error.
Action: Correct the problem indicated by the other message(s). If the solution is
not clear, contact Oracle Support Services.
ADVM-03613: Unable to write plug-in config file.
Cause: ACFS was unable to write the plug-in config file to disk.
Action: Try the command again. If the problem persists, contact Oracle Support
Services.
ADVM-03614: Plug-in cannot be enabled for more than number tags.
Cause: An attempt was made to enable the plug-in for more than the maximum
allowed number of tags.
Action: Enable plug-in with fewer tags.
ADVM-03615: An error occured when copying the list of tags.
Cause: This is an internal error.
Action: Try the command again. If the problem persists, contact Oracle Support
Services.
ADVM-03621: missing plug-in metric type
Cause: No plug-in metric type was specified.
Action: Enter a valid metric type from the following list: "acfsmetric1"
ADVM-03623: unable to modify the ACFS registration for mount point 'string'
Cause: Could not modify the ACFS registration for the specified mount point.
Action: Examine the accompanying error messages and respond accordingly. If
the solution is not clear, contact Oracle Support Services.
ADVM-03624: unable to modify registration for ACFS volume 'string'
Cause: Could not modify the ACFS registration for the ACFS volume.
Action: Examine the accompanying error messages and respond accordingly. If
the solution is not clear, contact Oracle Support Services.
ADVM-03626: invalid combination of -C and -f options
Cause: The 'acfsutil log' command was issued with both the -f and -C options.
This is a conflict, because the log file names are pre-specified for -C and may not
be specified using -f.
Action: Re-issue the 'acfsutil log' command with only the desired option. With -C,
the log files will be generated in the persistent log directory in the form
yymmddhhmmss.log. With -f the specified name will be used.
98-30 Oracle Database Error Messages
ADVM-03627: logging behavior change specified with cluster option
Cause: The 'acfsutil log' command was issued with both the -C option and and an
option that modifies the logging behavior.
Action: Re-issue the 'acfsutil log' command without the -C option to modify the
ACFS logging behavior. To create logs on all cluster nodes, issue 'acfsutil log -C'
with no other options.
ADVM-04001: Failed to open path string. Verify that string exists.
Cause: Path could not be opened.
Action: Verify the path is accessible before retrying.
ADVM-04002: unable to allocate a buffer
Cause: A request for process virtual memory by acfsdismount command failed.
This message is accompanied by other message(s) providing details on the error.
Action: Correct the problem indicated by the other message(s). If possible, change
options to reduce required memory and/or take steps to increase memory
available to the process. Otherwise, report this error to Oracle Support Services.
ADVM-04011: Failed to open volume string. Verify that string exists.
Cause: Volume could not be opened.
Action: Verify the ASM instance is operational and the volume is enabled and
accessible before retrying.
ADVM-04013: acfsdismount /all operation did not complete. Unable to retrieve a
mount point from the list of active ACFS file systems to dismount. It is possible
that not all file systems were dismounted.
Cause: Failed to obtain the next file system to dismount.
Action: Use acfsmountvol to determine if there are any file systems still mounted
and reissue 'acfsdismount /all' if necessary.
ADVM-04032: removing administrative network share for mount point string at
share name 'string'
Cause: Informational
Action: None
ADVM-04033: administrative network share 'string' does not share mount point
string as expected
Cause: Attempted to remove the administrative network share associated with
the specified ACFS mount point, but the network share does not share the
specified ACFS mount point as expected.
Action: Examine the network share at the specified share name. If the network
share shares an unmounted ACFS file system, manually remove the network share
using 'net share <share name> /delete'
ADVM-04034: administrative network share for mount point string does not exist at
share name 'string'
Cause: Informational
Action: None
ADVM-04035: retrieving information for administrative network share 'string'
failed
ADVM-00501 to ADVM-11069 98-31
Cause: While removing the administrative network share associated with the
specified ACFS mount point, failed to retrieve information on the administrative
network share. This message is accompanied by other messages providing details
on the error.
Action: Check for a network share at the specified share name. If a network share
exists at the specified share name and it shares an unmounted ACFS file system,
manually remove the network share using 'net share <share name> /delete'
ADVM-04036: removing administrative network share for mount point string at
share name 'string' failed
Cause: Failed to remove the administrative network share associated with the
specified ACFS mount point. This message is accompanied by other messages
providing details on the error.
Action: Manually remove the administrative network share at the specified share
name using 'net share <share name> /delete'
ADVM-04037: could not remove administrative network share for mount point
string at share name 'string'
Cause: Failed to remove the administrative network share associated with the
specified ACFS mount point. This message is accompanied by other messages
providing details on the error.
Action: Correct the error indicated by the accompanying messages.
ADVM-04038: Volume string is still mounted. Dismount will complete as soon as
activity ceases on the file system.
Cause: At the conclusion of the file system dismount request, the file system was
still mounted. This could be a result of open files on the mount point. The
dismount will finish as soon as activity ceases on the file system.
Action: To force dismount to complete, terminate any processes or applications
that are using the file system.
ADVM-04058: Ignoring unsupported ACFS command option: 'string'
Cause: An unsupported 'umount.acfs' command option was specified.
Action: No action required. The unmount will proceed without the option.
ADVM-04150: unable to retrieve mount point information from the ACFS driver
Cause: During unmount processing, an attempt to retrieve mount point
information from the ACFS driver failed.
Action: Verify the mount point is a valid ACFS file system before retrying the
unmount command. If the problem persists, contact Oracle Support Services.
ADVM-04151: unmount of mount point string failed
Cause: of the problem is unclear, contact Oracle Support Services.
Action: Correct the problem indicated by the other message(s). If the
ADVM-05001: must specify 'primary' or 'standby'
Cause: Command syntax requires 'primary' or 'standby' argument.
Action: At command line, indicate primary or standby for replication command.
ADVM-05002: must provide an Oracle Net alias to the primary replication site
Cause: The Oracle Net alias to connect to the primary replication site was not
specified.
98-32 Oracle Database Error Messages
Action: Provide Oracle Net alias to connect to the primary replication site.
ADVM-05003: must provide a primary mount point
Cause: The mount point on the replication primary site for the file system to be
replicated was not provided.
Action: Provide an existing mount point on the primary site for the file system to
be replicated.
ADVM-05004: cannot allocate a list of tag names
Cause: A request for process virtual memory failed. This message is accompanied
by other message(s) providing details on the error.
Action: Correct the problem indicated by the other message(s). If possible, change
options to reduce required memory and/or take steps to increase memory
available to the process. Otherwise, report this error to Oracle Support Services.
ADVM-05005: invalid tag name: string
Cause: User specified a tag name that has incorrect syntax.
Action: See the platform specific Oracle documentation for correct syntax for
ACFS tag names.
ADVM-05006: unable to initialize replication process data structures
Cause: Failed to determine path names for replication directories.
Action: Verify the specified mount point is an ACFS file system.
ADVM-05007: cannot initialize interrupt signal handler
Cause: The system could not initialize the mechanism to handle interrupts.
Action: Contact Oracle Support Services.
ADVM-05008: cannot lock file string to serialize ACFS replication commands
Cause: of the problem is unclear, contact Oracle Support Services.
Action: Correct the problem indicated by the other message(s). If the
ADVM-05009: ACFS replication initialization is already in progress.
Cause: Initialization was in progress on the replication site.
Action: Wait for the other initialization on replication site to complete.
ADVM-05010: ACFS replication initialization is still in progress.
Cause: The command cannot be run until replication initialization completes.
Action: Monitor initialization progress with the 'acfsutil repl info' command.
ADVM-05011: cannot open directory: string
Cause: of the problem is unclear, contact Oracle Support Services.
Action: Correct the problem indicated by the other message(s). If the
ADVM-05012: ACFS replication is already initialized.
Cause: ACFS replication has already been initialized on this system.
Action: Initialization cannot be undone unless replication is terminated or the file
system is reformatted.
ADVM-05013: ACFS replication cannot be initialized.
Cause: of the problem is unclear, contact Oracle Support Services.
Action: Correct the problem indicated by the other message(s). If the
ADVM-00501 to ADVM-11069 98-33
ADVM-05014: cannot verify replication configuration
Cause: of the problem is unclear, contact Oracle Support Services.
Action: Correct the problem indicated by the other message(s). If the
ADVM-05015: cannot cleanup replication directories
Cause: The application failed to cleanup from a previous replication instantiation.
Action: Verify user permissions and that the replication directory is available.
ADVM-05016: cannot update replication configuration with new trace level
Cause: The application was unable to communicate with the ACFS driver.
Action: Verify that the ADVM/ACFS drivers are loaded and running.
ADVM-05017: cannot create file: string
Cause: The application failed to create the specified file. This message is
accompanied by other message(s) providing details on the error.
Action: Correct the problem indicated by the other message(s). If the solution is
not clear, contact Oracle Support Services.
ADVM-05018: cannot get primary ADVM volume information for string
Cause: The application failed to get the ADVM volume path for the mounted
ACFS file system.
Action: Verify that the file system is mounted and of type ACFS.
ADVM-05019: cannot allocate space for the ADVM volume path
Cause: A request for process virtual memory failed. This message is accompanied
by other message(s) providing details on the error.
Action: Correct the problem indicated by the other message(s). If possible, change
options to reduce required memory and/or take steps to increase memory
available to the process. Otherwise, report this error to Oracle Support Services.
ADVM-05020: cannot start replication daemons
Cause: CRS has failed to start the replication daemons.
Action: Verify that CRS is running. Check the CRS logs to determine why the
replication daemons failed to start.
ADVM-05021: cannot stop replication daemons
Cause: CRS has failed to stop the replication daemons.
Action: Verify that CRS is running. Check the CRS logs to determine why the
replication daemons failed to stop.
ADVM-05022: internal CRS error
Cause: The application failed to initialize communication with CRS.
Action: Verify that CRS is running. Check the CRS logs to determine why the
replication daemons failed to start.
ADVM-05023: error checking for file: string
Cause: Informational
Action: None
ADVM-05024: The standby replication site is initialized. ACFS replication will
begin.
Cause: Informational
98-34 Oracle Database Error Messages
Action: None
ADVM-05025: waiting for the standby replication site to initialize
Cause: Informational
Action: None
ADVM-05026: caught interrupt; ACFS replication initialization is shutting down.
Cause: Informational
Action: None
ADVM-05027: cannot remove file: string
Cause: File system was not accessible.
Action: Verify the ASM instance is operational and the state of the file system
using 'acfsutil info fs' before retrying the command.
ADVM-05028: cannot obtain current time for events log
Cause: The application failed to get the current time for logging.
Action: Contact Oracle Support Services.
ADVM-05029: cannot write to the events log
Cause: The application failed to write to the specified file. This message is
accompanied by other message(s) providing details on the error.
Action: Correct the problem indicated by the other message(s). If the solution is
not clear, contact Oracle Support Services.
ADVM-05030: cannot clean up configuration file
Cause: Initialization failed and the configuration file created during failed
initialization could not be removed.
Action: Contact Oracle Support Services.
ADVM-05031: standby file system is not empty
Cause: The file system was not empty.
Action: Use an empty standby file system; either reformat the file system or
remove all files and directories under <standby mount point>/.
ADVM-05032: unable to determine user permissions
Cause: An error occurred attempting to acquire the user permissions. This
message is accompanied by other message(s) providing details on the error.
Action: Correct the problem indicated by the other message(s). Otherwise, report
this error to Oracle Support Services.
ADVM-05033: must provide a standby mount point
Cause: A mount point on the standby replication site was not provided.
Action: Provide an existing mount point with an empty file system on the
standby replication site.
ADVM-05034: cannot obtain path for directory: string
Cause: The application failed to locate the specified directory.
Action: Verify that the replication directory is available.
ADVM-05035: cannot open file for write: string
ADVM-00501 to ADVM-11069 98-35
Cause: The application failed to open the specified file. This message is
accompanied by other message(s) providing details on the error.
Action: Correct the problem indicated by the other message(s). If the solution is
not clear, contact Oracle Support Services.
ADVM-05036: cannot write to file: string
Cause: The application failed to write to the specified file. This message is
accompanied by other message(s) providing details on the error.
Action: Correct the problem indicated by the other message(s). If the solution is
not clear, contact Oracle Support Services.
ADVM-05037: cannot move file string to directory string
Cause: The application failed move the specified file.
Action: Verify that the replication directory is available.
ADVM-05038: cannot register Oracle Net service name
Cause: Unable to register the Oracle Net service name with the ASM instance.
Action: Verify the ASM instance is operational and the state of the file system
using 'acfsutil info fs' before retrying the command.
ADVM-05039: cannot unregister Oracle Net service name
Cause: Unable to unregister the Oracle Net service name from the ASM instance.
Action: Verify the ASM instance is operational and the state of the file system
using 'acfsutil info fs' before retrying the command.
ADVM-05040: cannot obtain Oracle Net service name from alias provided
Cause: Unable obtain the Oracle Net service name from the Oracle Net alias
provided on the command line.
Action: Verify that the Oracle Net alias exists and is properly formed.
ADVM-05041: Oracle Net service name is greater than string bytes
Cause: The Oracle Net service name specified for replication is greater than the
maximum allowed.
Action: Reduce the size of the Oracle Net service name being used for replication.
ADVM-05042: insufficient privileges to perform replication command.
Administrator access is required.
Cause: The caller does not have sufficient privileges to perform the replication
command.
Action: Execute the replication command from a user with administrator access.
ADVM-05043: insufficient privileges to perform replication command. ASM
administrator group access is required.
Cause: The caller does not have sufficient privileges to perform the replication
command.
Action: Execute the replication command from a user with ASM administrator
group access.
ADVM-05044: cannot obtain node name
Cause: Unable to get local node name through CRS.
Action: Verify that CRS is running.
98-36 Oracle Database Error Messages
ADVM-05045: invalid interval specified for replication statistics
Cause: The caller specified an invalid time interval for replication statistics.
Action: Verify the syntax of the time interval using 'acfsutil repl info' help flag and
retry.
ADVM-05046: invalid date range specified for replication statistics
Cause: The caller specified an invalid date range for replication statistics.
Action: Verify the syntax of the date range using 'acfsutil repl info' help flag and
retry.
ADVM-05047: time specified is in the future
Cause: The caller specified a date in the future.
Action: Verify the time specified is before the current time.
ADVM-05048: start time specified is newer than the end time specified
Cause: The caller specified a date range where the start time was more recent the
end time.
Action: Verify the start time is before the end time.
ADVM-05049: validating the remote connection
Cause: Informational
Action: None
ADVM-05050: remote connection cannot be established
Cause: The user name, password, or Oracle Net alias used to connect to the
remote site was not correct or the remote site was unreachable.
Action: Verify the connection information is correct and the status of the remote
site.
ADVM-05051: remote connection has been established
Cause: Informational
Action: None
ADVM-05052: standby replication site requires reinitialization
Cause: Initialization was unable to complete on the primary replication site and
left the standby replication site in an indeterminate state.
Action: On the standby replication site, run 'acfsutil repl terminate' and 'acfsutil
repl init' before retrying initialization on the the primary replication site.
ADVM-05053: replication's Oracle Net service name conflicts with the existing
ASM service name
Cause: The service name for replication specified in the Oracle Net alias conflicts
eith the Oracle Net service name that ASM uses.
Action: Review the Oracle Net alias for replication in tnsnames.ora and use a
different service name for the replication alias.
ADVM-05054: standby replication file system is mounted on more than one cluster
node
Cause: The standby replication file system was mounted on more than one node
in the cluster.
Action: Unmount the file system on all but one node on the standby replication
site and retry the initialization.
ADVM-00501 to ADVM-11069 98-37
ADVM-05055: invalid connection string for the primary replication site
Cause: The user name, password, or Oracle Net alias used to connect to the
primary replication site was not correct or was unreachable.
Action: Verify the connection information is correct and the status of the primary
replication site.
ADVM-05056: invalid connection string for the standby replication site
Cause: The user name, password, or Oracle Net alias used to connect to the
standby replication site was not correct or was unreachable.
Action: Verify the connection information is correct and the status of the standby
replication site.
ADVM-05058: command issued on the incorrect replication site
Cause: The command was issued on the incorrect replication site.
Action: Verify the command syntax. If issued on the primary file system, reissue
on the standby file system. If issued on the standby file system, reissue on the
primary file system.
ADVM-05059: ACFS replication not initialized
Cause: ACFS replication information cannot be retrieved as replication has not
been initialized.
Action: None
ADVM-05060: waiting for ACFS replication to terminate
Cause: Informational
Action: None
ADVM-05061: ACFS replication command interrupted
Cause: Informational
Action: None
ADVM-05062: cannot query CRS resource
Cause: The application failed to communicate with CRS.
Action: Verify that CRS is running. Check the CRS logs to determine why the CRS
resource is not responding.
ADVM-05063: cannot relocate CRS resource
Cause: The application failed to relocate CRS resource.
Action: Verify that CRS is running. Check the CRS logs to determine why the CRS
resource cannot be relocated.
ADVM-05064: the service name 'string' is not registered on the standby site
Cause: Possible causes include: 1.) Replication was not initialized on the standby
site. 2.) Mismatched service names. If the -c option is not used, the service name
specified in the alias for the standby file system did not match the service name
specified for the primary file system in the alias on the standby site. 3.) The alias
for the standby site referred to the wrong set of nodes.
Action: Possible actions include: 1.) Verify replication is initialized on the standby
site. 2.) Verify the service name used to connect to the standby site matches the one
registered on the standby site. Run 'lsnrctl status' on the standby site to verify. 3.)
Verify that the nodes listed in the standby alias have the standby file system
mounted.
98-38 Oracle Database Error Messages
ADVM-05065: cannot transfer files to the standby file system 'string'
Cause: Possible causes include: 1.) The standby mount point did not exist or was
not an ACFS file system. 2.) The standby file system was full.
Action: Possible actions include: 1.) Verify that the standby mount point exists
and is an ACFS file system. 2.) Verify that there is free space on the standby file
system.
ADVM-05066: ACFS replication is already paused
Cause: ACFS replication was paused by a previous call.
Action: None
ADVM-05067: cannot rename file string to string in directory string
Cause: The application failed to rename the specified file.
Action: Verify that the replication directory is available.
ADVM-05068: ACFS replication has not been paused
Cause: ACFS replication was not paused. Resume operation is not needed.
Action: None
ADVM-05069: ACFS replication update must specify at least one attribute
Cause: The command to update the replication configuration did not specify any
attributes to update.
Action: Specify at least one replication attribute to be updated.
ADVM-05070: command must be run on the primary replication site
Cause: 'acfsutil repl update' command was not run on the primary replication
site.
Action: Execute 'acfsutil repl update' on the primary replication site.
ADVM-05071: invalid username or password used to connect to the standby site
Cause: The username or password specified on the command line or in the wallet
was incorrect.
Action: Verify the username and password are correct when connecting to the
standby site.
ADVM-05072: cannot open events file string
Cause: Failed to open events log file.
Action: Verify the ASM instance is operational and the state of the file system
using 'acfsutil info fs' before retrying the command.
ADVM-05073: cannot query events log file
Cause: Failed to query events log file.
Action: Verify the ASM instance is operational and the state of the file system
using 'acfsutil info fs' before retrying the command.
ADVM-05075: cannot terminate replication
Cause: Failed to terminate replication.
Action: Verify the ASM instance is operational and the state of the file system
using 'acfsutil info fs' before retrying the command.
ADVM-05076: unable to determine CRS user/group
Cause: The application failed to determine CRS user and/or group.
ADVM-00501 to ADVM-11069 98-39
Action: Verify that CRS is running. Check the CRS logs to determine why the CRS
user and/or group cannot be determined.
ADVM-05077: could not complete replication synchronization
Cause: Failed to complete synchronization of primary and standby replication
sites.
Action: Verify the ASM instance is operational and the state of the file system
using 'acfsutil info fs' before retrying the command.
ADVM-05078: failed to synchronize primary and standby replication sites
Cause: Failed to synchronize replication sites.
Action: Verify the ASM instance is operational and the state of the file system
using 'acfsutil info fs' before retrying the command.
ADVM-05079: waiting for replication update to complete
Cause: Informational
Action: None
ADVM-05083: Initialization of the primary file system could not complete because
the standby is already configured for replication.
Cause: The standby file system was not expecting initialization data from this
primary. Possible causes include:
1. Stale replication state detected on standby file system from a previous
instantiation.
2. An incorrect replication standby site was supplied.
3. An incorrect replication standby file system was supplied.
Action: 1. Run 'acfsutil repl terminate' on the standby site for the standby file
system before retrying the initialization of the primary.
2. Verify the correct standby site is used.
3. Verify the correct standby file system is used.
ADVM-05084: The replication standby file system has been newly initialized and is
refusing files from the primary. The primary may need to be terminated and
newly initialized.
Cause: The standby file system was not expecting any data from the primary
except initialization data. A possible cause may be the standby file system was
terminated and newly initialized, but the primary was not.
Action: Verify the primary site and primary file system. Run 'acfsutil repl
terminate' on the primary site for the primary file system before retrying the
initialization of the standby.
ADVM-05085: cannot start replication because incompatible ACFS features already
exist
Cause: Failed to start replication: Either security or encryption or both is enabled
on the file system.
Action: Undo security or encryption or both, then try to initialize replication
again. To undo encryption and security respectively: acfsutil encr set -m
<mount-point> -u acfsutil sec prepare -m <mount-point> -u
ADVM-05086: listener is not running on the standby site
98-40 Oracle Database Error Messages
Cause: The listener was not started on the remote site or an incorrect node name
was specified in the standby alias definition.
Action: Verify the listener is started on the standby site. Check that the standby
alias contains the correct node names.
ADVM-05087: The event log does not cover the time range specifed.
Cause: The events log did not cover any portion of the time range specified in the
command.
Action: Change the time range or use an events log that covers the range
specified.
ADVM-05088: replicated file system size is below the minimum of stringG
Cause: An attempt was made to initialize replication on a file system that did not
have sufficient space.
Action: Resize the file system to at least the minimum size specified.
ADVM-05089: replication statistics cannot be queried on the standby site
Cause: An attempt was made to query the replication statistics on the standby
site.
Action: Query the replication statistics from the primary site.
ADVM-05090: interval is greater than string years
Cause: The interval specified was greater than the maximum allowed.
Action: Retry the command with a lower interval value.
ADVM-05091: The mount path specified exceeds the maximum length allowed on
this platform.
Cause: The specified mount path exceeded the maximum length on this platform.
Action: Use a valid mount path.
ADVM-05092: replicated file system free space is near the minimum threshold of
stringGB per active node, continuing with initialization
Cause: Initialization of replication was issued on a file system that is near the
minimum threshold of free space.
Action: Consider resizing the file system to allow for optimal replication
performance.
ADVM-05093: could not retrieve active node count on file system: string, error:
string
Cause: Could not get the number of nodes active on the specified file system.
Action: Verify at least one cluster node has the file system mounted, or address
the specified operating system dependent error code provided. If the solution is
not clear, contact Oracle Support Services.
ADVM-05094: replicated file system free space is below the minimum of stringGB
per active node, actual free space left: stringGB
Cause: An attempt was made to initialize replication on a file system that did not
have sufficient space.
Action: Resize the file system such that free space is at least the minimum size
specified.
ADVM-05158: Replication background processes are not running
ADVM-00501 to ADVM-11069 98-41
Cause: Replication background processes were stopped.
Action: Run 'acfsutil repl bg start <mountpoint>' to restart replication background
processes.
ADVM-05159: Last sync time with primary: string
Cause: Informational
Action: None
ADVM-05170: Cannot initialize replication while the cluster is in rolling migration
Cause: An attempt to initialize replication was rejected because the cluster was in
rolling migration. Replication initialization is not allowed during rolling
migration.
Action: Complete the rolling migration and then initialize replication.
ADVM-05171: Cannot terminate replication while the cluster is in rolling migration
Cause: An attempt to terminate replication was rejected because the cluster was in
rolling migration and the file system was mounted on more than one node.
Action: Either complete the rolling migration and then terminate replication, or
unmount this file system on the other nodes and then terminate replication.
ADVM-05172: Replication cannot be terminated because background processes are
not running.
Cause: Replication background processes were stopped and cannot finish
processing replication data.
Action: Run 'acfsutil repl bg start <mountpoint>' to restart replication background
processes and complete the apply of existing replication data, or run 'acfsutil repl
terminate standby immediate <mountpoint>' to terminate replication immediately
without applying the remaining replication data.
ADVM-05200: Stopping ACFS replication daemons on string
Cause: Informational
Action: None
ADVM-05201: Starting ACFS replication daemons on string
Cause: Informational
Action: None
ADVM-05202: ACFS replication daemons started successfully on string
Cause: Informational
Action: None
ADVM-05203: ACFS replication daemons stopped successfully on string
Cause: Informational
Action: None
ADVM-05204: Attempting to restart replication daemons on string
Cause: Informational
Action: None
ADVM-05205: Failed to initialize replication because A
再分享一下我老师大神的人工智能教程吧。零基础！通俗易懂！风趣幽默！还带黄段子！希望你也加入到我们人工智能的队伍中来！https://www.cnblogs.com/captainbed