DSXchange

You DO have the ORACLE_SID environment variable set in dsenv, don't you?

Specified driver could not be loaded suggests that the branded_odbc library directory (or the third party ODBC driver's library directory) is not in the search path for libraries. This search path is stored in the environment variable LD_LIBRARY_PATH, LIBPATH or SHLIB_PATH, depending on which varian...

It's not really about languages, it's about character sets. With National Language Support (NLS) enabled, DataStage uses maps on all I/O to transform all incoming character sets into Unicode, and all outgoing data from Unicode into an external character sets. This does not, and cannot, perform trans...

Are you using read cache for the lookups? Can you split the input stream (maybe using a link partitioner stage, maybe using a Transformer stage), running the separate streams through separate Transformer stages which will run in separate processes thereby achieving "partition parallelism" as well as...

Welcome aboard! :D

Do you want to know about UniVerse or DataStage? They're no longer the same thing.

UniVerse (the database) is owned, developed and sold by IBM.

My mail client disables these when there's no next or previous item respectively. On DSXChange I find it frustrating to click View Next to be taken to a screen that reports that "there is no next item". Then ensues a frustrating backtrack to get back to the Forum Index. Can you please, next time the...

Here's a sanitized version. Apologies for the paucity of comments. FUNCTION DumpTableDefinitions(TableDefinition, OutputFormat, ProjectName, ProjectDescription, OutputFile, Delimiter, OpenMode, HeaderLine, IncludeNullable, IncludeDescription) $COPYRIGHT "Copyright (c) 2002, Ray ...

Welcome aboard! :D The good news is that there are no data types within DataStage. So, if your source data character string is in a valid timestamp format, you can load it straight in to a column whose data type is "TimeStamp". If your source data character string is not in a valid timestamp format,...

There's also been some recent - like in the past week or two - posting activity about an Oracle patch needed to prevent this (memory leak) kind of thing when 32-bit clients (which DataStage presently must use) and 64-bit Oracle. Might be worth chasing that up. Search the forum for "memory leak" and/...

The original poster specifed server job, and posted in the server-job forum. That answer was, therefore, not entirely helpful.

Version 7.1 server jobs (this IS the server-job forum) don't have the sequence generator stage to which you refer.

That is a server-job answer to a parallel-job question in the parallel-job forum. Please take more care!

As well as permissions, check for file system full where you're trying to write the trace file. ODBC traces can grow very large very fast!

@INROWNUM and @OUTROWNUM always accurately report the number of rows processed by the respective link. I think it is your expectations that are wrong. Merely because you send N rows out of a Transformer stage on a link is no guarantee that the database server will accept all N rows. Or, if you're wr...

Search the forum for "metadata mismatch". It's warning you that what's in your job design doesn't match what's in the table. If you make them match (e.g. by editing your job design) the warning goes away.