RE: Could only connect via SVRMGR

We ran into similar problems with 7.3.4 on Solaris when the /u01 directory would fill up. This of course is where the Oracle binaries. We also had similar problems when we had an application that was generating hundreds of processes. We would kill "a bunch" of the processes only to have that many and more generated. We finally killed the application and that took care of the problem. Another time we had this type of problem we ended up flushing the shared pool and that enabled us to start logging into SQLPlus and/or the application again.

Hope this helps,
Nancy

-----Original Message-----
From: root_at_fatcity.com [mailto:root_at_fatcity.com]On Behalf Of Michael Ray Sent: Wednesday, January 10, 2001 11:15 AM To: Multiple recipients of list ORACLE-L Subject: Could only connect via SVRMGR

Had fun this morning where our most critical plant database would not allow new connections, but those already in were running just fine. I had a similar issue a couple months ago where moving the tnsnames file into the BIN directory solved the problem (I still don't know why!), but that wasn't the case this time.

I could tnsping the db but SQLPlus would hang from my desk. From the server, I could connect internal via svrmgr, but SQLPlus would still just hang using sys. I ended up crossing my fingers and bouncing the db, which worked thank goodness.

NT4 running 7.3.4 (I know, I know).

Any ideas?

Michael Ray
Oracle DBA
TRW, Marshall, IL Received on Wed Jan 10 2001 - 11:30:26 CST