Are there any known issues regarding Oracle on Windows XP? We have a system with a Win2K server on the back end and an XP client. Whether using Oracle 126.96.36.199 or 188.8.131.52 on these machines, we are running into ORA-01000 errors.
Background: Our application is written in VB, with OLEDB/ADO as middleware talking to the Oracle database. When logging on, the application opens a number of cursors to gather user setup information. Regardless of the server O/S, whenever we use an XP client cursors are not being closed by Oracle until the logon process is complete, despite the fact that our application is releasing the cursor each time. This is leading to excessive numbers of cursors being opened -- up to 1800 in one case.
We do not experience this problem when using a non-XP client against the same server, and our customers have also reproduced it using an XP client against an HP-UX server and cannot reproduce it using an NT client against the same HP-UX server.
We have set the following initialization parameters on the server...
_CLOSE_CACHED_OPEN_CURSORS=TRUE SESSION_CACHED_CURSORS=50 OPEN_CURSORS=1800 CURSOR_SHARING=FORCE...without effect. Any suggestions?
I would look to an error with the XP OLEDB/ADO drivers. Are you using the most current? If so, have any errors been reported to the provider of that middleware? Maybe an earlier release is required. The only Oracle bug I could find is 4263105, but it deals with the 10g release but has been shown to affect as far back as 184.108.40.206. It states that the close in the driver may not close cursors properly depending on scope. Maybe Don can find more on this.
Don Burleson adds:
"Are there any known issues regarding Oracle on Windows XP?" Yes, there are dozens of them listed on Metalink.
This was first published in May 2005