DSXchange

gpbarsky wrote:But when I invoke the command from within a job, it fails.

Ok, now you get to explain what this means. What does "within a job" mean, exactly? Can you post the actual error/failure message(s)?

Specifically, the update statement is the problem child here as it does not bind all (assumed) seven input columns.

Your sql is 'fine' and running it in DataStage v. Toad won't change the behaviour. I would guess 'no data' when viewing would mean a metadata problem. How did you import the metadata for these tables? As an experiment, if you set all fields to Varchar, can you then view the data?

Search the forums for your exact error, it has been discussed here before.

Search the forums for your exact error, it has been discussed here before.

A hashed file key cannot be null, you'll see an error logged when you attempt to write one. Note that in a "composite" key, individual fields can be null but the entire key cannot be.

Because you used your own sql and didn't properly bind all columns. Searching for "not all variables bound" would reveal 30+ conversations on this subject.

SQL Developer != OCI. Is this custom sql? If so, please post it. That or try letting the stage generate the sql for you. ps. No limit on OCI stages, the limit would be a database configuration one as each stage represents a discrete connection to the instance. I would stick with one OCI stage whenev...

bmouton wrote:We can't get the XSDs right and there is not much documentation, tutorials, or classes that address this that we have sought.

Documentation on XML in DataStage? Have you gotten your hands on the XML Best Practices document that Kim Duke is hosting for us in his Tips section?

So... after every insert, delete all records from the table? Doesn't that defeat the whole purpose that this table serves?

Seems to me that's more of a 'gimp' than a 'cleanup'.

Can't help you but just wanted to point out - if you're going to use the BBCode tags for bold, italics (etc) then you cannot check/enable the "Disable BBCode in this post" option. You can edit your post and uncheck it so things appear as you meant. Or at least 'Preview' posts first so easily noted ...

Probably, however you've never said what database you are using. For example, an Oracle DATE field is actually a timestamp.

DELETE VOC 'Pointer Name' - and the quotes are required as far as I know.

I don't see why you would need to create any kind of pointer. Access the table directly.

What's a "joiner stage"? Please post your job design and the complete, unedited abort message(s).