DSXchange

mekrreddy wrote:...load into an ORCLE table ...

The database from Lord of the Rings. _

The fastname must be a genuine node name, ideally the one on the fastest connection to that machine. Do you really have a node called "a"?

LIST.READU (list_readu) is hard coded for 80 column output. The device width does not affect that. You can use LIST.READU INTERNAL to capture the data into a dynamic array and DataStage BASIC routine to format it however you like. In version 8 you probably really need to interrogate the XMETALOCKINF...

Not really.

Some will suggest some convoluted set of commands such as but I would not be one of them.

You can answer this question yourself. Ask yourself what is stored in the XMETA database.

You use Director for this. Status is Running (you can filter this) and sort by start time.

Welcome aboard.

This is one that only your official support provider can resolve. No-one here has a patch for 8.2 - as far as I'm aware that version has not yet been released (but I've been wrong about such things before). Check whether you have been sent a new license file that omits server jobs.

Excel has probably applied a "numeric" format. Use Format Cells to change this.

"Performance" data are stored in the RT_STATUSnnn hashed file for the job. Annotations are stored in DS_JOBOBJECTS and have repository IDs of the form VnAm (where n and m are integers). Column definitions imported as table definitions or saved from jobs are stored in DS_METADATA hashed fil...

My guess is that you have used this as a table name and no such-named table exists in the schema that you are using (possibly a default schema).

Check again that you have done this, particularly on the inputs to the Lookup stage. If you have, check that you have subsequently re-compiled the job.

Not really. What I wrote is clear.

If you're asking about the "certain requirements" these are documented in the ODBC API manual (from Microsoft) - in essence the worksheet must be in strict columnar form and have ODBC-legal column headings.

Could be... we just don't know.

So HAVE you set the Preserve Partitioning flag to "Clear" in the Lookup stage? In the stage upstream of the Lookup stage on each input?

You can not use an environment variable name directly as the third argument of DSSetParam(). DataStage BASIC does not recognize environment variables.