Skip to main content
  • EN

Hi,

Currently having issues with a Microsoft SQL Server source table writing to an Oracle12c destination. The package appears to run smoothly without errors, however when checking the destination every field is null. It has the correct number of rows at any rate, but absolutely no data.

Bit more in depth...I have an Oracle Data source that writes to my Oracle destination DB correctly, so I believe the writer is configured correctly. I have tried removing the Oracle destination and simply having the MS data source write to a CSV, which also works. When I try to use the CSV as a data source and copy it to Oracle, I once again receive all nulls.

Was wondering if anyone has seen this before and if they have a working solution. I'm aware Oracle likes Uppercase and Microsoft seems to enjoy lower case and I'm investigating that route now. Any help much appreciated.

Thanks

Hello @mefromcanada

 

 

As you stated, my first thought is the case of the attributes. You mention that the correct number of features are present in the database, the NULLS would be as a result of an incorrectly matching source to destination attributes.

 

 

Are you able to share a sample of your data? I wouldn't mind trying to load the data, to see if it is, in fact, a case issue. One test you could perform quick if you want to use the 'BulkAttributeRenamer' transformer to change the case to match. This would be a quick test to demonstrate if this is, in fact, the issue.

 

Let me know if that helps.

Answered my own question ;)

Ultimately it's capitalization at fault and the table to table copy was treating the fields of the same name as completely different fields. Opening up the source columns and manually mapping them to the destination columns corrected the issue.

Hello @mefromcanada

 

 

As you stated, my first thought is the case of the attributes. You mention that the correct number of features are present in the database, the NULLS would be as a result of an incorrectly matching source to destination attributes.

 

 

Are you able to share a sample of your data? I wouldn't mind trying to load the data, to see if it is, in fact, a case issue. One test you could perform quick if you want to use the 'BulkAttributeRenamer' transformer to change the case to match. This would be a quick test to demonstrate if this is, in fact, the issue.

 

Let me know if that helps.
Thanks Trent...just had to play with the mappings a bit. Going in with the viewpoint that case <> CASE led me to mapping the fields as if they weren't the same name. All good now

 

 

Reply


Community Stats

30,189
Posts
114,582
Replies
37,853
Members
Terms & ConditionsCookie settings
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.