![]() |
Telelogic SYNERGY (steve huntington) | ![]() |
Topic Title: CR 'status' is not getting replicated after doing a DCM transfer Topic Summary: CR 'status' is not getting replicated after doing a DCM transfer Created On: 19-Nov-2004 07:27 Status: Read Only |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() Answer: Are you sure your CR update has been received? It could have been skipped. Check your log files if you are using CCM45SP2 protocol or the DCM receive notification to see what happened. | |
![]() |
|
Hi,
I transfer CRs from one database to another using DCS(Distributed Change Synergy). The change requests status are modified in the source database. After a DCM is done at source, the Change Request's status remain the same at the destination database as it existed before DCM receive was done. For example, at the destination database, if a CR status was in "assigned" state. The same CR status is changed at source database to "concluded" state and a DCM is done. This CR still remains in "assigned" state even after a DCM receive is done at the destination database. What could be the problem ??? |
|
![]() |
|
![]() |
|
Are you sure your CR update has been received?
It could have been skipped. Check your log files if you are using CCM45SP2 protocol or the DCM receive notification to see what happened. |
|
![]() |
|
![]() |
|
We are experiencing the same problem exactly. DCM completes successfully, but status is not getting updated. The only way to get over this problem was removing the problem and then DCM it again. However, this solution is unacceptable. Please, advise.
|
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.