3 Performing the Oracle Business Intelligence Upgrade
This chapter contains the procedure to upgrade Oracle Business Intelligence from Release 12.2.1 to Release 12.2.1.1. The upgrade is performed in-place, that is, the upgrade operations are performed on the existing 12.2.1 domain.
If you are upgrading from a 11g release, such as 11.1.1.7.x, follow the procedure described in the BI Migration Guide.
High-level upgrade steps:
- Installing Fusion Middleware Infrastructure Release 12.2.1.1
Download and install the Fusion Middleware Infrastructure Release 12.2.1.1 on the target system using the procedure in this section. - Installing Oracle Business Intelligence Release 12.2.1.1
Download and install the Oracle Business Intelligence distribution on the target system using the procedure in this section. - Running the Readiness Check
Oracle recommends that you run the Readiness Check before starting the upgrade process in order to ensure that your pre-upgrade environment is ready for upgrade. - Upgrading Schemas with the Upgrade Assistant
After you install the 12.2.1.1 product distributions, you must first upgrade the 12.2.1.0 schemas using the Upgrade Assistant. The Upgrade Assistant provides two options for upgrading schemas:Individually Selected SchemasandAll Schemas Used By a Domain. However, for the topology defined in this document, you must selectAll Schemas Used By a Domain. - Backing up the mapViewerConfig.xml File
The mapViewerConfig.xml file is overwritten by the reconfiguration templates when you run the Reconfiguration Wizard. Therefore, you must back up the mapViewerConfig.xml file before reconfiguring your 12.2.1.0 domain. - Reconfiguring the BI Domain with the Reconfiguration Wizard
After upgrading the schemas, run the Reconfiguration Wizard on your existing domain to reconfigure it before upgrading the domain configuration. - Restoring the mapViewerConfig.xml File
The mapViewerConfig.xml file is overwritten when you run the Reconfiguration Wizard on your domain. You can know that the mapViewerConfig.xml file is overwritten by checking its file size. You must restore the original file that you backed up before upgrading your domain with the Upgrade Assistant. - Upgrading the Configuration with the Upgrade Assistant
You must upgrade the 12.1.1.0 domain configuration using the Upgrade Assistant.
3.1 Installing Fusion Middleware Infrastructure Release 12.2.1.1
Download and install the Fusion Middleware Infrastructure Release 12.2.1.1 on the target system using the procedure in this section.
3.2 Installing Oracle Business Intelligence Release 12.2.1.1
Download and install the Oracle Business Intelligence distribution on the target system using the procedure in this section.
3.3 Running the Readiness Check
Oracle recommends that you run the Readiness Check before starting the upgrade process in order to ensure that your pre-upgrade environment is ready for upgrade.
- About Running a Pre-Upgrade Readiness Check with the Upgrade Assistant
You can run the Upgrade Assistant in -readiness mode to detect issues before you perform the actual upgrade. This can be done using the GUI or with silent upgrades using the response files. - Readiness Check Screens
This section describes the screens that are presented when running the Upgrade Assistant in -readiness mode.
3.3.1 About Running a Pre-Upgrade Readiness Check with the Upgrade Assistant
The Upgrade Assistant readiness check performs a read-only, pre-upgrade review of your existing Oracle Fusion Middleware schemas and Oracle WebLogic configurations.
The readiness check generates a formatted, time-stamped readiness report so you can address potential issues before you attempt the actual upgrade. If no issues are detected, you can begin the upgrade process. Oracle recommends that you read this report thoroughly before performing an upgrade.
For more information, see the Sample Readiness Report..
Note:
Alternatively, you can run the readiness check in -response mode to perform a silent readiness check using a response file. For more information on using a response file with the Upgrade Assistant, see Starting the Upgrade Assistant in Response File Mode.You can run the readiness check while your existing Oracle Fusion Middleware domain is online (while other users are actively using it), or offline.
Readiness checks can be run any number of times before any actual upgrades are attempted. However, do not run the readiness check after an upgrade has been performed, as the report will not provide valid results.
Note:
Oracle recommends that you run the readiness checks during off-peak hours to prevent possible performance degradation.
3.3.1.1 Starting the Upgrade Assistant in Readiness Mode
To perform a readiness check on your pre-upgrade environment, you will launch the Upgrade Assistant in -readiness mode as shown below:
-
Change directory to
$ORACLE_HOME/oracle_common/upgrade/binon UNIX operating systems or%ORACLE_HOME%/oracle_common/upgrade/binon Windows operating systems. -
Enter the following command to start the Upgrade Assistant.
On UNIX operating systems:
./ua -readinessOn Windows operating systems:
ua.bat -readinessProvide the required information in each of the Upgrade Assistant screens. The screens you see will vary depending on the upgrade options you select. The sections below describe the upgrade options and the information you will need to provide.
3.3.1.2 Performing the Readiness Check
When the Upgrade Assistant is started in -readiness mode, the following screens appear.
Alternatively, you can run the readiness check using a response file. For more information on using a response file with the Upgrade Assistant, see Starting the Upgrade Assistant in Response File Mode.
Note that these screens are a subset of the screens you will see.
Table 3-1 Upgrade Assistant Screens: Readiness Check
| Screen | When Screen Appears | Description |
|---|---|---|
|
Always. |
This screen provides an overview of the readiness check. |
|
|
Readiness Check Type:
|
Always. |
Readiness checks are only performed on schemas or component configurations that are at a supported upgrade starting point. There are two options to choose from. These options are described below:
|
|
When Individually Selected Schemas option is selected. |
This screen lists the available components for which the schemas will be selected. If you select something here, readiness check will be performed on that component's schema. |
|
|
Always. |
Use this screen to enter information required to connect to the selected schema and the database that hosts the schema. If the schema that is to be upgraded was created by RCU in a prior Fusion Middleware release then you will see a drop-down menu listing the possible schema names. |
|
|
Always. |
This screen provides a high-level overview of the readiness checks to be performed based on your selections. Click Save Response File if you plan to run the Upgrade Assistant again in —response (or silent) mode. |
|
|
Always. |
This screen displays the current status of the readiness check. Depending on what you have selected to check, the process can take several minutes. For a detailed report, click View Readiness Report. This button appears only after all the readiness checks are complete. Caution: To prevent performance degradation, consider running the readiness check during off-peak hours. |
|
|
If the readiness check completes successfully. |
You can now review the complete report. If the readiness check encounters an issue or error, review the log file to identify the issues, correct the issues, and then restart the readiness check. |
3.3.1.3 Understanding the Readiness Report
Now that you have completed the readiness checks for your domain, review the report to determine what actions - if any - need to be taken before the completion of a successful upgrade.
Each Readiness Report contains the following information:
| Report Information | Description | Required Action |
|---|---|---|
| Overall Readiness Status: SUCCESS or FAILURE | The top of the report indicates whether the Upgrade readiness check passed or completed with one or more errors. | If the report completed with one or more errors, search for FAIL and correct the failing issues before attempting to upgrade. You can re-run the readiness check as many times as necessary before an upgrade. |
|
Timestamp |
This is the date and time that the report was generated. |
No action required. |
|
Log file location |
This is the directory location of the generated log file. |
No action required. |
|
Readiness Report location |
This is the directory location of the generated readiness report. |
No action required. |
|
Names of components that were checked |
The names and versions of the components included in the check and status. |
If your domain includes components that cannot be upgraded to this release, such as SOA Core Extension, then do not attempt an upgrade. |
|
Names of schemas that were checked |
The names and current versions of the schemas included in the check and status. |
Review the version numbers of your schemas. If your domain includes schemas that cannot be upgraded to this release, then do not attempt an upgrade. |
|
Status: FAIL |
The individual readiness check test detected an issue. |
Do not upgrade until all FAILED issues have been resolved. |
|
Status: PASS |
The readiness check test detected no issues. |
If your readiness check report shows only the PASS status, then you can upgrade your environment. Note, however, that the Readiness Check cannot detect issues with externals such as hardware or connectivity during an upgrade. You should always monitor the progress of your upgrade. |
Upgrade readiness check completed with one or more errors.
This readiness check report was created on Tue May 30 11:15:52 EDT 2016
Log file is located at: /scratch/yourname/oracle/work/middleware_latest/oracle_common/upgrade/logs/ua2016-05-30-11-14-06AM.log
Readiness Check Report File: /scratch/yourname/oracle/work/middleware_latest/oracle_common/upgrade/logs/readiness2016-05-30-11-15-52AM.txt
Starting readiness check of components.
Oracle Metadata Services
Starting readiness check of Oracle Metadata Services.
Schema User Name: DEV11_MDS
Database Type: Oracle Database
Database Connect String: machinename@yourcompany.com
VERSION Schema DEV11_MDS is currently at version 12.1.1.1.0. Readiness checks will now be performed.
Starting schema test: TEST_REQUIRED_TABLES Test that the schema contains all the required tables
Completed schema test: TEST_REQUIRED_TABLES --> Test that the schema contains all the required tables +++ PASS
Starting schema test: TEST_REQUIRED_PROCEDURES Test that the schema contains all the required stored procedures
EXCEPTION Schema is missing a required procedure: GETREPOSITORYFEATURES
Completed schema test: TEST_REQUIRED_PROCEDURES --> Test that the schema contains all the required stored procedures +++ FAIL
Starting schema test: TEST_REQUIRED_VIEWS Test that the schema contains all the required database views
Completed schema test: TEST_REQUIRED_VIEWS --> Test that the schema contains all the required database views +++ PASS
Starting index test for table MDS_ATTRIBUTES: TEST_REQUIRED_INDEXES --> Test that the table contains all the required indexes
Completed index test for table MDS_ATTRIBUTES: TEST_REQUIRED_INDEXES --> Test that the table contains all the required indexes +++ PASS
Starting index test for table MDS_COMPONENTS: TEST_REQUIRED_INDEXES --> Test that the table contains all the required indexes
Completed index test for table MDS_COMPONENTS: TEST_REQUIRED_INDEXES --> Test that the table contains all the required indexes +++ PASS
Starting index test for table MDS_DEPENDENCIES: TEST_REQUIRED_INDEXES --> Test that the table contains all the required indexes
Completed index test for table MDS_DEPENDENCIES: TEST_REQUIRED_INDEXES --> Test that the table contains all the required indexes +++ PASS
Starting index test for table MDS_DEPL_LINEAGES: TEST_REQUIRED_INDEXES --> Test that the table contains all the required indexes
Completed index test for table MDS_DEPL_LINEAGES: TEST_REQUIRED_INDEXES --> Test that the table contains all the required indexes +++ PASS
Starting index test for table MDS_LABELS: TEST_REQUIRED_INDEXES --> Test that the table contains all the required indexes
Completed index test for table MDS_LABELS: TEST_REQUIRED_INDEXES --> Test that the table contains all the required indexes +++ PASS
Starting index test for table MDS_LARGE_ATTRIBUTES: TEST_REQUIRED_INDEXES --> Test that the table contains all the required indexes
Completed index test for table MDS_LARGE_ATTRIBUTES: TEST_REQUIRED_INDEXES --> Test that the table contains all the required indexes +++ PASS
Starting index test for table MDS_METADATA_DOCS: TEST_REQUIRED_INDEXES --> Test that the table contains all the required indexes
Completed index test for table MDS_METADATA_DOCS: TEST_REQUIRED_INDEXES --> Test that the table contains all the required indexes +++ PASS
Starting index test for table MDS_NAMESPACES: TEST_REQUIRED_INDEXES --> Test that the table contains all the required indexes
Completed index test for table MDS_NAMESPACES: TEST_REQUIRED_INDEXES --> Test that the table contains all the required indexes +++ PASS
Starting index test for table MDS_PARTITIONS: TEST_REQUIRED_INDEXES --> Test that the table contains all the required indexes
Completed index test for table MDS_PARTITIONS: TEST_REQUIRED_INDEXES --> Test that the table contains all the required indexes +++ PASS
Starting index test for table MDS_PATHS: TEST_REQUIRED_INDEXES --> Test that the table contains all the required indexes
Completed index test for table MDS_PATHS: TEST_REQUIRED_INDEXES --> Test that the table contains all the required indexes +++ PASS
Starting index test for table MDS_PURGE_PATHS: TEST_REQUIRED_INDEXES --> Test that the table contains all the required indexes
Completed index test for table MDS_PURGE_PATHS: TEST_REQUIRED_INDEXES --> Test that the table contains all the required indexes +++ PASS
Starting index test for table MDS_SANDBOXES: TEST_REQUIRED_INDEXES --> Test that the table contains all the required indexes
Completed index test for table MDS_SANDBOXES: TEST_REQUIRED_INDEXES --> Test that the table contains all the required indexes +++ PASS
Starting index test for table MDS_STREAMED_DOCS: TEST_REQUIRED_INDEXES --> Test that the table contains all the required indexes
Completed index test for table MDS_STREAMED_DOCS: TEST_REQUIRED_INDEXES --> Test that the table contains all the required indexes +++ PASS
Starting index test for table MDS_TRANSACTIONS: TEST_REQUIRED_INDEXES --> Test that the table contains all the required indexes
Completed index test for table MDS_TRANSACTIONS: TEST_REQUIRED_INDEXES --> Test that the table contains all the required indexes +++ PASS
Starting index test for table MDS_TXN_LOCKS: TEST_REQUIRED_INDEXES --> Test that the table contains all the required indexes
Completed index test for table MDS_TXN_LOCKS: TEST_REQUIRED_INDEXES --> Test that the table contains all the required indexes +++ PASS
Starting schema test: TEST_REQUIRED_TRIGGERS Test that the schema has all the required triggers
Completed schema test: TEST_REQUIRED_TRIGGERS --> Test that the schema has all the required triggers +++ PASS
Starting schema test: TEST_MISSING_COLUMNS Test that tables and views are not missing any required columns
Completed schema test: TEST_MISSING_COLUMNS --> Test that tables and views are not missing any required columns +++ PASS
Starting schema test: TEST_UNEXPECTED_TABLES Test that the schema does not contain any unexpected tables
Completed schema test: TEST_UNEXPECTED_TABLES --> Test that the schema does not contain any unexpected tables +++ PASS
Starting schema test: TEST_UNEXPECTED_PROCEDURES Test that the schema does not contain any unexpected stored procedures
Completed schema test: TEST_UNEXPECTED_PROCEDURES --> Test that the schema does not contain any unexpected stored procedures +++ PASS
Starting schema test: TEST_UNEXPECTED_VIEWS Test that the schema does not contain any unexpected views
Completed schema test: TEST_UNEXPECTED_VIEWS --> Test that the schema does not contain any unexpected views +++ PASS
Starting index test for table MDS_ATTRIBUTES: TEST_UNEXPECTED_INDEXES --> Test that the table does not contain any unexpected indexes
Completed index test for table MDS_ATTRIBUTES: TEST_UNEXPECTED_INDEXES --> Test that the table does not contain any unexpected indexes +++ PASS
Starting index test for table MDS_COMPONENTS: TEST_UNEXPECTED_INDEXES --> Test that the table does not contain any unexpected indexes
Completed index test for table MDS_COMPONENTS: TEST_UNEXPECTED_INDEXES --> Test that the table does not contain any unexpected indexes +++ PASS
Starting index test for table MDS_DEPENDENCIES: TEST_UNEXPECTED_INDEXES --> Test that the table does not contain any unexpected indexes
Completed index test for table MDS_DEPENDENCIES: TEST_UNEXPECTED_INDEXES --> Test that the table does not contain any unexpected indexes +++ PASS
Starting index test for table MDS_DEPL_LINEAGES: TEST_UNEXPECTED_INDEXES --> Test that the table does not contain any unexpected indexes
Completed index test for table MDS_DEPL_LINEAGES: TEST_UNEXPECTED_INDEXES --> Test that the table does not contain any unexpected indexes +++ PASS
Starting index test for table MDS_LABELS: TEST_UNEXPECTED_INDEXES --> Test that the table does not contain any unexpected indexes
Completed index test for table MDS_LABELS: TEST_UNEXPECTED_INDEXES --> Test that the table does not contain any unexpected indexes +++ PASS
Starting index test for table MDS_LARGE_ATTRIBUTES: TEST_UNEXPECTED_INDEXES --> Test that the table does not contain any unexpected indexes
Completed index test for table MDS_LARGE_ATTRIBUTES: TEST_UNEXPECTED_INDEXES --> Test that the table does not contain any unexpected indexes +++ PASS
Starting index test for table MDS_METADATA_DOCS: TEST_UNEXPECTED_INDEXES --> Test that the table does not contain any unexpected indexes
Completed index test for table MDS_METADATA_DOCS: TEST_UNEXPECTED_INDEXES --> Test that the table does not contain any unexpected indexes +++ PASS
Starting index test for table MDS_NAMESPACES: TEST_UNEXPECTED_INDEXES --> Test that the table does not contain any unexpected indexes
Completed index test for table MDS_NAMESPACES: TEST_UNEXPECTED_INDEXES --> Test that the table does not contain any unexpected indexes +++ PASS
Starting index test for table MDS_PARTITIONS: TEST_UNEXPECTED_INDEXES --> Test that the table does not contain any unexpected indexes
Completed index test for table MDS_PARTITIONS: TEST_UNEXPECTED_INDEXES --> Test that the table does not contain any unexpected indexes +++ PASS
Starting index test for table MDS_PATHS: TEST_UNEXPECTED_INDEXES --> Test that the table does not contain any unexpected indexes
Completed index test for table MDS_PATHS: TEST_UNEXPECTED_INDEXES --> Test that the table does not contain any unexpected indexes +++ PASS
Starting index test for table MDS_PURGE_PATHS: TEST_UNEXPECTED_INDEXES --> Test that the table does not contain any unexpected indexes
Completed index test for table MDS_PURGE_PATHS: TEST_UNEXPECTED_INDEXES --> Test that the table does not contain any unexpected indexes +++ PASS
Starting index test for table MDS_SANDBOXES: TEST_UNEXPECTED_INDEXES --> Test that the table does not contain any unexpected indexes
Completed index test for table MDS_SANDBOXES: TEST_UNEXPECTED_INDEXES --> Test that the table does not contain any unexpected indexes +++ PASS
Starting index test for table MDS_STREAMED_DOCS: TEST_UNEXPECTED_INDEXES --> Test that the table does not contain any unexpected indexes
Completed index test for table MDS_STREAMED_DOCS: TEST_UNEXPECTED_INDEXES --> Test that the table does not contain any unexpected indexes +++ PASS
Starting index test for table MDS_TRANSACTIONS: TEST_UNEXPECTED_INDEXES --> Test that the table does not contain any unexpected indexes
Completed index test for table MDS_TRANSACTIONS: TEST_UNEXPECTED_INDEXES --> Test that the table does not contain any unexpected indexes +++ PASS
Starting index test for table MDS_TXN_LOCKS: TEST_UNEXPECTED_INDEXES --> Test that the table does not contain any unexpected indexes
Completed index test for table MDS_TXN_LOCKS: TEST_UNEXPECTED_INDEXES --> Test that the table does not contain any unexpected indexes +++ PASS
Starting schema test: TEST_UNEXPECTED_TRIGGERS Test that the schema does not contain any unexpected triggers
Completed schema test: TEST_UNEXPECTED_TRIGGERS --> Test that the schema does not contain any unexpected triggers +++ PASS
Starting schema test: TEST_UNEXPECTED_COLUMNS Test that tables and views do not contain any unexpected columns
Completed schema test: TEST_UNEXPECTED_COLUMNS --> Test that tables and views do not contain any unexpected columns +++ PASS
Starting datatype test for table MDS_ATTRIBUTES: TEST_COLUMN_DATATYPES_V2 --> Test that all table columns have the proper datatypes
Completed datatype test for table MDS_ATTRIBUTES: TEST_COLUMN_DATATYPES_V2 --> Test that all table columns have the proper datatypes +++ PASS
Starting datatype test for table MDS_COMPONENTS: TEST_COLUMN_DATATYPES_V2 --> Test that all table columns have the proper datatypes
Completed datatype test for table MDS_COMPONENTS: TEST_COLUMN_DATATYPES_V2 --> Test that all table columns have the proper datatypes +++ PASS
Starting datatype test for table MDS_DEPENDENCIES: TEST_COLUMN_DATATYPES_V2 --> Test that all table columns have the proper datatypes
Completed datatype test for table MDS_DEPENDENCIES: TEST_COLUMN_DATATYPES_V2 --> Test that all table columns have the proper datatypes +++ PASS
Starting datatype test for table MDS_DEPL_LINEAGES: TEST_COLUMN_DATATYPES_V2 --> Test that all table columns have the proper datatypes
Completed datatype test for table MDS_DEPL_LINEAGES: TEST_COLUMN_DATATYPES_V2 --> Test that all table columns have the proper datatypes +++ PASS
Starting datatype test for table MDS_LABELS: TEST_COLUMN_DATATYPES_V2 --> Test that all table columns have the proper datatypes
Completed datatype test for table MDS_LABELS: TEST_COLUMN_DATATYPES_V2 --> Test that all table columns have the proper datatypes +++ PASS
Starting datatype test for table MDS_LARGE_ATTRIBUTES: TEST_COLUMN_DATATYPES_V2 --> Test that all table columns have the proper datatypes
Completed datatype test for table MDS_LARGE_ATTRIBUTES: TEST_COLUMN_DATATYPES_V2 --> Test that all table columns have the proper datatypes +++ PASS
Starting datatype test for table MDS_METADATA_DOCS: TEST_COLUMN_DATATYPES_V2 --> Test that all table columns have the proper datatypes
Completed datatype test for table MDS_METADATA_DOCS: TEST_COLUMN_DATATYPES_V2 --> Test that all table columns have the proper datatypes +++ PASS
Starting datatype test for table MDS_NAMESPACES: TEST_COLUMN_DATATYPES_V2 --> Test that all table columns have the proper datatypes
Completed datatype test for table MDS_NAMESPACES: TEST_COLUMN_DATATYPES_V2 --> Test that all table columns have the proper datatypes +++ PASS
Starting datatype test for table MDS_PARTITIONS: TEST_COLUMN_DATATYPES_V2 --> Test that all table columns have the proper datatypes
Completed datatype test for table MDS_PARTITIONS: TEST_COLUMN_DATATYPES_V2 --> Test that all table columns have the proper datatypes +++ PASS
Starting datatype test for table MDS_PATHS: TEST_COLUMN_DATATYPES_V2 --> Test that all table columns have the proper datatypes
Completed datatype test for table MDS_PATHS: TEST_COLUMN_DATATYPES_V2 --> Test that all table columns have the proper datatypes +++ PASS
Starting datatype test for table MDS_PURGE_PATHS: TEST_COLUMN_DATATYPES_V2 --> Test that all table columns have the proper datatypes
Completed datatype test for table MDS_PURGE_PATHS: TEST_COLUMN_DATATYPES_V2 --> Test that all table columns have the proper datatypes +++ PASS
Starting datatype test for table MDS_SANDBOXES: TEST_COLUMN_DATATYPES_V2 --> Test that all table columns have the proper datatypes
Completed datatype test for table MDS_SANDBOXES: TEST_COLUMN_DATATYPES_V2 --> Test that all table columns have the proper datatypes +++ PASS
Starting datatype test for table MDS_STREAMED_DOCS: TEST_COLUMN_DATATYPES_V2 --> Test that all table columns have the proper datatypes
Completed datatype test for table MDS_STREAMED_DOCS: TEST_COLUMN_DATATYPES_V2 --> Test that all table columns have the proper datatypes +++ PASS
Starting datatype test for table MDS_TRANSACTIONS: TEST_COLUMN_DATATYPES_V2 --> Test that all table columns have the proper datatypes
Completed datatype test for table MDS_TRANSACTIONS: TEST_COLUMN_DATATYPES_V2 --> Test that all table columns have the proper datatypes +++ PASS
Starting datatype test for table MDS_TXN_LOCKS: TEST_COLUMN_DATATYPES_V2 --> Test that all table columns have the proper datatypes
Completed datatype test for table MDS_TXN_LOCKS: TEST_COLUMN_DATATYPES_V2 --> Test that all table columns have the proper datatypes +++ PASS
Starting permissions test for table MDS_ATTRIBUTES: TEST_TABLE_GRANTS --> Test that tables have the proper GRANT permissions
Completed permissions test for table MDS_ATTRIBUTES: TEST_TABLE_GRANTS --> Test that tables have the proper GRANT permissions +++ PASS
Starting permissions test for table MDS_COMPONENTS: TEST_TABLE_GRANTS --> Test that tables have the proper GRANT permissions
Completed permissions test for table MDS_COMPONENTS: TEST_TABLE_GRANTS --> Test that tables have the proper GRANT permissions +++ PASS
Starting permissions test for table MDS_DEPENDENCIES: TEST_TABLE_GRANTS --> Test that tables have the proper GRANT permissions
Completed permissions test for table MDS_DEPENDENCIES: TEST_TABLE_GRANTS --> Test that tables have the proper GRANT permissions +++ PASS
Starting permissions test for table MDS_DEPL_LINEAGES: TEST_TABLE_GRANTS --> Test that tables have the proper GRANT permissions
Completed permissions test for table MDS_DEPL_LINEAGES: TEST_TABLE_GRANTS --> Test that tables have the proper GRANT permissions +++ PASS
Starting permissions test for table MDS_LABELS: TEST_TABLE_GRANTS --> Test that tables have the proper GRANT permissions
Completed permissions test for table MDS_LABELS: TEST_TABLE_GRANTS --> Test that tables have the proper GRANT permissions +++ PASS
Starting permissions test for table MDS_LARGE_ATTRIBUTES: TEST_TABLE_GRANTS --> Test that tables have the proper GRANT permissions
Completed permissions test for table MDS_LARGE_ATTRIBUTES: TEST_TABLE_GRANTS --> Test that tables have the proper GRANT permissions +++ PASS
Starting permissions test for table MDS_METADATA_DOCS: TEST_TABLE_GRANTS --> Test that tables have the proper GRANT permissions
Completed permissions test for table MDS_METADATA_DOCS: TEST_TABLE_GRANTS --> Test that tables have the proper GRANT permissions +++ PASS
Starting permissions test for table MDS_NAMESPACES: TEST_TABLE_GRANTS --> Test that tables have the proper GRANT permissions
Completed permissions test for table MDS_NAMESPACES: TEST_TABLE_GRANTS --> Test that tables have the proper GRANT permissions +++ PASS
Starting permissions test for table MDS_PARTITIONS: TEST_TABLE_GRANTS --> Test that tables have the proper GRANT permissions
Completed permissions test for table MDS_PARTITIONS: TEST_TABLE_GRANTS --> Test that tables have the proper GRANT permissions +++ PASS
Starting permissions test for table MDS_PATHS: TEST_TABLE_GRANTS --> Test that tables have the proper GRANT permissions
Completed permissions test for table MDS_PATHS: TEST_TABLE_GRANTS --> Test that tables have the proper GRANT permissions +++ PASS
Starting permissions test for table MDS_PURGE_PATHS: TEST_TABLE_GRANTS --> Test that tables have the proper GRANT permissions
Completed permissions test for table MDS_PURGE_PATHS: TEST_TABLE_GRANTS --> Test that tables have the proper GRANT permissions +++ PASS
Starting permissions test for table MDS_SANDBOXES: TEST_TABLE_GRANTS --> Test that tables have the proper GRANT permissions
Completed permissions test for table MDS_SANDBOXES: TEST_TABLE_GRANTS --> Test that tables have the proper GRANT permissions +++ PASS
Starting permissions test for table MDS_STREAMED_DOCS: TEST_TABLE_GRANTS --> Test that tables have the proper GRANT permissions
Completed permissions test for table MDS_STREAMED_DOCS: TEST_TABLE_GRANTS --> Test that tables have the proper GRANT permissions +++ PASS
Starting permissions test for table MDS_TRANSACTIONS: TEST_TABLE_GRANTS --> Test that tables have the proper GRANT permissions
Completed permissions test for table MDS_TRANSACTIONS: TEST_TABLE_GRANTS --> Test that tables have the proper GRANT permissions +++ PASS
Starting permissions test for table MDS_TXN_LOCKS: TEST_TABLE_GRANTS --> Test that tables have the proper GRANT permissions
Completed permissions test for table MDS_TXN_LOCKS: TEST_TABLE_GRANTS --> Test that tables have the proper GRANT permissions +++ PASS
Starting permissions test: TEST_DBA_TABLE_GRANTS Test that DBA user has privilege to view all user tables
Completed permissions test: TEST_DBA_TABLE_GRANTS --> Test that DBA user has privilege to view all user tables +++ PASS
Starting schema test: TEST_ENOUGH_TABLESPACE Test that the schema tablespaces automatically extend if full
Completed schema test: TEST_ENOUGH_TABLESPACE --> Test that the schema tablespaces automatically extend if full +++ PASS
Starting schema test: TEST_USER_TABLESPACE_QUOTA Test that tablespace quota for this user is sufficient to perform the upgrade
Completed schema test: TEST_USER_TABLESPACE_QUOTA --> Test that tablespace quota for this user is sufficient to perform the upgrade +++ PASS
Starting schema test: TEST_ONLINE_TABLESPACE Test that schema tablespaces are online
Completed schema test: TEST_ONLINE_TABLESPACE --> Test that schema tablespaces are online +++ PASS
Starting schema test: TEST_DATABASE_VERSION Test that the database server version number is supported for upgrade
INFO Database product version: Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
Completed schema test: TEST_DATABASE_VERSION --> Test that the database server version number is supported for upgrade +++ PASS
Finished readiness check of Oracle Metadata Services with status: FAILURE.
Common Infrastructure Services
Starting readiness check of Common Infrastructure Services.
Schema User Name: DEV1212_STB
Database Type: Oracle Database
Database Connect String: machinename@yourcompany.com
VERSION Schema STB is currently at version 12.1.2.0.0. Readiness checks will now be performed.
Starting schema test: TEST_REQUIRED_TABLES Test that the schema contains all the required tables
Completed schema test: TEST_REQUIRED_TABLES --> Test that the schema contains all the required tables +++ PASS
Completed schema test: TEST_REQUIRED_TABLES --> Test that the schema contains all the required tables +++ PASS
Starting schema test: TEST_UNEXPECTED_TABLES Test that the schema does not contain any unexpected tables
Completed schema test: TEST_UNEXPECTED_TABLES --> Test that the schema does not contain any unexpected tables +++ PASS
Starting schema test: TEST_REQUIRED_VIEWS Test that the schema contains all the required database views
Completed schema test: TEST_REQUIRED_VIEWS --> Test that the schema contains all the required database views +++ PASS
Starting schema test: TEST_MISSING_COLUMNS Test that tables and views are not missing any required columns
Completed schema test: TEST_MISSING_COLUMNS --> Test that tables and views are not missing any required columns +++ PASS
Starting schema test: TEST_UNEXPECTED_COLUMNS Test that tables and views do not contain any unexpected columns
Completed schema test: TEST_UNEXPECTED_COLUMNS --> Test that tables and views do not contain any unexpected columns +++ PASS
Starting schema test: TEST_UNEXPECTED_PROCEDURES Test that the schema does not contain any unexpected stored procedures
Completed schema test: TEST_UNEXPECTED_PROCEDURES --> Test that the schema does not contain any unexpected stored procedures +++ PASS
Starting permissions test: TEST_DBA_TABLE_GRANTS Test that DBA user has privilege to view all user tables
Starting permissions test: TEST_DBA_TABLE_GRANTS Test that DBA user has privilege to view all user tables
Completed permissions test: TEST_DBA_TABLE_GRANTS --> Test that DBA user has privilege to view all user tables +++ PASS
Completed permissions test: TEST_DBA_TABLE_GRANTS --> Test that DBA user has privilege to view all user tables +++ PASS
Starting permissions test for table COMPONENT_SCHEMA_INFO: TEST_TABLE_GRANTS --> Test that tables have the proper GRANT permissions
Completed permissions test for table TEST_TABLE_GRANTS: Test that tables have the proper GRANT permissions --> PASS +++ {3}
Starting permissions test for table SERVICETABLE: TEST_TABLE_GRANTS --> Test that tables have the proper GRANT permissions
Completed permissions test for table TEST_TABLE_GRANTS: Test that tables have the proper GRANT permissions --> PASS +++ {3}
Starting datatype test for table COMPONENT_SCHEMA_INFO: TEST_COLUMN_DATATYPES_V2 --> Test that all table columns have the proper datatypes
Completed datatype test for table COMPONENT_SCHEMA_INFO: TEST_COLUMN_DATATYPES_V2 --> Test that all table columns have the proper datatypes +++ PASS
Starting datatype test for table SERVICETABLE: TEST_COLUMN_DATATYPES_V2 --> Test that all table columns have the proper datatypes
Completed datatype test for table SERVICETABLE: TEST_COLUMN_DATATYPES_V2 --> Test that all table columns have the proper datatypes +++ PASS
Starting index test for table COMPONENT_SCHEMA_INFO: TEST_REQUIRED_INDEXES --> Test that the table contains all the required indexes
Completed index test for table COMPONENT_SCHEMA_INFO: TEST_REQUIRED_INDEXES --> Test that the table contains all the required indexes +++ PASS
Starting index test for table COMPONENT_SCHEMA_INFO: TEST_UNEXPECTED_INDEXES --> Test that the table does not contain any unexpected indexes
Completed index test for table COMPONENT_SCHEMA_INFO: TEST_UNEXPECTED_INDEXES --> Test that the table does not contain any unexpected indexes +++ PASS
Starting index test for table SERVICETABLE: TEST_REQUIRED_INDEXES --> Test that the table contains all the required indexes
Completed index test for table SERVICETABLE: TEST_REQUIRED_INDEXES --> Test that the table contains all the required indexes +++ PASS
Starting index test for table SERVICETABLE: TEST_UNEXPECTED_INDEXES --> Test that the table does not contain any unexpected indexes
Completed index test for table SERVICETABLE: TEST_UNEXPECTED_INDEXES --> Test that the table does not contain any unexpected indexes +++ PASS
Starting schema test: TEST_UNEXPECTED_TRIGGERS Test that the schema does not contain any unexpected triggers
Completed schema test: TEST_UNEXPECTED_TRIGGERS --> Test that the schema does not contain any unexpected triggers +++ PASS
Starting schema test: TEST_ENOUGH_TABLESPACE Test that the schema tablespaces automatically extend if full
Starting schema test: TEST_ENOUGH_TABLESPACE Test that the schema tablespaces automatically extend if full
Completed schema test: TEST_ENOUGH_TABLESPACE --> Test that the schema tablespaces automatically extend if full +++ PASS
Completed schema test: TEST_ENOUGH_TABLESPACE --> Test that the schema tablespaces automatically extend if full +++ PASS
Starting schema test: TEST_ONLINE_TABLESPACE Test that schema tablespaces are online
Starting schema test: TEST_ONLINE_TABLESPACE Test that schema tablespaces are online
Completed schema test: TEST_ONLINE_TABLESPACE --> Test that schema tablespaces are online +++ PASS
Completed schema test: TEST_ONLINE_TABLESPACE --> Test that schema tablespaces are online +++ PASS
Starting schema test: TEST_USER_TABLESPACE_QUOTA Test that tablespace quota for this user is sufficient to perform the upgrade
Starting schema test: TEST_USER_TABLESPACE_QUOTA Test that tablespace quota for this user is sufficient to perform the upgrade
Completed schema test: TEST_USER_TABLESPACE_QUOTA --> Test that tablespace quota for this user is sufficient to perform the upgrade +++ PASS
Completed schema test: TEST_USER_TABLESPACE_QUOTA --> Test that tablespace quota for this user is sufficient to perform the upgrade +++ PASS
Starting schema test: TEST_DATABASE_VERSION Test that the database server version number is supported for upgrade
Starting schema test: TEST_DATABASE_VERSION Test that the database server version number is supported for upgrade
INFO Database product version: Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
Completed schema test: TEST_DATABASE_VERSION --> Test that the database server version number is supported for upgrade +++ PASS
Completed schema test: TEST_DATABASE_VERSION --> Test that the database server version number is supported for upgrade +++ PASS
Finished readiness check of Common Infrastructure Services with status: SUCCESS.
Finished readiness check of components.
3.3.2 Readiness Check Screens
This section describes the screens that are presented when running the Upgrade Assistant in -readiness mode.
The Upgrade Assistant can be run in -readiness mode before you perform the actual upgrade to detect any potential problems with the pre-upgrade environment.
- Welcome
- Readiness Check Type: Individually Selected Schemas
- Readiness Check Type: Domain Based
The Domain Based option is used to check all of the upgrade-eligible schemas and/or component configurations used by the domain. The Upgrade Assistant detects all of the schemas for you. You can check schemas and component configurations at the same time. Or, if you prefer, you can select one or the other. In either case, you must specify the Domain Directory that is to be reviewed. - Available Components
This screen appears if you select Individually Selected Schemas in the Schemas screen. - Schema Credentials
- Readiness Summary
- Readiness Check
- Log Viewer
- Readiness Success
- Sample Readiness Report
3.3.2.1 Welcome
The Upgrade Assistant Readiness Check performs a read-only, pre-upgrade review of your existing Oracle Fusion Middleware schemas and Oracle WebLogic component configurations.
The Readiness Check provides a formatted, time-stamped Readiness Report so you can address any issues before you attempt the actual upgrade. If no issues are detected, you can begin the upgrade process.
The Upgrade Assistant Readiness Check can be run with your existing 11g or 12c domain online or offline.
Note:
While readiness check ships with 12.2.1, it only checks supported pre-upgrade environments.The Readiness Check can be run any number of times before the actual upgrade is performed. However, do not run after the Readiness Check after an upgrade has been performed, as the report will not provide valid results.
Oracle recommends that you read this report thoroughly before performing an upgrade.
3.3.2.2 Readiness Check Type: Individually Selected Schemas
You have two options when running the readiness check:
-
Individually Selected Schemas
-
Domain Based
Select the Individually Selected Schemas option to limit the check to specific schemas. Click Next and you will be required to supply the schema credentials.
Readiness checks are performed on the schemas that you connect to. The readiness check report tells you whether a schems is supported for an upgrade, or where an upgrade is needed.
3.3.2.3 Readiness Check Type: Domain Based
The Domain Based option is used to check all of the upgrade-eligible schemas and/or component configurations used by the domain. The Upgrade Assistant detects all of the schemas for you. You can check schemas and component configurations at the same time. Or, if you prefer, you can select one or the other. In either case, you must specify the Domain Directory that is to be reviewed.
You have several options when checking the WebLogic Server domain.
You can select one - or more - of the following options each time you run the Domain Based Readiness Check:
-
Include checks for all schemas
Select this option to enable the Upgrade Assistant to discover and review all components that have a schema available to upgrade.
-
Include checks for all configurations
Select this option to review component configurations for a managed WebLogic Server domain.
You can perform domain configuration check even when the domain is online or offline.
-
Perform online and offline readiness checks.
Select this option to perform additional online readiness checks . This option will require your domain to be online. You must provide the domain's host name, port, user name, and password that you plan to check.If you do not select this option your domain can be offline. You must provide the domain location that you plan to check.
Figure 3-3 WebLogic Server Readiness Check Options
Description of "Figure 3-3 WebLogic Server Readiness Check Options"
3.3.2.4 Available Components
This screen appears if you select Individually Selected Schemas in the Schemas screen.
If you chose Individually Selected Schemas this screen lists the available components for which the schemas will be selected. If you select something here, readiness check will be performed on that component's schema. You must select one or more components from the list to perform readiness check on them.
3.3.2.5 Schema Credentials
Use this screen to enter information required to connect to the selected schema and the database that hosts the schema. If the schema that is to be reviewed was created by RCU in a prior Fusion Middleware release then you will see a drop-down menu listing the possible schema names as shown below.
Click Connect to connect to the database then select the schema to be reviewed. NOTE: Most schemas will have this information pre-populated. If, however, the Upgrade Assistant is unable to detect the connection details, then they must be entered manually as shown below.
If multiple components are selected, then the Schema Credential screens appear in dependency order.
3.3.2.6 Readiness Summary
This screen provides a high-level overview of the readiness checks performed based on your selections.
For a detailed report, click View Log.
3.3.2.7 Readiness Check
This screen shows the overall progress and completion details of the running readiness check. If you are checking multiple components, then each gets component will have its own progress bar and will be checked in parallel. Once completed, click View Readiness Report to see the full text report.
CAUTION: If you are running the readiness check on your online production environment, Oracle recommends that you perform the check during off-peak hours to prevent performance degradation.
3.3.2.8 Log Viewer
Click View Log from any of the screens to see the latest logged information.
The log file is managed by the command line options you set. See Starting the Upgrade Assistant with Additional Parameters (Optional) for more information.
3.3.2.9 Readiness Success
Readiness success indicates that the readiness review was successfully completed.
Even with a successful completion of the review, you should still click View Readiness Report and review the Readiness Report before you perform the actual upgrade.
Figure 3-9 End of Readiness: Readiness Success
Description of "Figure 3-9 End of Readiness: Readiness Success "
3.3.2.10 Sample Readiness Report
A formatted Readiness Report is prepared for you after running the check. Make sure that you review the report and correct any issues before you start the actual upgrade. Use the Find option to search for a particular word within the report (such as a schema name or command, for example.)
The report also indicates where the completed Readiness Check Report file is located.
3.4 Upgrading Schemas with the Upgrade Assistant
After you install the 12.2.1.1 product distributions, you must first upgrade the 12.2.1.0 schemas using the Upgrade Assistant. The Upgrade Assistant provides two options for upgrading schemas: Individually Selected Schemas and All Schemas Used By a Domain. However, for the topology defined in this document, you must select All Schemas Used By a Domain.
Individually Selected Schemas
This option enables you to select the component schemas you want to upgrade. Select this option when you have other component schemas within the domain that you do not want to upgrade.
All Schemas Used By a Domain
This option allows the Upgrade Assistant to detect all the available schemas within the specified domain and include them in the upgrade.
- Identifying Schemas that Can be Upgraded with the Upgrade Assistant
Review the list of available schemas before you begin the upgrade by querying the schema version registry. - Upgrading the Schemas with the Upgrade Assistant
Run the Upgrade Assistant to upgrade all the schemas in the 12.2.1.0 domain to 12.2.1.1.
3.4.1 Identifying Schemas that Can be Upgraded with the Upgrade Assistant
Review the list of available schemas before you begin the upgrade by querying the schema version registry.
This optional step can be used if you want to manually query the schema_version_registry table before you start the upgrade process. It is important to note that the Upgrade Assistant identifies all schemas that are available for an upgrade and allows you to select the individual schemas you want to upgrade or allow Upgrade Assistant to upgrade all of the schemas in the domain. In addition, when you run the Upgrade Assistant in —readiness mode, you will receive a report with all of the schemas and their current pre-upgrade versions.
If you are using an Oracle database, connect to the database as a user having Oracle DBA privileges, and run the following from SQL*Plus to get the current version numbers:
SET LINE 120 COLUMN MRC_NAME FORMAT A14 COLUMN COMP_ID FORMAT A20 COLUMN VERSION FORMAT A12 COLUMN STATUS FORMAT A9 COLUMN UPGRADED FORMAT A8 SELECT MRC_NAME, COMP_ID, OWNER, VERSION, STATUS, UPGRADED FROM SCHEMA_VERSION_REGISTRY ORDER BY MRC_NAME, COMP_ID ;
The following report is generated when saved to a SQL script, for example version.sql.
If the number in the "VERSION" is at 11.1.1.7.0 or higher, and the STATUS column is 'VALID', then the schema is supported for upgrade.
schema_version_registry table retains the schemas at their pre-upgrade version after the upgrade.
Tip:
Compare the information you collect from the schema version registry and the corresponding schemas to determine whether there are schemas in your domain that are not available for an upgrade yet.
Notes about the schemas that need to be upgraded
-
For most components, the only schema version starting points that are valid for upgrading are 11g Release 1 (1.1.1.7.0, 11.1.1.8.0, or 11.1.1.9.0) or 12c (12.1.2, 12.1.3, or 12.2.1.0). If your schemas are not at a supported version, then you must upgrade them before using the 12c (12.2.1.1) upgrade procedures.
Some components, such as Oracle Enterprise Data Quality and Oracle Golden Gate Veridata, support an upgrade from versions other than the standard Oracle Fusion Middleware supported versions.
Refer to your component-specific installation and upgrade documentation for additional information about the schemas that are required for your upgrade.
-
If you used an OID-based policy store in 11g, make sure that you create a new 12c (12.2.1.1) OPSS schema before you perform the upgrade. After the upgrade, the OPSS schema will still remain LDAP-based store.
-
You can only upgrade schemas for products that are available for upgrade in the Oracle Fusion Middleware 12c (12.2.1.1) release. Do not attempt to upgrade a domain that includes components that are not yet available for upgrade to 12c (12.2.1.1).
3.4.2 Upgrading the Schemas with the Upgrade Assistant
Run the Upgrade Assistant to upgrade all the schemas in the 12.2.1.0 domain to 12.2.1.1.
If you are using DB2 in your 12.2.1.0 BI instance, then perform the following before starting the upgrade process:
- Sign in to the WebLodic Console.
- Go to Datasources under Services and select wlsservices_datasource.
- Change the user for data source 'wlsservices_datasource' from <PREFIX>_WLS_RUNTIME to <PREFIX>_WLS.
For example: Change the user from L1_WLS_RUNTIME to L1_WLS.
You can now proceed with the upgrade process.
3.5 Backing up the mapViewerConfig.xml File
The mapViewerConfig.xml file is overwritten by the reconfiguration templates when you run the Reconfiguration Wizard. Therefore, you must back up the mapViewerConfig.xml file before reconfiguring your 12.2.1.0 domain.
3.6 Reconfiguring the BI Domain with the Reconfiguration Wizard
After upgrading the schemas, run the Reconfiguration Wizard on your existing domain to reconfigure it before upgrading the domain configuration.
3.7 Restoring the mapViewerConfig.xml File
The mapViewerConfig.xml file is overwritten when you run the Reconfiguration Wizard on your domain. You can know that the mapViewerConfig.xml file is overwritten by checking its file size. You must restore the original file that you backed up before upgrading your domain with the Upgrade Assistant.