Netezza NZLOAD
Posted: Wed Aug 14, 2013 6:44 am
Hi All,
We are trying to load the netezza data base using Netezza Enterprise stage with load option defined as "nzload".
The load failed due to multiple reasons and below mentioned are scenarios.
Scenarion 1:
The metadata in the Netezza Enterprize stage in Set to VARCHAR with UNICODE option enable.
Then the job failed by throwing the below mentioned error.
Error:
Type mismatch for field 'DATA_SOURCE'. Fatal error.
Note: The metadata is imported from netezza database by using ODBC import option and the data is imported as VARCHAR(+) which sgnifies the UNICODE option.
Scenario 2:
Assuming a datatype missmatch we changed the metadata in the Netezza Enterprise Stage to VARCHAR with no UNICODE option enabled.
Then the job failed due to the below mentioned error.
Error:
Netezza_Enterprise_16,1: Error: RecordLength can only have INTERNAL reference to a zone.
Few of the reference from net suggested that NZ_DATABASE option if used it has to be modified, but we haven't configured any such option in our environment.
So looking out for solution which can possibly resolve the issue.
Thanks & Regards,
Sandeep
We are trying to load the netezza data base using Netezza Enterprise stage with load option defined as "nzload".
The load failed due to multiple reasons and below mentioned are scenarios.
Scenarion 1:
The metadata in the Netezza Enterprize stage in Set to VARCHAR with UNICODE option enable.
Then the job failed by throwing the below mentioned error.
Error:
Type mismatch for field 'DATA_SOURCE'. Fatal error.
Note: The metadata is imported from netezza database by using ODBC import option and the data is imported as VARCHAR(+) which sgnifies the UNICODE option.
Scenario 2:
Assuming a datatype missmatch we changed the metadata in the Netezza Enterprise Stage to VARCHAR with no UNICODE option enabled.
Then the job failed due to the below mentioned error.
Error:
Netezza_Enterprise_16,1: Error: RecordLength can only have INTERNAL reference to a zone.
Few of the reference from net suggested that NZ_DATABASE option if used it has to be modified, but we haven't configured any such option in our environment.
So looking out for solution which can possibly resolve the issue.
Thanks & Regards,
Sandeep