Oracle Databases Need to be Patched to a Minimum Patchset/PSU/RU level before April 2019 (DOC ID 2361478.1)

简介: In this Document Description   What we are announcing   What action you need to take    What is the change introduced by the patches listed above?  .

In this Document

Description
  What we are announcing
  What action you need to take 
  What is the change introduced by the patches listed above?
  Timelines
  Support and Questions
Occurrence
Symptoms
Workaround
Patches
History
References

APPLIES TO:

Oracle Database - Personal Edition - Version 9.2.0.1 and later
Oracle Database - Standard Edition - Version 9.2.0.1 and later
Oracle Database - Enterprise Edition - Version 9.2.0.1 and later
Information in this document applies to any platform.

DESCRIPTION

What we are announcing

All supported releases of Oracle Databases need to be patched to a minimum patchset/PSU level before April 2019 to ensure proper functioning of database links.

This note only applies to Database Server installations and the interoperability of database clients with database servers is not impacted by this patch.

 

What action you need to take 

For all database releases prior to 12.2.0.1, ensure that all interconnected databases are in the below mentioned patchset/ PSU/BP levels or above:

c84680ddab4f8b53cea610db1329bed46028ea75

 

In summary, 12.2.0.1 and higher releases, 11.2.0.4 and 12.1.0.2 patchsets have this fix included, while patches are available for 11.1.0.7 and 11.2.0.3 releases. If you have any other database server installations (e.g. 10.2.0.5, 11.2.0.2), you should upgrade such databases if you would like the older databases to continue using database links with newer versions of databases.  

 

What is the change introduced by the patches listed above?

The patches listed above make the older databases capable of supporting increased SCN soft limit (i.e. support transactions with higher SCN rate) though the increased SCN soft limit only becomes effective at a later time (after April 2019).

 

Timelines

 All databases should be at the above mentioned release/patchset/ PSU/BP levels (or above) before April 2019.

 

Support and Questions

If you have any queries please post them in the Database community page: https://community.oracle.com/message/14710245#14710245

OCCURRENCE

 Applicable to all Oracle database releases prior to 12.2.0.1

SYMPTOMS

Database Links might fail or encounter errors

WORKAROUND

 None

PATCHES

 Please refer the table Minimum Required PSU/RU above.

HISTORY

Added details regarding the change: 9-Mar-2018

Corrected the hyperlinks and information related to 11.2.0.3.29 (windows) : 7-Mar-2018 

Created: 15-Feb-2018 

目录
相关文章
|
4月前
|
SQL Oracle 关系型数据库
Oracle 11g 打PSU补丁教程
Oracle 11g 打PSU补丁教程
135 2
|
6月前
|
Oracle 关系型数据库 Linux
Requirements for Installing Oracle Database/Client 19c on OL8 or RHEL8 64-bit (x86-64) (Doc ID 2668780.1)
Requirements for Installing Oracle Database/Client 19c on OL8 or RHEL8 64-bit (x86-64) (Doc ID 2668780.1)
53 0
|
7月前
|
Oracle 关系型数据库 Linux
Oracle Linux: How To Disable NUMA At OS Level (Doc ID 2193586.1)
Oracle Linux: How To Disable NUMA At OS Level (Doc ID 2193586.1)
73 1
|
7月前
|
SQL Oracle 关系型数据库
实时计算 Flink版产品使用合集之如何获取 Oracle 自增 ID
实时计算Flink版作为一种强大的流处理和批处理统一的计算框架,广泛应用于各种需要实时数据处理和分析的场景。实时计算Flink版通常结合SQL接口、DataStream API、以及与上下游数据源和存储系统的丰富连接器,提供了一套全面的解决方案,以应对各种实时计算需求。其低延迟、高吞吐、容错性强的特点,使其成为众多企业和组织实时数据处理首选的技术平台。以下是实时计算Flink版的一些典型使用合集。
|
Oracle 关系型数据库
ORACLE中设置ID自增详细
ORACLE中设置ID自增详细
269 0
Zp
|
SQL Oracle 关系型数据库
Oracle sql使用sys_guid() 生成32位id乱码解决办法
Oracle sql使用sys_guid() 生成32位id乱码解决办法
Zp
2888 0
Oracle sql使用sys_guid() 生成32位id乱码解决办法
|
2月前
|
存储 Oracle 关系型数据库
Oracle数据库的应用场景有哪些?
【10月更文挑战第15天】Oracle数据库的应用场景有哪些?
187 64
|
7天前
|
存储 Oracle 关系型数据库
数据库数据恢复—ORACLE常见故障的数据恢复方案
Oracle数据库常见故障表现: 1、ORACLE数据库无法启动或无法正常工作。 2、ORACLE ASM存储破坏。 3、ORACLE数据文件丢失。 4、ORACLE数据文件部分损坏。 5、ORACLE DUMP文件损坏。
40 11
|
20天前
|
Oracle 关系型数据库 数据库
Oracle数据恢复—Oracle数据库文件有坏快损坏的数据恢复案例
一台Oracle数据库打开报错,报错信息: “system01.dbf需要更多的恢复来保持一致性,数据库无法打开”。管理员联系我们数据恢复中心寻求帮助,并提供了Oracle_Home目录的所有文件。用户方要求恢复zxfg用户下的数据。 由于数据库没有备份,无法通过备份去恢复数据库。
|
26天前
|
存储 Oracle 关系型数据库
oracle数据恢复—Oracle数据库文件大小变为0kb的数据恢复案例
存储掉盘超过上限,lun无法识别。管理员重组存储的位图信息并导出lun,发现linux操作系统上部署的oracle数据库中有上百个数据文件的大小变为0kb。数据库的大小缩水了80%以上。 取出&并分析oracle数据库的控制文件。重组存储位图信息,重新导出控制文件中记录的数据文件,发现这些文件的大小依然为0kb。