Sandra,
I might be missing some history here, but that error message is only
telling you that the application could not create a session to the
database.
This could be related to an error on the db stack, the network or the
application (connection pool) itself.
If there are no errors in the alert file (and listener logs), it is more
likely that the problem is on one of the other layers.
Kind regards,
--
Freek D'Hooge
Exitas NV
Senior Oracle DBA
email: freek.dhooge@xxxxxxxxx
tel +32(03) 443 12 38
http://www.exitas.be ;
On di, 2016-04-05 at 11:16 -0600, Sandra Becker wrote:
EE 11.2.0.4
ASM storage
Linux
Is it possible the following errors are caused by the ASM storage
being 100% used? I did not see any unable to extend errors in the
alert log. I also verified that the NFS mounts for archivelogs and
database/listener logs had plenty of free space.
Error: com.company.cfe.CfeException: Database connection
unavailable or possibly JNDI lookup failed for name
[java:CMP_RO_OracleDS].Unable to get managed connection for
CMP_RO_OracleDS; - nested throwable:
(javax.resource.ResourceException: Unable to get managed
connection
for CMP_RO_OracleDS
The QA team has been having connection issues off and on for about a
month. We're not sure when the ASM storage filled up since there are
no errors in any of the alert logs for the three databases that use
it. Last week our sys admin determined that one of the app servers
was tearing down the connections. Could the error be related to that
problem? No one really seems to understand this error, what caused
it, how to fix it. My colleague has requested additional ASM storage
and is confident that will resolve the connection issue.
A recommendation on a website or book that would help me understand
what it happening would be great, if such exists. Thank you.
Sandy B.
