I recently setup OWB for 11g R2 right after installing Oracle 11g. It’s fairly smooth to do, but there are some quirks along the way, enough to drive you batty. So I thought I’d share a few hints and techniques here…
1) during install, use the repository administration creation utility… BUT before you start, create the REPOSITORY USERS and REPOSITORY OWNER in the target database FIRST, also – grant them all the OWB_USER role. Otherwise, having OWB “create users” can cause problems along the way (it did for me anyhow)…
2) Make SURE your OWB user/owner is NOT the same as a source/target user in your database.
3) RUN THE ADMIN/CREATE ON THE SAME SERVER AS THE ORACLE SERVER INSTANCE!! I found out the hard way, that the stand-alone client for OWB doesn’t have all the necessary “install & prep” scripts needed for the repository.
4) After SUCCESSFUL install (you may need to run it twice or three times), go to all the INVALID PACKAGES in the OWB SCHEMA, and “re-compile them” completely, one at a time in alphabetical order. This should fix the INVALID packages (my install had about 5) that are needed for deployment.
5) After that, run OWB, log in for the first time – say NO to the upgrade option, and CONFIGURE your workspace to have the proper work areas.
oh by the way, if you ever get “java errors” while working with a mapping, then most likely the mapping is “corrupted” which means you MUST delete it and re-create it. Sometimes, it’s as easy as deleting only one of the corrupted transformations, and re-adding it.
You should be good to go.