Oracle export error

[Adrian Sobers2]

Whenever I try to run the export utility on Oracle (8.1.7.4, HP-UX 11.11) I get the following error:

Export: Release 8.1.7.4.0 - Production on Thu Jul 20 11:02:47 2006

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


Connected to: Oracle8i Enterprise Edition Release 8.1.7.4.0 - 64bit Production
With the Partitioning option
JServer Release 8.1.7.4.0 - 64bit Productionexport_base.sh[14]: 27333 Bus error(coredump)
oracle:PRODUCTION>

Any ideas as to what might be causing this?

[Steven E. Protter]

Shalom,

Missing oracle patch can cause it.

Missing OS patch can cause it.

http://www.google.com/url?sa=t&ct=res&cd=1&url=http%3A%2F%2Farchives.neohapsis.com%2Farchives%2Fhp%2F2000-q4%2F0089.html&ei=JY-_RI2GE5_M2wLvy9nJCQ&sig2=r6kWk9WubFINSMpaWf_-2A

Most likely you need a patch dealing with the export utility.

Since java is involved, make sure that is patched and is a supported version from oracles standpoint.

SEP

[Adrian Sobers2]

All of the latest OS and DB patches have been applied. Is there a specific patch for java or something for HP-UX that I need?

[Peter Godron]

I support Steven analysis, but could you please also post the code for export_base.sh ?

[Adrian Sobers2]

#!/usr/bin/ksh
#==============================================================================#

SID=IRDS
JOUR=`date '+%d%m'`

# remove the previous export..
rm /opt/oracle/data/Exports/${SID}????.dmp

# this is for a FULL DATABASE export
#exp userid=system/manager full=y file=/opt/oracle/data/Exports/${SID}${JOUR}.dmp log=/opt/oracle/data/Exports/${SID}.log

# this is for a schema level export for the IRDS database
exp userid=ird/ird2006ADm owner=ird file=/opt/oracle/data/Exports/${SID}${JOUR}.dmp log=/opt/oracle/data/Exports/${SID}.log

[Patti Johnson]

Adrian,

Anything in the alert.log (ora-7445 perhaps). Also does it fail when you try and export only one table? Another schema?

Local or remote db that you are exporting from?

Patti

[Adrian Sobers2]

Patti,

Nothing in those files at all.

It fails when I try to export another schema, table level only etc. I've been through all of that with an Oracle rep. They are still 'researching' the problem. I just wondered if anyone had come across this error before.

[Peter Godron]

Adrian,
can you check the dates on the files in $ORACLE_HOME/bin . Could somebody have slipped in a different version of exp?

[Patti Johnson]

Guessing this worked before. Have you tried to relink the exp binary?

[TwoProc]

I think I saw this back then when two objects of different types had the same name. I believe the conflict was between table names and trigger names.

Do you have triggers that have the same name as tables? If so, change the trigger name, and retry.

to locate candidates for further review:

select object_name,count(*)
from dba_objects
group by object_name
having count(*) >1;

check what comes out of here, and see if there are triggers with the same name of tables.

[Adrian Sobers2]

Yes this used to work before, it stopped only after I applied the April 2006 CPU patch update...

I checked the date, and also did the relinking of the exp whilst trouble-shooting with Oracle Rep. and that didn't solve the problem.

[Patti Johnson]

Any invalid objects? Possibly the ones for export/import. Have they suggested backing out the patch?
I'd consider running $O_H/rdbms/admin/catexp to recreate the export objects.

Patti

[Adrian Sobers2]

Patti,

Backing out of the patch didn't help at all.

I will try running the script you recommended.

[Adrian Sobers2]

Patti,

Running that script didn't help either.

Isn't there something wrong on the HP-UX OS side since the error involves, a Bus error (core dump)?

[Patti Johnson]

Do you get any messages from export before the Bus error ? Does it produce a core file - have you tried to ananlyze the core file?
What about other tools - sqlplus, imp ? can these tools run?
Did any of you environment variables change?
Also have you tried direct=y for the export.

[TwoProc]

Since you're on an unsupported version (and you're not going to get any help from Oracle on this) - try running the export from another ORACLE_HOME. Maybe on another HPUX, Linux or Windoze box hooked to that database via sqlnet. It could be that you can export just the troublesome sections from a remote connection - or, even the whole thing if need be.

[Adrian Sobers2]

Patti,

All of the other utilities run fine, except the export.

Oracle is analyzing the core dump.

I will try the remote connection export thingy ;)

[TwoProc]

Wow Adrian, I'm absolutely amazed that they are helping you on a version that is no longer supported. Cool though!