Operating System - HP-UX
1751847 Members
5195 Online
108782 Solutions
New Discussion

Re: DBLink Error between V8.1.7 and 9i

 
Chen Yingjie
Frequent Advisor

DBLink Error between V8.1.7 and 9i

We have got a DB Link Error(ORA-24365) from our testing environment.

Our testing environment is below.

System 1:

OS: AIX 5L 5.2 DB: Oracle9i
Character Set:
JA16SJISTILDE character set and AL16UTF16 NCHAR character set

System 2:
OS: HP-UX 11.00 DB: Oracle8i(8.1.7)
Character Set:
JA16SJIS character set or US7ASCII character set

We created DB Link from System 2 to System 1 and executed followings.

Error Log:

ih001 43: sqlplus xxxx/xxxx
SQL*Plus: Release 8.1.7.0.0 - Production on Tue Jul 25 10:36:37 2006

(c) Copyright 2000 Oracle Corporation. All rights reserved.

Connected to:
Oracle8i Enterprise Edition Release 8.1.7.4.0 - Production
With the Partitioning option
JServer Release 8.1.7.4.0 - Production

SQL> select * from tab@USER1.ORA9;
select * from tab@USER1.ORA9
*
ERROR at line 1:
ORA-02068: following servere error from USER1.ORA9
ORA-24365: error in character conversion

Can someone advise me how to fix this problem?

Thanks in advance.

Chen
1 REPLY 1
Indira Aramandla
Honored Contributor

Re: DBLink Error between V8.1.7 and 9i

Hi Chen,

The default UTF8 characterset for 9i or 10g is AL32UTF8, however this characterset is NOT recognised by any pre-9i clients/server systems. This causes several problems. Oracle recommends to use UTF8 instead of AL32UTF8 as database characterset if one has 8i (or older) servers and clients connecting to the 9i or 10g system until you can upgrade the older versions.

Creating database link from 8i database to 9i (AL32UTF8 characterset) results in ORA-24365.

After creating a database link from 8i database to 9i, selecting data across
the database link yields the following errors:ORA-24365:error in character conversion

This is due to BUG 2360739 according to oracle Metalink, results in error when the 9i database characterset is AL32UTF8, which is the default at creation time. There is a patch available for this Bug on 8.1.7.4 patchset for most of the affected platforms.

The workaround is to use the UTF8 characterset on the 9i database.


Indira A
Never give up, Keep Trying