Cause of RT_STATUSxxx

krystlecsy · Post by **krystlecsy** » Tue Jan 09, 2007 4:19 am

Hi all,

I browsed through issues regarding about RT_STATUSxxx or RT_CONFIGxxx and I'm curious to know what are the cause of this?

The errors are like:-

Cannot open executable job file RT_CONFIGxxx

If there are 3 projects residing on the same server but re-build index is only done on 1 of the project, will all the RT_STATUS errors' be resolved? Or a mass re-build index needs to be done?

ray.wurlod · Post by **ray.wurlod** » Tue Jan 09, 2007 4:36 am

RT_... are database tables in the Repository. They don't have any "cause" other than the job to which they relate being created.

Errors relating to being unable to open them are usually fairly standard things like lack of permission or corruption within the structure. Re-indexing will not help, because the RT_... tables are not indexed.

kumar_s · Post by **kumar_s** » Tue Jan 09, 2007 4:49 am

Is it only that that job with job no xxx, or for all the jobs that exist in project? It it confined to one, you can try to create a copy of the job and delete the old one and rename the existing one, which will create a new set of interfile hashed file and hence solves the problem. If you have problems in whole project, check for the permssions as mentioned. You may need to start some project clean up steps.

kcbland · Post by **kcbland** » Tue Jan 09, 2007 9:08 am

Projects are separate directories, so corruptions to one projects files doesn't affect other projects. If all projects are on the same file system and that file system runs out of space, then you have systemic problems. Otherwise, re-indexing a project is an isolated activity wrt other projects. The easiest way to fix jobs with corrupted or missing supporting files is to export and reimport the job as that creates a new set of supporting files.