Internal Website Search

attribute specifies the initial size of every new database file. The resize attribute specifies ... and resize values save space. Larger values can improve performance by reducing file fragmentation (many resize operations might cause fragmentation of the database file). The page attribute specifies the size

.o.UserException: Failed to resize file 'F:\CAP\AdherisHealthSolutions\DatabaseServer\data\patient ... of this exception is unclear, but here are several suggestions: Try to resize a copy of this database

of different queries. I have however traced it to database file resizing . In the test run yesterday we had resize amount set to default 256kb. We had another test run today and I've changed it to 256mb. Now the database file is resized approximately every hour. Each time at the same time we see these slow

this? dansmith Daniel Smith The stack trace indicates a delay during database file resize : at java ... :     System.setProperty("objectdb.temp.no- resize -clear", "true"); Alternatively ... , avoiding resize operations. If these solutions do not solve the problem, it may be possible to alter

even though there was no writing to the DB, they double in size exactly the amount of the resize value. This means everytime I restart the DB my DB is growing by resize value across all DB's, this also seems like a bug. I

file resizing . You may try avoiding file resizing by setting relevant configuration  (mainly

J visual vm is complaining of deadlock since upgrading to the 2.4.4_16 from _06 and using setting -Dobjectdb.temp.no- resize -clear=true The only other change is that we no longer create recovery or replay files as we were not using these. i have attached our full server strack trace

are reused but the the file not resized . The database is at the end empty again, but larger

but the database is never resized to a smaller file. Currently the only way to make the database file

could be to store many large objects and then to delete them, creating more space and avoiding resizing

had operations resize .  It didn't have write permissions; permission added and ODB Doctor is working