Oracle Recommended Patches -- "Oracle JavaVM Component Database PSU" (OJVM PSU) Patches (文档 ID 1929745.1)
From: https://support.oracle.com
What is "Oracle JavaVM Component Database PSU" ?
Oracle JavaVM Component Database PSU is released as part of the Critical Patch Update program from October 2014 onwards.
It consists of two separate patches:
- One for JDBC clients - applicable to Client, Instant Client, Database and Grid ORACLE_HOMES.
This is referred to as "JDBC Patch" in the rest of this document. - One for the Oracle JavaVM component within the Oracle Database - applicable to database ORACLE_HOMEs only.
This is referred to as "OJVM PSU" in the rest of this document.
As of January 2015 the "OJVM PSU" patches include all fixes from the "JDBC Patch".
For situations where the latest OJVM PSU cannot be installed immediately there is a "Mitigation Patch" that can be used.
OJVM PSU
OJVM PSU patches:
- include critical fixes for the Oracle JavaVM component within the Oracle Database
- are packaged separately from the Database PSU (or equivalent) as they cannot be installed in a RAC Rolling manner, nor in Standby First manner.
Keeping them separate allows customers to choose the most appropriate patching approach for each system- Oracle has also released "Combo" patches that bundle the OJVM
PSU in the same ZIP file as DB PSU and/or GI PSU for ease of download.
The OJVM component in these "Combo" patches is in a separate
subdirectory with its own install steps still required. October 2014 "Combo" patches do not include the JDBC Patch.
- Oracle has also released "Combo" patches that bundle the OJVM
- are applicable to all database installations regardless of which patching model is used (DB PSU, GI PSU, Security Patch Update (SPU), Windows Bundle Patch or Database Patch for Exadata)
- require the database home to be patched to at least October 2014 DB PSU (or equivalent)
- include binary changes to be applied to each Database ORACLE_HOME,
and "post install" steps to be execute on each database running from the
ORACLE_HOME - from January 2015 onwards: include the JDBC fixes
For situations where the latest OJVM PSU cannot be installed
immediately there is a "Mitigation Patch" that can be used as describe
below.
What is the "Mitigation Patch" ?
For situations where the latest OJVM PSU cannot be installed immediately there is a "Mitigation Patch" that can be used. The "Mitigation Patch" is an interim solution to protect against all currently known (Jul 2015) Oracle JavaVM security vulnerabilities in the database until such time as the OJVM PSU can be installed. It can also be used to protect database versions no longer covered by error correction support.
The "Mitigation Patch":
- is applicable only to database homes, not client nor Grid homes
- is only applicable to databases that have JavaVM installed
- has no dependency on the DB PSU (or equivalent) level
- can be installed in a RAC Rolling manner
- is a SQL only patch that needs to be installed and activated in each database
- hence it can be installed standby first but it
requires SQL steps to be executed to be effective, which cannot be done
on a read only standby
- hence it can be installed standby first but it
- affects use of Java and Java development in the database
- has been reviewed for January 2015, April 2015, July
2015, October 2015, January 2016, April 2016 and July 2016 and provides
mitigation against all currently known OJVM vulnerabilities - can be downloaded here: Patch:19721304
Read the "Using the Mitigation Patch" section later in this document to understand the impact of this patch.
JDBC Patch
The JDBC patches:
- include security fixes for JDBC
(Oct 2014 patches include fixes for CVE-2014-4289 and CVE-2014-6544 only) - are available packaged separately from the OJVM PSU and Database PSU (or equivalent) for ease of deployment to client environments
- are applicable to Client, Instant Client and Grid ORACLE_HOMES The
JDBC fixes are also applicable to the Database home regardless of
whether Oracle JavaVM is used in a database or not:- For October 2014 the JDBC Patch should also be installed in the Database home
- For January 2015 the OJVM PSU includes the JDBC fixes and so the
JDBC patch does not need to be installed in the Database home unless
OJVM PSU is not being installed yet - The JDBC Generic patches have been provided as a separate one-off
from July 2016 so that all customers can install that without issue.
- are applicable to all installations regardless of which patching model is used (DB PSU, GI PSU, Security Patch Update (SPU), Windows Bundle Patch or Database Patch for Exadata)
- have no dependency on OJVM PSU nor Database PSU (or equivalent) patch level
- can be installed in database server homes in a RAC Rolling manner
- do not require the database and listeners to be shutdown for patching in non-RAC environments
- do not require any post install steps be executed against individual databases
Latest JDBC patch availability information can be found in Document:756671.1 "Oracle Recommended Patches -- Oracle Database".
Oracle Recommended Patches -- "Oracle JavaVM Component Database PSU" (OJVM PSU) Patches (文档 ID 1929745.1)的更多相关文章
- oracle数据库 PSU,SPU(CPU),Bundle Patches 和 Patchsets 补丁号码快速参考 (文档 ID 1922396.1)
数据库 PSU,SPU(CPU),Bundle Patches 和 Patchsets 补丁号码快速参考 (文档 ID 1922396.1) 文档内容 用途 详细信息 Patchsets ...
- Oracle 11.2.0.4单实例打PSU,OJVM PSU补丁快速参考
写在前面: 1.Oracel打每个补丁的操作有时存在差异,所以不管多熟悉,都应该在打任何补丁之前阅读新补丁中附带的readme. 2.Oracle每季度都会更新一个最新的PSU,本文最新指的是当前最新 ...
- Oracle 11.2.0.4 DataGuard 环境打PSU,OJVM PSU补丁快速参考
环境:RHEL6.5 + Oracle 11.2.0.4 DataGuard physical standby 主库和备库都是单节点. 需求:主备库同时应用160719的PSU和OJVM PSU补丁. ...
- xtts v4for oracle 11g&12c(文档ID 2471245
xtts v4for oracle 11g&12c(文档ID 2471245.1) 序号 主机 操作项目 操作内容 备注: 阶段一:初始阶段 1.1 源端 环境验证 migrate_check ...
- Oracle版本发布规划 (文档 ID 742060.1)
Oracle Database Release Schedule of Current Database Releases (文档 ID 742060.1) Oracle Database RoadM ...
- 数据库 PSU,SPU(CPU),Bundle Patches 和 Patchsets 补丁号码快速参考 (文档 ID 1922396.1)
数据库 PSU,SPU(CPU),Bundle Patches 和 Patchsets 补丁号码快速参考 (文档 ID 1922396.1)
- 11i - 12 Gather Schema Statistics fails with Ora-20001 errors after 11G database Upgrade (文档 ID 781813.1)
11i - 12 Gather Schema Statistics fails with Ora-20001 errors after 11G database Upgrade (文档 ID 7818 ...
- Oracle Created Database Users: Password, Usage and Files References (文档 ID 160861.1)
This document is no longer actively maintained, for info on specific (new) users in recent product e ...
- Database Initialization Parameters for Oracle E-Business Suite Release 12 (文档 ID 396009.1)
In This Document Section 1: Common Database Initialization Parameters For All Releases Section 2: Re ...
随机推荐
- tp中session用来做权限方法 (缓解mysql压力)
http://www.thinkphp.cn/code/2617.html
- 1045 access denied for user 'root'@'localhost' using password yes的解决方法
今天把一个项目和项目的数据库都下载到了本地,安装好项目和在本地配置好数据库后,在浏览器登陆项目的后台却出现了以下错误: 后来上百度搜索了好几个答案,都是讲述修改数据库密码的步骤,但是就是没有说明为 ...
- 用HttpWebRequest提交带验证码的网站
using System; using System.Drawing; using System.IO; using System.Net; using System.Text; using Syst ...
- vmware workstation 上创建的centos 7.2 ,新添加一块网卡。无法找到配置文件。
在vmware workstation 11上,新建一个centos 7.2系统. 初装带有一个块网卡:能够在/etc/sysconfig/network-scripts/目录下找到相应的网卡配置文件 ...
- Django web 进阶
.路由系统 .模板引擎 simple_tag .Form .Ajax请求 -简单数据 -复杂数据 内容: -作业 model xss.csrf(安全方面的内容) 分页(公共的模块) 内容复习和今日内容 ...
- information_schema系列八(事物,锁)
今天我们主要看一下MySQL information_schema里面的关于innodb的锁和事物的两三个系统表: 看一下锁对应的sql: select * from innodb_lock_wait ...
- Python 2.7_初试连接Mysql查询数据导出到excel_20161216
由于每天到公司都需要先执行一遍检测操作,观察数据是否导入完整,今天想到能否自动连接Mysql执行SQL并导出数据,每天到公司直接查看excel文件即可 时间紧,代码初次试验,边摸索边学习吧. xlsx ...
- spring注解记录
集中记录spring常见注解 供今后查阅 @ControllerAdvice: ControllerAdvice的定义为: @Target(ElementType.TYPE) @Retention(R ...
- Linux C 开发环境配置
换了新电脑,重装了Fedora10,所有开发环境都要重新配置啦,开个随笔记录下过程,说不定以后还要用~ 首先Fedora10装好之后是不带 VIM 的,果断安装之: 打开终端,首先 su 命令切换到r ...
- SpreadJS电子表格
SpreadJS是wijmo旗下的一款HTML5电子表格控件. 官方网址:http://wijmo.com/products/spreadjs/ 在这里简单整理了SpreadJS几个比较简单的特点,如 ...