IBM Support

Information Server parallel Job may fail at runtime because of data source column names and table names containing '#' and '$' characters

Troubleshooting


Problem

For Information Server Parallel engine, '#' and '$' characters are internally reserved characters. However, Information Server supports most of the cases where those characters are used in data source column names, and table names. All database "Connectors" stages properly handle such columns and table names, but this support may vary for the other type of Stages accessing databases that might be used. Caution should be taken especially when migrating Jobs from "Server" to "Parallel" engine. This article describes how Information Server handles these situations and if needed, what to do in the development phase to get this feature enabled.

Symptom

At runtime, parallel Job may fail with error message like :
----
Syntax error: Error in "pxbridge" operator: Error in output
redirection: Error in output parameters: Error in modify adapter: Error
in binding: Expected '=', got: "#", line 121
Error in binding: Expected '=', got: "#", line 146
Error in binding: Expected '=', got: "$", line 151
Error in binding: Expected '=', got: "$", line 152
Error in binding: Expected '=', got: "$", line 153
Error in binding: Expected '=', got: "#", line 155
Error in binding: Expected '=', got: "#"
.../...
====
Note that when such a failure occurs, the Parallel Job has not yet started processing any data.

[{"Product":{"code":"SSZJPZ","label":"IBM InfoSphere Information Server"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Component":"--","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"8.7;8.5","Edition":"All Editions","Line of Business":{"code":"LOB76","label":"Data Platform"}}]

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:
25 April 2025

UID

swg21590770

Page Feedback