LISTE CODE ERREURS ORACLE.

 

ORA-14601	ORA-14601: Illegal to specify SUBPARTITIONS or STORE-IN while specifying a subpartition template
Cause	Cannot specify these clauses while specifying a template
Action	Correct the subpartition template clause.

 

ORA-14602	ORA-14602: SUBPARTITION TEMPLATE is legal only for a composite partitioned table
Cause	SUBPARTITION TEMPLATE can be specified only for composite partitioned tables
Action	Do not use SUBPARTITION TEMPLATE on non-partitioned or non-composite partitioned tables.

 

ORA-14603	ORA-14603: [SUBPARTITIONS | SUBPARTITION TEMPLATE] subpartition_count syntax is valid only for range-hash tables
Cause	This syntax is valid only if subpartitioning dimension is hash
Action	none

 

ORA-14604	ORA-14604: During CREATE TABLE time it is illegal to specify SUBPARTITIONS or STORE IN once a SUBPARTITION TEMPLATE has been specified
Cause	Once a subpartition template has been specified during a CREATE TABLE it is illegal to specify SUBPARTITIONS or STORE IN anywhere else
Action	Remove either the SUBPARTITIONS | STORE IN or remove the SUBPARTITION TEMPLATE clause

 

ORA-14605	ORA-14605: Name missing for subpartition / lob segment in template
Cause	A subpartition / lob segment was not specified a name in the template descriptions
Action	All subpartitions / lob segments must have names specified in the template

 

ORA-14606	ORA-14606: Tablespace was specified for previous subpartitions in template but is not specified for string
Cause	Tablespaces may either be specified for all subpartitions or must not be specified for any subpartitions
Action	Either specify tablespaces for all or for none of the subpartitions

 

ORA-14607	ORA-14607: Tablespace was not specified for previous subpartitions in template but is specified for string
Cause	Tablespaces may either be specified for all subpartitions or must not be specified for any subpartitions
Action	Either specify tablespaces for all or for none of the subpartitions

 

ORA-14608	ORA-14608: Tablespace was specified for the previous lob segments of column string in template but is not specified for string
Cause	Tablespaces may either be specified for all lob segments of a column or must not be specified for any lob segments of this column
Action	Either specify tablespaces for all or for none of the lob segments

 

ORA-14609	ORA-14609: Tablespace was not specified for the previous lob segments of column string in template but is specified for string
Cause	Tablespaces may either be specified for all lob segments of a column or must not be specified for any lob segments of this column
Action	Either specify tablespaces for all or for none of the lob segments

 

ORA-14610	ORA-14610: Lob attributes not specified for lob column string for subpartition string
Cause	Lob attributes of a column must be specified for all subpartitions or must not be specified at all
Action	Ensure lob attributes of a column are specified for all subpartitions or not specified at all

 

ORA-14611	ORA-14611: Duplicate subpartition name string in template
Cause	A subpartition name cannot be duplicated within the template
Action	Rename one of the subpartitions.

 

ORA-14612	ORA-14612: Duplicate lob segment name string for lob column string in template
Cause	Two lob segments of the same column were given the same name in the template
Action	Rename one of the lob segments

 

ORA-14613	ORA-14613: Attempt to generate name from parent name string and template name string failed as the combine named would have been longer than allowed
Cause	Any name generated from a partition name and template name must be less than the maximum permissible name for an identifier
Action	Shorten either partition or template name.

 

ORA-14614	ORA-14614: List value "string" specified twice in subpartition "string"
Cause	A list value cannot be specified more that once
Action	Remove one of the specifications of the value

 

ORA-14615	ORA-14615: List value "string" specified twice in subpartitions "string", "string"
Cause	A list value cannot be specified more that once
Action	Remove one of the specifications of the value

 

ORA-14616	ORA-14616: table is not subpartitioned by List method
Cause	A subpartition maintenance operation such as ALTER TABLE MODIFY SUBPARTITION ADD|DROP VALUES or ALTER TABLE DROP|SPLIT|MERGE SUBPARTITION can only be performed on List subpartitioned objects
Action	Re-issue the command against a List subpartitoned object.

 

ORA-14617	ORA-14617: cannot add/drop values to DEFAULT subpartition
Cause	A ADD/DROP VALUES operation is being done on the default subpartition
Action	Ensure that ADD/DROP VALUES is not done on the DEFAULT subpartition

 

ORA-14618	ORA-14618: cannot drop the last value of subpartition
Cause	ALTER TABLE DROP VALUES tried to drop the last value of the subpartition
Action	Cannot execute the command, unless two or more values exist for subpartition

 

ORA-14619	ORA-14619: resulting List subpartition(s) must contain at least 1 value
Cause	After a SPLIT/DROP VALUE of a list subpartition, each resulting subpartition(as applicable) must contain at least 1 value
Action	Ensure that each of the resulting subpartitions contains atleast 1 value

 

ORA-14620	ORA-14620: DEFAULT subpartition already exists
Cause	A subpartition already exists with DEFAULT value
Action	Remove the DEFAULT value from the list specified

 

ORA-14621	ORA-14621: cannot add subpartition when DEFAULT subpartition exists
Cause	An ADD SUBPARTITION operation cannot be executed when a subpartition with DEFAULT values exists
Action	Issue a SPLIT of the DEFAULT subpartition instead

 

ORA-14622	ORA-14622: Value string already exists in subpartition string
Cause	One of the list values in the ADD SUBPARTITION or ADD VALUES statement already exists in another subpartition
Action	Remove the duplicate value from the statement and try again

 

ORA-14623	ORA-14623: Value string does not exist in subpartition string
Cause	One of the list values in the SPLIT PARTITION or DROP VALUES statement does not exist in the subpartition
Action	Remove the value from the statement and try again

 

ORA-14624	ORA-14624: DEFAULT subpartition must be last subpartition specified
Cause	A subpartition description follows the one describing the default subpartition
Action	Ensure that the DEFAULT subpartition is the last subpartition description

 

ORA-14625	ORA-14625: subpartition contains rows corresponding to values being dropped
Cause	table subpartition contains rows for the values being dropped.
Action	DELETE all rows for the values being dropped and reissue statement

 

ORA-14626	ORA-14626: values being added already exist in DEFAULT subpartition
Cause	An ADD VALUE operation cannot be executed because the values being added exist in the DEFAULT subpartition
Action	Issue a SPLIT of the DEFAULT subpartition and then MERGE the split subpartition into the subpartition to which values need to be added

 

ORA-14627	ORA-14627: Invalid operation was specified on a GLOBAL partitioned index
Cause	An invalid operation such as ALTER INDEX DROP|SPLIT SUBPARTITION was specified on the global index
Action	Ensure that subpartition level operations are not specified on a GLOBAL index, since these are only RANGE partitioned

 

ORA-14628	ORA-14628: specification of bounds is inconsistent with LIST method
Cause	An operation such as ALTER TABLE SPLIT|ADD SUBPARTITION specified bounds that were inconsistent with List subpartitioning method
Action	Specify VALUES/subpartition descriptions correctly for SPLIT/ADD of List subpartitions

 

ORA-14629	ORA-14629: cannot drop the only subpartition of a partition
Cause	A drop subpartition command is being executed when there is only one subpartition in the partition
Action	none

 

ORA-14630	ORA-14630: subpartition resides in offlined tablespace
Cause	User attempted an operation requiring that we access data in a subpartition which resides in a tablespace which was taken offline. Such operations include trying to drop a tablespace of a table which has indices defined on it or is referenced by a constraint.
Action	Bring tablespace online before attempting the operation.

 

ORA-14631	ORA-14631: the partition bounds do not match the subpartition bounds of the partition
Cause	When exchanging a partitioned table with a composite partition the bounds that describe the partitions of the table must match the bounds that describe the subpartitions of the composite partition.
Action	Ensure that the bounds describing partitions in the partitioned table is the same as the bounds of the subpartitions in the the composite partition.

 

ORA-14632	ORA-14632: cannot specify PARALLEL clause when adding a List subpartition
Cause	User issued ALTER TABLE ADD SUBPARTITION statement with PARALLEL clause for a List subpartition of a Range/List partitioned object which is illegal
Action	Remove the PARALLEL clause.

 

ORA-14633	ORA-14633: Index maintainence clause not allowed for ADD list subpartition to a Composite partitioned table
Cause	The clause INVALIDATE or UPDATE GLOBAL INDEXES is allowed only for ADD hash subpartition to a composite partitioned table.
Action	Remove clause and reissue operation

 

ORA-14634	ORA-14634: Subpartition descriptions cannot be specified during the SPLIT/MERGE of a partition of a Range-List partitioned table
Cause	During a split or a merge of a partition of a range list partitioned table you cannot specify any subpartitioning information for the resulting partition (s)
Action	Remove all subpartitioning information from the DDL.

 

ORA-14635	ORA-14635: only one resulting subpartition can be specified for MERGE SUBPARTITIONS
Cause	ALTER TABLE MERGE SUBPARTITIONS contained more than one resulting subpartition for the MERGE
Action	Ensure that the statement describes exactly one subpartition as the target that need to be MERGEd

 

ORA-14636	ORA-14636: only 2 resulting subpartition can be specified for SPLIT SUBPARTITION
Cause	ALTER TABLE SPLIT SUBPARTITION contained more than 2 resulting subpartition for the SPLIT
Action	Ensure that the statement describes exactly 2 subpartitions as the target of the SPLIT operation

 

ORA-14637	ORA-14637: cannot merge a subpartition with itself
Cause	The same subpartition name was specified twice for the merge operation
Action	Re-submit operation with 2 distinct subpartition names within the same composite partition

 

ORA-14638	ORA-14638: cannot MERGE subpartitions in different Range Composite partitions
Cause	Attempted to MERGE subpartitions in different Range Composite partitions
Action	Reissue the command after ensuring that the 2 subpartitions being merged lie in the same composite partition

 

ORA-14639	ORA-14639: SUBPARTITIONS clause can be specfied only for Hash, Composite Range Hash table/partition
Cause	Attempted to specify SUBPARTITIONS clause on table that is not partitioned by the Composite Range-Hash method
Action	Reissue the command after ensuring that the SUBPARTITIONS clause is not specified, to specify a template for a Composite Range List object use the SUBPARTITION TEMPLATE clause

 

ORA-14640	ORA-14640: add/coalesce index partition operation is valid only for hash partitioned global indexes
Cause	User attempted to add or coalesce an index partition of a global index not partitioned by hash method.
Action	Issue the statement on a global index partitioned by hash method. or if the index is partitioned by range method consider using split/drop instead of add/coalesce.

 

ORA-14641	ORA-14641: STORE-IN clause can be specified only for a Hash, Composite Range Hash table/partition
Cause	Specifying a STORE-IN clause during CREATE/ALTER of a Range, Composite Range List partitioned table which is not allowed"
Action	Re-issue the stament after removing the STORE-IN clause

 

ORA-14642	ORA-14642: Bitmap index mismatch for tables in ALTER TABLE EXCHANGE PARTITION
Cause	The two tables in the EXCHANGE have usable bitmap indexes, and the INCLUDING INDEXES option has been specified and the tables have different hakan factors.
Action	Perform the exchange with the EXCLUDING INDEXES option or alter the bitmap indexes to be unusable.

 

ORA-14643	ORA-14643: Hakan factor mismatch for tables in ALTER TABLE EXCHANGE PARTITION
Cause	Either records_per_block has been minimized for one of the tables to be exchanged, but not the other, or the hakan factors for the tables to be exchanged are not equal.
Action	If records_per_block has been minimized for one of the tables, but not the other, either perform alter table with the NOMINIMIZE RECORDS_PER_BLOCK option for both tables, or perform alter table with the MINIMIZE RECORDS_PER_BLOCK for both tables. If the hakan factors do not match perform alter table with the NOMINIMIZE RECORDS_PER_BLOCK option for both tables.

 

ORA-14644	ORA-14644: table is not subpartitioned by Hash method
Cause	A subpartition maintenance operation such as ALTER TABLE MODIFY PARTITION COALESCE SUBPARTITION can only be performed on Hash subpartitioned objects
Action	Re-issue the command against a Hash subpartitoned object.

 

ORA-14645	ORA-14645: STORE IN clause cannot be specified for Range List objects
Cause	A STORE IN clause was specified for Range List partitioned object
Action	Re-issue the command after removng the STORE IN clause

 

ORA-14646	ORA-14646: Specified alter table operation involving compression cannot be performed in the presence of usable bitmap indexes
Cause	The first time a table is altered to include compression, it cannot have a usable bitmap index (partition). Subsequent alter table statements involving compression do not have this same restriction.
Action	A) Drop any bitmap indexes defined on the table, and re-create them once the operation is complete or, B) Mark all index fragments of all bitmap indexes defined on the table UNUSABLE and rebuild them once the operation is complete.

 

ORA-14700	ORA-14700: Object(s) owned by SYS cannot be locked by non-SYS user
Cause	Attempt to issue a LOCK TABLE statement on SYS owned object(s) by a non-SYS user, user should minimally have DML privileges
Action	Re-issue LOCK TABLE statement for non-SYS user after granting DML privileges on object, or non-SYS user should connect as SYS

 

ORA-15000	ORA-15000: command disallowed by current instance type
Cause	The user has issued a command to a conventional RDBMS instance that is only appropriate for an ASM instance. Alternatively, the user has issued a command to an ASM instance that is only appropriate for an RDBMS instance.
Action	Connect to the correct instance type and re-issue the command.

 

ORA-15001	ORA-15001: diskgroup "string" does not exist or is not mounted
Cause	An operation failed because the diskgroup specified does not exist or is not mounted by the current ASM instance.
Action	Verify that the diskgroup name used is valid, that the diskgroup exists, and that the diskgroup is mounted by the current ASM instance.

 

ORA-15002	ORA-15002: parameter LOCK_NAME_SPACE exceeds limit of string characters
Cause	The LOCK_NAME_SPACE initialization parameter contained a value that is too long.
Action	Correct the LOCK_NAME_SPACE initialization parameter.

 

ORA-15003	ORA-15003: diskgroup "string" already mounted in another lock name space
Cause	The diskgroup could not be mounted by the ASM instance because it was operating in a lockspace different than another existing
Action	Check the LOCK_NAME_SPACE initialization parameter value, or dismount the diskgroup from the other ASM instances.

 

ORA-15004	ORA-15004: alias "string" does not exist
Cause	The specified alias did not exist within the diskgroup.
Action	Check the alias name and diskgroup name.

 

ORA-15005	ORA-15005: name "string" is already used by an existing alias
Cause	An existing alias in the diskgroup used the same name.
Action	Select another alias name, or drop the existing alias.

 

ORA-15006	ORA-15006: template "string" does not exist
Cause	The specified template did not exist within the diskgroup.
Action	Check the template name and diskgroup name.

 

ORA-15007	ORA-15007: name is already used by an existing template
Cause	A template with the same name already exists.
Action	Select another template name, or drop the existing template.

 

ORA-15008	ORA-15008: cannot drop system template
Cause	The specified template was created by the system and must always exist for proper operation.
Action	Select another template name.

 

ORA-15009	ORA-15009: ASM disk "string" does not exist
Cause	The specified ASM disk was not found.
Action	Check the ASM disk name.

 

ORA-15010	ORA-15010: name is already used by an existing ASM disk
Cause	The specified name was already used in this diskgroup.
Action	Specify a different ASM disk name.

 

ORA-15011	ORA-15011: failure group "string" contains no members
Cause	The specified name did not match the failure group of any disks in the diskgroup. This usually indicates that the failure group name was specified incorrectly.
Action	Check the failure group name.

 

ORA-15012	ORA-15012: ASM file "string" does not exist
Cause	The ASM file was not found.
Action	Check the ASM file name.

 

ORA-15013	ORA-15013: diskgroup "string" is already mounted
Cause	An ALTER DISKGROUP MOUNT command specified the name of a diskgroup which is already mounted by the current ASM instance.
Action	Check the name of the diskgroup.

 

ORA-15014	ORA-15014: location "string" is not in the discovery set
Cause	The operating system path specified was outside the set of disks that are discovered by the instance.
Action	Specify a operating system path within the set of disks that are discovered based upon the ASM_DISKSTRING parameter. Alternatively, check the setting of the ASM_DISKSTRING parameter.

 

ORA-15017	ORA-15017: diskgroup "string" cannot be mounted
Cause	The specified diskgroup could not be mounted.
Action	Check for additional errors reported.

 

ORA-15018	ORA-15018: diskgroup cannot be created
Cause	The specified diskgroup could not be created.
Action	Check for additional errors reported.

 

ORA-15019	ORA-15019: discovered duplicate path "string" for "string"
Cause	The discovery encountered multiple paths to the same disk.
Action	Check that the ASM_DISKSTRING parameter specifies only a single path for each disk.

 

ORA-15020	ORA-15020: discovered duplicate ASM disk "string"
Cause	The discovery encountered two disks claiming to be the same named ASM disk.
Action	Check that the ASM_DISKSTRING parameter specifies only a single path for each disk.

 

ORA-15021	ORA-15021: parameter "string" is not valid in string instance
Cause	The specified parameter was not supported when starting an instance of this type.
Action	Delete the specified parameter from the INIT.ORA file.

 

ORA-15023	ORA-15023: reached maximum allowable number of disks string
Cause	An attempt was made to add another disk to a diskgroup which already contains the maximum number of disks allowed.
Action	Consider dropping existing disks from the diskgroup before adding additional ones, or create a new diskgroup.

 

ORA-15024	ORA-15024: discovered duplicately numbered ASM disk string
Cause	The discovery encountered two disks claiming to have the same ASM disk number.
Action	Check that the ASM_DISKSTRING parameter specifies only a single path for each disk.

 

ORA-15025	ORA-15025: could not open disk "string"
Cause	The specified disk could not be opened.
Action	Check the additional error messages, if any.

 

ORA-15026	ORA-15026: disk "string" is not an ASM disk
Cause	The disk did not contain a valid ASM disk header.
Action	Check to see if the data on the disk has been changed by some system administrator action.

 

ORA-15027	ORA-15027: active use of diskgroup "string" precludes its dismount
Cause	An ALTER DISKGROUP ... DISMOUNT command specified a diskgroup which had database client instances with open files in the diskgroup. Diskgroups cannot be dismounted until all open files in the diskgroup are closed by the database client instances.
Action	Stop all clients that are using this diskgroup and retry the ALTER DISKGROUP ... DISMOUNT command. The V$ASM_CLIENT fixed view in an ASM instance provides a list of its active database client instances.

 

ORA-15028	ORA-15028: ASM file "string" not dropped; currently being accessed
Cause	An attempt was made to drop an ASM file, but the file was being accessed by one or more database instances and therefore could not be dropped.
Action	Shut down all database instances that might be accessing this file and then retry the drop command.

 

ORA-15029	ORA-15029: disk "string" is already mounted by this instance
Cause	An attempt was made to add to a diskgroup a disk that was already mounted by the current instance as part of some (possibly other) diskgroup.
Action	Specify a different disk in the command. Note that not even the FORCE option can be used to correct the situation until the diskgroup containing the disk becomes dismounted by this instance.

 

ORA-15030	ORA-15030: diskgroup name "string" is in use by another diskgroup
Cause	A CREATE DISKGROUP command specfied a diskgroup name that was already assigned to another diskgroup.
Action	Select a different name for the diskgroup.

 

ORA-15031	ORA-15031: disk specification "string" matches no disks
Cause	The device specification string to a CREATE DISKGROUP command did not match any devices which could be discovered.
Action	Check the device specification string matches a disk on the system.

 

ORA-15032	ORA-15032: not all alterations performed
Cause	At least one ALTER DISKGROUP action failed.
Action	Check the other messages issued along with this summary error.

 

ORA-15033	ORA-15033: disk "string" belongs to diskgroup "string"
Cause	An attempt was made to ADD to a diskgroup a disk that was already part of another diskgroup, or an attempt was made to DROP / OFFLINE / ONLINE / CHECK a disk that was not part of the specified diskgroup.
Action	For ADD, check the path specifier for the disk. If it is certain that the disk is not in use by another diskgroup, the FORCE option may be used to override this check. For the other commands, check the name of the specified disk.

 

ORA-15034	ORA-15034: disk "string" does not require the FORCE option
Cause	An attempt was made to add the disk to the diskgroup using the FORCE option. The disk was not found to be in use at the present time, so the FORCE option was not permitted.
Action	Avoid gratuitous use of the FORCE option.

 

ORA-15035	ORA-15035: no disks belong to diskgroup "string"
Cause	An attempt was made to mount a diskgroup for which no member disks were discovered.
Action	Specify a valid diskgroup name that contains disks.

 

ORA-15036	ORA-15036: disk "string" is truncated
Cause	The size of the disk, as reported by the operating system, was smaller than the size of the disk as recorded in the disk header block on the disk.
Action	Check if the system configuration has changed.

 

ORA-15037	ORA-15037: disk "string" is smaller than mimimum of string MBs
Cause	The size of the disk, as reported by the operating system, was too small to allow the disk to become part of the diskgroup.
Action	Check if the system configuration is correct.

 

ORA-15038	ORA-15038: disk "string" size mismatch with diskgroup [string] [string] [string]
Cause	An attempt was made to mount into a diskgroup a disk whose recorded allocation unit size, metadata block size, or physical sector size was inconsistent with the other diskgroup members.
Action	Check if the system configuration has changed.

 

ORA-15039	ORA-15039: diskgroup not dropped
Cause	An attempt to drop a diskgroup failed.
Action	See the associated messages for details about why the drop was not successful.

 

ORA-15040	ORA-15040: diskgroup is incomplete
Cause	Some of the disks comprising a diskgroup were not present.
Action	Check the hardware to ensure that all disks are functional. Also check that the setting of the ASM_DISKSTRING initialization parameter has not changed.

 

ORA-15041	ORA-15041: diskgroup space exhausted
Cause	The diskgroup ran out of space.
Action	Add more disks to the diskgroup, or delete some existing files.

 

ORA-15042	ORA-15042: ASM disk "string" is missing
Cause	The specified disk, which is a necessary part of a diskgroup, could not be found on the system.
Action	Check the hardware configuration.

 

ORA-15043	ORA-15043: ASM disk "string" is not a diskgroup member
Cause	The specified disk has been removed from the diskgroup, but a disk matching its name was found.
Action	Check the hardware configuration.

 

ORA-15044	ORA-15044: ASM disk "string" is incorrectly named
Cause	Either the specified disk had its contents changed such that it no longer contained an ASM disk name in its header that matches the diskgroup information or its FAILGROUP information may have become inconsistent.
Action	Drop the disk from the diskgroup.

 

ORA-15045	ORA-15045: ASM file name "string" is not in reference form
Cause	The ASM file name was not in a form that can be used to reference an existing file because a file/incarnation number or an alias name was not present or a template name was included.
Action	Correct the specified ASM file name.

 

ORA-15046	ORA-15046: ASM file name "string" is not in single-file creation form
Cause	The ASM file name was not in a form that can be used to create an single file because a file/incarnation number was present.
Action	Correct the specified ASM file name.

 

ORA-15047	ORA-15047: ASM file name "string" is not in multiple-file creation form
Cause	The ASM file name was not in a form that can be used to create multiple files because either a fully-qualified file name or an alias name was present.
Action	Correct the specified ASM file name.

 

ORA-15048	ORA-15048: ASM internal files cannot be deleted
Cause	An attempt was made to delete a metadata file used by ASM to manage the diskgroup.
Action	Check the specified ASM file name.

 

ORA-15049	ORA-15049: diskgroup "string" contains string error(s)
Cause	Errors were discovered by the ALTER DISKGROUP CHECK command.
Action	See the alert log for details of the errors.

 

ORA-15050	ORA-15050: disk "string" contains string error(s)
Cause	Errors were discovered by the ALTER DISKGROUP CHECK DISK command.
Action	See the alert log for details of the errors.

 

ORA-15051	ORA-15051: file "string" contains string error(s)
Cause	Errors were discovered by the ALTER DISKGROUP CHECK FILE command.
Action	See the alert log for details of the errors.

 

ORA-15052	ORA-15052: ASM file name "string" is not in diskgroup "string"
Cause	The ASM file name did not contain a diskgroup name that specified the correct diskgroup as implied by the other arguments to the command.
Action	Correct the specified ASM file name or diskgroup name.

 

ORA-15053	ORA-15053: diskgroup "string" contains existing files
Cause	An attempt was made to drop a diskgroup that still contains existing files.
Action	Specify the INCLUDING CONTENTS option to drop the diskgroup and all of its existing files.

 

ORA-15054	ORA-15054: disk "string" does not exist in diskgroup "string"
Cause	An attempt was made to DROP (or CHECK) a disk that is not part of the specified diskgroup.
Action	Check the name of the specified disk and the specified diskgroup.

 

ORA-15055	ORA-15055: unable to connect to ASM instance
Cause	When accessing a diskgroup for the first time, the database was unable to connect to the required ASM instance.
Action	Check the additional error messages. May need to configure correct ASM sid or make sure the database instance has OS privileges for ASM SYSDBA.

 

ORA-15056	ORA-15056: additional error message
Cause	An operating system error occured.
Action	Correct the operating system error and retry the operation.

 

ORA-15057	ORA-15057: specified size of string MB is larger than actual size of string MB
Cause	A disk size expression exceeded the amount of storage actually availalable, as reported by the operating system.
Action	Specify a valid size.

 

ORA-15058	ORA-15058: disk "string" belongs to an incompatible diskgroup
Cause	An attempt was made to ADD to a diskgroup a disk which was already part of another diskgroup. The other diskgroup was written by a more recent software release.
Action	Check the path specifier for the disk. If it is certain that the disk is not in use by another diskgroup, the FORCE option may be used to override this check.

 

ORA-15059	ORA-15059: invalid device type for ASM disk
Cause	The device type of the discovered disk was not valid for use as an ASM disk.
Action	Check the file path and retry or exclude it from the discovery set. See the accompanying operating system error for additional information.

 

ORA-15060	ORA-15060: template "string" does not exist
Cause	A command specified a template name, either directly or as part of an ASM file name, which did not exist.
Action	Check the template specifier in the command.

 

ORA-15061	ORA-15061: ASM operation not supported [string]
Cause	An ASM operation was attempted that is invalid or not supported by this version of the ASM instance.
Action	This is an internal error code that is used for maintaining compatibility between software versions and should never be visible to the user; contact Oracle support Services.

 

ORA-15062	ORA-15062: ASM disk is globally closed
Cause	The disk to which the I/O request was issued has gone offline or has been globally closed by the background process. Check other messages in the trace files for more information.
Action	Bring the disk online for I/Os to get through.

 

ORA-15063	ORA-15063: ASM discovered an insufficient number of disks for diskgroup "string"
Cause	ASM was unable to find a sufficient number of disks belonging to the diskgroup to continue the operation.
Action	Check that the disks in the diskgroup are present and functioning, that the owner of the ORACLE binary has read/write permission to the disks, and that the ASM_DISKSTRING initialization parameter has been set correctly. Verify that ASM discovers the appropriate disks by querying V$ASM_DISK from the ASM instance.

 

ORA-15064	ORA-15064: communication failure with ASM instance
Cause	There was a failure to communicate with the ASM instance, most likely because the connection went down.
Action	Check the accompanying error messages for more information on the reason for the failure. Note that database instances will always return this error when the ASM instance is terminated abnormally.

 

ORA-15065	ORA-15065: hash collision for diskgroup names "string" and "string"
Cause	There was a collision in the group name used for the diskgroup. The diskgroup(s) cannot be mounted using colliding names.
Action	Use a different diskgroup name and also report to Oracle Support Services the two diskgroup names which collided.

 

ORA-15066	ORA-15066: offlining disk "string" may result in a data loss
Cause	Following I/O failures, the disks holding all copies of a data block were attempted to be taken offline.
Action	Check the accompanying error messages for more information on the reason for the disk I/O failures.

 

ORA-15067	ORA-15067: command or option incompatible with diskgroup redundancy
Cause	An attempt was made to use a feature which is not permitted by the diskgroup"s redundancy policy. Common examples are forcibly dropping a disk from an EXTERNAL REDUNDANCY diskgroup, using the FAILGROUP clauses with an EXTERNAL REDUNDANCY diskgroup, or using invalid template attributes.
Action	Omit the option from the command.

 

ORA-15068	ORA-15068: maximum number of diskgroups string already mounted
Cause	An attempt was made to mount more diskgroups than the instance is capable of mounting at one time.
Action	Dismount a mounted diskgroup and retry the command.

 

ORA-15069	ORA-15069: ASM file "string" not accessible; timed out waiting for lock
Cause	An attempt was made to access an ASM file, but the file is currently being created, resized, or deleted and therefore cannot be accessed.
Action	No action required, or try again later, after the create or resize has completed.

 

ORA-15070	ORA-15070: maximum number of files string exceeded in diskgroup "string"
Cause	The diskgroup ran out of space.
Action	Delete some existing ASM files or create files in a new diskgroup.

 

ORA-15071	ORA-15071: ASM disk "string" is already being dropped
Cause	An attempt was made to drop a disk from a diskgroup which was already in the process of being dropped from the diskgroup. Alternatively, an attempt was made to forcibly drop a disk from a diskgroup using the FORCE option which was already being forcibly dropped from the diskgroup.
Action	Check the ASM disk name and FORCE option as specified in the command.

 

ORA-15072	ORA-15072: command requires at least string failure groups, discovered only string
Cause	An attempt was made to create either a normal redundancy diskgroup for which fewer than two failure groups were both specified and discovered, or a high redundancy diskgroup for which fewer than three failure groups were both specified and discovered.
Action	Check the that the command does specify the required number of failure groups, and that all of the specified disks are discovered by ASM. A query of the V$ASM_DISK fixed view will show which disks are discovered by ASM.

 

ORA-15073	ORA-15073: diskgroup string is mounted by another ASM instance
Cause	An attempt was made to drop a diskgroup that is still mounted somewhere in the cluster by another instance.
Action	dismount the diskgroup from all nodes except the one performing the drop diskgroup command.

 

ORA-15074	ORA-15074: diskgroup string requires rebalance completion
Cause	An attempt was made to repeatedly add or drop disks from a diskgroup. ASM could not perform the operation given the current state of the diskgroup.
Action	Manually invoke the ALTER DISKGROUP REBALANCE command and allow the rebalance to run to completion. Alternatively, invoke the ALTER DISKGROUP UNDROP DISKS command and allow the rebalance to run to completion. After the rebalance has completed, retry the operation.

 

ORA-15075	ORA-15075: disk(s) are not visible cluster-wide
Cause	An ALTER DISKGROUP ADD DISK command specified a disk that could not be discovered by one or more nodes in a RAC cluster configuration.
Action	Determine which disks are causing the problem from the GV$OSM_DISK fixed view. Check operating system permissions for the device and the storage sub-system configuration on each node in a RAC cluster that cannot identify the disk.

 

ORA-15076	ORA-15076: Emulating I/O errors on the OSM disk
Cause	The disk to which the I/O request was issued is in an error emulation mode.
Action	Bring the disk online for I/Os to get through.

 

ORA-15077	ORA-15077: could not locate ASM instance serving a required diskgroup
Cause	The instance failed to perform the specified operation because it could not locate a required ASM instance.
Action	Start an ASM instance and mount the required diskgroup.

 

ORA-15078	ORA-15078: ASM diskgroup was forcibly dismounted
Cause	The diskgroup to which the I/O request was issued was forcibly dismounted (with the ALTER DISKGROUP DISMOUNT FORCE command) so that it could not be accessed.
Action	Mount the diskgroup to allow access again.

 

ORA-15079	ORA-15079: ASM file is closed
Cause	The file to which the I/O request was issued was closed. This could have been a consequence of the diskgroup being dismounted.
Action	Make sure the diskgroup is mounted and the file is open.