Benchmark Factory for Database 9.0 - User Guide

Store Procedure Examples

The following are some examples of statements that call stored procedures. To learn how to create a workload by importing SQL from a stored procedure, see Test Stored Procedures for Scalability.

Oracle Trace File Activation

Benchmark Factory allows you to import an Oracle trace files for use during database testing. The following provides Oracle commands that can be used to enable Oracle trace file activity.

Note: Please consult Oracle documentation for current trace file commands.

To turn on and off the trace use the ALTER SESSION command:

1. Set the TIMED_STATISTICS and MAX_DUMP_ FILE_SIZE parameters used by the sessions:

alter session

set timed_statistics=true

alter session

set max_dump_file_size=unlimited

2. Activate the trace:

 alter session set events

'10046 trace name context forever, level 4'

3. Stop the trace:

 alter session set events

'10046 trace name context off'

To activate a trace you don't have read/write access to:

1. Acquire the V$SESSION.SID and V$SESSION.SERIAL# values of the session you wish to trace.
2. Set the TIMED_STATISTICS and MAX_DUMP_FILE_SIZE parameters for the session utilizing the following procedure calls:

dbms_system.set_bool_param_in_session(

   sid     => 55,

   serial# => 1222,

   parnam  => 'timed_statistics',

   bval    => true)

dbms_system.set_int_param_in_session(

   sid     => 55,

   serial# => 1222,

   parnam  => 'max_dump_file_size',

   intval  => 2147483647)

Note: If using a release before Oracle 8, release 8.1.6, these parameters can be changed with ALTER SYSTEM commands.

3. Activate the trace.

dbms_support.start_trace_in_session(

   sid     => 55,

   serial  => 1222,

   waits   => true,

   binds   => true)

4. Stop the trace.

dbms_support.stop_trace_in_session(

  sid      => 55,

  serial   => 1222)

Create an ODBC Trace File

To create an ODBC trace file

1. Click the Start button from the Windows taskbar.
2. Select Settings | Control Panel. The Control Panel window displays.
3. Double-click on Administrative Tools. The Administrative Tools window displays.
4. Launch Data Source (ODBC). The ODBC Data Source Administrator window displays.
5. Click the Tracing tab.
6. Click the Start Tracing Now button. The Start Tracing Now button changes to Stop Tracing Now button.
7. Run the ODBC transactions to be traced.
8. When the transactions complete, click on the Stop Tracing Now button.
9. Click OK.

Configure Firewall for Remote Agents

In order to install remote agents through the Benchmark Factory console, you need to turn off the firewall or configure the firewall to allow traffic between the console machine and the agent machine. To allow traffic thru the firewall, enable Windows Management Instrumentation (WMI) and open TCP port 135 on the agent machine.

In addition, after the remote agent is installed, the Benchmark Factory console and the remote agent also communicate through port 4568 (by default). To enable this communication, configure an inbound rule on the console machine and an outbound rule on the agent machine.

Note: The console and remote agent communicate through port 4568 by default. You can change this port number in Edit | Settings | General. Check this setting to ensure you use the specified port number when creating inbound/outbound rules.

Enable WMI on Agent Machine

Enable Windows Management Instrumentation (WMI) to allow communication between the Benchmark Factory console and the remote agent. The following instructions are applicable to Windows 7. For more information, see http://msdn.microsoft.com/en-us/library/aa822854(v=vs.85).aspx.

To enable WMI (Windows 7)

1. Select Control Panel | System and Security | Windows Firewall.
2. Click Allow a program or feature through Windows Firewall.
3. Select the checkbox to the left of Windows Management Instrumentation (WMI).
4. Click OK.

Set Inbound and Outbound Rules

The Benchmark Factory console uses TCP port 135 to start agents remotely, and port 4568 is used by the console and the agent machine for communication. Create inbound and outbound rules to allow port 135 and port 4568 traffic through the Windows Firewall.

Create Inbound Rule on console machine

1. Select Control Panel | System and Security | Windows Firewall.
2. Click Advanced Settings. The Windows Firewall and Advanced Security dialog opens.
3. Click Inbound Rules (left panel).
4. Click New Rule under Actions (right panel).
5. Select Port in the New Inbound Rule Wizard. Click Next.
6. Select TCP and Specific local ports.
7. In the Specific local ports text box, enter "4568" to add these ports. Click Next.
8. Select Allow this connection. Click Next.
9. Select Domain, Private, and Public. Click Next.
10. Give your new rule a name and a description. Then click Finish to add the rule.
11. Your new rule appears in the Inbound Rules list.

Create Inbound Rule on agent machine

• On the agent machine, repeat the steps listed above for creating an inbound rule. However, in the Specific local ports text box, enter "135".

Create Outbound Rule on agent machine (if outbound connections are blocked)

1. Select Control Panel | System and Security | Windows Firewall.
2. Click Advanced Settings. The Windows Firewall and Advanced Security dialog opens.
   • If outbound connections are blocked, then continue to create a new outbound rule.

   • If outbound connections are allowed, then no action is required.

     Note: In Windows Firewall, outbound connections are set to “Allow” by default.

3. If outbound connections are blocked, click Outbound Rules (left panel).
4. Click New Rule under Actions (right panel).
5. Select Port in the New Outbound Rule Wizard. Click Next.
6. Select TCP and Specific local ports.
7. In the Specific remote ports text box, enter "4568" to add this ports. Click Next.
8. Select Allow this connection. Click Next.
9. Select Domain, Private, and Public. Click Next.
10. Give your new rule a name and a description. Then click Finish to add the rule.
11. Your new rule appears in the Outbound Rules list.

Troubleshooting

After enabling WMI and configuring inbound/outbound rules, if you encounter an error while attempting to install a remote agent because you are denied access, try the following.

Add a Registry key (Windows 7, Windows 8)

1. Open the Registry Editor (regedit.exe).

   Caution: Editing your Registry incorrectly can cause serious, system-wide problems. It is advised that you back up your Registry before modifying it.

2. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System.
3. Add a new DWORD (32-bit) Value.
4. Rename the key to "LocalAccountTokenFilterPolicy".
5. Give it a value of "1".
6. Close the Registry Editor.

Related Topics

Install Remote Agent on Windows