-
Export & Import
version 9.2.0.6
OS; UNIX 2.8
I wanted to capture a schema (without rows)in one database and copy it to another. So I did an export of the schema (rows=n) and imported it into the other database. When the import was done the tablespace I was importing to sucked up 4 gigs worth of contigious space even when no data was imported. The tablespace is locally managed with automatic extents and segments in the target but the host is dictionary managed.
Here's my theory... The import is somehow telling oracle " I don't care if you're locally managed, I want you to use the object storage clause in my create statement". If you have storage clauses in your table create statements I was under the impression Oracle ingores them because of the locally managed function?
After the import was done, I extracted all the ddl statements for the schema, stripped the storage clause than ran it. After it was done there was only 25 megs of used space in the tablespace instead of the 4 gigs of the earlier import.
So I guess the big question is how and why does the Oracle import feature bypass LMT storage options?
Oracle it's not just a database it's a lifestyle!
--------------
BTW....You need to get a girlfriend who's last name isn't .jpg
-
doesnt ignore them completely.
Example if you say create table .. inital 5Gb you will get 5gb worth of extents so if you extent sixe was 1Mb you would get 5000 extents straight away.
What is ignored is thinks like pctincrease, next etc..
-
You know, I had a sneaky suspicion that it was the initial extent that was causing all the havoc.
Now I guess the next question is how would one strip all storage clauses from an import to eliminate this hassle.
Oracle it's not just a database it's a lifestyle!
--------------
BTW....You need to get a girlfriend who's last name isn't .jpg
-
could use an indexfile, edit that using vi / sed / awk or whatever
create the objects then run with ignore=y
-
Originally posted by davey23uk
could use an indexfile, edit that using vi / sed / awk or whatever
create the objects then run with ignore=y
Yea, I know but you know as well as I do editing an indexfile with 100's of objects is about as much fun as yanking teeth. Sure would be nice to be able to have some variable like storage_clause=n.
Hmmmmmm, enhancement suggestion???
Oracle it's not just a database it's a lifestyle!
--------------
BTW....You need to get a girlfriend who's last name isn't .jpg
-
Aw, c'mon now. It's a simple token parser. That's about a 30 minute exercise for a jr. perl programmer.
Jeff Hunter
-
Haven't I seen someone posting a link to a free soft that would do things with dump files? Senile dementia ensures that I have no idea of the name.
"The power of instruction is seldom of much efficacy except in those happy dispositions where it is almost superfluous" - Gibbon, quoted by R.P.Feynman
-
Originally posted by DaPi
Haven't I seen someone posting a link to a free soft that would do things with dump files? Senile dementia ensures that I have no idea of the name.
maybe it was on DKB's site?
Jeff Hunter
-
I think it was this: http://www.dbasupport.com/forums/sho...threadid=36644 which might not help.
P.S. Jeff, what *are* you doing with your balls? Looks like some kind of sorting algorithm gone mad.
"The power of instruction is seldom of much efficacy except in those happy dispositions where it is almost superfluous" - Gibbon, quoted by R.P.Feynman
-
A) Precreate the tables with the scripts taken with below commands
EXECUTE DBMS_METADATA.SET_TRANSFORM_PARAM (DBMS_METADATA.SESSION_TRANSFORM, 'STORAGE',false);
SELECT DBMS_METADATA.GET_DDL('TABLE',<>) FROM DUAL; -- you can select from dictionary for the list of tables.
B)Import and use ignore=y
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|