05-21-2010
Rebooting 3 to 1 Cluster nodes.
hello Gurus,
My current set up is 3 to 1 Cluster (SUN Cluster 3.2) running oracle database. Task is to reboot the servers. My query is about the procedure to do the same.
My understanding is suspend the databases to avoid switchover. Then execute the command scshutdown to down the cluster and i'll be at OK prompt. Please help with the correct procedure.
Thanks in advance.
10 More Discussions You Might Find Interesting
1. High Performance Computing
Hi ! I have a simple setup of 2 PC (with linux Red-Hat) where the first PC is the primary machine and the second the backup. I use DRBD for data replication and Red-Hat cluster suite for HA (High Availability). I have tested both.
Now I NEED a COMMON IP ADDRESS (or Master/unique IP address) for... (0 Replies)
Discussion started by: Danny Gilbert
0 Replies
2. UNIX for Dummies Questions & Answers
Hi ! I have a simple setup of 2 PC (with linux Red-Hat) where the first PC is the primary machine and the second the backup. I use DRBD for data replication and Red-Hat cluster suite for HA (High Availability). I have tested both.
Now I NEED a COMMON IP ADDRESS (or Master/unique IP address) for... (3 Replies)
Discussion started by: Danny Gilbert
3 Replies
3. Red Hat
Hi all, i have 3 nodes cluster (Centos 5 cluster suit) with out quorum disk,
node vote = 1,
the value of a quorum = 2,
when 2 nodes going offline, cluster services are destoys.
How i can save the cluster and all services(move all services to one alive node)
with out quorum disk when other... (3 Replies)
Discussion started by: Flomaster
3 Replies
4. Solaris
Hi
we have 2 solaris 10 servers in veritas cluster.
also we have oracle cluster on the database end.
now we have a requirement to reboot both the servers as it has been running for more than a year.
can any one tell what is the procedure to bring down the cluster services in both the nodes... (7 Replies)
Discussion started by: newtoaixos
7 Replies
5. Solaris
Hey Admins,
I am running sun cluster 3.2 x86 on Vmware. I m facing an issue from 2 days..
One main node is continuously rebooting..... not sure... whats woring...
I just had change heartbeat timeout values on 1 this node... Now both node are just rebooting itself..seems panic..
Any... (1 Reply)
Discussion started by: snchaudhari2
1 Replies
6. Red Hat
Hi all.
May I get some expert advice on troubleshooting performance issues of a 1000 nodes Apache LB cluster. Users report slow loading/response of webpages. Different websites are hosted on this cluster for different clients. But all are reporting the same issue.
Could you please let me know... (1 Reply)
Discussion started by: admin_xor
1 Replies
7. AIX
Hi,
A customer I'm supporting once upon a time broke their 2 cluster node database servers so they could use the 2nd standby node for something else. Now sometime later they want to bring the 2nd node back into the cluster for resilance. Problem is there are now 3 VG's that have been set-up... (1 Reply)
Discussion started by: elcounto
1 Replies
8. UNIX for Advanced & Expert Users
Is there any way to create a arbitrary node for ocfs2 on a virtual machine (others are physical servers) so it won't go panic when one of physical server goes down?
This is for load balanced application servers.
Any setting example or tips?
Thanks. (0 Replies)
Discussion started by: malayo
0 Replies
9. Red Hat
Hi All;
I try to build a Redhat Cluster (CentOS 6) on vmware. But each node sees the other down like:
# clustat
Cluster Status for mycluster @ Wed Apr 8 11:01:38 2015
Member Status: Quorate
Member Name ID Status
------ ---- ... (0 Replies)
Discussion started by: Meacham12
0 Replies
10. Red Hat
Hi All;
I try to build a Redhat Cluster (CentOS 6) on vmware. But each node sees the other down like:
# clustat
Cluster Status for mycluster @ Wed Apr 8 11:01:38 2015
Member Status: Quorate
Member Name ID Status
------ ---- ... (1 Reply)
Discussion started by: Meacham12
1 Replies
LEARN ABOUT LINUX
clusterdb
CLUSTERDB(1) PostgreSQL Client Applications CLUSTERDB(1)
NAME
clusterdb - cluster a PostgreSQL database
SYNOPSIS
clusterdb [ connection-option... ] [ [ --verbose ] [ -v ] ] [ --table | -t table ] [ dbname ]
clusterdb [ connection-option... ] [ [ --all ] [ -a ] ] [ [ --verbose ] [ -v ] ]
DESCRIPTION
clusterdb is a utility for reclustering tables in a PostgreSQL database. It finds tables that have previously been clustered, and clusters
them again on the same index that was last used. Tables that have never been clustered are not affected.
clusterdb is a wrapper around the SQL command CLUSTER [cluster(7)]. There is no effective difference between clustering databases via this
utility and via other methods for accessing the server.
OPTIONS
clusterdb accepts the following command-line arguments:
-a
--all Cluster all databases.
[-d] dbname
[--dbname] dbname
Specifies the name of the database to be clustered. If this is not specified and -a (or --all) is not used, the database name is
read from the environment variable PGDATABASE. If that is not set, the user name specified for the connection is used.
-e
--echo Echo the commands that clusterdb generates and sends to the server.
-q
--quiet
Do not display progress messages.
-t table
--table table
Cluster table only.
-v
--verbose
Print detailed information during processing.
clusterdb also accepts the following command-line arguments for connection parameters:
-h host
--host host
Specifies the host name of the machine on which the server is running. If the value begins with a slash, it is used as the directory
for the Unix domain socket.
-p port
--port port
Specifies the TCP port or local Unix domain socket file extension on which the server is listening for connections.
-U username
--username username
User name to connect as.
-w
--no-password
Never issue a password prompt. If the server requires password authentication and a password is not available by other means such as
a .pgpass file, the connection attempt will fail. This option can be useful in batch jobs and scripts where no user is present to
enter a password.
-W
--password
Force clusterdb to prompt for a password before connecting to a database.
This option is never essential, since clusterdb will automatically prompt for a password if the server demands password authentica-
tion. However, clusterdb will waste a connection attempt finding out that the server wants a password. In some cases it is worth
typing -W to avoid the extra connection attempt.
ENVIRONMENT
PGDATABASE
PGHOST
PGPORT
PGUSER Default connection parameters
This utility, like most other PostgreSQL utilities, also uses the environment variables supported by libpq (see in the documentation).
DIAGNOSTICS
In case of difficulty, see CLUSTER [cluster(7)] and psql(1) for discussions of potential problems and error messages. The database server
must be running at the targeted host. Also, any default connection settings and environment variables used by the libpq front-end library
will apply.
EXAMPLES
To cluster the database test:
$ clusterdb test
To cluster a single table foo in a database named xyzzy:
$ clusterdb --table foo xyzzy
SEE ALSO
CLUSTER [cluster(7)]
Application 2010-05-14 CLUSTERDB(1)