IBM Support

Collecting Data: reporting a problem with Decision Server Insights

Question & Answer


Question

You are having a problem with the IBM Decision Server Insights component. You would like to know what documentation you must collect (MustGather) so that the IBM Operation Decision Manager Support team can diagnose your problem. If you gather this documentation before you contact support, it expedites the troubleshooting process and save you time.

Answer

For expediting diagnosis of issues in the DSI runtime, it's important to provide to the ODM technical support teams the following information / data:
1. A clear description of the issue
2. A description of the cluster: the number of catalog servers, the number of containers, the number of inbound servers, and the number of outbound servers
3. For each host in the cluster, provide:
  •    The name and IP
  •    The type of VM if used
  •    The amount of RAM
  •    The amount of swap space
  •    The database and the exact version: Oracle® or DB2®
  •    The database hosts: name and IP
  •    The version of the SQL driver
4. WLP dump of all servers in the cluster:
     <dsi install>/runtime/wlp/bin/server dump server_name --archive=package_file_name.dump.zip
     For more information, see "Generating a Liberty server dump from the command line" in the Knowledge Center.
  
5. Generate WXS map data by running the following command from the /wlp/bin directory:
  ./xscmd.sh -c showMapSizes -cep hostname:port > wxsmaps.txt
     Where hostname and port are specific to the catalog server. The default is localhost: 2809. On Windows®, use xcmd.bat.
If the problem is related to memory or performance, provide also Verbose GC data, Heap dumps and Javacore dumps
6. When collecting WLP dump, add --include=heap option for extra memory Heap dump
  <dsi install>/runtime/wlp/bin/server dump <server_name> --archive=package_file_name.dump.zip --include=heap
7. Create a snapshot of the JVM status, by using server javadump command. Javacore dumps must be taken at the point where the performance problem occurs. Many issues can be identified by taking 3 or 4 Javacore dumps 30 seconds apart on each of the servers.

<dsi install>/runtime/wlp/bin/server javadump <server_name>

8. Retrieve Verbosegc data by adding -Xverbosegclog:/I2A/tmp/gc_%Y%m%d_%H%S_%pid.log to the jvm.options files.
Where /I2A/tmp is changed to an appropriate directory. You can also add <X>,<Y> to the end of the command to specify the number of files and the number of cycles in each file.
For example, the following option creates 20 historical files with 1000 garbage collections in each.
-Xverbosegclog:/I2A/tmp/gc_%Y%m%d_%H%S_%pid.log,20,1000
Once you collected the information, you can submit the diagnostic data to IBM support.

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSQP76","label":"IBM Operational Decision Manager"},"ARM Category":[{"code":"a8m50000000CcsxAAC","label":"Decision Server Insights"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.10.1;8.10.2;8.10.3;8.8.0;8.8.1;8.9.0;8.9.1;8.9.2","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
23 July 2021

UID

swg21978785

Page Feedback