Troubleshooting
Problem
DB2 Command Editor fails to start with error message: "Could not create the Java Virtual Machine"
Symptom
Could not bring up DB2 Command editor.
Cause
IBM_JAVA_OPTIONS and _JAVA_OPTIONS environmental variables get updated with HP Mercury Quick Test Pro Professional related variables, which replaced the default value for -Xbootclasspath classes, making it impossible to start the IBM JVM specified for the DB2 command editor.
Resolving The Problem
Check the environment variables: IBM_JAVA_OPTIONS and JAVA_OPTIONS.
If they have the following values, delete or clear the values of the IBM_JAVA_OPTIONS and _JAVA_OPTIONS environment variables and restart the DB2 Command Editor.
IBM_JAVA_OPTIONS= -Xrunjvmhook -Xbootclasspath/a:C:\PROGRA~1\HP\QuickTest Professional\bin\java_shared\classes;C:\PROGRA~1\HP\QuickTest Professional\bin\java_shared\classes\jasmine.jar
_JAVA_OPTIONS=-Xrunjvmhook -Xbootclasspath/a:C:\PROGRA~1\HP\QuickTest Professional\bin\java_shared\classes;C:\PROGRA~1\HP\QuickTest Professional\bin\java_shared\classes\jasmine.jar
Note:
In this case the solution of deleting or clearing these environment variables may impact starting some versions of the HP Mercury products mentioned or other products using them. If possible, these products should be started by passing necessary vm arguments directly on the command line or through the equivalent of some kind of "ini" file like Eclipse. More recent versions of the above HP products supposedly do not use the environment variables or at least not in this manner. HP Support should be contacted for complete up to date information or workarounds.
Related Information
Was this topic helpful?
Document Information
Modified date:
16 June 2018
UID
swg21517110