| Issue Number | 4215 |
|---|---|
| Summary | Setup Web Interface to Set Job-ID on STAGE |
| Created | 2017-01-13 16:53:17 |
| Issue Type | New Feature |
| Submitted By | Englisch, Volker (NIH/NCI) [C] |
| Assigned To | Englisch, Volker (NIH/NCI) [C] |
| Status | Closed |
| Resolved | 2017-08-09 17:17:29 |
| Resolution | Fixed |
| Path | /home/bkline/backups/jira/ocecdr/issue.201466 |
When the Gatekeeper database gets refreshed from PROD the Job-IDs
between the GK and the CDR database don't match up anymore on the lower
tiers.
I'd like a way to adjust the sequence number on the lower tier
preventing nightly publishing jobs to fail because the Job-ID already
exists on GK.
The following command will reset the job-ID:
DBCC CHECKIDENT
( pub_proc , RESEED, new_int_value )
It's not clear yet if we will have the permission on STAGE to run the command necessary to update the DB.
The following scripts have currently been updated/created:
Database/Reseed-jobid.sql
Database/Reseed-jobid.py
DevSA.py
ResetMaxJobId.py
If it works on DEV and QA using the standard CDR database account, and it doesn't work on STAGE, that's a database configuration problem which CBIIT will be required to fix. If it doesn't work on DEV and QA, see if you can get the DBA team to fix the problem there first. Otherwise, go ahead and close OCECDR-4130 as "won't fix."
I had forgotten that I had already started to work on this ticket but what I thought I had to do was wrong or too complicated. Anyway, the required DBCC command can only be executed as a stored procedure when using Python.
Questions for ~bkline: (a) Do we have naming conventions for CDR procedure names and (b) where do we keep them?
If it works on DEV and QA using the standard CDR database account,
I can now answer this question: It works on DEV. :-)
For my information:
The two files Database/Reseed-jobid.sql and
Database/Reseed-jobid.py are not used anymore. The Python
script ResetMaxJobId.py has been renamed to
SetNextJobId.py.
The changes are in my Feynman-hold sandbox.
(a) Do we have naming conventions for CDR procedure names and (b) where do we keep them?
See https://ncisvn.nci.nih.gov/svn/oce_cdr/branches/ocecdr-4268/Database/procs.sql
Additional change to include the stored procedure in:
Database/procs.sql
This ticket is somewhat of a workaround or, to be precise, a make-our-life-easier for the GK issue. Once the GK ticket has been implemented, this menu item won't be needed anymore.
The modified files have been moved from the subversion sandbox directory Feynman-hold to the git repositories:
DevSA.py --> cdr-admin [hawking-c8e6c2b]
SetNextJobId.py --> cdr-admin [hawking c8e6c2b]
procs.sql --> cdr-server [hawking 2bda678c]
~volker: please assign story points for this ticket.
~duganal this ticket is a workaround until Blair has time to make necessary changes in GK. For this ticket itself Blair is not needed.
I've (re-)added the following files:
DevSA.py
SetNextJobId.py
https://github.com/NCIOCPL/cdr-admin/commit/66a0805
[ hawking ]
Thanks! Off to do the build. Let me know if/when the missing piece for OCECDR-4126 is finished, and I'll do a manual patch of the build.
I've successfully tested this internal ticket on QA. ~bkline, feel free to do some additional testing. Otherwise I'll mark it as QA Verified.
I'll trust you on this. :-)
This menu item to adjust the Job-ID number is only available on the
lower tier because only there is it useful. The Job-ID number on PROD
will never be adjusted.
Closing ticket.
Elapsed: 0:00:00.001207