Solution : https://service.sap.com/sap/support/notes/692646 (Connexion à SAP Service Marketplace requise)
Mots Clés :
table size category /sapmci/ostore1 >= 8 /sapmci/[mdsclient]rel >= 6/sapmci/[mdsclient]10024 >= 6 /sapmci/[mdsclient]10191 >= 6 /sapmci/[mdsclient]10005 >= 5 /sapmci/[mdsclient]10009 >= 5 /sapmci/[mdsclient]10013 >= 5 /sapmci/[mdsclient]10139 >= 4 /sapmci/[mdsclient]11107 >= 4 /sapmci/[mdsclient]11108 >= 4 /sapmci/[mdsclient]1010 >= 3 /sapmci/[mdsclient]10117 >= 3 /sapmci/[mdsclient]10124 >= 3 /sapmci/[mdsclient]10132 >= 3 /sapmci/[mdsclient]10135 >= 3 /sapmci/[mdsclient]10138 >= 3 /sapmci/[mdsclient]10151 >= 3 /sapmci/[mdsclient]10157 >= 3, table size category /sapmci/[mdsclient]10136 >= 5 /sapmci/[mdsclient]10140 >= 4 /sapmci/[mdsclient]10141 >= 4 /sapmci/[mdsclient]10142 >= 4 /sapmci/[mdsclient]11100 >= 4 /sapmci/[mdsclient]11101 >= 4 /sapmci/[mdsclient]11104 >= 4 /sapmci/[mdsclient]11105 >= 4, sm51 -> select relevant instances -> goto -> queue info, namespace /sapmci/[tablename], size category, master data management content integrator installation, size categories, java memory management refer, schedule report rsxmb_restart_message regularly, 2 memory setting j2ee enginefor
Notes associées :
709053 | Solaris LWP library usage for SAP J2EE Engine |
634689 | Central Note for Memory Issues, SAP J2EE Engine 6.20 |
602256 | XI: Mass restarting incorrect messages |
563359 | Performance optimization for tables with LOB columns |
552522 | Java Hotspot VM Memory Parameters (hint outdated) |
384971 | System parameters for high interface load |
354080 | Note collection for Oracle performance problems |
314530 | Number of RFC/CPIC connections for external clients |
39412 | How many work processes should be configured? |