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 

目录
相关文章
|
存储 Oracle 关系型数据库
ORACLE:根据父id查询所有子孙数据,或者根据子id查询所有父数据(start with connect by prior)
一、需求: 我们在开发中经常遇到一种数据库表的设计:一个表中包含父子信息数据,也就是常说的树形数据. —> 最常见的例子就是省市区一体表,就是通过id、pid、level来进行控制,从而一张表来存储数据.我们进行拿数据的时候,不用再连表拿取,直接通过(start with connect by prior)直接便利就会得到数据.
522 2
ORACLE:根据父id查询所有子孙数据,或者根据子id查询所有父数据(start with connect by prior)
|
9月前
|
Oracle 关系型数据库
ORACLE中设置ID自增详细
ORACLE中设置ID自增详细
198 0
|
Oracle 关系型数据库
Oracle多条重复id,查询时间最早的那条
Oracle多条重复id,查询时间最早的那条
109 0
|
Oracle 关系型数据库 数据库
Oracle 查看当前会话 SESSION ID 方法
查看当前会话的session  ID 有如下三种方法:   1.   v$mystat视图   SQL> desc v$mystat  Name                ...
1442 0
|
关系型数据库 Oracle
|
关系型数据库 Oracle
|
关系型数据库 Oracle
|
4天前
|
SQL Oracle 关系型数据库
【Oracle】玩转Oracle数据库(一):装上去,飞起来!
【Oracle】玩转Oracle数据库(一):装上去,飞起来!
39 7