DSXchange

You must have missed the entire duplicate thread on this with the same recommendation and a request to delete this one, eh?

Silly Wabbit.

IBM Support identified that 9.2.0.5 Client to be one of the 'problematic' ones. However, not nearly as problematic as 9.2.0.1 which I was given 'accidentally' one day. Good Lord was that a mess until that little detail was discovered. IBM suggested upgrading the client to 9.2.0.6, which we did and w...

How much benefit is there to using a Distributed Hashed File in this situation? I've got a similar issue where multiple copies of a particular hashed file are being created by a MI job that mod's the input stream and distributes the result across the X hashed files. However, the final job that consu...

First tell us what you are trying to accomplish. Forget about the 'how you are doing it' part for now, that will come later once we understand the motivation behind the question.

I'm curious about this 'forecasted requirement' from your client. What exactly is this all for? How often does one need to 'deploy' a project? I know some folks have many projects, sometimes way too many in my opinion, but hey - different strokes. The need for new projects is pretty rare around here...

You reinstalled the server as well? Specifics, please. What exact version/flavor of Windows are you running? What exact version of DataStage? Are you installing both components, client and server, on the same machine? As Ray asked, can you highlight a job in Director and from the Tools menu get it t...

In your profile, you've ranked yourself as a 'fresher' as well. Sounds like you've got your work cut out for you.

Your company should seriously consider bringing in a professional instructor or consultant for this, or sending everyone to an official training class.

ray.wurlod wrote:My guess was slightly astray. In fact your foreign key references ORDID on the ORDERS table. Therefore your INSERT statement for the ITEMS table appears to contain an ORDID value that does not exist on the ORDERS table.

AHA!

Perhaps you should double-check with your Support provider? I doubt many people have walked your path yet...

It instructs it to bypass MTS and establish a dedicated connection. Dedicated = more resources at the expense of non-dedicated connections.

No stages. Scripts. DSExecute a sqlplus script with your 'bunch' in it from the Job Control tab. Or run them one at a time so that each can log their individual runtimes plus success or failure into the job's log. You can even wrapper them with DSLogInfo calls to be more verbose... Running script 1....

Actually, it was a guess on his part. There's not enough information to know for sure. And it's not about the ITEMS table directly, but rather some value in the record who's field is part of the noted FK constraint does not exist in the table being constrained against. A different table. For example...

Did you change anything else in your jobs or environment for this? If all you did was set this option in your tnsnames file and saw an immediate change, I don't see how they can assert that had 'already been setup' at the database level and it must be a DataStage thing.

Fault type is 10. Layer type is BASIC run machine. Fault occurred in BASIC program DSD.GetRTProp at address 258. As noted, what changed? A fault type of 10 is a SIGBUS or 'bus error'. We get them on H-PUX when running Korn shell scripts if the $LD_PRELOAD environment variable is set in the dsenv fi...

Dang... the jury will disregard the previous testimony.