Interested to Buy Any Domain ? << Click Here >> for more details...
ORA-00031: session marked for kill
- 1 Answers
- 5327 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-00450: background process 'string' did not start
ORA-01865: not a valid era
ORA-31521: CDC subscription string already subscribes to publication ID string column string
ORA-02709: osnpop: pipe creation failed
NNO-00255: cannot initialize ROS
ORA-16206: database already configured as Logical Standby database
ORA-01871: the number of seconds must be less than 60
ORA-30158: The OCIFileWrite causes the file to exceed the maximum allowed size
ORA-23437: template authorization already exists for user
ORA-12090: cannot online redefine table "string"."string"
ORA-02783: Both post and wait functions were not specified
ORA-00261: log string of thread string is being archived or modified
Oracle Errors 
