Re: Odd MoS Note

  • From: Stefan Knecht <knecht.stefan@xxxxxxxxx>
  • To: Andy Klock <andy@xxxxxxxxxxxxxxx>
  • Date: Fri, 9 Mar 2018 11:55:17 +0700

Good catch! I hadn't seen that.

Yeah that would explain it.



On Fri, Mar 9, 2018 at 5:23 AM, Andy Klock <andy@xxxxxxxxxxxxxxx> wrote:



On Thu, Mar 8, 2018 at 1:25 PM, Rich J <rjoralist3@xxxxxxxxxxxxxxxxxxxxx>
wrote:

....
Yes, the headline appears to be misleading, to put it mildly.  The Oracle
forums has at least one thread on it where Oracle employees state that it
will only affect DB links between post-patched and pre-patched databases:

https://community.oracle.com/message/14710245

"In short, either both databases in the dblink connection should be
patched or unpatched, and there won't be any issues in the connectivity."

Rich



Not only that, but there is a little hint at the bottom of the note:

 System Change Number, ORA-19706 ,SCN low headroom issues, SCN Jumps
<https://support.oracle.com/epmos/main/kmservlet?operation=doSearch&task=SearchProduct&type=subcomponent&id=SCI_3_2DJZ358&prodid=PI_1_97NVP&comp=CI_3_2OYN_2088&name=System%20Change%20Number%2C%20ORA-19706%20%2CSCN%20low%20headroom%20issues%2C%20SCN%20Jumps&source=>

Which is this scary Oracle weed which propagates the SCN headroom bug when
using a db link.

Andy K




-- 
//
zztat - The Next-Gen Oracle Performance Monitoring and Reaction Framework!
Visit us at zztat.net | Support our Indiegogo campaign at igg.me/at/zztat |
@zztat_oracle

Other related posts: