Re: [sqlite] Corrupted database: On tree page 76852 cell 303: Rowid 18741471 out of order

On Wed, 5 Dec 2018 05:21:30 + Simon Slavin wrote: > On 5 Dec 2018, at 5:16am, Ryan Schmidt wrote: > > > https://kb.vmware.com/s/article/1008542 > > > > "VMware ESX acknowledges a write or read to a guest operating > > system only after that write or read is acknowledged by the > >

Re: [sqlite] Corrupted database: On tree page 76852 cell 303: Rowid 18741471 out of order

On 5 Dec 2018, at 12:22pm, Ryan Schmidt wrote: > Since I don't know what else may have gone wrong with the contents of the > registry by this point, it seems safer to erase the MacPorts installation and > start fresh. This will take a bit longer as every port has to be re-fetched > and

Re: [sqlite] Corrupted database: On tree page 76852 cell 303: Rowid 18741471 out of order

On Dec 4, 2018, at 22:42, Simon Slavin wrote: > On 5 Dec 2018, at 3:20am, Ryan Schmidt wrote: > >> $ sqlite3 /opt/local/var/macports/registry/registry.db >> SQLite version 3.25.2 2018-09-25 19:08:10 >> Enter ".help" for usage hints. >> sqlite> .load /tmp/macports.sqlext >> sqlite> pragma

Re: [sqlite] Corrupted database: On tree page 76852 cell 303: Rowid 18741471 out of order

On 2018/12/05 5:20 AM, Ryan Schmidt wrote: Hello, I have a corrupt SQLite database about which I'd appreciate your advice. The data is not critical but I'd like to fix it if it's possible and not too time-consuming. Even just knowing why the problem occurred or how to prevent it in the

Re: [sqlite] Corrupted database: On tree page 76852 cell 303: Rowid 18741471 out of order

On 5 Dec 2018, at 5:16am, Ryan Schmidt wrote: > https://kb.vmware.com/s/article/1008542 > > "VMware ESX acknowledges a write or read to a guest operating system only > after that write or read is acknowledged by the hardware controller to ESX. > Applications running inside virtual machines on

Re: [sqlite] Corrupted database: On tree page 76852 cell 303: Rowid 18741471 out of order

On Dec 4, 2018, at 22:42, Simon Slavin wrote: > On 5 Dec 2018, at 3:20am, Ryan Schmidt wrote: > >> $ sqlite3 /opt/local/var/macports/registry/registry.db >> SQLite version 3.25.2 2018-09-25 19:08:10 >> Enter ".help" for usage hints. >> sqlite> .load /tmp/macports.sqlext >> sqlite> pragma

Re: [sqlite] Corrupted database: On tree page 76852 cell 303: Rowid 18741471 out of order

On 5 Dec 2018, at 3:20am, Ryan Schmidt wrote: > $ sqlite3 /opt/local/var/macports/registry/registry.db > SQLite version 3.25.2 2018-09-25 19:08:10 > Enter ".help" for usage hints. > sqlite> .load /tmp/macports.sqlext > sqlite> pragma integrity_check; > *** in database main *** > On tree page

[sqlite] Corrupted database: On tree page 76852 cell 303: Rowid 18741471 out of order

Hello, I have a corrupt SQLite database about which I'd appreciate your advice. The data is not critical but I'd like to fix it if it's possible and not too time-consuming. Even just knowing why the problem occurred or how to prevent it in the future would be helpful. If there's something the

[sqlite] Corrupted database

On 2015-03-16 09:49 PM, Dave Dyer wrote: >> Do you still have a copy of the originally damaged Database? I believe a >> closer look to it will reveal more corruption than the assumed. > I have the original database. What other tests could I do to look for > evidence? > > It appears (so far)

[sqlite] Corrupted database

On 2015-03-16 08:35 PM, Dave Dyer wrote: > I have some addition evidence that there is an underlying problem, > exacerbated by some failure in SMB file sharing. > > In this instance, there is a set of duplicated records that did not > directly cause an indexing error, but which could have been

[sqlite] Corrupted database

On 16 Mar 2015, at 6:35pm, Dave Dyer wrote: > This "fully repaired" database turned out to contain a duplicated set of > records which did not cause an indexing problem, but which should not have > occurred, and was consistent with a duplicated transaction. If this had > been caused by a

[sqlite] Corrupted database

>I will have to say very sadly that if you absolutely have to have a >system where the DB file is not on the exact same machine (physical) >than the client software (the bit using SQLite code), then SQLite is not >a good choice - consider MySQL or Postgres perhaps. There was a crowd >some time

[sqlite] Corrupted database

On 3/16/15, Simon Slavin wrote: > > Because of the format in which SQLite keeps its indexes, you > cannot always repair a corrupted index by deleting the rows which you think > are corrupt. Sometimes you need to delete other rows too (for example those > immediately before and after a corrupt

[sqlite] Corrupted database

> >Do you still have a copy of the originally damaged Database? I believe a >closer look to it will reveal more corruption than the assumed. I have the original database. What other tests could I do to look for evidence? It appears (so far) that the database I reconstructed from the dump

[sqlite] Corrupted database

> >Do you still have a copy of the originally damaged Database? I believe a >closer look to it will reveal more corruption than the assumed. I have the original database. What other tests could I do to look for evidence? It appears (so far) that the database I reconstructed from the dump

[sqlite] Corrupted database

> >Do you still have a copy of the originally damaged Database? I believe a >closer look to it will reveal more corruption than the assumed. I have the original database. What other tests could I do to look for evidence? It appears (so far) that the database I reconstructed from the dump

[sqlite] Corrupted database

> >Do you still have a copy of the originally damaged Database? I believe a >closer look to it will reveal more corruption than the assumed. I have the original database. What other tests could I do to look for evidence? It appears (so far) that the database I reconstructed from the dump

[sqlite] Corrupted database

> >The only safe thing to do is to drop the index and remake it. Or do to >something which does that (e.g. VACUUM). As I said, the first step in my repair was to drop the offending index.

[sqlite] Corrupted database

> >The only safe thing to do is to drop the index and remake it. Or do to >something which does that (e.g. VACUUM). As I said, the first step in my repair was to drop the offending index.

[sqlite] Corrupted database

I have some addition evidence that there is an underlying problem, exacerbated by some failure in SMB file sharing. In this instance, there is a set of duplicated records that did not directly cause an indexing error, but which could have been created if a transaction failed (presumably due to a

[sqlite] Corrupted database

Hi Dave, ? thanks. In fact, I know, how to repair the database and get access to the data. What I was trying to track down a bit, is the reason for the database to get corrupted. But as Simon explained, this might have to do with "in-order-writing" of the RAID we're using. ? Alex ? ?

[sqlite] Corrupted database

Hi Simon, >So from all the above it's likely that the data in your tables is okay >, and only the indexes in that file are corrupt. ?So dropping and >?recreating your indexes should fix the file perfectly unless the >?violation of the UNIQUE requirement is in the primary index for a table. ? Yes,

[sqlite] Corrupted database

> On 5 Mar 2015, at 7:28am, Alexandr N?mec wrote: > > Hi Simon, > >> Does SQLite automatically detect and uncorrupt these problems the next time >> it opens the database, >> or has something been done to the hardware to break in-order writing ? > > No. The database can be opened

[sqlite] Corrupted database

If you can .dump it, can you also use .read to restore it? And if so, how damaged does it appear to be? My databases, with a corrupt index, couldn't be restored directly, but the duplicate entries could be seen, cleaned up, and then the restore succeeded. Or (more conveniently) remove the index

[sqlite] Corrupted database

Hi Dave, ? thanks for yoyr?reply. ? >I'd be interested if you could characterize the corruption. ? As I already replied to Simon, I can ".dump" the database but I can't run any ''select" queries. The SQLite shell displays "database disk image is malformed" and using C?API, error code

[sqlite] Corrupted database

Hi Simon, ? > Does SQLite automatically detect and uncorrupt these problems the next time > it opens the database, >?or has something been done to the hardware to break in-order writing ? ? No. The database can be opened successfully, but a simple "select" ends up with "database disk image is

[sqlite] Corrupted database

On 4 Mar 2015, at 9:07pm, Scott Hess wrote: > In the time I've been involved with high-volume SQLite clients (Google > Gears, then Chrome), what I've found is that the corruption invariably > (*) ends up being a case where distinct pages were not written > atomically, but where each page in

[sqlite] Corrupted database

I'd be interested if you could characterize the corruption. For example, can use still use .dump to dump the database, and if so what kind of damage is there? The cases I've encountered recently, the "corruption" was only a few duplicated records, which broke the uniqueness constraint on an

[sqlite] Corrupted database

I'd be interested if you could characterize the corruption. For example, can use still use .dump to dump the database, and if so what kind of damage is there? The cases I've encountered recently, the "corruption" was only a few duplicated records, which broke the uniqueness constraint on an

[sqlite] Corrupted database

On Wed, Mar 4, 2015 at 1:11 AM, Alexandr N?mec wrote: > we have a product that uses SQLite. Because it was running very stable for > years, we are still using SQLite 3.7.17. Now we've seen on one of our > installations that the database has been corrupted, we saw that there was a > power failure

[sqlite] Corrupted database

Hi all, ? we have a product that uses SQLite. Because it was running very stable for years, we are still using SQLite 3.7.17. Now we've seen on one of our installations that the database has been corrupted, we saw that there was a power failure around the time of the corruption. We tested power

Re: [sqlite] Corrupted database files

On 5 Jun 2014, at 1:16pm, Lasse Jansen wrote: > Thanks, spawning another process is a good idea. If you're going to continue to use SQLite in your own code on a Mac I encourage you to include the amalgamation files (.h and .c) rather than referring to a dynamic library.

Re: [sqlite] Corrupted database files

Thanks, spawning another process is a good idea. Filing a bug with Apple is probably not going to work, they don't encourage accessing a CoreData managed database without going through CoreData. 2014-06-05 13:49 GMT+02:00 David Empson : > On 5/06/2014, at 11:21 pm, Lasse

Re: [sqlite] Corrupted database files

Thanks for the suggestion, I think I'll try this. I probably need to detect the kind of error and use some retry-mechanism ... 2014-06-05 13:35 GMT+02:00 Richard Hipp : > On Thu, Jun 5, 2014 at 7:21 AM, Lasse Jansen wrote: > > > Hi, > > > > we have a Mac

Re: [sqlite] Corrupted database files

Unfortunately CoreData is closed source and is distributed as part of the Mac OS X SDK so there is no way to update it. 2014-06-05 13:33 GMT+02:00 RSmith : > > On 2014/06/05 13:21, Lasse Jansen wrote: > >> Hi, >> >> we have a Mac app that uses CoreData which internally uses

Re: [sqlite] Corrupted database files

On 5/06/2014, at 11:21 pm, Lasse Jansen wrote: > Hi, > > we have a Mac app that uses CoreData which internally uses SQLite. Some of > the queries are not expressible within CoreData, so we send them manually > using the sqlite library that comes with Mac OS X. Now some of

Re: [sqlite] Corrupted database files

On Thu, Jun 5, 2014 at 7:21 AM, Lasse Jansen wrote: > Hi, > > we have a Mac app that uses CoreData which internally uses SQLite. Some of > the queries are not expressible within CoreData, so we send them manually > using the sqlite library that comes with Mac OS X. Now some

Re: [sqlite] Corrupted database files

On 2014/06/05 13:21, Lasse Jansen wrote: Hi, we have a Mac app that uses CoreData which internally uses SQLite. Some of the queries are not expressible within CoreData, so we send them manually using the sqlite library that comes with Mac OS X. Now some of our users have reported that their

[sqlite] Corrupted database files

Hi, we have a Mac app that uses CoreData which internally uses SQLite. Some of the queries are not expressible within CoreData, so we send them manually using the sqlite library that comes with Mac OS X. Now some of our users have reported that their database file got corrupted and after some

Re: [sqlite] Corrupted Database

Özgür KELEŞ wrote: > We use sqlite in our industrial devices. But sometimes the database > corrupted. We could not find the problem , how it can be possible to > corrupt the database. http://www.sqlite.org/lockingv3.html Section 6.0 "How To Corrupt Your Database Files" --

[sqlite] Corrupted Database

Hi, We use sqlite in our industrial devices. But sometimes the database corrupted. We could not find the problem , how it can be possible to corrupt the database. It is possible to see powerless on devices and OS crashes cause of electromagnetic noises, rarely. I attached some of corrupted

Re: [sqlite] Corrupted database file.

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/05/2011 11:05 AM, Greg Morehead wrote: > Any insights on how this could occur would be greatly appreciated. http://www.sqlite.org/lockingv3.html#how_to_corrupt Roger -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment:

Re: [sqlite] Corrupted database with duplicated primary keys

Due to attach limits this is the part 002 of the file! - "Israel Lins Albuquerque" escreveu: > Attached has a database corrupted. > We use the version 3.6.23.1 in wince. > > the command: > pragma integrity_check; > > show many errors and > > Duplicate

Re: [sqlite] Corrupted database with duplicated primary keys

Due to attach limits this is the part 001 of the file! - "Israel Lins Albuquerque" escreveu: > Attached has a database corrupted. > We use the version 3.6.23.1 in wince. > > the command: > pragma integrity_check; > > show many errors and > > Duplicate

[sqlite] Corrupted database with duplicated primary keys

Attached has a database corrupted. We use the version 3.6.23.1 in wince. the command: pragma integrity_check; show many errors and Duplicate pk was founded using: SELECT u_pkey, count(*) FROM tp_gpsdata GROUP BY u_pkey HAVING count(*) > 1 ; this returns only 1 record SELECT * FROM

Re: [sqlite] Corrupted database (image is malformed): always the same size

On 21 Dec 2009, at 8:00am, Gianandrea Gobbo wrote: > At this stage, I cannot think of an applicative bug that leads to this > kind of corruption, where the database results always in the same size. The only time I ever saw a number of files all truncated to the same length, the fault was in

Re: [sqlite] Corrupted database (image is malformed): always the same size

Max Vlasov ha scritto: > On Fri, Dec 18, 2009 at 6:27 PM, Gianandrea Gobbo wrote: > > Gianandrea, I once had an experience with fixing a modified code that led to > database disk image malformation. If you can reproduce the bug with a > comparatively few number of steps, I'd

Re: [sqlite] Corrupted database (image is malformed): always the same size

I also using 2.8, but i wondering why your database has 200 kb from the beginning. my databases have only 3 or 4 kb's. But at my host if i am using sqlite queries which are $db-> like, i get the same error. funny thing, but the database is not malformed... > > On 18 Dec 2009, at 3:27pm,

Re: [sqlite] Corrupted database (image is malformed): always the same size

On Fri, Dec 18, 2009 at 6:27 PM, Gianandrea Gobbo wrote: > I'm using sqlite (2.8) on an embedded product, running a Linux kernel. > I'm experiencing sometimes a database corruption, and listing some > tables contents gets me a "SQL error: database disk image is malformed". > Ok,

Re: [sqlite] Corrupted database (image is malformed): always the same size

On 18 Dec 2009, at 3:27pm, Gianandrea Gobbo wrote: > I'm using sqlite (2.8) on an embedded product, running a Linux kernel. > I'm experiencing sometimes a database corruption, and listing some > tables contents gets me a "SQL error: database disk image is malformed". > Ok, there can be many

[sqlite] Corrupted database (image is malformed): always the same size

I'm using sqlite (2.8) on an embedded product, running a Linux kernel. I'm experiencing sometimes a database corruption, and listing some tables contents gets me a "SQL error: database disk image is malformed". Ok, there can be many reasons for this, but the strange thing that puzzles me is that

Re: [sqlite] Corrupted database

On Wed, Oct 14, 2009 at 6:06 PM, Dan Kennedy wrote: > >> The problem I think may be people using TerminateThread();  that's how >> you hard kill a thread.  It seems that can interrupt an I/O >> operation -- >> ie an operation that writes more than one cluster at a time.  

Re: [sqlite] Corrupted database

r 14, 2009 7:15 AM > To: General Discussion of SQLite Database > Subject: Re: [sqlite] Corrupted database > > On Mon, Oct 12, 2009 at 8:56 PM, McClellen, Chris > <cmcclel...@weather.com> wrote: >> What is your synchronous set to?  Full?  FYI If you are using .NET data >>

Re: [sqlite] Corrupted database

On Oct 14, 2009, at 2:59 PM, McClellen, Chris wrote: > I think the issue is : > > Thread 1 does exitprocess/terminateprocess (or process.kill, or > anything like that) > Thread 2 does write() -- the write I believe can be interrupted when > partially complete in these cases (only part of the

Re: [sqlite] Corrupted database

Discussion of SQLite Database Subject: Re: [sqlite] Corrupted database On Oct 14, 2009, at 2:51 PM, Reusche, Andrew wrote: > We get a "2" returned when we check synchronous. I think that's the > enum for "full". We do not explicitely kill any threads, but when we >

Re: [sqlite] Corrupted database

-users-boun...@sqlite.org MC> [mailto:sqlite-users-boun...@sqlite.org] On Behalf Of Teg MC> Sent: Wednesday, October 14, 2009 12:10 PM MC> To: General Discussion of SQLite Database MC> Subject: Re: [sqlite] Corrupted database MC> Hello Chris, MC> It's always a mistake to use Term

Re: [sqlite] Corrupted database

On Oct 14, 2009, at 2:51 PM, Reusche, Andrew wrote: > We get a "2" returned when we check synchronous. I think that's the > enum for "full". We do not explicitely kill any threads, but when we > decide to reboot or shutdown, we call "ExitProcess(0)" without > stopping > any DB threads, and

Re: [sqlite] Corrupted database

We get a "2" returned when we check synchronous. I think that's the enum for "full". We do not explicitely kill any threads, but when we decide to reboot or shutdown, we call "ExitProcess(0)" without stopping any DB threads, and I'm sure this isn't very healthy. Andrew This communication

Re: [sqlite] Corrupted database

exits" -Original Message- From: sqlite-users-boun...@sqlite.org [mailto:sqlite-users-boun...@sqlite.org] On Behalf Of Teg Sent: Wednesday, October 14, 2009 12:10 PM To: General Discussion of SQLite Database Subject: Re: [sqlite] Corrupted database Hello Chris, It's always a mist

Re: [sqlite] Corrupted database

grace MC> period, and such, terminatethread() is never called.. and we get no MC> corruption. MC> Just a thought. MC> -Original Message- MC> From: sqlite-users-boun...@sqlite.org MC> [mailto:sqlite-users-boun...@sqlite.org] On Behalf Of Dan Kennedy MC> Sent: Wednesday, Octo

Re: [sqlite] Corrupted database

te-users-boun...@sqlite.org] On Behalf Of Dan Kennedy > Sent: Wednesday, October 14, 2009 12:36 AM > To: General Discussion of SQLite Database > Subject: Re: [sqlite] Corrupted database > > > On Oct 14, 2009, at 12:42 AM, McClellen, Chris wrote: > >> But it does happen

Re: [sqlite] Corrupted database

Subject: Re: [sqlite] Corrupted database On Oct 14, 2009, at 12:42 AM, McClellen, Chris wrote: > But it does happen and we can reproduce it. Hard killing a thread is > essentially equivalent to turning off the power. We have always assumed that it is different. When you write data to

Re: [sqlite] Corrupted database

On Mon, Oct 12, 2009 at 8:56 PM, McClellen, Chris wrote: > What is your synchronous set to?  Full?  FYI If you are using .NET data > providers, it is set to "Normal" by default. Normal or Off, but no power failure was involved. (Yes, System.Data.SQLite is used) > If it

Re: [sqlite] Corrupted database

To: General Discussion of SQLite Database Subject: Re: [sqlite] Corrupted database On Oct 13, 2009, at 1:56 AM, McClellen, Chris wrote: > What is your synchronous set to? Full? FYI If you are using .NET > data > providers, it is set to "Normal" by default. > > If it is not

Re: [sqlite] Corrupted database

er 12, 2009 12:38 PM > To: General Discussion of SQLite Database > Subject: [sqlite] Corrupted database > > Hello, > > for a few months we have been occasionally getting corrupted databases > in the field. So far we were unable to acquire any of them from our > customers,

Re: [sqlite] Corrupted database

om: sqlite-users-boun...@sqlite.org [mailto:sqlite-users-boun...@sqlite.org] On Behalf Of Filip Navara Sent: Monday, October 12, 2009 12:38 PM To: General Discussion of SQLite Database Subject: [sqlite] Corrupted database Hello, for a few months we have been occasionally getting corrupted

[sqlite] Corrupted database

Hello, for a few months we have been occasionally getting corrupted databases in the field. So far we were unable to acquire any of them from our customers, but this week I finally got hold of one. Output from "pragma integrity_check" is included below. The schema is the following: CREATE

[sqlite] Corrupted database with Atomic write sector ?

Hi, We have performance issues with SQLite running on our file system (remote FS using Atomic Write Sector). In fact we are limited with the number of write by second allowed by our file system, let’s say we have 10 write/s After a series of benchmarks the log file (journal) seems to be the

Re: [sqlite] Corrupted database repairing

It's very dificult decision. I'm prefer to use some callback function for logging all queries. But I don't know how to realise this callback - trace and profile callbacks can't show query string with variables values. 2008/8/11, Dennis Cote <[EMAIL PROTECTED]>: > Alexey Pechnikov wrote: >> >> Can

Re: [sqlite] Corrupted database repairing

Alexey Pechnikov wrote: > > Can I get full log of sql statements for to sent it other network or store to > outher device? > Alexey, You may want to read http://www.sqlite.org/cvstrac/wiki?p=UndoRedo for an example of using triggers to generate SQL to modify a database. This example is

Re: [sqlite] Corrupted database repairing

В сообщении от Saturday 26 July 2008 10:23:57 Roger Binns написал(а): > Alexey Pechnikov wrote: > >> Maybe sqlite3_trace() or sqlite3_profile() can help with what you're > >> looking for here. > > Unfortunately sqlite3_trace isn't that useful as it only tells you the > text of the sql statement

Re: [sqlite] Corrupted database repairing

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Alexey Pechnikov wrote: >> Maybe sqlite3_trace() or sqlite3_profile() can help with what you're >> looking for here. Unfortunately sqlite3_trace isn't that useful as it only tells you the text of the sql statement but not any bound parameters. The

Re: [sqlite] Corrupted database repairing

В сообщении от Friday 25 July 2008 16:32:26 Derrell Lipman написал(а): > > Can I get full log of sql statements for to sent it other network or > > store to > > outher device? > > Maybe sqlite3_trace() or sqlite3_profile() can help with what you're > looking for here. Thanks!

Re: [sqlite] Corrupted database repairing

On Fri, Jul 25, 2008 at 5:23 AM, Alexey Pechnikov <[EMAIL PROTECTED]> wrote: > > > Database servers such as Oracle or PostgreSQL have transactions log and > > > restore log. > > > > Those logs are effectively duplicates of the data or ways of > > reconstructing the data. SQLite has a transaction

Re: [sqlite] Corrupted database repairing

В сообщении от Friday 25 July 2008 12:16:39 Roger Binns написал(а): > Alexey Pechnikov wrote: > > May be on FS layer? > > I specifically said VFS which is SQLite functionality - see > http://www.sqlite.org/c3ref/vfs.html and > http://www.sqlite.org/c3ref/io_methods.html Thanks, last link may be

Re: [sqlite] Corrupted database repairing

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Alexey Pechnikov wrote: > May be on FS layer? I specifically said VFS which is SQLite functionality - see http://www.sqlite.org/c3ref/vfs.html and http://www.sqlite.org/c3ref/io_methods.html > Which FS can help me for this? I'm using ext3 FS now on

Re: [sqlite] Corrupted database repairing

В сообщении от Friday 25 July 2008 03:40:22 Roger Binns написал(а): > Alexey Pechnikov wrote: > > Is any way to repair corrupted database? > > From a theoretical point of view the only way to repair a corrupted > database is if there are multiple redundant copies of data or of > generating that

Re: [sqlite] Corrupted database repairing

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Alexey Pechnikov wrote: > Is any way to repair corrupted database? - From a theoretical point of view the only way to repair a corrupted database is if there are multiple redundant copies of data or of generating that data. Since SQLite doesn't do

Re: [sqlite] Corrupted database repairing

В сообщении от Thursday 24 July 2008 20:48:08 Alexey Pechnikov написал(а): > Hello! > > Is any way to repair corrupted database? May be I have archive copy of > database and corrupted this pages - can I get correct pages and merge their > with archive database? > > P.S. I have no corrupted

[sqlite] Corrupted database repairing

Hello! Is any way to repair corrupted database? May be I have archive copy of database and corrupted this pages - can I get correct pages and merge their with archive database? P.S. I have no corrupted database now but this question is important for me. Best regards, Alexey.