That actually worked... I recreated that file with the contents that I
mentioned below and everything came back up. Very interesting that that
file was empty after the crash.
73,
Matthew W. Jones (KI4ZIB)
http://matburt.net
On Mon, Nov 23, 2009 at 2:19 PM, Matthew Jones
Hi Niels, interestingly enough.... the 'log' file is totally empty. So I went back and examined a backup from a few days ago and the contents of the file are:
""" 050000
17623 """
Which corresponded with a 'log.17623' file that was in the directory at the same time as the backup.
So it looks like maybe the new transaction log file that was hanging around: log.22420
Can't even be picked up because it is referenced by the 'log' file at the top of sql_logs/sql
Can I recreate this file with the right contents?
73, Matthew W. Jones (KI4ZIB) http://matburt.net
On Mon, Nov 23, 2009 at 2:09 PM, Niels Nes
wrote: On Mon, Nov 23, 2009 at 07:59:11PM +0100, Wouter Alink wrote:
Hi Matthew,
I think I've seen such an error before, but I wasn't able to reproduce it, and therefore did not report it. I think I deleted the old dbfarm and started from scratch as my data was easy to reproduce. I assume less destructive actions are feasible... perhaps deleting the contents in the log folder might help too, but I don't want to be held responsible.
Could you send us the content of your $prefix/dbfarm/$dbname/sql_logs/sql/log file?
Somehow it got corrupted, we are unsure to why this happens.
Niels
Good luck, Wouter
2009/11/23 Matthew Jones
: Martin, this database was created with the August 2009 SP2 release,
it was
never upgraded from an old release. In fact... this database has been running since it was created and started with the August 2009 SP2 release... there has never been any downtime until the whole thing deadlocked last night.
73, Matthew W. Jones (KI4ZIB) http://matburt.net
On Mon, Nov 23, 2009 at 1:33 PM, Martin Kersten < Martin.Kersten@cwi.nl> wrote:
Indeed, this indicates that you have installed a new version of MonetDB. One for which a warning was sent out to first dump your database, before installing the new version and loading the database again afterwards.
The feature to make such changes transparent to end-users is high on our list of todos.
regards, Martin
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ MonetDB-users mailing list MonetDB-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-users
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ MonetDB-users mailing list MonetDB-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-users
-- Niels Nes, Centrum Wiskunde & Informatica (CWI) Science Park 123, 1098 XG Amsterdam, The Netherlands room C0.02/M3.46, phone ++31 20 592-4098 url: http://www.cwi.nl/~niels http://www.cwi.nl/%7Eniels e-mail: Niels.Nes@cwi.nl
------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ MonetDB-users mailing list MonetDB-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-users