| Oracle® Warehouse Builder User's Guide 10g Release 2 (10.2.0.2) Part Number B28223-05 |
|
|
View PDF |
| Oracle® Warehouse Builder User's Guide 10g Release 2 (10.2.0.2) Part Number B28223-05 |
|
|
View PDF |
Auditing deployment and execution information can provide valuable insight into how your target is being loaded and what you can do to further optimize mapping and process flow settings and parameters. Also it can give you immediate feedback on deployment information to make you aware of the deployment history of an object. Auditing and deployment information is available to you using Oracle Warehouse Builder Repository Browser.
This section provides information:
The Oracle Warehouse Builder Repository Browser is a browser-based tool that generates reports data stored in Oracle Warehouse Builder repositories. Using the Repository Browser, you can view:
Detailed information about the design of a repository. Reports are generated from data stored in the Warehouse Builder repositories.
Reports that provide access to both high-level and detailed ETL runtime information. This information includes the following:
Timings for each mapping and process flows
Details of activities for each process flow
Error details
Deployment information to manage separate target environments
As an alternative to using the Repository Browser, you can access the same information through the Warehouse Builder public views. Launch a SQL*Plus session and query the public views. Refer to the Oracle Warehouse Builder API and Scripting Reference for a list of public views.
Audit reports provide information about deployment and ETL jobs. Each time you deploy an object or start a job, the details are stored in the repository. You can access this information in these 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. The Repository Browser Listener must be running.
To use the Repository Browser:
From the Design Center Tools menu, choose Repository Browser.
On the connection page, log in with your Warehouse Builder user name and password.
Choose Control Center Reports.
You can also open the browser when the Design Center is closed.
Opening the Repository Browser is a multistep process:
Before you can open the Repository Browser, the Repository Browser Listener must be started as described in Starting the Repository Browser Listener.
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.
The Repository Browser opens to the Login page where you log in to a repository as described in Logging in to a Repository.
Note:
In order 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 repository you want to browse. When you are not the owner of the repository, contact your database administrator who can give you this privilege.Before you can open the Repository Browser, the Repository Browser Listener must be started.
Starting the Repository Browser Listener
From the Start menu, select Programs, then the name of the Oracle home directory into which you installed Warehouse Builder, then Warehouse Builder, then Administration, and then Start OWB Browser Listener.
Stopping the Repository Browser Listener
From the Start menu, select Programs, then the name of the Oracle home directory into which you installed Warehouse Builder, then Warehouse Builder, then Administration, and then Stop OWB Browser Listener.
Before you can start the Repository Browser, the Repository Browser Listener must be started as described in Starting the Repository Browser Listener. 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 name of the Oracle home directory into which you installed Warehouse Builder, then Warehouse Builder, and then Repository Browser.
From the menu of the Design Center of the Warehouse Builder, select Tools, and then Repository Browser.
From within any web browser, type in the location of the Repository Connection page.
You can identify this location, by saving it after starting the Repository Browser using another method of starting the Repository Browser, or you can ask your Oracle Builder Administrator for the location.
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.
To login to a repository, specify the connection information for the repository you would like to access. If you do not know the connection information, contact your Warehouse Builder database administrator.
Specify the first Repository Browser page that you want to open:
When you want start by browsing through the Repository using the Repository Navigator page, select Design Repository.
When you want to start by viewing Repository Browser Control Center reports using the Control Center Reports page, select Control Center.
When you start the Repository Browser select Design Center as described in Starting the Repository Browser, the Repository Browser opens to the Repository Navigator page. From this page you can discover information about the design of Oracle Warehouse Builder Repositories such as:
You use the Repository Navigator page to search the metadata of a repository and to access metadata main properties, lineage, impact analysis, and list of related reports and Control Center reports for the repository.
Search
Search by object type, or name, or by both.
To search by object type, select the type of object for which you want to search in 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(s) of the name in which case, the search result is a list of objects whose names begin with those characters.
Click Go to start your search.
The Repository Browser displays the results of the search in a new page called the Repository Search Results page. You can also search for the new objects from a Repository Search Results page.
All
A navigator tree for the repository.
The use of the columns is described in the following table.
| 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 sign (+) or minus sin (-) 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. |
| Report | 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 Analysis page for the related item. |
Refresh
Click to refresh your view of the repository.
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.
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:
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:
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:
Implementation Reports can be run on Dimensions and Cubes. They provide information on how physical objects are used to implement logical objects.
Lineage and Impact Analysis Reports and Diagrams are available for Cubes, Dimensions, Materialized Views, Tables, Views, and Records.
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.
Lineage and Impact Analysis Diagrams
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.
An Impact Analysis Diagram is identical except it shows all objects and transformations that might be affected by a change to the subject. The subject is displayed on the left side of the screen.
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.
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 Analysis pages by clicking on the corresponding link on the left side of the page.
The Object Lineage page displays information about how object that you selected in the Repository Navigator is used.
From this page you can go to the Object Properties, Object Reports, or Object Impact Analysis pages by clicking on the corresponding link on the left side of the page.
The Object Impact Analysis 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.
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.
The Control Center 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:
Deployment Schedule Reports that show basic Warehouse attributes and display a node-tree giving details of all deployments in time order.
Object Summary Reports that show basic Warehouse attributes and list deployed objects (Processes, Maps and Data Objects) in type/name order with details of their latest deployment.
Locations Reports that show all Locations into which objects have been deployed.
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.
Execution Reports
Execution Schedule Reports that show basic Warehouse attributes and display a node-tree giving details of all Process Runs (and top-level Map Runs) in time order.
Execution Summary Reports that show basic Warehouse attributes and lists executed Processes (and top-level Maps) in type/name order.
From these top-level execution reports, you can access other reports that allow you to:
Monitor jobs using Execution Reports (sometimes called Execution Detail Reports) that show the execution job details of a given Process Run or Map Run; Execution Job Reports that show details of logical errors for a given target detected during the execution of Map Runs; and Job Error Diagnostic Reports that show basic details of runtime errors and target details, and, when possible, list source and target column details.
Display diagnostics using Error Table Execution Reports that show details of logical errors for a given target detected during the execution of Map Run; Trace Reports that show details of source and target values plus data errors detected during the execution of Map Runs; and Job File Reports that show basic Process or Map attributes, list log and data files associated with the Process or Map Run, and display the contents of the selected file.
Rerun jobs using Job Start Reports that show Process or Map identification properties (including latest deployment and latest execution dates), list all execution parameters for the Process as specified by the latest deployment, and assign parameter default values from the latest deployment specification.
Management Reports
The main Repository Browser management report is the Service Node Report that displays and enables 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.
Top-level deployment reports are Deployment Schedule Reports, Object Summary Reports, andLocations Reports. 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.
The Deployment Schedule report is a top-level Control Center report that shows basic Warehouse attributes and displays a node-tree giving details of all deployments in time order.
You 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 a 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. |
| Related Information | Other related information including a link to a related Deployment Error Detail Report, if appropriate. |
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.
An Object Summary Report shows basic Warehouse 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.
This one 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.
Shows details of a specific deployment error and lists all of the messages for the deployment error.
Within this report, you can:
Sort the error messages by message number.
Filter the error messages by severity.
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.
This execution report shows basic Warehouse 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.
This execution report shows basic Warehouse 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, execution status.
Filter Processes (and Maps) on type and execution status
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, 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.
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 one when the Map Run is executed with a particular setting of the Audit Level runtime parameter. Use this trace facility with care since it can generate a large volume of audit data.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
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.
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.
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.
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, column name.
The top-level management report is the Service Node Report. From this report you can open a Location Validation Report.
This management report display and enables you to manage service node information for the RAC system. Specifically, it shows basic Warehouse 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, and 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.)
This management report is 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
The following scenarios are examples of some typical actions performed by a user of the Repository Browser:
Identifying the Data Objects that are Deployed to a Specific Location
Identifying the Data Objects that are Deployed to a Specific Location
Identifying the Map Runs that Use a Specific Deployed Data Object
Discovering the Default Deployment-Time Settings of a Deployed Process
Updating Location Connection Details for a Changed Database Environment
Open the Execution Schedule Report to see the latest Processes runs.
Filter the information shown by using execution name, execution status and date range, as required.
Note any Process runs which are reported as having errors or not having completed.
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).
Open the Execution Schedule Report and note the Process run which is marked as having errors.
Click the Run Execution Report link which opens a Execution Report that provides details of the Process run.
Note any Map runs which are reported as having errors or not having completed.
Click the Run Execution Report link which opens a Execution Report that provides details of any Map run identified in Step 3.
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.
Open the Execution Summary Report to see list of all Processes.
Click the Process name to see its Execution Report.
Compare the results of previous runs, using hide/show feature to reveal further details as required.
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.
Open the Execution Schedule Report and note the Process Run which contains the required Map Run.
Click the Run Execution Report link which opens a Execution Report that provides details of the Process Run.
Click the Run Execution Report link which opens a Execution Report that provides details of the Map Run.
If the Map Run had Audit Level runtime parameter set to Complete, select the Trace tab link to see its Trace Report.
Filter trace lines by error and source or target as required, and note any unexpected source or target actions.
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.
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
Open the Deployment Schedule Report to see the latest deployments.
Filter the information shown by using date range, as required.
Note any deployments which are reported as having errors or not having completed.
Expand the tree structure for any deployment to see details of its components (that is, units and deployed objects).
For error messages, click the Deployment Error Detail Report link to display the related Deployment Error Detail Report.
Open the Locations Report to see the registered Locations.
Click the Location name link to see its Object Summary Report.
Filter the information shown by using object type and object status as required.
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.
Open the Object Summary Report to see list of all deployed objects.
Filter the information shown by using object type and object status as required.
Click the Name link for a data object to see its Deployment Report.
Select the Execution Report tab to display an Execution Report which is a a summary of how and when the data object was used in a Map Run.
Click the related Run Execution Report link to display an Execution Report which shows details of any Map Run.
Open the Object Summary Report to see all deployed Processes.
Click the Process Name link to see its Deployment Report.
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
Change any of the input parameter values, as required
Click Start to execute the new Process Run.
Open the Execution Schedule Report to see list of all Process Runs.
Click the Run Execution Report link to display the Execution Report for the given Process Run.
Click the appropriate related link to display the Job Start Report for the given Process.
The execution parameters have the default deployment-time settings.
Change any of the input parameter values, as required.
Click Start to execute a new Process Run.
Open the Execution Schedule Report to see the executing Process Runs.
If necessary, use the Execution Status filter to display only currently executing Process Runs.
Click Refresh as required, to follow the progress of the Process Runs.
Click the Run Execution Report link to display the Execution Report which shows the details of a given Process Run.
Click Refresh as required, to follow the progress of the Process Run.
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.
Open the Execution Schedule Report to see the executing Process Runs.
Click the Run Execution Report link to display the Execution Report that shows details of a given Process Run.
Click Stop to abort the given Process Run.
Click Refresh as required, to follow the progress of the Process Run as its execution is terminated.
Open the Execution Schedule Report to see the latest Processes Runs.
Filter the information shown by using execution name.
Select all the executions which are to be removed, and click Purge Selected Audit Details.
A confirmation screen will be shown, requesting that the action be confirmed.
Open the Deployment Schedule Report to see the latest deployments.
Filter the information shown by using date range.
Select all the deployments which are to be removed, and click the Purge Selected Audit Details.
A confirmation screen will be shown, requesting that the action be confirmed.
Open the Locations Report to see the registered Locations.
Select the Location which is to be unregistered, and click Unregister Selected Locations.
A confirmation screen will be shown, requesting that the action be confirmed.
Open the Locations Report to see the Locations.
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
Change the service description values, as necessary, and click Update Details.
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,
Open the Service Node Report to see the settings which currently describe the RAC system.
Update details and usage of the Service Nodes, then click Update Node Details for the requested changes to be made.
Add or Remove Service Nodes, as required.
Click Refresh to see the current settings of the RAC system.
Set the Net Service Name by which the Control Center may be accessed, as necessary.
|
 Copyright © 2000, 2009, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
