...
Post release actions:
1. GRBK-646: Check production DB if we have duplicate (same realm_id) entries in the
| Panelcode |
|---|
GB_USER_DEREF_RM_UPDATE_T a.select select realm_id, count  (*) as NUM_DUPS from GB_USER_DEREF_RM_UPDATE_T group by REALM_ID having count (*) > 1; |
Rollback:
â—� Anand Mehta rolls back the upgrade by doing the following:
1. (8:00 am to 8:15 am) Anand Mehta stops any running Tomcats.
2. (8:15 am to 8:25 am) Anand Mehta renames tomcat to tomcat-264 and tomcat-263 to tomcat on all app servers.
3. (8:25 am to 8:40 am) Anand Mehta backs up the existing properties files and puts the 2.6.2 properties files in the sakai directory.
4. (8:40 am to 9:40 am) Mark Pankow
1. I would import the SAKAI schema from the export taken manually. That should not take more than the 40 minutes alloted.
2. Additionally, measures above would allow for a restore and recovery to the point right before the upgrade using the 4AM hot backup.
3. Lastly, the standby base is there and ready to be converted to the primary in the event of catastrophic failure.
4. ADD: log transfer; reconnect primary database to hot standby
5. ADD: Any syntax, commands, sql scripts for these steps above
...