Oracle Export Problem

[Karthik S S]

Hi,

Recently we applied Oracle 8.1.7.4 patchset to the Oracle 8.1.7 installation. After this whenever we try to do a export we get the following error. What could be the problem??. Kindly let me know.

Thanks
Karthik


Connected to: Oracle8i Enterprise Edition Release 8.1.7.4.0 - Production
With the Partitioning option
JServer Release 8.1.7.4.0 - Production
Export done in US7ASCII character set and US7ASCII NCHAR character set

About to export specified users ...
. exporting pre-schema procedural objects and actions
. exporting foreign function library names for user SYSTEM
. exporting object type definitions for user SYSTEM
About to export SYSTEM's objects ...
. exporting database links
. exporting sequence numbers
EXP-00008: ORACLE error 904 encountered
ORA-00904: invalid column name
EXP-00000: Export terminated unsuccessfully

[Steven E. Protter · Accepted solution]

Oracle has different issues on different platforms.

Please specify the version of HP-UX and how many bits 32 or 64 you are running.

The problem could be almost anything.

Are you current with Oracle patches for the os? That are required? Java?

The checklist is long and any of these things could be the problem.

metalink seems to indicate on previous versions that this problem can be respository issues. There are special procedures for migrating a repository.

From metalink....

These errors occur when the 8.1.7 import and export utilities are used against an Oracle 8.1.6 database. If your repository is installed on an Oracle 8.1.6 database, do not install the import and export utilities from the Designer CD, instead install from oracle 8.1.6 CD.

Reference:
==========

CDR-22582 when exporting repository data from an Oracle 8.1.6 database

Regards,

Check your version numbers and source for export/import utilities and if this is a repository plan on not seeing your family for a few weeks and logging a long itar at metalink.

P

[Karthik S S]

Hi,

hp-ux version is 11.11, 64 Bit. I am not sure if I am current with the patches for Oracle 8.1.7. Where can I find them?? . Pl let me know.

Thanks
Karthik

[Steven E. Protter]

A little more reading has led me to believe this issue is caused by using 8.1.7 export utilities to export a 8.1.6 database.

What was your previous version number of Oracle?

Did you migrate the data? There is a procedure for that.

If you went 32 to 64 bit there is a special procedure with regards to 32 to 64 bit word size.

Its critical you are current on OS patches required for oracle, java and patches required for java.

See this metalink note.
http://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=43507.1

email me if you need the text, Oracle gets cranky when I post it.

http://www.hp.com/go/java for the java patches

Currently only 1.2 and 1.3, NOT 1.4 are certified with Oracle.

Required patches
http://www.hp.com/products1/unix/java/infolibrary/patches.html

swlist PH##_##### to see if the patch is installed. Pay attention to OS, and java version.

Get the patches from ITRC

choose individual patches, search the ones
you need, download them into a patches.zip file

Put it in its own little directory

unzip patches.zip

create_depot_hp-ux_11 -d /loc_or_a_new_patch_depot

swinstall -x autoreboot=true -x reinstall=false -s /loc_or_a_new_patch_depot \*

Obviously you don't want to do this on a production system except when you can down it.

You need to have all your bases covered so Oracle will work on problem when you call instead of making you check this stuff.

P

[Karthik S S]

Hi Stevan,

Thanks a ton for your quick response. Time being I have fixed the problem using a workaround suggested by oracle, i.e, Used export utility of Oracle 8.1.7.

http://metalink.oracle.com/metalink/plsql/showdoc?db=Bug&id=2534916

However, as you suggested I will go through the patches required for hp-ux and install them so that I can avoid any potetial problems in the future.

Thanks once again,

Karthik

[Brian Crabtree]

What you need to do is run the $ORACLE_HOME/rdbms/admin/catexp.sql script to relink the export views from 8.1.7.0.0 to 8.1.7.4.0. This should resolve this problem.

Brian