Maintaining Disk Space on the ENTM Server

Document ID : KB000012702
Last Modified Date : 14/02/2018
Show Technical Document Details
Introduction:

From a customer perspective some files were identified on the ENTM Server which were considered too big, and their size keeps growing every day.

Question:

What file from the below list can we delete or set to zero ?

./APMS/AccessControl/policies/DMS__/ERROR_LOG
./APMS/AccessControl/policies/DMS__/updates.dat
./APMS/AccessControl/policies/DMS__/seos_pvf.dat
./APMS/AccessControl/policies/DH__/updates.dat
./APMS/AccessControl/policies/DH__/seos_pvf.dat
./MessageQueue/tibco/cfgmgmt/ems/data/datastore/async-msgs.db

Answer:

With this background information you can decide yourself what to do.

./APMS/AccessControl/policies/DMS__/ERROR_LOG

This is the pmdb's error log file. You can view its contents with this command:
# sepmd -e DMS__

To reduce the file size to 0 you clear the error log with this command:
# sepmd -c DMS__

There is no operational risk involved to clear the error log.


./APMS/AccessControl/policies/DMS__/updates.dat

This is the pmdb's updates file containing a log of all the replication transactions to the subscribers.
You can view its contents with this command:
# sepmd -C DMS__

To reduce the file size to 0 you clear the updates file with this command:
# sepmd -t DMS__ auto

There is normally no operational risk involved in this operation.
The file however might be needed for any future migration operation.


./APMS/AccessControl/policies/DMS__/seos_pvf.dat

This file is part of the pmdb database.
You may try to reindex the database which would delete any obsolete data using these commands:

# secons -s
# cd /opt/CA/AccessControlServer/APMS/AccessControl/policies/DMS__
# dbmgr -u -close
# dbmgr -u -build all
# seload

There is no operational risk involved expect the downtime while this operation is ongoing.


./APMS/AccessControl/policies/DH__/updates.dat

What was said above also applies here for the Distribution Server.


./APMS/AccessControl/policies/DH__/seos_pvf.dat

What was said above also applies here for the Distribution Server.


./MessageQueue/tibco/cfgmgmt/ems/data/datastore/async-msgs.db

This is the datastore of the Message Queue subsystem.
A big file size is indicating that there are undelivered messages still waiting in any Queue

To confirm and find out which Q is holding back the data run these commands:

# /opt/CA/AccessControlServer/MessageQueue/tibco/ems/5.1/bin/tibemsadmin
> connect ssl://localhost:7243
Login name (admin): admin
Password:
Connected to: ssl://localhost:7243
ssl://localhost:7243> show queues

If you do not have UARM installed the queue/audit would probably have grown large.
To purge its contents you would run in the tibemsadmin

purge queue queue/audit

Please see also this document for further recommended actions:
https://www.ca.com/us/services-support/ca-support/ca-support-online/knowledge-base-articles.TEC1009372.html


There is no operational risk involved in this case.