1 person found this helpful
There seems to be a bit of chatter regarding issues in 3.0.3 in particular. I would suggest rolling back a version notch and re-try.
Yup, so when I installed 3.0.2 now everything is working. Not sure how regression testing works at Oracle but there is no way 3.0.3 was production ready when a basic test fails!
Having the same issue with the installation of ORDS 3.0.3 . Thank you for the sharing, it save my time to figure out.
The bug was identified a while back and should have been addressed in the 503 patch. We're checking on what happened.
This is an unfortunate bug that affects APEX 5.0.3 *new* installations. It does not affect those installations where the APEX 5.0.3 patch set is applied. I filed the bug:
Bug 22588461 - ORDS 3.0.3 FAILS WHEN RUN AGAINST A NEW INSTALLATION OF APEX 5.0.3
We're working on a fix right now and hope to have this resolved by close of business today. I apologize for the confusion and time wasted that this has caused.
I fear, I have to contradict.
Just for the records and for correctnes:
This bug effects also "old" 5.0.x" installation that has been patched onto 5.0.3.
and when in that process also ORDS 3.0.3 has been installed over a "old" 5.0.2.
Excacly such constallation was the case for me.
I am not so sure that it can't work. I use it exactly in this combination, ords 3.0.3 and apex 5.0.3 (upgraded from 4.2.x => 5.0 => 5.0.1 => 5.0.2 => 5.0.3 ).
And it all works, both with running on Tomcat and also on the command line using the standalone jetty version.
But I really couldn't get ords 3.0.3 to run on AIX, in that patch there is now a hard dependency on the oracle JDK and a specific X509 implementation, so it won't run with an IBM JDK.
I also did have a few hiccups with 3.0.3 and nowadays I don't install the ORDS_METADATA repository for the new ords features any more when I configure APEX. Then I typically install APEX and run the apex_rest_config.sql to enable the APEX 4.2 restful integration so that APEX 5.0 can serve the static files.
When I want to use the new restful services I create another DAD using
java -jar ords.war setup --database rest
and then map it to a different url:
java -jar ords.war map-url --type base-path /rest rest
That way the "old" and the "new" restful services are better separated ... takes away some of my pains .
Best of luck,