View Incident Report

Serious

Reported By: Uli Becker
Reported On: 7/7/2009
For: Version 2.02 Build 14

# 3026 Trying to ALTER a Prepared Stored Procedure Can Cause Access Violation When Procedure Executed

I execute a script in order to update tables and procedure before the application starts. It looks like the following. The begin..exception..end block is necessary so that the application can be started several times without raising errors.

Now the problem. I executed this script AFTER having prepared all procedures. There was no error because of the exception block. But this causes an av when executing the procedure afterwards.

BEGIN
  Execute Immediate 'ALTER PROCEDURE "CalcRechnung" (IN "RechnungenID" INTEGER,
IN "StatusID" INTEGER, IN "SkipHW" BOOLEAN)
...
EXCEPTION
END;

BEGIN
  Execute Immediate 'ALTER PROCEDURE "InsertRechnung" (OUT "ReturnIdentity"
INTEGER, IN "PatientenID" INTEGER, IN "BehandlerID" INTEGER,
IN "SaetzeID" INTEGER, IN "iStatus" INTEGER,
IN "Diagnose" CLOB COLLATE DEU_CI, IN "BGHeilverfahren" INTEGER)
...
EXCEPTION
END;

Resolution

Fixed Problem on 7/10/2009 in version 2.02 build 15

Products Affected

ElevateDB Additional Software and Utilities
ElevateDB DAC Client-Server
ElevateDB DAC Client-Server with Source
ElevateDB DAC Standard
ElevateDB DAC Standard with Source
ElevateDB DAC Trial
ElevateDB LCL Standard with Source
ElevateDB VCL Client-Server
ElevateDB VCL Client-Server with Source
ElevateDB VCL Standard
ElevateDB VCL Standard with Source
ElevateDB VCL Trial

More Support Options

Search Incident Reports

Support Forums

Frequently Asked Questions

Technical Bulletins

Technical Articles

Product Manuals

Roadmap