DSXchange

I did find a reference that notes to start with 1 node for every 2 CPU's as a rule of thumb.

I seem to be going around in circles with this. We are migrating to a 9.1.2 environment from 7.5.1 and I am looking for guidance on setting up logical nodes for the configuration file. We are running DataStage v9.1.2 on AIX 6.1 on a 6-way processor system with (say) 128gig that is connected to fiber...

I am in the same boat - going from 7.5.1 to 9.1.2. There is no direct migration path. Your best bet is to build a completely new 9.1.2 environment and use the command-line import command for the individual projects. You may find that you have to run a fix on your 7.5.1 projects (research OCI8TO9.B)....

I am planning on migrating from 7.5.1a to 8.7. There is a requirement for 8.7 that states you have to be at AIX 6.1. - So yes, you have to go to v6.1 first before you can install v8.7. DS 8.5 is supported under AIX v5.3, but like the posts say, there is not an inplace upgrade to get to v8.7. You hav...

Hi, We are running DataStage v7.5.2 on an AIX v5.3 platform. The development staff has a new requirement to read remote files (I do not know the details). In doing some research it looks like I can either 1) Use NFS to map a remote file system and have DataStage access the file as if were local. 2) ...

The Version Control trail is: -Initialize from Development -Promote to QA -Promote to Production Definitely nothing is getting promoted back down to Development. The specific development group does not have Version Control on their machines, no one else has access to the server, and I am the only co...

Hi, I have to initialize jobs into Version Control (I administer the toolset but am not a DataStage Developer) for an offshore team on a regular basis. On occasion, I will get an email back from the group that the Source Job in the Development Project has been set to "Read Only" mode. The ...

Done, now I can get back to my overly complex data warehouse modeling project. :D

Since it's client based, it doesn't matter where any given project is located. Connect to the Version Control repository on your original server like normal, then when you promote change the 'Host system' value in the 'Attach to project' dialogue box. The first time you'll need to actually type the...

:? This change shouldn't change your process at all, other than the fact that when you promote to Production, you'll point to the new 'partition'. ... Even though my Production project is in a different instantiation of DataStage that is essentially on a different machine? I must appologize because...

Hi, Factoids: We have had 1 DataStage (7.5.1a) server environment setup that contains production, qa, version control, and development projects. This DataStage environment is on an AIX machine (5.3) and runs on one of the four partitions defined on the machine. I administer the "Ascential"...

Hi You need to find out if the problem is really due to your database. First thing to do would be to swap out the database stage that performs the writes to writing out to a dataset (or even a sequential file). If the job performs well writing to files or datasets then you have a database performan...

Hi, We seem to have a situation brewing that is causing jobs to run critically slow. By that I mean I can see database activity related to inserts running around 15 per minute. I would expect tens of thousand's of inserts per minute. This has only recently started and is somewhat rare. We are on 7.5...

Added to the wish list. Tanks for pointing that out - I adminster the Ascential product line but don't develop DataStage jobs, so I am rarely in here. I design, implement, and maintain databases - and help the DS Developers.

Here is the issue: DataStage allows you to run the DB2 LOAD command with full knowledge that tables can go into a check pending state because of the command. Yet, apparently DataStage does not provide a solution to this common issue. There should be a simple method of running a set integrity command...