RESOURCE_LIMIT=TRUE And IDLE_TIME Set for Profile But No Sessions Are SNIPED

(Doc ID 2048871.1)

Last updated on DECEMBER 01, 2016

Applies to:

Oracle Database - Enterprise Edition - Version and later
Information in this document applies to any platform.
***Checked for relevance on 01-Dec-2016***


Problem Summary
RESOURCE_LIMIT=TRUE and profile with IDLE_TIME=<value> but no sessions are SNIPED

Problem Description
12c container database created with RESOURCE_LIMIT=TRUE
Profile created with IDLE_TIME=<x minutes>.
And this profile is assigned to a user.

Database sessions are never marked as SNIPED in spite of exceeding IDLE_TIME.


Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms