Move Grid Control repository db to a different server.

If you want to restore to another server that will have the same name (and IP address) as the original server, your steps should work just fine.

The IP address will be different, will that present a problem?

Also,
We are moving from hp-ux servers to titanium servers.

Thanks

I expect that will be a problem.  I've moved other Oracle databases from server to server and I knew that i just needed to changes the tnsnames.ora files on the clients or applciation servers to the new server.  For the OEM Grid Control repository however, I think it may use configuration values that are stored in other places than the tnsnames.ora file, but I don't where these might be, or if Oracle supports modifying them.

When I said "that will be a problem" I meant the different IP address.  I don't know if a different O/S will be a problem, or not.

But if the O/S is different, there is no way that you can do a backup and restore from the old server to the new server, right?

Yeah, that's right. I was trying to research metalink but the only note that I could fine was "Note 388090.1"  Title: Cross Platform EM Grid Control Repository/OMS Migration.  Which I'm not sure is still supported.  The Note states that it is Distributed to customers with guidance from an Oracle Support because of the complex process.  I couldn't fine the note on matalink anymore but I was able to google it with the subject "Moving db repository to another existing database without losing the data"

Any thoughts

That was one of my concerns, keeping the old data.  If all possible we need the old data.