IDLE_TIME profile
Hi
If a select statement or update statement takes a long time to execute, does this counted as idle time?
Thanks
user12023552 wrote:
Hi
If a select statement or update statement takes a long time to execute, does this counted as idle time?
ThanksTime to read
http://download.oracle.com/docs/cd/E11882_01/server.112/e10592/statements_6010.htm#SQLRF01310
Which says,
IDLE_TIME
Specify the permitted periods of continuous inactive time during a session, expressed in minutes. Long-running queries and other operations are not subject to this limit.HTH
Aman....
Similar Messages
-
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 AMSQL> 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 -
Oracle profile - IDLE_TIME DEFAULT - value ?
Friends
How can I determine the value of DEFAULT for the IDLE_TIME in Oracle profile.
CREATE PROFILE DEFAULT LIMIT
idle_time <value | UNLIMITED | DEFAULT>
Thanks
Vishal V.Ok, I found it.
"Default" profile has default values.
Thanks
Vishal -
Hello,
I have a profile, test_profile, which I set the idle_time to 2 minutes. I created a test_user and alter the user to the test_profile. After loging in the test_user and let the session sits for 3 minutes, I am still able to perform a query. How come the idle_time of 2 minutes did not log off the test_user? How does idle_time work? Thank you.Make sure that the resource_limit parameter is set to TRUE. Otherwise, Oracle won't enforce the resource limits specified in profiles.
Justin -
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 PMI 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. -
How to view/edit/delete the user created profile in oracle 9i? Very Urgent
Friends,
I logged in as system in oracle 9i.
SQL> create profile testpro limit
2 idle_time 1;
Profile created.
SQL> alter user scott profile testpro;
User altered.
Then i logged in to sqlplusw as a scott user.
and i waited for 10 mins after that.
sql> select * from cat;
its working......
how come? i have already set a idle time to 1 minute.
Please correct me if im wrong.
Also, how can i view/edit/delete the user created profile.
Thanks & Regards
Sathyguy
Message was edited by:
sathyguyThe resource limits set for a profile are enforced only when you enable resource limitation for the database.
Enabling and Disabling Resource Limits While the Database is Open
ALTER SYSTEM SET RESOURCE_LIMIT = TRUE;
http://download-west.oracle.com/docs/cd/B10501_01/server.920/a96521/users.htm#15451
Manu -
How to create log entry when session exceeded profile's limit ?
Hi all,
is there any way to create entry in log_table (or some log file) when session exceeded its profile's limit (i.e. idle_time) ?
If this entry can be created when session status changes to 'SNIPED', it would be great.
I've tried with trigger "AFTER SERVERERROR" but it doesn't fire on errors like below:
ORA-02396: exceeded maximum idle time, please connect againThank for any help in advance.
Oracle ver: 10.2.0.4 (Windows XP and Linux RH4).
Tomasz K.Thanks for your reply.
I had audit enabled already,
but there is no real reason logged in audit trail why the session has been disconnected.
ACTION_NAME has only 'LOGOFF' [clear exit] or 'LOGOFF BY CLEANUP' (which includes all "brute" disonnect reasons, as network failure, app failure or "session limit exceeded).
Is there any way to differentiate 'LOGOFF BY CLEANUP' audit entries into more precise descriptions ?
Thanks
Tomasz K. -
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. -
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, ChrisRI 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.... -
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'sDefault 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 -
User profile doesn't stop execution due to it's restriction
Oracle Version:
SQL> select * from v$version;
BANNER
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bi
PL/SQL Release 10.2.0.4.0 - Production
CORE 10.2.0.4.0 Production
TNS for IBM/AIX RISC System/6000: Version 10.2.0.4.0 - Productio
NLSRTL Version 10.2.0.4.0 - ProductionSome initial data:
SQL> show parameter resource_l
NAME TYPE VALUE
resource_limit boolean TRUEDDL for user:
CREATE USER TEST_READER
IDENTIFIED BY VALUES 'AFBD6BEB29FF93AA'
DEFAULT TABLESPACE USERS
TEMPORARY TABLESPACE TEMP
PROFILE ARGUS_READER_PROFILE
ACCOUNT UNLOCK;
-- 1 Role for TEST_READER
GRANT ARGUS_READONLY_USER TO TEST_READER;
ALTER USER TEST_READER DEFAULT ROLE ALL;
-- 1 System Privilege for TEST_READER
GRANT SELECT ANY DICTIONARY TO TEST_READER;
-- 1 Object Privilege for TEST_READER
GRANT INSERT ON ARGUS_SYS.PLAN_TABLE TO TEST_READER;Small limit for LOGICAL_READS_PER_CALL = 100000 in profile:
SQL> ALTER PROFILE ARGUS_READER_PROFILE LIMIT
2 SESSIONS_PER_USER 10
3 CPU_PER_SESSION UNLIMITED
4 CPU_PER_CALL 60000
5 CONNECT_TIME DEFAULT
6 IDLE_TIME DEFAULT
7 LOGICAL_READS_PER_SESSION DEFAULT
8 LOGICAL_READS_PER_CALL 100000
9 COMPOSITE_LIMIT DEFAULT
10 PRIVATE_SGA 31457280
11 FAILED_LOGIN_ATTEMPTS 10
12 PASSWORD_LIFE_TIME UNLIMITED
13 PASSWORD_REUSE_TIME UNLIMITED
14 PASSWORD_REUSE_MAX UNLIMITED
15 PASSWORD_LOCK_TIME UNLIMITED
16 PASSWORD_GRACE_TIME UNLIMITED
17 PASSWORD_VERIFY_FUNCTION NULL;
Profile altered.Some huge SQL:
SQL> conn test_reader/test@****
Connected.
SQL> set autotrace traceonly
SQL> @C:\work\test\222.sql
Enter value for ddmmyyyybegin: '19.02.2012'
old 128: TO_DATE (&ddmmyyyybegin, 'dd.MM.yyyy'))
new 128: TO_DATE ('19.02.2012', 'dd.MM.yyyy'))
Enter value for ddmmyyyyend: '19.03.2013'
old 131: TO_DATE (&ddmmyyyyend, 'dd.MM.yyyy'))))
new 131: TO_DATE ('19.03.2013', 'dd.MM.yyyy'))))
Enter value for int851: 851
old 132: AND (o.order_type_id = &int851))
new 132: AND (o.order_type_id = 851))
Enter value for int900: 10000
old 138: WHERE ROWNUM <= &int900) a
new 138: WHERE ROWNUM <= 10000) a
Enter value for int600: 1
old 139: WHERE rnum >= &int600
new 139: WHERE rnum >= 1
FROM argus_sys.service_special_conn rsc,
ERROR at line 58:
ORA-02395: exceeded call limit on IO usageProfile worked, statistic for logical reads:
SQL> select * from v$sesstat where statistic# in (9) and sid = 2146;
SID STATISTIC# VALUE
2146 9 100031New limit for LOGICAL_READS_PER_CALL=150000 in profile
SQL> ALTER PROFILE ARGUS_READER_PROFILE LIMIT
2 SESSIONS_PER_USER 10
3 CPU_PER_SESSION UNLIMITED
4 CPU_PER_CALL 60000
5 CONNECT_TIME DEFAULT
6 IDLE_TIME DEFAULT
7 LOGICAL_READS_PER_SESSION DEFAULT
8 LOGICAL_READS_PER_CALL 150000
9 COMPOSITE_LIMIT DEFAULT
10 PRIVATE_SGA 31457280
11 FAILED_LOGIN_ATTEMPTS 10
12 PASSWORD_LIFE_TIME UNLIMITED
13 PASSWORD_REUSE_TIME UNLIMITED
14 PASSWORD_REUSE_MAX UNLIMITED
15 PASSWORD_LOCK_TIME UNLIMITED
16 PASSWORD_GRACE_TIME UNLIMITED
17 PASSWORD_VERIFY_FUNCTION NULL;
Profile altered.The same query:
SQL> conn test_reader/test@****
Connected.
SQL> set autotrace traceonly
SQL> @C:\work\test\222.sql
Enter value for ddmmyyyybegin: '19.02.2012'
old 128: TO_DATE (&ddmmyyyybegin, 'dd.MM.yyyy'))
new 128: TO_DATE ('19.02.2012', 'dd.MM.yyyy'))
Enter value for ddmmyyyyend: '19.03.2013'
old 131: TO_DATE (&ddmmyyyyend, 'dd.MM.yyyy'))))
new 131: TO_DATE ('19.03.2013', 'dd.MM.yyyy'))))
Enter value for int851: 851
old 132: AND (o.order_type_id = &int851))
new 132: AND (o.order_type_id = 851))
Enter value for int900: 10000
old 138: WHERE ROWNUM <= &int900) a
new 138: WHERE ROWNUM <= 10000) a
Enter value for int600: 1
old 139: WHERE rnum >= &int600
new 139: WHERE rnum >= 1And.... It lasts and lasts...
In the second session I see, that logical reads have exceeded 200k and it still going further..
At last:
Execution plan...
Statistics
98252 recursive calls
0 db block gets
409072 consistent gets
0 physical reads
1616 redo size
1688278 bytes sent via SQL*Net to client
7542 bytes received via SQL*Net from client
431 SQL*Net roundtrips to/from client
18906 sorts (memory)
0 sorts (disk)
6446 rows processedStatistic from v$sesstat:
SQL> select * from v$sesstat where statistic# in (9) and sid = 2146;
SID STATISTIC# VALUE
2146 9 409726
Question is:
Do I correctly compare statistic value of sesstat 'session logical reads' with 'LOGICAL_READS_PER_CALL' from profile?
If yes - Why had profile limit been ommited in the second case, while in the first there was a stop?Have compared execution plans - they are the same.
Have made traces.
For 10K limit:
---HERE SQL ----
call count cpu elapsed disk query current rows
Parse 1 0.00 0.00 0 0 0 0
Execute 1 0.00 0.00 0 0 0 0
Fetch 1 0.67 0.70 0 100001 0 0
total 3 0.67 0.70 0 100001 0 0
Misses in library cache during parse: 0
Optimizer mode: ALL_ROWS
Parsing user id: 3427
Rows Row Source Operation
0 SORT AGGREGATE (cr=0 pr=0 pw=0 time=0 us)
0 NESTED LOOPS (cr=0 pr=0 pw=0 time=0 us)
0 TABLE ACCESS BY INDEX ROWID SERVICE_SPECIAL_CONN (cr=0 pr=0 pw=0 time=0 us)
0 INDEX RANGE SCAN IND_SVC_SPEC_CONN_SERVICE (cr=0 pr=0 pw=0 time=0 us)(object id 1023868)
0 TABLE ACCESS BY INDEX ROWID SERVICE_SPECIAL_CONN_TYPE (cr=0 pr=0 pw=0 time=0 us)
0 INDEX UNIQUE SCAN PK_NUMBER_SPECIAL_CONN_TYPE (cr=0 pr=0 pw=0 time=0 us)(object id 1023562)
0 VIEW (cr=0 pr=0 pw=0 time=89 us)
0 COUNT STOPKEY (cr=0 pr=0 pw=0 time=85 us)
0 VIEW (cr=0 pr=0 pw=0 time=78 us)
0 SORT ORDER BY STOPKEY (cr=0 pr=0 pw=0 time=76 us)
5729 CONCATENATION (cr=99989 pr=0 pw=0 time=708938 us)
5729 NESTED LOOPS (cr=99989 pr=0 pw=0 time=703205 us)
5729 NESTED LOOPS OUTER (cr=82798 pr=0 pw=0 time=588603 us)
5729 NESTED LOOPS (cr=82790 pr=0 pw=0 time=565680 us)
5730 NESTED LOOPS (cr=65609 pr=0 pw=0 time=451164 us)
5730 NESTED LOOPS (cr=48414 pr=0 pw=0 time=359469 us)
5730 NESTED LOOPS (cr=31220 pr=0 pw=0 time=256264 us)
5730 NESTED LOOPS (cr=14025 pr=0 pw=0 time=135922 us)
5730 HASH JOIN RIGHT OUTER (cr=2563 pr=0 pw=0 time=67108 us)
41 TABLE ACCESS FULL MEASURED_DAMAGE_KIND (cr=3 pr=0 pw=0 time=164 us)
5730 INLIST ITERATOR (cr=2560 pr=0 pw=0 time=45976 us)
5730 TABLE ACCESS BY INDEX ROWID ORDER_L (cr=2560 pr=0 pw=0 time=45974 us)
5730 INDEX RANGE SCAN IND6_ORDER_ORDER_TYPE_STATE (cr=17 pr=0 pw=0 time=11554 us)(object id 1023412)
5730 TABLE ACCESS BY INDEX ROWID DEPARTMENT_L (cr=11462 pr=0 pw=0 time=58655 us)
5730 INDEX UNIQUE SCAN PK_DEPARTMENT_L (cr=5732 pr=0 pw=0 time=30776 us)(object id 1023205)
5730 TABLE ACCESS BY INDEX ROWID INSTALLATION_L (cr=17195 pr=0 pw=0 time=105341 us)
5730 INDEX UNIQUE SCAN PK_INSTALLATION_L (cr=11462 pr=0 pw=0 time=63663 us)(object id 1023366)
5730 TABLE ACCESS BY INDEX ROWID LIN_ORDER (cr=17194 pr=0 pw=0 time=94252 us)
5730 INDEX UNIQUE SCAN PK_LIN_ORDER (cr=11462 pr=0 pw=0 time=60346 us)(object id 1023159)
5730 TABLE ACCESS BY INDEX ROWID ORDER_LDN (cr=17195 pr=0 pw=0 time=75887 us)
5730 INDEX UNIQUE SCAN IND_ORDER_LDN (cr=11462 pr=0 pw=0 time=42138 us)(object id 1023370)
5729 TABLE ACCESS BY INDEX ROWID SERVICE_L (cr=17192 pr=0 pw=0 time=109193 us)
5729 INDEX UNIQUE SCAN PK_SERVICE_L (cr=11460 pr=0 pw=0 time=67339 us)(object id 1023216)
7 TABLE ACCESS BY INDEX ROWID SERVICE_LINE_TYPE (cr=8 pr=0 pw=0 time=16179 us)
7 INDEX UNIQUE SCAN PK_LINE_TYPE (cr=1 pr=0 pw=0 time=7396 us)(object id 1023563)
5729 TABLE ACCESS BY INDEX ROWID CLIENT (cr=17191 pr=0 pw=0 time=101030 us)
5729 INDEX UNIQUE SCAN PK_CLIENT (cr=11460 pr=0 pw=0 time=61941 us)(object id 1023006)
0 NESTED LOOPS (cr=0 pr=0 pw=0 time=0 us)
0 NESTED LOOPS (cr=0 pr=0 pw=0 time=0 us)
0 NESTED LOOPS (cr=0 pr=0 pw=0 time=0 us)
0 NESTED LOOPS (cr=0 pr=0 pw=0 time=0 us)
0 NESTED LOOPS OUTER (cr=0 pr=0 pw=0 time=0 us)
0 NESTED LOOPS (cr=0 pr=0 pw=0 time=0 us)
0 NESTED LOOPS (cr=0 pr=0 pw=0 time=0 us)
0 NESTED LOOPS OUTER (cr=0 pr=0 pw=0 time=0 us)
0 TABLE ACCESS BY INDEX ROWID ORDER_L (cr=0 pr=0 pw=0 time=0 us)
0 INDEX RANGE SCAN IND_ORDER_FILTER_DATE (cr=0 pr=0 pw=0 time=0 us)(object id 1023432)
0 TABLE ACCESS BY INDEX ROWID MEASURED_DAMAGE_KIND (cr=0 pr=0 pw=0 time=0 us)
0 INDEX UNIQUE SCAN PK_MEASURED_DAMAGE_KIND (cr=0 pr=0 pw=0 time=0 us)(object id 1023179)
0 TABLE ACCESS BY INDEX ROWID INSTALLATION_L (cr=0 pr=0 pw=0 time=0 us)
0 INDEX UNIQUE SCAN PK_INSTALLATION_L (cr=0 pr=0 pw=0 time=0 us)(object id 1023366)
0 TABLE ACCESS BY INDEX ROWID SERVICE_L (cr=0 pr=0 pw=0 time=0 us)
0 INDEX UNIQUE SCAN PK_SERVICE_L (cr=0 pr=0 pw=0 time=0 us)(object id 1023216)
0 TABLE ACCESS BY INDEX ROWID SERVICE_LINE_TYPE (cr=0 pr=0 pw=0 time=0 us)
0 INDEX UNIQUE SCAN PK_LINE_TYPE (cr=0 pr=0 pw=0 time=0 us)(object id 1023563)
0 TABLE ACCESS BY INDEX ROWID DEPARTMENT_L (cr=0 pr=0 pw=0 time=0 us)
0 INDEX UNIQUE SCAN PK_DEPARTMENT_L (cr=0 pr=0 pw=0 time=0 us)(object id 1023205)
0 TABLE ACCESS BY INDEX ROWID LIN_ORDER (cr=0 pr=0 pw=0 time=0 us)
0 INDEX UNIQUE SCAN PK_LIN_ORDER (cr=0 pr=0 pw=0 time=0 us)(object id 1023159)
0 TABLE ACCESS BY INDEX ROWID CLIENT (cr=0 pr=0 pw=0 time=0 us)
0 INDEX UNIQUE SCAN PK_CLIENT (cr=0 pr=0 pw=0 time=0 us)(object id 1023006)
0 TABLE ACCESS BY INDEX ROWID ORDER_LDN (cr=0 pr=0 pw=0 time=0 us)
0 INDEX UNIQUE SCAN IND_ORDER_LDN (cr=0 pr=0 pw=0 time=0 us)(object id 1023370)
Elapsed times include waiting on following events:
Event waited on Times Max. Wait Total Waited
---------------------------------------- Waited ---------- ------------
SQL*Net message to client 1 0.00 0.00
SQL*Net break/reset to client 2 0.03 0.03
********************************************************************************For 15K limit:
---HERE SQL ----
call count cpu elapsed disk query current rows
Parse 1 3.02 5.51 31 792 0 0
Execute 1 0.00 0.00 0 0 0 0
Fetch 431 20.57 161.50 10751 262214 0 6446
total 433 23.59 167.02 10782 263006 0 6446
Misses in library cache during parse: 1
Optimizer mode: ALL_ROWS
Parsing user id: 3427
Rows Row Source Operation
6433 SORT AGGREGATE (cr=17212 pr=756 pw=0 time=5429792 us)
1750 NESTED LOOPS (cr=17212 pr=756 pw=0 time=4849653 us)
1750 TABLE ACCESS BY INDEX ROWID SERVICE_SPECIAL_CONN (cr=15067 pr=756 pw=0 time=4791139 us)
1750 INDEX RANGE SCAN IND_SVC_SPEC_CONN_SERVICE (cr=13316 pr=376 pw=0 time=2319918 us)(object id 1023868)
1750 TABLE ACCESS BY INDEX ROWID SERVICE_SPECIAL_CONN_TYPE (cr=2145 pr=0 pw=0 time=37156 us)
1750 INDEX UNIQUE SCAN PK_NUMBER_SPECIAL_CONN_TYPE (cr=395 pr=0 pw=0 time=17962 us)(object id 1023562)
6446 VIEW (cr=116530 pr=0 pw=0 time=2185799 us)
6446 COUNT STOPKEY (cr=116530 pr=0 pw=0 time=2127750 us)
6446 VIEW (cr=116530 pr=0 pw=0 time=2114840 us)
6446 SORT ORDER BY STOPKEY (cr=116530 pr=0 pw=0 time=2082566 us)
6446 CONCATENATION (cr=116530 pr=0 pw=0 time=948468 us)
6432 NESTED LOOPS (cr=116258 pr=0 pw=0 time=946404 us)
6432 NESTED LOOPS OUTER (cr=96958 pr=0 pw=0 time=759862 us)
6432 NESTED LOOPS (cr=96950 pr=0 pw=0 time=727695 us)
6432 NESTED LOOPS (cr=77650 pr=0 pw=0 time=573315 us)
6432 NESTED LOOPS (cr=58350 pr=0 pw=0 time=463952 us)
6432 NESTED LOOPS (cr=39050 pr=0 pw=0 time=328850 us)
6432 NESTED LOOPS (cr=19750 pr=0 pw=0 time=180901 us)
6432 HASH JOIN RIGHT OUTER (cr=6884 pr=0 pw=0 time=90821 us)
41 TABLE ACCESS FULL MEASURED_DAMAGE_KIND (cr=3 pr=0 pw=0 time=158 us)
6432 INLIST ITERATOR (cr=6881 pr=0 pw=0 time=64458 us)
6432 TABLE ACCESS BY INDEX ROWID ORDER_L (cr=6881 pr=0 pw=0 time=1006803 us)
6432 INDEX RANGE SCAN IND6_ORDER_ORDER_TYPE_STATE (cr=3919 pr=0 pw=0 time=961726 us)(object id 1023412)
6432 TABLE ACCESS BY INDEX ROWID DEPARTMENT_L (cr=12866 pr=0 pw=0 time=92628 us)
6432 INDEX UNIQUE SCAN PK_DEPARTMENT_L (cr=6434 pr=0 pw=0 time=47602 us)(object id 1023205)
6432 TABLE ACCESS BY INDEX ROWID INSTALLATION_L (cr=19300 pr=0 pw=0 time=153272 us)
6432 INDEX UNIQUE SCAN PK_INSTALLATION_L (cr=12866 pr=0 pw=0 time=93766 us)(object id 1023366)
6432 TABLE ACCESS BY INDEX ROWID LIN_ORDER (cr=19300 pr=0 pw=0 time=135255 us)
6432 INDEX UNIQUE SCAN PK_LIN_ORDER (cr=12866 pr=0 pw=0 time=85808 us)(object id 1023159)
6432 TABLE ACCESS BY INDEX ROWID ORDER_LDN (cr=19300 pr=0 pw=0 time=108460 us)
6432 INDEX UNIQUE SCAN IND_ORDER_LDN (cr=12866 pr=0 pw=0 time=60726 us)(object id 1023370)
6432 TABLE ACCESS BY INDEX ROWID SERVICE_L (cr=19300 pr=0 pw=0 time=159645 us)
6432 INDEX UNIQUE SCAN PK_SERVICE_L (cr=12866 pr=0 pw=0 time=97446 us)(object id 1023216)
7 TABLE ACCESS BY INDEX ROWID SERVICE_LINE_TYPE (cr=8 pr=0 pw=0 time=28277 us)
7 INDEX UNIQUE SCAN PK_LINE_TYPE (cr=1 pr=0 pw=0 time=15130 us)(object id 1023563)
6432 TABLE ACCESS BY INDEX ROWID CLIENT (cr=19300 pr=0 pw=0 time=148792 us)
6432 INDEX UNIQUE SCAN PK_CLIENT (cr=12866 pr=0 pw=0 time=88216 us)(object id 1023006)
14 NESTED LOOPS (cr=272 pr=0 pw=0 time=2903 us)
14 NESTED LOOPS (cr=228 pr=0 pw=0 time=2584 us)
14 NESTED LOOPS (cr=184 pr=0 pw=0 time=2155 us)
14 NESTED LOOPS (cr=140 pr=0 pw=0 time=1758 us)
14 NESTED LOOPS OUTER (cr=110 pr=0 pw=0 time=1432 us)
14 NESTED LOOPS (cr=110 pr=0 pw=0 time=1367 us)
14 NESTED LOOPS (cr=66 pr=0 pw=0 time=967 us)
14 NESTED LOOPS OUTER (cr=22 pr=0 pw=0 time=584 us)
14 TABLE ACCESS BY INDEX ROWID ORDER_L (cr=6 pr=0 pw=0 time=362 us)
14 INDEX RANGE SCAN IND_ORDER_FILTER_DATE (cr=3 pr=0 pw=0 time=136 us)(object id 1023432)
14 TABLE ACCESS BY INDEX ROWID MEASURED_DAMAGE_KIND (cr=16 pr=0 pw=0 time=130 us)
14 INDEX UNIQUE SCAN PK_MEASURED_DAMAGE_KIND (cr=2 pr=0 pw=0 time=66 us)(object id 1023179)
14 TABLE ACCESS BY INDEX ROWID INSTALLATION_L (cr=44 pr=0 pw=0 time=211 us)
14 INDEX UNIQUE SCAN PK_INSTALLATION_L (cr=30 pr=0 pw=0 time=131 us)(object id 1023366)
14 TABLE ACCESS BY INDEX ROWID SERVICE_L (cr=44 pr=0 pw=0 time=209 us)
14 INDEX UNIQUE SCAN PK_SERVICE_L (cr=30 pr=0 pw=0 time=137 us)(object id 1023216)
0 TABLE ACCESS BY INDEX ROWID SERVICE_LINE_TYPE (cr=0 pr=0 pw=0 time=39 us)
0 INDEX UNIQUE SCAN PK_LINE_TYPE (cr=0 pr=0 pw=0 time=16 us)(object id 1023563)
14 TABLE ACCESS BY INDEX ROWID DEPARTMENT_L (cr=30 pr=0 pw=0 time=155 us)
14 INDEX UNIQUE SCAN PK_DEPARTMENT_L (cr=16 pr=0 pw=0 time=81 us)(object id 1023205)
14 TABLE ACCESS BY INDEX ROWID LIN_ORDER (cr=44 pr=0 pw=0 time=262 us)
14 INDEX UNIQUE SCAN PK_LIN_ORDER (cr=30 pr=0 pw=0 time=181 us)(object id 1023159)
14 TABLE ACCESS BY INDEX ROWID CLIENT (cr=44 pr=0 pw=0 time=185 us)
14 INDEX UNIQUE SCAN PK_CLIENT (cr=30 pr=0 pw=0 time=121 us)(object id 1023006)
14 TABLE ACCESS BY INDEX ROWID ORDER_LDN (cr=44 pr=0 pw=0 time=174 us)
14 INDEX UNIQUE SCAN IND_ORDER_LDN (cr=30 pr=0 pw=0 time=101 us)(object id 1023370)
Elapsed times include waiting on following events:
Event waited on Times Max. Wait Total Waited
---------------------------------------- Waited ---------- ------------
SQL*Net message to client 431 0.00 0.00
SQL*Net more data to client 643 0.00 0.07
SQL*Net message from client 431 2066.60 3307.29
db file sequential read 756 0.01 4.49
********************************************************************************After, I'de made serial test to determine the stop point and found that LOGICAL_READS_PER_CALL=116700
Which is very close to value in the following string of second trace:
6446 COUNT STOPKEY (cr=116530 pr=0 pw=0 time=2127750 us)Well. I'm ready to admit, my understanding was wrong.
After some investigation, I've found, that 'CR' (consistrent reads) from trace refers to 'consistent gets' (While I queried 'session logical reads') wait from v$sesstat and in profile it is called 'LOGICAL_READS'.
Sorry, my fault. -
Alter user ...changing profiles..urgent..
I wanted to know one thing if i have a list of users and i want to change their idle time limit what wud be a good script all together so that i dont have to make changes for every user and i can do it in one statement for all of them. Please suggest.
BEst regards,
AshishIf all your users have only one profile ( or the DEFAULT profile assigned to every user when it is created ) you can change the limit on resource on that profile and it will apply to all users.
For example if every user has default profile, change the resource limit idle time like this :
alter profile default limit idle_time 55;
HTH
Chandar
Maybe you are looking for
-
There any way to re-sign the app developed with Adobe DPS?
Hi Everyone , I explain a problem that I have with DPS Single Edition ( it useful that is until May ) to see if anyone knows a solution. I have developed an app for a client , but the client wants to publish the app in Apple Developer with your name
-
Why do iPhotos I put on an SD card show up as 2 files?
Why do iPhotos (.tif, or .jpeg format) I put on an SD card in my Mac Pro, show up as 2 files in my new EVD player? The player displays the photo alright but clicking to go to the next photo brings up a note that that file by the same name is an unsu
-
When not using EJBs can I make BD a Singleton and cache facade instances?
Hi, In an application which does not use EJBs can I make BD(Business Delegate) a singleton? I was very sure about doing this but when I tried Google on the same subject the answers were'nt supportive of this but that was in the context of application
-
My son has a PC w. a Logitech Camera and they are on Yahoo Instant Messaging. Can I have AV communication with iSight and iChat with them? If yes, how? Powerbook G4 Mac OS X (10.4.8)
-
HT4759 My phone reads that my phone has never been back up, how can I back it up
I need to know the steps to back up up phone in icloud