RE: SQL comparison addition:

2003-11-12 Thread Chris Stephens
I'll try tracing the session. Global.client_dim is just a table with client info and a column that corresponds to client logins to enable row level security. Thanks for the suggestions. As stated earlier..i'll post the resolution. chris -Original Message- Sent: Tuesday, November 11, 200

Re: SQL comparison addition:

2003-11-11 Thread Vladimir Begun
You can flush shared pool, optionally, then enable SQL tracing and CBO tracing and check the trace file, anyway you will be asked to do that when you open a tar. What Oracle version do you use? What's the object you're referencing in your query -- global.client_dim? Is it a [partitioned] table, [m]

RE: SQL comparison addition:

2003-11-11 Thread Chris Stephens
SQL> select sys_context('userenv','session_user'), 2 dump(sys_context('userenv','session_user')), a.reports_login, 3 dump(a.reports_login) 4 from global.client_dim a 5 WHERE sys_context('userenv','session_user') = trim(a.REPORTS_LOGIN); SYS_CONTEXT('USERENV','SESSION_USER') --

Re: SQL comparison addition:

2003-11-11 Thread Vladimir Begun
Chris There is a contradiction below: Chris Stephens wrote: SQL> select sys_context('userenv','session_user'), 2 dump(sys_context('userenv','session_user')), a.reports_login, 3 dump(a.reports_login) 4 from global.client_dim a 5 WHERE sys_context('userenv','session_user') = a.REPORTS

Re: SQL comparison addition:

2003-11-11 Thread Daniel Fink
Hmmm... I was expecting to see something like Yong writes about. The only suggestion I have is to use DUMP() the next time this happens and figure out where the two strings differ. Daniel Chris Stephens wrote: > SQL> select sys_context('userenv','session_user'), > 2 dump(sys_context('userenv

RE: SQL comparison addition:

2003-11-11 Thread Yong Huang
I don't see any extraneous characters in sys_context('userenv','session_user')either. But the trailing null in v$session.machine for Windows connections is a known problem. Bug 646174 shows version 8.1.5. I tried in 9.2.0.1. It still exists: SQL> select dump(machine) from v$session where machine =

RE: SQL comparison addition:

2003-11-11 Thread Chris Stephens
But wouldn't whitespace show up when I select '|'||reports_login||'|' ?? -Original Message- Sent: Tuesday, November 11, 2003 11:34 AM To: Multiple recipients of list ORACLE-L Perhaps it's your clients? I've spouted off here before about the MACHINE column of V$SESSION having an extra C

RE: SQL comparison addition:

2003-11-11 Thread Chris Stephens
SQL> select sys_context('userenv','session_user'), 2 dump(sys_context('userenv','session_user')), a.reports_login, 3 dump(a.reports_login) 4 from global.client_dim a 5 WHERE sys_context('userenv','session_user') = a.REPORTS_LOGIN; SYS_CONTEXT('USERENV','SESSION_USER')

Re: SQL comparison addition:

2003-11-11 Thread Daniel Fink
I may be barking up the wrong tree, but humour an old dba... Could you try running the following and post the output? select sys_context('userenv','session_user'), dump(sys_context('userenv','session_user')), a.reports_login, dump(a.reports_login) from global.client_dim a WHERE sys_context('user

RE: SQL comparison addition:

2003-11-11 Thread Jesse, Rich
Perhaps it's your clients? I've spouted off here before about the MACHINE column of V$SESSION having an extra CHR(0) at then end of it for Winders clients. Maybe something similar's happening to you, but with whitespace (the TRIM in your statement won't lop off CHR(0)). HTH! Rich Rich Jesse