two task communication error during login of a busy system
Guess2Apr 2 2009 — edited Apr 2 2009We have a busy database with alot of logins/logouts. We are getting alot of performance problems with logging in. So we turned on listener and server side sqlnet tracing. This makes the log in times worse. with tracing on it now takes 90 seconds to login.
so from the unix prompt we tried logging into oracle without using @database_name to avoid the listener. We get a two task communication error when we do this.
I googled this error and there are a laundry list of things that it could be. Any ideas?