View Incident Report

Serious

Reported By: Terry Swiers
Reported On: 3/30/2021
For: Version 2.34 Build 1

# 4809 Jobs Not Being Initialized Correctly Results in Locking Errors with the USE Statement

I'm seeing the server going Not Responding when attempting to stop the server. I have the following job defined to run at server start.

It hangs for me about 95% of the time for about a little over a minute before it completes the stop process.

CREATE JOB "MemUtilDB-Initialize"
RUN AS "System"
FROM DATE '2021-03-07' TO DATE '2099-12-31'
AT SERVER START
BETWEEN TIME '00:00' AND TIME '23:59:59.999'
BEGIN
USE "MemUtilDB";

EXECUTE IMMEDIATE 'CREATE PROCEDURE "ExternalProcedure" (IN "aParam1" VARCHAR(128) COLLATE "UNI", IN "aParam2" CLOB COLLATE "UNI")
EXTERNAL NAME "ExtModule"
VERSION 1.00';

END

Comments

Use of the USE statement in a job would result in a dangling read lock being created during the job initialization that, subsequently, caused locking errors.

Resolution

Fixed Problem on 3/31/2021 in version 2.34 build 2

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 PHP Standard
ElevateDB PHP Standard with Source
ElevateDB PHP Trial
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