RE: Rejected to advance the SCN Issues

From: Powell, Mark <mark.powell2_at_hp.com>
Date: Tue, 25 Jun 2013 14:36:50 +0000
Message-ID: <1E24812FBE5611419EFAFC488D7CCDD1186D82DC_at_G6W2491.americas.hpqcorp.net>

The following Oracle support notes might be of interest depending on your unidentified Oracle version/patch information.

Note: 1393360.1 ORA-19706 and Related Alert Log Messages Note: 1503937.1 Master Note: Overview for SCN issues

-----Original Message-----

From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Bala Krishna Sent: Tuesday, June 25, 2013 3:30 AM
To: oracle-l_at_freelists.org
Subject: Rejected to advance the SCN Issues

Hi All,
Almost all our Databases are affected with below errors , we suspect that its because of our distrubuted transactions .

Rejected the attempt to advance SCN over limit by 212 hours worth to 0x0c2c.ae9cc069, by distributed transaction remote logon, remote DB: XXXXX.xxxx.com.
 Client info : DB logon user APPS, machine XXXXXXX, program , and OS user XXXXXXX

As if now we've mitigated this issue by setting below parameters.

_external_scn_rejection_threshold_hours=24

My question:-

1. Distrubuted Transactions are being failed sometimes with ORA-600 , ORA-19706: invalid SCN & some instance crashes are also observed.

I've read in this blog (
http://www.orainternals.com/2012/01/20/scn-what-why-and-how/) and it says that

At commit time, a co-ordinated SCN is needed for the distributed transaction and maximum SCN value from all participating databases is chosen.

So which means , since there is a increase in SCN number we should be facing this kind of issues even for local transactions rather than distrubted transactions right ? but we're not facing such issues as such ?

Regards
Bala

--

http://www.freelists.org/webpage/oracle-l

--

http://www.freelists.org/webpage/oracle-l Received on Tue Jun 25 2013 - 16:36:50 CEST