List:MaxDB« Previous MessageNext Message »
From:Thomas Anhaus Date:February 20 2003 7:39am
Subject:RE:DB shutdown after CREATE DBPROC statement
View as plain text  
>Hello List,

>i have two procedures. The procedure PROC_TEST calls the procedure PROC_SUB.

>------ cut start ------

>CREATE DBPROC PROC_SUB (IN input TIMESTAMP) AS
>    VAR
>        actualTimestamp TIMESTAMP;
>    TRY
>        SELECT TIMESTAMP
>        INTO :actualTimestamp
>        FROM DBA.DUAL;
>    CATCH
>        if $rc<> 100 THEN STOP ($rc, 'Unexpected error.');


>CREATE DBPROC PROC_TEST AS
>    VAR
>        actualTimestamp TIMESTAMP;
>    TRY
>        SELECT TIMESTAMP
>        INTO :actualTimestamp
>        FROM DBA.DUAL;
>
>        CALL PROC_SUB(actualTimestamp);
>    CATCH
>        if $rc<> 100 THEN STOP ($rc, 'Unexpected error.');

>------ cut end ------

>The syntax "CALL PROC_SUB(actualTimestamp);" in the procedure PROC_TEST is
>wrong,
>ist must show "CALL PROC_SUB(:actualTimestamp);".
>If i use the wrong syntax the following DB error occured:

>Native error: 800
>Text: [SAP AG] [SQLOD32DLL][SAP DB]General error;800 implicit SERVERDB
>restart (connection aborted).

>Is it a desired feature or a bug?
>I expect a warning or an error from the syntaxcheck and
>no DB shutdown.

>I use the SQL Studio 7.4(.3.6) on Windows 2000 and the DB Kernel 7.4.3.10 on
>a SUSE 8.1 (2.4.19-4GB) system.

This is a bug, not the desired behavior. We will try to reproduce
and fix it.
Thanks for reporting the problem.

Regards,
Thomas 
-- 
Thomas Anhaus
SAP DB, SAP Labs Berlin
thomas.anhaus@stripped
http://www.sapdb.org/
_______________________________________________
sapdb.general mailing list
sapdb.general@stripped
http://listserv.sap.com/mailman/listinfo/sapdb.general



Thread
DB shutdown after CREATE DBPROC statementCarsten Sprenger - MediaTransfer AG Netresearch & Consulting19 Feb
RE:DB shutdown after CREATE DBPROC statementThomas Anhaus20 Feb