Oracle 11g Error Codes and Solution Suggestions from ORA-15200 to ORA-15400
- ORA-15200: initialization parameter string (string) is not a power of two
- Cause: The value specified for this initialization parameter was not a power of two.
- Action: Correct the initialization parameter value and restart the instance.
- ORA-15201: disk string contains a valid RDBMS file
- Cause: A disk specified in a CREATE DISKGROUP or ALTER DISKGROUP … ADD DISK command appeared to contain a file from an existing database. By default, ASM will not allow a diskgroup to be created using this disk, as a safeguard against damaging an existing database.
- Action: Check that the ASM disk specification is correct. Otherwise, when storage from a defunct database is reused as part of an ASM diskgroup, specify the FORCE option to the ASM SQL command.
- ORA-15202: cannot create additional ASM internal change segment
- Cause: The mount of a diskgroup by an additional instance in a RAC cluster required more space for internal use by ASM than was available in the diskgroup.
- Action: Delete unused files from the diskgroup or add additional disks to the diskgroup and retry the operation.
- ORA-15203: diskgroup string contains disks from an incompatible version of ASM
- Cause: Diskgroup was created by an ASM instance with a higher compatibility setting.
- Action: Use an ASM instance with the appropriate software version to mount the diskgroup.
- ORA-15204: database version string is incompatible with diskgroup string
- Cause: The database compatibility of the diskgroup was advanced to a later version.
- Action: Upgrade the database instance to appropriate version of ORACLE.
- ORA-15205: requested mirror side unavailable
- Cause: The requested mirror side of a block is either unallocated or allocated on a disk that has been dropped from the diskgroup.
- Action: Resubmit the request or try another mirror side.
- ORA-15206: duplicate diskgroup string specified
- Cause: A command specified the same diskgroup twice.
- Action: Specify each diskgroup only once.
- ORA-15210: conflicting or duplicate PERMISSION options
- Cause: The PERMISSION clause contained the USER, GROUP, or OTHER keyword more than once.
- Action: Specify each keyword, at most, once.
- ORA-15211: conflicting or duplicate OWNERSHIP options
- Cause: The OWNERSHIP clause contained either the OWNER or the GROUP keyword more than once.
- Action: Specify each keyword, at most, once.
- ORA-15212: missing or invalid OWNER or GROUP name
- Cause: The command did not specify a valid name for either the OWNER or the GROUP keyword.
- Action: Specify a valid name for either the OWNER or the GROUP keyword.
- ORA-15213: command operates on only one attribute
- Cause: More than one disk group attribute was specified in the ALTER DISKGROUP statement.
- Action: Specify only one disk group attribute per ALTER DISKGROUP statement.
- ORA-15214: missing or invalid attribute specification
- Cause: The command did not specify a valid attribute name or a valid attribute value.
- Action: Specify a valid attribute name and value pair.
- ORA-15215: missing or invalid user name
- Cause: The command did not specify a valid user name.
- Action: Specify a valid user name.
- ORA-15216: missing or invalid user group name
- Cause: The command did not specify a valid user group name.
- Action: Specify a valid user group name.
- ORA-15217: missing or invalid timeout value after DROP AFTER
- Cause: The command did not specify a valid timeout value after the DROP AFTER clause.
- Action: Specify a valid timeout value after the DROP AFTER clause.
- ORA-15218: timeout value exceeded range
- Cause: The OFFLINE timeout value exceeded the range of 0-136 years, inclusive. 136 years are 49674 days, 1192176 hours, and 71530560 minutes.
- Action: Specify a timeout value within the range of 0-136 years, inclusive.
- ORA-15219: conflicting or duplicate disk region options
- Cause: The command contained one or more of the following:
- – both the HOT and the COLD keywords
- – both the MIRRORHOT and the MIRRORCOLD keywords
- – the HOT keyword more than once
- – the COLD keyword more than once
- – the MIRRORHOT keyword more than once
- – the MIRRORCOLD keyword more than once
- Action: Specify either the HOT or the COLD keyword and either the MIRRORHOT or the MIRRORCOLD keyword, at most, once.
- ORA-15220: invalid file attribute specification
- Cause: The keyword UNPROTECTED, MIRROR, HIGH, FINE, or COARSE was specified in a MODIFY FILE clause. These file attributes are immutable once a file is created.
- Action: Specify a disk region keyword; for example, HOT, COLD, MIRRORHOT, or MIRRORCOLD.
- ORA-15221: ASM operation requires compatible.asm of string or higher
- Cause: The ASM operation specified requires a higher disk group attribute value for compatible.asm.
- Action: Set the disk group attribute compatible.asm to or above the requested version.
- ORA-15230: diskgroup ‘string‘ does not require the FORCE option
- Cause: An attempt was made to MOUNT or DROP a disk group with the FORCE option.
- Action: MOUNT and DROP diskgroup with the FORCE option are only permitted if the diskgroup cannot be mounted normally.
- ORA-15231: advancing diskgroup compatibility would exclude connected clients
- Cause: Disk group compatibility could not be advanced because connected clients were at a lower compatibility than the target value.
- Action: Make sure all connected clients are at target compatibility level or higher.
- ORA-15232: cannot advance diskgroup compatibility due to offline disks
- Cause: Disk group compatibilty could not be advanced because some disks are offline.
- Action: Retry the command after offline disks are dropped.
- ORA-15233: cannot advance diskgroup compatibility due to [string]
- Cause: Disk group compatibilty could not be advanced because of errors.
- Action: Check the alert log for more information on the reason for the failure.
- ORA-15234: target RDBMS compatibility (string) exceeds ASM compatibility (string)
- Cause: An attempt was made to advance RDBMS compatibility beyond the disk group’s ASM compatibility.
- Action: Advance ASM compatibility before advancing RDBMS compatibility.
- ORA-15235: diskgroup string mount mode conflicts with existing mount
- Cause: The mode specified in the diskgroup mount command conflicted with the mode in which it was mounted on some other instance.
- Action: Specify a compatible mode in the diskgroup mount command.
- ORA-15236: diskgroup string mounted in restricted mode
- Cause: The specified diskgroup was mounted in restricted mode prohibiting client access.
- Action: Dismount the diskgroup and remount it in appropriate mode.
- ORA-15237: attribute string cannot be set in CREATE DISKGROUP
- Cause: The specified attribute may not be set with the CREATE DISKGROUP command.
- Action: Check the attribute name or use ALTER DISKGROUP SET ATTRIBUTE.
- ORA-15238: string is not a valid value for attribute string
- Cause: The specified value was not valid for the attribute.
- Action: Check the attribute name and value.
- ORA-15239: allocation unit size higher than string requires RDBMS compatibility string
- Cause: The allocation unit size requested exceeded the limit imposed by the RDBMS compatibility setting.
- Action: Use a smaller allocation unit size or specify a higher RDBMS compatibility setting.
- ORA-15240: attribute name string is invalid
- Cause: The attribute name was not valid or was not recognized.
- Action: Check the attribute name.
- ORA-15241: attribute string is read only
- Cause: The attribute value is read-only and cannot be changed.
- Action: None. The attribute value cannot be changed.
- ORA-15242: could not set attribute string
- Cause: An error occurred while setting the attribute.
- Action: Look at the underlying error(s) on the error stack.
- ORA-15243: string is not a valid version number
- Cause: The given version number was invalid, or not valid in this context.
- Action: Verify that the version number is valid and is appropriate for this command. Check for additional errors reported.
- ORA-15244: new compatibility setting less than current [string]
- Cause: The compatibility setting was invalid. The compatibility setting can only be advanced.
- Action: Check the version number.
- ORA-15245: ASM disk string is already being brought online
- Cause: An attempt was made to bring online a disk that is already being brought online.
- Action: Change the ONLINE statement to exclude the disk.
- ORA-15246: cannot bring ASM disk string both online and then offline in the same statement
- Cause: An attempt was made to bring the specified disk both online and offline in the same statement.
- Action: Revise the statement to either bring the disk online or take the disk offline.
- ORA-15247: cannot specify both WAIT and NOWAIT options in the same statement
- Cause: An attempt was made to specify both WAIT and NOWAIT options in the same statement.
- Action: Revise the statement and include at most one option.
- ORA-15248: ASM attributes feature not enabled
- Cause: The ASM attributes feature was not enabled.
- Action: Advance disk group ASM compatibility to version 11.1.0 or newer.
- ORA-15249: could not locate ASM attribute string
- Cause: The specified attribute could not be accessed.
- Action: Check the attribute name and examine underlying error(s) on the error stack.
- ORA-15250: insufficient diskgroup space for rebalance completion
- Cause: The command attempted to reduce the available diskgroup space below the current space used.
- Action: Consult V$ASM_DISK to determine the space requirements for the diskgroup contents, and repeat the command after making the required storage available.
- ORA-15251: only restricted mount is allowed in the ASM instance
- Cause: The ASM instance was started in restricted mode, and an attempt was made to mount a diskgroup in non-restricted mode.
- Action: Start the ASM instance in non-restricted mode and mount the diskgroup again, or mount the diskgroup in restricted mode.
- ORA-15252: user name ‘string‘ does not exist in OS user dictionary
- Cause: The specified user name was not a valid operating system user.
- Action: Specify a valid operating system user.
- ORA-15253: user group name ‘string‘ exceeds limit of string characters
- Cause: The length of the specified user group name exceeded the maximum limit.
- Action: Reduce the length of the user group name to a value within the limit.
- ORA-15254: user group ‘string‘ already exists in disk group
- Cause: The specified user group name already existed in the disk group.
- Action: Specify a different user group name.
- ORA-15255: user group ‘string‘ does not exist in disk group ‘string‘
- Cause: The specified user group name did not exist in the disk group.
- Action: Specify a valid user group name.
- ORA-15256: user ‘string‘ is already a member of user group ‘string‘
- Cause: The specified user was already a member of the specified user group.
- Action: Specify either an alternate user or an alternate user group.
- ORA-15257: exceeded string number of members per user group
- Cause: The maximum number of members per user group was exceeded.
- Action: Delete existing members of the user group to create space.
- ORA-15258: user group entry number must be between string and string, inclusive
- Cause: The specified user group entry number was beyond the acceptable range.
- Action: Specify a valid value for the user group entry number.
- ORA-15259: user ‘string‘ is not a member of user group ‘string‘
- Cause: The specified user was not a member of the specified user group.
- Action: Specify either an alternate user or an alternate user group.
- ORA-15260: permission denied on ASM disk group
- Cause: An attempt was made to perform an operation on an ASM disk group without the appropriate privileges.
- Action: Ask the ASM administrator to perform the operation or grant the required privileges.
- ORA-15261: user ‘string‘ already exists in disk group ‘string‘
- Cause: The specified UID already existed in the disk group.
- Action: Specify a different UID.
- ORA-15262: user ‘string‘ does not exist in disk group ‘string‘
- Cause: The specified UID did not exist in the disk group.
- Action: Specify a user with a valid UID.
- ORA-15263: user name ‘string‘ exceeds limit of string characters
- Cause: The length of the specified user name exceeded the maximum limit.
- Action: Reduce the length of the user name to a value within the limit.
- ORA-15264: Operating system function returned error string
- Cause: An operating system error occurred.
- Action: Correct the operating system error and retry the operation.
- ORA-15265: user identification number not in range of [string,string]
- Cause: The operating system user identification number exceeded the maximum value.
- Action: Change the user identification number to a value within the accepted range.
- ORA-15266: user identification number ‘string‘ is not allowed
- Cause: This user identification number is used internally by ASM.
- Action: Please choose a different user identification number.
- ORA-15268: internal Oracle file string already exists.
- Cause: File was already in existence.
- Action: This is an internal error. Contact Oracle Support Services.
- ORA-15269: group identification number not in range of [string,string]
- Cause: The operating system group identification number exceeded the maximum value.
- Action: Change the group identification number to a value within the accepted range.
- ORA-15270: disk string is not a quorum disk
- Cause: The specified disk was not a quorum disk.
- Action: Retry the operation without the quorum attribute for the disk.
- ORA-15271: failgroup string is a quorum failgroup
- Cause: The specified failgroup was a quorum failgroup.
- Action: Retry the operation with the quorum attribute for the failgroup.
- ORA-15272: failgroup string is not a quorum failgroup
- Cause: The specified failgroup was not a quorum failgroup.
- Action: Retry the operation without the quorum attribute for the failgroup.
- ORA-15273: Could not create the required number of voting files.
- Cause: The required number of voting files could not be created. See accompanying messages for possible causes.
- Action: See accompanying messages for possible actions.
- ORA-15274: Not enough failgroups (string) to create voting files
- Cause: The number of failgroups required for this redundancy were not present in the diskgroup to create voting files.
- Action: Retry the operation after creating new failgroup(s).
- ORA-15275: Not enough contiguous space (string AUs) in disk string to allocate a voting file
- Cause: The specified disk did not have enough space to allocate a voting file on it.
- Action: Ensure that there is at least 1 disk with the required space in atleast the required number of failgroups for the diskgroup.
- ORA-15276: ASM diskgroup string has cluster voting files
- Cause: An attempt was made to drop a diskgroup that contained cluster voting files.
- Action: Move the cluster voting files out of the diskgroup and retry the operation.
- ORA-15277: disk string is a quorum disk
- Cause: The specified disk was a quorum disk.
- Action: Retry the operation with the quorum attribute for the disk.
- ORA-15278: external redundancy diskgroup requires at least one regular disk
- Cause: An attempt was made to create an external redundancy diskgroup with only quorum disks.
- Action: Specify atleast one regular disk to create an external redundancy diskgroup.
- ORA-15279: user ‘string‘ is currently being deleted
- Cause: The specified user was in the process of being deleted and could not be used.
- Action: Either abandon this operation or specify a different user.
- ORA-15280: user ‘string‘ owns existing files
- Cause: An attempt was made to drop a user that still owns existing files.
- Action: Specify the INCLUDING CONTENTS option to drop the user and all of the owned files.
- ORA-15281: not all specified disks were brought ONLINE
- Cause: Some of the disks specified either experienced I/O errors while being brought ONLINE, or were simultaneously brought OFFLINE or dropped in another session, or were full.
- Action: Query V$ASM_DISK or use ASMCMD LSDSK to determine which disks were not brought ONLINE. Inspect any additional error messages and the alert log to determine the exact cause. If some of the disks failed, either fix the cause of the failures or drop the disks. If some of the disks are full, either free space in the disk group or add new disks to the diskgroup.
- ORA-15282: ASM disk “string” is not visible cluster-wide
- Cause: An ALTER DISKGROUP ONLINE command specified a disk that could not be discovered by one or more nodes in a RAC cluster configuration.
- Action: Check operating system permissions for the device and the storage sub-system configuration on each node in the RAC cluster that cannot identify the disk.
- ORA-15283: ASM operation requires compatible.rdbms of string or higher
- Cause: The ASM operation specified requires a higher disk group attribute value for compatible.rdbms.
- Action: Set the disk group attribute compatible.rdbms to or above the requested version.
- ORA-15284: ASM terminated ALTER DISKGROUP ONLINE
- Cause: None of the disks specified by ALTER DISKGROUP ONLINE could be brought ONLINE.
- Action: Inspect additional error messages and the alert log to determine why the specified disks cannot be brought ONLINE.
- ORA-15285: disk ‘string‘ violates disk group attribute string
- Cause: Including the specifed disk would violate a restriction imposed by the specified disk group attribute.
- Action: Retry the operation while omitting the offending disk or change the attribute.
- ORA-15286: could not set disk group attribute string due to offline disks
- Cause: The specified disk group attribute could not be set because the disk group includes offline disks.
- Action: Retry the operation after the offline disks in this disk group are dropped or brought online.
- ORA-15287: could not set disk group attribute string due to incompatible disks
- Cause: The specified disk group attribute could not be set because the disk group includes disks that conflict with the new value.
- Action: Retry the operation after dropping the conflicting disks in this disk group.
- ORA-15288: disk(s) require disk group attribute string clause
- Cause: Some of the disks specified by the command also require the specified disk group attribute to be stated.
- Action: Retry the command including an ATTRIBUTE clause for the required disk group attribute. Alternatively, omit the disks that require setting the disk group attribue. See the alert log for additional information on the disks that require setting the disk group attribute.
- ORA-15289: ASM disk string cannot be resized beyond string M
- Cause: A resize disk command specified a size beyond the maximum allowed for this disk.
- Action: Check alert logs from all ASM instances to identify the reason for the size limitation. If there are any 10g database instances using this disk group, shut down those instances and retry the resize operation.
- ORA-15290: operation not permitted on offline disk string
- Cause: An attempt was made to specify an operation that is only permitted on disks that are online. The specified disk was not online.
- Action: Online the disk or wait for online to complete before retrying the operation.
- ORA-15291: ASM could not add disk “string” to disk group “string“
- Cause: An attempt was made to add a disk to a disk group while the distribution of disks in failure groups was too uneven.
- Action: Add or drop disks to or from failure groups to balance their distribution in all failure groups and retry the operation.
- ORA-15292: Disk name string is being used by another disk
- Cause: The specified disk name could not be reused because an 11.1.0.6.0 or earlier database instance had it cached in memory.
- Action: Do one of the following
- – Specify a different name for the disk.
- – Wait for the rebalance to complete successfully.
- – Identify the database instance with the problem and shut it down before retrying the command.
- ORA-15293: operation disallowed by ASM_POWER_LIMIT
- Cause: This operation required data movement in order to complete successfully. However, ASM_POWER_LIMIT was set to zero, thereby preventing this operation.
- Action: Repeat the operation after setting ASM_POWER_LIMIT to a non-zero value.
- ORA-15294: SYSASM privilege not allowed on database instance
- Cause: The SYSASM privilege was not allowed on this database instance; it is allowed only on an ASM instance.
- Action: Use either the SYSDBA or the SYSOPER privilege.
- ORA-15295: ASM instance software version string less than client version string
- Cause: The ASM instance software version was less than the client version.
- Action: Upgrade the ASM instance software. Check the alert log for more information on the reason for the failure.
- ORA-15298: possible lost disk write detected during crash recovery
- Cause: ASM crash recovery read a block who’s version was older than expected.
- Action: None. End users will not see this error. ASM automatically traps this error and attempts a fallback recovery.
- ORA-15299: FINE striping not allowed for the Staleness Registry
- Cause: An SQL command attempted to set the striping attribute of the ASM_STALE template to FINE striping.
- Action: Do not modify the striping attribute of the ASM_STALE template.
- ORA-15300: File string is incompatible with this operation
- Cause: The file type was incompatible with the operation.
- Action: Use another file of the correct type.
- ORA-15301: cannot change string of the open file ‘string‘
- Cause: A SET OWNERSHIP or SET PERMISSION command was attempted on an open file.
- Action: Close the file and retry the SQL command.
- ORA-15302: active use of files owned by user ‘string‘ precludes its drop
- Cause: A DROP USER command specified a user owning files that were in use.
- Action: Close all files owned by this user.
- ORA-15303: Voting files could not be created in diskgroup string due to small Allocation Unit size
- Cause: An attempt was made to create voting files in a diskgroup with a small Allocation Unit size.
- Action: Create voting files in a different diskgroup whose Allocation Unit size is at least 1 mega byte.
- ORA-15304: operation requires ACCESS_CONTROL.ENABLED attribute to be TRUE
- Cause: An attempt was made to run an operation that required the ACCESS_CONTROL.ENABLED attribute to be set to TRUE, but its existing state was FALSE.
- Action: Set the ACCESS_CONTROL.ENABLED attribute to TRUE and retry the operation.
- ORA-15305: cannot operate on ASM internal files
- Cause: An attempt was made to operate on Automatic Storage Management (ASM) metadata used to manage the diskgroup.
- Action: Check the specified ASM file name.
- ORA-15306: ASM password file update failed on at least one node
- Cause: A CREATE USER, ALTER USER, DROP USER, GRANT, or REVOKE command failed on at least one node of the Automatic Storage Management (ASM) cluster.
- Action: Check the ASM alert logs for more information.
- ORA-15307: disk string not discoverable by CSS; diskgroup string has CSS voting files
- Cause: An attempt was made to add a disk which cannot be discovered by Cluster Synchronization Services (CSS). CSS has voting files in the disk group and will not be able to use the new disk if CSS cannot discover the disks.
- Action: Update the Automatic Storage Management (ASM) disk string in the Grid Plug and Play (GPnP) profile to include the specified disk and retry the operation. Alternatively, migrate the CSS voting files out of the diskgroup and retry the operation
- ORA-15308: could not access ASM SPFILE in RDBMS instance
- Cause: A relational database management system (RDBMS) instance attempted to access an Automatic Storage Management (ASM) SPFILE.
- Action: Connect to an ASM instance and reissue the command. Alternatively, specify an RDBMS SPFILE.
- ORA-15309: could not access database SPFILE in ASM instance
- Cause: An Automatic Storage Management (ASM) instance attempted to access a relational database management system (RDBMS) SPFILE.
- Action: Connect to an RDBMS instance and reissue the command. Alternatively, specify an ASM SPFILE.
- ORA-15310: process terminated due to signal
- Cause: A process was terminated as a result of a signal in the I/O path.
- Action: Reconnect to the database or the ASM instance. If the process termination resulted in instance termination, restart the instance.
- ORA-15311: process terminated due to fenced I/O
- Cause: A process was terminated because it was fenced from doing any more I/Os.
- Action: Reconnect to the database or the ASM instance. If the process termination resulted in instance termination, restart the instance.
- ORA-15312: invalid file type
- Cause: Automatic Storage Management (ASM) could not determine the type of file.
- Action: The file specified is not supported with Automatic Storage Management (ASM). Specify a supported file type for the operation.
- ORA-15315: Write errors in disk group string could lead to inconsistent ASM metadata.
- Cause: One or more failures occurred while writing ASM metadata to disk.
- Action: Repair the hardware problem and remount the disk group. Check the accompanying errors and alert log for the disks which reported the error.
- ORA-15316: Previous client instance string has not fully exited.
- Cause: One or more processes from a prior instantiation of this client were not fenced.
- Action: Make sure all processes belonging to the client instance exited. Check the client alert log and the trace file of the process that terminated the instance.
- ORA-15318: disks in disk group string cannot be resized
- Cause: Execution of ASM Storage Reclamation Utility script was incomplete on the specified disk group.
- Action: Execute ASM Storage Reclamation utility on the disk group to complete the operation.
- ORA-15321: cannot set attribute with connected clients
- Cause: The disk group attribute could not be set because there were connected clients.
- Action: Shut down connected clients and retry the command. Query the V$ASM_CLIENT fixed view in an ASM instance or use ASMCMD LSCT to list active clients.
- ORA-15323: ASM password update has failed on local node
- Cause: A CREATE USER, ALTER USER, DROP USER, GRANT, or REVOKE command failed on the local node of the Automatic Storage Management (ASM) cluster.
- Action: Check the ASM alert logs for more information.
- ORA-15324: requested operation is not allowed on the password file string
- Cause: An attempt was made to run an operation that is not supported on password files.
- Action: Specify a new file name or a file with the correct file type and retry the operation.
- ORA-15325: file string is not a valid password file
- Cause: An attempt was made to open a file that had a type different from the password file.
- Action: Specify correct password file name and retry the operation.
- ORA-15326: specified input string is a not an ASM file
- Cause: The attributes could not be obtained as the specified input is either a disk group or a directory.
- Action: Specify a valid Automatic Storage Management (ASM) file name.
- ORA-15327: remote ASM is not enabled
- Cause: An operation was requested that requires remote ASM to be enabled.
- Action: Enable remote ASM.
- ORA-15328: user identification string ‘string‘ exceeds limit of string characters
- Cause: The user identification string provided for this operation exceeded the maximum number of characters allowed.
- Action: Provide a user identification string of shorter length.
- ORA-15329: cluster identification string ‘string‘ exceeds limit of string characters
- Cause: The cluster identification string provided for this operation exceeded the maximum number of characters allowed.
- Action: Provide a cluster identification string of shorter length.
- ORA-15330: ASM user name format requires COMPATIBLE.ASM of string or higher
- Cause: The ASM user name format specified requires a higher disk group attribute value for COMPATIBLE.ASM.
- Action: Set the disk group attribute COMPATIBLE.ASM to or above the requested version.
- ORA-15331: ASM proxy instance ORACLE_SID string does not start with string
- Cause: The ASM proxy instance was started with an invalid ORACLE_SID prefix.
- Action: Start the ASM proxy instance with an ORACLE_SID that begins with the correct prefix.
- ORA-15332: ASM proxy instance cannot connect to an ASM server
- Cause: The ASM proxy instance could not find an ASM server to connect to during startup.
- Action: Verify that an ASM server instance is running and accessible in the cluster and restart the proxy instance.
- ORA-15333: disk is not visible on client instance
- Cause: An ALTER DISKGROUP ADD DISK statement specified a disk that could not be discovered by all ASM client instances.
- Action: Check the ASM alert logs for more information. Check operating system permissions for the device and the storage subsystem configuration.
- ORA-15334: VUBG process terminated with error
- Cause: The volume background process terminated with error.
- Action: Warm start instance.
- ORA-15335: ASM metadata corruption detected in disk group ‘string‘
- Cause: A corruption was detected reading a block. It may be recoverable.
- Action: The corruption could be the result of a storage problem, a configuration issue, or a software bug. Check the alert log for the result of the recovery attempt. If unsuccessful, contact Oracle Support Services with the incident information.
- ORA-15400: not running on supported ASM appliance
- Cause: An attempt was made to initialize the server code as an appliance when it was not running a supported appliance configuration.
- Action: Check the appliance configuration and retry the operation.