DSXchange

kripakarprasad wrote:It gives out an error at the parameter declaration stage itself.

Then you probably still have them set to a Date type. This solution would require you to change them to a String as I noted.

One way to automate this would be by playing the old export-edit-import game.

If you are doing this before/after job via the ExecDOS subroutine (equivalent to ExecSH on a UNIX server, I guess) all you need is exactly the same thing you'd need if you ran it from the command line. Since your 'buyers.bat' file doesn't seem to need any parameters, all you'd put in the Input Value...

The Dynamic Relational Stage allows you to connect to any supported database with a single stage, which means you could (theoretically) swap out your underlying database and only have to change a single parameter to continue to use the same jobs. Reality is a harsh mistress, however, and it doesn't ...

Welcome! One way would be to not pass them in as parameters, but simply use SYSDATE - 1 and SYSDATE in your source query in their place. Problem is you have no way to 'override' those values when the job is run out of sequence. You could also setup two String parameters with the values you've listed...

In other words, it was a data issue? Or at least a metadata issue?

Please post exactly what the problem and solution was that you found, it will help others who come here with the same problem find a resolution.

Thanks!

Exactly. The update fails with the ORA-01401 which triggers the insert which fails with an ORA-00001. Fix the update issue so that it only 'fails' when there are no records with those keys to update.

No problem. Just wanted to make sure you were aware of the issue.

You might also let us know where the error is being generated. Are you using Custom Sql in any of your stages? That kind of error generally comes from improperly formatted custom sql more than any generated sql like the 'Insert then Update' example you posted.

How about your source stage?

gdean wrote:So, before re-indexing all the users should be out of datastage?

Yes - all users.

Read the BASIC pdf manual and the online help for examples. You can also search the forum for keywords involved in working with sequential files in BASIC - openseq, closeseq, etc. For example, this recent post discusses (in great detail) how the OpenSeq function works. You shouldn't have any problem...

That's the kind of message you would get if you tried to migrate the 'wrong way', i.e. from 7.5 to 6.

Please re-read my first post and provide more information so we can help you.

Vincent - this help?

We need the exact steps that you performed to be able to help, including the old and new version numbers plus the actual error message you are receiving. One thing - if all you did was export your jobs as a backup / precaution and then 'upgraded your server' with all of the old jobs still in place -...

Found something interesting. If I come here and have X number of unread posts, linking off to the DataStageExchange site resets my 'last logon' time and my unread count to zero. This is even when opening the other site up in a 'New Window'. When I close that session, the first time I navigate anywhe...

I have been using hash files with no problem when the relationship was 1:1. Looks like in cases where I have 1:N I am not getting all the possible records I need to get if I was trying to get an inner join. Is there a way to get the output from a 1:N relationship between stream and hash files ? No....