Import 300G DB - Page 2
DBAsupport.com Forums - Powered by vBulletin
Page 2 of 3 FirstFirst 123 LastLast
Results 11 to 20 of 28

Thread: Import 300G DB

  1. #11
    Join Date
    Aug 2001
    Location
    Waterloo, On
    Posts
    547
    AT 300 GB, I think most of it would be row data.
    I suggest, instead of exporting the whole database at one go, you export the structure first (with rows = N). After importing the structure, you can export/import rows or even load data using SQL*loader.

    Raminder Singh

    Oracle Certified DBA: Oracle 8i, 9i


    Mail me at raminderahluwalia@rediffmail.com.

  2. #12
    Join Date
    Apr 2002
    Location
    Germany.Laudenbach
    Posts
    448
    Hi,
    it's not he OS

    NT 5.0 could store Exabytes?

    http://www.raidtoolbox.com/support.html

    Orca
    I think the filesize is limited by 64Bit -Address-pointer.

    So 300G should never be a problem.

    Hey Unix!! what's with your 2G-Limitation?

    Is ist always the same tables it stops?


    Orca

  3. #13
    Join Date
    Jun 2000
    Location
    Madrid, Spain
    Posts
    7,448
    nt supports large files if itīs ntfs huh

  4. #14
    Join Date
    Apr 2002
    Location
    Germany.Laudenbach
    Posts
    448

    Talking

    Originally posted by pando
    nt supports large files if itīs ntfs huh
    Yes, as you can read on the html-link.
    But i would say VERY LARGE Files!

    Orca


  5. #15
    Join Date
    Mar 2002
    Posts
    301
    After export DB with ROWS=N, i must load data
    into a certain order because a referential integrity!

    Unix don't support importfile more than 2G??


  6. #16
    Join Date
    May 2002
    Location
    USA
    Posts
    462
    It seems u are using windows 2000 . let me know if your hard disks are properly merged . if the export terminates in the middle just check if the .dmp file size if it has reached hard disk capacity ?
    alternative solution is try using tablespace / schema option in your export.
    siva prakash
    DBA

  7. #17
    Join Date
    Apr 2002
    Location
    Germany.Laudenbach
    Posts
    448
    Originally posted by bensmail
    After export DB with ROWS=N, i must load data
    into a certain order because a referential integrity!

    Unix don't support importfile more than 2G??

    You can import the data into the Unix-Db from the win2k-Server.

    imp user/pwd@unix_db_serviceName ...
    Orca
    Importing with constraints is slow!
    Before inserting data you should dsiable all constraints.

    Orca

  8. #18
    Join Date
    Mar 2002
    Posts
    301
    Thank's ALL it works:
    With ROWS=N and with disabling constraints before IMPORT.

  9. #19
    Join Date
    Apr 2001
    Location
    Czechia
    Posts
    712
    Originally posted by bensmail
    The goal for this export is to migrate a instance (300G)
    from Win2000 to Unix.
    Is there another method to migrate without exp/imp?
    Export and Import structure first, then the small tables.
    For the large tables use direct-load insert. You need both instances running and db link created.
    Approved, definitely faster than exp/imp.
    Ales
    The whole difference between a little boy and an adult man is the price of toys

  10. #20
    Join Date
    Apr 2002
    Location
    Germany.Laudenbach
    Posts
    448
    Originally posted by ales
    Originally posted by bensmail
    The goal for this export is to migrate a instance (300G)
    from Win2000 to Unix.
    Is there another method to migrate without exp/imp?
    Export and Import structure first, then the small tables.
    For the large tables use direct-load insert. You need both instances running and db link created.
    Approved, definitely faster than exp/imp.
    Hi,
    how then you will control COMMIT; So you need to define for every Table a PL/SQL-Block.

    Orca

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