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
templAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Jon_RaymondCommented:
Try running DBCC CheckDB against the database.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
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
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server

From novice to tech pro — start learning today.