![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: MOdule load time... Topic Summary: Created On: 20-Feb-2004 19:13 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() Answer: we migrated to Doors 7 last weekend. I personally tested doing a beta migration with and without open/save/close -ing modules in Doors 6 before Doors 7 and it does provide a significant improvement. it doesnt need to be the telelogic script, just open exclusive, save and close. Dont display modules else it will take forever. I also noticed that modules setup for shareable have a longer loadtime. I also noticed that some views have been corrupted in some way that it takes them a really long time to load in DOors 7 | |
![]() |
|
Greetings!
After migrating to DOORS 7 from 5.2, we experienced a significant increase in module load times. After many phone calls with Telelogic Support, I received a call from a representative who stated that I should delete all 'FontInfo.dtc' files from the data directory. That these files were carried over from the legacy versions and are not required in V7. It was suggested that I search the data directory for 'FontInfo.dtc', highlight all of the located files, and delete. I was wondering if anyone else has gone through this procedure and what effects, if any, resulted. Also, could not find any documented reference to 'FontInfo.dtc' files and their use. Is there any? Any information will be greatly appreciated. Thanks! -=[ Bob Padilla ]=- Ciena Corpoartion rpadilla@ciena.com |
|
![]() |
|
![]() |
|
Haven't tried it yet, but I'd be interested in the results, our support team are busy counting how many FontInfo.dtc files there are in our Database :-)
------------------------- Graham Stradling, Alcatel-Lucent. |
|
![]() |
|
![]() |
|
Checked our database, we have around 1500 of these files, asked Doors support for confimation that this was a recommended procedure, the response is below :-
"In certain circumstances we suggested this procedure for DOORS 6 to resolve data issues. However this issue was resolved in DOORS 7 and we strongly suggest that you do not delete these files as it may invalidate your data" Steve Ham Application Support Lucent Technologies |
|
![]() |
|
![]() |
|
In a 5.2 to 7 migration I was told to touch the database with Doors 6 first. Open all modules in 6, save and close. This made an improvement over not opening, saving and closing before going to 7.
|
|
![]() |
|
![]() |
|
There's a "ModuleMigrator" script in the Support page to finish modifying the v5 modules into v6 format. It takes a while but its MUCH better than doing it manually.
- Louie |
|
![]() |
|
![]() |
|
I was told, and it is in the documentation, that it is not necessary to open each module in DOORS 6 first if the database is being migrated immediately to DOORS 7.
Alec |
|
![]() |
|
![]() |
|
And I was told TODAY, that the module migrator must be run when going from 5.2 to 7. I know this does not agree with the installation instructions.
------------------------- Wayne Sanders-Unrein Honeywell Aero Electronics Olathe, KS, USA |
|
![]() |
|
![]() |
|
We migrated from 5.2 to 7 yesterday. It went well, but I would like to contribute our experience to this thread regarding saving the modules to complete migration.
Despite repeatedly asking Telelogic (Support desk, Telelogic France, Telelogic consultants) if it was necessary, they said no, the procedure is simple: copy the 5.2 database to the new location, make your D6 point to this location, launch DOORS6 as Admin, and close down. Then make D7 point to the same database. The database is then migrated. We did this procedure, and when first launching a module, it was immediately clear that loading time was much worse. I checked the forum and found the thread on "module migrator". We then saved each module in DOORS7, which dramatically improved the loading times. Also the traffic profile (between client and server) changed. Before saving, there were high throughput rates (irregular, sometimes exceeding 1MB/s), mainly dowloading to the client. After the save, the profile returned to a situation more or less as with 5.2 (with faster loading times. Our conlusion: the saving of each module should be part of the migration procedure. ------------------------- Pieter de Waard www.nhindustries.com |
|
![]() |
|
![]() |
|
we migrated to Doors 7 last weekend. I personally tested doing a beta migration with and without open/save/close -ing modules in Doors 6 before Doors 7 and it does provide a significant improvement. it doesnt need to be the telelogic script, just open exclusive, save and close. Dont display modules else it will take forever.
I also noticed that modules setup for shareable have a longer loadtime. I also noticed that some views have been corrupted in some way that it takes them a really long time to load in DOors 7 |
|
![]() |
Telelogic DOORS
» Administration
»
MOdule load time...
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.