![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Hi. We are seeing the following on one of our servers (running on Windows Server 2003 w/8.0.2.4433): The database is running mirrored logs. The mirrored log directory has a current log file, as well as a log file one day back. However, the primary database directory has log files going back to June (one per day). I have verified that all the children database are current (at least within the past 24 hours). Therefore I believe the contents of the mirror log directory is correct. I realize I could clean them up manually, but why are the primary log files not getting cleaned up automatically? Just as few more pieces of information: 1) The database and dbremote run as services 2) We run a dbbackup job each evening that renames and restarts the transaction log 3) delete old logs is on 4) This was working for several years, up until mid June. -- Andrew Braunstein |
#3
| |||
| |||
|
|
What is your full dbremote command line? -- ----------------------------------------------- Robert Waywell Sybase Adaptive Server Anywhere Developer - Version 8 Sybase Certified Professional Sybase's iAnywhere Solutions Please respond ONLY to newsgroup EBF's and Patches: http://downloads.sybase.com choose SQL Anywhere Studio >> change 'time frame' to all To Submit Bug Reports: http://case-express.sybase.com/cx/cx...c?CASETYPE=Bug SQL Anywhere Studio Supported Platforms and Support Status http://my.sybase.com/detail?id=1002288 Whitepapers, TechDocs, and bug fixes are all available through the iAnywhere Developer Community at www.ianywhere.com/developer "Andrew Braunstein" <abraunstein (AT) healthwyse (DOT) com> wrote in message news:43546db2 (AT) forums-2-dub (DOT) .. Hi. We are seeing the following on one of our servers (running on Windows Server 2003 w/8.0.2.4433): The database is running mirrored logs. The mirrored log directory has a current log file, as well as a log file one day back. However, the primary database directory has log files going back to June (one per day). I have verified that all the children database are current (at least within the past 24 hours). Therefore I believe the contents of the mirror log directory is correct. I realize I could clean them up manually, but why are the primary log files not getting cleaned up automatically? Just as few more pieces of information: 1) The database and dbremote run as services 2) We run a dbbackup job each evening that renames and restarts the transaction log 3) delete old logs is on 4) This was working for several years, up until mid June. -- Andrew Braunstein |
![]() |
| Thread Tools | |
| Display Modes | |
| |