Release Notes > Connector and connectivity issues > Db2 for LUW Database Ingestion Connector
  

Db2 for LUW Database Ingestion Connector

Fixed issues

The tables in this section describe recent fixed issues for Db2 for LUW Database Ingestion connector in Metadata Command Center. Not all monthly releases include fixed issues.
October 2026 fixed issues
Issue
Description
SCAN-41949
When you run a metadata extraction job on a DB2 stored procedure that declares a variable with the ANCHOR TO ROW syntax, the job fails with the following error: Parse error (NoViableAlt) on token
SCAN-41373
When you run a metadata extraction job on a db2 stored procedure that contains a SIGNAL SQLSTATE ... SET MESSAGE_TEXT statement, the job fails with the following error: Parse error (InputMismatch) on token: 'SQLSTATE'
SCAN-41169
When you run a metadata extraction job on db2 views that use double-dot notation with an omitted schema, the job fails with the following error: Parse error (NoViableAlt) on token '.'
SCAN-41056
When you run a metadata extraction job on a Netezza stored procedure that uses the AS keyword before a MERGE statement alias, the job fails with the following error: Parse error (InputMismatch) on token: 'AS'
SCAN-41005
When you run a metadata extraction job on a db2 view that references the built-in table functions MON_GET_LOCKS or MON_GET_CONNECTION, the job does not generate lineage for the view and fails with the following error: Cannot resolve MON_GET_LOCKS neither as a PL/SQL object nor type
SCAN-40690
When you run a metadata extraction job on a DB2 view that contains a condition that compares a comparison expression to an integer literal (for example, column > 0 = 1), the job fails with the following error: Parse error (NoViableAlt) on token: '='
SCAN-38604
When you run a metadata extraction job, the job doesn't extract stored procedures that use the LATERAL clause.
SCAN-38905
When you run a job to extract metadata of scripts or views that contain an inline Common Table Expression (CTE) within a subquery, data lineage is not generated and the following error appears in the job log: Parse error (InputMismatch) on token: 'AS'
SCAN-39340
When you run a job to extract metadata of stored procedures that contain the ^= operator, the job fails with the following error: Parse error (NoViableAlt) on token: '='
SCAN-40091
When you run a job to extract metadata of stored procedures that contain the (+) join operator, the job fails with the following error: Parse error (NoViableAlt) on token: ')'