For about two hours last evening our database started producing these errors
and various jobs failed.
This morning all seems quiet. However we do rebuild our indexes overnight.
Should we worry about this?
The jobs that failed do not process any text columns (the only mention I
found on microsofts site).
The File ID cannot relate to sysfiles. Does anyone know what is does relate
to?
SQL Server 2000 SP3A.Hi
Please run DBCC checktable to see if there are any corruption related errors on this table. Take full database backup before you execute dbcc checktable.
If the output come clear then you do not want to worry any more
Thank
Har
MCDB
-- Paul Cahill wrote: --
For about two hours last evening our database started producing these error
and various jobs failed
This morning all seems quiet. However we do rebuild our indexes overnight
Should we worry about this
The jobs that failed do not process any text columns (the only mention
found on microsofts site)
The File ID cannot relate to sysfiles. Does anyone know what is does relat
to
SQL Server 2000 SP3A|||Thanks Hari
How do I tell which table. I tried offering up the number above as an ID to
sysobjects but nothing came back.
Paul
"Hari" <hari_prasad_k@.hotmail.com> wrote in message
news:F3226200-D6DC-4939-8773-4E5CFC0FA567@.microsoft.com...
> Hi,
> Please run DBCC checktable to see if there are any corruption related
errors on this table. Take full database backup before you execute dbcc
checktable.
> If the output come clear then you do not want to worry any more.
> Thanks
> Hari
> MCDBA
>
> -- Paul Cahill wrote: --
> For about two hours last evening our database started producing these
errors
> and various jobs failed.
> This morning all seems quiet. However we do rebuild our indexes
overnight.
> Should we worry about this?
> The jobs that failed do not process any text columns (the only
mention I
> found on microsofts site).
> The File ID cannot relate to sysfiles. Does anyone know what is does
relate
> to?
> SQL Server 2000 SP3A.
>
>|||Hi,
I feel that it should be a problem with tempdb. If it is the case no issues.
Anyway can you execute DBCC CHECKDB('dbname') for that database and ensure
no errors.
Thanks
Hari
MCDBA
"Paul Cahill" <XYZpaul.cahillXYZ@.blueyonder.co.uk> wrote in message
news:O0Ga6aBNEHA.2844@.tk2msftngp13.phx.gbl...
> Thanks Hari
> How do I tell which table. I tried offering up the number above as an ID
to
> sysobjects but nothing came back.
> Paul
>
> "Hari" <hari_prasad_k@.hotmail.com> wrote in message
> news:F3226200-D6DC-4939-8773-4E5CFC0FA567@.microsoft.com...
> > Hi,
> >
> > Please run DBCC checktable to see if there are any corruption related
> errors on this table. Take full database backup before you execute dbcc
> checktable.
> > If the output come clear then you do not want to worry any more.
> >
> > Thanks
> > Hari
> > MCDBA
> >
> >
> > -- Paul Cahill wrote: --
> >
> > For about two hours last evening our database started producing
these
> errors
> > and various jobs failed.
> > This morning all seems quiet. However we do rebuild our indexes
> overnight.
> > Should we worry about this?
> >
> > The jobs that failed do not process any text columns (the only
> mention I
> > found on microsofts site).
> >
> > The File ID cannot relate to sysfiles. Does anyone know what is
does
> relate
> > to?
> >
> > SQL Server 2000 SP3A.
> >
> >
> >
>|||I was starting to suspect as much.
Let's just assume this never happened :)
Paul
"Hari" <hari_prasad_k@.hotmail.com> wrote in message
news:Oom$kfBNEHA.3420@.TK2MSFTNGP11.phx.gbl...
> Hi,
> I feel that it should be a problem with tempdb. If it is the case no
issues.
> Anyway can you execute DBCC CHECKDB('dbname') for that database and ensure
> no errors.
> Thanks
> Hari
> MCDBA
>
> "Paul Cahill" <XYZpaul.cahillXYZ@.blueyonder.co.uk> wrote in message
> news:O0Ga6aBNEHA.2844@.tk2msftngp13.phx.gbl...
> > Thanks Hari
> >
> > How do I tell which table. I tried offering up the number above as an ID
> to
> > sysobjects but nothing came back.
> >
> > Paul
> >
> >
> >
> > "Hari" <hari_prasad_k@.hotmail.com> wrote in message
> > news:F3226200-D6DC-4939-8773-4E5CFC0FA567@.microsoft.com...
> > > Hi,
> > >
> > > Please run DBCC checktable to see if there are any corruption related
> > errors on this table. Take full database backup before you execute dbcc
> > checktable.
> > > If the output come clear then you do not want to worry any more.
> > >
> > > Thanks
> > > Hari
> > > MCDBA
> > >
> > >
> > > -- Paul Cahill wrote: --
> > >
> > > For about two hours last evening our database started producing
> these
> > errors
> > > and various jobs failed.
> > > This morning all seems quiet. However we do rebuild our indexes
> > overnight.
> > > Should we worry about this?
> > >
> > > The jobs that failed do not process any text columns (the only
> > mention I
> > > found on microsofts site).
> > >
> > > The File ID cannot relate to sysfiles. Does anyone know what is
> does
> > relate
> > > to?
> > >
> > > SQL Server 2000 SP3A.
> > >
> > >
> > >
> >
> >
>
Monday, March 19, 2012
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment