| Issue Number | 4317 |
|---|---|
| Summary | Refresh CDR QA Database |
| Created | 2017-09-21 15:22:10 |
| Issue Type | Improvement |
| Submitted By | Englisch, Volker (NIH/NCI) [C] |
| Assigned To | Englisch, Volker (NIH/NCI) [C] |
| Status | Closed |
| Resolved | 2017-10-20 13:52:05 |
| Resolution | Fixed |
| Path | /home/bkline/backups/jira/ocecdr/issue.214615 |
Before the Fermi user testing starts we want to refresh the CDR database to use relatively current data.
The CDR database on QA has been refreshed using last night's backup from PROD.
According to the instructions the script CreateLogins_YYMMDDhhmmss.sql would need to be run but it appears everything is working even without. Would you know why that is, ~bkline?
I will be closing this ticket in a couple of days unless some problems are reported related to the refresh.
I don't know why the CreateLogins script isn't needed. ~gaoz would be more likely to know.
Since you didn't reply to my offer to let you practice restoring the scheduled job settings, I'm going to tackle that task myself so it's done before the weekly publishing job kicks in.
..., I'm going to tackle that task myself ....
Done.
If you have another approach than editing the scheduler manually I'd like to hear about it. I was busy with other stuff and not able to jump at this right away.
No problem. At some point we may want to see if automating the process is feasible, but for now I do it manually. At least we have the script to capture the settings before they're blown away, so we're not working from memory. :-)
The users finished a week of QC on our QA server without incidents. I'm declaring the refresh of the CDR database as successful and closing this ticket.
Elapsed: 0:00:00.001189