Please login or register. August 18, 2019, 12:29:02 AM

Author Topic: hacmp temp storage for tl/sp upgrade  (Read 12091 times)

0 Members and 1 Guest are viewing this topic.


  • New Member
  • *
  • Posts: 2
  • Karma: +0/-0
hacmp temp storage for tl/sp upgrade
« on: October 24, 2008, 11:15:39 PM »
Hi Gurus,

Is it possible to create a temporary storage on the oraclevg FS for the tl8sp2? My rootvg is getting low on free space, less than 3G.

I'm I going to use System Management (C-SPOC)/HACMP Logical Volume Management/Shared File Systems.

Is that correct? Is that safe?

I want to do the update always on the passive node which it doesn't have the resources. Is that possible? You can see the oraclevg on both node.

Thank you for any comments you may add.

John R Peck

  • Administrator
  • Senior Member
  • *****
  • Posts: 134
  • Karma: +0/-0
Re: hacmp temp storage for tl/sp upgrade
« Reply #1 on: October 25, 2008, 04:10:13 PM »
3GB of free space shouldn't be a problem surely for any update - this isn't Windows Bloatware  ;D 
You could run three complete AIX web servers and the entire rootvg site in that space.

If you are updating Oracle, that and any other applications, should always be in at least a separate filesystem or two,
and ideally in a separate volume group.  You can add another volume to a volume group to give it more space and remove it later.  Increasing filesystems is easy, shrinking them back again may not be ! 

Sounds like you have isolated Oracle and I believe your passive node updating is the correct approach.


  • Jr. Member
  • **
  • Posts: 5
  • Karma: +0/-0
Re: hacmp temp storage for tl/sp upgrade
« Reply #2 on: October 26, 2008, 07:04:58 AM »
I do not think it is good idea to keep the TL on the shared storage of the cluster while doing the upgrade on passive node. I hope you are going to stop the HACMP on passive node before the upgrade.

Better you keep it on a DVD or on a NFS share.


  • Administrator
  • Hero Member
  • *****
  • Posts: 1139
  • Karma: +0/-0
Re: hacmp temp storage for tl/sp upgrade
« Reply #3 on: October 26, 2008, 09:05:23 PM »
1) I agree with hellonair - that it is not a good idea to be using shared storage for rootvg maintenance.
2) iirc (if I recall correctly) we advise to bring a nods being updated into a dawn status - move any active resources to the remaining node(s), stop hacmp, and start updates.

Before starting any updates on a HACMP node you need to verify that your application/service is supported in the new environment. We have situations discussed here where applications did not work after an update.

With HACMP (PowerHA) I strongly recommend doing an alt_disk_install plus update, so that should the application and update not work as expected you just need to reboot the node to restore the old situation.

Re: 3G in rootvg left. I guess I wonder how large your rootvg disks are - assumming they are mirrored. For an update, that should be plenty - as temporary storage. I generally only have 1G set aside for an update. However, I am wondering a bit about what else you have in your rootvg - if it is filling up. Applications and data should not be in rootvg, but in seperate volume groups.