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 ...
随机推荐
- 创建DAO模式的步骤
1.建立数据库epet 2.创建实体类,和相对应的数据库是对应的 3.创建Dao的基类接口类BaseDao 4.创建Dao的实现类BaseDaoImpl 5.创建具体表的Dao类 6.创建具体表的Da ...
- 洛谷P1371 NOI元丹
P1371 NOI元丹 71通过 394提交 题目提供者洛谷OnlineJudge 标签云端评测 难度普及/提高- 提交 讨论 题解 最新讨论 我觉得不需要讨论O long long 不够 没有取 ...
- Python学习一(面向对象和函数式编程)
学习了一周的Python,虽然一本书还没看完但是也收获颇多,作为一个老码农竟然想起了曾经荒废好久的园子,写点东西当做是学习笔记吧 对Python的语法看的七七八八了,比较让我关注的还是他编程的思想,那 ...
- Caused by: java.lang.NoSuchMethodError: javax.persistence.spi.PersistenceUnitInfo.getValidationMode
进行 spring mvc jpa整合时.Junit方法测试时. 异常: org.springframework.beans.factory.BeanCreationException: Error ...
- zend studio中ctrl+鼠标左键无法转到类或函数定义文件的解决方法
转载自:http://blog.csdn.net/wide288/article/details/21622183 zend studio中ctrl+鼠标左键无法转到类或函数定义文件的解决方法: ze ...
- 1o_Samba
∮Linux下Samba的安装配置 §Linux 下文件共享软件 Samba 是一款实现跨主机,跨平台文件共享的软件.同类型的软件还有 ftp,nfs 不再赘述. §文件共享协议 Windows : ...
- teeChart 修改注册表实现无试用到期提示
teechart在注册表的跟目录为HKEY_CLASSES_ROOT\CLSID,以下的子目录会根据版本的不同发生改变,但是最底级的目录是TypeLib(例如[HKEY_CLASSES_ROOT\CL ...
- 解决ASP.Net第一次访问慢的处理(IIS8)
本篇经验以IIS8,Windows Server 2012R2做为案例. IIS8 运行在 Windows Server 2012 and Windows 8 版本以上的平台上. IIS中应用程序池和 ...
- sea.js 入门
上个月学了 require.js 现在顺便来学学 sea.js. 对比下这两种的区别,看自己喜欢哪个,就在接下来的项目中去使用它吧. seajs中的所有 JavaScript 模块都遵循 CMD 模块 ...
- Visual Studio 2015 工具箱丢失
网上主要的解答分为两种:1. 未打开设计界面 2. 重置 实际上,还有一个原因是,没有启动完整版的VS. 安装完后,会有两个VS的程序,一个是Blend For Visual Studio 2015, ...