RE: Named user lock facility in IDS?
This is a discussion on RE: Named user lock facility in IDS? within the Informix forums, part of the Database Server Software category; --> David, So what you're trying to do is use the database to contain data so that your external applications ...
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
04-20-2008, 04:05 PM
| ||||
| ||||
 RE: Named user lock facility in IDS? David, So what you're trying to do is use the database to contain data so that your external applications can do some form of mutex locking? __________________________________________________ _______________ http://liveearth.msn.com      |
|
04-20-2008, 04:05 PM
| ||||
| ||||
| Re: Named user lock facility in IDS? On Jul 23, 4:07 pm, "Ian Michael Gumby" <im_gu...@hotmail.com> wrote: > David, > > So what you're trying to do is use the database to contain data so that your > external applications can > do some form of mutex locking? > > __________________________________________________ _______________http://liveearth.msn.com I think that the Gumby's got it. You should be using system semaphores or global mutex locks for this. Also any database without logging (ie without transactions) is HIGHLY at risk for catastrophic data loss! If you can turn logging/ transactions on for those databases at once! If your apps are not properly written to handle locking then recode the immediately and turn logging on ASAP. You may also be able to take advantage of IDS 11 (Cheetah)'s new isolation level (COMMITTED READ ... LAST COMMITTED) to avoid concurrency and lockout issues while maintaining data integrity and safety with minimal recoding. Art S. Kagel |
Linear Mode
