[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 (fwd)

[Christian Zimmermann]

Looks like the issue is with the way the Mysql upgrade was done...

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

---------- Forwarded message ----------
Date: Tue, 4 Jan 2011 03:30:48 -0500
From: Cron Daemon <root at authors.repec.org>
To: "aras at authors.repec.org" <aras at authors.repec.org>
Subject: 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

db4.6_recover: file unknown has LSN 493110/3893017, past end of log at 493110/3503504
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 493110/3893017, past end of log at 493110/3503504
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 493110/3893017, past end of log at 493110/3503504
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 493110/3893017, past end of log at 493110/3503504
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 493110/3893017, past end of log at 493110/3503504
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 493110/3893017, past end of log at 493110/3503504
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 493110/3893017, past end of log at 493110/3503504
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 493110/3893017, past end of log at 493110/3503504
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