B Patch Set Assistant Screens

This appendix contains screenshots and descriptions for the Patch Set Assistant screens:

Welcome
Select Component
Prerequisites
Schema
Examine
Upgrade Summary
Upgrade Progress
Upgrade Success

B.1 Welcome

Description of the illustration psa_welcome.gif

The Welcome screen is displayed each time you start the installer.

NOTE: The version number on the 11.1.2.1.0 Patch Set Assistant Welcome screen is listed as 11.1.1.6.0. This is a known issue.

You can click View Log at any time during the schema upgrade process to view the log file. A separate window (Log File Viewer) is displayed that contains the messages being written to the log file. The top of the Log File Viewer contains the location and name of the log file. You can click Refresh to see the most recent messages being logged.

B.2 Select Component

Description of the illustration PSA.PNG

Use this screen to select the component schema you want to update.

The Patch Set Installer lists all components that are found in the Middleware home. For example, if you started the Patch Set Installer from the /home/Oracle/Middleware/Oracle_IDM1/bin directory (on UNIX operating systems) or c:\Products\Oracle\Middleware\Oracle_IDM1\bin directory (on Windows operating systems), the Patch Set Installer will list all components found in /home/Oracle/Middleware directory (on UNIX operating systems) or c:\Products\Oracle\Middleware directory (on Windows operating systems).

You can only use Patch Set Assistant to update one top-level component at a time. In the figure above, notice that Oracle Privileged Account Manager is selected, which means Patch Set Assistant would update the OPAM schema as well as the OPSS schema, upon which the OPAM schema is dependent. However, the top-level "Oracle Metadata Services" box is not selected even though that schema is going to be updated.

If you wanted to update either of the other two top-level schema found in this Middleware home (in this case, "Oracle Metadata Services") you would have to restart the Patch Set Assistant and select MDS separately.

B.3 Prerequisites

Description of the illustration psa_prerequisites.gif

Use this screen to verify that you have satisfied the database prerequisites before you continue. You must check all the boxes acknowledging that all prerequisites for upgrade have been met, or else you will be unable to continue to the next screen.

Select Database backup completed to verify that you have backed up your database as described in Section 4.2.1, "Back Up Your Database and Database Schemas".

Select Database version is certified by Oracle for Fusion Middleware upgrade to verify that you have read the System Requirements and Supported Platforms for Oracle Fusion Middleware 11gR1 document on the Oracle Fusion Middleware Supported System Configurations page, and that your database is certified for use with Oracle Fusion Middleware.

B.4 Schema

Description of the illustration psa_schema.gif

Use this screen to specify database connection credentials and schema information for upgrade. This screen appears once for each component schema that needs to be updated; each time after the first time the screen will have all the database credential values filled in for you. If you have schemas on different databases then you will need to alter your database connection information accordingly.

The following table describes the fields on this screen:

Field	Description
Database Type	Select your database type from the drop-down list. Only database types that are valid for the schema are available in this list.
Connect String	Specify the connection credentials to your database. For Oracle databases: host:port/service_name For Microsoft SQL Server and IBM DB2 databases: host:port;DatabaseName=dbname
DBA User Name	Specify the user name and role of the database administrator user. NOTE: Oracle Privileged Account Manager schema must be updated by a Database user with SYSDBA privileges. So credentials provided to connect to the database should have SYSDBA privilege. For Oracle databases, enter SYS or any user with DBA role (for example, `sys as sysdba` or any user with DBA privileges). Note that the SYS database user can grant DBA privileges to an ordinary database user 'SCOTT' with the following SQL DDL statement: GRANT DBA TO SCOTT; For Microsoft SQL Server databases, enter `sa` or any user with `db_owner` role. For IBM DB2 databases, enter `db2admin` or any user with `DBA` role. For Hypersonic databases, enter `sa`. For Sybase databases, enter `sa`. For MySQL databases, enter `root`.
DBA Password	Enter the password for your database administrator user.

After these values are filled in, click Connect to connect to your database. After the connection succeeds, two additional fields will become active on the screen:

Field Description

Field	Description
Schema User Name	This drop-down list contains all available product schemas in the database to which you are connected. Select the schema you want to update from the drop-down list. NOTE: The Oracle WebCenter Content Server - Complete (`prefix_OCS`) and Oracle WebCenter Content: Records (`prefix_URMSERVER`) schemas will require you to manually enter the name of the schema; they will not appear in the drop-down list and the Connect button will not be active for these schemas. NOTE: If the drop-down list is empty, make sure you have connected to the database as a user with the required privileges.
Schema Password	Specify the password for the selected schema.

Schema User Name

This drop-down list contains all available product schemas in the database to which you are connected. Select the schema you want to update from the drop-down list.

NOTE: The Oracle WebCenter Content Server - Complete (prefix_OCS) and Oracle WebCenter Content: Records (prefix_URMSERVER) schemas will require you to manually enter the name of the schema; they will not appear in the drop-down list and the Connect button will not be active for these schemas.

NOTE: If the drop-down list is empty, make sure you have connected to the database as a user with the required privileges.

Schema Password

Specify the password for the selected schema.

B.5 Examine

Description of the illustration psa_examine.gif

This page displays the status of each component schema for upgrade. The meaning of the status indicators for the components is listed in the following table.

Status	Description
in progress	The Patch Set Assistant is examining whether or not the schema can be upgraded.
pending	The schema will be examined when the Patch Set Assistant is finished examining the preceding component.
already upgraded	The schema was previously successfully upgraded with the Patch Set Assistant or was created with the latest version of the Repository Creation Utility (RCU). No action will be taken on this schema.
failed	The schema can not be upgraded.
skipped	The examination of this schema was skipped. This is caused when the examination of a dependent schema fails.
succeeded	The examination of the schema was successful and the schema is ready to be upgraded.

B.6 Upgrade Summary

Description of the illustration psa_upgrade_summary.gif

Use this page to review a summary of the options you have selected and to start the upgrade process.

Click Save Response File to save this upgrade information to a response file. This file can be used later of you want to run the Patch Set Assistant from the command line. For more information, see Section 4.3.4, "Using the Patch Set Installer from the Command Line".

B.7 Upgrade Progress

Description of the illustration psa_upgrade_progress.gif

This screen shows you the progress of your schema upgrade. The "Upgrade Progress" bar moves from 0% at the beginning to 100% when the upgrade is complete.

B.8 Upgrade Success

Description of the illustration psa_upgrade_complete.gif

This screen indicates that the upgrade was successful.

Be sure to view the log file located in the MW_HOME/oracle_common/upgrade/logs (on UNIX operating systems) or MW_HOME\oracle_common\upgrade\logs (on Windows operating systems) directory for details about the upgrade. You can view the log file with any text editor, or you can click the View Log button.