Interested to Buy Any Domain ? << Click Here >> for more details...
ORA-00031: session marked for kill
- 1 Answers
- 5323 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 |
TNS-01050: %s
ORA-01308: initialization parameter utl_file_dir is not set
ORA-19017: Attributes can only be simple scalars
PCC-02022: Found end of file while scanning a SQL statement
ORA-22303: type "string"."string" not found
ORA-39121: Table string can't be replaced, data will be skipped. Failing error is: string
KUP-04011: file system is full
ORA-24000: invalid value string, string should be of the form [SCHEMA.]NAME
ORA-12626: TNS:bad event type
ORA-24038: RETRY_DELAY and MAX_RETRIES cannot be used for a 8.0 compatible multiple consumer queue
ORA-01303: subordinate process error: number. Check alert and trace logs
ORA-07680: sou2os: another call to ORACLE currently executing
Oracle Errors 
