Code Tester for Oracle®

Version 3.0 Installation and Configuration

Contents
Introduction to this Guide 3
Installation and Administration of Code Tester for Oracle 4
System Requirements 5
Test Repository Installation and Access Options 7
Schema Privileges 13
Installing Code Tester for Oracle® 15
Silent Installation 15

Silent Uninstall 16

Backend Administration 17
Rebuilding the Code Tester Backend 17

Providing Instance-wide Access to Code Tester 19

Restricting Access to a Single Schema 20
Installing or Upgrading an Existing Code Tester Repository 21
Removing a Test Repository 23
Uninstalling Code Tester for Oracle 24
About Dell 25
Contacting Dell 25
Technical support resources 25
Copyright 26
 1
Introduction to this Guide
This guide describes how to install and use Code Tester for Oracle® administrative features.

Additional Information
In addition to this guide, there are a number of options available for quickly finding the
information you need.

Online Help
There are several ways to access online help topics.

To... Do This...
Display the table of contents for help Select the content tab in an open help
topics window.
Search for a specific help topic Select the index tab in an open window.
Select the index tab in an open help
Display the index for help topics
window.
In the window or dialog, do one of the
following:
Display help from a window or dialog
Click Help button
Press F1

Release Notes
To access the latest release notes, go to:

http://documents.software.dell.com/CodeTesterForOracle
 2
Installation and Administration of Code
Tester for Oracle
Code Tester for Oracle automates the process of testing PL/SQL programs, making it possible for
you to identify bugs and verify program correctness in a fraction of the time it has taken
previously. Rather than write (and maintain) thousands of lines of test code, PL/SQL
programmers describe the expected behavior of their programs through a graphical interface.
Code Tester then generates the required test code, and runs it whenever you reCode Tester (either
through the interface or via command line execution).

The following provides a summary of how Code Tester works:

l You describe the expected behavior of your program through the Test Builder interface.
In some cases, you will provide some customization logic, but for the most part, you
simply point and click.
l Code Tester stores your test definitions in a repository (Oracle backend) so that you can
easily manage them over time. This same repository also provides a means of
documenting and analyzing the state of your code testing.
l Code Tester generates a PL/SQL package that implements the tests you have described,
automatically incorporating any customization logic you have provided.
l You run your test as needed (usually after each change you make to the program and in
overnight builds) with the press of a button from the Test Dashboard. Code Tester
performs all required initialization and clean up.
l Code Tester automatically verifies the results and displays them in an intuitive “red-light,
green-light” Results Viewer.
l Create back ups of your test definitions and share them among developers and application
groups through the import/export facility.
 3
System Requirements
Before installing Code Tester for Oracle, ensure your system meets the following minimum
hardware and software requirements:

l Platform: 1.0 GHz x86 compatible CPU

l Memory: 512 MB of RAM recommended
l Hard Disk Space: 100 MB of disk space for installation
l Operating System:
l Microsoft Windows 2000 Professional Edition (Service Pack 4)
l Microsoft Windows Server 2003 32-bit and 64-bit (Service Pack 1 or later)
l Microsoft Windows Vista 32-bit and 64-bit (All Service Packs)
l Microsoft Windows Server 2008 32-bit and 64-bit (All Service Packs)
l Microsoft Windows Server 2012 32-bit and 64-bit (All Service Packs)
l Microsoft Windows 7 32-bit and 64-bit (All Service Packs)

l Microsoft Windows 8 and 8.1 32-bit and 64-bit (All Service Packs)

Note: These are the Dell-supported operating systems. Code Tester may run on
older Windows versions that are not supported.

l Database Client:
l Oracle SQL Net 9
l Oracle SQL Net 10
l Oracle SQL Net 11, plus Instant Client

Note: Code Tester for Oracle has been tested on Oracle Exadata 2.0 running Oracle
database 11g R2.

l Database Server

l Oracle 9i Database Release 2 (9.2.0.6 or above), 10g R1, 10g R2, 12c;
Oracle Express Edition, 11g R1, 11g R2

l Cloud Database Server:

l Oracle databases running on Amazon EC2.

Required Database Privileges:

The schema in which you install Code Tester must have these privileges:

CREATE PROCEDURE
Code Tester for Oracle 6
System Requirements

CREATE SEQUENCE

CREATE SESSION

CREATE SYNONYM

CREATE TABLE

CREATE TRIGGER

CREATE VIEW

CREATE TYPE

Note 1: Code Tester will create a schema with the necessary privileges as part of the installation
process, when the create new user and install into new user schema option is selected on Step 2
of the Repository Wizard.

Note 2: We recommend that you install Code Tester into its own schema, and create public
synonyms so that all developers will be able to use Code Tester and share their test definitions.
This will also help you keep application code distinct from the Code Tester code base. To do
this, your schema must also have CREATE and DROP PUBLIC SYNONYM privileges.

Note 3: The Code Tester repository schema and any schema executing a test require the execute
privilege on the DBMS_RANDOM package.
 4
Test Repository Installation and
Access Options
Code Tester for Oracle uses a backend repository to store tests and testing results. Each database
being tested must have its own repository.

When you install Code Tester, you must specify the Oracle schema into which the test repository
will be placed. This repository (a set of tables) holds the definitions of the tests for your
programs. This schema can be created specifically for the Code Tester repository, or those tables
can be placed in an existing schema.

Before you install Code Tester, you should decide where the repository and the test code
generated by Code Tester will be placed, in relation to the code being tested.

This section reviews the most common configurations and offers advice about how to install and
use Code Tester to match those configurations. In each configuration we explain how to use
Code Tester in these three different types of schemas:

The owner of the Code Tester repository. When you

Code Tester Schema install Code Tester, the database tables and packages that
hold the repository are placed in this schema.
The schema from which testing is performed. In other
words, you always connect to the Test Schema when you
Test Schema
start up Code Tester. This schema owns the test objects
created by Code Tester.
Code Schema The schema that owns the code (or has execute authority
on the code) being tested. To test this code, you must have
execute authority from the Test Schema on the programs in
the Code Schema.

Installation Options
You can install and use Code Tester in each of the following configurations.

l Shared repository
l Private repository
l Shared repository, Code Schema = Test Schema
l Single, shared test schema for all developers
l Separate test schema for each application

Installing a Shared Repository

Code Tester for Oracle 8
Test Repository Installation and Access Options

There are two ways to create a shared repository:

l Public Synonyms
l Private Synonyms

Public Synonyms

Choose the "Create public synonyms..." option in the Installer.

Code Tester will then create public synonyms for the repository so that it can be accessed from
any other schema in that database instance.

Private Synonyms

In Code Tester the Installer does not automatically create private synonyms. You must create
them by running scripts manually in SQL*Plus or Toad or another execution environment.

When you install Code Tester, do not check the "Create public synonyms..." option. Instead,
install the repository into the specified schema without public synonyms. After the installation is
complete, open your SQL execution environment and connect to the Code Tester schema. You
will then run two scripts, each of which are located in the Code subdirectory of Code Tester's
installation folder:

qu_grant_execute.sql: When running this SQL*Plus compatible script, you specify the name of
the Test Schema from which you want to run Code Tester. The EXECUTE privilege is then
granted to you schema for all Code Tester objects.

After running this script for each of the schemas from which you want to run Code Tester, you
will need to connect to each of these schemas in turn and run the following script:

qu_private_synonyms.sql: When running this SQL*Plus compatible script, you specify the name
of the Code Tester Schema (owner of the repository). Private synonyms are then created for all
relevant Code Tester objects.

Code Tester can now be used from each of these individual Test Schemas.

Installing a Private Repository

This is the simplest installation. The schema in which the repository is installed is also the test
schema and the code schema. You simply install Code Tester into the application code schema.
The repository of test information is private to this schema and cannot be seen, used, or run by
any other schema.
Code Tester for Oracle 9
Test Repository Installation and Access Options

Good for: Small projects, evaluating Code Tester

How to do this: Install, but do not install public synonyms during the install and do not install
any private synonyms afterwards.

To use Code Tester: Connect to the schema in which Code Tester was installed (and which also
contains your code or has execute authority on the code you want to test).

Advantages

You don't need any special privileges to install the product (as long as your code schema has the
privileges to create procedures, tables, etc.).

Disadvantages

l The repository is not shared, so other members of your development team cannot see,
change or run your test definitions.
l Multiple, private repositories consume more database resources.
l Lots of different kinds of code (source code, test code, Code Tester repository) are all
mixed in together, making it hard to manage your code base.

Installing a Shared Repository, Code Schema = Test Schema

You install Code Tester into its own schema and make the repository and test engine available
to the various Code Schema through public or private synonyms. You run Code Tester from the
Code Schema (owns the application code). In other words, the Test Schema is the same as the
Code Schema.
Code Tester for Oracle 10
Test Repository Installation and Access Options

Good for: Team development, in which test definitions need to be shared.

How to do this: Install with public synonyms or create private synonyms after installation
is finished.

To use Code Tester: Connect to your Code Schema and choose the programs in (or accessible
from) that schema.

Advantages

l All test definitions are stored in a single, shared repository.

l You don't have to set up a separate Test Schema from which testing is performed.

Disadvantages

l You need to be able to connect to a schema that creates a new user in Oracle.
l Need ability to create public synonyms (if that approach is chosen)
l All test objects are defined in the Code Schema to which they apply. Test objects are,
therefore, mixed in with application code, which can be confusing.

Installing a Single Shared Test Schema for all Developers Repository

In this configuration, you take the extra step of creating a schema in which test code will be
created for all applications on which members of the team are working.
Code Tester for Oracle 11
Test Repository Installation and Access Options

Code Tester does not create the Test Schema. You will need to do this yourself outside of the
Code Tester install, but it does not have to be created before you install Code Tester.

Good for: Team development, in which the same team works on several different applications.

How to do this: Install with public or private synonyms, depending on whether you want the
repository to be available to all schemas or a selected subset. Click here for more details.

To use Code Tester: Connect to the shared Test Schema and choose the programs to test from the
relevant Code Schema.

Advantages

l All test definitions are stored in a single, shared repository.

l Test objects are kept separate from application code
l Developers can easily move between test definitions of various applications

Disadvantages

l Test code for multiple applications are mixed together, which can make it difficult to
keep test code distinct and manageable in the Dashboard.

Installing a Separate Test Schema for Each Application Repository

In this configuration, you take the extra step of creating a separate schema in which test code
will be created for each application on which members of the team are working.

Code Tester does not create the Test Schemas. You will need to do this yourself outside of the
Code Tester install, but it does not have to be created before you install Code Tester.
Code Tester for Oracle 12
Test Repository Installation and Access Options

Good for: Team development, in which different members of the team work on different
applications or subsystems.

How to do this: Install with public or private synonyms, depending on whether you want the
repository to be available to all schemas or a selected subset.

To use Code Tester: Connect to the Test Schema for your application and choose the programs to
test from the relevant Code Schema.

Advantages

l All test definitions are stored in a single, shared repository.

l Test objects are kept separate from application code
l Developers working on one application cannot see or run tests for another application.

Disadvantages

l Must create the largest number of new schemas (for three applications, you will have one
Code Tester Schema and three Test Schemas). This results in more management effort and
more database resources devoted to the schemas.
 5
Schema Privileges
The schema in which you install Code Tester must have the following privileges:

ALTER SESSION

CREATE PROCEDURE

CREATE SEQUENCE

CREATE SESSION

CREATE SYNONYM

CREATE TABLE

CREATE TRIGGER

CREATE VIEW

CREATE TYPE

Note: Some tests will require the creation of an object type and nested table type, so you may
need to add a CREATE TYPE privilege to an account.

Please note the following:

l If requested, Code Tester creates a schema with the necessary privileges as part of the
installation process.
l We recommend that you install Code Tester into its own schema, and create public
synonyms so that all developers will be able to use Code Tester and share their test
definitions. This will also help you keep application code distinct from the Code Tester
code base. To do this, your schema must also have CREATE and DROP PUBLIC
SYNONYM privileges.
l You may need additional privileges to test certain kinds of objects, such as files and
cursor variables. If such a schema is not yet available, you will need to ask your DBA to
connect to a SYSDBA account to create that schema (this can all be done from within the
Code Tester installer; see the release notes to get started).

Note: If you have not previously installed utPLSQL, then the qu_utplsql_api package will be
marked invalid. Code Tester will not use this package unless utPLSQL has been installed and
you want to run utPLSQL test packages.

Required Schema Packages for Code Tester Installation

The following Oracle packages are required to install Code Tester for Oracle:

SYS.DBMS_UTILITY
Code Tester for Oracle 14
Schema Privileges

SYS.DBMS_DESCRIBE

SYS.DBMS_LOB

SYS.DBMS_RANDOM

SYS.DBMS_SQL

XDB.DBMS_XMLDOM

XDB.DBMS_XMLPARSER

XDB.DBMS_XSLPROCESSOR

When installing Code Tester where these packages not are accessible, you will receive the
following message:

Code Tester for Oracle cannot be installed successfully because this schema does not
have access to the following packages: xxx... Please contact your DBA to obtain access
to these packages

Obtain the required permissions and continue with the installation procedures.
 6
Installing Code Tester for Oracle®
To install Code Tester for Oracle:

1. Double-click the Code Tester for Oracle installer. The Code Tester for Oracle setup
wizard displays.
2. Click Next. The licenses agreement displays.
3. Read the licenses agreement and click the I accept the terms in the license agreement
radio button.
4. Click Next. The Destination Folder dialog displays. Accept the default location and click
Next or click Change to enter the desired location. After setting the desired folder, click
OK, then click Next. The Install Database Respository dialog displays.
5. Click Next to install the database repository. Or, check the Install database repository
after install completes using the Repository Manager check box if you wish to install
the repository after the install completes.
6. Click Next. The Ready to Install dialog displays.
7. Click Install. The Installing Code Tester for Oracle dialog displays.
8. After installation completes, the Install Wizard Complete dialog displays and provides the
following options:
a. Launch Code Tester for Oracle: Launches Code Tester for Oracle.
b. Show the Release Notes: Displays the release notes.
9. Select Launch Code Tester for Oracle. Code Tester launches.
10. Select Help | Authorize. The Authorization dialog displays.
11. Enter the required licenses information.
12. Click OK. The installation process is complete.

Silent Installation
For Windows 7 and 2008, you must open the "command prompt" as the administrator to get
permission to run the install.

Code Tester for Oracle provides silent installation for frontend client only installs.

The following provides procedures for command line silent installation:

The command line for silent installation is:

msiexec /i Code TesterCodeTesterOracle_2.6.0.XXX.msi/qn

INSTALLDIR="<Installation Directory>"
Code Tester for Oracle 16
Installing Code Tester for Oracle®

If option INSTALLDIR="<Installation Directory>" is ommited then QCTO will be installed in

the default directory:

<Install Directory> is a destination directory for QCTO installation.

Examples:

msiexec /i Code TesterCodeTesterOracle_2.6.0.XXX.msi /qn

The Code TesterCodeTesterOracle_2.6.0.XXX.msi located in the current directory will be

installed in the default directory: c:\Program Files\Code Tester Software\Code Tester for Oracle.

msiexec /i "c:\My Files\Code TesterCodeTesterOracle_2.6.0.XXX.msi " /qn

INSTALLDIR="c:\TEMP\MyWork

The c:\My Files\Code TesterCodeTesterOracle_2.6.0.XXX.msi will be installed in the directory

"c:\TEMP\My Work".

Silent Uninstall
The following command performs the silent uninstall for Code Tester for Oracle.

msiexec /x Code TesterCodeTesterOracle_2.6.0.XXX.msi /qn

 7
Backend Administration
By accessing the Code Tester for Oracle administration, you can also perform the following
administrative operations in your Oracle instance (backend):

l Repository Management
l Install or Upgrade Test Repository
l Remove Test Repository
l Repository Management

From Code Tester for Oracle Repository Management you can:

l Rebuild the Code Tester backend

l Provide instance-wide access to Code Tester
l Restrict access to Code Tester to a single schema

To access Repository Management

1. Click the Start button from the Windows task bar.

2. Select All Programs | Code Tester Software | Code Tester for Oracle | Code Tester |
Administration | Repository Management. The Code Tester Repository Wizard displays.
The following options are provided:
l Rebuild Code Tester Backend
l Provide instance-wide access to Code Tester
l Restrict access to Code Tester to single schema

Note: The following three procedures require that you begin from the Code Tester Repository
Wizard dialog.

Rebuilding the Code Tester Backend

This option reinstalls all Code Tester backend packages from disk.

To rebuild the Code Tester backend

1. Click the Rebuild Code Tester backend radio button.

2. Click Next. The directory and login information dialog displays.
3. Enter the User Name.
4. Enter the Password.
5. From the Database drop-down, select the desired database.
Code Tester for Oracle 18
Backend Administration

6. Click Next. The backend rebuilds. This will take several minutes. When the rebuilding
process completes, the Finished dialog displays.
7. Click Finish.
 8
Providing Instance-wide Access to
Code Tester
This option creates public synonyms for Code Tester objects in the connected schema.

To provide Instance-wide access to Code Tester

1. Click the Provide instance-wide access to Code Tester radio button.

2. Click Next. The directory and login information dialog displays.
3. Enter the User Name.
4. Enter the Password.
5. From the Database drop-down, select the desired database.
6. Click Next.
l If no installation issues are detected, instance-wide access will be granted.
l If installation issues are detected, the Repository installation issues dialog
displays. Review the issues displayed and click Back to select another schema, or
fix the issue presented. Or, click Ignore missing privileges and continue by
clicking Next.
7. Click Finish when the processing completes.
 9
Restricting Access to a Single Schema
This option removes public synonyms for Code Tester objects from the connected schema.

To restrict access to Code Tester

1. Click the Restrict access to Code Tester to single schema radio button.
2. Click Next. The Provide directory and login information dialog displays.
3. Enter the User Name.
4. Enter the Password.
5. From the Database drop-down, select the desired database.
6. Click Next. The restrictions are applied.
7. When the processing completes, click Finish.
 10
Installing or Upgrading an Existing
Code Tester Repository
The upgrade process consists of running the installation script in an existing schema. You will
do this by choosing the upgrade path offered in the installer. The install script will then
automatically apply any necessary changes to your current installation to bring it up to the
new version.

Note: If you do not create synonyms, then you will only be able to access this install of Code
Tester from within the Code Tester schema only (which will likely be the same schema as your
application code).

From the Repository Manager you can:

l Install a new Code Tester repository

l Upgrade an existing Code Tester repository

Installing a New Code Tester Repository

To install a new Code Tester test repository

1. Click the Start button from the Windows task bar.

2. Select All Programs | Code Tester Software | Code Tester for Oracle | Administration
| Install or Upgrade Test Repository. The Code Tester Repository Wizard displays. The
following options are provided:
l Install new Code Tester repository
l Upgrade existing Code Tester repository
3. Select Install new Code Tester repository.
4. Click Next. The Repository installation dialog displays and provides the
following options:
l Install into existing user schema
l Create new user and install into new user schema
l Deinstall Code Tester first: Check this box to run the deinstall script before
starting the install process
l Create public synonyms after installation: Check this box to provide access to
Code Tester from any schema in this instance.
5. Click Next. The Provide directory and login information dialog displays.
6. Enter the User Name.
7. Enter the Password.
8. From the Database drop-down, select the desired database.
Code Tester for Oracle 22
Installing or Upgrading an Existing Code Tester Repository

9. Click Next. The Confirm dialog displays.

10. Click Install.
11. The Processing dialog displays and the schema installs. The Finished dialog displays.
12. Click Finish. The Confirm dialog displays.
13. Click Yes to install another the Code Tester backend objects into another schema, or
Cancel to close the wizard.

When all scripts have been run, Code Tester will validate your installation and notify you of
any problems. You may safely ignore any Oracle errors that appear within the scrolling
feedback region of the installer, as long as you see a green message indicated that your
installation has succeeded.

Upgrading an Existing Code Tester Repository

To upgrade an existing Code Tester repository from the administration menu

1. Click the Start button from the Windows task bar.

2. Select All Programs | Code Tester Software | Code Tester for Oracle | Administration
| Install or Upgrade Test Repository. The Code Tester Repository Wizard displays. The
following options are provided:
l Install new Code Tester repository
l Upgrade existing Code Tester repository
3. Select Upgrade existing Code Tester repository.
4. Click Next. The directory and login dialog information displays.
5. Enter the required parameters.
6. Click Next. The Upgrade Code Tester Repository dialog displays.
7. Click Next. The repository upgrades. When the upgrade completes, the Finished
dialog displays.
8. Click Finish.
 11
Removing a Test Repository
You can remove a test repository from Code Tester if required.

To remove a repository

1. Click the Start button from the Windows task bar.

2. Select All Programs | Code Tester Software | Code Tester for Oracle | Administration
| Remove Test Repository. The Provide directory dialog displays.
3. Accept the default directory or navigate to the directory where Code Tester for Oracle
is installed.
4. Click Next. The Uninstall Repositories dialog displays. This window displays the names
of any schemas into which Code Tester repository was installed from this workstation.
You will need to type in the password and then verify the version in that schema. If you
do not see the schema from which you wish to uninstall Code Tester, then see step 5.
5. Click Add New Schema. The Provide scheme information dialog displays. Fill in the
schema name, password, and database name. Press Next to add this schema to the grid.
Repeat as many times as necessary.
6. Click Next. The Confirm deinstallation dialog displays.
7. Select Yes, I want to remove the selected repositories check box.
8. Click Next. The repository uninstalls and the Finished dialog displays.
9. Click Finish.
 12
Uninstalling Code Tester for Oracle
To uninstall Code Tester for Oracle

1. Click the Start button from the Windows task bar.

2. Select All Programs | Software| Code Tester for Oracle | Uninstall Code Tester for
Oracle. The Code Tester for Oracle uninstall dialog displays.
3. Click Yes. The Code Tester Repository Wizard displays. Use the wizard to uninstall a
repository or click Cancel and go to step 13.
4. Click Next. The Uninstall Repositories dialog displays.
5. Right-click inside the Code Tester Installation Status dialog. A drop-down displays.
6. Click Add new schema.
7. Fill in the required parameters.
8. Click Next.
9. Repeat steps 6 and 7 for each schema you wish to uninstall.
10. Click Next when finished adding the schemas. The confirm deinstallation dialog displays.
Click the Yes, I want to remove the selected repositories check box.
11. Click Next. When the repositories complete deinstallation, the Finished dialog displays.
12. Click Finish.
The uninstall completes and the uninstall completion dialog displays.
Code Tester for Oracle 25
About Dell

About Dell
Dell listens to customers and delivers worldwide innovative technology, business solutions and
services they trust and value. For more information, visit www.software.dell.com.

Contacting Dell
Technical support:

Online support

Product questions and sales:

(800) 306-9329

Email:

[email protected]

Technical support resources

Technical support is available to customers who have purchased Dell software with a valid
maintenance contract and to customers who have trial versions. To access the Support
Portal, go to

http://software.dell.com/support/.

The Support Portal provides self-help tools you can use to solve problems quickly and
independently, 24 hours a day, 365 days a year. In addition, the portal provides direct access to
product support engineers through an online Service Request system.

The site enables you to:

l Create, update, and manage Service Requests (cases)

l View Knowledge Base articles

l Obtain product notifications
l Download software. For trial software, go to Trial Downloads.
l View how-to videos
l Engage in community discussions
l Chat with a support engineer
Code Tester for Oracle 26
Copyright

Copyright

©2014 Dell Inc.

ALL RIGHTS RESERVED.

This guide contains proprietary information protected by copyright. The software described in
this guide is furnished under a software license or nondisclosure agreement. This software may be
used or copied only in accordance with the terms of the applicable agreement. No part of this
guide may be reproduced or transmitted in any form or by any means, electronic or mechanical,
including photocopying and recording for any purpose other than the purchaser’s personal use
without the written permission of Dell Software Inc.

The information in this document is provided in connection with Dell Software products. No
license, express or implied, by estoppel or otherwise, to any intellectual property right is
granted by this document or in connection with the sale of Dell Software products. EXCEPT
AS SET FORTH IN DELL SOFTWARE’S TERMS AND CONDITIONS AS SPECIFIED IN
THE LICENSE AGREEMENT FOR THIS PRODUCT, DELL SOFTWARE ASSUMES NO
LIABILITY WHATSOEVER AND DISCLAIMS ANY EXPRESS, IMPLIED OR STATUTORY
WARRANTY RELATING TO ITS PRODUCTS INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR
PURPOSE, OR NON-INFRINGEMENT. IN NO EVENT SHALL DELL BE LIABLE FOR
ANY DIRECT, INDIRECT, CONSEQUENTIAL, PUNITIVE, SPECIAL OR INCIDENTAL
DAMAGES (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF PROFITS,
BUSINESS INTERRUPTION OR LOSS OF INFORMATION) ARISING OUT OF THE USE
OR INABILITY TO USE THIS DOCUMENT, EVEN IF DELL SOFTWARE HAS BEEN
ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Dell Software makes no
representations or warranties with respect to the accuracy or completeness of the contents of this
document and reserves the right to make changes to specifications and product descriptions at
any time without notice. Dell Software does not make any commitment to update the
information contained in this document.

If you have any questions regarding your potential use of this material, contact:

Dell Software Inc.

Attn: LEGAL Dept
5 Polaris Way
Aliso Viejo, CA 92656

Refer to our Web site (www.software.dell.com) for regional and international office information.

Trademarks

Dell, the Dell logo, Code Tester, vWorkspace, and Toad are trademarks of Dell Inc. and/or its
affiliates. Other trademarks and trade names may be used in this document to refer to either the
entities claiming the marks and names or their products. Dell disclaims any proprietary interest in
the marks and names of others.