Re: oracle OCI.dll NLS error on connect
- From: listmail@xxxxxxxxxxxx (Listmail)
- Date: Fri, 23 Dec 2005 12:48:52 -0500
I imagine that he wants to keep things 1:1. I know at first I wanted to upgrade things to the same level, but I've been running a 9iR2 repository/admin database against a few 8i databases for a couple years now. Additionally I run compiled perl scripts (activeperl 5.8.7 build 813 and oracle-dbd 1.16) on solaris boxes which house Oracle 8i databases/oracle_homes and fortunately this error does not occur. This allows me to wait until '06 when we start migrating our remnants to 9.2.0.7 (give or take a dot release).
Mitchell, Louise M wrote:
That's enough to convince me as well. I only recently installed the client and put the 8.1.7 at the recommendation of our Oracle DBA, but don't know why he recommended that.
Thanks for the response.
L
-----Original Message-----
From: listmail [mailto:listmail@xxxxxxxxxxxx] Sent: Thursday, December 22, 2005 8:30 AM
To: dbi-users@xxxxxxxx
Subject: Re: oracle OCI.dll NLS error on connect
Sorry, but I do not remember if I had worked around this by setting NLS environment variable(s) in Windows on each client or not. The situation was painful enough to convince me to upgrade all my (Perl) client machines to the 9iR2 client (or technically, at least a bare minimum install to get the newer Net8 install). I haven't had any issues accessing my 8i databases using DBD-Oracle 1.16 and the 9iR2 client.
Mitchell, Louise M wrote:
Did anyone figure this one out? I am having the same issue, but don't see a response to this initial posting.
I have oracle 8.1.7 client installed and the following:
Windows Server 2003 ActivePerl 5.8.7 build 813 DBI 1.49 DBD-Oracle 1.16
BTW, is anyone else having issues with PPM? Seems like the last few releases have had bugs.... it's getting frustrating?
L
***************
oracle OCI.dll NLS error on connect
listmail
Mon, 07 Nov 2005 09:13:55 -0800
I get the following error when connecting to an 8i oracle database from
workstations with the Oracle 8i client installed or if their Oracle Home selector is set to the 8i home. If the workstations only have the
Oracle 9i client installed or if the Oracle Home selector is set to the 9i home, then this error does not occur. From the looks of the error my guess is that the (unpatched?) 8i OCI.dll doesn't contain a OCINlsEnvironmentVariableGet function/subroutine.
Error dialog:
The procedure entry point OCINlsEnvironmentVariableGet could not be located in the dynamic link library OCI.dll
For those of you that may have seen this, is there a switch I can use within the DBI connect call or perhaps an environment variable that I can set within the perl code to work around this?
Windows XP and NT
ActivePerl 5.8.7 build 813 (modules installed using ppm) DBI 1.48 DBD-Oracle 1.16
.
- Prev by Date: Re: auto repair script for mysql
- Next by Date: $DBI::errstr == (no error string)
- Previous by thread: Re: oracle OCI.dll NLS error on connect
- Next by thread: Silencing DBI "(err=0, errstr=undef, state=undef)" errors
- Index(es):
Relevant Pages
|
