| Oracle® Fusion Middleware Patching Guide 11g Release 1 (11.1.1.6.0) Part Number E16793-13 |
|
|
PDF · Mobi · ePub |
| Oracle® Fusion Middleware Patching Guide 11g Release 1 (11.1.1.6.0) Part Number E16793-13 |
|
|
PDF · Mobi · ePub |
The Patch Set Assistant is used in patch set releases only to update the database schemas of Oracle Fusion Middleware components. The schemas that are valid for updating with the Patch Set Assistant must meet one of the following criteria:
The schema was created in an 11g release using the Repository Creation Utility (RCU).
The schema was upgraded from 10g to 11g using the Upgrade Assistant.
Note:
The Patch Set Assistant does not upgrade schemas that are in customer databases, which is any database that has not used the Upgrade Assistant (UA), Repository Creation Utility (RCU), or Patch Set Assistant (PSA).
If you need to upgrade a schema in such a database, refer to Section 4.2, "Special Instructions for Standalone Oracle Portal Repository Schemas".
The Patch Set Assistant updates 11g Release 1 schema versions starting at 11.1.1.2.0 to version 11.1.1.6.0. See Table 4-1 for specific information.
If your existing schema version is 11.1.1.1.0, you must migrate to version 11.1.1.2.0 before you can run the Patch Set Assistant. See Appendix C, "Using Patch Assistant to Migrate from 11g Release 1 (11.1.1.1.0) to Release 1 (11.1.1.2.0)" for more information.
If you are interested in creating new schemas or dropping existing schemas, you must use the Repository Creation Utility (RCU). Information is provided in Oracle Fusion Middleware Repository Creation Utility User's Guide.
This chapter contains the following topics:
Section 4.1, "Which Schemas Need to be Updated with Patch Set Assistant?"
Section 4.2, "Special Instructions for Standalone Oracle Portal Repository Schemas"
Section 4.3, "Before You Begin Using the Patch Set Assistant"
The component schemas in Table 4-1 (default names shown) must be updated with the Patch Set Assistant in order to update them to 11g Release 1 (11.1.1.6.0). Remember to also update the dependent schemas in addition to the component schemas for your own product.
Notes About the Schemas That Need to Be Updated
Table 4-1 lists only the schemas for products that are available in the latest Oracle Fusion Middleware 11g Release 1 patch set.
For example, the Identify and Access Management components are currently not available in the current patch set and are not listed here.
To apply the latest patch set and upgrade the schemas for those products, see the Oracle Fusion Middleware Patching Guide in the Oracle Fusion Middleware 11g Release 1 (11.1.1.5.0) documentation library.
Oracle Portal is included in this Oracle Fusion Middleware patch set, but a schema upgrade is not required. As a result, the Patch Set Assistant for this release upgrades the PORTAL schema to its latest version, which is currently 11.1.1.4.0.
If the Discussions Crawler schema has not previously been installed using RCU, then migrating Discussions will automatically install the Discussions Crawler schema, assigning the same password as the Discussions schema. If you then attempt to update the Discussions Crawler schema individually, the Patch Set Assistant will warn that the schema has already been updated.
The component names shown in Table 4-1 are the component names used in previous Oracle Fusion Middleware releases. Some of these product and component names have changed for Oracle Fusion Middleware 11g Release 1 (11.1.1.6.0).
For more information, see Section 5.1, "New Product Names for Oracle WebCenter and Oracle Enterprise Content Management Suite".
Table 4-1 Schemas That Require Updating for the Latest Release
| Component Name | Schema(s) | Dependencies | Required For |
|---|---|---|---|
|
Audit Services |
|
None. |
11.1.1.2.0 to 11.1.1.6.0 11.1.1.3.0 to 11.1.1.6.0 11.1.1.5.0 to 11.1.1.6.0 |
|
Metadata Services |
|
None. |
11.1.1.2.0 to 11.1.1.6.0 11.1.1.3.0 to 11.1.1.6.0 11.1.1.4.0 to 11.1.1.6.0 11.1.1.5.0 to 11.1.1.6.0 |
|
Oracle Enterprise Scheduler Service |
|
The |
11.1.1.5.0 to 11.1.1.6.0 |
|
Oracle Platform Security Services |
|
None. |
11.1.1.4.0 to 11.1.1.6.0 11.1.1.5.0 to 11.1.1.6.0 |
|
Portal |
|
None. |
11.1.1.2.0 to 11.1.1.4.0 11.1.1.3.0 to 11.1.1.4.0 |
|
Oracle Internet Directory |
NOTE: The Oracle Internet Directory schema ( |
None. |
11.1.1.2.0 to 11.1.1.6.0 11.1.1.3.0 to 11.1.1.6.0 11.1.1.4.0 to 11.1.1.6.0 11.1.1.5.0 to 11.1.1.6.0 |
|
Master and Work Repository (Oracle Data Integrator) |
|
None. |
11.1.1.3.0 to 11.1.1.6.0 |
|
SOA Infrastucture |
|
The |
11.1.1.2.0 to 11.1.1.6.0 11.1.1.3.0 to 11.1.1.6.0 11.1.1.5.0 to 11.1.1.6.0 |
|
WebCenter Spaces |
|
The |
11.1.1.2.0 to 11.1.1.6.0 11.1.1.3.0 to 11.1.1.6.0 |
|
Discussions (WebCenter Suite) |
|
None. |
11.1.1.2.0 to 11.1.1.6.0 11.1.1.3.0 to 11.1.1.6.0 |
|
Discussions Crawler |
|
The |
11.1.1.2.0 to 11.1.1.6.0 11.1.1.3.0 to 11.1.1.6.0 |
|
Activity Graph and Analytics |
|
None. |
11.1.1.4.0 to 11.1.1.6.0 11.1.1.5.0 to 11.1.1.6.0 |
|
Oracle Universal Records Management 11g |
|
None. |
11.1.1.4.0 to 11.1.1.6.0 11.1.1.5.0 to 11.1.1.6.0 |
|
Oracle Content Server 11g - Complete |
|
None. |
11.1.1.4.0 to 11.1.1.6.0 11.1.1.5.0 to 11.1.1.6.0 |
|
Oracle Secure Enterprise Search |
|
The |
11.2.1 to 11.2.2 |
If you are using an Oracle Portal repository stored outside of the OracleAS Metadata Repository (any database that has not used the Upgrade Assistant, Repository Creation Utility, or Patch Set Assistant), then do not use the Patch Set Assistant to update the Portal schemas in the repository. Instead, refer to "Upgrading an Oracle Portal Repository in a Customer Database" in Oracle Fusion Middleware Upgrade Guide for Oracle Portal, Forms, Reports, and Discoverer.
This section contains information about things you should check before you run the Patch Set Assistant:
Section 4.3.3, "Shut Down All Components Using the Schemas You Want to Update"
Section 4.3.4, "Check the aq_tm_processes Value for Oracle Portal"
Make sure you have backed up your existing database and database schemas before you run the Patch Set Assistant, as instructed in Section 3.5.3, "Backing Up Your Database and Database Schemas".
Before running Patch Set Assistant, you should check to make sure that your database is up and running and that the schemas you want to upgrade are at versions that are supported for upgrade. To check this, perform the following SQL command:
SELECT VERSION, STATUS, UPGRADED FROM SCHEMA_VERSION_REGISTRY;
If the number in the "VERSION" column is 11.1.1.2.0 or greater, then the schema is supported for upgrade.
If you are using an Oracle database, you should recompile database objects after running the Patch Set Assistant by connecting to the database as SYS and running the following from SQL*Plus:
@?/rdbms/admin/utlrp.sql
After running utlrp.sql, and before you upgrade your schema, issue the following query to ensure there are no longer any invalid database objects:
SELECT owner, object_name FROM all_objects WHERE status='INVALID';
Take note of any invalid objects. The existence of invalid database objects may prevent the upgrade from completing successfully.
Before running Patch Set Assistant, shut down any Oracle Fusion Middleware components (including the Managed Server and Oracle instances) that may be using the schemas you want to update.
If you are running the Patch Set Assistant for the Oracle Portal schema on an Oracle database, make user that the aq_tm_processes value in your database is greater than 0. To check, use the following command after connecting to the database:
show parameter aq_tm_processes;
If the value returned is 0, use the following command to change the value to 1:
alter system set aq_tm_processes=1 scope=both;
The following sections describe how to run the Patch Set Assistant when you are installing the Oracle Fusion Middleware 11g Release 1 (11.1.1.5.0) patch set:
Section 4.4.1, "General Information about the Patch Set Assistant"
Section 4.4.3, "Using the Patch Set Assistant Graphical Interface"
Section 4.4.4, "Using the Patch Set Installer from the Command Line"
Section 4.4.5, "Verifying the Schema Version Number After Update"
The Patch Set Assistant is installed into the bin directory in your Oracle home by the Patch Set Installer (see Chapter 3, "Applying the Latest Oracle Fusion Middleware Patch Set").
You can use the Patch Set Assistant to patch any component schema in the Middleware home from where the Patch Set Assistant started. For example, if your Middleware home contains two Oracle homes: one for Oracle SOA Suite and a second for Oracle Identity Management, you can run the Patch Set Assistant from one Oracle home (for example, the SOA Oracle home) and patch the schemas for the components in both that Oracle home and the second Oracle home (for example, the Identity Management Oracle home).
Note:
In an environment where no products other than Application Developer have been installed in an Oracle home, you can update the Metadata Services (prefix_MDS) schema from the bin directory in the Oracle Common home.
To start Patch Set Assistant, go to the bin directory in the Oracle home for the product schema you want to patch, then run the following command:
On UNIX operating systems:
cd ORACLE_HOME/bin
./psa
On Windows operating systems:
CD ORACLE_HOME\bin
psa.bat
Follow the instructions in Table 4-2 to use the Patch Set Assistant to update your schemas.
If you need additional help with any of the screens, refer to Appendix B, "Patch Set Assistant Screens" or click Help on the screen to access the online help.
Table 4-2 Patch Set Assistant Screens
| Screen | Description |
|---|---|
|
This page introduces you to the Patch Set Assistant. |
|
|
Select the top-level component you want to upgrade. NOTE: If you are upgrading from Release 11.1.1.2.0 or 11.1.1.3.0, the |
|
|
Verify that you have satisfied the database prerequisites. |
|
|
Specify your database credentials to connect to your database, then select the schema you want to update. Note that this screen appears once for each schema that must be updated as a result of the component you selected on the Select Component screen. |
|
|
This page displays the status of the Patch Set Assistant as it examines each component schema. Verify that your schemas have a "successful" indicator in the Status column. |
|
|
Verify that the schemas listed to be upgraded are the ones you expect. |
|
|
This screen shows the progress of the schema update. |
|
The full command line syntax for the Patch Set Assistant is shown below:
./psa (or psa.bat) -response response_file [-logLevel log_level [-help]]
See Table 4-3 for descriptions for these parameters.
Table 4-3 Patch Set Assistant Command Line Parameters
| Parameter | Required or Optional Parameter? | Description |
|---|---|---|
|
|
Required. |
Full path and name of the input response file. |
|
|
Optional. |
Logging level. One of the following:
The default logging level is NOTIFICATION. |
|
|
Optional. |
View all of the command line options. |
To generate the response file used with the -response parameter, you should run the Patch Set Assistant GUI (Section 4.4.3, "Using the Patch Set Assistant Graphical Interface"). On the Upgrade Summary screen, click Save Response File to save your information to a response file.
You can use the SQL command below to verify that the schema version in schema_version_registry has been properly updated:
SELECT VERSION, STATUS, UPGRADED FROM SCHEMA_VERSION_REGISTRY;
Check that the number in the "VERSION" column matches the latest version number for that schema.
If the status appears as "INVALID" then the schema update failed. You should examine the logs files to determine the reason for the failure. For more information, see Section 4.5, "Patch Set Assistant Log Files".
If you are using an Oracle database, you should recompile database objects after running the Patch Set Assistant by connecting to the database as SYS and running the following from SQL*Plus:
SQL> @?/rdbms/admin/utlrp.sql
This will compile the database objects that were updated by Patch Set Assistant.
Then issue the following query to ensure there are no longer any invalid database objects:
SELECT owner, object_name FROM all_objects WHERE status='INVALID';
None of the database objects for the updated schema should be invalid at this point. If there are any, run the utlrp.sql command again and check again. If the problem persists, you should file a service request.
When the amount of data in Oracle Fusion Middleware databases grows very large, maintaining the databases can become difficult and can affect performance. Oracle Fusion Middleware 11g Release 1 (11.1.1.4.0) and later provide a set of tools that can help you purge the Oracle Fusion Middleware of unneeded data.
When a new Oracle Fusion Middleware user installs the latest Oracle SOA Suite schemas using the Repository Creation Utility (RCU), stored procedures required by the Oracle SOA Suite purge scripts are automatically installed in the database.
However, if you are running Oracle Fusion Middleware 11g Release 1 (11.1.1.2.0) or Release 1 (11.1.1.3.0), these stored procedures are not installed automatically. As a result, after you run the Patch Set Assistant to update your Oracle SOA Suite schemas to the latest version, you must manually install the necessary database objects using the following procedure. This procedure is necessary if you want to use the purging capabilities provided by Oracle SOA Suite 11g Release 1 (11.1.1.4.0) or later:
Locate, download, and unpack the latest Oracle Fusion Middleware 11g Repository Creation Utility (RCU) software archive.
For more information, see "Obtaining RCU" in the Oracle Fusion Middleware Repository Creation Utility User's Guide.
The directory where you unpack the RCU software is referred to as the RCU_HOME directory.
Using SQLPlus, connect to the database where the Oracle SOA Suite schemas are installed using the database user that owns the SOAINFRA schema.
Run the following script to load the database objects required for purging Oracle SOA Suite data:
RCU_HOME/rcu/integration/soainfra/sql/soa_purge/soa_purge_scripts.sql
Run the following script to load the database objects required for verifying the Oracle SOA Suite data in the database:
RCU_HOME/rcu/integration/soainfra/sql/verify/soa_verify_scripts.sql
After you load the database objects using the provided SQL scripts, refer to "Managing Database Growth" in the Oracle Fusion Middleware Administrator's Guide for Oracle SOA Suite for more information.
The Patch Set Assistant writes log files to the following locations:
On UNIX operating systems:
MW_HOME/oracle_common/upgrade/logs/psatimestamp.log
On Windows operating systems:
MW_HOME\oracle_common\upgrade\logs\psatimestamp.log
Some components will create a second log file called psatimestamp.out, also in the same location.
The timestamp will reflect the actual date and time that Patch Set Assistant was run.
Should any failures occur when running Patch Set Assistant, these log files will be needed to help diagnose and correct the problem; do not delete them. You can alter the contents of your log files by specifying a different -logLevel from the command line.
Some of the operations performed by the Patch Set Assistant may take longer to complete than others. If you want to see the progress of these long operations, you can see this information in the log file, or you can use the following query:
SELECT VERSION, STATUS, UPGRADED FROM SCHEMA_VERSION_REGISTRY WHERE OWNER='schema_name';
In the query results, the STATUS field will be either "UPGRADING" or "UPGRADED" during the schema patching operation, and will become "VALID" when the operating is finished.
|
 Copyright © 2011, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|