JimTRjr wrote:based upon the plethora of provided details, I can conclude that the source of the error is either an Oracle bug or Problem Exists Between Keyboard And Chair.
I'm having an issue how the sql parser is treating my hiearchical query across a dblink. Right now, I'm still developing in Toad in my APEX database, however this is not really an APEX issue, but more of a general database question.
I can write a query in my main application database that works. I can write queries in my APEX database with links to my parent database that work just fine. When I try to tackle a working hiearchical query (one with start with and connect by syntax) from my parent database, copy into my APEX DB, add the appropriate dblinks to all the table references, the query errors.
When I run an explain plan, reveiw the associated parced SQL, the parcer is not correctly identifying my alias' and throws an error that a column is not in the table. I tried removing all alias that I could, but the problem is I have two joined tables that have the same column names in my base query, so one at least one of needs to be aliased. The pasrser is not recognizing the alias. The parcer will reassign is own alias as A10, A11, etc..., but when it tries to find A10.aliased_column, it throws the error.
Any advice using hiearchical queries across a DBlink?
Edited by: JimTRjr on Feb 1, 2013 2:52 PM
JimTRjr wrote:then post reproducible test case so we can test it ourselves.
I'm leaning toward the bug side, verses the keyboard and chair.
Edited by: JimTRjr on Feb 1, 2013 3:06 PM