Small correction:
alter system kill session: *Mode = KILL SOFT -/-/-*
alter system kill session immediate: *Mode = KILL HARD SAFE -/-/-*
alter system disconnect session: *Mode = KILL HARD SAFE DISCONNECT/-/-*
alter system disconnect session immediate:
*Mode = KILL SOFT DISCONNECT/-/-*
On Wed, Aug 28, 2019 at 12:12 AM Sayan Malakshinov <xt.and.r@xxxxxxxxx>
wrote:
Hi Mladen,
THere is a doc about this: New Alert Log Entries In 12.2 Related To
Session Kill: KILL SESSION for sid= (Doc ID 2438653.1)
It can be:
1. *Mode = KILL HARD SAFE -/-/-* - for 'alter system kill session'
2. *Mode = KILL HARD SAFE DISCONNECT/-/-* for alter system disconnect
session
3. *Mode = KILL SOFT* - soft kill by PMON
And unfortunately it still doesn't log 'crash', ie 'oradebug event
immediate crash'
On Tue, Aug 27, 2019 at 11:21 PM Mladen Gogala <gogala.mladen@xxxxxxxxx>
wrote:
Version is Oracle 12.2. I killed a session which had an application
problem and saw the following log in the alert.log:
KILL SESSION for sid=(8, 43679):
Reason = alter system kill session
Mode = KILL HARD SAFE -/-/-
Requestor = USER (orapid = 225, ospid = 23311, inst = 1)
Owner = Process: USER (orapid = 224, ospid = 23257)
Result = ORA-0
What is "KILL HARD SAFE"? What modes are available, what is the meaning
of particular mode and how do I change the modes? That doesn't seem to be
documented anywhere.
--
Best regards,
Sayan Malakshinov
Oracle performance tuning engineer
Oracle ACE Associate
http://orasql.org
