We get this message quite frequently when we use our test oracle instance which is much less powerful and less used than the production instance. On production this occurs rarely.

What I am guessing is happening is that the login process is not actually failling but taking too long, because when you try next time it works fine.

This would suggest that there is a threshhold time for login beyond which wf assumes that the login attempt is invalid, NOT because the password is invalid, but because the instance is not present or not reachable.

Does anyone know if this is a settable parameter we can set higher for our test instance where login takes longer?

Thanks

John

Tried to do this in Oracle SQLNET.ORA set to 300s = 5 mins to timeout. Works in 9.2+

#Timeout Parameters
SQLNET.INBOUND_CONNECT_TIMEOUT = 300
SQLNET.SEND_TIMEOUT = 300
SQLNET.RECV_TIMEOUT = 300

http://www.psoug.org/reference/net_services.html

This message has been edited. Last edited by: hammo1j,