Refer to My Oracle Support article Oracle Warehouse Builder is part of the standard installation on all hosts running Oracle Database 11g Release 2. Oracle Warehouse Builder It is included in Oracle Database Skip Headers. Copy the Javadoc to any appropriate location for convenient reference. Note: Check My Oracle Support article Do not apply additional patches unless they have been tested with Oracle LSH and listed in article See "Finding More Information".
Note: Oracle recommends taking a full backup at this point. Note: If a new Oracle Database patch set for 11gR2 is released in future, the article number If the article applies to a newer release, it should display the new article number for the Note: Be sure to install the Oracle Examples, which are included in the media pack and include Oracle Text. Note: Oracle recommends taking a full backup after the upgrade.
Edit init. You can upgrade an Oracle Warehouse Builder Release On the Database Information page, enter the host name, port number, and the service name where Oracle Warehouse Builder is installed. On the Choose Upgrade Operation page, select Export entire repository to a file.
For an Oracle Warehouse Builder Release Log File: the name of the export operation log file that stores status and statistical information. At the end of the export process, a status message appears. The export operation creates the file. On the Database Information page, enter the host name, port number, and the service name where Oracle Warehouse Builder Repository is installed. Click Next. On the Choose Upgrade Operation page, select Import entire repository from file.
On the File Information page, enter or browse to find the name of the files used when exporting the repository. When importing an Oracle Warehouse Builder Release Oracle Warehouse Builder provides the utility to upgrade the entire repository from Release After the upgrade, you should use the Repository browser to update all locations, and then run the deployed objects, and mappings. For Repository upgrade from Release This warning message is not displayed every time, such as if you have both The process of migrating the repository to a different Oracle Database instance involves the export of the existing repository to a file, and subsequent import of information from that file into a new repository on the other Oracle Database instance.
This process is virtually identical to upgrading from an Oracle Warehouse Builder Release The main differences are:. Before the import, you must create users on the target instance with the same names as Oracle Warehouse Builder users on the original instance. At the time of importing, you must provide the credentials of a remote Oracle Database instance where the export files reside.
This MDL zip archive includes information about all the workspaces in the repository, with each workspace stored as a separate file. Before importing the repository, in the target Oracle Database instance that contains the migrated repository, create the same users who had access to the original repository. You must do this to ensure that the security information is correctly imported.
However, you must register these users as Oracle Warehouse Builder users; the upgrade process handles this automatically. In step 6 , you are entering the credential of the source remote database, which contains the repository MDL and log files. The locations in your Oracle Warehouse Builder repository must also be upgraded for compatibility with Oracle Warehouse Builder There are two ways to perform this upgrade:.
Use the script provided with Oracle Warehouse Builder Release Oracle recommends using the provided scripts. Use the Repository Browser Locations Report to perform the upgrades one at a time. This procedure is as effective as using the script, but requires more effort. Alternatively, you can also un-register and re-register all locations. However, in this case you must also redeploy all your mappings to affected locations; therefore, this procedure is not recommended.
You can also use Locations Reports from the Repository Browser to perform the locations upgrade process as follows. Under Connection details, under Location Status, because the status is Unknown, enter the password and click Get Status. Design-time objects in your projects are automatically modified during the upgrade process to be compatible with Oracle Warehouse Builder Release This section lists the changes that are made.
Changes to Oracle Warehouse Builder Release When you move a design from Oracle Warehouse Builder Release Mapping Table Function Operators: The mapping operators for table functions are upgraded to have only one input group and one output group. Mapping Key Lookup Operators: The mapping operators for key lookups are upgraded to the new lookup operator.
Business Presentation Modules: Business presentation modules and their contents are discarded. Changes to Oracle Warehouse Builder Release 9. When you move a design from Oracle Warehouse Builder Release 9. Control Centers and Locations: After an upgrade, there is no association between the locations and the control centers that they reference.
You must review the control center details using the Edit Control Center dialog box and select the locations associated with this control center. Locations and Control Center Connections: Locations and Control Center connections are moved out of the projects that own them so that they can be shared across the entire workspace. If the view recompilation has not been performed, this statement returns no rows. The following steps recompile the views in the database. Run the pre-check script so named because it was initially released in CPUJan , which reports the maximum number of views and objects that may be recompiled:.
The purpose of this step is to help you determine whether view recompilation should be done at the same time as the PSU install, or scheduled later. If the database is not in a RAC environment, perform this step and skip the next step.
If the database is in a RAC environment, go to the next step. Run the view recompilation script. If the database is in a RAC environment, run the view recompilation script as follows.
Stop all instances except the one where the view recompilation is being executed. Check the log file for any errors. If any invalid objects were reported, run the utlrp. Then, manually recompile any invalid objects. For example:. These instructions are for a database that is created or upgraded after the installation of PSU You must execute the steps in for any new database only if it was created by any of the following methods:.
Using a script that was created by DBCA that creates a database from a sample database. Upgraded databases require that you perform the steps in if these steps have not previously been performed; otherwise, no post-installation steps need to be performed.
If this is not the case, you must execute the steps in against the database before deinstalling the PSU. Shut down all instances and listeners associated with the Oracle home that you are updating.
Run the OPatch utility specifying the rollback argument as follows. Start all database instances running from the Oracle home. Follow these steps for each node in the cluster, one node at a time:. Shut down the instance on the node. Start the instance on the node. Depending on the type of home, enter the following commands or command. For ASM homes:. Follow the instructions listed in Section only on the node for which the steps in were executed during the patch application.
All other instances can be started and accessed as usual while you are executing the deinstallation steps. Other known issues are as follows.
The following ignorable errors may be encountered while running the catbundle. The view recompilation pre-check script returns different results during subsequent runs such as after the first time you ran it. The results the maximum number of views and objects that may be recompiled may be more or less than reported in the previous running of the script.
This is expected behavior, and is not a problem. If the view recompilation script has already been run, a message is displayed indicating that the script has already been applied. This is not a problem, because as the instructions note, you do not need to run the script if it has already been run. On HP-UX systems, the following ignorable warnings may be encountered during the relinking of the oracle binary:. The inventory list of patches for PSU This situation can result in the following issues that do not require any action on your part:.
If you install PSU
0コメント