Solution : https://service.sap.com/sap/support/notes/690241 (SAP Service marketplace login required)
Summary :
This SAP Note addresses the error ORA-04031 in SAP R/3 systems when running on Oracle versions from 8.1.7 to 9i or 10g. The error, associated with insufficient space in the shared SQL area of Oracle's shared pool, often occurs with large SQL statements optimized using RBO, featuring extensive inlists requiring significant memory. Recommendations include optimizing SQL statement performance with a switch to the Cost Based Optimizer to use the more efficient inlist iterator access path and increasing the SHARED_POOL_SIZE parameter. Implementing these steps can mitigate memory allocation issues, improving R/3 system stability and performance.
Key words :
shared pool size 4 500m 650m 6 1g 1g 10 1g 1, large sql statementsthe shared sql area, statement alter system flush shared_pool, library cachethe library cache includes, sql statements run multiple times, xcpus = cpu_countthe existing values, private sql areasoracle represents, automatic subpoolsin oracle 9i, users private sql area, large memory allocations require
Related Notes :
1472386 | ORA-04031 out of memory error in BW systems |
890797 | SAP TDMS - required and recommended system settings |
869006 | Composite SAP note: ORA-04031 |
830576 | Parameter recommendations for Oracle 10g |
789011 | FAQ: Oracle memory areas |
706132 | Composite SAP Note: Problems with Oracle 9i |
507254 | ORA-4031 and ORA-3113 when processing large IN lists |
505246 | Several ora-600 [12333] and ora-4031 errors |