Results 1 to 3 of 3
  1. #1
    Join Date
    Mar 2004
    Posts
    4

    Unanswered: Shared pool problem.

    I have a java application running on OC4J904 and connecting to Oracle 8.1.7 using JDBC. My DB die when i implemented the application and found out that the shared pool memory has been used out. So I increased the shared pool size to 500MB but after a few days the free memory still become very low. My application is quite small so Im not sure why it taken up so many resources.

    Is there any way to avoid Oracle from using up the shared pool or configure the Oracle to free out the memory, or is better to write script to automatically flush the shared pool when its low?

    Any suggestion are welcome.

    Thanks.

  2. #2
    Join Date
    Sep 2003
    Location
    Virginia, USA
    Posts
    246
    I think you have a memory leak (bug). Check Oracle for a patch.

    I do not think the problem is your shared pool being too small. The shared pool has a built-in aging mechanism, and Oracle should not run out of memory unless everything is needed at once, which does not sound true in your case.

  3. #3
    Join Date
    Nov 2002
    Posts
    833
    what exact version and patchlevel you are running?

    how did you set the java_pool size?
    and did you install the jvm properly?

Posting Permissions

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