we wait 15 minutes and then try again
The first time you try hit the pool, it doesn't exist, so it'll get marked bad in the pool cache with a timeout of 15 minutes. On the next request after the timeout expires ORDS will attempt to create the pool again. If it's present and correctly configured it will succeed and from that point it will work as expected
You can config this with db.invalidPoolTimeout
I will try this parameter. Is it documented ? Is it in minutes ?
you can set it to say
where m=minute, s=second, h=hour
I will try as soon as possible.