How to reduce the number of records in CMR_IOALOG?

Tools and several solutions to manage Control-M products
Post Reply
User avatar
gilkeden
Nouveau
Nouveau
Posts: 5
Joined: 29 Apr 2009 12:00

How to reduce the number of records in CMR_IOALOG?

Post by gilkeden » 27 Jul 2009 4:17

I'm running with Control-M6.3 with Oracle, there are around 7000 jobs/day, 3 days of retention for the log.

When I run ctmdbcount, I can see the CMR_IOALOG=883122, it seems a huge value regarding the number of jobs.
We are running daily 'ctmlog -delete from date to date' and the 'ctmdbopt'.
Do you think that this value is normal or can we reduce it ??
Thanks,

User avatar
Walty
Nouveau
Nouveau
Posts: 473
Joined: 20 Jan 2006 12:00

How to reduce the number of records in CMR_IOALOG?

Post by Walty » 28 Jul 2009 12:59

Hi,
in the past, i have encountered a situation where the IOALOG was not removed correctly.

- Check the amount of entries in the CMR_IOALOG table:
select count(*) from CMR_IOALOG or ctmdbcount | grep CMR_IOALOG
Normaly this table is supposed to be cleaned during New Day Procedure, and old IOALOG records are removed.

- If you have put: Maximum Days Retained by CONTROL-M Log=3
Check that you don't have older days: select count(*) from CMR_IOALOG where ODATE<'yyyymmjj' (ODATE -3)

If you have entries oldest that ODATE -3, it shows that Control-M is unable to clean correctly the log during the General Daily.
- Clean manually the unwanted entries in this table:
delete from CMR_IOALOG where ODATE<'yyyymmjj' (ODATE -3)
Best regards
Walty

User avatar
gilkeden
Nouveau
Nouveau
Posts: 5
Joined: 29 Apr 2009 12:00

Post by gilkeden » 28 Jul 2009 9:03

Many thanks to you Walty, you were right, the CMR_IOALOG was not cleaned correctly.

lee_ray

Post by lee_ray » 04 Aug 2009 9:49

Hi,

I think the retention period determines number of days the log keeps in CMR_IOALOG, so you should filter the table by LOGDATE, not the ODATE.

Try the query as follow (GETDATE()-3 means retention period is 3):

select * from CMR_IOALOG where LOGDATE < CONVERT(char( 8 ), GETDATE()-3, 112)

You should get 0 row counts.

PS - I am running Control-M 6.4, but it should work on either version.

User avatar
philmalmaison
Nouveau
Nouveau
Posts: 1148
Joined: 08 Jun 2007 12:00
Location: Ile de France

Post by philmalmaison » 05 Aug 2009 11:15

as this table have created many problem in the past, from the 6.3 version, it has been cut in CMR_IOALOG_<N>, so you shouldn't have any problem with full tablespace as it can happend before.

the cleanup is made as the log retention in control-m server parameters.

regards
philmalmaison

Post Reply