April 1, 2010 at 7:39 am
As soon as change management sign's off, we will re-start the SQL Service, should hopefully fix the db.
That being said, some strange entries in the error log. I have never seen a SPID with an S on it:
2010-04-01 01:34:24.90 spid3s Error: 17053, Severity: 16, State: 1.
2010-04-01 01:34:24.90 spid3s LogWriter: Operating system error 1784(The supplied user buffer is not valid for the requested operation.) encountered.
2010-04-01 01:34:24.93 spid3s Write error during log flush.
2010-04-01 01:36:12.43 spid55 Error: 9001, Severity: 21, State: 1.
2010-04-01 01:36:12.43 spid55 The log for database 'tempdb' is not available. Check the event log for related error messages. Resolve any errors and restart the database.
2010-04-01 01:36:12.46 spid54 Error: 9001, Severity: 21, State: 1.
2010-04-01 01:36:12.46 spid54 The log for database 'tempdb' is not available. Check the event log for related error messages. Resolve any errors and restart the database.
2010-04-01 01:36:19.57 spid15s Drop Temp Obj: Failed, serializing drops...
2010-04-01 01:36:19.57 spid15s Drop Temp Obj: ...exc w/ser (9001,1), wait (0x40ms), WITH cursor(s)...
2010-04-01 01:36:19.64 spid15s Drop Temp Obj: ...exc w/ser (9001,1), wait (0x80ms), WITH cursor(s)...
2010-04-01 01:36:19.76 spid15s Drop Temp Obj: ...exc w/ser (9001,1), wait (0x100ms), WITH cursor(s)...
2010-04-01 01:36:20.01 spid15s Drop Temp Obj: ...exc w/ser (9001,1), wait (0x200ms), WITH cursor(s)...
2010-04-01 01:36:20.51 spid15s Drop Temp Obj: ...exc w/ser (9001,1), wait (0x400ms), WITH cursor(s)...
2010-04-01 01:36:21.53 spid15s Drop Temp Obj: ...exc w/ser (9001,1), wait (0x800ms), WITH cursor(s)...
2010-04-01 01:36:23.57 spid15s Drop Temp Obj: ...exc w/ser (9001,1), wait (0x1000ms), WITH cursor(s)...
2010-04-01 01:36:23.57 spid15s Drop Temp Obj: ...serializing drops FAILED.
What causes a S to be Appended to a SPID
/* ----------------------------- */
Tochter aus Elysium, Wir betreten feuertrunken, Himmlische, dein Heiligtum!
April 1, 2010 at 8:05 am
A system process has 's' appended to the session id in the error log. Check when SQL starts up, lots of system processes then.
I suggest you contact MS's customer support people regarding this. Also check your disks, especially the ones that TempDB is on.
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
April 1, 2010 at 8:19 am
Since when did the S get added? I now see it on other servers, I guess I just had not noticed it before. It seems to be dumbing down the log, it should be a given that any SPID < 50 is a system SPID, but thank you Microsoft for making more poeple think they can do our job by dumbing it down.
/* ----------------------------- */
Tochter aus Elysium, Wir betreten feuertrunken, Himmlische, dein Heiligtum!
April 1, 2010 at 9:10 am
GregoryF (4/1/2010)
Since when did the S get added?
SQL 2005 RTM iirc
It seems to be dumbing down the log, it should be a given that any SPID < 50 is a system SPID, but thank you Microsoft for making more poeple think they can do our job by dumbing it down.
Gee... Do you prefer stuff cryptic with magic numbers that need memorising?
I recall reading somewhere (that I now cannot find) that it is possible in 2005+ to have system sessions with a SPID above 50. Need to search for it.
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
November 23, 2010 at 4:40 pm
Have you got this issue solved? how? I am having the same issue.
December 8, 2010 at 1:02 pm
Waz r the tempdb not available due to the db placed on a different drive that was not available to the server due to some issue? I had seen this only on 1 instance when the drive which had tempdb files went down.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply