RE: Best practice for backing out of Application Patches
Thanks to Thomas Mercadante, Stephen Lee and Rick Cale for their responses. I think it's pretty unanimous that if this needs to be done, I would just restore to the point in time taken right before the patches were installed. Either I could do an export/restore/import or refresh from the production Database (As long as the problem was caught before getting put on the production Database). I just want to be covered from all angles before this application goes into production. Thanks again! -Scott Stefick At 12:14 PM 12/3/02 -0800, you wrote: Scott, Of course, the answer is "It depends". It all depends on the kind of software patches that are being applied. Are you talking about adding a column to a table that allows nulls? There might not be a need to back this patch out - the column might be able to stay depending on how it is used during an insert or select statment. If the application does not use the column, then removing it from the table might need to be done. On the other hand, if you are using version 8.1.7, you can always drop the column from the table. If your patches are just updates to schema views, you can always simply e-apply the prior version of the views to back the updates out of the database. see, it all depends on the kind of schema update that was performed. and it can get very complicated when you are talking about foreign keys - literally hundreds of tables could be involved - and you probably do not want to be trying to figure out what got touched by an update. probably the best answer is - to back all database changes out of a schema, perform a database point-in-time restore back to before you applied the patches. if I had your job, and this was a purchased application, this is what I would do. hope this helps. Tom Mercadante Oracle Certified Professional -Original Message- Sent: Tuesday, December 03, 2002 2:25 PM To: Multiple recipients of list ORACLE-L >Sorry, I forgot a Subject title! > >Gurus, > >I was just given a project to maintain a Computerized Maintenance >Management System. When I asked the companies support staff how to roll >back patches in the backend Oracle Database (Ver. 8174), they said that >there was no way to do this. I'm guessing I could use logminer just >incase a patch doesn't work. Would this be a good solution, or are there >other (better) ways of safeguarding myself when it comes to >patching? Obviously, I will be applying the patches to a test instance >first, but I don't want to have to go back to restore from a backup if the >patch causes unexpected issues. > >TIA! -Scott Stefick ** Scott Stefick UNIX Systems Administrator Oracle Certified Professional DBA Wm. Rainey Harper College 847.925.6130 ** -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: Scott Stefick INET: [EMAIL PROTECTED] Fat City Network Services-- 858-538-5051 http://www.fatcity.com San Diego, California-- Mailing list and web hosting services - To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing). -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: Mercadante, Thomas F INET: [EMAIL PROTECTED] Fat City Network Services-- 858-538-5051 http://www.fatcity.com San Diego, California-- Mailing list and web hosting services - To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing). ** Scott Stefick UNIX Systems Administrator Oracle Certified Professional DBA Wm. Rainey Harper College 847.925.6130 ** -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: Scott Stefick INET: [EMAIL PROTECTED] Fat City Network Services-- 858-538-5051 http://www.fatcity.com San Diego, California-- Mailing list and web hosting services - To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).
RE: Best practice for backing out of Application Patches
Scott, Of course, the answer is "It depends". It all depends on the kind of software patches that are being applied. Are you talking about adding a column to a table that allows nulls? There might not be a need to back this patch out - the column might be able to stay depending on how it is used during an insert or select statment. If the application does not use the column, then removing it from the table might need to be done. On the other hand, if you are using version 8.1.7, you can always drop the column from the table. If your patches are just updates to schema views, you can always simply e-apply the prior version of the views to back the updates out of the database. see, it all depends on the kind of schema update that was performed. and it can get very complicated when you are talking about foreign keys - literally hundreds of tables could be involved - and you probably do not want to be trying to figure out what got touched by an update. probably the best answer is - to back all database changes out of a schema, perform a database point-in-time restore back to before you applied the patches. if I had your job, and this was a purchased application, this is what I would do. hope this helps. Tom Mercadante Oracle Certified Professional -Original Message- Sent: Tuesday, December 03, 2002 2:25 PM To: Multiple recipients of list ORACLE-L >Sorry, I forgot a Subject title! > >Gurus, > >I was just given a project to maintain a Computerized Maintenance >Management System. When I asked the companies support staff how to roll >back patches in the backend Oracle Database (Ver. 8174), they said that >there was no way to do this. I'm guessing I could use logminer just >incase a patch doesn't work. Would this be a good solution, or are there >other (better) ways of safeguarding myself when it comes to >patching? Obviously, I will be applying the patches to a test instance >first, but I don't want to have to go back to restore from a backup if the >patch causes unexpected issues. > >TIA! -Scott Stefick ** Scott Stefick UNIX Systems Administrator Oracle Certified Professional DBA Wm. Rainey Harper College 847.925.6130 ** -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: Scott Stefick INET: [EMAIL PROTECTED] Fat City Network Services-- 858-538-5051 http://www.fatcity.com San Diego, California-- Mailing list and web hosting services - To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing). -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: Mercadante, Thomas F INET: [EMAIL PROTECTED] Fat City Network Services-- 858-538-5051 http://www.fatcity.com San Diego, California-- Mailing list and web hosting services - To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).
Best practice for backing out of Application Patches
Sorry, I forgot a Subject title! Gurus, I was just given a project to maintain a Computerized Maintenance Management System. When I asked the companies support staff how to roll back patches in the backend Oracle Database (Ver. 8174), they said that there was no way to do this. I'm guessing I could use logminer just incase a patch doesn't work. Would this be a good solution, or are there other (better) ways of safeguarding myself when it comes to patching? Obviously, I will be applying the patches to a test instance first, but I don't want to have to go back to restore from a backup if the patch causes unexpected issues. TIA! -Scott Stefick ** Scott Stefick UNIX Systems Administrator Oracle Certified Professional DBA Wm. Rainey Harper College 847.925.6130 ** -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: Scott Stefick INET: [EMAIL PROTECTED] Fat City Network Services-- 858-538-5051 http://www.fatcity.com San Diego, California-- Mailing list and web hosting services - To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).