Bad indexes after software upgrade 7.3.00 Build 27

July 15, 2009 at 3:38 am

[] [] [] [] [] [] [] []

Related:

  1. NetWeaver 7.0/7.10: System copy (supplementary note)Symptom This note contains additions to the guidelines. Other terms...
  2. Problems w/ database links during the System Switch UpgradeSymptom What must I bear in mind during the system...
  3. Performance during Uppgrade – JOB_RASUVAR2Symptom During the upgrade you face a long runtime of...
  4. DB2 z/OS: Overview of transports and correctionsSymptom This note contains an overview of all transports and...

Symptom

B*TREE BAD INDEX 865672 (ROOT) in the knldiag.err since the software upgrade to Version 7.3.00 Build 27.
Other terms

Bad index, performance problems Performance problems;
Reason and Prerequisites

Problems may occur with the database indexes in Versions older than 7.3.00 Build 25. Note 541895 contains more detailed information.
The affected indexes are deactivated as of Version 7.3.00 Build 27 (they are set to “bad”).
Solution

Using the Database Manager GUI, you can activate (create again) the affected indexes.
1. Displaying the relevant indexes:
To display the relevant indexes, go to: Recovery -> Index actions -> Search
You can determine this information in SQL Studio as follows: SELECT * FROM info_bad_indexes2. Recreating the bad indexes:
You should recreate the indexes at times of minimal system workloads. In the index display of the Database Manager GUI, select the affected index(es) and then choose recreate.

[Slashdot] [Digg] [Reddit] [del.icio.us] [Facebook] [Technorati] [Google] [StumbleUpon]

Leave a Comment