Interested to Buy Any Domain ? << Click Here >> for more details...
ORA-00031: session marked for kill
- 1 Answers
- 5316 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-01326: compatability of 9.0 or greater required to build into the logstream
NNL-01055: Requests received: number
PLS-00114: identifier 'string' too long
ORA-09808: Could not obtain user clearance.
ORA-29263: HTTP protocol error
ORA-33284: (DBERR12) Analytic workspace string cannot be opened in MULTI mode before converting it by the latest version of string.
NNL-00901: CONTENT ERROR responses sent: number
PLS-00727: MODIFY LIMIT is supported only on schema-level varray types
CLSS-00001: skgxn not active
ORA-08434: raw data has invalid trailing sign
ORA-00091: LARGE_POOL_SIZE must be at least string
QSM-01090: no query rewrite after view merging
Oracle Errors 
