PM12008: Index regeneration fails to run properly.

APAR status

• Closed as Permanent restriction.

Error description

• Updating Indexing (automatically or manually) causes the
  following error:
  
  This is the error message:
  2010/03/24 12:50:47  ERROR: Failed to optimize search index.
  Stack trace: java.io.IOException: background merge hit
  exception: _28v:
  c1 _29o:c3 _29p:c1 _2aw:c2 _2ax:c1 _2c4:c2 _2c5:c1 _2dc:c1
  _2dd:c9 _2dn:
  c1 into _2ei [optimize]
  
   at java.lang.Throwable.?init?(Throwable.java:67)
  
   at
  org.apache.lucene.index.IndexWriter.optimize(IndexWriter.java:17
  36)
  
   at
  org.apache.lucene.index.IndexWriter.optimize(IndexWriter.java:17
  27)
  
   at
  org.apache.lucene.index.IndexWriter.optimize(IndexWriter.java:17
  07)
  
   at
  com.telelogic.cs.search.SearchIndex.doOptimize(SearchIndex.java:
  102)
   at com.telelogic.cs.search.SearchIndexerThread.redoDocuments
  
  (SearchIndexerThread.java:1051)
  
   at
  com.telelogic.cs.search.SearchIndexerThread.run(SearchIndexerThr
  ead.
  java:429)
  
  Caused by:
  
  java.lang.NullPointerException
  
   at org.apache.lucene.store.BufferedIndexOutput.writeBytes
  
  (BufferedIndexOutput.java:49)
  
   at
  org.apache.lucene.store.IndexOutput.writeBytes(IndexOutput.java:
  40)
  
   at
  org.apache.lucene.index.SegmentMerger.mergeNorms(SegmentMerger.j
  ava:
  566)
  
   at
  org.apache.lucene.index.SegmentMerger.merge(SegmentMerger.java:1
  35)
  
   at
  org.apache.lucene.index.IndexWriter.mergeMiddle(IndexWriter.java
  :
  
  3273)
  
   at
  org.apache.lucene.index.IndexWriter.merge(IndexWriter.java:2968)
  
   at
  org.apache.lucene.index.ConcurrentMergeScheduler$MergeThread.run
  
  (ConcurrentMergeScheduler.java:240).
  
  
  
  Known Workaround:
  
  Install the latest patch (5.2.0.2 02) and disable the Search
  Optimizer by adding the following line to the pt.cfg file:
  
  [CCM_SYSTEM][SEARCH_OPTIMIZE_TIMER_MINS]0[/SEARCH_OPTIMIZE_TIMER
  _MINS][/CCM_SYSTEM]
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Index regeneration fails to run properly.
  

Problem conclusion

• A workaround to avoid the problem has been provided in
  Rational Change 5.2.0.2.02 and 5.3.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels