Inspect SGA Job creates a new session instead of connecting to existing Oracle DB session
说明
SQL Optimizer creates a new Oracle DB session every time Inspect SGA job is run. By default, the Inspect SGA Job is expected to connect to the connected DB session. This causes overhead of the Oracle database and there is a risk of service failure due to the Oracle DB process count limit setting.
Error seen "Could not load file or assembly 'file:///C:\Program Files\Quest Software\Toad for Oracle 2023 R1 Edition\SQL Optimizer for Oracle 9.3\LogEngine.dll' or one of its dependencies. The module was expected to contain an assembly manifest." SupportBundle Quest SQL Optimizer for Oracle TOAD Call Stack "Server stack trace: at System.Reflection.RuntimeAssembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)at System.Reflection.RuntimeAssembly.InternalLoadAssemblyName(AssemblyName assemblyRef, Evidence assemblySecurity, RuntimeAssembly reqAssembly, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)at System.Reflection.RuntimeAssembly.InternalLoadFrom(String assemblyFile, Evidence securityEvidence, Byte[] hashValue, AssemblyHashAlgorithm hashAlgorithm, Boolean forIntrospection, Boolean suppressSecurityChecks, StackCrawlMark& stackMark)at System.Reflection.Assembly.LoadFrom(String assemblyFile)at Quest.Tuning.Common.Business.DisposableAssemblyLoader.RemoteLoader.LoadAssembly(String fullName)at System
解决办法
WORKAROUND: None STATUS: The issue will be fixed in a future release of SQL Optimizer of Oracle
缺陷ID
SOFO-2835
其他信息
SQL Optimizer for Oracle v9.3.4
Oracle Server/Client : Oracle 18c
Toad For Oracle : 16.3
