I keep seeing things pop up and people having trouble getting the Discoverer / BIP integration working. I will say this is not the easiest of configurations, but with some additional steps anyone should be able to complete the task. For those of you that have been following along, the latest Discoverer Cumulative Patch (CU4, p6357481) was released and the Discoverer / BIP integration was not included with created a new interop patch for everyone numbered 6622352.
Just a couple notes on the install. If you are applying the patch to a unix system you’re going to have to run the dos2unix command on the CreateOIDContainer.sh file in the <OH>/discoverer/util directory.  Also, notice the CreateOIDContainer.sh file, yes its case sensitive and don’t forget to edit the file and replace the %ORACLE_HOME% directive with your actual Oracle Home path, while you’re at it make sure you chmod 750 CreateOIDContainer.sh too. Can you tell it was a windows guy who wrote the script ;-).
Anyways, before executing the CreateOIDContainer.sh script you’ll also need to properly setup all your paths which includes:
export ORACLE_HOME=<Your Oracle Home Path>
export LIBPATH=$ORACLE_HOME/lib32:$ORACLE_HOME/lib:$ORACLE_HOME/jlib:$LIBPATH
export LD_LIBRARY_PATH=$ORACLE_HOME/lib32:$ORACLE_HOME/lib:$ORACLE_HOME/jlib:$LD_LIBRARY_PATH
The big kicker that bit me this last time was that I was getting an error that the Discoverer product container doesn’t exist in the OID Repository. Well, for some reason that container doesn’t actually exist until a user is created in the OID through something like OIDDAS, since this client was using Server Chaining to bring in all their users (another blog post soon) we had never actually created a “new” native user in OID.
Needless to say the 10.1.2.3 Discoverer patch set can’t come soon enough which includes this patch with it. Till then feel free to drop me a line if you have any questions. If you want some more in depth examples of the config let me know and I’ll get some screen shots the next time I do this.