Florian K�rner wrote : >2. I use a stored procedure that is called by the program. It works fine. >Then I add a new column to a table that isn't even used in the stored >procedure. Now every call of the stored procedure causes the database to go >offline. Logfile dbm.prt says "command param_abortsession". Then I delete >and recreate the stored procedure and everything is fine again. Why?
This is a known problem. The stored procedure is compiled when the create dbproc statement is executed. If a table used in the stored procedure is altered afterwards, the stored procedure has to recompiled. Up to now this is not done automatically, but it's on our TODO list. Thomas -- Thomas Anhaus SAP DB, SAP Labs Berlin [EMAIL PROTECTED] http://www.sapdb.org/ _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
