I have a situation where I will see a kernel process use 100% of a
processor on a Linux system when I try to evaluate an expression in a
CALL statement.  I have not seen a return from calling the stored
procedure over the course of a weekend.  Here's the example I have put
together from 7.3.0.25 on a Linux system (RedHat 7.3):

-----

First stored procedure:

CREATE DBPROC osdl_sapdb_test1
AS
  VAR some_var FIXED (5);
SUBTRANS BEGIN;
  SET some_var = 4;
  CALL osdl_sapdb_test2_part2(:some_var - 1);
SUBTRANS END;;

-----

Second stored procedure:

CREATE DBPROC osdl_sapdb_test2_part2(IN some_var FIXED(5))
AS
SUBTRANS BEGIN;
SUBTRANS END;;

-----

Changing to call statement to simply be:

  CALL osdl_sapdb_test2_part2(:some_var);

avoids this issue.  I can collect x_cons output or trace data if someone
would like me to.

Thanks,
Mark

-- 
Mark Wong - - [EMAIL PROTECTED]
Open Source Development Lab Inc - A non-profit corporation
15275 SW Koll Parkway - Suite H - Beaverton OR, 97006
(503)-626-2455 x 32 (office)
(503)-626-2436      (fax)
http://www.osdl.org/archive/markw/

_______________________________________________
sapdb.general mailing list
[EMAIL PROTECTED]
http://listserv.sap.com/mailman/listinfo/sapdb.general

Reply via email to