Re: dbimport causes memory fault(coredump)

Mike, I don't know if this applys to you but, I got coredumps using dbimport when my databases had large stored procedures. For some reason, our stored procedures which had 25 or more variables defined in them were causing the dbimport to dump core. My solution was to take the ".sql" file and break it into two sql files. One with the database table schema and one with the procs and triggers. Then I ran the dbimport on the table file, and ran the proc file using dbaccess. Hope this helps! Tracy Nedd tracyn@banctec.clark.net } } To all, } } I am getting a memory fault(coredump) when I do a dbimport on a specific } database. This occurs approximatley 30 seconds to 1 Minute into the dbimport. } } I am using ON-LINE DS 7.11 UC1 and ESQL/C 7.11 UC1 on an HP9000 Hp/ux 10.01. } The hardware is an HP9000 k200 with 2 processors and 896 MB of RAM. There } seems to adequate space available in the dbspace where I was importing the } databse. I even tried other dbspaces. } } The dbiport is using the following syntax: } dbimport -c -q -d dbspace -f /dev/rmt/0m -b 64 -s 2097151 database. } } I even tried dbimport from disk and I achieved the same results. } } Can anybody explain why this is happening? and how I can resolve this problem? } } Note, dbimport on other exported database work with out a PROBLEM. } } Any help is much appreciated. } } Thanks } } Mike Proulx } Systems Administrator } SSA Mid-Atlantic } }