When ATS is active, each aborted transaction is written to a file in the specified directory.
The following table provides the naming convention for ATS files:
ats.target.source.threadId.timestamp.sequence
| Name | Description |
|---|---|
| target | The name of the database server receiving this replicate transaction |
| source | The name of the database server that originated the transaction |
| threadId | The identifier of the thread that processed this transaction |
| timestamp | The value of the internal time stamp at the time that this ATS instance was started |
| sequence | A unique integer, incremented by ATS each time a transaction is spooled |
The naming convention ensures that all filenames that ATS generates are unique, and therefore name collision is unlikely. However, when ATS opens a file for writing, any previous file contents will be overwritten. (ATS does not append to a spool file; if a name collision does occur with an existing file, the original contents of the file will be lost.)
The following is an example ATS filename for a transaction sent by server g_amsterdam to server g_beijing:
ats.g_beijing.g_amsterdam.D_2.000529_23:27:16.6Home | [ Top of Page | Previous Page | Next Page | Contents | Index ]