Closed libdgg closed 1 year ago
CB emailed stakeholders (and the OIT team) on 2023-02-21 with status update (parsed out here for timeline steps):
2/21: Zo and Beth have successfully reindexed the Fedora QA database after adding more data from production.
2/21: Email stakeholders to please check the testing version of your applications to ensure they are working properly and let us know when you have done so.
2/24: Date for any feedback from stakeholders. We would like to hear from you before Friday.
2/27 - 3/3: Putting the production Fedora into read-only mode next week to let OIT copy its data to a new, upgraded database. Read-only mode is necessary to prevent changes entering the database after the copy starts, so you don’t lose work in the migration.
3/6 - 3/10:
CLOSING this ticket. Moved the content into the EPIC ticket and tracking from there going forward.
2023-02-10: UPDATE
Now, In QA We attempted to reindex the Fedora QA database this week, but the process failed. The issue appears similar to one previously encountered in 2015. Zo is reaching out to someone in OIT who was involved back then for help. Once the reindexing process is working, we will rerun it with more data copied from Production to ensure all data types are covered. Despite the documentation, we found the reindexing process requires Fedora to be shut down. So, the affected applications will be missing critical functionality throughout the reindexing process. The applications themselves do not need to be shut down, but interactions with Fedora (uploads, downloads, etc.) will not work. Search and metadata retrieval should function normally. We still need to confirm that the old database works after the reindexing process completes. We plan to confirm this before we meet with the OIT database team next Friday, February 10th. As we complete more of this work, I will reach out to you to test the QA applications against the upgraded database.
Plan for production We will put Fedora into read-only mode for the week before Spring Break. This will allow the database team to copy the production database to the new Oracle version. If this copy goes smoothly, then no reindexing may be necessary. If the copy does not produce useable results, we will need to reindex the Fedora data into a new, empty database. During Spring Break, we will shut Fedora down and start this process. Once Fedora is running with the upgraded database, I will again reach out to complete testing for the production applications.
Backout plan Since all our plans involve moving data to a new database, our primary plan in case of issues is to revert to the old database. If this is not possible, we must request the latest backup of data available, and go through disaster recovery. As the current version of Oracle is reaching end-of-life, we will need to complete more testing and reattempt the upgrade at a later date.