This content has been marked as final. Show 5 replies
We have found 2 causes for this so far:1 person found this helpful
1- Check the presence of pending transaction - look in DBA_2PC_PENDING and resolve these
2- Check for old open transactions. In our case, some developpers were doing explain plan in Toad that left open transaction for days...
select round((sysdate - t.start_date)*24*60) minutes, s.inst_id, s.sid, s.serial#, s.username, s.program, s.module, s.action, t.xidusn, t.used_urec, t.used_ublk, t.recursive, t.start_date
from GV$SESSION s, GV$TRANSACTION t
where s.saddr = t.ses_addr
and s.inst_id = t.inst_id
order by 1 desc;
Get rid of the old transaction then do:
exec DBMS_CAPTURE_ADM.set_parameter('capture_name', '_CHECKPOINT_FORCE', 'Y');
Hope this helps,
Thanks for your reply. That worked for required checkpoint SCN after clearing the 2PC pending transactions. But, the start SCN and first SCN are still at same SCN. How can they move forward?.
Leave it alone and wait. Every 6 hours (last time I checked), you'll see in alert "first scn changed".
That's correct. The First SCN is changed now.
Thanks for your help.
The First SCN, Required Checkpoint SCN, start SCN are hanging again. I don't see any 2PC pending transactions. The streams apply is working fine. But, these SCNs are not moving forward on capture side. Any idea why?.
I have already set the CHECKPOINTFORCE to Y.