Re: Database recovery after running out of disk space.

[Stefaan A Eeckels <Stefaan.Eeckels@xxxxxx>]

On Fri, 19 Jan 2007 21:08:29 +0000 (UTC)
Tanveer Virani <TanveerVirani@elluminate.com> wrote:

> + Repairing V2MasterTableDataSource 029APP_AuditLog
> last_boundary = 80503076019634555
> last_area_pointer = -80503076019285587
> [com.mckoi.debug.Debug - Exception thrown: 'File corrupt:
> last_area_pointer is before data part of file.'] 
> java.io.IOException:
> File corrupt: last_area_pointer is before data part of file.
>    at com.mckoi.store.AbstractStore.open(AbstractStore.java:205) 
>    at com.mckoi.database.V1FileStoreSystem.openStore (V1FileStoreSystem.java:145) 

That would mean that real length of 029APP_Auditlog is 348968, while
the header of the file says that its size is 80503076019634555 (this
is unlikely to say the least). The file is clearly corrupt, and there's 
little hope you can recover it. 

What you could try and to is create a new empty database, and copy the
freshly created, empty Auditlog table file (...APP_Auditlog.koi) to the
corrupted database's 029APP_Auditlog.koi file. Don't hold out too many
hopes, because the generation of the file is also kept in the database 
structures and the new file might not be usable.

With access to the database, the database definition and the source code
a correct, empty file can be reconstructed - it all depends how
important it is and how much your customer wants to spend on it. 

Recovering from the last good backup seems the way to go.

Take care,

-- 
Stefaan A Eeckels
-- 
Never explain by malice what can be adequately explained by stupidity.
However:
Sufficiently advanced stupidity is indistinguishable from malice.