Integrity and Optimization failures

Hi All-
I have a websense log database that the Optimization and Integrity check
jobs fail on. My problem is I cannot determine WHY exactly these jobs have
failed. If I run the DBCC CHECKDB and DBCC SHOWCONTIG commands nothing
appears to be a problem. I even tried running the optimization and integrity
checks while the database is in single user mode to no avail. How can I A.
determine what the problem is and B. correct it?
Thank You for your help in advance!
--GREENTHUMB--
I suggest you specify a report file for the Maint plan and check for specific error messages in that
report file.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"GreenThumb" <GreenThumb@.discussions.microsoft.com> wrote in message
news:B77C25CE-B5FA-4CF2-AF33-EC4383B0F947@.microsoft.com...
> Hi All-
> I have a websense log database that the Optimization and Integrity check
> jobs fail on. My problem is I cannot determine WHY exactly these jobs have
> failed. If I run the DBCC CHECKDB and DBCC SHOWCONTIG commands nothing
> appears to be a problem. I even tried running the optimization and integrity
> checks while the database is in single user mode to no avail. How can I A.
> determine what the problem is and B. correct it?
> Thank You for your help in advance!
> --GREENTHUMB--
|||Hi Tibor-
I have enabled writing to the Event Log and notification to my e-mail but
the error message is extremely vague:
Event Type:Warning
Event Source:SQLSERVERAGENT
Event Category:Job Engine
Event ID:208
Date:4/20/2005
Time:10:13:13 AM
User:N/A
Computer:XXXXXXXXX
Description:
SQL Server Scheduled Job 'Integrity Checks Job for DB Maintenance Plan
'Integrity check for wslogdb55'' (0xAAA25C1534A233429802DCAD2F19BC91) -
Status: Failed - Invoked on: 2005-04-20 10:13:06 - Message: The job failed.
The Job was invoked by User XXX\ADMINISTRATOR. The last step to run was step
1 (Step 1).
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
"Tibor Karaszi" wrote:

> I suggest you specify a report file for the Maint plan and check for specific error messages in that
> report file.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "GreenThumb" <GreenThumb@.discussions.microsoft.com> wrote in message
> news:B77C25CE-B5FA-4CF2-AF33-EC4383B0F947@.microsoft.com...
>
>
|||The vagueness of that message is exactly why I suggested to specify in the maint plan to create a
report file. In there you will find the error messages from SQL Server.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"GreenThumb" <GreenThumb@.discussions.microsoft.com> wrote in message
news:67884CB9-7C98-4242-A4AC-900F49ACD0E7@.microsoft.com...[vbcol=seagreen]
> Hi Tibor-
> I have enabled writing to the Event Log and notification to my e-mail but
> the error message is extremely vague:
> Event Type: Warning
> Event Source: SQLSERVERAGENT
> Event Category: Job Engine
> Event ID: 208
> Date: 4/20/2005
> Time: 10:13:13 AM
> User: N/A
> Computer: XXXXXXXXX
> Description:
> SQL Server Scheduled Job 'Integrity Checks Job for DB Maintenance Plan
> 'Integrity check for wslogdb55'' (0xAAA25C1534A233429802DCAD2F19BC91) -
> Status: Failed - Invoked on: 2005-04-20 10:13:06 - Message: The job failed.
> The Job was invoked by User XXX\ADMINISTRATOR. The last step to run was step
> 1 (Step 1).
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
>
> "Tibor Karaszi" wrote:
|||Hi Tibor-
Okay - I enabled the reports and the error given is "database is already
open and can only have one user at a time". However, I checked Single User
Mode *AND* even detached and re-attached and set to Single User to no avail.
I also checked Process info. but that database was not being accessed. Any
ideas?
Thank You!!!
--GREENTHUMB--
Microsoft (R) SQLMaint Utility (Unicode), Version Logged on to SQL Server
'ORCRASV005' as 'GWN\services' (trusted)
Starting maintenance plan 'Integrity check for wslogdb55' on 4/20/2005
6:35:03 PM
[1] Database wslogdb55: Check Data and Index Linkage...
[Microsoft SQL-DMO] Error 22285: [SQL-DMO]Database 'wslogdb55' is already
open and can only have one user at a time.
The following errors were found:
[Microsoft][ODBC SQL Server Driver][SQL Server]Database 'wslogdb55' is
already open and can only have one user at a time.
** Execution Time: 0 hrs, 0 mins, 4 secs **
End of maintenance plan 'Integrity check for wslogdb55' on 4/20/2005 6:35:07
PM
SQLMAINT.EXE Process Exit Code: 1 (Failed)
"Tibor Karaszi" wrote:

> The vagueness of that message is exactly why I suggested to specify in the maint plan to create a
> report file. In there you will find the error messages from SQL Server.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "GreenThumb" <GreenThumb@.discussions.microsoft.com> wrote in message
> news:67884CB9-7C98-4242-A4AC-900F49ACD0E7@.microsoft.com...
>
>
|||You need to uncheck the checkbox in the maintenance plan that says to
"Repair minor problems" and it should work fine. When you have that checked
it tries to put the db in single user mode and if it can't it errors. You
really don't want it repairing things on it's own anyway.
Andrew J. Kelly SQL MVP
"GreenThumb" <GreenThumb@.discussions.microsoft.com> wrote in message
news:432B45E0-DA60-455B-AA32-84EC8FCC3700@.microsoft.com...[vbcol=seagreen]
> Hi Tibor-
> Okay - I enabled the reports and the error given is "database is already
> open and can only have one user at a time". However, I checked Single
> User
> Mode *AND* even detached and re-attached and set to Single User to no
> avail.
> I also checked Process info. but that database was not being accessed.
> Any
> ideas?
> Thank You!!!
> --GREENTHUMB--
>
> Microsoft (R) SQLMaint Utility (Unicode), Version Logged on to SQL Server
> 'ORCRASV005' as 'GWN\services' (trusted)
> Starting maintenance plan 'Integrity check for wslogdb55' on 4/20/2005
> 6:35:03 PM
> [1] Database wslogdb55: Check Data and Index Linkage...
> [Microsoft SQL-DMO] Error 22285: [SQL-DMO]Database 'wslogdb55' is already
> open and can only have one user at a time.
> The following errors were found:
> [Microsoft][ODBC SQL Server Driver][SQL Server]Database 'wslogdb55' is
> already open and can only have one user at a time.
> ** Execution Time: 0 hrs, 0 mins, 4 secs **
> End of maintenance plan 'Integrity check for wslogdb55' on 4/20/2005
> 6:35:07
> PM
> SQLMAINT.EXE Process Exit Code: 1 (Failed)
> "Tibor Karaszi" wrote:
|||Since this job is checking database integrity, is this always a good
practice?