I have correct the issue by simply upgrading system tables i think that its a must to do and i havent done it!!! Sorry men for the inconvenience.
However i have lost several log data in the database because a log area was wrong, its the second time it happens in that machine, i hope that in the new one it wont. The problem i think is that at some point the log files (not the disk) gets some incorrect data and after that it isnt able to recover that data and db crashes. There is any method to parse redo-logs and erase bad redo entries so that the db can succesfully start losing minimal data? The times it happens i do a complete restoration with initialitation until the latest redo log backup file done automagically (auto log mode) but i always lose several amount of data of the "until that time" not written redo log backup of the redo area. Thanks for the support, Josu. ---------- Forwarded message ---------- From: Josu <[EMAIL PROTECTED]> Date: Thu, 4 Nov 2004 11:15:35 +0100 Subject: new upgraded database seems to be read only! To: [EMAIL PROTECTED] Hi all again, I have managed to migrate the db from one host with version .00.08 to another one using .00.19 the problem now is ......... The existing data and tables on the new host seem to be read only, i can't modify/alter them but in the original host i can. Also i can create new tables and insert new data but i can't modify imported old data from the other host backups. How can i solve this? The idea is not to continue using the old machine and use this new one with the old host original data/squema. Many thanks, Josu. -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
