DB2 Linked Server

Hi List, anyone can help me?
I need to make a connection between SQL2000 SP3 and DB2 running on AS400.
When i try to make a Linked server i could not be able to see the ODBC
Driver for DB2.
What driver is needed to install the odbc support? is from MS?
ThanksHi
You need to get the DB2 ODBC/OLE DB driver from IBM and install it on your
SQL Server.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Tinchos" <Tinchos@.discussions.microsoft.com> wrote in message
news:A9564915-2DC7-431F-B1C3-BC4565CC5DCB@.microsoft.com...
> Hi List, anyone can help me?
> I need to make a connection between SQL2000 SP3 and DB2 running on AS400.
> When i try to make a Linked server i could not be able to see the ODBC
> Driver for DB2.
> What driver is needed to install the odbc support? is from MS?
> Thanks|||Mike Epprecht (SQL MVP) wrote:
> Hi
> You need to get the DB2 ODBC/OLE DB driver from IBM and install it on your
> SQL Server.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Tinchos" <Tinchos@.discussions.microsoft.com> wrote in message
> news:A9564915-2DC7-431F-B1C3-BC4565CC5DCB@.microsoft.com...
>>Hi List, anyone can help me?
>>I need to make a connection between SQL2000 SP3 and DB2 running on AS400.
>>When i try to make a Linked server i could not be able to see the ODBC
>>Driver for DB2.
>>What driver is needed to install the odbc support? is from MS?
>>Thanks
>
>
and when you do, please tell us how did you set the connection string

DB2 Linked Server

Hi List, anyone can help me?
I need to make a connection between SQL2000 SP3 and DB2 running on AS400.
When i try to make a Linked server i could not be able to see the ODBC
Driver for DB2.
What driver is needed to install the odbc support? is from MS?
ThanksHi
You need to get the DB2 ODBC/OLE DB driver from IBM and install it on your
SQL Server.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Tinchos" <Tinchos@.discussions.microsoft.com> wrote in message
news:A9564915-2DC7-431F-B1C3-BC4565CC5DCB@.microsoft.com...
> Hi List, anyone can help me?
> I need to make a connection between SQL2000 SP3 and DB2 running on AS400.
> When i try to make a Linked server i could not be able to see the ODBC
> Driver for DB2.
> What driver is needed to install the odbc support? is from MS?
> Thanks|||Mike Epprecht (SQL MVP) wrote:
> Hi
> You need to get the DB2 ODBC/OLE DB driver from IBM and install it on your
> SQL Server.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Tinchos" <Tinchos@.discussions.microsoft.com> wrote in message
> news:A9564915-2DC7-431F-B1C3-BC4565CC5DCB@.microsoft.com...
>
>
>
and when you do, please tell us how did you set the connection string

DB2 Linked Server

Hi List, anyone can help me?
I need to make a connection between SQL2000 SP3 and DB2 running on AS400.
When i try to make a Linked server i could not be able to see the ODBC
Driver for DB2.
What driver is needed to install the odbc support? is from MS?
Thanks
Hi
You need to get the DB2 ODBC/OLE DB driver from IBM and install it on your
SQL Server.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Tinchos" <Tinchos@.discussions.microsoft.com> wrote in message
news:A9564915-2DC7-431F-B1C3-BC4565CC5DCB@.microsoft.com...
> Hi List, anyone can help me?
> I need to make a connection between SQL2000 SP3 and DB2 running on AS400.
> When i try to make a Linked server i could not be able to see the ODBC
> Driver for DB2.
> What driver is needed to install the odbc support? is from MS?
> Thanks
|||Mike Epprecht (SQL MVP) wrote:
> Hi
> You need to get the DB2 ODBC/OLE DB driver from IBM and install it on your
> SQL Server.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Tinchos" <Tinchos@.discussions.microsoft.com> wrote in message
> news:A9564915-2DC7-431F-B1C3-BC4565CC5DCB@.microsoft.com...
>
>
and when you do, please tell us how did you set the connection string

DB_NAME anomaly

On my SP3 db_name(0) and db_name(1) are returning the same thing. Can anybody else try this? Beta of Yukon is doing the same thing...But the following code returns 1:

select db_id(db_name(0))I think that is expected behavior. Try running:USE master
GO
SELECT db_id(db_name(0)), db_id(db_name(1)), db_name(0)
USE tempdb
GO
SELECT db_id(db_name(0)), db_id(db_name(1)), db_name(0)
USE model
GO
SELECT db_id(db_name(0)), db_id(db_name(1)), db_name(0)
USE msdb
GO
SELECT db_id(db_name(0)), db_id(db_name(1)), db_name(0)
USE pubs
GO
SELECT db_id(db_name(0)), db_id(db_name(1)), db_name(0)To see if you get:
-- -- ---------------------------------------
1 1 master

(1 row(s) affected)


-- -- ---------------------------------------
2 1 tempdb

(1 row(s) affected)


-- -- ---------------------------------------
3 1 model

(1 row(s) affected)


-- -- ---------------------------------------
4 1 msdb

(1 row(s) affected)


-- -- ---------------------------------------
5 1 pubs

(1 row(s) affected)-PatP|||Got it, db_name(0) is the same as db_name(), - the current database.

The reason I asked was because sysprocesses have house-keeping-related processes with dbid=0 which are being reported to have no database context. Once I changed "where db_name(dbid) is not null" to "where dbid > 0" everything worked OK.|||The reason I asked was because sysprocesses have house-keeping-related processes......

Sure it does.. :D
Now who's on crack huh?

by the way how is that sp_recompile going.. :D

DB Will not Grow

I am running SQL Server 2000 with SP3 and all avail hotfixes and security patches since then. I try to keep very current on patches and security hotfixes. It is on a rather large IBM Win 2K server box with all the latest SP and security hotfixes.

I have read the problem when the file can not grow fast enough to keep up and I agree with you that does not seem to be the problem. If that was the case I should still be able to grow the file manually with Enterprise manager or Alter Database command. When I try to change the file size in Enterprise manager it acts like it changes it but if I change it press OK then open it back up it is set back to what it was previously, and puts the following error in the SQL error logs:

Source spid65
fcb::ZeroFile(): GetOverLappedResult() failed with error 2.

The same error happens in the SQL error logs when running the Alter Database command even though it says it completed successfully it never changes the size.

I do think this error is the source of my problem but I can find it no where on the web, on Microsofts site, in this or any other message boards even. Either I have something set up very wrong or I found a new bug.

The real thing that gets me is that the transaction log grows just fine but the data file will not. Although if I try to shrink the transaction log file it will not shrink, which maybe related to this or it could be its own problem.

I have tried to set it to grow in MB rather than % I agree this should be the way it is always done, but that does not seem to help either.Try to capture the events using PROFILER during this process.

And refer to this KBA (http://support.microsoft.com/default.aspx?scid=KB;en-us;Q305635) for more information.|||Is this a clustered system? We are seeing the same problem after failing over our cluster, running SQL 2000 Enterprise w SP2. Prior to the failover last week, when our server guys installed some new OS patches, everything was normal. I added a second data file on the Primary filegroup as a short-term measure, but I'm going to call MS soon if I can't figure it out.

Thanks,
James

DB Suspect (full error log attached)

Hi Gurus,
One of my DBs on a SQL box (SQL 2000 enterprise edtion SP3 on Win2k Advanced server) went suspect yesterday. Here is part of the error log. Would appreciate any help/suggestions.
2004-06-07 16:17:42.74 spid72 Getpage: bstat=0x9, sstat=0x10000, cache
2004-06-07 16:17:42.74 spid72 pageno is/should be:objid is/should be:
2004-06-07 16:17:42.74 spid72 (1:772511)/(1:772511)457768688/1269579561
2004-06-07 16:17:42.74 spid72 ... IAM indicates that page is allocated to this object
2004-06-07 16:17:42.74 spid72 Error: 605, Severity: 21, State: 1
2004-06-07 16:17:42.74 spid72 Attempt to fetch logical page (1:772511) in database 'S094000' belongs to object 't050_pre_arch', not to object 't050_campaign_candidate'..
2004-06-07 16:17:42.75 spid72 Error: 644, Severity: 21, State: 5
2004-06-07 16:17:42.75 spid72 Could not find the index entry for RID '16905830100' in index page (1:772510), index ID 9, database 'S094000'..
2004-06-07 16:17:42.75 spid72 Error: 3314, Severity: 21, State: 4
2004-06-07 16:17:42.75 spid72 Error while undoing logged operation in database 'S094000'. Error at log record ID (63154:9493:281)..
2004-06-07 16:17:42.80 spid72 Using 'dbghelp.dll' version '4.0.5'
*Dump thread - spid = 72, PSS = 0x70f85200, EC = 0x70f85528
(actual dump manually taken out here)
* ----
2004-06-07 16:17:44.77 spid72 Stack Signature for the dump is 0x03737F82
2004-06-07 16:17:44.77 spid72 SQL Server Assertion: File: <scanrid.cpp>, line=321
Failed Assertion = 'm_len != 0'.
2004-06-07 16:17:44.77 spid72 Error: 3624, Severity: 20, State: 1.
2004-06-07 16:17:45.05 spid72 Error: 3314, Severity: 21, State: 4
2004-06-07 16:17:45.05 spid72 Error while undoing logged operation in database 'S094000'. Error at log record ID (63154:9493:281)..
2004-06-07 16:17:45.05 spid72 Error: 9001, Severity: 21, State: 1
2004-06-07 16:17:45.05 spid72 The log for database 'S094000' is not available..
2004-06-07 16:17:45.36 spid72 Error: 3314, Severity: 21, State: 5
2004-06-07 16:17:45.36 spid72 Error while undoing logged operation in database 'S094000'. Error at log record ID (63154:9189:1)..
2004-06-07 16:17:46.34 spid15 Starting up database 'S094000'.
2004-06-07 16:17:47.56 spid15 Analysis of database 'S094000' (27) is 16% complete (approximately 2 more seconds)
2004-06-07 16:17:49.28 spid15 Analysis of database 'S094000' (27) is 100% complete (approximately 0 more seconds)
2004-06-07 16:17:49.30 spid15 Recovery of database 'S094000' (27) is 0% complete (approximately 28 more seconds) (Phase 2 of 3).
2004-06-07 16:18:09.83 spid15 Recovery of database 'S094000' (27) is 17% complete (approximately 98 more seconds) (Phase 2 of 3).
2004-06-07 16:18:13.50 spid15 Recovery of database 'S094000' (27) is 21% complete (approximately 88 more seconds) (Phase 2 of 3).
2004-06-07 16:18:18.67 spid15 Recovery of database 'S094000' (27) is 25% complete (approximately 83 more seconds) (Phase 2 of 3).
2004-06-07 16:18:23.36 spid15 Recovery of database 'S094000' (27) is 30% complete (approximately 77 more seconds) (Phase 2 of 3).
2004-06-07 16:18:28.38 spid15 Recovery of database 'S094000' (27) is 34% complete (approximately 72 more seconds) (Phase 2 of 3).
2004-06-07 16:18:34.88 spid15 Recovery of database 'S094000' (27) is 39% complete (approximately 69 more seconds) (Phase 2 of 3).
2004-06-07 16:18:39.81 spid15 Recovery of database 'S094000' (27) is 43% complete (approximately 64 more seconds) (Phase 2 of 3).
2004-06-07 16:18:44.13 spid15 Recovery of database 'S094000' (27) is 48% complete (approximately 58 more seconds) (Phase 2 of 3).
2004-06-07 16:18:48.85 spid15 Recovery of database 'S094000' (27) is 52% complete (approximately 53 more seconds) (Phase 2 of 3).
2004-06-07 16:18:54.44 spid15 Recovery of database 'S094000' (27) is 56% complete (approximately 48 more seconds) (Phase 2 of 3).
2004-06-07 16:19:00.66 spid15 Recovery of database 'S094000' (27) is 61% complete (approximately 44 more seconds) (Phase 2 of 3).
2004-06-07 16:19:06.38 spid15 Recovery of database 'S094000' (27) is 65% complete (approximately 39 more seconds) (Phase 2 of 3).
2004-06-07 16:19:12.85 spid15 Recovery of database 'S094000' (27) is 70% complete (approximately 35 more seconds) (Phase 2 of 3).
2004-06-07 16:19:19.55 spid15 Recovery of database 'S094000' (27) is 74% complete (approximately 30 more seconds) (Phase 2 of 3).
2004-06-07 16:19:27.02 spid15 Recovery of database 'S094000' (27) is 78% complete (approximately 26 more seconds) (Phase 2 of 3).
2004-06-07 16:19:34.21 spid15 Recovery of database 'S094000' (27) is 82% complete (approximately 21 more seconds) (Phase 2 of 3).
2004-06-07 16:19:43.72 spid15 Recovery of database 'S094000' (27) is 86% complete (approximately 17 more seconds) (Phase 2 of 3).
2004-06-07 16:19:52.25 spid15 Recovery of database 'S094000' (27) is 90% complete (approximately 12 more seconds) (Phase 2 of 3).
2004-06-07 16:20:02.85 spid15 Recovery of database 'S094000' (27) is 93% complete (approximately 7 more seconds) (Phase 2 of 3).
2004-06-07 16:20:14.79 spid15 Recovery of database 'S094000' (27) is 97% complete (approximately 3 more seconds) (Phase 2 of 3).
2004-06-07 16:20:23.47 spid15 Recovery of database 'S094000' (27) is 99% complete (approximately 0 more seconds) (Phase 2 of 3).
2004-06-07 16:20:23.47 spid15 266 transactions rolled forward in database 'S094000' (27).
2004-06-07 16:20:23.72 spid15 Recovery of database 'S094000' (27) is 99% complete (approximately 0 more seconds) (Phase 3 of 3).
2004-06-07 16:20:25.04 spid15 Recovery of database 'S094000' (27) is 100% complete (approximately 0 more seconds) (Phase 3 of 3).
2004-06-07 16:20:25.04 spid15 1 transactions rolled back in database 'S094000' (27).
2004-06-07 16:20:25.05 spid15 Recovery is checkpointing database 'S094000' (27)
2004-06-07 16:21:19.65 spid61 Getpage: bstat=0x9, sstat=0x10000, cache
2004-06-07 16:21:19.65 spid61 pageno is/should be:objid is/should be:
2004-06-07 16:21:19.65 spid61 (1:772511)/(1:772511)457768688/1269579561
2004-06-07 16:21:19.65 spid61 ... IAM indicates that page is allocated to this object
2004-06-07 16:21:19.65 spid61 Error: 605, Severity: 21, State: 1
2004-06-07 16:21:19.65 spid61 Attempt to fetch logical page (1:772511) in database 'S094000' belongs to object 't050_pre_arch', not to object 't050_campaign_candidate'..
2004-06-07 16:21:19.71 spid61 Error: 644, Severity: 21, State: 5
2004-06-07 16:21:19.71 spid61 Could not find the index entry for RID '16905830100' in index page (1:772510), index ID 9, database 'S094000'..
2004-06-07 16:21:19.71 spid61 Error: 3314, Severity: 21, State: 4
2004-06-07 16:21:19.71 spid61 Error while undoing logged operation in database 'S094000'. Error at log record ID (63154:10761:6)..
2004-06-07 16:21:19.71 spid61 Using 'dbghelp.dll' version '4.0.5'
*Dump thread - spid = 61, PSS = 0x43897200, EC = 0x43897528
Hi -
1. Important :: {Do you have previously clean backup? If yes, please restore
from the backup.}
OR
1. Execute DBCC CHECKDB to determine the extent of the damage, use the
REPAIR_REBUILD clause. If problem persists drop and re-create the index
Also Please provide output from DBCC CHECKDB.
2. Examine the error log for any errors prior to error 3414. It is important
to examine errors that occurred before the first occurrence of error 3414
because subsequent attempts to start the server might not give the detailed
error information you need to diagnose the problem. If you do not have
sufficient information to recover from the previous errors, you can recover
from known clean backups
I guess the problem is with the corrupt index Allocation Map or some thing
whirred in the sysobjects table.
Thanks
-Surajit
"G0" <anonymous@.discussions.microsoft.com> wrote in message
news:6AB317BC-5A70-43FC-BB47-33D5ED697253@.microsoft.com...
> Hi Gurus,
> One of my DBs on a SQL box (SQL 2000 enterprise edtion SP3 on Win2k
Advanced server) went suspect yesterday. Here is part of the error log.
Would appreciate any help/suggestions.
>
> 2004-06-07 16:17:42.74 spid72 Getpage: bstat=0x9, sstat=0x10000, cache
> 2004-06-07 16:17:42.74 spid72 pageno is/should be: objid is/should
be:
> 2004-06-07 16:17:42.74 spid72 (1:772511)/(1:772511)
457768688/1269579561
> 2004-06-07 16:17:42.74 spid72 ... IAM indicates that page is allocated
to this object
> 2004-06-07 16:17:42.74 spid72 Error: 605, Severity: 21, State: 1
> 2004-06-07 16:17:42.74 spid72 Attempt to fetch logical page (1:772511)
in database 'S094000' belongs to object 't050_pre_arch', not to object
't050_campaign_candidate'..
> 2004-06-07 16:17:42.75 spid72 Error: 644, Severity: 21, State: 5
> 2004-06-07 16:17:42.75 spid72 Could not find the index entry for RID
'16905830100' in index page (1:772510), index ID 9, database 'S094000'..
> 2004-06-07 16:17:42.75 spid72 Error: 3314, Severity: 21, State: 4
> 2004-06-07 16:17:42.75 spid72 Error while undoing logged operation in
database 'S094000'. Error at log record ID (63154:9493:281)..
> 2004-06-07 16:17:42.80 spid72 Using 'dbghelp.dll' version '4.0.5'
> *Dump thread - spid = 72, PSS = 0x70f85200, EC = 0x70f85528
> (actual dump manually taken out here)
>
* ----
--
> 2004-06-07 16:17:44.77 spid72 Stack Signature for the dump is
0x03737F82
> 2004-06-07 16:17:44.77 spid72 SQL Server Assertion: File:
<scanrid.cpp>, line=321
> Failed Assertion = 'm_len != 0'.
> 2004-06-07 16:17:44.77 spid72 Error: 3624, Severity: 20, State: 1.
> 2004-06-07 16:17:45.05 spid72 Error: 3314, Severity: 21, State: 4
> 2004-06-07 16:17:45.05 spid72 Error while undoing logged operation in
database 'S094000'. Error at log record ID (63154:9493:281)..
> 2004-06-07 16:17:45.05 spid72 Error: 9001, Severity: 21, State: 1
> 2004-06-07 16:17:45.05 spid72 The log for database 'S094000' is not
available..
> 2004-06-07 16:17:45.36 spid72 Error: 3314, Severity: 21, State: 5
> 2004-06-07 16:17:45.36 spid72 Error while undoing logged operation in
database 'S094000'. Error at log record ID (63154:9189:1)..
> 2004-06-07 16:17:46.34 spid15 Starting up database 'S094000'.
> 2004-06-07 16:17:47.56 spid15 Analysis of database 'S094000' (27) is
16% complete (approximately 2 more seconds)
> 2004-06-07 16:17:49.28 spid15 Analysis of database 'S094000' (27) is
100% complete (approximately 0 more seconds)
> 2004-06-07 16:17:49.30 spid15 Recovery of database 'S094000' (27) is 0%
complete (approximately 28 more seconds) (Phase 2 of 3).
> 2004-06-07 16:18:09.83 spid15 Recovery of database 'S094000' (27) is
17% complete (approximately 98 more seconds) (Phase 2 of 3).
> 2004-06-07 16:18:13.50 spid15 Recovery of database 'S094000' (27) is
21% complete (approximately 88 more seconds) (Phase 2 of 3).
> 2004-06-07 16:18:18.67 spid15 Recovery of database 'S094000' (27) is
25% complete (approximately 83 more seconds) (Phase 2 of 3).
> 2004-06-07 16:18:23.36 spid15 Recovery of database 'S094000' (27) is
30% complete (approximately 77 more seconds) (Phase 2 of 3).
> 2004-06-07 16:18:28.38 spid15 Recovery of database 'S094000' (27) is
34% complete (approximately 72 more seconds) (Phase 2 of 3).
> 2004-06-07 16:18:34.88 spid15 Recovery of database 'S094000' (27) is
39% complete (approximately 69 more seconds) (Phase 2 of 3).
> 2004-06-07 16:18:39.81 spid15 Recovery of database 'S094000' (27) is
43% complete (approximately 64 more seconds) (Phase 2 of 3).
> 2004-06-07 16:18:44.13 spid15 Recovery of database 'S094000' (27) is
48% complete (approximately 58 more seconds) (Phase 2 of 3).
> 2004-06-07 16:18:48.85 spid15 Recovery of database 'S094000' (27) is
52% complete (approximately 53 more seconds) (Phase 2 of 3).
> 2004-06-07 16:18:54.44 spid15 Recovery of database 'S094000' (27) is
56% complete (approximately 48 more seconds) (Phase 2 of 3).
> 2004-06-07 16:19:00.66 spid15 Recovery of database 'S094000' (27) is
61% complete (approximately 44 more seconds) (Phase 2 of 3).
> 2004-06-07 16:19:06.38 spid15 Recovery of database 'S094000' (27) is
65% complete (approximately 39 more seconds) (Phase 2 of 3).
> 2004-06-07 16:19:12.85 spid15 Recovery of database 'S094000' (27) is
70% complete (approximately 35 more seconds) (Phase 2 of 3).
> 2004-06-07 16:19:19.55 spid15 Recovery of database 'S094000' (27) is
74% complete (approximately 30 more seconds) (Phase 2 of 3).
> 2004-06-07 16:19:27.02 spid15 Recovery of database 'S094000' (27) is
78% complete (approximately 26 more seconds) (Phase 2 of 3).
> 2004-06-07 16:19:34.21 spid15 Recovery of database 'S094000' (27) is
82% complete (approximately 21 more seconds) (Phase 2 of 3).
> 2004-06-07 16:19:43.72 spid15 Recovery of database 'S094000' (27) is
86% complete (approximately 17 more seconds) (Phase 2 of 3).
> 2004-06-07 16:19:52.25 spid15 Recovery of database 'S094000' (27) is
90% complete (approximately 12 more seconds) (Phase 2 of 3).
> 2004-06-07 16:20:02.85 spid15 Recovery of database 'S094000' (27) is
93% complete (approximately 7 more seconds) (Phase 2 of 3).
> 2004-06-07 16:20:14.79 spid15 Recovery of database 'S094000' (27) is
97% complete (approximately 3 more seconds) (Phase 2 of 3).
> 2004-06-07 16:20:23.47 spid15 Recovery of database 'S094000' (27) is
99% complete (approximately 0 more seconds) (Phase 2 of 3).
> 2004-06-07 16:20:23.47 spid15 266 transactions rolled forward in
database 'S094000' (27).
> 2004-06-07 16:20:23.72 spid15 Recovery of database 'S094000' (27) is
99% complete (approximately 0 more seconds) (Phase 3 of 3).
> 2004-06-07 16:20:25.04 spid15 Recovery of database 'S094000' (27) is
100% complete (approximately 0 more seconds) (Phase 3 of 3).
> 2004-06-07 16:20:25.04 spid15 1 transactions rolled back in database
'S094000' (27).
> 2004-06-07 16:20:25.05 spid15 Recovery is checkpointing database
'S094000' (27)
> 2004-06-07 16:21:19.65 spid61 Getpage: bstat=0x9, sstat=0x10000, cache
> 2004-06-07 16:21:19.65 spid61 pageno is/should be: objid is/should
be:
> 2004-06-07 16:21:19.65 spid61 (1:772511)/(1:772511)
457768688/1269579561
> 2004-06-07 16:21:19.65 spid61 ... IAM indicates that page is allocated
to this object
> 2004-06-07 16:21:19.65 spid61 Error: 605, Severity: 21, State: 1
> 2004-06-07 16:21:19.65 spid61 Attempt to fetch logical page (1:772511)
in database 'S094000' belongs to object 't050_pre_arch', not to object
't050_campaign_candidate'..
> 2004-06-07 16:21:19.71 spid61 Error: 644, Severity: 21, State: 5
> 2004-06-07 16:21:19.71 spid61 Could not find the index entry for RID
'16905830100' in index page (1:772510), index ID 9, database 'S094000'..
> 2004-06-07 16:21:19.71 spid61 Error: 3314, Severity: 21, State: 4
> 2004-06-07 16:21:19.71 spid61 Error while undoing logged operation in
database 'S094000'. Error at log record ID (63154:10761:6)..
> 2004-06-07 16:21:19.71 spid61 Using 'dbghelp.dll' version '4.0.5'
> *Dump thread - spid = 61, PSS = 0x43897200, EC = 0x43897528
>
>
|||In addition to Surajit's post:
http://www.karaszi.com/SQLServer/inf...suspect_db.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"G0" <anonymous@.discussions.microsoft.com> wrote in message
news:6AB317BC-5A70-43FC-BB47-33D5ED697253@.microsoft.com...
> Hi Gurus,
> One of my DBs on a SQL box (SQL 2000 enterprise edtion SP3 on Win2k Advanced server) went suspect yesterday.
Here is part of the error log. Would appreciate any help/suggestions.
>
> 2004-06-07 16:17:42.74 spid72 Getpage: bstat=0x9, sstat=0x10000, cache
> 2004-06-07 16:17:42.74 spid72 pageno is/should be: objid is/should be:
> 2004-06-07 16:17:42.74 spid72 (1:772511)/(1:772511) 457768688/1269579561
> 2004-06-07 16:17:42.74 spid72 ... IAM indicates that page is allocated to this object
> 2004-06-07 16:17:42.74 spid72 Error: 605, Severity: 21, State: 1
> 2004-06-07 16:17:42.74 spid72 Attempt to fetch logical page (1:772511) in database 'S094000' belongs to
object 't050_pre_arch', not to object 't050_campaign_candidate'..
> 2004-06-07 16:17:42.75 spid72 Error: 644, Severity: 21, State: 5
> 2004-06-07 16:17:42.75 spid72 Could not find the index entry for RID '16905830100' in index page
(1:772510), index ID 9, database 'S094000'..
> 2004-06-07 16:17:42.75 spid72 Error: 3314, Severity: 21, State: 4
> 2004-06-07 16:17:42.75 spid72 Error while undoing logged operation in database 'S094000'. Error at log
record ID (63154:9493:281)..
> 2004-06-07 16:17:42.80 spid72 Using 'dbghelp.dll' version '4.0.5'
> *Dump thread - spid = 72, PSS = 0x70f85200, EC = 0x70f85528
> (actual dump manually taken out here)
> * ----
> 2004-06-07 16:17:44.77 spid72 Stack Signature for the dump is 0x03737F82
> 2004-06-07 16:17:44.77 spid72 SQL Server Assertion: File: <scanrid.cpp>, line=321
> Failed Assertion = 'm_len != 0'.
> 2004-06-07 16:17:44.77 spid72 Error: 3624, Severity: 20, State: 1.
> 2004-06-07 16:17:45.05 spid72 Error: 3314, Severity: 21, State: 4
> 2004-06-07 16:17:45.05 spid72 Error while undoing logged operation in database 'S094000'. Error at log
record ID (63154:9493:281)..
> 2004-06-07 16:17:45.05 spid72 Error: 9001, Severity: 21, State: 1
> 2004-06-07 16:17:45.05 spid72 The log for database 'S094000' is not available..
> 2004-06-07 16:17:45.36 spid72 Error: 3314, Severity: 21, State: 5
> 2004-06-07 16:17:45.36 spid72 Error while undoing logged operation in database 'S094000'. Error at log
record ID (63154:9189:1)..
> 2004-06-07 16:17:46.34 spid15 Starting up database 'S094000'.
> 2004-06-07 16:17:47.56 spid15 Analysis of database 'S094000' (27) is 16% complete (approximately 2 more
seconds)
> 2004-06-07 16:17:49.28 spid15 Analysis of database 'S094000' (27) is 100% complete (approximately 0 more
seconds)
> 2004-06-07 16:17:49.30 spid15 Recovery of database 'S094000' (27) is 0% complete (approximately 28 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:18:09.83 spid15 Recovery of database 'S094000' (27) is 17% complete (approximately 98 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:18:13.50 spid15 Recovery of database 'S094000' (27) is 21% complete (approximately 88 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:18:18.67 spid15 Recovery of database 'S094000' (27) is 25% complete (approximately 83 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:18:23.36 spid15 Recovery of database 'S094000' (27) is 30% complete (approximately 77 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:18:28.38 spid15 Recovery of database 'S094000' (27) is 34% complete (approximately 72 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:18:34.88 spid15 Recovery of database 'S094000' (27) is 39% complete (approximately 69 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:18:39.81 spid15 Recovery of database 'S094000' (27) is 43% complete (approximately 64 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:18:44.13 spid15 Recovery of database 'S094000' (27) is 48% complete (approximately 58 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:18:48.85 spid15 Recovery of database 'S094000' (27) is 52% complete (approximately 53 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:18:54.44 spid15 Recovery of database 'S094000' (27) is 56% complete (approximately 48 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:19:00.66 spid15 Recovery of database 'S094000' (27) is 61% complete (approximately 44 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:19:06.38 spid15 Recovery of database 'S094000' (27) is 65% complete (approximately 39 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:19:12.85 spid15 Recovery of database 'S094000' (27) is 70% complete (approximately 35 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:19:19.55 spid15 Recovery of database 'S094000' (27) is 74% complete (approximately 30 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:19:27.02 spid15 Recovery of database 'S094000' (27) is 78% complete (approximately 26 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:19:34.21 spid15 Recovery of database 'S094000' (27) is 82% complete (approximately 21 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:19:43.72 spid15 Recovery of database 'S094000' (27) is 86% complete (approximately 17 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:19:52.25 spid15 Recovery of database 'S094000' (27) is 90% complete (approximately 12 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:20:02.85 spid15 Recovery of database 'S094000' (27) is 93% complete (approximately 7 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:20:14.79 spid15 Recovery of database 'S094000' (27) is 97% complete (approximately 3 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:20:23.47 spid15 Recovery of database 'S094000' (27) is 99% complete (approximately 0 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:20:23.47 spid15 266 transactions rolled forward in database 'S094000' (27).
> 2004-06-07 16:20:23.72 spid15 Recovery of database 'S094000' (27) is 99% complete (approximately 0 more
seconds) (Phase 3 of 3).
> 2004-06-07 16:20:25.04 spid15 Recovery of database 'S094000' (27) is 100% complete (approximately 0 more
seconds) (Phase 3 of 3).
> 2004-06-07 16:20:25.04 spid15 1 transactions rolled back in database 'S094000' (27).
> 2004-06-07 16:20:25.05 spid15 Recovery is checkpointing database 'S094000' (27)
> 2004-06-07 16:21:19.65 spid61 Getpage: bstat=0x9, sstat=0x10000, cache
> 2004-06-07 16:21:19.65 spid61 pageno is/should be: objid is/should be:
> 2004-06-07 16:21:19.65 spid61 (1:772511)/(1:772511) 457768688/1269579561
> 2004-06-07 16:21:19.65 spid61 ... IAM indicates that page is allocated to this object
> 2004-06-07 16:21:19.65 spid61 Error: 605, Severity: 21, State: 1
> 2004-06-07 16:21:19.65 spid61 Attempt to fetch logical page (1:772511) in database 'S094000' belongs to
object 't050_pre_arch', not to object 't050_campaign_candidate'..
> 2004-06-07 16:21:19.71 spid61 Error: 644, Severity: 21, State: 5
> 2004-06-07 16:21:19.71 spid61 Could not find the index entry for RID '16905830100' in index page
(1:772510), index ID 9, database 'S094000'..
> 2004-06-07 16:21:19.71 spid61 Error: 3314, Severity: 21, State: 4
> 2004-06-07 16:21:19.71 spid61 Error while undoing logged operation in database 'S094000'. Error at log
record ID (63154:10761:6)..
> 2004-06-07 16:21:19.71 spid61 Using 'dbghelp.dll' version '4.0.5'
> *Dump thread - spid = 61, PSS = 0x43897200, EC = 0x43897528
>
>

DB Suspect (full error log attached)

Hi Gurus,
One of my DBs on a SQL box (SQL 2000 enterprise edtion SP3 on Win2k Advanced
server) went suspect yesterday. Here is part of the error log. Would apprec
iate any help/suggestions.
2004-06-07 16:17:42.74 spid72 Getpage: bstat=0x9, sstat=0x10000, cache
2004-06-07 16:17:42.74 spid72 pageno is/should be: objid is/should be:
2004-06-07 16:17:42.74 spid72 (1:772511)/(1:772511) 457768688/12695795
61
2004-06-07 16:17:42.74 spid72 ... IAM indicates that page is allocated to
this object
2004-06-07 16:17:42.74 spid72 Error: 605, Severity: 21, State: 1
2004-06-07 16:17:42.74 spid72 Attempt to fetch logical page (1:772511) in
database 'S094000' belongs to object 't050_pre_arch', not to object 't050_c
ampaign_candidate'..
2004-06-07 16:17:42.75 spid72 Error: 644, Severity: 21, State: 5
2004-06-07 16:17:42.75 spid72 Could not find the index entry for RID '169
05830100' in index page (1:772510), index ID 9, database 'S094000'..
2004-06-07 16:17:42.75 spid72 Error: 3314, Severity: 21, State: 4
2004-06-07 16:17:42.75 spid72 Error while undoing logged operation in dat
abase 'S094000'. Error at log record ID (63154:9493:281)..
2004-06-07 16:17:42.80 spid72 Using 'dbghelp.dll' version '4.0.5'
*Dump thread - spid = 72, PSS = 0x70f85200, EC = 0x70f85528
(actual dump manually taken out here)
* ----
--
2004-06-07 16:17:44.77 spid72 Stack Signature for the dump is 0x03737F82
2004-06-07 16:17:44.77 spid72 SQL Server Assertion: File: <scanrid.cpp>,
line=321
Failed Assertion = 'm_len != 0'.
2004-06-07 16:17:44.77 spid72 Error: 3624, Severity: 20, State: 1.
2004-06-07 16:17:45.05 spid72 Error: 3314, Severity: 21, State: 4
2004-06-07 16:17:45.05 spid72 Error while undoing logged operation in dat
abase 'S094000'. Error at log record ID (63154:9493:281)..
2004-06-07 16:17:45.05 spid72 Error: 9001, Severity: 21, State: 1
2004-06-07 16:17:45.05 spid72 The log for database 'S094000' is not avail
able..
2004-06-07 16:17:45.36 spid72 Error: 3314, Severity: 21, State: 5
2004-06-07 16:17:45.36 spid72 Error while undoing logged operation in dat
abase 'S094000'. Error at log record ID (63154:9189:1)..
2004-06-07 16:17:46.34 spid15 Starting up database 'S094000'.
2004-06-07 16:17:47.56 spid15 Analysis of database 'S094000' (27) is 16%
complete (approximately 2 more seconds)
2004-06-07 16:17:49.28 spid15 Analysis of database 'S094000' (27) is 100%
complete (approximately 0 more seconds)
2004-06-07 16:17:49.30 spid15 Recovery of database 'S094000' (27) is 0% c
omplete (approximately 28 more seconds) (Phase 2 of 3).
2004-06-07 16:18:09.83 spid15 Recovery of database 'S094000' (27) is 17%
complete (approximately 98 more seconds) (Phase 2 of 3).
2004-06-07 16:18:13.50 spid15 Recovery of database 'S094000' (27) is 21%
complete (approximately 88 more seconds) (Phase 2 of 3).
2004-06-07 16:18:18.67 spid15 Recovery of database 'S094000' (27) is 25%
complete (approximately 83 more seconds) (Phase 2 of 3).
2004-06-07 16:18:23.36 spid15 Recovery of database 'S094000' (27) is 30%
complete (approximately 77 more seconds) (Phase 2 of 3).
2004-06-07 16:18:28.38 spid15 Recovery of database 'S094000' (27) is 34%
complete (approximately 72 more seconds) (Phase 2 of 3).
2004-06-07 16:18:34.88 spid15 Recovery of database 'S094000' (27) is 39%
complete (approximately 69 more seconds) (Phase 2 of 3).
2004-06-07 16:18:39.81 spid15 Recovery of database 'S094000' (27) is 43%
complete (approximately 64 more seconds) (Phase 2 of 3).
2004-06-07 16:18:44.13 spid15 Recovery of database 'S094000' (27) is 48%
complete (approximately 58 more seconds) (Phase 2 of 3).
2004-06-07 16:18:48.85 spid15 Recovery of database 'S094000' (27) is 52%
complete (approximately 53 more seconds) (Phase 2 of 3).
2004-06-07 16:18:54.44 spid15 Recovery of database 'S094000' (27) is 56%
complete (approximately 48 more seconds) (Phase 2 of 3).
2004-06-07 16:19:00.66 spid15 Recovery of database 'S094000' (27) is 61%
complete (approximately 44 more seconds) (Phase 2 of 3).
2004-06-07 16:19:06.38 spid15 Recovery of database 'S094000' (27) is 65%
complete (approximately 39 more seconds) (Phase 2 of 3).
2004-06-07 16:19:12.85 spid15 Recovery of database 'S094000' (27) is 70%
complete (approximately 35 more seconds) (Phase 2 of 3).
2004-06-07 16:19:19.55 spid15 Recovery of database 'S094000' (27) is 74%
complete (approximately 30 more seconds) (Phase 2 of 3).
2004-06-07 16:19:27.02 spid15 Recovery of database 'S094000' (27) is 78%
complete (approximately 26 more seconds) (Phase 2 of 3).
2004-06-07 16:19:34.21 spid15 Recovery of database 'S094000' (27) is 82%
complete (approximately 21 more seconds) (Phase 2 of 3).
2004-06-07 16:19:43.72 spid15 Recovery of database 'S094000' (27) is 86%
complete (approximately 17 more seconds) (Phase 2 of 3).
2004-06-07 16:19:52.25 spid15 Recovery of database 'S094000' (27) is 90%
complete (approximately 12 more seconds) (Phase 2 of 3).
2004-06-07 16:20:02.85 spid15 Recovery of database 'S094000' (27) is 93%
complete (approximately 7 more seconds) (Phase 2 of 3).
2004-06-07 16:20:14.79 spid15 Recovery of database 'S094000' (27) is 97%
complete (approximately 3 more seconds) (Phase 2 of 3).
2004-06-07 16:20:23.47 spid15 Recovery of database 'S094000' (27) is 99%
complete (approximately 0 more seconds) (Phase 2 of 3).
2004-06-07 16:20:23.47 spid15 266 transactions rolled forward in database
'S094000' (27).
2004-06-07 16:20:23.72 spid15 Recovery of database 'S094000' (27) is 99%
complete (approximately 0 more seconds) (Phase 3 of 3).
2004-06-07 16:20:25.04 spid15 Recovery of database 'S094000' (27) is 100%
complete (approximately 0 more seconds) (Phase 3 of 3).
2004-06-07 16:20:25.04 spid15 1 transactions rolled back in database 'S09
4000' (27).
2004-06-07 16:20:25.05 spid15 Recovery is checkpointing database 'S094000
' (27)
2004-06-07 16:21:19.65 spid61 Getpage: bstat=0x9, sstat=0x10000, cache
2004-06-07 16:21:19.65 spid61 pageno is/should be: objid is/should be:
2004-06-07 16:21:19.65 spid61 (1:772511)/(1:772511) 457768688/12695795
61
2004-06-07 16:21:19.65 spid61 ... IAM indicates that page is allocated to
this object
2004-06-07 16:21:19.65 spid61 Error: 605, Severity: 21, State: 1
2004-06-07 16:21:19.65 spid61 Attempt to fetch logical page (1:772511) in
database 'S094000' belongs to object 't050_pre_arch', not to object 't050_c
ampaign_candidate'..
2004-06-07 16:21:19.71 spid61 Error: 644, Severity: 21, State: 5
2004-06-07 16:21:19.71 spid61 Could not find the index entry for RID '169
05830100' in index page (1:772510), index ID 9, database 'S094000'..
2004-06-07 16:21:19.71 spid61 Error: 3314, Severity: 21, State: 4
2004-06-07 16:21:19.71 spid61 Error while undoing logged operation in dat
abase 'S094000'. Error at log record ID (63154:10761:6)..
2004-06-07 16:21:19.71 spid61 Using 'dbghelp.dll' version '4.0.5'
*Dump thread - spid = 61, PSS = 0x43897200, EC = 0x43897528Hi -
1. Important :: {Do you have previously clean backup? If yes, please re
store
from the backup.}
OR
1. Execute DBCC CHECKDB to determine the extent of the damage, use the
REPAIR_REBUILD clause. If problem persists drop and re-create the index
Also Please provide output from DBCC CHECKDB.
2. Examine the error log for any errors prior to error 3414. It is important
to examine errors that occurred before the first occurrence of error 3414
because subsequent attempts to start the server might not give the detailed
error information you need to diagnose the problem. If you do not have
sufficient information to recover from the previous errors, you can recover
from known clean backups
I guess the problem is with the corrupt index Allocation Map or some thing
whirred in the sysobjects table.
Thanks
-Surajit
"G0" <anonymous@.discussions.microsoft.com> wrote in message
news:6AB317BC-5A70-43FC-BB47-33D5ED697253@.microsoft.com...
> Hi Gurus,
> One of my DBs on a SQL box (SQL 2000 enterprise edtion SP3 on Win2k
Advanced server) went suspect yesterday. Here is part of the error log.
Would appreciate any help/suggestions.
>
> 2004-06-07 16:17:42.74 spid72 Getpage: bstat=0x9, sstat=0x10000, cache
> 2004-06-07 16:17:42.74 spid72 pageno is/should be: objid is/should
be:
> 2004-06-07 16:17:42.74 spid72 (1:772511)/(1:772511)
457768688/1269579561
> 2004-06-07 16:17:42.74 spid72 ... IAM indicates that page is allocated
to this object
> 2004-06-07 16:17:42.74 spid72 Error: 605, Severity: 21, State: 1
> 2004-06-07 16:17:42.74 spid72 Attempt to fetch logical page (1:772511)
in database 'S094000' belongs to object 't050_pre_arch', not to object
't050_campaign_candidate'..
> 2004-06-07 16:17:42.75 spid72 Error: 644, Severity: 21, State: 5
> 2004-06-07 16:17:42.75 spid72 Could not find the index entry for RID
'16905830100' in index page (1:772510), index ID 9, database 'S094000'..
> 2004-06-07 16:17:42.75 spid72 Error: 3314, Severity: 21, State: 4
> 2004-06-07 16:17:42.75 spid72 Error while undoing logged operation in
database 'S094000'. Error at log record ID (63154:9493:281)..
> 2004-06-07 16:17:42.80 spid72 Using 'dbghelp.dll' version '4.0.5'
> *Dump thread - spid = 72, PSS = 0x70f85200, EC = 0x70f85528
> (actual dump manually taken out here)
>
* ----
--
> 2004-06-07 16:17:44.77 spid72 Stack Signature for the dump is
0x03737F82
> 2004-06-07 16:17:44.77 spid72 SQL Server Assertion: File:
<scanrid.cpp>, line=321
> Failed Assertion = 'm_len != 0'.
> 2004-06-07 16:17:44.77 spid72 Error: 3624, Severity: 20, State: 1.
> 2004-06-07 16:17:45.05 spid72 Error: 3314, Severity: 21, State: 4
> 2004-06-07 16:17:45.05 spid72 Error while undoing logged operation in
database 'S094000'. Error at log record ID (63154:9493:281)..
> 2004-06-07 16:17:45.05 spid72 Error: 9001, Severity: 21, State: 1
> 2004-06-07 16:17:45.05 spid72 The log for database 'S094000' is not
available..
> 2004-06-07 16:17:45.36 spid72 Error: 3314, Severity: 21, State: 5
> 2004-06-07 16:17:45.36 spid72 Error while undoing logged operation in
database 'S094000'. Error at log record ID (63154:9189:1)..
> 2004-06-07 16:17:46.34 spid15 Starting up database 'S094000'.
> 2004-06-07 16:17:47.56 spid15 Analysis of database 'S094000' (27) is
16% complete (approximately 2 more seconds)
> 2004-06-07 16:17:49.28 spid15 Analysis of database 'S094000' (27) is
100% complete (approximately 0 more seconds)
> 2004-06-07 16:17:49.30 spid15 Recovery of database 'S094000' (27) is 0%
complete (approximately 28 more seconds) (Phase 2 of 3).
> 2004-06-07 16:18:09.83 spid15 Recovery of database 'S094000' (27) is
17% complete (approximately 98 more seconds) (Phase 2 of 3).
> 2004-06-07 16:18:13.50 spid15 Recovery of database 'S094000' (27) is
21% complete (approximately 88 more seconds) (Phase 2 of 3).
> 2004-06-07 16:18:18.67 spid15 Recovery of database 'S094000' (27) is
25% complete (approximately 83 more seconds) (Phase 2 of 3).
> 2004-06-07 16:18:23.36 spid15 Recovery of database 'S094000' (27) is
30% complete (approximately 77 more seconds) (Phase 2 of 3).
> 2004-06-07 16:18:28.38 spid15 Recovery of database 'S094000' (27) is
34% complete (approximately 72 more seconds) (Phase 2 of 3).
> 2004-06-07 16:18:34.88 spid15 Recovery of database 'S094000' (27) is
39% complete (approximately 69 more seconds) (Phase 2 of 3).
> 2004-06-07 16:18:39.81 spid15 Recovery of database 'S094000' (27) is
43% complete (approximately 64 more seconds) (Phase 2 of 3).
> 2004-06-07 16:18:44.13 spid15 Recovery of database 'S094000' (27) is
48% complete (approximately 58 more seconds) (Phase 2 of 3).
> 2004-06-07 16:18:48.85 spid15 Recovery of database 'S094000' (27) is
52% complete (approximately 53 more seconds) (Phase 2 of 3).
> 2004-06-07 16:18:54.44 spid15 Recovery of database 'S094000' (27) is
56% complete (approximately 48 more seconds) (Phase 2 of 3).
> 2004-06-07 16:19:00.66 spid15 Recovery of database 'S094000' (27) is
61% complete (approximately 44 more seconds) (Phase 2 of 3).
> 2004-06-07 16:19:06.38 spid15 Recovery of database 'S094000' (27) is
65% complete (approximately 39 more seconds) (Phase 2 of 3).
> 2004-06-07 16:19:12.85 spid15 Recovery of database 'S094000' (27) is
70% complete (approximately 35 more seconds) (Phase 2 of 3).
> 2004-06-07 16:19:19.55 spid15 Recovery of database 'S094000' (27) is
74% complete (approximately 30 more seconds) (Phase 2 of 3).
> 2004-06-07 16:19:27.02 spid15 Recovery of database 'S094000' (27) is
78% complete (approximately 26 more seconds) (Phase 2 of 3).
> 2004-06-07 16:19:34.21 spid15 Recovery of database 'S094000' (27) is
82% complete (approximately 21 more seconds) (Phase 2 of 3).
> 2004-06-07 16:19:43.72 spid15 Recovery of database 'S094000' (27) is
86% complete (approximately 17 more seconds) (Phase 2 of 3).
> 2004-06-07 16:19:52.25 spid15 Recovery of database 'S094000' (27) is
90% complete (approximately 12 more seconds) (Phase 2 of 3).
> 2004-06-07 16:20:02.85 spid15 Recovery of database 'S094000' (27) is
93% complete (approximately 7 more seconds) (Phase 2 of 3).
> 2004-06-07 16:20:14.79 spid15 Recovery of database 'S094000' (27) is
97% complete (approximately 3 more seconds) (Phase 2 of 3).
> 2004-06-07 16:20:23.47 spid15 Recovery of database 'S094000' (27) is
99% complete (approximately 0 more seconds) (Phase 2 of 3).
> 2004-06-07 16:20:23.47 spid15 266 transactions rolled forward in
database 'S094000' (27).
> 2004-06-07 16:20:23.72 spid15 Recovery of database 'S094000' (27) is
99% complete (approximately 0 more seconds) (Phase 3 of 3).
> 2004-06-07 16:20:25.04 spid15 Recovery of database 'S094000' (27) is
100% complete (approximately 0 more seconds) (Phase 3 of 3).
> 2004-06-07 16:20:25.04 spid15 1 transactions rolled back in database
'S094000' (27).
> 2004-06-07 16:20:25.05 spid15 Recovery is checkpointing database
'S094000' (27)
> 2004-06-07 16:21:19.65 spid61 Getpage: bstat=0x9, sstat=0x10000, cache
> 2004-06-07 16:21:19.65 spid61 pageno is/should be: objid is/should
be:
> 2004-06-07 16:21:19.65 spid61 (1:772511)/(1:772511)
457768688/1269579561
> 2004-06-07 16:21:19.65 spid61 ... IAM indicates that page is allocated
to this object
> 2004-06-07 16:21:19.65 spid61 Error: 605, Severity: 21, State: 1
> 2004-06-07 16:21:19.65 spid61 Attempt to fetch logical page (1:772511)
in database 'S094000' belongs to object 't050_pre_arch', not to object
't050_campaign_candidate'..
> 2004-06-07 16:21:19.71 spid61 Error: 644, Severity: 21, State: 5
> 2004-06-07 16:21:19.71 spid61 Could not find the index entry for RID
'16905830100' in index page (1:772510), index ID 9, database 'S094000'..
> 2004-06-07 16:21:19.71 spid61 Error: 3314, Severity: 21, State: 4
> 2004-06-07 16:21:19.71 spid61 Error while undoing logged operation in
database 'S094000'. Error at log record ID (63154:10761:6)..
> 2004-06-07 16:21:19.71 spid61 Using 'dbghelp.dll' version '4.0.5'
> *Dump thread - spid = 61, PSS = 0x43897200, EC = 0x43897528
>
>|||In addition to Surajit's post:
http://www.karaszi.com/SQLServer/in..._suspect_db.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"G0" <anonymous@.discussions.microsoft.com> wrote in message
news:6AB317BC-5A70-43FC-BB47-33D5ED697253@.microsoft.com...
> Hi Gurus,
> One of my DBs on a SQL box (SQL 2000 enterprise edtion SP3 on Win2k Advanced serve
r) went suspect yesterday.
Here is part of the error log. Would appreciate any help/suggestions.
>
> 2004-06-07 16:17:42.74 spid72 Getpage: bstat=0x9, sstat=0x10000, cache
> 2004-06-07 16:17:42.74 spid72 pageno is/should be: objid is/should be
:
> 2004-06-07 16:17:42.74 spid72 (1:772511)/(1:772511) 457768688/1269579
561
> 2004-06-07 16:17:42.74 spid72 ... IAM indicates that page is allocated
to this object
> 2004-06-07 16:17:42.74 spid72 Error: 605, Severity: 21, State: 1
> 2004-06-07 16:17:42.74 spid72 Attempt to fetch logical page (1:772511) in datab
ase 'S094000' belongs to
object 't050_pre_arch', not to object 't050_campaign_candidate'..
> 2004-06-07 16:17:42.75 spid72 Error: 644, Severity: 21, State: 5
> 2004-06-07 16:17:42.75 spid72 Could not find the index entry for RID '169058301
00' in index page
(1:772510), index ID 9, database 'S094000'..
> 2004-06-07 16:17:42.75 spid72 Error: 3314, Severity: 21, State: 4
> 2004-06-07 16:17:42.75 spid72 Error while undoing logged operation in database
'S094000'. Error at log
record ID (63154:9493:281)..
> 2004-06-07 16:17:42.80 spid72 Using 'dbghelp.dll' version '4.0.5'
> *Dump thread - spid = 72, PSS = 0x70f85200, EC = 0x70f85528
> (actual dump manually taken out here)
> * ---
--
> 2004-06-07 16:17:44.77 spid72 Stack Signature for the dump is 0x03737F8
2
> 2004-06-07 16:17:44.77 spid72 SQL Server Assertion: File: <scanrid.cpp>
, line=321
> Failed Assertion = 'm_len != 0'.
> 2004-06-07 16:17:44.77 spid72 Error: 3624, Severity: 20, State: 1.
> 2004-06-07 16:17:45.05 spid72 Error: 3314, Severity: 21, State: 4
> 2004-06-07 16:17:45.05 spid72 Error while undoing logged operation in database
'S094000'. Error at log
record ID (63154:9493:281)..
> 2004-06-07 16:17:45.05 spid72 Error: 9001, Severity: 21, State: 1
> 2004-06-07 16:17:45.05 spid72 The log for database 'S094000' is not ava
ilable..
> 2004-06-07 16:17:45.36 spid72 Error: 3314, Severity: 21, State: 5
> 2004-06-07 16:17:45.36 spid72 Error while undoing logged operation in database
'S094000'. Error at log
record ID (63154:9189:1)..
> 2004-06-07 16:17:46.34 spid15 Starting up database 'S094000'.
> 2004-06-07 16:17:47.56 spid15 Analysis of database 'S094000' (27) is 16% comple
te (approximately 2 more
seconds)
> 2004-06-07 16:17:49.28 spid15 Analysis of database 'S094000' (27) is 100% compl
ete (approximately 0 more
seconds)
> 2004-06-07 16:17:49.30 spid15 Recovery of database 'S094000' (27) is 0% complet
e (approximately 28 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:18:09.83 spid15 Recovery of database 'S094000' (27) is 17% comple
te (approximately 98 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:18:13.50 spid15 Recovery of database 'S094000' (27) is 21% comple
te (approximately 88 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:18:18.67 spid15 Recovery of database 'S094000' (27) is 25% comple
te (approximately 83 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:18:23.36 spid15 Recovery of database 'S094000' (27) is 30% comple
te (approximately 77 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:18:28.38 spid15 Recovery of database 'S094000' (27) is 34% comple
te (approximately 72 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:18:34.88 spid15 Recovery of database 'S094000' (27) is 39% comple
te (approximately 69 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:18:39.81 spid15 Recovery of database 'S094000' (27) is 43% comple
te (approximately 64 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:18:44.13 spid15 Recovery of database 'S094000' (27) is 48% comple
te (approximately 58 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:18:48.85 spid15 Recovery of database 'S094000' (27) is 52% comple
te (approximately 53 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:18:54.44 spid15 Recovery of database 'S094000' (27) is 56% comple
te (approximately 48 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:19:00.66 spid15 Recovery of database 'S094000' (27) is 61% comple
te (approximately 44 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:19:06.38 spid15 Recovery of database 'S094000' (27) is 65% comple
te (approximately 39 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:19:12.85 spid15 Recovery of database 'S094000' (27) is 70% comple
te (approximately 35 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:19:19.55 spid15 Recovery of database 'S094000' (27) is 74% comple
te (approximately 30 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:19:27.02 spid15 Recovery of database 'S094000' (27) is 78% comple
te (approximately 26 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:19:34.21 spid15 Recovery of database 'S094000' (27) is 82% comple
te (approximately 21 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:19:43.72 spid15 Recovery of database 'S094000' (27) is 86% comple
te (approximately 17 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:19:52.25 spid15 Recovery of database 'S094000' (27) is 90% comple
te (approximately 12 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:20:02.85 spid15 Recovery of database 'S094000' (27) is 93% comple
te (approximately 7 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:20:14.79 spid15 Recovery of database 'S094000' (27) is 97% comple
te (approximately 3 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:20:23.47 spid15 Recovery of database 'S094000' (27) is 99% comple
te (approximately 0 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:20:23.47 spid15 266 transactions rolled forward in databa
se 'S094000' (27).
> 2004-06-07 16:20:23.72 spid15 Recovery of database 'S094000' (27) is 99% comple
te (approximately 0 more
seconds) (Phase 3 of 3).
> 2004-06-07 16:20:25.04 spid15 Recovery of database 'S094000' (27) is 100% compl
ete (approximately 0 more
seconds) (Phase 3 of 3).
> 2004-06-07 16:20:25.04 spid15 1 transactions rolled back in database 'S
094000' (27).
> 2004-06-07 16:20:25.05 spid15 Recovery is checkpointing database 'S0940
00' (27)
> 2004-06-07 16:21:19.65 spid61 Getpage: bstat=0x9, sstat=0x10000, cache
> 2004-06-07 16:21:19.65 spid61 pageno is/should be: objid is/should be
:
> 2004-06-07 16:21:19.65 spid61 (1:772511)/(1:772511) 457768688/1269579
561
> 2004-06-07 16:21:19.65 spid61 ... IAM indicates that page is allocated
to this object
> 2004-06-07 16:21:19.65 spid61 Error: 605, Severity: 21, State: 1
> 2004-06-07 16:21:19.65 spid61 Attempt to fetch logical page (1:772511) in datab
ase 'S094000' belongs to
object 't050_pre_arch', not to object 't050_campaign_candidate'..
> 2004-06-07 16:21:19.71 spid61 Error: 644, Severity: 21, State: 5
> 2004-06-07 16:21:19.71 spid61 Could not find the index entry for RID '169058301
00' in index page
(1:772510), index ID 9, database 'S094000'..
> 2004-06-07 16:21:19.71 spid61 Error: 3314, Severity: 21, State: 4
> 2004-06-07 16:21:19.71 spid61 Error while undoing logged operation in database
'S094000'. Error at log
record ID (63154:10761:6)..
> 2004-06-07 16:21:19.71 spid61 Using 'dbghelp.dll' version '4.0.5'
> *Dump thread - spid = 61, PSS = 0x43897200, EC = 0x43897528
>
>sql

DB Maintenance Plan failure

Good morning all...
SQL Server 2000, SP3 running on a W2K Server Cluster.
All other DB Maint Plans run fine (12 DBs). But on one,
we get the following error:
"[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'
I've searched and read everything I can find, but nothing
seems to be "our" problem. Suggestions ranged from
priviledge accounts to "are you running SP3".
Anyone seen this and/or have suggestions?
Thanks,
TonyGood afternoon Tony,
This error can occur if you have indexed views in your database, and you
have the "Reorganize indexes and data pages"check box checked in your
maintenance plan. Indexed views require a number of options to be set in a
certain way when they are build or reindexed, and you have to make sure that
the login under which the maintenance plan is running has them set
correctly. The two options most likely to be set wrongly are
QUOTED_IDENTIFIER and ARITH_ABORT, which should both be ON.
--
Jacco Schalkwijk
SQL Server MVP
"Tony Bowman" <anonymous@.discussions.microsoft.com> wrote in message
news:e72901c3f0b9$664ca1a0$a001280a@.phx.gbl...
> Good morning all...
> SQL Server 2000, SP3 running on a W2K Server Cluster.
> All other DB Maint Plans run fine (12 DBs). But on one,
> we get the following error:
> "[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'
> I've searched and read everything I can find, but nothing
> seems to be "our" problem. Suggestions ranged from
> priviledge accounts to "are you running SP3".
> Anyone seen this and/or have suggestions?
> Thanks,
> Tony|||Unless they fixed something I don't think this is something you can adjust.
I believe the only way around it is to create your own scheduled job that
does the reorgs and don't use the MP.
--
Andrew J. Kelly
SQL Server MVP
"Jacco Schalkwijk" <NOSPAMjaccos@.eurostop.co.uk> wrote in message
news:u0QDhwL8DHA.2796@.TK2MSFTNGP09.phx.gbl...
> Good afternoon Tony,
> This error can occur if you have indexed views in your database, and you
> have the "Reorganize indexes and data pages"check box checked in your
> maintenance plan. Indexed views require a number of options to be set in a
> certain way when they are build or reindexed, and you have to make sure
that
> the login under which the maintenance plan is running has them set
> correctly. The two options most likely to be set wrongly are
> QUOTED_IDENTIFIER and ARITH_ABORT, which should both be ON.
> --
> Jacco Schalkwijk
> SQL Server MVP
>
> "Tony Bowman" <anonymous@.discussions.microsoft.com> wrote in message
> news:e72901c3f0b9$664ca1a0$a001280a@.phx.gbl...
> > Good morning all...
> > SQL Server 2000, SP3 running on a W2K Server Cluster.
> > All other DB Maint Plans run fine (12 DBs). But on one,
> > we get the following error:
> > "[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'
> >
> > I've searched and read everything I can find, but nothing
> > seems to be "our" problem. Suggestions ranged from
> > priviledge accounts to "are you running SP3".
> >
> > Anyone seen this and/or have suggestions?
> >
> > Thanks,
> > Tony
>

DB Maintenance Plan failure

Good morning all...
SQL Server 2000, SP3 running on a W2K Server Cluster.
All other DB Maint Plans run fine (12 DBs). But on one,
we get the following error:
"[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'
I've searched and read everything I can find, but nothing
seems to be "our" problem. Suggestions ranged from
priviledge accounts to "are you running SP3".
Anyone seen this and/or have suggestions?
Thanks,
TonyGood afternoon Tony,
This error can occur if you have indexed views in your database, and you
have the "Reorganize indexes and data pages"check box checked in your
maintenance plan. Indexed views require a number of options to be set in a
certain way when they are build or reindexed, and you have to make sure that
the login under which the maintenance plan is running has them set
correctly. The two options most likely to be set wrongly are
QUOTED_IDENTIFIER and ARITH_ABORT, which should both be ON.
Jacco Schalkwijk
SQL Server MVP
"Tony Bowman" <anonymous@.discussions.microsoft.com> wrote in message
news:e72901c3f0b9$664ca1a0$a001280a@.phx.gbl...
> Good morning all...
> SQL Server 2000, SP3 running on a W2K Server Cluster.
> All other DB Maint Plans run fine (12 DBs). But on one,
> we get the following error:
> "[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'
> I've searched and read everything I can find, but nothing
> seems to be "our" problem. Suggestions ranged from
> priviledge accounts to "are you running SP3".
> Anyone seen this and/or have suggestions?
> Thanks,
> Tony|||Unless they fixed something I don't think this is something you can adjust.
I believe the only way around it is to create your own scheduled job that
does the reorgs and don't use the MP.
Andrew J. Kelly
SQL Server MVP
"Jacco Schalkwijk" <NOSPAMjaccos@.eurostop.co.uk> wrote in message
news:u0QDhwL8DHA.2796@.TK2MSFTNGP09.phx.gbl...
> Good afternoon Tony,
> This error can occur if you have indexed views in your database, and you
> have the "Reorganize indexes and data pages"check box checked in your
> maintenance plan. Indexed views require a number of options to be set in a
> certain way when they are build or reindexed, and you have to make sure
that
> the login under which the maintenance plan is running has them set
> correctly. The two options most likely to be set wrongly are
> QUOTED_IDENTIFIER and ARITH_ABORT, which should both be ON.
> --
> Jacco Schalkwijk
> SQL Server MVP
>
> "Tony Bowman" <anonymous@.discussions.microsoft.com> wrote in message
> news:e72901c3f0b9$664ca1a0$a001280a@.phx.gbl...
>

DB Maintenance & Single-User Mode

SQL Server 2000 SP3 running on Windows Server 2003. The machine is a
quad-Xeon 2.2 GHz with 4 GB of RAM.
The SQL Server instance has 4 non-system databases, including the SharePoint
Services content database. We've been running, at 2:00 AM, weekly complete
backups and nightly transaction log backups--with integrity checks and
optimizations.
Every morning, we find that only the SharePoint database has been set to
"Single User" restricted access. Every time, the log shows:
"DBCC CHECKDB (STS_1182080930, repair_fast) executed by NT AUTHORITY\SYSTEM
found 0 errors and repaired 0 errors."
The links below point to related information. This appears to have been a
bug in SQL Server 7. Is it still a bug in SQL Server 2000 SP3?
Thanks,
Jim
"FIX: SQLMaint.exe Sets Database Status Incorrectly"
http://support.microsoft.com/default...b;EN-US;276234
"a problem about repair damaged database and single user mode"
http://groups.google.com/groups?q=sq...t.c om&rnum=5
Yes but it's not necessarily a good idea to use that option
and you'd probably want to clear the Attempt to repair any
minor problems check box in the maintenance plan.
If you get DBCC errors, you'd want to manually intervene and
do some type of root cause analysis. Then proceed with
whatever action from there.
-Sue
On Mon, 30 Aug 2004 16:29:38 -0500, "Jim Moon"
<jmoon()at()uab.edu> wrote:

>SQL Server 2000 SP3 running on Windows Server 2003. The machine is a
>quad-Xeon 2.2 GHz with 4 GB of RAM.
>The SQL Server instance has 4 non-system databases, including the SharePoint
>Services content database. We've been running, at 2:00 AM, weekly complete
>backups and nightly transaction log backups--with integrity checks and
>optimizations.
>Every morning, we find that only the SharePoint database has been set to
>"Single User" restricted access. Every time, the log shows:
>"DBCC CHECKDB (STS_1182080930, repair_fast) executed by NT AUTHORITY\SYSTEM
>found 0 errors and repaired 0 errors."
>The links below point to related information. This appears to have been a
>bug in SQL Server 7. Is it still a bug in SQL Server 2000 SP3?
>Thanks,
>Jim
>"FIX: SQLMaint.exe Sets Database Status Incorrectly"
>http://support.microsoft.com/default...b;EN-US;276234
>
>"a problem about repair damaged database and single user mode"
>http://groups.google.com/groups?q=sq...t.c om&rnum=5
>
|||Thank you, Sue.
Jim
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:8gq7j0pemr387cd2csrsainr9v11a0npf6@.4ax.com...
> Yes but it's not necessarily a good idea to use that option
> and you'd probably want to clear the Attempt to repair any
> minor problems check box in the maintenance plan.
> If you get DBCC errors, you'd want to manually intervene and
> do some type of root cause analysis. Then proceed with
> whatever action from there.
> -Sue
> On Mon, 30 Aug 2004 16:29:38 -0500, "Jim Moon"
> <jmoon()at()uab.edu> wrote:
>

DB Maintenance & Single-User Mode

SQL Server 2000 SP3 running on Windows Server 2003. The machine is a
quad-Xeon 2.2 GHz with 4 GB of RAM.
The SQL Server instance has 4 non-system databases, including the SharePoint
Services content database. We've been running, at 2:00 AM, weekly complete
backups and nightly transaction log backups--with integrity checks and
optimizations.
Every morning, we find that only the SharePoint database has been set to
"Single User" restricted access. Every time, the log shows:
"DBCC CHECKDB (STS_1182080930, repair_fast) executed by NT AUTHORITY\SYSTEM
found 0 errors and repaired 0 errors."
The links below point to related information. This appears to have been a
bug in SQL Server 7. Is it still a bug in SQL Server 2000 SP3?
Thanks,
Jim
"FIX: SQLMaint.exe Sets Database Status Incorrectly"
http://support.microsoft.com/default.aspx?scid=kb;EN-US;276234
"a problem about repair damaged database and single user mode"
http://groups.google.com/groups?q=sql+server+dbcc+checkdb+single+user+mode&hl=en&lr=&ie=UTF-8&selm=etEeJupv%24GA.176%40cppssbbsa01.microsoft.com&rnum=5Yes but it's not necessarily a good idea to use that option
and you'd probably want to clear the Attempt to repair any
minor problems check box in the maintenance plan.
If you get DBCC errors, you'd want to manually intervene and
do some type of root cause analysis. Then proceed with
whatever action from there.
-Sue
On Mon, 30 Aug 2004 16:29:38 -0500, "Jim Moon"
<jmoon()at()uab.edu> wrote:
>SQL Server 2000 SP3 running on Windows Server 2003. The machine is a
>quad-Xeon 2.2 GHz with 4 GB of RAM.
>The SQL Server instance has 4 non-system databases, including the SharePoint
>Services content database. We've been running, at 2:00 AM, weekly complete
>backups and nightly transaction log backups--with integrity checks and
>optimizations.
>Every morning, we find that only the SharePoint database has been set to
>"Single User" restricted access. Every time, the log shows:
>"DBCC CHECKDB (STS_1182080930, repair_fast) executed by NT AUTHORITY\SYSTEM
>found 0 errors and repaired 0 errors."
>The links below point to related information. This appears to have been a
>bug in SQL Server 7. Is it still a bug in SQL Server 2000 SP3?
>Thanks,
>Jim
>"FIX: SQLMaint.exe Sets Database Status Incorrectly"
>http://support.microsoft.com/default.aspx?scid=kb;EN-US;276234
>
>"a problem about repair damaged database and single user mode"
>http://groups.google.com/groups?q=sql+server+dbcc+checkdb+single+user+mode&hl=en&lr=&ie=UTF-8&selm=etEeJupv%24GA.176%40cppssbbsa01.microsoft.com&rnum=5
>|||Thank you, Sue.
Jim
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:8gq7j0pemr387cd2csrsainr9v11a0npf6@.4ax.com...
> Yes but it's not necessarily a good idea to use that option
> and you'd probably want to clear the Attempt to repair any
> minor problems check box in the maintenance plan.
> If you get DBCC errors, you'd want to manually intervene and
> do some type of root cause analysis. Then proceed with
> whatever action from there.
> -Sue
> On Mon, 30 Aug 2004 16:29:38 -0500, "Jim Moon"
> <jmoon()at()uab.edu> wrote:
>>SQL Server 2000 SP3 running on Windows Server 2003. The machine is a
>>quad-Xeon 2.2 GHz with 4 GB of RAM.
>>The SQL Server instance has 4 non-system databases, including the
>>SharePoint
>>Services content database. We've been running, at 2:00 AM, weekly
>>complete
>>backups and nightly transaction log backups--with integrity checks and
>>optimizations.
>>Every morning, we find that only the SharePoint database has been set to
>>"Single User" restricted access. Every time, the log shows:
>>"DBCC CHECKDB (STS_1182080930, repair_fast) executed by NT
>>AUTHORITY\SYSTEM
>>found 0 errors and repaired 0 errors."
>>The links below point to related information. This appears to have been a
>>bug in SQL Server 7. Is it still a bug in SQL Server 2000 SP3?
>>Thanks,
>>Jim
>>"FIX: SQLMaint.exe Sets Database Status Incorrectly"
>>http://support.microsoft.com/default.aspx?scid=kb;EN-US;276234
>>
>>"a problem about repair damaged database and single user mode"
>>http://groups.google.com/groups?q=sql+server+dbcc+checkdb+single+user+mode&hl=en&lr=&ie=UTF-8&selm=etEeJupv%24GA.176%40cppssbbsa01.microsoft.com&rnum=5
>

DB Maintenance & Single-User Mode

SQL Server 2000 SP3 running on Windows Server 2003. The machine is a
quad-Xeon 2.2 GHz with 4 GB of RAM.
The SQL Server instance has 4 non-system databases, including the SharePoint
Services content database. We've been running, at 2:00 AM, weekly complete
backups and nightly transaction log backups--with integrity checks and
optimizations.
Every morning, we find that only the SharePoint database has been set to
"Single User" restricted access. Every time, the log shows:
"DBCC CHECKDB (STS_1182080930, repair_fast) executed by NT AUTHORITY\SYSTEM
found 0 errors and repaired 0 errors."
The links below point to related information. This appears to have been a
bug in SQL Server 7. Is it still a bug in SQL Server 2000 SP3?
Thanks,
Jim
"FIX: SQLMaint.exe Sets Database Status Incorrectly"
http://support.microsoft.com/defaul...kb;EN-US;276234
"a problem about repair damaged database and single user mode"
de&hl=en&l
r=&ie=UTF-8&selm=etEeJupv%24GA.176%40cppssbbsa01.microsoft.com&rnum=5" target="_blank">http://groups.google.com/groups? q=...soft.com&rnum=5Yes but it's not necessarily a good idea to use that option
and you'd probably want to clear the Attempt to repair any
minor problems check box in the maintenance plan.
If you get DBCC errors, you'd want to manually intervene and
do some type of root cause analysis. Then proceed with
whatever action from there.
-Sue
On Mon, 30 Aug 2004 16:29:38 -0500, "Jim Moon"
<jmoon()at()uab.edu> wrote:

>SQL Server 2000 SP3 running on Windows Server 2003. The machine is a
>quad-Xeon 2.2 GHz with 4 GB of RAM.
>The SQL Server instance has 4 non-system databases, including the SharePoin
t
>Services content database. We've been running, at 2:00 AM, weekly complet
e
>backups and nightly transaction log backups--with integrity checks and
>optimizations.
>Every morning, we find that only the SharePoint database has been set to
>"Single User" restricted access. Every time, the log shows:
>"DBCC CHECKDB (STS_1182080930, repair_fast) executed by NT AUTHORITY\SYSTEM
>found 0 errors and repaired 0 errors."
>The links below point to related information. This appears to have been a
>bug in SQL Server 7. Is it still a bug in SQL Server 2000 SP3?
>Thanks,
>Jim
>"FIX: SQLMaint.exe Sets Database Status Incorrectly"
>http://support.microsoft.com/defaul...kb;EN-US;276234
>
>"a problem about repair damaged database and single user mode"
>de&hl=en&
lr=&ie=UTF-8&selm=etEeJupv%24GA.176%40cppssbbsa01.microsoft.com&rnum=5" target="_blank">http://groups.google.com/groups? q=...soft.com&rnum=5
>|||Thank you, Sue.
Jim
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:8gq7j0pemr387cd2csrsainr9v11a0npf6@.
4ax.com...
> Yes but it's not necessarily a good idea to use that option
> and you'd probably want to clear the Attempt to repair any
> minor problems check box in the maintenance plan.
> If you get DBCC errors, you'd want to manually intervene and
> do some type of root cause analysis. Then proceed with
> whatever action from there.
> -Sue
> On Mon, 30 Aug 2004 16:29:38 -0500, "Jim Moon"
> <jmoon()at()uab.edu> wrote:
>
>

db maint plan fail

Hi ,
i am trying to set up a database maintainenance plan on SQL server 2000 with
SP3 on Windows 2000 server but i encountered the following error :
Executed as user : NT AUTHORITY\SYSTEM. sqlmaint.exe failed (SQLState 42000)
Error : 22029. The step failed
could anyone advise ?
tks & rdgsHi,
Could you tell us what sort of job you are performing using Maintenance
Plan. If it is Transaction log backup ensure that your database recovery
models selected for backup must be either FULL or BULK_LOGGED. If it is
SIMPLE then log backup will fail.
Thanks
Hari
SQL Server MVP
"maxzsim" <maxzsim@.discussions.microsoft.com> wrote in message
news:1764E240-8F7F-4A96-B316-095633386279@.microsoft.com...
> Hi ,
> i am trying to set up a database maintainenance plan on SQL server 2000
> with
> SP3 on Windows 2000 server but i encountered the following error :
> Executed as user : NT AUTHORITY\SYSTEM. sqlmaint.exe failed (SQLState
> 42000)
> Error : 22029. The step failed
> could anyone advise ?
> tks & rdgs|||Hi ,
i am backing up only the master , msdb & model dbs and i have changed the
mode to full backup however , i still got the same error
rdgs
"Hari Prasad" wrote:
> Hi,
> Could you tell us what sort of job you are performing using Maintenance
> Plan. If it is Transaction log backup ensure that your database recovery
> models selected for backup must be either FULL or BULK_LOGGED. If it is
> SIMPLE then log backup will fail.
> Thanks
> Hari
> SQL Server MVP
> "maxzsim" <maxzsim@.discussions.microsoft.com> wrote in message
> news:1764E240-8F7F-4A96-B316-095633386279@.microsoft.com...
> > Hi ,
> >
> > i am trying to set up a database maintainenance plan on SQL server 2000
> > with
> > SP3 on Windows 2000 server but i encountered the following error :
> > Executed as user : NT AUTHORITY\SYSTEM. sqlmaint.exe failed (SQLState
> > 42000)
> > Error : 22029. The step failed
> >
> > could anyone advise ?
> > tks & rdgs
>
>|||Hi
If you right click on the plan in Enterprise Manager and call up the
Maintenance Plan History do you get a more detailed error message?
Also are you just performing backups or are you also defining integrity
checks. If so do not attempt to repair minor problems on the system DBs as
the process cannot get exclusive access to master or msdb (too many other
processes).
Yours
Alasdair Russell
"maxzsim" wrote:
> Hi ,
> i am backing up only the master , msdb & model dbs and i have changed the
> mode to full backup however , i still got the same error
> rdgs
>
> "Hari Prasad" wrote:
> > Hi,
> >
> > Could you tell us what sort of job you are performing using Maintenance
> > Plan. If it is Transaction log backup ensure that your database recovery
> > models selected for backup must be either FULL or BULK_LOGGED. If it is
> > SIMPLE then log backup will fail.
> >
> > Thanks
> > Hari
> > SQL Server MVP
> >
> > "maxzsim" <maxzsim@.discussions.microsoft.com> wrote in message
> > news:1764E240-8F7F-4A96-B316-095633386279@.microsoft.com...
> > > Hi ,
> > >
> > > i am trying to set up a database maintainenance plan on SQL server 2000
> > > with
> > > SP3 on Windows 2000 server but i encountered the following error :
> > > Executed as user : NT AUTHORITY\SYSTEM. sqlmaint.exe failed (SQLState
> > > 42000)
> > > Error : 22029. The step failed
> > >
> > > could anyone advise ?
> > > tks & rdgs
> >
> >
> >