Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.tools -> Re: Export 8.1.6.1.0 -> 8.1.5.0.0 failing

Re: Export 8.1.6.1.0 -> 8.1.5.0.0 failing

From: George <george_at_is.co.za>
Date: 2000/08/07
Message-ID: <398e4dc8$0$233@helios.is.co.za>

Reading the subject of your message I am assuming you are exporting from 8.1.6 and importing on 8.1.5.

If so you need to use the 8.1.5. export utility to export the data from you 8.1.6 database and also use the 8.1.5 import.

The import and export tool version generally needs to be the same version as you target db. especially if going to a lower version.

good luck.

George
  Martijn Spronk <spronk_at_columbusgroup.com> wrote in message news:398AF9FC.CB4A6344_at_columbusgroup.com...   I tried to move some data from our dev (8.1.6.1.0 on Linux) to a   production database (8.1.5.0.0 on Solaris 8)..   I exported using:
  exp system/manager file=bugtrax.dmp owner=bugtrax   and imported using:
  imp system/manager fromuser=bugtrax touser=bugtrax file=bugtrax.dmp

  However, is gives me an error saying:

  Import: Release 8.1.5.0.0 - Production on Fri Aug 4 09:18:48 2000

  (c) Copyright 1999 Oracle Corporation. All rights reserved.     

  Connected to: Oracle8i Enterprise Edition Release 8.1.5.0.0 - Production
  With the Partitioning and Java options   PL/SQL Release 8.1.5.0.0 - Production

  IMP-00010: not a valid export file, header failed verification   IMP-00000: Import terminated unsuccessfully

  I can't imagine it would be a version problem. I would imagine that the error
  message would be a bit more meaningful in that case.   I moved data before (for a different owner) the other way around (8.1.5 -> 8.1.6) and
  that was never a problem.

  I made sure I did transport in binary mode. And also, if I try ftping the dump file back
  to the dev server, and try to import it into the 8.1.6.1 version, there is no problem.
  So the problem doesn't lie with export, and not with the file transfer...
  it seems to be the 8.1.5.0.0 import that's causing a problem.

  Is the CATEXP.SQL or CATALOG.SQL script ran when you create the database
  with the Wizzard? Would not running it cause a meaningless error message like this?! HELP!

  Martijn

  --

  Columbus Group
  Vancouver & Toronto, Canada
  @: spronk_at_columbusgroup.com
  TalkTo: 604.801.5758 x 248     

--
Received on Mon Aug 07 2000 - 00:00:00 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US