Can you give me a bit of information as to why you thought you had database problems in the first place?
OME maintains the database by running cleanup and repair scripts automatically on a daily schedule.
Running the installshield repair only affects the files on the file system, but does not touch the SQL database.
If you happened to modify the database manually, we'd need a bit more info on that to see how best to help.
Depending on what you are looking to do, you can either:
1. Install a new copy of OME on a new box or VM and start fresh.
2. If you want to retain your database (and assuming it has not been corrupted), you can do a MS backup of the database and install a new copy of OME on a new VM/box and use the re-targeting instructions to install the same version of OME and re-target to your backed up database. But note that needs to be the same version of OME.
Can you give me a bit of information as to why you thought you had database problems in the first place?
OME maintains the database by running cleanup and repair scripts automatically on a daily schedule.
Running the installshield repair only affects the files on the file system, but does not touch the SQL database.
If you happened to modify the database manually, we'd need a bit more info on that to see how best to help.
Depending on what you are looking to do, you can either:
1. Install a new copy of OME on a new box or VM and start fresh.
2. If you want to retain your database (and assuming it has not been corrupted), you can do a MS backup of the database and install a new copy of OME on a new VM/box and use the re-targeting instructions to install the same version of OME and re-target to your backed up database. But note that needs to be the same version of OME.
Had OME 1.1 running with SQL onbox on a VM server -> Then Installed OME 2.0.1 on a different VM box and connected the app to the database on the earlier box and disabled OME 1.1 services.
I changed the SNMP trap settings on all of my servers to point to the new OME server
My Alert traps don't seem to function right - even after I selecting most of the MIB's - I just a few email or alerts being trapped.
Couple of changes on Server names do not reflect in OME DB - it still picks up the OLD DNS name - even after deleting it and re-discovering it.
I somehow feel due to this - support assist is also not functioning right - as alert traps are not being captured.
vikoda
18 Posts
1214
0
Posted March 17th, 2015 12:00
Can anyone please help?