Do you want to use the Oracle In-Memory Advisor in an Oracle Multitenant environment?
This is possible but with the current version it will require a workaround. The next available version of the IM Advisor is designated to support it without any workarounds.
At the moment the IM Advisor does not install into the CDB$ROOT container. But it can be installed into any PDB.
- Create the user IMADVISOR in the PDB as local user first
- No objects must be placed into the IMADVISOR schema but the user must have a default and a temporary tablespace
- Install the IM Advisor locally in this PDB by using the install script imstimadv.sql
- The script will detect the presences of the IMADVISOR schema. If the IMADVISOR schema is empty, it will proceed. It will then ask you to press ENTER instead of prompting you to set the password and default tablespace. Unless you setup the IMADVISOR user with an automated authentication method, it will still prompt you for the IMADVISOR’s password when it connects to the IMADVISOR user
An issue which I learned about in the past days:
ORA-24817 get raised when using the IM Advisor.’s imadvisor_fetch_recommendations script unless you do not have a massive shared pool configured. The script does a SET LONGCHUNKSIZE 2000000000; and this needs to be reduced.
There has been a bug filed for it and I think it’s supposed to be fixed in the next release of the IM Advisor.
–Mike
