From: mshields0350@my-deja.com Newsgroups: comp.databases.oracle.server Subject: Re: Oracle 8.1.6.1 import Date: Mon, 01 Jan 2001 17:51:11 GMT Organization: Deja.com Lines: 64 Message-ID: <92qg2d$82n$1@nnrp1.deja.com> References: <92oipv$vei$1@nnrp1.deja.com> NNTP-Posting-Host: 209.134.132.48 X-Article-Creation-Date: Mon Jan 01 17:51:11 2001 GMT X-Http-User-Agent: Mozilla/4.0 (compatible; MSIE 5.01; Windows NT 5.0) X-Http-Proxy: 1.1 x60.deja.com:80 (Squid/1.1.22) for client 209.134.132.48 X-MyDeja-Info: XMYDJUIDmshields0350 In article , "Richard Sutherland" wrote: > Actually, you need 65535 -- 65536 doesn't work > > Are both databases on the same OS/version? What are they? > > I tried setting the recordlength with no change in results. Here is the error message: >>>>imp sys/xxxxx file=io_data.dmp ignore=y full=y recordlength=65535 Import: Release 8.1.6.1.0 - Production on Mon Jan 1 11:40:17 2001 (c) Copyright 1999 Oracle Corporation. All rights reserved. Connected to: Oracle8i Enterprise Edition Release 8.1.6.1.0 - Production With the Partitioning option JServer Release 8.1.6.0.0 - Production Export file created by EXPORT:V08.01.06 via direct path import done in US7ASCII character set and US7ASCII NCHAR character set IMP-00046: using FILESIZE value from export file of 2147483648 . importing SYS's objects into SYS . importing DBO's objects into DBO . . importing table "ERROR_LOG" 108 rows imported . . importing table "IO_AGE" 2 rows imported . . importing table "IO_ANALYSIS"Segmentation fault (core dumped) The OS is Redhat Linux 6.2 - kernel 2.2.16-4. The hardware and operating systems are identical. The export was created with: TABLES=( about 40 tables ) ROWS=y INDEXES=n CONSTRAINTS=n STATISTICS=none GRANTS=y COMPRESS=y DIRECT=y On the same database, I have already imported a 90 Million row partitioned table with no problems. If I do the import with INDEXFILE=x, the file 'x' is truncated at: REM ... 2 rows REM CREATE TABLE "DBO"."IO_ANALYSIS" ("ID_ANALYSIS" NUMBER(8, 0) NOT NULL REM ENABLE, "ID_CLIENT" NUMBER(8, 0) NOT NULL ENABLE, "ID_UNIT_DEF" REM NUMBER(8, 0) NOT NULL ENABLE, "ID_REC" NUMBER(8, 0) NOT NULL ENABLE, Which almost makes me think that the seg fault is happening during table creation, EVEN though the table gets created in the DB correctly before the seg fault. > > Richard Sutherland > > rvsutherland@yahoo.com > > Sent via Deja.com http://www.deja.com/