DSXchange

We've been trying to log entries into a control file regarding a job including info. like the Calling Sequence We have a routine that is called at the beginning of each sequence and at the end to log the start and end of a Sequence Example design MainSeq RoutineActivity -> Insert Runnin into Control...

Hi We were able to solve the problem - after diggin in we realized that there some oracle modules that were not loaded correctly. main_program: Error loading "orchoracle": Could not load "orchoracle": 0509-022 Cannot load module /home/dsadm/Ascential/DataStage/PXEngine/lib/liborc...

We recently went thru with an upgrade of Datastage from 7.1r2 to 7.5.1 with any issues. Connectivity to DB2 is seamless. We now have to connect to Oracle9.2.0.1.0 as well We have been facing problems with trying to connect to oracle from datastage We have searched the forum for "like issues&quo...

Hi

It seems as though the dsenv we were using was corrupt - we replaced the existing one with a backup copy that we had created and presto - things worked fine

Will have to check the actual cause corruption in the dsenv file.

Can you do a netstat -a | grep -i fin Do you see any connections out there with a finwait2 status? If so, you will have to wait for the no -a | grep tcp_finwait2 value divided by 2 seconds to expire before these connections die and you can restart the service. I set this value to 60 for 30 seconds....

Hi After having installed Datastage 7.5.1A, we were not able to configure the plugin for the Oracle Enterprise Stage fro which we changed entries in the dsenv file and shutdown n restarted the engine a couple of times Subsequently(after having restarted the engine a couple of time) we have not been ...

In continuation Another diff between Use existing (Discard records) and the Overwrite option wud include: The schema file would be generated afresh with the overwrite option and that it remains as is in the case of Use Existing(Discard records). But then wont that also be done through the Use existi...

Hi Whats the difference between the Use existing (Discard records) and the Overwrite option in Filesets and Dataset According to the output I see the only difference is that overwrite create the fileset/Dataset if it is not already created without any warning while a warning is thrown in the latter ...

Where DO the rows go, given that you seem to be implying that they don't go where you expect them to? yes in my case when selector value are 2,1 then they are going to dataset label 2 when selector value are 3,10 then they are going to dataset label 1 so it is not behaving as I expected the input s...

That's correct for DataStage processes, because DataStage is a 32-bit client as far as DB2 is concerned. Environment variables for DataStage processes should be set in the dsenv script. Other client software that you may have may require 64-bit libraries. It's OK to have both in your shared library...

It's because - intentionally or otherwise - you designed your job to do that. You have not provided anything like enough information to enable anyone to diagnose this. For example, how many processing nodes are defined in the configuration file under which the job was run? Have you tested it with a...

Hi I am confused regarding the effect of defining multiple files in the Sequential stage as targets My current design is like this DB2 -> Sorter -> SeqFile NAME AGE ---------- ----------- ADARSH 23 AKSHAY 25 ADARSH 24 - 29 ADARSH 22 ANUP 22 LAMBA 34 ADARSH 27 - 23 - 24 adarsh 12 In the Sort stage I'...

After having installed DS 7.1r2 while running parallel jobs we have been getting the following warning persistently:

Failed to connect to JobMonApp on port 13401

Is it the APT_NO_JOBMON variable that has to be set to NO...if so do i do set in the dsenv file?

Thanx in advance

The Libpath in the dsenv must point to the 32 bit libraries, because DataStage is a 32 bit application The issue occurs when you try to execute a UNIX script connecting to DB2. In this type of script you must set the LIBPATH to the 64 bit library, because the UNIX system is seen as a 64 bit client ...

Looks like you are on a 64 bit UNIX server connecting to DB2. Is you DB2 instance a 32 bit or 64 bit database? DataStage is a 32 bit application and needs to have the links set to the 32 bit libraries. If you are trying to run UNIX commands (db2 or db2load) then the librarys need to point to the 64...