LOGICAL_READS_PER_CALL (profile)

I am trying to limit a user from heavy database usage.
The user will just be querying a single table for 1 row at a time.
What is a good value to set LOGICAL_READS_PER_CALL to? my DB is 8K block size.
I am also thinking of setting this too: CPU_PER_CALL
What is a good ms time for it?
(ALTER PROFILE developer LIMIT cpu_per_call 3000;)

Hi user;
Please see below notes which could be helpful for your issue
How To Calculate The Blocks Used In A Query To Configure LOGICAL_READS_PER_CALL [ID 872133.1]
Profile Resource Parameters [ID 1153989.1]
Also see:
How To Use PROFILES To Limit User Resources [ID 1016552.102]
Script to list profile resources and limits [ID 1019933.6]
Regard
Helios

Similar Messages

ORA-02394: exceeded session limit on IO usage

I have one sql took much time to run and got this..
ORA-02394: exceeded session limit on IO usage, you are being logged of
when I checked profile options
SQL> select PROFILE,RESOURCE_NAME,LIMIT from dba_profiles where RESOURCE_NAME='LOGICAL_READS_PER_SESSION';
PROFILE RESOURCE_NAME
LIMIT
DEFAULT LOGICAL_READS_PER_SESSION
UNLIMITED
SQL> select PROFILE,RESOURCE_NAME,LIMIT from dba_profiles where RESOURCE_NAME='LOGICAL_READS_PER_CALL';
PROFILE RESOURCE_NAME
LIMIT
DEFAULT LOGICAL_READS_PER_CALL
UNLIMITED
Is there anything we can do here bcaz both profiles have been set to unlimted?

Hello,
Oracle 8.1.7.4 is the final patchset of the last release for Oracle 8i, so it's a rather
stable version.
Do you have a way to tune this query so that it can run faster ?
Do you have correct statistics on the optimizer ?
Best regards,
Jean-Valentin

Does the Resource Profile LOGICAL_READS_PER_CALL count TEMP

Does anyone know if the profile resource LOCIAL_READS_PER_CALL counts reads from the TEMP/SORT segment.
The reason I'm asking is because we had an adhoc report user write a query that caused a huge cartiesian product that consumed all of the temp tablespace, 8.5G. The knee-jerk reaction would be to add more space to the TEMP tablespace, but the poorly written query was the problem. The user running the query does have a profile that restricts the LOGICAL_READS_PER_CALL to 3500000. The query did fail since it could not allocate any space from the TEMP tablespace, but not before it caused two other sessions to fail for the same reason. The query had several sort/merge operations so I was hoping that when it was reading back from a temp segment it would be added to the counter and would then terminate the session.
If this counter is not used for TEMP reads does anyone know of another way to limit the amount of temp space for a particular user?

Logical read concerns the block read into the buffer no ? So I don't see relation with the tablespace TEMP.

Profiles: Setting CPU_PER_CALL & LOGICAL_READS_PER_CALL

Hello, I just enabled profiles on 10g, and set some basic limitations (idle_time, connect_time, etc.)
However my main target is to set cpu_per_call & logical_reads_per_call.
Is there a way to monitor queries of a specific user for i.e. a week in order to come up with a max threshold for cpu and IO so I can further set this as a limitation through profiles?
Thank you in advance !

In my opinion CPU_PER_CALL and LOGICAL_READS_PER_CALL would be tough to manage. It may be more appropriate to look into Resource Manager. I think that provides better control over resources.
If you do still want to specify CPU_PER_CALL and LOGICAL_READS_PER_CALL you'll need to gather statistical data on the users. One way to do that would be to setup LOGON / LOGOFF triggers to take snapshots of the session based statistics. Another option may be to look into AWR / STATSPACK or other performance monitoring tools.

Password expire date back to 2011 from 2012 after assigned a user profile

Friends,
I created a profile test as
COMPOSITE_LIMIT UNLIMITED
SESSIONS_PER_USER UNLIMITED
CPU_PER_SESSION UNLIMITED
CPU_PER_CALL UNLIMITED
LOGICAL_READS_PER_SESSION UNLIMITED
LOGICAL_READS_PER_CALL UNLIMITED
IDLE_TIME 60
CONNECT_TIME UNLIMITED
PRIVATE_SGA UNLIMITED
FAILED_LOGIN_ATTEMPTS 5
PASSWORD_LIFE_TIME 120
PASSWORD_REUSE_TIME 60
PASSWORD_REUSE_MAX 30
PASSWORD_VERIFY_FUNCTION NULL
PASSWORD_LOCK_TIME 1
PASSWORD_GRACE_TIME 7;
the user default profile default PASSWORD_LIFE_TIME is 180 and password expired date is 1/7/2012. the test account was created in 7/11/2011.
Now I assign test user to test profile successfully.
However. expire date becomes 11/8/2011 1 from 1/7/2012 by select dba_users
which wrong is in my profile or somewhere?
As I think, the account password expired should be start after assigned new profile with PASSWORD_LIFE_TIME. but is seems expire date is start from original account created date.
Thanks
newdba
Edited by: Oradb on May 24, 2012 1:56 PM

I would think the expire time would be based on the last password change time which Oracle stores in the rdbms base table for user information (user$). Find a second user, alter the password, check the expire date, then assign the user to the new profile, re-check the expiration date. Post back. Behavior may vary between releases so include full Oracle version of test.
HTH -- Mark D Powell --

Incorrect user profile setting after database import

We migrateed the production databsae from Solaris running 10.2.0.3 to OEL running 10.2.0.5. The method we used is exp/imp and it seem everything fine. However, it found that some of the user profile (ie. IDLE TIME, ) limit is not the the same as the old database. It seem the user profile is not migrated successfully.
Exp.par
cat expPRODN_normal.par
full=y
direct=y
buffer=409600000
feedback=100000
compress=y
statistics=none
consistent=n
log=/db/oracle/exp_for_linux/expPRODN_full.log
filesize=2000mb
file=/db/oracle/exp_for_linux/1
imp.par
cat imp_PRD.par
full=y
buffer=409600000
statistics=none
log=/db/oracle/lyn/imp_PRD.log
file=/import/PRODN/1
In old database:
SYS@PRODN1>select resource_name, limit from dba_profiles where profile='DEFAULT' order by resource_name;
RESOURCE_NAME LIMIT
COMPOSITE_LIMIT UNLIMITED
CONNECT_TIME UNLIMITED
CPU_PER_CALL UNLIMITED
CPU_PER_SESSION UNLIMITED
FAILED_LOGIN_ATTEMPTS 5
IDLE_TIME 60
LOGICAL_READS_PER_CALL UNLIMITED
LOGICAL_READS_PER_SESSION UNLIMITED
PASSWORD_GRACE_TIME UNLIMITED
PASSWORD_LIFE_TIME UNLIMITED
PASSWORD_LOCK_TIME UNLIMITED
RESOURCE_NAME LIMIT
PASSWORD_REUSE_MAX UNLIMITED
PASSWORD_REUSE_TIME UNLIMITED
PASSWORD_VERIFY_FUNCTION NULL
PRIVATE_SGA UNLIMITED
SESSIONS_PER_USER 3
16 rows selected.
SYS@PRODN1>
In new database:
sys@SPRD1> select resource_name, limit from dba_profiles where profile='DEFAULT' order by resource_name;
RESOURCE_NAME LIMIT
COMPOSITE_LIMIT UNLIMITED
CONNECT_TIME UNLIMITED
CPU_PER_CALL UNLIMITED
CPU_PER_SESSION UNLIMITED
FAILED_LOGIN_ATTEMPTS 10
IDLE_TIME 60
LOGICAL_READS_PER_CALL UNLIMITED
LOGICAL_READS_PER_SESSION UNLIMITED
PASSWORD_GRACE_TIME UNLIMITED
PASSWORD_LIFE_TIME UNLIMITED
PASSWORD_LOCK_TIME UNLIMITED
RESOURCE_NAME LIMIT
PASSWORD_REUSE_MAX UNLIMITED
PASSWORD_REUSE_TIME UNLIMITED
PASSWORD_VERIFY_FUNCTION NULL
PRIVATE_SGA UNLIMITED
SESSIONS_PER_USER UNLIMITED
16 rows selected.
sys@OIMSPRD1>
You can see limit value of FAILED_LOGIN_ATTEMPTS, IDLE_TIME and SESSIONS_PER_USER are different.

It is not a user profile, but the default one which already exist by default in the database and not overwritten when importing.
By the way, IDLE_TIME is same on both sides.
Nicolas.

Oracle Profiles

dear all
i am creating a profile and using some resource parameter
my resource_limit parameter is true....
SQL> show parameter resource;
NAME TYPE VALUE
resource_limit boolean TRUE
resource_manager_plan string INTERNAL_PLAN
SQL> CREATE PROFILE poweruser LIMIT
2 SESSIONS_PER_USER UNLIMITED,
3 CPU_PER_SESSION UNLIMITED ,
4 CPU_PER_CALL 30000,
5 CONNECT_TIME 60,
6 LOGICAL_READS_PER_SESSION UNLIMITED,
7 LOGICAL_READS_PER_CALL 1000,
8 COMPOSITE_LIMIT 5000000;
SESSIONS_PER_USER UNLIMITED,
ERROR at line 2:
ORA-02376: invalid or redundant resource
help me
CHeers

dear all
we have 3 profiles A B C
users logged in will be under this profile .... OK ..
Now we have a plan of resource management in which
A Profile will be using 60% CPU
B Profile will be using 20% CPU
C Profile will be using 20% CPU
PLAN name is PROJECT_PLAN
now we want to use this plan in our database but there are other profiles also in DATABASE ,.....
if we alter resource_manager_plan which is a initialization parmeter then it would be like this plan will be used by whole DB ...
we dont want to do that....we want only these 3 profiles should come under this plan of resource management....
Needed Guidance is this
CHeers

Session geting disconnected before IDLE_TIME in profile

Hi !
My database is :
SQL> select * from v$version;
BANNER
Oracle9i Enterprise Edition Release 9.2.0.4.0 - Production
PL/SQL Release 9.2.0.4.0 - Production
CORE 9.2.0.3.0 Production
TNS for Linux: Version 9.2.0.4.0 - Production
NLSRTL Version 9.2.0.4.0 - Production
on os :
SQL> !uname -a
Linux abc-dc 2.4.21-50.ELsmp #1 SMP Tue May 8 17:18:29 EDT 2007 i686 i686 i386 GNU/Linux
I have created a profile Kill_session and set idle_time as 30 minutes(I think the unit for this value is min).
and the profile has been given to the a user genweb. Now when I log in with genweb the session getting disconnected very frequently....not even staying 3 min. inactive.
Its showing :
ORA-02396: exceeded maximum idle time, please connect again
But if I assign default profile to the user genweb in which idle_time is unlimited the session is not getting disconnected.
The ping response is strong. Issue is happening in both the case, if I connect via listener or connect logging in the server.
Also :
sho parameter resource
NAME TYPE VALUE
enqueue_resources integer 1692
resource_limit boolean TRUE
resource_manager_plan string
SQL> select * from dba_profiles where profile='KILL_SESSION';
PROFILE RESOURCE_NAME RESOURCE LIMIT
KILL_SESSION COMPOSITE_LIMIT KERNEL DEFAULT
KILL_SESSION SESSIONS_PER_USER KERNEL DEFAULT
KILL_SESSION CPU_PER_SESSION KERNEL DEFAULT
KILL_SESSION CPU_PER_CALL KERNEL DEFAULT
KILL_SESSION LOGICAL_READS_PER_SESSION KERNEL DEFAULT
KILL_SESSION LOGICAL_READS_PER_CALL KERNEL DEFAULT
KILL_SESSION IDLE_TIME KERNEL 30
KILL_SESSION CONNECT_TIME KERNEL DEFAULT
KILL_SESSION PRIVATE_SGA KERNEL DEFAULT
KILL_SESSION FAILED_LOGIN_ATTEMPTS PASSWORD DEFAULT
KILL_SESSION PASSWORD_LIFE_TIME PASSWORD DEFAULT
KILL_SESSION PASSWORD_REUSE_TIME PASSWORD DEFAULT
KILL_SESSION PASSWORD_REUSE_MAX PASSWORD DEFAULT
KILL_SESSION PASSWORD_VERIFY_FUNCTION PASSWORD DEFAULT
KILL_SESSION PASSWORD_LOCK_TIME PASSWORD DEFAULT
KILL_SESSION PASSWORD_GRACE_TIME PASSWORD DEFAULT
SQL> select profile from dba_users where username ='GENWEB';
PROFILE
KILL_SESSION
I had to change the profile for the user to default.
Sorry for posting all this long output. Pls. help me ....
Am I missing something here?
Edited by: gc on Jan 21, 2011 2:11 AM

SQL> create profile KILL_SESSION2 limit idle_time 30;
Profile created.
SQL> ALTER USER GENWEB PROFILE KILL_SESSION2;
User altered.
But same result.
Connecting through plsql developer from a client pc. also login to server using putty and then sqlplue in both case sessions are disconnected in seconds.
sho parameter resource_limit
NAME TYPE VALUE
resource_limit boolean TRUE

CPU limits in profile

Hi all,
11.2.0.1
aix 6.1
We have a new app to be implemented in our existing PROD db. Since this is not so priority app we want to control/limit is CPU usage so not to affect the critical app (priority) that is currently running in our PROD dataabase.
I am creating this profile for this new app.
CREATE PROFILE app_new LIMIT
   SESSIONS_PER_USER          UNLIMITED
   CPU_PER_SESSION            3000
   CPU_PER_CALL               3000
   CONNECT_TIME               45
   LOGICAL_READS_PER_SESSION DEFAULT
   LOGICAL_READS_PER_CALL     1000
   PRIVATE_SGA                15K
   COMPOSITE_LIMIT            5000000;
I am only concern with CPU and Memory, so the parameter I am concerned with is CPU_PER_SESSION, CPU_PER_CALL, and PRIVATE_SGA.
My question is, what is the good low limit value for these parameters?
CPU_PER_SESSION Specify the CPU time limit for a session, expressed in hundredth of seconds.
CPU_PER_CALL Specify the CPU time limit for a call (a parse, execute, or fetch), expressed in hundredths of seconds.
What happens if my cpu_per_session & cpu_per_call reaches 3000? will it abort the process?
Thanks a lot,
zxy

>Maybe you can give me basic safe commands just to allot 20% cpu to user HR.
And safe command is :
BEGIN
DBMS_RESOURCE_MANAGER.CREATE_SIMPLE_PLAN(SIMPLE_PLAN => 'SIMPLE_PLAN1',
CONSUMER_GROUP1 => 'MYGROUP1', GROUP1_PERCENT => 80,
CONSUMER_GROUP2 => 'MYGROUP2', GROUP2_PERCENT => 20);
END;
Source:Creating a Simple Resource Plan
But a complete study of Resource plan manager need to be well understand and that is free, easy to understand by docs :
Managing Resources with Oracle Database Resource Manager
Just start reading above link and navigate by clicking on next page link. Trust me, only this is the valid and safe way to learn the things.
Regards
Girish Sharma

Restricting session through PROFILE

Hi
I created a user and pinned him to a profile which ideally shouldn't allow him to create parallel sessions.
First I created the profile.
CREATE PROFILE ext_user_prof LIMIT
SESSIONS_PER_USER 1 ---- Cann't create parallel sessions.
CPU_PER_SESSION UNLIMITED ---- Unlimited CPU Time.
CPU_PER_CALL 3000 ---- Single call limited the call for 30 secs.
CONNECT_TIME 15 ---- Session cann't last more than 15 mins.
LOGICAL_READS_PER_SESSION DEFAULT ---- Data block reads from memory is subject to DEFAULT profile.
LOGICAL_READS_PER_CALL 1000 ---- A single call cann't read more 1000 data blocks.
PRIVATE_SGA 15K ---- A single call cann't allocate more than 15K SGA memory.
COMPOSITE_LIMIT 5000000 Then I created the user.
CREATE USER EXT_USER IDENTIFIED
BY mypass123
DEFAULT TABLESPACE users
TEMPORARY TABLESPACE temp
QUOTA 5K ON users
PROFILE ext_user_prof
ACCOUNT UNLOCKWhen tried logging into the DB, with the user I created, I can open parallel sessions (Meaning, I can open several connections). Now, is there some thing wrong in the code or the way I understand the parallel session concept?
I use oracle 9.2
Thanks and Warm regards
Guru
Message was edited by:
guruparan18
Added the version detail and formated the code.

Many thanks to Pavan and Surachart.
Now, I am getting the error. So, please tell whether my understanding is right. If the RESOURCE_LIMIT is set to FALSE, the user can login irrespective of the restrictions he has in PROFILE. And when the RESOURCE_LIMIT is set as TRUE, I get this error.
Wonderful.
Further to that, where can I find what is the system setting ( Which table to look into for the detail of the setting?).

Problem testing profile.

Howdy all. Im attempting to use a profile to limit resources as a test. Here is the needed info, followed by my question.
CREATE PROFILE "MYPROFILE" LIMIT CPU_PER_SESSION 1
CPU_PER_CALL 1
CONNECT_TIME 1
IDLE_TIME 1
SESSIONS_PER_USER 1
LOGICAL_READS_PER_SESSION 1
LOGICAL_READS_PER_CALL 1
PRIVATE_SGA 1K
COMPOSITE_LIMIT 1
PASSWORD_LIFE_TIME DEFAULT
PASSWORD_GRACE_TIME DEFAULT
PASSWORD_REUSE_MAX DEFAULT
PASSWORD_REUSE_TIME DEFAULT
PASSWORD_LOCK_TIME DEFAULT
FAILED_LOGIN_ATTEMPTS UNLIMITED
PASSWORD_VERIFY_FUNCTION DEFAULT
CREATE USER "MYUSER" PROFILE "MYPROFILE" IDENTIFIED BY "*******" DEFAULT TABLESPACE "USERS" TEMPORARY TABLESPACE "TEMP" ACCOUNT UNLOCK
GRANT ALTER SESSION TO "MYUSER"
GRANT CREATE CLUSTER TO "MYUSER"
GRANT CREATE DATABASE LINK TO "MYUSER"
GRANT CREATE SEQUENCE TO "MYUSER"
GRANT CREATE SESSION TO "MYUSER"
GRANT CREATE SYNONYM TO "MYUSER"
GRANT CREATE TABLE TO "MYUSER"
GRANT CREATE VIEW TO "MYUSER"
GRANT UNLIMITED TABLESPACE TO "MYUSER"
GRANT SELECT ON "OE"."INVENTORIES" TO "MYUSER"
GRANT SELECT ON "OE"."ORDERS" TO "MYUSER"
GRANT SELECT ON "OE"."ORDER_ITEMS" TO "MYUSER"
GRANT SELECT ON "OE"."PRODUCTS" TO "MYUSER"
GRANT SELECT ON "OE"."PRODUCT_DESCRIPTIONS" TO "MYUSER"
GRANT SELECT ON "OE"."PRODUCT_INFORMATION" TO "MYUSER"
GRANT SELECT ON "OE"."PRODUCT_PRICES" TO "MYUSER"
GRANT SELECT ON "OE"."PROMOTIONS" TO "MYUSER"
GRANT SELECT ON "OE"."SYDNEY_INVENTORY" TO "MYUSER"
GRANT SELECT ON "OE"."TORONTO_INVENTORY" TO "MYUSER"
GRANT SELECT ON "OE"."WAREHOUSES" TO "MYUSER"
GRANT SELECT ON "SH"."CAL_MONTH_SALES_MV" TO "MYUSER"
GRANT SELECT ON "SH"."CHANNELS" TO "MYUSER"
GRANT SELECT ON "SH"."COSTS" TO "MYUSER"
GRANT SELECT ON "SH"."COUNTRIES" TO "MYUSER"
GRANT SELECT ON "SH"."CUSTOMERS" TO "MYUSER"
GRANT SELECT ON "SH"."FWEEK_PSCAT_SALES_MV" TO "MYUSER"
GRANT SELECT ON "SH"."PRODUCTS" TO "MYUSER"
GRANT SELECT ON "SH"."PROMOTIONS" TO "MYUSER"
GRANT SELECT ON "SH"."SALES" TO "MYUSER"
GRANT SELECT ON "SH"."TIMES" TO "MYUSER"
GRANT "CONNECT" TO "MYUSER"
GRANT "MYROLE" TO "MYUSER"
GRANT "RESOURCE" TO "MYUSER"
My thinking is that I should be able to log in to ISQLPlus as myUser, run a query, wait > 1 minute, try to run it again, and it should fail because of the IDLE_TIME paramter of the profile I have created. But that doesn't happen, it simply reruns the query. Any ideas?
TIA, ChrisR

I didn't do the "alter system set resource_limit....." before my testing.
Thanks.

Oracle profile and password limits

Hi there, I don't understand what's limiting my password selection. It appears that the profile is default and doesn't have limitations.
Any help would be appreciated.
Thanks
db2> alter user system identified by "xxxxx";
alter user system identified by "xxxxx"
ERROR at line 1:
ORA-28003: password verification for the specified password failed
ORA-20003: Password should contain at least one \
digit, one character and one punctuation
db2> select profile from dba_users where username='SYSTEM';
PROFILE
DEFAULT
db2> select resource_name, resource_type, limit from dba_profiles where profile='DEFAULT';
RESOURCE_NAME RESOURCE
LIMIT
COMPOSITE_LIMIT KERNEL
UNLIMITED
SESSIONS_PER_USER KERNEL
UNLIMITED
CPU_PER_SESSION KERNEL
UNLIMITED
RESOURCE_NAME RESOURCE
LIMIT
CPU_PER_CALL KERNEL
UNLIMITED
LOGICAL_READS_PER_SESSION KERNEL
UNLIMITED
LOGICAL_READS_PER_CALL KERNEL
UNLIMITED
RESOURCE_NAME RESOURCE
LIMIT
IDLE_TIME KERNEL
UNLIMITED
CONNECT_TIME KERNEL
UNLIMITED
PRIVATE_SGA KERNEL
UNLIMITED
RESOURCE_NAME RESOURCE
LIMIT
FAILED_LOGIN_ATTEMPTS PASSWORD
UNLIMITED
PASSWORD_LIFE_TIME PASSWORD
UNLIMITED
PASSWORD_REUSE_TIME PASSWORD
UNLIMITED
RESOURCE_NAME RESOURCE
LIMIT
PASSWORD_REUSE_MAX PASSWORD
UNLIMITED
PASSWORD_VERIFY_FUNCTION PASSWORD
SFDC_VERIFY_PWD
PASSWORD_LOCK_TIME PASSWORD
UNLIMITED
RESOURCE_NAME RESOURCE
LIMIT
PASSWORD_GRACE_TIME PASSWORD
UNLIMITED
16 rows selected.

I found what the issue was. Does anyone know how to
look at the Resource limits and there value?Other than the DBA_PROFILES view that you queried in the previous post? Or some other resource limits (i.e. Resource Manager limits?)
Justin

Allows more connection then the profile values

I am using the below version.
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Prod
PL/SQL Release 10.2.0.1.0 - Production
CORE 10.2.0.1.0 Production
TNS for Linux: Version 10.2.0.1.0 - Production
NLSRTL Version 10.2.0.1.0 - Production
Here is the profile i am using for one of my schema.
CREATE PROFILE auditprofile LIMIT
SESSIONS_PER_USER 2
CPU_PER_SESSION UNLIMITED
CPU_PER_CALL UNLIMITED
CONNECT_TIME UNLIMITED
LOGICAL_READS_PER_SESSION DEFAULT
LOGICAL_READS_PER_CALL UNLIMITED
PRIVATE_SGA UNLIMITED
COMPOSITE_LIMIT UNLIMITED
idle_time unlimited
failed_login_attempts 10
password_life_time unlimited
password_reuse_time unlimited
password_reuse_max unlimited
password_lock_time unlimited
password_grace_time unlimited
still it allows to connect more then 2 session. Any explanation is highly appreciated...

Shrinika wrote:
I am using the below version.
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Prod
PL/SQL Release 10.2.0.1.0 - Production
CORE 10.2.0.1.0 Production
TNS for Linux: Version 10.2.0.1.0 - Production
NLSRTL Version 10.2.0.1.0 - Production
Here is the profile i am using for one of my schema.
CREATE PROFILE auditprofile LIMIT
SESSIONS_PER_USER 2
CPU_PER_SESSION UNLIMITED
CPU_PER_CALL UNLIMITED
CONNECT_TIME UNLIMITED
LOGICAL_READS_PER_SESSION DEFAULT
LOGICAL_READS_PER_CALL UNLIMITED
PRIVATE_SGA UNLIMITED
COMPOSITE_LIMIT UNLIMITED
idle_time unlimited
failed_login_attempts 10
password_life_time unlimited
password_reuse_time unlimited
password_reuse_max unlimited
password_lock_time unlimited
password_grace_time unlimited
still it allows to connect more then 2 session. Any explanation is highly appreciated...Did you set the parameter RESOURCE_LIMIT=TRUE at the system level before trying out?
alter system set resource_limit=true;HTH
Aman....

Profile LIMIT=DEFAULT ?

I'm using profiles in the database to prevent to much sessions per user. I have the next situation
1 select resource_name,limit
2 from dba_profiles
3 where profile = 'NEW_PROFILE'
4* order by 1,2
SQL> /
RESOURCE_NAME LIMIT
COMPOSITE_LIMIT DEFAULT
CONNECT_TIME DEFAULT
CPU_PER_CALL DEFAULT
CPU_PER_SESSION DEFAULT
FAILED_LOGIN_ATTEMPTS 3
IDLE_TIME DEFAULT
LOGICAL_READS_PER_CALL DEFAULT
LOGICAL_READS_PER_SESSION DEFAULT
PASSWORD_GRACE_TIME DEFAULT
PASSWORD_LIFE_TIME DEFAULT
PASSWORD_LOCK_TIME DEFAULT
RESOURCE_NAME LIMIT
PASSWORD_REUSE_MAX 13
PASSWORD_REUSE_TIME UNLIMITED
PASSWORD_VERIFY_FUNCTION DEFAULT
PRIVATE_SGA DEFAULT
SESSIONS_PER_USER 1
16 rows selected.
A lot of resources have the value DEFAULT
Can somebody tell me what the value is of the DEFAULT's

Default means unlimited for the profile element. In other words, CONNECT_TIME DEFAULT means that you will be able to be connected to the database for all the time that the database can be started.
Joel Pérez

Limiting user activity using Oracle Profiles

I am hoping to reduce the impact of a certain group of users on system performance. I can allocate a separate Oracle profile to them but when I set limits, what happens?
Composite Limits - I'll leave alone, too much math required!
Sessions/User - I can't limit that, they may feasibly and reasonably have several sessions
CPU/Session - Ok, it's not a % of the CPU available but CPU seconds/100. What happens when that number is reached - is the sessions killed or what?
CPU/Call - See above
Logical Reads/Session - What happens when this limit is reached? Does the session die?
Logical Reads/Call - See above
Idle Time - Set to 300
Connect Time - I do not wish to restrict this
Private SGA - I am not sure about this (I don't even know if we are using multi-threaded server architecture!)
So it seems to me, that none of these will meet my needs and consumer resource groups would be the correct thing... but can anyone please confirm?
Thanks

I've used CPU_per_call and logical_reads_per_call for our dynamic search. If user happens to enter such criteria that he cannot get at least a row back within certain limits he gets back certain oracle error and on the screen he gets something like "your query used too much resources, enter better criteria" :)
The overall impact of such queries was limited because of totla rows limit for search typically 100. So at most users could use 100 * almost resource limit per one search.
If your users can issue whatever statements they like then this is not usable because for example for aggregate queries logical_reads_per_call will be reached quickly and user won't get back result of quite normal statement.
So probably you have to use resource groups indeed.
Gints Plivna
http://www.gplivna.eu

LOGICAL_READS_PER_CALL (profile)

Similar Messages

Maybe you are looking for