When you import a reference table from an Oracle, IBM DB2, or Microsoft SQL Server database, the Analyst tool cannot display the preview if the table, view, schema, synonym, or column names contain mixed case or lowercase characters.

To preview data in tables that reside in case-sensitive databases, set the Support Mixed Case Identifiers attribute on the database connection to true.

When you create a reference table from inferred column patterns in one format, the Analyst tool populates the reference table with column patterns in a different format.

For example, when you create a reference table for the column pattern X(5), the Analyst tool displays the following format for the column pattern in the reference table:

XXXXX

.

When you import an Oracle database table, verify the length of any VARCHAR2 column in the table. The Analyst tool cannot import an Oracle database table that contains a VARCHAR2 column with a length greater than 1000.

To read a reference table, you need execute permissions on the connection to the database that stores the table data values. For example, if the reference data warehouse stores the data values, you need execute permissions on the connection to the reference data warehouse. You need execute permissions to access the reference table in read or write mode. The database connection permissions apply to all reference data in the database.

When you run a mapping with a transformation that specifies a reference table, the mapping uses the current version of the reference table in the Model repository. You cannot select an historical version of the reference table when you configure the transformation.

If another user restores the reference table to an earlier version in a concurrent Developer tool session, the reference table versions are no longer identical across the sessions. If you configure and run a mapping that uses the reference table, the mapping might fail, because the current session does not identify the current reference table version. To ensure that the mapping uses the current reference table, refresh the Model repository before you run the mapping.

When you configure an unmanaged reference table to permit edits, verify that the reference table uses simple data types such as string and number. Also, verify that the reference table does not define any constraint on the reference table metadata or make use of default values for columns.