This tutorial shows you how to re-deploy the migrated dimensions and cube.
Approximately 30 minutes
This tutorial covers the following topics:
|
Overview | |
|
Prerequisites | |
|
Specify OLAP Descriptors for Dimensions | |
|
||
|
Re-Deploy the Dimensions and the Cube Using the Control Center Manager | |
|
Post Migration - View the Data | |
|
Summary | |
Place the cursor over this icon to load and view all
the screenshots for this tutorial. (Caution: This action loads all screenshots
simultaneously, so response time may be slow depending on your Internet connection.)
Note: Alternatively, you can place the cursor over each individual icon in the following steps to load and view only the screenshot associated with that step.
In tutorial "Migrating Runtime Metadata to OWB 10gR2", you noticed that in Control Center Manager all the objects show as successfully deployed except for the dimensions and the cube. This is because the model behind dimensions and cube has significantly changed between 10gR1 and 10gR2 releases of OWB.
After migration, the 10gR1 cube design is migrated as a cube and a table. For example the BSALES cube after migration to OWB 10gR2 adds a BSALES table along with the BSALES cube. Similarly, a dimension becomes a dimension and a table. At runtime, a deployed cube or a dimension in an OWB 10gR1 repository after migration to the OWB 10gR2 repository becomes a deployed table.
In the Control Center Manager, the tables representing the dimensions and the cube are shown as "deployed" while the dimensions and the cube itself are shown as "New" or "Not Deployed."
In this tutorial, you will focus on re-deploying the migrated dimensions and cubes.
Before starting this tutorial, you should:
| 1. |
Have completed tutorial "Setting Up the Environment for Migration" |
| 2. |
Have completed tutorial "Migrating Design Metadata to OWB 10gR2" |
| 3. | Have completed tutorial "Migrating Runtime Metadata to OWB 10gR2" |
In this topic, you will specify OLAP descriptors for the migrated dimensions. Note that this step is not an essential step for migration. This is being done only to configure the dimensions for the OLAP catalog and the relational catalog. When you specify the OLAP descriptors such as the Long description attribute or the Time span attribute for the TIME dimension, then scripts are generated for populating the CWM2 OLAP metadata catalog.
To specify OLAP descriptors for all the dimensions, perform the following steps:
|
1. |
Assuming that you are already logged in the Design center, expand OWB_DEMO > Databases > Oracle > TGT > Dimensions. Right-click BCHANNEL and select Open Editor.
The Data Object Editor displays.
|
||||||||||||
|
2. |
In the Dimension Details panel of the Data Object Editor, click the Attributes tab.
|
||||||||||||
| 3. |
In the Attributes tabbed page, for the LONG_DESC attribute, select Long description from the Descriptor drop-down list.
From the Diagram menu, select Close Window to exit the Data Object Editor.
|
||||||||||||
| 4. |
Similarly, you will specify the Long description descriptor for one of the attributes of each dimension. In OWB_DEMO > Databases > Oracle > TGT > Dimensions, right-click BGEOGRAPHY and select Open Editor. In the Data Object Editor, click the Attributes tab. For the LONG_DESC attribute, select Long description from the Descriptor drop-down list.
From the Diagram menu, select Close Window to exit the Data Object Editor.
|
||||||||||||
| 5. |
In OWB_DEMO > Databases > Oracle > TGT > Dimensions, right-click BPRODUCT and select Open Editor. In the Data Object Editor, click the Attributes tab. For the LONG_DESC attribute, select Long description from the Descriptor drop-down list.
From the Diagram menu, select Close Window to exit the Data Object Editor.
|
||||||||||||
| 6. |
For the BT_TIME time dimension, specify a few extra descriptors. In OWB_DEMO > Databases > Oracle > TGT > Dimensions, right-click BT_TIME and select Open Editor. In the Data Object Editor, click the Attributes tab. Specify the following descriptors to the attributes as shown below:
From the Diagram menu, select Close Window to exit the Data Object Editor. In the Design Center, from the Design menu, select Save All. In Warehouse Builder warning dialog box , click Yes to save the changes. |
||||||||||||
In this topic you change the deployment option of the dimensions and the cube from "Deploy Data Objects only" to "Deploy to Catalog only".
Oracle Warehouse Builder provides four deployment options for dimensional objects:
|
Deploy All: For a relational or ROLAP implementation, the dimensional object is deployed to the database and a CWM definition to the OLAP catalog. For a MOLAP implementation, the dimensional object is deployed to the analytic workspace. |
|
|
Deploy Data Objects Only: This is the default deployment option. This option deploys the dimensional object only to the database. You can select this option only for dimensional objects that use a relational implementation. This option is equivalent to the code generation of OWB 10gR1. If you deploy the objects using this option, you will not be able to view the loaded data through the Data Viewer because the Data Viewer uses OLAP catalog metadata to show data. |
|
|
Deploy to Catalog Only: This option deploys the CWM definition to the OLAP catalog only. Use this option if you want applications such as BI Beans or Discoverer for OLAP to access the dimensional object data after you deploy data only. Using this option, you can view the loaded data
in the dimensions and the cube in the Data Viewer. |
|
|
Deploy Aggregation: This deploys the aggregations defined on the cube measures. This option is available only for cubes. | |
Note: This step is not an essential step for successful migration.
To set the deployment option for the dimensions and the cube, perform the following steps:
| 1. |
In OWB_DEMO > Databases > Oracle > TGT > Dimensions, right-click the appropriate dimension and select Configure from the menu. In the Configuration Properties dialog box, set the deployment options
property to Deploy to Catalog only, as shown in the screenshot
for the BCHANNEL dimension.
Click OK. Similarly, set the deployment option for the other three dimensions: BPRODUCT, BGEOGRAPHY, and BT_TIME.
|
| 2. |
You will set the deployment option for the cube also. In OWB_DEMO > Databases > Oracle > TGT > Cubes, right-click BSALES and select Configure from the menu. In the Configuration Properties dialog box, set the deployment options property to Deploy to Catalog only, as shown in the screenshot.
Click OK. In the Design Center, from the Design menu, select Save All.
In Warehouse Builder warning dialog box , click Yes to save the
changes. |
To deploy the dimensions and cube, perform the following steps:
| 1. |
In the Tools menu, select Control Center Manager.
Note: If you exited from the Design Center and logged in again for deployment, you may have to enter the password to access the migrated control center, OWB_RT. In the Connection information dialog box, enter rta_101 as the password for the user rta_101.Click OK.
The Control Center Manager displays.
|
| 2. |
Expand LOC_TGT > TGT > Dimensions. In the Object Details panel, for all the dimensions, the Design Status is set to New and Deploy Status is set to Not Deployed.
Note: You will get the details of past deployments jobs you performed, in the Control Center Jobs panel. You may limit this listing of deployment jobs by number of days and number of items. Change the Number of Days to 1 to and Number of Items to 2 in order to show only list only 2 deployment jobs happened in past one day.
|
| 3. |
Click Default Actions. The Deploy Action changes from None to Create. To deploy, select Deploy > To Control Center from the File menu, or click the Deploy button.
The Edit Oracle Database Location dialog box displays. This is to register the target schema. Enter owbtgt as the password and click Test Connection. If the connection is successful, proceed to the next step. If not, check the password. Click OK.
Note that in the Control Center Jobs panel, the deployment status changes from "generate" to "run" to "completed successfully." |
| 4. |
All the dimensions are deployed successfully as shown in the screenshot.
Note: If the deployment is not successful and you get errors, consider dropping the dimensions first and then deploy again. To drop the dimensions, select Drop from the Deploy Action drop-down list and click Deploy. After the dimensions are reported as successfully dropped, select Create from the Deploy Action drop-down list and click Deploy.
|
| 5. |
To deploy the cube, BSALES, expand LOC_TGT > TGT > Cubes. In the Object Details panel, the Design Status is set to New and Deploy Status is set to Not Deployed. Click Default Actions. The Deploy Action changes from None to Create.
Click Deploy to deploy the cube.
|
| 6. |
Note that in the Control Center Jobs panel, the deployment status changes from "generate" to "run" to "completed successfully." The cube BSALES is deployed successfully.
|
Now you will view the data in the migrated dimensions and cube. In an ideal migration scenario, dimensions and the cube will already be containing data and only incremental data will need to be added by executing the process flow on definite intervals.
| 1. |
Expand PROC_LOC > PROC_MOD > PFP and select LOAD_WH. The process flow is shown as successfully deployed. You do not need to re-deploy the process flow in this scenario. Also, you do not need to execute the process flow to upload the data into the dimensions and the cube because you have already uploaded the data prior to migration. Note: In case, you did not execute the process flow to upload data prior to migration or you want to refresh data in the dimensions and the cube and hence want to execute the process flow, perform the following steps: To execute the process flow, from File menu, select Start or click the Start button, as highlighted in the screenshot. During the execution of the process flow, you will need to enter owf_mgr schema password to register the Oracle Workflow location.
Warning: During the execution of the process flow, if you get an error, "PLS-00201: identifier 'WB_RT_Workflow_Util_10g.Allow_Caching' must be declared", try the following workaround. Drop and re-deploy the process flow that you want to execute or if not feasible, deploy any other process flow. Deploying any other process flow will let you get around this error and you will be able to successfully execute the process flow.
|
| 2. |
Due to tightening up of the security model within OWB 10gR2, the Oracle Workflow(OWF) user has to be granted one of the database roles in order to execute a process flow. Therefore, before you drop and re-deploy the process flow (as a workaround to the error listed above), you need to register the OWF user by using the Register Warehouse Builder Users wizard from the Security > Users node in Global Explorer panel. To get access to the security node, ensure you log in to the design center as the repository owner. If not already logged in, log in to the Design Center with username/password as rep_owner/rep_owner. In the Global Explorer panel, expand the Security node. Right-click the Users node and select New. Note: You must save or revert your changes before creating a new user. To save previous changes, select Save All from the Design menu .
The Register Warehouse Builder Users Wizard is launched. Click Next on the Welcome page. On the Select DB user to register page, you can select from the available list of database users or create a new one that will be automatically registered as Warehouse Builder target user. Select owf_mgr from the Available DB Users list and click > to move it to Selected Users list.
On the Check user as target schema page, de-select the Used as target schema option. You need not make OWF user, a target user. Click Next.
On the Summary page, examine the details and click Finish. The Fix Database Default Role for Users dialog box diaplays. In the Fix Database Default Role for Users dialog box, enter sys or <your SYS password> in SYSDBA Password field in the Fix Now section.
Click OK. Notice that owf_mgr user gets added inside the Security > Users node, in the Global Explorer panel. Note: The step of registering the Oracle Workflow user, owf_mgr, is because of the new security model. This new security model means that you do not have to embed the password for the Control Center in database-links owned by the OWF user. The Control Center user is highly privileged and its password is tightly controlled. In this tutorial, you will not execute the process flow. Hence, you will not perform step 1 and 2 of this topic in the normal course of this tutorial and is only provided as extra information in case you need to execute a migrated process flow in your real migration scenario. In the next step, you will view the data in the migrated dimensions and cube. Being able to view the data in the migrated dimensions and cube proves that the migration process does not deal or tamper with actual user's data already uploaded in the Warehouse objects.
|
| 3. |
To view data in the migrated dimensions, in the Project Explorer panel, expand OWB_DEMO > Databases > Oracle > TGT > Dimensions. Right-click BPRODUCT and select Data.
In the Data viewer, you see the following data, as shown in the screenshot.
|
| 4. |
To view the cube BSALES data, in the Project Explorer panel, expand OWB_DEMO > Databases > Oracle > TGT > Cubes. Right-click BSALES and select Data.
|
In this lesson, you learned how to:
|
Re-deploy the migrated dimensions and cube | |
|
View data in the migrated dimensions and the cube | |
This tutorial concludes the task of migrating your data warehouse project implemented using OWB 10gR1 to OWB 10gR2. Now, your project is ready to utilize the many new enhancements and features the new release of Warehouse Builder brings with it.
Place the cursor over this icon
to hide all screenshots.