wweicker's questions

I have an Oracle instance which has user1, user2 and user3 accounts. Yesterday I was able to log in to all three accounts. Today, I can get in to user1 and user3, but user2 is completely 'frozen' in some way that I don't understand.

If I try to log in to user2 with sqlplus it just spins forever. It does not connect, does not time out, nothing happens until I press CTRL+C to kill the process. Connecting as user1 or user3 is instantaneous.

I thought I would try locking user2 out and then try unlocking it. The query to lock the user ran for 25 minutes before I gave up! Locking user1 then unlocking user1 ran instantly.

Using TOAD and connecting as a DBA, I used Session Browser to investigate. I found 11 connections to the database as user2. Five of these appear to be my failed attempts at connecting using sqlplus. None of these connections are showing any open cursors, a current statement or any locks. On the waits tab 10 of the connections show a "row cache lock" with:

• seconds in wait between 3,000 and 60,000
• P1 = 7
• P1 Text = "cache id"
• P2 = 0
• P2 Text = "mode"
• P3 = 3
• P3 Text = "request"

One of the connections stands out as it appears to be very old. It shows a "SQL*Net message from client" with:

• seconds in wait > 600,000
• P1 = 1413697536
• P1 Text = "driver id"
• P2 = 1
• P2 Text = "#bytes"
• P3 = 0
• P3 Text = ""

I am not able to kill any of these 11 sessions. After I issue the kill command (using TOAD, with or without immediate option) it runs for 45-60 seconds then says "Session is marked for kill." but the session never goes away.

Any ideas what this means or how I can kill these sessions and restore access to the user2 account?

Update: There were some interesting lines in the alert log:

Tue Dec 29 09:37:45 2009
WARNING: inbound connection timed out (ORA-3136)
Tue Dec 29 10:25:45 2009
>>> WAITED TOO LONG FOR A ROW CACHE ENQUEUE LOCK! pid=17
System State dumped to trace file [snip]\udump\ora_1988.trc
Tue Dec 29 10:54:17 2009
WARNING: inbound connection timed out (ORA-3136)
Tue Dec 29 10:55:47 2009
WARNING: inbound connection timed out (ORA-3136)
Tue Dec 29 10:56:47 2009
WARNING: inbound connection timed out (ORA-3136)
Tue Dec 29 10:57:47 2009
WARNING: inbound connection timed out (ORA-3136)
Tue Dec 29 11:12:17 2009
WARNING: inbound connection timed out (ORA-3136)
Tue Dec 29 12:06:17 2009
WARNING: inbound connection timed out (ORA-3136)
Tue Dec 29 12:26:47 2009
WARNING: inbound connection timed out (ORA-3136)
Tue Dec 29 12:27:47 2009
WARNING: inbound connection timed out (ORA-3136)
Tue Dec 29 13:46:17 2009
WARNING: inbound connection timed out (ORA-3136)
Wed Dec 30 10:02:16 2009 >>> WAITED TOO LONG FOR A ROW CACHE ENQUEUE LOCK! pid=37
System State dumped to trace file [snip]\udump\ora_2860.trc
Wed Dec 30 11:55:59 2009
orakill: attempting to kill tid=436
Wed Dec 30 11:56:04 2009
orakill: ssthreadkill(tid=436) unable to get the thread list mutex: err=0

Resolution: It seems like this is a 10.2.0.3 bug and I need to restart the instance, which I do not have permission to do, so I will have wait a few days.

I have an ASP.NET application running on a client server (W2k3, IIS6, .NET 2.0). FWIW, this is a Test instance, it hasn't been moved into Production yet. So it is not running under SSL, load balancing, etc.

When I access one of the pages on their server from our office, the page gets hit once. Inspecting the IIS logs (c:WINDOWS\system32\LogFiles\W3SVC1) show a GET for that page, then I push a button on the page and the log file shows a POST. This seems to be working fine so far.

Now when I remote into the client's network and access the page from one of their local machines, the log file shows a GET, then I push the button on the page and the log shows two POSTs at the same second. The first one shows status (sc-status, sc-substatus, sc-win32-status) 200 0 64, the second shows 200 0 0.

In the log file, both POSTs are identical. Basically the log looks like this (except I masked some of the data):

#Fields: date time s-ip cs-method cs-uri-stem cs-uri-query s-port cs-username c-ip cs(User-Agent) sc-status sc-substatus sc-win32-status 
2009-08-11 20:19:32 x.x.x.x GET /File.aspx - 80 - y.y.y.y Mozilla/4.0+(compatible;+MSIE+8.0;+Windows+NT+6.0;+WOW64;+Trident/4.0;+SLCC1;+.NET+CLR+2.0.50727;+.NET+CLR+3.5.21022;+.NET+CLR+3.5.30729;+.NET+CLR+3.0.30618;+MDDR;+OfficeLiveConnector.1.4;+OfficeLivePatch.0.0) 200 0 0
2009-08-11 20:19:45 x.x.x.x POST /File.aspx - 80 - y.y.y.y Mozilla/4.0+(compatible;+MSIE+8.0;+Windows+NT+6.0;+WOW64;+Trident/4.0;+SLCC1;+.NET+CLR+2.0.50727;+.NET+CLR+3.5.21022;+.NET+CLR+3.5.30729;+.NET+CLR+3.0.30618;+MDDR;+OfficeLiveConnector.1.4;+OfficeLivePatch.0.0) 200 0 64
2009-08-11 20:19:45 x.x.x.x POST /File.aspx - 80 - y.y.y.y Mozilla/4.0+(compatible;+MSIE+8.0;+Windows+NT+6.0;+WOW64;+Trident/4.0;+SLCC1;+.NET+CLR+2.0.50727;+.NET+CLR+3.5.21022;+.NET+CLR+3.5.30729;+.NET+CLR+3.0.30618;+MDDR;+OfficeLiveConnector.1.4;+OfficeLivePatch.0.0) 200 0 0

The problem is, the page is getting hit twice. The database performs an operation for the first request, then the second request detects that a duplicate operation is being performed and throws an error message. The users think their operation failed, but it actually succeeded.

The error description of sc-win32-status 64 is: "The specified network name is no longer available." This leads me to believe, given that both POST requests show an HTTP status of 200, that the server is successful in serving the request, but the client is never notified and resubmits the request.

• How can I troubleshoot this?

• Any ideas what could be causing this behavior on their internal network only?

• I should mention, this is happening at two separate client sites, but does not happen at six of our other client sites, or in our office, or connecting to any of our eight clients over the web.

• What could be making this reproducible 100% of the time on their local network but 0% of the time anywhere else?

Update: I found a very small number of the duplicated POST requests had sc-win32-status of 995 instead of 64 as originally reported. The error description of sc-win32-status=995 is: "The I/O operation has been aborted because of either a thread exit or an application request." This doesn't make any sense (considering I have full access to the code). I still don't understand how or why this issue is occurring, but the new error code leads me to believe it may not be a network issue after all and I am now investigating the possibility of a random code bug.

We just acquired 7 new Dell Optiplex machines with Vista 64 bit installed. We installed all of our tools and applications on one of the machines and then used Norton Ghost to deploy to the other 6 machines. We have found that the ghosted machines do not recognize any USB keyboards at all when booted into Windows.

The USB mice work fine. We tried all of the 6 different USB ports with both keyboards and mice; the mice work on all 6 ports but the keyboards do not work on any of them.

All these keyboards work fine on other computers. They work in the BIOS and when booting off the system restore disc to run the recovery tools / repair / restore / reinstall options, just not at the main Windows login prompt or beyond. The same behavior occurs in safe mode as well.

Edit:

We initially thought that this was limited to a keyboard/USB issue, but it seems to be deeper rooted than that. If we use the on screen keyboard to get past the login prompt we are just stuck at a blank screen. Just the default blueish background wallpaper with no shell, no ability to used the on screen keyboard to bring up task manager or anything like that.

Any ideas what the problem might be or how to proceed?

I have an ASP file that is trying to make a webservice request to an ASP.NET webservice running on the same server under the same virtual directory. In IIS the virtual directory is set up to disable anonymous access and "integrated windows authentication" is turned on.

So the problem is, when the user's machine requests to run the ASP page or even manually run the WebService.asmx .NET file, it works because the user's credentials are passed along, however when the ASP file tries to invoke the webservice we get a 401.2 - Unauthorized: Access is denied due to server configuration.

For example:

• "DIRECTORY\user1" from a browser on the user machine requests Service.asmx which works fine.
• "DIRECTORY\user1" from a browser on the user machine requests File1.asp which works fine.
• _________ from within File1.asp on the server requests Service.asmx which returns 401.2

So I assumed I needed to set NTFS permissions on WebService.asmx to allow the ASP account Read & Execute permissions, but I don't know what account it runs under, and upon further thought after reading some of the reponses, it seems like we aren't getting to the NTFS level, IIS is completely rejecting the request because anonymous access is turned off.

Does this indicate that we need to get the ASP process running under a domain account?