Creating a New Ingres Development Environment

This chapter describes how to move your existing development installation into a new Ingres development installation, where you can test your databases and applications and make any necessary changes to ensure that they work correctly.

The goal is to test thoroughly in the new development environment so that you can confidently perform the upgrade to the production system. The upgrade to the production system is described in subsequent chapters.

Note: If you are migrating from Ingres 6.4, read Considerations for Ingres 6.4 before performing the tasks in this chapter.

Platform-specific Examples in This Guide

While most of the examples used in this guide are specific to UNIX, the concepts described also apply to the Windows environment. For information on upgrading in the VMS environment, see the appendix "Considerations for Alpha OpenVMS."

How You Move an Existing Development Installation into the New Development Installation

Note: Back up all data before starting.

The overall process for moving your existing development installation into a new Ingres development installation is as follows:

1. Create a development installation of the new Ingres.
2. Prepare your applications.
3. Load databases and applications into the new installation.
4. Prepare your system.
5. Test applications and procedures.
6. Practice the upgrade.

Create a Development Installation of the New Ingres

To install Ingres on the development machine, following these steps.

Note: The following procedure assumes that the development computer will support both the original and new version Ingres installations.

UNIX:

1. Create a new Ingres directory in a location with sufficient disk space. In this example, the directory is called /ing2006/ingres.

   Execute the following commands:

   mkdir /ing2006/ingres

   chmod 755 /ing2006/ingre

2. Set the environment to the original and new development installations. To do this, create two scripts. In this example, the scripts are named "setold" and "setnew."

   Here are example scripts for the C shell. You may need to adjust them for your specific installation.

   For example, the PATH settings may be different, and LD_LIBRARY_PATH may be named LIBPATH or SHLIB_PATH, depending on the platform. In this example, the "old" installation is an Ingres 6.4 installation.

   setold:
   setenv II_SYSTEM /ing64
   set path=(. /usr/local/bin /bin /usr/ucb /usr/sbin /usr/openwin/bin $II_SYSTEM/ingres/bin $II_SYSTEM/Ingres/utility /usr/ccs/bin)
   set inst=`ingprenv1 II_INSTALLATION`
   setenv LD_LIBRARY_PATH /usr/lib:/usr/openwin/lib
   set prompt=`whoami`.`uname -n`"[$inst]% "
   echo "Switching to original Ingres 6.4 [$inst] installation"

   setnew:
   setenv II_SYSTEM /ing2006
   set path=(. /usr/local/bin /bin /usr/ucb /usr/sbin /usr/openwin/bin $II_SYSTEM/ingres/bin $II_SYSTEM/ingres/utility /usr/ccs/bin)
   set inst=`ingprenv II_INSTALLATION`
   setenv LD_LIBRARY_PATH /usr/lib:/usr/openwin/lib:$II_SYSTEM/ingres/lib
   set prompt=`whoami`.`uname -n`"[$inst]% "
   echo "Switching to new 2006 [$inst] installation"

3. If required, define aliases in the C shell or shell functions in the Bourne or Korn shell to invoke the setold and setnew scripts.

   For example:

   alias setold source ~ingres/setold
   alias setnew source ~ingres/setnew

4. Use the "setnew" alias to switch to the new Ingres environment, and change directory to $II_SYSTEM/ingres.
5. Follow the installation instructions to install Ingres.

   Note: Do not use the same data, checkpoint, journal, dump, or log directories as the original installation; the directories can, however, be on the same disks.