DBAsupport.com Forums - Powered by vBulletin
Results 1 to 4 of 4
  1. #1
    Join Date
    Jan 2002



    we have a 3 tier app that seems to consistantly drive up the
    ram usage of our oracle.exe process (on winNT)

    so generally we get to the point where we can't connect to it and get the ORA-04030 error (the memory never goes down much). i restart the app and the process begins all over.

    here's what i really want to do: find out what oracle processes are taking up what memory when the oracle.exe process is maxing out. ie at any point in time, see what is taking up so much memory?

    is it clients/server processes, or lgwr or dbwr et... what's killing us?

  2. #2
    On the Oracle side, some quick suggestions for reducing memory
    utilization include:

    (1) reducing db_block_buffers and shared_pool_size as these are the
    heaviest users.

    (2) reducing sort_area_size, hash_area_size and sort_direct_buffers as
    these reserve memory on a per-process basis. If possible, simply set
    hash_join_enabled = false and sort_direct_writes = false. sort_area_size is
    usually okay at 1m.

    (3) reducing the degree of intranode parallelism may help, particularly
    if you are implementing a high degree of parallelism without a good reason for
    doing so.
    The brain is a wonderful organ; it starts working the moment you get up in the morning and does not stop until you get into the office.

  3. #3
    Join Date
    Jan 2002
    thanks for the reply.

    we've tried many tuning methods including most of the ones you mentioned. i will try adjusting some of the others where applicable.

    i guess the question still remains, is it possible to get an accurate representation of what's taking up what portion of memory in the oracle.exe process at any given time in winNt?

  4. #4
    Join Date
    Jan 2002

Posting Permissions

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

Click Here to Expand Forum to Full Width

We have made updates to our Privacy Policy to reflect the implementation of the General Data Protection Regulation.