Home > Server Error > Server Error 1204 Severity 17 State 2 Occurred

Server Error 1204 Severity 17 State 2 Occurred

Extra or invalid key for the keys:Server: Msg 8956, Level 16, State 1, Line 1Index row (1:3362:61) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 223000) points I got the following error on a dev server: Error: Number (1204) Severity (17). Click more to access the full version on SAP ONE Support launchpad (Login required). Possible chain linkage problem.Server: Msg 8978, Level 16, State 1, Line 1Table error: Object ID 18099105, index ID 1. navigate here

Does anyone have any ideas what might be going on? Possible chain linkage problem.Server: Msg 8981, Level 16, State 1, Line 1Table error: Object ID 18099105, index ID 1. Re-run your command when there are fewer active users, or contact a user with System Administrator (SA) role to reconfigure SQL Server with more LOCKS. Did anybody ever run into a similar situation?

Another question is that when the number of locks is set to 10,000, I run sp_lock while the code is running and the number of rows returned was often over 10,000. The problem I am running into is running out of locks all the time with 50000 locks. Rerun your statement when there are fewer active users. Warning: sybase_query(): Sybase: Server message: SQL Server has run out of LOCKS.

Privacy statement  © 2016 Microsoft. Client IP address is 'XXXX'. 00:00000:00048:2006/03/03 07:32:13.82 server SQL Text: sp_lock 00:00000:00071:2006/03/03 07:32:13.82 server Error 1204, Severity 17, State 2 occurred for User 'XXXX'. I set it to 15,000 and ran the same code: Same error. This is an internal system error.

but it didn't have an answer. Still, I didn't get the error. SQL Server has run out of LOCKS. http://sfh01.sapdevcenter.com/nntp-archive/action/article/%[email protected]%3E Extra or invalid key for the keys:Server: Msg 8956, Level 16, State 1, Line 1Index row (1:3364:41) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070717 and BEGIN_TIME = 130000) points

A colleague suggested that installing service packs may take care of it (the client is running SQL Server 2008 R2 (RTM)), but I haven't found anything online to support that theory. Choose the number of locks you want to configure and issue this command: 1> sp_configure "number of locks", 2> go Because the number of locks parameter is dynamic, you do Extra or invalid key for the keys:Server: Msg 8956, Level 16, State 1, Line 1Index row (1:3362:10) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 193000) points you have ASE level settings for them also .

Extra or invalid key for the keys:Server: Msg 8956, Level 16, State 1, Line 1Index row (1:3362:75) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 234500) points https://apps.support.sap.com/sap/support/knowledge/preview/en/1924859 Moreover, this didn't even happen on SQL Server but Sybase 11.9. Extra or invalid key for the keys:Server: Msg 8956, Level 16, State 1, Line 1Index row (1:3362:46) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 213000) points Possible chain linkage problem.Server: Msg 8978, Level 16, State 1, Line 1Table error: Object ID 18099105, index ID 1.

The table that is being manipulated looks something like this create table LotLineInfo( LineIDNo numeric (10, 0) identity , LotID int NULL, LineNo int NULL, Step varchar (30) NULL, StepTime varchar check over here All new questions should be directed to the appropriate forum at the SAP Community Network (SCN). Extra or invalid key for the keys:Server: Msg 8956, Level 16, State 1, Line 1Index row (1:3362:59) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 223000) points Forums Archive > ASE > Administration > "Error 1204 Locks" Error 1204 Locks 6 posts in Administration .

WARNING! Before making any changes to Adaptive Server, refer to the chapter “Memory Use and Performance” in the Performance and Tuning: Basics and the chapter “Configuring Memory” in the System Administration Guide: I am kind of pressed for time and hoping I don't have to resort to a stored procedure right now. Extra or invalid key for the keys:Server: Msg 8956, Level 16, State 1, Line 1Index row (1:3362:4) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 191500) points his comment is here I set it to 5000, and it still didn't seem to work.

Extra or invalid key for the keys:Server: Msg 8956, Level 16, State 1, Line 1Index row (1:3364:47) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070717 and BEGIN_TIME = 131500) points Extra or invalid key for the keys:Server: Msg 8956, Level 16, State 1, Line 1Index row (1:3362:34) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 204500) points Extra or invalid key for the keys:Server: Msg 8956, Level 16, State 1, Line 1Index row (1:3362:22) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 200000) points

The Memory Used column indicates the amount of memory used by the configured locks.

Could someone be running a robot to tie up SQL? Anybody knows why? But there is a page where multiple records are updated individually and then one of these records is updated again in a following sql statement. Prior to changing the locking mechanism 10,000 locks were more than enough.

Page (1:2669) is missing a reference from previous page (1:3126). Check your lock escalation, as the number and type (page/extent etc) of locks acquired will depend upon several factors. The server is > currently > configured for 22000 locks (but we've been increasing this > value > steadily over the past few weeks). weblink Any ideas on what to look for?

Once we increase the > locks we > have a few days where early morning processing does not > run out > of locks and then we see the 1204 again. Extra or invalid key for the keys:Server: Msg 8956, Level 16, State 1, Line 1Index row (1:3362:6) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 193000) points Extra or invalid key for the keys:Server: Msg 8956, Level 16, State 1, Line 1Index row (1:3362:3) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 191500) points It seems strange that it used not to work at 10,000 locks (repeatedlly) but once I set the number of locks to 20,000 once, then it worked with the number of

Search for additional results Visit SAP Support Portal's SAP Notes and KBA Search. Once we increase the locks we have a few days where early morning processing does not run out of locks and then we see the 1204 again. All rights reserved.Terms of Use|Trademarks|Privacy Statement|Site Feedback SAP Knowledge Base Articles - Preview 1924859 - 1204 Out of LOCKS Error followed by 3914 Error causes blocking on server - ASE 15.7 Versions in which this error is raised All versions Copyright © 2008.

Extra or invalid key for the keys:Server: Msg 8956, Level 16, State 1, Line 1Index row (1:3362:47) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 213000) points number of records is 1 million.Error code is 1204, "SQL Server has run out of LOCKS".But when we increase the number of locks, we get another error message which says this