Oracle 12c R2 Error Codes and Solution Suggestions from ORA-15300 to ORA-15400
- 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.
Cause: A SET OWNERSHIP or SET PERMISSION command was attempted on an open file.
Action: Close the file and retry the SQL command.
Cause: A DROP USER command specified a user owning files that were in use.
Action: Close all files owned by this user.
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.
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.
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.
Cause: A CREATE USER, ALTER USER, DROP USER, GRANT, or REVOKE command failed on the specified node of the Automatic Storage Management (ASM) cluster.
Action: Check the ASM alert logs for more information.
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
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.
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.
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.
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.
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.
Cause: An Oracle ASM disk resize command specified a size that was less than the size required to support the voting file present on the disk.
Action: Increase the size specified for the disk.
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.
Cause: One or more processes from a prior instantiation of this client were not fenced.
Action: Ensure that all processes belonging to the client instance have exited. Check the client alert log and the trace file of the process that terminated the instance.
Cause: The specified user identification number did not belong to a valid operating system user.
Action: Specify a valid operating system user.
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.
Cause: A DROP USER command specified a user currently being assigned as the owner of one or more files with a SET OWNERSHIP command.
Action: Wait for the SET OWNERSHIP command to complete and then retry the DROP USER command
Cause: A SET OWNERSHIP command assigned this user as the owner of one or more files which were open at the time of assignment, and hence this user cannot be dropped due to possible inconsistencies in file ownerships.
Action: Restart all ASM client instances of the cluster in a rolling manner.
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 LSOF to list active clients.
Cause: An attempt was made to drop the owner of a user group from the group’s member list.
Action: Specify a user group member who is not the owner of the user group.
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.
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.
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.
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.
Cause: An operation was requested that requires remote ASM to be enabled.
Action: Enable remote ASM.
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.
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.
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.
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.
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.
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.
Cause: The volume background process terminated with error.
Action: Warm start instance.
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.
Cause: An ADD VOLUME command specified a STRIPE_COLUMNS equal to 1 and specified the STRIPE_WIDTH argument.
Action: If striping is required, set STRIPE_COLUMNS to greater than 1. If striping is not required, do not set STRIPE_WIDTH.
Cause: You did not specify a valid database name for this command.
Action: Specify a valid database name.
Cause: The client was not found as an orphaned client and hence is not a legitimate candidate to reconnect to Oracle ASM.
Action: Shut down and restart the remote client to be considered as a new client in the cluster.
Cause: Oracle ASM has already fenced this client.
Action: Shut down and restart the remote client to be considered as a new client in the cluster.
Cause: Creation of the member cluster failed.
Action: Check the alert logs and trace files of the Oracle ASM instance for more information on the reason for the failure, as well as checking the accompanying error messages.
Cause: Deletion of the member cluster failed.
Action: Check the alert logs and trace files of the Oracle ASM instance for more information on the reason for the failure, as well as checking the accompanying error messages.
Cause: An operation was requested that requires Oracle Flex ASM to be enabled.
Action: Enable Oracle Flex ASM.
Cause: The specified Oracle ASM client was not registered with this instance.
Action: Check the alert logs and trace files of the client for more information on the reason for the failure, as well as the accompanying error messages.
Cause: One or more ASM client instances were not connected to an ASM instance.
Action: Check that all of the ASM client instances are connected to an ASM instance and retry the operation.
Cause: The client process attempting to identify or create the ASM file terminated or was interrupted.
Action: Correct the cause of the process interruption and retry the operation.
- ORA-15347: logical block size string of ASM file ‘string‘ is too small for disk group sector size string
Cause: An attempt was made to create a file on ASM whose logical block size was less than the sector size for the disk group.
Action: Check if the system configuration has changed. Correct the error and retry the operation.
Cause: ASMLIB was found in more than one location.
Action: Check the configuration of ASMLIB and ensure that only one library is configured.
Cause: The operation failed because either Oracle Local Repository (OLR) was not available or AFD disk string attribute did not exist.
Action: Check that Oracle Clusterware is properly configured using ‘ocrcheck -local’ command.
Cause: The parameter passed in for SYS_ASMFD_PROPERTIES was invalid.
Action: Pass in the correct parameter. Refer to the product documentation for a list of allowed parameter values.
Cause: The sparse grid disk was out of space.
Action: Add more space to the disk group by adding more disks or add more space to existing disks by resizing them.
Cause: The client name passed in was invalid.
Action: Pass in a valid client name. The valid client name is of format instance name:dbunique name:cluster name or instance name:dbunique name
Cause: The disk type did not match the disk group sparse type.
Action: Ensure that the disk type matches the disk group sparse type.
Cause: The grid disk format command failed.
Action: Check the grid disk logs and take corrective actions.
Cause: An attempt was made to create fine-grained striping files on sparse disk groups. Fine-grained striping files cannot be created on sparse disk groups.
Action: Create the file on a regular disk group, or create a coarse-grained striping file on a sparse disk group.
- ORA-15358: query for materialized space to sparse grid disk “string” of disk group “string” has failed
Cause: The query for materialized space to the cell server has failed.
Action: Check the ASM and cell alert logs and take corrective actions.
Cause: An error occurred while scanning for ASM label.
Action: Look at the underlying errors on the error stack. Check other messages in the trace files for more information.
Cause: An error occurred while setting AFD filter status.
Action: Look at the underlying errors on the error stack. Check other messages in the trace files for more information.
Cause: Looking up of the member cluster failed.
Action: Execute the ‘asmcmd lscc’ command to list all of the configured member clusters. If the member cluster listed in the message is not present, it might have been forcibly deleted. Refer to the product documentation for more information. If the member cluster listed in the message was present, contact Oracle Support Services.
Cause: An invalid cluster name was supplied.
Action: Specify a cluster 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.
Cause: The command did not specify a valid version number.
Action: Correct the version number in the command. It should be of the form #.#.#.#.# or other forms with fewer numbers delimited by a period.
Cause: The specified member cluster version was not supported by the Storage Server.
Action: Upgrade or downgrade the storage server to a version that is compatible with member cluster and retry the operation. Install a member cluster using a supported version. Refer to product documentation for a complete list of supported releases.
Cause: The specified member cluster was already configured.
Action: Execute the ‘asmcmd lscc’ command to list all of the configured member clusters. Reexecute the command with a member cluster name that has not already been configured.
- ORA-15366: unable to delete configuration for member cluster ‘string‘ because the directory ‘string‘ was not empty
Cause: Deleting the member cluster configuration failed because some files were present.
Action: Deinstall the member cluster and rerun the command. If the command fails again, execute the ‘asmcmd rmcc <member_cluster_name> -f’ command to force deletion of the configuration for the member cluster.
Cause: The specified member cluster was not configured.
Action: Execute the ‘asmcmd lscc’ command to list all of the configured member clusters. Reexecute the command with a member cluster name that is configured.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: An Oracle Call Interface (OCI) call returned the OCI_INVALID_HANDLE return code and did not store the error on the stack.
Action: Contact Oracle Support Services.
Cause: An attempt was made to access a disk group number greater than 63 with a database version lower than 12.1.
Action: Upgrade the database to version 12.1 or higher and retry the operation.
Cause: An attempt was made to run a command that is not supported on a member cluster.
Action: Rerun the command on the storage server.
Cause: The software version of the client is not supported by current release of the ASM software.
Action: Upgrade the client to the later release that is compatible with Oracle ASM and retry the operation. Refer to product documentation for a complete list of supported releases.
- ORA-15373: SYSDG, SYSKM, SYSRAC, and SYSBACKUP administrative privileges cannot be granted on an ASM instance.
Cause: An attempt was made to grant or revoke SYSDG, SYSKM, SYSRAC, or SYSBACKUP administrative privileges to a user on an ASM instance.
Action: Do not attempt to grant SYSDG, SYSKM, SYSRAC, or SYSBACKUP administrative privileges on an ASM instance.
Cause: The client instance detected an invalid configuration.
Action: Install and configure Oracle Grid Infrastructure and retry the operation. Refer to product documentation for more information.
Cause: An attempt was made to create or modify a disk group with a physical sector size value smaller than its logical sector size value.
Action: Review the SQL statement and fix any discrepancies.
- ORA-15376: The existence of native disk ‘string‘ does not allow disk group string from changing sector sizes. Sector size of native disk is string.
Cause: An attemp was made to change the physical or logical sector size value. Changing the sector size value is not allowed when there are native disks (physical sector equal to logical sector size) in the disk group, because this could cause invalid I/O operations.
Action: Drop the native disks or replace them for disks that support sector size emulation.
- ORA-15377: Block size (string) for file ‘string‘ is incompatible with the selected sector size (string).
Cause: The operation could not be completed because the sector size was incompatible for the specified file.
Action: Re-create or migrate the file to a block size that is compatible with the desired sector size, and redo the operation.
Cause: This is an internal error.
Action: Check the accompanying error messages. Contact Oracle Support Services.
Cause: This is an internal error.
Action: Check the accompanying error messages. Contact Oracle Support Services.
Cause: The file group name specified was invalid.
Action: Specify a valid file group name.
Cause: The command did not specify a valid file group client string.
Action: Specify a valid file group client string with alphanumeric characters.
Cause: The file group name specified was invalid.
Action: Specify a valid file group name.
Cause: An invalid property was specified for the ASM file group.
Action: Check documentation for valid ASM file group properties. The valid ASM file group property is of format file type.property name or property name
Cause: An invalid file type was specified for the ASM file group property.
Action: Check documentation for valid ASM file types.
Cause: The specified file group did not exist within the disk group.
Action: Check the file group name and disk group name.
Cause: A file group with the same name already exists.
Action: Select another file group name, or drop the existing file group. While creating non-CDB, multitenant container database (CDB), or pluggable database (PDB), manually create a file group for this non-CDB, multitenant container database (CDB), or pluggable database (PDB).
Cause: An attempt was made to drop a file group that still contains existing files.
Action: Specify the CASCADE option to drop the file group and all of the associated files.
Cause: The specified file group property affects the file group itself or all files in the file group, it is not specific to a type of file.
Action: Remove the file type from the name of the property.
Cause: The command did not specify a valid file group property name or a valid file group property value.
Action: Specify a valid file group property name and value pair.
Cause: An invalid value was specified for the ASM file group property.
Action: Check documentation for acceptable values for this ASM file group property.
Cause: The specified file group was created by the system and must always exist for proper operation.
Action: Select another file group name.
Cause: The specified file group was created by the system and must hold the default values for proper operation.
Action: Select another file group name.
Cause: The specified file did not exist within the file group.
Action: Check the file number and the file group number.
Cause: A command specified the same file group property more than once for the same file type.
Action: Specify only one file group property for a file type.
Cause: An attempt was made to move a file to a file group with an incompatible redundancy specification, or to change the redundancy specification of a file group in a way that is incompatible with existing files in that file group.
Action: Specify a valid redundancy property for the file group. Only write-once files, such as the offline archive log and backup set, support parity protection. Other types of files must be configured with an unprotected, mirror or high redundancy. The file group redundancy can be changed from a parity protection scheme to unprotected, mirror, or high, and conversely, as long as the file group does not contain any files.
Cause: More than one file group property was specified in the ADD FILEGROUP or MODIFY FILEGROUP statement.
Action: Specify only one file group property per statement.
Cause: The file group redundancy could not be changed to UNPROTECTED because some disks were offline.
Action: Retry the command after the offline disks are dropped.
Cause: The specified file group property cannot be changed.
Action: Retry the command providing a non read-only file group property
Cause: The specified value for COMPATIBLE.RDBMS attribute exceeds the COMPATIBLE setting for RDBMS for one or more clients.
Action: Verify the RDBMS compatibility for each client of this disk group.
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.