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

Database migration #76

Open
nekrut opened this issue Sep 19, 2024 · 0 comments
Open

Database migration #76

nekrut opened this issue Sep 19, 2024 · 0 comments

Comments

@nekrut
Copy link
Contributor

nekrut commented Sep 19, 2024

Status of data transfer:

  • database dumps transferred; size: 3.7TB, 56 files
  • flat files transferred size: ~8.2TB (no access)

Waiting on Drew for the following:

  • Verify checksums for dumps
  • Clarify which files map to which databases/sites
  • Confirm we have everything for both db dumps and flat files (2 still in progress)
  • Help map files to databases/sites

Flat files:
In progress: (2)

  • CryptoDB - transferring from UPenn
  • HostDB - transferring from UGA ?
  • Finished: (9)
  • AmoebaDB - finished
  • FungiDB -finished
  • MicrosporidiaDB -finished 7.7G
  • PlasmoDB -finished
  • TrichDB -finished
  • VectorBase -finished
  • PiroplasmaDB - finished 95
  • ToxoDB -finished
  • TriTrypDB -finished

Oracle instance:

  • VM setup! (access via ssh, which should be sufficient)
  • Oracle software: TACC will install
  • Oracle licensing: we can start with the free developer license To obtain the license we simply need to accept the terms during software installation.
  • Paid license: maybe the personal license is a possibility. Perpetual, named user, 521$ with one year of support. Must be for an on-premises setup (which is what we have). As per description, "...Designed without technical limits, time bombs or other "gotchas", the Personal Edition provides all the power of the Oracle Database … ability to handle virtually any type or size of data (from gigabytes of transactions to terabytes of XML data)..." I can't find any mention of "per core" or any other fine print. As long as there are no hidden costs, this may be a solution (we would need 2 such licenses).
  • I think we should start with the free license and upgrade to personal use as soon as we need it (for support, or to download a particular software patch, unlock a feature, etc.) or when we are ready to start exporting the data, whichever comes first.
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

1 participant