SQL HEXTORAW with SUBSELECT and INLIST

Question

Hello guys,
i have the following table definition
TAB_A
===========
COL1 RAW(16)
COL2 RAW(16)
TAB_B
===========
COL1 RAW(16)
COL2 RAW(16)
Now the SELECT looks like the following:
SELECT * FROM TAB_A WHERE COL1 IN ( SELECT COL2 FROM TAB_B where COL1 = HEXTORAW('12234CX'));Now i have the problem that the COL1 of TAB_A is indexed, but the index can not be used, because of oracle doesn't do an implicit conversion for COL1 of TAB_A.
How can i use the function HEXTORAW() in that case, that the values that are returned from the SUBSELECT are translated into RAW.
Thanks and Regards

Answer 1

user11981296 wrote:
Hello John,
the index is also not be used when using a HINT ... so therefore it is not an optimizer problem .. it is a "data type" problem.
RegardsNo, Oracle is fully capable of using an index on a raw column, assuming that one exists.
SQL> desc raw_test
Name                                      Null?    Type
ID                                                 NUMBER
ADDRESS                                            RAW(8)
SQL> set autot trace explain
SQL> SELECT * FROM raw_test
  2  WHERE address = HEXTORAW('5358B2E88');
Execution Plan
Plan hash value: 1291953311
| Id  | Operation                   | Name          | Rows  | Bytes | Cost (%CPU)| Time     |
|   0 | SELECT STATEMENT            |               |   897 | 17043 |     3   (0)| 00:00:01 |
|   1 |  TABLE ACCESS BY INDEX ROWID| RAW_TEST      |   897 | 17043 |     3   (0)| 00:00:01 |
|*  2 |   INDEX RANGE SCAN          | RAW_TEST_ADDR |   359 |       |     1   (0)| 00:00:01 |
Predicate Information (identified by operation id):
   2 - access("ADDRESS"=HEXTORAW('05358B2E88') )So, something else is going on. If the hint does not drive it to using the index, then you have hinted incorrectly.
John