Turbo Tip: Adding Oracle DB as a Target

Document created by gp.deciantis Expert on Sep 9, 2015Last modified by Stephen Wilson on Oct 3, 2016
Version 8Show Document
  • View in full screen mode

     Turbonomic extends its control from the infrastructure and VM level into the applications. By collecting data from application targets Turbonomic is able to understand the application demand for resources AND make intelligent decisions to ensure that the demand is always being met by your infrastructure.

 

NOTE :: The following documentation is only applicable for versions higher than Turbonomic 5.2 licenses with Application Control Support.  If you do not have the Application Control Module or Application Edition, please contact your Customer Experience representative or your Account Executive for licensing.

 

 

This setup is designed to guide you through implementing application control for Oracle databases.

 

Prerequisite for installation

  • Check to make sure that you are running a version of Turbonomic higher than 5.2
    • You can do so by following the instructions located here
  • Have the ability to connect to the Oracle instance as the sysdba user
    • On Linux
      • SSH to your Oracle instance
    • On Windows
      • Connect to a RDP session and use the command prompt
  • The Service ID (SID) of the oracle instance you want to connect to.  This information should be provided by the Oracle DBA.

 

NOTE :: You may require your company's Oracle DBA to perform the installation steps.

 

1.  Checking for the Dynamic Performance View to Oracle DB

 

Turbonomic reads exclusively from the Dynamic Performance View (V$) to gather the metrics required to assure performance on Oracle DB.  To validate that these view are here you must do the following. 

  • For Oracle instances installed on Linux
    • SSH to the linux instance that Oracle is running on
  • For Oracle instances installed on Windows
    • RDP to the Windows instance and bring up a command prompt
  • Connect to the Oracle instance as sysdba using the sqlplus command.
    • sqlplus /nolong
    • connect <user> as sysdba
  • Validate that the Dynamic Performance views or "V$" tables are created by running the following command
    • select * from dba_tables;

If a result is returned then the dynamic views are already created and you can move on to step 2.  If a result is not returned then these views need to be created

 

1.A Create Dynamic Performance Views

  • Create the views by running the following command
    • NOTE :: This must be run as a user connected as SYSDBA
    • @?/rdbms/admin/catalog.sql

This will create all the views and synonyms required for V$ to be accessible. It may take a few minutes for this script to complete.  Once these views are created you can proceed to step two

 

2. Configuring an Oracle user for Turbonomic

After V$ has been created you must have a user that is able to access V$.  In the next steps we will create a user called 'turbonomic_acm' with a password 'password'. You will likely want to change the username and password combination to fit the policies of your business.

 

  • Create the turbonomic user
    • Run the create user command at the sqlplus prompt
      • CREATE USER turbonomic_acm IDENTIFIED BY password;
    • Grant connection privileges to the turbononmic user
      • GRANT CONNECT TO c##vmturbo_acm;
    • The turbonomic user needs to have access to both the V$ tables and the temp tables to run queries when collecting data
      • GRANT select_catalog_role to 'turbonomic_acm';
      • GRANT resource to 'turbonomic_acm';

 

Below are the views that Turbonomic needs to access to collect data from an Oracle instance:

 

V$INSTANCE

V$LOG

V$LOGFILE

V$PARAMETER

V$PGASTAT

V$RESOURCE_LIMIT

V$SGASTAT

V$SYS_TIME_MODEL

V$SYSMETRIC

V$SYSSTAT

 

 

3. Adding Oracle DB targets to Turbonomic

 

  • Go to the Admin Tab > Workflows > Target Configuration > Database > Oracle
  • Set the Scope to the custom group you created in Step 1. And replace the Port Number, Service, Username, and Password values with the port, SID, username, and password values from the previous steps respectively.
    • NOTE :: For Scope to work properly all Oracle SID must be the same.

 

Screen Shot 2015-09-09 at 8.54.39 AM.png

4. Click “Add” and “Apply”

5. Make sure to hit the "Rediscover" button after adding your targets

6. You will eventually be able to see your Oracle DB discovered in the Inventory tab.

Attachments

    Outcomes