Non UTF-8 Character in V$session

Question

Hello
The oracle clusterware process racgimon is putting a Non utf-8 character into v$session and so causing problems. The value is NT-AUTORITÄT\SYSTEM. Any ideas of how to correct this ?
Database Parameters
NLS_LANGUAGE     GERMAN
NLS_TERRITORY     GERMANY
NLS_CHARACTERSET     AL32UTF8
Thank you.

Answer 1

I did something along that line (but I used a different test account since System account localisation is different on my test machine) - see below.
So far it would seem the case is that certain characters (code) in v$session.osuser is not handled properly, in general, not only for racgimon.exe.
Perhaps the assumption is that os account names for 'osuser' consists of ascii characters only (and read as such, even if codes 0x80-FF is used).
The value of CharacterSet from dump() output above is misleading for this column as it isn't 'typed' correctly (as you say, non utf-8 representation), as it would be with regular tables'. Still, I believe something similar to "pass-through scenario" is going on.
Note on the use of [url http://download.oracle.com/docs/cd/B28359_01/server.111/b28286/functions027.htm]convert function, as it should not be used, however it says "+...the only practical use of the function is to correct data that has been stored in a wrong character set.+" which would seem to apply here, so I guess this temporary use of convert is ok.
The account setup for test is AüTÄT, just to involve some non-ascii characters.
SQL> select osuser
  , dump(osuser,16) dump_incorrect_chars
  , convert(osuser,'al32utf8','we8mswin1252') osusercorr
  , dump(convert(osuser,'al32utf8','we8mswin1252'),16) dump_corrected
from v$session
where program = 'sqlplus.EXE';
OSUSER               DUMP_INCORRECT_CHARS
OSUSERCORR           DUMP_CORRECTED
Odd7\A¿T¿            Typ=1 Len=10: 4f,64,64,37,5c,41,fc,54,c4,54
Odd7\AüTÄT           Typ=1 Len=12: 4f,64,64,37,5c,41,c3,bc,54,c3,84,54I also found that oracle.exe process itself, started under Localsystem, is using a "common" name instead. It shows up as SYSTEM instead of LocalSystem or principal name in v$session.osuser. Perhaps this is related to how/from where process is spawned, via SCM or not (e.g. Scheduler).
SQL> select sid, osuser, program from v$session;
SID OSUSER               PROGRAM
   2 SYSTEM               ORACLE.EXE (PMON)
  15 SYSTEM               ORACLE.EXE (MMON)
  16 SYSTEM               ORACLE.EXE (MMNL)
  17 NT instans\SYSTEM    sqlplus.EXEI guess, to avoid this mess, we need to find some workaround such as:
- change the client process os account i.e. start as .\Localsystem or account other than Localsystem.
- change locale for the user account so that non localised name NT-AUTHORITY\SYSTEM is used
- change the way process is started, so that user name is picked up without the NT-AUTORITÄT prefix.
Hope this helps.
Edited by: orafad on May 25, 2011 1:59 PM
Edited by: orafad on May 25, 2011 2:25 PM