RE: Move to new hardware and upgrade o/s
- From: "Cunningham, Mike" <mcunningham@xxxxxxxxxxxxxx>
- To: "ksmadduri@xxxxxxxxx" <ksmadduri@xxxxxxxxx>, oracle Freelists <Oracle-L@xxxxxxxxxxxxx>
- Date: Fri, 6 Jun 2014 10:41:17 -0700
Hi Kumar, we do something similar to what you are discussing. When I have a
new server that will re place an old server here is what we do. Assume old
server is named *svrprd*.
1) Build new server and name it svrprdnew (ip is not important at this
point).
2) Install all necessary software (oracle, agents, etc.)
a. In this case I would install both the same oracle version as on svrprd
and the new version in a different oracle home
3) Also, prepare filesystems as you have stated.
Now come the maintenance window to put new server into service. It takes me
about 45 minutes on average, but we have the ability to be down on weekends.
4) Move databases from srvprd to svrprdold
5) Rename svrprd to srvprdold and give it a new ip address. Restart
network.
6) Rename svrprdnew to srvprd and give it the proper ip address so it is
the same as original srvprd server. Reboot.
At this time, when the new srvprd server is finished with the reboot nobody in
the organization should even realize the hardware changed. All host names and
ip addresses are as they were originally.
When the appropriate time arrives to upgrade the databases you will already
have the new oracle home ready for the upgrade.
I hope this helps and I’m sorry I don’t use ASM so I can’t offer help in that
area, but I would suppose that should work fine.
Michael Cunningham
Senior Database Administrator
The Doctors' Company
707.226.0221 - desk
707.337.0184 - cell
From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On
Behalf Of Kumar Madduri
Sent: Friday, June 06, 2014 10:24 AM
To: oracle Freelists
Subject: Move to new hardware and upgrade o/s
I am working on moving the current boxes to new ones and upgrade to 11.2.0.4
The original idea was to do this.
Install software and move the databases one by one. Create new firewall rules
for this because host name and ip change.
But another thing came to mind since we have firewalls and I would have to
redefine new firewall rules
1. Get new box with new hostname.
2. Install 11.2.0.4 Grid, 11.2.0.2 rdbms, 11.2.0.4 rdbms.
3. All our development, int environments are on NAS. So the same storage can be
mounted on new boxes
4. When ready to cut over, shutdown old development box; bring up new box;
re-ip the new box to have same ip address as old box (still keep the new host
name. Just change ip address to old one).
5. Tell asm on new box about the new databases (alter system set asm_diskstring
=''''').
6. Bring up the databases
7. Do the upgrade when developers are ok (one by one since we have more than
one database on the same box in dev and int)
The advantange in this method is
1. We move all databases in one shot from old to new.
2. We can upgrade to 11.2.0.4 one after other
3. Most important, I think is we dont have to worry about firewall rules
because we are getting same ip address back.
The one issue I think in this approach is
Since we use oracle apps, fnd_nodes would not be updated with the new database
server name till we run autoconfig again (thiss would be done as part of
11.2.0.4 upgrade). Till then the topology would be out of sync. But we have not
really enabled 'autoconfig' on our database server. So even though topology
would be out of sync (temporarily),l am thinking we would be ok since tnsnames
would be updated manually for those environments that are not upgraded.
Do you see any issues or is there a better way to accomplish the same ? The
reason I think about this approach is I wanted to avoid redefining all the
firewall rules if I can (with change in IP) and I can decommision the old box
relatively earlier once I am done with the move and it is stable for couple of
weeks.
Thank you
Kumar
Confidentiality Notice: This message and any attachments hereto may contain
confidential and privileged communications or information and/or attorney
client communications or work-product protected by law. The information
contained herein is transmitted for the sole use of the intended recipient(s).
If you are not the intended recipient or designated agent of the recipient of
such information, you are hereby notified that any use, dissemination, copying
or retention of this e-mail or the information contained herein is strictly
prohibited and may subject you to penalties under federal and/or state law. If
you received this e-mail in error, please notify the sender immediately and
permanently delete this e-mail.
Other related posts:
