Solution : https://service.sap.com/sap/support/notes/808505 (SAP Service marketplace login required)
Summary :
SAP Note outlines handling secondary connections with varying character sets between SAP system databases and Oracle databases. Primary databases use WE8DEC or UTF8, while secondary ones might use different regional character sets. Key considerations involve ensuring NLS_LANG environment variable matches the primary database's character set to prevent Oracle from automatic data conversion. For remote databases with an alternative character set, manual specification in DBCON transaction may be required to avoid default conversion. This ensures compatibility, particularly post-SAP kernel release 6.40 for non-Unicode systems and adjustments in the handling of character sets in the context of Oracle Instant Client and Instant Client Light. Patches and specific configurations are suggested to address issues with charset recognition during connection setups.
Key words :
parameter valuenls_language americannls_territory americanls_characterset we8dec, internal sap character sets utf16, terms multiple nls environment, fixed key word nchar, permitted character sets mentioned, country-specific character sets, easy connect string exists, unicode solution note structure, unsupported server character set %, instant client light version
Related Notes :
| 1319517 | Unicode Collection Note |
| 606359 | FAQ: Oracle National Language Support (NLS) |