Recieving 904 error when querying local collections

Question

We've been recieving an intermitant bug within several packaged routines when we attempt to query local table collections.
We've bounced between using the old "THE(SELECT(CAST...) from dual) d" and new "TABLE(CAST...) d" syntacticals for several weeks.
On recompilation of the packages, a 904 error is raised on casting out of the collection. We literaly put back the old/new syntactical and all is well until the next build when we recieve the same 904 error once again.
The problem seems to arise most often in objects that have methods which either use other packaged code or access table data. The collections are valid at runtime in all occurances of the issue.
We're running 8.1.6 Release 3 on Sun boxes. Oddly, our development NT boxes rarely exibit the error even with hundreds of builds a day.
Has anyone come across this same issue, and is there a fix or a simple WA (not catching the 904 error and trying the other syntactical flavor - too much maintenance).
Thanks in advance
Cheers
S T U E
null

Answer 1

I had the same or vary similar problem.
I solved it by changing the ${oracle.jdeveloper.deploy.dir} in the internal-targets.xml file to the middleware home mine was /oracle/fmwhome using the new PS6 example VirtualBox download.
This is the old path in the internal-targets.xml file: /oracle/jdevhome/jdeveloper/modules/net.sf.antcontrib_1.1.0.0_1-0b2/lib
Here is the new path: /oracle/fmwhome/modules/net.sf.antcontrib_1.1.0.0_1-0b2/lib
This reference is around line 12 in the taskdef
<taskdef resource="net/sf/antcontrib/antcontrib.properties">
<classpath>
<pathelement location="${middleware.install.home.directory}/modules/net.sf.antcontrib_1.1.0.0_1-0b2/lib/ant-contrib.jar"/> i changed this line middleware.install.home.directory is a var that points to /oracle/fmwhome
</classpath>
</taskdef>
Hope this helps.
Edited by: 825836 on Aug 15, 2012 11:31 AM