Re: Export Import - Linux to Sloaris error

From: Siv Chelakkara <Siv.Chelakkara_at_3cc.co.wayne.mi.us>
Date: Mon, 26 Jun 2000 13:52:05 -0400
Message-Id: <10540.110456@fatcity.com>

Geeta,

This has nothing to do with different operating systems. You need to = create export views to import from a later database version to an earlier = one. see excerpt from Metalink Doc ID 61949.1 below:

Export Views:
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

  Export views, created by the "CATEXP.SQL" script, are internal views = used by=20
  the Oracle Export utility to organize the data it sends to the dump = file. Most
  views are used to group the information needed to create DDL statements, = which
  in turn recreate data dictionary objects. Others are used exclusively = by=20
  Oracle Development. =20

  The export views are not static from version to version of Oracle. As = new=20
  features are added to the Oracle data dictionary, the views have to = change to
  handle them. When running an export executable from one version of = Oracle=20
  against a different database version, it is quite possible that the = executable
  will encounter errors because of version-related changes. Normally, this = can
  be resolved simply by running the version of "CATEXP.SQL" that matches = the
  executable against the database. When trying to make an export that = is=20
  backwards-compatible to an older database, it is often necessary to = shuffle=20
  versions of executables and scripts. The following is the normal process = used:

Source database is newer than the target database:

Run the older "CATEXP.SQL" script on the database to be exported.
Use the older EXP utility to create the dump file.
Use the older IMP utility to import to the target database.
Run the newer "CATEXP.SQL" script on the exported database to restore its export views to the original (correct) version.

  It is also possible to have a situation where the source database is = older=20
  than the target, but you do not have access to the original Export = utility. If
  you must use an export executable from one version against an older = Oracle=20
  database version, it may be necessary to change the export views.

Source database is older than the target database:

Run the newer "CATEXP.SQL" script on the database to be exported.
Use the newer EXP utility to create the dump file.
Use the newer IMP utility to import to the target database.
Run the older "CATEXP.SQL" on the exported database to restore = its export views to the original (correct) version.

Hope this helps.

Sivaram

>>> "Geeta Iyer" <geeta.iyer_at_sprintparanet.com> 06/26/00 12:43PM >>>
Hello all,

I have a strange situation.

Export a user from a Solaris Box 2.6, Oracle 8.1.5 Import to Linux 2.1.6, Oracle 8.1.6 -- works like a charm.

Export a user from a Linux 2.1.6, Oracle 8.1.6 Import to a Solaris Box 2.6, Oracle 8.1.5 -- does not work get the = following
error

IMP-00010: not a valid export file,header failed verification
IMP-00021:operating system error - error code (dec2, hex 0x2)
IMP-00000:import terminated unsuccessfully

The recordlength on the export and import should match due to diff OS, but even with the same record length it does not work..any one experience the same.. or have any ideas??? What am I missing?

Thanks in advance,

Geeta Iyer
Sprint Enterprise Network Services
Work: (303)220-4788
Pager: 800-724-3508
E-Mail: Geeta.Iyer_at_SprintParanet.com=20

If you're bored, then visit the list's website: http://www.lazydba.com = (updated daily)
to unsubscribe, send a blank email to oracledba-unsubscribe_at_quickdoc.co.uk= Received on Mon Jun 26 2000 - 12:52:05 CDT