event

Oracle 11.1.0:

Oracle 10.2.0:

Oracle 10.1.0:

Oracle 9.2.0:

Oracle 8.1.7:

Oracle 8.0.6:

Oracle 7.3.4:

Related Error Messages:

Cause: The current session was requested to set a trace event by another session.

Action: This is used internally; no action is required.

ORA-02194: event specification syntax error %s (minor error %s) near '%s'

Cause: There is a syntax error in an event specification.

Action: Fix the error.

ORA-02436: date or system variable wrongly specified in CHECK constraint

Cause: An attempt was made to use a date constant or system variable, such as USER, in a check constraint that was not completely specified in a CREATE TABLE or ALTER TABLE statement. For example, a date was specified without the century.

Action: Completely specify the date constant or system variable. Setting the event 10149 allows constraints like "a1 > '10-MAY-96'", which a bug permitted to be created before version 8.

ORA-02482: Syntax error in event specification (%s)

Cause: Illegal event string

Action: Enter a legal event string

ORA-02779: Stat failed on core dump directory

Cause: The package was unable to get information about the directory into which the servers are to dump core in the event of an exception.

Action: Check the permissions on the directory or use a different directory name.

ORA-02780: Name given for the core dump directory is invalid

Cause: The name given for the directory in which the server processes are to dump core in the event of an exception does not correspond to a directory.

Action: Use a different name.

ORA-04090: '%s' specifies same table, event and trigger time as '%s'

Cause: Trigger is of duplicate event and trigger time.

Action: Combine the triggering information into one trigger which is fired at the given time.

ORA-06441: ssvwatev: Incorrect parameter passed to function call

Cause: Either the ORACLE process id, or wait time or event ID is invalid.

Action: The additional information indicates the process id, time and event id.

ORA-06443: ssvpstev: Incorrect parameter passed to function call

Cause: An invalid event ID is passed in to this routine.

Action: The additional information indicates the event id.

ORA-06445: ssvpstevrg: Incorrect parameters passed to function call

Cause: An invalid event id, or the low and high event ID do not exist.

Action: The additional information indicates the error number. It also contains the event id, low boundary and high boundary.

ORA-06791: TLI Driver: poll returned error event

Cause: TLI received an unexpected event while polling the communication channel for possible incoming messages.

Action: Contact your customer support representative.

ORA-06801: TLI Driver: listen for SPX server reconnect failed

Cause: An unknown event occurred on the client's listening socket.

Action: Contact your customer support representative.

ORA-08105: Oracle event to turn off smon cleanup for online index build

Cause: set this event only under the supervision of Oracle development

Action: debugging only

ORA-09924: Can't spawn process - core dump directory not created properly

Cause: ORACLE was unable to spawn a background process because the directory that holds the core dumps produced by ORACLE processes in the event of exceptions was not created properly.

Action: Examine the directory pointed to by the initialization parameter "core_dump_dest". Make sure that all of the following is true: 1. The directory exists. 2. The name indeed points to a directory, and is not a file. 3. The directory is accessible and writable to the ORACLE user.

ORA-10031: sort debug event (S*)

Cause: ORACLE was unable to spawn a background process because the directory that holds the core dumps produced by ORACLE processes in the event of exceptions was not created properly.

Action: Examine the directory pointed to by the initialization parameter "core_dump_dest". Make sure that all of the following is true: 1. The directory exists. 2. The name indeed points to a directory, and is not a file. 3. The directory is accessible and writable to the ORACLE user.

ORA-10128: Dump Partition Pruning Information

Cause: ORACLE was unable to spawn a background process because the directory that holds the core dumps produced by ORACLE processes in the event of exceptions was not created properly.

Action: Examine the directory pointed to by the initialization parameter "core_dump_dest". Make sure that all of the following is true: 1. The directory exists. 2. The name indeed points to a directory, and is not a file. 3. The directory is accessible and writable to the ORACLE user.

ORA-10132: dump plan after compilation

Cause: ORACLE was unable to spawn a background process because the directory that holds the core dumps produced by ORACLE processes in the event of exceptions was not created properly.

Action: Examine the directory pointed to by the initialization parameter "core_dump_dest". Make sure that all of the following is true: 1. The directory exists. 2. The name indeed points to a directory, and is not a file. 3. The directory is accessible and writable to the ORACLE user.

ORA-10134: dump plan after compilation

Cause: ORACLE was unable to spawn a background process because the directory that holds the core dumps produced by ORACLE processes in the event of exceptions was not created properly.

Action: Examine the directory pointed to by the initialization parameter "core_dump_dest". Make sure that all of the following is true: 1. The directory exists. 2. The name indeed points to a directory, and is not a file. 3. The directory is accessible and writable to the ORACLE user.

ORA-10165: mark session to be aborted during shutdown normal

Cause: ORACLE was unable to spawn a background process because the directory that holds the core dumps produced by ORACLE processes in the event of exceptions was not created properly.

Action: Examine the directory pointed to by the initialization parameter "core_dump_dest". Make sure that all of the following is true: 1. The directory exists. 2. The name indeed points to a directory, and is not a file. 3. The directory is accessible and writable to the ORACLE user.

ORA-10262: Don't check for memory leaks

Cause: ORACLE was unable to spawn a background process because the directory that holds the core dumps produced by ORACLE processes in the event of exceptions was not created properly.

Action: Examine the directory pointed to by the initialization parameter "core_dump_dest". Make sure that all of the following is true: 1. The directory exists. 2. The name indeed points to a directory, and is not a file. 3. The directory is accessible and writable to the ORACLE user.

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

Cause: ORACLE was unable to spawn a background process because the directory that holds the core dumps produced by ORACLE processes in the event of exceptions was not created properly.

Action: Examine the directory pointed to by the initialization parameter "core_dump_dest". Make sure that all of the following is true: 1. The directory exists. 2. The name indeed points to a directory, and is not a file. 3. The directory is accessible and writable to the ORACLE user.

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

Cause: ORACLE was unable to spawn a background process because the directory that holds the core dumps produced by ORACLE processes in the event of exceptions was not created properly.

Action: Examine the directory pointed to by the initialization parameter "core_dump_dest". Make sure that all of the following is true: 1. The directory exists. 2. The name indeed points to a directory, and is not a file. 3. The directory is accessible and writable to the ORACLE user.

ORA-10290: kdnchk - checkvalid event - not for general purpose use.

Cause: ORACLE was unable to spawn a background process because the directory that holds the core dumps produced by ORACLE processes in the event of exceptions was not created properly.

Action: Examine the directory pointed to by the initialization parameter "core_dump_dest". Make sure that all of the following is true: 1. The directory exists. 2. The name indeed points to a directory, and is not a file. 3. The directory is accessible and writable to the ORACLE user.

ORA-10291: die in tbsdrv to test control file undo

Cause: ORACLE was unable to spawn a background process because the directory that holds the core dumps produced by ORACLE processes in the event of exceptions was not created properly.

Action: Examine the directory pointed to by the initialization parameter "core_dump_dest". Make sure that all of the following is true: 1. The directory exists. 2. The name indeed points to a directory, and is not a file. 3. The directory is accessible and writable to the ORACLE user.

ORA-10295: die after file header update durning cf xact

Cause: ORACLE was unable to spawn a background process because the directory that holds the core dumps produced by ORACLE processes in the event of exceptions was not created properly.

Action: Examine the directory pointed to by the initialization parameter "core_dump_dest". Make sure that all of the following is true: 1. The directory exists. 2. The name indeed points to a directory, and is not a file. 3. The directory is accessible and writable to the ORACLE user.

ORA-10296: disable ORA-379

Cause: ORACLE was unable to spawn a background process because the directory that holds the core dumps produced by ORACLE processes in the event of exceptions was not created properly.

Action: Examine the directory pointed to by the initialization parameter "core_dump_dest". Make sure that all of the following is true: 1. The directory exists. 2. The name indeed points to a directory, and is not a file. 3. The directory is accessible and writable to the ORACLE user.

ORA-10297: customize dictionary object number cache

Cause: ORACLE was unable to spawn a background process because the directory that holds the core dumps produced by ORACLE processes in the event of exceptions was not created properly.

Action: Examine the directory pointed to by the initialization parameter "core_dump_dest". Make sure that all of the following is true: 1. The directory exists. 2. The name indeed points to a directory, and is not a file. 3. The directory is accessible and writable to the ORACLE user.

ORA-10298: ksfd i/o tracing

Cause: ORACLE was unable to spawn a background process because the directory that holds the core dumps produced by ORACLE processes in the event of exceptions was not created properly.

Action: Examine the directory pointed to by the initialization parameter "core_dump_dest". Make sure that all of the following is true: 1. The directory exists. 2. The name indeed points to a directory, and is not a file. 3. The directory is accessible and writable to the ORACLE user.

ORA-10299: Trace prefetch tracking decisions made by CKPT

Cause: ORACLE was unable to spawn a background process because the directory that holds the core dumps produced by ORACLE processes in the event of exceptions was not created properly.

Action: Examine the directory pointed to by the initialization parameter "core_dump_dest". Make sure that all of the following is true: 1. The directory exists. 2. The name indeed points to a directory, and is not a file. 3. The directory is accessible and writable to the ORACLE user.

ORA-10309: Trigger Debug event

Cause: ORACLE was unable to spawn a background process because the directory that holds the core dumps produced by ORACLE processes in the event of exceptions was not created properly.

Action: Examine the directory pointed to by the initialization parameter "core_dump_dest". Make sure that all of the following is true: 1. The directory exists. 2. The name indeed points to a directory, and is not a file. 3. The directory is accessible and writable to the ORACLE user.

ORA-10319: Trace PGA statistics maintenance

Cause: ORACLE was unable to spawn a background process because the directory that holds the core dumps produced by ORACLE processes in the event of exceptions was not created properly.

Action: Examine the directory pointed to by the initialization parameter "core_dump_dest". Make sure that all of the following is true: 1. The directory exists. 2. The name indeed points to a directory, and is not a file. 3. The directory is accessible and writable to the ORACLE user.

ORA-10342: Raise unknown exception in ACQ_ADD when checkpointing

Cause: ORACLE was unable to spawn a background process because the directory that holds the core dumps produced by ORACLE processes in the event of exceptions was not created properly.

Action: Examine the directory pointed to by the initialization parameter "core_dump_dest". Make sure that all of the following is true: 1. The directory exists. 2. The name indeed points to a directory, and is not a file. 3. The directory is accessible and writable to the ORACLE user.

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-10370: parallel query server kill event

Cause: internal use only

Action: this event should never be set externally*Comment: commands a slave to commit suicide, codes line

ORA-10371: disable TQ hint

Cause: internal use only

Action: this event should never be set externally*Comment: Stops the generation of the TQ hint (for testing purposes)

ORA-10372: parallel query server kill event proc

Cause: internal use only

Action: this event should never be set externally*Comment: commands a slave to commit suicide, codes proc & weapon

ORA-10373: parallel query server kill event

Cause: internal use only

Action: this event should never be set externally*Comment: commands a slave to commit suicide, code count & context

ORA-10378: force hard process/range affinity

Cause: internal use only

Action: this event should never be set externally*Comment: commands a slave to commit suicide, code count & context

ORA-10380: kxfp latch cleanup testing event

Cause: internal use only

Action: this event should never be set externally*Comment: commands a slave to commit suicide, code count & context

ORA-10381: kxfp latch cleanup testing event

Cause: internal use only

Action: this event should never be set externally*Comment: commands a slave to commit suicide, code count & context

ORA-10382: parallel query server interrupt (reset)

Cause: internal use only

Action: this event should never be set externally*Comment: commands a slave to clear its buffers and reset itself

ORA-10383: auto parallelization testing event

Cause: internal use only

Action: this event should never be set externally*Comment: commands a slave to clear its buffers and reset itself

ORA-10384: parallel dataflow scheduler tracing

Cause: internal use only

Action: this event should never be set externally*Comment: commands a slave to clear its buffers and reset itself

ORA-10385: parallel table scan range sampling method

Cause: internal use only

Action: this event should never be set externally*Comment: commands a slave to clear its buffers and reset itself

ORA-10386: parallel SQL hash and range statistics

Cause: internal use only

Action: this event should never be set externally*Comment: commands a slave to clear its buffers and reset itself

ORA-10387: parallel query server interrupt (normal)

Cause: internal use only

Action: this event should never be set externally*Comment: commands a slave to leave the server group normally

ORA-10388: parallel query server interrupt (failure)

Cause: internal use only

Action: this event should never be set externally*Comment: commands a slave to leave the server group (query failed)

ORA-10389: parallel query server interrupt (cleanup)

Cause: internal use only

Action: this event should never be set externally*Comment: commands a slave to leave the server group (signaled by PMON, coordinator died)

ORA-10390: Trace parallel query slave execution

Cause: internal use only

Action: this event should never be set externally*Comment: commands a slave to leave the server group (signaled by PMON, coordinator died)

ORA-10391: trace PX granule allocation/assignment

Cause: internal use only

Action: this event should never be set externally*Comment: commands a slave to leave the server group (signaled by PMON, coordinator died)

ORA-10392: parallel query debugging bits

Cause: internal use only

Action: this event should never be set externally*Comment: commands a slave to leave the server group (signaled by PMON, coordinator died)

ORA-10393: print parallel query statistics

Cause: internal use only

Action: this event should never be set externally*Comment: commands a slave to leave the server group (signaled by PMON, coordinator died)

ORA-10394: generate a fake load to test adaptive and load balancing

Cause: internal use only

Action: this event should never be set externally*Comment: commands a slave to leave the server group (signaled by PMON, coordinator died)

ORA-10395: adjust sample size for range table queues

Cause: internal use only

Action: this event should never be set externally*Comment: commands a slave to leave the server group (signaled by PMON, coordinator died)

ORA-10397: suppress verbose parallel coordinator error reporting

Cause: internal use only

Action: this event should never be set externally*Comment: commands a slave to leave the server group (signaled by PMON, coordinator died)

ORA-10398: enable timeouts in parallel query threads

Cause: internal use only

Action: this event should never be set externally*Comment: commands a slave to leave the server group (signaled by PMON, coordinator died)

ORA-10399: trace buffer allocation

Cause: internal use only

Action: this event should never be set externally*Comment: commands a slave to leave the server group (signaled by PMON, coordinator died)

ORA-10403: fake CPU number for default degree of parallelism

Cause: internal use only

Action: this event should never be set externally*Comment: commands a slave to leave the server group (signaled by PMON, coordinator died)

ORA-10404: crash dbwr after write

Cause: internal use only

Action: this event should never be set externally*Comment: commands a slave to leave the server group (signaled by PMON, coordinator died)

ORA-10405: emulate broken mirrors

Cause: internal use only

Action: this event should never be set externally*Comment: commands a slave to leave the server group (signaled by PMON, coordinator died)

ORA-10406: enable datetime TIMESTAMP, INTERVAL datatype creation

Cause: internal use only

Action: this event should never be set externally*Comment: commands a slave to leave the server group (signaled by PMON, coordinator died)

ORA-10407: enable datetime TIME datatype creation

Cause: internal use only

Action: this event should never be set externally*Comment: commands a slave to leave the server group (signaled by PMON, coordinator died)

ORA-10408: disable OLAP builtin window function usage

Cause: internal use only

Action: this event should never be set externally*Comment: commands a slave to leave the server group (signaled by PMON, coordinator died)

ORA-10409: enable granule memset and block invalidation at startup

Cause: internal use only

Action: this event should never be set externally*Comment: commands a slave to leave the server group (signaled by PMON, coordinator died)

ORA-10410: trigger simulated communications errors in KSXP

Cause: internal use only

Action: this event should never be set externally*Comment: commands a slave to leave the server group (signaled by PMON, coordinator died)

ORA-10423: dump the call stack if the specified error is cleared

Cause: If an unknown module is clearing an error that you expected to be resignalled, you can use this event to aid your debugging. Whenever that error is cleared the call stack will be dumped to the trace file. This only works for non-OS Oracle errors. Usage: event="10423 trace name context forever, level " Example: event="10423 trace name context forever, level 28" Each time ORA-28 is cleared the stack will be dumped.

Action: Creates a stack dump each time the specified error is cleared.

ORA-10450: signal ctrl-c in kdddca (drop column) after n rows

Cause: If an unknown module is clearing an error that you expected to be resignalled, you can use this event to aid your debugging. Whenever that error is cleared the call stack will be dumped to the trace file. This only works for non-OS Oracle errors. Usage: event="10423 trace name context forever, level " Example: event="10423 trace name context forever, level 28" Each time ORA-28 is cleared the stack will be dumped.

Action: Creates a stack dump each time the specified error is cleared.

ORA-10451: Force heap segment compression bypassing compatibility checks

Cause: If an unknown module is clearing an error that you expected to be resignalled, you can use this event to aid your debugging. Whenever that error is cleared the call stack will be dumped to the trace file. This only works for non-OS Oracle errors. Usage: event="10423 trace name context forever, level " Example: event="10423 trace name context forever, level 28" Each time ORA-28 is cleared the stack will be dumped.

Action: Creates a stack dump each time the specified error is cleared.

ORA-10453: Dump compression statistics to trace file

Cause: If an unknown module is clearing an error that you expected to be resignalled, you can use this event to aid your debugging. Whenever that error is cleared the call stack will be dumped to the trace file. This only works for non-OS Oracle errors. Usage: event="10423 trace name context forever, level " Example: event="10423 trace name context forever, level 28" Each time ORA-28 is cleared the stack will be dumped.

Action: Creates a stack dump each time the specified error is cleared.

ORA-10454: Disable column reordering during compression

Cause: If an unknown module is clearing an error that you expected to be resignalled, you can use this event to aid your debugging. Whenever that error is cleared the call stack will be dumped to the trace file. This only works for non-OS Oracle errors. Usage: event="10423 trace name context forever, level " Example: event="10423 trace name context forever, level 28" Each time ORA-28 is cleared the stack will be dumped.

Action: Creates a stack dump each time the specified error is cleared.

ORA-10462: enable recovery debug module

Cause: If an unknown module is clearing an error that you expected to be resignalled, you can use this event to aid your debugging. Whenever that error is cleared the call stack will be dumped to the trace file. This only works for non-OS Oracle errors. Usage: event="10423 trace name context forever, level " Example: event="10423 trace name context forever, level 28" Each time ORA-28 is cleared the stack will be dumped.

Action: Creates a stack dump each time the specified error is cleared.

ORA-10463: enable controlfile test

Cause: If an unknown module is clearing an error that you expected to be resignalled, you can use this event to aid your debugging. Whenever that error is cleared the call stack will be dumped to the trace file. This only works for non-OS Oracle errors. Usage: event="10423 trace name context forever, level " Example: event="10423 trace name context forever, level 28" Each time ORA-28 is cleared the stack will be dumped.

Action: Creates a stack dump each time the specified error is cleared.

ORA-10464: enable incremental checkpoint debug for split brain check

Cause: If an unknown module is clearing an error that you expected to be resignalled, you can use this event to aid your debugging. Whenever that error is cleared the call stack will be dumped to the trace file. This only works for non-OS Oracle errors. Usage: event="10423 trace name context forever, level " Example: event="10423 trace name context forever, level 28" Each time ORA-28 is cleared the stack will be dumped.

Action: Creates a stack dump each time the specified error is cleared.

ORA-10466: enable HARD check for block write

Cause: If an unknown module is clearing an error that you expected to be resignalled, you can use this event to aid your debugging. Whenever that error is cleared the call stack will be dumped to the trace file. This only works for non-OS Oracle errors. Usage: event="10423 trace name context forever, level " Example: event="10423 trace name context forever, level 28" Each time ORA-28 is cleared the stack will be dumped.

Action: Creates a stack dump each time the specified error is cleared.

ORA-10467: amplify control file record expansion for testing

Cause: If an unknown module is clearing an error that you expected to be resignalled, you can use this event to aid your debugging. Whenever that error is cleared the call stack will be dumped to the trace file. This only works for non-OS Oracle errors. Usage: event="10423 trace name context forever, level " Example: event="10423 trace name context forever, level 28" Each time ORA-28 is cleared the stack will be dumped.

Action: Creates a stack dump each time the specified error is cleared.

ORA-10468: log writer debug module

Cause: If an unknown module is clearing an error that you expected to be resignalled, you can use this event to aid your debugging. Whenever that error is cleared the call stack will be dumped to the trace file. This only works for non-OS Oracle errors. Usage: event="10423 trace name context forever, level " Example: event="10423 trace name context forever, level 28" Each time ORA-28 is cleared the stack will be dumped.

Action: Creates a stack dump each time the specified error is cleared.

ORA-10498: Trim blank characters including contol characters

Cause: If an unknown module is clearing an error that you expected to be resignalled, you can use this event to aid your debugging. Whenever that error is cleared the call stack will be dumped to the trace file. This only works for non-OS Oracle errors. Usage: event="10423 trace name context forever, level " Example: event="10423 trace name context forever, level 28" Each time ORA-28 is cleared the stack will be dumped.

Action: Creates a stack dump each time the specified error is cleared.

ORA-10520: recreate view only if definition has changed

Cause: If an unknown module is clearing an error that you expected to be resignalled, you can use this event to aid your debugging. Whenever that error is cleared the call stack will be dumped to the trace file. This only works for non-OS Oracle errors. Usage: event="10423 trace name context forever, level " Example: event="10423 trace name context forever, level 28" Each time ORA-28 is cleared the stack will be dumped.

Action: Creates a stack dump each time the specified error is cleared.

ORA-10522: turn off wrap source compression

Cause: If an unknown module is clearing an error that you expected to be resignalled, you can use this event to aid your debugging. Whenever that error is cleared the call stack will be dumped to the trace file. This only works for non-OS Oracle errors. Usage: event="10423 trace name context forever, level " Example: event="10423 trace name context forever, level 28" Each time ORA-28 is cleared the stack will be dumped.

Action: Creates a stack dump each time the specified error is cleared.

ORA-10523: force recreate package even if definition is unchanged

Cause: If an unknown module is clearing an error that you expected to be resignalled, you can use this event to aid your debugging. Whenever that error is cleared the call stack will be dumped to the trace file. This only works for non-OS Oracle errors. Usage: event="10423 trace name context forever, level " Example: event="10423 trace name context forever, level 28" Each time ORA-28 is cleared the stack will be dumped.

Action: Creates a stack dump each time the specified error is cleared.

ORA-10550: signal error during create as select/create index after n rows

Cause: If an unknown module is clearing an error that you expected to be resignalled, you can use this event to aid your debugging. Whenever that error is cleared the call stack will be dumped to the trace file. This only works for non-OS Oracle errors. Usage: event="10423 trace name context forever, level " Example: event="10423 trace name context forever, level 28" Each time ORA-28 is cleared the stack will be dumped.

Action: Creates a stack dump each time the specified error is cleared.

ORA-10590: kga (argus debugger) test flags

Cause: If an unknown module is clearing an error that you expected to be resignalled, you can use this event to aid your debugging. Whenever that error is cleared the call stack will be dumped to the trace file. This only works for non-OS Oracle errors. Usage: event="10423 trace name context forever, level " Example: event="10423 trace name context forever, level 28" Each time ORA-28 is cleared the stack will be dumped.

Action: Creates a stack dump each time the specified error is cleared.

ORA-10591: kga (argus debugger) test flags

Cause: If an unknown module is clearing an error that you expected to be resignalled, you can use this event to aid your debugging. Whenever that error is cleared the call stack will be dumped to the trace file. This only works for non-OS Oracle errors. Usage: event="10423 trace name context forever, level " Example: event="10423 trace name context forever, level 28" Each time ORA-28 is cleared the stack will be dumped.

Action: Creates a stack dump each time the specified error is cleared.

ORA-10592: kga (argus debugger) test flags

Cause: If an unknown module is clearing an error that you expected to be resignalled, you can use this event to aid your debugging. Whenever that error is cleared the call stack will be dumped to the trace file. This only works for non-OS Oracle errors. Usage: event="10423 trace name context forever, level " Example: event="10423 trace name context forever, level 28" Each time ORA-28 is cleared the stack will be dumped.

Action: Creates a stack dump each time the specified error is cleared.

ORA-10593: kga (argus debugger) test flags

Cause: If an unknown module is clearing an error that you expected to be resignalled, you can use this event to aid your debugging. Whenever that error is cleared the call stack will be dumped to the trace file. This only works for non-OS Oracle errors. Usage: event="10423 trace name context forever, level " Example: event="10423 trace name context forever, level 28" Each time ORA-28 is cleared the stack will be dumped.

Action: Creates a stack dump each time the specified error is cleared.

ORA-10594: kga (argus debugger) test flags

Cause: If an unknown module is clearing an error that you expected to be resignalled, you can use this event to aid your debugging. Whenever that error is cleared the call stack will be dumped to the trace file. This only works for non-OS Oracle errors. Usage: event="10423 trace name context forever, level " Example: event="10423 trace name context forever, level 28" Each time ORA-28 is cleared the stack will be dumped.

Action: Creates a stack dump each time the specified error is cleared.

ORA-10595: kga (argus debugger) test flags

Cause: If an unknown module is clearing an error that you expected to be resignalled, you can use this event to aid your debugging. Whenever that error is cleared the call stack will be dumped to the trace file. This only works for non-OS Oracle errors. Usage: event="10423 trace name context forever, level " Example: event="10423 trace name context forever, level 28" Each time ORA-28 is cleared the stack will be dumped.

Action: Creates a stack dump each time the specified error is cleared.

ORA-10596: kga (argus debugger) test flags

Cause: If an unknown module is clearing an error that you expected to be resignalled, you can use this event to aid your debugging. Whenever that error is cleared the call stack will be dumped to the trace file. This only works for non-OS Oracle errors. Usage: event="10423 trace name context forever, level " Example: event="10423 trace name context forever, level 28" Each time ORA-28 is cleared the stack will be dumped.

Action: Creates a stack dump each time the specified error is cleared.

ORA-10597: kga (argus debugger) test flags

Cause: If an unknown module is clearing an error that you expected to be resignalled, you can use this event to aid your debugging. Whenever that error is cleared the call stack will be dumped to the trace file. This only works for non-OS Oracle errors. Usage: event="10423 trace name context forever, level " Example: event="10423 trace name context forever, level 28" Each time ORA-28 is cleared the stack will be dumped.

Action: Creates a stack dump each time the specified error is cleared.

ORA-10598: kga (argus debugger) test flags

Cause: If an unknown module is clearing an error that you expected to be resignalled, you can use this event to aid your debugging. Whenever that error is cleared the call stack will be dumped to the trace file. This only works for non-OS Oracle errors. Usage: event="10423 trace name context forever, level " Example: event="10423 trace name context forever, level 28" Each time ORA-28 is cleared the stack will be dumped.

Action: Creates a stack dump each time the specified error is cleared.

ORA-10599: kga (argus debugger) test flags

Cause: If an unknown module is clearing an error that you expected to be resignalled, you can use this event to aid your debugging. Whenever that error is cleared the call stack will be dumped to the trace file. This only works for non-OS Oracle errors. Usage: event="10423 trace name context forever, level " Example: event="10423 trace name context forever, level 28" Each time ORA-28 is cleared the stack will be dumped.

Action: Creates a stack dump each time the specified error is cleared.

ORA-10603: cause an error to occur during truncate (for testing purposes)

Cause: If an unknown module is clearing an error that you expected to be resignalled, you can use this event to aid your debugging. Whenever that error is cleared the call stack will be dumped to the trace file. This only works for non-OS Oracle errors. Usage: event="10423 trace name context forever, level " Example: event="10423 trace name context forever, level 28" Each time ORA-28 is cleared the stack will be dumped.

Action: Creates a stack dump each time the specified error is cleared.

ORA-10604: trace parallel create index

Cause: If an unknown module is clearing an error that you expected to be resignalled, you can use this event to aid your debugging. Whenever that error is cleared the call stack will be dumped to the trace file. This only works for non-OS Oracle errors. Usage: event="10423 trace name context forever, level " Example: event="10423 trace name context forever, level 28" Each time ORA-28 is cleared the stack will be dumped.

Action: Creates a stack dump each time the specified error is cleared.

ORA-10605: enable parallel create index by default

Cause: If an unknown module is clearing an error that you expected to be resignalled, you can use this event to aid your debugging. Whenever that error is cleared the call stack will be dumped to the trace file. This only works for non-OS Oracle errors. Usage: event="10423 trace name context forever, level " Example: event="10423 trace name context forever, level 28" Each time ORA-28 is cleared the stack will be dumped.

Action: Creates a stack dump each time the specified error is cleared.

ORA-10606: trace parallel create index

Cause: If an unknown module is clearing an error that you expected to be resignalled, you can use this event to aid your debugging. Whenever that error is cleared the call stack will be dumped to the trace file. This only works for non-OS Oracle errors. Usage: event="10423 trace name context forever, level " Example: event="10423 trace name context forever, level 28" Each time ORA-28 is cleared the stack will be dumped.

Action: Creates a stack dump each time the specified error is cleared.

ORA-10607: trace index rowid partition scan

Cause: If an unknown module is clearing an error that you expected to be resignalled, you can use this event to aid your debugging. Whenever that error is cleared the call stack will be dumped to the trace file. This only works for non-OS Oracle errors. Usage: event="10423 trace name context forever, level " Example: event="10423 trace name context forever, level 28" Each time ORA-28 is cleared the stack will be dumped.

Action: Creates a stack dump each time the specified error is cleared.

ORA-10608: trace create bitmap index

Cause: If an unknown module is clearing an error that you expected to be resignalled, you can use this event to aid your debugging. Whenever that error is cleared the call stack will be dumped to the trace file. This only works for non-OS Oracle errors. Usage: event="10423 trace name context forever, level " Example: event="10423 trace name context forever, level 28" Each time ORA-28 is cleared the stack will be dumped.

Action: Creates a stack dump each time the specified error is cleared.

ORA-10609: trace for array index insertion

Cause: If an unknown module is clearing an error that you expected to be resignalled, you can use this event to aid your debugging. Whenever that error is cleared the call stack will be dumped to the trace file. This only works for non-OS Oracle errors. Usage: event="10423 trace name context forever, level " Example: event="10423 trace name context forever, level 28" Each time ORA-28 is cleared the stack will be dumped.

Action: Creates a stack dump each time the specified error is cleared.

ORA-10610: trace create index pseudo optimizer

Cause: If an unknown module is clearing an error that you expected to be resignalled, you can use this event to aid your debugging. Whenever that error is cleared the call stack will be dumped to the trace file. This only works for non-OS Oracle errors. Usage: event="10423 trace name context forever, level " Example: event="10423 trace name context forever, level 28" Each time ORA-28 is cleared the stack will be dumped.

Action: Creates a stack dump each time the specified error is cleared.

ORA-10611: causes migration to fail - testing only

Cause: If an unknown module is clearing an error that you expected to be resignalled, you can use this event to aid your debugging. Whenever that error is cleared the call stack will be dumped to the trace file. This only works for non-OS Oracle errors. Usage: event="10423 trace name context forever, level " Example: event="10423 trace name context forever, level 28" Each time ORA-28 is cleared the stack will be dumped.

Action: Creates a stack dump each time the specified error is cleared.

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-10622: test/trace online index (re)build

Cause: A bug (or upgrade) hits unicode assertions (csid, csform, bfc)

Action: Event makes RDBMS skip assertions and patch up datastructures

ORA-10623: Enable Index range scan Prefetch - testing only

Cause: A bug (or upgrade) hits unicode assertions (csid, csform, bfc)

Action: Event makes RDBMS skip assertions and patch up datastructures

ORA-10624: Disable UJV invalidation on drop index

Cause: A bug (or upgrade) hits unicode assertions (csid, csform, bfc)

Action: Event makes RDBMS skip assertions and patch up datastructures

ORA-10625: Turn off redo log dump for the index when OERI 12700

Cause: A bug (or upgrade) hits unicode assertions (csid, csform, bfc)

Action: Event makes RDBMS skip assertions and patch up datastructures

ORA-10626: specify timeout for online index rebuild to wait for DML

Cause: A bug (or upgrade) hits unicode assertions (csid, csform, bfc)

Action: Event makes RDBMS skip assertions and patch up datastructures

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-10629: force online index build to backoff and retry DML lock upgrade

Cause: Will do sanity checking on the kdiss state.

Action: set this event only under the supervision of Oracle development

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-10650: disable cache-callback optimisation

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-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-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-10706: Print out information about global enqueue manipulation

Cause: When enabled, prints out activity in ksi routines.*Action: INternal system parameter (_ksi_trace) can be used in addition to setting this event to limit output information on selected set of global enqueue server enqueue type(s) For example: _ksi_trace = RTXA output information only for RT and XA lock types.//

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-10709: enable parallel instances in create index by default

Cause: When enabled, prints out activity in ksi routines.*Action: INternal system parameter (_ksi_trace) can be used in addition to setting this event to limit output information on selected set of global enqueue server enqueue type(s) For example: _ksi_trace = RTXA output information only for RT and XA lock types.//

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-10710: trace bitmap index access

Cause: When enabled, prints out activity in ksi routines.*Action: INternal system parameter (_ksi_trace) can be used in addition to setting this event to limit output information on selected set of global enqueue server enqueue type(s) For example: _ksi_trace = RTXA output information only for RT and XA lock types.//

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-10711: trace bitmap index merge

Cause: When enabled, prints out activity in ksi routines.*Action: INternal system parameter (_ksi_trace) can be used in addition to setting this event to limit output information on selected set of global enqueue server enqueue type(s) For example: _ksi_trace = RTXA output information only for RT and XA lock types.//

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-10712: trace bitmap index or

Cause: When enabled, prints out activity in ksi routines.*Action: INternal system parameter (_ksi_trace) can be used in addition to setting this event to limit output information on selected set of global enqueue server enqueue type(s) For example: _ksi_trace = RTXA output information only for RT and XA lock types.//

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-10713: trace bitmap index and

Cause: When enabled, prints out activity in ksi routines.*Action: INternal system parameter (_ksi_trace) can be used in addition to setting this event to limit output information on selected set of global enqueue server enqueue type(s) For example: _ksi_trace = RTXA output information only for RT and XA lock types.//

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-10714: trace bitmap index minus

Cause: When enabled, prints out activity in ksi routines.*Action: INternal system parameter (_ksi_trace) can be used in addition to setting this event to limit output information on selected set of global enqueue server enqueue type(s) For example: _ksi_trace = RTXA output information only for RT and XA lock types.//

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-10715: trace bitmap index conversion to rowids

Cause: When enabled, prints out activity in ksi routines.*Action: INternal system parameter (_ksi_trace) can be used in addition to setting this event to limit output information on selected set of global enqueue server enqueue type(s) For example: _ksi_trace = RTXA output information only for RT and XA lock types.//

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-10716: trace bitmap index compress/decompress

Cause: When enabled, prints out activity in ksi routines.*Action: INternal system parameter (_ksi_trace) can be used in addition to setting this event to limit output information on selected set of global enqueue server enqueue type(s) For example: _ksi_trace = RTXA output information only for RT and XA lock types.//

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-10717: trace bitmap index compaction trace for index creation

Cause: When enabled, prints out activity in ksi routines.*Action: INternal system parameter (_ksi_trace) can be used in addition to setting this event to limit output information on selected set of global enqueue server enqueue type(s) For example: _ksi_trace = RTXA output information only for RT and XA lock types.//

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-10718: event to disable automatic compaction after index creation

Cause: When enabled, prints out activity in ksi routines.*Action: INternal system parameter (_ksi_trace) can be used in addition to setting this event to limit output information on selected set of global enqueue server enqueue type(s) For example: _ksi_trace = RTXA output information only for RT and XA lock types.//

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-10719: trace bitmap index dml

Cause: When enabled, prints out activity in ksi routines.*Action: INternal system parameter (_ksi_trace) can be used in addition to setting this event to limit output information on selected set of global enqueue server enqueue type(s) For example: _ksi_trace = RTXA output information only for RT and XA lock types.//

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-10720: trace db scheduling

Cause: When enabled, prints out activity in ksi routines.*Action: INternal system parameter (_ksi_trace) can be used in addition to setting this event to limit output information on selected set of global enqueue server enqueue type(s) For example: _ksi_trace = RTXA output information only for RT and XA lock types.//

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-10722: set parameters for CPU frequency calculation (debug)

Cause: When enabled, prints out activity in ksi routines.*Action: INternal system parameter (_ksi_trace) can be used in addition to setting this event to limit output information on selected set of global enqueue server enqueue type(s) For example: _ksi_trace = RTXA output information only for RT and XA lock types.//

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-10724: trace cross-instance broadcast

Cause: When enabled, prints out activity in ksi routines.*Action: INternal system parameter (_ksi_trace) can be used in addition to setting this event to limit output information on selected set of global enqueue server enqueue type(s) For example: _ksi_trace = RTXA output information only for RT and XA lock types.//

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-10725: bitmap index version control

Cause: When enabled, prints out activity in ksi routines.*Action: INternal system parameter (_ksi_trace) can be used in addition to setting this event to limit output information on selected set of global enqueue server enqueue type(s) For example: _ksi_trace = RTXA output information only for RT and XA lock types.//

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-10726: frequent itemset counting

Cause: When enabled, prints out activity in ksi routines.*Action: INternal system parameter (_ksi_trace) can be used in addition to setting this event to limit output information on selected set of global enqueue server enqueue type(s) For example: _ksi_trace = RTXA output information only for RT and XA lock types.//

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-10731: dump SQL for CURSOR expressions

Cause: When enabled, prints out activity in ksi routines.*Action: INternal system parameter (_ksi_trace) can be used in addition to setting this event to limit output information on selected set of global enqueue server enqueue type(s) For example: _ksi_trace = RTXA output information only for RT and XA lock types.//

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-10732: honor pctfree during insert into AQ IOTs

Cause: When enabled, prints out activity in ksi routines.*Action: INternal system parameter (_ksi_trace) can be used in addition to setting this event to limit output information on selected set of global enqueue server enqueue type(s) For example: _ksi_trace = RTXA output information only for RT and XA lock types.//

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-10733: test transient-IOT metadata during PMO cleanup

Cause: When enabled, prints out activity in ksi routines.*Action: INternal system parameter (_ksi_trace) can be used in addition to setting this event to limit output information on selected set of global enqueue server enqueue type(s) For example: _ksi_trace = RTXA output information only for RT and XA lock types.//

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-10734: reroute external procedures

Cause: When enabled, prints out activity in ksi routines.*Action: INternal system parameter (_ksi_trace) can be used in addition to setting this event to limit output information on selected set of global enqueue server enqueue type(s) For example: _ksi_trace = RTXA output information only for RT and XA lock types.//

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-10735: debug ksws operations

Cause: When enabled, prints out activity in ksi routines.*Action: INternal system parameter (_ksi_trace) can be used in addition to setting this event to limit output information on selected set of global enqueue server enqueue type(s) For example: _ksi_trace = RTXA output information only for RT and XA lock types.//

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-10736: buffer cache pin history dump

Cause: When enabled, prints out activity in ksi routines.*Action: INternal system parameter (_ksi_trace) can be used in addition to setting this event to limit output information on selected set of global enqueue server enqueue type(s) For example: _ksi_trace = RTXA output information only for RT and XA lock types.//

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-10737: test block checking

Cause: When enabled, prints out activity in ksi routines.*Action: INternal system parameter (_ksi_trace) can be used in addition to setting this event to limit output information on selected set of global enqueue server enqueue type(s) For example: _ksi_trace = RTXA output information only for RT and XA lock types.//

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-10738: internal block testing

Cause: When enabled, prints out activity in ksi routines.*Action: INternal system parameter (_ksi_trace) can be used in addition to setting this event to limit output information on selected set of global enqueue server enqueue type(s) For example: _ksi_trace = RTXA output information only for RT and XA lock types.//

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-10740: disables fix for bug 598861

Cause: When enabled, prints out activity in ksi routines.*Action: INternal system parameter (_ksi_trace) can be used in addition to setting this event to limit output information on selected set of global enqueue server enqueue type(s) For example: _ksi_trace = RTXA output information only for RT and XA lock types.//

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-10750: test rollback segment blksize guessing for index array insert

Cause: When enabled, prints out activity in ksi routines.*Action: INternal system parameter (_ksi_trace) can be used in addition to setting this event to limit output information on selected set of global enqueue server enqueue type(s) For example: _ksi_trace = RTXA output information only for RT and XA lock types.//

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-10780: LogMiner API trace event

Cause: When enabled, prints out activity in ksi routines.*Action: INternal system parameter (_ksi_trace) can be used in addition to setting this event to limit output information on selected set of global enqueue server enqueue type(s) For example: _ksi_trace = RTXA output information only for RT and XA lock types.//

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-10781: LogMiner reader trace event

Cause: When enabled, prints out activity in ksi routines.*Action: INternal system parameter (_ksi_trace) can be used in addition to setting this event to limit output information on selected set of global enqueue server enqueue type(s) For example: _ksi_trace = RTXA output information only for RT and XA lock types.//

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-10782: LogMiner preparer trace event

Cause: When enabled, prints out activity in ksi routines.*Action: INternal system parameter (_ksi_trace) can be used in addition to setting this event to limit output information on selected set of global enqueue server enqueue type(s) For example: _ksi_trace = RTXA output information only for RT and XA lock types.//

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-10783: LogMiner builder trace event

Cause: When enabled, prints out activity in ksi routines.*Action: INternal system parameter (_ksi_trace) can be used in addition to setting this event to limit output information on selected set of global enqueue server enqueue type(s) For example: _ksi_trace = RTXA output information only for RT and XA lock types.//

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-10784: LogMiner dictionary trace event

Cause: When enabled, prints out activity in ksi routines.*Action: INternal system parameter (_ksi_trace) can be used in addition to setting this event to limit output information on selected set of global enqueue server enqueue type(s) For example: _ksi_trace = RTXA output information only for RT and XA lock types.//

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-10785: LogMiner trace event

Cause: When enabled, prints out activity in ksi routines.*Action: INternal system parameter (_ksi_trace) can be used in addition to setting this event to limit output information on selected set of global enqueue server enqueue type(s) For example: _ksi_trace = RTXA output information only for RT and XA lock types.//

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-10786: call push/pop (KSU)

Cause: When enabled, prints out activity in ksi routines.*Action: INternal system parameter (_ksi_trace) can be used in addition to setting this event to limit output information on selected set of global enqueue server enqueue type(s) For example: _ksi_trace = RTXA output information only for RT and XA lock types.//

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-10787: trace intra-instance broadcast

Cause: When enabled, prints out activity in ksi routines.*Action: INternal system parameter (_ksi_trace) can be used in addition to setting this event to limit output information on selected set of global enqueue server enqueue type(s) For example: _ksi_trace = RTXA output information only for RT and XA lock types.//

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-10788: trace call stacks

Cause: When enabled, prints out activity in ksi routines.*Action: INternal system parameter (_ksi_trace) can be used in addition to setting this event to limit output information on selected set of global enqueue server enqueue type(s) For example: _ksi_trace = RTXA output information only for RT and XA lock types.//

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-10789: LogMiner test event

Cause: When enabled, prints out activity in ksi routines.*Action: INternal system parameter (_ksi_trace) can be used in addition to setting this event to limit output information on selected set of global enqueue server enqueue type(s) For example: _ksi_trace = RTXA output information only for RT and XA lock types.//

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-10790: LogMiner trace event

Cause: When enabled, prints out activity in ksi routines.*Action: INternal system parameter (_ksi_trace) can be used in addition to setting this event to limit output information on selected set of global enqueue server enqueue type(s) For example: _ksi_trace = RTXA output information only for RT and XA lock types.//

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-10791: Logical Standby swithover/failover trace event

Cause: When enabled, prints out activity in ksi routines.*Action: INternal system parameter (_ksi_trace) can be used in addition to setting this event to limit output information on selected set of global enqueue server enqueue type(s) For example: _ksi_trace = RTXA output information only for RT and XA lock types.//

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-10792: Logical Standby XDAT trace event

Cause: When enabled, prints out activity in ksi routines.*Action: INternal system parameter (_ksi_trace) can be used in addition to setting this event to limit output information on selected set of global enqueue server enqueue type(s) For example: _ksi_trace = RTXA output information only for RT and XA lock types.//

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-10793: Logical Standby trace event

Cause: When enabled, prints out activity in ksi routines.*Action: INternal system parameter (_ksi_trace) can be used in addition to setting this event to limit output information on selected set of global enqueue server enqueue type(s) For example: _ksi_trace = RTXA output information only for RT and XA lock types.//

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-10794: Logical Standby trace event

Cause: When enabled, prints out activity in ksi routines.*Action: INternal system parameter (_ksi_trace) can be used in addition to setting this event to limit output information on selected set of global enqueue server enqueue type(s) For example: _ksi_trace = RTXA output information only for RT and XA lock types.//

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-10808: Enable assert when waiting without a reason

Cause: When enabled, prints out activity in ksi routines.*Action: INternal system parameter (_ksi_trace) can be used in addition to setting this event to limit output information on selected set of global enqueue server enqueue type(s) For example: _ksi_trace = RTXA output information only for RT and XA lock types.//

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-10809: Trace state object allocate / free history

Cause: When enabled, prints out activity in ksi routines.*Action: INternal system parameter (_ksi_trace) can be used in addition to setting this event to limit output information on selected set of global enqueue server enqueue type(s) For example: _ksi_trace = RTXA output information only for RT and XA lock types.//

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-10830: Trace group by sort row source

Cause: When enabled, prints out activity in ksi routines.*Action: INternal system parameter (_ksi_trace) can be used in addition to setting this event to limit output information on selected set of global enqueue server enqueue type(s) For example: _ksi_trace = RTXA output information only for RT and XA lock types.//

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-10831: Trace group by rollup row source

Cause: When enabled, prints out activity in ksi routines.*Action: INternal system parameter (_ksi_trace) can be used in addition to setting this event to limit output information on selected set of global enqueue server enqueue type(s) For example: _ksi_trace = RTXA output information only for RT and XA lock types.//

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-10839: trace / debug caching module (qesca.c)

Cause: When enabled, prints out activity in ksi routines.*Action: INternal system parameter (_ksi_trace) can be used in addition to setting this event to limit output information on selected set of global enqueue server enqueue type(s) For example: _ksi_trace = RTXA output information only for RT and XA lock types.//

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-10840: trace / debug pl/sql caching module (kkxmInitCache)

Cause: When enabled, prints out activity in ksi routines.*Action: INternal system parameter (_ksi_trace) can be used in addition to setting this event to limit output information on selected set of global enqueue server enqueue type(s) For example: _ksi_trace = RTXA output information only for RT and XA lock types.//

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-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-10859: Disable updates of message retry count

Cause: N/A

Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE TRANSLATED OR DOCUMENTED. IT IS USED ONLY FOR DISABLING THE RETRY FEATURE IN THE EVENT THAT IT CAUSES OTHER INTERNAL ERRORS.

ORA-10860: event for AQ admin disable new name parser

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. THIS EVENT IS NOT TO BE TURNED ON BY ANY CUSTOMER. DOING SO, MAY CAUSE AQ DICTIONARY CORRUPTION

ORA-10864: event to enable AQ dedicated propagation

Cause: NA

Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE TRANSLATED OR DOCUMENTED. WHEN THIS EVENT IS SET, ONE JOB QUEUE PROCESS WILL PROPAGATE FOR ONLY ONE PROPAGATION SCHEDULE

ORA-10891: disable column pruning in ANSI join transformation

Cause: N/A

Action: Set this event only under the supervision of Oracle development.*Comment: Not for general purpose use.LEVEL ACTION//--------------------------------------------------------------------------- > 0 Do not attempt to automatically prune away unreferenced columns during ANSI join transformation when compiling SQL queries.

ORA-10912: Used to perform admin operations on locally managed SYSTEM tablespace

Cause: N/A

Action: The event should be used only under the supervision of Oracle Support

ORA-10925: trace name context forever

Cause: N/A

Action: The event should be used only under the supervision of Oracle Support

ORA-10926: trace name context forever

Cause: N/A

Action: The event should be used only under the supervision of Oracle Support

ORA-10927: trace name context forever

Cause: N/A

Action: The event should be used only under the supervision of Oracle Support

ORA-10928: trace name context forever

Cause: N/A

Action: The event should be used only under the supervision of Oracle Support

ORA-10929: trace name context forever

Cause: N/A

Action: The event should be used only under the supervision of Oracle Support

ORA-10930: trace name context forever

Cause: N/A

Action: The event should be used only under the supervision of Oracle Support

ORA-10931: trace name context forever

Cause: N/A

Action: The event should be used only under the supervision of Oracle Support

ORA-10932: trace name context forever

Cause: N/A

Action: The event should be used only under the supervision of Oracle Support

ORA-10933: trace name context forever

Cause: N/A

Action: The event should be used only under the supervision of Oracle Support

ORA-10936: trace name context forever

Cause: N/A

Action: The event should be used only under the supervision of Oracle Support

ORA-10938: trace name context forever

Cause: N/A

Action: The event should be used only under the supervision of Oracle Support

ORA-10939: trace name context forever

Cause: N/A

Action: The event should be used only under the supervision of Oracle Support

ORA-10940: trace name context forever

Cause: N/A

Action: The event should be used only under the supervision of Oracle Support

ORA-10941: trace name context forever

Cause: N/A

Action: The event should be used only under the supervision of Oracle Support

ORA-10943: trace name context forever

Cause: N/A

Action: The event should be used only under the supervision of Oracle Support

ORA-10944: trace name context forever

Cause: N/A

Action: The event should be used only under the supervision of Oracle Support

ORA-10945: trace name context forever

Cause: N/A

Action: The event should be used only under the supervision of Oracle Support

ORA-10946: trace name context forever

Cause: N/A

Action: The event should be used only under the supervision of Oracle Support

ORA-10947: trace name context forever

Cause: N/A

Action: The event should be used only under the supervision of Oracle Support

ORA-10973: backout evet for 2619509

Cause: 2619509 catches offsets when not reading/writing on full character boundary. To facilitate backward compatiblity event is being introduced.

Action: To help upgrade/migrate issues which already have corrupt data

ORA-10977: trace event for RepAPI

Cause: N/A.

Action: Set this event only under the supervision of Oracle development.*Comment: Not for general purpose use.

ORA-10980: prevent sharing of parsed query during Materialized View query generation

Cause: N/A.

Action: Set this event only under the supervision of Oracle development.*Comment: Not for general purpose use.

ORA-10984: subquery materialized view-related event

Cause: N/A

Action: Set this event only under the supervision of Oracle development.*Comment: Not for general purpose use.//--------------------------------------------------------------------------- > 0 A REFRESH FAST subquery MATERIALIZED VIEW which satisfies the pre 8.2 ORACLE server requirements will be treated as a many-many subquery MATERIALIZED VIEW.

ORA-10985: event for NULL refresh of materialized views

Cause: N/A

Action: Set this event only under the supervision of Oracle development.*Comment: Not for general purpose use.

ORA-10986: donot use HASH_AJ in refresh

Cause: N/A

Action: Set this event while doing refresh if the delta snapshot is small*Comment: Not for general purpose use.//--------------------------------------------------------------------------- > 0 Refresh uses NOT EXISTS sub-query instead of HASH_AJ

ORA-10987: event for the support of caching table with object feature

Cause: N/A

Action: Set this event while caching tables with object features.*Comment: Not for general purpose use.//--------------------------------------------------------------------------- > 0 Turn off the checking of object features of a cached table

ORA-10988: event to get exclusive lock during materialized view refresh in IAS

Cause: N/A

Action: Set this event if you want to get exclusive lock on the Updatable MV container table during refresh in IAS*Comment: Not for general purpose use.LEVEL ACTION//--------------------------------------------------------------------------- > 0 Get exclusive lock on the updatable MV container table during refresh in IAS

ORA-10989: event to internally create statistics MV

Cause: N/A

Action: The event is internally used to create statsMV*Comment: Not for general purpose use.LEVEL ACTION//--------------------------------------------------------------------------- > 0

ORA-10990: dump spreadsheet info

Cause: N/A

Action: The event is internally used to create statsMV*Comment: Not for general purpose use.LEVEL ACTION//--------------------------------------------------------------------------- > 0

ORA-10992: event to enable dbms_job instead of dbms_scheduler

Cause: N/A

Action: The event is internally used to create statsMV*Comment: Not for general purpose use.LEVEL ACTION//--------------------------------------------------------------------------- > 0

ORA-10995: general event for materialized views

Cause: N/A

Action: This internal event is used to enable various actions associated with MVs. The event level is interpreted as a bitmap of actions to enable.//*Comment: Not for general purpose use.LEVEL ACTION//---------------------------------------------------------------------------0x0001 enable callback-based refresh0x0002 invalidate dependents for online redef0x0004 allow PCT fast refresh after CONSIDER FRESH

ORA-10998: event to enable short stack dumps in system state dumps

Cause: N/A

Action: enables short stack dumps for every active process in a system state dump*Comment: set this event only under the supervision of Oracle Support

ORA-12099: Don't go into fast table scan (kdst) mode

Cause: N/A

Action: enables short stack dumps for every active process in a system state dump*Comment: set this event only under the supervision of Oracle Support

ORA-12472: policy %s is being used

Cause: The policy which was being dropped due to event propagation from OID was applied to some table or schema.

Action: Drop a policy in OID only if it is not used in any of the databases using the policy.

ORA-12505: TNS:listener does not currently know of SID given in connect descriptor

Cause: The listener received a request to establish a connection to adatabase or other service. The connect descriptor received by the listenerspecified a SID for an instance (usually a database instance) that eitherhas not yet dynamically registered with the listener or has not beenstatically configured for the listener. This may be a temporary conditionsuch as after the listener has started, but before the database instancehas registered with the listener.

Action: - Wait a moment and try to connect a second time. - Check which instances are currently known by the listener by executing: lsnrctl services - Check that the SID parameter in the connect descriptor specifies an instance known by the listener. - Check for an event in the listener.log file.

ORA-12514: TNS:listener does not currently know of service requested in connect descriptor

Cause: The listener received a request to establish a connection to adatabase or other service. The connect descriptor received by the listenerspecified a service name for a service (usually a database service)that either has not yet dynamically registered with the listener or hasnot been statically configured for the listener. This may be a temporarycondition such as after the listener has started, but before the databaseinstance has registered with the listener.

Action: - Wait a moment and try to connect a second time. - Check which services are currently known by the listener by executing: lsnrctl services - Check that the SERVICE_NAME parameter in the connect descriptor of the net service name used specifies a service known by the listener. - If an easy connect naming connect identifier was used, check that the service name specified is a service known by the listener. - Check for an event in the listener.log file.

ORA-12521: TNS:listener does not currently know of instance requested in connect descriptor

Cause: The listener received a request to establish a connection to adatabase or other service. The connect descriptor received by the listenerspecified in addition to the service name an instance name for an instance(usually a database instance) that either has not yet dynamically registeredwith the listener or has not been statically configured for the listener.This may be a temporary condition such as after the listener has started,but before the database instance has registered with the listener.

Action: - Wait a moment and try to connect a second time. - Check which instances are currently known by the listener by executing: lsnrctl services - Check that the INSTANCE_NAME parameter in the connect descriptor specifies an instance name known by the listener. - Check for an event in the listener.log file.

ORA-12591: TNS:event signal failure

Cause: The TNS software is unable to signal an event occurrence.

Action: For further details, turn on tracing and reexecute the operation.If error persists, contact Oracle Customer Support.

ORA-12593: TNS:no registered connection

Cause: An attempt to solicit network event activity has failed becauseno connections are registered for event notification.

Action: Not normally visible to the user. For further details, turnon tracing and reexecute the operation. If error persists, contactOracle Customer Support.

ORA-12615: TNS:preempt error

Cause: A request to service an event failed because no event notificationhas yet been posted.

Action: Not normally visible to the user. For further details, turnon tracing and reexecute the operation. If error persists, contactOracle Customer Support.

ORA-12616: TNS:no event signals

Cause: The TNS software is unable to enable event signals.*Action: Not normally visible to the user. For further details, turnon tracing and reexecute the operation. If error persists, contactOracle Customer Support.*Cause: The operation failed because the type of data specified is unknown.

Action: Not normally visible to the user. For further details, turnon tracing and reexecute the operation. If error persists, contactOracle Customer Support.

ORA-12622: TNS:event notifications are not homogeneous

Cause: An attempt to register a connection for event notification failedbecause the event notification type conflicts with existing registrations.

Action: Not normally visible to the user. For further details, turnon tracing and reexecute the operation and contact Oracle CustomerSupport.

ORA-12624: TNS:connection is already registered

Cause: An attempt to register a connection for event notification failedbecause the connection is already registered.

Action: Not normally visible to the user. For further details, turnon tracing and reexecute the operation and contact Oracle CustomerSupport.

ORA-12626: TNS:bad event type

Cause: An attempt to register a connection for event notification failedbecause the event type is unknown.

Action: Not normally visible to the user. For further details, turnon tracing and reexecute the operation and contact Oracle CustomerSupport.

ORA-12628: TNS:no event callbacks

Cause: An attempt to register a connection for event notification failedbecause asynchronous callbacks are not available.

Action: Not normally visible to the user. For further details, turnon tracing and reexecute the operation and contact Oracle CustomerSupport.

ORA-12629: TNS:no event test

Cause: An attempt to register a connection for event notification failedbecause the ability to test for events is not available.

Action: Not normally visible to the user. For further details, turnon tracing and reexecute the operation and contact Oracle CustomerSupport.

ORA-12801: error signaled in parallel query server %s

Cause: A parallel query server reached an exception condition.

Action: Check the following error message for the cause, and consult your error manual for the appropriate action.*Comment: This error can be turned off with event 10397, in which case the server's actual error is signaled instead.

ORA-12816: parallel create index fastpath operation

Cause: A parallel query server reached an exception condition.

Action: Check the following error message for the cause, and consult your error manual for the appropriate action.*Comment: This error can be turned off with event 10397, in which case the server's actual error is signaled instead.

ORA-13522: event to toggle checking for duplicate sql id (num)

Cause:

Action: Event will determine whether to filter out duplicates for Top SQL selection.

ORA-14244: illegal operation for a System or Composite Range/System partitioned table

Cause: any operation done to a System or Composite Range/System partitioned table is controlled through event 14240

Action: Ensure that the event is turned on

ORA-14526: This event is no longer used.

Cause: any operation done to a System or Composite Range/System partitioned table is controlled through event 14240

Action: Ensure that the event is turned on

ORA-14527: Allow ROWID datatype for partitioning key columns

Cause: any operation done to a System or Composite Range/System partitioned table is controlled through event 14240

Action: Ensure that the event is turned on

ORA-14528: simulated crash during drop table optimization

Cause: Oracle internal testing only

Action: Never set this event (to be used only for internal testing)

ORA-14529: copy hakan factor during ctas at facilitate exchange partition

Cause: Oracle internal testing only

Action: Never set this event unless running into bug 3747472

ORA-15159: Internal testing event

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

Action: Traces execution of rolling upgrade. Level indicates verbosity of tracing.////

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

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

Action: None.//

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: 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-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-16030: session specific change requires a LOG_ARCHIVE_DEST_n destination

Cause: The following event caused an incompatibility: Parameter LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST was in use when an attempt was made to change the LOG_ARCHIVE_MIN_SUCCEED_DEST parameter with an ALTER SESSION command.

Action: Replace any LOG_ARCHIVE_DEST and LOG_ARCHIVE_DUPLEX_DEST parameters with LOG_ARCHIVE_DEST_n (n = 1...10) parameters.

ORA-16054: Event for automatic RFS gap sequence detection

Cause: This is a Oracle internal event code. The condition is posted when the ARC process is about to request the remote RFS to detect gap sequence. The event is used to allow run time disabling of the automatic gap sequence detection. Such run time disable function allows the ORATST to test the other get gap sequence code path: kcrrggs()...etc

Action: N/A, this is a Oracle internal event code

ORA-16106: Event for enabling netslave testing

Cause: This is a Oracle internal event code. It is used to test LGWR or single ARCH sending log files using another netslave process.

Action: N/A, this is a Oracle internal event code

ORA-16111: log mining and apply setting up

Cause: This logical standby process is setting up to begin processing changes.

Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.

ORA-16112: log mining and apply stopping

Cause: This logical standby process is cleaning up and stopping Logical Standby apply.

Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.

ORA-16113: applying change to table or sequence %s

Cause: The process is applying changes to a specific schema object.

Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.

ORA-16114: applying DDL transaction with commit SCN %s

Cause: The process is applying a DDL change that's committed at the given SCN.

Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.

ORA-16115: %s\% of LogMiner dictionary loading is done

Cause: The process is loading dictionary information from the redo stream. This activity may take a few minutes.

Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.

ORA-16116: no work available

Cause: The process is idle waiting for additional changes to be made available.

Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.

ORA-16117: processing

Cause: The process is performing its primary function and is not waiting on any significant event.

Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.

ORA-16119: building transaction at SCN %s

Cause: The transaction being committed at the given SCN is being prepared for apply.

Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.

ORA-16120: dependencies being computed for transaction at SCN %s

Cause: The transaction committed at the given SCN is being analyzed for dependencies.

Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.

ORA-16121: applying transaction with commit SCN %s

Cause: The transaction committed at the given SCN is being applied.

Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.

ORA-16122: applying large dml transaction at SCN %s

Cause: A large transaction is being applied before the commit has been seen. The current redo being applied ends as the given SCN.

Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.

ORA-16123: transaction %s %s %s is waiting for commit approval

Cause: The apply process is waiting for approval to commit a transaction. This transaction may depend on another or other synchronization activity may delay the committing of a transaction.

Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.

ORA-16124: transaction %s %s %s is waiting on another transaction

Cause: The apply process is waiting to apply additional changes. This transaction likely depends on another.

Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.

ORA-16125: large transaction %s %s %s is waiting for more data

Cause: The apply process is waiting until additional changes for a large transaction are retrieved from the log stream.

Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.

ORA-16126: loading table or sequence %s

Cause: Information on the given table or sequence is being loaded into an in memory cache for future use.

Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.

ORA-16127: stalled waiting for additional transactions to be applied

Cause: This process is waiting for additional memory before continuing. Additional log information cannot be read into memory until more transactions have been applied to the database, thus freeing up additional memory.

Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes. If this message occurs often and changes are not being applied quickly, increase available SGA or the number of apply processes.

ORA-16128: User initiated stop apply successfully completed

Cause: Logical standby was shutdown in an orderly fashion.

Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.

ORA-16155: enable arch procs to not exceed log_archive_max_processes

Cause: disallow arch processes to exceed log_archive_max_processes in releases prior to 9i. Note that in 9i and subsequent releases this event is not required. We reserve this event for 9i and subsequent releases to allow us to backport the new log_arch_max_processes behavior for earlier releases.

Action: No action is required.

ORA-16183: Internal event for testing purposes

Cause: This is an internal event used for testing purposes

Action: No action is necessary.

ORA-16189: Internal event for testing RTA purposes

Cause: This is an internal event used for testing purposes

Action: No action is necessary.

ORA-16190: Internal event for RFS Auth testing purposes

Cause: This is an internal event used for testing purposes

Action: No action is necessary.

ORA-16200: Skip procedure requested to skip statement

Cause: Logical standby called a skip procedure that requested for a particular statement not to be applied.

Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.

ORA-16201: Skip procedure requested to apply statement

Cause: Logical standby called a skip procedure that requested for a particular statement to be applied.

Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.

ORA-16202: Skip procedure requested to replace statement

Cause: Logical standby called a skip procedure that requested for a particular statement to be replaced with a new statement.

Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.

ORA-16204: DDL successfully applied

Cause: A DDL statement has successfully commited on the logical standby database.

Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.

ORA-16205: DDL skipped due to skip setting

Cause: A setting in the logical standby skip table indicates that this type of DDL should always be skipped.

Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.

ORA-16222: automatic Logical Standby retry of last action

Cause: A failure occurred while running Logical Standby apply. A new attempt is automatically being made by Logical Standby apply.

Action: No action is necessary. This informational statement is provided to record the event for diagnostic purposes.

ORA-16223: DDL skipped, unsupported in current version

Cause: The given DDL statement was not supported in the current version of Logical Standby and was skipped.

Action: No action is necessary. This informational statement is provided to record the event for diagnostic purposes.

ORA-16227: DDL skipped due to missing object

Cause: A table or other database object upon which this DDL depends is not defined on the Logical Standby database.

Action: No action is necessary, this infomational statement is provided to record the event for diagnostic purposes.

ORA-16230: committing transaction %s %s %s

Cause: Logical Standby apply was committing changes for the given transaction.

Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.

ORA-16231: DDL barrier

Cause: Logical Standby was holding back changes until dependent changes were applied.

Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.

ORA-16234: restarting to reset Logical Standby apply

Cause: Logical Standby encountered a work load that required a restart to properly reschedule.

Action: No action necessary. This informational statement is provided to record the event for diagnostic purposes.

ORA-16235: DDL skipped because import has occurred

Cause: An object was exported from the primary database and imported into the Logical Standby database. This DDL occurred before the export.

Action: No action necessary. This informational statement is provided to record the event for diagnostic purposes.

ORA-16240: Waiting for logfile (thread# %s, sequence# %s)

Cause: Reader process is idle waiting for additional logfile to be available.

Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.

ORA-16241: Waiting for gap logfile (thread# %s, sequence# %s)

Cause: Reader process is idle waiting for the logfile to fill the log sequence gap.

Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.

ORA-16242: Processing logfile (thread# %s, sequence# %s)

Cause: Reader process is processing the logfile.

Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.

ORA-16243: paging out %s bytes of memory to disk

Cause: Builder process is paging out momery to free up space in lcr cache.

Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.

ORA-16244: taking checkpoint and paging out %s bytes to disk

Cause: Builder process is taking a checkpoint to advance restart_scn

Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.

ORA-16245: paging in transaction %s, %s, %s

Cause: Builder process is paging in transactions from disk.

Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.

ORA-16246: User initiated abort apply successfully completed

Cause: SQL Apply was stopped using the abort option.

Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.

ORA-16247: DDL skipped on internal schema

Cause: Logical Standby ignores DDLs on internal schemas such as SYS and SYSTEM. For a complete list of internal schemas ignored by Logical Standby perform the following query: SELECT owner FROM dba_logstdby_skip WHERE statement_opt = 'INTERNAL SCHEMA'.

Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.

ORA-16257: Switchover initiated stop apply successfully completed

Cause: SQL Apply was stopped because of a switchover.

Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.

ORA-16401: archivelog rejected by RFS

Cause: An attempt was made to re-archive an existing archivelog. This usually happens because either a multiple primary database or standby database(s) or both are trying to archive to this standby database.

Action: See alert log and trace file for more details. No action is necessary; this is an informational statement provided to record the event for diagnostic purposes.

ORA-16404: Internal event for simulating software version mismatches

Cause: This is an Oracle internal event code. It is used to test software version mismatches between the primary and a standby database. Setting this event causes the software version number to be incremented by the value of the event level.

Action: N/A, this is a Oracle internal event code

ORA-16405: Internal event for simulating software version mismatches

Cause: This is an Oracle internal event code. It is used to test software version mismatches between the primary and a standby database. Setting this event causes the software version number to be decremented by the value of the event level.

Action: N/A, this is a Oracle internal event code

ORA-16410: enable simulated LGWR netslave infinite wait

Cause: Causes the LGWR to wait indefinitely to simulate network connection indefinite stall.

Action: N/A, this is a Oracle internal event code

ORA-16414: Event to prevent MRP from clearing online redo logfiles

Cause: This is a Oracle internal event code. This event is used to prevent the MRP process from automatically creating and/or clearing the online redo logfiles (ORLs) on a standby database.

Action: N/A, this is a Oracle internal event code

ORA-16415: Event to enable lock dumping

Cause: This is a Oracle internal event code. This event is used to enable dumping of lock structures when desired.

Action: N/A, this is a Oracle internal event code

ORA-16615: event for Data Guard NetSlave testing

Cause: This is an Oracle internal event code. This event is used for verifying NetSlave functionality in Data Guard. DO NOT USE.

Action: N/A, this is an Oracle internal event code.

ORA-16616: event for Data Guard monitor testing

Cause: This is an Oracle internal event code. This event is used for verifying Monitor functionality in Data Guard. DO NOT USE.

Action: N/A, this is an Oracle internal event code.

ORA-16620: one or more databases could not be contacted for a delete operation

Cause: The Data Guard broker could not reach one or more standby databases for either a delete database operation or a delete broker configuration operation.

Action: This typically indicates a network problem where the standby database is unable to respond to the primary database. In the event of this situation, examine the primary database's Data Guard broker log for to determine which standby databases could not be reached. Then for each standby database not reached, connect to that database and shut down the broker by setting the initialization parameter, dg_broker_start, to false. After the broker has been shut down for the standby database, locate the Data Guard broker configuration files from the standby database's dg_broker_config_file[1|2] parameter values and delete them.

ORA-16634: Event for Data Guard NetSlave tracing

Cause: This is an Oracle internal event code. This event is used to control trace output of the Data Guard NetSlave process. DO NOT USE.

Action: N/A, this is an Oracle internal event code.

ORA-16662: event for controlling Data Guard NetSlave network timeout

Cause: This is an Oracle internal event code. This event is used to control the network timeout value used by the Data Guard NetSlave process. DO NOT USE.

Action: N/A, this is an Oracle internal event code.

ORA-16787: event for Data Guard Resource Guard process testing

Cause: This is an Oracle internal event code. This event is used for verifying Resource Guard process functionality. DO NOT USE.

Action: N/A, this is an Oracle internal event code.

ORA-16817: unsynchronized Fast-Start Failover configuration

Cause: The Fast-Start Failover target standby database was not synchronized with the primary database. As a result, a Fast-Start Failover could not happen automatically in case of a primary database failure.

Action: Ensure that the Fast-Start Failover target standby database is running and that the primary database can ship redo logs to it. When the standby database has received all of the redo logs from the primary database, the primary and standby databases will then be synchronized. The Data Guard configuration may then failover automatically to the standby database in the event of loss of the primary database.

ORA-16818: Fast-Start Failover suspended

Cause: The primary database was intentionally shutdown. As a result, a Fast-Start Failover could not happen automatically.

Action: Start up the primary database. This effectively restores the ability to automatically do a Fast-Start Failover in the event of a failure of the primary database.

ORA-17506: I/O Error Simulation

Cause: The i/o request is marked with error because the i/o error simulation event is turned on.

Action:

ORA-17616: Event to disable pupulating V$RMAN_STATUS

Cause: The i/o request is marked with error because the i/o error simulation event is turned on.

Action:

ORA-17617: Event to disable populating V$RMAN_OUTPUT

Cause: The i/o request is marked with error because the i/o error simulation event is turned on.

Action:

ORA-19021: General event for XML operations

Cause: Disables functional evaluation of XML XPath operators on level 1

Action: N/A, this is a Oracle internal event code

ORA-19022: XML XPath functions are disabled

Cause: Event 19021 is enabled, which prevents functional evaluation of Xpath operations

Action: If the XML functional evaluation is disabled. Disable event 19021 to not see this error message

ORA-19027: Event for supressing query rewrite with XML operators

Cause: This event turns off query rewrite for XML operators

Action: N/A, this is a Oracle internal event code

ORA-19119: Event for turning on XMLQuery and XMLTable function

Cause: This event turns on the XMLQuery and XMLTable functions

Action: N/A, this is a Oracle internal event code

ORA-19120: Event for changing behavior of XMLQuery and XMLTable functions

Cause: This event changes the behavior of the XMLQuery and XMLTable functions

Action: N/A, this is a Oracle internal event code

ORA-22700: object access trace event number

Cause: N/A

Action: If the trace event number is set to a level greater than 0 then all the dangling REFs are dumped.*Note: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE TRANSLATED OR DOCUMENTED.

ORA-22829: Event to allow LATERAL views

Cause: N/A

Action: Enables usage of LATERAL views. This event can be removed once this feature is tested and documented.

ORA-24040: AQ tracing event

Cause: N/A

Action: Event used to trace operation of AQ.*Note: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE TRANSLATED OR DOCUMENTED.//

ORA-24910: Event to enable optimized fetch protocol

Cause: N/A

Action: Set this event in your environment to obtain better fetch performance*Note: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE TRANSLATED OR DOCUMENTED.

ORA-24912: Listener thread failed. %s

Cause: Thread listening for event notification exited because of an error. The error encountered is appended to the error message.

Action: The client needs to be restarted.

ORA-24951: EMON tracing event

Cause: N/A

Action: Event used to trace EMON.*Note: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE TRANSLATED OR DOCUMENTED.

ORA-25260: AQ latch cleanup testing event

Cause: N/A.

Action: event used for AQ statistics latch cleanup testing.

ORA-25273: AQ QMN process alternate cleanup event

Cause: N/A.

Action: event used for AQ QMN alternate cleanup mode.

ORA-25274: AQ Buffered Queue event

Cause: N/A.

Action: event used for AQ Buffered Queue mode.

ORA-26531: replication parallel push failure recovery test event

Cause: N/A.

Action: event used to simulate site failure for parallel push testing.

ORA-26532: replication parallel push simulated site failure

Cause: A parallel push executed with event 26531 enabled raises this error to simulation failure of network or destination site.

Action: Do not enable the event for normal operation.

ORA-26703: event for configuring STREAMS rules cache

Cause: Not Applicable

Action: Set this event only under the supervision of Oracle support.

ORA-26707: STREAMS or_expand complexity

Cause: Not Applicable.

Action: Set this event only under the supervision of Oracle Support.

ORA-26728: event for configuring STREAMS apply segcol mapping cache

Cause: Not Applicable

Action: Set this event only under the supervision of Oracle support.

ORA-26729: event for configuring STREAMS apply destination object cache

Cause: Not Applicable

Action: Set this event only under the supervision of Oracle support.

ORA-27373: unknown or illegal event source queue

Cause: The source queue specified for the event based job or event based schedule was either not found or was of the wrong type.

Action: Check if the queue exists. If it does make sure it is a multiple consumer queue and it is a post 8.1 compatible queue. Single consumer queues and old-style queues cannot be used as event source queues.

ORA-27374: insufficient privileges on event source queue

Cause: The job owner had insufficient privileges on the event source queue that was specified for the job.

Action: The job owner has to have dequeue privileges on event source queue or he has to have manage queue or dequeue any queue system privileges. Make sure one of these privileges is granted.

ORA-27375: valid agent name must be specified for secure queues

Cause: The queue specified for the event based job or schedule was a secure queue and either no agent name was specified or an invalid agent name was specified.

Action: If no agent name was specified, retry the call with a valid agent name. If the agent name was valid, check if the agent is currently subscribed to the queue and, in the case of jobs, check is the agent has been authorized to act as the job owner.

ORA-27376: event condition cannot be NULL

Cause: A null event condition was passed in for an event based job or schedule. This is not allowed.

Action: Pass in a legal event condition.

ORA-27377: windows cannot have event based schedules

Cause: Event based schedules for windows are currently not supported.

Action: Use a time-based schedule instead.

ORA-28266: Application Context tracing event

Cause: N/A

Action: Debugging event for KZCTX layer.

ORA-29352: event '%s' is not an internal event

Cause: The DBMS_SYSTEM.WAIT_FOR_EVENT procedure was called with an event name that is not an internal event.

Action: Check the list of events from X$KSLED and verify the event name parameter passed to the WAIT_FOR_EVENT procedure.

ORA-29891: enable debugging in ODCI user-defined routines

Cause: For internal use only

Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE TRANSLATED OR DOCUMENTED. IT IS USED FOR SETTING A NEW EVENT FOR DEBUGGING SUPPORT IN ODCI USER-DEFINED ROUTINES

ORA-30030: suppress resumable related error message

Cause: none

Action: This event is to be used if the errors 30031 and 30032 wish to be suppressed.

ORA-30440: can't fast refresh;refresh complete or set event 30441 for partial refresh

Cause: none

Action: This event is to be used if the errors 30031 and 30032 wish to be suppressed.

ORA-30627: Oracle event to pass temp lobs by ref from sql

Cause:

Action: set this event only under the supervision of Oracle development

ORA-30628: Oracle event to turn off passing temp lobs by ref

Cause:

Action: set this event only under the supervision of Oracle development

ORA-32333: disable table scn update for Materialized view

Cause: an event is set for disabling table scn update to prevent deadlock situation. (bug 1376209)

Action: disable null refresh and/or base table scn update for Materialized view

ORA-32338: on commit refresh grab all the detailed tables

Cause: an event is set to let on-commit MV refresh to grab all the detailed tables, no matter whether they have modified or not.

Action:

ORA-32343: let MVIEW engine know that it is IMPORT from 9i or earlier

Cause: N/A.

Action: Set this event only under the supervision of Oracle development. Not for general purpose use.

ORA-39089: ku trace event

Cause: Explicitly set.

Action: Set this event only under the supervision of Oracle development.*Comment: Turn on/off various ku trace and debug features (documentation in kupp.c and kupp.h).

ORA-41605: schema extended name not allowed: %s

Cause: An attempt was made to specify a schema extended name for an event structure, a rule class, or an action call-back procedure.

Action: Specify the object name with out a schema extension.

ORA-41617: action preference name \"%s\" collides with an event attribute name

Cause: An attempt was made to create an action preference with the same name as an attribute in the event structure.

Action: Choose a different name for action preference and try again.

ORA-41622: invalid primitive event object in rule class properties : %s

Cause: In the rule class properties, the name used for one or the primitive event objects was not found in the corresponding composite event structure.

Action: Correct the name of the primitive event object in the rule class properties and try again.

ORA-41625: event structure %s does not exist

Cause: The object type that represents the event structure was not created in the user's schema.

Action: Create the object type with the event structure's name and try again.

ORA-41627: event structure object type in inconsistent state

Cause: The object type specified for the event structure was in an inconsistent state.

Action: Fix the object type and try again.

ORA-41636: invalid duration specification at the primitive event level

Cause: An attempt was made to specify a duration policy for the primitive events when the composite event was configured with TRANSACTION or SESSION duration policy.

Action: Correct the rule class properties and try again.

ORA-41637: missing primitive event name

Cause: The name attribute of the object element in the rule class properties was not specified. This is a required value.

Action: Specify the name of the primitive event and try again.

ORA-41650: invalid composite event structure

Cause: A composite event structure may only have attributes that are either table aliases or of an object type that is defined in the owner's schema.

Action: Ensure that the event structure has no scalar attributes and all the embedded types in it are defined in the owner's schema.

ORA-41651: Event structure object type has one or more dependent objects

Cause: An attempt was made to configure an object type that has one or more dependents as a event structure. The object type cannot be modified due to the dependent objects.

Action: Create a new object type for the event structure and try again.

ORA-41659: invalid primitive event \"%s\" for the rule class

Cause: An attempt was made to use an invalid primitive event in a rule condition.

Action: Correct the input and try again.

ORA-41662: number of primitive events in the composite event exceeds maximum limit

Cause: An attempt was made to create a composite event structure with more than 32 primitive events.

Action: Use a composite event that consists of fewer primitive events.

ORA-41664: invalid consumption policy for the primitive event

Cause: An attempt was made to use EXCLUSIVE consumption policy for a primitive event when the composite event is configured for RULE consumption policy.

Action: Correct the rule class properties and try again.

ORA-41669: invalid list of primitive event identifiers

Cause: An attempt was made to pass an empty list of primitive event identifiers to the CONSUME_PRIM_EVENTS API.

Action: Correct the input and try again.

ORA-41670: duplicate or invalid event name in equal specification

Cause: An attempt was made to specify a duplicate or invalid primitive event for the rule class's equal property.

Action: Correct the input and try again.

ORA-41671: duplicate table names in the event structure with table aliases

Cause: The table used for an event structure has the same name as another table or a primitive event type in the event structure.

Action: Use an event structure with distinct table names for table aliases.

ORA-41672: invalid rowid passed in for \"%s\" table

Cause: An attempt was made to pass a NULL or invalid rowid for a table in the event structure.

Action: Correct the input and try again.

ORA-41674: dmlevents policy allowed only for event structures with table aliases

Cause: An attempt was made to use the dmlevents policy for an event structure with no table alias constructs.

Action: Correct the rule class properties and try again.

ORA-41675: schema for data tables does not match that of the rule class

Cause: An attempt was made to use the dmlevents policy for a rule class that refers to table residing in different schema. To use the dmlevents policy, the table associated with table aliases in the event structure and the rule class should exist in the same schema.

Action: Remove dmlevents specification from rule class properties.

ORA-41676: invalid use of dmlevents policy for primitive event

Cause: An attempt was made to use the dmlevents policy for a primitive event defined with more than one table alias attribute.

Action: Remove the dmlevents specification from the rule class properties.

ORA-41679: dmlevents specification only allowed with table alias attributes

Cause: An attempt was made to use the dmlevents policy for an event structure not containing any table alias attributes.

Action: Remove the dmlevents specification from the rule class properties.

ORA-41683: unable to lock a rule in the rule class

Cause: A rule matching the current event is locked by another session.

Action: Reissue the command after committing the other sessions. ///////////////////////////////////////////////////////////////////////////// Reserving 42000 - 42249 for Online Redefinition error codes./////////////////////////////////////////////////////////////////////////////

ORA-43901: sampling repeatibility event

Cause: A rule matching the current event is locked by another session.

Action: Reissue the command after committing the other sessions. ///////////////////////////////////////////////////////////////////////////// Reserving 42000 - 42249 for Online Redefinition error codes./////////////////////////////////////////////////////////////////////////////

ORA-43902: qksDestroyServices debugging event

Cause: A rule matching the current event is locked by another session.

Action: Reissue the command after committing the other sessions. ///////////////////////////////////////////////////////////////////////////// Reserving 42000 - 42249 for Online Redefinition error codes./////////////////////////////////////////////////////////////////////////////

This parameter is documented in the Oracle Server Reference Guide. Search for more info about [ event ] on the Oracle FAQ.