Sponsored Content
Operating Systems AIX HACMP 5.4.1->5.5 offline upgrade - different instance numbers ? Post 302655313 by bakunin on Wednesday 13th of June 2012 04:22:59 AM
Old 06-13-2012
Might this fix IZ14738 apply to your problem? See the following link for details:

IBM IZ14738: INSTANCE NUMBER DISCREPANCY LEADS TO PARTITIONED CLUSTER

I hope this helps.

bakunin
 

9 More Discussions You Might Find Interesting

1. AIX

Upgrade Hacmp to 5.4

Anyone ever did the upgrade before from 5.1? Any tips? (0 Replies)
Discussion started by: adiriot
0 Replies

2. Shell Programming and Scripting

replace first instance(not first instance in line)

Alright, I think I know what I am doing with sed(which probably means I don't). But I cant figure out how to replace just the first occurance of a string. I have tried sed, ed, and grep but can't seem to figure it out. If you have any suggestions I am open to anything! (3 Replies)
Discussion started by: IronHorse7
3 Replies

3. AIX

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... (1 Reply)
Discussion started by: itik
1 Replies

4. AIX

upgrade hacmp

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

5. AIX

MQ upgrade(ver.6to7) in a HACMP cluster

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

6. AIX

HACMP does not start db2 after failover (db2nodes not getting modified by hacmp)

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

7. Shell Programming and Scripting

Need help in getting the oracle instance name which is offline in 10g through shell scripting

:wall:Hi, I am not sure whether i can post this question in this forum or not. because it is not completely releated to unix, but also oracle. My question is, How can we know the instance name(particularly the last number, eg., in INST_DB12, i need 12) when it is OFFLINE(i.e., down)... (1 Reply)
Discussion started by: Dpu
1 Replies

8. Shell Programming and Scripting

help needed to put instance numbers

Hi All I need help am having a source file as below emp dept class subclass region country division first i need to get line count and i need to divide by 3 it is an parameter passing value number of lines 7 (8 Replies)
Discussion started by: ragu.selvaraj
8 Replies

9. Shell Programming and Scripting

Help extracting single instance of numbers which repeat

Hi, the title isn't very descriptive but it'll be easier to explain what I need if I write out the coordinates from which I need to extract certain information: ATOM 2521 C MAM X 61 44.622 49.357 12.584 1.00 0.00 C ATOM 2522 H MAM X 61 43.644 49.102 12.205 ... (10 Replies)
Discussion started by: crunchgargoyle
10 Replies
PG_UPGRADECLUSTER(8)					 Debian PostgreSQL infrastructure				      PG_UPGRADECLUSTER(8)

NAME
pg_upgradecluster - upgrade an existing PostgreSQL cluster to a new major version. SYNOPSIS
pg_upgradecluster [-v newversion] version name [newdatadir] DESCRIPTION
pg_upgradecluster upgrades an existing PostgreSQL server cluster (i. e. a collection of databases served by a postmaster instance) to a new version specified by newversion (default: latest available version). The configuration files of the old version are copied to the new cluster. The cluster of the old version will be configured to use a previously unused port since the upgraded one will use the original port. The old cluster is not automatically removed. After upgrading, please verify that the new cluster indeed works as expected; if so, you should remove the old cluster with pg_dropcluster(8). Please note that the old cluster is set to "manual" startup mode, in order to avoid inadvertently changing it; this means that it will not be started automatically on system boot, and you have to use pg_ctlcluster(8) to start/stop it. See section "STARTUP CONTROL" in pg_createcluster(8) for details. The newdatadir argument can be used to specify a non-default data directory of the upgraded cluster. It is passed to pg_createcluster. If not specified, this defaults to /var/lib/postgresql/version/name. Please note that this program cannot upgrade clusters which use tablespaces. If you use those, you have to upgrade manually. OPTIONS
-v newversion Set the version to upgrade to (default: latest available). --logfile filel Set a custom log file path for the upgraded database cluster. --locale=locale Set the default locale for the upgraded database cluster. If this option is not specified, the locale is inherited from the old cluster. --lc-collate=locale --lc-ctype=locale --lc-messages=locale --lc-monetary=locale --lc-numeric=locale --lc-time=locale Like --locale, but only sets the locale in the specified category. HOOK SCRIPTS
Some PostgreSQL extensions like PostGIS need metadata in auxiliary tables which must not be upgraded from the old version, but rather initialized for the new version before copying the table data. For this purpose, extensions (as well as administrators, of course) can drop upgrade hook scripts into /etc/postgresql-common/pg_upgradecluster.d/. Script file names must consist entirely of upper and lower case letters, digits, underscores, and hyphens; in particular, dots (i. e. file extensions) are not allowed. Scripts in that directory will be called with the following arguments: <old version> <cluster name> <new version> <phase> Phases: init A virgin cluster of version new version has been created, i. e. this new cluster will already have template1, but no user databases. Please note that you should not create tables in this phase, since they will be overwritten by the dump/restore operation. finish All data from the old version cluster has been dumped/reloaded into the new one. The old cluster still exists. The scripts are called as the user who owns the database. SEE ALSO
pg_createcluster(8), pg_dropcluster(8), pg_lsclusters(1), pg_wrapper(1) AUTHOR
Martin Pitt <mpitt@debian.org> Debian 2012-10-08 PG_UPGRADECLUSTER(8)
All times are GMT -4. The time now is 12:46 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy