sul-dlss / libsys-webforms

Rails applications for various Symphony reporting & updating tools.
1 stars 2 forks source link

Do final steps to move app to production #319

Closed dlrueda closed 7 years ago

dlrueda commented 7 years ago

Before cutover day:

On day we cut over to prod:

dlrueda commented 7 years ago

For sequences:

sys@LTRXDEV1> select max (batch_id) from ora_sul.sal3_batch_requests_batch ; MAX(BATCH_ID)

Elapsed: 00:00:00.03 sys@LTRXDEV1> select batch_id from ora_sul.sal3_batch_requests_batch ; no rows selected Elapsed: 00:00:00.00 sys@LTRXDEV1> create sequence ora_sul.sal3_batch_requests_batch_seq ; Sequence created. Elapsed: 00:00:00.11

sys@LTRXDEV1> select max (batch_id) from ora_sul.uni_updates_batch ; MAX(BATCH_ID)

15190 Elapsed: 00:00:00.01 sys@LTRXDEV1> create sequence ora_sul.uni_updates_batch_seq start with 15191 ; Sequence created. Elapsed: 00:00:00.06

matthewahmed commented 7 years ago

The sequence names in LTRXDEV1 are SAL3_BATCH_REQUESTS_BATCH_SEQ, UNI_UPDATES_BATCH_SEQ. I take it the above means they should they be set to one more than the MAX(BATCH_ID) at the time of the switch over.

I've copied the updated EXPEND_RPT and ENCUMB_RPT packages to LTRXPRD1, with the procedures to schedule reports to run immediately. The current reports still work with this.

dlrueda commented 7 years ago

No, once sequences are made on the uni_updates_bat_seq especially, the old code will break, including calling it from a couple of automated scripts that run daily.

We need to make the sequences at the same time I put three updated scripts into place, and some pl/sql code into place.