| Oracle® Transparent Gateway for DRDA Installation and User's Guide 10g Release 2 (10.2) for UNIX Part Number B16217-02 |
|
|
PDF · Mobi · ePub |
| Oracle® Transparent Gateway for DRDA Installation and User's Guide 10g Release 2 (10.2) for UNIX Part Number B16217-02 |
|
|
PDF · Mobi · ePub |
Migration to new instances of Oracle Transparent Gateway for DRDA from an existing installation is straightforward, provided some guidelines. This chapter covers how to make these new installations as easy as possible.
This chapter provides information that is specific to 10.2 release of the Oracle Transparent Gateway for DRDA. This chapter contains the following sections:
Migration is the process of converting an installed version of an Oracle Database into a later version. This migration generally involves running the Oracle Migrate (MIG) utility to modify Oracle Database control file structures from the format of one version to the format of another version.
Upgrading is the process of converting an Oracle Database from an installed release into a later release of the same version. For example, transforming patch release 8.0.3 into patch release 8.0.4 is called upgrading.
Step 1: Install the New Release
Install the new release of the gateway in a separate directory, as discussed in Chapter 4, "Installing the Gateway".
Caution:
Do not install the gateway over a previously existing gateway installation. This corrupts the existing installation.Step 2: Transferring initsid.gtwboot Gateway Boot Initialization parameters.
In previous releases, the gateway used two Gateway Initialization files ( initsid.gtwboot and initsid.ora), or it used a Startup Shell Script (drdaDB2.sh) and one initialization file (initsid.ora). In this release, all parameters have been migrated into a single Gateway Initialization file: initsid.ora. Migrating a previous release involves copying the parameters from the initsid.gtwboot or Startup Shell Script into the initsid.ora. The format of the parameters can be found in Appendix C, "DRDA-Specific Parameters".
Step 3: Transferring initsid.ora Gateway Initialization File parameters.
Copy the initsid.ora from the old gateway instance to the new instance. The formats of the parameters in the initsid.ora Gateway Initialization File have changed. Refer to "Gateway Initialization File Parameters" in Appendix C, "DRDA-Specific Parameters".
During the migration from version 4, version 8, or version 9 gateway instances to the latest Oracle Database 10g release, if problems are encountered, then it is always possible to revert to the previous version. Assuming a working version 4 gateway instance exists, simply change the TNSNAMES.ORA entries from using the Oracle Database 10g gateway instance to the older version 4 instance. Remember to remove the "(HS=)" entry from the SQL*Net connect definition.
Oracle recommends that you keep the old gateway home and instance configurations intact and operational, when you are installing a new release of the gateway and upgrading the existing instances, in case you have problems with the upgrade. This will ensure minimal downtime between changes to different gateway instances.
The 10.2 release of the Oracle Transparent Gateway for DRDA introduces new and changed initialization parameters if you are migrating from a version 4, version 8, or version 9 gateway to the Oracle Database 10g gateway.
Parameters introduced in the 10.2 release of the gateway, listed in the following table, may be added to the Gateway Initialization File:
DRDA_CACHE_TABLE_DESC
DRDA_GRAPHIC_LIT_CHECK
DRDA_GRAPHIC_PAD_SIZE
DRDA_GRAPHIC_TO_MBCS
DRDA_MBCS_TO_GRAPHIC
DRDA_PROCDESC_STMT
DRDA_PROCDESCPARMS_STMT
DRDA_PROCCALL_MASK
DRDA_FUNCDESC_STMT
DRDA_FUNCDESCPARMS_STMT
DRDA_FUNCCALL_MASK
DRDA_GRAPHIC_CHAR_SIZE
The usage of the following parameter has changed in version 9 of the gateway:
DRDA_CONNECT_PARM
The following table lists the parameters whose names have been changed in version 9 of the gateway, and their corresponding old names. Refer to Oracle Database Heterogeneous Connectivity Administrator's Guide for more detailed information about these parameters.
| New Name | Old Name |
|---|---|
HS_COMMIT_STRENGTH_POINT |
COMMIT_STRENGTH_POINT |
HS_DB_DOMAIN |
DB_DOMAIN |
HS_DB_INTERNAL_NAME |
DB_INTERNAL_NAME |
HS_DB_NAME |
DB_NAME |
HS_DESCRIBE_CACHE_HWM |
DESCRIBE_CACHE_HWM |
HS_LANGUAGE |
LANGUAGE |
HS_NLS_DATE_FORMAT |
NLS_DATE_FORMAT |
HS_NLS_DATE_LANGUAGE |
NLS_DATE_LANGUAGE |
HS_OPEN_CURSORS |
OPEN_CURSORS |
HS_ROWID_CACHE_SIZE |
ROWID_CACHE_SIZE |
The following parameters are obsolete for the 10g version. Remove them from your configuration files:
MODE
SERVER_PATH
DRDA_OVERRIDE_FROM_CODEPAGE
DRDA_OVERRIDE_TO_CODEPAGE
ERROR_LOGGING
ERROR_REPORTING
ERRORTAG
gateway_SID
GROUP_BY_OFF
GTWDEBUG
INCREMENT_CURSORS
DRDA_CALLDESC_STMT
DRDA_CALLDESC_PROC
A part of the Normal Installation for the gateway involves binding a package and (as an option) installing data dictionary views on the DRDA Server. This release of the gateway (10.2.0) is compatible with version 4, version 8, and version 9 packages that have been previously bound. The data dictionary views, however, have changed with the 10.2 release. If you plan to utilize the data dictionary views that are provided by the gateway, then you must migrate to the new views. Oracle recommends that you install the new views as discussed in Chapter 11, "Configuring the Gateway". If you have changed certain DRDA parameters of the Gateway Initialization parameters as a result of the migration, then a rebind of the package will be required.
The gateway uses the Heterogeneous Services (HS) facilities of Oracle Database and Oracle Net. gateway service name entries in the tnsnames.ora need a slight modification so that Oracle Net that the gateway will be using the HS facilities. Refer to "Configuring Oracle Net" for detailed information.
|
 Copyright © 2005, Oracle. All rights reserved. Legal Notices |
|
