![]() If you run: 'orakill ', you may see 'Kill of thread id in instance successfully signalled' the session still exists and you cannot drop the user. If you try to kill the session using a windows command from the cmd line. You should find the spid of this session. You may have tried to use the disconnect command using syntax similar to this: 'alter system disconnect session '123,19162' immediate ' but you get the error: ORA-00031: session marked for kill. 'alter system kill session '123,19162' immediate 'Īs a result of kill session command the status has changed to killed for this session but it still exists and is considered a blocking session. The blocking session was tracked and trying to kill it with the command: There is a blocking session from that user. You executed "drop user" by running the command 'drop user myuser cascade ' as sys but it doesn't work. ![]() Information in this document applies to any platform. Oracle Database Backup Service - Version N/A and later Oracle Cloud Infrastructure - Database Service - Version N/A and later Oracle Database Exadata Cloud Machine - Version N/A and later Oracle Database Cloud Schema Service - Version N/A and later Oracle Database - Enterprise Edition - Version 10.2.0.3 and later Kill A Process - Not able to clear session
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |