DSXchange

Hi Prasoon, The problem is that you have @INROWNUM in your key generation statement which always reflect the current record therefore you cannot restart the numbering for the reject table. What I would suggest is using inserting a transformer between the target table and the reject table like this: ...

That didn't really work, did it!

Hopefully, this will demonstrate what I was trying to say:

Input 1
TgtOra 1
RejOra

Input 2
TgtOra 2
RejOra

Input 3
TgtOra
RejOra 3

Input 4
TgtOra 4
RejOra


Cheers,
Bob.

Hi Prasoon,

Can you clarify what input and output you get from the pl/sql example and what DataStage is giving you so we can be clear as to what the problem is?

Something like:

Input TgtOra RejOra
1 1
2 2
3 3
4 4

Cheers,
Bob.

Hi Kannan, I would consider pivotting the data so you have it in the following format: 123,AB,StatusCode1 123,CD,StatusCode2 123,EF,StatusCode3 etc. Now your look up is simple. Send the success records down a link which performs a look up on the Id (123) back to the original data to determine if any...

Hi there, You could try something like this: (I've never actually had the chance to implement it....) It's less sophisticated than using build ops but might be more supportable in the long term. Source data: File name InputF44.txt Key Name Dob Type 1 Fred 01/01/1982 AB45 2 Dave 01/02 1974 TY76 3 Joh...

Hi there,

Have you tried launching a simple unix script to delete and recreate the surrogate key file?

Cheers,
Bob.

Hi there,

Have you tried launching a simple unix script to delete and recreate the surrogate key file?

Cheers,
Bob.

Hi John, It sounds to me like you wish to run a job where the end date is today and the start date is the end date from the previous run. I would store the end from each run in a table. Then when the job runs next time you can retrieve that value using a job which reads the table and writes it out t...

I don't know if you have fixed this one yet, but you could try something like this: (I assume that you have a database of 700m records to which you are trying add new records, but first check if they already exist and if they do, don't add them.) Firstly, you need to reduce the 700m records to a new...

Hi Julio,

I tried setting the job to UTF-16 but the result was the same, unfortunately.

Bob.

Hi Julio,

All columns are set to unicode as they are throughout the whole application.

I can't really choose which columns to set to unicode or not.

It seems strange to me that QS doesn't appear to handle utf-8 when it uses that code page under the hood.


Bob.

Guys, In order to process multi-national data our DS jobs are set to character set utf8 on the NLS settings tab for the job. I have recently changed the dsenv settings to reflect this as follows: NLS_LANG=AMERICAN_AMERICA.UTF8 export NLS_LANG # This entry can help with special characters LC_CTYPE=C....

Dear Mortals, Sorry if my first post wasn't clear, hope this helps! The output should look something like this, <Friends> <Owner> <Pr_Key> 1 </Pr_Key> <Name> Bob </Name> <Contacts> <Friend_Number> 1 </Friend_Number> <Friend_Name> Friend 1 </Friend_Name> <Friend_Number> 2 </Friend_Number> <Friend_Nam...

I am having a problem with repeating groups. I have read the various posts and the best practises document but I still cannot get it to work. I have reduced the exercise to a simple example whereby Friend_Name and Friend_Number are the repeating group for the name. The Friend_Number is defined as th...

Guys, I was wondering if anyone has seen this problem before? When I sign in to Administrator the NLS button is greyed out so I can't change the project default NLS setting. I have checked the credentials in SuiteAdmin and I am set up as DS and QS Administrator. I can change the job default NLS sett...