Error 3521: Improper Qualified Name (too many dots)

[kas]

Hello,

I am getting the following error "Error 3521: Improper Qualified Name (too many dots) when running a workflow that has been running just fine for a long time. It is a SQL query using a Vertica ODBC connection in an Input tool. Query is below. The query runs fine in DBeaver currently as well.

(

Select

edw_semantic_vw.sem_agreement_current_vw.agreement_nr,

edw_semantic_vw.sem_agreement_current_vw.pt1_kind_cde,

edw_semantic_vw.sem_agreement_current_vw.paid_to_dt,

edw_semantic_vw.sem_agreement_current_vw.agreement_status_cde,

edw_semantic_vw.sem_agreement_current_vw.agreement_status_reason_cde,

edw_semantic_vw.sem_agreement_current_vw.agreement_status_reason_nm

From

edw_semantic_vw.sem_agreement_current_vw

Where

edw_semantic_vw.sem_agreement_current_vw.agreement_source_cde = 'Vntg1' and edw_semantic_vw.sem_agreement_current_vw.agreement_status_cde not in ('Nb','Nr','Un')

And edw_semantic_vw.sem_agreement_current_vw.agreement_status_dt > (Current_Date - 100))

UNION (

Select

edw_semantic_vw.sem_agreement_current_vw.agreement_nr,

edw_semantic_vw.sem_agreement_current_vw.pt1_kind_cde,

edw_semantic_vw.sem_agreement_current_vw.paid_to_dt,

edw_semantic_vw.sem_agreement_current_vw.agreement_status_cde,

edw_semantic_vw.sem_agreement_current_vw.agreement_status_reason_cde,

edw_semantic_vw.sem_agreement_current_vw.agreement_status_reason_nm

From

edw_semantic_vw.sem_agreement_current_vw

Where

edw_semantic_vw.sem_agreement_current_vw.agreement_source_cde = 'Vntg1' and edw_semantic_vw.sem_agreement_current_vw.agreement_status_cde not in ('Nb','Nr','Un'))

Any thoughts would be greatly appreciated.

Thank you,

Kim

[apathetichell]

https://community.alteryx.com/t5/Alteryx-Designer-Desktop-Discussions/Error-3521/td-p/741501

[kas]

@apathetichell 

I saw that, thank you...doesn't answer my question.

[apathetichell]

put your db in quotes. it could be a driver/version difference.

[kas · Accepted solution]

Quotes weren't the answer...ungrouping the first part of the query fixed my issue...nothing else needed changing.

I solved my problem.

[NeoInfiniTech]

Hello @kas,

If you wouldn't mind, could you please also post the query here where the first part is "ungrouped"? Although I don't have much knowledge of Vertica queries, I would be interested in seeing what kind of structural change made to the query solved the issue and made it possible to run it in Alteryx.

Thanks in advance.

[kas]

@NeoInfiniTech 

Select

edw_semantic_vw.sem_agreement_current_vw.agreement_nr,

edw_semantic_vw.sem_agreement_current_vw.pt1_kind_cde,

edw_semantic_vw.sem_agreement_current_vw.paid_to_dt,

edw_semantic_vw.sem_agreement_current_vw.agreement_status_cde,

edw_semantic_vw.sem_agreement_current_vw.agreement_status_reason_cde,

edw_semantic_vw.sem_agreement_current_vw.agreement_status_reason_nm

From

edw_semantic_vw.sem_agreement_current_vw

Where

edw_semantic_vw.sem_agreement_current_vw.agreement_source_cde = 'Vntg1' and edw_semantic_vw.sem_agreement_current_vw.agreement_status_cde not in ('Nb','Nr','Un')

And edw_semantic_vw.sem_agreement_current_vw.agreement_status_dt > (Current_Date - 100)

UNION (

Select

edw_semantic_vw.sem_agreement_current_vw.agreement_nr,

edw_semantic_vw.sem_agreement_current_vw.pt1_kind_cde,

edw_semantic_vw.sem_agreement_current_vw.paid_to_dt,

edw_semantic_vw.sem_agreement_current_vw.agreement_status_cde,

edw_semantic_vw.sem_agreement_current_vw.agreement_status_reason_cde,

edw_semantic_vw.sem_agreement_current_vw.agreement_status_reason_nm

From

edw_semantic_vw.sem_agreement_current_vw

Where

edw_semantic_vw.sem_agreement_current_vw.agreement_source_cde = 'Vntg1' and edw_semantic_vw.sem_agreement_current_vw.agreement_status_cde not in ('Nb','Nr','Un'))

[NeoInfiniTech]

Thank you!

[apathetichell]

@kas - clarification though - your initial statement was that the query had not been changed and had been running "just fine for a long time" for prior to the 3521 issue. Is that not true? If it's true - what you did does not diagnose why the error would suddnely start popping up. That's what I was trying to diagnose.