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

Thread: Import/Export anormal behaviour on target-DB

  1. #1
    Join Date
    Jun 2008
    Posts
    17

    Import/Export anormal behaviour on target-DB

    Hello together,

    I did on the source-DB one export with paramter full=y. On the target -DB the scenario exist. So I re-create two tablespaces (data1,data2) before I start to import the dump-file. Now it seems that some views does not work correctly. Why? Could someone explain me the behaviour?

    Regards

  2. #2
    Join Date
    Mar 2007
    Location
    Ft. Lauderdale, FL
    Posts
    3,555
    Define "not work correctly".

    Look at the import log.
    Last edited by PAVB; 08-20-2008 at 06:50 AM.
    Pablo (Paul) Berzukov

    Author of Understanding Database Administration available at amazon and other bookstores.

    Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.

  3. #3
    Join Date
    Dec 2007
    Posts
    82
    look at import log for full description and compile invalid objects in your database.
    CHEERS...
    /MR

  4. #4
    Join Date
    Jun 2008
    Posts
    17
    Again, within my import.log I got Oracle-errors 2298.. So I think I have some problems with constraints. If I import with contraints=n, how could I activate the contraints on the traget DB? Or what I have to do after the import job?

  5. #5
    Join Date
    Jun 2008
    Posts
    17
    One difference between the source-DB and the target-DB is that on the target-DB one view does not work. I wrote it. But I got no error or failure. The sql plus worksheet hang-up, but on the source-DB I got the result of the statement within a few seconds...

  6. #6
    Join Date
    Mar 2007
    Location
    Ft. Lauderdale, FL
    Posts
    3,555
    Quote Originally Posted by NetCohort
    If I import with contraints=n, how could I activate the contraints on the traget DB? Or what I have to do after the import job?
    Script your constraints in your source database.
    Run script on your target database.
    Pablo (Paul) Berzukov

    Author of Understanding Database Administration available at amazon and other bookstores.

    Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.

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