DBAsupport.com Forums - Powered by vBulletin
Results 1 to 7 of 7

Thread: Import Best Practise

  1. #1
    Join Date
    Jan 2004
    Posts
    30

    Import Best Practise

    Hi,

    I need to import a 5.5gb exp.dmp to another database for database migration. Can someone suggest what are the best practise for import (or may be export).

    thankz is advance.

  2. #2
    Join Date
    Mar 2001
    Location
    Ireland/Dublin
    Posts
    688
    very difficult question ...
    try to use exp & imp utility and help to them, or if you do it the first time you can create test database and do import into it.
    Best wishes!
    Dmitri

  3. #3
    Join Date
    Jan 2001
    Posts
    3,134
    More info needed!

    Are they the same OS?
    Same Oracle version?
    Is this a full, schema, table level import?
    What is the capitol of Malaysia?

    MH
    Last edited by Mr.Hanky; 04-01-2004 at 02:56 PM.
    I remember when this place was cool.

  4. #4
    Join Date
    Jan 2004
    Posts
    30
    Originally posted by Mr.Hanky
    More info needed!

    Are they the same OS?
    Same Oracle version?
    Is this a full, schema, table level import?
    What is the capitol of Malaysia?

    MH
    Hi Hanky,

    1) The OS are the same.
    2) Not same oracle version. Source database 8.1.6. New database 8.1.7.
    3) Schema level.
    4) Iz't related? Kuala Lumpur

  5. #5
    Join Date
    Jan 2001
    Posts
    3,134
    Well, it sounds like you already have the export complete, no.
    As A rule I always export more than I need (indexes, grants, ect..) just in case there is a problem or applications changes their mind. Better to have more than get caught without.

    In your case I would zip (compress) the .dmp, ftp it over.
    From there you can drop the old schema, re-create the user and do the import. Or just drop all the schemas objects and do the import.
    There should be no compatability issues since you are exporting from a Oracle 8.1.6 and importing to 8.1.7...
    BUT TAKE A BACKUP ANYWAY!!
    just to be safe.

    MH
    I remember when this place was cool.

  6. #6
    Join Date
    Apr 2003
    Location
    South Carolina
    Posts
    148
    I would also make sure (if possible) that ALL small rollback segments
    are offline and have only 1 LARGE rollback segment online

    Gregg

  7. #7
    Join Date
    Jan 2001
    Posts
    3,134
    Originally posted by gbrabham
    I would also make sure (if possible) that ALL small rollback segments
    are offline and have only 1 LARGE rollback segment online

    Gregg
    True, if there are large tables just use
    BUFFER= (I usually use 8000000, roughly 7 MB's)
    COMMIT=y

    this way you will not blow out your RBS by issuing a commit every time the buffer limit is reached.

    MH
    I remember when this place was cool.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  


Click Here to Expand Forum to Full Width