Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase ««123»»

Faultfinding possible I/O issues Expand / Collapse
Author
Message
Posted Tuesday, April 24, 2012 10:50 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 4:28 PM
Points: 43,028, Visits: 36,193
Both of the errors you've listed indicate there's some form of disk problem. Maybe contact the SAN vendor (assuming it's a SAN) and get them to check it out.


Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1289195
Posted Wednesday, April 25, 2012 9:08 AM


SSCarpal Tunnel

SSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal Tunnel

Group: General Forum Members
Last Login: Today @ 12:22 PM
Points: 4,356, Visits: 6,191
SQLIOSIM is the tool to use to validate that an IO subsystem will properly handle SQL Server IO-style workloads.

Best,

Kevin G. Boles
SQL Server Consultant
SQL MVP 2007-2012
TheSQLGuru at GMail
Post #1289974
Posted Wednesday, April 25, 2012 9:14 AM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Friday, August 8, 2014 3:25 AM
Points: 2,285, Visits: 781
http://support.microsoft.com/default.aspx?scid=kb;en-us;815183

the error Could not open FCB for invalid file ID %d in database '%.*ls'. is know to cause data corruption, thread errors and runtime errors

are there different service pack versions on the shipper and shipee?


MVDBA
Post #1289982
Posted Wednesday, April 25, 2012 9:16 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 4:28 PM
Points: 43,028, Visits: 36,193
TheSQLGuru (4/25/2012)
SQLIOSIM is the tool to use to validate that an IO subsystem will properly handle SQL Server IO-style workloads.


But SQL needs to be stopped when running that. The aim is to validate the IO subsystem, nor slaughter it.



Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1289985
Posted Wednesday, April 25, 2012 9:16 AM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Friday, August 8, 2014 3:25 AM
Points: 2,285, Visits: 781
by the way -

FCB stands for File Control Block, the physical file structure used
by SQL to write in and read data from the storage.

i've had these before when i defragged a database and the log shipping made the same changes on the target.


MVDBA
Post #1289987
Posted Wednesday, April 25, 2012 9:33 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 4:28 PM
Points: 43,028, Visits: 36,193
michael vessey (4/25/2012)
FCB stands for File Control Block, the physical file structure used
by SQL to write in and read data from the storage.


Almost.

FCB means "File Control Bank"
It's an in-memory structure that keeps track of various pieces of file information for the files in the database.

i've had these before when i defragged a database and the log shipping made the same changes on the target.


Defragged as-in a disk defrag tool? Most 'online' disk defrag tools don't support SQL Server and will cause all sorts of damage if they're run on an open, in-use SQL database.



Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1290012
Posted Wednesday, April 25, 2012 9:35 AM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Friday, August 8, 2014 3:25 AM
Points: 2,285, Visits: 781
index defrag

MVDBA
Post #1290019
Posted Wednesday, April 25, 2012 9:37 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 4:28 PM
Points: 43,028, Visits: 36,193
How can you do an index defrag of a log shipping secondary? It's read-only at best. Or do you mean index rebuild on the primary and log shipping copied that over? If the latter caused that error on the secondary, there's something wrong with that DB or server.


Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1290024
Posted Wednesday, April 25, 2012 9:50 AM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Friday, August 8, 2014 3:25 AM
Points: 2,285, Visits: 781
GilaMonster (4/25/2012)
How can you do an index defrag of a log shipping secondary? It's read-only at best. Or do you mean index rebuild on the primary and log shipping copied that over? If the latter caused that error on the secondary, there's something wrong with that DB or server.


are you having a senior moment ?

i defragged the indexes on the primary (or shipper) and when the log is copied across the same changes are applied to the secondary (or shipee)


MVDBA
Post #1290047
Posted Wednesday, April 25, 2012 9:50 AM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Wednesday, June 12, 2013 5:52 AM
Points: 52, Visits: 214
michael vessey (4/25/2012)
http://support.microsoft.com/default.aspx?scid=kb;en-us;815183

the error Could not open FCB for invalid file ID %d in database '%.*ls'. is know to cause data corruption, thread errors and runtime errors

are there different service pack versions on the shipper and shipee?


On one of the three server pairs in question, yes the hotfixes don't match (2282+2187, and I am awaiting clearance to patch)...and of the four times we have had this problem, the mismatched shippee was the host TWICE.
Post #1290048
« Prev Topic | Next Topic »

Add to briefcase ««123»»

Permissions Expand / Collapse