Impossible to exit Quest Code Tester if the database connection drops whilst the Test Builder is (4332283)
It is impossible to exit Quest Code Tester if the database connection drops, when working in the Test Builder. ... None. ... STATUS: ... Waiting for a fix to be released in a future version of Quest Code Tester for Oracle.
When opening a function, procedure, or package I get "An attempt to perform a FORALL on table $TA (4270024)
I'm trying to load a function, procedure, or package into QCTO but when I tried to load it I get the following error: ... The last action taken during that procedure's execution was: ... $TABLE_NAME is not a table anywhere.
When multiple outcomes are expressions, the code fails to compile or shows error 'ORA-06502' (4240461)
When multiple outcomes are expressions, and they are of different types (number, string, date), the resulting generated code either fails to compile or gets a runtime error: 'ORA-06502 - PL/SQL: numeric or value error'.
Error during installation: "XMLDB - QU_XML (PACKAGE BODY) is not valid during install" (4286860)
The qu_xml.pkb file is wrapped. ... Wrapping disrupts the use of comments in the body to determine whether or not to try to compile the package. ... It should NOT be compiled when XMLDB is not available on the instance.
Is it possible to change the Test Builder from a modal to a non-modal dialogue? (4332311)
Is it possible to change the Test Builder from a modal to a non-modal dialogue, so that it's possible to use the Dashboard when the Test Builder is open, just like the Test Editor? (And therefore be able to have multiple Test Builders open?)
"ORA-02291: integrity constraint (.) violated - parent key not found." when trying to import xm (4329616)
Importing the old qut-format works fine. ... WORKAROUND: ... Please import the unit in the old qut-file format. ... STATUS: ... Waiting for a fix to be released in a future version of Quest Code Tester for Oracle.
Need to get license key sent (4239039)
Do not have license key for product and need to have it sent.
Failing to generate type in database leads to failing compilation of test code. (4241600)
Having imported a Test Definition which was originally created in QCT version 2.5.1.849 into version 2.6.1.935, it is impossible to run/compile the test code. ... It is a Type in the QCT schema that fails to compile.
Encoding error when test cases are imported with cmd / command line (4214292)
If you do the import manullay through the GUI, it works fine. ... WORKAROUND ... Manually import the Test Cases
Running a large test suite gives error "ORA-04031 unable to allocate string bytes of shared memory" (4307901)
Code Tester 1.8 is able to run about 3500 test cases spread across about 50 test definitions with all in a single test suite. ... After upgrading to Code Tester 2.5.1, running all the tests in the single test suite gave the following error:
How do I get a Quest product's CD shipped to me? (4250787)
How do I request a Quest product's CD to be shipped to me? ... In order to make this request, you will need to do the following: ... 1) Create a new case via Manage Service Requests ... 2) In the case, make sure that you include your authorization key.
Quest Code Tester For Oracle crashes when trying to create a Support Bundle (4334212)
Quest Code Tester For Oracle crashes when trying to create a Support Bundle The Oracle Home is not selected for the current connection<br> <p>WORKAROUND</p> ... <p>Please do not leave "Connect using:" combobox empty but select an Oracle Home there. Besides that it is a good idea to have one of the Oracle Homes marked as default using "Set as default home for Code Tester" check box.</p>
ORA-06502: PL/SQL: numeric or value error: character string buffer too small... (4323660)
User upgraded from 2.6 to 2.6.1 then applied workaround in SOL 114652 for the 'BINARY_DOUBLE' or BINARY_FLOAT' issue but now getting this error: ... ORA-06512: at line 14 ... Note that only affected DB is Oracle 9i
"Created On" field in the Properties Tab of the Quest Code Editor is incomprehensible or has no information. (4290654)
User opens the Quest Code Tester Editor and selects a test case from the Test Cases Node. ... On the right panel, the "Created On" field in the Properties Tab has no info. ... It only shows the following,
Getting ORA-06502 when creating a test definition (4333585)
Getting ORA-06502 when creating test definition for a function in a package (pressing save). ... Unable to create test when the test program has a huge code <p>WORKAROUND</p><p>overwrite the installation script files with two files contained in the attached zip package (just open them in toad and run them).
Error during installation of Code Tester: "Cannot open file" (4222887)
During installation of Code Tester following error occurs and installation is aborted: "Unexpected error occurred. ... The filename, directory name, or volume label syntax is incorrect." ... One of the Oracle clients installed on machine is missing required DLL file, such as OCI.DLL file.
Is it possible to enable verbose logging when using QctoCmd.exe ? (4238874)
Is it possible to enable verbose logging when using QctoCmd.exe? ... This is not currently possible. ... STATUS: ... Enhancement request CR983658 has been submitted to Development for consideration in a future release of Quest Code Tester for Oracle.
Is there any way to import XML export files using a non Win32 API? (4335134)
How can we import test definitions using a non Win32-API? ... Tthere you will find all the information needed in order to import XML export files using a PL/SQL API.
PLS-00313: 'q_QCTO_TYPE1' not declared in this scope, when using nested object types (4240289)
When the following objects are in the database, there are problems generating tests for the package: ... 'creating a test for qcto_package.prc2 is not possible because it results in an invalid generated test package PLS-00313: 'q_QCTO_TYPE1' not declared in this scope'
ORA-03113 When executing a large number of test cases combined (4214259)
ORA-03113 when executing a large number of test cases together. ... When they are run individually, they execute as expected ... WORKAROUND ... 1) Select all unit-tests inside that big test definition
Is it possible to check the message aswell as the number when checking an exception (4240636)
You can create a test case where you check the exception. ... This can be done by checking the Number or the Code, but is it possible if you can check the message itself? ... WORKAROUND: ... None.
Ability to create new tests in same wizard (4241450)
When you want to create 5 different test sets (with 5 different parameters, you need to do the following every time) ... Select "accept all and save test" or "save test" The wizard jumps to the test.
Edit Test option not opening correct test (4240845)
When you open a TEST, this is done on 3 levels: ... 2 UNIT TEST ... 3 TEST CASE ... When you are in a test case and you use the option 'Edit Test', you will open the MAIN test. ... If this test has 2 unit tests, with both 5 test cases the system will always open the first unit test.
Test case ROWTYPE input parameter column names are not updated when an underlying column name is (4236750)
Test case ROWTYPE input parameter column names are not updated when an underlying column name is changed. ... None.
Log4j Vulnerability CVE-2021-44228 (4273218)
Are Toad products affected by the Log4j vulnerability CVE-2021-44228? <p><strong>Toad for Oracle:</strong><br>Toad for Oracle does not use Log4j. Therefore this vulnerability does not affect the product.<br>Toad for Oracle uses OraLDAPClntNN.dll (where NN is oracle version number like 12, 18, 19, etc)</p><p><br>It's unclear if Oracle LDAP client this uses Log4j, but believe this is not the case. </p><p>Some more information about the exploit:<br>"An attacker who can control log messages or log message parameters can execute arbitrary code loaded from LDAP servers when message lookup substitution is enabled"<br><br>Toad doesn't use any log message lookup substitution. The only messages we get from LDAP are numeric error codes, and Toad does not use any lookup substitution on them, or anything else.</p><p><br><strong>Toad Edge:</strong><br>Toad Edge doesn't use Log4j 2, but does use Log4 1.2.17<br><br>The range for this particular security vulnerability (CVE-2021-44228) is Log 4j 2.x to Log4j 2.15.0-rc1<br>Also, Toad Edge is not a server based application. The attack needs to happen over HTTP(S) requests.<br><br><br><strong>Unaffected products:</strong></p><p>Toad for Oracle</p><p>Toad for Oracle Editions</p><p>Toad for SQL Server</p><p>Toad for DB2</p><p>Toad for SAP</p><p>Toad for Data Point</p><p>Toad Intelligence Central</p><p>Toad Data Modeler</p><p>Toad Edge</p><p>SQL Navigator</p><p>SQL Optimizer for Oracle</p><p>SQL Optimizer for SQL Server</p><p>SQL Optimizer for DB2 LUW</p><p>SQL Optimizer for DB2 ZOS</p><p>SQL Optimizer for SAP</p><p>Benchmark Factory for Databases</p><p>Code Tester for Oracle</p><p>Toad DevOps Toolkit</p><p></p><p>Spotlight on Oracle</p><p>Spotlight on SAP</p><p>Spotlight on DB2 LUW</p><p></p>
新产品关联性