To extract the data from either database, use
hcidbdump -[r|e] [-f ] [-d ] [-b]
OutputFileName will be filled with the database entries in Len10 format.
Unfortunately, the only way to reload either database, that I can think of, is to build a reload thread which can read in the extracted entries and direct them to the appropriate destination thread (for recovery DB entries) or forcing an error (for error DB entries). Since extracted data loses all of its metadata, the thread will depend completely on any routing information present in the data to reload, once the database is reinitialized. You will need to check the engine documentation to learn which metadata fields are writeable and which are not.
Rather than reload the recovery database directly, it might be better to extract DB entries for individual destination threads to files labeled with the destination thread names, then use the thread control popup menu (in the Network Monitor page) to inject the file contents into the destination thread.
Personally, I can’t think of any reason to reload the error database. Error database entries don’t have a destination thread to go to and therefore don’t move or leave once they land. IMHO, it is better to simply leave the error database clear once it is reinitialized.
Migration Consultant
Coffee Regional Medical Center
Eastern Time Zone