DSXchange

Sainath.Srinivasan wrote:Database level integrity constraints and commit intervals.

How is that ? Do you mean there is a configuration to be done ? Please explain.

Do you know which conditions can cause two nodes to lock each other ?

Also when there are many records, it creates 2 Oracle Session that are blocking each other...

Also tried that in the sequential mode, it's weird...

For each of these folders, check the remaining space using a df function

There are indexes

I noticed this lock when I browed the SGA trace :

TX - row lock contention

happens when i have more that just a few rows to update.

Does this ring a bell ?

I think it is more efficient to import the contents of the seq file using a single column and then dispatching with an import column stage.

Not very sure but you can call unix command in your routine.

From there you can run a command using sqlplus and thus running a stored procedure or a SQL statement.

Is it really compulsory to create so many jobs ?

ora_DWH_DIM_PRD_LOC_insert: When checking operator: When binding input interface field "PRD_LOC_NAT_COD" to field "PRD_LOC_NAT_COD": Implicit conversion from source type "ustring[max=30]" to result type "string[max=30]": --> In load/Append mode only (everythin...

Where does the data come from ?

If you want a powerful solution and you're using a DB, I strongly recommend to create a stored procedure function that will handle any possible depth.

From there call the stored procedure in a SQL statement in Datastage.

Also, this is the most efficient method to me.

Hello guys, I have a few questions regarding the CDC stage ? 1) As Suggested by Ray and others, it's better to split inserts and updates. So I use a switch stage after my CDC on the change code and redirect my data to two oracle stage to the same table. Is this okay to use Load/Append for inserts an...

Still slow...

I wonder if it would be nice to use a change apply stage to rebuild the whole data and then truncate/reload instead of inserting/updating. it seems updating is a huge pain.

What do you think ?

Please note that the source structure and ref structure must be IDENTICAL for the SCD stage to perform. So you might rename one of these columns to get names to match.

Hello all, I'm trying to implement SCD-Type 2 using SCD stage. (Version 8.1). Details: Source, Reference and lookup - DB2 tables source table has only one key column CUST_ID, generated by DB2. Reference table is not defined with any key column. But as per the business rule, If SourceTable.CUST_ID=R...

I don't know what to add. With an Oracle insert and a array size of 1 I don't see how a row could fail to go down the reject link. ... Thanks though. I've just made significant progress on this... in fact the "weird" characters and the oracle insert error are not linked... I've just seen ...