RE: patches

[Boivin, Patrice J]

Title: Pro*C for Oracle 817 on Win2000?

Yechiel,   If that's your philosophy, and there are known unpatched bugs in the server software, how can you be 100 percent sure it will stay up?   Granted, many of these bugs are esoteric, but not all.   I am curious what Oracle Support consultants do when they have a 24x7 contract, with all these patches.  Surely they have a list.   Regards, Patrice Boivin Systems Analyst (Oracle Certified DBA) [Boivin, Patrice J]  -----Original Message----- From: Yechiel Adar [mailto:[EMAIL PROTECTED]] Sent: Friday, November 29, 2002 3:49 AM To: Multiple recipients of list ORACLE-L Subject: Re: patches We only apply patches as needed and where needed. For example: I had a problem with export taking a long time on one system. I installed a patch for this problem (after testing in test environment of course) only on that database.   My motto is: If it ain't broken do not fix it.   I have seen too many follow up fixes to install something I do not need.   Yechiel Adar Mehish ----- Original Message ----- From: Boivin, Patrice J To: Multiple recipients of list ORACLE-L Sent: Wednesday, November 27, 2002 9:05 PM Subject: patches I am wondering how your sites handle patching production servers.   I just did a search in MetaLink, since 8174 was released there have been 48 patches (if I just select RDBMS).   If I select other items in my search, I get upwards of 70 additional bug fixes.   How do high reliability sites handle patching?  I assume they would rather fix potential problems (testing the patches on a testbed of course) rather than just apply bug fixes as problems are encountered on production servers.   regards, Patrice Boivin Systems Analyst (Oracle Certified DBA)