Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Sybase System 11; Failed to map a local name to an object id!

98 views
Skip to first unread message

Christian Volmering

unread,
Dec 20, 2002, 6:59:35 AM12/20/02
to
Hello everyone,
I've got a problem with the PC Client for Linux 11.9.2.
I'm trying to connect to a Sybase ASE 11.0.3.3 over a ODBC driver from a
windoze box. But after installation and configuration I only get the
message: 'cs_locale: cslib user api layer: common libary error: Failed to
map a local name to an object id!' from the ODBC SQL Server driver. This
error does'nt write anything to the sybini.err file. Here is what I've
done:
I've first installed the Open Client Runtime and the Option for
Licensed Products. With the OC OS Config Utility I processed the
Environment configuration where I setup the language to default wich
should be us_english, iso_1 according to the locales.dat in the locales
dir in the $(SYBASE) path. After that I used dsedit for the interface
setup. The ping worked fine and now I was able to connect to the server
with the isql tool.
The last thing was to add a DSN for the ODBC conection. But I was'nt able
to conenct over that because of the problem descriped previosly in this
message.
Oure Server is running on Linux Slackware, Kernel 2.4.18 an the master
server is set to the same locals as i configured on my windoze box wich
is runs on W2k SP3. The connection is made over the Winsock lib (TCP).
I was not able to fix this problem. Does anyone have an Idea how to solve
this?
Thanks in advance,
Christian Volmering [KOCH Software Consulting GmbH]

odbcpse

unread,
Dec 23, 2002, 11:28:50 AM12/23/02
to Christian Volmering
Hi Christian,

I am not 100% I understand this - is the ODBC driver installed on a
WindowsPC?
Windows 2000 SP3? What is the version of the Open Client and ODBC
driver being used?
When you experience the odbc trouble you should turn on the ODBC trace.
If this is on the
Windows platform than you use the ODBC adminsitrator to turn on the
trace. It
might provide a clue as to what is causing the failure.

Because the Client Library error occors on cs_locale, I would guess that
there
is some charset problem on the client - if the ASE is setup as iso_1,
us_english,
then the client side should eb able to support this.

pv

0 new messages