When something unexpected happens during the migration process, you must enable java logging to further investigate the issue involved. The more detailed the log file is, the more convenient it is for you or the Support team to locate the issue.
To enable java logging, add the following line to the notes.ini file. There is no need to restart the Domino server.
Detailed migration log information is recorded in the Domino console log.
This section provides common issues you may encounter during migration process, and the corresponding solution to solve them.
com.filenet.api.exception.EngineRuntimeException exception when executing the qptool migration command
com.filenet.api.exception.EngineRuntimeException: FNRCE0057E: E_READ_ONLY: Method failed because an object or property is read-only.
The user specified on the command line does not have certain access rights on the object store.
Grant all permission access right on the object store to the user as described in Step 4 of the Preparing to migrate Quickr for Domino places to Connections Content Manager procedure.
- OOM Exception
java.lang.OutOfMemoryError exception when executing qptool migration command
08/05/2013 08:24:57 Agent error: JVMDUMP006I Processing dump event "systhrow", detail "java/lang/OutOfMemoryError" - please wait.
08/05/2013 08:24:57 Agent error: JVMDUMP007I JVM Requesting Snap dump using 'E:\IBM\Lotus\Domino\data\Snap.20130508.082457.3972.0001.trc'
08/05/2013 08:24:57 Agent error: JVMDUMP010I Snap dump written to E:\IBM\Lotus\Domino\data\Snap.20130508.082457.3972.0001.trc
08/05/2013 08:24:57 Agent error: JVMDUMP007I JVM Requesting Heap dump using 'E:\IBM\Lotus\Domino\data\heapdump.20130508.082457.3972.0002.phd'
08/05/2013 08:24:58 Agent error: JVMDUMP010I Heap dump written to E:\IBM\Lotus\Domino\data\heapdump.20130508.082457.3972.0002.phd
08/05/2013 08:24:58 Agent error: JVMDUMP013I Processed dump event "systhrow", detail "java/lang/OutOfMemoryError".
The java heap size can not satisfy the memory requirement of qptool process when running migration command.
To resolve this issue, increase the java maximum heap size setting in the notes.ini file. You can adjust the JavaMaxHeapSize parameter in notes.ini as follows:
In this example, 256M memory is specified as the java maximum heap size for all domino process, which is sufficient in most cases. If it still does not solve the OOM exception, you can increase the java maximum heap size to 512M, 1024M... and so on.
com.filenet.api.exception.EngineRuntimeException exception when saving document or creating folder during place migration
com.filenet.api.exception.EngineRuntimeException: FNRCD0009E: DB_ERROR: The database access failed with the following error:
ErrorCode -101, Message 'DB2 SQL Error: SQLCODE=-101, SQLSTATE=54001, SQLERRMC=null, DRIVER=4.13.127' ObjectStore: "ICObjectStore",
This message can be returned when an attempt is made to prepare or execute an SQL statement that exceeds a limit, such as a memory limit, an SQL limit, or a database limit.
Enable the amount of memory that is allocated for application requests to grow automatically by setting the APPL_MEMORY database configuration parameter to AUTOMATIC on the FileNet database FNOS & FNGCD.
Take the FNOS database, for example. The same procedures apply to database FNGCD.
- Open the Command Line Processor window. This launches the DB2 command line window.
- Connect to FileNet databases FNOS using the connect to FNOS command:
- Change the APPLHEAPSZ parameter using the update db cfg for FNOS using APPLHEAPSZ AUTOMATIC command:
- Check the modified parameter APPLHEAPSZ using the get db cfg command: