ORA-01291: missing logfile in Rep Agent -Sybase Replication Server 16

[former_member246062]

Hello All

E.2018/06/16 04:45:47.214 ERROR com.sybase.ds.oracle.logmnr.LogMinerScannerTa  Start SCN = 800178910044 ,End SCN=800178911044

E.2018/06/16 04:45:47.215 ERROR com.sybase.ds.oracle.logmnr.ParallelLogMinerS  Log scanner <com.sybase.ds.oracle.logmnr.ParallelLogMinerScanner@385becc> stopped because of error: ORA-01291: missing logfile

Receiving the Logfile missing error in the Rep Agent frequently .

State Action

----------- ----------------------------------------------------

REPLICATING Transitioning- LogReader is stopping due to error.

ra_helplocator - showing LSN number whose archive file has not been present (older than 3 days LSN [archive file]) in the archive location due to archiving policy of 72 hours in source system.

My question is , why the Rep Agent's locator is looking for older archive logs (2(or) 3 days older files) when there are active transactions going at the source systems at present.

[former_member285566]

Hi,

One of the possible reasons is that the truncation point hadn't been moved because of lower replication activities. There is SAP KBA (1988032 - Keeping locater current during times of low replication activity - SRS) that explains this and provides a workaround.

Thanks,

Hunter

[former_member246062]

Implemented the rs_ticket also in our environment. This will be helpful when there are lesser txns systems, whereas ours is high volumnous txn system .

Still we are receiving the same Log file missing issue ,

When we check 'ra_helptran' , there are open txns listed in Rep Agent but it is in False state.

Most of the times in Rep Server's Inbound queue getting open Txns (admin who,sqt) .

Is there any workaround for this?

When we purge these open txns, will it result in data loss?

[former_member89972]

What is the replication set up like ? What are the primary and replicate database flavors?

ASE/Oracle ==> REP-SERVER ==> ASE/Oracle ?

I have seen this for another replication server called Attunity Replicate ( very similar to SAPs log based Replication Server ) and something similar came up in this context when Oracle logminer was used. It read from Oracle (source) and replicated to Teradata. Recommendation there was to use file system based redo log files ( rather than use log miner internal to Oracle) And also use "cio" setting on the file system where redo logs are held.

HTH

Avinash