ajeet.singh on Saturday, February 18 2012, 03:18 PM

Netezza bulk Reader\Writer issue in Infomatica.

Hi,
I work on Netezza datawarehouse and i use Netezza bulk reader/writer for reading the source and loading the target tables.
I am facing a weird situation when i used a flat file as one of the target in mappings.
Scenario as like:-
1. Reading records from table by using Netezza bulk reader.
2. Having 3 targets in which 2 are tables and 1 is Flat file.
3. Both the target tables are having Netezza bulk writer and Flat file is having File writer.
4. Structure of mapping like:-
i) 1 target table (say T1) is directly linked from Source Qualifier.
ii) 1 target table (say T2) and flat file linked with filter transformation.
iii) Filter transformation is linked with Source Qualifier in which we are filter records based on some conditions.
5) Ideally the number of rows which are getting sourced should get loaded to target table T1.
6) And a subset of source table which satisfies the filter condition should get loaded in target table T2 and flat file. The table t2 and flat file should have same number as they are linked with same filter transformation.
7) The Actual behavior is like:-
i) File writer starts loading flat file the moment it encounter a row which satisfies filter condition but because of Netezza writer in other target table T1 and T2 nothing gets loaded at this point. This is expected
ii) But as soon as all the rows got read the Netezza bulk writer loads both table T1 and T2 table. Now the weird things is T2 loads same number of row which get loaded in Flat file (this is fine) but the T1 loads the number of row after rejecting around same number of rows which got loaded in Flat file. i.e. Total rows from source minus(-) (not exactly same) rows loaded in flat file.
I am not able to find any valid clarification for this behavior.
The important thing is that on using Relational reader/Writer in mapping the T1 table is not rejecting any rows.
Please advice on this unique behavior of Netezza Bulk Reader/Writer when it is used with Flat file.
Please note that the property “STOP ON ERROR” is set to 1 in workflow.
Any help on this will be highly appreciated.

Thanks,
Ajeet
Resolved
The discussion has been resolved.
Locked
The discussion has been locked.
       
  • 2
    Replied by saurav.mitra on Sunday, February 19 2012, 03:06 AM · Hide · #1
    Does the target table have constraints? If yes I think we need to disable constraint. Please check the session log and the reject file once more to get more insight on the issue.
  •  
  • 2
    Replied by sugsez on Monday, February 20 2012, 10:27 AM · Hide · #2
    Please check 2 things in the Netezza target property:
    1. Is there a possibility that the input data is containing the default delimiter character of the target? Try changing the default delimiter character
    2. By default ignore key constraint is disabled. Enable this if source is having duplicate records and you do not want to reject duplicate data while loading to the target...
  •  
  •  
    0
    Replied by ajeet.singh on Monday, February 20 2012, 05:50 PM · Hide · #3
    Thanks alot guys!!Issue got fix after enabling Ignore Key Constraint..
Discussions are now locked. You will not be able to reply to this discussion