Troubleshooting the Cognos® PowerCube data migration tool
If you encounter issues when migrating IBM® Cognos® PowerCube data to Elasticsearch in an IBM Connections™ deployment, refer to these troubleshooting tips or consult the IBM® Support database for recent tech notes.
Problem | Solution |
---|---|
Error: Could not find or load main class com.ibm.connections.metrics.cognos.cube.migration.CubeMigration |
Verify that the When you run the migration tool, start it from the migration_tool folder within the folder where you extracted the tool. |
Exception in thread "main" java.lang.NoClassDefFoundError: org.apache.log4j.LogManager at com.ibm.connections.metrics.cognos.cube.migration.CubeMigration.<clinit>(CubeMigration.java:35)Caused by: java.lang.ClassNotFoundException: org.apache.log4j.LogManager at java.net.URLClassLoader.findClass(URLClassLoader.java:609) at java.lang.ClassLoader.loadClassHelper(ClassLoader.java:925) at java.lang.ClassLoader.loadClass(ClassLoader.java:870) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:343) at java.lang.ClassLoader.loadClass(ClassLoader.java:853) ... 1 more |
Verify that the When you run the migration tool, replace Cognos_lib_path with the full path to the cognos folder. |
>>> Failed to connect cognos server |
The Cognos® server-related properties are not configured correctly. Check the log.out file for the detailed connection error. If you see the following error in the log, then verify that the config.ini
file contains the correct values for "CM-REQ-4342 An error occurred with the client ...<errorCode>cmAuthenticateFailed</errorCode>" If you see one of the following errors, then edit the config.ini file and
set the
|
>>> Failed to deploy cubes: -2 |
Check the log.out file for the detailed connection error: CM-REQ-4342 An error occurred with the client. If you see that error, then copy the MigrationPkg.zip file from the migration tool root folder into the Cognos_Install_Path/CognosBI/deployment/ folder. |
>>> Failed to deploy cubes: -3 |
First, check the log.out file for the detailed connection error: CNC-BAL-0503 The Server has failed.. If you see that error, then check the WebSphere® SystemErr.log/SystemOut.log file for the following error: java.lang.LinkageError: loading constraint violation when overriding method "javax/xml/soap/AttachmentPart.getDataHandler()Ljavax/activation/DataHandler;" during creation of class "org/apache/axis/attachments/AttachmentPart": loader "com/cognos/pogo/isolation/ParanoidClassLoader@ad6434f" of class "org/apache/axis/attachments/AttachmentPart" and loader "com/ibm/oti/vm/BootstrapClassLoader@27d079f5" of class "javax/xml/soap/AttachmentPart" have different types for the method signature If you see both errors, this indicates that your Cognos® WebSphere® Application Server profile is using JDK 8 instead of JDK 7 as required. Your JDK might have been upgraded inadvertently if you applied the WebSphere® Application Server ifix 8.5.5.14. Complete the following steps to revert the JDK to version 7 for use by Cognos®:
|
>>> Failed to connect ES. ES cluster status is IOException: Connection refused: no further information |
The configuration settings contain an incorrect host name/IP address or port for the
Elasticsearch server. Verify that the config.ini file contains the correct
values for the |
>>> Failed to connect ES. Exception is java.io.IOException: keystore password was incorrect |
The configuration settings contain an incorrect keystore name or password for the Elasticsearch
server. Verify that the config.ini file contains the correct values for the
|
>>> Failed to connect ES. ES cluster status is IOException: null |
The Elasticsearch server is not accessible. Verify that the Elasticsearch server's status is
good, the config.ini file contains the correct values for the
|