This content has been marked as final. Show 3 replies
Resetting LSNs can be done using db_load -r lsn or using the lsn_reset() method, and it is done in place.
If your log files are corrupted, you would need to verify the database files (you can use the db_verify BDB utility or the verify() method). The actions you will further take depend on the result of verifying the database files:
- if they verify correctly then you just need to reset the LSNs and the file IDs in the databases and start with a fresh environment,
- if they do not verify correctly, you could restore the data from the most recent backup, or you can perform a salvage dump of the data in the database files using db_dump -r or db_dump -R and than reload the data using db_load; see the Dumping and Reloading Databases doc section in the Berkeley DB Programmer's Reference Guide.
Thanks, that seems to work great.
Would you know of general environment parameters that can be changed to increase the speed of the db_load process?
In the prior post, there was a link to our documentation, this would be a great place to look for tuning parameters. In general, parameters dealing with cache, database page size, btree/hash, comparison functions and record ordering all can have an effect on db_load performance. Each and every application is unique and you will have to tune for your environment.