ORA-15122: ASM file name 'string' contains
an invalid file number
Cause:
A numeric file name was specified which did not contain a valid ASM file
number. The ASM file number follows immediately after the diskgroup name. It
must be preceeded by a '.' character, and contain only numeric characters.
Action:
Correct the file name specification.
ORA-15123: ASM file name 'string' contains
an invalid incarnation number
Cause:
A numeric file name was specified which did not contain a valid ASM incarnation
number. The ASM incarnation number follows immediately after the ASM file
number. It must be preceeded by a '.' character, and contain only numeric
characters.
Action:
Correct the file name specification.
ORA-15124: ASM file name 'string' contains
an invalid alias name
Cause:
A file name was specified which did not contain a valid ASM alias name. The ASM
alias name, if present, follows immediately after the diskgroup name, in place
of the ASM file number. It must be preceeded by a slash, start with an
alphabetic character, and consist of up to 48 characters which are alphabetic,
numeric, or the characters '$', '_', '-', or '#". A space can separate two
parts of an alias name.
Action:
Correct the file name specification.
ORA-15125: ASM file name 'string' contains
an invalid template name
Cause:
A file name was specified to ASM which did not contain a valid template name.
The template name, if present, follows immediately after the ASM incarnation
number or the ASM alias name, if such is used in place of the ASM file number.
It must be enclosed in parenthesis, start with an alphabetic character, and
consist of up to 30 characters which are alphabetic, numeric, or the characters
'$' and '_'.
Action:
Correct the file name specification.
ORA-15126: component within ASM file name 'string'
exceeds maximum length
Cause:
The maximum identifier length of 30 characters was exceeded for the diskgroup
name, template name, or alias name field within the ASM file name.
Action:
Correct the file name specification.
ORA-15127: ASM file name 'string' cannot use
templates
Cause:
A fully qualified ASM file name was specified. Such a specification does not
permit the inclusion of a template name in the ASM file name.
Action:
Correct the file name specification.
ORA-15128: ASM file name 'string' exceeds
maximum length string
Cause:
The maximum ASM file name length of 256 characters was exceeded for the
combination of diskgroup name, file number, template name, alias name plus
punctuation within the ASM file name.
Action:
Correct the file name specification.
ORA-15129: entry 'string' does not refer to
a valid directory
Cause:
The entry indicated did not refer to a directory. Attempt was made to access
the contents of this directory.
Action:
Correct the error and try again.
ORA-15130: diskgroup "string" is
being dismounted
Cause:
The diskgroup is being dismounted by request or because an I/O error was
encountered that could not be handled by taking the disks offline. A disk
cannot be offlined whenever doing so could result in all copies of a redundant
extent being unavailable.
Action:
Repair the hardware problem and re-mount the diskgroup. Refer to the alert log
to determine which disks have failed.
ORA-15131: block string of file string
in diskgroup string could not be read
Cause:
A block could not be read because the disk containing the block is either
offline or an I/O error occured while reading the block. If this is mirrored
file, then all disks that contain a copy of the block are either offline or
received errors.
Action:
Repair the affected disk and bring it back online. Refer to accompanying error
messages to determine which disk has failed.
ORA-15132: block string of file string
in diskgroup string could not be written
Cause:
A block could not be written because the disk containing the block is either
offline or an I/O error occured while writing the block. If this is mirrored file,
then insufficient disks which contain a copy of the block are either offline or
received errors.
Action:
Repair the affected disk and bring it back online. Refer to accompanying error
messages to determine which disk has failed.
ORA-15133: instance recovery required for diskgroup
string
Cause:
An instance in the cluster crashed making instance recovery necessary.
Action:
None. This error should not normally be seen by an ASM client. ASM will trap
this error and retry the operation after doing instance recovery automatically.
ORA-15150: instance lock mode 'string'
conflicts with other ASM instance(s)
Cause:
Some other ASM instance used the lock name space in a conflicting mode.
Action:
Shut down the other instance or start up in compatible mode. Alternatively, set
the DB_UNIQUE_NAME initialization parameter to avoid the conflict.
ORA-15151: missing or invalid version number for
rolling migration
Cause:
The command did not sepcify a valid version number.
Action:
Correct the version number in the command. It should be of the form v#.#.#.#.#
or other forms with fewer numbers delimited by a period. The version number
must be different from the current software version of the instance.
ORA-15152: cluster in rolling upgrade
Cause:
The cluster was already in the middle of rolling upgrade.
Action:
Rolling upgrade needs to be stopped before attempting to start again.
ORA-15153: cluster not in rolling upgrade
Cause:
The cluster was not in rolling upgrade.
Action:
Start the rolling upgrade using the ALTER SYSTEM START ROLLING command.
ORA-15154: cluster rolling upgrade incomplete
Cause:
The cluster was still performing rolling upgrade.
Action:
Ensure that all the instances in the cluster are upgraded before retrying the
command.
ORA-15155: version incompatible with the cluster
Cause:
The current software version of the instance was incompatible with the other
members of the cluster.
Action:
Make sure that all the members of the cluster are at the same version. If you
are attempting to perform rolling upgrade, execute ALTER SYSTEM START ROLLING
command. Ensure that the version being upgraded to is compatible with the
existing version of the cluster.
ORA-15156: cluster in rolling upgrade from version
[string] to [string]
Cause:
The current software version of the instance was incompatible with the rolling
upgrade operation of the cluster.
Action:
The version number of new member instance must be one of the two versions
involved in the rolling upgrade.
ORA-15157: rolling migration is not allowed
Cause:
The cluster was not capable of handling ASM rolling migration.
Action:
The Oracle Cluster Services is using vendor clusterware. Oracle cannot perform
rolling upgrade or downgrade using vendor cluster ware. Restart ASM instances
using Oracle cluster ware and retry the operation.
ORA-15158: rolling upgrade prevented by string
Cause:
One or more instances were blocking the rolling upgrade.
Action:
Terminate or wait until the reported operation is complete before attempting
the rolling upgrade to the cluster.
ORA-15160: rolling migration internal fatal error
in module string,string
Cause:
Rolling migration experienced a fatal error.
Action:
Please contact Oracle support services.
ORA-15161: invalid SYS_CLUSTER_PROPERTIES parameter
Cause:
The parameter passed in for SYS_CLUSTER_PROPERTIES is invalid
Action:
Pass in the correct parameter, refer to user documentation for a list of
allowed parameter values.
ORA-15162: cluster in rolling downgrade
Cause:
The cluster was already in the middle of rolling downgrade.
Action:
Rolling downgrade needs to be stopped before attempting to start again.
ORA-15163: cluster not in rolling downgrade
Cause:
The cluster was not in rolling downgrade.
Action:
Start the rolling downgrade using the ALTER SYSTEM START ROLLING command.
ORA-15164: cluster rolling downgrade incomplete
Cause:
The cluster was still performing rolling downgrade.
Action:
Ensure that all the instances in the cluster are downgraded before retrying the
command.
ORA-15166: cluster in rolling downgrade from version
[string] to [string]
Cause:
The current software version of the instance was incompatible with the rolling
downgrade operation of the cluster.
Action:
The version number of new member instance must be one of the two versions
involved in the rolling downgrade.
ORA-15168: rolling downgrade prevented by string
Cause:
One or more instances were blocking the rolling downgrade.
Action:
Terminate or wait until the reported operation is complete before attempting
the rolling downgrade to the cluster.
ORA-15169: destination 'string' is a
subdirectory of 'string'
Cause:
Attempt to rename directory failed because the new directory name was a
subdirectory of the original directory.
Action:
Correct the path of the destination and try again.
ORA-15170: cannot add entry 'string' in
directory 'string'
Cause:
Other errors prevented directory/alias creation.
Action:
Correct the errors and try again.
ORA-15171: invalid syntax in the alias path after 'string'
Cause:
An invalid alias/directory name syntax was specified.
Action:
Correct the alias path and try again.
ORA-15173: entry 'string' does not exist in
directory 'string'
Cause:
The specified alias did not exist in the given directory.
Action:
Correct the alias path and try again.
ORA-15175: cannot create alias for diskgroup
metadata file 'string'
Cause:
An attempt was made to create an alias for a diskgroup metadata file.
Action:
Correct the alias path and try again.
ORA-15176: file 'string' already has an
alias associated with it
Cause:
An attempt was made to create an alias for a file that already had an existing
alias.
Action:
Correct the file name and try again or drop existing alias.
ORA-15177: cannot operate on system aliases
Cause:
An attempt was made to modify a system alias.
Action:
Correct the alias name and try again.
ORA-15178: directory 'string' is not empty;
cannot drop this directory
Cause:
An attempt was made to drop a directory that contained valid entries.
Action:
Correct the directory path or specify the FORCE option to drop a directory that
is not empty.
ORA-15179: missing or invalid alias name
Cause:
The command did not specify a valid alias identifier.
Action:
Specify a valid alias identifier.
ORA-15180: could not open dynamic library string,
error [string]
Cause:
The library was not accessible
Action:
Correct the permissions of the library and try again.
ORA-15181: symbol [string] not found in
library string, error [string]
Cause:
An error was encountered while loading the specified ASMLIB symbol.
Action:
Correct the error reported and try again.
ORA-15182: ASMLIB [string] version mismatch,
ORACLE version [string]
Cause:
The ASMLIB version reported is not supported by the ORACLE binary.
Action:
Install the correct library and try again.
ORA-15183: ASMLIB initialization error [string]
Cause:
Unable to initialize the ASMLIB in ORACLE.
Action:
Contact ASMLIB library vendor support with the error details.
ORA-15184: ASMLIB error could not be determined [string]
[string]
Cause:
An error was encountered which cannot be diagnosed further.
Action:
Contact ASMLIB libary vendor for support.
ORA-15185: could not close dynamic library string,
error [string]
Cause:
Could not close the dynamic library.
Action:
Contact ASMLIB libary vendor for support.
ORA-15186: ASMLIB error function = [string],
error = [string], mesg = [string]
Cause:
An error occured during a call to function listed in the error.
Action:
The detailed message associated with the error is listed along with the error.
Correct the error and try again or contact ASMLIB library vendor for support.
ORA-15192: invalid ASM disk header [string]
[string] [string] [string] [string]
Cause:
ASM encountered an invalid disk header.
Action:
Contact Oracle Support Services.
ORA-15196: invalid ASM block header [string:string]
[string] [string] [string] [string != string]
Cause:
ASM encountered an invalid metadata block.
Action:
Contact Oracle Support Services.
ORA-15197: suppressing string additional ASM
messages
Cause:
The ASM command generated so many erorrs that this summary message was reported
in place of many individual messages.
Action:
If the command contained multiple actions, try separating each action into its
own command and executing each command by itself. Otherwise, try not to
generate so many errors.
ORA-15198: operation string is not yet
available
Cause:
An unimplemented operation was attempted.
Action:
Consider upgrading to later releases as they become available.
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 ZONE 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 ZONE 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-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: 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-15450: invalid volume name specifier
Cause:
The volume name specified was invalid
Action:
Specify a valid volume name.
No hay comentarios:
Publicar un comentario