I found one instance of this error and the stated solution was to regenerate the OBIEE extract files which we did. We ran the Data Lineage load plan early this morning and it ran the SQL Parser step (6) correctly, but failed on the Dashboard source (step 8) - which at the time we had the dashboard extract from an incorrect version (22.214.171.124.1). I attempted a reload skipping the dashboard steps (to see if the other steps would complete), but it failed on the parser on run #2. We were then able to get the catalog installed at 126.96.36.199.0 and redo all the extracts, but it keeps failing on the SQL Parser with the following error:
ODI-1519: Serial step "DATA_LINEAGE (InternalID:4220174002)" failed because child step "Dimension_ETL (InternalID:4254366002)" is in error.
ODI-1519: Serial step "Dimension_ETL (InternalID:4254366002)" failed because child step "OBIEE (InternalID:4254367002)" is in error.
ODI-1519: Serial step "OBIEE (InternalID:4254367002)" failed because child step "SDE_DL_OBIEE_SQL_PARSER (InternalID:820843030)" is in error.
ODI-1217: Session DATALINEAGE_ETL_SDE_DL_OBIEE_SQL_PARSER (12341510) fails with return code 7000.
ODI-1226: Step Parse SQL fails after 1 attempt(s).
ODI-1232: Procedure Parse SQL execution fails.
Caused By: org.apache.bsf.BSFException: exception from Jython:
Traceback (most recent call last):
File "<string>", line 1, in <module>
File "<string>", line 56, in parse_sql
File "<string>", line 22, in parse_sql_query
AttributeError: 'NoneType' object has no attribute 'group'
I am stumped as to how it could have run once this morning, but since then keeps failing. We also cleared the directory and put re-regenerated extract files out on the server to ensure something wasn't stuck from an existing file.
Your question is OBIA specific.
I suggest you to move it to OBIA group.