does anybody know from where the language and codepage settings for the SQL connection are picked up, when an Essbase load rule uses an OCI connection to an Oracle database for dimension or data loads? We already tried to set the environment variable NLS_LANG but it seems not to work for the codepage.
Problem is that there are some characters in dimension alias names on the SQL side which we would like to translate to a certain codepage to have them look OK in the cube. On an old Essbase system (V7) we used the Oracle ODBC driver which worked OK for the tranlation. On the current system (EPM 188.8.131.52) Oracle OBDC is not working at all and the data direct ODBC drivers also do not translate correct. Therefore we would like to try OCI.
Switching to Unicode is no option as quite a bit of the end-users are accessing the cubes via Excel AddIn, which does not support Unicode.
Thanks & Regards,