DSXchange

We are running 9.2.0.3 right now. I'm curious about the 'major issues' comment you've made. Would that keep me from using the new stage or are these just Oracle issues, not something of concern to DataStage? In our brief time testing DataStage with 9.2.0.3, we discovered three different issues that...

Hello folks -- I apologize if this was asked before. I am attempting to write data from an Oracle table, formatted through several stages, and written as an decimal of (6,2) to output sequential file stage. The flat file is set as fixed format of 6 character long for this field. The value can be nul...

quote: Originally posted by shiva459 [br]Is there a way to modify the generated job control code for the sequencer so as to set the warnings limit to unlimited for the particular child jobs in the sequencer?. This may not be relevant to your question, but we utilizes the command line to run jobs. Wi...

quote: Originally posted by Ray.Wurlod [br]Try running the job using a smaller configuration (perhaps only two nodes) and monitor memory and disk space consumption. The scale-up factor to four nodes is approximately linear. To add to this, also ensure that your kernel is compiled with the configurat...

quote: Originally posted by kcbland [br]There is no conversion required by DataStage Server. If the source column has metadata as smallint and the target column has metdata of string, simply map the column over. The same is true for DataStage PX. -T.J. * * * ... now if this can make breakfast, my li...

quote: Originally posted by roy [br]Hi All, Is anyone aware of any issues regarding this upgrade? platform is Win NT DataCenter on Unisys macine DB SQL Server 2000. we use OLE DB and I heard that it was rewritten in version 6. any pitfalls to this updrage[?] You are better off waiting until Twister ...

quote: Originally posted by roy I always prefer treating warnings as a sign that something is "really" wrong and execution shouldn't continue. This would not be possible for PX jobs, where warnings are a dime a dozen. Here is something you could use for your Trigger: jobname.$JobStatus = #...

quote: Originally posted by etldw [br]Hi, I accidently made some changes to a datastage job and save the changes. Can I retrieve the previous version of that job. I don't have the version control stuff. The reason I'm asking, because I was told Datastage keeps a few version for each datastage job. T...

quote: Originally posted by dsproj2003 [br]Hi, I have a transfomer stage which has 'x' # of rows in input stream. There is no constraint on the transformer. Even then, the output is 'y' # of rows where y < x. There are no corresponding warnings/messages in the log file. The transformer stage automat...

The enviroment variable APT_RDBMS_COMMIT_ROWS can be set to a number equal to your desired commit rate. If you set it to 0, then PX will issue a single commit for all of the records being processed. I am fairly certain that this env var works with DB2, but I am not sure if it works with other datab...

Ray, One of the most important design rules is to limit sorts and hashes. Sorting and hashing are the mostly costly operations in PX because they almost always hit the disk. You can look in the temporary work space and watch it fill up with files during a sort or hash stage. However, you can contro...

However, when I try to use $ENV as a value for my environment variable $TARGET_UID, DataStage replies with the following message: Missing Parameters $TARGET_UID [$ENV] How can I use a "dynamic" environment variable that is being looked up during runtime? GetEnvironment() function does wha...

Hi All, I am using DS.TOOLS to clear the status file. The Datastage director shows the status as COMPILED. But when i view the log, new log messages are logged indicating that the job is still running. Also I am unable to compile the jobe from designer and the message given is that this job is stil...

Hey, thanks for the tip! I'll have to see if that helps me out on my platform (Tru64) as I was told by support that I had to wait for a 64bit version of the OCI9 plugin to be released before it would work for me. Nah. The problems we were having with Oracle9i and DS 6.0 was fixed with DS 6.0r1 rele...

If you set those users' inactivity timeout to, say, 60 minutes, then one hour after they leave their sessions idle they are cleanly logged out, nothing left locked. Hahahaha. "Cleanly." Hahaha. It took us 3 weeks to figure out what the heck was going on with the strange error messages. On...