[MonetDB-users] dump & restore errors
Hi, I'm failing to restore a dump from Feb09 to Aug09. I get these errors continuously when I try to restore: 0 tuples !current transaction is aborted (please ROLLBACK) !current transaction is aborted (please ROLLBACK) !current transaction is aborted (please ROLLBACK) !current transaction is aborted (please ROLLBACK) !current transaction is aborted (please ROLLBACK) !current transaction is aborted (please ROLLBACK) !current transaction is aborted (please ROLLBACK) !current transaction is aborted (please ROLLBACK) !current transaction is aborted (please ROLLBACK) The problem is that the error messages aren't descriptive, I can't know what's going on. Any ideas? Thanks, Alex. -- View this message in context: http://www.nabble.com/dump---restore-errors-tp25530320p25530320.html Sent from the monetdb-users mailing list archive at Nabble.com.
On 21-09-2009 06:09:08 -0700, Alex Bo. wrote:
I'm failing to restore a dump from Feb09 to Aug09. I get these errors continuously when I try to restore:
0 tuples !current transaction is aborted (please ROLLBACK) !current transaction is aborted (please ROLLBACK) !current transaction is aborted (please ROLLBACK) !current transaction is aborted (please ROLLBACK) !current transaction is aborted (please ROLLBACK) !current transaction is aborted (please ROLLBACK) !current transaction is aborted (please ROLLBACK) !current transaction is aborted (please ROLLBACK) !current transaction is aborted (please ROLLBACK)
The problem is that the error messages aren't descriptive, I can't know what's going on. Any ideas?
You can try mclient -e, which echoes out the statement before it is sending them to the server, which might give you a dialog of what's going on. It's a feature request (that I'm willing to consider to implement) to request a line number of file or standard input from mclient when it encounters an error.
On Mon, 21 Sep 2009, Fabian Groffen wrote:
On 21-09-2009 06:09:08 -0700, Alex Bo. wrote:
I'm failing to restore a dump from Feb09 to Aug09. I get these errors continuously when I try to restore:
0 tuples !current transaction is aborted (please ROLLBACK) !current transaction is aborted (please ROLLBACK) !current transaction is aborted (please ROLLBACK) !current transaction is aborted (please ROLLBACK) !current transaction is aborted (please ROLLBACK) !current transaction is aborted (please ROLLBACK) !current transaction is aborted (please ROLLBACK) !current transaction is aborted (please ROLLBACK) !current transaction is aborted (please ROLLBACK)
The problem is that the error messages aren't descriptive, I can't know what's going on. Any ideas?
You can try mclient -e, which echoes out the statement before it is sending them to the server, which might give you a dialog of what's going on. It's a feature request (that I'm willing to consider to implement) to request a line number of file or standard input from mclient when it encounters an error.
The errors that are observed are probably due to the paralel loader quiting. And also gives a problem finding out what line breaks. Now the solution might be to disable(?) the paralel loader, or more easy: load it from a file and hope that the error message will show up. Stefan
Stefan de Konink wrote:
On Mon, 21 Sep 2009, Fabian Groffen wrote:
On 21-09-2009 06:09:08 -0700, Alex Bo. wrote:
I'm failing to restore a dump from Feb09 to Aug09. I get these errors continuously when I try to restore:
0 tuples !current transaction is aborted (please ROLLBACK) !current transaction is aborted (please ROLLBACK) !current transaction is aborted (please ROLLBACK) !current transaction is aborted (please ROLLBACK) !current transaction is aborted (please ROLLBACK) !current transaction is aborted (please ROLLBACK) !current transaction is aborted (please ROLLBACK) !current transaction is aborted (please ROLLBACK) !current transaction is aborted (please ROLLBACK)
The problem is that the error messages aren't descriptive, I can't know what's going on. Any ideas? You can try mclient -e, which echoes out the statement before it is sending them to the server, which might give you a dialog of what's going on. It's a feature request (that I'm willing to consider to implement) to request a line number of file or standard input from mclient when it encounters an error.
The errors that are observed are probably due to the paralel loader
Unlikely: there is no parallel loading in the Aug2009 release.
quiting. And also gives a problem finding out what line breaks. Now the solution might be to disable(?) the paralel loader, or more easy: load it from a file and hope that the error message will show up.
What may help is to have mclient read the dump from stdin instead of by using the dump file as command line argument. When reading from stdin, mclient reads one line at a time (which makes it very slow for large dumps!), and so an error is reported at the query that caused it. When reading a file from the command line, mclient reads large chunks (making it a lot faster), but then looses the ability to report on which query caused the error. In the Aug2009 release, a number of bugs have been fixed in the code that creates the dump. It could be that you're hit by one of those in the Feb2009 version of the dump code.
Stefan
------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ MonetDB-users mailing list MonetDB-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-users
-- Sjoerd Mullender
participants (4)
-
Alex Bo. -
Fabian Groffen -
Sjoerd Mullender -
Stefan de Konink