DSXchange

You don't have your ODBC connectitivity properly configured. If you search for 'uvodbc.config' you'll find there are two files you need to edit.

What happens when you try the Plug-In metadata via the OCI stage route?

[dedoop]

As long as the O/S provides support for 32bit programs, I'm sure you'd be fine. In the absense of a 64bit version of DataStage for the platform, of course.

As noted, there's absolutely no need for a 64bit O/S simply to have 64bit hashed files.

clarcombe wrote:Is there a command to remove the HF beforehand (unmkdbfile ?)

Yes, unmkdbfile is also known as 'rm'.

Or more specifically, for the entire directory and its contents:

rm -rf <directory>

Still doesn't really explain what you need to do or what exactly you mean by 'with different metadata'. Can you try again please? Perhaps with an example or three?

Possibly, but you don't need to as a relative path will work fine here. Meaning, specifing the attachment file without a path = in the current project.

Specifically, searching for DS.REINDEX should get you want you want. Also, what makes you think you need to reindex your projects?

7.5x2 on UNIX? I don't think so...

Interesting. An assertion error eh? That would imply something is very, very wrong under the covers. Basically, a coder asserts ('to state or declare positively and often forcefully or aggressively') that a certain condition is true and should always be true. In your case, that would be that "nP is ...

From the Administrator:

Multiple instance has no bearing on getting multiple records. Your sql is not correct, not sure what else to say.

Known behaviour - I believe you need to 'escape' the single-quotes by adding a 'backwards slash' in front of each one.

Sounds to me that the 'restartability' works just fine - it starts where it left off. What makes you say that the DPCR is 'not able to reset and then run', that also looks to me to have happened fine. Your issue is the DPCR job continues to abort, triggering your Exception and Terminator again. What...

When you do, please expand on what the heck you mean by 'dynamic sql in routines'.

I've tried to help. Twice now. Perhaps third time is the charm - leave the date in internal format and sent that to the DB2 stage.