We use TMS 13.1.2v. 255 GB Hard Disc capacitiy on the Win2008 server . I see below disk space errors about the TMS. Our HDD space is full. How to delete the old log file. How to fix problem. I couldn't delete old log file. I took the backup of the system log files.
Database Server Disk Space
An error has occurred while getting disk space information from the database. This may be caused by the fact that under SQL Server default settings, OLE Automation procedures are not enabled. Please refer to help for information on how to enable this option.
The "An error has occurred while getting disk space information from the database. This may be caused by the fact that under SQL Server default settings, OLE Automation procedures are not enabled. Please refer to help for information on how to enable this option."
Message simply means TMS can not read the diskspace available from the SQL Server. This method is no longer enabled by default on SQL Servers and this message is simply telling you that it can't do it unless you enable the OLE Automation procedures. This in itself isn't a problem, it just means TMS can't report on the database server's diskspace.
Your database files tho show that you have a very big log file. This means your database was probably installed to be in 'full recovery' mode and no one has been managing the log file. When in 'full recovery' mode you can restore to any point in time in the transaction history (cool..) but the transaction log will continually grow unless you manage it (bad..). The alternative is to use 'simple recovery mode', in this mode you can only restore to where you have backups (reasonable..) but the transaction log will stay a reasonable size without upkeep (cool).
In full recovery mode, you can reduce the size of the transaction log by doing a backup, followed by a 'shrink files' operation. Normally if you do regular backups, the transaction log will stay a reasonable size. The filesize itself will not reduce until you do a shrink. think of the filesize as a big box.. the database will fill that box as needed and empty it when you do backups, but if the box will ever become full, that's when it auto-expands. It never auto-shrinks the box.. so once it grows, it stays big. Shrink operations is how you reduce the size of the box.
This page tells you how to view/change recovery modes - http://msdn.microsoft.com/en-us/library/ms189272.aspx
I would recommend changing to simple recovery model, then doing a shrink operation on your database log file. See http://msdn.microsoft.com/en-us/library/ms190757(v=sql.120).aspx for more help on shrinking.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...