YTD, QTD and Year grain metrics = ORA-00942: table or view does not exist

Question

Hi everyone,
I'm having a weird issue. I've got some GL data that I want to report on in three different grains: Quarter To Date, Year To Date and Entire Year. For the first two measures, I've setup a time dimension and I'm using the ToDate function. Works perfectly. For the third measure, I select the SUM aggregation and then in the Levels Tab, I go to my time dimension and set the logical level to "Year".
Each measure reports correctly by itself, however, when I join in the three in one report, the who thing blows up on me and gives me an ORA message:
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 17001] Oracle Error code: 942, message: ORA-00942: table or view does not exist at OCI call OCIStmtExecute. [nQSError: 17010] SQL statement preparation failed. (HY000)
When I only do two of the measures (any two), the report works fine. But it's when I add that third measure in, I get myself in trouble. Additionally, I checked the log file and the report never gets to the point where it generates a physical query. It's only creating a logical query and then it doesn't save the physical query anywhere.
Can anyone explain what the problem is? Why don't these three measures behave well together? What can I do to force them to co-operate?
It seems that the real culprit is the entire year measure. It only behaves well with 1 other measure, but once you get two additional measures, it causes the report to get the ORA error.
Thanks for any help you can give!
-Joe

Answer 1

It turns out I was incorrect that there were no physical queries being generated. They were there in the log files, they had so many SAWITH<number> clauses that I thought they were the logical query (i.e. saw_0, saw_1, etc).
Once I found the physical query, I ran it by hand and also got the table did not exist error. I added in WITH clause by with clause until I got the error to occur. After about an hour of digging, it turned out that a query using a full outer join (about 16 queries in) caused the table does not exist error. I'm not sure what it is about the full outer join that makes Oracle not see the table. When I get some free time I'll dig deeper into that issue.
But once I realized what was going on, I went into the DB connections and disabled FULL OUTER JOINs. No problem now.
Like I said, if I find what caused the original problem (i.e. what syntactically was incorrect about the FULL OUTER JOIN), I'll update this post.
-Joe