Thomas Cataldo wrote: > > To reproduce it: > > dbmcli -d aair -u dbm,dbm -uSQL dummy,dummy > > > sql_execute call process_protocole_total(3) > ERR > -24988,ERR_SQL: sql error > -8888,connection broken > > >db_state > OK > State > OFFLINE > > --- > > ====> kernel is crashed. > > Attached are the stored procedures used to trigger the crash.
After having had much trouble we now know that not the dbprocedures are the problem (as expected), but the stack. If you use the default-value of 310KB for the configuration parameter _MAXTASK_STACK (it can be found in the parameter-group support; not general and not extended) then the dbprocedure crashes. If you use (for example) 450KB, then it works. Unfortunately, the stack-usage is (by now) not checked at every place it should be checked. Therefore more stack is used than reserved for the usage and then the kernel crashes. More checks will be included. It is always a problem to think of situations (in your example some dbprocs called by another one and there on top a not-too-easy sql-statement) were we may be near the border of the stack. Therefore: please increase the configuration parameter. Thank you for preparing all that stuff you sent. Elke SAP Labs Berlin _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
