| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
 |
 | |||
| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
|
| |||
Home -> Community -> Mailing Lists -> Oracle-L -> RE: what is the best practice when apply application new release into database?
The answer is, it depends. If the changes are strictly in the =
application code for a particular application then no, but if you must =
change database objects that are being referenced by other applications, =
then you may need down time. Changes to database objects can affect =
other objects. Check out the ALL_DEPENDENCIES view.
Dick Goulet
Senior Oracle DBA
Oracle Certified 8i DBA
-----Original Message-----
From: Tao Zuo [mailto:Tao_Zuo_at_npd.com]
Sent: Thursday, May 27, 2004 10:44 AM
To: oracle-l_at_freelists.org
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 =
(once a week may be) into production database. We would like to suggest =
give us down time for the new application deployment but get questioned =
from application team if this is a must, since we have multiple =
application running on the same database, this will impact other =
applications. I would like to get input from oracle-l community...
Thanks.
FAQ is at http://www.freelists.org/help/fom-serve/cache/1.htmlput 'unsubscribe' in the subject line.
-----------------------------------------------------------------
----------------------------------------------------------------
Please see the official ORACLE-L FAQ: http://www.orafaq.com
----------------------------------------------------------------
To unsubscribe send email to: oracle-l-request_at_freelists.org
 |
 |