Balakrishnan wrote: > > I have a problem with SAP DB 7.3. > Our application uses JDBC for connecting the SAP DB. > After running our application around 2 weeks, suddenly > error "Connection down, session released" is thrown from > the SAP DB whenever a new connection is tried to open. > This error message is thrown in the midst of updation/insertion > sequence and not accessing the database after idle time. > > This error message is given for around 1 1/2 hours > from SAP DB whenever a new connection is tried to open. > After that SAP DB gives up by asking to restart > (-813, Restart Required). > > I searched the mailing lists and the solution that was > provided was to COMMIT RELEASE the session from time to time. > Our application uses POOLMAN for caching the connections > and the connection timeout is set to 20 minutes. So for > every 20 minutes the connections will be closed by the POOLMAN and > new connection will be opened. Also our > application will send only around an average of 5-10 SQL > statements before making a commit or rollback. > > The parameters SESSION_TIMEOUT set to 0(for no timeout as specified > in the documentation), MAXUSERTASKS is set to 150 > and MAXSERVERTASKS is set to 30. > > Is there any option or parameter that need to be changed > to avoid this problem? > > Please let me know if you need more information.
At that time when -813 is returned: Is your kernel in the state OFFLINE / COLD ? Then please provide the knldiag, which will help us to see what may have happened. Perhaps afterwards we will need some more info, but let us start with this. If you can provide the exact statements (the last working fine, the first resulting in such an error), this may help, too. Elke SAP Labs Berlin _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
