本帖最后由 郑全 于 2020-5-26 11:24 编辑
Bug 23066146 - Connection to PDB results in kpoataf-fetch: [1403] trace generation
Bug 23066146 Connection to PDB results in kpoataf-fetch: [1403] trace generation.
This note gives a brief overview of bug 23066146.
The content was last updated on: 11-MAR-2020
Click here for details of each of the sections below.
Affects:
Product (Component)
Oracle Server (Rdbms)
Range of versions believed to be affected
Versions BELOW 18.1
Versions confirmed as being affected
12.2.0.1 (Base Release)
12.1.0.2 (Server Patch Set)
12.1.0.1 (Base Release)
11.2.0.4
Platforms affected
Generic (all / most platforms affected)
Fixed:
The fix for 23066146 is first included in
18.1.0
12.2.0.1.171121 (Nov 2017) Database Release Update (DB RU)
12.1.0.2.191015 (Oct 2019) Database Patch Set Update (DB PSU)
12.1.0.2.191015 (Oct 2019) Database Proactive Bundle Patch
12.2.0.1.171130 (Nov 2017) Bundle Patch for Windows Platforms
12.1.0.2.190315 (Mar 2019) Bundle Patch for Windows Platforms
Interim patches may be available for earlier versions - click here to check.
Symptoms:
Related To:
Unwanted or Excess Trace / Alert messages
(None Specified)
Description
If you see lots of trace files with just text kpoataf-fetch: [1403] whenever a connection is made to a pluggable database and the
service name being used has SID mentioned in tnsnames.ora, then you are hitting this bug.
Workaround
Use service name rather than SID in tnsnames.ora file.
Please note: The above is a summary description only. Actual symptoms can vary. Matching to any symptoms here does not confirm that you are encountering this problem. For questions about this bug please consult Oracle Support.
References
Bug:23066146 (This link will only work for PUBLISHED bugs)
Note:245840.1 Information on the sections in this article
|