Check the spelling of the referenced table and column error.

[venkataramana_paidi]

Hi ,

I am implementing the SCD 2 on employee table.   While executing the job it is throwing the below error.  But it is not showing which field spelling is wrong or not existed. It is showing just Column <> only.

SESSION JOB_IU_CIVIL_D_EMPLOYEES_SCD|DATAFLOW DF_IU_CIVIL_D_EMPLOYEES_SCD|STATEMENT <GUID::'04babb3f-f9f6-4251-a5df-c0c5cb2bbda4' QUERY TCConvert_1>

Column <> was not found in table <QT_GET>. Check the spelling of the referenced table and column and ensure that the table  exists and such a column exists in the table.

Please help me to resolve this issue.

Thanks & Regards,

Ramana.

[venkataramana_paidi]

I think somehow by mistakenly I removed the natural key from the QT_GET output schema after table comparison transform mapping . Due to this, I was facing the issue. Now that issue got resolved.

[former_member198401]

Excellent!!

[former_member198401]

Ramana,

Please close the thread...

[akhileshkiran]

Hi

In some cases the Data Services is having the Case Sensitive Issue with the column names. Can you please check if you are using the source as Template Table. Check the Template Table Target in the previous Dataflow and Update the column name to CAPITALS or based on your Final Target Table Structure.

Regards,

Akhilesh Kiran.

[venkataramana_paidi]

Some of my field names in the source & target are different. Is there any issue with this.

[venkataramana_paidi]

Hi Akhilesh,

Thanks for your response.  My source tables & target tables having different field names like empname in the source  and emp_name in the target like that. Is it make any issue for this error.

Thanks & Regards,

Ramana.

[akhileshkiran]

Hi ,

The Primary & Compare Column Field names in the Table Comparison need to be same. Or else  you will get error.

In the below STOREKEY is the column from Source and this is like STORE_KEY in the Target Table. Rename the filed in the Query Transform as same structure in the Target Table before any TC.

Regards,

Akhilesh Kiran.

[Former Member]

Can you post the TC screenshot? Will get an idea what went wrong.

[venkataramana_paidi]

[akhileshkiran]

Hi ,

If you get any Validation Error. 

Take a New query transform before Table comparison and rename the source columns according to the Target Input fields.Please post the validation error if possible.

Regards,

Akhilesh Kiran.

[Former Member]

I could see a mismatch in the primary key name.

please have a look to this link.

[venkataramana_paidi]

Hi Pravi,

In the key column list, primary key is the natural key from the source.  Key column from generated key column is the surrogate key from the target.

Thanks & Regards,

Ramana

[former_member198401]

Make sure that the column names in Query Transformation QT_GET in your job contains exactly the same name as in the Target table.

[Former Member]

Can you post the screenshot of your query ?

[venkataramana_paidi]

Hi Pravi,

Please find the below screenshot.

Without table comparison , I mean normal flow working fine. If I am using SCD flow then only throwing this error.

Thanks & Regards,

Ramana.