Re: Not a typical ORA-03113 error

Update:

I did search through the Metalink site and found some useful information. Number 1 thing I did was turn on trace logging. I then had the client login, search (generate the error) and exit out. I then compared this log to a log I generated which DID NOT get the error. Anyway, what I found was an extremely high number of "transport read" errors. Although both logs had these errors the rate was very high in the client's log (176 vs 307).

To make a long story short I found that the client could successfully login and do a search if she did it in the early morning hours (prior to 8am) or after 4:30pm (gov't office...got pretty dead after 4:30). Anyway, we went ahead and checked out our router dsu/csu just to make sure it was not a problem there.

So, although the problem has not been solved we are fairly certain that the clients network is (at busy times) not able to reliably connect...even though in my original note I stated that the user did a test plugging in their workstation and bypassing their local network and got the same error...this was a one time test with a long network cable and I don't think it is or should be considered a valid test.

That's it for now.

JB

jbyy4u_at_yahoo.com (JB) wrote in message news:<aaed8e6c.0204171430.63414054_at_posting.google.com>...
> We have approx. 60 clients (60 sites) connected via WAN to our
> network. At each site we have one Windows 2000 Pro running a GUI
> front-end (Using SQL*net) and all 60 clients are working fine when
> doing searches. But, at these 60 locations there have been additional
> workstations connected running either Windows 98, NT or 2000. At only
> 1 of these locations (that had 2 additional 98 PC's connected and
> running the app.) both connected PC's suddenly stopped working and
> they get the ORA-03113 error. (They get logged in fine, the error only
> occurs when they do a search and they don't lose connectivity to the
> db - i.e. they get a nice friendly msg saying no results found and
> they can continue using the GUI).
>
> We had them eliminate any problems with their network by having them
> take one of the troubled workstations and hooking it directly to our
> router/hub (remember the 2k Pro at this site is working fine). This
> did not help. Verified with another site running with Windows 98 and
> the app. works fine for them.
>
> User swears there have been no changes on their PC's. We had the user
> re-install the SQL*net and GUI app. but no luck.
>
> Looked through trace files and could find no reference to this error.
>
> Any ideas or suggestions would be greatly appreciated.
>
> TIA.
>
> JB
Received on Wed May 01 2002 - 17:36:14 CDT