Isn't it a permission issue in your DB?
Are you sure the user you use to connect to the DB is allowed to see the view and use it?
You also can create the view yourself by hand in the physical layer directly, it will just be a bit annoying as you will have to create all the columns and set their types accordingly to your view, but still a way to do things (which doesn't help if you have permissions issues as the view will not be accessible).
Hi Gianni, thanks for you answer. Table DWH_R12.FAC_RECEIVING_TAB is visible in the physical layer. It does not carry any grants. DB-User of all OBIEE tables and views is the DB-user DWH_R12. That user has almost all rights like SYS. This user did CREATE OR REPLACE VIEW DWH_R12.PFAC_VENDOR_PERF_OV_V as .... BI Administration Tool connects with user weblogic. I'm don't know what DB-User is used by BI-Server/weblogic, but as checked above: other DWH_R12.tables without any grant are visible for BI-Server/weblogic. regards LPNO
Hi Gianni, Thanks for your answer, that gave me an idea. Now here's the setup to get it right. It was quite a long way…
I used an ill connection pool. This was created by my wizard choices, when I created a RDP-File from scratch and it had used
Data source name: R12-Test (the ODBC-connection to talk to BI-Server)
Crucial point is the connection type. Default here is ODBC, thus this connects the physical layer back to BI-Server. Because of this I guess I got this strange circular reference, where I get in the input, what should be shown in the output. All other strange error were because this user did not have much permissions/rights After changing the connection pool properties to
Then it connected the right way round and meta data import started to fly.