5/16/2024 8:40:26 AM
|
| |
| slxdeveloper.com Community Forums |
|
| |
|
|
The Forums on slxdeveloper.com are now retired. The forum archive will remain available for the time being. Thank you for your participation on slxdeveloper.com!
Forum to discuss using the SalesLogix OLE DB Provider from external applications (including usage of built-in provider procedures). View the code of conduct for posting guidelines.
|
|
|
|
errors in slx_DBIDs
Posted: 07 Aug 06 3:50 PM
|
fiogf49gjkf0d We are getting the following error when trying to add an order in SLX. It seems to me that we have too many people competeing for unique table IDs. Is there some limit as to how many users there can be in Saleslogix at one time? We have over 150. Can I change the number of IDs to get at each time to say 100 or 1000 to increase performance. Our log files are full of table deadlocks and timeouts trying to add new records.
Source : odbcdrv_open_cursor
Description : Access violation.
SQL : slx_DBIDs('tablename', 10)
or
spGetNewSequenceNumber : Transaction (Process ID 216) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
thanks, |
|
|
|
Re: errors in slx_DBIDs
Posted: 07 Aug 06 4:01 PM
|
fiogf49gjkf0d You certainly can generate many more ID's at once, in fact, if you're inserting in a large batch of data, I would recommend it.
The second parameter for slx_dbids is the number of ID's to create. The way that works is it grabs the last value from the sitekeys table (for the passed tablename and sitecode of the local system), increments it by the value passed as the second parameter and then writes it back and opens the data set of created ID values. So it does improve performance as you are reducing the trips to that table and also the locks placed on the table. Give that a try and your errors will likely go away. However, based on the error message you posted, it looks like you are pre-6.2 (ie: 6.0-6.1). The OLEDB provider was problematic in those versions and rewritten for 6.2 so you are likely to still see some weirdness like this from time to time, that is, until you upgrade to 6.2 or higher  |
|
|
| |
|
Re: errors in slx_DBIDs
Posted: 07 Aug 06 4:24 PM
|
fiogf49gjkf0d No, I wouldn't think so. Locks to the sitekeys table occur when a new ID is created. It is not likely that all 150 users are creating a new record all at once to cause an issue (if this were the case you'd likely have users getting similar errors while using SLX, not just from your app) |
|
|
|
Re: errors in slx_DBIDs
Posted: 07 Aug 06 4:32 PM
|
fiogf49gjkf0d
While I have not seen this error it does ring a bell. What is the version/servicepack/hotfix level of your SLX?
Is you backend Database Oracle or SQL?
|
|
|
|
You can
subscribe to receive a daily forum digest in your
user profile. View the site code
of conduct for posting guidelines.
 Forum RSS Feed - Subscribe to the forum RSS feed to keep on top of the latest forum activity!
|
|
|
|
|
|
|
|