The aim of this Knowledge Base Article is to state the uses of the creation of .sapjvmrc file manually in the SAP JVM folder.
NOTE: Although creation of the .sapjvmrc file does help to do quick modifications on settings in the SAP environment, it is generally not recommended to use as this will overwrite all JVM settings. Any parameter additions to the .sapjvmrc file will take action everytime an SAP JVM is started from this location. Also other JVMs started from there will take the settings from .sapjvmrc. This file can't be placed somewhere else. The ideal option would be to create the JavaVM with some options, e.g. the Java heap settings, as this can also change in the future. Another point to note is that the sapjvm folder should not get overwritten by "sapcpe"; else you will have to copy the file to the source destination to make sure that it doesn't get removed at next startup.
However, usually there are no risks to apply the mentioned flags in this KBA on any productive system. This is just a pure supportability feature and detailed analysis.
- Release Independent
- SAP NetWeaver
- Business intelligence platform
-XX:+MallocStatEnableUafRecog -XX:+MallocStatUafRecogUseBackFence -XX:+MallocStatUseTrailingCushion -XX:MallocStatUafRecogBufferSize=2g -XtraceFileIoBasic -XX:+EnablePerThreadJavaIoInfoTracing -XtraceFile=<path to file> 2266011 exit code 67, com.sap.sql.connect.pool.Pool.start, SAP JAVA versions, SAPJVM versions, Deployment of queue
About this pageThis is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).
Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.