JR33306: AFTER UPGRADE TO IA 8.1.1 FROM 8.1 AND DO NOT HAVE REQUISITE XME TA PATCH WHEN THEY UPGRADE, ISSUES WITH DELETE OPERATION

APAR status

• Closed as program error.

Error description

• Due to a version mismatch issue of the model class jar on the
  classpath, the model upgrade deployer does not completely
  update the repository database
  
  First, users would not be able to deploy or upgrade any model
  that extends the upgraded model. For example, after the
  'investigate' model is upgraded, any attempt to deploy a model
  that extends the 'investigate' model will result in an error.
  Second, a key usage of the XMetaCore model is in determining
  objects that are the targets of unidirectional non-containment
  references for the purposes of deriving deletion candidates.
  That is, when an object in the repository is deleted, we use
  the XMetaCore information to determine whether there are other
  objects in the repository that are pointing to the object being
  deleted via a unidirectional reference. If there is an inverse
  cascade rule, that object pointing to the delete object will
  also be deleted. If an inverse cascade rule is not present,
  that object's reference is set to null. When the XMetaCore
  information in the repository is not complete and valid (i.e.
  in the case after the model has been upgraded), delete
  operations may leave inconsistent data in the repository.
  
  After the 'investigate' model has been upgraded, deletions to
  any object in the repository may result in 'investigate'
  instances not being properly updated -- leading to repository
  data inconsistencies. Specifically, if there is any
  unidirectional reference from class X in the 'investigate'
  model to any other modeled class Y (either in the same or
  different model), and if an instance of Y is deleted from the
  repository without the related X instance also explicitly
  deleted at the same time, then data corruption will occur. A
  repository exception would occur if the user tried to
  subsequently load the X instance, because it will be pointing
  to an object that had already been deleted.
  

Local fix

• XMeta team will create a patch
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  Upgrade to Information Analyzer 8.1.1 results in missing
  internal repository structures in XMeta database
  ****************************************************************
  PROBLEM DESCRIPTION:
  Upgrading to IBM InfoSphere Information Analyzer Version 8.1.1
  may result in missing updates to internal repository structures
  in the XMeta database. This may lead to silent repository
  corruption when metadata is deleted from the XMeta repository.
       The missing structures
  could also cause visible errors when  subsequent model
  upgrades are applied to the repository. For    example, an
  error will occur if a FastTrack 8.1.1 installation  is
  subsequently attempted.
           Users who have applied both
  Metadata repository patches CQ150366and JR33055 (or its
  replacements) before installing Information Analyzer 8.1.1 are
  not affected.
  ****************************************************************
  RECOMMENDATION:
  Users who have not yet installed Information Analyzer 8.1.1
  should apply both Metadata repository prerequisite patches
  CQ150366 and JR33055 (or any newer rollup patch that includes
  these fixes).
            Users who have
  applied patch CQ150366 but not JR33055 (or its  replacements)
  should apply JR33055 to the Information Server   services
  domain environment. After the JR33055 patch is        applied,
  run the following command from the Information Server  domain's
  ASBServer/bin directory:
  _deployment -r          At the completion
  of this command, the missing internal        repository
  structures will be rebuilt.
  
  This change is included in 8.1 Fix Pack 1.
  
  ****************************************************************
  

Problem conclusion

• The Metadata repository's model deployment component was fixed
  to correctly modify the internal repository structures during
  the Information Analyzer 8.1.1 installation.
  

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:

Modules/Macros

• DOMAIN
  

Fix information

• Fixed component name

  WIS METADATA SE

• Fixed component ID

  5724Q36MS

Applicable component levels

• R810 PSY

     UP