06-25-2008
hacmp upgrade with db2
Hi All,
My company is going to upgrade the db2 on the one node hacmp, I think there's one backup.
After the upgrade of the db2. Do I need to restart cluster and server? I mean, do a graceful shutdown of the cluster, reboot the server and do a cluster start. Is that it? Do I need to reboot the backup server after the primary was rebooted and cluster is up.
Please advise me more.
Thanks in advance.
8 More Discussions You Might Find Interesting
1. AIX
Anyone ever did the upgrade before from 5.1? Any tips? (0 Replies)
Discussion started by: adiriot
0 Replies
2. AIX
Hello
I am a noobie to HACMP
I have 2 55A servers and a 7031 disk subsystem
For HACMP to work, do I need to have the hdisks on both servers to match the same drives??
The hdisks on each box are currently different:
hdisk0 and hdisk1 are the internal disks and hdisk2-5 are on the D24 on... (1 Reply)
Discussion started by: mhenryj
1 Replies
3. AIX
Friends,
take a look at this:
clmid007:/clocal/tech/user/testlab/cppruntime $ lslpp -l |grep xlC
xlC.aix50.rte 8.0.0.4 COMMITTED C Set ++ Runtime for AIX 5.0
xlC.cpp 6.0.0.0 COMMITTED C for AIX Preprocessor
xlC.msg.en_US.cpp 6.0.0.0 ... (3 Replies)
Discussion started by: ak835
3 Replies
4. UNIX for Dummies Questions & Answers
Hi...
I m working on UNIX z/OS. Actually i have to pass the parameters from the JCL to java-db2 program thru PARM. I am able to pass the arguments but the problem occured is, it is throwing an exception while loading the db2 driver as 'Javaclassnotfound:com.ibm.db2.jcc.DB2Driver'... (0 Replies)
Discussion started by: Sujatha Gowda
0 Replies
5. AIX
Hi,
I need to upgrade one of my clusters from HACMP 5.41 to HACMP 6.1.
Is there an easy + clean way to do it ? Any hurdles I have to anticipate? What should I read - anything I found so far seems to talk only about HACMP 5.x - and looks pretty straight forward.
Thanks and regards
zxmaus (1 Reply)
Discussion started by: zxmaus
1 Replies
6. AIX
Hi
What is the procedure to upgrade the MQ from 6 to 7 in aix hacmp cluster. Do i need to bring down the cluster
services running in both the nodes and then give #smitty installp in both the nodes separately. Please assist... (0 Replies)
Discussion started by: samsungsamsung
0 Replies
7. AIX
hi,
when I do a failover, hacmp always starts db2 but recently it fails to start db2..noticed the issue is db2nodes.cfg is not modified by hacmp and is still showing primary node..manually changed the node name to secondary after which db2 started immediately..unable to figure out why hacmp is... (4 Replies)
Discussion started by: gkr747
4 Replies
8. AIX
Hello,
I did offline HACMP(PowerHA) upgrade 5.4.1 to 5.5 - basically stopped HACMP services and upgraded cluster.* filesets.
Tried to start services again - topsvcs refused to start on second node complaining that node instance numbers are different - and indeed they are different.
This is... (2 Replies)
Discussion started by: vilius
2 Replies
LEARN ABOUT OPENSOLARIS
scversions
scversions(1M) System Administration Commands scversions(1M)
NAME
scversions - Sun Cluster version management
SYNOPSIS
scversions [-c]
DESCRIPTION
Note -
Beginning with the Sun Cluster 3.2 release, Sun Cluster software includes an object-oriented command set. Although Sun Cluster software
still supports the original command set, Sun Cluster procedural documentation uses only the object-oriented command set. For more infor-
mation about the object-oriented command set, see the Intro(1CL) man page.
The scversions command commits the cluster to a new level of functionality after a rolling-upgrade to new Sun Cluster software. With no
arguments, the scversions command prints a message indicating whether a commitment is needed.
OPERANDS
The following operands are supported:
-c Commit the set of nodes that are currently active members of the cluster to the highest possible level of functionality.
When you upgrade a node (either through upgrade to a new release of the product or by application of a patch) and boot it back
into the cluster, some of the internal protocols on that node might have to run at lower versions in order to cooperate cor-
rectly with other nodes in the cluster. When the cluster is in this state, some administrative actions might be disabled and
some new functionality introduced in the upgrade might be unavailable.
When you run this command once from any node after all nodes are upgraded, the cluster switches to the highest versions of
internal protocols possible. Assuming that all nodes have the same Sun Cluster software installed at that time, all new func-
tionality becomes available and any administrative restrictions are removed.
If a node that has not been upgraded is an active member of the cluster at the time you run the -c option to scversions, the
command has no effect because the cluster is already running at the highest possible level of functionality.
If a node has not been upgraded and is not an active member of the cluster when you run the -c option to scversions (for exam-
ple, if that node is down for maintenance), the internal protocols of the cluster are upgraded to the highest possible ver-
sions. You might have to upgrade the node that was not an active member of the cluster to enable it to rejoin the cluster.
EXIT STATUS
0 Success
non-zero Failure
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWsczu |
+-----------------------------+-----------------------------+
|Interface Stability |Evolving |
+-----------------------------+-----------------------------+
SEE ALSO
scinstall(1M)
Sun Cluster 3.2 17 Aug 2007 scversions(1M)