Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Community Member

LMS 4.1 - huge upm.db

Hi All,

From one day to the next our UPM database (upm.db) has blown up from 4 Gb to 35 Gb.

Data purging didn't reduce the size of the db.

What happened ? And how can I compact the db again ?

Thank you for your suggestions.

1 ACCEPTED SOLUTION

Accepted Solutions
Silver

Re: LMS 4.1 - huge upm.db

Hi,

You can reinitialize the database if you do not have a requirement to retain the data.

This will delete the contents of the entire database including all polled data, poller and threshold configurations.

1.  Stop the Ciscoworks daemons (ie 'net stop crmdmgtd')

2.  Take a backup of LMS and HUM

From a command line,

3.  cd $NMSROOT\bin (where $NMSROOT is the location of your installation)

4.  perl dbRestoreOrig.pl dsn=upm dmprefix=UPM

5.  Restart the daemons (ie 'net start crmdmgtd')

6.  Wait 20 minutes before logging back on to LMS

If you want to preserve the data:

1.  Verify you have at least 2x the size of the upm.db free on the drive.

2.  Set the purge schedule to daily for purging all the old data.

3.  Run a purge job & wait for the purge job to complete.

4.  Stop the Ciscoworks daemons (ie 'net stop crmdmgtd')

5.  Take a backup of LMS and HUM

From a command line,

6.  Rebuild the database.

6.1  cd $NMSROOT\databases\upm

6.2  dbunload -c  "dbf=upm.db;uid=dba;pwd=" -ar

Note: replace with your password.

7.  Wait.  This process is time consuming.

8.  Restart the daemons (ie 'net start crmdmgtd')

9.  Wait 20 minutes before logging back on to LMS

Thanks

4 REPLIES
Silver

Re: LMS 4.1 - huge upm.db

Hi,

You can reinitialize the database if you do not have a requirement to retain the data.

This will delete the contents of the entire database including all polled data, poller and threshold configurations.

1.  Stop the Ciscoworks daemons (ie 'net stop crmdmgtd')

2.  Take a backup of LMS and HUM

From a command line,

3.  cd $NMSROOT\bin (where $NMSROOT is the location of your installation)

4.  perl dbRestoreOrig.pl dsn=upm dmprefix=UPM

5.  Restart the daemons (ie 'net start crmdmgtd')

6.  Wait 20 minutes before logging back on to LMS

If you want to preserve the data:

1.  Verify you have at least 2x the size of the upm.db free on the drive.

2.  Set the purge schedule to daily for purging all the old data.

3.  Run a purge job & wait for the purge job to complete.

4.  Stop the Ciscoworks daemons (ie 'net stop crmdmgtd')

5.  Take a backup of LMS and HUM

From a command line,

6.  Rebuild the database.

6.1  cd $NMSROOT\databases\upm

6.2  dbunload -c  "dbf=upm.db;uid=dba;pwd=" -ar

Note: replace with your password.

7.  Wait.  This process is time consuming.

8.  Restart the daemons (ie 'net start crmdmgtd')

9.  Wait 20 minutes before logging back on to LMS

Thanks

LMS 4.1 - huge upm.db

I saw this once where a customer added a poller for all ports on all devices.

Did you add a poller?

Cheers,

Michel

Community Member

LMS 4.1 - huge upm.db

Hi Michel,

No poller was added recently.

Community Member

LMS 4.1 - huge upm.db

Hi ngoldwat,

The procedure worked fine. I have again a slim upm.db without losing data.

Thanks for your help.

Silvia

964
Views
0
Helpful
4
Replies
CreatePlease to create content