Control Compliance Suite, Oracle Data Collector: query returned with message(s).,"Oracle Homes Not Found on server.
search cancel

Control Compliance Suite, Oracle Data Collector: query returned with message(s).,"Oracle Homes Not Found on server.

book

Article ID: 163210

calendar_today

Updated On:

Products

Control Compliance Suite Databases Oracle

Issue/Introduction

When collecting from an Oracle Configured Database type asset, the following error is seen in the messages tab of the job: {DATE.EN_US} {TIME.EN_US},Oracle Data Collector: query returned with message(s).,"Oracle Homes Not Found on server. on server {HOSTNAME.EN_US}.{DOMAIN.EN_US}.com. ",Error,{SID.EN_US}.{HOSTNAME.EN_US}.{DOMAIN.EN_US}.com,Oracle Configured Databases,, 

 

in the messages tab of the job;

{DATE.EN_US} {TIME.EN_US},Oracle Data Collector: query returned with message(s).,"Oracle Homes Not Found on server. on server {HOSTNAME.EN_US}.{DOMAIN.EN_US}.com. ",Error,{SID.EN_US}.{HOSTNAME.EN_US}.{DOMAIN.EN_US}.com,Oracle Configured Databases,, 

in the BVOOSStrategies.log on the data collecting CCS manager;

  4D|     558|     5F8|"blade|BVOUnixOracleHo|  270| 4/28/2016|14:30:23:376|Information:Failed getting Oracle Home from oratab file
  4E|     558|     5F8|"blade|BVOUnixOracleHo|  271| 4/28/2016|14:30:23:376|Information:
sidDEV1:/u01/app/oracle/product/12.1.0/dbhome_1:D
  4F|     558|     5F8|"blade|BVOUnixOracleHo|  272| 4/28/2016|14:30:23:376|Error:0x80004005
  50|     558|     5F8|"blade|BVOUnixOracleHo|  390| 4/28/2016|14:30:23:376|Information:In OracleHomeFallback1

 

Cause

This error message is returned when the data collector cannot read/access the /etc/oratab file or when the /etc/oratab has unexpected entries.

example of unexpected entry in /etc/oratab

sidDEV1:/u01/app/oracle/product/12.1.0/dbhome_1:D  <= unexpected "D" and causes the error
sidDEV2:/u01/app/oracle/product/12.1.0/dbhome_1:Y
sidPRD2:/u01/app/oracle/product/12.1.0/dbhome_1:N

The format of /etc/oratab stipulates a Y or a N at the end of the line, anything else is not valid and also causes the Oracle Data collector to throw this error.
 

Resolution

  1. Make sure the /etc/oratab file can be accessed, queried and enumerated.
  2. Make sure the format of the /etc/oratab file is correct, a Y or a N at the end of each line.