Urgent: Project has been corrupted

[ram1899]

If you have Backup of the project Just delete the project and and Re-import the Project fresh. In my past project when we had this problem we have deleted the Project and imported it again. It worked ( We did it in v6)
It might work for you

[ray.wurlod]

Then again, you might have a corrupted DS_JOBOBJECTS on your backup.

Even so you're in a better position to attempt repairs. uvfixfile without the -fix option will tell you whether repairs are necessary. You can then use either uvfixfile or the newer fixtool to effect repairs. However the danger still exists that you may truncate a group.

DS_JOBOBJECTS has a number of indexes, so you need to be wary of these too. You may prefer to disconnect them while repairing the main file and reconnect them afterwards (see SET.INDEX command).

Arnd, DS_JOBOBJECTS tends to have many oversized records, so it may well be the case that OVER.30 is larger than DATA.30.

[vinodlakshmanan]

The problem has been solved by importing the entire 6.0 code into a new project and making the changes again, as the changes were not many.
I can easily get the DS_JOBOBJECTS file from this new project and put it in the old projet to try and fix it, but I want to try it the hard way.

DS_JOBOBJECTS has a number of indexes, so you need to be wary of these too. You may prefer to disconnect them while repairing the main file and reconnect them afterwards (see SET.INDEX command).

Arnd, DS_JOBOBJECTS tends to have many oversized records, so it may well be the case that OVER.30 is larger than DATA.30.

So what exactly do I have to do before running UVFIXFILE? And what is this fix tool, can it be run from manager / director?

I also did not get a reply to one of my earlier questions: is tarring and moving hash files the correct way to transfer them between servers.

Thanks Ray,ArndW and others.

Vinod

[ray.wurlod]

Code: Select all

SET.INDEX DS_JOBOBJECTS INFORM

Record the location of the indexes directory.

Code: Select all

SET.INDEX DS_JOBOBJECTS TO NULL

Now DS_JOBOBJECTS believes it has no indexes.

Now effect your repair. fixtool is $DSHOME/bin/fixtool - executed alone or with -H command line option it will generate syntax help.

Code: Select all

SET.INDEX DS_JOBOBJECTS TO pathname

where pathname is the pathname you recorded earlier.
This makes DS_JOBOBJECTS believe once again that it has indexes.

Code: Select all

BUILD.INDEX DS_JOBOBJECTS ALL

Resynchronize the secondary indices with the data in the main file.

[ram1899]

Hi Ray,

As per Vinod the project is corrupted after importing to V7 from V6. Then there is a good Chance that V6 Import is Good.

One other thing is say you have project X and it is been courrupted. ( At present client place smtimes the Jobs are not getting compiled & we can not open the Jobs in this case we Export the Which has problem from project X and we delet the Job from project and reimport the Job it Clears all the Errors and we can compile the Job) It works Ray. When we delete the Job or project it deletes all the Underlying system files also and creates a new one when you import.

I have learned this hard way and it works


Thank you

Then again, you might have a corrupted DS_JOBOBJECTS on your backup.

Even so you're in a better position to attempt repairs. uvfixfile without the -fix option will tell you whether repairs are necessary. You can then use either uvfixfile or the newer fixtool to effect repairs. However the danger still exists that you may truncate a group.

DS_JOBOBJECTS has a number of indexes, so you need to be wary of these too. You may prefer to disconnect them while repairing the main file and reconnect them afterwards (see SET.INDEX command).

Arnd, DS_JOBOBJECTS tends to have many oversized records, so it may well be the case that OVER.30 is larger than DATA.30.