Results 1 to 5 of 5
  1. #1
    Join Date
    Dec 2003
    Posts
    1,074

    Unanswered: Setting up profiles

    Are there any rules-of-thumb that you start with when implementing resource limits through profiles? I have been reading about this information, but actual settings for the following escape me:

    CPU/Session (Sec./100)
    CPU/Call (Sec./100)
    Reads/Session (Blocks)
    Reads/Call (Blocks)

    Do you start low, and increase these values if users have valid complaints about not being able to complete tasks? What values do you start with? The only one that makes sense is CPU/Call, where you can limit the amount of CPU time consumed per call to say, 30 seconds, be setting this to 3000.

    -Chuck

  2. #2
    Join Date
    Apr 2003
    Location
    Greenville, SC (USA)
    Posts
    1,155
    Just 1 opinion...

    I only use idle and connect times as limitations.... Be sure you understand
    the queries against the db if you are going to use other limits.

    Gregg

  3. #3
    Join Date
    Dec 2003
    Posts
    1,074
    Can I get this information, on a per query basis, from v$session? I never thought about that. Or is there a better way?
    -cf

  4. #4
    Join Date
    Apr 2003
    Location
    Greenville, SC (USA)
    Posts
    1,155
    Yes ... You can get connect and idle times from v$session ... For some of my clients, I limit the connect time (users that wont log off ...) etc ... Here's a little script to monitor session idle time ...

    col sid format 999
    col username format a10 truncated
    col status format a1 truncated
    col logon format a17
    col idle format a9
    col program format a30 truncated

    select
    sid,username,status,
    to_char(logon_time,'dd-mm-yy hh:mi:ss') "LOGON",
    floor(last_call_et/3600)||':'||
    floor(mod(last_call_et,3600)/60)||':'||
    mod(mod(last_call_et,3600),60) "IDLE",
    program
    from
    v$session
    where
    type='USER'
    order by last_call_et;


    Gregg

  5. #5
    Join Date
    Jun 2004
    Posts
    796
    Provided Answers: 1
    Chuck,

    As far as I can see the only reason for setting up the 4 parameters that you mentioned is to limit a heavy user or users (e.g. by rationing how much CPU they can use either in a call or in a session) - I have yet to meet a user that I disliked so much as to set these up in his profile (though I have been tempted a few times!)

    As Gregg said, idle times & connect times are a more 'user friendly' way of monitoring the users.
    90% of users' problems can be resolved by punching them - the other 10% by switching off their PCs.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •