Re: Odd MoS Note
Date: Thu, 8 Mar 2018 17:23:18 -0500
Message-ID: <CADo_RaPCvHiuHP4MEAfj-uEUWsLfJ0mpvwSp-8EuyZGc8tSfQg_at_mail.gmail.com>
On Thu, Mar 8, 2018 at 1:25 PM, Rich J <rjoralist3_at_society.servebeer.com>
wrote:
> ....
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
> 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
>
-- http://www.freelists.org/webpage/oracle-lReceived on Thu Mar 08 2018 - 23:23:18 CET