I cannot comment on Oracle logic around the numbering ... BUT we also have the same software version and created everything with a Version 9 connection pool which works great.
Can you do this manually?
By Creating New Database in the Physical Layer and there in the Database Type selecting Essbase 11. Try this way and let us know the output.
Mark if helps,
Thanks. Thats all the confirmation I needed. I'm having another issue so can't really test things out properly but I'm certain its not related to the Essbase connection. I'll create another discussion for that.
We had the same issue. To solve it in fact, you just need to change the database connection to ESSBASE 9 and once you finish to import the cubes, you can re-change the connection to ESSBASE 11 to ensure you have full compatibility and database properties.
Thanks - yes I also have seen that - but have you found there to be any difference in system behavior whether the connector is set up 9 or 11 afterwards ?
(since we could not notice anything and maybe missed something here ?)
I'm not 100% sure but I think keeping the database in version 9 limit the possibilities in the database properties tab. So better to keep only 11. Maybe somebody will raise an SR with Oracle.
ok - thanks
will try my luck with an SR and let you know
I did raise a SR and they said to switch it to 11 after importing as mentioned above but were not able to provide any details as to the differences between 9 and 11 settings. They raised a bug in regards to the issue and I haven't heard anything since.
I'm having other major problems with Essbase in 220.127.116.11 now. So frustrating. It was half fixed by the .1 patch. Prior to 18.104.22.168.1 nqsserver crashed when creating a 2nd view on an analysis. Now it just seems to do it on Essbase sources.