| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
Home -> Community -> Usenet -> c.d.o.server -> Re: Cloning DB to different UNIX platform
See comments embedded.
Rick Denoire <100.17706_at_germanynet.de> schreef in berichtnieuws
t640muslp88mvknd8u3gi2khg60fqs5bqq_at_4ax.com...
| "Anton Buijs" <aammbuijs_at_xs4all.nl> wrote:
|
| >A full export will create all users and create everything in the same
| >tablespace as where it came from. When the tablespace does not exist, the
| >users default tablespace is choosen.
|
| Exactly. Since SYS is going to do the import, whose default tablespace
| is SYSTEM...
|
| Well, at least if the tablespaces are created (which asumes that the
| corresponding paths exists on the target platform), then you should be
| right.
|
We talk about a FULL import after a FULL export.
Then everything that does not exist, will be created, except the SYSTEM's
tablespace with the catalog etc...
I proposed to create tablespaces in advance because in most cases the
datafile names will not match, causing the tablespace creation to fail,
resulting in segments created in the wrong tablespace.
So when the full import sees user SCOTT is in the dump, user SCOTT will be
created by import. And if it's tables EMP and DEPT where in tablespace
USERS, they will be created in tablespace USERS, not SYSTEM. When tablespace
USERS does not exist, the users default tablespace will be used. If that one
does not exists: table creation fails and you will find errors in the import
log.
This is one reason why it is not a good idea to keep SYSTEM a users default
tablespace.
The user that is doing the import (SYS in your case) is not relevant here,
as long as he has the priviliges to do a full import.
| >Just remember that objects of SYS are not part of the export (including
| >grants given on SYS objects).
| >There are more users that are not exported, even in a full export:
ORDSYS,
| >MDSYS, CTXSYS and ORDPLUGINS. See 8i Utilities Guide, Chapter 1 - Export,
| >paragraph Export Modes.
|
| I did not mean that SYS objects would be exported/imported. So we
| agree here.
Just wanted to mention it because lot of people don't realize it.
|
| >Ok, I know lots of things can go wrong but as said: export/import is the
| >only way to port a db to another platform.
|
| Convinced.
|
| Bye
| Rick
|
Received on Sun Aug 18 2002 - 16:58:03 CDT
![]() |
![]() |