Enabling discovery of Oracle Homes
BMC Database Automation can discover Oracle homes in the following ways:
- By using a global inventory pointer that references in the inventory where the home is registered.
- If the home exists in an inventory where BMC Database Automation has already discovered a database.
- By using /app/clarity/dagent/etc/oracle_inventories.conf, where you can define a list of paths to inventories on the agents.
Enabled Oracle Homes display under Pending Approval > Applications, at which point you can select and approve Oracle Homes into a domain.
Before you begin
Before you enable discovery and provisioning of Oracle Homes, ensure that the following requirement is met.
- (Windows) Registry contains the service named as OracleService<ORACLE_SID> for the database which you want to be discovered
- (Linux) /opt/oracle/oratab file contains an entry for the database which you want to be discovered
To enable discovery and provisioning of Oracle Homes
- On the BMC Database Automation manager, set can_create_oracle_home=true in /app/clarity/dmanager/etc/d2500_config.
- On the Manager, expand the /app/clarity/dmanager/var/customization.zip file.
- Open the app_manifest.xml file in a text editor and add the following line:
<application module="GA::Custom::OracleHome" />
See Pushing files to Agents by using the Manager. - Place the updated customization.zip file under /app/clarity/dmanager/var/.
- To ensure that the updated customization.zip file is delivered to the agents and extracted locally under /app/clarity/dagent/etc/custom, do one or both of the following:
- Restart the dmanager service on the manager:service dmanager restart
- Restart the dagent service on the associated agent
Where to go next
To upgrade an Oracle database, see Upgrading-a-database. To create an Oracle Home, see Creating-an-Oracle-Home.
Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*