Hello,
I've run a single update-statement with dbmcli on a table with a lot of rows, were most of them were changed. The log device is too small and so it ends up in log full. I'm not able to do anything with the database then (like change the state of the db). autolog is on, but that does not matter her, because it can't backup data in the log-device with is maybe rollbacked (as far as I know). I always thought maxdb use space in the data-device if a single transaction is too big for the log device??
If I run the same sql-statement in the loadercli, several
(auto-)log-backups are made. It seems, that the loadercli devides the statement in several transactions.
I had a backup, so I killed every thread belonging to this DB, and then I were able to drop and recreate it.
How can I "recover" in this LOG FULL situation and bring the DB back to live when I have not a backup for the state just before? I have this behavior in 7.4.23 and 7.5.19.
Martin
-- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
