Howdy,
I am trying to determine the best way to set up a
maintenance plan using the SQL 2000 wizard.
The problem I'm having is related to rebuilding an index
on a table that contains a computed column.
When the maintenance job reaches the table with a
computed column the job craters.
From the job log I have this entry:
Rebuilding indexes for
table 'tblTEval_Response_Demographic'
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 1934:
[Microsoft][ODBC SQL Server Driver][SQL Server]DBCC
failed because the following SET options have incorrect
settings: 'QUOTED_IDENTIFIER, ARITHABORT'.
Script for the table being addressed:
CREATE TABLE [dbo].[tblTEval_Response_Demographic] (
[RowID] [int] IDENTITY (1, 1) NOT NULL ,
[strEvalSubID] AS ('ES' + right([RowID],10)) ,
[intEvalID] [int] NOT NULL ,
[ClassID] [int] NOT NULL ,
[Badge] [int] NOT NULL ,
[dEval_Date] [smalldatetime] NOT NULL
) ON [PRIMARY]
GO
select @.@.Version
Microsoft SQL Server 2000 - 8.00.760 (Intel X86) Dec
17 2002 14:22:05 Copyright (c) 1988-2003 Microsoft
Corporation Standard Edition on Windows NT 5.0 (Build
2195: Service Pack 3)
I'm using the simple recovery mode and I have auto update
statistics and auto create statistics checked in the
database properties. Compatibility level is 80. Other
properties are unchecked.
What's the best way of handling this situation?
Thanks,
--Terry
Replace msnd with msn to reply directly.Andrew,
Thanks for the input.
If I'm writing my own maintenance plan what would I do differently to
obviate the error? Would it be as simple as changing the settings
'QUOTED_IDENTIFIER, ARITHABORT' just before addressing the index on
the table in question and resetting them afterward?
--Terry
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message news:<ueyo$1wfDHA.1712@.TK2MSFTNGP11.phx.gbl>...
> The way to handle it that I know of is to create your own scheduled job that
> rebuilds the index and don't use the maintenance plan for this.
> --
> Andrew J. Kelly
> SQL Server MVP
>
> "Terry" <ntuser_man@.msdn.com> wrote in message
> news:047c01c37ee2$9937b760$a401280a@.phx.gbl...
> >
> > Howdy,
> >
> > I am trying to determine the best way to set up a
> > maintenance plan using the SQL 2000 wizard.
> >
> > The problem I'm having is related to rebuilding an index
> > on a table that contains a computed column.
> > When the maintenance job reaches the table with a
> > computed column the job craters.
> >
> > From the job log I have this entry:
> >
> > Rebuilding indexes for
> > table 'tblTEval_Response_Demographic'
> > [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 1934:
> > [Microsoft][ODBC SQL Server Driver][SQL Server]DBCC
> > failed because the following SET options have incorrect
> > settings: 'QUOTED_IDENTIFIER, ARITHABORT'.
> >
> > Script for the table being addressed:
> >
> > CREATE TABLE [dbo].[tblTEval_Response_Demographic] (
> > [RowID] [int] IDENTITY (1, 1) NOT NULL ,
> > [strEvalSubID] AS ('ES' + right([RowID],10)) ,
> > [intEvalID] [int] NOT NULL ,
> > [ClassID] [int] NOT NULL ,
> > [Badge] [int] NOT NULL ,
> > [dEval_Date] [smalldatetime] NOT NULL
> > ) ON [PRIMARY]
> > GO
> >
> > select @.@.Version
> > Microsoft SQL Server 2000 - 8.00.760 (Intel X86) Dec
> > 17 2002 14:22:05 Copyright (c) 1988-2003 Microsoft
> > Corporation Standard Edition on Windows NT 5.0 (Build
> > 2195: Service Pack 3)
> >
> > I'm using the simple recovery mode and I have auto update
> > statistics and auto create statistics checked in the
> > database properties. Compatibility level is 80. Other
> > properties are unchecked.
> >
> > What's the best way of handling this situation?
> >
> > Thanks,
> >
> > --Terry
> >
> > Replace msnd with msn to reply directly.
Showing posts with label related. Show all posts
Showing posts with label related. Show all posts
Friday, March 23, 2012
Monday, March 19, 2012
Maintaining a one-to-one match on related tables
I have a series of tables already containing data. The first table is a list
of employees. The next is a list of team names.
There is a Primary Key for each employee which relates to a foreign key in
the team names.
The employee table would have
pkid
FirstName
LastName
fkOfficeID
department
The team table would have only
fkEmployeeID
TeamName
Now, I know how to generate a SELECT set with a LEFT JOIN and a search for
NULL in the TeamName to generate a list of employees that do not have a team
name assigned to them, however. Not every employee would have a coresponding
record in the team table, only certain offices have teams.
What is the statement that would:
"INSERT and UPDATE a specific team name record in the team table for
each corresponding record in the employee table for any employee who's
"Office ID" is 5 department is Accounting and is missing a record in the
team table."
I could VB my way through this by
Creating the list of all offices that have teams
Creating the SELECT set mentioned above and whittling it down to
those employees in each office who are in Accounting
IF NOT EXISTS-ing my way through the team list and adding the
appopriate team record
But, is there an easier way? Is it a two step process, one to determine the
missing records in the one-to-one relationship where needed and then do the
team table update?
Julianand the vb programmers here wonder why vb makes me pull my hair out... ;)
insert into team (fkEmployeeID, TeamName)
select e.pkid, 'Office 5 Accounting Team 1'
from employee e
where fkofficeid=5
and department='Accounting'
and not exists (select * from team where fkemployeeid=e.pkid)
not sure what you need to update...
stjulian wrote:
> I have a series of tables already containing data. The first table is a li
st
> of employees. The next is a list of team names.
> There is a Primary Key for each employee which relates to a foreign key in
> the team names.
> The employee table would have
> pkid
> FirstName
> LastName
> fkOfficeID
> department
> The team table would have only
> fkEmployeeID
> TeamName
>
> Now, I know how to generate a SELECT set with a LEFT JOIN and a search for
> NULL in the TeamName to generate a list of employees that do not have a te
am
> name assigned to them, however. Not every employee would have a corespondi
ng
> record in the team table, only certain offices have teams.
> What is the statement that would:
> "INSERT and UPDATE a specific team name record in the team table for
> each corresponding record in the employee table for any employee who's
> "Office ID" is 5 department is Accounting and is missing a record in the
> team table."
> I could VB my way through this by
> Creating the list of all offices that have teams
> Creating the SELECT set mentioned above and whittling it down to
> those employees in each office who are in Accounting
> IF NOT EXISTS-ing my way through the team list and adding the
> appopriate team record
> But, is there an easier way? Is it a two step process, one to determine th
e
> missing records in the one-to-one relationship where needed and then do th
e
> team table update?
> Julian
>
>|||I think like a VB programmer, you know, linearly. What I love about you guys
in SQL is your way of looking at data in 3 dimensions. Folding it on itself
(using table aliases).
Should the line be "from employee AS e" ?
I should take a class on query design.
I'll give it a try tomorrow. Keep an eye on this thread.
Julian
"Trey Walpole" <treypole@.newsgroups.nospam> wrote in message
news:eETCybEAGHA.1268@.TK2MSFTNGP11.phx.gbl...
> and the vb programmers here wonder why vb makes me pull my hair out... ;)
> insert into team (fkEmployeeID, TeamName)
> select e.pkid, 'Office 5 Accounting Team 1'
> from employee e
> where fkofficeid=5
> and department='Accounting'
> and not exists (select * from team where fkemployeeid=e.pkid)
>
> not sure what you need to update...
> stjulian wrote:|||Although the issues are 2D, thinking 3D is more impressive. :)
ML
http://milambda.blogspot.com/|||I prefer thinking of it as
VB = "For each x, do this"
SQL = "For all x's, do this"
the AS is optional in aliasing a table or column.
my personal preference is to include AS for column aliases and not for
table aliases.
stjulian wrote:
> I think like a VB programmer, you know, linearly. What I love about you gu
ys
> in SQL is your way of looking at data in 3 dimensions. Folding it on itsel
f
> (using table aliases).
> Should the line be "from employee AS e" ?
> I should take a class on query design.
> I'll give it a try tomorrow. Keep an eye on this thread.
> Julian
>
> "Trey Walpole" <treypole@.newsgroups.nospam> wrote in message
> news:eETCybEAGHA.1268@.TK2MSFTNGP11.phx.gbl...
>
of employees. The next is a list of team names.
There is a Primary Key for each employee which relates to a foreign key in
the team names.
The employee table would have
pkid
FirstName
LastName
fkOfficeID
department
The team table would have only
fkEmployeeID
TeamName
Now, I know how to generate a SELECT set with a LEFT JOIN and a search for
NULL in the TeamName to generate a list of employees that do not have a team
name assigned to them, however. Not every employee would have a coresponding
record in the team table, only certain offices have teams.
What is the statement that would:
"INSERT and UPDATE a specific team name record in the team table for
each corresponding record in the employee table for any employee who's
"Office ID" is 5 department is Accounting and is missing a record in the
team table."
I could VB my way through this by
Creating the list of all offices that have teams
Creating the SELECT set mentioned above and whittling it down to
those employees in each office who are in Accounting
IF NOT EXISTS-ing my way through the team list and adding the
appopriate team record
But, is there an easier way? Is it a two step process, one to determine the
missing records in the one-to-one relationship where needed and then do the
team table update?
Julianand the vb programmers here wonder why vb makes me pull my hair out... ;)
insert into team (fkEmployeeID, TeamName)
select e.pkid, 'Office 5 Accounting Team 1'
from employee e
where fkofficeid=5
and department='Accounting'
and not exists (select * from team where fkemployeeid=e.pkid)
not sure what you need to update...
stjulian wrote:
> I have a series of tables already containing data. The first table is a li
st
> of employees. The next is a list of team names.
> There is a Primary Key for each employee which relates to a foreign key in
> the team names.
> The employee table would have
> pkid
> FirstName
> LastName
> fkOfficeID
> department
> The team table would have only
> fkEmployeeID
> TeamName
>
> Now, I know how to generate a SELECT set with a LEFT JOIN and a search for
> NULL in the TeamName to generate a list of employees that do not have a te
am
> name assigned to them, however. Not every employee would have a corespondi
ng
> record in the team table, only certain offices have teams.
> What is the statement that would:
> "INSERT and UPDATE a specific team name record in the team table for
> each corresponding record in the employee table for any employee who's
> "Office ID" is 5 department is Accounting and is missing a record in the
> team table."
> I could VB my way through this by
> Creating the list of all offices that have teams
> Creating the SELECT set mentioned above and whittling it down to
> those employees in each office who are in Accounting
> IF NOT EXISTS-ing my way through the team list and adding the
> appopriate team record
> But, is there an easier way? Is it a two step process, one to determine th
e
> missing records in the one-to-one relationship where needed and then do th
e
> team table update?
> Julian
>
>|||I think like a VB programmer, you know, linearly. What I love about you guys
in SQL is your way of looking at data in 3 dimensions. Folding it on itself
(using table aliases).
Should the line be "from employee AS e" ?
I should take a class on query design.
I'll give it a try tomorrow. Keep an eye on this thread.
Julian
"Trey Walpole" <treypole@.newsgroups.nospam> wrote in message
news:eETCybEAGHA.1268@.TK2MSFTNGP11.phx.gbl...
> and the vb programmers here wonder why vb makes me pull my hair out... ;)
> insert into team (fkEmployeeID, TeamName)
> select e.pkid, 'Office 5 Accounting Team 1'
> from employee e
> where fkofficeid=5
> and department='Accounting'
> and not exists (select * from team where fkemployeeid=e.pkid)
>
> not sure what you need to update...
> stjulian wrote:|||Although the issues are 2D, thinking 3D is more impressive. :)
ML
http://milambda.blogspot.com/|||I prefer thinking of it as
VB = "For each x, do this"
SQL = "For all x's, do this"
the AS is optional in aliasing a table or column.
my personal preference is to include AS for column aliases and not for
table aliases.
stjulian wrote:
> I think like a VB programmer, you know, linearly. What I love about you gu
ys
> in SQL is your way of looking at data in 3 dimensions. Folding it on itsel
f
> (using table aliases).
> Should the line be "from employee AS e" ?
> I should take a class on query design.
> I'll give it a try tomorrow. Keep an eye on this thread.
> Julian
>
> "Trey Walpole" <treypole@.newsgroups.nospam> wrote in message
> news:eETCybEAGHA.1268@.TK2MSFTNGP11.phx.gbl...
>
Monday, February 20, 2012
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...
> 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?
>
> --
> 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.
[vbcol=seagreen]
>
> Best Regards,
> MP Wong
> "Greg D. Moore (Strider)" wrote:
Greg Moore
SQL Server DBA Consulting Remote and Onsite available!
Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html
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...
> 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?
>
> --
> 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.
[vbcol=seagreen]
>
> Best Regards,
> MP Wong
> "Greg D. Moore (Strider)" wrote:
Greg Moore
SQL Server DBA Consulting Remote and Onsite available!
Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html
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
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
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 startin
g
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...
> That doesn't sound good.
> Sounds like a corrupt transaction log on the model database. And since th
e
> model database should rarely change, it's even less likely you should see
> this.
> Does this continue to occur?
>
> --
> Greg Moore
> SQL Server DBA Consulting Remote and Onsite available!
> Email: sql (at) greenms.com [url]http://www.greenms.com/sqlserver.html[/ur
l]
>
>|||"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.
[vbcol=seagreen]
>
> Best Regards,
> MP Wong
> "Greg D. Moore (Strider)" wrote:
>
Greg Moore
SQL Server DBA Consulting Remote and Onsite available!
Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html
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 startin
g
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...
> That doesn't sound good.
> Sounds like a corrupt transaction log on the model database. And since th
e
> model database should rarely change, it's even less likely you should see
> this.
> Does this continue to occur?
>
> --
> Greg Moore
> SQL Server DBA Consulting Remote and Onsite available!
> Email: sql (at) greenms.com [url]http://www.greenms.com/sqlserver.html[/ur
l]
>
>|||"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.
[vbcol=seagreen]
>
> Best Regards,
> MP Wong
> "Greg D. Moore (Strider)" wrote:
>
Greg Moore
SQL Server DBA Consulting Remote and Onsite available!
Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html
Subscribe to:
Posts (Atom)