Herr David Krcek wrote: > > Hi List, > > i run into a problem with sapdb 7.4.03.32. > > After running fine, the temp area of my database starts to grow very > fast and and the DB stops with DB_FULL. > During this the db don't response any request. > The size of the db (unicde) is 550 MB (perm data) and the temp area > can grow up 5.5 GB (and stops then, because DB_FULL). > The main application, that runs on this DB is a webshop (with jboss). > > My questions are: > Is there a chance see why the temp space grow ? > How can i stop that or better how to prevent ? > > Thanks. > David >
Oops, you are using a version which is nearly 3 years old. But nevertheless, I assume your problem is caused by a very complex statement, no idea if with subqueries or a join. This causes huge intermediate results, filling up your database, not responding in the meantime. Try to find out the statement causing the problem: 1. Start the trace: dbmcli -d <dbname> -u <dbm,dbm> db_execute diagnose vtrace order on 2. Execute that application when your growing situation is there: 3. Flush the trace: dbmcli -d <dbname> -u <dbm,dbm> trace_flush 4. Create the text representation: dbmcli -d <dbname> -u <dbm,dbm> trace_prot a 5. Copy the text representation to a local file: dbmgetf -d <dbname> -u <dbm,dbm> -k KNLTRCPRT -f <local file name> 6. Stop writing of the trace: dbmcli -d <dbname> -u <dbm,dbm> db_execute diagnose vtrace order off. If you check this file, you may see the statement when looking for PACKET from the bottom of the file upwards. Then you should do some update statistics for the tables concerned. Or you should check if indices should be created for columns / combination of columns used in the qualification. Use the explain statement for checking if the statement will be handled different (and better) when indices are created. If you are the owner of the application you may check the statement itself (sometimes statements can be rewritten to influence the performance in a very positive way). On the other hand you should think about upgrading your kernel as during the last years 'some' changes were done helping to improve the performance. And I do not think about upgrading to 7.4.3.*, but to 7.5 / 7.6. Elke SAP Labs Berlin > > -- > MaxDB Discussion Mailing List > For list archives: http://lists.mysql.com/maxdb > To unsubscribe: > http://lists.mysql.com/[EMAIL PROTECTED] > > > -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]