Re: Enterprise Replication & Locks

On 27 Mar 97 at 18:34, stiglich@promarkone.com wrote: > I did an onstat -k after this happened and it only showed a few > locks ( on tblspace 100002 only). I bumped up the number of locks > to 100000 and it worked fine. Yes, the locks get released "immediately" the transaction fails. It is difficult to assess why you are using so many locks with the information to hand, but here are a few thoughts: 1. If you have any referential constraints involving the table you are loading, (potentially many) extra locks will be acquired. 2. Try locking the table EXCLUSIVE before doing the load. 3. Try using dbload and committing every 1000 records or so (-n 1000). 4. If your database has logging, committing every N records will load your table up faster, but you can only do this with dbload. 5. Check your release notes for the maximum number of locks for your port. They're in $INFORMIXDIR/release/* HTH. -- Ciao, Billy Vandag is ek in: Kuwait City Q: Why do they call camels "ships of the desert"?