DSXchange

You can string a series of commands together using a semi-colon as a separator. This is normal UNIX stuff.


Etc, etc. Works just fine like this in DSExecute or ExecSH.

Be curious if that's the case. Even though it wasn't said, I was working under the assumption that the SQL "runs fine in TOAD" or whatever the equivalent is for Sybase, and this was specifically a User-Defined SQL issue.

As noted earlier, the script you had in place sounds like it would work - you just need to make it a little more 'robust' so that errors are reported properly back to the script caller.

Check this post for the bits you missed when moving the VERSION project.

Well, one option would be to fix your job so it doesn't generate any warnings. I'd never consider running any job with unlimited warnings, way too many opportunities for trouble there. Have you tried unscheduling and rescheduling the job? Not really sure why you would be seeing the behaviour you are...

One option would be to not do this as User Defined SQL and see if it works. Other than that, there are a couple of things you could try for grins. One would be to remove the whitespace, the blank lines before the FROM and the WHERE clauses. I've seen times where simple stuff like that can 'confuse' ...

Suggest that you check out the CFF or Complex Flat File stage. It lives to process COBOL files and, with a proper FD to work with, can handle all of those data types automagically.

Search the forum if you have specific questions, it's use has been discussed here quite a bit.

There's no log created during Import that I've ever seen or heard of.

Have you tried resetting the job from the Director after it aborts? See if it then logs an entry labelled "From previous run..." and let us know what's in there.

ray.wurlod wrote:The downside is that now I've got nothing to add to what's already been posted on this thread!

Other than the fact that you've got nothing to add, that is.

I'm sorry, but how can you expect anyone to be able to help with so little information posted?

Please post the entire error message from the log. There should be some clue in there with regards to what it didn't like about the row it 'failed to read'.

I've worked with Oracle for years and don't recall ever seeing that particular message. For completeness sake, could you let us know what stage you are using to write to Oracle? An OCI stage? What type of field - VARCHAR2, NUMBER? Was there a mismatch in the metadata? Where was the 'truncation' happ...

Oh, perfectly well aware of what a Kalashnikov AK47 is - just wasn't quite sure of the relevance to the topic being discussed. And as we drift ever further from the dock... I guess the connection was short usernames. Not nice to poke fun at 'short' people. And you know Arnd has a soft spot for autom...

Still curious what the #PCDATA tag is supposed to mean.

D wrote:But Craig, my reply was (like my forum moniker) short and to the point

Yes, that it was. :D

Not sure what Ray and Arnd are prattling on about, however...