Message-Id: <10737.126280@fatcity.com> From: "Michael Ray" Date: Wed, 10 Jan 2001 08:05:30 -0800 Subject: Could only connect via SVRMGR --=_287343AC.50315C33 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Content-Disposition: inline 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 217-826-3011 x2438 --=_287343AC.50315C33 Content-Type: text/plain Content-Disposition: attachment; filename="TEXT.htm"

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
217-826-3011 x2438