When ATS is active, all failed replication transactions are recorded in ATS files. Each ATS file contains all the information pertinent to a single failed transaction. If a replicated transaction fails for any reason (constraint violation, duplication, and so forth), all the buffers in the replication message that compose the transaction are written to a local operating-system file. You can use the ATS files to identify problems or as input to custom utilities that extract or reapply the aborted rows.
Aborted-transaction spooling only occurs if the entire transaction is aborted. Transactions defined with row scope that have aborted rows but are successfully committed on the target tables are not logged.
All rows that fail conflict resolution for a transaction that has row scope defined are also written to the RIS file (Row Information Spooling Files), if defined.
In some cases, such as with long transactions, the database server itself aborts transactions. In these cases, Enterprise Replication does not generate an ATS file.
Home | [ Top of Page | Previous Page | Next Page | Contents | Index ]