> how reliable is the feature in the DBMCli which shows broken indices?
DBMGui, of course ...
Florian Schmitz
______________________
acardo technologies AG
Königswall 18a
44137 Dortmund
fon: +49 (0) 2 31 / 58 44 97 - 0
fax: +49 (0) 2 31 / 58 44 97 - 21
mail: [EMAIL PROTECTED]
web: www.acardo.com
Florian Schmitz schrieb:
Hi Martin,
how reliable is the feature in the DBMCli which shows broken indices?
We suffer from a quite similar problem like Michael, but there are no
broken indices shown.
Even Index-recovery says there are no broken indices. So i guess that
there are none, but DB is growing and growing while we're putting more
and more out-of-date stuff into our archive-instance.
Thanks,
Flo
Florian Schmitz
______________________
acardo technologies AG
Königswall 18a
44137 Dortmund
fon: +49 (0) 2 31 / 58 44 97 - 0
fax: +49 (0) 2 31 / 58 44 97 - 21
mail: [EMAIL PROTECTED]
web: www.acardo.com
Kittel, Martin schrieb:
Hi Michael,
Is there any possibility to run some kind of compaction/repair which
will delete this unused space. I've tried allready the DB check,
which failed with -9041 Index not accessible.
you have bad/broken indices in your database. You should try and
recreate them using either dbmgui or 'sql_recreateindex' in dbmcli.
Once you do not have bad indices any more, a database structure check
will free unused pages.
Best wishes,
Martin.
--
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
