We've just done the same. We named the new server as per the old one for simplicity, we have a number of systems connecting to this server and instead of amending all the tnsnames files this was easier. We didn't have any issues as long as you only have one visible on the network at a time. We copied the database over -> re-created listener,tnsnames etc -> shut original down and started the mk2. Not aware of any 'hard coding' of server name apart from the above files.
I will have to rename the new server to meet our server farm naming standards - the old 1 is 'Oracle1".
1. When you copied the database over - this is the step I'm looking into now. Did you use the Database Upgrade Assistant or Export, then Import or another method? Several ways to get there I suppose.
2. You "started the mk2" Is this the name of your new server or an Oracle term? Sorry, I'm a SQl Server DBA, fairly new with Oracle.
As it happened we exported our live Db and imported into a blank DB on the 10g server. It was fairly small (30GB), so this was adequate for what we wanted to do.
Sorry about the original 'mk2' reference, I was referring to the 'new' instance on the 10g server.
Thanks kutz13. That helps. I did some reading last night about the Database Upgrade Assistant - that upgrades the db in-place. So of course I cant use that because my new 10g db will be on another server.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.