gpw7368
asked on
ASE running out of locks
I have an application which i migrated from EA server to weblogic. it is using sybase database.
Now applicataion runs fine on Sybase ea server but throwing an error on weblogic when application is updating one table.
That table is huge it has totalrow 166957279.
Error is :
run():SQLException
com.sybase.jdbc2.jdbc.SybS
mand when there are fewer active users, or contact a user with System Administra
tor (SA) role to reconfigure ASE with more LOCKS.
at com.sybase.jdbc2.tds.Tds.p
at com.sybase.jdbc2.tds.Tds.n
at com.sybase.jdbc2.tds.TdsRe
at com.sybase.jdbc2.tds.TdsRe
at com.sybase.jdbc2.jdbc.SybR
at weblogic.jdbc.wrapper.Resu
xt(Unknown Source)
Please help me resolve this error
Now applicataion runs fine on Sybase ea server but throwing an error on weblogic when application is updating one table.
That table is huge it has totalrow 166957279.
Error is :
run():SQLException
com.sybase.jdbc2.jdbc.SybS
mand when there are fewer active users, or contact a user with System Administra
tor (SA) role to reconfigure ASE with more LOCKS.
at com.sybase.jdbc2.tds.Tds.p
at com.sybase.jdbc2.tds.Tds.n
at com.sybase.jdbc2.tds.TdsRe
at com.sybase.jdbc2.tds.TdsRe
at com.sybase.jdbc2.jdbc.SybR
at weblogic.jdbc.wrapper.Resu
xt(Unknown Source)
Please help me resolve this error
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Running the same code through two different middle layers does not mean the same SQL is being sent to the Sybase back end.
Almost certainly there are connection profiles and transaction management settings you will need to look at more closely in Weblogic.
A table lock isn't "better" than a page lock - there is no one size fits all here. It might've helped you here because it would allow the table to be locked with just one lock rather than many, which would help resolve running out of locks. It could cause other problems for you though.
Almost certainly there are connection profiles and transaction management settings you will need to look at more closely in Weblogic.
A table lock isn't "better" than a page lock - there is no one size fits all here. It might've helped you here because it would allow the table to be locked with just one lock rather than many, which would help resolve running out of locks. It could cause other problems for you though.
The problem with using table locks is that can prevent concurrent access to data in the table - however, if your process is using up all available locks, it is probably locking most or even all the table anyway.
As Joe said, the application may well be sending somewhat different sql to the server. You can have a look at what is being sent by using the MDA tables monProcessSQLText and monSysSQLText.
As Joe said, the application may well be sending somewhat different sql to the server. You can have a look at what is being sent by using the MDA tables monProcessSQLText and monSysSQLText.
ASKER
Lock type = sh_page.
is table lock is better than this?
Also now it is not throwing out of locks error anymore. But it is pretty slow. It is inserting one row at every 45 seconds on avg when running on weblogic. Weblogic is supposed to be faster than EA server.
I dont understand why it is so slow on weblogic and so fast on ea server. The application code and database both are same. The application is running on weblogic since friday and it hasnt completed yet.
While on easerver it only takes 3-4 hours.
Please help me with this..thanks