Icon View Incident Report

Serious Serious
Reported By: Robert Perelegre
Reported On: 7/30/2018
For: Version 2.28 Build 4
# 4674 SQL and Procedure Caching Can Interfere with Opening Databases After a Restore

If I put SQLStmtCacheSize = 100 and FuncProcCacheSize = 100 in the session of ElevateDB Manager and I try to restore the backup (using the catalog) the error "ElevateDB Error #300 Cannot lock the database XXXXXX for shared access" this is the error reported the last time and I reproduced it in all servers using SQLStmtCacheSize and FuncProcCacheSize

Comments Comments
The issue was that the SQL and procedure caching was causing ancillary procedures that were referenced in triggers and other table-level constructs to be loaded and cached when tables were opened during the database restore. This would cause the database to stay open exclusively past the completion of the restore, and any further attempts to open the database normally (shared) would encounter an exception.

Resolution Resolution
Fixed Problem on 7/31/2018 in version 2.28 build 5

Products Affected 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