Strange number comparison behaviour in Oracle 11.2.0.3.0 with existsNode

Check out document number, Doc ID 14087914.8 (Bug Number 14087914) on support.oracle.com.

Per the document, try to following to see if the results no produce what you are expecting.

alter session set "_fix_control"='9569678:off

Your other option, involves upgrading to 11.2.0.4.

CodeHunter