I have an issue with the ODB Doctor running endlessly on a 1.35GB ODB file. It gets to three progress dots quickly then stops progressing, all while consuming 100% CPU until killed manually. There is plenty of /tmp space and space on the drive where the new database is being placed. When I run the DB Doctor without a destination file (just to check the database) it quickly goes to 5 progress dots before stopping. It looks like it's hitting some sort of resource constraints, possibly memory. Can you please assist in troubleshooting?
ObjectDB Doctor [version 2.6.1]
Copyright (c) 2015, ObjectDB Software. All rights reserved.
Scanning the database file...
PID USER PR NI VIRT RES SHR S %CPU %MEM
32349 cap 20 0 2372m 690m 9312 S 100 17.7 7:16.22 java
/dev/sdb1 50G 39G 8.3G 83% /data/data01 (dest drive)
/dev/sdc1 16G 654M 15G 5% /tmp
-rw-r--r-- 1 cap chrtsupt 1344399360 Mar 18 10:10 consumer_target_Kroger_15.odb
-rw-r--r-- 1 cap chrtsupt 20 Mar 18 10:10 consumer_target_Kroger_15.odb$
-rw-r--r-- 1 cap chrtsupt 262144 Mar 18 10:10 NEW_consumer_target_Kroger_15.odb
-rw-r--r-- 1 cap chrtsupt 483 Mar 18 10:10 NEW_consumer_target_Kroger_15.odb$
/cap/AdherisHealthSolutions/Java/bin/java -Xms1024M -Xmx2048M -cp /cap/AdherisHealthSolutions/DatabaseServer/bin/objectdb-2.6.1.jar com.objectdb.Doctor /cap/AdherisHealthSolutions/DatabaseServer/data/consumer_target_Kroger_15.odb /cap/AdherisHealthSolutions/DatabaseServer/data/NEW_consumer_target_Kroger_15.odb