We do monthly releases ... There is a agreed release window too. But one week before the release, we test the release scripts on our release databases to make sure that 1. we don't break anything 2. anything that gets invalid gets fixed by recompiles Then we have 'acceptance users', project manager, developers test the application against the release database (which get refreshed daily from production, and release is applied to them). We don't have downtime for releases, but we have a agreed upon release window. Raj ------------------------------------------------------------------------ --------=20 Rajendra dot Jamadagni at nospamespn dot com=20 All Views expressed in this email are strictly personal.=20 select standard_disclaimer from company_requirements;=20 QOTD: Any clod can have facts, having an opinion is an art ! -----Original Message----- From: Tao Zuo [mailto:Tao_Zuo@xxxxxxx] Sent: Thursday, May 27, 2004 10:44 AM To: oracle-l@xxxxxxxxxxxxx Subject: what is the best practice when apply application new release into database? Hi All, We need to apply application new release into database pretty often =3D (once a week may be) into production database. We would like to suggest =3D give us down time for the new application deployment but get questioned =3D from application team if this is a must, since we have multiple =3D application running on the same database, this will impact other =3D applications. I would like to get input from oracle-l community... Thanks. ---------------------------------------------------------------- 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 -----------------------------------------------------------------