Skip to end of metadata
Go to start of metadata

Use

Number of bad indexes: <number>

 

Explanation

If an index tree is destroyed this may have an enormous impact on performance. Especially when big tables are affected commands may run amok and slow down the whole system up to a near stand-still. 
Indexes may get corrupt because of hardware failures and seldomly software problems. 

 

User Response

Indexes marked as bad are identified and shown in Database Studio and transaction db50. They can directly be regenerated without the need to specify their exact definition.
As often hardware problems have caused bad indexes you should generally check the hardware as next time permanent data pages might be affected. Run a CHECK DATA.

 

More Information

Relevant  DB-Analyzer Files
Helpful with ...
DBAN_RUNNING_COMMANDS.prtIdentify possible long-running commands. 
SAP Note
Helpful with ...
928037 - FAQ: SAP MaxDB Indexes Provides general information about indexes. 
167394 - SAP MaxDB: BAD INDEX Bad indexes after recovery or restart - what to do? 
Expert Sessions (Link to trainings)
Content / Helpful with ...

Session 16: SAP MaxDB SQL Query Optimization (Part 1)
Session 16: SAP MaxDB SQL Query Optimization (Part 2)

General information about SQL optimization also showing the importance of ready-for-use indexes.
Documentation (Links)
Helpful with ...
  

                            

  • No labels