Oracle 12c R2 Error Codes and Solution Suggestions from ORA-15200 to ORA-15300
- 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.
Cause: A disk specified in a CREATE DISKGROUP or ALTER DISKGROUP … ADD DISK command appeared to contain a file from an existing database or a foreign volume. By default, as a safeguard against damaging an existing database or foreign volume, ASM does not allow a disk group to be created using this disk.
Action: Check that the ASM disk specification is correct. Otherwise, when storage from a defunct database or unmounted foreign volume is reused as part of an ASM disk group, specify the FORCE option to the ASM SQL command. See the alert log for more information.
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.
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.
Cause: The COMPATIBLE parameter for the RDBMS instance is less than the value of the compatible.rdbms attribute for the disk group.
Action: Update the COMPATIBLE parameter for RDBMS instance to a version greater than or equal to compatible.rdbms version. The compatible attributes for diskgroups cannot be lowered.
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.
Cause: A command specified the same diskgroup twice.
Action: Specify each diskgroup only once.
Cause: The PERMISSION clause contained the USER, GROUP, or OTHER keyword more than once.
Action: Specify each keyword, at most, once.
Cause: The OWNERSHIP clause contained either the OWNER or the GROUP keyword more than once.
Action: Specify each keyword, at most, once.
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.
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.
Cause: The command did not specify a valid attribute name or a valid attribute value.
Action: Specify a valid attribute name and value pair.
Cause: The command did not specify a valid user name.
Action: Specify a valid user name.
Cause: The command did not specify a valid user group name.
Action: Specify a valid user group name.
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.
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.
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.
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.
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.
Cause: An attempt was made to rename a disk that is offline.
Action: Check the ASM disk name as specified in the command.
Cause: An attempt was made to ADD and DROP the specified ASM disk in the same statement.
Action: Revise the statement to specify distinct ASM disks in the ADD disk and DROP disk clauses.
Cause: An attempt was made to label a disk that is already provisioned for ASM.
Action: Check the ASM disk name as specified in the command.
Cause: A LABEL SET command specified a label name that was already used by another ASM disk.
Action: Select a different name for the label.
Cause: A LABEL CLEAR command specified a label name that was not used by ASM.
Action: Select a different name for the label.
Cause: An error occurred while setting/clearing the ASM label.
Action: Look at the underlying error(s) on the error stack. Check other messages in the trace files for more information.
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.
Cause: Disk group compatibility could not be advanced because connected clients were at a lower compatibility than the target value.
Action: Ensure that all connected clients are at the target compatibility level or higher.
Cause: Disk group compatibilty could not be advanced because some disks are offline.
Action: Retry the command after offline disks are dropped.
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.
Cause: An attempt was made to advance RDBMS compatibility beyond the disk group’s ASM compatibility.
Action: Advance ASM compatibility before advancing RDBMS compatibility.
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.
Cause: The specified diskgroup was mounted in restricted mode prohibiting client access.
Action: Dismount the diskgroup and remount it in appropriate mode.
Cause: An invalid attribute was specified with the CREATE DISKGROUP command.
Action: Check the valid attributes for CREATE DISKGROUP command and specify a valid one.
Cause: The specified value was not valid for the attribute.
Action: Check the attribute name and value.
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.
Cause: The attribute name was not valid or was not recognized.
Action: Check the attribute name.
Cause: The attribute value is read-only and cannot be changed.
Action: None. The attribute value cannot be changed.
Cause: An error occurred while setting the attribute.
Action: Look at the underlying error(s) on the error stack.
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.
Cause: The compatibility setting was invalid. The compatibility setting can only be advanced.
Action: Check the version number.
Cause: An attempt was made to bring a disk online that was either already online or was being brought online.
Action: Change the ONLINE statement to exclude the disk.
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.
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.
Cause: The ASM attributes feature was not enabled.
Action: Advance disk group ASM compatibility to version 11.1.0 or newer.
Cause: The specified attribute could not be accessed.
Action: Check the attribute name and examine underlying error(s) on the error stack.
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.
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.
Cause: The specified user name was not a valid operating system user.
Action: Specify a valid operating system user.
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.
Cause: The specified user group name already existed in the disk group.
Action: Specify a different user group name.
Cause: The specified user group name did not exist in the disk group.
Action: Specify a valid user group name.
Cause: The specified user was already a member of the specified user group.
Action: Specify either an alternate user or an alternate user group.
Cause: The maximum number of members per user group was exceeded.
Action: Delete existing members of the user group to create space.
Cause: The specified user group entry number was beyond the acceptable range.
Action: Specify a valid value for the user group entry number.
Cause: The specified user was not a member of the specified user group.
Action: Specify either an alternate user or an alternate user 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.
Cause: The specified UID already existed in the disk group.
Action: Specify a different UID.
Cause: The specified UID did not exist in the disk group.
Action: Specify a user with a valid UID.
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.
Cause: An operating system error occurred.
Action: Correct the operating system error and retry the operation.
Cause: The operating system user identification number exceeded the maximum value.
Action: Change the user identification number to a value within the accepted range.
Cause: This user identification number is used internally by ASM.
Action: Please choose a different user identification number.
Cause: File was already in existence.
Action: This is an internal error. Contact Oracle Support Services.
Cause: The operating system group identification number exceeded the maximum value.
Action: Change the group identification number to a value within the accepted range.
Cause: The specified disk was not a quorum disk.
Action: Retry the operation without the quorum attribute for the disk.
Cause: The specified failgroup was a quorum failgroup.
Action: Retry the operation with the quorum attribute for the failgroup.
Cause: The specified failgroup was not a quorum failgroup.
Action: Retry the operation without the quorum attribute for the failgroup.
Cause: The required number of voting files could not be created. See accompanying messages for possible causes.
Action: See accompanying messages for possible actions.
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).
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.
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.
Cause: The specified disk was a quorum disk.
Action: Retry the operation with the quorum attribute for the 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.
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.
Cause: An attempt was made to drop a user that still owns existing files.
Action: Specify the CASCADE option to drop the user and all of the owned files.
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.
Cause: This is an internal error.
Action: Check the accompanying error messages. Contact Oracle Support Services.
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.
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.
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.
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.
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.
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.
Cause: An ALTER DISKGROUP ADD DISK or RESIZE DISK command specified a disk with a size greater than the specified instance could use.
Action: Check the storage subsystem configuration on the specified node.
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.
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.
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.
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.
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.
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.
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.
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.
Cause: The file type was incompatible with the operation.
Action: Use another file of the correct type.