Greatings, I would like to get a general feel of when people patch their databases to the next patch level. How do you present to management the need to take the time to implement the patches? At my old job I would lay the blame on the application vendor (Vendor won't support the application if we move to version x.x.x.x) or the manager wouldn't feel it necessary to take the time ("we'll wait 'til next week."). Now if I'm a more full-time DBA how do I go about deciding when a database needs patched? When do you feel comfortable that patch will not cause more harm than good? Thanks!!!! --------------------------------- Do you Yahoo!? Yahoo! Finance: Get your refund fast by filing online ---------------------------------------------------------------- Please see the official ORACLE-L FAQ: http://www.orafaq.com ---------------------------------------------------------------- To unsubscribe send email to: oracle-l-request@xxxxxxxxxxxxx put 'unsubscribe' in the subject line. -- Archives are at //www.freelists.org/archives/oracle-l/ FAQ is at //www.freelists.org/help/fom-serve/cache/1.html -----------------------------------------------------------------