Charles Hooper wrote:
> > Charles Hooper wrote:
> > > I disagree regarding the statement "Never, never, never export". If
> > > the old database server was running some variant of 8i, 9i, or 10.1,
> > > the RMAN method would not move the database to the new server. One of
> > > the advantages of using export and import is to perform repeated
> > > testing of Oracle upgrades, and/or application upgrades. For instance,
> > > if I was running Oracle 8.1.7.3 on an old server, and wanted to test
> > > application compatibility with Oracle 10.2.0.2, exporting from the old
> > > server and importing into the new server is perfectly acceptable. The
> > > export/import process also allows database reconfiguration changes, and
> > > testing those changes without risking harm to the production database -
> > > such changes may be moving to a different character set to support XML
> > > data (watch out for problems with this change), moving to locally
> > > managed tablespaces, changing file location, changing database SID
> > > name, etc. Yes, RMAN or other commands can be used to help with some
> > > of these tasks, but it is very easy to script an export, create
> > > tablespace, and import.
> >
> > Export/import has worked consistently ( and will continue to work in
> > the future ) in a variety of tasks for as long as I have been working
> > with oracle. Obviously there are improvements in 10g but the old
> > functionality for compatibility will be around for a long time.
> >
> > You are right on target Mr. Hooper.
> >
> > >
> > > I do agree that you should not export, delete the database, and import
> > > to "improve" performance. There are great risks with this practice,
> > > and it has been covered from time to time on asktom.oracle.com.
> >
> > This is a technique? Not familiar with that flawed approach.
>
> Exporting the database, deleting the database, and importing the
> database was annouced as a recommended practice to be done twice a year
> during the Oracle session at the Infor (now the third largest ERP
> company) conference this past April. Also included in the
> recommendations during the session: RAID 5 should be used for the
> tablespaces that store database data, a new _tablespace_ should be
> started when the current _tablespace_ exceeds 2GB because it will make
> the database faster. The session was littered with such suggestions.
> Their support site suggested the following for dealing with objects in
> the recycle bin that caused problems when adding users to the
> application: "delete from SYS.OBJ$ where name like 'BIN%' and name not
> like 'BINARY%';"
>
> With tips like these offered by application developers, it is easy to
> see how the experts on this group can significantly improve Oracle
> configurations at customer sites. It must be interesting to walk into
> some of these sites.
>
> Charles Hooper
> PC Support Specialist
> K&M Machine-Fabricating, Inc.
Wow. What did they mean by "deleting the database"? Based on the rest
of the "advice" they give, I guess this is fairly academic, but I'm
curious. Do they mean deleting the relevant datafiles at O/S level or
simply dropping a schema?
Received on Fri Nov 17 2006 - 08:08:02 CST
