ORA-00031: session marked for kill
- 1 Answers
- 5450 Views
- I also Faced
- E-Mail Answers
Answer / guest
Cause: The session specified in an ALTER SYSTEM KILL SESSION
command cannot be killed immediately (because it is rolling
back or blocked on a network operation), but it has been
marked for kill. This means it will be killed as soon as
possible after its current uninterruptable operation is done.
Action: No action is required for the session to be killed,
but further executions of the ALTER SYSTEM KILL SESSION
command on this session may cause the session to be killed
sooner.
Please add more information about this Error
| Is This Answer Correct ? | 4 Yes | 2 No |
ORA-16507: unrecognized request identifier
ORA-33284: (DBERR12) Analytic workspace string cannot be opened in MULTI mode before converting it by the latest version of string.
ORA-24163: dblink is not supported in rules engine DDLs
ORA-12914: Cannot migrate tablespace to dictionary managed type
ORA-22340: cannot string type "string"."string". Dependent tables must be upgraded to latest version
DRG-11301: error while indexing document
ORA-14168: only one subpartition may be modified
ORA-32140: cannot peform this operation on stream
AMD-00135: measure #string: RDBMS measure column data type not specified
PCC-02435: This attribute is only valid for internal LOB types
TNS-12151: TNS:received bad packet type from network layer
QSM-01131: query has ONLY_MULTIMV_REWRITE hint
Oracle Errors 
