Page 2 of 2
Posted: Fri Jul 27, 2007 7:20 am
by chulett
chulett wrote:Then you need to ascertain what changed yesterday. If not the job iteself, then what in the job's environment? Obviously, something did - the hard part can be figuring out what.
Ah... so it's only advice worth putting effort into when it comes from Ray, eh?
Posted: Fri Jul 27, 2007 8:57 am
by abhilashnair
chulett wrote:chulett wrote:Then you need to ascertain what changed yesterday. If not the job iteself, then what in the job's environment? Obviously, something did - the hard part can be figuring out what.
Ah... so it's only advice worth putting effort into when it comes from Ray, eh?
Hey Chulett, it is not like that...No offence meant by me...but the last thing we can think of is what you said at the outset itself i.e. env being corrupt..Anyway here it has happend..What caused such a serious error...I thought DS was quite stable tool and on top of it it is set up on UNIX platform.
Anyways....any solutions...we have 200 odd jobs in this env...will it all go for a toss...I dread even thinking of it
Posted: Fri Jul 27, 2007 9:22 am
by hema arvind
Hi Abhilash,
If no other option works, try releasing the job from manager.
Go to DS Manager.select the job,click on Tools -> release job
this would create a replica of the job.
we had it worked out when we faced the same problem.
just try out !!
Posted: Fri Jul 27, 2007 3:22 pm
by ray.wurlod
It's quite possible - likely even - that the difference is not in DataStage at all - it might be in the target database, or in the way that LD_LIBRARY_PATH is set up, or all kinds of things. More detective work is required.
Posted: Mon Jul 30, 2007 10:51 am
by abhilashnair
The whole project had to be exported and then reimported back. Luckily we lost no jobs in the process.
What caused this no one knows still?