After creating a new profile or altering an old one to limit the following profile resources there is no change:
SESSIONS_PER_USER CPU_PER_SESSION CPU_PER_CALL CONNECT_TIME IDLE_TIME LOGICAL_READS_PER_SESSION COMPOSITE_LIMIT PRIVATE_SGA
The resource usage limits are not enforced and the users that are assigned the profile continue to use resources beyond profile’s limits.
The initialization parameter RESOURCE_LIMIT is set to FALSE (default). Set RESOURCE_LIMIT = TRUE in INIT.ORA and restart your database. This ensures that the resource limits will be enforced.
You can also modify this parameter at system level via the following command:
SQL> ALTER SYSTEM SET RESOURCE_LIMIT = TRUE ;
This will only apply for new sessions. The sessions that are already started will not be affected.
It is possible to check the current value of this parameter by running the following query:
SQL> SELECT * FROM V$PARAMETER WHERE NAME = 'resource_limit' ;