pok3rm4n
asked on
running SQL query on multiple database targets from Oracle cloud control 12c
Hello Experts,
I have Oracle cloud control 12c, with 11g OEM repository database. There are many database targets registered which are a mix of 11g and 12c. When I run SQL queries againt multiple targets, it fails on 12c database targers with the below message
Unable to launch /usr/app/oracle/product/11 .2.0/bin/s qlplus -s /nolog : No such file or directory
Looks like this is due to the database on cloud control is 11g which is what is currently certified.
I am just trying to understand how I can work around this problem and get to run sql queries against 11g and 12c databases from my cloud control.
Thanks
I have Oracle cloud control 12c, with 11g OEM repository database. There are many database targets registered which are a mix of 11g and 12c. When I run SQL queries againt multiple targets, it fails on 12c database targers with the below message
Unable to launch /usr/app/oracle/product/11
Looks like this is due to the database on cloud control is 11g which is what is currently certified.
I am just trying to understand how I can work around this problem and get to run sql queries against 11g and 12c databases from my cloud control.
Thanks
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Ine thing I failed to mention was that some of these targets where the query was failing were upgraded from 11g to 12c. As mark suggested, the target information was not updated in cloud control after the target database was upgraded to 12c. I would have thought this would be automatic.
For those interested in the solution, I updated ORACLE_HOME setting following the steps mentioned in "Section14.8.2 Configuring a Target Database for Secure Monitoring"
https://docs.oracle.com/cd/E63000_01/EMADM/discovery_db.htm#EMADM15264
Regards,
For those interested in the solution, I updated ORACLE_HOME setting following the steps mentioned in "Section14.8.2 Configuring a Target Database for Secure Monitoring"
https://docs.oracle.com/cd/E63000_01/EMADM/discovery_db.htm#EMADM15264
Regards,
If Iam not wrong the SQL statement has to be executed via the OEM agent