Close on the heels of our recent updates to the recommended EBS 11i Database parameters, our database and applications performance architects have published updates for EBS Release 12. The updated note is now available here:
Our architects have refreshed a large number of recommended settings based upon customer feedback and their ongoing performance and scalability tests.
New updates
- Removal of Application Upgrade Considerations section.
- Addition of Advanced Queuing (AQ) note to common parameters.
- Addition of note to the job_queue_processes
- Addition of diagnostic_dest to 11gR1-specific parameters.
- Addition of background_dump_dest, user_dump_dest, core_dump_dest to 11gR1 removal list.
- Addition of plsql_native_library_dir, plsql_native_library_subdir_count, plsql_optimize_level to 11gR1 removal list.
- Addition of #MP to _optimizer_autostats_job=false.
- Updates to undo_retention section.
- Addition of Timed_Statistics.
- Addition of nls_language, nls_length_semantics, _sqlexec_progression_cost.
- Removal of nls_length_semantics.
- Removal of SGA_TARGET from Sections 2, 3, and 4, as this is in the common parameters.
- Removal of db_block_buffers row from sizing table.
- Updates to "Specific Notes on Table."
- Updates to common parameters introduction.
As
we've noted before, these changes are extremely important and can have
profound impact on the performance of your Apps database. All Apps
DBAs should spend some quality time comparing your current database
settings with the latest recommendations in this document.
Related Articles
Comments (3)
Thank you for the update Prasad.
I have one question and one comment on these parameters.
First the question, is the use of AMM (memory_target) supported or recommended for use when running R12 on 11g? We recently went live on 11.1.0.6 using AMM but reverted back to ASMM (sga_target) due to performance issues in our custom programs. We have recently upgraded to 11.1.0.7 but have not tested going back to AMM.
The comment, for those upgrading from 11.1.0.6 to 11.1.0.7 remember to set all of the hidden parameters back to the recommended values. Interoperability Notes Oracle E-Business Suite Release 12 with Oracle Database 11g Release 1 (Doc 735276.1) does not mention it but you will find that the upgrade will reset these parameters and if you run your production without these parameters you will experience very poor system performance.
Posted by Joshua Hernandez | September 17, 2009 6:01 AM
Posted on September 17, 2009 06:01
Joshua,
Thanks for the comment. MEMORY_TARGET is not certified with EBS yet. Our architects would like to hold off on it until large workloads are run. Looks like it will be of less benefit for EBS customers unless they use it in virtualized environments.
Regarding the resetting of parameters, I will have it checked and updated in the interop note.
-Prasad
Posted by Prasad Akkiraju
|
September 17, 2009 6:17 AM
Posted on September 17, 2009 06:17
Hi, slightly off-topic but ...
The O/S requirements have changed from 11i -> 12 with regards to the ulimits.
the ulimit -s for 11i seems to be the same as for 10gR2 DB i.e ulimit -s => 32768
For Apps 12 the documentation has changed to ulimit -s unlimited.
This is causing me some problems on a Solaris 9/10 box as the stack is reserving 2G of space and in a JVM this leaves only about 1.7G for heap space. This size JVM is too small for some BI Publisher reports.
Is there a neccesity for ulimit -s to be unlimited ? If not can you recommend a value? . An SR has already been raised with Support (and Sun) but there didn't seem to be a definitive answer.
Thanks
dominic
Posted by Dominic West | November 18, 2009 4:00 AM
Posted on November 18, 2009 04:00