Symptom
- Running a dump transaction <database> with truncate_only is not truncating the log
- Normal dump transaction <database> command didn't truncate log records after it's completed.
- Database is being replicated
- dbcc gettrunc reports a secondary truncation point
1> use <database name>
2> go
1> dbcc gettrunc
2> go
secondary trunc page secondary trunc state dbrepstat generation id database id database name ltl version
-------------------- --------------------- --------- ------------- ----------- ------------------------------ -----------
440883 1 231 3 19 <database> 700
- sp_helpdb shows the same number of free kilobytes in ASE for the log segment after issuing the dump transaction
1> sp_helpdb <database>
2> go
name db_size owner dbid created status
---- ------------- ----- ---- ------------ --------------
<database> 5800.0 MB sa 19 Oct 30, 2013 no options set
(1 row affected)
.
.
.
--------------------------------------------------------------
log only free kbytes = 221424
Read more...
Environment
- SAP Adaptive Server Enterprise (ASE) All Versions
- SAP Replication Server (SRS) All Versions
Product
Keywords
KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.
SAP Knowledge Base Article - Preview