PM95985: Rebase error: 'The string ?x? is invalid because it contains 51 bytes, but the most bytes permitted for this field is 50'

Fixes are available

APAR status

Closed as program error.

Error description

APAR Description: The UCM integration between IBM Rational
ClearCase and ClearQuest products utilizes the
UCMUtilityActivity record to facilitate operations like deliver
and rebase. This record type is limited to 50 characters for
ucm_view and ucm_stream fields in the UCM package; however, the
integration is designed so that longer stream or view names are
allowed and will be truncated to fit in the fields.

ClearQuest 7.1.2 added support for Open Services for LifeCycle
Collaboration (OSLC) and this is the only method of connecting
to a UCM-integrated ClearQuest database in ClearCase 8.x. Due to
a product defect, long stream and view names are not properly
truncated when using OSLC. A rebase operation on such a stream,
for example, will result in this error:

M:\view_for_long_stream?cleartool rebase -recommended
Advancing to baseline 'base4' of component 'CVOB1'
Updating rebase view's config spec...
Creating integration activity...
cleartool: Error: 'CRVAP0290E CRMUD0032E The string
'abcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxy' is invalid
because it contains 51 bytes, but the most bytes permitted for
this field is 50. '
cleartool: Error: Unable to connect the integration activity to
ClearQuest.
cleartool: Error: Unable to create integration activity.
cleartool: Error: Unable to perform integration.
cleartool: Error: Unable to rebase stream
'abcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxy'.

Steps to reproduce:

1. Create a stream with a name longer than 50 characters on a
ClearQuest-integrated UCM project using OSLC
2. Create a baseline on the integration stream
3. Rebase the stream with long name

Workarounds:

1. If you are using full ClearCase client and have ClearQuest
installed, use crmregister to remove the existing OSLC
connection to the ClearQuest database and reregister it without
the -url option.
2. If you are using ClearTeam Explorer with web views on a
ClearCase 8.0.x WAN Server, the only option is to checkout the
ClearQuest schema and modify the UCMUtilityActivity record so
that the ucm_stream and ucm_view fields accept more than 50
characters.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:                                              *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The IBM Rational ClearCase UCM/ClearQuest OSLC integration
will generate an error to the user for view tags or stream
names longer than 50 characters for entry into ClearQuest
records.

Problem conclusion

Fixed in ClearCase 8.0.0.9 and 8.0.1.2.

Temporary fix

Comments

APAR Information

APAR number
PM95985
Reported component name
CLRCASE MSITE W
Reported component ID
5724G3200
Reported release
800
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2013-08-28
Closed date
2013-12-13
Last modified date
2013-12-13

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
CLRCASE MSITE W
Fixed component ID
5724G3200

Applicable component levels

R800 PSN
UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSSH3S","label":"Rational ClearCase MultiSite"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
13 December 2013

Tips

PM95985: Rebase error: 'The string ?x? is invalid because it contains 51 bytes, but the most bytes permitted for this field is 50'

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

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

Fixed component ID

Applicable component levels

R800 PSN

Document Information

Share your feedback

Need support?