IBM Support

Vob server operation Create Container failed

Troubleshooting


Problem

This technote explains why an error will occur when attempting to add a new file to source control using IBM® Rational® ClearCase® on Microsoft® Windows® accessing a UNIX® or Linux® VOB in an interoperation (interop) environment.

Symptom

  • Attempts to add a new object to source control in a UNIX VOB from Windows results in the following error:

    V:\user_wx\testvob2\source>cleartool mkelem file.txt
    Creation comments for "file.txt":
    mkelem comment
    .
    cleartool: Error: Vob server operation "Create Container" failed.
    Additional information may be available in the vob_log on host "VOB_server"
    cleartool: Error: Unable to create directory "\\VOB_server\vobstore\testvob2.vbs\s\sdft\1a":
    operation not permitted.
    cleartool: Error: Unable to create element "file.txt".

    Errors in vob_log on the UNIX/Linux server:

    12/23/02 13:27:29 vob_server(20995): Error: unable to set ownership of file s/sdft/16/28: Not owner
    12/23/02 13:27:29 vob_server(20995): Error: Unable to create container /vobstore/testvob2.vbs/s/sdft/1a: Not owner


    cleartool describe -long of the VOB from Windows:

    H:\>cleartool desc -l vob:\testvob2
    versioned object base "\testvob2"
    created 02-Jan-03.11:53:46 by ClearCase Administrator (vobadm.tesas@VOB_server) "Created using create_vob(8s)."
    VOB family feature level: 3
    VOB storage host:pathname "VOB_server.domain.com:/4clearcase//vobadm/vobstore/testvob2.vbs"
    VOB storage global pathname "\\VOB_server.domain.com\home\vobadm\vobstore\testvob2.vbs"
    database schema version: 54
    VOB ownership:
    owner nobody
    group nobody
    Additional groups:
    group nobody
    group domain\group1


    credmap for logged in user from Windows:

    C:\Rational\ClearCase\etc\utils>credmap VOB_server.domain.com
    Identity on local system:
    User: domain\user_wx (NT:S-1-5-21-2025429....)
    Primary group: domain\group1 (NT:S-1-5-21-2025429....)

    The primary group, domain\group1, of the user account is in the VOB's Additional Group list, but the cleartool describe for the VOB shows nobody as the group owner on Windows.

    Note: A describe of the same VOB from the UNIX/Linux side shows the correct group ownership.


  • You may also see slightly different error messages on the Linux log file such as the following:

    2013-05-15T08:52:40-04:00 vob_server(31498): Error: unable to set ownership of file s/sdft/0/30/tmp_1108.138: Operation not permitted
    2013-05-15T08:52:40-04:00 vob_server(31498): Error: Unable to create container /disk1/vobstrg/cadscript.vbs/s/sdft/0/30/tmp_1108.138: Operation not permitted
    2013-05-15T08:52:40-04:00 vob_server(31498): Error: unable to set ownership of file s/sdft/16/2e/tmp_1108.139: Operation not permitted
    2013-05-15T08:52:40-04:00 vob_server(31498): Error: Unable to create container /disk1/vobstrg/cadscript.vbs/s/sdft/16/2e/tmp_1108.139: Operation not permitted
    2013-05-15T08:52:40-04:00 vob_server(31498): Error: unable to set ownership of file s/sdft/11/35/tmp_1108.140: Operation not permitted

Cause

  • The group that owns the VOB exists on UNIX or Linux, but it does not exist on Microsoft Windows.

    Nobody (or -2) reported as the group owner on the VOB is preventing the vob_server process from setting the group ownership on the data storage container, /testvob.vbs/s/sdft/1a.

  • The VOB has NOBODY as an additional group, and the element being checked out has ownership set to that additional group.

Resolving The Problem

You will need to do one or more of the following:

  • Use protectvob to set the VOB group ownership to a group on UNIX (or Linux) that has an identical group on Windows:

    cleartool protectvob -chgrp <group_name> \\Hostname\share\MyVOB.vbs

    Review the ClearCase Command Reference Guide on the topic of protectvob (cleartool man protectvob) for more information.

  • Create a group on Windows that matches the current VOB group owner on UNIX or Linux.

    Consult your system administrator or operating system manuals for assistance.

    Note: The VOB's group owner does not have to be the same as the user's primary group.

  • Restart ClearCase

[{"Product":{"code":"SSSH27","label":"Rational ClearCase"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Interop","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF015","label":"IRIX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"7.0;7.0.1;7.1;7.1.1;7.1.2;8.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}},{"Product":{"code":"SSSH27","label":"Rational ClearCase"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Interop: CCFS","Platform":[{"code":"","label":""}],"Version":"","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
16 June 2018

UID

swg21147316

Page Feedback