DSXchange

hi_manoj wrote:Is there any way to read the table (not partition) in parallel execution mode,

Not if you're using the Oracle Enterprise stage. "Maybe" if you're using an Oracle Connector stage.

You missed the value comparison for the first Index() function. And you probably want "And" rather than "Or" if you want to exclude these records (it's not clear what you mean by "filter"). Index((to_transf._ID), "___Req",1) = 0 And Index((to_transf._ID), &quo...

My bad. You should have quoted the names in the LIST.ITEM commands. But the INSERT statements failed safe. Having made your changes, can you open the job in Designer? If not, what error message do you now get? Can you also find to who deleted RT_BP6487.O and castigate them severely? You might also t...

My bad. You should have quoted the names in the LIST.ITEM commands. But the INSERT statements failed safe. Having made your changes, can you open the job in Designer? If not, what error message do you now get?

Can you also find to who deleted RT_BP6487.O and castigate them severely?

Yes. Make an additional column in Table B that is a copy of the key and map that to the output.

The second person personal pronoun in English is spelled "you". U is one of our posters - it's a Burmese name.

This may be recoverable. Does RT_BP6487.O exist in the project directory? (It will be a sub-directory.) If it does, all you need to do is to re-create the VOC entries. INSERT INTO VOC (F0, F1, F2, F3) VALUES ('RT_BP6487', 'F', 'RT_BP6487', 'D_DSG_BP.O'); INSERT INTO VOC (F0, F1, F2, F3) VALUES ('RT_...

Open Director. Disable display of categories. Sort by status. Select the aborted jobs and adjust the window so that only these are showing. From the Project menu choose Print, within the print dialog choose print to file.

You can generate any value you need in an upstream Transformer stage. For a certain subset of functions, such as substring, you could also use a Modify stage.

Yes, that's how the Oracle Enterprise stage works, and indeed how the Oracle Enterprise stage is documented as working.

Have you updated the version of MySQL too?

This seems to be an error originating in Netezza. Please check the Netezza manuals for a description of this error. Also check (or have your UNIX System Administrator check) whether the process table on the system had become full.

It's not possible without a severe amount of hacking of the repository database. UniVerse version 9.6 did not support triggers on hashed files (this became available in UniVerse version 10.0 but, by that time, the DataStage engine had diverged from UniVerse). The only way to intercept updates to the...

Then it's almost certain that performing the join in the database - whether using SQL from DataStage or using a stored procedure - will be faster than performing the join in DataStage itself. If the SQL from DataStage is exactly the same as the SELECT statement executed by the stored procedure, then...