We again look to have a problem. I did only one software change, took citatation change out of APU to try rid us from the overload.... Cron Daemon writes
db4.6_recover: file unknown has LSN 493362/2698220, past end of log at 493362/1823218 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 493362/2698220, past end of log at 493362/1823218 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 493362/2696775, past end of log at 493362/1823218 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 493362/2696775, past end of log at 493362/1823218 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 493362/2132591, past end of log at 493362/1823218 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 493362/2132591, past end of log at 493362/1823218 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 493362/2698220, past end of log at 493362/1823218 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 493362/2698220, past end of log at 493362/1823218 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 493362/2132591, past end of log at 493362/1823218 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 493362/2132591, past end of log at 493362/1823218 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 493362/2698220, past end of log at 493362/1823218 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 493362/2698220, past end of log at 493362/1823218 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 493362/2132591, past end of log at 493362/1823218 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 493362/2132591, past end of log at 493362/1823218 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_checkpoint: /home/aras/acis/RI/data/ACIS/records: unable to flush: No such file or directory db4.6_checkpoint: txn_checkpoint: failed to flush the buffer cache: No such file or directory db4.6_checkpoint: txn_checkpoint: No such file or directory
-- Cheers, Thomas Krichel http://openlib.org/home/krichel http://authorclaim.org/profile/pkr1 skype: thomaskrichel