<@U04S8PLJWMT> What does this error mean in a conn...
# replication-ask-ai
j
@kapa.ai What does this error mean in a connection builder stream? java.lang.RuntimeException: Uncaught exception of type 'STATEMENT_ERROR' on line 3 at position 0 : SQL compilation error: error line 99 at position 33 invalid identifier '""'
k
The knowledge sources you provided don’t mention this specific error message or a “connection builder stream,” so I can’t give a definitive, Airbyte‑documented explanation. From the pattern of other errors in the sources (all are database/SQL compilation or syntax issues surfaced by connectors), this looks like a SQL compilation error coming from your destination database, where the generated SQL contains an identifier that ends up being just
""
(empty double quotes). That would be an invalid column or table name, so the database reports: >
invalid identifier '""'
In Airbyte terms, this usually means: - The connector or normalization step generated SQL with a malformed identifier (e.g., an empty column name, or a name that got stripped down to nothing after quoting/escaping). - The error is raised by the database engine and then wrapped as a
RuntimeException
in the connector, similar to how other SQL syntax/compilation errors are surfaced in the logs in the examples you shared (e.g., MySQL and Postgres syntax errors). [[ASP normalization](https://discuss.airbyte.io/t/2670); [pg_stat_statements error](https://discuss.airbyte.io/t/3693)] Because there’s no direct reference to this exact error in the knowledge sources, I can’t say which connector or which field is causing it. To move forward, you’d typically: 1. Look at the full job logs around this error to find the exact SQL statement being run. 2. Inspect line 99 of that SQL to see which identifier is being generated as
""
. 3. Adjust the problematic field name (in the source schema or in the connection builder mapping) or open an issue with that SQL snippet so the connector can be fixed. If you can share the connector type (source/destination) and the generated SQL around line 99, I can help interpret it further, but that detail is not present in the current knowledge sources.