DSXchange

You will have to put JobA within another Job Sequence and then use the looping logic with Counter value set to the ParamA value. That way, JobA will run as many times you want with the correct instance ID's.

Hope that helps.

dsusersaj wrote: You will get the 'Select List' property when you right click Table-->Add sub property-->Select List.

Aaah...there it is

Is the column you are trying to increment is a key column on that table or another regular column within that table? If its a regular column, you can lookup against your table and get the max value for that key and use a Transformer to increment the value before you load it into the table. If it's a...

It worked perfectly after that BUT for me to utilize an upsert in this manner on PROD would encur a large amount of work and redesign considering that most of the tables will have a portion of the update key as the PKey but not it in it's entirity. What this means is you are trying to insert duplic...

You would still need to correct your transform to properly handle the NULL's and avoid rejects in the future when the data comes in with NULL values.

If (IsNull(lk_trim_trans.doc_notes)) Then TrimLeadingTrailing(lk_trim_trans.doc_notes) Else TrimLeadingTrailin(lk_trim_trans.doc_notes) What you are doing here is trying to Trim the NULL which is not possible. Your transform logic should be If (IsNull(lk_trim_trans.doc_notes)) Then SetNull() Else T...

Are you saying that you are seeing records in the warehouse tables with duplicate keys in your table. That really seems strange. Can you please confirm that again and examples of some dummy data should help us answer you better.

Are you sure the 700 input records are distinct records? I would check that by putting a Remove Duplicates stage after your Funnel Stage. Usually, partial records get dropped when there is a key contention. As per the message file, I think it gets created only when your load job fails which is not y...

You can use Change capture stage without any problem as long as you partition and sort the data. You could also use Merge Stage and collect the rejects in a different link.

Netezza can handle much longer column names. The problem is not with netezza it might be with netezza plugins in datastage. Opened a case with IBM they are going to send a patch.

Is there any filename/tablename/columnname length limit for datastage.
We have a problem with columnnames exceeding 31 characters using netezza as database. Can anyone who faced this issue please comment how you resolved this.
Thanks
Kris

You can remove all the occurences of a character as follows:

This should help:

Do you have an explanation as to why you want to do it that particular way? Writing the query using where condition is efficient than reading all the rows and then applying the condition in the transformer stage.

Can you please post how you want your target data to look? From what I understand a full outer join should do.