Categories
- All Categories
- 15 Oracle Analytics Sharing Center
- 15 Oracle Analytics Lounge
- 208 Oracle Analytics News
- 41 Oracle Analytics Videos
- 15.7K Oracle Analytics Forums
- 6.1K Oracle Analytics Idea Labs
- Oracle Analytics User Groups
- 76 Oracle Analytics Trainings
- 14 Oracle Analytics Data Visualizations Challenge
- Find Partners
- For Partners
OAC - erreur on a simple calculation (count distinct) placed on a Tile component

Hello,
From a while a have this error when I put a filter in this simple test workbook. I create also a support ticket for that ( 4-0000564990 ) a month ago but thet don't find anything yet. I suppose that is a bug after the March 2025 version because I don't have this error before.
Without filter on the first field (Etablissment) work very fine, but if i chose a any value I have an errour (here AL003 - CH DIE). This is a classic dimension field. The calculation is: Nb familles metiers = COUNT(distinct "DOM_BVA_CM_PNM"."Dim Metier"."Famille metier (code)")
It seem that the error it's related to AGO fonction (the second filter on date). The date is in format DD/MM/YYYY in datebase and workbook, I met also
GMT+01:00 in OAC console settings. If I chose no date on second filter It works also but if I choose one I have the error message.
[nQSError: 46043] Internal error: No matching table for expr A_BVA_CM_FACT_PNM.ETAB_ID, File server/Query/Optimizer/SmartScheduler/PhysicalRequestGenerator/Src/SQOSPSimplifyJoin.cpp, line 214.",
Il semble que vous utilisiez peut-être un objet non-date avec la fonction AGO. VoirOAC Error While Using AGO Function With Non Date/Time Column or Attribute
Thanks,
Daniel
Answers
-
Hi
This error normally happens if you are using time series calculated for a non-date/time datatype column. Can you please confirm data type of the date filter column?
thanks
Gayathri
1 -
Hello,
The format for the DATEREFENCE field is DATE (in the Oracle schema and in the physical layer of the SM).
In the workbook in the dashboard filter the format in set to Auto (dd/MM/YYYY) and the field is recognized as Date as you see below. I don't understand the error related to the time series (AGO function or other).
Thanks!
0 -
Hello @GayathriAnand-Oracle and thanks for the answer on the SR 4-0000564990.
I didn't have any solution yet on my problem (SR opened 2 months ago affected to a guy named Nathan that sugest me to close it and open another SR).
Daniel
0 -
Hi Daniel
We will have a zoom call with you to review this issue. SR will be updated. Thank you for your patience.
Regards
Gayathri
0