Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Validate SIARD fills main drive #330

Open
krosenbe opened this issue Sep 14, 2022 · 3 comments
Open

Validate SIARD fills main drive #330

krosenbe opened this issue Sep 14, 2022 · 3 comments

Comments

@krosenbe
Copy link

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:

  1. Load SIARD
  2. Validate SIARD
@luis100
Copy link
Member

luis100 commented Sep 16, 2022

Please try to go to Preferences > Settings and change the "Temporary folder" path.

@luis100
Copy link
Member

luis100 commented Sep 16, 2022

Also, if resources are an issue, you can try to validate using the command-line tool:
https://github.com/keeps/dbptk-developer/wiki/Validation

@krosenbe
Copy link
Author

krosenbe commented Oct 17, 2022

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants