ORA-16003: standby database is restricted to read-only access

ORA-16003: standby database is restricted to read-only access

Cause: To ensure its integrity, a standby database can only be opened for read-only access.

Action: Re-issue the ALTER DATABASE OPEN specifying READ ONLY.

ORA-16002: database already open for read-write access by another instance

ORA-16002: database already open for read-write access by another instance

Cause: The database has been opened for read-write access by another instance, and cannot be opened for read-only access by this instance.

Action: This instance must be opened for read-only access, or all other instances must first be shut down and re-opened for read-write access.

ORA-16001: database already open for read-only access by another instance

ORA-16001: database already open for read-only access by another instance

Cause: The database has been opened for read-only access by another instance, and cannot be opened for read-write access by this instance.

Action: This instance must be opened for read-write access, or all other instances must first be shut down and re-opened for read-only access.

ORA-16000: database open for read-only access

ORA-16000: database open for read-only access

Cause: The database has been opened for read-only access. Attempts to modify the database using inappropriate DML or DDL statements generate this error.

Action: In order to modify the database, it must first be shut down and re-opened for read-write access.

ORA-15206: duplicate diskgroup string specified

ORA-15206: duplicate diskgroup string specified

Cause: A command specified the same diskgroup twice.

Action: Specify each diskgroup only once.

ORA-15205: requested mirror side unavailable

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-15204: database version string is incompatible with diskgroup string

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-15203: diskgroup string contains disks from an incompatible version of ASM

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-15202: cannot create additional ASM internal change segment

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-15201: disk string contains a valid RDBMS file

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-15200: initialization parameter string (string) is not a power of two

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-15199: Internal ASM tracing event number 15199

ORA-15199: Internal ASM tracing event number 15199

Cause: Set this event only under the supervision of Oracle development.

Action: Traces execution of ASM. Level indicates verbosity of tracing.

ORA-15198: operation string is not yet available

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-15197: suppressing string additional ASM messages

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-15196: invalid ASM block header (string:string( (string( (string( (string( (string = string(

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-15195: Internal ASM testing event number 15195

ORA-15195: Internal ASM testing event number 15195

Cause: Set this event only under the supervision of Oracle development.

Action: The level controls which ASM errors are simulated.

ORA-15194: Internal ASM-DB interaction testing event number 15194

ORA-15194: Internal ASM-DB interaction testing event number 15194

Cause: Set this event only under the supervision of Oracle development.

Action: The level controls which ASM-DB operation is interuppted.

ORA-15193: Internal ASM tracing event number 15193

ORA-15193: Internal ASM tracing event number 15193

Cause: Set this event only under the supervision of Oracle development.

Action: None.

ORA-15192: invalid ASM disk header (string( (string( (string( (string( (string(

ORA-15192: invalid ASM disk header (string( (string( (string( (string( (string(

Cause: ASM encountered an invalid disk header.

Action: Contact Oracle Support Services.

ORA-15191: Internal ASM testing event number 15191

ORA-15191: Internal ASM testing event number 15191

Cause: Set this event only under the supervision of Oracle development.

Action: The level controls which ASM errors are emulated.

ORA-15190: Internal ASM testing event number 15190

ORA-15190: Internal ASM testing event number 15190

Cause: Set this event only under the supervision of Oracle development.

Action: The level controls which ASM disks encounter rebalance IO errors.

ORA-15186: ASMLIB error function = (string(, error = (string(, mesg = (string(

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-15185: Could not close dynamic library string, error (string(

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-15184: ASMLIB error could not be determined (string( (string(

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-15183: ASMLIB initialization error (string(

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-15182: ASMLIB (string( version mismatch, ORACLE version (string(

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-15181: Symbol (string( not found in library string, error (string(

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-15180: Could not open dynamic library string, error (string(

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-15179: missing or invalid alias name

ORA-15179: missing or invalid alias name

Cause: The command did not specify a valid alias identifier.

Action: Specify a valid alias identifier.

ORA-15178: directory string is not empty; cannot drop this directory

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-15177: cannot operate on system aliases

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-15176: file string already has an alias associated with it

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-15175: cannot create alias for diskgroup metadata file string

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-15173: entry string does not exist in directory string

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-15171: invalid syntax in the alias path after string

ORA-15171: invalid syntax in the alias path after string

Cause: An invalid alias or directory name syntax was specified.

Action: Correct the alias path and try again.

ORA-15170: cannot add entry string in directory string

ORA-15170: cannot add entry string in directory string

Cause: Other errors prevented directory or alias creation.

Action: Correct the errors and try again.

ORA-15169: destination string is a subdirectory of string

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-15168: rolling downgrade prevented by string

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-15166: cluster in rolling downgrade from version (string( to (string(

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-15164: cluster rolling downgrade incomplete

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-15163: cluster not in rolling downgrade

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-15162: cluster in rolling downgrade

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-15158: rolling upgrade prevented by string

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-15157: rolling upgrade or downgrade is not allowed

ORA-15157: rolling upgrade or downgrade is not allowed

Cause: The cluster was not capable of handling ASM rolling upgrade or downgrade.

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-15156: cluster in rolling upgrade from version (string( to (string(

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-15155: version incompatible with the cluster

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-15154: cluster rolling upgrade incomplete

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-15153: cluster not in rolling upgrade

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-15152: cluster in rolling upgrade

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-15151: missing or invalid version number for rolling upgrade or downgrade

ORA-15151: missing or invalid version number for rolling upgrade or downgrade

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-15150: instance lock mode string conflicts with other ASM instance(s)

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-15133: instance recovery required for diskgroup string

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-15132: block string of file string in diskgroup string could not be written

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 or 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-15131: block string of file string in diskgroup string could not be read

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 or 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-15130: diskgroup string is being dismounted

ORA-15130: diskgroup string is being dismounted

Cause: The diskgroup is being dismounted by request or because an I or 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-15129: entry string does not refer to a valid directory

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-15128: ASM file name string exceeds maximum length string

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-15127: ASM file name string cannot use templates

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-15126: component within ASM file name string exceeds maximum length

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-15125: ASM file name string contains an invalid template name

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.