APAR status
Closed as program error.
Error description
Requirements fail to get pushed to RequistePro from Rational Requirements Composer via integration Manage Requirements. An error is present in the log. 'CRRRC1800E The RequisitePro operation failed: Error retrieving new database key.'
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: * **************************************************************** * PROBLEM DESCRIPTION: * **************************************************************** * RECOMMENDATION: * **************************************************************** Using the integration of Rational Requirements Composer and RequisitePro, an error occurs when the user tries to manage requirements. This might happen when in a concurrent transactions different users are trying to manage requirements. For some users the manage requirements action does not work and returns an error: "Error retrieving new database key." instead.
Problem conclusion
A logic was added to increase the fault tolerance.
Temporary fix
Comments
APAR Information
APAR number
PM25502
Reported component name
RATL REQ COMP C
Reported component ID
5724W8702
Reported release
711
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-10-28
Closed date
2011-03-28
Last modified date
2011-03-28
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
R711 PSN
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSSHCT","label":"Rational RequisitePro"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.1.1","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
28 March 2011