RE: dbimport - Long Transaction Aborted

The informix configuration has been basically left alone since we set up the system because it is not under a real heavy load. Our main database does not handle transactions so our logical logs do not fill up very quickly hence we never increased their size. I will increase the logs and see if that solves the problem. Thank you for the response. SHARED MEMORY: Make desired changes and press ESC to record changes. Press Interrupt to abort changes. Press F2 or CTRL-F for field-level help. SHARED MEMORY PARAMETERS Server Number [ 0] Server Name [ol_ortho ] Server Aliases [ol_ortho1 ] Dbspace Temp [tempdbs ] Deadlock Timeout [ 60] Secs Number of Page Cleaners [ 10] Forced Residency [N] Stack Size (K) [ 32] Non Res. SegSize (K) [ 8192] Optical Cache Size (K) [ 0] Dbspace Down Option [2] Preserve Log For Log Backup [Y] Heterogeneous Commit [N] Transaction Timeout [ 300] Physical Log Buffer Size [ 64] K Long TX HWM [ 50] Logical Log Buffer Size [ 64] K Long TX HWM Exclusive [ 60] Max # of Logical Logs [ 30] Index Page Fill Factor [ 90] Max # of Locks [ 7000] Add SegSize (K) [ 8192] Max # of Buffers [ 35000] Total Memory (K) [ 0] Resident Shared Memory size [ 78842] Kbytes Page Size [ 2] Kbytes nter a unique value to be associated with this version of INFORMIX-OnLine. >-----Original Message----- >From: abhay@cheerful.com [mailto:abhay@cheerful.com] >Sent: Friday, April 16, 1999 3:23 PM >To: BKarsten@OLGC.COM >Cc: informix-list@iiug.org >Subject: Re:dbimport - Long Transaction Aborted > > >>I am trying to use dbimport to make a copy of my >>database. This worked just >>fine 2 weeks ago. I received the following error from >>dbimport while it is >>running "create unique index": >> >> 458 - Long Transaction aborted. >> >>We are running Informix 7.23.UC2 on SunOS 2.5.1 >>My database is getting close to 2 gig overall, but >>none of the individual >>tables are over 600 meg. >>I have plenty of disk space allocated to the dbspace. >>I have ontape -c running to tape and onstat -l says >>that all logs are backed >>up. >>Any help or suggestions on where to start to look for >>the problem is >>appreciated. >>Brock J. Karsten >>Systems Manager >>1275 W Washington St. >>Tempe, AZ 85281 >>(800) 937-5520 x5356 >>(602) 286-5356 >>Fax: (602) 231-6496 >>bkarsten@olgc.com >> <<Karsten, Brock (E-mail).vcf>> >> - Karsten, Brock (E-mail).vcf >The ontape -c to tape is not going to help u >in avoiding long transactions. >It must be baking up the logical logs. >But backing up the logical logs has nothing to >do with the Long Transaction. >Check ur Long Transaction parameters in onconfig. >Add logical logs to increase the logical log space. >Can u send onconfig file ? >Abhay Mannur. >--------------------------------------------------- >Get free personalized email at http://www.iname.com