1833868 Members
1607 Online
110063 Solutions
New Discussion

pro-c on IA64

 
Wanda Canade'
Advisor

pro-c on IA64

running a pro-c application on a client IA64 i received ORA-01458 error (invalid length inside variable character string). This problem don't occurre on different platform (hp-ux 9000/800).
I think the problem is due to a different value between NLS_LANG and DB charset. how to set this varaible on my clent?
thanks

10 REPLIES 10
Alex Lavrov.
Honored Contributor

Re: pro-c on IA64

Set it as environment variable:

export NLS_LANG=blablabla
I don't give a damn for a man that can only spell a word one way. (M. Twain)
Wanda Canade'
Advisor

Re: pro-c on IA64

I tried to set this value to the same of DB charset. But it doesn't work. In attachment all settings of Db(linux AS3.0 with oracle 9.2.0.5 server) and of client (IA64 with hp-ux 11.23).
have I to set a particolar NLS_LANG value for itanium?
Alex Lavrov.
Honored Contributor

Re: pro-c on IA64

Can you paste here lines from code that generate the error?
I don't give a damn for a man that can only spell a word one way. (M. Twain)
Peter Godron
Honored Contributor

Re: pro-c on IA64

Wanda Canade'
Advisor

Re: pro-c on IA64

I don't know the programm code but I think the problem is on a pl/sql procedure.
Alex Lavrov.
Honored Contributor

Re: pro-c on IA64

Well, some code will be very useful
I don't give a damn for a man that can only spell a word one way. (M. Twain)
Wanda Canade'
Advisor

Re: pro-c on IA64

I looked at some metalink notes. According with the note 3473428.8 I'd like use an env variable, this because there are a lot of procedures that have the same problem.
Infact I tied to trasport c and pro-c application of my company from hp-ux 9000/800 platform to IA64 platform.
Peter Godron
Honored Contributor

Re: pro-c on IA64

Wanda,
please let us know if your test and workaround is OK.

For non-metalink users:
Bug 3473428:

Product (Component) JDBC (Oci)
Range of versions believed to be affected Versions < 10.1.0.2

JDBC OCI defineColumnType () behaves incorrectly when NLS_LANG
differs from the DB charset (and is not US7ASCII).

eg:
create table tkpjif01 (x char(40));
insert into tkpjif01 values ('a234567890b234567890c234567890')
stmt.defineColumnType (1, Types.CHAR, 2);
select x from tkpjif01
print out the result set
The output is supposed to be "a2" but shows as "a23456"

Workaround:
Use NLS_LANG=.US7ASCII
OR
Use NLS_LANG the same as the database character set

Regards
Wanda Canade'
Advisor

Re: pro-c on IA64

I tried the value in the note but it doesn't work. I don't know if US7ASCI is ok for IA64. But the DB charset is US7ASCI.
Wanda Canade'
Advisor

Re: pro-c on IA64

i have to change application's code.
Thank you for collaboration
Bye