RE: SQL*Net Client 10.2.0.1 issue
Date: Thu, 15 Jan 2009 16:38:10 -0800
Thank you Orysia,
This solved my problem.
- Eric Hutchinson
From: Husak, Orysia - PHX [mailto:Orysia.Husak_at_chw.edu] Sent: Thursday, January 15, 2009 3:44 PM To: EricHutchinson_at_comcast.net; oracle-l_at_freelists.org Subject: RE: SQL*Net Client 10.2.0.1 issue
The issue may be related to a Windows Security configuration.
The problem is caused by a security policy called "Create Global Objects".
The user account that is used to run the program does not have the "Create
global objects" user right. This security policy was introduced with Windows
2000 SP4, and determines if applications started during a Terminal Services
session can create or
access globally accessible memory.
By default, members of the Administrators group, the System account, and Services that are started by the Service Control Manager are assigned the "Create global objects" user right.
To implement the solution, please execute the following steps:
- Click Start, point to Programs, point to Administrative Tools, and then click Local Security Policy.
- Expand Local Policies, and then click User Rights Assignment.
- In the right pane, double-click Create global objects.
- In the Local Security Policy Setting dialog box, click Add.
- In the Select Users or Group dialog box, click the user account that you want to add, click Add, and then click OK.
- Click OK.
Sr. Database Management Specialist
Catholic Healthcare West IT
From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org]
On Behalf Of Eric Hutchinson
Sent: Thursday, January 15, 2009 1:25 PM To: oracle-l_at_freelists.org
Subject: SQL*Net Client 10.2.0.1 issue
I have a weird problem I hope you can help me with.
I have a Windows Server 2003 Standard Edition (on VMware) with a web app that connects to an Oracle 10.2.0.3 DB on Red Hat 5 (also on VMware). I installed the Administrator package of the Oracle client for windows (32-bit) as the local Administrator.
Administrator can connect to the remote DB every time.
A domain user, using remote desktop to the server, cannot connect to the database. No SQL*Net trace files are generated. It does not seem to get that far.
Remotely connecting to the web app reaches the database, after which the domain user (RDP to the server) can connect with no problem, until the next server reboot.
Has anyone seen anything like this? Have any idea what is going on?
As a workaround we can connect via the web app after each server reboot, but I'd like a proper solution.
Thanks in advance,
- Eric Hutchinson