• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 431
  • Last Modified:

sql server 6.5 database repair

Hi everybody,

I have run sqlmaint.exe to check the consistency of my SQL Server 6.5 database.
The check fails and the generated log contains a large number of lines of the following form

Extent not within segment: Object 94623380, indid 1 includes extents on allocation page 106240 which is not in segment 1.
Extent not within segment: Object 94623380, indid 1 includes extents on allocation page 109312 which is not in segment 1.
Extent not within segment: Object 238623893, indid 255 includes extents on allocation page 112640 which is not in segment 1.
Extent not within segment: Object 238623893, indid 255 includes extents on allocation page 112384 which is not in segment 1.
Extent not within segment: Object 238623893, indid 255 includes extents on allocation page 112128 which is not in segment 1.
Extent not within segment: Object 238623893, indid 255 includes extents on allocation page 111872 which is not in segment 1.
Extent not within segment: Object 238623893, indid 255 includes extents on allocation page 111104 which is not in segment 1.
Extent not within segment: Object 238623893, indid 255 includes extents on allocation page 111616 which is not in segment 1.
Extent not within segment: Object 238623893, indid 255 includes extents on allocation page 110336 which is not in segment 1.
Extent not within segment: Object 238623893, indid 255 includes extents on allocation page 109824 which is not in segment 1.
Extent not within segment: Object 238623893, indid 255 includes extents on allocation page 110080 which is not in segment 1.
Extent not within segment: Object 238623893, indid 255 includes extents on allocation page 109568 which is not in segment 1.


How can I repair the database?
I have exported it to a backup device and successfully imported it again, but
without any change in the sqlmaint.exe log

Any idea?

- Josef
0
templ
Asked:
templ
  • 2
1 Solution
 
Jon_RaymondCommented:
Try running DBCC CheckDB against the database.
0
 
templAuthor Commented:
done.
the problem persists.
then I have shut down the sql server and restartet it.
now it seems to work fine.
this is a bit frightening, isn't it?

thanks anyway for the comment.
0
 
Jon_RaymondCommented:
Yes. You should do this regularly as part of a maintenance script through the scheduler.  You can also try the maintenance wizard which will create a similar routine.
0

Featured Post

Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now