[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
Fri Dec 31 09:42:32 CST 2010
What the heck is all that, and how would a reboot help?
Christian Zimmermann FIGUGEGL!
Department of Economics
University of Connecticut
341 Mansfield Road, Unit 1063
Storrs, CT 06269-1063
http://ideas.repec.org/zimm/ christian.zimmermann at uconn.edu
http://ideas.repec.org/e/pzi1.html
On Fri, 31 Dec 2010, Cron Daemon wrote:
> db4.6_recover: file unknown has LSN 492969/2475660, past end of log at 492969/1295897
> db4.6_recover: Commonly caused by moving a database from one database environment
> db4.6_recover: to another without clearing the database LSNs, or by removing all of
> db4.6_recover: the log files from a database environment
> db4.6_recover: file unknown has LSN 492969/2475660, past end of log at 492969/1295897
> db4.6_recover: Commonly caused by moving a database from one database environment
> db4.6_recover: to another without clearing the database LSNs, or by removing all of
> db4.6_recover: the log files from a database environment
> db4.6_recover: file unknown has LSN 492969/2475660, past end of log at 492969/1295897
> db4.6_recover: Commonly caused by moving a database from one database environment
> db4.6_recover: to another without clearing the database LSNs, or by removing all of
> db4.6_recover: the log files from a database environment
> db4.6_recover: file unknown has LSN 492969/2475660, past end of log at 492969/1295897
> db4.6_recover: Commonly caused by moving a database from one database environment
> db4.6_recover: to another without clearing the database LSNs, or by removing all of
> db4.6_recover: the log files from a database environment
> db4.6_recover: file unknown has LSN 492969/2475660, past end of log at 492969/1295897
> db4.6_recover: Commonly caused by moving a database from one database environment
> db4.6_recover: to another without clearing the database LSNs, or by removing all of
> db4.6_recover: the log files from a database environment
> db4.6_recover: file unknown has LSN 492969/2475660, past end of log at 492969/1295897
> db4.6_recover: Commonly caused by moving a database from one database environment
> db4.6_recover: to another without clearing the database LSNs, or by removing all of
> db4.6_recover: the log files from a database environment
> db4.6_recover: file unknown has LSN 492969/2475660, past end of log at 492969/1295897
> db4.6_recover: Commonly caused by moving a database from one database environment
> db4.6_recover: to another without clearing the database LSNs, or by removing all of
> db4.6_recover: the log files from a database environment
> db4.6_recover: file unknown has LSN 492969/2475660, past end of log at 492969/1295897
> db4.6_recover: Commonly caused by moving a database from one database environment
> db4.6_recover: to another without clearing the database LSNs, or by removing all of
> db4.6_recover: the log files from a database environment
> db4.6_recover: file unknown has LSN 492969/2475660, past end of log at 492969/1295897
> db4.6_recover: Commonly caused by moving a database from one database environment
> db4.6_recover: to another without clearing the database LSNs, or by removing all of
> db4.6_recover: the log files from a database environment
> db4.6_recover: file unknown has LSN 492969/2475660, past end of log at 492969/1295897
> db4.6_recover: Commonly caused by moving a database from one database environment
> db4.6_recover: to another without clearing the database LSNs, or by removing all of
> db4.6_recover: the log files from a database environment
> db4.6_recover: file unknown has LSN 492969/2475660, past end of log at 492969/1295897
> db4.6_recover: Commonly caused by moving a database from one database environment
> db4.6_recover: to another without clearing the database LSNs, or by removing all of
> db4.6_recover: the log files from a database environment
> db4.6_recover: file unknown has LSN 492969/2475660, past end of log at 492969/1295897
> db4.6_recover: Commonly caused by moving a database from one database environment
> db4.6_recover: to another without clearing the database LSNs, or by removing all of
> db4.6_recover: the log files from a database environment
>
More information about the RAS-run
mailing list