ORA-10627: Dump the content of the index leaf block

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 or index since it

ORA-10620: Operation not allowed on this segment

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-10619: Avoid assertions when possible

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-10618: Operation not allowed on this segment

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-10617: Cannot create rollback segment in dictionary managed tablespace

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-10616: Operation not allowed on this tablespace

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-10615: Invalid tablespace type for temporary tablespace

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-10614: Operation not allowed on this segment

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-10589: Test recovery had to corrupt string data blocks in order to proceed

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-10588: Can only allow 1 corruption for normal media or standby recovery

ORA-10588: Can only allow 1 corruption for normal media or standby recovery

Cause: The number specified in the ALLOW n CORRUPTION option is too big.

Action: change to allow zero or one corruption.

ORA-10587: Invalid count for ALLOW n CORRUPTION option

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-10586: Test recovery had to corrupt 1 data block in order to proceed

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-10585: Test recovery can not apply redo that may modify control file

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-10584: Can not invoke parallel recovery for test recovery

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-10583: Can not recovery file string renamed as missing during test recovery

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-10582: The control file is not a backup control file

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-10581: Can not modify redo log header during test recovery

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-10580: Can not modify datafile header during test recovery

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-10579: Can not modify control file during test 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-10578: Can not allow corruption for managed 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-10577: Can not invoke test recovery for managed standby database recovery

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-10576: Give up restoring recovered datafiles to consistent state: some error occurred

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 or standby recovery, and that may make the datafiles recovered consistent again.

ORA-10575: Give up restoring recovered datafiles to consistent state: out of memory

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 or standby recovery, and that may make the datafiles recovered consistent again.

ORA-10574: Test recovery did not corrupt any data block

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-10573: Test recovery tested redo from change string to string

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-10572: Test recovery canceled due to errors

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-10571: Test recovery canceled

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-10570: Test recovery complete

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-10568: Failed to allocate recovery state object: out of SGA memory

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-10567: Redo is inconsistent with data block (file# string, block# string)

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-10566: Test recovery has used all the memory it can use

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-10565: Another test recovery session is active

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-10564: tablespace string

ORA-10564: tablespace string

Cause: Report tablespace name for details of another error.

Action: See associated error message.

ORA-10563: Test recovery had to corrupt data block (file# string, block# string) in order to proceed

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-10562: Error occurred while applying redo to data block (file# string, block# string)

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-10561: block type string , data object# string

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-10560: block type string

ORA-10560: block type string

Cause: Report block type for details of another error.

Action: See associated error message.

ORA-10389: parallel query server interrupt (cleanup)

ORA-10389: parallel query server interrupt (cleanup)

Cause: internal use only

Action: this event should never be set externally

ORA-10388: parallel query server interrupt (failure)

ORA-10388: parallel query server interrupt (failure)

Cause: internal use only

Action: this event should never be set externally

ORA-10387: parallel query server interrupt (normal)

ORA-10387: parallel query server interrupt (normal)

Cause: internal use only

Action: this event should never be set externally

ORA-10382: parallel query server interrupt (reset)

ORA-10382: parallel query server interrupt (reset)

Cause: internal use only

Action: this event should never be set externally

ORA-10373: parallel query server kill event

ORA-10373: parallel query server kill event

Cause: internal use only

Action: this event should never be set externally

ORA-10372: parallel query server kill event proc

ORA-10372: parallel query server kill event proc

Cause: internal use only

Action: this event should never be set externally

ORA-10371: disable TQ hint

ORA-10371: disable TQ hint

Cause: internal use only

Action: this event should never be set externally

ORA-10370: parallel query server kill event

ORA-10370: parallel query server kill event

Cause: internal use only

Action: this event should never be set externally

ORA-10364: Do not clear GIMH_STC_SHUT_BEGIN state during shutdown

ORA-10364: Do not clear GIMH_STC_SHUT_BEGIN state during shutdown

Cause: internal use only

Action: Enables testing of shutdown begin event by not clearing GIMH_STC_ SHUT_BEGIN state before shutdown completes.

ORA-10362: simulate a write error to take a file offline

ORA-10362: simulate a write error to take a file offline

Cause: internal use only

Action: Enables testing of DBWR taking a file offline because of a write error. The level is the absolute file number of the file to be taken offline when DBWR attemts to write to it.

ORA-10361: check buffer change vector count consistency

ORA-10361: check buffer change vector count consistency

Cause: internal use only

Action: invoke buffer change vector count consistency every 5 minutes

ORA-10360: enable dbwr consistency checking

ORA-10360: enable dbwr consistency checking

Cause: internal use only

Action: enables consistency checking of buffers written by dbwriter and consistency checking of LRU working sets

ORA-10284: simulate zero or infinite asynch I or O buffering

ORA-10284: simulate zero or infinite asynch I or O buffering

Cause: Used in KCF, level=1 out of space (red), level=2 infinite (green)

Action: none

ORA-10282: Inhibit signalling of other backgrounds when one dies

ORA-10282: Inhibit signalling of other backgrounds when one dies

Cause: Used in KSB

Action: none

ORA-10281: maximum time to wait for process creation

ORA-10281: maximum time to wait for process creation

Cause: used to override the default SPMXWAIT, level = timeout in sec.

Action: none

ORA-10270: Debug shared cursors

ORA-10270: Debug shared cursors

Cause: Enables debugging code in shared cursor management modules

Action: none

ORA-10269: Don t do coalesces of free space in SMON

ORA-10269: Don t do coalesces of free space in SMON

Cause: setting this event prevents SMON from doing free space coalesces

Action: none

ORA-10268: Don t do forward coalesce when deleting extents

ORA-10268: Don t do forward coalesce when deleting extents

Cause: setting this event keeps kts from coalescing forward at each extent when dropping a temp segment.

Action: none

ORA-10267: Inhibit KSEDMP for testing

ORA-10267: Inhibit KSEDMP for testing

Cause: Some tests may generate internal or fatal errors on purpose.

Action: LEVEL used by KSEDMP is one less than level of this event.

ORA-10266: Trace OSD stack usage

ORA-10266: Trace OSD stack usage

Cause: Porters should implement this to help them debug their stack implementations. It should be used in at least smcstk().

Action: none

ORA-10265: Keep random system generated output out of error messages

ORA-10265: Keep random system generated output out of error messages

Cause: so test system files don t diff

Action: none

ORA-10263: Don t free empty PGA heap extents

ORA-10263: Don t free empty PGA heap extents

Cause: This is useful for debugging since watchpoints are lost on free

Action: none

ORA-10262: Don t check for memory leaks

ORA-10262: Don t check for memory leaks

Cause: Setting this event to level one causes memory leak checking to be disabled. Setting this event to any other non-zero number allows that number to be used as a threshold value when checking for memory leaks in the PGA, SGA, and UGA heaps.

Action: none