DSXchange

No, not good. Go to the Administrator for the project and issue this: CLEAR.FILE RT_LOG1478 - that will empty it. Then use the Director to put back your 'auto-purge' settings in case it ever gets run again.

The other thing you can try is to touch into existence a file called errlog in the $DSHOME directory, when it exists special stuff is written there when there's a problem.

Sure you are attached to the right project? Using the right number? In a job, see if you can use a hashed file to view the contents of it.

Close, case is important and the jobno field is a string. Try: select * from DS_JOBS where JOBNO='1478';

Arnd, do you mean the &COMO& directory under the project?

Your understanding is exactly right, just wanted to double-check. Not sure what's up with this yet, I'll play with your code and see if any light-bulbs go off. :idea: In the meantime, I'd suggest adding breadcrumbs - calls to DSLogInfo() after each step with dumps of the information available at eac...

Bind parameters are definitely part of it. Post your sql and let us know what stage you are using.

Yes, you can but it does get a little 'tricky' and you need to understand all of the rules the stage enforces. Since you (more than likely) don't have a good way to bind the columns in the stage unless you're doing deletes in the merge as well - I'm assuming we're talking OCI stage here, yes? - I fo...

Welcome aboard. :D

First suggest, try searching here for a generic part of your error message. For example, an exact search for "appears not to be supported by code page" got a couple of hits, see if either one helps.

Yes, you'll need to change the jobs as you've noted and you could do it manually on the 8.x side if you like. Your other option is to find (on the 7.5.x client cdrom) the utility that will do it for you automatically. Should be somewhere under the "unsupported" folder, from what I recall, ...

ray.wurlod wrote:2. If it needs to be reset use dsjob command (-mode RESET) to run the job.

Since sometimes this confuses people, please note that a RESET run does not in fact run the job, it simply resets it. You must then issue a normal run afterwards to actually run it.

Well... as least we're finally at a Resolved status. Thanks for your perseverance, hopefully anyone stumbling across this same issue in SQL Server will make it all the way to the end and save themselves a lot of time. I've stashed this away in my Favorites on the off-chance I have the... pleasure......

If you've never been into the Windows Registry, you probably should get help from someone who has. You use 'regedit' to clean the registry by searching for and deleting anything for 'Ascential'... assuming no other Ascential tool is still installed after the DataStage client has been uninstalled. An...

What exact 7.x version are you running? And when you checked the Oracle client across servers, they are all exactly the same? Meaning all four values - 9.2.0.5 or 10.2.0.1 for example - are the same. Have you checked with your official support provider to see if there is a patch for this? It sounds....

P.S.: OT: can DS read directly from a pipe, i.e. directly from the output of a command, i.e. the Perl CSV written to stdout? Pipes and stdout are two different things, but yes the Sequential File stage supports both. The former by a specific Pipe read/write enabling option in the stage and the latt...