- Print
- DarkLight
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
The FIMS database keeps stopping, what causes that and how do I fix it?
Answer:
The FIMS database will crash for many reasons, here are some of the more common ones:
1. The database extents have reached their maximum and need to be adjusted. To check database extents, do the following:
'Corrupt block detected when attempting to release a buffer'
Please create a support case.
1. The database extents have reached their maximum and need to be adjusted. To check database extents, do the following:
- Run the FIMS database Health Audit
- Check the found.lg file and note any errors that occur. The found.lg file is located in npo\found\fims\dbfiles. Errors with extents are also noted there.
- Another symptom of this is that database backups will not complete
- Check the found.lg file and note any errors that occur. With database corruption, you will see a message like the following:
'Corrupt block detected when attempting to release a buffer'
Please create a support case.
Was this article helpful?