Fixes are available
Rational ClearCase Fix Pack 14 (8.0.1.14) for 8.0.1
Rational ClearCase Fix Pack 4 (9.0.0.4) for 9.0
Rational ClearCase Fix Pack 15 (8.0.1.15) for 8.0.1
Rational ClearCase Fix Pack 5 (9.0.0.5) for 9.0
Rational ClearCase Fix Pack 6 (9.0.0.6) for 9.0
Rational ClearCase Fix Pack 16 (8.0.1.16) for 8.0.1
Rational ClearCase Fix Pack 17 (8.0.1.17) for 8.0.1
Rational ClearCase Fix Pack 18 (8.0.1.18) for 8.0.1
Rational ClearCase Fix Pack 19 (8.0.1.19) for 8.0.1
Rational ClearCase Fix Pack 20 (8.0.1.20) for 8.0.1
Rational ClearCase Fix Pack 21 (8.0.1.21) for 8.0.1
Rational ClearCase Fix Pack 22 (8.0.1.22) for 8.0.1
Rational ClearCase Fix Pack 23 (8.0.1.23) for 8.0.1
Rational ClearCase Fix Pack 24 (8.0.1.24) for 8.0.1
Rational ClearCase Fix Pack 25 (8.0.1.25) for 8.0.1
APAR status
Closed as program error.
Error description
When performing audited builds in an IBM Rational ClearCase dynamic view, if a Derived Object (DO) is being winked in over another DO, or if a winked-in DO needs to be rebuilt, the delete operation will succeed, but teh following error will appear in the MVFS log: mvfs2nt_vop_fsync: vnode @ 0xFFFFFA80069FF6E0 status=0xc0000022 - Permission denied Note: status=0xc0000022 is the Windows "access denied" NTSTATUS code. "Permission denied" is the "human readable equivalent. This error message does not cause the build to fail, and has no known operational impact.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: * * Audited builds in ClearCase dynamic views on Microsoft * * Windows. * **************************************************************** * PROBLEM DESCRIPTION: * * When performing audited builds in a ClearCase dynamic view, * * the customer may see an "ACCESS DENIED" error log entry when * * deleting a derived object, although the delete operation * * completes successfully. * * This error does not affect the build outcome. * **************************************************************** * RECOMMENDATION: * ****************************************************************
Problem conclusion
This status is logged when a winked in derived object is being replaced by a rebuilt object or by a different winked in object, if a filesystem flush operation is incorrectly called for a non-modifiable object in VOB storage. This problem has been fixed in ClearCase 8.0.1.14 and 9.0.0.4.
Temporary fix
Comments
APAR Information
APAR number
PI30193
Reported component name
CLEARCASE WIN
Reported component ID
5724G2900
Reported release
801
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2014-11-21
Closed date
2017-03-16
Last modified date
2017-03-16
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
CLEARCASE WIN
Fixed component ID
5724G2900
Applicable component levels
R801 PSY
UP
R900 PSY
UP
Document Information
Modified date:
16 October 2021