2 Replies Latest reply on Dec 5, 2007 7:59 PM by Bill Robinson

    How Do You Reduce Bladelogic Disk Usage?

      What steps can be taken to reduce the size of the bladelogic database, and keep it's size from growing out of control?

       

      At one client we manually emptied out the job_run_event table, because support recommended against running the full cleanup job on versions prior to 7.2. Manually cleaning out that table was very effective, reducing database size by 75%.

       

      We just ran a full cleanup in version 7.4.1 and I don't see any change in the database size. We also did a shrink afterwards on the database.

       

      The documentation for the BLCLI clenaup command doesn't explicitly state whether the job_run_event table is emptied. Should I assume it's not?

       

      +Delete : performFullCleanupJob

       

      This command performs a full clean-up job. The clean-up deletes all objects marked for deletion and cleans all unused files from the file server and the temporary file storage area on the Application Server+

        • 1. Re: How Do You Reduce Bladelogic Disk Usage?

          Yesterday we saw further weirdness with this space problem.

          Our populate reports job failed.

          When we looked to see why, it had filled up the entire disk with a tmp file, then went belly up when the disk ran out of space!

          The file reached 21gigs.

          • 2. Re: How Do You Reduce Bladelogic Disk Usage?
            Bill Robinson

            i just tried this on my demo drive and it does seem to clean out the job_run_event table:

             

            -


            SQL> select job_id from job where name like 'RedHat Patch Analysis';

             

            JOB_ID

            -


            2000021

             

            SQL> select job_event_id from job_run_event where job_id = 2000021;

             

            JOB_EVENT_ID

            -


            2000964

            2000966

            2001160

            2001161

            2001162

            2007935

            2007937

            2007933

            2007934

            2007936

             

            10 rows selected.

             

             

            run cleanup blcli

             

             

            SQL> select job_id from job where name like 'RedHat Patch Analysis';

             

            no rows selected

             

            SQL> select job_event_id from job_run_event where job_id = 2000021;

             

            no rows selected

             

            -


             

             

             

            this was a 7.3 install upgraded to 7.4.1, oracle xe on linux