Troubleshooting
Problem
Collect the following MustGather information to help IBM Support troubleshoot problems when experiencing issues with ODBC or an SQL data source on an IBM DataPower Gateway Appliance.
Symptom
DataPower error messages such as:
"There are currently insufficient resources to start the SQL endpoint"
"SQL data source object failed to start"
"Starting DB connection failed"
"data source ID missing"
"There are currently insufficient resources to start the SQL endpoint"
"SQL data source object failed to start"
"Starting DB connection failed"
"data source ID missing"
Diagnosing The Problem
1. Describing the Problem:
- Specify the problem you are having with your SQL data source object; point out any error messages you see in the system logs or from another resource.
- If the problem is reproducible, include the steps you followed to reproduce the issue.
2. Collecting information to debug the problem:
- Collect a configuration export and an error report. Steps to collect this information are provided in the technote "Collecting Data: DataPower Gateway Appliances problem determination".
Note:
Enabling debug-level logging with the SQL endpoint configured causes a noticeable impact on DataPower performance, which is due to increased and enhanced diagnostics added which can impact resources. The debug log is still a valuable, even essential, tool, but do expect it to slow performance. - To enable additional tracing in addition to the debug log, open the SQL data source object on DataPower and add the parameter: "TraceFile" logtemp://<logfilename>.trace on the data source Configuration Parameters tab.
The Value field can contain any target file: logtemp://<logfilename>.trace or (if a crash could occur and off-box logging is preferable), dpnfs://<logfilename>.trace . But the Name field must contain TraceFile.
This TraceFile option causes a trace file to be created for each connection the SQL object initiates, and logs all data sent over that connection. This option has a small impact on DataPower over-head, much less than the debug logging has. - Gather any additional information which might not be contained on the device but instead on a remote SQL server (such as the product name and software version of your database application, and any errors logged there or any questionable behavior noted).
- Provide sample request and response messages for the one or more services affected.
- Depending on the problem, you may be asked to provide packet captures of the traffic entering or exiting the DataPower device.
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SS9H2Y","label":"IBM DataPower Gateway"},"Component":"General","Platform":[{"code":"PF009","label":"Firmware"}],"Version":"2018.4.1","Edition":"Edition Independent","Line of Business":{"code":"LOB45","label":"Automation"}}]
Was this topic helpful?
Document Information
Modified date:
20 October 2021
UID
swg21447477