Database corruption 3 times in 2 months!!

[datgfrab]

I have been having constant problems with corruption. In the last two months I have had to initialize the database three times. Apart from a 2 week period where the backup worked fine (after reinstalling OFA's and initializing the database) the backup has been constantly causing issues. I would just like to find out why the database is corrupting so frequently. Any idea's on what could cause this to happen?? I am running Arcserve 11.5 SP2 on a Windows 2003 server with plenty on disk space...

Many Thanks,

David.

 

[dvdlots]

I have also been plagued by this and usually end up doing a complete re-install every 4-6 months. It happened on version 11, 11.1 and 11.5 on 2 different servers on 2 seperate networks. Bad programming imho!!!

 

[davidmichel]

from what I've seen it is typically the result of a database getting into the 5gb range. The default database does not scale well. In version 12.0 VLDB was replaced with MS SQL Express as the default database.

You can try using the catalog database instead. This is enabled via the Server Admin. Configuration, Database tab and there is a check box there.

 

[datgfrab]

I have been keeping an eye on my backup and it seems that I am only having problems with the cat files not being merged into the database( They stay in the temp folder)! The database engine seems to stop during the backup but my files are still being backed up onto tape. I then have to do a mergecat to manually insert the files into the database.
I thought the database was corrupting so I initialised the database yesterday but I am still having the same problem...

I am about to install service pack 4 (from SP2) and then see how it goes... I was just wondering if anybody else has had this exact issue...

 

[datgfrab]

PROBLEM SOLVED!

For anyone who has had this problem or similar: Basically I have never been running database maintenence on a regular basis, so I decided to run a check on each individual database. I used the dbcheck, keybuild and dbfix tools to scan and rebuild each database that showed errors. Reinitializing the astpsdat database did not fix the problem as it contained no errors!

Here is a link to the knowledge base article:

http://supportconnect.ca.com/sc/kb/...&docid=389855&bypass=yes&fromscreen=kbresults

I ran the dbcheck on every individual database just to be sure. I found errors in asobject and astape so I then ran the keybuild utility. Maybe everyone will have different results...

Hope this helps...