Posted by: Peter Scott on: January 14, 2008
Recently, I mentioned a quirk in OWB 10.2 with a dimension table target configured as a type 2 slowly changing dimension. We have been working on some load performance problems with straight-forward OWB maps. As part of this investigation we wanted to change some of the hints being used in the mapping; for a start we wanted to remove the parallel hint. This is relatively simple to do (in principle) go into the mapping configuration, chose the the dimension operator and then go into the load hint window and make your choices. However the choices don’t stick and a few moments later they are back to the default APPPEND & PARALLEL. On the other hand, OWB 11g has no default load hints on dimension operator.
Oh, one final thing, if you are part of a team developing OWB maps check that all of your development workstations are using the same JAR file versions, least the code you deploy works (and performs) differently to that of your colleagues.
Pete,
I checked this issue on 10.2.0.2 and oddly enough, there are no default hints on the table operators for the dimension. Sounds like something they put in in 10.2.0.3 and took out again in 11g …
Borkur
[...] gig with an old client up there and spent my days (as short and dark as they were) sitting next to Pete Scott and drinking coffee. We had run in to a bit of problem with bad performance of some OWB mappings [...]
January 14, 2008 at 8:39 pm
Peter,
Have you got any specifics for the type of jar files we should keep in sync? There are quite some of them in an OWB installation as you probably know.