Failed SVN dump import with error msg "deferred operation failed"
james sun (1●2●2)
| asked Sep 25 '12, 1:27 p.m.
edited Oct 13 '17, 3:51 p.m. by David Lafreniere (4.8k●7) Hi,
Node-path: XD/releases/6.1.0And, here is the revision 28232 - Node-path: XD/releases/6.1.0Apparently someone removed the main path XD/releases/current then copied the path XD/releases/current back down to XD/releases/current. In the meantime, there is no path XD/releases/current in the svn repository today. I tried to remove both 28232 and 28233 revisions in the dump file, but it caused problem when other revisions references the revision 28233. Any one has an idea/suggestion how to handle this situation? Thanks a lot. James |
Accepted answer
James,
If you look in your Error log view in the RTC Eclipse client, you should find a complete stacktrace for the error. That may reveal more details about what could be wrong. David Lafreniere selected this answer as the correct answer
Comments Michael,
Michael Valenta
commented Sep 27 '12, 8:55 a.m.
| edited Oct 13 '17, 3:52 p.m.
FORUM MODERATOR / JAZZ DEVELOPER
This looks more like a general failure involving DB2 than a specific failure in the importer. What version of DB2 are you using? Are you able to perform standard operations in RTC independently of the importer (e.g. can you check-in file changes, deliver, ect.)? If you attempt to resume the import, do you get the same error?
Hi Michael,
Michael Valenta
commented Sep 29 '12, 6:24 p.m.
| edited Oct 13 '17, 3:53 p.m.
FORUM MODERATOR / JAZZ DEVELOPER
I've never seen that type of DB2/SQL failure during an import. I suggest you log a defect report against RTC/Source Control and provide all the details you have provided in this forum post. Also, please include the stack trace for all the failures.
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.