Hi,
I ran into this issue with the ODBC stage. We use a single job to read different schema files and using RCP load it to different target tables( truncate and insert). Some of the schema files may have additional columns that are not needed in the target table.
On 8.1(our earlier version), the ODBC property "Drop Unmatched Fields" in schema reconciliation is set to Yes and the job runs fine.
The same job on 11.3 complains of the fields from input schema that are not present in the target table.
Is this a bug in 11.4? Has anyone experienced this behavior?
Drop Unmatched Fields - ODBC
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Version 11.3.1.2 is the most recent version available right now. Version 11.5 has been announced and is to be available to download later this month (Oct 2015).
There are at least 4 yes/no settings in the ODBC Connector stage to test out. Which ones have you tried? If they are not working as expected then contact Support.
There are at least 4 yes/no settings in the ODBC Connector stage to test out. Which ones have you tried? If they are not working as expected then contact Support.
Choose a job you love, and you will never have to work a day in your life. - Confucius