DSXchange

PREVDTD is present only for deleted and not re-created objects.

Doubtless there is somewhere in the XMETA repository where this information is also kept, but I have not yet had the opportunity to analyze where this might be.

Possibly not, however, since it's notoriously difficult to run a BAT file on a UNIX system. The logic could be converted into a UNIX shell script however, and one would need dsexport to be available on the server machine.

I don't know for sure whether this will work in version 8, but it's worth trying.

CLEAR.FILE is probably safer than either of the repair utilities (uvfixfile or fixtool), for various reasons. Reinstate your log purge settings after clearing the log using the Director client.

Clear or repair the log hashed file. Search here for clues.

Search for the exact error message, which I would guess is about the NLS_LANG environment variable, but I'm not going to waste my time speculating. Post the exact error message and we'll be able to be more help, assuming that you don't find what you need when you search.

DS_CONNECT (which may be DS.CONNECT) can be executed through Administrator client Command window. It's an interactive environment so you will need to use the Response window there.

Does it really say "<unix error>" (sic) when failing to import metadata?

Insert then select is not permitted in the one stage or the one job (or, therefore, the one shared container) anywhere in a parallel job, because it is a "blocking operation" that thwarts pipeline parallelism.

Select Detail view in the Status screen in Director; the user will be displayed there. I believe (without checking) that dsjob -jobinfo command also gives the user ID.

Please post the exact and complete error message.

You can execute this command from the Administrator client's Command window. Be very sure that you have exclusive access to the project, otherwise your indexes will become invalidated.

There IS a limit with 64-bit hashed files, it's probably more than the operating system file size limit. The theoretical limit is 19 million TB (approximately) but that all has to be on the one file system. Please note also that UniVerse is a separate database product. The DataStage Engine has not b...

Rows per transaction is available when writing to the database, rather than when reading from it.

It's an informational message (connection open), not an error.