A colleague of mine has just bought a classic laptop with Microsoft Windows Vista Home Premium SP1 (eh oh well ...) and, since its activities around each wheel to create web apps that interface with Oracle, has tried to install on this laptop, Oracle Instant Client 10.2.0.1. He followed the standard procedure, opting for an installation from an administrator, set up the tnsnames.ora entries with the correct, yet, launching a prompt sqlplus, or Toad, etc., shows the following error:
On the OTN forum we recommend:
1) correctly set the environment variables ORACLE_HOME, TNS_ADMIN, LD_LIBRARY_PATH and PATH
2) check the security settings of Windows as lacking permission "create global objects"
Now, the number 1 solution did not work and, apparently, Windows Vista Home Premium SP1 is not possible, or at least I have not found, access to policies a secure facility, so I could not verify the absence of the privilege "create global objects" for my user.
San Google, as usual, came to help me with this article by Christian Shay in which the author points out that Windows Vista is available for a package that allows you to install Oracle Client 10.2.0.3 directly, ie without need, as before, to install the client version 10.2.0.1 then patch it to 10.2.0.3 that, in fact, solves the problem SP2-1503. Retained
my time link to download the Oracle client version 10.2.0.3 for Windows Vista / Windows 2008!
install this package everything went smoothly, until I tried a connection to my db test with TOAD and end up with the following error (Bella Vista, yes yes):
Another Google search and landing on asktoad.com site and more specifically in this FAQ , here we read that the problem is caused by UAC: User Access Control, which is the system control user access to Windows Vista, when enabled (and it is by default) does not ensure that a user write access to Program Files directory . Also from the FAQ says that when Toad 9.5 is installed it creates a file called lexlib.new that, when you launch the GUI Toad should be renamed lexlib.lxl This has not been allowed by its UAC (unless Toad running as a user Administrator).
There are two solutions: *
disable UAC, for example as shown in this guide
Toad * run as administrator user
I chose the first option, which is very easy to implement!
0 comments:
Post a Comment