each week we have the same failure, allways on the same time.
03:00000:03078:2006/04/23 00:48:48.03 server Starting diagnostics for read failure:
03:00000:03078:2006/04/23 00:48:48.03 server Device Information:
Device number = 10
Phyname = /xxxx1/xxxxt/xx.dat
03:00000:03078:2006/04/23 00:48:48.03 server Buffer Information:
Buf addr = 0x104bda9d8f8, Mass addr = 0x104bda9d8f8
Buf pageno = 2108339, Mass pageno = 2108339, dbid = 4
03:00000:03078:2006/04/23 00:48:48.03 server
Buf virtpg = 167783347, Mass virtpg = 167783347
Buf stat = 0x1, Mass stat = 0x1008
Mass keep = 1, Mass awaited = 0
03:00000:03078:2006/04/23 00:48:48.03 server Page Information from first read attempt: Page read from disk ppageno = 2108339, pobjid = 468193687, pin
did = 255 pnextpg = 2108340, pprevpg = 2108338 plevel = 251, pstat = 0x20 pts_hi = 8, pts_lo = 1354996469
03:00000:03078:2006/04/23 00:48:48.03 server Page Information from second read attempt: Page read from disk ppageno = 2108339, pobjid = 221930273, pi
ndid = 0 pnextpg = 0, pprevpg = 0 plevel = 0, pstat = 0x891 pts_hi = 10, pts_lo = -1627039446
03:00000:03078:2006/04/23 00:48:48.03 server SDES Information:
dbid = 4, objid = 221930273, scur.pageid = 2108339
sstat = 0x20000c1, sstat2 = 0x200020
suid = 1, cacheid = 0
03:00000:03078:2006/04/23 00:48:48.03 server PSS Information:
pstat = 0x10100, pcurdb = 4, pspid = 3078
p2stat = 0x1000, p3stat = 0x18800
plasterror = 0, preverror = 0, pattention = 0:
03:00000:03078:2006/04/23 00:48:48.03 server End diagnostics for read failure:
03:00000:03078:2006/04/23 00:48:48.03 server Suspect a Device or OS problem, Second IO successfull
03:00000:03078:2006/04/23 00:48:48.03 server Diagnostic checks have been turned on to report if a corrupted page is read from or written to disk. Use
DBCC TRACEOFF(615) to turn these checks off.
03:00000:03078:2006/04/23 00:48:48.05 server Error: 694, Severity: 24, State: 1
03:00000:03078:2006/04/23 00:48:48.05 server An attempt was made to read logical page '2108339', virtpage '167783347' from virtual device '10' for ob
ject '221930273' in database '4'. The page was not read successfully. You may have a device problem or an operating system problem.
which means each week you have a job that does the same thing and fetches page 2108339 in dbid 4.
This database is corrupt. You need to go back to a good backup, considering this has been happening over weeks I take that previous backups are also corrupt.
BCP out all the data that is sitting on vdevno=10. There is a script in codexchange.sybase.com that maps objects to devices. From that list, bcp out all objects sitting on vdevno=10. You may lose data for objid 221930273.
Drop all the tables that you just bcp'ed out.
Initialize a new disk the same size as vdevno=10.
Create the new tables using user defined segments on the new device
Change the segmap in master..sysusages for the vdevno=10 to 0
dbcc dbrepair(4, remap)
Do a full dbcc check.