‎2007 Jul 06 8:35 AM
‎2007 Jul 06 8:41 AM
Hi
see the links
The Link will be helpful to you.
Very good document:
http://www.doag.org/pub/docs/sig/sap/2004-03/Buhlinger_Maxi_Version.pdf
Reward points for useful Answers
Regards
Anji
‎2007 Jul 06 8:40 AM
‎2007 Jul 06 8:41 AM
Hi
see the links
The Link will be helpful to you.
Very good document:
http://www.doag.org/pub/docs/sig/sap/2004-03/Buhlinger_Maxi_Version.pdf
Reward points for useful Answers
Regards
Anji
‎2007 Jul 06 8:48 AM
Hi Soumya,
In different situations problems can occur which are caused by the used codetype (UNICODE):
<b>problems during the installation (is the codetype of database and application server set correctly?)</b>
<b>problems during a database update (during the catalog migration</b>)
<b>problems with passwords (e.g. during connect using the DBSL)</b>
<b>problems with parameters concerning the size of internal buffers (e.g. PACKET_SIZE) converting problems </b>
<b>problems with data types </b>
Dependent on the error situation you need to check different files/traces. In case of installation or upgrade problems you should check the installation log files. In case of connect problems the corresponding developer traces should be checked. The database trace might also be useful in case the error occurs in the database.
If you work with a Unicode system and the files you read and write are Unicode, everything is quite safe. Problems arise when textual data is converted from Unicode to a non-Unicode character set: The data might contain characters which do not exist in the target character set. On the other hand, when textual data is converted from non-Unicode to Unicode, the typical problem is that the software assumes the data to be encoded in a code page different from the one which was actually used.
so u can use this fm
NLS_STRING_CONVERT_TO_SYS for all conversions of Hexadecimal values.
<i>if found usefull reward pts</i>
Regards
Sathish:)