LSN Error: 9003

Recently I encountered an error related to LSN. The error message was like
this: Error: 9003, Severity: 20, State: 1 The LSN (4:304:1) passed to log
scan in database 'model' is invalid.. I have to overwrite the model database
with a copy from another server before the server can start up.
Does anyone know what is the cause of this error and is there a way to
prevent this from happening? We are using SQL Server 2000 Standard with SP4
on Windows 2000 Standard Edition with SP4.
Thanks,
MP Wong"mpWong" <mpWong@.discussions.microsoft.com> wrote in message
news:1F8606F4-FB74-4275-8359-73BD2CC31A90@.microsoft.com...
> Recently I encountered an error related to LSN. The error message was like
> this: Error: 9003, Severity: 20, State: 1 The LSN (4:304:1) passed to log
> scan in database 'model' is invalid.. I have to overwrite the model
> database
> with a copy from another server before the server can start up.
>
That doesn't sound good.
Sounds like a corrupt transaction log on the model database. And since the
model database should rarely change, it's even less likely you should see
this.
Does this continue to occur?
> Does anyone know what is the cause of this error and is there a way to
> prevent this from happening? We are using SQL Server 2000 Standard with
> SP4
> on Windows 2000 Standard Edition with SP4.
> Thanks,
> MP Wong
--
Greg Moore
SQL Server DBA Consulting Remote and Onsite available!
Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html|||Hi Greg,
This is the first time I have seen this error. We have about 30 servers and
this one is probably the oldest. Does it signal that the hardware is starting
to fail? We have checked the RAID log records and everything seems normal.
This error could have been caused by a server restart one day earlier.
Best Regards,
MP Wong
"Greg D. Moore (Strider)" wrote:
>
> "mpWong" <mpWong@.discussions.microsoft.com> wrote in message
> news:1F8606F4-FB74-4275-8359-73BD2CC31A90@.microsoft.com...
> > Recently I encountered an error related to LSN. The error message was like
> > this: Error: 9003, Severity: 20, State: 1 The LSN (4:304:1) passed to log
> > scan in database 'model' is invalid.. I have to overwrite the model
> > database
> > with a copy from another server before the server can start up.
> >
> That doesn't sound good.
> Sounds like a corrupt transaction log on the model database. And since the
> model database should rarely change, it's even less likely you should see
> this.
> Does this continue to occur?
>
> > Does anyone know what is the cause of this error and is there a way to
> > prevent this from happening? We are using SQL Server 2000 Standard with
> > SP4
> > on Windows 2000 Standard Edition with SP4.
> >
> > Thanks,
> > MP Wong
> --
> Greg Moore
> SQL Server DBA Consulting Remote and Onsite available!
> Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html
>
>|||"mpWong" <mpWong@.discussions.microsoft.com> wrote in message
news:501B9B7B-05BD-43B7-93C3-7CF75355D6A9@.microsoft.com...
> Hi Greg,
> This is the first time I have seen this error. We have about 30 servers
> and
> this one is probably the oldest. Does it signal that the hardware is
> starting
> to fail? We have checked the RAID log records and everything seems normal.
> This error could have been caused by a server restart one day earlier.
If it happened the one time... and you can correlate it with the server
restart, I'd PROBABLY ignore it.
But if it's happening more than once, then yes, definitely look at your
hardware.
>
> Best Regards,
> MP Wong
> "Greg D. Moore (Strider)" wrote:
>>
>> "mpWong" <mpWong@.discussions.microsoft.com> wrote in message
>> news:1F8606F4-FB74-4275-8359-73BD2CC31A90@.microsoft.com...
>> > Recently I encountered an error related to LSN. The error message was
>> > like
>> > this: Error: 9003, Severity: 20, State: 1 The LSN (4:304:1) passed to
>> > log
>> > scan in database 'model' is invalid.. I have to overwrite the model
>> > database
>> > with a copy from another server before the server can start up.
>> >
>> That doesn't sound good.
>> Sounds like a corrupt transaction log on the model database. And since
>> the
>> model database should rarely change, it's even less likely you should see
>> this.
>> Does this continue to occur?
>>
>> > Does anyone know what is the cause of this error and is there a way to
>> > prevent this from happening? We are using SQL Server 2000 Standard with
>> > SP4
>> > on Windows 2000 Standard Edition with SP4.
>> >
>> > Thanks,
>> > MP Wong
>> --
>> Greg Moore
>> SQL Server DBA Consulting Remote and Onsite available!
>> Email: sql (at) greenms.com
>> http://www.greenms.com/sqlserver.html
>>
--
Greg Moore
SQL Server DBA Consulting Remote and Onsite available!
Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html