August 6, 2009 at 2:07 pm
Symptom
When you peform a System Copy with SAPinst using the Migration Monitor for the import, the following error occurs during the database build phase.
The error can be found in the fileprep_build.log:
Info: Processing of tpl file using str files
Processing undefined
ERROR: Unable to open undefined
ERROR: OS error message: No such file or directory
Other terms
SAPINST 640 Patch [...]
July 13, 2009 at 2:29 am
Symptom
SAP JVM 6.1 Patch Collection 2 (build 6.1.003)
Solution
The SAP JVM Patch Collection 2 relates to the SAP JVM build 6.1.003.
It contains the following enhancements and corrections:
When parsing XML documents inside JAR archives using the DocumentBuilder.parse(String uri) method, the JAR file was opened from within the parser but never closed. Even using the usual [...]
July 10, 2009 at 5:37 am
Symptom
SAP JVM 5.1 Patch Collection 28 (build 5.1.040)
Solution
SAP JVM 5.1 Patch Collection 28 relates to the SAP JVM build 5.1.040.
It contains the following enhancements and corrections:
JIT compiler: Fix crashes in the JIT compiler while performing “loop unrolling” due to inconsistencies in its internal data structures (there were “dead nodes” in a tree representation [...]
July 2, 2009 at 8:31 am
Symptom
SAP JVM 5.1 Patch Collection 26 (build 5.1.037)
Solution
SAP JVM 5.1 Patch Collection 26 relates to the SAP JVM
build 5.1.037.
It contains the following enhancements and corrections:
When parsing XML documents inside JAR archives using the DocumentBuilder.parse(String uri) method, the JAR file was opened from within the parser but never closed. Even using the usual workaround [...]
July 2, 2009 at 8:27 am
Symptom
SAP JVM 5.1 Patch Collection 27 (build 5.1.039)
Solution
SAP JVM 5.1 Patch Collection 27 relates to the SAP JVM
build 5.1.039.
It contains the following enhancements and corrections:
Avoid crashes when using VM option “-XX:+DumpStackTraceOnSystemExit”.Improved traces for file open errors with ZIP files.CMS Garbage Collector: Corrected handling of marking stack overflows in the concurrent marking and precleaning phases, [...]
June 30, 2009 at 10:56 am
Symptom
You have defined a split mapping for which many messages are created as a result of the mapping. During the processing, the system generates the dump SYSTEM_NO_ROLL, which shows that the main memory is insufficient.
Other terms
Interface collection, MMF, split mapping, trace
Reason and Prerequisites
This is caused by an error in the source code.
Solution
Implement the [...]