Follow these instructions to troubleshoot common issues for Endeca integration.
Troubleshooting ETL
To troubleshoot ETL, view logging information in the ODI Operator tab. Key areas of interest include row counts, logical SQL for the business model mapping, and the timing of steps in the ETL. To troubleshoot logical SQL, obtain the SQL from the Operator, then run it in IssueSQL in Log Level 2 and obtain the SQL query from the Oracle BI Server's log, nqquery.log.
Note that repository metadata changes may impact ETL. If columns of joins are modified in the RPD, this may impact data extracted by ODI. Also, ROW_WID = 0 rows may cause less or no data to be returned if a fact table is joined to a dimension table missing a ROW_WID = 0 row.