Overblog Suivre ce blog
Editer la page Administration Créer mon blog
/ / /

 

LISTE CODE ERREURS ORACLE.

 

ORA-15080 ORA-15080: synchronous I/O operation to a disk failed
Cause  A synchronous I/O operation invoked on a disk has failed.
Action  Make sure that all the disks are operational.

 

ORA-15081 ORA-15081: failed to submit an I/O operation to a disk
Cause  A submission of an I/O operation to a disk has failed.
Action  Make sure that all the disks are operational.

 

ORA-15082 ORA-15082: ASM failed to communicate with database instance
Cause  There was a failure when ASM tried to communicate with a database 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 the ASM instances may return this error when a database instance is terminated abnormally.

 

ORA-15083 ORA-15083: failed to communicate with ASMB background process
Cause  A database instance failed to communicate with its ASMB background process when attempting to access an ASM file.
Action  Check the alert log for more information on the reason for the failure.

 

ORA-15090 ORA-15090: handle string is not a valid descriptor
Cause  The file handle was not valid in this session.
Action  Submit a handle obtained from a successful call to DBMS_DISKGROUP.OPEN().

 

ORA-15091 ORA-15091: operation incompatible with open handle in this session
Cause  The current session contained an open handle from the DBMS_DISKGROUP PL/SQL package which precluded performing the command.
Action  Close the hanlde with DBMS_DISKGROUP.CLOSE() before executing the command, or execute the command in a different session.

 

ORA-15092 ORA-15092: I/O request size string is not a multiple of logical block size string
Cause  The length of the request was not a multiple of logical block size.
Action  Correct the error and retry the operation.

 

ORA-15093 ORA-15093: buffer only contains string bytes, I/O requested is string bytes
Cause  The buffer supplied for write was too small to satisfy the request.
Action  Correct the error and retry the operation.

 

ORA-15094 ORA-15094: attempted to write to file opened in read only mode
Cause  The file handle passed to DBMS_DISKGROUP.WRITE() did not have write privileges.
Action  Obtain a file handle in read-write mode and retry the write operation.

 

ORA-15095 ORA-15095: reached maximum ASM file size (string GB)
Cause  An ASM file creation or file resize operation exceeded the maximum file size permitted by ASM.
Action  Use smaller files.

 

ORA-15096 ORA-15096: lost disk write detected
Cause  A failure either by disk hardware or disk software caused a disk write to to be lost, even though ASM received acknowledgement that the write completed. Alternatively, a clustering hardware failure or a clustering software failure resulted in an ASM instance believing that another ASM instance had crashed, when in fact it was still active.
Action  The disk group is corrupt and cannot be recovered. The disk group must be recreated, and its contents restored from backups.

 

ORA-15097 ORA-15097: cannot SHUTDOWN ASM instance with connected RDBMS instance
Cause  A SHUTDOWN command was issued to an ASM instance that had one or more connected RDBMS instances.
Action  Connect to each RDBMS instance and shut it down, and then reissue the SHUTDOWN command to the ASM instance. Alternatively, use the SHUTDOWN ABORT command. Note that issuing the SHUTDOWN ABORT command to an ASM instance results in abormal termination of all RDBMS instances connected to that ASM instance.

 

ORA-15100 ORA-15100: invalid or missing diskgroup name
Cause  The command did not specify a valid diskgroup name.
Action  Specify a valid diskgroup name.

 

ORA-15101 ORA-15101: no action specified
Cause  The ALTER DISKGROUP command did not specify any alterations.
Action  Specify at least one operation clause.

 

ORA-15102 ORA-15102: invalid POWER expression
Cause  The syntax of the POWER expression was invalid.
Action  Specify a valid POWER expression.

 

ORA-15103 ORA-15103: conflicting or duplicate REPAIR options
Cause  The command specified conflicting or duplicate REPAIR keywords.
Action  Specify only one REPAIR action.

 

ORA-15104 ORA-15104: conflicting CONTENTS options
Cause  The command specified conflicting or duplicate INCLUDING CONTENTS or EXCLUDING CONTENTS options.
Action  Specify only one option.

 

ORA-15105 ORA-15105: missing or invalid FAILGROUP name
Cause  The command did not specify a valid failure group name.
Action  Specify a valid failure group name.

 

ORA-15106 ORA-15106: missing or invalid operating system disk locator string
Cause  The command did not specify a valid operating system path for the device as a string.
Action  Specify a valid operating system path for the device.

 

ORA-15107 ORA-15107: missing or invalid ASM disk name
Cause  The command did not specify a valid ASM disk name identifier.
Action  Specify a valid ASM disk name identifier.

 

ORA-15108 ORA-15108: missing or invalid template name
Cause  The command did not specify a valid template name identifier.
Action  Specify a valid template name identifier.

 

ORA-15109 ORA-15109: conflicting protection attributes specified
Cause  The command contained an invalid combination of the UNPROTECTED, MIRROR, or PARITY keywords.
Action  Specify only one keyword.

 

ORA-15110 ORA-15110: no diskgroups mounted
Cause  No diskgroups were specified in the ASM_DISKGROUPS parameter, so instance startup or the ALTER DISKGROUP ALL MOUNT command did not mount any diskgroups.
Action  Specify valid diskgroups in the ASM_DISKGROUPS parameter or ignore the error.

 

ORA-15111 ORA-15111: conflicting or duplicate STRIPE options
Cause  The command contained both a FINE and COARSE keyword, or contained the FINE keyword more than once, or contained the COARSE keyword more than once.
Action  Specify only one keyword.

 

ORA-15112 ORA-15112: No diskgroups are currently mounted.
Cause  An ALTER DISKGROUP ALL command did not find any mounted diskgroups upon which to operate. Either instance shutdown or an ALTER DISKGROUP ALL DISMOUNT command did not dismount any diskgroups, or an ALTER DISKGROUP ALL UNDROP DISKS command did not undrop any disks.
Action  Mount the diskgroups on which you wish to operate or ignore the error.

 

ORA-15113 ORA-15113: alias name "string" refers to a directory
Cause  The name specified referred to a directory in the alias directory and not a valid alias entry.
Action  Check the alias name and retry.

 

ORA-15114 ORA-15114: missing or invalid ASM file name
Cause  The command did not specify a valid ASM file name identifier.
Action  Specify a valid ASM file name identifier.

 

ORA-15115 ORA-15115: missing or invalid ASM disk size specifier
Cause  The command did not specify a valid ASM disk size.
Action  Specify a valid ASM disk size.

 

ORA-15116 ORA-15116: invalid combination of ALTER DISKGROUP options
Cause  The ALTER DISKGROUP options may not be combined in this manner.
Action  Issue separate ALTER DISKGROUP commands to accomplish the desired action.

 

ORA-15117 ORA-15117: command only operates on one diskgroup
Cause  An ALTER DISKGROUP, CREATE DISKGROUP, or DROP DISKGROUP command specified a list of diskgroups or the keyword ALL in a context where only a single diskgroup was permitted.
Action  Issue separate ALTER DISKGROUP, CREATE DISKGROUP, or DROP DISKGROUP commands to accomplish the desired action.

 

ORA-15120 ORA-15120: ASM file name "string" does not begin with the ASM prefix character
Cause  A file name was specified to ASM which did not begin with the ASM prefix character (currently "+"). ASM uses the prefix to determine that a file specification is in fact an ASM file.
Action  Correct the file name specification.

 

ORA-15121 ORA-15121: ASM file name "string" contains an invalid diskgroup name
Cause  A file name was specified that did not contain a valid diskgroup name. The diskgroup name follows immediately after the ASM prefix character. It must 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-15122 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 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 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 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 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 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 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 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 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 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 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 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 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 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-15152 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 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 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 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 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 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-15158 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-15162 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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-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-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-15192 ORA-15192: invalid ASM disk header [string] [string] [string] [string] [string]
Cause  ASM encountered an invalid disk header.
Action  Contact Oracle Support Services.

 

ORA-15193 ORA-15193: Internal ASM tracing event number 15193
Cause  Set this event only under the supervision of Oracle development.
Action  None.

 

ORA-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-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-15196 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 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 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-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-15200 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 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 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 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 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 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 ORA-15206: duplicate diskgroup string specified
Cause  A command specified the same diskgroup twice.
Action  Specify each diskgroup only once.

 

ORA-16000 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-16001 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-16002 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-16003 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-16004 ORA-16004: backup database requires recovery
Cause  The control file is for a backup database which requires recovery, and cannot be opened for read-only access by this instance.
Action  Perform the necessary recovery and re-open for read-only access.

 

ORA-16005 ORA-16005: database requires recovery
Cause
 The database requires recovery, and therefore cannot be opened for read-only access by this instance.
Action  Perform the necessary recovery and re-open for read-only access.

 

ORA-16006 ORA-16006: audit_trail destination incompatible with database open mode
Cause  The audit_trail initialization parameter was set to "DB" (or TRUE), which is incompatible with a database opened for read-only access.
Action  When the database is opened for read-only access, the audit_trail initialization parameter can only be set to "OS" or "NONE" (FALSE).

 

ORA-16007 ORA-16007: invalid backup control file checkpoint
Cause  The backup control file being opened for read-only access does not contain a valid control file checkpoint. Therefore the database cannot be opened for read-only access.
Action  First open the database for read-write access which will result in valid control file checkpoint. Then re-open the database for read-only access.

 

ORA-16008 ORA-16008: indeterminate control file checkpoint
Cause  The control file for the database being opened for read-only access was created via CREATE CONTROLFILE. Therefore a control file checkpoint could not be calculated and the database cannot be opened for read-only access.
Action  First open the database for read-write access which will result in valid control file checkpoint. Then re-open the database for read-only access.

 

ORA-16009 ORA-16009: remote archive log destination must be a STANDBY database
Cause  The database associated with the archive log destination service name is other than the required STANDBY type database. Remote archival of redo log files is not allowed to non-STANDBY database instances.
Action  Take the necessary steps to create the required compatible STANDBY database before retrying the ARCHIVE LOG processing.

 

ORA-16011 ORA-16011: Archivelog Remote File Server process in Error state
Cause  The archivelog remote file server (RFS) process at the specified standby database site has experienced an unrecoverable error and is unable to receive further archive log data.
Action  Correct the problem at the standby database site.

 

ORA-16012 ORA-16012: Archive log standby database identifier mismatch
Cause  The database identifiers of the Primary and Standby database do not match. Remote archival of redo log files is not allowed to incompatible STANDBY database instances.
Action  Take the necessary steps to create the required compatible STANDBY database before retrying the ARCHIVE LOG processing.

 

ORA-16013 ORA-16013: log string sequence# string does not need archiving
Cause  An attempt was made to archive the named file manually, but the file did not require archiving. The file had previously been successfully archived.
Action  No action is required.

 

ORA-16014 ORA-16014: log string sequence# string not archived, no available destinations
Cause  An attempt was made to archive the named log, but the archive was unsuccessful. The archive failed because there were no archive log destinations specified or all destinations experienced debilitating errors.
Action  Verify that archive log destinations are being specified and/or take the necessary step to correct any errors that may have occurred.

 

ORA-16015 ORA-16015: log string sequence# string not archived, media recovery disabled
Cause  An attempt was made to archive the named log, but the archive was unsuccessful. A standby archive log destination was specified and the database was not media recovery enabled. This is not allowed.
Action  Disable the standby destination or enable media recovery and retry.

 

ORA-16016 ORA-16016: archived log for thread string sequence# string unavailable
Cause  The managed standby database recovery operation has timed out waiting for the requested archived log file.
Action  Verify that the primary database is still archiving redo logs to the standby recovery database site and reissue the RECOVER STANDBY DATABASE WAIT command.

 

ORA-16017 ORA-16017: cannot use LOG_ARCHIVE_DUPLEX_DEST without a primary archive destination
Cause  The parameter LOG_ARCHIVE_DUPLEX_DEST was set to a non-NULL value when the primary archive destination was set to NULL explicitly.
Action  Set the primary archive destination to a valid non-NULL value.

 

ORA-16018 ORA-16018: cannot use string with LOG_ARCHIVE_DEST_n or DB_RECOVERY_FILE_DEST
Cause  One of the following events caused an incompatibility:
1) Parameter LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST was in use when a LOG_ARCHIVE_DEST_n (n = 1...10) parameter was encountered while fetching initialization parameters.
2) An ALTER SYSTEM ARCHIVE LOG START TO command was in effect when a LOG_ARCHIVE_DEST_n parameter was encountered while fetching initialization parameters.
3) A LOG_ARCHIVE_DEST_n parameter was in use when an ALTER SYSTEM command was used to define a value for either the LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST parameter.
4) Parameter DB_RECOVERY_FILE_DEST was in use when an attempt was made to use an ALTER SYSTEM or ALTER SESSION command to define a value for LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST.
Action  Eliminate any incompatible parameter definitions.

 

 

Haut de Page www.dba-ora.fr

Partager cette page

Repost 0
Published by