My Oracle Support Banner

RESOURCE_LIMIT=TRUE And IDLE_TIME Set for Profile But No Sessions Are SNIPED (Doc ID 2048871.1)

Last updated on FEBRUARY 02, 2022

Applies to:

Oracle Database - Enterprise Edition - Version to [Release 12.1]
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Information in this document applies to any platform.


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.




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

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