I am able to take export of a oracle 8i database(database is on a NT box). Now if I try to take the export of the same database, from a Sun box , which has oracle 8.0.5 , using SQL*net connection, I am getting following errors:
Ora -904, Exp-00008, ora-1003 on some tables of system tablespace. Can any one through some light on this.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Export usually works just fine (and a whole lot faster in most cases) if it is done directly on the server. That way the version of the database and the version of export are in sync. If you have Oracle8.0.5 for NT and you install the database utilities portion of that on your client (in a separate Oracle_home from your 8i Oracle_home!) then you should be able to export your 8.0.5 database from the sun server via a client if you wish.
I too agree with Skandalam's comment. But Skandalam in your comment you stated like this -- 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
backwards-compatible to an older database, it is often necessary to shuffle versions of executables and scripts. --
What exactly I need to do now. Where do I need to run the catexp.sql and on which version of database.
I misunderstood your question at first, so my first comment was not helpful.
If you install Oracle8i software on the Sun server, you should be able to export the NT server from there, if you want to.
Wouldn't it be simpler though to do the export directly on the NT server, then copy or FTP the dump file to the Sun server?
Sorry for putting u into confusion. Infact I am able to take export of oracle 8i database which is on NT. But the problem is : I 've to set up a cron job on NT to do this export on a daily basis. But as I already have 100's of other batch processes running on NT box all through the night, I don't want to put any more on it. Hope now U have understood the back ground of my problem.
Ok, if you could do the Oracle export from another computer that would mean only one less job to schedule on NT (and that seems like a very small advantage) but it could likely add significantly to network traffic during the export. The Oracle database on NT has to at least read all of the Oracle data for the export anyway regardless of which machine initiates the job.
Is the number of batch jobs and their I/O requirements so high on the NT server that offloading writing of the export dump file to another machine will help? Are you sure that the network connection will not be a bottleneck during the export? Are there any other processes generating network traffic at the time that may be impacted?
Business Accounts
Answer for Membership
by: skandalamPosted on 2000-08-03 at 20:26:54ID: 3766212
This is because the export views in both systems are slightly different.
I am assuming you got this error while doing a full export. And it would occur while exporting tablespace definitions. Right?
I also assume that you do not get this error if do user level/table level export.
Here is what Oracle says about it's export views.
Export views, created by the "CATEXP.SQL" script, are internal views used by
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
Oracle Development.
The export views are not static from version to version of Oracle. As new
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
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
backwards-compatible to an older database, it is often necessary to shuffle
versions of executables and scripts.