This page explains how to manage the "Could not reserve enough space for object heap" DMT error message that occurs during any Database extraction.
This error means that there is not enough available free memory to perform the browse or the extraction.
Release | Yes/No |
|---|---|
| 8.0.x |  |
| 7.3.x | |
| 7.2.x | |
| 7.0.x |  |
RDBMS | Yes/No |
|---|---|
| Oracle Server | NA |
| Microsoft SQL Server | NA |
| CSS2 | NA |
| CSS1 | NA |
When the customer tries to browse the schemas he wants to extract, if the JVM Memory Size value is too high, the below issue occurs:
In the Browse.castlog2 log file (in the delivery folder), we can see the messages below:
2014-11-07 10:24:09.460 DETAIL Error occurred during initialization of VM
2014-11-07 10:24:09.463 DETAIL Could not reserve enough space for object heap
2014-11-07 10:24:09.465 DETAIL Error: Could not create the Java Virtual Machine.
2014-11-07 10:24:09.467 DETAIL Error: A fatal exception has occurred. Program will exit.
2014-11-07 10:24:09.469 ERROR Error running CAST database extractor!
2014-11-07 10:24:09.472 ERROR An error has occurred during command processing
com.castsoftware.util.logger.exceptions.LogException:
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(:0)
- The solution is to reduce the JVM Memory Size, for instance from 1G to 500M:
No impact on the analysis result. The extraction will take more time to be done.
Reference Webcall : 29531
