After a Clarity refresh that refreshes the Clarity database from an environment that has SQL Curves enabled to one that doesn't, the Load Data Warehouse fails. In the Data Warehouse logs there are errors related to the Curve tables.
Here is an example:
ERROR: ENCOUNTERED EXCEPTION WHILE MERGING INTO DWH_FIN_PLAN_CRV_FACTS. function dwh_cast_curve_fct(HOSTNAME.nk_curve) does not exist
Where: PL/pgSQL function inline_code_block line 22 at RAISE
Turning off SQL Curves will also fail, because it will attempt to remove information from the DWH that doesn't exist, and fail as well.
Clarity Any Release
The Clarity database anticipates that SQL Curves is already enabled in the DWH database, but the DWH tables do not contain the Curve information.
A rebuild of the DWH database is recommended to resolve this issue.
To avoid the problem in the future, the SQL Curves feature should be consistently enabled across environments.