I had this kind of problem when working with large amount of commands
(>20000) inside batch files and getting out of locks.
Another app had this kind of problem because not closing the connection.
Since you have not specified the DB version, neither what interface you are
using, I'll try to help with my personal experience with Java and the way I
work to avoid this kind of trouble:
// declare your db related here, to be accessible in finally clause
java.sql.Connection cn = null;
java.sql.Statement st = null;
java.sql.ResultSet rs = null;
try {
// put here the code to open the connection, statement, result set and so
on.
// don't close anything here, because you are closing all in the finally
clause.
} catch( Exception e ) {
e.printStackTrace(); // put your exception treatment here
} finally {
// Close first the resultset, then statement and then connection.
// I don't know if this affects SapDB, but solves a
// well known bug in Oracle (don't remember version).
try { rs.close(); } catch( Exception e1 ) {}
try { st.close(); } catch( Exception e1 ) {}
try { cn.close(); } catch( Exception e1 ) {}
}
This will guarantee that the connection is being released. Always.
I expect this help.
Best regards,
Edson Richter
----- Original Message -----
From: "D�hr, Markus IDV" <[EMAIL PROTECTED]>
To: "'Sue Hubbard'" <[EMAIL PROTECTED]>;
<[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Tuesday, July 01, 2003 8:03 AM
Subject: RE: Max Performance of Sapdb
> We've created a sapdb which handle 500 transations per second
> (combination of inserts/updates/deletes) it handles it for
> about 15-20 minutes and then freezes with no error messages.
> We've verified that we have not run out of disk space, dev
> space, log file space, memory and cpu usage.
- Which version are you using (7.3 or 7.4)?
- what's the output of "dbmcli -u <controluser,controlpw> <SID> show active"
when the DB 'hangs'
The only thing I can imagine (beyond a software bug) is some deadlock that's
not detected or you're running out of DB locks. Is there something in
knldiag or knldiag.err when it's hanging?
> Is there a limitation on how many (simple -- no joins)
> transactions per second can be applied? We need to get it up
> to 2000 per second. We've only started testing with sapdb
> and have limited knowledge of the parameters.
There's nothing like a "soft limit". It depends on how you have built your
DB, how many devspaces you have (one big or several little ones), how big
your DATA_CACHE/CACHE_SIZE is and other things. Can you sum your config
here, probably someone has some ideas what you can try.
Greetz,
SIEGENIA-AUBI KG
Informationswesen
i.A.
Markus D�hr
SAP-CC/BC, SAPDB-DBA
Tel.: +49 6503 917-152
Fax: +49 6503 917-7152
E-Mail: [EMAIL PROTECTED]
Internet: http://www.siegenia-aubi.com
_______________________________________________
sapdb.general mailing list
[EMAIL PROTECTED]
http://listserv.sap.com/mailman/listinfo/sapdb.general
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.495 / Virus Database: 294 - Release Date: 30/6/2003
_______________________________________________
sapdb.general mailing list
[EMAIL PROTECTED]
http://listserv.sap.com/mailman/listinfo/sapdb.general
