3.5.3 PolyServe MxS Oracle Database Solution Pack Release Notes (August 2008)

Installation and Operation 4
Very Large SGA Buffer Pools
On 64-bit systems, MxODM is routinely tested for functionality and
efficiency when performing I/O into very large SGA buffer pools. An
SGA db block buffer cache size of 20GB has been tested with both Real
Application Clusters (RAC) and non-RAC on systems configured with
32GB of main memory.
Very Large Aggregate PGA for Parallel Query Option
By setting the init.ora parameter “pga_aggregate_target” to 20000M, this
release of MxODM has been tested with Parallel Query index creates on
tables as large as 500GB on Oracle10g R2.
Large Numbers of Users Connecting as Dedicated Server Processes
This release of MxODM has a fixed limit of 1024 instantiations of the
library on a server. This limit has been tested by setting the init.ora
“processes” parameter to 950 and invoking Pro*C benchmark client
processes using the dedicated server model. Setting the init.ora
“processes” parameter to 950 leaves sufficient headroom for the Oracle
background processes such as DBWR, LGWR and Parallel Query slaves,
which can be significant in value.
Should this fixed limit not be sufficient for your client connect needs,
MxODM has been fully tested with the Multi-threaded Server (MTS)
option of Oracle.
Very Large Files
This release of MxODM has been throroughly tested with Oracle10g
BIGFILE tablespaces greater than 2TB using both OLTP and DSS
workloads.
Log Messages
MxODM stores log messages in the directory $ORACLE_HOME/lib/pmxs-
odm/log. The prefix of each log message specifies the date and time of the
message and the process ID of the process that called the ODM library
function.