Deadlock question

Broad question. Are there any settings in the onconfig, that if not properly set, could lead to an increase in deadlock issues (showing a LOT of -243's and -154's) . I just upgraded to 9.30.FC3 and I am seeing an awful lot of dead locks... Just wondering. -- Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/

Jason wrote: > Broad question. > > Are there any settings in the onconfig, that if not properly set, could > lead to an increase in deadlock issues (showing a LOT of -243's and > -154's) . > > I just upgraded to 9.30.FC3 and I am seeing an awful lot of dead locks... > > Just wondering. > > > 154 means a distributed deadlock. This you change your environment, or created synonyms? TXTIMEOUT (onconfig setting) is used to control the deadlock timeout for distributed transactions. Are your tables lock level the same as before? I believe 9.30 has a setting for default table lock level if not specified at creation time. Don't remember the setting but it should be mentioned in the release notes. Regards

Have you done a dbexport/dbimport? Is the lock mode for your tables still set to row, rather than page, level? -- Neil Truby t:01932 724027 Director m:07798 811708 Ardenta Limited e:neil.truby@ardenta.com "Jason" <emailsucks@email.com> wrote in message news:oprsop0jt4luby4m@news.email.com... > Broad question. > > Are there any settings in the onconfig, that if not properly set, could > lead to an increase in deadlock issues (showing a LOT of -243's and -154's) > . > > I just upgraded to 9.30.FC3 and I am seeing an awful lot of dead locks... > > Just wondering. > > > > -- > Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/