Administer > General Concepts for Configuration > Reset the NNMi Configuration and Database

Reset the NNMi Configuration and Database

<<This information probably belongs in the administration section, but there doesn’t seem to be a good place for it right now. Move it if we ever get a general administration chapter.>>

If you want to completely restart discovery and redo all of the NNMi configuration, or if the NNMi database has become corrupted, you can reset the NNMi configuration and database. This process deletes all of the NNMi configuration, topology, and incidents.

For information about the commands identified in this procedure, see the appropriate reference pages, or the Linux manpages.

Follow these steps:

  1. Stop the NNMi services:

    ovstop -c

  2. Optional. Because this procedure deletes the database, you might want to back up the existing database before proceeding:

    nnmbackup.ovpl -type offline -target <backup_directory>
  3. Optional. If you want to keep any of the current NNMi configuration, use the nnmconfigexport.ovpl command to output the NNMi configuration to an XML file.

    Tip The nnmconfigexport.ovpl command does not retain SNMPv3 credentials. See the nnmconfigexport.ovpl reference page, or the Linux manpage, for more information.

  4. Optional. Use the nnmtrimincidents.ovpl command to archive the NNMi incidents. Incidents are archived in the CSV format, as described in the nnmtrimincidents.ovpl reference page or Linux manpage.
  5. Drop and recreate the NNMi database.

    • For the embedded database, run the following command:

      nnmresetembdb.ovpl -nostart
    • For an Oracle database, ask the Oracle database administrator to drop and recreate the NNMi database. Maintain the database instance name.
  6. If you have installed iSPIs or stand-alone products that integrate with NNMi, reset those products to remove the old topology identifiers. For specific procedures, see the product documentation.
  7. Start the NNMi services:

    ovstart -c

    NNMi now has only the default configurations as if you had just installed the product on a new system.

  8. Start configuring NNMi. Do one of the following:

    • Use the Quick Start Configuration Wizard.
    • Enter information into the Configuration workspace in the NNMi console.
    • Use the nnmconfigimport.ovpl command to import some or all of the NNMi configuration that you saved in step 3.

Tip If you are using the nnmconfigimport.ovpl command to import large amounts of configurations (such as 9,500 node groups or 10,000 incident configurations), consider using the -timeout option to adjust the import transaction timeout from its default value of 60 minutes (3600 seconds) to something longer. See the nnmconfigimport.ovpl reference page, or the Linux manpage, for more information.