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)
Hi,
Can anybody advice whether it is possible to configure HACMP in HP-UX Server.
To my knowledge HACMP is IBM Solution.
Thanks && Regards,
N. Poorna Chandra Rao. (2 Replies)
Hi,
I needed space on a FS, and when I've added the space on the filesystem, I did it trough the regular smitty fs inteface and not with smitty cl_lvm.
Can someone help me to repair the situat before a faileover happen ?
Thanks for your help,:mad: (13 Replies)
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)
Hi.
We have a two node HA cluster.
We got a request to change one of the VG name?
Is there an option to do this online ? If it requires downtime can someone please explain me the steps for doing it ?
Let me know if you need any outputs from the servers (1 Reply)
Hi,
I have question about HA. I have 2 node cluster (node A and node B). I have configured network and disk HB. If my network is up and i remove both the fc cables from node A will my cluster failover to node B? I have checked and its not working, if i want my cluster to failover in this... (5 Replies)
hello
ive 2 nodes aix 6100-04-10-1119 with hacmp 6.1.0.0
my qustion is :
can i add default gateway to one member node with hacmp a live or to do take over to realse one of the members ?
thanks
When it is urgent, then open the thread up in the appropriate subforum next time, thanks. (3 Replies)
Discussion started by: ariec
3 Replies
LEARN ABOUT DEBIAN
postgresql-common
PG_WRAPPER(1) Debian PostgreSQL infrastructure PG_WRAPPER(1)NAME
pg_wrapper - wrapper for PostgreSQL client commands
SYNOPSIS
client-program [--cluster version/cluster] [...]
(client-program: psql, createdb, dropuser, and all other client programs installed in /usr/lib/postgresql/version/bin).
DESCRIPTION
This program is run only as a link to names which correspond to PostgreSQL programs in /usr/lib/postgresql/version/bin. It determines the
configured cluster and database for the user and calls the appropriate version of the desired program to connect to that cluster and
database, supplying any specified options to that command.
The target cluster is selected by the following means, in descending order of precedence:
1. explicit specification with the --host option
2. explicit specification with the --cluster option
3. if the PGHOST environment variable is set, no further cluster selection is performed. The default PostgreSQL version and port number
(from the command line, the environment variable PGPORT, or default 5432) will be used.
4. explicit specification with the PGCLUSTER environment variable
5. matching entry in ~/.postgresqlrc (see postgresqlrc(5)), if that file exists
6. matching entry in /etc/postgresql-common/user_clusters (see user_clusters(5)), if that file exists
7. If only one local cluster exists, that one will be selected.
8. If several local clusters exist, the one listening on the default port 5432 will be selected.
If none of these rules match, pg_wrapper aborts with an error.
OPTIONS --cluster version/cluster
cluster is either the name of a local cluster, or takes the form host:port for a remote cluster. If port is left empty (i. e. you just
specify host:), it defaults to 5432.
ENVIRONMENT
PGCLUSTER
If $PGCLUSTER is set, its value (of the form version/cluster) specifies the desired cluster, similar to the --cluster option. However,
if --cluster is specified, it overrides the value of $PGCLUSTER.
PG_CLUSTER_CONF_ROOT
This specifies an alternative base directory for cluster configurations. This is usually /etc/postgresql/, but for testing/development
purposes you can change this to point to e. g. your home directory, so that you can use the postgresql-common tools without root
privileges.
FILES
/etc/postgresql-common/user_clusters
stores the default cluster and database for users and groups as set by the administrators.
$HOME/.postgresqlrc
stores defaults set by the user himself.
SEE ALSO user_clusters(5), postgresqlrc(5)AUTHOR
Martin Pitt <mpitt@debian.org>
Debian 2013-01-04 PG_WRAPPER(1)