Skip Headers
Oracle® Fusion Middleware Patching Guide
11g Release 1 (11.1.1.6.0)

Part Number E16793-19
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

4 Updating Your Schemas with Patch Set Assistant

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:

Note:

The Patch Set Assistant does not upgrade schemas that are in customer databases, which includes any database that has not been updated using the Upgrade Assistant (UA), Repository Creation Utility (RCU), or Patch Set Assistant (PSA).

If you are an Oracle Portal user, note that the Oracle Portal schema can in certain circumstances be installed in a customer database. For more information, 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:

4.1 Which Schemas Need to be Updated with 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).

Schemas that are not listed in Table 4-1 do not need to be upgraded to 11g Release 1 (11.1.1.6.0).

Notes About the Schemas That Need to Be Updated

Table 4-1 Schemas That Require Updating for the Latest Release

Component Name Schema(s) Dependencies Required For

Audit Services

prefix_IAU

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

prefix_MDS

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

prefix_ESS

The prefix_MDS schema must be updated first.

11.1.1.5.0 to 11.1.1.6.0

Oracle Platform Security Services

prefix_OPSS

None.

11.1.1.4.0 to 11.1.1.6.0

11.1.1.5.0 to 11.1.1.6.0

Portal

prefix_PORTAL

None.

11.1.1.2.0 to 11.1.1.6.0

11.1.1.3.0 to 11.1.1.6.0

Oracle Internet Directory

ODS

NOTE: The Oracle Internet Directory schema (ODS) cannot be prepended with a custom prefix.

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 Business Intelligence Platform

prefix_BIPLATFORM

The prefix_MDS schema must be updated first.

11.1.1.3.0 to 11.1.1.6.0

Master and Work Repository (Oracle Data Integrator)

prefix_ODI_REPO

None.

11.1.1.3.0 to 11.1.1.6.0

SOA Infrastucture

prefix_SOAINFRA

The prefix_MDS schema must be updated first.

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

prefix_WEBCENTER

The prefix_MDS schema must be updated first.

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)

prefix_DISCUSSIONS

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

prefix_DISCUSSIONS_CRAWLER

The prefix_DISCUSSIONS schema must be updated first.

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

prefix_ACTIVITIES

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

prefix_URMSERVER

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

prefix_OCS

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

prefix_SEARCHSYS

The prefix_ESS must be updated first.

11.2.1 to 11.2.2


4.2 Special Instructions for Standalone Oracle Portal Repository Schemas

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.

4.3 Before You Begin Using the Patch Set Assistant

This section contains information about things you should check before you run the Patch Set Assistant:

4.3.1 Back Up Your Database and Database Schemas

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.4, "Backing Up Your Database and Database Schemas".

4.3.2 Check Your Database and 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 OWNER, 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 before running the Patch Set Assistant to check for invalid objects before the upgrade. Connect to the database as SYS and run 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.

4.3.3 Shut Down All Components Using the Schemas You Want to Update

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.

4.3.4 Check the aq_tm_processes Value for Oracle Portal

If you are running the Patch Set Assistant for the Oracle Portal schema on an Oracle database, make sure 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;

4.4 Running the Patch Set Assistant

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:

4.4.1 General Information about the Patch Set Assistant

The Patch Set Assistant is installed into the bin directory in the Oracle Common home by the Product or Patch Set Installer (see Section 3.6.1, "About the Installers Used for Patching").

You can use the Patch Set Assistant to patch any component schema in the Middleware home from where the Patch Set Assistant started.

4.4.2 Starting the Patch Set Assistant

To start Patch Set Assistant, go to the bin directory in the Oracle Common home, then run the following command:

On UNIX operating systems:

cd MW_HOME/oracle_common/bin
./psa

On Windows operating systems:

CD MW_HOME\oracle_common\bin
psa.bat

4.4.3 Using the Patch Set Assistant Graphical Interface

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

Welcome

This page introduces you to the Patch Set Assistant.

Select Component

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 prefix_ACTIVITIES schema will not be available in your environment as this schema was not introduced until Release 11.1.1.4.0. Make sure you de-select this schema from the WebCenter Portal component; otherwise the Patch Set Assistant will ask for credentials for this schema.

Prerequisites

Verify that you have satisfied the database prerequisites.

Schema

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.

Examine

This page displays the status of the Patch Set Assistant as it examines each component schema. Verify that your schemas have a "succeeded" or "already upgraded" indicator in the Status column.

Upgrade Summary

Verify that the schemas listed to be upgraded are the ones you expect.

Upgrade Progress

This screen shows the progress of the schema update.

Upgrade Success

 

4.4.4 Using the Patch Set Installer from the Command Line

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

-response

Required.

Full path and name of the input response file.

-logLevel

Optional.

Logging level. One of the following:

  • TRACE

  • NOTIFICATION

  • WARNING

  • ERROR

  • INCIDENT_ERROR

The default logging level is NOTIFICATION.

-help

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.

Note:

When Patch Set Assistant is run in -reponse file mode, it will not upgrade any schemas that return "already upgraded" during the Examine phase. These schemas will skip the upgrade phase entirely. This applies only when Patch Set Assistant is run in -response file mode.

4.4.5 Verifying the Schema Version Number After Update

You can use the SQL command below to verify that the schema version in schema_version_registry has been properly updated:

SELECT OWNER, 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".

4.4.6 Checking for Invalid Database Objects

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.

4.5 Patch Set Assistant Log Files

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.