Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
![]() |
![]() |
Home -> Community -> Mailing Lists -> Oracle-L -> RE: SID & SERIAL#
Jared,
I have seen it on 9i when I used TOAD ... in TOAD the locks tab is = extremely slow ... so slow that <insert your favorite joke here> ... so = I kill the server process and reconnect within TOAD, I come back with = same sid, but different serial# ...
Raj
-------------------------------------------------------------------------=
-----Original Message-----
From: oracle-l-bounce_at_freelists.org
[mailto:oracle-l-bounce_at_freelists.org]On Behalf Of Jared Still
Sent: Sunday, February 15, 2004 5:24 PM
To: Oracle-L Freelists
Subject: Re: SID & SERIAL#
Yeah, I've seen this a number of times.
At times when table is locked, and the session is disconnected ( PC crashes ), SMON goes about its cleanup duties, but something isn't quite right.
The session will die and come right back with a new serial#.
You can't kill it, no matter what you do.
You can't get rid of the lock either.
There is only one recourse: bounce the database.
I have seen this happen on Solaris, DG/UX and Windows, versions 7.3, 8.0 and 8.1. Not yet on 9i, maybe it's been fixed.
It hasn't happened to me in about 2 years. It would be interesting to see it again and try to capture a trace of what is going on.
Jared
![]() |
![]() |