Limitations for copying database definitions to a project

Some limitations apply when you copy a database definition from the Database Explorer to a project in the Data Definition view. Some of these limitations have workarounds.

• If you copy a DB2 Universal Database for Linux, UNIX, and Windows or DB2 Universal Databaseâ for iSeries table with a DATALINK column data type, the link control options for the column will not be copied. The DATALINK column length will change to 200, and the link options will change to NO LINK CONTROL. You can update these properties in the table editor after you copy the table to the Data Definition view.

• Schema and table metadata might not be copied when you use a DB2 Universal Database Version 8 client to connect to a Version 7 or earlier of DB2 Universal Database for z/OS database. To fix the problem, install DB2 Universal Database for z/OS PTF UQ72081.

• Character string data types might not be copied properly for connections to iSeries servers. The types CHAR FOR BIT DATA, VARCHAR FOR BIT DATA, and LONG VARCHAR FOR BIT DATA might be copied without the FOR BIT DATA options. To fix this problem, use the table editor in the Data perspective to edit the affected columns.

• Schema object names that contain DBCS characters might not be copied properly from iSeries systems. Delimited identifiers might be missing quotation marks. To fix the problem, use the table editor to edit the column and constraint names.

• Identifiers for primary key constraints are not copied for OS/390 connections.

• Column default values that are stored procedures or functions, or that are defined with an identity clause are not copied properly and can produce non-ASCII characters in a table document. The non-ASCII characters cause problems when the document loads. To fix this problem, edit the problem tblxmi document and remove the default tag and value.

• If you copy a table, the foreign keys must be ordered in the same sequence as the referenced primary keys. Otherwise, the foreign keys will be mapped incorrectly.

• When you copy a table that contains a foreign key, copy the table with the primary key at the same time. You cannot copy tables that contain foreign key references on their own.

 

Parent topic

Defining database objects