CDR Tickets

Issue Number 3972
Summary Refresh CDR DEV Server
Created 2015-09-18 11:21:42
Issue Type Improvement
Submitted By Englisch, Volker (NIH/NCI) [C]
Assigned To Englisch, Volker (NIH/NCI) [C]
Status Closed
Resolved 2016-01-05 17:56:19
Resolution Fixed
Path /home/bkline/backups/jira/ocecdr/issue.170440
Description

The data on our CDR server hasn't been updated in more than a year (before May 2014).
We should start thinking about having it refreshed so that we have fresh data available once we start working on Darwin.

Comment entered 2016-01-05 17:56:10 by Englisch, Volker (NIH/NCI) [C]

The CDR DEV database has been refreshed with the nightly backup from PROD from last night, 2016-01-04.

This is the first time I've run a refresh in the CBIIT environment, so please let me know if you find anything that isn't working properly and I may have missed.

Comment entered 2016-01-05 17:59:04 by Englisch, Volker (NIH/NCI) [C]

It would probably help if more people received the message to pay attention after the DEV DB refresh. So far the message went to the one guy who is on vacation.

Comment entered 2016-01-05 18:03:01 by Englisch, Volker (NIH/NCI) [C]

, in the ticket to update the PullDevData.py/PushDevData.py scripts you also created a new script CheckDevData.py. I haven't found anywhere how to run this script or what to do with it.
Is the script necessary to complete the DB refresh?

The related ticket is OCECDR-3733.

Comment entered 2016-01-06 18:22:17 by Englisch, Volker (NIH/NCI) [C]

I've updated the CDR documentation for the refresh but have a couple more questions I need to check on.

https://cdr.cancer.gov/cgi-bin/cdr/Filter.py?DocId=CDR0000269608&Filter=name:Documentation+Help+Screens+Filter

Comment entered 2016-01-08 12:35:36 by Kline, Bob (NIH/NCI) [C]

You run CheckDevData.py after the refresh to find out what's been lost. Then you review the output and see if any of the things that were lost are still needed. If they are, you restore them. I have attached the output of the check for this refresh.

Comment entered 2016-01-08 12:40:49 by Englisch, Volker (NIH/NCI) [C]

Thanks! I remember seeing that output before - probably on your computer - but I don't know how to run it. I pulled up the webpage created by CheckDevData.py and entered the directory location of the pulled documents and schemas but that didn't create the output you attached.

Comment entered 2016-01-08 13:10:39 by Kline, Bob (NIH/NCI) [C]

My guess is that the web server can't read your dump of the old DB. I bet if you do a recursive chmod 777 on it you'll get the right output. Or you can work from the copy I dropped in d:\tmp\DevData-20160104131140.

Comment entered 2016-01-08 17:23:23 by Englisch, Volker (NIH/NCI) [C]

You guessed correctly and I will add the information to our documentation for the refresh-process.

Comment entered 2016-01-13 18:21:14 by Englisch, Volker (NIH/NCI) [C]

Documentation has been updated.
Closing ticket.

Attachments
File Name Posted User
DevData-20160104.html 2016-01-08 12:35:36 Kline, Bob (NIH/NCI) [C]

Elapsed: 0:00:00.001826