Skip Headers
Oracle® Warehouse Builder User's Guide
11g Release 1 (11.1)

B31278-06
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

27 Auditing Deployments and Executions

Auditing deployment and execution information can provide valuable insights into how your target is being loaded and how you can further optimize mapping and process flow settings and parameters. It also provides immediate feedback on deployment information that enables you to retrieve the deployment history of an object. The Repository Browser in Oracle Warehouse Builder provides the auditing and deployment information.

This section covers the following topics:

About the Repository Browser

The Repository Browser is a browser-based tool that generates reports from data stored in Oracle Warehouse Builder repositories. Using the Repository Browser, you can view:

As an alternative to using the Repository Browser, you can access the same information through the public views. Start a SQL*Plus session and query the public views. Refer to Oracle Warehouse Builder API and Scripting Reference for a list of public views.

Viewing Audit Reports

Audit reports provide information about deployment and ETL jobs. Each time you deploy an object or start a job, the details of these activities are stored in the workspace. You can access this information from the following environments:

  • Control Center Manager

  • Repository Browser

The Repository Browser provides the information in the form of predefined reports. The reports are displayed in your default Web browser. Note that the Repository Browser Listener must be running.

To use the Repository Browser:

  1. From the Design Center Tools menu, select Repository Browser.

  2. On the connection page, log in with your user name and password.

You can also open the browser when the Design Center is closed.

Opening the Repository Browser

Opening the Repository Browser is a multistep process:

  1. Before you can open the Repository Browser, the Repository Browser Listener must be started as described in "Starting the Repository Browser Listener in Windows".

  2. When the Repository Browser Listener is running, you can start the Repository Browser in a number of ways as described in "Starting the Repository Browser".

  3. The Repository Browser opens to the Login page where you log in to a workspace as described in "Logging in to a Workspace".

Note:

To open the Repository Browser, you must have the ACCESS_PUBLICVIEW_BROWSER system privilege. You automatically have this privilege when you are the owner of the workspace you want to browse. When you are not the owner of the workspace, contact your database administrator who can give you this privilege.

Starting and Stopping the Repository Browser Listener

Before you can open the Repository Browser, the Repository Browser Listener must be started.

Starting the Repository Browser Listener in Windows

Open a command prompt window and run startOwbbInst.bat. This file is located in the OWB_ORACLE_HOME\owb\bin\win32 directory. Set the password for the oc4j administrator.

Stopping the Repository Browser Listener

Open a command prompt window and run stopOwbInst.bat. Provide the oc4j administrator password that you set while running startOwbInst.bat.

The stopOwbbInst.bat file is located in the OWB_ORACLE_HOME\owb\bin\win32 directory.

Starting the Repository Browser Listener in Unix

Run ./startOwbbInst.sh. This file is located in the OWB_ORACLE_HOME/owb/bin/unix directory. Set the password for the oc4j administrator.

Stopping the Repository Browser Listener in Unix

Run ./stopOwbInst.sh. Provide the oc4j administrator password that you set while running startOwbInst.sh.

The stopOwbbInst.sh file is located in the OWB_ORACLE_HOME/owb/bin/unix directory.

Starting the Repository Browser

Once the Listener is running, you can start the Repository Browser in any one of the following ways:

  • From the Start menu, select Programs, then the Warehouse Builder folder, and then Warehouse Builder, Repository Browser.

  • From the menu of the Design Center of the Warehouse Builder, select Tools, Repository Browser.

  • From within any web browser, type the location of the Repository Connection page. For example, if the Repository Browser Listener is running on a machine named owb_server, then typing the following address will start the Repository Browser:

    https://owb_server:8999/owbb/RABLogin.uix?mode=design

    or

    https://owb_server:8999/owbb/RABLogin.uix?mode=runtime

Regardless of which approach you take, once you start the Repository Browser, the browser opens the Repository Connection page from which you log in to the Repository Browser.

Logging in to a Workspace

To log in to a workspace, specify the connection information for the workspace you would like to access. If you do not know the connection information, contact your database administrator.

Once you log in to the repository browser, you can view any of the following reports:

  • Deployment

  • Execution

  • Management

If you want to browse through the workspace using the Repository Navigator page, select Design Center: Navigator.

The Design Center

When you log in, the Repository Browser opens the Reports page. From this page you can navigate to the Navigator page to obtain information about the design of Oracle Warehouse Builder Repositories such as:

Repository Navigator

Use the Repository Navigator page to search the metadata of a workspace and to access metadata main properties, lineage, impact analysis, and a list of related reports and Control Center reports for the workspace.

Search

Search by the object type, or name, or both.

  • To search by object type, select the type of object you want to search from the Search By Type list. The search result is a list of all objects of this type.

  • To search by name, type the name of the object in the Search field. You can search for just the first character of the name, in which case the search result is a list of objects whose names begin with that character.

Click Go to start your search.

The Repository Browser displays the results of the search in a new page called the Repository Objects Search page. You can also search for the new objects from this page.

All

Contains a navigator tree for the workspace.

The use of the columns is described in Table 27-1:

Column Head Description:

Focus

Click an icon in this column to change the focus of the tree.

Name

The name of an item in the tree.

Click the plus (+) or minus (-) sign next to an item in the tree to expand or collapse the tree.

Click the Name of the object to open the Object Properties page for that object.

Reports

Click an icon in this column to open the Object Reports page for the related item.

Lineage

Click an icon in this column to open the Object Lineage page for the related item.

Impact

Click an icon in this column to open the Object Impact page for the related item.


Refresh

Click to refresh your view of the workspace.

The tree collapses when you refresh the data. If you had navigated or focused to a specific area before refreshing, you need to navigate or focus again to the desired node in the tree.

Related Links

Click Control Center: Reports to open the Control Center Reports page from which you can select a deployment, execution, or management report.

Object Reports

The Object Reports page provides access to the predefined Design Center reports for the object that you selected in the Repository Navigator. Use these reports to examine your metadata.

Click a Report name to display a report.

The following types of reports are available:

Summary Reports

The type of information displayed in a summary report is determined by the object selected. For example, a Table Summary Report lists all tables in the module. A Materialized View Summary Report lists all materialized views in the module. Header information that identifies the module is also displayed. Selecting the name of an item displays the detailed report for that item.

Summary reports are available for the following objects:

Advanced Queue
Collection
Cube
Dimension
External Table
File
Function
Materialized View
Procedure
Sequence
Table Library
Table Function
Table
Transform Map
View

Detailed Reports

The type of information displayed in a detailed report is determined by the object selected. Detailed reports provide comprehensive information about an item. For example, a Detailed Table Report lists information about the table columns, keys, foreign keys, and physical configuration parameters.

Detailed reports include:

Detailed Advanced Queue Report
Detailed Collection Report
Detailed Connector Report
Detailed Cube Implementation Report
Detailed Dimension Implementation Report
Detailed Dimension Report
Detailed External Table Report
Detailed File Module Report
Detailed File Report
Detailed Function Library Report
Detailed Function Report
Detailed Installation Report
Detailed Location Report
Detailed Materialized View Report
Detailed Module Report
Detailed Object Report
Detailed Process Flow Activity Report
Detailed Process Flow Module Report
Detailed Process Flow Package Report
Detailed Process Flow Package Report
Detailed Process Flow Report
Detailed Process Transition Report
Detailed Project Report
Detailed Record Report
Detailed Repository Report
Detailed Runtime Location Report
Detailed Sequence Report
Detailed Table Function Report
Detailed Table Report
Detailed Transform Map Report
Detailed Transform Map Report
Detailed View Report

Implementation Reports

Implementation Reports can be run on Dimensions and Cubes. They provide information about how physical objects are used to implement logical objects.

Impact Analysis Reports

Impact Analysis Reports list all items belonging to the subject of the report. The name of the mapping and the name of the item that it is mapped to is also displayed. The report provides a one-step impact analysis for all items related to the selected item.

For example, if you want a list of all the columns in a table used as sources in any mappings, use this report.

Lineage Reports

Lineage Reports are similar to Impact Analysis Reports. They list items that are used as targets in a mapping.

Object Properties

The Object Properties page displays the properties of the object that you selected in the Repository Navigator.

From this page you can go to the Object Reports, Object Lineage, or Object Impact pages by clicking on the corresponding link on the left side of the page.

Object Lineage

The Object Lineage page displays the lineage diagram for the object that you selected in Repository Navigator. A Lineage Diagram graphically displays all the objects and transformations that are used to make up the subject of the Diagram. Lineage can be performed at either the object level or the item level. At the Object Level, the diagram can contain Tables, Views, Materialized Views, Dimensions, Cubes, Records, and Operators. At the item level the diagram can contain Columns, Measures, Fields, Operator Parameters, and Level Attributes. The Lineage Diagram is displayed with the subject on the right side of the screen.

From this page you can go to the Object Properties, Object Reports, or Object Impact pages by clicking on the corresponding link on the left side of the page.

Object Impact

The Object Impact page displays the Impact Analysis diagram for the object that you selected in the Repository Navigator. The Impact Analysis diagram is a graphical representation of the objects on which the definition of the selected object depends. As such, it represents the potential impact of a change in the definition of the selected object. The subject is displayed on the left side of the screen.

From this page you can go to the Object Reports, Object Properties, or Object Lineage pages by clicking on the corresponding link on the left side of the page.

Lineage and Impact Analysis diagrams are created based on a Dependency Index. In order for the data displayed in the diagram to be current, the index must be refreshed.

Control Center Reports

The Control Center section of the Repository Browser provides the following types of reports: Deployment Reports, Execution Reports, and Management Reports.

Note:

You can access the Design Object Reports from any Control Center Reports by clicking the Design Repository: Navigator link on the report page.

Deployment Reports

Top-level deployment reports are:

From these top-level deployment reports, you can accessDeployment Error Detail Reports and Deployment Reports that supply details about the deployment of a specific process flow, mapping, or data object.

Execution Reports

Top-level execution reports

From these top-level execution reports, you can access other reports that allow you to:

Management Reports

The main Repository Browser management report is the Service Node Report that displays and allows you to manage service node information for the RAC system.

Also, from a Locations Report (a top-level deployment report) you can access the Location Validation Report that shows basic Location attributes, current Control Center connection details, and current Location connection details.

Deployment Reports

Top-level deployment reports are Deployment Schedule Report, Object Summary Report, andLocations Report. From these top-level deployment reports, you can accessDeployment Error Detail Reports and Deployment Reports that supply details about the deployment of a specific Process, Map, or Data Object.

Deployment Schedule Report

The Deployment Schedule report is a top-level Control Center report that shows basic attributes and displays a node-tree giving details of all deployments in time order.

Use Deployment Schedule reports to view run details, and access Data Object, Map, and Process Deployment reports. With a Deployment Schedule Report, you can:

  • Expand deployments to show run details.

  • Filter deployments on date range.

  • Set a date range for which you want to view deployments.

  • Refresh report to show up-to-date deployment details.

  • When you have sufficient privileges, you can purge selected deployment audit details.

Location Deployment Schedule Report

A Location Deployment Schedule Report is similar in appearance to a Deployment Schedule Report except that it only shows the deployments for a specific location and does not offer you the opportunity to purge audit details.

Deployment Details Report

A report with the columns described in the following table:

Column Name Description
Select Click to select this node in the deployment tree. This functionality is used in conjunction with the purge facility on Deployment Schedule Report.
Focus Click the icon in this column to change the focus of the tree to this node.
Name A tree that represents all of the items in this deployment report. To expand a node, click its plus icon (+). To collapse a node, click its minus icon (-).
Dep A number that identifies a deployment run.
Type The type of item.
Obj Status The status of the object.
Date The date of deployment.
Dep Status The status of the deployment. These include the following:
  • Complete: Indicates that the deployment is complete.

  • Busy: Indicates that the deployment is in progress.

  • Ready: Indicates that the job has just started or is about to end.

Note: If the deployment status shows a Ready status for a very long time, use the script deactivate_deployment.sql located in the OWB_ORACLE_HOME/owb/rtp/sql folder to deactivate the status of the deployment.

Related Information Other related information including a link to a related Deployment Error Detail Report, if appropriate.

Locations Report

This deployment report shows all Locations into which objects have been deployed.

Within this report, you can:

  • Sort Locations on name and latest deployment time.

  • When you have sufficient privileges, you can un-register selected Locations.

  • When you have sufficient privileges and a link appears in the Validation column, you can open a related Location Validation Report in order to test and update connection details for a Location.

Object Summary Report

An Object Summary Report shows basic attributes and lists deployed objects (Processes, Maps and Data Objects) in type/name order with details of their latest deployment.

Within this report, you can:

  • Sort execution runs on name, type, location, latest deployment time, object status.

  • Filter objects on type and status.

Location Object Summary Report

A Location Object Summary Report is similar to an Object Summary Report except that it also includes a Location parameters section. When you have sufficient privileges, you can update certain Web Server Base parameters, if applicable.

Deployment Report

This help topic is displayed for Data Object Deployment Report, Map Deployment Report, and Process Deployment Report

This deployment report supplies details about the deployment of a specific Process, Map, or Data Object.

When the item is a Process, this report shows basic Process attributes and lists all deployments of the Process and its sub-Processes in time order. When the item is a Map, this report shows basic Map attributes and lists all deployments in time order. When the item is a Data Object, this report shows basic Data Object attributes and lists all deployments of the Data Object and its second-class Data Objects in time order.

Within this report you can:

  • Sort deployments on deployment time.

  • Filter deployments on deployment status.

Deployment Error Detail Report

Shows details of a specific deployment error and lists all the messages for the deployment error.

Within this report, you can:

  • Sort the error messages by message number.

  • Filter the error messages by severity.

Execution Reports

The top-level execution reports are Execution Schedule Reports and Execution Summary Reports.

From these top-level execution reports, you can accessError Table Execution Reports, Job Error Diagnostic Reports, Trace Reports, Execution Job Reports, Job File Reports, Job Start Reports, andExecution Reports.

Execution Schedule Report

This execution report shows basic attributes and displays a node-tree giving details of all Process Runs (and top-level Map Runs) in time order.

Within this report, you can:

  • Focus on details for one Process Run.

  • Expand Process Run to show activity run details.

  • Filter Process Runs on execution name, execution status and date range (for example, to display only runs with 'busy' status).

  • Use the calendar icon for date picker available to set start and end of date range.

  • Refresh report to show up-to-date execution run details.

  • When you have sufficient privileges, you can purge selected Process Run execution audit details.

Execution Summary Report

This execution report shows basic attributes and lists executed Processes (and top-level Maps) in type, name order.

Within this report, you can:

  • Sort execution runs on name, type, latest execution time, and execution status.

  • Filter Processes (and Maps) on type and execution status

Error Table Execution Report

This execution report shows details of logical errors for a given target detected during the execution of Map Runs.

Within this report, you can:

  • Sort logical errors on map type, map name, execution start time, rule type, and rule usage.

  • Filter logical errors on map name, rule type and rule usage.

  • When you have sufficient privileges, you can use the Purge Error Table to remove selected logical errors.

Trace Report

This execution report, also called the Map Run Trace Report, shows details of source and target values plus data errors detected during the execution of Map Runs.

Within this report, you can:

  • Sort files on rowkey, table name.

  • Filter diagnostic trace on execution severity and source or target.

Note:

Trace diagnostic are available when the Map Run is executed with a particular setting of the Audit Level runtime parameter. Use this trace facility only if required because it can generate a large volume of audit data.

Execution Job Report

An Execution Job Report shows detail information about the execution of either a Process Run or a Map Run.

Execution Job Report for a Process Run

When the Execution Job Report is for a Process Run, it shows basic Process Run execution details, lists execution parameters, lists activity (Map and sub-Process) details in time order, and lists error messages.

Within an Execution Job Report for a Process Run, you can:

  • Hide or show activity details to show Map Run details.

  • Refresh report to show up-to-date execution run details.

  • Abort the Process Run.

Execution Job Report for a Map Run

When the Execution Job Report is for a Map Run, it shows basic Map Run execution details, including source and target Data Objects, lists execution parameters, lists map step details in time order, lists error messages, lists logical error details, and displays the contents of the SQL Loader log file (if applicable).

Within an Execution Job Report for a Map Run, you can:

  • Hide or show map step details, including source and target Data Objects.

  • Refresh report to show up-to-date execution run details.

  • Sort logical errors on error table, map step, rule type, rule usage.

  • Abort the Map Run.

  • When your role has sufficient privileges, you can purge Error and Trace audit details for the Map Run and purge Error Table to remove selected logical errors

Job File Report

This execution report shows basic Process or Map attributes, lists log and data files associated with the Process or Map Run, and displays the contents of the selected file.

Within a Job File Report, you can:

  • Sort files on file type, creation time.

  • View the contents of any selected file.

Job Start Report

This execution report shows Process or executable Map identification properties, including latest deployment and latest execution dates, lists all execution parameters for the Process or executable Map as specified by the latest deployment, and assign parameter default values from the latest deployment specification.

Within a Job Start Report, you can:

  • Sort execution parameters on name, category.

  • Change values of any input parameter where permitted.

  • Change the default Execution Name as necessary.

  • Reset all parameter settings to their default values.

  • Apply basic validation to parameter values.

  • Start the Process or Map Run, which means it is scheduled for execution immediately.

  • Navigate to the Deployment Report for latest deployment details of Process or Map.

  • Navigate to the Execution Run Report for latest execution of current Process or Map.

Execution Report

An execution report (sometimes called an Execution Detail Report) shows all of the execution run details of a given Process, a given Map, or all of the Map Runs for which a given Data Object is a source or target.

When the Execution Report is for a Process, the report shows basic Process or Map attributes and lists the Process or Map Runs in time order.

Within an Execution Report, you can:

  • Sort the Process or Map Runs on execution start time.

  • Hide or show a Process or Map Run to show activity run details.

  • Filter Process or Map Runs on execution status and execution severity.

Job Error Diagnostic Report

This execution report (sometimes also referred to as the Run Error Diagnostic Report) shows basic details of runtime error, shows target details, and lists source and target column details, where possible. Note that some column values are displayed only when your role has appropriate privilege.

Within this report, you can sort column details on source/target category, source/target name, rowkey, and column name.

Management Reports

The top-level management report is the Service Node Report. From this report you can open a Location Validation Report.

Service Node Report

This management report displays and allows you to manage service node information for the RAC system. Specifically, it performs the following functions:

  • shows the basic attributes

  • lists details and status of all service nodes currently used in the RAC system, generated from the underlying system tables

  • lists service nodes available to the RAC system which are currently not in use

  • shows the net service name to be used to access the runtime repository

Within a Service Node Report, you can:

  • Sort service nodes on instance number, instance name, runtime version.

  • Update an instance number when the node is not enabled or active.

  • Set or unset an enabled setting. (Note that you can never change an active setting as it is maintained by the RAC system.)

  • Remove selected service nodes that are not enabled or active from being used by the RAC system.

  • Add a node to the service, from the list of available nodes.

  • Set the runtime repository net service name.

  • Refresh report to show up-to-date service node details.

(Note that you can add, remove or update node details only if you have sufficient privilege.)

Location Validation Report

This management report shows basic Location attributes, current Control Center connection details, and current Location connection details.

Within a Location Validation Report, you can:

  • Test the Location connection

  • Update Location connection details

Common Repository Browser Tasks

The following scenarios are examples of some typical actions performed by a user of the Repository Browser:

Identifying Recently-Run Processes

  1. Open the Execution Schedule Report to see the latest Processes runs.

  2. Filter the displayed information by using execution name, execution status and date range, as required.

  3. Note any Process runs which are reported as having errors or not having completed.

  4. Expand the tree structure for any Process run identified in Step 3 to see details of its activities (that is, any of its sub-processes and maps).

Identifying Why a Process Run Failed

  1. Open the Execution Schedule Report and note the Process run which is marked as having errors.

  2. Click the Run Execution Report link which opens a Execution Report that provides details of the Process run.

  3. Note any Map runs which are reported as having errors or not having completed.

  4. Click the Run Execution Report link which opens a Execution Report that provides details of any Map run identified in Step 3.

  5. For any process-level or map-level error messages, click the Run Error Diagnostic Report link which opens a Job Error Diagnostic Report that displays more details of the error, including source data values.

Comparing Process Runs

  1. Open the Execution Summary Report to see list of all Processes.

  2. Click the Process name to see its Execution Report.

  3. Compare the results of previous runs, using hide/show feature to reveal further details as required.

  4. To see details of all of the activities of a Process, click the Run Execution Report link against any Process run which opens a Execution Report for that Process.

Discovering Why a Map Run Gave Unexpected Results

  1. Open the Execution Schedule Report and note the Process Run which contains the required Map Run.

  2. Click the Run Execution Report link which opens a Execution Report that provides details of the Process Run.

  3. Click the Run Execution Report link which opens a Execution Report that provides details of the Map Run.

  4. If the Map Run had Audit Level runtime parameter set to Complete, select the Trace tab link to see its Trace Report.

  5. Filter trace lines by error and source or target as required, and note any unexpected source or target actions.

  6. For error messages, click the Run Error Diagnostic Report link which opens a Job Error Diagnostic Report that displays more details of the error, including source data values.

  7. Click Purge Error and Trace Lines to remove all details or errors and trace for this Map Run, if they are no longer required.

    If purging, a confirmation screen will be shown, requesting that the action be confirmed.

Identifying Recently-Made Deployments

  1. Open the Deployment Schedule Report to see the latest deployments.

  2. Filter the displayed information by using date range, as required.

    Note any deployments which are reported as having errors or not having completed.

  3. Expand the tree structure for any deployment to see details of its components (that is, units and deployed objects).

  4. For error messages, click the Deployment Error Detail Report link to display the related Deployment Error Detail Report.

Identifying the Data Objects that are Deployed to a Specific Location

  1. Open the Locations Report to see the registered Locations.

  2. Click the Location name link to see its Object Summary Report.

  3. Filter the displayed information by using object type and object status, as required.

  4. Click the Name link for a Data Object to see its Deployment Report.

    Details are shown for all deployments of this Data Object and its second-class Data Objects.

Identifying the Map Runs that Use a Specific Deployed Data Object

  1. Open the Object Summary Report to see list of all deployed objects.

  2. Filter the information shown by using object type and object status as required.

  3. Click the Name link for a data object to see its Deployment Report.

  4. Select the Execution Report tab to display an Execution Report, which is a summary of how and when the data object was used in a Map Run.

  5. Click the related Run Execution Report link to display an Execution Report, which shows details of any Map Run.

Discovering the Default Deployment-Time Settings of a Deployed Process

  1. Open the Object Summary Report to see all deployed Processes.

  2. Click the Process Name link to see its Deployment Report.

  3. Select the Start Report tab for the given Process to display a Job Start Report for the Process.

    The execution parameters have the default deployment-time settings.

  4. Change any of the input parameter values, as required.

  5. Click Start to execute the new Process Run.

Rerunning a Process

  1. Open the Execution Schedule Report to see list of all Process Runs.

  2. Click the Run Execution Report link to display the Execution Report for the given Process Run.

  3. Click the appropriate related link to display the Job Start Report for the given Process.

    The execution parameters have the default deployment-time settings.

  4. Change any of the input parameter values, as required.

  5. Click Start to execute a new Process Run.

Monitoring a Process Run

  1. Open the Execution Schedule Report to see the executing Process Runs.

  2. If necessary, use the Execution Status filter to display only currently executing Process Runs.

  3. Click Refresh as required, to follow the progress of the Process Runs.

  4. Click the Run Execution Report link to display the Execution Report, which shows the details of a given Process Run.

  5. Click Refresh as required, to follow the progress of the Process Run.

  6. For Process Runs known to the Workflow system, click the Related information link to switch across to the Oracle Workflow Monitor and follow its progress in a graphical display. Use the browser's Back button to return to the current report page.

Aborting a Process Run

  1. Open the Execution Schedule Report to see the executing Process Runs.

  2. Click the Run Execution Report link to display the Execution Report, which shows details of a given Process Run.

  3. Click Stop to abort the given Process Run.

  4. Click Refresh as required, to follow the progress of the Process Run as its execution is terminated.

Removing the Execution Audit Details for a Process

  1. Open the Execution Schedule Report to see the latest Processes Runs.

  2. Filter the displayed information by using execution name.

  3. Select all the executions which are to be removed, and click Purge Selected Audit Details.

    A confirmation screen is shown, requesting you to confirm the action.

Removing Old Deployment Audit details

  1. Open the Deployment Schedule Report to see the latest deployments.

  2. Filter the displayed information by using date range.

  3. Select all the deployments which are to be removed, and click the Purge Selected Audit Details.

    A confirmation screen is shown, requesting you to confirm the action.

Viewing Error Tables Created as a Result of Data Auditor Execution

  1. Ensure that you grant privileges to the Repository Browser on the error table.

    See "Granting Privileges on Error Tables".

  2. Open the Execution Summary Report or Execution Schedule Report to see a list of all the Processes.

  3. Click the link in the Related Information column corresponding to the process flow that contained the data auditor to display the Execution Job Report for the process flow.

  4. Click the link in the Related Information column corresponding to the data auditor activity to display the Execution Job Report for the activity.

  5. Data that violated the data auditor constraints is listed in the Logical Errors table. Click on the link in the Error Table column to display the Execution Report for the error table.

If you have sufficient privileges, you can use the Execution Report for an error table to purge data from that error table.

Unregistering a Location

  1. Open the Locations Report to see the registered Locations.

  2. Select the Location which is to be unregistered, and click Unregister Selected Locations.

    A confirmation screen is shown, requesting you to confirm the action.

Updating Location Connection Details for a Changed Database Environment

  1. Open the Locations Report to see the Locations.

  2. Select the Location which is to be validated, and click the Validation link.

    The Location Validation Report will be displayed, showing the connection details of the Location and the Control Center

  3. Change the service description values, as necessary, and click Update Details.

  4. Click Test Connection to validate the current connection settings for the Location.

    Note that the results of Location connection tests are not maintained beyond the current session.

Updating Service Node Details in a Changing RAC Environment

  1. Open the Service Node Report to see the settings which currently describe the RAC system.

  2. Update details and usage of the Service Nodes, then click Update Node Details for the requested changes to be made.

  3. Add or Remove Service Nodes, as required.

  4. Click Refresh to see the current settings of the RAC system.

  5. Set the Net Service Name by which the Control Center may be accessed, as necessary.