Btrieve Error Disk Full (error=18) - while running converts

If you receive this error, it is likely caused by the drive being out of space. When this happens, the convert will not run properly and it may impact the active BTR file that was attempting to be updated. Do not run any further converts if you receive this error so that you don't impact other BTR files. 

To fix this follow these steps: 

1) Have the hosting team increase the size of the drive where the FOS Data is being stored. 2) It is recommended that you restart all PSQL services. 

3) You will then want to compare the BTR file that was being converted to the .OLD files available. You may likely see a .OLD file that contains all the data and was renamed during the failed convert. If you tried recreating the BTR, you may even see an active .BTR file with little or no data. To restore the old file, simply rename the files as needed so that the active BTR file is the old one containing the proper data. 

Example: 

4) Once the proper BTR file is active, re-run the convert for that BTR. 

5) If successful, continue the remaining converts as planned. 

• Related Articles

• Btrieve Error: I/O error during disk read/write (error=2) audtrail: btrieve_status(Thread10428) (Thread 0)

  Error: Btrieve Error: I/O error during disk read/write (error=2) audtrail: btrieve_status(Thread10428) (Thread 0) Solution: Error message is received upon login to FOS for all users. Clear all Pervasive Sessions and/or reboot the FOS server.

• Common Btrieve Errors

  1 – Normally the temp directory is set to another location besides the data server. The path may be changed in the ‘Utilities’ menu at the login window. 2 – The file is corrupted. The error message should indicate which file. The file must be sent to ...

• Btrieve error 51 when converting CREWDUTY.BTR for 3.13

  When running the crewduty.btr for 3.13 the user may get a Btrieve error51. This is due to the DDFs not being updated when the 3.13 installer ran. Solution 1. Check the ddf files in the FOS Data folder - they should have a date of 11/16/22 2. If all ...

• Btrieve Error: Btrieve Status 6 - The key number parameter is invalid. Key=[6] DBIERR_NOSUCHINDEX.

  Error: Btrieve Status 6 - The key number parameter is invalid. Key=[6] DBIERR_NOSUCHINDEX. Solution: Converts were missed during an update. Review a copy of the convert.txt file and look to see what converts were missed. All missed converts will need ...

• Btrieve Error: Btrieve error 3006 userinfo: btrieve_status(Thread3524) (Thread 0)

  Error: Btrieve error 3006 userinfo: btrieve_status(Thread3524) (Thread 0) Solution: Btrieve error 3006 generally means the client machine and FOS server are not communicating. It is possible that there are hung sessions in Pervasive which may be ...