It's all about the answers!

Ask a question

clearcase connector: javax.wvcm.WvcmException


Lin Ye (30632611) | asked Jun 10 '10, 4:56 p.m.
Hi,

I got failures when running the synchronization stream:

javax.wvcm.WvcmException: Failure while trying to execute cleartool command:

cleartool describe -fmt %m|%p|%n\n M:/DO_NOT_USE_main_229415ac-2ec6-493a-b63a-df1cc7e4a96c/...

... lots of paths here ...

version|oid:89bc4aee.489a4645.bde4.76:1a:88:f2:bc:73@vobuuid:fff9bba3.ea374602.8cc8.5d:77:26:49:5a:7f|M:/DO_NOT_USE_main_229415ac-2ec6-493a-b63a-df1cc7e4a96c/energy_credit/energy_credit/tags/build-114/static/reports/sql/overlimit.sql@@\main\1
cleartool: Error: Error from VOB database: "\energy_credit".
cleartool: Error: Trouble opening VOB database: "\energy_credit".
cleartool: Error: Error from VOB database: "\energy_credit".
cleartool: Error: Trouble opening VOB database: "\energy_credit".
cleartool: Error: Error from VOB database: "\energy_credit".
cleartool: Error: Trouble opening VOB database: "\energy_credit".

current working directory: M:\DO_NOT_USE_main_229415ac-2ec6-493a-b63a-df1cc7e4a96c
command result status: 0
command duration: 31751 ms
process environment:

at com.ibm.rational.wvcm.ct.CommandResult.assertSuccess(CommandResult.java:86)
at com.ibm.rational.wvcm.ct.CCaseLib.executeBatched(CCaseLib.java:961)
at com.ibm.rational.wvcm.ct.CCaseLib.describeForObjInfo(CCaseLib.java:1255)
at com.ibm.rational.wvcm.ct.CCaseLib.describeForObjInfo(CCaseLib.java:1211)
at com.ibm.rational.wvcm.ct.CCaseObjInfo.getObjInfos(CCaseObjInfo.java:106)
at com.ibm.rational.wvcm.ct.CCaseObjInfo.lookupObjInfos(CCaseObjInfo.java:94)
at com.ibm.rational.wvcm.ct.CTElement.lookupControlledResourceLocs(CTElement.java:281)
at com.ibm.rational.wvcm.ct.CTProvider.doFindCrsInView(CTProvider.java:1479)
at com.ibm.rational.wvcm.ct.CTProvider.doFind(CTProvider.java:1398)
at com.ibm.rational.wvcm.ri.impl.WvcmServiceConverter.doFind(WvcmServiceConverter.java:1395)
at com.ibm.rational.wvcm.ri.impl.ResourceListImpl.doFind(ResourceListImpl.java:74)
at com.ibm.rational.wvcm.interop.InteropStream.doFindCRsInWorkspace(InteropStream.java:1751)
at com.ibm.rational.wvcm.interop.InteropStream.sendoverContent(InteropStream.java:1475)
at com.ibm.rational.wvcm.interop.InteropStream.sendoverChanges(InteropStream.java:1156)
at com.ibm.rational.wvcm.interop.InteropStream.sendoverTree(InteropStream.java:2311)
at com.ibm.rational.wvcm.interop.InteropStream.createClone(InteropStream.java:2787)
at com.ibm.rational.wvcm.interop.InteropStream.internalSetCloneRoot(InteropStream.java:2921)
at com.ibm.rational.wvcm.interop.InteropStream.internalSetCloneRoots(InteropStream.java:3037)
at com.ibm.rational.wvcm.interop.InteropStream.doOperation(InteropStream.java:3932)
at com.ibm.team.connector.scm.operations.ConnectorOps.synchronizeStream(ConnectorOps.java:209)
at com.ibm.team.connector.scm.cli.AbstractCcConnectorSubCommand.synchronizeStream(AbstractCcConnectorSubCommand.java:184)
at com.ibm.team.connector.scm.cli.SyncSubcommand.synchronizeStream(SyncSubcommand.java:112)
at com.ibm.team.connector.scm.cli.SyncSubcommand.run(SyncSubcommand.java:74)
at com.ibm.team.filesystem.cli.core.internal.SubcommandLauncher.run(Unknown Source)
at com.ibm.team.filesystem.cli.core.internal.SubcommandLauncher.doStart(Unknown Source)
at com.ibm.team.filesystem.cli.core.internal.SubcommandLauncher.run(Unknown Source)
at com.ibm.team.filesystem.cli.core.internal.Application.start(Unknown Source)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(Unknown Source)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(Unknown Source)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(Unknown Source)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(Unknown Source)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:618)
at org.eclipse.equinox.launcher.Main.invokeFramework(Unknown Source)
at org.eclipse.equinox.launcher.Main.basicRun(Unknown Source)
at org.eclipse.equinox.launcher.Main.run(Unknown Source)


The synchronization works for the past weeks but from this week I got the failures on 4 sync streams. Anybody knows the reason? Thanks.

Lin

5 answers



permanent link
Lin Ye (30632611) | answered Jun 10 '10, 5:44 p.m.
I ran "cleartool describe" on the vob directly.

We have files which contain spaces in the names, for example "One Off - Swaps.csv". Command "cleartool describe" failed on these files. The error message is "Unable to access "..../One": No such file or directory.

That is different from the error printed in log. Another thing is if the file name cannot contain spaces then how does the initial import succeed on those files.

Any suggestion would be appreciated. Thanks

permanent link
Lin Ye (30632611) | answered Jun 10 '10, 6:16 p.m.
Well I got the error.

After running dbcheck on the vob, I got these errors:

------------------------------------------------------------------------
Processing key file: vob_db.k01(1), total of 852 nodes

Problems at node 607:
* delete chain's next-pointer=0 is out of range

Problems at node 151:
* node is not referenced by either the b-tree or delete chain

Problems at node 168:
* node is not referenced by either the b-tree or delete chain
...

But we never changed anything from clearcase. Our data flow is one way: RTC > CC. So the errors should come from rtc-cc connector. But how and why did this happen...

permanent link
Geoffrey Clemm (30.0k23035) | answered Jun 10 '10, 11:53 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
All the ClearCase Synchronizer does is run a sequence of cleartool
commands. If a cleartool command fails, the CC Synchronizer prints out
the cleartool command that failed (as you indicated in your first note).

If you've got dbcheck errors on your VOB, then you need your CC Admin to
fix that VOB. There's nothing the CC Connector can do if your VOB has
errors.

Cheers,
Geoff

On 6/10/2010 6:22 PM, Raistlin wrote:
Well I got the error.

After running dbcheck on the vob, I got these errors:

------------------------------------------------------------------------
Processing key file: vob_db.k01(1), total of 852 nodes

Problems at node 607:
* delete chain's next-pointer=0 is out of range

Problems at node 151:
* node is not referenced by either the b-tree or delete chain

Problems at node 168:
* node is not referenced by either the b-tree or delete chain
..

But we never changed anything from clearcase. Our data flow is one
way: RTC> CC. So the errors should come from rtc-cc connector.
But how and why did this happen...

permanent link
Geoffrey Clemm (30.0k23035) | answered Jun 10 '10, 11:54 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
If you put quotes around the pathnames with spaces (whatever are the
appropriate quotes for your OS command line tool), you should get the
same errors that the CC Synchronizer was reporting.

Cheers,
Geoff

On 6/10/2010 5:52 PM, Raistlin wrote:
I ran "cleartool describe" on the vob directly.

We have files which contain spaces in the names, for example "One
Off - Swaps.csv". Command "cleartool describe" failed
on these files. The error message is "Unable to access
"..../One": No such file or directory.

That is different from the error printed in log. Another thing is if
the file name cannot contain spaces then how does the initial import
succeed on those files.

Any suggestion would be appreciated. Thanks

permanent link
Lin Ye (30632611) | answered Jun 11 '10, 12:44 a.m.
Hi,

Thank you very much for your reply.

Lin

Your answer


Register or to post your answer.