1 2 Previous Next 11 Replies Latest reply on Jan 21, 2011 4:40 AM by helder.fernandes

    Database Tuning on MDR Secondary Manager

      Hi all,

       

      I've observed that using version 6.0.1.5 as manager platform and MDR configured, database tuning is not performed on the secondary manager and thus triggerring capacity errors. DB tuning on the primary manager works nicely using the configured settings. Obviously, on the secondary manager these settings are displayed in the gui but not applied?

       

      Anyone has similar observations or even a fix maybe?

       

      Thanks, Adrian

        • 1. Re: Database Tuning on MDR Secondary Manager

          Could be the setting only running when it's active? not standby

          • 2. Re: Database Tuning on MDR Secondary Manager

            Maybe, but this would be rather a bug than a feature since all other scheduled tasks are running properly on the secondary, passive manager. Anyone from McAfee here to enlighten on this?

             

            Cheers, Adrian

            • 3. Re: Database Tuning on MDR Secondary Manager

              I Don´t have MDR, but I´m having problems with de DB tunning, the manager version is 6.0.7.9. Db tunning is scheduled but I always have the result Failure.

               

               

              Any ideas ?

              • 4. Re: Database Tuning on MDR Secondary Manager

                What error message do you receive? Do you have the ems.log showing these?

                • 5. Re: Database Tuning on MDR Secondary Manager

                  Hello David,

                   

                   

                  The ems.log show´s the follow:

                   

                  2011-01-14 05:00:09,197 INFO  [Thread-216] iv.scheduler.DBMaintenanceAdapter -  ***** DB Tuning is in PROGRESS******
                  2011-01-14 05:00:09,197 INFO  [Thread-216] iv.scheduler.DBMaintenanceAdapter -  ***** DB Tuning for ALL TABLES is in PROGRESS******
                  2011-01-14 05:00:15,932 ERROR [PerfMonSummaryTimer] STDERR - SummaryItem:CPU Utilization: Metric ID = 1
                  SegmentSize = 5
                  SegmentData:High: SegmentData:Medium: SegmentData:Low: 1017;1010;1011;SegmentData:Not enabled: SegmentData:Not connected:
                  2011-01-14 05:00:15,932 ERROR [PerfMonSummaryTimer] STDERR - SummaryItem:TCP/UDP Flow Utilization: Metric ID = 2
                  SegmentSize = 5
                  SegmentData:High: SegmentData:Medium: SegmentData:Low: 1017;1003;1005;1020;1021;1022;1023;1010;1011;SegmentData:Not enabled: SegmentData:Not connected:
                  2011-01-14 05:00:15,932 ERROR [PerfMonSummaryTimer] STDERR - SummaryItem:Sensor Throughput Utilization: Metric ID = 3
                  SegmentSize = 5
                  SegmentData:High: SegmentData:Medium: SegmentData:Low: 1017;1003;1005;1020;1021;1022;1023;1010;1011;SegmentData:Not enabled: SegmentData:Not connected:
                  2011-01-14 05:00:15,932 ERROR [PerfMonSummaryTimer] STDERR - FIFO Cache Got an entry :  key = 0, value = [SummaryItem:CPU Utilization: Metric ID = 1
                  SegmentSize = 5
                  SegmentData:High: SegmentData:Medium: SegmentData:Low: 1017;1010;1011;SegmentData:Not enabled: SegmentData:Not connected: , SummaryItem:TCP/UDP Flow Utilization: Metric ID = 2
                  SegmentSize = 5
                  SegmentData:High: SegmentData:Medium: SegmentData:Low: 1017;1003;1005;1020;1021;1022;1023;1010;1011;SegmentData:Not enabled: SegmentData:Not connected: , SummaryItem:Sensor Throughput Utilization: Metric ID = 3
                  SegmentSize = 5
                  SegmentData:High: SegmentData:Medium: SegmentData:Low: 1017;1003;1005;1020;1021;1022;1023;1010;1011;SegmentData:Not enabled: SegmentData:Not connected: ]
                  2011-01-14 05:00:19,197 INFO  [ContainerBackgroundProcessor[StandardEngine[jboss.web]]] iv.ui.jspBean.ResourceTreeWebCache - Removing node states from cache for user Id : 120
                  2011-01-14 05:00:19,197 INFO  [ContainerBackgroundProcessor[StandardEngine[jboss.web]]] iv.ui.jspBean.ResourceTreeWebCache - Removing tree nodes from cache for user id: 120
                  2011-01-14 05:00:26,932 INFO  [BuildWebTierHomeCacheThread] iv.subsmgmt.facade -  the list returned is,[]
                  2011-01-14 05:00:26,947 INFO  [BuildWebTierHomeCacheThread] iv.subsmgmt.facade -  the list returned is,[]
                  2011-01-14 05:00:26,963 INFO  [BuildWebTierHomeCacheThread] iv.subsmgmt.facade -  the list returned is,[]
                  2011-01-14 05:00:26,963 INFO  [BuildWebTierHomeCacheThread] iv.subsmgmt.facade -  the list returned is,[]
                  2011-01-14 05:00:26,979 INFO  [BuildWebTierHomeCacheThread] iv.subsmgmt.facade -  the list returned is,[]
                  2011-01-14 05:00:26,994 INFO  [BuildWebTierHomeCacheThread] iv.subsmgmt.facade -  the list returned is,[]
                  2011-01-14 05:00:26,994 INFO  [BuildWebTierHomeCacheThread] iv.subsmgmt.facade -  the list returned is,[]
                  2011-01-14 05:00:27,010 INFO  [BuildWebTierHomeCacheThread] iv.subsmgmt.facade -  the list returned is,[]
                  2011-01-14 05:00:27,026 INFO  [BuildWebTierHomeCacheThread] iv.subsmgmt.facade -  the list returned is,[]
                  2011-01-14 05:00:27,307 INFO  [Thread-101] iv.core.DiscoveryService.status -     [STATE] xpto1 ACTIVE
                  2011-01-14 05:00:42,995 INFO  [Thread-103] iv.core.DiscoveryService.status -     [STATE]  xpto2 ACTIVE
                  2011-01-14 05:00:51,995 INFO  [Thread-98] iv.core.DiscoveryService.status -     [STATE]  xpto3 ACTIVE
                  2011-01-14 05:01:08,855 INFO  [Thread-100] iv.core.DiscoveryService.status -     [STATE]  xpto4  ACTIVE
                  2011-01-14 05:01:09,855 INFO  [Thread-99] iv.core.DiscoveryService.status -     [STATE]  xpto5  ACTIVE
                  2011-01-14 05:01:27,121 INFO  [BuildWebTierHomeCacheThread] iv.subsmgmt.facade -  the list returned is,[]
                  2011-01-14 05:01:27,121 INFO  [BuildWebTierHomeCacheThread] iv.subsmgmt.facade -  the list returned is,[]
                  2011-01-14 05:01:27,136 INFO  [BuildWebTierHomeCacheThread] iv.subsmgmt.facade -  the list returned is,[]
                  2011-01-14 05:01:27,136 INFO  [BuildWebTierHomeCacheThread] iv.subsmgmt.facade -  the list returned is,[]
                  2011-01-14 05:01:27,152 INFO  [BuildWebTierHomeCacheThread] iv.subsmgmt.facade -  the list returned is,[]
                  2011-01-14 05:01:27,152 INFO  [BuildWebTierHomeCacheThread] iv.subsmgmt.facade -  the list returned is,[]
                  2011-01-14 05:01:27,167 INFO  [BuildWebTierHomeCacheThread] iv.subsmgmt.facade -  the list returned is,[]
                  2011-01-14 05:01:27,183 INFO  [BuildWebTierHomeCacheThread] iv.subsmgmt.facade -  the list returned is,[]
                  2011-01-14 05:01:27,183 INFO  [BuildWebTierHomeCacheThread] iv.subsmgmt.facade -  the list returned is,[]
                  2011-01-14 05:01:39,918 INFO  [Thread-95] iv.core.DiscoveryService.status -     [STATE]  xpto6  ACTIVE
                  2011-01-14 05:01:46,590 INFO  [Thread-216] iv.core.alert.dbcoordinator - Denied tuning Tuner (AlertTuning) id 28849

                  • 6. Re: Database Tuning on MDR Secondary Manager

                    What is the size of iv_alert and iv_packetlog? -- > <MySQL>\data\lf

                    You can also count the rows from the MySQL CLI -- > select count(*) from iv_alert; // select count(*) from iv_packetlog;

                     

                    If they return a few million rows you could run purge.bat to decrease the size of the tables and try again....

                     

                     

                    Message was edited by: David_Aloy on 20/01/11 17:53:09 GMT
                    • 7. Re: Database Tuning on MDR Secondary Manager

                      Hello David,

                       

                      The BD has 520704 alerts and 445043 packet logs, the size is 220 MB and 185 MB respectively.

                       

                      I think the DB is not so big at this time.

                      • 8. Re: Database Tuning on MDR Secondary Manager

                        Definitely not a size issue... Is there any other task running on the manager? For example File Maintenance?

                        • 9. Re: Database Tuning on MDR Secondary Manager

                          There are other tasks in the Manager, but they don't run at the same different, the alert data pruning run's eight hours before the DB tunning, and the backup of the DB is scheduled in a different day.

                          1 2 Previous Next