Skip to Main Content
Forums

ORDS, SODA & JSON in the Database

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

ORDS 19.1 RESTFul-Service 404 not found Messages with db.customURL

AndyHJun 5 2019 — edited Jun 6 2019

We have an ORDS configuration using customURL.

Upgraded ORDS from 18.4 to 19.1, all APEX access works without error but RESTful access fails with a 404 and a message referring to not finding the database and URLMapping.

Returned to ORDS 18.4 and all works.

I noticed a similar thread in July 2018 regarding an upgrade between 18.1 and 18.2 - at the time @"ossiossi" was talking with @"thatJeffSmith-Oracle" about raising a bug with Oracle, but I've not been able to find a reference to it and a workaround.

Anyone else had this issue? Anyone resolved it?

--

Andy

Message was edited by: AndyH Original ORDS version was 18.4, not 18.1

Comments

Emad Al-Mousa

please check this documentation from oracle: http://docs.oracle.com/cd/B19306_01/network.102/b14213/sqlnet.htm

recommended value is 10

SQLNET.EXPIRE_TIME=10

can you try it and update us if it works fine with you...

garywicke

Thanks for the quick response.


I have set the parameter to 120 minutes due to the way the application needs to connect to the database.  It holds the connection open on purpose and I need it to be 120 minutes to cover the gap in processing time. 


I'm looking to find out more details about when and why the database connection is being dropped by the database if indeed it is being dropped from the database side at all.


I was hoping there was an database audit command but I haven't found it yet.


Thanks again!!


-gary

Ratnesh Kumar Roy

Hello,

Where  do you get this issue.  It usually comes in sql developer when you connect to database.

Regards.

garywicke

Thanks for your response!


As noted above the application holds the database connection open while it does some SELECTs and some processing and then tries to write the data back out to the database but by that time it appears the connection has been open too long and the application gets a 'Connection closed' error message.


I've raised the SQLNET.EXPIRE_TIME to 120 minutes and the error occurs before that much time has expired so I'm assuming that parameter is not the cause.


The profile for the user has the IDLE_TIME set to UNLIMITED so I ruled out that as well.


The network folks say there is no firewall parm set to cancel a connection.


I'm looking for the AUDIT command or whatever setting I can change in the database to increase the audit trail detail to try and identify who is breaking the connection and why. 


Is there a database tracing parm I can set to see all the detail about the connections and especially when the database terminates one?



Thanks very much!

-gary

garywicke

This did indeed turn out to be a firewall setting.

My original question was never answered so I'm closing the discussion.

I'll try elsewhere.

-gary

1 - 5

Post Details

Added on Jun 5 2019
4 comments
1,803 views