What went wrong ?

[Former Member]

Dear all,

I`m trying to figure out what went wrong with my database.

During the higher load the users were suddenly getting DBIF_RSQL_SQL_ERROR, no matter what they wanted to do. When checking system I found many messages like:

Database error -1000 at OPC access to table REPOLOAD

> POS(1) Too many lock requests

> Include ??? line 0000.

Run-time error "DBIF_REPO_SQL_ERROR" occurred

Run-time error "DBIF_RSQL_SQL_ERROR" occurred

Database error -1000 at OPC

> POS(1) Too many lock requests

Database error -1000 at OPC

> POS(1) Too many lock requests

Database error -1000 at OPC

> POS(1) Too many lock requests

Database error -1000 at EXE

> POS(1) Too many lock requests

According to documentation I found error -1000:

1000: Too many lock requests

Explanation

There are too many locks or lock requests.

User Request

You can try to repeat the SQL statement at a later time or cancel the transaction. If this situation occurs frequently, then the MAXLOCKS general database parameter is too small and should be increased

Database kernel showed following messages:

2009-12-07 16:04:18 8126 ERR 5 Catalog Catalog update failed,IFR_ERROR=-1000,DESCRIPTION=UNDEFINED

2009-12-07 16:05:13 8170 ERR 5 Catalog Catalog update failed,IFR_ERROR=-1000,DESCRIPTION=UNDEFINED

2009-12-07 16:10:13 8182 ERR 5 Catalog Catalog update failed,IFR_ERROR=-1000,DESCRIPTION=UNDEFINED

2009-12-07 16:15:09 8229 ERR 5 Catalog Catalog update failed,IFR_ERROR=-1000,DESCRIPTION=UNDEFINED

2009-12-07 16:15:13 8123 ERR 5 Catalog Catalog update failed,IFR_ERROR=-1000,DESCRIPTION=UNDEFINED

So do you think it is just about MAXLOCKS parameter or also with catalog cache sizing could be wrong ?

Version : MaxDB 7.6.6.7.

Thank you for your comments.

Pavol

[lbreddemann]

> Database error -1000 at OPC

> > POS(1) Too many lock requests

> 1000: Too many lock requests

> Explanation

> There are too many locks or lock requests.

> 2009-12-07 16:04:18 8126 ERR 5 Catalog Catalog update failed,IFR_ERROR=-1000,DESCRIPTION=UNDEFINED

> So do you think it is just about MAXLOCKS parameter or also with catalog cache sizing could be wrong ?

> Version : MaxDB 7.6.6.7.

Hi there,

it's really just about the MAXLOCKS setting.

As you seem the "Catalog update failure"-message also points out error no. -1000.

It's the same "too many lock requests" error as before.

Having a MAXLOCKS value of 1.000.000 or even 3.000.000 is not unusual with MaxDB!

regards,

Lars

[Former Member]

Btw, MAXLOCKS was set to 600 000, now I set it to 1 000 000.