Migrating to new instances of the 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 will 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 the Oracle Database Gateway for APPC for Microsoft Windows. It contains the following sections:
Follow these steps to migrate an existing gateway to 12c Release 1 (12.1) of the gateway using the SNA communication protocol.
Note that if you are using the gateway's 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 initsid.ora file. Proceed to "Parameter Changes: Version 4 to 12c Release 1 (12.1) 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 an existing gateway installation. Doing so will corrupt the existing installation.Copy the initsid.ora file from the old gateway instance to the new instance.
Note that if you are migrating from Release 9.0.1 or earlier of the gateway, then PGA_TRACE is not supported, you will need to modify the parameter to TRACE_LEVEL, instead.
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 will help ensure minimal downtime between changes to different gateway instances.
The 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 communicate to Oracle Net that the gateway uses HS facilities. For more information, refer to "Configuring the Oracle Network for the Gateway".
This release of the Oracle Database Gateway for APPC introduces new and changed initialization parameters if you are migrating from version 4 gateway to 12c Release 1 (12.1) of the gateway.
Note:
This section does not apply to you if you are migrating to 12c Release 1 (12.1) from version 8 of the Oracle Database Gateway for APPC.If you are using the gateway's TCP/IP support for IMS Connect, then you will not be migrating from version 4 to the current release of the gateway. However, you will need to place valid Heterogeneous Services parameters into your initsid.ora file.
This chapter contains references to the particular HS parameters 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.New Gateway Initialization Parameters
The following parameters are in the gateway initialization file (initsid.ora):
Note:
TheHS_ parameters are specific to Oracle Heterogeneous Services. For details on HS parameters, refer to the Oracle Database Administrator's Guide.Renamed Gateway Initialization File Parameters
Following is a list of the gateway initialization file (initsid.ora) parameters that have been renamed in this release of the gateway, the parameters' former names are shown in parentheses.
The following parameters are now obsolete. Please remove them from your configuration files:
MODE
SERVER_PATH
ERROR_LOGGING
ERROR_REPORTING
ERRORTAG
GATEWAY_SID
GROUP_BY_OFF
GTWDEBUG
INCREMENT_CURSORS
INIT_CURSORS
LIST
MAX_LOG_SIZE
OPTIMIZE_FILE_OPEN
ORDER_BY_OFF
RESOLVE_BINDS
RETRY
SET
SNMP_SUPPORT
SQL_TRACE
TRIM_CURSORS
D_OPEN_CURSORS
D_INIT_CURSORS
D_INCREMENT_CURSORS
D_TRIM_CURSORS
PGA_TRACE
The following sections are for users who have an existing release of the gateway using the SNA protocol but who wish to switch to using TCP/IP support for IMS Connect.
The TCP/IP support for IMS Connect feature in this release of the gateway allows you to continue to use existing TIPs.
Follow these instructions:
Make sure you have used the pg4tcpmap tool to insert valid parameter values into the PGA_TCP_IMSC table.
Refer to Chapter 9, "Gateway Configuration Using TCP/IP Communication Protocol" for instructions on loading the PGA_TCP_IMSC table.
Make sure that the LANGUAGE parameter in your TIPs is set to american_america_us7ascii.
Use PGAU to regenerate the IMS TIPs.
Add the following new TCP/IP parameters to the initsid.ora file:
PGA_TCP_DB
PGA_TCP_USER
PGA_TCP_PASS
You will find descriptions and information about adding these parameters in Parameter Changes: Version 4 to 12c Release 1 (12.1) 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 side profile name and theNLS_LANGUAGE parameter has been set to a value of american_america_us7ascii, then you will not need to recompile these TIPs. You will still need to map your parameter values using the pg4tcpmap tool.Note:
TIPS must be recompiled when changing the communication protocol from SNA to TCP/IP.If you have existing TIPs that were generated previously on a gateway using the SNA 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 suitable ASCII character set in the DEFINE TRANSACTION command.
This is due to the fact that the gateway assumes that the suitable user exit in IMS Connect is being used, which would translate between the suitable ASCII and EBCDIC character sets.