It's all about the answers!

Ask a question

[closed] RTC-CC synchronization fails "Unable to find replica in registry"


Simon Eickel (1.1k65056) | asked Oct 19 '12, 8:51 a.m.
closed Sep 16 '13, 1:08 a.m.
Hi everybody,

I'm facing a new problem with the RTC CC synchronizer.
When I try to synchronize a Componant from RTC to CC I'm getting this error message in the build result:

Problem running 'synchronizeStream':
Synchronization blocked by error:
javax.wvcm.WvcmException: CRRTC4023W The root at "Pathname|/workspace/_g0cLwBnmEeKAl7bYR3ursA/SCM" could not be transferred.
The synchronizer was not able to complete the requested operation
Fix any errors reported in the rest of the log file.
javax.wvcm.WvcmException: CRRTC4061E: The synchronization process cannot be completed. The "cleartool" command completed with a non-zero status or error message:
 
cleartool describe -short oid:8dd06fcb.177d11e2.9d69.00:50:56:a8:00:78@vobuuid:8d406f37.177d11e2.9d69.00:50:56:a8:00:78

cleartool: Error: Unable to find replica in registry for VOB with object ID:"8d406f37.177d11e2.9d69.00:50:56:a8:00:78"
cleartool: Error: Unable to locate versioned object base with object id: "8d406f37.177d11e2.9d69.00:50:56:a8:00:78".

current working directory: M:\DO_NOT_USE_rtc_sync
command result status: 1
command duration: 52 ms
process environment:

Build failed. Exit value was 3.

The strange thing on this?
It's true - this VOB uuid does not exists - but I don't know why he trys this ID. The VOB which he should use (adjusted in the Synch Stream Properties) has a different UUID.

Any idea how to get this error solved?

Greetings,
Simon

Comments
Simon Eickel commented Oct 19 '12, 10:05 a.m. | edited Oct 22 '12, 11:41 a.m.

build log:
2012-10-19 14:35:55 [Jazz build engine]
2012-10-19 14:35:55 [Jazz build engine] Substituted the following configuration element property variables:
2012-10-19 14:35:55 [Jazz build engine]     com.ibm.team.build.cmdline : com.ibm.team.build.cmdline.arguments = --config "${configDir}" synchronizeStream --location "Stream|URI:itemOid/com.ibm.team.scm.Workspace/_g0cLwBnmEeKAl7bYR3ursA" --repository-uri "${repositoryAddress}" --username "${userId}" --passwordFile "${passwordFile}" --propertiesFile "sync_via_build.properties"    -->   com.ibm.team.build.cmdline.arguments = --config "${configDir}" synchronizeStream --location "Stream|URI:itemOid/com.ibm.team.scm.Workspace/_g0cLwBnmEeKAl7bYR3ursA" --repository-uri "${repositoryAddress}" --username "ccadm02" --passwordFile "${passwordFile}" --propertiesFile "sync_via_build.properties"
2012-10-19 14:35:55 [Jazz build engine]     com.ibm.team.build.cmdline : com.ibm.team.build.cmdline.arguments = --config "${configDir}" synchronizeStream --location "Stream|URI:itemOid/com.ibm.team.scm.Workspace/_g0cLwBnmEeKAl7bYR3ursA" --repository-uri "${repositoryAddress}" --username "ccadm02" --passwordFile "${passwordFile}" --propertiesFile "sync_via_build.properties"    -->   com.ibm.team.build.cmdline.arguments = --config "${configDir}" synchronizeStream --location "Stream|URI:itemOid/com.ibm.team.scm.Workspace/_g0cLwBnmEeKAl7bYR3ursA" --repository-uri "https://rtcmu.rsint.net:9443/ccm/" --username "ccadm02" --passwordFile "${passwordFile}" --propertiesFile "sync_via_build.properties"
2012-10-19 14:35:55 [Jazz build engine]     com.ibm.team.build.cmdline : com.ibm.team.build.cmdline.arguments = --config "${configDir}" synchronizeStream --location "Stream|URI:itemOid/com.ibm.team.scm.Workspace/_g0cLwBnmEeKAl7bYR3ursA" --repository-uri "https://rtcmu.rsint.net:9443/ccm/" --username "ccadm02" --passwordFile "${passwordFile}" --propertiesFile "sync_via_build.properties"    -->   com.ibm.team.build.cmdline.arguments = --config "C:/Users/ccadm02/ClearCaseSynchronizer/_g0cLwBnmEeKAl7bYR3ursA.synchronizer" synchronizeStream --location "Stream|URI:itemOid/com.ibm.team.scm.Workspace/_g0cLwBnmEeKAl7bYR3ursA" --repository-uri "https://rtcmu.rsint.net:9443/ccm/" --username "ccadm02" --passwordFile "${passwordFile}" --propertiesFile "sync_via_build.properties"
2012-10-19 14:35:55 [Jazz build engine]     com.ibm.team.build.cmdline : com.ibm.team.build.cmdline.arguments = --config "C:/Users/ccadm02/ClearCaseSynchronizer/_g0cLwBnmEeKAl7bYR3ursA.synchronizer" synchronizeStream --location "Stream|URI:itemOid/com.ibm.team.scm.Workspace/_g0cLwBnmEeKAl7bYR3ursA" --repository-uri "https://rtcmu.rsint.net:9443/ccm/" --username "ccadm02" --passwordFile "${passwordFile}" --propertiesFile "sync_via_build.properties"    -->   com.ibm.team.build.cmdline.arguments = --config "C:/Users/ccadm02/ClearCaseSynchronizer/_g0cLwBnmEeKAl7bYR3ursA.synchronizer" synchronizeStream --location "Stream|URI:itemOid/com.ibm.team.scm.Workspace/_g0cLwBnmEeKAl7bYR3ursA" --repository-uri "https://rtcmu.rsint.net:9443/ccm/" --username "ccadm02" --passwordFile "C:/Users/ccadm02/ClearCaseSynchronizer/_g0cLwBnmEeKAl7bYR3ursA.synchronizer/ccadm02.cred.txt" --propertiesFile "sync_via_build.properties"
2012-10-19 14:35:55 [Jazz build engine]
2012-10-19 14:35:55 [Jazz build engine] running on host: MU716718
2012-10-19 14:35:55 [Jazz build engine] Should build occur?
2012-10-19 14:35:55 [Jazz build engine] Yes: Always build a user initiated request.
2012-10-19 14:35:55 [Jazz build engine] Invoking build participant "com.ibm.team.build.cmdline"
synchronizer version number "3.0.100.v20120430_0235"
WARNING: Current runtime locale "en_US" does not match stream's declared locale "en_US_US".
ClearCase version 7.1.2.1 (Fri Dec 17 17:22:14 EST 2010) (7.1.2.01.00_2010D.FCS)
ClearCase version 7.1.2.2 (Tue Mar 29 16:47:51 EST 2011) (7.1.2.02.00_2011A.FCS)
ClearCase version 7.1.2.3 (Thu Jun 23 22:31:05 EDT 2011) (7.1.2.03.00_2011B.FCS)
ClearCase version 7.1.2.4 (Fri Sep 09 23:31:19 EDT 2011) (7.1.2.04.00_2011C.FCS)
ClearCase version 7.1.2.5 (Wed Nov 30 03:31:03 EST 2011) (7.1.2.05.00_2011D.D111129)
ClearCase version 7.1.2.6 (Wed Mar 28 22:31:08 EDT 2012) (7.1.2.06.00_2012A.D120328)
@(#) MVFS version 7.1.2.6 (Wed Mar 21 00:28:00 2012)
cleartool                         7.1.2.6 (Wed Mar 21 00:50:53 2012)
db_server                         7.1.2.6 (Wed Mar 21 02:05:43 2012)
VOB database schema version: 54
Starting operation: export
WARNING: Current runtime locale "en_US" does not match stream's declared locale "en_US_US".
Scanning for folders whose member count exceeds 1000
Processed activity "Error while trying to transfer: Pathname|/workspace/_g0cLwBnmEeKAl7bYR3ursA/SCM
    Reason Code: forbidden
    Reason: CRRTC4023W The root at "Pathname|/workspace/_g0cLwBnmEeKAl7bYR3ursA/SCM" could not be transferred.
The synchronizer was not able to complete the requested operation
Fix any errors reported in the rest of the log file. " in 2744 millisecond(s)
Jazz:
Number of files created = 0
Number of files updated = 0
Number of folders created = 0
Number of folders updated = 0
Number of symbolic links created = 0
ClearCase:
Number of files created = 0
Number of files updated = 0
Number of folders created = 0
Number of folders updated = 0
Number of symbolic links created = 0


Problem running 'synchronizeStream':
Synchronization blocked by error:
javax.wvcm.WvcmException: CRRTC4023W The root at "Pathname|/workspace/_g0cLwBnmEeKAl7bYR3ursA/SCM" could not be transferred.
The synchronizer was not able to complete the requested operation
Fix any errors reported in the rest of the log file.
javax.wvcm.WvcmException: CRRTC4061E: The synchronization process cannot be completed. The "cleartool" command completed with a non-zero status or error message:
 
cleartool describe -short oid:8dd06fcb.177d11e2.9d69.00:50:56:a8:00:78@vobuuid:8d406f37.177d11e2.9d69.00:50:56:a8:00:78

cleartool: Error: Unable to find replica in registry for VOB with object ID:"8d406f37.177d11e2.9d69.00:50:56:a8:00:78"
cleartool: Error: Unable to locate versioned object base with object id: "8d406f37.177d11e2.9d69.00:50:56:a8:00:78".

current working directory: M:\DO_NOT_USE_rtc_sync
command result status: 1
command duration: 52 ms
process environment:

Build failed. Exit value was 3.


Build Stacktrace:
javax.wvcm.WvcmException: CRRTC4023W The root at "Pathname|/workspace/_g0cLwBnmEeKAl7bYR3ursA/SCM" could not be transferred.
The synchronizer was not able to complete the requested operation
Fix any errors reported in the rest of the log file.
    at com.ibm.rational.wvcm.interop.InteropStream.addCloneRoot(InteropStream.java:3572)
    at com.ibm.rational.wvcm.interop.InteropStream.tryAddCloneRoots(InteropStream.java:3648)
    at com.ibm.rational.wvcm.interop.InteropStream.addCloneRoots(InteropStream.java:3683)
    at com.ibm.rational.wvcm.interop.InteropStream.doOperation(InteropStream.java:4761)
    at com.ibm.team.connector.scm.operations.ConnectorOps.synchronizeStream(ConnectorOps.java:239)
    at com.ibm.team.connector.scm.cli.AbstractCcConnectorSubCommand.synchronizeStream(AbstractCcConnectorSubCommand.java:266)
    at com.ibm.team.connector.scm.cli.SyncSubcommand.synchronizeStream(SyncSubcommand.java:113)
    at com.ibm.team.connector.scm.cli.SyncSubcommand.run(SyncSubcommand.java:71)
    at com.ibm.team.filesystem.cli.core.internal.SubcommandLauncher.run(SubcommandLauncher.java:673)
    at com.ibm.team.filesystem.cli.core.internal.SubcommandLauncher.doStart(SubcommandLauncher.java:402)
    at com.ibm.team.filesystem.cli.core.internal.SubcommandLauncher.run(SubcommandLauncher.java:179)
    at com.ibm.team.filesystem.cli.core.internal.Application.start(Application.java:45)
    at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
    at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
    at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:600)
    at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:620)
    at org.eclipse.equinox.launcher.Main.basicRun(Main.java:575)
    at org.eclipse.equinox.launcher.Main.run(Main.java:1408)
Caused by: javax.wvcm.WvcmException: CRRTC4061E: The synchronization process cannot be completed. The "cleartool" command completed with a non-zero status or error message:
 
cleartool describe -short oid:8dd06fcb.177d11e2.9d69.00:50:56:a8:00:78@vobuuid:8d406f37.177d11e2.9d69.00:50:56:a8:00:78

cleartool: Error: Unable to find replica in registry for VOB with object ID:"8d406f37.177d11e2.9d69.00:50:56:a8:00:78"
cleartool: Error: Unable to locate versioned object base with object id: "8d406f37.177d11e2.9d69.00:50:56:a8:00:78".

current working directory: M:\DO_NOT_USE_rtc_sync
command result status: 1
command duration: 52 ms
process environment:

    at com.ibm.rational.wvcm.ct.CommandResult.computeOperationFailedException(CommandResult.java:136)
    at com.ibm.rational.wvcm.ct.CommandResult.assertSuccess(CommandResult.java:108)
    at com.ibm.rational.wvcm.ct.CommandProvider.execute(CommandProvider.java:213)
    at com.ibm.rational.wvcm.ct.CCaseLib.describeShort(CCaseLib.java:1376)
    at com.ibm.rational.wvcm.ct.CCaseLib.describeShort(CCaseLib.java:1401)
    at com.ibm.rational.wvcm.ct.CCaseLib.gpath(CCaseLib.java:2733)
    at com.ibm.rational.wvcm.ct.CCaseLib.gpath(CCaseLib.java:2725)
    at com.ibm.rational.wvcm.ct.CTElement.lookupMyControllableResourceLoc(CTElement.java:137)
    at com.ibm.rational.wvcm.ct.CTProvider.doFindCRInView(CTProvider.java:1523)
    at com.ibm.rational.wvcm.ct.CTProvider.doFind(CTProvider.java:799)
    at com.ibm.rational.wvcm.ri.impl.WvcmServiceConverter.doFind(WvcmServiceConverter.java:501)
    at com.ibm.rational.wvcm.ri.impl.ResourceImpl.doFind(ResourceImpl.java:560)
    at com.ibm.rational.wvcm.interop.InteropStream.doFindCRInWorkspace(InteropStream.java:2111)
    at com.ibm.rational.wvcm.interop.InteropStream.createClone(InteropStream.java:3310)
    at com.ibm.rational.wvcm.interop.InteropStream.addCloneRoot(InteropStream.java:3546)
    ... 23 more

sync properties:
Jazz properties:
com.ibm.rational.wvcm.HAS_CLONE_INFO: true
com.ibm.rational.wvcm.LOG_MINIMUM_DURATION: 300000
com.ibm.rational.wvcm.VERSION_KNOWS_PARENT: true
com.ibm.team.connector.scm.BUILD_DEF_LOC_STR: itemOid/com.ibm.team.build.BuildDefinition/_hJSaQBnmEeKeYe8KubJT9w
com.ibm.team.connector.scm.BUILD_ENGINE_NAME: rtc_sync.synchronizer
com.ibm.team.connector.scm.BUILD_ENGINE_SLEEP_TIME: 120
com.ibm.team.connector.scm.BUILD_KIND: CLI
com.ibm.team.connector.scm.BUILD_RESULT_LOC_STR: itemOid/com.ibm.team.build.BuildResult/_duDiIRnpEeKAl7bYR3ursA
com.ibm.team.connector.scm.CLI_PATH: eclipse\ccc
com.ibm.team.connector.scm.DEFER_CONTENT_OPS: 300000
com.ibm.team.connector.scm.INSTALL_LOCATION: C:\Program Files (x86)\IBM\ClearCaseSynchronizer\ccctools
com.ibm.team.connector.scm.MAX_CHANGE_SET_SIZE: 1500
com.ibm.team.connector.scm.MAX_NUM_AUTO_COMMIT_ENTRIES: 0
com.ibm.team.connector.scm.MAX_NUM_BATCH_ENTRIES: 5000
com.ibm.team.connector.scm.MAX_NUM_QUERY_ENTRIES: 5000
com.ibm.team.connector.scm.POST_SYNC_OPERATION_PATH:
com.ibm.team.connector.scm.PRE_SYNC_OPERATION_PATH:
com.ibm.team.connector.scm.PROCESS_VISUAL_STUDIO_FILES:
com.ibm.team.connector.scm.REPOSITORY_ROOT_UUID: _Yi_pwQquEeG_tK8r4JP2BA
com.ibm.team.connector.scm.REPOSITORY_URI: https://rtcmu.rsint.net:9443/ccm/
com.ibm.team.connector.scm.SCRIPT_LOCATION_PREFIX: C:\Users\ccadm02\ClearCaseSynchronizer
com.ibm.team.connector.scm.STREAM_SCRIPT_DIR: C:\Users\ccadm02\ClearCaseSynchronizer_g0cLwBnmEeKAl7bYR3ursA.synchronizer
com.ibm.team.connector.scm.SYMLINKS_SUPPORTED: true
com.ibm.team.connector.scm.SYNC_HOST: MU716718
com.ibm.team.connector.scm.SYNC_HOST_IS_WINDOWS: true
com.ibm.team.connector.scm.SYNC_USER_ID: ccadm02
com.ibm.team.connector.scm.SYNC_VIA_BUILD: true
com.ibm.team.connector.scm.TEAM_AREA_PATH: itemOid/com.ibm.team.process.TeamArea/_7-wnULVeEeGro57EnIuqjA
com.ibm.team.connector.scm.WORKITEM_TEMPLATE_ID: 3811
com.ibm.team.interop.DESYNC:
com.ibm.team.interop.DISABLE_HASHING_FOR_CONTENT_COMPARE:
com.ibm.team.interop.FORCE_EXCEPTION:
com.ibm.team.interop.IGNORE_TASK_CREATION_FAILURE: false
com.ibm.team.interop.MAXIMUM_MEMBER_COUNT: 1000
com.ibm.team.interop.MERGE_WORKSPACE: Workspace|URI:itemOid/com.ibm.team.scm.Workspace/_g62VoBnmEeKAl7bYR3ursA
com.ibm.team.interop.RESOURCES_PER_CLONE_LINK_UPDATE: 1000
com.ibm.team.interop.RESTARTABLE_IMPORTS: true
ClearCase properties:
INSTALL_LOCATION: C:\Program Files (x86)\IBM\ClearCaseSynchronizer\ccctools
STREAM_SCRIPT_DIR: C:\Users\ccadm02\ClearCaseSynchronizer_g0cLwBnmEeKAl7bYR3ursA.synchronizer
VERSION_STRING: ClearCase version 7.1.2.1 (Fri Dec 17 17:22:14 EST 2010) (7.1.2.01.00_2010D.FCS)
ClearCase version 7.1.2.2 (Tue Mar 29 16:47:51 EST 2011) (7.1.2.02.00_2011A.FCS)
ClearCase version 7.1.2.3 (Thu Jun 23 22:31:05 EDT 2011) (7.1.2.03.00_2011B.FCS)
ClearCase version 7.1.2.4 (Fri Sep 09 23:31:19 EDT 2011) (7.1.2.04.00_2011C.FCS)
ClearCase version 7.1.2.5 (Wed Nov 30 03:31:03 EST 2011) (7.1.2.05.00_2011D.D111129)
ClearCase version 7.1.2.6 (Wed Mar 28 22:31:08 EDT 2012) (7.1.2.06.00_2012A.D120328)
@(#) MVFS version 7.1.2.6 (Wed Mar 21 00:28:00 2012)
cleartool                         7.1.2.6 (Wed Mar 21 00:50:53 2012)
db_server                         7.1.2.6 (Wed Mar 21 02:05:43 2012)
VOB database schema version: 54
com.ibm.rational.wvcm.LOG_MINIMUM_DURATION: 300000
com.ibm.rational.wvcm.WORKSPACE_LOCATION: BASE_CC_VIEW|DO_NOT_USE_rtc_sync||BRTYPE|brtype:rtc_sync@\rtc_sync_play
com.ibm.rational.wvcm.ct.CHECKIN_COMMENT:
com.ibm.rational.wvcm.ct.CLEARCASE_LOGIN_NAME: ccadm02
com.ibm.rational.wvcm.ct.CLEARCASE_TRACE_TRIGGERS: false
com.ibm.rational.wvcm.ct.CLEARQUEST_DBSET_NAME: sample_schema_repo
com.ibm.rational.wvcm.ct.CLEARQUEST_LOGIN_NAME: admin
com.ibm.rational.wvcm.ct.CLEARQUEST_UCM_RECORD_ACTION:
com.ibm.rational.wvcm.ct.CLEARQUEST_USERDB_NAME: SAMPL
com.ibm.rational.wvcm.ct.COMPONENT_VOB_TAG:
com.ibm.rational.wvcm.ct.DUMP_ENV: false
com.ibm.rational.wvcm.ct.GPATH: \MU716718\ccstg_c
com.ibm.rational.wvcm.ct.HOST: MU716718
com.ibm.rational.wvcm.ct.HPATH: \MU716718\ccstg_c
com.ibm.rational.wvcm.ct.LOCALE: en_US_US
com.ibm.rational.wvcm.ct.MAX_CT_CMD_LEN: 16384
com.ibm.rational.wvcm.ct.PROVIDER_MAX_CACHE_SIZE: 10000
com.ibm.rational.wvcm.ct.PVOB_TAG:
com.ibm.rational.wvcm.ct.REPORT_ACTIVITY_MORE_THAN: 60000
com.ibm.rational.wvcm.ct.STG_LOC: \MU716718\ccstg_c
com.ibm.rational.wvcm.ct.SYNC_CC_VERSION_COMMENTS: false
com.ibm.rational.wvcm.ct.TRIPLE_SET: false
com.ibm.rational.wvcm.ct.VIEW_TAG: DO_NOT_USE_rtc_sync
com.ibm.team.connector.scm.CHARACTER_SET: windows-1252
com.ibm.team.connector.scm.LINE_DELIMITER: CRLF
com.ibm.team.connector.scm.LINE_DELIMITER_WORKSPACE: PLATFORM
com.ibm.team.connector.scm.cc.ide.ui.IS_UCM_STREAM: false
com.ibm.team.interop.FORCE_EXCEPTION:
com.ibm.team.interop.IGNORE_TASK_CREATION_FAILURE: false
com.ibm.team.interop.IMPORT_ONLY: false
com.ibm.team.interop.OTHER_STREAM_LOCATION: BRANCH|brtype:rtc_sync@\rtc_sync_play||BRTYPE|brtype:rtc_sync@\rtc_sync_play
com.ibm.team.interop.OTHER_WORKSPACE_NAME:


Karl Weinert commented Oct 19 '12, 11:46 a.m.
JAZZ DEVELOPER

I have not figured out where the oid is coming from just yet but I was able to repro your error by setting up the sync stream then unregistering and untagging the VOB I had used during the setup.
You can find some information about the VOB from the  "ClearCase synchronized Stream" view.
Right click the Synchronized stream you are have having difficulty with, choose properties.
Check the ClearCase provider properties to see if it shows the correct VOB information.
 You can try to change the vob there but I had some difficulty since changing it seemed to want to oid of the missing vob.


Simon Eickel commented Oct 19 '12, 3:15 p.m.

Hi Karl,

yes, that would meet my testing, too.
I had setup synchronisation with a special VOB. Deleted that VOB and chooses another VOB. And since then I have this trouble. But the strange thing is ... even with a completly new repository and a completly new Stream - the problem still exists ...


Simon Eickel commented Oct 22 '12, 9:14 a.m.

Interesting thing on this:
I have a RTC test environment which is using the same CC VOBs for synchronization. There everything is fine - so this trouble has to be anywhere inside the RTC configuration - maybe any client/server configuration which is saved anywhere?

I already tried using a different workspace but with no effect.


Karl Weinert commented Oct 22 '12, 10:44 a.m.
JAZZ DEVELOPER

Hi Simon,

I am researching where this configuration is set.  As far as I can tell the configuration is stored in the database but I have not been able to find the oid of the VOB there. I'll keep looking but it might be time to open a PMR. It is definitely odd that a new stream shows the same problem. That was going to be my next suggestion since that did the trick in my testing


Geoffrey Clemm commented Oct 22 '12, 11:52 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
The fact that this runs in your RTC test environment should help us track down what is going on (by comparing how you have your RTC test environment configred, compared to how you have your RTC non-test environment configured).

A couple of questions:
- When you are configuring your synchronization stream, do you always run the RTC client on the same machine as your synchronization host (i.e. the machine that is running the sync engine process)?  

  • When you created your sync stream in the test environment, were you synchronizing with the same ClearCase branch as in the non-test environment?

Simon Eickel commented Oct 22 '12, 3:15 p.m.

Hi Geoff,
first thing: yes I used the same workstation to recreate the sync for the test environment and yes I used the same branch / VOB in CC for this test.
Yes, the RTC client is running on the same workstation where the sync engine process is running.

The two server (prod RTC and test RTC) are configured the same way, so everything should be equal. The client is the same and the branch / VOB is the same. In the Test environment it's running and in the prod environment it sneers at this VOB-uuid where I don't know where it's coming from. Even when using another Stream.


Geoffrey Clemm commented Oct 22 '12, 5:48 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

OK, we may be getting close ... is the name of the new VOB you are using by any chance the same as the name of a Jazz component that already exists in your RTC repository?   If so, can you rename that RTC component (at least for now),  try to create a new sync stream?


Simon Eickel commented Oct 23 '12, 5:16 a.m.

Hi Geoff,
the name of the new VOB is not the name of the component. The name of the old VOB was the same name as the component as the default sync between RTC/CC needs the VOB name as the same value as the component.

The new VOB is named different but has a sub-sub-folder which is named the same way as the component because my testing made me think that the folder (using the attribute for subfolder) needs to be the same name as the component.

But I can try to rename the RTC component anyway. My first testing will be to test the synchronization on another workstation again - maybe this VOB uuid is stored anywhere on the workstation and that's why it's remembers over stream borders and different workspaces...


Karl Weinert commented Oct 23 '12, 9:07 a.m.
JAZZ DEVELOPER

Simon are you using the original component?  Here's some info I got from the developer that works on this code.
Jazz SCM's component is mapped to UCM component ( or baseCC VOB root ), and Jazz SCM's file or a folder is mapped to a CC element.
It would fail in a new stream if you try to add the Jazz SCM component you used to sync to the stream and sync-out the component to ClearCase.


Simon Eickel commented Oct 23 '12, 9:30 a.m.

Hi Karl,
I'm not sure if I really understand the meaning.
I mapped the same RTC component which I synced to a baseCC Vob root to a different subfolder of another VOB.
Means same RTC component but different CC element.
That worked on both systems (prod and test) till I deleted the VOB and used another VOB.

What do you mean with "original component"?


Karl Weinert commented Oct 23 '12, 11:30 a.m.
JAZZ DEVELOPER

Simon are you able to open a PMR for this issue?


Simon Eickel commented Oct 24 '12, 1:05 a.m.

Hi Karl,
PMR is open since yesterday morning (German time).
PMR 93256,999,724

Krzysztof Kazmierczyk wrote me that he already internally escalated it to "Karl" - I thought that was you.


Simon Eickel commented Oct 24 '12, 2:42 a.m.

Hi Karl,
just one more information:
Tried this sync from another workstation and there I get the same error. So this VOB uuid is not stored on the workstation - it's stored anywhere else (maybe database like Geoff said)


Simon Eickel commented Oct 24 '12, 4:31 a.m.

one more question:
the build engine runs with this arguments:
--config "${configDir}" synchronizeStream --location "Stream|URI:itemOid/com.ibm.team.scm.Workspace/_g0cLwBnmEeKAl7bYR3ursA" --repository-uri "${repositoryAddress}" --username "${userId}" --passwordFile "${passwordFile}" --propertiesFile "sync_via_build.properties"

Maybe in the config of this synch is anything faulty? But where to find? But that would not explain why the synch is blocked ...

Made some other tests:
Synchronizing another Component to the same VOB is working - in the same stream. So... the problem is on the Component i think.


showing 5 of 15 show 10 more comments

The question has been closed for the following reason: "The question is answered, right answer was accepted" by eickel Sep 16 '13, 1:08 a.m.

Accepted answer


permanent link
Simon Eickel (1.1k65056) | answered Nov 08 '12, 4:50 a.m.
Hi there,

this problem is solved now. To give you the information how we solved it (thanks to Karl and IBM) I write this answer (maybe more ppl have this trouble).

There is a possibility to remove all "clones" on a component. Each Element/folder/VOB seems to set a clone on the component.
You can get information about clones on a component using the ClearCase Synchronizer subcommand "clones"


ccc clones -c <component> -r <repository> -u <username> -P <password>

To delete the clones on a component just use the clones command with option -X


ccc clones -c <component> -r <repository> -X -u <username> -P <password>

I got the error message when tried to remove the clones that there are another components with the same name. This I got resolved when renaming the component, removing the clones on the renamed componend and then name it back to the original name.

Note: You need Jazz Administration permission (member of the jazz admin group) to remove the clones.
Geoffrey Clemm selected this answer as the correct answer

One other answer



permanent link
Karl Weinert (2.0k42536) | answered Oct 19 '12, 9:05 a.m.
JAZZ DEVELOPER
edited Oct 19 '12, 9:16 a.m.
This looks like a problem on the ClearCase end
See this Technote for more information on that error.

You can verify by running the failing describe command.
cleartool describe -short  oid:8dd06fcb.177d11e2.9d69.00:50:56:a8:00:78@vobuuid:8d406f37.177d11e2.9d69.00:50:56:a8:00:78

You will need to be in a view and it should be ok to use the one created by RTC to run the describe.

Comments
Simon Eickel commented Oct 19 '12, 9:26 a.m.

Hi Karl,

thanks for your comment.
As I described the VOB does not exist. The cleartool command fails because there is no VOB with this ID. But the strange thing is I don't know why the synchronizer is searching for this ID because the only VOB provided inside the synchronizer has another ID.

I created some more sync trys with other Streams but everytime he fails on this.


Karl Weinert commented Oct 19 '12, 9:40 a.m.
JAZZ DEVELOPER

My mistake, I didn't compare the oid of the command with the oid in the error.
Can you dump the vob that it is supposed to be using.  cleartool dump vob:\vob-tag
Paste in the oids from that output.
Is there anything more information in the  build logs?


Simon Eickel commented Oct 19 '12, 10:03 a.m.

Hi Karl,
no problem.
OID of the VOB which is stored inside the config of the synchronizer is:
oid=52a99986.19e511e2.8d77.00:50:56:a8:00:78

This is the whole build log is written in the next answer because it's too big:


Simon Eickel commented Oct 19 '12, 10:05 a.m.

That you see that the oid is the one from the VOB out of the properties:

rbroot@ccmu01# cleartool dump vob:/vobs/rtc_sync_play

/vobs/rtc_sync_play
oid=52a99986.19e511e2.8d77.00:50:56:a8:00:78  dbid=1 (0x1)
mtype=versioned object base


Paul Komar commented Nov 07 '12, 5:26 p.m.

Simon, have you tried to remove the existing sync roots?

I can see from the stack trace that the sync code is trying to add a root in the removed VOB.