Someone was playing with replication and now the

DBA > Job Interview Questions > Sybase Interview Questions and Answers

More DBA job interview questions and answers at http://dba.fyicenter.com/Interview-Questions/

(Continued from previous question...)

Someone was playing with replication and now the transaction log on OLTP is filling

Once replication has been configured, ASE adds another marker to the transaction log. The first marker is the conventional one that marks which transactions have had their data written to disk. The second is there to ensure that the transactions have also been replicated. Clearly, if someone installed replication and did not clean up properly after themselves, this marker will still be there and consequently the transaction log will be filling up. If you are certain that replication is not being used on your system, you can disable the secondary truncation marker with the following commands:

1. use <database>
2. go
1. dbcc settrunc(ltm, ignore)
2. go

The above code is the normal mechanism for disabling the trucation point. I have never had a problem with it. However, an alternative mechanism for disabling the truncation point is given below. I do not know if it will work in situations that the previous example won't, or if it works for databases that are damaged or what. If someone knows when you use it and why, please let me know (mailto:dowen@midsomer.org).

1. sp_role "grant", sybase_ts_role, sa
2. go
1. set role sybase_ts_role on
2. go
1. dbcc dbrepair(dbname, ltmignore)
2. go
1. sp_role "revoke", sybase_ts_role, sa
2. go

This scenario is also very common if you load a copy of your replicated production database into development.