JCo causes configuration failure on 32-bit UNIX


On a UNIX computer, the configuration tasks invoked by the SAP Solution Manager Setup menu command do not complete successfully, and the channel open error is displayed.

This error typically occurs when the Java Data Collector identifies the JCo on a 32-bit UNIX computer as 64-bit rather than 32-bit.

To diagnose and resolve the issue in calling the 32-bit JCo

  1.  Verify the architecture of the following components, whether 32-bit or 64-bit, as described in the following table: 

    Warning

    Note

    In this problem scenario, the OS kernel, JVM, and JCo are 32-bit, while the CPU is 64-bit. The SAP JCo must be 32-bit to match the OS kernel and JVM (but not the CPU).

  2.  If you get an error message when attempting to run the JCo (instead of a report of .jar specifications), verify the following issues (and, if necessary, perform the tasks):
  3. Set up a menu command trace (as described in Setting up a menu command trace) for the SAP Solution Manager Setup menu command of the SAP Solution Manager (SSM_SOLMAN) application class.
     After setting up the trace, select the SAP Solution Manager Setup menu command and perform the basic configuration tasks (as described in Configuring SAP Solution Manager systems and SAP satellite systems). Then verify that the following string appears in the trace:
    <Path to Java executable> -d64 -classpath
  4. After verifying that the OS kernel, JVM, and JCo are 32-bit (see step 1) and that the -d64 argument appears in the trace (see step 3), define the jcoBitType32 pconfig variable under /SSM/SYSTEMS/ (as described on page 56) with a value of 1.

The jcoBitType32 pconfig variable, set to a value of 1, disables the -d64 argument that the Java Data Collector was using to call the JCo in 64-bit mode.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC PATROL for SAP Solution Manager 2.3