Known issues and limitations for Data Gate

Limitations

Maximum of one Db2 for z/OS source

A single Data Gate instance can have a maximum of one Db2 for z/OS source.

Maximum of one target database

A single Data Gate instance can have a maximum of one target database ( Db2 or Db2 Warehouse).

Columns with a data type of XML or LOB are not supported

Columns with a data type of XML or LOB are not supported. A Db2 for z/OS table with unsupported columns can be added into Data Gate, then be loaded and synchronized. But the values of the columns with these unsupported types will therefore be missing in the target table.

Table load and synchronization conditions

A table cannot be loaded and synchronized if one or more of the following conditions apply:

• A mask has been defined for the table with a CREATE MASK statement.
• A permission has been granted on a table column with a CREATE PERMISSION statement.
• One or more table columns have a security label.
• One or more table columns use a field procedure (FIELDPROC).

Important: If you try to load and synchronize a table that satisfies one of these conditions, the Data Gate server on Cloud Pak for Data stops and then restarts automatically after an outage period of five to ten minutes. Hence, you need not do anything to recover from the server shutdown.

Maximum of 100 synchronization-enabled tables

You can load a maximum of 100 synchronization-enabled tables concurrently.

Indexes and access control lists are not inherited

Indexes and access control lists defined on the Db2 for z/OS source tables will not be inherited by the Data Gate target tables.

Red Hat OpenShift route exposure limitation

A Red Hat® OpenShift® route can only expose a single hostname with a fixed port of 443 for external access. Therefore, when you provision your first Data Gate instance, the route port is 443 by default. If you want to provision more than one instance to connect to the same z/OS LPAR, you must specify a different port, for example 44443. This means that on the z/OS side, you must configure the Policy Agent rule accordingly. That is, the rule needs to specify the second hostname and port that is specified when the Data Gate instance is provisioned. On the load balancer node, you must configure the forwarding rule so that it forwards requests from the specified port Data Gate instance that is specified to the Red Hat OpenShift route port (port 443). See the step ("In the Port field, specify the network port that is used by the route.") in Creating a service instance for Data Gate from the web client.