Wrong Client NLS settings when running R3trans

[Former Member]

Hello, after refresh of TST database with PRD database (NLS LANG AMERICAN_AMERICA.WE8DEC), I created the OPS$DOMAIN\TSTADM and OPS$DOMAIN\SAPSERVICETST and reset the SAPSR3 pasword using brconnect.

The R3trans -x fails :

ERROR => Cannot decrypt password I got from table SAPUSER: rc = 16

What I can see that may be the cause is the

Client NLS settings: AMERICAN_AMERICA.UTF8

which should be AMERICAN_AMERICA.WE8DEC, since environment variable NLS_LANG is set in this way, and the database is also WE8DEC.

Can anybody why the NLS setting is wrong ? how to fix it?

Thanks a lot kin regards,

Dino Dose

[Former Member]

Which DB/OS?

On unix/oracle there are .csh and .sh environment files for Oracle user in home directory of sidadm and orasid. There you can change the NLS settings.

Can you paste the entire trans.log file.

[Former Member]

Hello. I found the matter. It is Windows path in the environment.

There are two kernels on the disk, uc and nuc. The uc path came before the nuc, so when running R3trans , the unicode version was started, causing the error.

Fixing the path the non unicode R3trans was started and the return code was 0000.