IBM Support

Impact MySQL Data Source SQL returns null when using select as alias.

Troubleshooting


Problem

Sometimes when using a MySQL datasource in an Impact policy using DirectSQL, if the SQL uses the syntax:
SELECT COLUMN AS OTHERNAME FROM TABLE WHERE ...
The results see a null value returned, whereas if the SQL uses the syntax:
SELECT COLUMN FROM TABLE WHERE ...
The results contain the correct value.

Symptom

The expected results from the SQL are not received.

Document Location

Worldwide

[{"Type":"MASTER","Line of Business":{"code":"LOB77","label":"Automation Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSB2GF","label":"Netcool\/Impact"},"ARM Category":[{"code":"a8m0z000000bqcVAAQ","label":"Impact"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions"}]

Log InLog in to view more of this document

This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.

Document Information

Modified date:
09 May 2025

UID

ibm17161436