SYMPTOM:
Consider that a column from a partition mapping table (PMT) is to be added to an attribute form. When browsing to the PMT in the Attribute Editor in Strategy Developer 9.4.1 - 10.x, no columns show up, as shown:
The physical view of its base tables also does not show any columns:
The same is seen when going to Warehouse Catalog and checking the Table Structure:
However, existing schema objects which are mapped to this PMT continue to show the columns correctly
CAUSE:
When the existing project tables in the Warehouse Catalog are read and any PMT tables are encountered, the entire data from the PMT table is retrieved. This is to get the list of base tables of the PMT. This data is brought back in an unordered form i.e. the SQL generated to get the data from the PMT table does not contain any ORDER BY clause. Next, the columns of the base table corresponding to the first row of data from the PMT table are attempted to be read from the warehouse database. If this table is not present in the warehouse, Warehouse Catalog is unable to establish the column structure of the base table, and hence the base table physical view shows no columns.
This is a known issue with Strategy Developer 9.4.1 - 10.x
ACTION:
Contact Strategy Technical Support for an update on the status of this issue.
WORKAROUND:
Since there is no way of knowing which table will be in the first row of data from the PMT table, the number of rows in the PMT table and the actual base tables existing in the project warehouse must be consistent.
