Message-Id: <10708.124322@fatcity.com> From: "Jay Hostetter" Date: Tue, 12 Dec 2000 10:17:34 -0500 Subject: RE: Core Dump during Import on 8.1.6 (related to duck pecking) Scott, The path is fine. 8.0.5 was installed after the problem started. Thanks Jay Hostetter Oracle DBA D. & E. Communications Ephrata, PA USA >>> 12/12/00 09:40AM >>> What is your $PATH shell variable equal to? Sounds like you might be = trying to use the 8.0.5 imp rather than 8.1.6, due to "$ORA805_HOME/bin" being in your $PATH before "ORA816_HOME/bin". If not, do an "env" at the unix command line and check for any suspicious variables... HTH, Scott > -----Original Message----- > From: Jay Hostetter [SMTP:jhostetter@decommunications.com]=20 > Sent: Tuesday, December 12, 2000 7:51 AM > To: Multiple recipients of list ORACLE-L > Subject: Core Dump during Import on 8.1.6 (related to duck pecking) >=20 > Some consultants have arrived with an export file from a 7.3.4 = database. > We must import this file into an 8.1.6.2.0 database (identical to the > scenario that Dennis Taylor posted). Every time I import this file, I = get > a "Memory Fault (coredump)" error. There is no trace file, no alert log > entry, just a core file. > I am doing a full import. I have tried creating the schema owner and > importing using TOUSER, but I still get the coredump. I have checked > kernel parameters (this is a new system). I have relinked Oracle. I = have > increased the SGA and tablespaces, but to no avail. We installed 8.0.5 > on the same machine, and imported the file with no problem. We exported > it from 8.0.5 and tried the full import into 8.1.6, but we still get the > coredump. > I did manage to import a different export file that the consultants > brought with them (from 8.0.5) into a seperated 8.1.6 database. > I have logged a TAR, but thought I would run it by the real experts = for > some suggestions. > This is a new install of 8.1.6, patched to 8.1.6.2 on a cluster = running > Tru64 version 5.1. >=20 >=20 >=20 > Jay Hostetter > Oracle DBA