December 29, 2014 at 11:49 am
We have a SQL Server 2008 SP3 Enterprise cluster. Two database CheckDB jobs failed, one of the databases jobs failed two days in a row. I copied the databases after the reported corruption and restored them to our test environment (test and production servers are not identical) and retested the CheckDB. That ran successfully. I also queried the 2 production database tables, they also ran successfully. The databases are mostly used 9-5, M-F, the jobs failed on a Saturday and Sunday night.
Message from Job:
Source: {5DAA337E-9AC6-42A4-A846-054D25886600}
Executing query "DECLARE @GUID UNIQUEIDENTIFIER
EXECUTE msdb..sp...".: 100% complete End Progress
DTExec: The package execution returned DTSER_FAILURE (1). Started: 11:00:01 PM Finished: 11:00:02 PM Elapsed: 1.154 seconds.
The package execution failed. The step failed.
Error logs are not giving me any information. Job doesn't show much to work with. What are my options? Comments / URLs are appreciated. Thanks...
December 30, 2014 at 1:41 am
Not enough information there. The CheckDB output would have been written to the error log. Look there.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
December 30, 2014 at 8:20 am
Both jobs ran successfully last night.
Still baffled by what happened here. Error logs had no information about a failure. Job logs showed a failure but without explanation. Same with the event viewer. No explanation as to what happened.
There are some underlying concerns here - we had a issue about a month ago where the default instance went down (the jobs that failed are on a named instance). Further review showed that our cluster Microsoft and third party drivers are old, 2009 timeframe, and need upgrading. This and other changes are being considered. Could this have contributed - don't know.
Any comments about this would be appreciated - thanks.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply