Error repair DB with dbcc checkdb

Hi,
I try to repair DB that is in state Emergency Mode, but=20
execute it the following instruction:
dbcc checkdb ('viaticos', REPAIR_ALLOW_DATA_LOSS )
with ALL_ERRORMSGS
show the error
Server: Msg 8966, Level 16, State 1, Line 1
No se puede leer y establecer un pestillo en la p=E1gina=20
(1:177) con el tipo de
pestillo SH. Error en sysindexes.
Ejecuci=F3n de DBCC completada. Si hay mensajes de error,=20
consulte al
administrador del sistema.
How do i for repair the DB?
Than'k
From Google translation page:
A latch in the page (1:177) with the type of latch SH. Error in sysindexes
cannot be read and be established.
(Pretty good translation actually)
One of the pages in the leaf level of the sysindexes clustered index is
corrupt. This error cannot be repaired so you'll have to revert to your
disaster recovery strategy. I recommend you call Product Support to help you
out. (http://support.microsoft.com)
Regards
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Ivan Alexander Laverde" <anonymous@.discussions.microsoft.com> wrote in
message news:104c001c43f4c$d6aaaaf0$a101280a@.phx.gbl...
Hi,
I try to repair DB that is in state Emergency Mode, but
execute it the following instruction:
dbcc checkdb ('viaticos', REPAIR_ALLOW_DATA_LOSS )
with ALL_ERRORMSGS
show the error
Server: Msg 8966, Level 16, State 1, Line 1
No se puede leer y establecer un pestillo en la pgina
(1:177) con el tipo de
pestillo SH. Error en sysindexes.
Ejecucin de DBCC completada. Si hay mensajes de error,
consulte al
administrador del sistema.
How do i for repair the DB?
Than'k

Error repair DB with dbcc checkdb

Hi,
I try to repair DB that is in state Emergency Mode, but execute it the following instruction:
dbcc checkdb ('viaticos', REPAIR_ALLOW_DATA_LOSS )
with ALL_ERRORMSGS
show the error
Server: Msg 8966, Level 16, State 1, Line 1
No se puede leer y establecer un pestillo en la p=E1gina (1:177) con el tipo de
pestillo SH. Error en sysindexes.
Ejecuci=F3n de DBCC completada. Si hay mensajes de error, consulte al
administrador del sistema.
How do i for repair the DB?
Than'kFrom Google translation page:
A latch in the page (1:177) with the type of latch SH. Error in sysindexes
cannot be read and be established.
(Pretty good translation actually)
One of the pages in the leaf level of the sysindexes clustered index is
corrupt. This error cannot be repaired so you'll have to revert to your
disaster recovery strategy. I recommend you call Product Support to help you
out. (http://support.microsoft.com)
Regards
--
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Ivan Alexander Laverde" <anonymous@.discussions.microsoft.com> wrote in
message news:104c001c43f4c$d6aaaaf0$a101280a@.phx.gbl...
Hi,
I try to repair DB that is in state Emergency Mode, but
execute it the following instruction:
dbcc checkdb ('viaticos', REPAIR_ALLOW_DATA_LOSS )
with ALL_ERRORMSGS
show the error
Server: Msg 8966, Level 16, State 1, Line 1
No se puede leer y establecer un pestillo en la página
(1:177) con el tipo de
pestillo SH. Error en sysindexes.
Ejecución de DBCC completada. Si hay mensajes de error,
consulte al
administrador del sistema.
How do i for repair the DB?
Than'k

Error repair DB with dbcc checkdb

Hi,
I try to repair DB that is in state Emergency Mode, but=20
execute it the following instruction:
dbcc checkdb ('viaticos', REPAIR_ALLOW_DATA_LOSS )
with ALL_ERRORMSGS
show the error
Server: Msg 8966, Level 16, State 1, Line 1
No se puede leer y establecer un pestillo en la p=E1gina=20
(1:177) con el tipo de
pestillo SH. Error en sysindexes.
Ejecuci=F3n de DBCC completada. Si hay mensajes de error,=20
consulte al
administrador del sistema.
How do i for repair the DB?
Than'kFrom Google translation page:
A latch in the page (1:177) with the type of latch SH. Error in sysindexes
cannot be read and be established.
(Pretty good translation actually)
One of the pages in the leaf level of the sysindexes clustered index is
corrupt. This error cannot be repaired so you'll have to revert to your
disaster recovery strategy. I recommend you call Product Support to help you
out. (http://support.microsoft.com)
Regards
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Ivan Alexander Laverde" <anonymous@.discussions.microsoft.com> wrote in
message news:104c001c43f4c$d6aaaaf0$a101280a@.phx
.gbl...
Hi,
I try to repair DB that is in state Emergency Mode, but
execute it the following instruction:
dbcc checkdb ('viaticos', REPAIR_ALLOW_DATA_LOSS )
with ALL_ERRORMSGS
show the error
Server: Msg 8966, Level 16, State 1, Line 1
No se puede leer y establecer un pestillo en la pgina
(1:177) con el tipo de
pestillo SH. Error en sysindexes.
Ejecucin de DBCC completada. Si hay mensajes de error,
consulte al
administrador del sistema.
How do i for repair the DB?
Than'ksql

error rebuild index with dbcc

I have an error like this, every time I reindex this table
via db maintenance plan.
Rebuilding indexes for table 'tbJOTrStatusbyWC'
[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'.
What does it means this error ?
How to setting 'QUOTED_IDENTIFIER, ARITHABORT'
thx.You most probably have an index on a computed columns or an indexed view. And unfortunately, the
maint plan doesn't execute the needed SET commands to be able to rebuild these indexes. You would
have to create your own (TSQL) job where you execute needed SET commands and then DBCC DBREINDEX (or
DBCC INDEXDEFRAG).
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as ugroup=microsoft.public.sqlserver
"kresna rudy kurniawan" <kresnark@.yahoo.com> wrote in message
news:3c9401c37b42$a2255740$a601280a@.phx.gbl...
> I have an error like this, every time I reindex this table
> via db maintenance plan.
> Rebuilding indexes for table 'tbJOTrStatusbyWC'
> [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'.
> What does it means this error ?
> How to setting 'QUOTED_IDENTIFIER, ARITHABORT'
> thx.|||Tibor is correct in that the maintenance wizard has issues with things such
as computed columns and indexed views. I suggest you create your own
scheduled job to do the DBREINDEX and not use the wizard and all should be
fine.
--
Andrew J. Kelly
SQL Server MVP
"Tibor Karaszi" <tibor.please_reply_to_public_forum.karaszi@.cornerstone.se>
wrote in message news:u$PV9Y2eDHA.3788@.tk2msftngp13.phx.gbl...
> > You are wrong,
> I'm pretty certain that I'm not. But you are welcome to think so, if you
wish.
> I still recommend that you check very closely if you have either indexes
on computed columns or
> indexes on views.
> You do not need any special SET options if you have an PK over several
columns, so it has to be
> something else.
> --
> Tibor Karaszi, SQL Server MVP
> Archive at: http://groups.google.com/groups?oi=djq&as
ugroup=microsoft.public.sqlserver
>
> "kresna rudy kurniawan" <kresnark@.yahoo.com> wrote in message
> news:3d9d01c37b5e$e471ee80$a601280a@.phx.gbl...
> > You are wrong,
> >
> > I don't use a computed columns, I use multi colums(JONo,
> > OPID,seqNo) for my primay key, this is the structure.
> >
> > TrackMainID int 4 1
> > JONo int 4 0
> > OPID int 4 0
> > SeqNo int 4 0
> > QtyIN numeric 5 1
> > QtyOut numeric 5 1
> > QtyOpen numeric 5 1
> > WCID int 4 1
> > FirstInDate datetime 8 1
> > LastOutDate datetime 8 1
> >
> > I still don't understand the message : incorrect
> > settings: 'QUOTED_IDENTIFIER, ARITHABORT'
> >
> > I must setting where ?
> >
> >
> >
> > >--Original Message--
> > >You most probably have an index on a computed columns or
> > an indexed view. And unfortunately, the
> > >maint plan doesn't execute the needed SET commands to be
> > able to rebuild these indexes. You would
> > >have to create your own (TSQL) job where you execute
> > needed SET commands and then DBCC DBREINDEX (or
> > >DBCC INDEXDEFRAG).
> > >
> > >--
> > >Tibor Karaszi, SQL Server MVP
> > >Archive at: http://groups.google.com/groups?oi=djq&as
> > ugroup=microsoft.public.sqlserver
> > >
> > >
> > >"kresna rudy kurniawan" <kresnark@.yahoo.com> wrote in
> > message
> > >news:3c9401c37b42$a2255740$a601280a@.phx.gbl...
> > >> I have an error like this, every time I reindex this
> > table
> > >> via db maintenance plan.
> > >>
> > >> Rebuilding indexes for table 'tbJOTrStatusbyWC'
> > >> [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'.
> > >>
> > >> What does it means this error ?
> > >> How to setting 'QUOTED_IDENTIFIER, ARITHABORT'
> > >>
> > >> thx.
> > >
> > >
> > >.
> > >
>sql

error msg 601

Hallo,
I'm using SQL Server 2000.
I've made solution:
1. Dbcc checktable (sysobjects) with no_infomsgs
2. And I'was also removing all hint "WITH (NOLOCK)" behind the INSERTED
and DELETED tables
Can anybody help me?
rgds
betty
Betty,
what are you trying to do ?
INSERTED and DELETED are no real tables, but virtual views of the
transaction log which you use inside a trigger.
Markus
|||Hi..
Thx 4 u.
For remaining-me `bout INSERTED and DELETED. But actualy i have no problem
with INSERTED and DELETED. I've just tried to make some ilustration with IT.
So what i'm doing for with Error 601 ?
betty
<m.bohse@.quest-consultants.com> wrote in message
news:1133426095.099168.137810@.g49g2000cwa.googlegr oups.com...
> Betty,
> what are you trying to do ?
> INSERTED and DELETED are no real tables, but virtual views of the
> transaction log which you use inside a trigger.
> Markus
>

Error message:

One of our production box is running really slow right now.. and I issue the following statement: DBCC MEMUSAGE and I got back the following error message:
Server: Msg 8966, Level 16, State 4, Line 1
Could not read and latch page (1:204858) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (1:206393) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (1:206392) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
The comment doesn't even finish. I thought there were some corruption on our databases, but I schedule a job and ran it through all our databases with DBCC checkdb. None of them seems to have any integrity or data corruption problem.
Any idea where else I should look for any possible problems? I free the buffer and procedure cache using
DBCC FREEPROCCACHE
go
DBCC DROPCLEANBUFFERS
go
already!
help!
What sql server build are you on? You might consider going through
826433 PRB: Additional SQL Server Diagnostics Added to Detect Unreported I/O
http://support.microsoft.com/?id=826433 and also considre opening a case
with PSS Support for this.
In the meantime, I'd suggest you check your Application and Sys event logs
for hardware errors. Also check your backups. Do you see the same error
message after restoring them?
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.

Error message:

One of our production box is running really slow right now.. and I issue the
following statement: DBCC MEMUSAGE and I got back the following error mess
age:
Server: Msg 8966, Level 16, State 4, Line 1
Could not read and latch page (1:204858) with latch type SH. VerifyPageId fa
iled.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (1:206393) with latch type SH. VerifyPageId fa
iled.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (1:206392) with latch type SH. VerifyPageId fa
iled.
Server: Msg 8966, Level 16, State 1, Line 1
The comment doesn't even finish. I thought there were some corruption on ou
r databases, but I schedule a job and ran it through all our databases with
DBCC checkdb. None of them seems to have any integrity or data corruption p
roblem.
Any idea where else I should look for any possible problems? I free the buf
fer and procedure cache using
DBCC FREEPROCCACHE
go
DBCC DROPCLEANBUFFERS
go
already!
help!What sql server build are you on? You might consider going through
826433 PRB: Additional SQL Server Diagnostics Added to Detect Unreported I/O
http://support.microsoft.com/?id=826433 and also considre opening a case
with PSS Support for this.
In the meantime, I'd suggest you check your Application and Sys event logs
for hardware errors. Also check your backups. Do you see the same error
message after restoring them?
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.

Error message:

One of our production box is running really slow right now.. and I issue the following statement: DBCC MEMUSAGE and I got back the following error message:
Server: Msg 8966, Level 16, State 4, Line 1
Could not read and latch page (1:204858) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (1:206393) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (1:206392) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
The comment doesn't even finish. I thought there were some corruption on our databases, but I schedule a job and ran it through all our databases with DBCC checkdb. None of them seems to have any integrity or data corruption problem.
Any idea where else I should look for any possible problems? I free the buffer and procedure cache using
DBCC FREEPROCCACHE
go
DBCC DROPCLEANBUFFERS
go
already!
help!What sql server build are you on? You might consider going through
826433 PRB: Additional SQL Server Diagnostics Added to Detect Unreported I/O
http://support.microsoft.com/?id=826433 and also considre opening a case
with PSS Support for this.
In the meantime, I'd suggest you check your Application and Sys event logs
for hardware errors. Also check your backups. Do you see the same error
message after restoring them?
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.