Monday 19 March 2012

ORA-15054: disk string does not exist in diskgroup string

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-15053: diskgroup string contains existing files

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-15052: ASM file name string is not in diskgroup string

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-15051: file string contains string error(s)

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-15050: disk string contains string error(s)

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-15049: diskgroup string contains string error(s)

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-15048: ASM internal files cannot be deleted

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-15047: ASM file name string is not in multiple-file creation form

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-15046: ASM file name string is not in single-file creation form

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 or incarnation number was present.

Action: Correct the specified ASM file name.

ORA-15045: ASM file name string is not in reference form

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 or incarnation number or an alias name was not present or a template name was included.

Action: Correct the specified ASM file name.

ORA-15044: ASM disk string is incorrectly named

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-15043: ASM disk string is not a diskgroup member

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-15042: ASM disk string is missing

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-15041: diskgroup space exhausted

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-15040: diskgroup is incomplete

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-15039: diskgroup not dropped

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-15038: disk string size mismatch with diskgroup (string( (string( (string(

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-15037: disk string is smaller than mimimum of string MBs

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-15036: disk string is truncated

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-15035: no disks belong to diskgroup string

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-15034: disk string does not require the FORCE option

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-15033: disk string belongs to diskgroup string

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 or OFFLINE or ONLINE or 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-15032: not all alterations performed

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-15031: disk specification string matches no disks

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-15030: diskgroup name string is in use by another diskgroup

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-15029: disk string is already mounted by this instance

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-15028: ASM file string not dropped; currently being accessed

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-15027: active use of diskgroup string precludes its dismount

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-15026: disk string is not an ASM disk

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-15025: could not open disk string

ORA-15025: could not open disk string

Cause: The specified disk could not be opened.

Action: Check the additional error messages, if any.

ORA-15024: discovered duplicately numbered ASM disk string

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-15023: reached maximum allowable number of disks string

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-15021: parameter string is not valid in string instance

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-15020: discovered duplicate ASM disk string

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-15019: discovered duplicate path string for string

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-15018: diskgroup cannot be created

ORA-15018: diskgroup cannot be created

Cause: The specified diskgroup could not be created.

Action: Check for additional errors reported.

ORA-15017: diskgroup string cannot be mounted

ORA-15017: diskgroup string cannot be mounted

Cause: The specified diskgroup could not be mounted.

Action: Check for additional errors reported.

ORA-15014: location string is not in the discovery set

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-15013: diskgroup string is already mounted

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-15012: ASM file string does not exist

ORA-15012: ASM file string does not exist

Cause: The ASM file was not found.

Action: Check the ASM file name.

ORA-15011: failure group string contains no members

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-15010: name is already used by an existing ASM disk

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-15009: ASM disk string does not exist

ORA-15009: ASM disk string does not exist

Cause: The specified ASM disk was not found.

Action: Check the ASM disk name.

ORA-15008: cannot drop system template

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-15007: name is already used by an existing template

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-15006: template string does not exist

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-15005: name string is already used by an existing alias

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-15004: alias string does not exist

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-15003: diskgroup string already mounted in another lock name space

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-15002: parameter LOCK_NAME_SPACE exceeds limit of string characters

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-15001: diskgroup string does not exist or is not mounted

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-15000: command disallowed by current instance type

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-14700: Object(s) owned by SYS cannot be locked by non-SYS user

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-14646: Specified alter table operation involving compression cannot be performed in the presence of usable bitmap indexes

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-14645: STORE IN clause cannot be specified for Range List objects

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-14644: table is not subpartitioned by Hash method

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-14643: Hakan factor mismatch for tables in ALTER TABLE EXCHANGE PARTITION

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-14642: Bitmap index mismatch for tables in ALTER TABLE EXCHANGE PARTITION

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-14641: STORE-IN clause can be specified only for a Hash, Composite Range Hash table or partition

ORA-14641: STORE-IN clause can be specified only for a Hash, Composite Range Hash table or partition

Cause: Specifying a STORE-IN clause during CREATE or 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-14640: add or coalesce index partition operation is valid only for hash partitioned global indexes

ORA-14640: add or 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 or drop instead of add or coalesce.