Hi,
Well I guess it was just that the rollback was taking an unreasonable
amount of time.
Is it possible to drop the table before the db tries the
rollback on startup, so that the db can come up in a consistent state?
Or alternately startup the db with that table tablelocked and
other tables accessible?
Regards,
Ajit
-----Original Message-----
From: Hahn, Uwe [mailto:[EMAIL PROTECTED]
Sent: Monday, March 15, 2004 7:58 PM
To: 'Ajit Aranha'; [EMAIL PROTECTED]
Subject: RE: 7.3 and DEMO Logmode
Hello Ajit,
in 7.3 the logentries of large transactions are copied into transaction
specific log files in the data area if the log is becoming full.
This makes it possible to overwrite the log area and to assure that the
rollback will work.
Regards,
Uwe
>-----Original Message-----
>From: Ajit Aranha [mailto:[EMAIL PROTECTED]
>Sent: Monday, March 15, 2004 11:48 AM
>To: [EMAIL PROTECTED]
>Subject: 7.3 and DEMO Logmode
>
>Can someone tell me if rollback is possible for an extremely large
>transaction (deleting 2000000 records from a table using a single
delete
>statement.This is 50% of table contents)
>I'm using 7.3.0.30 with DEMO Log.
>
> If the log is auto overwritten during the execution of the delete and
>the delete is then aborted. (i.e. client/server is killed) will the
>statement be rolled back?
>
>The db was restarted but did not come to an online state. I gave up on
>it after 3 hours (kernel.exe was busy during this period).
>
>Regards,
>Ajit
--
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe:
http://lists.mysql.com/[EMAIL PROTECTED]
--
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
