Troubleshooting the Quickr migration tools

Troubleshooting the Quickr migration tools
Problem Solution
This error message displays:
 com.filenet.api.exception.EngineRuntimeException: FNRCE0057E: E_READ_ONLY: 
Method failed because an object or property is read-only.
Problem: A com.filenet.api.exception.EngineRuntimeException exception occurs when running the qptool migration command.
Cause: The user specified on the command line does not have certain access rights on the object store.
Grant all permission access rights on the object store to the user as described in step 6 of Prepare to migrate Quickr for Domino places to Connections Content Manager.
This error message displays:
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"
Problem: A com.filenet.api.exception.EngineRuntimeException exception occurs when saving a document or creating a folder during place migration.
Cause: This message might 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 databases FNOS and FNGCD. For example, perform these steps for the FNOS database (the same procedure would apply to the FNGCD database):

Open the Command Line Processor window to launch the DB2 command line window.

Connect to the FileNet database FNOS using the command connect to FNOS.

Change the parameter APPLHEAPSZ using the command update db cfg for FNOS using APPLHEAPSZ AUTOMATIC.

Check the modified parameter APPLHEAPSZ using the command get db cfg.
For more information about the DB2 SQL Error: SQLCODE=-101, SQLSTATE=54001, refer to SQL0101N
The following messages display:
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".
Problem: A java.lang.OutOfMemoryError exception occurs when executing qptool migration command.
Cause: The java heap size cannot satisfy the memory requirement of the qptool process when running the migration command.
Increase the java maximum heap size setting in the notes.ini file. We can adjust the JavaMaxHeapSize parameter in the notes.ini file: JavaMaxHeapSize=256M.
In this example, 256M memory is specified as the java maximum heap size for all Domino processes, which is sufficient in most cases. If it still does not solve the OOM exception, we can increase the java maximum heap size to 512M, 1024M, and so on as needed.
The following sequence of messages displays:
NotesException: Notes error: The object store database is disabled.  (C:\DOCUME~1\bjliupf\LOCALS~1\Temp\eo41333748tm)

[24A8:0002-2220]    at lotus.domino.local.EmbeddedObject.NextractFile(Native Method)

[24A8:0002-2220]    at lotus.domino.local.EmbeddedObject.extractFile(Unknown Source)

[24A8:0002-2220]    at lotus.domino.local.EmbeddedObject.getInputStream(Unknown Source)

[24A8:0002-2220]    at com.lotus.quickplace.migration.FileNetUtility.saveFileNetDocument(FileNetUtility.java:1081)

[24A8:0002-2220]    at com.lotus.quickplace.qom.QPPlace$QDRoomMigration.migrateDocumentVersion(QPPlace.java:3068)

[24A8:0002-2220]    at com.lotus.quickplace.qom.QPPlace$QDRoomMigration.migrateDocument(QPPlace.java:3190)

[24A8:0002-2220]    at com.lotus.quickplace.qom.QPPlace$QDRoomMigration.migrateFolder(QPPlace.java:2802)

[24A8:0002-2220]    at com.lotus.quickplace.qom.QPPlace$QDRoomMigration.migrateRoom(QPPlace.java:2668)

[24A8:0002-2220]    at com.lotus.quickplace.qom.QPPlace.migrateDataToFileNet(QPPlace.java:1049)

[24A8:0002-2220]    at com.lotus.quickplace.qom.QPPlace.migration(QPPlace.java:1141)

[24A8:0002-2220]    at com.lotus.quickplace.api.QPAPIPlaceHandler.migration(QPAPIPlaceHandler.java:1589)

[24A8:0002-2220]    at com.lotus.quickplace.api.QPAPIPlaceHandler.handle(QPAPIPlaceHandler.java:255)

[24A8:0002-2220]    at com.lotus.quickplace.api.QPAPIPlaceHandler.handle(QPAPIPlaceHandler.java:96)

[24A8:0002-2220]    at com.lotus.quickplace.api.QPAPIInterface.handleAction(QPAPIInterface.java:306)

[24A8:0002-2220]    at com.lotus.quickplace.api.QPAPIInterface.traverse(QPAPIInterface.java:199)

[24A8:0002-2220]    at com.lotus.quickplace.api.QPAPIInterface.traverse(QPAPIInterface.java:208)

[24A8:0002-2220]    at com.lotus.quickplace.api.QPAPIInterface.traverse(QPAPIInterface.java:208)

[24A8:0002-2220]    at com.lotus.quickplace.api.QPAPIInterface.traverse(QPAPIInterface.java:208)

[24A8:0002-2220]    at com.lotus.quickplace.api.QPAPIInterface.traverse(QPAPIInterface.java:208)

[24A8:0002-2220]    at com.lotus.quickplace.api.QPAPIInterface.traverse(QPAPIInterface.java:177)

[24A8:0002-2220]    at com.lotus.quickplace.api.QPAPIInterface.process(QPAPIInterface.java:152)

[24A8:0002-2220]    at com.lotus.quickplace.api.QPAPI.process(QPAPI.java:223)

[24A8:0002-2220]    at com.lotus.quickplace.api.QPAPI.process(QPAPI.java:172)

[24A8:0002-2220]    at com.lotus.quickplace.qptool.QPToolCmd.run(QPToolCmd.java:387)

[24A8:0002-2220]    at com.lotus.quickplace.qptool.QPTool.run(QPTool.java:446)

[24A8:0002-2220] 05/13/2013 01:15:51 PM 10765 ERROR [main] com.lotus.quickplace.migration.FileNetUtility    - FileNetUtility: saveFileNetDocument, 
[ Failed to add attachment: A.pdf to document : A.pdf]
Problem: Failed to add attachment due to NotesException: Notes error: The object store database is disabled.
Cause: The attachment is stored in DAOS (Domino Attachment and Object Service), but the DAOS feature is not configured on current Domino server.
Enable the DAOS feature for the current Domino server as described in the DAOS Quick Start Guide.

The DAOS base path configure parameter in the DAOS Setting tab must specify the correct location where the actual attachment data is stored.

You only need to enable the DAOS feature for places that report this exception. Do not use the “-c” flag (copy-style compact) if you select option 3 mentioned in the guide as the way to enable DAOS feature on place, since it will move existing attachments out of the NSF and into the DAOS repository.
Parent topic:
Troubleshooting tips