Skip to Main Content
  • Questions
  • The request could not be mapped to any database

Breadcrumb

Question and Answer

Connor McDonald

Thanks for the question, Murugananth.

Asked: February 02, 2021 - 2:22 am UTC

Last updated: February 02, 2021 - 6:46 am UTC

Version: 20.2

Viewed 10K+ times! This question is

You Asked

Hi,
I have installed apex with ORDS(20.3) (and Tomcat) and I am getting below error (once in a month)

'The request could not be mapped to any database. Check the request URL is correct, and that URL to database mappings have been correctly configured'
We usually unlock APEX_LISTENER,APEX_REST_PUBLIC_USER,APEX_PUBLIC_USER,ORDS_PUBLIC_USER users and restart Tomcat.
Please let us know if there is any permanent fix for this issue

and Connor said...

Check out Jeff's FAQ on this topic

https://www.thatjeffsmith.com/archive/2020/01/ords-frequently-asked-questions

Most commonly it is a URL construction error - you shouldn't need to be altering any database users when this occurs. If those accounts you listed are getting locked, this would suggest someone is trying to connect with the wrong password (either via ORDS or directly) causing them to be locked, which could then cause the issue (because we no longer can connect to APEX)

Rating

  (1 rating)

Is this answer out of date? If it is, please let us know via a Comment

Comments

Murugananth, February 03, 2021 - 6:27 am UTC

This could not be URL construction error as I could access same url previous day and the next day I facing the error.
The issue could be because the accounts are expiring
I found the below post on this. I will update here if the issue persists
https://connor-mcdonald.com/2019/01/11/my-apex-was-fine-and-then-it-wasnt/