DSXchange

Consider your nit picked.

The colon-number goodies are parameter markers. The number is the column number defined in the stage. So... :2 gets substituted with the value of the second column when the update runs.

Search this forum for your entire message and you'll turn up several discussions on the topic. As Ken mentions, you've specified at least one of your fields as being 'too small' in the OCI stage metadata, and OCI had to 'truncate' it to bring it back. Now, this can be a field declared as a NUMBER in...

Exactly! Write your own job control and have it do whatever you want. Another possibility: launch the job control job once and then, in a loop, run your polling job. Sleep for two minutes at the bottom of the loop. Lather, rinse, repeat.

Oh, and build some way out of the loop. Food for thought.

Obviously the error is in the shell script. Possibly, but not necessarily. If you are running on HP/UX, then simply using the Korn shell in DataStage can cause a core dump on some versions. I've seen this in the past where they ran fine in Dev or Test but started core dumping on the Production serv...

I got the the follwoin g similar results AccessTime : 32730 AccessDate : 13517 ModDate : 13517 ...etc Now, looking at above values , it does not make any sense! I do not know how to read , calculate and compare values!!! If you read the documentation on the STATUS command (which is in the Basic.pdf...

Kinda what I figured... but was hoping I was overlooking something to make the syntax a little easier to handle. Oh well.

There is a post on this topic in the FAQ Forum, which I'm sure a search would have turned up.

Plus it depends on which 7.x version you have. It's been around for awhile working a certain way but its functionality was 'enhanced' in the 7.5 release.

As Ray notes, it's all documented. Check it out, play with it in a job and then come back with more questions.

Either way should work. If you are generating the flat file data yourself, then you have the option of removing the offending characters on the way down - then it's not an issue for the job reading the resulting file. If you're stuck with sequential file data with line terminators in data fields, th...

No, you don't need to build an anonymous block to call the procedure, a simple 'call' statement is supposed to work. I don't make use of them but others have reported success here several times using that syntax. From what I recall, do it from the Custom SQL area, not the Before or After SQL tabs. T...

ADN is the Ascential Developer Network and is here. It is Ascential's official version of a site like this one and registering gives you access to their File Library.

You'll find the file in question is called DataStageBackup.zip in the Product Application category.

FWIW, I use it with a registered version of WinZip, which gives you access to WinZip's Command Line Interface. I hooked this into the backup script with the (off the top of my head) 'move' option in WinZip and so now instead of ending up with 15 exported projects taking up almost a Gig of disk space...

You quoted their requirements:

Sridhar G wrote:Can anybody give an idea on how to get the log for only the last run and not for the entire day.

Searching the forum will turn up lots of advice on this, including this post.

Usually, errors are 'detected' in your Transformers as they are the primary active stages in jobs. You'll need to post the actual error message before anyone can help you, however. You can also try resetting (not recompiling) the job after it fails and see if it puts anything in the log labelled as ...