×
 
 
  •  
$helper.renderConfluenceMacro('{bmc-global-announcement:$space.key}')

Space banner

   

This version of the product has reached end of support. The documentation is available for your convenience. However, you must be logged in to access it. You will not be able to leave comments.
BMC Database Automation 8.9 ... Configuring after installation Discovering databases

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.

Note

  • The oracle_inventories.conf file should have an entry for each inventory on the node (specify the location to the inventory, not the home) one per line. For example, /app/oracle/oraInventory
  • Changes to this file only take effect after the dagent service has been restarted.

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

Important

For new installations of version 8.6 and later, these settings are enabled by default.

  1. On the BMC Database Automation manager, set can_create_oracle_home=true in /app/clarity/dmanager/etc/d2500_config.

  2. On the Manager, expand the /app/clarity/dmanager/var/customization.zip file.
  3. 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.
  4. Place the updated customization.zip file under /app/clarity/dmanager/var/.
  5. 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

Note

Ensure that there are no jobs running before you restart the manager service.
    • Restart the dagent service on the associated agent

Note

If there is no Global Inventory Pointer or any existing databases on the nodes, you must define a list of paths to inventories on the Agents to facilitate Oracle Home discovery by editing the following file:

/app/clarity/dagent/etc/oracle_inventories.conf

The oracle_inventories.conf file should have an entry for each inventory on the node, one for each line, for example: /app/oracle/oraInventory.

Where to go next

To upgrade an Oracle database, see Upgrading a database. To create an Oracle Home, see Creating an Oracle Home.

Was this page helpful? Yes No Submitting... Thank you
Last modified by Winner kumar Jaiswal on Dec 20, 2018
discovery task oracle_home

Comments

Log in or register to comment.

Discovering databases
Enabling discovery of Sybase databases
© Copyright 2013 - 2018 BMC Software, Inc.
Legal notices

Powered by Atlassian Confluence and Scroll Viewport

© Copyright 2005-2024 BMC Software, Inc. Use of this site signifies your acceptance of BMC’s Terms of Use . BMC, the BMC logo, and other BMC marks are assets of BMC Software, Inc. These trademarks are registered and may be registered in the U.S. and in other countries.