IT27317: NEW SEMI-DETACHED INDEX FRAGMENT INCURRED DURING LOGICAL RECOVERY WILL CAUSE DEFERRED INDEX RECREATION OF WHOLE INDEX

APAR status

• Closed as duplicate of another APAR.

Error description

• Adding a new fragment to a fragmented table is a leight weight
  operation even with indexes defined on it.  In case of
  'semi-detached' indices - no explicit storage specification, so
  index following table's fragmentation - this would involve
  equally simple and cheap index fragment creation.
  
  If such new index fragment creation is incurred during logical
  recovery, whether at server restart or during a logical restore,
  it is deferred until after logical recovery completed, then
  progressed on the final set of data.  Yet now it's not only this
  single new index fragment that's being created, but all
  pre-existing fragments of this index would be dropped and
  re-created as well - a potentially very costly and time
  consuming operation delaying the affected table becoming fully
  operational.
  
  Solving this design problem, existing since ever, is not being
  worked on.
  

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

• This APAR is a duplicate of IT28321
  

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