Cannot open executable job file RT_CONFIG623

Sandhya.Arumugam · Post by **Sandhya.Arumugam** » Mon Apr 17, 2006 5:46 am

Hi,

whenever I open data stage director,I got one error for one job.I am unable to understand this problem.the error is

Can not open the executable file RT_CONFIG623

Thans in advance,
Sandhya

kcbland · Post by **kcbland** » Mon Apr 17, 2006 7:17 am

Use DS.TOOLS to repair the repository. Search the forum to learn how to access it.

DSguru2B · Post by **DSguru2B** » Mon Apr 17, 2006 8:00 am

Also try exporting and importing the job again.

mahi_mahi · Post by **mahi_mahi** » Mon Apr 17, 2006 9:44 am

DSguru2B wrote:Also try exporting and importing the job again.

But how do we know RT_LOGnnn belongs to which job?
Where can we find the information?

kcbland · Post by **kcbland** » Mon Apr 17, 2006 9:46 am

To find out a jobs internal number, you must look at internal file DS_JOBS. Search for help on that.

kcbland · Post by **kcbland** » Mon Apr 17, 2006 9:47 am

Of course, once you're already there to find out the jobs number, you could just run DS.TOOLS and be finished.

DSguru2B · Post by **DSguru2B** » Mon Apr 17, 2006 1:56 pm

mahi_mahi wrote:But how do we know RT_LOGnnn belongs to which job?
Where can we find the information?

It can be found out by using Kcbland's way, moreover I think it would be obvious that the job which is giving the problem is showing up its RT_CONFIG.

ray.wurlod · Post by **ray.wurlod** » Mon Apr 17, 2006 3:17 pm

This is unrelated to RT_LOG623 and is unlikely to be corrected by anything in DS.TOOLS.

Search the forum for this particular error message (leave off the particular job number). It has been fully explained in the past. You have a corrupted RT_CONFIG623 hashed file here.

kcbland · Post by **kcbland** » Mon Apr 17, 2006 3:51 pm

Methought there was a repair repository files under the DS.TOOLS repair indices processing? Was I drinking heavily at the time?

kommven · Post by **kommven** » Mon Apr 17, 2006 4:28 pm

Can you re-create the same error?

Try developing a similar job and try to get similar error.
This is the way to get solution....

made a mistake, do it again here get the cause and never do it again...

chulett · Post by **chulett** » Mon Apr 17, 2006 4:32 pm

kcbland wrote:Methought there was a repair repository files under the DS.TOOLS repair indices processing? Was I drinking heavily at the time?

Possibly, but that's a story for another day.

ray.wurlod · Post by **ray.wurlod** » Mon Apr 17, 2006 9:43 pm

kcbland wrote:Methought there was a repair repository files under the DS.TOOLS repair indices processing? Was I drinking heavily at the time?

DS.REINDEX is separate from DS.TOOLS. Without access to DataStage at the moment I can't recall if there is an option under DS.TOOLS to repair indices. Certainly they removed the option to search out orphaned job components, though the verb remains.

Nonetheless, this is almost certainly NOT a problem with indexes. Even if its indexes are corrupt, you can open a hashed file.

Further, none of the RT_... hashed files is indexed. Only the DS_... hashed files are indexed.

kcbland · Post by **kcbland** » Mon Apr 17, 2006 10:29 pm

ray.wurlod wrote:Certainly they removed the option to search out orphaned job components, though the verb remains.

That must have been my repressed memory, but it's gone now under 7.5. I wonder why it's gone, because log, config, and status corruption seems to be so common. Sometimes importing the job again doesn't work because of a lock on one of the files, or the file is in a state that it can't be deleted and bombs the import when it tries to delete the job. I've manually cleaned out a jobs files when this happens.