PI48081: ASSETS CAN BECOME INACCESSIBLE IN THE WEB CLIENT AND MULTIPLE ASSETBUSYEXCEPTION ENTRIES CAN BE SEEN IN THE LOG.

Rational Asset Manager Fix Pack 4 (7.5.2.4) for 7.5.2
Rational Asset Manager 7.5.3
Rational Asset Manager 7.5.3.1
Rational Asset Manager 7.5.3.2
Rational Asset Manager 7.5.3.3
Rational Asset Manager 7.5.4
Rational Asset Manager 7.5.4.1
Rational Asset Manager 7.5.4.2
Rational Asset Manager 7.5.4.3
Rational Asset Manager 7.5.4.4
Rational Asset Manager 7.5.4.5
Rational Asset Manager 7.5.4.6
Rational Asset Manager 7.5.4.7
Rational Asset Manager 7.5.4.9
Rational Asset Manager 7.5.4.8
Rational Asset Manager 7.5.4.10

APAR status

• Closed as fixed if next.

Error description

• Using IBM Rational Asset Manager 7.5.2.2, Assets can become
  inaccessible due to inconsistent revision count information in
  the RAM schema database.
  The revision count is one of the columns of the Asset table. It
  is also part of the xml stored in the Manifest column. The two
  revision counts should be the same before or after the asset
  update. If not, the AssetBusyException is thrown.
  
  Errors such as the following can be observed in the ramdebug.log
  file.
  
  08/18/15 00:11:22 CEST] CRRAM0001E  26024657 ERROR
  com.ibm.ram.repository.fsearch.assets.AssetIndexBuilder - Error
  indexing asset:
  182925.  This asset will be partially indexed.  Error ID:
  BB862170498542072B6D5F75811FA25B
  com.ibm.ram.repository.core.IRepositoryAccess$RepositoryExceptio
  n: Asset was busy being updated. Couldn't migrate asset.
  
  Caused by:
  com.ibm.ram.repository.core.IRepositoryAccess$AssetBusyException
  : Asset is busy being updated by someone else. Asset is
  "{5637677A-41A6-A6B3-1C6F-361E00A27951} \u200e[1.2.4]"
  

Local fix

• Contact IBM Rational technical support to get a guidance on a
  possible workaround
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * server                                                       *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * The revision count is one of the columns of the Asset table. *
  * It is also part of the xml stored in the Manifest column.    *
  * The two revision counts should be the same before or after   *
  * the asset update. If not, the AssetBusyException is thrown.  *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  

Problem conclusion

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

• R752 PSY

     UP