Perform the following steps to prepare for upgrading the previous versions of Oracle Database Gateway for APPC to current versions:

1. Make backups of altered PGA shipped files.

2. Remove or rename any old gateway directories.

Upgrade considerations are as follows:

• PGAU control files from Gateway release 8 or 9 are upward compatible and you do not need to change them.

• After upgrade, the PG Data Dictionary (PG DD) contains all of its earlier entries without modification. New PGAU control information is added along with some columns to support new features, but no customer entries are altered by the upgrade.

• All TIPs from Oracle Database Gateway for APPC release 4.0.1 or earlier must be recompiled because of the changes in the following:

  • PL/SQL compatibility

  • Gateway server RPC interface

  • UTL_PG interface

• If you have existing TIPs that were generated previously on a gateway using the SNA communication protocol and you want to utilize the new TCP/IP feature, then TIPs will have to be regenerated by PGAU with mandatory NLS_LANGUAGE and Side Profile Settings. Specify the appropriate ASCII character set in the DEFINE TRANSACTION command.

  This is because the gateway assumes that the user exit in IMS Connect is being used, which would translate between the ASCII and EBCDIC character sets.

  Caution:

  An upgraded PG Data Dictionary (PG DD) cannot be accessed by an earlier release of PGAU.

If you want to restore a previous release of gateway, then you must restore the following components to their previous versions:

• PGAU

• PG DD

• Gateway server

You can install the gateway in any of the following ways:

• On the same system as the existing Oracle database but in a different directory.

  All tasks for this type of installation or upgrade are discussed in this section.

• On a system different from a local Oracle database.

• On the same system as the Oracle database, and in the same Oracle home directory. Note that in this case, the Oracle database and the gateway must be at the same Release level.

Use Table 4-1 as a guide to step through the Oracle Universal Installer. At each prompt from the Oracle Universal Installer, perform the actions described in the Response column of the table to install the gateway on your UNIX platform.

When the Oracle Universal Installer confirms that the installation is complete, verify that the installation procedure was successful. To do this, read the contents of the installation log file, which is located in the $ORACLE_HOME/install directory. The default file name is make.log.

The Deinstallation Tool (deinstall) is available in the installation media before installation, and is available in Oracle home directories after installation. It is located in the path $ORACLE_HOME/deinstall.

The deinstall command stops Oracle software, and removes Oracle software and configuration files on the operating system.

The command uses the following syntax, where variable content is indicated by italics:

deinstall -home complete path of Oracle home [-silent] [-checkonly] [-local]
[-paramfile complete path of input parameter property file] [-params name1=value
name2=value . . .] [-o complete path of directory for saving files] [-help | -h]

The options are:

• -silent

  Use this flag to run the command in silent or response file mode. If you use the -silent flag, then you must use the -paramfile flag, and provide a parameter file that contains the configuration values for the Oracle home that you want to deinstall or deconfigure.

  You can generate a parameter file to use or modify by running deinstall with the -checkonly flag. The deinstall command then discovers information from the Oracle home that you want to deinstall and deconfigure. It generates the properties file, which you can then use with the -silent option.

  You can also modify the template file deinstall.rsp.tmpl, located in the response folder.

• -checkonly

  Use this flag to check the status of the Oracle software home configuration. Running the command with the -checkonly flag does not remove the Oracle configuration. The -checkonly flag generates a parameter file that you can use with the deinstall command.

• -local

  Use this flag on a multinode environment to deconfigure Oracle software in a cluster.

  When you run deconfig with this flag, it deconfigures and deinstalls the Oracle software on the local node (the node where deconfig is run). On remote nodes, it deconfigures Oracle software, but does not deinstall the Oracle software.

• -paramfile complete path of input parameter property file

  Use this flag to run deconfig with a parameter file in a location other than the default. When you use this flag, provide the complete path where the parameter file is located.

  The default location of the parameter file depends on the location of deconfig:

  • From the installation media or stage location: $ORACLE_HOME/inventory/response

  • From an unzipped archive file from Oracle Technology Network: /ziplocation/response

  • After installation from the installed Oracle home: $ORACLE_HOME/deinstall/response

• -params [name1=value name 2=value name3=value . . .]

  Use this flag with a parameter file to override one or more values that you want to change in a parameter file you have already created.

• -o complete path of directory for saving response files

  Use this flag to provide a path other than the default location where the properties file (deinstall.rsp.tmpl) is saved.

  The default location of the parameter file depends on the location of deconfig:

  • From the installation media or stage location before installation: $ORACLE_HOME/

  • From an unzipped archive file from Oracle Technology Network: /ziplocation/response/

  • After installation from the installed Oracle home: $ORACLE_HOME/deinstall/response

• -help | -h

  Use the help option (-help or -h) to obtain additional information about the command option flags.

1. Log in as the installation owner.
2. Run the deinstall command, providing information about your servers as prompted.