Administer > Transforming, loading, and extracting data > Overview of the mass load utilities > Configure the loading utilities

Configure the massload utility

Overview

Before using the massload utility you might want to change the following to suit the environment

By default, the maximum amount of memory allocated to the JVM heap for massload is 64 MB. If this is not increased, the JVM can eventually run out of memory during the load process.

The maximum amount of memory allocated to the heap can be varied by using the -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.

Modify the JVM heap size for the massload utility

1. Log on as non-root user.

2. Edit the massload utility file...
   WC_INSTALL/bin/massload.sh

3. Change the JVM heap size to 1024 MB by specifying the -Xms and -Xmx options

   • If -Xms and -Xmx are already specified, change values to your heap size. Update all occurrences of -Xms and -Xmx.

   • If -Xms and -Xmx are not specified, change all occurrences of...

     $JAVA_HOME/bin/java

     ...in the utility command file to...

     $JAVA_HOME/bin/java -Xms1024M -Xmx1024M

4. Save the changes.

Change the directory for the massload utility error log

By default, the massload utility writes the error log to either...

• The directory where the input file resides.

• WC_USER/instances/instance/logs

To change the location of the massload utility error log:

1. Edit the massload utility file...
   WC_INSTALL/bin/massload.sh

2. Change error report location setting:

   • If the parameter...

     -Dcom.ibm.wcm.ErrorReporterDir

     ...is already specified, change the directory to the new location for the massload utility error log. Update all occurrences.

   • If the parameter...

     -Dcom.ibm.wcm.ErrorReporterDir

     ...is not specified in the file, change all occurrences of...

     %JAVA_HOME%\bin\java %PM_ARGS%

     ...to...

     %JAVA_HOME%\bin\java %PM_ARGS% -Dcom.ibm.wcm.ErrorReporterDir= error_log_directory

   The directory you specify must exist. The massload utility does not create the directory for you. If the specified directory does not exist, no error log file is produced.

   If you have configured message logging for the massload utility, a DirNotExististException message is logged in the message log

3. Save the changes.

4. (Optional) Configure the MassLoadCustomizer.properties file.

Oracle considerations

For Oracle, the massload utility must be using the thick client during instance creation and the migration process. The bootstrap data gets processed during these processes.

(Optional) By default, the massload utility uses the Oracle thick JDBC client.

To change the massload utility to use the Oracle thin JDBC client:

1. Extract DbConnectionImplIDProperty.properties from the following file:

   WC_INSTALL/lib/loader/oracle/dbconnect.zip

2. Open DbConnectionImplIDProperty.properties in a text editor.

3. Locate the following text:

   ConnectStringID = jdbc:oracle:oci8:@

4. Change the text to match the following text:

   ConnectStringID = jdbc:oracle:thin:@

5. Save the changes.

6. Add the updated DbConnectionImplIDProperty.properties file to the WC_INSTALL/lib/loader/oracle/dbconnect.zip file. Overwrite the existing file in the archive.

Previous topic:

Configure the idresgen utility

Next topic:

Configure the MassLoadCustomizer.properties file

Related concepts

Overview of the mass load utilities

Related reference

massload utility (Server environment)

+

Search Tips   |   Advanced Search