DSXchange

Hi Chulett and Ray, thank you for your help. Unfortunately I can't see Ray's full entry because I'm no premium member (I know that's my own fault ;)). We made a workaround which doesn't really do exactly what it should, but it's enough for the job: We have a load_timestamp for the start of the main ...

Hi Chulett, what I need it for: I have a loop where I start a wait-for-file-job to see if the file is already here. Let's say they are named File1 ... File32. In my wait-for-file-job I compare the current date with the start date of the main sequence in order to guarantee that the whole searching pr...

Hi datastagers, in order to calculate the period of time between a fix timestamp and the current timestamp I would need something like a SecondsSinceFromTimestamp(fix_timestamp, current_timestamp) in my sequence job but unfortunately haven't found a good possibility to do that so far. Do you have an...

So that I have a lookup to check the date_from and then I have my two streams...a really good idea, I thought about corrective steps after the SCD2 steps, but I think your idea is the proper one. Thanks a lot!

Hi everybody, I have a little tricky case: Data can be valid on the basis of a month. So a record can be valid from 01.03.2013 to 31.12.2999 for example. CASE 1: changes in the same month of date_from If the record is created in March for example (date_from: 01.03.2013) and changes are made in the S...

We made an additional limitation for the data to work with and the error has never come again. So I agree with you, that it is a space limitation/performance problem. Unfortunately I have no access or answer from a db admin, which would have been very interestering and helpful for the upcoming proje...

It started on 23 February at 05:31 and the last log entry was on 23 February at 06:18. I stopped it on 25 February in the morning.

No, I've not talked to the DB admin or SYS admin so far but I'll try to reach them to test it and keep you informed.

Hi,
at the same time there's mostly running only this one job, but it can happen that it overlaps with two or three other jobs which end two or five minutes after the start of the problem-job.

Today it even doesn't finish when I start it manually without having done any changes in the job.

Hey,
they are all Oracle Connector Stages (database behind is Oracle 11g)

Hi everybody, there's something curiously going on in my datastage jobs: I have some (data intensive) SCD1-jobs with a lot of look ups. Most of the time they finish, but very often I have the last log entry for 6 o'clock when I check it at 9 o'clock and it should run approx. 1 hour. When I stop and ...

Let me show you an example how it should look like

Entry on 08.07.2012:
ID FROM_DATE TEXT
1 08.07.2012 A

Entry on 09.07.2012:
ID FROM_DATE TEXT
1 08.07.2012 A
1 09.07.2012 Ab (new entry)

ID + FROM_DATE = SK

Thank you for so many replies :) The concatenation is not really what I need, by saying "combined surrogate key" I meant that I have two fields which build together the PK. One is the ID (generated Surrogate Key Value) and another is the FromDate. As soon as I get a new data record with th...

Thank you for your ideas so far. @ jwiles: Yes, unfortunately I HAVE to use the same SK with another date because of foreign keys. That makes using the SCD stage not really simple. @ SURA: You mean a stored procedure where I check if an update happens and if yes, I keep the SK? I'm asking this (perh...

I'm not sure if I got you. The idea with the transformer afterwards sounds good but I'm scared it doesn't prevent from generating a new sk id within the scd Stage... It's not easy to handle :/

Hi everybody, due to foreign keys which I have to consider in my core dwh, I need a combined surrogate key which consists of the "surrogate key id" + the effective date. I have to realize that via the SCD stage of DataStage. I either get an error for violating constraints or too little dat...