Unexpected database engine shutdown, E5110

[dydhda]

I am running Arcserve 2000, SP4, which is now unsupported by CA so I am having difficulties resolving the following problem:

Each day, immediately as my GFS job finishes (7 or 8 seconds after the rescheduling of the job), I get the error:

E5110 The database is no longer available

The database engine shuts down and stops. It then needs to be started manually before any further jobs will run.

I can find no reference to this error code anywhere so if anyone has encountered it before or has any suggestions on what I can do to correct the problem their advice would be much appreciated.

 

[davidmichel]

ck the ARCserve temp directory when no jobs are running for files. If there are *.cat files run mergecat.exe. If there are any other files delete them.

Next run dbcheck to verify the integrity of the databases. Or if you don't care about the database just initilize all of them.

 

[mohamdr]

Do not inisilize all databases inisilize only astpsdat otherwise you will loose all GFS job info ,it is not nessary to inisilize all of then when encounter problem with database since the most growing database astpsdat is causing the backup to fail.

 

[dydhda]

Thanks for the advice - I cleared the ARCserve temp directory and the problem now seems to be resolved. (I chose not to initialise the databases and kept the GFS information)

 

[Mathieugagnon]

I have the same problem, i found the file but i don't understand the option i must take

someone can help me!?

 

[davidmichel]

dydhda, not sure what file you are talking about. Take a look at this faq it might help.
What are those files in the ARCserve\Temp directory? faq478-4059

 

[dydhda]

davidmichel, I'm not sure which part you don't understand. Your advice;

"Check the ARCserve temp directory when no jobs are running for files. If there are *.cat files run mergecat.exe. If there are any other files delete them."

solved the problem. I deleted the contents of the ARCserve temp directory (there were no .cat files) and the database engine does not crash any more.

Many thanks for your help.