![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: v81 to v83 Upgrade Topic Summary: Created On: 13-Aug-2008 15:44 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
We are figuring to upgrade from v8.1 to v8.3. Do I understand the reality and what needs to be done correctly?
o We already have the v8.2 licensing installed. o We shut down the server, install v8.3, redefine the DOORS service to point to v8.3. o Install v8.3 on the clients. o There is no 'migration' of the data needed. o v8.1 clients can access a v8.3 server without incident, although its better to upgrade all the clients. o v8.3 clients can access a v8.1 server without incident. Anything else I need to know? - Louie |
|
![]() |
|
![]() |
|
Louie,
Just an FYI, there is a known issue that is not documented in their "Known Issues" with 8.3 that may effect your decision to upgrade. If you do not have an integration with Synergy Change, users have experienced a DXL error when creating a baseline. The baselines are created, but in some instances DOORS will lock up and the process has to be terminated through the Task Manager. The issue seems to be intermittent, it took me over 50 baselines to reproduce the error when it was first reported to me, though I have users that create a lot baselines and see the problem 4 to 5 times a day. I've started noticing issues where the user had other modules opened when they baselined and DOORS locked up. Becuase the user did not save the other module, the objects they created were "purged". The issue with this is if these "purged" objects contained links to other objects, the target object now has a hung link reference that can't be removed without sending the inlinks.dtc file for the module to Telelogic. I've been fighting with Telelogic for over a month and half now to release a patch for this and I continually told to upgrade to 9.0 as it is fixed there. The funny thing is they don't know how they fixed it. From Telelogic Support: Scott, the link issue could be still regarding the defect. The defect about creating a baseline we found in DOORS 8.3 is resolved in DOORS 9.0 as I had mentioned earlier. The exact root cause was not determined by the developers. I heard from the developers that the code was re-designed in DOORS 9.0, and that resolved the baseline issue in DOORS 9.0. My suggestion to you would be to hold off until they release a patch or go straight to 9.0. ------------------------- Scott Boisvert Engineering Tools Administrator L-3 Communications - Avionics Systems scott.boisvert@l-3com.com |
|
![]() |
|
![]() |
|
Installation of v83 on the server will remove v81 on the server. The v83 MSI removes v81. If you want both then reinstall v81 at a different port.
Installation of v90 on the server will not remove v81, so v81 and v90 will coexist at different ports. Data migration is needed but similar to upgrade from v71 to v81. |
|
![]() |
Telelogic DOORS
» Administration
»
v81 to v83 Upgrade
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.