![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Archiving a huge project Topic Summary: How do you change the temporary directory Created On: 21-Aug-2006 16:34 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
I am having some trouble archiving a huge project, basically I am running out of space in the temporary area that doors uses to compile the project archive. What I'm trying and failing to do is change the directory DOORS compiles the data in to a directory with enough available space. I have tried the following without success: -
1) specifying the local area with the -f command line switch (no effect) 2) Changing the TMP and TEMP environmental variables to point at an area with more space 3) Changing anything that I can find that mentions the old temp area to the area with more space. Nothing works, the archive procedure still writes to my old temporary area. Anyone have any idea how to solve this one? I suspect I've somehow been nobbled by computer services, but maybe I'm getting paranoid and there's somthing I'm missing! ------------------------- Regards, Richard Good |
|
![]() |
|
![]() |
|
You can get the local data folder executing this DXL command: "print "Perm: " (getenv("LocalData")) "\tCommandLine: " (getenv("DOORSLOCALDATA")) "\n"
The first is the registry value, the 2nd is the value used in the Command Line. When using -f in the command line be sure to double quote the path. Understand that 'more space' means you redirect the area to a different drive. If DOORS installed on your D drive then perhaps redirect it to somewhere on your C drive. Try emptying out your 'Recycle Bin'. - Louie |
|
![]() |
|
![]() |
|
Hi Chris, Hi Louie,
is the archive procedure really done on client side? I think, the archives will be created on server side and then transfered to client, so may be your server needs more temporary space? This is only a guess, but you could have a look at it ![]() Greetings Reik ------------------------- Evosoft GmbH for Siemens Industry Sector Berlin, Germany |
|
![]() |
|
![]() |
|
Thanks for the replies. My understanding of the archive operation (I don't claim to fully understand it, perhaps someone can enlighten me) is that the server compresses the various files for modules and baselines on the server and then sends them to the client machine piece meal, it then zips them up into a dpa it may well do somthing else on the server side at this point, but I think that the sending data from the server type messages towards then end of the process are not strictly accurate. Note that the temporary area seems to be cleared at the end of the operation. Try using the "file monitor" utility from sysinternals to monitor the operation if you don't believe me, assuming that unlike me you haven't been locked out of using such things and assuming there isn't some sort of server setting that alters the archive behaviour to be as you describe! Anyway I can assure you I'm not imagining running out of memory on my computer!
------------------------- Regards, Richard Good |
|
![]() |
|
![]() |
|
On a side note, what is the size of the dpa when you archive your projects? This is a question to all.
The biggest dpa file I ever reached was 3 gigs in size, which included module's baselines. ------------------------- pete.kowalski(at)motorola.com |
|
![]() |
|
![]() |
|
Pete,
The archive in question is 10.5 gigs ------------------------- Regards, Richard Good |
|
![]() |
Telelogic DOORS
» General Discussion
»
Archiving a huge project
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.