06-26-2014 10:33 PM
Occasionally our Oracle database is down during work hours. This causes our pre-assigned Oracle libraries to (eventually) time out. It takes a fairly long time to timeout, and this causes issues with one of our web applications, as the lengthy startup for the workspace server causes the web application to abort. It also causes EG to take a *long* time to start the workspace server.
Is there a setting, either on the Oracle libname statement, or in the Oracle client (even better) that will cause this scenario to "fail fast"?
And if there are reasons why this would be a bad idea, please let me know. But, when Oracle is up, the connection is quite snappy, so I would think I could shorten the timeout period a lot without causing problems.
06-26-2014 11:05 PM
Do you use the DEFER = YES option on your Oracle pre-assigned libraries? We use it on all of our external database pre-assigned libraries as it helps speed up connections to workspace servers and helps reduce timeout problems because database connections are only established when they are actually used, rather than being active throughout the workspace server sessions.