N/A

Oracle workload: In Benchmark Factory 7.2 or later, if you attempt to use Oracle capture files created in an earlier version of Benchmark Factory (6.9.3 or earlier) and .NET Framework 2.0 is not installed, Windows may prompt you to install it (for example, in Windows 8 or later).

Workaround: Install .NET Framework 2.0 (3.5).

N/A

Issue: If you start a trace file capture using the current version of Benchmark Factory and then start another trace file capture using version 7.2 (or earlier) on the same database, the earlier version of Benchmark Factory cannot detect the current version performing a capture. This can result in an invalid capture.

Solution: For best results, do not perform trace file captures using both the current and an earlier version of Benchmark Factory concurrently on the same database.

N/A

SQL Server workload: After capturing activity from a user logged-in using Windows authentication, attempting to replay the capture using the ODBC profile results in the following error:

"Could not obtain information about Windows NT group/user '<group/user>', error code 0x5."

Workaround: Use a domain account to start SQL Server service and make sure the account can connect to the Active Directory of Domain.

N/A

Oracle workload: In an Oracle capture and replay, Benchmark Factory cannot generate the Statspack report if the local replay directory is mapped to drive "B." This is because Benchmark Factory must have drive B open to execute a background .bat file during oracle capture and replay.

Workaround: Do not map your local replay directory to drive "B" when running an Oracle capture and replay in which you chose to generate the Statspack report.

109221

N/A

Capture and Replay

Connections -

Teradata ODBC

Connections -

Transaction Wizard and IBM CLI Driver

N/A

Connections -

Microsoft Oracle ODBC Driver

Connections -

SQL Server DB-Library (Obsolete) Connection

Attempting to run a benchmark test using a Microsoft SQL Server DB-Library (Obsolete) connection to SQL Server 2014 results in an error.

Workaround: Use the Microsoft SQL Server ODBC driver or SQL Server native connection.

Connections -

IBM DB2 CLI Driver

N/A

Connections -

IBM DB2 CLI Driver

Attempting to connect using an IBM DB2 CLI ODBC connection from Benchmark Factory running as a limited user (not Administrator) could result in the following error: "[IBM][CLI Driver]SQL1031N the database directory cannot be found on the indicated file system."

Workaround: Run Benchmark Factory as Administrator.

N/A

Connections

In Windows 10, if you open a New Connection dialog, create an SAP data source and then attempt to create a SQL Server data source, Benchmark Factory might close unexpectedly.

General -

Benchmark Factory Console

Background: This issue applies to benchmark testing using a SQL Server or SAP native connection when the Refresh data retention option is selected in the Test Options tab.

Issue Description: In a test where the connection is lost while tables are loading, if you reconnect and attempt to rerun the job, Benchmark Factory might error with the following messages: “The Expected Total rows are not the same as the Actual Total rows,” or “a duplicate key was found” (when creating an index). The test is then canceled due to errors.

Resolution: Recreate and run a new job against your selected database using the native connection.

N/A

If testing against a database other than Oracle, SQL Server, DB2, SAP, or MySQL, and using the Object/Data Retention option Refresh data using backup sets, backup sets might not be created resulting in a canceled test.

114266

Installation

(uninstall)

Beginning with release 7.1.1 in Windows 7 or later, if you have multiple editions of Benchmark Factory installed side-by-side (e.g., a Beta and a Commercial edition), and then uninstall one edition, you might encounter the following error when attempting to run a job:

" This object does not represent an OLE control"

Workaround: Do one of the following:

• Open the Benchmark Factory application directory for the edition that is displaying the error. Then right-click the Benchmark Factory executable (BFactory.exe) and select Run As Administrator.
• Or run the installer in Repair mode. To do this, right-click the .msi installer used to install the edition that is displaying the error and select Repair.

ST115773

Applies in Toad for Oracle suites (12.5 or later): When the database connection or the SQL statement contains Chinese characters, attempting to send SQL from SQL Optimizer for Oracle to Benchmark Factory results in an error. This issue only occurs when Spotlight on Oracle is launched prior to the other applications mentioned here.

Workaround: Always launch Benchmark Factory and SQL Optimizer for Oracle prior to launching Spotlight on Oracle if sending SQL from SQL Optimizer to Benchmark Factory.

N/A

License keys compatible with Benchmark Factory 5.8.1 (or earlier) are no longer supported. See Product Licensing for instructions on how to upgrade an earlier-version license key.

N/A

In a new installation (not an upgrade) of Benchmark Factory 7.2 or later, a Standard (Limited) user may encounter a Repository error when attempting to launch the application. The issue involves the SQLite database that is used as the default database in a new installation of Benchmark Factory 7.2 or later.

Workaround: Do one of the following:

• Run Benchmark Factory using an Administrator account.
• In the directory containing the SQLite database file, grant Write permission to all users. This directory is located in the following location in Windows 7: C:\ProgramData\Quest Software\BMF\Repository.

BMF-202

N/A

Connections -

Oracle

If you have multiple Oracle clients installed, after connecting using one Oracle home, attempting another connection using a different Oracle home results in an error.

Workaround: Close and then re-open Benchmark Factory.

N/A

When creating a new SAP connection, if you partially define an SAP ASE ODBC DSN, then click "Cancel," and then switch to the Native tab of the New Connection dialog (or select a different connection type), Benchmark Factory quits unexpectedly. This is a known issue with the SAP ASE ODBC driver.

To create a native SAP connection, use the Native tab of the New Connection dialog. To create an SAP ODBC connection, finish defining the SAP ODBC DSN in the ODBC tab of the New Connection dialog.

N/A

On Windows Server 2012 R2, attempting to run a TPC-C, TPC-D, or TPC-H benchmark test using the MySQL ODBC connection could cause Benchmark Factory to unexpectedly close. There is a known issue with the MySQL 8.0 ODBC driver on a Windows Server 2012 R2 system in which the latest updates are not installed.

Workaround: Ensure the latest Windows Server 2012 R2 updates are installed, or use MySQL ODBC driver version 5.3.

N/A

Benchmark Factory has been tested with the following:

• Citrix XenApp 6.5