Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Strange GM Behavior-Any clues?

Status
Not open for further replies.

Drakhan

Technical User
Jun 3, 2002
67
0
0
US
This error occured literally "out of the blue". Here is the enviroment:

Software:
GM 5.7.2404
Windows 2000 Server
SQL 7.0 SP3

Hardware:
Quad Xeon
2 GB RAM
60 GB HD

Users:
350 Users

We have begun to receive the following SQL error at logon:

General SQL error.

Native SQL error: 8645

Context: goTop

MSSQL: GoldMine_SM: dbo.CONTUDEF

1: Server message: A time out occurred while waiting for memory resources to execute the query. Rerun the query.

BDE Error Cat:Code: [51:3]

BDE: 500 [21/6/1999] GoldMine: 5.70.20404

User: MASTER

Window: &Cancel

Template: 7169

Details:

NATIVEMSG: A time out occurred while waiting for memory resources to execute the query. Rerun the query.

Other symptoms
From the SQL DBA:
This table had almost 50,000 locks on it a few minutes ago. There was
blocking on this table as well. It dropped down to 3900 and now it's on
it's way back up. You may want to schedule a reboot for tonight and see if
things improve tomorrow. Is it normal for 10 processes to 50,000 locks i.e each connection is locking about 5,000 rows in the CONTACT1 table.

More from the SQL DBA:
I'm still seeing a massive number of locks on the CONTACT1 table. There are two connections are running updates that are being blocked by selects.

UPDATE dbo.CONTACT1 SET NOTES=NULL,LASTTIME='08:54' WHERE RECID='92U367R&SP7I W<' AND LASTTIME='08:47' Running since 7:01 AM

UPDATE dbo.CONTACT1 SET LASTUSER='E042577',LASTDATE='20030627 00:00:00.000',LASTTIME='07:56' WHERE RECID='9L52YD3#^B;,^C]' AND LASTUSER='#332152' AND LASTDATE='20030613 00:00:00.000' AND LASTTIME='09:49' Running since 8:55 AM

The select currently has ~4000 row locks on the table.

Thanks in advance for any suggestions or help!
 
Drakhan,

I think SQL 2000 might well help with this.

Also in the BDE alias make sure the MAXDBPROCESS is set high I'd suggest 5 per connected user.

I'd also consider droping and recreating the indexes.

Regards,

Richard.
PRIOR Analytics UK
 
Thanks for your assistance Richard - I'll go ahead and try that!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top