PM49020: ReqWeb is unresponsive after clearing a suspect relationship (external)

APAR status

• Closed as program error.

Error description

• - IBM Rational RequisitePro Web (ReqWeb) appears unresponsive
  due to a database lock when modifying a requirement and such
  action causes its relationships to be suspect
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  USERS AFFECTED:
  - Users of Rational RequisitePro client for Web (RequisiteWeb)
  modifying a requirement with cross-project relathionships and
  both projects of the relationship reside in the same database
  schema.
  
  PROBLEM DESCRIPTION:
  - When modifying a requirement and such action causes its
  relationships to be suspect, the RequisiteWeb does not complete
  the operation and states either timeout errors or resource busy
  status depending of the type of database being used.?
  
  The common problems are, depending of the database type:
  SQL Server.
  The requirement update request takes a while to have the
  RequisiteWeb to respond and finaly after a while finishes with
  this error:
  ReqPro40.Requirement.Save-?ReqPro40.Rules.SaveRequirement-?ReqPr
  OLE DB Provider for ODBC Drivers: [Microsoft][ODBC SQL Server
  Driver]Timeout expired
  
  Oracle.
  The requirement update request never return and seems to hang.?
  If another request is made over the same requirement an error
  displays:
  ReqPro40.Requirement.Save-?ReqPro40.Rules.SaveRequirement-?ReqPr
  OLE DB Provider for ODBC Drivers: [Microsoft][ODBC driver for
  Oracle][Oracle]ORA-00054: resource busy and acquire with NOWAIT
  specified
  

Problem conclusion

• RequisiteWeb code was updated to correctly update the
  requirement and its relationships successfully without
  causing table locks.
  The fix for this APAR was included in RequisitePro version
  7.1.1.8, 7.1.2.5 and 7.1.3.1.
  

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

• Fixed component name

  REQUISITEPRO WI

• Fixed component ID

  5724G3900

Applicable component levels

• R712 PSN

     UP