Resolution
This is a step-by-step process to clear the logs on the VMS Server.
- You need to ensure that there is enough disk space available to do the pruning and subsequently compact the database, as VMS needs space
for temporary files.
- Back up your Database (DB) files first before you proceed with any of these steps.
(Program Files\CSCOpx\MDC\Sybase\Db\IDS\idsmdc.db & idsmdc.log)
- You can double-click on the files on the GUI and on version 2.3 of VMS and 2.x of IPS MC, and change the file size. The next time the
pruning daemon runs, it ideally prunes these files, and the daemon runs automatically.
- Stop the VMS services and run this command in order to truncate manually is the idsmdc.log file:
dbbackup -xo -c"uid=idsmdc;pwd= ;dbn=idsmdc;eng=sqlcoredbserver;links=tcpip{dobroadcast=no;host=localhost;port=10033}"
- You can use your idsmdc database password for this.
In order to get the IDSMC password:
ccraccess -getData "" Custom Custom /d:DEFAULT "" idsmdc DB-Credential
- Run the net start crmdmgtd command in order to restart the service.
Note: If the DB file becomes too big, it can lead to database corruption. So it is recommended to regularly prune that file. Database pruning does not reduce the size of the database itself (the .db and .log files). The database deletes records, but it does not return the memory to the operating system. It marks it as free and keeps it internal to the database for re-use. When pruning runs, the .db file remains about the same size and the .log file actually grows.
- After pruning the DB file, complete the steps in the instructions on the provided link in order to compact it and reduce the size. Refer to Compacting the Database section of Maintaining Security Monitor for these instructions.
In addition, you can move the files in this directory, \CSCOpx\MDC\Sybase\Db\IDS\AlertPruneData, to a backup or other file server, as these contain pruned events that you might want to restore. In this way, you can free up some space.
