This content has been marked as final. Show 2 replies
Have you tried analizing the OWBSYS schema? You can do it directly from SQL Plus or using Tools -> Optimize Repository in OWB. Oracle recomends running the optimize repository option from time to time.
the solution was surprisingly: I dropped the newly created database (UTF8) and created a new one with the WE8MSWIN1252 character set. And now it works perfectly!
I didn't know that UTF8 is just for the "Big Boys". I tried it since my customers insist on UTF8. But they have some Unix with 64 Bit. That's too much for my poor Win7.