DSXchange

Another way is to write the rows to a flat file and then load them via your databases load utility. You could then parse the load utility log file for errors/warnings/etc. The down side of this approach is that you have to significantly change your jobs and also implement extra steps. The upside is ...

Hi Ken, With regards to your questions I had gone thro the same problem long back. The resolution is. 1. Change your Version 5.1 to Version 5.2.1. I had tested with 1000+ jobs and it doesnt take time. Almost instant. 2. Also do remember of that too many folders inside datastage project impact the re...

Set up an extra output link to capture rows rejected by Informix. ---> Transformer -------> Informix | +-------------> SeqFile [Reject] Set the limit on this rejects link to 1. The job will abend as soon as the first rejected row is processed. HOWEVER... This is not best practice, as an aborted job ...

When you run the job, in the "Limits" tab, set it to abort after 1 warning. Keep in mind, however, how your Rows per Transaction setting will affect that behaviour. -craig lfrumke@sears.com wrote on 03/24/2003 11:56:18 AM: > Hi everybody, > > We are running DataStage 4.0 on Solaris. > We have a job ...

Hi, We have many big projects with the jobs split in categories (folders), usualy not much more that 10 jobs per categorie. However, our refresh rate is still extremely slow, and can take up to 40 seconds to refresh. We are running DataStage 4.0 on Solaris 2.6. Spliting the jobs overs many projects ...

There have been improvements over the years in shipment of meta data down to the DS client, but as I recall, most of those were related to enormous jobs in the DS Designer... not sure if those impacted the overall job list. It was certainly good to see, from Martis comment, the impact of folders. Ho...

Actually, this problem was acknowledged by Ascential via this listserv some months back. My feeling from the email was that the problem would be fixed in a later release. Im trying to track down the original correspondence of the problem. L *****E-Mail Confidentiality Notice***** This message (inclu...

Hi everybody, We are running DataStage 4.0 on Solaris. We have a job which inserts new or updates existing record on Informix database. Here is Transaction Group parameters: Isolation level - None Rows per transaction = 1000 On Fail - Rollback How can we make this job abend if sql fails? Thank you, ...

There is a case on the eservices website that references this behavior. We also ran into this issue, and it is related to the large number of jobs. There wasnt a workaround or fix, as I remember. At 10:00 AM 3/24/2003 -0800, you wrote: >I was curious as to hearing from anyone with a lot of >jobs in ...

Hi Ken, We have 500+ jobs in the same project...but have ours broken up into folders. Therefore the refresh time is small because its broken up for a single folder display. We are on Ascential Datastage 5.2.0.7 and Solaris 2.8. Weve never experienced a problem with slow refresh rates on our producti...

We have noticed the same thing. One of the biggest thing that we have seen is that when you have a lot of sequencers in your project it takes forever to export. My question is what is Ascential doing about it and has anyone suggested to Ascential that they fix the problem? -----Original Message-----...

I ran into the same situation on 5.2r1 on AIX. Our workaround was to split jobs among several projects, which you dont wish to do. That was actually the recommendation from Ascential. This worked fine for us as we could split our development projects based on sources, and once the jobs were imported...

I was curious as to hearing from anyone with a lot of jobs in a single project. Heres some of my observations: 1. 500+ jobs in a project causes a long refresh time in the DataStage Director. During this refresh, your Director client is completely locked up. Any edit windows open are hung until the r...

Any now you know why I recommended to Xiong to use sqlldr. If you produce an insert only file and an update only file, you have the flexibility to ship the data to any database. For what youve learned about the ORAOCI8 stage, youll have a different set of "rules" for each plugin. The OCI plugins hav...

This is a topic for an orphaned message.