Migrating to new instances of Oracle Database Gateway for APPC from an existing installation is straightforward, provided you follow some guidelines. This chapter provides information to make these new installations as easy as possible. It also provides the parameters you need if you are using the TCP/IP for IMS Connect communication protocol on your gateway.
This chapter provides information that is specific to this release of Oracle Database Gateway for APPC for AIX 5L Based Systems (64-Bit), HP-UX Itanium, Solaris Operating System (SPARC 64-Bit), Linux x86, and Linux x86-64. It contains the following sections:
Follow these steps to migrate an existing gateway to Release 11.2 of the gateway using the SNA communication protocol.
Note that if you are using the gateway TCP/IP support for IMS Connect, you will not be migrating an existing release to the current release of the gateway. However, you will need to place valid Heterogeneous Services parameters into your
ora file. Proceed to "Parameter Changes: Version 4 to Release 11.2 of the Gateway".
Install the new release of the gateway in a separate directory as outlined in Chapter 4, "Installing the Gateway".
Caution:Do not install the gateway over a previously existing gateway installation. Doing this corrupts the existing installation.
If you are migrating from Release 9.0.1 or earlier of the gateway,
PGA_TRACE is not supported. You need to modify the parameter to
If you have encrypted some of the parameters at file
.ora by using
dg4pwd, copy the
.pwd file from the old gateway instance to the new instance.
Oracle recommends that you keep the old gateway Oracle home directory and instance configurations intact and operational when you are installing a new release of the gateway and upgrading existing instances, in case there are problems with the upgrade. This helps to ensure minimum down time between changes to different gateway instances.
Oracle Database Gateway for APPC uses the Heterogeneous Services (HS) facilities of Oracle and Oracle Net. If you are upgrading from a version 4 gateway, then you need to slightly modify the gateway service name entries in the
tnsnames.ora file. Add an
(HS=) clause to tell Oracle Net that the gateway uses HS facilities. For more information, refer to Section 5.1, "Configuring the Oracle Network for the Gateway".
This release of Oracle Database Gateway for APPC introduces new and changed initialization parameters if you are migrating from a Version 4 gateway to Release 11.2 of the gateway.
Note:The "Parameter Changes: Version 4 to Release 11.2 of the Gateway" section does not apply to you if you are migrating to Release 10.2.0 from Version 8 of the Oracle Database Gateway for APPC.
If you are using the gateway TCP/IP support for IMS Connect, you will not be migrating from Version 4 to the current release of the gateway. However, you need to place valid Heterogeneous Services parameters into your
This chapter contains references to the particular HS parameters that you need to run the gateway.
Note:Refer to the Oracle Database Heterogeneous Connectivity User's Guide for a complete list and descriptions of all HS parameters used in Oracle products.
HS_parameters are specific to Oracle Heterogeneous Services. For details on HS parameters, refer to the Oracle Database Heterogeneous Connectivity User's Guide.
The following sections are for those users who have an existing release of the gateway using the SNA protocol, but who want to switch to using TCP/IP support for IMS Connect.
The TCP/IP support for IMS Connect feature in this release of the gateway enables you to continue to use existing TIPs.
Follow these instructions:
Refer to Chapter 12, "Gateway Configuration Using TCP/IP Communication Protocol" for instructions to load the
Use PGAU to regenerate the IMS TIPs.
Add the following new TCP/IP parameters to the
You will find descriptions and information about adding these parameters in Section 14.1.5, "Parameter Changes: Version 4 to Release 11.2 of the Gateway". You will also find descriptions of the parameters in Appendix B, "Gateway Initialization Parameters for TCP/IP Communication Protocol".
Note:If your TIPs from a previous version of the gateway were already defined using a SideProfileName and the
NLS_ LANGUAGEparameter has been set to a value of
american_america_us7ascii, then you will not need to recompile these TIPs. You still need to map your parameter values using the
Note:TIPs must be recompiled when changing communication protocol from SNA to TCP/IP.
If you have existing TIPs that were generated previously on a gateway using the SNA communication package protocol, and you want to use the new TCP/IP feature, then the TIPs 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 appropriate user exit in IMS Connect is being used, which would translate between the appropriate ASCII and EBCDIC character sets.