CDR Tickets

Issue Number 3996
Summary Schedule QA to be refreshed monthly
Created 2015-11-06 16:19:07
Issue Type Improvement
Submitted By Osei-Poku, William (NIH/NCI) [C]
Assigned To Englisch, Volker (NIH/NCI) [C]
Status Closed
Resolved 2016-03-18 15:09:03
Resolution Fixed
Path /home/bkline/backups/jira/ocecdr/issue.173393
Description

As we discussed in yesterday's CDR meeting, there is the need to have at least one of the lower tiers refreshed regularly to enable us train, practice and test CDR functionalities with new or updated data. It looks like the consensus was to schedule a job to regularly update QA (instead of stage) on a monthly basis.

Comment entered 2016-01-21 12:23:34 by Englisch, Volker (NIH/NCI) [C]

I have submitted a DBA ticket to explore this option (DBATEAM-2233).

Comment entered 2016-01-25 18:50:43 by Englisch, Volker (NIH/NCI) [C]

The DBA team replied with the following message:

Below is what can be executed when you want to refresh CDR database:
EXECUTE master.dbo.USP_RefreshDBFromProd 'CDR'

I will try to perform a refresh in order to test the stored procedure provided. If it works successfully and we do have the ability to perform a refresh of the CDR database without having to involve the CBIIT or DBA team we will not need a scheduled process.

Comment entered 2016-02-11 18:15:35 by Englisch, Volker (NIH/NCI) [C]

I tried, I failed, I cried!

Apparently I do not have permissions to update the CDR database by myself. I will check with Yuen tomorrow if he can run the refresh and check if we could get permissions to update our DBs ourselves.

Comment entered 2016-03-18 15:08:47 by Englisch, Volker (NIH/NCI) [C]

I tried, I failed, I cried!

I tried again, I succeeded, I'm bursting with joy!

I was able to refresh the CDR database on QA with yesterday's backup from PROD. The process took about 20 minutes. Two (maybe three) things to keep in mind:

  • I have to logon to SQL Server Management Studio using my NIH account

  • The restore command

     EXECUTE master.dbo.USP_RefreshDBFromProd 'CDR'

    must be submitted using the master DB

  • (maybe) we'll need to run refreshManifest.py prior to using XMetaL

Comment entered 2016-03-21 13:46:42 by Englisch, Volker (NIH/NCI) [C]

It appears the refresh was successful and we're now able to refresh QA on demand.
Closing ticket.

Comment entered 2016-04-01 17:12:21 by alan

I am happy for you!

And to think, this great happiness was brought to you by your friendly
systems administrators.

–

Thanks,

Alan
___________________________________
Alan Meyer
NCI OCPL - Office of Communications & Public Liaison
Contractor: Sapient Government Services
NCI: 301.435.4865

Comment entered 2016-04-02 20:18:50 by alan

I remember entering that last comment quite a while ago. I think it must have gone into a JIRA time warp and come out on April Fool's day.

Ah well.

Comment entered 2016-04-02 20:24:06 by alan

Found it.

I sent it my email to ncijirambx@mail.nih.gov at 4:31 pm on March 18. I must not have realized that ncijirambx is actually in Kazakhstan, by way of Tierra del Fuego.

Comment entered 2016-04-02 21:04:11 by Englisch, Volker (NIH/NCI) [C]

This is great! It means there is a chance we'll still be getting lost messages from Alan for years to come. I can't wait!!! :-)

Elapsed: 0:00:00.001501