DSXchange

Welcome aboard.

Have you asked your support provider? IBM may have such a document that they may be prepared to share with you. If so, it is not a document currently in the public domain.

Had you used Dynamic RBDMS stages in the original design, anticipating this requirement, and were you 100% certain that the Sybase table and column name and data types exactly match the Oracle ones, then the answer could have been Yes. As it is, the answer is definitely No, for exactly the same reas...

Event ID is a sequential numeric integer. Obtain earlier event numbers by subtraction, perhaps in a counted loop with a -1 increment.
Don't go beyond 0.

Or simply print from Director (includes print to file capability) status view with whatever filter/view you require in place.

You should be looking in /apps/Ascential/Projects/edw_stage/RT_SC4334

Of course not. The query optimizer will disable the use of indices since a full table scan is required anyway (assuming no Filter is applied). Using indices in this case would only increase the I/O cost.

Actually an index on NAME may help if the current setting is sort by name.

Indeed that's the only way.

There are two example "tester" routines in the Repository that show you precisely how to do this.

0 means that the log is currently empty. Writes to the log are buffered, which is probably why you're not able to get log entries from within a short-running job.

You can (as root or dsadm) start the dsdlockd process without restarting DataStage, from the $DSHOME directory. nohup bin/dsdlockd > dsdlockd.log 2>&1 & You can also get dsdlockd to perform just a single probe by adding a -p option to the command line. bin/dsdlockd -p Try never to kill DataS...

U has not logged in for some weeks, so probably will not be able to give you anything. Neither is any of the remainder of the corpus of participants likely to be willing to give you anything, lest it does not meet your - at present unstated - precise requirement. Perhaps you could post your exact re...

No. Numeric data are stored in binary format. The zero-padding is irrelevant: it only becomes relevant when the number is converted to a string (perhaps only for the purposes of display).

Yes, but why would you? If you can match the file names with a regular expression you can read all files with a single Sequential File stage, using File Pattern as the method and the regular expression as the pattern.

There is internal corruption in your job design. Re-compiling it may correct the issue, otherwise I hope you have a backup (export) of the job design.

Restarting your DataStage server is the safest. A process ID (if that's what you mean by PSID) of 0 ought not to hold any DataStage locks - it suggests problems in the lock table itself. If you can post the relevant lines from a LIST.READU EVERY report then more targeted suggestions may be able to b...