Re: Rebuilding EDB From Log Files

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Susan (susan_at_mgmmirage.nospam.com)
Date: 03/03/05 

Date: Thu, 3 Mar 2005 13:25:40 -0800

you mean you have every transaction log that was ever generated? did you
never perform a backup? how long has that database been in existence?

"Michael A. Gronlund, Jr." <mgronlund@traxic.com> wrote in message
news:uucVt3CIFHA.3612@TK2MSFTNGP09.phx.gbl...
> Thanks for the reply
>
> Normally I Would Except: http://support.microsoft.com/?id=278958 Says It
Can
> Be Done
>
> And
>
>
http://groups-beta.google.com/group/microsoft.public.exchange.misc/msg/6cc3173cbc7297cc
>
> Acknowledges it to be a problem "fixed" AFTER SP1
>
> Mike
>
> P.S. I Have A Case Open With MS Just Availing myself to other avenues of
> information
>
> "Ed Woodrick" <ewoodrick@ed-nospam-com.com> wrote in message
> news:ultxcuCIFHA.1580@TK2MSFTNGP10.phx.gbl...
> > It's time to cut your losses and go on with life.
> >
> > You'll probably notice that the Service Pack recommends backing up
before
> > and after the SP, just to get rid of this type of problem.
> >
> > If you *HAVE* to recover the database, then I'd recommend getting on the
> > phone with Microsoft Support. If it can be done, they are teh ones to
> > help.
> >
> > "Michael A. Gronlund, Jr." <mgronlund@traxic.com> wrote in message
> > news:euE6aJCIFHA.2276@TK2MSFTNGP15.phx.gbl...
> >> Has a utility been made available to update 7.3704.5 log files to
> >> 7.3704.8?
> >>
> >> I'm try to rebuilding my edb files from the log files and its throwing
> >> the JET_errInvalidCreateDbVersion error because the first couple of log
> >> file are Exchange 2003 RTM and the the remaining logs are Exchange 2003
> >> SP1. Running eseutil /ml on the logs dumps out:
> >>
> >>
> >> Log file: C:\Program Files\Exchsrvr\MDBDATA\E0000001.log
> >> lGeneration: 1 (0x1)
> >> Checkpoint: NOT AVAILABLE
> >> creation time: 12/22/2004 05:06:22
> >> prev gen time: 00/00/1900 00:00:00
> >> Format LGVersion: (7.3704.5)
> >> Engine LGVersion: (7.3704.8)
> >> <snip>
> >>
> >> Log file: C:\Program Files\Exchsrvr\MDBDATA\E0000002.log
> >> lGeneration: 2 (0x2)
> >> Checkpoint: NOT AVAILABLE
> >> creation time: 12/22/2004 09:12:37
> >> prev gen time: 12/22/2004 05:06:22
> >> ERROR: Invalid log version. Format LGVersion: (7.3704.8).
Expected:
> >> (7.3704.5).
> >>
> >> Please Note This Is The Only Error and on all the remaining files show:
> >>
> >> Format LGVersion: (7.3704.8)
> >> Engine LGVersion: (7.3704.8)
> >>
> >> TIA for any help.
> >>
> >> Mike
> >>
> >
> >
>
>

Relevant Pages

  • Re: Large Transaction Log Backup after Database Backup
    ... script and see for yourself that the database backup doesn't truncate the ... ALTER DATABASE steve SET RECOVERY FULL ... But my understanding was that the transaction log was> truncated after a full database backup. ...
    (microsoft.public.sqlserver.server)
  • Re: Transaction Log Size
    ... Backup database does not empty the transaction log files. ... How to Shrink the SQL Server 7.0 Transaction Log ...
    (microsoft.public.sqlserver.server)
  • Disaster Averted?
    ... Some process, unknown at this point, flooded a transaction log to the point ... the .mdf file was 0 bytes according to EM. ... Following the backup, I ... the database was now Suspect! ...
    (microsoft.public.sqlserver.server)
  • Re: Transaction Log Size
    ... We currently use a 3rd party backup agent to backup our SQL databases and ... transaction logs (Commvault Galaxy iDataAgent for SQL) and the database is ... Because we are using a 3rd party agent to backup the database, ... > here are some articles on how to shrink your transaction log. ...
    (microsoft.public.sqlserver.server)
  • Re: Transaction log problems
    ... IF you have to shrink a database or file it ... sure that you get that database backup on tape or to another machine. ... > We are using SQL Server 2000 on Windows Server 2003 Standard Edition, ... > One of the databases has recently begun showing large growth of the> transaction log and it is causing us some problems. ...
    (microsoft.public.sqlserver.server)