How To
Summary
When executing the OPCCBackup.sh|.cmd command line utility on a reporting server, you may see a warning about the "tools.jar file is not found". When using an Oracle database for the content store, you may also see the following error in the OPCCBackup command output when the content store is being backed up, depending on the version of Cognos being used:
"[exec] ORA-39006: internal error"
The error occurs when the Java that is being used is not a full Java SDK. Note that the Java that is included with newer versions of IBM Cognos Analytics is a Java Runtime Environment (JRE) only. When an Oracle database is used for the Cognos content store, the Oracle datapump utility that executes as part of the OPCCBackup command requires JAR files that are only available in a full Java SDK.
The warning about the missing tools.jar file can be safely ignored in a DB2-based environment.
Steps
-
Copy the java_8.0_64 SDK that applies to the operating system of the Reporting server from the OpenPages with Watson media onto each reporting server where the OPCCBackup and OPCCRestore utilities will be used; the java_8.0_64 SDK is located on the OpenPages media as follows:
Linux: ...\OP_8.2_Non_Embedded\IBM_Java\Linux64\java_8.0_64Windows: ...\OP_8.2_Non_Embedded\IBM_Java\WIN64\java_8.0_64 - Ensure that the new Java location is accessible by the user used to run the OPCCBackup command utility. The user must have read, write, and execute permissions on Java.
- Open the file <CC_HOME>/tools/bin/op-cc-backup-restore-env.sh|.cmd in a text editor and search for JAVA_HOME= . Replace the value with the location of the Java SDK, and save the file.
Document Location
Worldwide
Was this topic helpful?
Document Information
Modified date:
08 May 2025
UID
ibm16204125