Database Administration (MOSC)

MOSC Banner

On 12C R2 kill session J000 in alertlog file

edited Aug 7, 2020 3:34PM in Database Administration (MOSC) 12 commentsAnswered

Hi all,

On our servers 12c release 2 in the alertlog file, I can see many of these traces:

KILL SESSION for sid=(x, y):

  Reason = alter system disconnect session

  Mode = KILL HARD SAFE DISCONNECT/-/-

  Requestor = J000 (orapid = Z, ospid = w, inst = 1)

  Owner = Process: USER (orapid = v, ospid = u)

  Result = ORA-0

Since the requestor is J000 (Job queu slave process), is it normal to have these traces?

I assume that these killed session wrere sessions related to jobs on the database server. Can these killed session also be gost sessions killed by Oracle?

Best regards.

Carl

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center