DSXchange

Is this a temp table?
Why are you creating it in DS, any specific reason?
If i were you, i would convince the dba to create the table pre-hand. This way all you need to do is just load the rows and by-pass any such issues.

If doing this is SQL scares you then you can do it in DataStage, build a parameter file and then call the job by passing the parameters to it, via the parameter file. You can also build the date inside a job and within that job itself, in the transformer, call the second job that takes in the date p...

There you are Kumar......
Congrats to all of you guys, you guys are awesome.

chulett wrote:Substring at 10 so you just get the date portion. Use IConv only on that as the DB2 stage expects dates in internal format. See if that works.

That is your solution right there.

Well the error states that its violating the primary keys. You are getting a duplicate somewhere. How are you updating the table, are you trying to update one of the keys, like say the Date column. Also when the table contains data and you try to insert a record with allt he same keys present it wil...

Why me particularly? Because your everyone's favourite Actually you need to put the codes advised by our fellow forum users in a stage variable and for the last value specify a default value like say 'R'. In the constraint of your target you need to specify stgvar <> 'R' and in the constraint for t...

According to the sample data, it seems like the duplicates are to be detected on PLAN_ID. For that, i dont think the two columns need to be concatenated. Initialise svCountKey=0 svCountKey= If Plan_id=svkey OR @INROWNUM=1 Then svCountKey+1 else svCountKey svKey=plan_id I added @INROWNUM = 1 in Kris'...

Its a database error. Google 'ORA-03135' and you will get to the core of the problem.
Regards,

Kim, is just the master of the underlying repository.

I guess you will be better off writting a sed/awk script in manipulating your data.

All your schedules are stored using ControlM scheduling utitlity.
You will need to do a little research to find how and where the schedules are stored in unix.
Or someone might know the solution here.

You will have to unlock the table space.
DB2 usually locks the Table space if a deadlock occurs or the data size is more than the page size alloted. You might want to increase the page size for the table as well.
Consult your DBA for this issue.

The issue is with the permissions. You say that its working fine with the dsadm ID.

Probably the online manual developer missed it out .

There is documentation for Pivot stage.
You should have a folder structure on your desktop close to this:
C:\Program Files\Ascential\DataStage7.5.1\Docs and with in that folder there is a pdf named PIVOT.