maximum workspace capacity?

[Lozzip]

Good morning.
I have the following problem:
I have a workspace that weighs more than 2,15 gb ... pro/e nn let me save any changes in that woorkspace.

the local.ddb file weighs 2.1 gb ... the ldbcompact nn file manages to perform compaction but it stops first.

Can you tell me if there is a memory limit for a workspace? ? ?

do you have solutions to this problem? ? ?

Thank you in advance.

alessandro.

 

[cletus]

Hi, you have to delete the local.ddb file.
save all the content of the workspaces (by checking in or exporting provisionally to disk), emptiness and gates.
exit intralink and cancell the file.
when rebooting intralink, the file is automatically recreated.
It's good not to let this file grow too much, usually when it comes to 600-700mb I already realize a slowdown in the rescues.

 

[Lozzip]

nice discomfort

thank you very much for the info.

 

[Lozzip]

I tried, but during check-in, intralink always makes the same mistake:
"an error occurred during writing on the workspace file c:\proe_laborwf3\.proi\local.ddb"

The only thing I have to do is a physical copy of the workspace folder. and then completely empty the .proi folder. but I'm afraid to lose all the changes in progress.

other solutions?

 

[cletus]

writing error on the local.ddb file I don't know what it is due to, I'm sorry but I don't have much knowledge about it.
I do not know therefore if it can help to solve, but regarding the size of the ws you can banally make a purge.
another thing, when I check out a component I use the "link" option and not "local copy", it turns out to be slower in loading server models instead of local, I do not have physical copies of models occupying space in the ws.
the way to copy the contents of the folder is a further security that you should adopt, I never needed to do it though you should not (I see forced to use the conditional) lose changes data.
I don't know.

 

[nicksoft]

I tried, but during check-in, intralink always makes the same mistake:
"an error occurred during writing on the workspace file c:\proe_laborwf3\.proi\local.ddb"

The only thing I have to do is a physical copy of the workspace folder. and then completely empty the .proi folder. but I'm afraid to lose all the changes in progress.

other solutions?

tried to use the export and deletion of the archive as cletus suggested? Obviously you can verify that the exported data is correct before you delete the local archive, if you are afraid to lose the current changes.

 

[Lozzip]

I still tried because I'm afraid to lose everything.
I'll explain.

If I delete .proi, then I collect a workspace, I open the assemblies that interest me from the previously copied folder, and save all in the new workspace. result, I get files that intalink signals with already existing name, nn recognizes the version and location of where it should then checkout.
so chekout impossible.

 

[Lozzip]

I forgot, intralink nn let me do the disc exposure.
the only thing I can race is the copy of the folder from .proi to another place

 

[wired]

Hi.
If you ruined the local db there is little to do. try to see if it makes you create new workspaces, if you, then export items from old ws to new ones and as you check in.
Replace, move, etc the loca db, will not allow you to recover data....

 

[Lozzip]

I can't do anything.
the localddb nn is ruined but has reached the maximum size. so he can no longer index anything. only solution would be the oldbcompact but ankesso nn works for the same reason.

I think I'm...

no one knows how to deceive intralink so that nn appears "existing name", once saved in the workspace the files I previously copied out from .proi?

 

[cletus]

no one knows how to deceive intralink so that nn appears "existing name", once saved in the workspace the files I previously copied out from .proi?

as I said yesterday, copy of the .proi folder, delete ws (from intralink), delete local.ddb. I'd get back intralinks and collect the ws you need.
then check out in the ws of the model, then import from disk the modified version, so it turns out as modified in the status_workspace.
It's a Carthonian job, take it slow, maybe leaving the parts and then assembling them.

 

[Lozzip]

Okay grz of everything.


I'll try.

 

[Lozzip]

I tried but not to do.

the problem is that within the workspace folder, nn there are all the changed details. ..very likely some changes sell only recorded in the localddb. copying the folder as recommended I would lose many changes.

alternative solution, would export to the disk, from intralink, all modified components, and as you said, import them consecutively.
sin that in my case is not possible. ..deduco that anke export, however little, modifies the localddb file, which being to the maximum size, nn allows me to do no operation.

At this point I think I'm dealing with:-(

What do you say?

 

[cletus]

most likely some changes sell only recorded in the localddb.

That sounds weird, though, I noticed something.
if I deliberately edit (e.g.geometric) to a part, this obviously turns out "modified" in the ws and the .prt file I find saved in the folder \.proi\nome_ws. the parts instead not modified I can not find them. Here we go.
working together sometimes happens that some parts are modified, although I voluntarily did not make any changes. had it in the \.pro\nome_ws folder I have no trace of these .prt; It's like they haven't been modified.
so I think that the deliberately modified models are just the ones that are located in the premises, and that then you can copy in a temporary folder.

 

[goodwin]

It's a breakup I know....
Can you tell me if ldbcompact can be launched on windows 7 64 bit machines?
It doesn't work. .
Thank you.

 

[sbaldiserra]

the correct procedure to import data from file system into a ws is as follows:

1 - empty ws creation.
2 - amounts all the files you have on file system.
3 - update all ws files with common space, with check-out command.
4 - re-import files from file system.

the second imports changes the state of the ws in "modified".
it would be more correct to import only items actually bringing a change.

Hi.