At 11:17 AM 4/19/2001 -0400, Jim Lambert wrote:
>Are you using Oracle in Shared Server mode (MTS)?
>
>We had this problem with Oracle 8.1.5 and 8.1.6 in MTS mode. When we
>switched to Dedicated Server mode, it went away. BTW, this is a
>'know' Oracle bug and it's suppose to be fixed in 8.1.7, but we
>haven't tested it yet.
Yes and no on the MTS question. One of the DBA-types here set up the server
to use MTS a few days ago, but shut it off that same day. As far as he can
tell, it's definitely not on. I set SERVER = DEDICATED in the tnsnames.ora
on the client, but the problem is still there.
The server that I'm trying to access is 8.1.7, so if it's purely an MTS
problem, then it doesn't look like the new version solves it. Now for the
good/interesting part. The table is also on a remote server running 8.0.5
and that has never been set to use MTS. When I tell the script to use that
server, the problem goes away.
So, the way I see it, there are three major possibilities: a) It's an MTS
problem and the local server still has traces of it or b) it's a timing
issue with the server being on the same subnet (100M link vs. T-1) or c)
it's something else in 8.1.7 that isn't in 8.0.5.
If you or anyone else has any suggestions, I would be more than happy to
hear them, as I'd much prefer to use the local server.
