Determine JAVA_POOL_SIZE minimum value (Doc ID 269231.1)

APPLIES TO:

Oracle Database - Enterprise Edition - Version 8.1.7.4 to 9.2.0.7 [Release 8.1.7 to 9.2]
Information in this document applies to any platform.

GOAL

 To assist with determining the minimum recommended values for setting
the INIT.ORA parameter JAVA_POOL_SIZE.

SOLUTION

Checked for relevance on 01-Jun-2007

This issue can occur on any platform.

FIX

Oracle Server - Enterprise Edition - Version: 8i
Reference guide for 8.1.5 does not list the range of values for the java_pool_size parameter. Not all users are using Java, and you want to minimize this parameter for system performance. 
From trial and error, an instance will not start up with 512000 bytes, but it will startup with a value of 1000000 (1MB). 
*Note: The default value in 8i is 20000k. 


Oracle Server - Enterprise Edition - Version: 9i
The JAVA_POOL_SIZE is recommended to be set to 24 MB minimum and 150 MB or higher when applying any patchset. 

If using PORTAL, install of product requires 50MB minimum for the JAVA_POOL_SIZE.

RMAN also uses this parameter - 50MB - 70MB minimum is suggested for the JAVA_POOL_SIZE

APPS configuration and upgrades suggest 50MB minimum is suggested for the JAVA_POOL_SIZE

REFERENCES

NOTE:262951.1 - Minimum recommended Database parameter values when migrating to Oracle 9.0.1.X/9.2.0.X
NOTE:107698.1 - Minimum value for JAVA_POOL_SIZE Setting for init.ora

NOTE:216205.1 - Database Initialization Parameters for Oracle Applications 11i
BUG:2870946 - Appst9203 : Java Upgrade Takes 10 Hours

---

REFERENCES

BUG:2870946  - APPST9203 : JAVA UPGRADE TAKES 10 HOURS
NOTE:107698.1  - Minimum value for JAVA_POOL_SIZE Setting for init.ora
NOTE:216205.1  - Database Initialization Parameters for Oracle Applications Release 11i
NOTE:262951.1  - Minimum recommended Database parameter values when migrating to Oracle 9.0.1.X/9.2.0.X