The dreaded Local.ddb overload issue

[nsfreund]

Pro-Users,

I have hit the wall with the dreaded local.ddb overload. I have some
modified and new components in my workspace that were not checked into
the commonspace. I had an error when trying to check in the changes to
the commonspace and I soon found the problem with the local.ddb file. I
have been grasping at straws trying to get workspace access to the
files. I have located where my workspaces are located on my C: drive -
after deleting the local.ddb file and restarting Intralink, I tried
creating a brand new workspace then going out and copying all of the
files from the "old" workspace into the "new" workspace that was created
after deleting the local.ddb file. The strange thing is, when I look at
the folder I see all of the files, but when I open Pro-E through that
Intralink workspace I do not see any files.



Am I completely screwed when it comes to accessing these files and
ultimately getting them into Intralink as modified parts?



Wildfire 3.0

Intralink 3.4 M020



Thanks,

Nick

[ptc-356787]

It is possible to retrieve your work from a corrupt .proi if you know what
you are doing. You need to be careful of renamed files - if they have been
renamed in Intralink then the physical file will not have been renamed. It
will still have the old name. Provided you watch out for this, then the
chances are you will be able to retrieve lost data from corrupt workspaces.
Chances are, you may only have one or two files that have actually been
intentionally modified. Move these files (to C: for example), delete the
local.ddb, restart Intralink and create a new workspace. Add the assembly in
question to your workspace and then pull in your parts and assembly from C:
IN THAT ORDER - otherwise the assembly from backup will try and pull in
unmodified part files from your workspace.



Hope this helps.



Phil



















Phillip Wolstenholme
BEng (Hons) AMIMechE Prof MICME
Senior Design Engineer,
Fort Vale Engineering Ltd.,

[msteffke]

Nick, what you were attempting is definitely tabboo with intralink.
The names are encrypted and you really have to know what you are doing.

For future reference here are a couple tricks I've used over the years
on these oversized or corrupted .ddbs. These are probably not promoted
by PTC, but when all else fails I try them as a last ditch effort.
The first is windows system restore. I have found that when you do a
system restore, it restores your local.ddb to the restore date. This
can be good and bad. The result is that your local.ddb is good, but it
no longer perfectly matches the data in your .proi folders. If you are
comfortable with what changes were made, such as a part modification,
you may be able to get something checked in.
#2. Sometimes a corrupt workspace will function, but no longer
compact, giving errors. This will lead to certain doom sooner or later.
What I have done in this case is, starting with the ugliest workspace,
create a new workspace with a similiar name, export everything from the
original WS to the new WS, then delete the old WS. Then try to do a
compact. Do this to each workspace until the compact is successful.
I have used these methods on Intralink 3.4 only.
Mark Steffke
Engineering System Administrator
The Delfield Company
Manitowoc Foodservice
T 989.775.9215
Integrity, Commitment to Stakeholders, and Passion for Excellence

[ptc-356787]

Hi Nick,



PTC wouldn't recommend because I doubt even some of their people would know
how to go about doing it. In Intralink 8, files are indeed encrypted but
only to the point that they are embedded in: lid_XXXXX.wfcont (client side,
modified data) and sid_XXXXX.wfcont (server side, unmodified data) which you
can move and rename the extension to .asm, .prt or .drw. Take your time and
be careful what you're doing. It's not as complicated as it sounds and will
save you a lot of effort in the case of a corrupted workspace. Intralink is
NOT likely to get screwed up because it is no different to backing a file up
from a session of Pro/E and then retrieving from backup. You just need to be
careful what you're doing and take your time.



Hope you get it sorted.



Phil