ORA-57000 to ORA-59801

97 ORA-57000 to ORA-59801

ORA-57000: TimesTen IMDB error: string: Cause: An error occurred during a TimesTen operation.; Action: Look up the error code in the TimesTen error documentation to diagnose.
ORA-57005: TimesTen Grid transient transaction failure: string: Cause: A transaction failed because a TimesTen Grid element was temporarily unreachable.; Action: Roll back the transaction and immediately retry.
ORA-57006: TimesTen Grid transaction failure: string: Cause: A transaction failed because a TimesTen Grid element was temporarily unreachable.; Action: Roll back the transaction, wait for the element to recover, and retry the transaction. Element recovery may require administrator action.
ORA-57007: TimesTen Grid transient statement failure: string: Cause: A statement failed because a TimesTen Grid element was temporarily unreachable.; Action: Immediately retry the current statement.
ORA-57008: TimesTen Grid statement failure: string: Cause: A TimesTen Grid element is temporarily unavailable.; Action: Wait for the element to recover and retry the current statement. Element recovery may require administrator action.
ORA-59000: not all rebalance phases were run: Cause: The previous rebalance for the group did not run all of the phases.; Action: See GV$ASM_OPERATION for more details. Run all rebalance phases using the ALTER DISKGROUP REBALANCE command.
ORA-59001: Disk 'string' must be online before disk 'string'.: Cause: An attempt was made to online a disk that contains old copies of the data present in another offline disk.; Action: Online the disks in the correct order. FORCE option may be used to override this check.
ORA-59002: Disk revalidation failed for ASM disk group 'string' on instance string due to ORA-string.: Cause: The disk revalidation failure could be due to various reasons. Signaling ORA-15020 during discovery was a probable one. See the alert log for more details.; Action: Ensure that the disks in operation are visible to all the nodes in the cluster before issuing a retry.
ORA-59003: database is not prepared for split.: Cause: Split was issued on a database which is either not prepared or did not complete the last time.; Action: Prepare the database before issuing split on it or drop the existing mirror copy and then retry the split mirror operations.
ORA-59004: No rebalance is running for group string.: Cause: An attempt was made to modify the property of a rebalance that was not running.; Action: Issue the ALTER DISKGROUP REBALANCE command without the MODIFY keyword to schedule another rebalance.
ORA-59005: Oracle ASM IOServer functionality is not supported on this platform.: Cause: This platform did not support ASM IOServer functionality.; Action: Refer to the documentation for the list of platforms that support Oracle ASM IOServer functionality and consider moving to one of those platforms.
ORA-59006: connection request from stale database instance is rejected.: Cause: The database instance was attempting to fail over from a stale IOServer cluster.; Action: Restart the database instance to initiate a new connection.
ORA-59007: cannot find a usable network from the client: Cause: The database instance was not using any of the configured ASM networks.; Action: Check the ASM network configuration in the database instance.
ORA-59008: All configured ASM networks are unusable.: Cause: All configured ASM networks encountered an error. ASM IOServer was unable to proceed.; Action: Check the status of the configured ASM network interfaces. Restart the ASM IOServer instance after the interfaces become operational.
ORA-59009: ASM IOServer instance is not ready to accept clients.: Cause: ASM IOServer instance was not ready to accept clients.; Action: Execute 'alter system enable client access' for ASM IOServer instance to accept clients.
ORA-59010: cannot SHUTDOWN ASM IOServer instance with connected client string.: Cause: A SHUTDOWN command was issued to an ASM IOServer instance that had one or more connected clients.; Action: Stop all clients that are using this ASM IOServer instance and retry the SHUTDOWN command. Alternatively, use the SHUTDOWN ABORT command to force disconnection with all the clients.
ORA-59011: operation failure for group string because too many disks are offline: Cause: Too many disks were offline in the disk group.; Action: Ensure that the disks are online and retry the operation.
ORA-59012: Disk %0!s uses an invalid physical sector size (%1!s).: Cause: The disk used a physical sector size value that is not standard or is not currently supported.; Action: The disk cannot be used for an ASM disk group.
ORA-59013: Disk %0!s uses an invalid logical sector size (%1!s).: Cause: The disk used a logical sector size value that is not standard or is not currently supported.; Action: The disk cannot be used for an ASM disk group.
ORA-59014: file %0!s in disk group %1!s was not prepared for split: Cause: The specified file was not prepared for split.; Action: Check the accompanying error messages for more information about the reason for the failure.
ORA-59015: Oracle ASM scrubbing is disabled.: Cause: An attempt was made to perform Oracle ASM scrubbing but it was disabled.; Action: Enable Oracle ASM scrubbing.
ORA-59016: Disk group string cannot be mounted due to invalid symbols: Cause: A mount operation was attempted for a disk group that contains invalid characters in its name. Starting in version 12.2.0.2.0, disk group names should only contain alphanumeric characters and the underscore character.; Action: Use the 'renamedg' tool to change the disk group name to a valid name. Afterwards, change the names of the disks by mounting the disk group in restricted mode and using the ASM SQL command 'ALTER DISKGROUP name RENAME DISKS ALL'.
ORA-59017: Oracle ASM scrubbing is stopping a previous operation.: Cause: The system cannot accept new scrubbing operations if a previous one is being stopped.; Action: Wait until the previous Oracle ASM scrubbing operation stops completely before initiating a new one.
ORA-59018: Oracle ASM scrubbing requires an Allocation Unit size of at least 1 MB.: Cause: The operation was not executed because the Allocation Unit was less than 1 MB.; Action: Run the operation on a disk group with an Allocation Unit of at least 1 MB.
ORA-59019: cannot start SCRB process: Cause: The ASM Scrubbing Master (SCRB) process failed during startup.; Action: Review the alert log to find out the reason behind the process startup failure.
ORA-59020: dropping mirror copy '%0!s' in disk group '%1!s' is already in progress: Cause: The drop mirror copy was already issued on the specified file group.; Action: Wait for the previous drop mirror copy to complete. Check the ASM alert log or check that the corresponding file group is deleted using the V$ASM_FILEGROUP view.
ORA-59021: drop of child file '%0!s' in disk group '%1!s' is not allowed: Cause: The operation failed because child file deletion was attempted.; Action: Child files can be deleted collectively only as part of drop mirror copy operation.
ORA-59022: dropping mirror copy '%0!s' in disk group '%1!s' failed as prepare is not complete: Cause: Prepare of mirror copy has not completed; Action: Wait for the prepare mirror copy to complete. Check the ASM alert log or check that the split status of the file group using the V$ASM_FILEGROUP view.
ORA-59023: command requires attribute '%0!s' to be set to '%1!s': Cause: The disk group was still running the necessary background operations preventing the attribute name from setting to value value, which is a prerequisite for the command.; Action: Confirm that all disks in the disk group are online, and wait until the attribute is set to the proper value. The attribute may not get set to the proper value if any of the disks in the disk group are offline. This may take a while.
ORA-59024: dropping mirror copy '%0!s' in disk group '%1!s' failed as the file split is complete: Cause: Split of mirror copy has completed.; Action: None
ORA-59025: creation of mirror copy for database '%0!s' failed: Cause: Another mirror copy for the database existed when the operation was attempted or failure occurred when communicating with ASM instance.; Action: If a mirror copy exists with PREPARED state, then either create another database using the existing mirror copy or drop the existing mirror copy. If a mirror copy exists in FAILED state, then drop the mirror copy. Thereafter, retry the operation.
ORA-59026: dropping file group '%0!s' in disk group '%1!s' failed as the file group has prepared mirror copies: Cause: Dropping a file group with prepared mirror copies is not allowed.; Action: Drop all the prepared mirror copies and try again.
ORA-59027: file group redundancy cannot be modified when there is a mirror copy: Cause: A mirror copy for the database existed or the disk group was still running the necessary background operations preventing the file group redundancy change.; Action: Create another database using the existing mirror copy or drop the existing mirror copy and wait for the rebalance operations to complete. Then retry the operation.
ORA-59028: rebalance did not complete after the last mirror split operation on database '%0!s': Cause: Rebalance after the last mirror split operation was either still running or not scheduled yet.; Action: If a rebalance is already running allow it to complete, otherwise issue a new one.
ORA-59029: All ASM disks in %0!s are already online or being brought online.: Cause: An attempt was made to bring disks online that were either already online or were being brought online.; Action: Check the status of the disks before changing the ONLINE statement to exclude the disks in the failure group or disk group.
ORA-59030: disk group '%0!s' containing file group '%1!s' has too many offline disks: Cause: A mirror split operation failed because the disk group containing the files had insufficient number of online disks. This could prevent some files in the target database from being opened. The operation failed early to give the administrator a chance to fix the errors.; Action: Ensure that the disk group has the required number of disks online and then retry the command.
ORA-59031: operation cannot be run concurrently with other mirror split operations on mirror copy '%0!s' in disk group '%1!s': Cause: Another conflicting Mirror Split operation was already running.; Action: Retry after the conflicting Mirror Split operation has finished.
ORA-59032: rebalance did not complete after the last mirror split or change redundancy operation: Cause: The rebalance operation after the last mirror split operation or change redundancy was either still running or not scheduled yet.; Action: If a rebalance is already running, then allow it to complete; otherwise, issue the rebalance operation.
ORA-59033: failed to start Oracle ASM instance because it was unable to open SPFILE '%0!s': Cause: An attempt to start the Oracle ASM instance failed because the ASM server parameter file (SPFILE) could not be opened. The SPFILE was configured in the indicated disk group. One or more of the disks in the disk group were inaccessible. This was likely due to the remote node or nodes being inactive.; Action: Issue the 'olsnodes' command to retrieve the list of nodes in the cluster. Start up all the remote nodes in the cluster that were previously inactive. Issue the 'crsctl start cluster' command on this node and verify that the Oracle ASM instance is active.
ORA-59035: HARDCHECK error during I/O: Cause: A Hardware Assisted Resilient Data (HARD) check error was encountered by ASM Rebalance (ARB) process during I/O operations.; Action: See the alert log for more information. Reconnect to the database or the ASM instance. If the process termination resulted in instance termination, restart the instance.
ORA-59036: Offline disks prevent data reconstruction from parity redundancy.: Cause: An attempt to reconstruct data from parity redundancy failed because some disks in the disk group were offline.; Action: Bring all disks in the disk group online to make data reconstruction from parity redundancy feasible.
ORA-59037: dropping mirror copy '%0!s' in disk group '%1!s' failed: Cause: An attempt was made to drop a mirror copy that did not exist.; Action: Check V$ASM_DBCLONE_INFO for list of valid mirrors. Ensure that the specified mirror copy exists and retry the operation.
ORA-59038: Too many mirror copies found: Cause: An attempt was made to create a mirror copy of the database that already has the maximum number of mirror copies.; Action: Drop or split an existing mirror copy and retry operation.
ORA-59039: Oracle ASM scrubbing is already running.: Cause: An attempt was made to issue an ASM scrubbing operation when there was another scrubbing operation still running.; Action: Wait for the running operation to finish and try again. Or, stop the running operation with ALTER DISKGROUP DG SCRUB STOP.
ORA-59040: ASM file property has changed.: Cause: An attempt was made to issue an ASM scrubbing operation and there was a file that changed one property.; Action: Wait for the ASM scrubbing operation to retry the operation automatically.
ORA-59041: database '%0!s' has data files in multiple disk groups: Cause: A mirror split operation was issued on a database whose data files were located in multiple disk groups.; Action: Ensure that all the data files are located on the same disk group either by moving all the data files to a single disk group or by dropping the data files of other disk groups. And, then retry the operation.
ORA-59042: creation of database from '%0!s' using mirror copy '%1!s' in disk group '%2!s' failed: Cause: An attempt was made to create a database from a mirror copy that did not exist.; Action: Connect to the database and check V$ASM_DBCLONE_INFO for list of valid mirrors. Ensure that the specified mirror copy is created and then retry the operation.
ORA-59300: missing or invalid site name: Cause: The command did not specify a valid site name.; Action: Specify a valid site name.
ORA-59301: incorrect SITE token usage: Cause: Site names were provided for some disks in the SQL statement and missing for others.; Action: Either specify site names for all of the disks or none in the SQL statement and retry the operation.
ORA-59302: The attribute string must be string or higher.: Cause: An attempt was made to set an attribute to a version that was lower than the minimum supported.; Action: Set the attribute to at least the minimum supported version. Alternatively lower the minimum supported version and try again.
ORA-59303: The attribute string (string) of the diskgroup being mounted should be string or higher.: Cause: An attempt was made to mount a diskgroup whose compatibility was lower than the minimum supported.; Action: Advance the diskgroup compatibility by mounting it in restricted mode OR lower the minimum supported compatibility and try again.
ORA-59304: external and global users are not supported for ASM: Cause: A user type not supported by ASM was supplied.; Action: Check the Oracle ASM documentation that external and global users are not supported for ASM.
ORA-59305: The disk group being mounted is incompatible with this software version.: Cause: An attempt was made to mount a disk group using a software version that is incompatible with the disk group.; Action: Contact Oracle Support Services.
ORA-59306: The parameter 'string' is invalid.: Cause: The value of the parameter was invalid.; Action: Provide a valid value of the parameter.
ORA-59307: The disk group redundancy is not external.: Cause: An attempt was made to rename the disk fail group in a disk group whose redundancy type was not external.; Action: Specify a disk group whose redundancy type is external.
ORA-59308: The disk 'string' cannot be assigned to a site because the disk group 'string' contains Cluster Synchronization Services voting files.: Cause: An attempt to assign a site to a disk failed because the disk group contained Cluster Synchronization Services (CSS) voting files.; Action: Move the CSS voting files to a different disk group using the command 'crsctl replace votedisk' and retry the operation.
ORA-59309: Failure group name 'string' is already used by an existing ASM disk.: Cause: The specified failure group name was already used in this diskgroup.; Action: Specify a different failure group name.
ORA-59311: The specified ASM instance 'string' does not exist.: Cause: The specified ASM instance did not exist or was terminated.; Action: Specify a valid ASM instance name.
ORA-59312: Disk 'string' cannot be assigned to a site because it is an Oracle Exadata disk.: Cause: An attempt to assign a site to an Oracle Exadata disk failed because the operation is not allowed in Oracle Exadata.; Action: Run the command 'cellcli -e alter cell siteName' to update the cell site information.
ORA-59313: All mirrors of the block are lost, likely due to multiple storage failures.: Cause: There were multiple failures in the storage subsystem. All redundant copies of the block were lost and Oracle wrote the hexadecimal value BADFDA7A into the block location of the lost block to signify that the block data could not be recovered from a redundant copy.; Action: Check the system logs and storage logs to identify the failure that led to the lost block.
ORA-59314: file type not supported for the operation: Cause: The operation did not support files of the given type.; Action: Retry the operation with a file of supported type.
ORA-59315: Parity is not supported for file '%0!s' with type '%1!s'.: Cause: The given file type did not support the creation of parity files.; Action: Retry creating the parity files with a supported file type.
ORA-59316: ASM software is incompatible with disk group string due to missing patch string: Cause: The ASM software was not compatible with the disk group.; Action: Action: Apply the missing patch and retry the operation.
ORA-59317: client %0!s software is incompatible with disk group %1!s due to missing patch %2!s: Cause: The client software was not compatible with the disk group.; Action: Apply the missing patch on corresponding client software and retry the operation.
ORA-59318: ASM software is incompatible with disk group string COMPATIBLE.ASM string: Cause: The ASM software did not support the attribute value for COMPATIBLE.ASM.; Action: Check alert log to identify the missing patches, apply the patches, and retry the operation. Or, advance COMPATIBLE.ASM to a version that is supported by this software.
ORA-59319: database software is incompatible with disk group string COMPATIBLE.RDBMS string: Cause: The specified value for COMPATIBLE.RDBMS was not compatible with one or more clients.; Action: Check the ASM alert log for information about the clients and missing patches, apply the patches on the corresponding database software, and retry the operation.
ORA-59320: client %0!s software is incompatible with disk group %1!s patch %2!s: Cause: The client software was not compatible with the specified patch.; Action: Apply the missing patch on corresponding client software and retry the operation.
ORA-59321: ASM software is incompatible with disk group string patch string: Cause: The ASM software did not support enabling the specified patch.; Action: Apply the missing patch and retry the operation.
ORA-59322: database software is incompatible with disk group string patch string: Cause: The specified patch was not compatible with one or more clients.; Action: Check the ASM alert log for information about the clients and missing patches, apply the patches on corresponding database software, and retry the operation.
ORA-59323: cannot alter exclusive instance mode with more than once instance running: Cause: There was at least one other running ASM instance.; Action: Ensure that there is only one ASM instance when running the command.
ORA-59324: cannot alter exclusive instance mode outside of rolling migration or rolling patch: Cause: ASM cluster was not in rolling migration or rolling patch.; Action: ASM cluster needs to be in rolling migration or rolling patch.
ORA-59325: cannot start multiple ASM instances under exclusive mode: Cause: There was at least one other running ASM instance, and the ASM cluster was in exclusive mode.; Action: Ensure that the ASM cluster is not in exclusive mode when trying to bring up another ASM instance.
ORA-59326: ASM rolling mode exit prevented by string: Cause: One or more instances were blocking the rolling mode exit.; Action: Terminate the operation or wait until the reported operation is complete before attempting to take the cluster out of rolling mode.
ORA-59327: Dropping more fail groups is not allowed with disk group redundancy.: Cause: There was an attempt to drop at least one fail group, resulting in a fail group count below the recommended number.; Action: Use the FORCE option when trying to drop fail groups. Check the trace files of the Oracle ASM instance for more information.
ORA-59328: Offlining more failure groups is not allowed with disk group redundancy.: Cause: There was an attempt to offline at least one failure group resulting in a reduced number of online failure groups which is required to maintain the quorum consensus.; Action: Increase the number of online failure groups by onlining any offline failure groups or add enough quorum or regular failure groups.
ORA-59329: parity requires at least %0!s failure groups; found only %1!s: Cause: An attempt to set the redundancy specification of a file group to a parity protection scheme failed because of insufficient failure groups.; Action: Add enough failure groups to the disk group and then retry setting the file group redundancy.
ORA-59330: Disk zones are deprecated for disk groups that use virtually allocated allocation metadata.: Cause: Disk zones are no longer supported for disk groups that use virtually allocated allocation metadata.; Action: Do not attempt to create or modify a file with file attributes that are related to disk zones.
ORA-59500: unable to create member cluster 'string' in the absence of at least one disk group with the ACCESS_CONTROL.ENABLED attribute set to TRUE: Cause: An attempt was made to configure a member cluster when there was no mounted disk group with the ACCESS_CONTROL.ENABLED attribute set to TRUE.; Action: Set the ACCESS_CONTROL.ENABLED attribute to TRUE on an existing mounted disk group, mount a disk group that already has the ACCESS_CONTROL.ENABLED attribute set to TRUE, or create a disk group with the ACCESS_CONTROL.ENABLED attribute set to TRUE. Retry the operation.
ORA-59501: failed to register database with IOServer instance: Cause: The database instance failed to register with a valid IOServer instance.; Action: Check the alert log to identify the underlying reason for the failure and take the suggested corrective action.
ORA-59502: relocate client to string is already in progress: Cause: Another relocate client command was in progress.; Action: Retry the command after the initial relocate client command completes.
ORA-59503: client 'string' not allowed to reconnect: Cause: The client in Standard mode tried to reconnect to an ASM instance that did not support Flex mode.; Action: Check the ASM instance configurations within the cluster to match the client mode.
ORA-59504: rejecting a request originating from site 'string' to OFFLINE a disk 'string' configured in site 'string': Cause: The request to OFFLINE a disk was rejected by the ASM instance because the request was issued from a site that was different from the site in which the disk was configured.; Action: Retry the request from the site in which the disk is configured.
ORA-59505: instance 'string' shutting down on site 'string' due to rejected OFFLINE request: Cause: The instance terminated because the storage was inaccessible from the site requesting the disk OFFLINE.; Action: Issue the command 'crsctl query cluster sites <site_name>' to retrieve the status of the indicated site. Address the storage accessibility issues if the indicated site is in a QUARANTINED state. Issue the command 'crsctl modify cluster site <site_name> -s rejuvenate' to set the status to ONLINE after the storage access has been restored.
ORA-59506: database process in a network read for too long: Cause: A process on database instance connected to an ASM instance was in a SQL*Net read for too long. Possible reasons include failure of the node on which ASM instance was running or the communication channel disruption. This was detected by the Fence Monitor Process (FENC) or the ASM Background Process (ASMB) and the call was interrupted.; Action: Usually none, as the database instance fails over to another available ASM instance. If the problem keeps recurring, contact Oracle Support Services.
ORA-59507: mismatch of parameter '%0!s' between database and ASM instance '%1!s': Cause: The value for the parameter was different in the database instance and in the ASM instance to which it was connected.; Action: Set the parameter to the same value in both the instances.
ORA-59508: invalid GUID 'string' specified: Cause: The operation was rejected because the supplied Globally Unique Identifier (GUID) was syntactically invalid.; Action: Retry the command specifying the Globally Unique Identifier (GUID) as a text string of 32 hexadecimal digits (0-f) without a hyphen (-) character or the hexadecimal literal prefix (0x). Refer to the command inline help or product documentation for more information.
ORA-59509: failed to create member cluster '%0!s' because the specified GUID '%1!s' is already configured: Cause: An attempt to add the indicated member cluster with the indicated Globally Unique Identifier (GUID) was rejected because a member cluster with that GUID was already defined.; Action: Execute the command 'asmcmd lscc' to list the existing member clusters and cluster GUIDs. Retry the original command with a cluster GUID that has not already been configured.
ORA-59510: unable to modify member cluster 'string': Cause: An attempt to modify the member cluster failed.; Action: Check the alert logs and trace files of the Oracle ASM instance for more information about the reason for the failure, as well as check the accompanying error messages.
ORA-59511: member cluster '%0!s' already configured with disk access mode '%1!s': Cause: An attempt to modify the member cluster failed because it was already configured with the specified disk access mode.; Action: No action is required.
ORA-59512: The specified Oracle IOServer instance '%0!s' does not exist.: Cause: The specified Oracle IOServer instance did not exist or was terminated.; Action: Issue the 'srvctl status ioserver' command to list the active Oracle IOServer instances. Specify a valid Oracle IOServer instance name and retry the command.
ORA-59513: rejecting a request to relocate the client to string: Cause: The request to relocate a client was rejected because either the client or the ASM instance with the client connection was not running in Flex Mode.; Action: Check the configuration of both instances.
ORA-59514: The command is not supported on a storage server.: Cause: An attempt was made to run a command that was not supported on a storage server.; Action: Rerun the command on a member cluster.
ORA-59515: The service name was missing from the command for relocation.: Cause: The command for relocation was specified without the service name which is an invalid format.; Action: Specify a valid Oracle service name and instance name and retry the command: ALTER SYSTEM RELOCATE CLIENT TO <service_name/target_id>
ORA-59516: Could not connect to an IOS instance.: Cause: The instance failed to perform the specified operation because it could not locate a required IOS instance.; Action: Start the required IOS instance before starting the database instance.
ORA-59517: The command is not supported on an ACC.: Cause: An attempt was made to run a command that was not supported on ACC (ASM Client Cluster).; Action: No action is required.
ORA-59518: Client instance %0!s is already connected to this ASM instance.: Cause: A connection already existed from an ASM Background (ASMB) process to this ASM instance and was still active.; Action: None. Other ASMB processes from the client instance renew the disk groups. If the problem keeps recurring, contact Oracle Support Services.
ORA-59600: file string has too many mirror copies; string needed, string allowed: Cause: The specified file had too many mirror copies when the requested change was applied.; Action: Retry the command using a lower redundancy scheme, or reduce the existing redundancy level (if preparing a mirror split), or wait for the BALANCE phase of the rebalance operation to complete.
ORA-59601: file group redundancy cannot be modified when associated with a volume: Cause: An attempt was made to modify the redundancy of a file group which was associated with an ASM volume and contained at least one file.; Action: Drop the ASM volume associated with the file group and retry the operation.
ORA-59602: Moving ASM internal files to a file group is not allowed.: Cause: An attempt was made to execute an ALTER DISKGROUP MOVE FILE TO FILEGROUP statement on a metadata file used by ASM to manage the disk group.; Action: This action is not allowed.
ORA-59603: operation requires all disks in disk group string to be online: Cause: An attempt was made to modify the redundancy of a file group when some disks were offline.; Action: Drop the offline disks and wait for the rebalance operations to complete, or online the offline disks and wait for the online to complete. Then retry the operation.
ORA-59604: offline disks encountered during rebalance of disk group 'string': Cause: Rebalance was run in the presence of offline disks.; Action: Bring the offline disks online.
ORA-59605: file 'string' not available; file group 'string' has too many disks offline: Cause: A file identify operation failed because the file group specified was no longer available.; Action: Verify that all disks in this disk group are online or dropped and retry the command.
ORA-59606: cannot change redundancy of individual file types in file groups associated with a volume: Cause: An attempt was made to modify the redundancy of one or more file types in a file group associated with an ASM volume.; Action: Change the redundancy of the entire file group and not that of individual file types.
ORA-59607: COMPATIBLE.CLIENT is a read-only property by default: Cause: An attempt was made to modify the COMPATIBLE.CLIENT property of a file group without the FORCE option. COMPATIBLE.CLIENT property cannot be downgraded under any circumstances so caution should be exercised when manually modifying this property.; Action: Use the FORCE option to override this check.
ORA-59608: FORCE option cannot be used for file group property 'string': Cause: An attempt was made to use the FORCE option on a property that does not allow it.; Action: Remove the FORCE option and try again.
ORA-59609: cannot move a file that has prepared mirror copies: Cause: An attempt was made to move a file that has a prepared mirror copy.; Action: Create another database using the existing mirror copy or drop the existing mirror copy and wait for the rebalance operations to complete. Then, retry the operation.
ORA-59610: database version string is incompatible with file group 'string': Cause: The COMPATIBLE parameter for the Relational Database Management System (RDBMS) instance was lower than the value of the compatible.client property for the file group.; Action: Update the COMPATIBLE parameter for the RDBMS instance to a version greater than or equal to the compatible.client version.
ORA-59700: Failgroup string already belongs to site string: Cause: An attempt was made to add the specified failgroup to more than one site.; Action: Retry the operation providing the correct failgroup name and the site name while specifying the disk.
ORA-59701: Incorrect number of data sites string specified. Maximum allowed: string.: Cause: An attempt was made to create an extended redundancy disk group with an invalid number of sites.; Action: Retry the operation specifying valid number of sites in the disk group.
ORA-59702: Incorrect number of quorum sites string specified. Maximum allowed: string.: Cause: An attempt was made to create an extended redundancy disk group with an invalid number of sites.; Action: Retry the operation specifying valid number of sites in the disk group.
ORA-59703: Inconsistent site information in disk 'string': Cause: The site information stored in the disk header did not match disk group information.; Action: Drop the disk from the disk group or provide a site name that matches the site stored in the disk header.
ORA-59704: command requires at least string data sites and string quorum sites, discovered string data sites and string quorum sites: Cause: An insufficient number of sites were specified and discovered when creating an extended redundancy disk group.; Action: Check that the command specifies the required number of data sites and quorum sites, and that all of the specified disks are discovered by ASM. A query of the V$ASM_DISK fixed view shows the disks discovered by ASM.
ORA-59705: Dropping a site is not allowed.: Cause: An attempt was made to drop a site.; Action: Set the disks of the given site offline with 'ALTER DISKGROUP dg OFFLINE DISK disk' command.
ORA-59706: The specified allocation unit size 'string' is less than the minimum required for extended disk groups.: Cause: Extended disk groups required the allocation unit size to be at least 4M.; Action: Change the allocation unit size to at least 4M and retry.
ORA-59707: Site "string" does not exist in disk group "string".: Cause: The specified name did not match the site of any disks in the disk group. This usually indicates that the site name was specified incorrectly.; Action: Check the site name.
ORA-59708: Cluster site operation failed with error string.\nstring: Cause: This is an internal error.; Action: Check the accompanying error messages. Contact Oracle Support Services.
ORA-59709: No site identified for the disk string: Cause: The disk did not belong to any site.; Action: Specify the site information in the SQL command. In the case of an ASM appliance, cellcli command can also be used to record the site information for the disk. For non-appliance, asmcmd can be used.
ORA-59710: site information mismatch between disk group string and disk string: Cause: The site information of the specified disk did not match with the existing disks in the disk group.; Action: If the site information is associated with the existing disks in the disk group, then specify the site information for the new disk. If the site information is not associated with the existing disks in the disk group, then do not specify the site information for the new disk.
ORA-59711: The site identified by GUID 'string' does not exist.: Cause: An attempt to retrieve a site failed because there wasn't a configured site using the indicated Globally Unique Identifier.; Action: Add the indicated site using the command 'crsctl add cluster site site -guid guid'. Retry the original command. If retrying does not work, contact Oracle Support Services.
ORA-59712: The site identified by site name 'string' does not exist.: Cause: An attempt to retrieve a site failed because there wasn't a configured site using the indicated site name.; Action: Add the indicated site using the command 'crsctl add cluster site site'. Retry the original command. If retrying does not work, contact Oracle Support Services.
ORA-59713: The site name 'string' does not exist in the disk group 'string'.: Cause: An attempt was made to add a disk with a new site name to a disk group, which is not allowed.; Action: Change the site name to an existing one in the disk group and retry.
ORA-59714: invalid site name 'string' specified.: Cause: An invalid site name was supplied.; Action: Specify a site name which is at least one character but no more than 15 characters in length. The cluster name must be alphanumeric, it cannot begin with a numeric character, and it may contain hyphen (-) characters. However, it cannot end with a hyphen (-) character.
ORA-59715: missing site information in disk group 'string': Cause: The site information was not present in all the disks of the disk group.; Action: Specify sites for the disks using the 'asmcmd rename' command or using SQLPLUS and retry the operation.
ORA-59716: dropping all disks of the quorum site is not allowed: Cause: Dropping of the specified disks resulted in the loss of the quorum site. If only a subset of disks in the quorum site are specfied, then check the state of other disks in the V$ASM_DISK view.; Action: Modify the command to retain at least one disk in the quroum site and retry the operation.
ORA-59717: rebalance could not complete due to an unavailable site in disk group 'string': Cause: At least one of the sites had each disk in either dropping or forcing state.; Action: Undrop the dropping disks or add disks to the site.
ORA-59718: One or more disks are identified with a foreign site GUID 'string'.: Cause: The indicated site GUID was not associated with any of the configured sites.; Action: Execute the command 'crsctl query cluster site -all' to list the existing sites. Associate the indicated site GUID with a site using 'crsctl modify cluster site site -addguid guid' and retry the operation.
ORA-59719: disk group 'string' mounted but contains foreign site GUIDs: Cause: An attempt was made to mount a disk group with foreign site GUIDs.; Action: This is a warning. Examine the accompanying error messages for details.
ORA-59720: data sites in disk group string have a different number of fail groups.: Cause: An attempt was made to create a disk group with a different number of fail groups at each data site.; Action: Ensure that the data sites have an equal number of fail groups and try again.
ORA-59800: active use of disk 'string' precludes its label clear: Cause: A LABEL CLEAR command specified a disk that was in use.; Action: Dismount the disk group that is using this disk and retry the the LABEL CLEAR command. Query the V$ASM_CLIENT fixed view in an ASM instance or use ASMCMD LSOF to list active clients.
ORA-59801: ASM Filter Driver is not configured in the system.: Cause: An ASM Filter Driver command was run without either an ASM Filter Driver library present or kernel driver loaded.; Action: Execute the command ASMCMD AFD_STATE to find the status of an ASM Filter Driver.