My Oracle Support Banner

Sessions/Instance Termination When Archive Destination Filled Up (Doc ID 2580032.1)

Last updated on AUGUST 29, 2019

Applies to:

Oracle Database - Enterprise Edition - Version 12.1.0.1 and later
Information in this document applies to any platform.
Sessions & Instance Termination When Archive Destination Filled Up

Symptoms

When the archive destination is full, sessions connected already get killed due to "Reason = dbms_service.kill_session".

Applicable for both CDB and non-CDB environment, below information lists in alert log:

TESTPDB3(3):KILL SESSION for sid=(3063, 3455):
TESTPDB3(3): Reason = dbms_service.kill_session
TESTPDB3(3): Mode = KILL HARD FORCE -/-/-
TESTPDB3(3): Requestor = USER (orapid = 432, ospid = 45234, inst = 1)
TESTPDB3(3): Owner = Process: USER (orapid = 236, ospid = 567454)
TESTPDB3(3): Result = ORA-0
2019-08-20T13:58:44.345345+05:30
TESTPDB4(4):KILL SESSION for sid=(333, 646856):
TESTPDB4(4): Reason = dbms_service.kill_session
TESTPDB4(4): Mode = KILL HARD FORCE -/-/-
TESTPDB4(4): Requestor = USER (orapid = 764, ospid = 785754, inst = 1)
TESTPDB4(4): Owner = Process: USER (orapid = 645, ospid = 895574)
TESTPDB4(4): Result = ORA-0

Changes

Upgrade to 12c from older release.

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.