This is expected and does not indicate problems with your migrated data. Validate the cubes and dimensions and fix errors that may prevent you from redeploying the objects. Redeploy the objects as this is necessary for updating the audit history. In a previous release you may have created a mapping with Advanced Queues.
Only if you intend to redeploy such a mapping in this release, you must first create a separate table for each AQ with the following structure:. If you upgraded the Oracle Database for Oracle 10g and created a new database instance, you should have followed the instructions for Upgrading Oracle Workflow on a New Oracle Database Instance. Now that you have upgraded runtime metadata through the Control Center Upgrade Assistant, you can re-register the Workflow locations and redeploy the process flow modules and packages.
After redeploying mappings, update the configuration of each mapping to benefit from the new features available in the upgraded version of Warehouse Builder. If you are upgrading from release 9. You can skip this section if release 9. You can update the mapping configuration either by using the Warehouse Builder interface, or by running a script to update all the mappings in the Oracle Metabase OMB Plus scripting utility.
To update the configuration of each mapping using the Warehouse Builder interface:. In the upgraded Warehouse Builder client, right-click each mapping and select Configure. In the Configuration Properties box, expand the Sources and Targets node. Redeploy each mapping for which you changed the configuration properties in order to generate new code.
Alternatively, you can update all mappings by running the script provided for this purpose on the Oracle Technology Network. The update script is called UpdMapConfig. Download the UpdMapConfig. Change the context in OMB Plus to the correct project and module. You must run this script module by module. At the OMB Plus prompt, type source , and then the location of the script surrounded by quotation marks. Run the following commands in OMB Plus to update the mappings and commit the changes to the design repository:.
Complete the instructions in this section only if both of the following are true :. If both of these points are true, you must copy the following objects from the computer hosting the existing instance of Oracle Database to the computer hosting the new instance:.
External Directories: You must also copy all external directories from the computer hosting the existing instance of Oracle Database to the computer on which Oracle Database 10 g resides.
Make sure to re-create identical file system directories. Skip Headers. Migrating An Oracle Database Environment If your current version of Oracle Database is compatible with Warehouse Builder, you can keep the current version or optionally choose to upgrade to a higher compatible version of the database. Upgrading to Oracle Database 10 g Upgrading to Oracle9i Database Release 2 9.
Migrating a Complete Database Follow the instructions in the upgrade documentation for Oracle Database 10 g. To upgrade Oracle Workflow on a new Oracle Database instance: Run the Oracle Workflow assistant in Upgrade mode on the new database instance to upgrade the workflow schema. Register the Workflow user in the new repository. The final step is Redeploying Process Flows.
Any instructions in the Release Notes supersede the instructions in this guide. Install a new repository. Installing Optional Components Optional See Chapter 5 for instructions on installing and configuring optional components. Deinstalling Oracle Warehouse Builder Optional You have the option of deinstalling the existing components from the previous release. Exporting Target Schemas from the Existing Runtime Environment Pre-create the tablespaces in the Oracle Database 10 g environment to exactly match the tablespaces in the existing version of Oracle Database.
Copying External Directory References to the New Database Instance Complete this section if in the pre-existing Warehouse Builder environment includes external directories which are used by external tables and flat files. Rename the generated script.
Repeat steps 2 through 6 for each target schema user you intend to migrate. Repeat these instructions for each target schema you want to migrate. Registering the Users from the Previous Warehouse Builder Environment Log on to the Design Center as the repository owner that you defined when creating the new repository.
Add and register a user for each target schema you migrated into the new database. Upgrading a Design Repository Follow these instructions if you want to upgrade only a portion of an existing repository. Use the new version of Warehouse Builder to create a new repository. Import design metadata into the new repository.
Note: To upgrade, you must export and import metadata using the Metadata Loader. Warehouse Builder upgrade does not support files that were exported or imported using back end database commands.
Importing Design Metadata to Warehouse Builder 10 g Release 2 After having installed the new software, you must import and upgrade design metadata into the new version of Warehouse Builder.
Note: Warehouse Builder upgrade does not support files that were exported or imported using back end database commands. Upgrading a Runtime Repository to a Control Center In previous releases, runtime repositories were managed by the interface known as the Deployment Manager. Using the Control Center Upgrade Assistant Use the Control Center Upgrade Assistant to move audit data from a runtime repository that you created in a previous release.
Before you Begin If you recently migrated to an Oracle 10g database using the full migration option, ensure that you completed the steps for Upgrading Oracle Workflow on a New Oracle Database Instance. Supported Upgrade Scenarios Use this assistant to complete any of the scenarios illustrated in Figure Connect to the repository as the repository owner. Connecting to an Existing Runtime Repository As you use the Control Center Upgrade Assistant, the assistant prompts you to connect to a runtime repository.
This is the case for the most common upgrade scenarios including the following scenarios: Since the time you created the runtime repository, you did not upgrade the Oracle Database to a new version. Choosing An Upgrade Operation Use the upgrade operations in the following order: Select Move to transfer location registration information and audit data from the pre-existing runtime repository to the new control center.
Proceed with Upgrading Locations in the Design Repository. Move When you select the Move operation, the assistant prompts you to connect to the original runtime repository as a repository owner. Upgrade The assistant lists the locations registered in the new control center and displays whether they are valid or not.
Upgrade Operation: Location Details Use this button to check and fix locations for possible errors. Generate Use this operation to generate a Tcl script that you then must alter to update location information in the design repository. To generate a Tcl script that updates location information: Ensure that you previously imported MDL from the previous design repository to the new Warehouse Builder 10 g Release 2 Click Generate. Reviewing Selections in the Upgrade Assistant Verify your selections in the assistant before clicking Finish.
Run the Tcl script against the new design repository. On the Name page, enable the Set and Save option. Register all of the locations and provide any passwords. Updating Mapping Configuration to Benefit from New Features After redeploying mappings, update the configuration of each mapping to benefit from the new features available in the upgraded version of Warehouse Builder.
Use the following criteria to determine whether you can skip this section: If you are upgrading from release 9. To update the configuration of each mapping using the Warehouse Builder interface: In the upgraded Warehouse Builder client, right-click each mapping and select Configure. In the Sources and Targets node: Delete the contents of the Schema configuration parameters field. Delete the contents of the DB Links configuration parameters field.
To update the configuration of each mapping using a script: Download the UpdMapConfig. Connect to the new design repository. Run the script in OMB Plus. For every backward slash, enter a second backward slash to escape the first. Select Get Status to evaluate its status and view the results of various tests. For each location, the assistant checks that the password is valid and that it is the same as the registered password.
The assistant verifies that the version registered for the location is the same as the actual version. If the assistant detects any errors, then you can select Upgrade to correct the errors. Use this operation to generate a TCL script of OMB Plus commands that you can use to alter the location information stored against locations in the design repository.
Such information was not stored against locations in Warehouse Builder Also, depending on your migration path, it may have been altered as part of migration. Ensure that you previously imported MDL from the previous design repository to the new Warehouse Builder Either edit the script in the user interface and select save again.
Or edit the script in Notepad. Therefore, in the Tcl script, change the line. On the summary page, control center refers to the new control center to which you are upgrading. Runtime repository refers to the repository from which you are upgrading. When you run the script, the details for the control center and the location address are seeded into the design repository.
Each location is associated with the control center. The registration details are also added to the logical location because, beginning in Warehouse Builder In the Design Center, expand the project node, and expand the Configurations node. To view and re-deploy the migrated objects, start the Control Center Manager from the Tools menu. For security purposes, the location passwords are not saved. In the Control Center Manager, right click each location and select Register.
Enter the password and optionally test the connection. As a general rule, when migrating from the previous release to Warehouse Builder 11g, you can run migrated mappings immediately without redeploying them in the new environment. For all other jobs, however, you must take further action before running jobs for the first time.
The objects that require further action include, but are not limited to the following: dimensions and cubes, Discoverer integration, process flows, schedules, and data profiles. This section includes the following additional instructions for reusing objects you created in a previous release:.
Beginning in Warehouse Builder 11g, hierarchy versioning is available and enabled as a default for type 2 slowly changing dimensions. If you migrate a type 2 slowly changing dimension, verify that the settings are set correctly after migration. For these dimensions to behave in the same way as originally designed in a previous release, you must first deselect hierarchy versioning and then deploy the dimension.
Each level is listed together with its level attributes. With this new version of Warehouse Builder, each level except the highest has an attribute representing the parent ID. To turn off hierarchy versioning, remove the entry from Record History and leave it blank. When you migrate a target schema from Warehouse Builder 10g Release 2 To do this, you set the configuration property called Deployment Options to Deploy to Catalog Only and deploy the dimensions.
Warehouse Builder 10g Release 2 After upgrading from Warehouse Builder 10g Release 1 or prior, dimensions and cubes appear as new objects in the Control Center Manager.
New validation rules may cause errors or warnings that did not exist in your previous installation. This is expected and does not indicate problems with the migrated data. Validate the cubes and dimensions and fix errors that may prevent you from redeploying the objects.
Redeploy the objects as this is necessary for updating the audit history. In a previous release you may have created a mapping with Advanced Queues. Only if you intend to redeploy such a mapping in this release, you must first create a separate table for each AQ with the following structure:.
Re-register the workflow locations and then select one process flow package to redeploy in the new environment. Preferably, redeploy a small process flow package with a single, simple process flow. Subsequently, other process flows created in this release can run without redeployment. For process flows and schedules from release Warehouse Builder 10g Release 1 and earlier, you need redeploy each object separately in the new environment.
Complete the instructions in this section only if both of the following are true :. If both of these points are true, you must copy the following objects from the computer hosting the existing instance of Oracle Database to the computer hosting the new instance:.
External Directories: You must also copy all external directories from the computer hosting the existing instance of Oracle Database to the computer on which the new Database resides. Make sure to re-create identical file system directories. Migrating data profiles that you created in a previous release is not supported in Warehouse Builder 11 g Release 1. You must manually recreate any data profile metadata you created in a previous release.
Skip Headers. Identify and complete any changes necessary to the database environment. Any instructions in the Release Notes supersede the instructions in this guide. Otherwise, proceed to the next step. Install a new repository. Deinstalling Oracle Warehouse Builder Optional You have the option of deinstalling the existing components from the previous release.
Migrating An Oracle Database Environment If your current version of Oracle Database is compatible with Warehouse Builder, then you can keep the current version or optionally choose to upgrade to a higher compatible version of the database. Upgrading to Oracle Database 11 g The final step is "Reusing Process Flows and Schedules". Take the following precautions now, that is, prior to upgrading runtime metadata. Register the Workflow user in the new repository.
Install a new repository on Oracle Database 11 g. Installing and Enabling Optional Components Optional See Chapter 5 for instructions on installing and configuring optional components.
Installing the Warehouse Builder Software on the Client computers Repeat the instructions Installing the Warehouse Builder Software for each computer to be used as a client. Exporting Target Schemas from the Existing Runtime Environment Pre-create the tablespaces in the new Database environment to exactly match the tablespaces in the existing version of Oracle Database.
Creating the Target Schemas and Users in the New Database The steps you take here depend on the version from which you are upgrading. Copying External Directory References to the New Database Instance Complete this section if in the pre-existing Warehouse Builder environment includes external directories which are used by external tables and flat files.
Rename the generated script. Repeat steps 2 through 6 for each target schema user you intend to migrate. Repeat these instructions for each target schema you want to migrate. To export all design metadata: Copy the tcl script from the home directory of the current release into a temporary directory. Run OMB Plus using the tcl script. For Unix, type the following command on the same line: owb To import all design metadata: If you have not already done so, create a workspace and a workspace owner in the new release.
Enter the commands on the same line. For UNIX, type the following command on the same line: owb Selectively Migrating Design Metadata Follow these instructions if you want to migrate only a portion of an existing repository. Use the new version of Warehouse Builder to create a new repository. Import design metadata into the new repository. To export existing metadata into an MDL file: Use the prior version of the Warehouse Builder client to select the project, collection, or public transformation you want to export.
Importing Design Metadata to Warehouse Builder After having installed the new software, you must import and upgrade design metadata into the new version of Warehouse Builder. The Metadata Import dialog is displayed. The options available are: Create new metadata only: Adds new metadata to a repository.
In the Match By section, select Universal Identifier. Use this dialog to import the following: Additional language metadata User-defined definitions Click OK to save your selections and close the Import Advanced dialog. Click Import to import the MDL file. Upgrading Existing Control Centers or Runtime Repositories In previous releases, runtime repositories were managed by the interface known as the Deployment Manager.
Using the Control Center Upgrade Assistant Use the Control Center Upgrade Assistant to move audit data from a runtime repository or control center that you created in a previous release. Supported Upgrade Scenarios Use this assistant to complete any of the scenarios illustrated in Figure Connecting to a New Control Center Connect to the repository created in the Oracle Database when you recently installed the latest version of this product.
Connect to the repository as the repository owner. Choose a Workspace From the newly created repository, select the workspace you created during the installation process. Connecting to an Existing Runtime Repository Or Control Center As you use the Control Center Upgrade Assistant, the assistant prompts you for the connection details to the previous runtime repository or control center. The script assumes that at most one property with the given name exists.
Connect as workspaceOwner or workspaceUser with execute, deploy, and administrative privileges. For an auditId that represents a deployment job, this script expedites the job cleanly. The returnNumber and returnCode are the result values assigned to the job, and have the following values:. Connect as workspaceOwner or workspaceUser with execute, deploy, and administrative privileges, such as SYS.
In this script, userName is the name of the schema or user who has the new upgrade privileges. A deployment is a collection of deployment units, which are collections of objects deployed by the same deployment action to the same location. The auditId represents an execution job about which this script print the job details.
The script is of the form:. After the registration details are reset, you must register the passwords for all previously registered locations. These properties controls the behavior of the Control Center Service.
This password is used by the Control Center Service at startup time. In its unchanged form the script takes the three keys required to identify the executable task. The task runs in the background with the default parameters configured before deployment. Connect as workspaceOwner or workspaceUser with execute privilege. The workspace is nominated in the parameters, and should be declared as workspaceOwner.
A module name cannot be used because it is not a deployable object. You can then access the public views. A single-quote character must be replaced by a sequence of four single-quote characters ''''.
The script takes the three keys required to identify the executable task. The task runs with the default parameters configured before deployment. A Control Center Service, when available, provides access to the deployment and execution features of an Oracle Warehouse Builder repository.
When the service is invoked using this script, a monitoring job is created; it restarts the service if it fails, or if the database is brought back online.
0コメント