Database Software

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

OWB 10.2 Key lookup generates wrong code

572152Apr 12 2007 — edited Jul 17 2007

Hi. I have a problem with the key lookup component. When using the component with values from a constant it produces SQL that makes a LEFT OUTER JOIN towards the lookup table. That means I get all the rows in the lookup table instead of only the row with a known natural key specified in the constant attribute. Example of SQL produced

SELECT
NVL("KEY_LOOKUP"."FORVALTNING_NKEY", NULL) "FORVALTNING_NKEY",
NVL("KEY_LOOKUP"."FORVALTNING_NAME", NULL) "FORVALTNING_NAME",
NVL("KEY_LOOKUP"."FORVALTNING_ID", NULL) "FORVALTNING_ID"
FROM
"FORVALTNING" "KEY_LOOKUP"
LEFT OUTER JOIN DUAL CONSTANT ON ( ( "KEY_LOOKUP"."FORVALTNING_ID" = FULLPACKAGENAME."GET_CONSTANT_0_DUMMY" ) )

When not using the key lookup component with a constant operator, a RIGHT OUTER JOIN is produced in the SQL. In version 10.1, the (+) outer join operator was used and it worked. We have quite a lot of mappings that we DON'T want to change. Anybody knows if this bug/feature has been fixed in any patch?

Locked Post

New comments cannot be posted to this locked post.

Locked on Aug 14 2007

Added on Apr 12 2007

#data-warehousing, #warehouse-builder

7 comments

1,330 views