1. Start Oracle Universal Installer.
2. Enter the path of an existing ORACLE_HOME, or a new path for a stand-alone installation.
3. [Optional] Enter the ORACLE_HOME name.
4. Select Oracle Database Provider for DRDA for installation.
5. In the Interview panel, enter the following information:

   • Oracle Database Provider for DRDA listener host name and/or IP address

     Specify host name or IP address of the network interface where Oracle Database Provider for DRDA is the listener.

     Default is an empty string.

   • Oracle Database Provider for DRDA listener port number

     Specify the port number of Oracle Database Provider for DRDA Listener.

     Default is 1446.

   • Oracle Database Provider for DRDA RDB map name

     Specify the external relational database name that the client applications use as a location qualifier.

     Default is DRDAAS.

   • Oracle Database connection descriptor

     Specify the connection descriptor to use to connect to the Oracle Database. Valid values are:

     • TNS(tns_name_sentry), such as TNS(orcl)

     • oracle_sid or ORACLE_SID

       This accesses the local Oracle Database before Oracle Database Provider for DRDA starts, based on the setting of the environment variable $ORACLE_SID.

     • TNS-Descriptor

       For example:

       DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=drdaas))
       (CONNECT_DATA=(SERVICE_NAME=drdaas.us.oracle.com))); 
       

       Default is oracle_sid.

6. Select Finish.
7. At the command prompt, create a diagnostic directory:

   % mkdir -p $ORACLE_HOME/log/diag/dps

Typically, no additional parameters are needed beyond those specified during installation.

In more advanced scenarios, it may be necessary to specify more than one DATA_PORT parameter or configure more than one RDB_MAP entry. Still more complex installations may require multiple Oracle Database Provider for DRDA instances.

For a list of parameters and their options, refer to the section Configuration Parameters.

There are two sets of database objects that must be installed: Global Objects and Per-User Objects.

To facilitate correct interpretation of DRDA-based application SQL from it's native DB2 dialect to Oracle, the user must create a SQL Translation Profile.

SQL Translation Profiles are managed on a per-user basis. In contrast, DRDA packages are managed on the application basis. As a result, only one SQL translation profile name may be associated with a specific DRDA package. The same SQL Translation Profile may be also associated with many packages; for consistency, the same SQL Translation Profile should be associated with each defined package.

To create an additional translation profile, DRDA users must request a profile name from the DRDA administrator and then invoke the drdasqtt_translator_setup.sql script, in $ORACLE_HOME/drdaas/admin/ directory. The section ‘Create a SQL Translation Interface Package and Translation Profile demonstrates how to create a SQL Translation Profile for profile name DB2ZOS; this code creates the template of a translation profile.

The file drdaas.ora defines the instances of Oracle Database Provider for DRDA. This file is composed of initialization parameters that define the instances of the Application Server.

The file drdaas.ora may be customized. However, it may also be created at installation time from questions posed by the Installer and from user input.

The drdaas.ora configuration file must be located in the Oracle Home, under the product administration directory.

The default location is: $ORACLE_HOME/drdaas/admin.

Note that parameters that are qualified by the instance name apply only to that specific instance. Parameters that are not qualified by an instance name apply to all instances specified in the file.

# Example pre-configured instance named "drdaas"
# defines a single port and an rdb map that uses
# the local database instance accessed through
# the ORACLE_SID environmental variable.
drdaas.DATA_PORT = 10.0.0.1:1446
drdaas.RDB_MAP = RDB(DB2DS4M)->ORACLE_SID
#
# Example instance using a single port and a single rdb map
drdasingle.DATA_PORT = 10.0.0.1:1546
drdasingle.RDB_MAP = RDB(DB2DSN1)->TNS(ora101)
#
# Example instance using multiple rdb mappings
drdamulti.DATA_PORT = 10.0.0.1:2446
drdamulti.RDB_MAP = RDB(DB2DSN1)->TNS(ora101)
drdamulti.RDB_MAP = RDB(DB2DSN2)->TNS(ora102)
drdamulti.RDB_MAP = RDB(DB2DSN3)->TNS(ora103)
#
# global section affects all instances unless overridden
PROTOPROC_TRACE="ALL ERROR"

Users who must perform administrative functions must have the DRDAAS_ADMIN_ROLE role. This enables privilege grants on a specific DRDA package, and assigning package attributes (SQL translation profile name).

For installations that do not have the default role ALL, have several default roles for users, such as CONNECT or RESOURCE, and add the add DRDAAS_ADMIN_ROLE role to the default list.

The DRDAAS_ADMIN_ROLE role is not meant for users who must use the DRDA packages. They should have the DRDAAS_USER_ROLE assignment, instead.

Administration is mainly concerned with granting and revoking of privilege to users, setting attributes on packages, and dropping packages.

Users who create packages, or are designated as owners of a package, have implicit authority over that package and may grant access to others. For example, the package owner may grant RUN privileges to any number of users. An owner may also set package attributes and drop the package.

However, in order to bind a package initially, a user must have BIND privilege, either for any package in a collection, or specifically for that package. Only users who have the DRDAAS_ADMIN_ROLE role may grant authorization to users for packages that are not already bound, or are not created or owned by that user. For information on how to grant access to a package and how to set package attributes, refer DRDA Package Authorization.

The DRDA administrator must perform these functions before supplying the user with the DRDA package name and (optionally) the SQL translation profile name.

Only a DRDA administrator may grant access to specific DRDA packages.

Refer the section on Granting and Revoking a User’s Package Privileges to understand how to grant the BIND, DROP and EXECUTE privileges to user DRDAUSRx for package ORACLE.MYPACKAGE.

The DRDA Administrator may also designate a SQL translation profile name to associate with the DRDA package.

Refer the section on Setting and Deleting Translation Profile Name for a DRDA Package to understand how to set the profile name to DB2ZOS.

Each user who accesses the database through DRDA must have the DRDAAS_USER_ROLE user role as a default.

Users commonly have the default role ALL, which immediately enables all granted roles. If a user has explicit default roles, they must also have the DRDAAS_USER_ROLE role, as described in the section Adding DRDAAS_USER_ROLE to Default Values.

Note that failing to specify the complete list of default roles may prevent the user from connecting to the database, or form being able to address certain resources implicitly.

Refer to Oracle® Database SQL Language Reference and Oracle Database Security Guide.

1. Change directory to $ORACLE_HOME/rdbms/admin.

   > cd $ORACLE_HOME/rdbms/admin
   

2. Connect to the database using the SYSDBA option.

   connect / as sysdba
   

3. Run the removal script.

   catnodrdaas.sql
   

4. Drop the user-created tablespace sysibm and its contents.

   > drop tablespace sysibm;

1. In Oracle Universal Installer, click Installed Products.
2. Select the desired ORACLE_HOME.

   Either select the whole ORACLE_HOME, or open ORACLE_HOME navigation tree and select Oracle Database Provider for DRDA product software.

3. Click Remove.