Blogger List

Steven Feuerstein Indicates Oracle ACE director status
PL/SQL Obsession

Guy Harrison Indicates Oracle ACE status
Database topics

Bert Scalzo Indicates Oracle ACE status
Toad for Oracle, Data Modeling, Benchmarking
Dan Hotka Indicates Oracle ACE director status
SQL Tuning & PL/SQL Tips

Valentin Baev
It's all about Toad

Ben Boise
Toad SC Discussions

Dan Clamage

Kevin Dalton
Benchmark Factory

Peter Evans 
Business Intelligence, Data Integration, Cloud and Big Data

Vaclav Frolik  
Toad Data Modeler, Toad Extension for Eclipse

Devin Gallagher
Toad SC discussions

Stuart Hodgins
JProbe Discussions

Julie Hyman
Toad for Data Analysts

  Henrik "Mauritz" Johnson
Toad Tips & Tricks on the "other" Toads
  Mark Kurtz
Toad SC discussions
Daniel Norwood
Tips & Tricks on Toad Solutions
Amit Parikh
Toad for Oracle, Benchmark Factory,Quest Backup Reporter
Debbie Peabody
Toad Data Point
Gary Piper
Toad Reports Manager
John Pocknell
Toad Solutions
Jeff Podlasek
Toad for DB2
Kuljit Sangha
Toad SC discussions
Michael Sass 
Toad for DB2
Brad Wulf
Toad SC discussions
Richard To
SQL Optimization
  Toad Data Modeler Opens in a new window
Data Modeling
  Toad Higher Education
How Hi-Ed Uses Toad
  Real Automated Code Testing for Oracle
Quest Code Tester blog


Toad World blogs are a mix of insightful how-tos from Quest experts as well as their commentary on experiences with new database technologies.  Have some views of your own to share?  Post your comments!  Note:  Comments are restricted to registered Toad World users.

Do you have a topic that you'd like discussed?  We'd love to hear from you.  Send us your idea for a blog topic.

Dec 14

Written by: QCTO Blog
Tuesday, December 14, 2010  RssIcon

Written by Finn Ellebaek Nielsen

This blog post describes a few tips on how to handle installations of multiple QCTO versions on the same Windows client and the same Oracle instance.

Use Case

Your manager has asked you to check out the latest QCTO beta release or the brand new QCTO production release and only if you're happy with it and have tested it with your existing test definitions will it get installed on your colleagues' desktops too and your repository will be migrated.

Client Installation

When installing a new version of the QCTO client program on Windows you may encounter that Windows Installer asks whether you would like to repair the existing installation or it complains that another version of the program is already installed. In both cases, your only option is to uninstall the existing installation through Control Panel.

This happens when Quest hasn't updated the unique ID of the QCTO Windows Installer package (a GUID) in the new release. This is to be expected between the beta releases but it has also happened with production releases in the past.

You can work around this issue by taking a copy of your installation after you have installed it. Then, if you need to uninstall it in order to be able to install a newer production/beta version, you simply uninstall it and use your back to restore the files removed as part of the uninstall process.

Here is one way of doing exactly that:

  • When installing, choose an installation folder name with the QCTO version number in it, eg "C:\Program Files (x86)\Quest Software\Quest Code Tester for Oracle 2.0.0 Beta 4" (on Windows 64-bit) or "C:\Program Files\Quest Software\Quest Code Tester for Oracle 1.9.1" (on Windows 32-bit).
  • After the installation has finished and if you're using Windows XP or Windows Vista/7 with Classic Start Menu:
    • In Windows Explorer, take a copy of the entire installation folder (append ".bak" to the folder name) to eg "C:\Program Files (x86)\Quest Software\Quest Code Tester for Oracle 2.0.0 Beta 4.bak" or "C:\Program Files\Quest Software\Quest Code Tester for Oracle 1.9.1.bak".
    • In Start Menu, rename the Start Menu QCTO folder to include the version number (unfortunately, the installation program doesn't allow you to specify the name of the folder), eg from "Start Menu | Programs | Quest Software | Quest Code Tester for Oracle" to "... Quest Code Tester for Oracle 1.9.1". This can be done by right clicking the folder through Start Menu and selecting "Rename". The menu folder is called "Quest Code Tester for Oracle - BETA" for the beta versions.
    • In Start Menu, create a folder called "Start Menu | Programs | Quest Software | Quest Code Tester for Oracle Backup". Copy the QCTO folder into this new folder by dragging the folder while clicking on the right mouse button and selecting "Copy here" from the context menu.
  • After the installation has finished and if you're on Windows Vista/7 using the new Start Menu:
    • In Windows Explorer, take a copy of the entire installation folder to eg "C:\Program Files (x86)\Quest Software\Quest Code Tester for Oracle 2.0.0 Beta 4.bak" or "C:\Program Files\Quest Software\Quest Code Tester for Oracle 1.9.1.bak".
    • Microsoft has changed the security mechanisms around Start Menu so you need to take ownership of the %ALLUSERSPROFILE% folder, typically "C:\Users\All Users". Please refer to this tip for a description on how to do so.
    • Rename the Start Menu folder by issuing the following in a Command Prompt (change version numbers according to your preference and please note that the menu folder is called "Quest Code Tester for Oracle - BETA" for the beta versions):
      cd "%ALLUSERSPROFILE%\Microsoft\Windows\Start Menu\Programs\Quest Software"
      rename "Quest Code Tester for Oracle" "Quest Code Tester for Oracle 1.9.1"
    • Make a backup copy of the Start Menu folder by issuing the following in a Command Prompt (change version numbers according to your preference):
      cd "%ALLUSERSPROFILE%\Microsoft\Windows\Start Menu\Programs\Quest Software"
      xcopy /i /e "Quest Code Tester for Oracle 1.9.1" "Quest Code Tester for Oracle Backup\Quest Code Tester for Oracle 1.9.1"

Remember that if you make changes to any of the QCTO files installed (eg my_codetester_template.pkg or my_codetester_example.pkg), you'll need to take a fresh copy of these files too. In general, it's recommended to move those files out of the QCTO installation folder structure to prevent this from happening.

Client and Repository Version Synchronization

The version of the QCTO program installed on your Windows client must be compatible with the version of the QCTO repository that you connect to. So a newer version of the client program will not work with an older version of the repository and vice versa.

For this reason, you need to install a new repository when installing a new client version and it's a good idea to name the QCTO repository after the version, such as QCTO191 for the 1.9.1 release or QCTO200B4 for the 2.0.0 Beta 4 release.

I assume that you're using QCTO with the so-called "Shared Repository" installation option, in which:

  • The QCTO repository is stored in a separate schema.
  • The generated test programs are owned by this schema.
  • The schema is shared by multiple developers.
  • The programs under test are residing in their original schemas (different from the QCTO repository schema).

Multiple Versions

Adopting the recommended naming of the schemas used for the QCTO repository will enable you to try out new releases without disrupting your colleagues. Just remember to connect to the correct schema from the client program, import your test definitions and you're ready to roll.

Using Expired Beta Versions

You can continue to use expired beta versions if you need to verify behavior in a previous beta version. This is achieved by changing the date of your system clock. Obviously this is not advisable to do in a production client, so I suggest you do this in a controlled environment, such as a Virtual Machine.

Installing Multiple Versions of Quest Code Tester
del.icio.usFacebookDiggGoogleLive BookmarksNewsvineStumbleUponTechnoratiYahooDotNetKicks
Search Blog Entries
Blog Archives
<May 2013>
April, 2013 (13)
March, 2013 (10)
February, 2013 (5)
January, 2013 (7)
December, 2012 (6)
November, 2012 (10)
October, 2012 (8)
September, 2012 (6)
August, 2012 (8)
July, 2012 (8)
June, 2012 (12)
May, 2012 (21)
April, 2012 (10)
March, 2012 (16)
February, 2012 (19)
January, 2012 (20)
December, 2011 (19)
November, 2011 (14)
October, 2011 (12)
September, 2011 (17)
August, 2011 (15)
July, 2011 (16)
June, 2011 (13)
May, 2011 (15)
April, 2011 (8)
March, 2011 (21)
February, 2011 (17)
January, 2011 (16)
December, 2010 (13)
November, 2010 (13)
October, 2010 (7)
September, 2010 (15)
August, 2010 (11)
July, 2010 (13)
June, 2010 (12)
May, 2010 (14)
April, 2010 (12)
March, 2010 (13)
February, 2010 (12)
January, 2010 (7)
December, 2009 (10)
November, 2009 (12)
October, 2009 (15)
September, 2009 (18)
August, 2009 (13)
July, 2009 (23)
June, 2009 (14)
May, 2009 (17)
April, 2009 (7)
March, 2009 (14)
February, 2009 (7)
January, 2009 (12)
December, 2008 (7)
November, 2008 (11)
October, 2008 (19)
September, 2008 (14)
August, 2008 (11)
July, 2008 (14)
June, 2008 (19)
May, 2008 (12)
April, 2008 (18)
March, 2008 (13)
February, 2008 (8)
January, 2008 (7)
December, 2007 (5)
November, 2007 (8)
October, 2007 (13)
September, 2007 (13)
August, 2007 (16)
July, 2007 (11)
June, 2007 (6)
May, 2007 (5)
April, 2007 (5)
March, 2007 (8)
February, 2007 (6)
January, 2007 (6)
December, 2006 (5)
November, 2006 (8)
October, 2006 (4)
August, 2006 (3)