Interested to Buy Any Domain ? << Click Here >> for more details...
ORA-00031: session marked for kill
- 1 Answers
- 5398 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-30151: File already exists
ORA-37115: New OLAP API history is not allowed
ORA-22611: TDS version is not recognized
TNS-12597: TNS:connect descriptor already in use
ORA-32578: password for SYS already specified
RMAN-08106: channel string: restoring block(s)
ORA-24067: exceeded maximum number of subscribers for queue string
RMAN-03001: recovery manager command sequencer component initialization failed
ORA-14113: partitioned table cannot have column with LOB datatype
ORA-19037: XMLType result can not be a fragment
ORA-02033: a cluster index for this cluster already exists
ORA-38744: file string is not the same file seen at start of flashback
Oracle Errors 
