A Upgrade Assistant Screens
The screens for the Oracle Fusion Middleware Upgrade Assistant vary depending upon the type of Oracle Fusion Middleware software you are upgrading.
Refer to the following sections for more information:
Note:
The screens documented in this appendix are not necessarily in sequels order. Depending on the options you select, you may not see all of the screens. See Chapter 1, "Using the Upgrade Assistant" for general information on the screens that are used for each upgrade type.
A.1 Welcome
The Oracle Fusion Middleware Upgrade Assistant is used to upgrade component schemas, component configurations, and standalone system component configurations from Fusion Middleware 11g Release 1 (11.1.1.6.0 or 11.1.1.7.0) to Fusion Middleware 12c (12.1.2).
A.2 Schemas
Select Schemas to upgrade schemas for your installed components. The Upgrade Assistant will list components that are candidates for schema upgrade. It is possible that your environment does not use one of the listed components and, therefore, does not need a schema upgrade for the component. When using the Upgrade Assistant to upgrade schemas, upgrade schemas one domain at a time. After the schemas are upgraded, and the domain has been reconfigured and upgraded, launch the Upgrade Assistant again for each additional domain that requires an upgrade.
CAUTION: Upgrade only those schemas that will be used to support your 12.1.2.0.0 components. Do not upgrade schemas that are currently being used to support 11g components that are not included in the Oracle Fusion Middleware 12.1.2.0.0 release.
A.3 WebLogic Component Configurations
Figure A-3 WebLogic Component Configurations
Description of "Figure A-3 WebLogic Component Configurations "
Select the WebLogic Component Configurations option to upgrade component configurations for a managed WebLogic Server domain. You will be prompted to supply the connection details required to connect to the WebLogic Administration Server that is managing the domain.
| Element | Description |
|---|---|
|
The host of the administration sever. Be sure to include the full host name; for example: fusionHost1.example.com |
|
|
The listening port of the administration server. Typically, the administration server listens on port 7001. |
|
|
The username that is used to log in to the administration server. This is the same username you use to log in to the Administration Console for the domain. |
|
|
The password for the administrator account that is used to log in to the administration server. This is the same password you use to log in to the Administration Console for the domain. |
A.4 Standalone Components
Select the Standalone System Component Configurations option when you will be upgrading a standalone system component, such as Oracle HTTP Server (OHS). You will be prompted to select one of the following:
| Option | Description |
|---|---|
|
Create a New Domain |
Standalone system components will have a separate standalone domain in 12c. A standalone domain is a container for system components, such as Oracle HTTP Server. It has a directory structure similar to an Oracle WebLogic domain, but it does not contain an Administration Server or Managed Servers. It can contain one or more instances of system components of the same type, such as Oracle HTTP Server, or a mix of types. Management tools, such as the Configuration Wizard, pack and unpack, WLST, and Node Manager can operate on standalone domains. |
|
Update an Existing Domain |
Once a standalone domain has been created for a system component in 12.1.2.0.0, you can select this option to extend that domain for another standalone system component. |
A.5 Available Components
The Upgrade Assistant provides a list of installed Oracle Fusion Middleware components that have schemas that can be upgraded. When you select a component, the schemas and any dependencies are automatically selected.
To select a schema, click the box next to the component name.
To select all available schemas, click the box next to Available Components. This will select all components and their available schemas.
CAUTION: Upgrade only those schemas that will be used to support your 12.1.2.0.0 components. Do not upgrade schemas that are currently being used to support 11g components that are not included in the Oracle Fusion Middleware 12.1.2.0.0 release.
A.6 Component List
This screen provides a list of components that will be included in the WebLogic domain's component configuration upgrade. The name of the domain is provided along with the list of components located within the domain.
Review the list to verify that the correct components will be upgraded. If you do not see the components you want to upgrade, you may have selected the wrong domain. Use the Back button to specify a different domain.
A.7 Prerequisites
This screen requires you to acknowledge that all prerequisites have been met before you continue with the upgrade. You must check the boxes before you can continue.
The Upgrade Assistant will not verify that the prerequisites have been met.
A.8 Domain Directory
When upgrading a standalone system component, such as Oracle HTTP Server (OHS), you have two choices for configuring the component's upgrade domain directory:
Beginning with 12c (12.1.2), standalone system components will have their own standalone domain. Use this screen to specify the domain option you want to apply to the standalone system component you are upgrading.
When you are upgrading your 11g standalone system components (which had no previous domain associations), you must first create a new standalone domain for your system components.
Specify the location and name of a new (unique) directory to be created for the upgrade of your system components.
After you have created a new 12.1.2 standalone domain for your upgraded 11g system components, you can extend the standalone domain with additional standalone system components using this option.
This option would also be used if a domain was created with the "Create a New Domain" option and you re-run the upgrade.
Click Browse and use the navigation tree to select a valid domain directory (a directory that contains a config.xml file in the config directory of a 12.1.2.0.0 domain), and click Next.
A.9 11g Domain Directory
When upgrading schemas for OPSS or Audit, you must specify the existing Oracle WebLogic 11g domain directory. The Upgrade Assistant requires the 11g domain location to access the jps-config.xml file.
Click Browse and use the navigation tree to select a WebLogic domain directory of the 11g domain to be upgraded.
A.10 Select Schemas
Use this screen to enter information required to connect to the selected schema and the database that hosts the schema. Click Connect to connect to the database then select the schema to be upgraded.
NOTE: For WebLogic Server domain schemas you will manually enter the 11g schema user name and password.
The following table describes the elements that appear on this screen.
| Element | Description |
|---|---|
|
Select the database type from the drop-down menu. The types of databases available in the menu varies, depending on the schema you are about to upgrade. NOTE: The database type shown in the example above is for Oracle Edition-Based Redefinition (EBR) schemas. Be sure to select the correct database type for your upgrade. |
|
|
Enter the location of the database. For example, if you are selecting an Oracle database, the following URL format could be used: host:port/db_service_name If you are using a Microsoft SQL Server or IBM DB2 database, then select the database type from the drop-down menu, and review the text below the field, which provides the syntax required for each database type. |
|
|
Enter the database user name used to connect to the database. For Oracle database users, the user of Upgrade Assistant must be granted the Oracle "DBA" role. |
|
|
Enter the password associated with the specified DBA database user. |
|
|
Enter the user name of the schema, for example, DEV_MDS. |
|
|
Enter the password associated with the specified schema user name. |
|
|
Edition Name |
When Oracle Database enabled for edition-based redefinition is selected as the database type, you must specify the existing edition name. NOTE: Before upgrading an EBR-enabled schema from Fusion Middleware 11g Release 1 (11.1.1.6.0 or 11.1.1.7.0), you must first connect to the database server and create an edition on the database server for 12c (12.1.2). The new edition for 12.1.2 must be a child of your 11.1.1.6.0 or 11.1.1.7.0 edition. For more information on creating an edition on the server for edition-based redefinition, see "Creating an Edition on the Server for Edition-Based Redefinition" in Planning an Upgrade of Oracle Fusion Middleware. |
A.11 Instance Directories
When upgrading system components, such as OHS, you must provide the directory locations of the 11g instances that will be used as a starting point for creating new 12c component instances.
Use the Add button to include more than one instance, if needed.
NOTE: You cannot use the Upgrade Assistant to upgrade Oracle 10g instances to Oracle 12c. You must first upgrade Oracle 10g instances to 11g. For more information on migrating 10g to 11g, see the 11g upgrade documentation for your components.
A.12 Node Manager
Use this screen to specify the credentials of the Node Manager that will be used to create a domain during the upgrade of standalone system components.
Note:
The username and password are only used to authenticate connections between Node Manager and clients. They are independent from the server Administrator ID and password.
| Element | Description |
|---|---|
|
The username used to access Node Manager. |
|
|
The password used to access Node Manager. You will need to re-enter the password for confirmation. |
|
|
Listen Address |
Enter the DNS name or IP address upon which Node Manager listens in the Listen Address field. |
|
The listening port number of Node Manager. |
A.13 OWSM Policy Manager
Use this screen to enter the credentials for the WebLogic Administration Server domain where the Oracle Web Services Manager (OWSM) Policy Manager is deployed.
| Element | Description |
|---|---|
|
The host where an Administration Server for the domain is running. Be sure to include the full host name; for example: fusionHost1.example.com |
|
|
The listening port of the administration server. Typically, the administration server listens on port 7001. |
|
|
The username that is used to log in to the administration server. This is the same username you use to log in to the Administration Console for the domain. |
|
|
The password for the administrator account that is used to log in to the administration server. This is the same password you use to log in to the Administration Console for the domain. |
A.14 ODI Options
Figure A-14 Oracle Data Integrator (ODI) Options
Description of "Figure A-14 Oracle Data Integrator (ODI) Options"
Select from the following options the operations you want the Upgrade Assistant to perform. Click Next to continue.
| Option | Description |
|---|---|
|
Replace KMs with mandatory updates |
This selection replaces standard KMs with the newest version. Any customizations to standard KMs will be lost. |
|
Upgrade topology and security metadata |
This selection replaces topology and security artifacts such as Technologies, Datatypes, Security Profiles and others with the newest version. Any customizations will be lost. |
|
Upgrade repository to use GUIDs |
This selection sets the repository to 12c full mode. All objects will be referenced using 12c GUID rather than the internal ID. If you uncheck this, then the repository is left in "11g compatibility mode," which allows the user to execute already generated 11g interface objects. The repository can be switched to 12c full mode using the graphical user interface or an SDK call. CAUTION: Once the repository is switched, you cannot revert to the previous 11g compatibility mode. |
|
Upgrade interfaces to use 12c mappings - losing 11g SDK compatibility |
This selection converts all 11g interfaces to 12c mappings. Once converted to 12c mappings, all of the existing scenarios must be regenerated before use. You cannot use the existing 11g SDK applications; they must be upgraded to use the 12c SDK. If this option is not selected, the conversion to 12c mappings is not performed. The interfaces remain and can be only modified by the 11g SDK (in the graphical interface they are read-only). These can be modified and regenerated/executed using the 11g SDK. Once the user has modified there custom application, the interfaces can then be converted to 12c mappings using the graphical interface or the 12c SDK. NOTE: In order for this migration to work properly, all interfaces in the 11g repository must be valid (they should not return any errors when validating from 11g Studio, for example). If an 11g interface is not valid, the Upgrade Assistant will not stop - even if some 11g interfaces fail during migration. The Upgrade Assistant will try to migrate any invalid interfaces into a 12c mapping, but the migration of that interface may fail, or exceptions may be printed to the log file. If this occurs, the resulting mapping will be invalid. To ensure a successful upgrade, all interfaces in the 11g repository must be valid. |
A.15 ODI Supervisor
When you created the Master and Work repositories for ODI, the Repository Creation Utility prompted you to supply a password for the default SUPERVISOR account. On the ODI Supervisor screen, enter the following:
| Element | Description |
|---|---|
|
ODI Supervisor User Name |
Supervisor account name for the ODI repository to be upgraded. The Supervisor user should be |
|
ODI Supervisor Password |
Password that you created for the ODI Supervisor account. |
A.16 ODI Upgrade Key
This screen generates a unique identifier or upgrade key to convert 11g IDs for repository objects into unique GUIDs. You can use the auto-generated upgrade key or you can specify your own key in the Upgrade Key field.
Consider the following two scenarios when selecting an upgrade key:
-
You know that an ID used in the 11g repository is the same as a project ID located in an XML file exported from the same repository. Use the Upgrade Key field to enter the project ID that was used in the 11g repository.
In this scenario, the upgrade key used to upgrade the repository should be the same as the upgrade key used to import the XML file into the upgraded 12c repository. This ensures that the project object in the import file will be properly matched with the project object in the repository (when using one of SYNONYM import modes).
-
You have 11g XML export file provided from a source containing objects created in another repository and you do not know which IDs were used. Use the auto-generated upgrade key or specific your own unique ID to avoid duplicate IDs.
In this scenario, there is a chance that the file may contain a project that has the same internal ID. To prevent erroneous object matching, which may corrupt the metadata, a different, custom upgrade key should be used when importing that file into the repository.
NOTE: When multiple copies of the same object exist (in a repository or exported in XML files), the same GUID should be produced for all copies of the object. For this reason, the same upgrade key must be used for all upgrade operations involving the copies of that particular object.
A.17 Examine
This screen displays the status of the Upgrade Assistant as it examines each component, verifying that the component is ready for upgrade.
The Upgrade Assistant examines each component to be sure it meets a minimum set of criteria before you begin the upgrade process.
The description of the status indicators for the components is listed in the following table:
| Status | Description |
|---|---|
|
The component has already been upgraded in a previous Upgrade Assistant session or the schema was recently created by Repository Creation Utility 12.1.2.0.0 for the current release and does not require an upgrade. No action will be performed on this component. |
|
|
The Upgrade Assistant is examining the upgrade items for the component. |
|
|
The component will be examined when the Upgrade Assistant finishes the preceding component. |
|
|
Upgrade items were missing or did not meet upgrade criteria. The Upgrade Assistant cannot upgrade the component. Click View Log to troubleshoot the errors. |
|
|
Upgrade items were found and are valid for upgrade. |
Canceling the examination process has no effect on the schemas or configuration data; the only consequence is that the information the Upgrade Assistant has collected must be collected again in a future upgrade session.
A.18 Examine Failure
This dialog box appears when one of more of your components failed the examination phase and you selected to continue with the upgrade. If there was an examination failure, you should consider canceling the upgrade (click No) and review the log files. See Troubleshooting Your Upgrade for more information.
Click Yes to continue the upgrade.
A.19 Upgrade Summary
Use this screen to review a summary of the options you have selected and to start the upgrade process.
Expand and collapse the tree to show or hide details about the data provided in the wizard screens, such as schema details, Oracle WebLogic Server connection details, and Oracle WebLogic domain directory information.
Click Upgrade to start the upgrade process.
If you are upgrading a schema, verify that you have a backup of the database that hosts the schema.
The Save Response File option creates a file that can be used as input to the Upgrade Assistant. The response file collects all the information that you have entered through the Upgrade Assistant's graphical user interface screens, and enables you to perform a silent upgrade at a later time. The silent upgrade performs exactly the same function that the Upgrade Assistant wizard performs, but you do not have to manually enter the data again.
A.20 Upgrade Progress
This screen shows the status of the upgrade process.
The status of each component upgrade is indicated by one of the following messages that can appear next to the component name. The following table describes each status message.
| Status | Description |
|---|---|
|
The Upgrade Assistant is upgrading the component's upgrade items. |
|
|
The component will be upgraded when the Upgrade Assistant finishes the preceding component. |
|
|
The component was upgraded previously by the Upgrade Assistant or the component was just installed and is already at the latest version. No action will be taken on this component. |
|
|
skipped |
The component is dependent on another component which has a status of "failed". When the status is "skipped" no upgrade is attempted for that component. |
|
failed |
Upgrade items were missing or did not meet upgrade criteria. The component cannot be upgraded. Click View Log to troubleshoot the errors. |
|
Upgrade items were upgraded successfully. |
If any components are not upgraded successfully, refer to the Upgrade Assistant log files for more information.
A.21 Upgrade Success
The upgrade was successful. The Post-Upgrade Actions window describes the manual tasks you must perform to make the component function in the new installation. This is an optional window that will only show up if a component has post-upgrade steps.
In addition, be sure to do the following:
-
View the
postupgrade.txtfile in the Oracle home:On Unix systems:
ORACLE_HOME/oracle_common/upgrade/logs
On Windows systems:
ORACLE_HOME\oracle_common\upgrade\logs
-
Review the Upgrade Guide specific to your Oracle Fusion Middleware environment for more information about any additional post-upgrade tasks.
A.22 Upgrade Failure
The upgrade of one or more components has failed. The component cannot be upgraded at this time. Click View Log to troubleshoot the errors.
For more information, see Troubleshooting Your Upgrade.
A.23 Cancel Upgrade
This screen prompts you to confirm your decision to cancel the upgrade.
Important Note: If you cancel a schema upgrade, you must restore a backup of the database that hosts the schema and its environment (the pre-upgrade directory structure).