1. We are loading dv tables using data warehouse. None of the dv tables are being referenced in the data mart. But I can't run datamart jobs while the DV load is running for tables which are not being referenced in the mart. Is this by design ?
2.We deployed compose to Prod for the first time. And while generating ETL commands under data warehouse section for some of the tables I am getting below error. I verified the landing tables are present in both Compose model as well in the db. I have to open that table in the ETL set and manually associate the source table name from the drop down.
Just wanted to know why this issue is happening ?
Mapping Map_FACTS_COUNTRY_PLAN_BREAKDOWN_CMDM uses table FACTS_COUNTRY_PLAN_BREAKDOWN that does not exist in the source Mapping Map_FACTS_SOURCE_DATA_FEED_CMDM uses table FACTS_SOURCE_DATA_FEED that does not exist in the source Mapping Map_META_CMDM_SOURCE_PRECEDENCE_CMDM uses table META_CMDM_SOURCE_PRECEDENCE that does not exist in the source Mapping Map_META_CTMS_EVENT_CONFIG_CMDM uses table META_CTMS_EVENT_CONFIG that does not exist in the source Mapping Map_META_REF_DATA_CATALOG_CMDM uses table META_REF_DATA_CATALOG that does not exist in the source
1. You cannot run a mart task while a DW load is running. The ETL Runno's are used as part of the mart processing to detect new records that have changed, and with missing reference processing we need to ensure the warehouse is quiesced while the mart refresh is executed.
2. For ETL generation - please click "Clear Landing Cache" before code generation.(Open the Manage ETL Sets / Manage ETL tasks screen) . Compose has a metadata cache that it manages and its possible the landing cache was populated before the source tables were created . Please try that and let me know if that resolves the issue.
