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 ...
随机推荐
- MonkeyRunner测试一MonkeyRunner的使用
最近搭建MonkeyRunner开发环境,安装PyDev时,饱受折磨,现在终于搞定.因为一些原因,用了JDK1.6,在线安装插件PyDev成功后,Windows-Preferences里找不到PyDe ...
- js 实现动态的图片时钟
效果如下图 附件有图片 http://files.cnblogs.com/files/biyongyao/时钟.rar 源代码 <!DOCTYPE html> <html> ...
- 转@OneToMany或@ManyToOne的用法-annotation关系映射篇(上)
原文:http://blog.sina.com.cn/s/blog_6fef491d0100obdm.html 例如我们用一个例子来开启JPA的一对多和多对一的学习. 比如你去当当网上买书籍,当当网就 ...
- live555+ffmpeg如何提取关键帧(I帧,P帧,B帧)
live555+ffmpeg如何提取关键帧(I帧,P帧,B帧)开发流媒体播放器的时候,特别是在windows mobile,symbian(S60)平台开发时,很可能遇到需要自己开发播放器的情况.S ...
- 【MongoDB】MongoDB 3.2 SCRAM-SHA-1验证方式
新版本已取消addUser方法,改使用createUser方法 官方地址:https://docs.mongodb.com/manual/tutorial/create-users/ 官方地址:htt ...
- 使用archlinux作为日常开发机已经半年了,随便写一下
机器配置 CPU: Intel Core i5-6200U CPU @ 2.8GHz RAM: 6114MiB / 7421MiB Resolution: 1920x2160 在arch下常用的软件 ...
- git和nginx安装
原始地址: https://www.zybuluo.com/freeethy/note/192109 git安装 设置git的username和email (注册gitlab的账号密码) $$ git ...
- 会话状态已创建一个会话 ID,但由于响应已被应用程序刷新而无法保存它
解决方法是新建 全局应用程序类 Global.asax 在 Session_Start 函数中 添加 string sessionId = Session.SessionID; protected v ...
- 几种linux脚本的简单执行方法
1.hash脚本文件名:assign 内 容:#!/bin/sh cd $1ls 执行: [root@db2 ~]# sh helle2.sh /usr 或者[root@db2 ~]#./helle2 ...
- R&Rstudio安装各种包
安装rCharts的方法 install.packages('devtools') library(devtools) require(devtools) install_github('ramnat ...