Oracle - Enterprise Manager extractor

Ensure that you create a database user and assign the appropriate rights. During ETL configuration, specify these user details so that the ETL can connect to the database for extracting data.

You must configure the ETL to connect to OEM for collecting the OEM metrics. ETL configuration includes specifying the basic and optional advanced properties. While configuring the basic properties is sufficient, you can optionally configure the advanced properties for additional customization.

A. Configuring the basic properties

Some of the basic properties display default values. You can modify these values when required.

To configure the basic properties:

1. Navigate to Administration > ETL & System Tasks, and select ETL tasks.
2. On the ETL tasks page, click Add > Add ETL. The Add ETL page displays the configuration properties. You must configure properties in the following tabs: Run configuration, Entity catalog, Oracle OEM Configuration, and Connection parameters
   
   
3. On the Run Configuration tab, do the following:
   1. Select Oracle Enterprise Manager Extractor from the ETL module list. The name of the ETL is displayed in the ETL task name box. You can edit this field to customize the name.
   2. Specify whether you want to import the performance and configuration metrics for all entities or import only performance metrics for database instances and RAC clusters.
4. Click the Entity catalog tab, and select one of the following options:
   
   • Shared Entity Catalog: Select if other ETLs access the same entities that are used by the OEM ETL. This is the default selection.
     • From the Sharing with Entity Catalog list, select the entity catalog name that is shared between ETLs.
   • Private Entity Catalog: Select if only this ETL is used for extracting data from the OEM resources.

5. Click the Oracle OEM Configuration tab, and configure the following properties:
6. Click the Connection parameters tab, and configure the following properties so that the ETL can connect to the database:
   • An existing data source or a custom data source to which the ETL must connect
   • The database credentials and other details, such as data source name and connection URLs depending on the selected custom data source

7. (Optional) Override the default values of properties in the following tabs:

   Run configuration

   Object relationships

   ETL task properties
8. Click Save.
   The details of the newly configured OEM ETL are displayed.

(Optional) B. Configuring the advanced properties

You can configure the advanced properties to change the way the ETL works and to define the data collection period.

To configure the advanced properties:

1. On the Add ETL page, click Advanced.

2. Configure the following additional properties:

   Oracle OEM configuration

   Property	Description
   Schema to use	Specify the database schema name that you want to use. The default schema is SYSMAN.
   Entity black list	Specify the names of entities (separated by a semicolon) that you want the ETL to exclude while importing, such as clusters and database instances. You can also use regular expressions to filter entities while importing. For example, PP12DB1*;PP12DB2*
   Entity white list	Specify the names of specific entities (separated by a semicolon) that you want the ETL to import, such as clusters and database instances. You can also use regular expressions for importing entities. For example, PP11OLAM*;PS28OLAM*;PLRS*;

   Additional properties

   Property	Description
   List of properties	Specify additional properties for the ETL that act as user inputs during run. You can specify these values now or you can do so later by accessing the "You can manually edit ETL properties from this page" link that is displayed for the ETL in the view mode. Click Add. In the etl.additional.prop.n field, specify an additional property. Click Apply. Repeat this task to add more properties.

   Loader configuration

   Property	Description
   Empty dataset behavior	Specify the action for the loader if it encounters an empty dataset: Warn: Generate a warning about loading an empty dataset. Ignore: Ignore the empty dataset and continue parsing.
   ETL log file name	The name of the file that contains the ETL run log. The default value is: %BASE/log/%AYEAR%AMONTH%ADAY%AHOUR%MINUTE%TASKID
   Maximum number of rows for CSV output	A numeric value to limit the size of the output files.
   CSV loader output file name	The name of the file that is generated by the CSV loader. The default value is: %BASE/output/%DSNAME%AYEAR%AMONTH%ADAY%AHOUR%ZPROG%DSID%TASKID
   Continuous Optimization loader output file name	The name of the file that is generated by the Continuous Optimization loader. The default value is: %BASE/output/%DSNAME%AYEAR%AMONTH%ADAY%AHOUR%ZPROG%DSID%TASKID
   Remove domain suffix from datasource name (Only for systems)	Select True to remove the domain from the data source name. For example, server.domain.com will be saved as server. The default selection is False.
   Leave domain suffix to system name (Only for systems)	Select True to keep the domain in the system name. For example: server.domain.com will be saved as is. The default selection is False.
   Skip entity creation (Only for ETL tasks sharing lookup with other tasks)	Select True if you do not want this ETL to create an entity and discard data from its data source for entities not found in Continuous Optimization. It uses one of the other ETLs that share a lookup to create a new entity. The default selection is False.

   Scheduling options

   Property	Description
   Hour mask	Specify a value to run the task only during particular hours within a day. For example, 0 – 23 or 1, 3, 5 – 12.
   Day of week mask	Select the days so that the task can be run only on the selected days of the week. To avoid setting this filter, do not select any option for this field.
   Day of month mask	Specify a value to run the task only on the selected days of a month. For example, 5, 9, 18, 27 – 31.
   Apply mask validation	Select False to temporarily turn off the mask validation without removing any values. The default selection is True.
   Execute after time	Specify a value in the hours:minutes format (for example, 05:00 or 16:00) to wait before the task is run. The task run begins only after the specified time is elapsed.
   Enqueueable	Specify whether you want to ignore the next run command or run it after the current task. Select one of the following options: False: Ignores the next run command when a particular task is already running. This is the default selection. True: Starts the next run command immediately after the current running task is completed.

3. Click Save.
   The ETL tasks page shows the details of the newly configured OEM ETL.
   
   

After you configure the ETL, you can run it to collect data. You can run the ETL in the following modes:

A. Simulation mode: Only validates connection to the data source, does not collect data. Use this mode when you want to run the ETL for the first time or after you make any changes to the ETL configuration.

B. Production mode: Collects data from the data source.

A. To run the ETL in the simulation mode

1. Navigate to Administration > ETL & System Tasks, and select ETL tasks.
2. On the ETL tasks page, click the ETL. The ETL details are displayed.
   
   
   
3. In the Run configurations table, click Edit  to modify the ETL configuration settings.
4. On the Run configuration tab, ensure that the Execute in simulation mode option is set to Yes, and click Save.
5. Click Run active configuration. A confirmation message about the ETL run job submission is displayed.
6. On the ETL tasks page, check the ETL run status in the Last exit column.
   OK Indicates that the ETL ran without any error. You are ready to run the ETL in the production mode.
7.  If the ETL run status is Warning, Error, or Failed:
   1. On the ETL tasks page, clickin the last column of the ETL name row.
   2. Check the log and reconfigure the ETL if required.
   3. Run the ETL again.
   4. Repeat these steps until the ETL run status changes to OK.

B. To run the ETL in the production mode

To run the ETL manually

1. On the ETL tasks page, click the ETL. The ETL details are displayed.
2. In the Run configurations table, click Edit  to modify the ETL configuration settings. The Edit run configuration page is displayed.
3. On the Run configuration tab, select No for the Execute in simulation mode option, and click Save.
4. To run the ETL immediately, click Run active configuration. A confirmation message about the ETL run job submission is displayed.
   When the ETL runs, it collects data from the source and transfers it to the BMC Helix Continuous Optimization database.

To schedule the ETL run in the production mode

1. On the ETL tasks page, click the ETL, and click Edit task. The ETL details are displayed.
   
2. On the Edit task page, do the following, and click Save:
   • Specify a unique name and description for the ETL task.
   • In the Maximum execution time before warning field, specify the duration for which the ETL must run before generating warnings or alerts, if any.
   • Select a predefined or custom frequency for starting the ETL run. The default selection is Predefined.
   • Select the task group and the scheduler to which you want to assign the ETL task.
3. Click Schedule. A message confirming the scheduling job submission is displayed.
   When the ETL runs as scheduled, it collects data from the source and transfers it to the BMC Helix Continuous Optimization database.

Verify that the ETL ran successfully and the data is refreshed in BMC Helix Continuous Optimization.

To verify whether the ETL ran successfully

1. Click Administration > ETL and System Tasks > ETL tasks.
2. In the Last exec time column corresponding to the ETL name, verify that the current date and time are displayed.
3. In the Last exit column corresponding to the ETL name, verify that the status is OK.
   In case of WARNING or ERROR, click in the last column of the ETL name row to review the log files.

To verify whether the data is refreshed:

1. In the Workspace tab, expand (domain name) > (entities) > Systems > Instances.
2. In the left pane, verify that the hierarchy displays the new and updated instances of OEM.
3. Click an instance and click the Metrics tab in the right pane.
4. Check if the Last Activity column in the Configuration data and Performance metrics tables displays the current date.

The following image shows some sample metrics data: