ORA-10281: maximum time to wait for process creation
Cause: used to override the default SPMXWAIT, level = timeout in sec.
Action: None
ORA-10282: Inhibit signalling of other backgrounds when one dies
Cause: Used in KSB
Action: None
ORA-10284: simulate zero/infinite asynch I/O buffering
Cause: Used in KCF, level=1 out of space (red), level=2 infinite (green)
Action: None
ORA-10452: Cannot do block media recovery; media recovery session may be in progress
Cause: A media recovery, RMAN, or flashback database session may have been in progress when an attempt was made to perform block media recovery on the standby database.
Action: Check for and cancel any conflicting recovery session and perform block media recovery on the standby database.
ORA-10456: cannot open standby database; media recovery session may be in progress
Cause: A media recovery, RMAN, or flashback database session may have been in progress on a mounted instance of a standby database when an attempt was made to open the standby database.
Action: Check for and cancel any conflicting recovery session and open the standby database.
ORA-10457: cannot close standby database due to active media recovery
Cause: A media recovery session was in progress on a standby database when an attempt was made to close the standby database.
Action: Cancel the media recovery session and close the standby database.
ORA-10458: standby database requires recovery
Cause: A standby database was in a state requiring media recovery when an attempt was made to open the standby database.
Action: Perform the necessary recovery and open the standby database.
ORA-10459: cannot start media recovery on standby database; another instance may be open
Cause: An attempt was made to perform media recovery on a standby database while another instance performed recovery on the standby or had the standby open.
Action: Close the standby on all other instances, cancel any conflicting recovery session, and perform manual recovery.
ORA-10469: error creating control file backup, no checkpoint
Cause: The control file being backed up did not contain a valid control file checkpoint. Therefore the control file could not be backed up, as such a backup would not be usable later for recovery. A common cause for this situation is that you executed CREATE CONTROLFILE, which mounts the database, but not ALTER DATABASE OPEN, to open the database. The latter operation generates a valid control file checkpoint.
Action: Open the database with ALTER DATABASE OPEN ..., which results in a valid control file checkpoint. Run the backup operation again.
ORA-10546: Cannot perform block media recovery; standby database does not have requisite redo.
Cause: An attempt was made to perform block media recovery on the standby database when the necessary redo was not available.
Action: Wait until the necessary redo is available and reattempt block media recovery.
ORA-10547: Cannot perform block media recovery; standby database is not caught up with primary.
Cause: An attempt was made to perform block media recovery on the standby database up to scn %s, which is greater than the highest scn of %s yet applied at the standby.
Action: Recover the standby up to scn %s and reattempt block media recovery.
ORA-10548: Cannot perform block media recovery on a read-only plugged-in datafile.
Cause: An attempt was made to perform block media recovery on a read-only plugged-in datafile.
Action: Convert the plugged-in datafile to read/write and reattempt block media recovery.
ORA-10549: Cannot perform block media recovery using a read-only plugged-in backup datafile.
Cause: An attempt was made to perform block media recovery using a backup of a read-only plugged-in datafile.
Action: Reattempt block media recovery using a backup taken after the plugged-in datafile has been converted to read/write.
ORA-10552: Inconsistent plug-in file string encountered during standby recovery
Cause: Standby recovery in read-only mode stopped and the database was closed because recovery encountered a plug-in file that was already converted.
Action: Try opening the database again or restart standby recovery.
ORA-10553: Incompatible UNTIL CONSISTENT clause
Cause: RECOVER UNTIL CONSISTENT required database-level recovery with a backup control file.
Action: Omit the UNTIL CONSISTENT clause and retry recovery.
ORA-10554: Media recovery failed to bring datafile string to a consistent point
Cause: Media recovery couldn't recover database to a consistent point due to the specified datafile.
Action: Restore a backup of the datafile.
ORA-10560: block type 'string'
Cause: Report block type for details of another error.
Action: See associated error message.
ORA-10561: block type 'string', data object# string
Cause: Report block type and data object number for details of another error.
Action: See associated error message.
ORA-10562: Error occurred while applying redo to data block (file# string, block# string)
Cause: See other errors on error stack.
Action: Investigate why the error occurred and how important is the data block. Media and standby database recovery usually can continue if user allows recovery to corrupt this data block.
ORA-10563: Test recovery had to corrupt data block (file# string, block# string) in order to proceed
Cause: Test recovery completed.
Action: No action is needed. Test recovery has ended successfully. See other messages on error stack for a summary of the result of the test recovery.
ORA-10564: tablespace string
Cause: Report tablespace name for details of another error.
Action: See associated error message.
ORA-10565: Another test recovery session is active
Cause: There can only be one test recovery session at any time. Another test recovery session is active.
Action: Wait till the other test recovery session completes.
ORA-10566: Test recovery has used all the memory it can use
Cause: Test recovery tests redo in memory. It can no longer proceed because it has consumed all the memory it can use.
Action: No action is needed. Test recovery has ended successfully. See other messages on error stack for a summary result of the test recovery.
ORA-10567: Redo is inconsistent with data block (file# string, block# string)
Cause: There are two possible causes of this error: (1) A write issued by Oracle was lost by the underlying OS or storage system. (2) an Oracle internal error.
Action: Investigate why the error occurred and how important is the data block. Media and standby database recovery usually can continue if user allows recovery to corrupt this data block.
ORA-10568: Failed to allocate recovery state object: out of SGA memory
Cause: out of SGA memory
Action: Restart the instance. If problem persists, call Oracle support.
ORA-10570: Test recovery complete
Cause: Test recovery completed.
Action: No action is needed. Test recovery has ended successfully. See other messages on error stack for a summary result of the test recovery.
ORA-10571: Test recovery canceled
Cause: User canceled test recovery.
Action: No action is needed. Test recovery has ended successfully. See other messages on error stack for a summary of the result of the test recovery.
ORA-10572: Test recovery canceled due to errors
Cause: See other errors on the error stack.
Action: is needed. See other messages on error stack for a summary of the result of the test recovery so far.
ORA-10573: Test recovery tested redo from change string to string
Cause: This message show the range of test recovery have tested.
Action: No action is needed. See other messages on error stack.
ORA-10574: Test recovery did not corrupt any data block
Cause: This message summarizes test recovery result.
Action: No action is needed. See other messages on error stack.
ORA-10575: Give up restoring recovered datafiles to consistent state: out of memory
Cause: There were not enough memory to restore recovered datafiles to consistent state
Action: This error is just a warning: You may not be able to open the database with resetlogs immediately after this error. However, you may continue media/standby recovery, and that may make the datafiles recovered consistent again.
ORA-10576: Give up restoring recovered datafiles to consistent state: some error occurred
Cause: See alert file or other errors on the stack for a cause of the problem.
Action: This error is just a warning: You may not be able to open the database with resetlogs immediately after this error. However, you may continue media/standby recovery, and that may make the datafiles recovered consistent again.
ORA-10577: Can not invoke test recovery for managed standby database recovery
Cause: Test recovery option is used for managed standby database recovery.
Action: Either remove the test recovery option or invoke manual test standby database recovery.
ORA-10578: Can not allow corruption for managed standby database recovery
Cause: You used the allow corruption option for managed standby database recovery.
Action: Either remove the allow corruption option or invoke manual standby database recovery.
ORA-10579: Can not modify control file during test recovery
Cause: To proceed with recovery, test recovery needs to modify the control file. But test recovery is not allowed to modify control file.
Action: No action is needed. Test recovery has ended successfully. It can only go so far in the redo stream.
ORA-10580: Can not modify datafile header during test recovery
Cause: To proceed with recovery, test recovery needs to modify a datafile header. But test recovery is not allowed to modify datafile headers.
Action: No action is needed. Test recovery has ended successfully. It can only go so far in the redo stream.
ORA-10581: Can not modify redo log header during test recovery
Cause: To proceed with recovery, test recovery needs to modify a redo log header. But test recovery is not allowed to modify redo log headers.
Action: No action is needed. Test recovery has ended successfully. It can only go so far in the redo stream.
ORA-10582: The control file is not a backup control file
Cause: User requested backup control file test recovery, but the control file is not a backup control file.
Action: Use a backup control file, or do not use USING BACKUP CONTROLFILE option.
ORA-10583: Can not recovery file string renamed as missing during test recovery
Cause: One of the files to be recovered is renamed as missing.
Action: Rename the file to the correct file or offline it.
ORA-10584: Can not invoke parallel recovery for test recovery
Cause: Both test recovery and parallel recovery are requested.
Action: Drop either one of the two recovery options.
ORA-10585: Test recovery can not apply redo that may modify control file
Cause: Test recovery has encountered a special redo that may modify control file.
Action: No action is needed. Test recovery has proceeded successfully as far as it could from its starting point.
ORA-10586: Test recovery had to corrupt 1 data block in order to proceed
Cause: This message summarizes test recovery result: Oracle may have to corrupt one block in order to apply the range of redo tested.
Action: See alert log for details of the problem.
ORA-10587: Invalid count for ALLOW n CORRUPTION option
Cause: The number specified in the ALLOW n CORRUPTION option is too big.
Action: Use a smaller number.
ORA-10588: Can only allow 1 corruption for normal media/standby recovery
Cause: The number specified in the ALLOW n CORRUPTION option is too big.
Action: change to allow zero or one corruption.
ORA-10589: Test recovery had to corrupt string data blocks in order to proceed
Cause: This message summarizes test recovery result: Oracle may have to corrupt a number of data blocks as specified in the message in order to apply the range of redo tested.
Action: See alert log for details of the problems.
ORA-10614: Operation not allowed on this segment
Cause: This procedure can be used only on segments in tablespaces with AUTO SEGMENT SPACE MANAGEMENT
Action: Recheck the segment name and type and re-issue the statement
ORA-10615: Invalid tablespace type for temporary tablespace
Cause: Tablespace with AUTO SEGMENT SPACE MANAGENEMT specified cannot be used as a temporary tablespace
Action: Recheck the tablespace name and re-issue the statement
ORA-10616: Operation not allowed on this tablespace
Cause: Cannot perform the operation on tablespace with AUTO SEGMENT SPACE MANAGEMENT
Action: Recheck the tablespace name and re-issue the statement
ORA-10617: Cannot create rollback segment in dictionary managed tablespace
Cause: Rollback segments cannot be created in dictionary managed tablespaces when SYSTEM tablespace is locally managed
Action: Recheck the tablespace name and re-issue the statement
ORA-10618: Operation not allowed on this segment
Cause: This DBMS_SPACE operation is not permitted on segments in tablespaces with AUTO SEGMENT SPACE MANAGEMENT
Action: Recheck the segment name and type and re-issue the statement
ORA-10619: Avoid assertions when possible
Cause: A bug (or upgrade) hits unicode assertions (csid, csform, bfc)
Action: Event makes RDBMS skip assertions and patch up datastructures
ORA-10620: Operation not allowed on this segment
Cause: Cannot alter freelist storage parameter for segments in tablespaces with AUTO SEGMENT SPACE MANAGEMENT
Action: Recheck the segment name and re-issue the statement
ORA-10627: Dump the content of the index leaf block
Cause: Generate a complete index tree dump, not just an overview during alter session set events immediate trace name treedump
Action: This event is recommended only for small table/index since it
ORA-10628: Turn on sanity check for kdiss index skip scan state
Cause: Will do sanity checking on the kdiss state.
Action: set this event only under the supervision of Oracle development
ORA-10630: Illegal syntax specified with SHRINK clause
Cause: An illegal option was specified with the SHRINK clause
Action: Verify the SQL Reference Manual and reissue the command
ORA-10631: SHRINK clause should not be specified for this object
Cause: It is incorrect to issue shrink on the object
Action: Verify the object name and type and reissue the command
ORA-10632: Invalid rowid
Cause: Segment Highwatermark was overwritten due to shrink and space reused
Action: Reissue this command.
ORA-10633: No space found in the segment
Cause: Raised while trying to find space during segment shrink
Action: This error should be trapped internally and treated. The user should not be able to see the error.
ORA-10634: Segment is already being shrunk
Cause: Only one invocation of shrink can be in progress on a segment at any time
Action: Reissue the command after the first shrink is over
ORA-10635: Invalid segment or tablespace type
Cause: Cannot shrink the segment because it is not in auto segment space managed tablespace or it is not a data, index or lob segment.
Action: Check the tablespace and segment type and reissue the statement
ORA-10636: ROW MOVEMENT is not enabled
Cause: To shrink a data segment, row movement must be enabled.
Action: Enable row movement and reissue this command.
ORA-10637: The segment does not exist
Cause: Segment to be shrunk has been dropped
Action: None
ORA-10638: Index status is invalid
Cause: Cannot shrink an index which is being rebuilt or disabled is an unusable state.
Action: None
ORA-10639: Dump library cache during kksfbc-reparse-infinite-loop error
Cause: During this error a library cache dump is necessary , so enable librarycache dump if event is set.
Action: Dump a library cache if this event is set when reparse error.
ORA-10640: Operation not permitted during SYSTEM tablespace migration
Cause: SYSTEM tablespace is being migrated to locally managed format.
Action: Reissue this command once SYSTEM tablespace migration is over.
ORA-10641: Cannot find a rollback segment to bind to
Cause: SYSTEM tablespace migration requires rollback segment in locally managed tablespace.
Action: Drop rollback segments in dictionary managed tablespaces other than SYSTEM and create rollback segments in locally managed tablespace and retry migration.
ORA-10642: Found rollback segments in dictionary managed tablespaces
Cause: When SYSTEM tablespace is migrated found rollback segments in dictionary managed tablespaces.
Action: Drop the rollback segments in dictionary managed tablespaces and reissue the command
ORA-10643: Database should be mounted in restricted mode and Exclusive mode
Cause: When SYSTEM tablespace is being migrated database should be mounted in Exclusive mode and in Restricted mode.
Action: Reissue this command after mounting the database in right mode.
ORA-10644: SYSTEM tablespace cannot be default temporary tablespace
Cause: When SYSTEM tablespace is being migrated no user should have SYSTEM as the default temporary tablespace.
Action: Reissue this command after altering the default temporary tablespace setting for all users.
ORA-10645: Recursive Extension in SYSTEM tablespace during migration
Cause: When SYSTEM tablespace is being migrated, dictionary tables tried to extend recursively. Must be caught and processed internally. Should not be thrown to the user.
Action: Report the error as a bug.
ORA-10646: Too many recursive extensions during SYSTEM tablespace migration
Cause: When SYSTEM tablespace is being migrated, dictionary tables tried to extend recursively more than 1000 times.
Action: If SYSTEM tablespace is very large, then simply reissue the tablespace migration command.
ORA-10647: Tablespace other than SYSTEM, string, string not found in read only mode
Cause: When SYSTEM tablespace is being migrated, tablespaces other than the three should be ALTERed to read only.
Action: Alter the tablespace status to read only and retry migration.
ORA-10648: Tablespace SYSAUX is not offline
Cause: The SYSAUX tablespace was online while SYSTEM tablespace was being migrated.
Action: Alter the SYSAUX tablespace status to offline and retry migration.
ORA-10649: Turn off/trace lob index freelist coalesce
Cause: Will turn off or trace lob index freelist coalescing
Action: set this event only under the supervision of Oracle development
ORA-10651: incorrect file number block number specified
Cause: The dba specified is not valid
Action: Check if the dba specified belongs to the segment and is under the segment HWM and reissue the statement
ORA-10652: Object has on-commit materialized views
Cause: It is illegal to issue shrink on an object with on-commit materialized views
Action: None
ORA-10653: Table is in a cluster
Cause: It is illegal to shrink a table belonging to a cluster
Action: None
ORA-10654: Table is of type temporary or external
Cause: It is illegal to shrink a temporary table or an external table
Action: None
ORA-10655: Segment can be shrunk
Cause: Error message returned when called in probe mode by OEM
Action: None
ORA-10656: Table is in unusable state due to incomplete operation
Cause: ALTER TABLE SHRINK operation was tried on the table which is in unusable state because of previously failed/incomplete operation.
Action: If the previous operation was
- DROP COLUMN, resubmit DROP COLUMN CONTINUE
- DROP TABLE, resubmit DROP TABLE <table> PURGE
ORA-10657: Lob column to be shrunk does not exist
Cause: Shrink was issued on a lob segment that did not exist
Action: None
ORA-10658: Lob column to be shrunk is marked unused
Cause: Shrink was issued on a lob segment that is marked as unused
Action: None
ORA-10659: Segment being shrunk is not a lob
Cause: Shrink was issued on a segment that should be a first class lob or other data type stored in lob
Action: None
ORA-10660: Segment is a shared lob segment
Cause: Shrink was issued on a segment that was being shared by multiple lob columns
Action: None
ORA-10661: Invalid option specified
Cause: Check option can be specified for one segment only
Action: None
ORA-10662: Segment has long columns
Cause: Shrink was issued on a segment with long columns. This is not supported.
Action: None
ORA-10663: Object has rowid based materialized views
Cause: Shrink was issued on an object with rowid based materialized views.
Action: Drop the rowid based materialized views and issue shrink on the object
ORA-10664: Table has bitmap join indexes
Cause: SHRINK was issued on a table with bitmap join indexes.
Action: Drop bitmap join indexes and reissue SHRINK on the object.
ORA-10665: Inject Evil Literals
Cause: Event 10665 is set to some number > 0, causing 1/(value-1) of all literals to be replaced by 2000 letter 'A's. A value of 1 does not corrupt anything.
Action: never set this event
ORA-10668: Inject Evil Identifiers
Cause: event 10668 is set to some number > 0, causing 1/(value-1) of all identifiers to be replaced by a maximum amount of x's. It is common for an identifier to be parsed once with a max of 30 bytes, then reparsed later with a max of 4000, so it may not be possible to inject such an identifier without the aid of this event. A value of 1 causes no identifiers to be corrupted.
Action: never set this event
ORA-10690: Set shadow process core file dump type (Unix only)
Cause: Control core file size for shadow processes
Action: Level 1: Detach SGA before dumping core Level 2: Do not produce any core
ORA-10691: Set background process core file type (Unix only)
Cause: Control core file size file for background processes
Action: Level 1: Detach SGA before dumping core
ORA-10700: Alter access violation exception handler
Cause: Use this event to control what the VMS exception handler does when it encounters an access violation.
Action: Level: >=10 Suspend current process on access violation *** SET THIS EVENT ONLY UNDER THE SUPERVISION OF ORACLE DEVELOPMENT ***
ORA-10701: Dump direct loader index keys
Cause: Dumps index keys at various points in a direct load based on the value of this event.
Action: None
ORA-10704: Print out information about what enqueues are being obtained
Cause: When enabled, prints out arguments to calls to ksqcmi and ksqlrl and the return values.
Action: Level indicates details: Level: 1-4: print out basic info for ksqlrl, ksqcmi 5-9: also print out stuff in callbacks: ksqlac, ksqlop 10+: also print out time for each line
ORA-10706: Print out information about global enqueue manipulation
Cause: When enabled, prints out activity in ksi routines.
Action: Level indicates details: 0-4: show args for each main call 5-9: also indicate callbacks 10+: also printout time for each line
ORA-10707: Simulate process death for instance registration
Cause: When enabled, process commits suicide to test instance registration recovery code.
Action: Level indicates where the process will die
ORA-10828: memory allocator error
Cause: Error in the memory allocator
Action: Check the trace files and other relevant output
ORA-10841: Default un-inintialized charact set form to SQLCS_IMPLICIT
Cause: client side, such as JDBC-THIN 8i client sends 0 as charset form
Action: This event sets charset form as SQLCS_IMPLICIT when it is 0
ORA-10842: Event for OCI Tracing and Statistics Info
Cause: This event is meant for tracing OCI Calls and getting statistics
Action: This event sets tracing OCI Calls and gets statistics info
ORA-10848: OCI Non Blocking not supported with string
Cause: Attempt made to set connection as non-blocking with another feature that does not support non-blocking.
Action: Use blocking connection.
ORA-10852: Enable tracing for Enqueue Dequeue Operations
Cause: NA
Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE TRANSLATED OR DOCUMENTED. IT IS USED ONLY FOR INTERNAL TESTING.
ORA-10854: Sets poll count used for AQ listen code under RAC
Cause: NA
Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE TRANSLATED OR DOCUMENTED. IT IS USED ONLY FOR INTERNAL TESTING.
ORA-10862: resolve default queue owner to current user in enqueue/dequeue
Cause: resolve default queue owner to current user in enqueue/dequeue.
Action: turn on if client wish to resolve the default queue owner to the current user. If not turned on, the default queue owner will be resolved to the login user.
ORA-10863: Control behavior of buffered background operations
Cause: NA
Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE TRANSLATED OR DOCUMENTED. IT IS USED ONLY FOR INTERNAL TESTING.
ORA-10865: Control tracing of notification operations
Cause: NA
Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE TRANSLATED OR DOCUMENTED. IT IS USED ONLY FOR INTERNAL TESTING.
ORA-10873: file string needs to be either taken out of backup mode or media recovered
Cause: An attempt was made to open a database after an instance failure or SHUTDOWN ABORT interrupted an online backup.
Action: If the indicated file is not a restored backup, then issue the ALTER DATABASE END BACKUP command and open the database. If the file is a restored online backup, then apply media recovery to it and open the database.
ORA-10877: error signaled in parallel recovery slave string
Cause: A parallel recovery slave reached an exception condition.
Action: Check the following error message for the cause, and consult your error manual for the appropriate action.
ORA-10878: parallel recovery slave died unexpectedly
Cause: A parallel recovery slave died unexpectedly, PMON cleaning up the process.
Action: Check your system for anomalies and reissue the statement. If this error persists, contact Oracle Support Services. See trace file for more details.
ORA-10900: extent manager fault insertion event #string
Cause: causes faults to be generated in instrumented extent code
Action: this should only be enabled for internal testing
ORA-10902: disable seghdr conversion for ro operation
Cause: causes seghdr conversion to be turned off for ro ops(#555856)
Action: this should be enabled only if determined that bug 555856 has occured. Table needs to be exported subsequently
No hay comentarios:
Publicar un comentario