When loading an OLAP cube from a star schema, if a key from the fact
table is found to have no match in the corresponding dimension table,
the cube build will fail with errors such as:

   ERROR: A key was found for a member of the "TIME" dimension in
          fact table that cannot be found in the "WORK.TIME"
          dimension table.
   ERROR: The fact keys cannot be mapped during the loading of star
          schema.
   ERROR: Cube "missingkey" cannot be created.

or:

   ERROR: More unique keys were detected in the fact table than in
          the dimension table for the "TIME" dimension.
   ERROR: The fact keys cannot be mapped during the loading of star
          schema.
   ERROR: Cube "missingkey" cannot be created.

The problem is in determining how many and which precise keys only exist
in the fact table. This could be very time consuming and not always
necessary if your data does not have to be completely clean.

This problem will soon be addressed in a 9.1.3 Service Pack with the
addition of a new option for PROC OLAP. The IGNORE_MISSING_DIMKEYS
option can be specified when building a cube from a star schema to allow
the SAS OLAP Server to ignore and log error conditions detected when the
fact table contains foreign keys that are not present in one of the
contributing dimension tables and enable the cube creation to complete
successfully.

The IGNORE_MISSING_DIMKEYS can be set to either TERSE or VERBOSE. When
IGNORE_MISSING_DIMKEYS=TERSE is specified, the cube build continues and
the fact table row with the missing key is ignored and is not included
in the cube. The SAS log receives an entry that lists the total number
of key values that are missing from each dimension table. Specifying a
value of VERBOSE produces the same behavior, except that the log
receives additional information where the missing keys are listed for
each dimension table.


A fix for SAS 9.1.3 (9.1 TS1M3) for this issue is available at:

http://www.sas.com/techsup/download/hotfix/e9_sbcs_prod_list.html#014309

For customers running SAS with Asian Language Support (DBCS), this
fix should be downloaded from:

http://www.sas.com/techsup/download/hotfix/e9_dbcs_prod_list.html#014309

Operating System and Release Information

A fix for SAS 9.1.3 (9.1 TS1M3) for this issue is available at:

A fix for SAS 9.1.3 (9.1 TS1M3) with Asian Language Support (DBCS) for this issue is available at :