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 DD contains all of its earlier entries without modification. New PGAU control information has been 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, due to changes in the following:

  • PL/SQL compatibility

  • gateway server RPC interface

  • UTL_PG interface

• TCP/IP only: If you have existing TIPs that were generated previously on a gateway using the SNA communication protocol and you want to use the new TCP/IP feature, then the 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 due to the fact that the gateway assumes that the appropriate user exit in IMS Connect is being used, which would translate between the appropriate 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

1. 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.

2. On a system different from a local Oracle database .
3. 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.

1. Click Start, then Settings, then Control Panel.
2. Select Services. A list of all Windows services appears.
3. Select an Oracle service (those services begin with Oracle).
4. Click Stop.
5. Continue to select and stop Oracle services until all active Oracle services are stopped.

1. From the Start Menu, select Run.
2. Enter the path of the executable file name. For example:

   D:\Disk1\setup.exe

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 ORACLE_HOME\deinstall.

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

The script 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 noninteractive mode. This option requires a properties file that contains the configuration values for the Oracle home that is being deinstalled or deconfigured.

  To create a properties file and provide the required parameters, see the template file deinstall.rsp.tmpl, located in the response folder. If you prefer, instead of using the template file, you can generate a properties file by using the -checkonly option to have deconfig discover information from the Oracle home that you want to deinstall and deconfigure. The tool will generate the properties file, which you can then use with the -silent option.

• -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.

• -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\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 files

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

  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 optional flags

1. Log in as a member of the Administrators group.
2. Run the deinstall command, providing information about the Oracle System Identifier (SID), when prompted.