Troubleshooting tips for UNIX/Linux environment

Troubleshooting tips are provided for some of the common issues that might occur during installation of Sterling B2B Integrator.

Table 1. Troubleshooting tips for UNIX/Linux environment
Situation Message or Symptom Explanation/Resolution
Installing You encounter errors or problems during installation. Explanation

The installation creates several log files that you can use to diagnose problems like the failure of an installation.


Examine the log files generated during installation:
  • ant.install.log (in the <install_dir> directory)
  • /<install_dir>/PreInstallSI.log
  • /<install_dir>/InstallSI.log
Installing When you entered an absolute path during installation, a message indicated that the command was not found. Explanation

You entered an incorrect path. Check the information entered.


Enter the correct path.

Installing a desktop tool or resource
Cannot download any of the following:
  • Map Editor and associated standards
  • Graphical Process Modeler
  • Web Template Designer

When you install Sterling B2B Integrator, system files are created that contain an internal IP address. If you install Sterling B2B Integrator behind a firewall, and your firewall is configured to accept an external IP address from a client computer, you may not be able to download the desktop tools and resources. The firewall will reject the internal IP address from a client residing outside of the firewall.


Modify the system files that contain the invalid IP address. Follow these steps:

  1. Navigate to /<install_dir>/bin.
  2. Stop Sterling B2B Integrator.
  3. Enter the following command followed by the external IP address:
    ./ <external_IP_address>
  4. Restart Sterling B2B Integrator.
Installing Memory and ulimit errors. Explanation

The installation fails with memory and ulimit errors.


  • Refer to the Viewing and Editing Performance Configuration Settings in the Performance Management documentation. Modify your memory setting accordingly.
  • Refer to the Operating System Configuration Checklist and tune the ulimit settings.
e-Invoice Upgrade: Oracle Add Constraint Error When you upgrade Sterling e-Invoicing and are using an Oracle database, if the upgrade fails with the error message name is already used by an existing object, this occurs because the default behavior for the "drop constraint" command changed in Oracle 10. Explanation

The index that is used to support the constraint is now only removed if the index was generated by the create constraint command. The indexes for Sterling e-Invoicing are always generated from constraints during an install. If you receive this error during a Sterling e-Invoicing upgrade, it is because of how the database was restored, the version of Oracle you are using, and because the Oracle imp command exported the indexes and constraints separately. There is no way to determine when the imp command will not add a create index command to the export file if it was generated by a constraint – but if it does add the command, the database restore process loses the association of the constraint and its underlying index. The database script that runs during a Sterling e-Invoicing upgrade executes two steps: 1. First, it drops the unique constraint so the next step can redefine it using additional columns. However, the drop constraint command does not remove the underlying index if the association with its index was lost. 2. The next command that redefines this constraint requires a different index definition, but in this scenario the name of the index the constraint wants to use already exists, which causes the name is already used by an existing object error.


If you receive this error message, the solution for this problem is to drop the index and rerun the Sterling e-Invoicing upgrade. The drop index command you should use is: drop index UNQ_EINV_CANON

Apply a fix pack or Upgrade The /<install_dir>/installed_data directory is created (if clustered, on each node) during an upgrade or when applying a fix pack.

This directory can become very large and take up needed space on the file system.


The information in this directory is used when applying a fix pack or upgrading, but is not required afterward. The deployment/cleanup tasks for the upgrade or fix pack do not remove this directory.


The directory can be manually removed to increase the available space for the file system:
  1. Navigate to /<install_dir>
  2. Enter rm -r installed_data
Accessing the URL Attempts to access the URL for Sterling B2B Integrator display the message: Page cannot be displayed Resolution

See the information on Changes to Network Interface Bindings to update either the property file or the dashboard.

Cluster Installation Cluster is not working properly and your machine is running dual-stack - IPv4 and IPv6. Explanation

You can see the node went down from User Interface, but the node is running.


  • Find your iPv6 address in the /etc/hosts file and update file admin_host.2 = <IPv6 address>.
  • Edit file and modify the following:
    • Replace &HOST_NAME with the ipv6 address string.
    • Change mcast_addr=FFFF::
  • Run the ./ script to apply the changes.
Cluster Installation or Upgrade When configuring TCPS the following warning can be found in the activemqbroker.log: SunCertPathBuilderException: unable to find valid certification path to requested target. Resolution

Add the system certificate to the trust store using the KeyTool command.

Cluster Installation or Upgrade When configuring TCPS the following warning can be found in the activemqbroker.log: Invalid cipher suites specified. Resolution

Do not mention any SSL cipher in the ActiveMQconfig.xml.

Node status on a dual-stack machine Displays Node went down status in Node Status page, but the node is up and running. Explanation

Sterling B2B Integrator is configured using an IPv4 address on a dual-stack machine. The Node Status page displays Node went down status, but the node is up and running.


Modify the and files by completing the following steps:

  1. Identify the IPv6 address of the host machine from the /etc/hosts file.
  2. Navigate to the /install_dir/properties directory.
  3. Edit file and add the IPv6 address: admin_host.2 = <IPv6 address>
  4. Edit and modify the following:
    • &HOST_NAME=<IPv6 address>
    • mcast_addr=FFFF::<IPv4 address
  5. Run the ./ script to apply the changes.