Recursive Datetime Type Checking
Administrators use this system setting to specify whether to enforce strict recursive data type checking for comparisons between identical data types (for example, integer to integer) or non-compatible data types (for example, integer to short integer) on all data sources or with all datasets.
Valid Values
- On — Enforces strict recursive checking for identical or noncompatible data types on all data sources or datasets. Default
- Off — Relaxes strict recursive checking for
date and time data types on all data sources or datasets. However, if there are
too many data type inconsistencies, you may want to change the data types to be
compatible or use constants of the correct data type when comparing a column to
a value. For example, after you migrate content from Oracle BI Enterprise
Edition to Oracle Analytics, you might start seeing this type of check error in your reports because eary
versions of Oracle BI Enterprise
Edition didn't enforce strict checks:
[nQSError: 22024] A comparison is being carried out between non-compatible types <type1> and <type2>
Apply Required
Yes.
Change Effective
After a few minutes.
Edition
Professional and Enterprise.
API Key and Values
API Key — RecursiveDatetimeTypeChecking
API Values —
YESNO