You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description:
I created a SIARD extract with lots of BLOBS (not sure if that has anything to do with this issue).
Extract is ~400G on E:\ drive
Validation nearly filled C:\ drive under C:\Users<me>.dbvtk.
After validation size of .dbvtk folder is ~33G.
Because the drive was nearly full, I moved the .dbvtk folder to the E:\ drive, but now DBPTK Desktop does not recognize that the validation has completed unless I move the folder back to C:\Users.
Would like to be able to save/open the validation from somewhere other than C:\Users.
Is there a way to do that?
Context:
DBPTK Desktop: Windows Server 2019 Standard version 1809 build 17763.3287
Steps required to reproduce the bug:
Load SIARD
Validate SIARD
The text was updated successfully, but these errors were encountered:
I changed the Temporary folder path and re-ran the validation.
It got to T_6.0-1 Validating Primary Keys and started to fill the c:\Users\<me>\.dbvtk\mapdb folder before I killed it.
Since I moved the previous .dbvtk folder, dbptk doesn't recognize that I've already validated the siard file - is there any way to tell dbptk to open that particular validation report from the new location?
Description:
I created a SIARD extract with lots of BLOBS (not sure if that has anything to do with this issue).
Extract is ~400G on E:\ drive
Validation nearly filled C:\ drive under C:\Users<me>.dbvtk.
After validation size of .dbvtk folder is ~33G.
Because the drive was nearly full, I moved the .dbvtk folder to the E:\ drive, but now DBPTK Desktop does not recognize that the validation has completed unless I move the folder back to C:\Users.
Would like to be able to save/open the validation from somewhere other than C:\Users.
Is there a way to do that?
Context:
Steps required to reproduce the bug:
The text was updated successfully, but these errors were encountered: