on 08-11-2014 7:41 AM
Hi Experts,
We are facing IdM DB space issue in our PRD environment. Upon observing, it was found that the below tables are taking much space in IdM DB. Could anyone tell me what impact will my PRD system have if I truncate the below tables to free space. Please do help us out in this , if this problem is not solved, this will become the show stopper.
mc_exec_stat
MC_LOGS
MC_SYSLOG
mxi_entry
mxi_link_audit
mxi_link
MXI_OLD_VALUES
MXI_VALUES
MXP_AUDIT
MXP_Audit_Variables
MXP_Ext_Audit
Kind Regards,
Mohamed Fazil
I don't know what you mean with too much diskspace? Perhaps you can post the sizes here and the number of entries in your system so we can evaluate if it's normal or not.
Most of the tables you list should not be touched and if you truncate link and entry you will delete all your assignments and entry data, and you would possibly be looking for a new job the next day.
The log tables should be maintained by the housekeeping as mentioned, but
mc_exec_stat
MC_LOGS
MC_SYSLOG
can be cleaned but neither should have that much data, but large amounts of transactions cause logs to grow. Have you checked that your backup is cleaning the transaction logs? Also reduce loglevels to ERROR to reduce the amount logged here.
MXP_Audit_Variables should not contain audits that are not in the provisioning queue, if you delete those workflows will fail.
MXP_Ext_Audit can probably be cleaned without affecting operations (reports might be affected though) but you'll loose the detailed execution history on the entries, perhaps you can do partials, delete entries older than 3 years or similar.
For future reference:
List transaction log sizes (SQL Server):
DBCC SQLPERF(LOGSPACE)
List table siszes (SQL Server):
DECLARE @SpaceUsed TABLE( TableName VARCHAR(100)
,No_Of_Rows BIGINT
,ReservedSpace VARCHAR(15)
,DataSpace VARCHAR(15)
,Index_Size VARCHAR(15)
,UnUsed_Space VARCHAR(15)
)
DECLARE @str VARCHAR(500)
SET @str = 'exec sp_spaceused ''?'''
INSERT INTO @SpaceUsed EXEC sp_msforeachtable @command1=@str
SELECT * FROM @SpaceUsed order by CAST(REPLACE(ReservedSpace,' KB','') as INT) desc
Oracle undo, user and redofiles:
select * from dba_data_files where tablespace_name LIKE 'UNDOTB%1' OR tablespace_name LIKE 'USERS%';
select l.group#,f.member,l.archived,l.bytes/1078576 bytes,l.status,f.type
from v$log l, v$logfile f
where l.group# = f.group#
-
C
Message was edited by: Per Krabsetsve
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You should check the constant for the execution threshold logging if the mc_exec_stat table is large:
MX_LOG_EXEC_THRESHOLD
Increase the value (milliseconds) to 5000 or something and see if it reduces the number of new entries logged. If you also have performance issues you should probably look at the contents of the table or the view idmv_exec_stat before you clear the table.
Hi Fazil,
Have you configured dispatcher house keeping settings. The house keeping procedures will clean up the logs for you. You can schedule them based on your requirement.
Regards,
Dileep Reddy
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
86 | |
10 | |
10 | |
9 | |
6 | |
6 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.