Hi, I've a question, does anyone knows which platform is most stable for SAPDB? I've only had experience on NT 4 & Win2k Server.
Linux (Intel) Windows NT/Windows 2000 Solaris HP-UX Tru64 AIX Rgds, Joshua -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Stephen Gutknecht (SAPDB) Sent: Friday, November 30, 2001 1:37 PM To: [EMAIL PROTECTED] Subject: Production server with "-907 POS(1) Space for user session exhausted.", memory leaks? Hi, One of my production sapdb servers failed unexpectedly when sapdb started to refuse new database connections. The server is running Windows 2000 Service Pack 2 with 2GB of physical RAM. SAPDB is KERNEL 7.3.0 BUILD 008-000-054-008 - the ODBC driver was 7.02.05. The sapdb database is allocated 512MB of RAM for a database of about 3GB in size. Machine is single processor. What the server was doing ==================== I run the sapdb server and my applications on the same system. In other words, I have my applications use the ODBC driver connect to localhost. What is rather unique about my application is that I tend to execute 10,000 to 100,000 small programs that open database, execute a few SQL statements (all quick) and then close the database. So it is constantly opening up a new ADO / ODBC connection on the same computer. At the same time, I also have a couple master programs that run in an endless loop using a single ODBC open. In other words, the ODBC session is opened when the program starts and the program does a endless loop with a 30 second pause to query the database for a quick status dump (SELECT on one of my tables). I mention this, as the programs that already had the ODBC session open kept working fine, it was the programs that attempted to open new ODBC sessions that got the "-907 POS(1) Space for user session exhausted." error. Virtual and physical memory on the system were fine at the time I encountered the problem... so I am suspecting some internal problem in the sapdb or ODBC driver. I did a backup of the server at first thinking that my logs might have been full, but that did not help. I ultimately rebooted the server and everything returned to normal. Server has been production on sapdb for about 2 months, we have not had any problems like this before. Server was only at 1/2 load ===================== What was also interesting was that the server was only running at about 1/2 peak capacity at the time of failure. I have run it harder before (twice as many concurrent programs executing against database) without any problem. Is there an ODBC driver memory leak? ============================== Recently on the list I read references to memory leaks in the ODBC driver interface? Are there details on this? If this matters - I use a dsn-less connection for all of my sessions: "UID=user1;PWD=****;ServerDB=DB1;ServerNode=localhost;DRIVER={LiveCache 7.2};" Thanks for any information. Stephen Gutknecht on the road: currently in Sacramento, California
