A warning occurred while parsing SQL expressions of Database views or InfoSphere DataStage jobs

When Information Governance Catalog parses SQL expressions from Database views and InfoSphere® DataStage® jobs, warnings might occur.

By parsing SQL expressions, Information Governance Catalog updates metadata. It infers information about data flow between Database views and their base tables, and between InfoSphere DataStage jobs and the accessed data sources. In some cases, warnings are displayed while parsing SQL expressions. See the following sections for symptoms of the issue and solution.

Symptoms

The following examples show warnings that might occur when SQL statements are parsed:

WARNING
For Netezza Connector Stage "Netezza_Connector_2", cannot parse SQL: null
---
For more information, see igc.log and igc-admin-services.log files.

2015-06-09
      09:30:52,238 ERROR ConnectorProperties - Could not parse sql for stage:
      dstage.job4.ODBC_Connector_0 SQL: select a, b

Resolving the problem

In some cases, the warning message can be ignored. The following list describes possible scenarios, and suggests what to do next.

Using procedural statements: Procedural language extensions, such as PL/SQL, are not supported by Information Governance Catalog.; If you find such statements in the log files, you can ignore the warning.

Using statements that do not express data flow: The examples of statements that do not express data flow are DROP TABLE, ANALYZE TABLE.; If you find such statements, you can ignore the warning. The data flow analysis is not affected.

Using standard-based SQL statements: If you use standard SQL statements, or standard-based statements, for example SELECT FROM, or INSERT INTO, or UPDATE, and the warning occurs, it means that a syntax element is not supported by the parser.; Contact IBM support for adding parser support for such elements. Provide the igc-admin-services.log file from the server.

Using invalid SQL syntax: Standard SQL statements might contain invalid syntax elements, for example, a missing comma.; Check the syntax of your SQL statements for invalid characters, and correct all errors.

For information which stages in InfoSphere DataStage support lineage, see the InfoSphere DataStage and QualityStage stages that support lineage technote.

Missing base tables

Symptoms: In some cases, the SQL parsing is successful, but one or more base tables or base views were not imported into the metadata repository. The "Error linking view" error is displayed in the Lineage Information section of a database view details page. The view is not linked to one or more of its base tables.

Resolving the problem

To resolve the problem, complete the following steps:

Generate a list of all database views where SQL parsing succeeded but base tables were not imported. For instructions how to generate such list, see the Missing base tables after parsing SQL expressions of Database views technote.
Import all missing tables and views.
Force reanalysis of all dependent assets by clicking Detect Lineage Relationships on the asset type window.