[RAS] Cron <aras at nebka> /usr/bin/db4.6_recover -h ~/acis/RI/data ; /usr/bin/db4.6_checkpoint -1 -h ~/acis/RI/data && /usr/bin/db4.6_archive -d -h ~/acis/RI/data

Christian Zimmermann christian.zimmermann at uconn.edu
Thu Dec 30 11:51:17 CST 2010


On Thu, 30 Dec 2010, Cron Daemon wrote:

> db4.6_recover: unable to join the environment
> db4.6_recover: DB_LOGC->get: LSN 492902/9628236: invalid log record header
> db4.6_recover: Log file corrupt at LSN: [492902][9628180]
> db4.6_recover: PANIC: Invalid argument
> db4.6_recover: DB_ENV->open: DB_RUNRECOVERY: Fatal error, run database recovery
>

aras at nebka:~/acis/userdata$ db4.6_recover
aras at nebka:~/acis/userdata$ /usr/bin/db4.6_checkpoint -1 -h ~/acis/RI/data
db4.6_checkpoint: PANIC: fatal region error detected; run recovery
aras at nebka:~/acis/userdata$ db4.6_recover
aras at nebka:~/acis/userdata$ /usr/bin/db4.6_checkpoint -1 -h ~/acis/RI/data
db4.6_checkpoint: PANIC: fatal region error detected; run recovery
aras at nebka:~/acis/userdata$ db4.6_recover
aras at nebka:~/acis/userdata$ /usr/bin/db4.6_checkpoint -1 -h ~/acis/RI/data
db4.6_checkpoint: PANIC: fatal region error detected; run recovery

BTW, load is still high.



More information about the RAS-run mailing list