Shutdown_timeout not an issue, one-value set to a time properly set, two- no
transactions are occurring...like I said a test database.
Actually tried connecting w/o using SID. I wasn't sure if it was a listener
problem or not.

I initially thought that some of the services in windoze wasn't up and
running, so I decided to wait awhile(30 minutes) still took too long. Also
tried reducing some of the services that were starting...that didn't help
much.

I wasn't having this problem until win SP 4 was installed. However, I had
another separate machine, the version of oracle was different was using
pathset 1 (9.2.0.1), and that has win SP4 on it, and no issues. The db that
causes a freeze/hang is 9.2.0.3. I hoping to see if anyone possibly could
have encountered this w/ their db using this version w/ win SP4. I guess
I'll have to try and test it out on my other machine *sigh*.
Thanks,

-----Original Message-----
From: Seefelt, Beth [mailto:Beth.[Email Address Removed]
Sent: Thursday, August 28, 2003 7:16 PM
To: Oracle DBA Help; LazyDBA.com Discussion
Subject: RE: listener problems?


I would try first to verify that it's a listener problem. Try
connecting directly by setting oracle_sid and connection without @sid.
Does that hang also?

This is a real shot in the dark, but check your
ORA_<SID>_SHUTDOWN_TIMEOUT reg param. Is it set to a high enough value.
The default is only 30 seconds which may not give the database time to
shutdown cleanly which means recovery will run when the system reboots
if there were active transactions when you shutdown.


-----Original Message-----
From: Oracle DBA Help [mailto:[Email Address Removed]
Sent: Thursday, August 28, 2003 5:33 PM
To: LazyDBA.com Discussion
Subject: listener problems?


Hi all,
I am running a 9.2.0.3 on Win2k Advanced server. Everytime I reboot the
server, I have a hard time connecting to the database. What happens is
it always seems to hang when trying to connect. The database is open
andrunning, based on the alert.log, and the listener seems to be ok,
when I do a tnsping is normal, and checking status seems good.
I resolve the issue by restarting all the oracle services(Database, MTS
recovery, Agent, Listener). Now...this not something I want to do,
every time machine is rebooted (either by user or "blackout").
Now there's nothing unusual in the alert log, and the listener log
didn't show any problems. Any one encounter this probleme.

It's win2k Advanced server w/ service pack 4.

FYI it's a test db, so I'm not too overly concerned about it, b/c it's
not happening to our production database. However our production db is
on service pack 2. So I was curious to see if anyone has encountered
this, and if so, is it the service pack, or something else?
Thanks,
X
Oracle LazyDBA home page