If you didn't disable redo log writing the changes of all _committed_ transactions should exist after a restart. Kind regards Uwe
>-----Original Message----- >From: news [mailto:[EMAIL PROTECTED] On Behalf Of Sven K�hler >Sent: Tuesday, May 10, 2005 1:49 PM >To: [email protected] >Subject: Dataloss possible? > >Hi, > >we're using a MaxDB-based application. Some people claim, that the data >they entered has disappeared. In fact, not whole records disappeared, >but the data has been changed to a previous version somehow. > >Now can you imagine, how that can happen? Is it possible, that >MaxDB has >a bug that causes such dataloss? Some hints: > >- The Log is in overwrite-mode, since the database is small and i do >daily full backs. > >- I upgraded from 7.5.0.24 to 7.5.0.26 by > - stopping the database > - using SDBINST > - starting the database again > - reloading system tables > >- The system did not crash > > >I can't really imagine, that MaxDB throws away changes. Can you? > > >-- >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]
