MSSQLSERVER error(s) - severity and state

Hi
W2K3 std edition (no SP) - SQL Server Std SP3
I have a lot of errors showing up in app log on different days and times in
the form of:
***********************************
MSSQLSERVER, Category (2), Event ID: 17055
Description:
18052
Error: 3314, Severoty:21, State: 4
***********************************
The 'error' number varies between, 3314, 9001 and 823.
The account is always the same one.
Trawling through the SQL log - I can see some entries with the following
detail:
***********************************
database 'XYZ' cannot be opened. it has been marked SUSPECT by recovery. See
the event log for more information.
***********************************
DBCC CHECKDB shows no errors on this database.
Any pointers on this very much appreciated.
All SQL services are currently running.
Thanks
BryanIf I were you, I would suck and backup as much of the data as you can
from the database files / disks. Seems to me that this is a hard error
inidcating that your underlying disks are about to die (or the
controller has a defect). Backup up and then checking / replacing the
databases would be the best to do. (for me)
HTH, Jens Suessmeyer.|||Hi Jens
Thanks for the prompt reply.
Would this still be the case, as I have a whole bunch of DBs stting on the
same disk location.
I should have also noted that this is a SAN attached server.
Are there any particular tools (that are non intrusive as this is a
production server) that can check the integrity of a particular database
(other than DBCC CHECKDB/CHECKALLOC/CHECKCATALOG)?
Thanks
Bry
"Jens" wrote:

> If I were you, I would suck and backup as much of the data as you can
> from the database files / disks. Seems to me that this is a hard error
> inidcating that your underlying disks are about to die (or the
> controller has a defect). Backup up and then checking / replacing the
> databases would be the best to do. (for me)
> HTH, Jens Suessmeyer.
>|||All of the errors point to disk problems, but given you are on a SAN(NAS?) I
would expect the problem is not hardware, but either overloading or
networking.
If you NAS/SAN configuration is not tuned properly, you could get the error
codes you listed.
Another possibility (which is why I added NAS rather than SAN) is that if
you have a bad or misconfigured switch, you could be seeing packe drops if
your server is 100MB and the switch port is 10MB.
Just ideas.
--
Joseph R.P. Maloney, CSP,CCP,CDP
"bryan" wrote:

> Hi
> W2K3 std edition (no SP) - SQL Server Std SP3
> I have a lot of errors showing up in app log on different days and times i
n
> the form of:
> ***********************************
> MSSQLSERVER, Category (2), Event ID: 17055
> Description:
> 18052
> Error: 3314, Severoty:21, State: 4
> ***********************************
> The 'error' number varies between, 3314, 9001 and 823.
> The account is always the same one.
> Trawling through the SQL log - I can see some entries with the following
> detail:
> ***********************************
> database 'XYZ' cannot be opened. it has been marked SUSPECT by recovery. S
ee
> the event log for more information.
> ***********************************
> DBCC CHECKDB shows no errors on this database.
> Any pointers on this very much appreciated.
> All SQL services are currently running.
> Thanks
> Bryan
>
>|||Hi Joseph
Thanks for your comments, always appreciated. I shall certainly take a look
at all your suggestions.
I will update any progress I make.
Best rgds
Bryan
"jrpm" wrote:
[vbcol=seagreen]
> All of the errors point to disk problems, but given you are on a SAN(NAS?)
I
> would expect the problem is not hardware, but either overloading or
> networking.
> If you NAS/SAN configuration is not tuned properly, you could get the erro
r
> codes you listed.
> Another possibility (which is why I added NAS rather than SAN) is that if
> you have a bad or misconfigured switch, you could be seeing packe drops if
> your server is 100MB and the switch port is 10MB.
> Just ideas.
> --
> Joseph R.P. Maloney, CSP,CCP,CDP
>
> "bryan" wrote:
>