Copy of Oracle FAQ ORACLE RECOVERY without DUL
ORAFAQ HOME | ORAFAQ ASK QUESTION | ORAFAQ ADD INFO | ORAFAQ SEARCH | ORAFAQ E-MAIL
 

Index > ORACLE Server Parameters > event

event


Oracle 10.0.1:

Paramter Name:event
Description:debug event control - default null string
Type:CHAR Obsoleted:FALSE
Can ALTER SESSION:FALSE Can ALTER SYSTEM:FALSE

Oracle 9.2.0:

Paramter Name:event
Description:debug event control - default null string
Type:CHAR Obsoleted:FALSE
Can ALTER SESSION:FALSE Can ALTER SYSTEM:FALSE

Oracle 8.1.7:

Paramter Name:event
Description:debug event control - default null string
Type:CHAR Obsoleted:TRUE
Can ALTER SESSION:FALSE Can ALTER SYSTEM:FALSE

Oracle 8.0.6:

Paramter Name:event
Description:debug event control - default null string
Type:CHAR Obsoleted:FALSE
Can ALTER SESSION:FALSE Can ALTER SYSTEM:FALSE

Oracle 7.3.4:

Paramter Name:event
Description:debug event control - default null string
Type:CHAR Obsoleted:FALSE
Can ALTER SESSION:FALSE Can ALTER SYSTEM:FALSE

Related Error Messages:

ORA-00017: session requested to set trace event
    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-08331: Wait operation timed out

    Cause: Oracle timed out waiting for an event

    Action: Contact your Oracle support representative

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-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-10131: use v$sql_plan code path for explain plan

    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-10133: 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-10198: check undo record

    Cause: for Oracle internal event tracing only

    Action: do NOT set this event for customers' database

ORA-10262: Don't check for memory leaks

    Cause: for Oracle internal event tracing only

    Action: do NOT set this event for customers' database

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

    Cause: for Oracle internal event tracing only

    Action: do NOT set this event for customers' database

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

    Cause: for Oracle internal event tracing only

    Action: do NOT set this event for customers' database

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

    Cause: for Oracle internal event tracing only

    Action: do NOT set this event for customers' database

ORA-10291: die in tbsdrv to test controlfile undo

    Cause: for Oracle internal event tracing only

    Action: do NOT set this event for customers' database

ORA-10294: enable PERSISTENT DLM operations on non-compliant systems

    Cause: for Oracle internal event tracing only

    Action: do NOT set this event for customers' database

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

    Cause: for Oracle internal event tracing only

    Action: do NOT set this event for customers' database

ORA-10296: disable ORA-379

    Cause: for Oracle internal event tracing only

    Action: do NOT set this event for customers' database

ORA-10297: customize dictionary object number cache

    Cause: for Oracle internal event tracing only

    Action: do NOT set this event for customers' database

ORA-10298: ksfd i/o tracing

    Cause: for Oracle internal event tracing only

    Action: do NOT set this event for customers' database

ORA-10299: Trace prefetch tracking decisions made by CKPT

    Cause: for Oracle internal event tracing only

    Action: do NOT set this event for customers' database

ORA-10300: disable undo compatibility check at database open

    Cause: for Oracle internal event tracing only

    Action: do NOT set this event for customers' database

ORA-10309: Trigger Debug event

    Cause: for Oracle internal event tracing only

    Action: do NOT set this event for customers' database

ORA-10319: Trace PGA statistics maintenance

    Cause: for Oracle internal event tracing only

    Action: do NOT set this event for customers' database

ORA-10335: extra check in kck_rls_check

    Cause: for Oracle internal event tracing only

    Action: do NOT set this event for customers' database

ORA-10342: Raise unknown exception in ACQ_ADD when checkpointing

    Cause: for Oracle internal event tracing only

    Action: do NOT set this event for customers' database

ORA-10344: Simulate kghxal returning 0 in ACQ_ADD but no exception

    Cause: for Oracle internal event tracing only

    Action: do NOT set this event for customers' database

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-10374: parallel query server interrupt (validate lock value)

    Cause: internal use only

    Action: this event should never be set externally *Comment: commands a slave to validate its lock value

ORA-10376: turn on table queue statistics

    Cause: internal use only

    Action: this event should never be set externally *Comment: commands a slave to validate its lock value

ORA-10378: force hard process/range affinity

    Cause: internal use only

    Action: this event should never be set externally *Comment: commands a slave to validate its lock value

ORA-10379: direct read for rowid range scans (unimplemented)

    Cause: internal use only

    Action: this event should never be set externally *Comment: commands a slave to validate its lock value

ORA-10380: kxfp latch cleanup testing event

    Cause: internal use only

    Action: this event should never be set externally *Comment: commands a slave to validate its lock value

ORA-10381: kxfp latch cleanup testing event

    Cause: internal use only

    Action: this event should never be set externally *Comment: commands a slave to validate its lock value

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-10396: circumvent range table queues for queries

    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-10411: simulate errors in IMR

    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-10412: trigger simulated errors in CGS/CM interface

    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-10450: signal ctrl-c in kdddca (drop column) after n rows

    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-10451: Force heap segment compression bypassing compatibility checks

    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-10452: Force use of old kdsgrp() - see bug 2442351

    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-10462: enable recovery debug module

    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-10498: Trim blank characters including contol characters

    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-10520: recreate view only if definition has changed

    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-10522: turn off wrap source compression

    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-10523: force recreate package even if definition is unchanged

    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-10550: signal error during create as select/create index after n rows

    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-10590: kga (argus debugger) test flags

    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-10591: kga (argus debugger) test flags

    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-10592: kga (argus debugger) test flags

    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-10593: kga (argus debugger) test flags

    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-10594: kga (argus debugger) test flags

    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-10595: kga (argus debugger) test flags

    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-10596: kga (argus debugger) test flags

    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-10597: kga (argus debugger) test flags

    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-10598: kga (argus debugger) test flags

    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-10599: kga (argus debugger) test flags

    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-10603: cause an error to occur during truncate (for testing purposes)

    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-10604: trace parallel create index

    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-10605: enable parallel create index by default

    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-10606: trace parallel create index

    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-10607: trace index rowid partition scan

    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-10608: trace create bitmap index

    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-10609: trace for array index insertion

    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-10610: trace create index pseudo optimizer

    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-10611: causes migration to fail - testing only

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

    Cause: Will do sanity checking on the kdiss state.

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

ORA-10700: Alter access violation exception handler

    Cause: Will do sanity checking on the kdiss state.

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

ORA-10703: Simulate process death during enqueue get

    Cause: Will do sanity checking on the kdiss state.

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

ORA-10705: Print Out Tracing information for every I/O done by ODSs

    Cause: Will do sanity checking on the kdiss state.

    Action: 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-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-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-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-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-10934: Reserved. Used only in version 7.x.

    Cause: N/A

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

ORA-10935: Reserved. Used only in version 7.x.

    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-10937: 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_schedule instead of dbms_job

    Cause: N/A

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

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

    Cause: N/A

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

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 a database or other service. The connect descriptor received by the listener specified a SID for an instance (usually a database instance) that either has not yet dynamically registered with 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 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 a database or other service. The connect descriptor received by the listener specified a service name for a service (usually a database service) that either has not yet dynamically registered with 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 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 a database or other service. The connect descriptor received by the listener specified in addition to the service name an instance name for an instance (usually a database instance) that either has not yet dynamically registered with 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 because no connections are registered for event notification.

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

ORA-12615: TNS:preempt error

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

    Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle 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, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support. *Cause: The operation failed because the type of data specified is unknown.

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

ORA-12622: TNS:event notifications are not homogeneous

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

    Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation and contact Oracle Customer Support.

ORA-12624: TNS:connection is already registered

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

    Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation and contact Oracle Customer Support.

ORA-12626: TNS:bad event type

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

    Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation and contact Oracle Customer Support.

ORA-12628: TNS:no event callbacks

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

    Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation and contact Oracle Customer Support.

ORA-12629: TNS:no event test

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

    Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation and contact Oracle Customer Support.

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.


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

ORAFAQ HOME | ORAFAQ ASK QUESTION | ORAFAQ ADD FAQ | ORAFAQ SEARCH | ORAFAQ E-MAIL
All content of this page is copy from www.orafaq.com