David Paul wrote:Don't confuse yourself... It's just saying to convert data into your local DB type...
Can you give me a full explaination about the DL http://vibhorkumar.wordpress.com/2011/02/27/fix-of-ora-29275-partial-multibyte-character/ you mentioned?
I don't understand the query in it well.
Edited by: ranit B on Dec 22, 2012 5:46 PM
1] /* check this in both your LOCAL and REMOTE databases */ select dump('a',1010) from dual; I got -- Typ=96 Len=1 CharacterSet=AL32UTF8: 97 So, my charset encoding is AL32UTF8. Similarly, find yours for both Local & Remote DBs. 2] /* Then do */ CONVERT(transaction_reason,'<local_charset>','<remote_charset>')
SELECT CONVERT('Ä Ê Í Õ Ø A B C D E ', 'US7ASCII', 'WE8ISO8859P1') FROM DUAL;
And, could you please check and respond a little fast. We are stuck here since a long time. I don't like dragging issues. ;)
CREATE TABLE TEST_TMP AS SELECT CONVERT(TRANSACTION_REASON,'<REMOTE_CharacterSet>','<LOCAL_CharacterSet>') FROM APPS.MTL_TRANSACTION@OAPPS.COM --it is using db link. WHERE LAST_UPDATE_DATE>=TO_DATE('18-12-2012 22:01:58', 'dd-mm-yyyy hh24:mi:ss');
David Paul wrote:This seems difficult coz this error is assoicated to a DDL like creating a table, which can only be realized in run-time.
It is helpful. But I have one doubt, is there a method to catch the issue before it raises?
BEGIN execute immediate 'CREATE TABLE TEST_TMP AS SELECT CONVERT(TRANSACTION_REASON,''<REMOTE_CharacterSet>'',''<LOCAL_CharacterSet>'') FROM APPS.MTL_TRANSACTION@OAPPS.COM --it is using db link. WHERE LAST_UPDATE_DATE>=TO_DATE(''18-12-2012 22:01:58'', ''dd-mm-yyyy hh24:mi:ss'')'; EXCEPTION when others then DBMS_OUTPUT.PUT_LINE(SQLERRM); END;