RE: To do or not to do (export)?
- From: "Hostetter, Jay M" <JHostetter@xxxxxxxxxxxxxxxxxxxx>
- To: <cicciuxdba@xxxxxxxxx>, "David Ballester" <ballester.david@xxxxxxxxx>
- Date: Wed, 7 Oct 2009 06:39:18 -0400
Your export from Sunday is still quite handy for recreating a dropped
user, recreating dropped PL/SQL, fixing privileges that have been
changed, etc. I always make sure that we have daily export (often times
with ROWS=N) for this purpose. You can always import with SHOW=Y to
find the commands that you need.
Jay
________________________________
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Guillermo Alan Bort
Sent: Wednesday, October 07, 2009 6:10 AM
To: David Ballester
Cc: oracle-l-freelists
Subject: Re: To do or not to do (export)?
Yes, you are correct and this is the point that has been made, however,
from an application point of view, in that case I would not be able to
guarantee consitency...
If I have an export from last sunday, and it's wednesday, I would still
go for wither a full DB restore or a db duplication en export/import of
the whole schema, not just the table.
But that's just my point of view...
cheers.
Alan Bort
Oracle Certified Professional
On Wed, Oct 7, 2009 at 6:19 AM, David Ballester
<ballester.david@xxxxxxxxx> wrote:
**DISCLAIMER
This e-mail message and any files transmitted with it are intended for the use
of the individual or entity to which they are addressed and may contain
information that is privileged, proprietary and confidential. If you are not
the intended recipient, you may not use, copy or disclose to anyone the message
or any information contained in the message. If you have received this
communication in error, please notify the sender and delete this e-mail
message. The contents do not represent the opinion of D&E except to the extent
that it relates to their official business.
Other related posts:
