Users Guide

Restoring Databases | Getting Started
76 OMNM 6.5.3 User Guide
Restoring Databases
Restoring from FILENAME.mysql is a three step process. This occurs, again, in a command shell:
1 Drop the database:
mysqladmin -u USERNAME -p drop owbusdb
or
mysqladmin -u USERNAME --password=[password] drop owbusdb
2 Recreate the database
mysqladmin -u USERNAME -p create owbusdb
or
mysqladmin -u USERNAME --password=[password] create owbusdb
3 Import the backup data
mysql -u USERNAME -p owbusdb < FILENAME.mysql
or
mysql -u USERNAME --password=[password] owbusdb < FILENAME.mysql
Here are restoration commands for all the databases:
mysql -u root --password=dorado owmetadb < owmetadb.mysql
mysql -u root --password=dorado owbusdb < owbusdb.mysql
mysql -u root --password=dorado lportal < lportal.mysql
mysql -u root --password=dorado synergy < synergy.mysql
NOTE:
If the database contains Asian Characters use the following restore database
mysqldump -u root --password=dorado -A --routines --default-character-
set=latin1 < omnm.mysql
NOTE:
If you receive the error “Access Denied. Invalid Role for this device” or if the application(s) fails with
error indicating that it cannot connect to the device after a network change, There may be a DNS
resolution issue. You may still be able to ping or connect to a device by IP address but testing server
connectivity by using hostname will confirm or rule out a DNS problem. This would only be a problem if
the device(s) were discovered or set to “Manage by Hostname.” If the system was migrated to a system
that is not using DNS, then name resolution could fail and there would be no connectivity to devices. The
solution from the Resource Manager is to Right-click > edit and un-check “Manage by Hostname.” This
will then default to Manage by IP address. Alternatively, you can fix name resolution in your environment.
NOTE:
Whenever you upgrade your system and your database is on a separate server, you must run the
dbpostinstall script on the (primary) application server too.