Administer > Transforming, loading, and extracting data > Overview of the mass load utilities > Configure the loading utilities
Configure the massextract utility
Before using the massextract utility you might want to change the following to suit the environment.
Procedure
- Change the Java Virtual Machine (JVM) heap size used for the massextract utility.
By default, the maximum amount of memory allocated to the JVM heap is 64 MB. If this is not increased, the JVM can eventually run out of memory during the extract process. The maximum amount of memory allocated to the Java heap can be varied by using the JVM -mx option in the Java command. If you are loading files that are more than 500 MB, then increase the JVM heap size to 512 MB or 1024 MB.
To modify the JVM heap size for the massextract utility:
- Open the massextract utility file located in:
- WC_INSTALL/bin/ massextract.sh
- WC_INSTALL\bin\ massextract.cmd
- WCDE_INSTALL\bin\ massextract.bat
- Change the JVM heap size to 1024 MB by specifying the -Xms and -Xmx options of the Java command:
- If the -Xms and -Xmx parameters are already specified in the file, change the values to the heap size that you want. Ensure that you update all occurrences of -Xms and -Xmx.
- If the -Xms and -Xmx parameters are not specified in the file, change all occurrences of %JAVA_HOME%\bin\java in the utility command file to %JAVA_HOME%\bin\java -Xms1024M -Xmx1024M.
- Save the changes.
- Optional: By default, the massextract utility uses the Oracle thick JDBC client.
To change the massextract utility to use the Oracle thin JDBC client:
- Edit...
WC_INSTALL/properties/OracleConnectionCustomizer.properties
- Locate the following text:
ConnectStringID = jdbc:oracle:oci8:@
- Change the text to match the following text:
ConnectStringID = jdbc:oracle:thin:@
- Save the changes.
Previous topic: Configure timestamp and date data handling
Related concepts
Overview of the mass load utilities
Related reference