Driver Error

[mithooooo]

Hi All,

I have following problem while loading data from source to target table using informatica:

1. I get this error: Database driver erro: wrt_8229 (Unique constraint violation). I set "Update else Insert" to fix this but
same error comes again! can someone help me how do I handle this. I also tried deleting all the rows that were violating this condition and tried to re-run the ETL. It throws the same error every time..."Unique Contrain Violation"... so some rows get loaded to the target table and most of them get "failed". (The target table already has some data)

2. My log file in workflow manager does not open (says "check space on disk) I tried cleaning most of stuff...but still the same!

Can you please guide me on how to proceed.

Regards

 

[blom0344]

1. Can this be something with referential integrity being violated? In other words is the table you are loading doing a reference to another table?

T. Blom
Information analyst
tbl@shimano-eu.com

 

[mithooooo]

My target table is a fact table and has five keys, which are not the keys for source table. There is only one source table and one target table(FACT table).

How should I proceed.

Thanks!

 

[blom0344]

Okay, regardless of the keys defined in the targettable. If you create an ETL mapping that writes multiple combinations
of the target-key to the target you will get constraint-errors, no matter how you define the strategy.

Your ETL mapping should be properly set-up to write unique combinations to the target, or else you may need to change the targets key.........




T. Blom
Information analyst
tbl@shimano-eu.com

 

[mithooooo]

Thanks for a prompt reply.

Should I write a SQL query in the Source Qualifier to say "Select Distinct values" only!

Can I do that...

 

[mithooooo]

I ran a query on my target table to find out whether the combination key has any duplicate rows and the query returned no rows which means there could be some other problem!

Can you please help.

thanks!

 

[blom0344]

Generally speaking, the granularity of the output of the mapping should match the primary key of the target table.

Example:

The target should store sales-revenue by customer,year,month.
The primary key of the target should be over three fields:
customer,year, month.

Your mapping should read from the sales-source tables (which will be more detailed, with sold items in it) To get the right granularity your mapping will do at least an aggregation step (with possible other transformations) to consolidate the sales data to the right level.

An insert/update strategy will then succesfully either insert a new combination or update an existing one...

T. Blom
Information analyst
tbl@shimano-eu.com