Informix 5.02.UC1 gives problems with dbimport

Hi All I am running Informix 5.02.UC1 on HP-UX 9.04. For dbimporting fairly = large databases (100-150 MB), dbimport crashes midway with the error = message: sqlobj: memory allocation failed The machine has 128 MB of RAM. I dont think this should matter because = the operating system can swap out the memory that is no longer required. I dont know if I need to bump up some configuration parameter or if = there is some other alternative. When we get this problem, usually we = figure out which tables are left to be dbimported, then write a script = to upload the rest of the tables from the flat file data using SQL LOAD = commands. However we need this to work so some of our testers can = dbexport and dbimport the data whenever they need to. These testers do = not know SQL or Unix shell scripting. Heres a copy of my tbconfig file: #************************************************************************= ** # # INFORMIX SOFTWARE, INC. # # Title: tbconfig.std # Sccsid: @(#)tbconfig.std 9.1.2.1 2/4/93 12:01:23 # Description: INFORMIX-OnLine Configuration Parameters # #************************************************************************= ** # Root Dbspace Configuration ROOTNAME rootdbs # Root dbspace name ROOTPATH /dev/vg00/rdbspace1 # Path for device containing root =dbspace ROOTOFFSET 0 # Offset of root dbspace into device = (Kbytes) ROOTSIZE 35000 # Size of root dbspace (Kbytes) # Disk Mirroring Configuration MIRROR 0 # Mirroring flag (Yes =3D 1, No =3D 0) MIRRORPATH # Path for device containing root =dbspace mirror MIRROROFFSET 0 # Offset into mirror device (Kbytes) # Physical Log Configuration PHYSDBS rootdbs # Name of dbspace that contains physical = log PHYSFILE 4000 # Physical log file size (Kbytes) # Logical Log Configuration LOGFILES 5 # Number of logical log files LOGSIZE 7500 # Size of each logical log file (Kbytes) # Message Files MSGPATH /usr/informix/turbo.log_1 # OnLine message log pathname CONSOLE /dev/console # System console message pathname # Archive Tape Device TAPEDEV /dev/rmt/0m # Archive tape device pathname #TAPEDEV /dev/null TAPEBLK 1024 # Archive tape block size (Kbytes) TAPESIZE 1956084 # Max amount of data to put on tape = (Kbytes) TAPESIZE 1956084 # Max amount of data to put on tape = (Kbytes) # Logical Log Backup Tape Device LTAPEDEV /dev/null # Logical log tape device pathname LTAPEBLK 1024 # Logical log tape block size (Kbytes) LTAPESIZE 1956084 # Max amount of data to put on log tape = (Kbytes)# Identification Parameters SERVERNUM 1 # Unique id associated with this OnLine =instance DBSERVERNAME festes_1 # Unique name of this OnLine instance # Shared Memory Parameters RESIDENT 0 # Forced residency flag (Yes =3D 1, No = =3D 0)USERS 64 # Maximum number of concurrent user = processes TRANSACTIONS 100 # Maximum number of concurrent = transactions LOCKS 10000 # Maximum number of locks BUFFERS 2000 # Maximum number of shared memory =buffers TBLSPACES 800 # Maximum number of active tblspaces CHUNKS 8 # Maximum number of chunks DBSPACES 8 # Maximum number of dbspaces and = blobspaces PHYSBUFF 32 # Size of physical log buffers (Kbytes) LOGBUFF 32 # Size of logical log buffers (Kbytes)LOGSMAX 10 # Maximum number of logical log files CLEANERS 1 # Number of page-cleaner processes SHMBASE 0x0 # Shared memory base address CKPTINTVL 300 # Checkpoint interval (in seconds) LRUS 8 # Number of LRU queues LRU_MAX_DIRTY 60 # LRU modified begin-cleaning limit = (percent) LRU_MIN_DIRTY 50 # LRU modified end-cleaning limit = (percent) LTXHWM 80 # Long TX high-water mark (percent) LTXEHWM 90 # Long TX exclusive high-water mark = (percent) # Machine- and Product-Specific Parameters DYNSHMSZ 0 # Dynamic shared memory size (Kbytes) GTRID_CMP_SZ 32 # Number of bytes to use in GTRID = comparision DEADLOCK_TIMEOUT 60 # Max time to wait for lock in =distributed env. TXTIMEOUT 300 # Transaction timeout for I-STAR (in = seconds)SPINCNT 0 # No. of times process tries for latch STAGEBLOB # Reserved for INFORMIX-OnLine/Optical # System Page Size BUFFSIZE 2048 # Page size (do not change!) # End of tbconfig file If you have seen this happen, or if you have any ideas, I would = appreciate any pointers to help solve this problem. TIA Sujit Pal