Name Last modified Size Description
Parent Directory -
files/ 2017-09-30 02:42 -
README.txt 2017-10-03 07:19 11
Patch 26635944 - Oracle JavaVM Component Release Update 12.2.0.1.171017
This document describes how you can install Patch 26635944 - Oracle JavaVM Component Release Update (OJVM RU) 12.2.0.1.171017 on your Oracle Database 12c Release 2 (12.2.0.1.0).
This patch is not Oracle RAC Rolling installable.
This patch is Database Vault installable. Review My Oracle Support Document 1195205.1 for details on how to apply this patch to a Database Vault environment.
This patch is not Data Guard Standby First Installable.
This document is accurate at the time of release. For any changes and additional information regarding Oracle JavaVM Component Release Update 12.2.0.1.171017, see these related documents that are available at My Oracle Support (http://support.oracle.com/):
Document 2297779.1 Oracle JavaVM Component Release Update 12.2.0.1.171017 Known Issues
This document includes the following sections:
The Oracle JavaVM Component Release Update 12.2.0.1.171017 is cumulative and includes the Database CPU program security content.
Before you install or deinstall the patch, ensure that you meet the following requirements. For an Oracle RAC environment, meet these prerequisites on each of the nodes.
Read My Oracle Support Document 1929745.1 Oracle Recommended Patches -- "Oracle JavaVM Component Database PSU and RU" (OJVM PSU and OJVM RU) Patches.
Ensure that the Oracle Database on which you are installing the patch or from which you are rolling back the patch is Oracle Database 12c Release 2 (12.2.0.1.0).
You must use the OPatch utility version 12.2.0.1.7 or later to apply this patch. Oracle recommends that you use the latest released OPatch version for 12.2, which is available for download from My Oracle Support patch 6880880 by selecting the 12.2.0.1.0 release.
For information about OPatch documentation, including any known issues, see My Oracle Support Document 293369.1 OPatch documentation list.
Ensure that you set the ORACLE_HOME environment variable to the Oracle home of the Oracle Database.
Ensure that the $PATH definition has the following executables: make, ar, ld and nm. The location of these executables depends on your operating system. On many operating systems, they are located in /usr/ccs/bin.
Ensure that you verify the Oracle Inventory because OPatch accesses it to install the patches. To verify the inventory, run the following command. If the command displays some errors, then contact Oracle Support and resolve the issue.
$ opatch lsinventory
(Only for Installation) Maintain a location for storing the contents of the patch ZIP file. In the rest of the document, this location (absolute path) is referred to as PATCH_TOP_DIR. Extract the contents of the patch ZIP file to the location (PATCH_TOP_DIR) you have created above. To do so, run the following command:
$ unzip -d <PATCH_TOP_DIR> p26635944_12201_<PLATFORM_NAME>.zip
(Only for Installation) Determine whether any currently installed interim patches conflict with this patch 26635944 as shown as follows:
$ cd <PATCH_TOP_DIR>/26635944 $ opatch prereq CheckConflictAgainstOHWithDetail -ph ./
The report will indicate the patches that conflict with this patch and the patches for which the current 26635944 is a superset.
|
Note: When OPatch starts, it validates the patch and ensures that there are no conflicts with the software already installed in theORACLE_HOME. OPatch categorizes conflicts into the following types:
|
If this OJVM RU is going to be installed after the installation of a DB RUR patch, then ensure that the post install steps for the DB RUR patch have already been completed prior to installing this OJVM RU. See Issue 2 for more information.
Ensure that you shut down all the services running from the Oracle home.
For a Non Oracle RAC environment, shut down all databases and listeners associated with the Oracle home that you are updating. For more information, see Oracle Database Administrator's Guide.
For an Oracle RAC environment, shut down all the services (database, ASM, listeners, nodeapps, and CRS daemons) running from the Oracle home on all the nodes you want to patch. After all nodes are patched, start all services. OPatch is used on only one node at a time.
To install the patch, follow these steps.
Set your current directory to the directory where the patch is located and then run the OPatch utility by entering the following commands:
$ cd <PATCH_TOP_DIR>/26635944
Install the patch by running the following command:
$ opatch apply
If apply fails for make target jox_refresh_knlopt when applying the patch to the database home, see Issue #1 in Section 8, "Known Issues" for more information.
Verify whether the patch has been successfully installed by running the following command:
$ opatch lsinventory
Start the services from the Oracle home.
If there are errors, see Section 8, "Known Issues".
Perform the following postinstallation steps described in Section 4.1, "Loading Modified SQL Files Into the Database".
To perform the postinstallation, follow these steps:
The following steps load modified SQL files into the database.
Datapatch is run to complete the post-install SQL deployment for the RU. For further details about Datapatch, including Known Issues and workarounds to common problems, see: Database 12c Post Patch SQL Automation (Doc ID 1585822.1).
For each separate database running on the same shared Oracle home being patched, run the datapatch utility as described in Table 1.
Table 1 Steps to Run the Datapatch Utility for Standalone DB Versus Single/Multitenant (CDB/PDB) DB
| Steps | Standalone DB | Steps | Single/Multitenant (CDB/PDB) DB |
|---|---|---|---|
|
1 |
|
1 |
|
|
2 |
|
2 |
|
|
3 |
|
3 |
|
|
4 |
|
4 |
|
|
5 |
|
5 |
|
|
6 |
|
6 |
|
|
7 |
|
7 |
|
|
8 |
|
8 |
|
|
9 |
|
9 |
|
|
10 |
|
10 |
|
|
11 |
11 |
|
|
|
12 |
|
Footnote 1 For an Oracle RAC environment, see Starting the Database for Post Installation Steps in an Oracle RAC Environment.
Footnote 2 It is recommended the Post Install step be run on all pluggable databases; however, the following command (SQL> alter pluggable database PDB_NAME open upgrade) could be substituted to only open certain PDBs in the single/multitenant database. Doing so will result in the Post Install step only being run on the CDB and opened PDB's. To update a pluggable database at a later date (skipped or newly plugged in), open the database using the alter pluggable database command mentioned previously and rerun the datapatch utility. See My Oracle Support Document 1935365.1 Multitenant Unplug/Plug Best Practices for more information about the procedure for unplugging/plugging with different patch releases (in both directions).
Footnote 3 For an Oracle RAC environment, see Restarting the Database after Running the Post Installation Steps in an Oracle RAC Environment.
Starting the Database for Post Installation Steps in an Oracle RAC Environment
On only one node, perform the following steps to start an Oracle RAC database in startup upgrade mode.
sqlplus /nolog SQL> CONNECT / AS SYSDBA SQL> STARTUP SQL> alter system set cluster_database=false scope=spfile; $ORACLE_HOME/bin/srvctl stop database -d <dbname> sqlplus /nolog SQL> CONNECT / AS SYSDBA SQL> STARTUP UPGRADE
Restarting the Database after Running the Post Installation Steps in an Oracle RAC Environment
To start the database back in normal mode
sqlplus /nolog SQL> CONNECT / AS SYSDBA SQL> alter system set cluster_database=true scope=spfile; SQL> SHUTDOWN $ORACLE_HOME/bin/srvctl start database -d <dbname>
The datapatch utility will then run the necessary apply scripts to load the modified SQL files into the database. An entry will be added to the dba_registry_sqlpatch view reflecting the patch application. In the dba_registry_sqlpatch view, verify the Status for the APPLY is "SUCCESS". For any other status, refer to the following My Oracle Support note for additional information and actions: Document 1609718.1 Datapatch Known Issues.
Check the following log files in $ORACLE_BASE/cfgtoollogs/sqlpatch/26635944/<unique patch ID> for errors:
26635944_apply_<database SID>_<CDB name>_<timestamp>.log
where database SID is the database SID, CDB name is the name of the multitenant container database, and timestamp is of the form YYYYMMMDD_HH_MM_SS.
After installing the SQL portion of the patch, some packages could become INVALID. This will get recompiled upon access or you can run utlrp.sql to get them back into a VALID state.
cd $ORACLE_HOME/rdbms/admin sqlplus /nolog SQL> CONNECT / AS SYSDBA SQL> @utlrp.sql
If there are errors, see Section 8, "Known Issues".
You must execute the steps in Section 4, "Postinstallation" for any new database. There are no actions required for databases that have been upgraded.
Ensure to follow the Prerequisites as described in Section 2, "Prerequisites". To deinstall the patch, follow these steps. For an Oracle RAC environment, perform these steps on any one of the nodes:
Deinstall the patch by running the following command:
$ opatch rollback -id 26635944
Start the services from the Oracle home.
Ensure that you verify the Oracle Inventory and compare the output with the one run before the patch installation and re-apply any patches that were rolled back as part of this patch apply. To verify the inventory, run the following command:
$ opatch lsinventory
Perform the following post deinstallation steps described in Section 7.1, "Loading Modified SQL Files Into the Database".
The following steps load modified SQL files into the database.
For each separate database running on the same shared Oracle home being patched, run the datapatch utility as described in Table 2.
Table 2 Steps to Run the datapatch Utility for Standalone DB Versus Single/Multitenant (CDB/PDB) DB
| Steps | Standalone DB | Steps | Single/Multitenant (CDB/PDB) DB |
|---|---|---|---|
|
1 |
|
1 |
|
|
2 |
|
2 |
|
|
3 |
|
3 |
|
|
4 |
|
4 |
|
|
5 |
|
5 |
|
|
6 |
|
6 |
|
|
7 |
|
7 |
|
|
8 |
|
8 |
|
|
9 |
|
9 |
|
|
10 |
|
10 |
|
|
11 |
|
||
|
12 |
|
Footnote 1 For an Oracle RAC environment, see Starting the Database for Post Deinstallation Steps in an Oracle RAC Environment.
Footnote 2 It is recommended the Post Install step be run on all pluggable databases; however, the following command (SQL> alter pluggable database PDB_NAME open upgrade) could be substituted to only open certain PDBs in the single/multitenant database. Doing so will result in the Post Install step only being run on the CDB and opened PDB's. To update a pluggable database at a later date (skipped or newly plugged in), open the database using the alter pluggable database command mentioned previously and rerun the datapatch utility. See My Oracle Support Document 1935365.1 Multitenant Unplug/Plug Best Practices for more information about the procedure for unplugging/plugging with different patch releases (in both directions).
Footnote 3 For an Oracle RAC environment, see Restarting the Database after Running the Post Deinstallation Steps in an Oracle RAC Environment.
Starting the Database for Post Deinstallation Steps in an Oracle RAC Environment
On only one node, perform the following steps to start an Oracle RAC database in startup upgrade mode.
sqlplus /nolog SQL> CONNECT / AS SYSDBA SQL> STARTUP SQL> alter system set cluster_database=false scope=spfile; $ORACLE_HOME/bin/srvctl stop database -d <dbname> sqlplus /nolog SQL> CONNECT / AS SYSDBA SQL> STARTUP UPGRADE
Restarting the Database after Running the Post Deinstallation Steps in an Oracle RAC Environment
To start the database back in normal mode
sqlplus /nolog SQL> CONNECT / AS SYSDBA SQL> alter system set cluster_database=true scope=spfile; SQL> SHUTDOWN $ORACLE_HOME/bin/srvctl start database -d <dbname>
The datapatch utility will then run the necessary apply scripts to load the modified SQL files into the database. An entry will be added to the dba_registry_sqlpatch view reflecting the patch application. In the dba_registry_sqlpatch view, verify the Status for the APPLY is "SUCCESS". For any other status, refer to the following My Oracle Support note for additional information and actions: Document 1609718.1 Datapatch Known Issues.
Check the following log files in $ORACLE_HOME/sqlpatch/26635944/ for errors:
26635944_rollback_<database SID>_<CDB name>_<timestamp>.log
where database SID is the database SID, CDB name is the name of the multitenant container database, and timestamp is of the form YYYYMMMDD_HH_MM_SS.
After installing the SQL portion of the patch, some packages could become INVALID. This will get recompiled upon access or you can run utlrp.sql to get them back into a VALID state.
cd $ORACLE_HOME/rdbms/admin sqlplus /nolog SQL> CONNECT / AS SYSDBA SQL> @utlrp.sql
If there are errors, see Section 8, "Known Issues".
For information about OPatch issues, see My Oracle Support Document 293369.1 OPatch documentation list.
For issues documented after the release of this Oracle JavaVM Component Release Update 12.2.0.1.171017, see My Oracle Support Document 2297779.1 Oracle JavaVM Component Release Update 12.2.0.1.171017 Known Issues.
The known issues are as follows.
Problem: An ORA-04068 error may appear in the Database alert log file when datapatch is run.
During a successful run of the datapatch tool with no errors indicated, an ORA-04068 error may appear in the Database alert log file:
ORA-04068: existing state of packages has been discarded
Workaround: This is a retryable error in datapatch itself. If a patch installation receives it, then datapatch will automatically retry the operation once, before reporting it as a failure. The fact that datapatch did not report the retry and ran successfully with no errors confirms that the patch was successfully installed, and that another Oracle background process received the error. The ORA-04068 error should be ignored as long as datapatch runs successfully with no errors indicated (possibly after an automatic retry).
If the Database Jul2017 Release Update Revision 12.2.0.1.171017 (aka Patch 26518812) is also being applied during this same patching event, you must wait to begin the steps of this subject Patch 26635944 until all steps of Patch 26518812 (including post installations steps) are complete before beginning this subject OJVM patch. This will avoid the following potential error stack which can occur if the two patches are installed in parallel:
ORA-12012: error on auto execute of job "SYS"."ORA$AT_OS_OPT_SY_1" ORA-20001: Statistics Advisor: Invalid task name for the current user ORA-06512: at "SYS.DBMS_STATS", line 47207 ORA-06512: at "SYS.DBMS_STATS_ADVISOR", line 882 ORA-06512: at "SYS.DBMS_STATS_INTERNAL", line 20059 ORA-06512: at "SYS.DBMS_STATS_INTERNAL", line 22201 ORA-06512: at "SYS.DBMS_STATS", line 47197
This patch includes the following bug fixes.
For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/us/corporate/accessibility/index.html.
Access to Oracle Support
Oracle customers have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/support/contact.html or visit http://www.oracle.com/accessibility/support.html if you are hearing impaired.
Patch 26635944 - Oracle JavaVM Component Release Update 12.2.0.1.171017 for UNIX
Copyright © 2006, 2017, Oracle and/or its affiliates. All rights reserved.
This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.
If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.
This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark licensed through X/Open Company, Ltd.
This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.