9 More Discussions You Might Find Interesting
1. Solaris
Hi, hoping someone can help, its been a while since I used Solaris.
After creating a NGZ (non global zone), the NGZ can access the GZ (Global Zone) and the GZ can access the NGZ (using ssh, zlogin)
However, the NGZ cannot access any other netwqork devices, it can't even see the default router
... (2 Replies)
Discussion started by: GazinLincoln
2 Replies
2. Solaris
I am planning to do solaris 11 global zone patching having solaris 10 branded zone. I have a doubts on step 8 specially
Can someone clear my step 8 doubts or if anything wrong between step 1 to step 9 please correct that also as I have pretty good idea about Step 10 mean patching in solaris 10... (2 Replies)
Discussion started by: amity
2 Replies
3. Solaris
Hi Gurus
I am not able to find the patching procedure for solaris 10 ( sol10 u11) to latest patchset with sun cluster having failover zones so that same I should follow.
Take an instance, there are sol1 and sol2 nodes and having two failover zones like sozone1-rg and sozone2-rg and currently... (1 Reply)
Discussion started by: nick101
1 Replies
4. UNIX for Advanced & Expert Users
Dear all,
recently, I migrated a solaris zone from one host to another. The zone was inside of a zpool. The zpool cotains two volumes.
I did the following:
host1:
$ zlogin zone1 shutdown -y -g0 -i0 #Zone status changes from running to installed
$ zpool export zone1
host2:
$ zpool... (2 Replies)
Discussion started by: custos
2 Replies
5. Solaris
Hi All
Kindly let me know how can I move Solaris 10 OS running update 10 on physical machine to another machine solaris zone running Solaris 10 update 11 (2 Replies)
Discussion started by: amity
2 Replies
6. Solaris
Hi,
A quick question: Can Solaris 10 local zones be moved to a Solaris 11 global zone and work well?
Thank you in advance! (5 Replies)
Discussion started by: aixlover
5 Replies
7. Solaris
Hi,
Is it possible to have a Solaris cluster of 2 nodes at SITE-A using SVM and creating metaset using say 2 LUNs (on SAN). Then replicating these 2 LUNs to remote site SITE-B via storage based replication and then using these LUNs by importing them as a metaset on a server at SITE-B which is... (0 Replies)
Discussion started by: dn2011
0 Replies
8. Solaris
I have a general question regarding Zone Migration.
I have an older system that is currently running a zone configured with ProFTPD & SSL.
If I want to migrate or clone that zone to another (much newer) system, will I still have to setup & configure ProFTPD & SSL on the new system? (3 Replies)
Discussion started by: em23
3 Replies
9. Solaris
Hi All ,
I try to install some packages in my global zone...
On the execution of the installion of the script it quits by saying the error
"Non global zone check failed"
Kindly help me in this regard
Thanks in advance,
jeganr (7 Replies)
Discussion started by: jegaraman
7 Replies
CLUSTERDB(1) PostgreSQL Client Applications CLUSTERDB(1)
NAME
clusterdb - cluster a PostgreSQL database
SYNOPSIS
clusterdb [ connection-options... ] [ --table | -t table ] [ dbname ]
clusterdb [ connection-options... ] [ --all | -a ]
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 touched.
clusterdb is a shell script wrapper around the backend command CLUSTER [cluster(7)] via the PostgreSQL interactive terminal psql(1). There
is no effective difference between clustering databases via this or other methods. psql must be found by the script and a database server
must be running at the targeted host. Also, any default settings and environment variables available to psql and the libpq front-end
library do apply.
clusterdb might need to connect several times to the PostgreSQL server, asking for a password each time. It is convenient to have a
$HOME/.pgpass file in such cases.
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 a response.
-t table
--table table
Clusters table only.
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 host begins with a slash, it is used as the directory for
the Unix domain socket.
-p port
--port port
Specifies the Internet TCP/IP 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
--password
Force password prompt.
DIAGNOSTICS
CLUSTER
Everything went well.
clusterdb: Cluster failed.
Something went wrong. clusterdb is only a wrapper script. See CLUSTER [cluster(7)] and psql(1) for a detailed discussion of error
messages and potential problems. Note that this message may appear once per table to be clustered.
ENVIRONMENT
PGDATABASE
PGHOST
PGPORT
PGUSER Default connection parameters.
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 2002-11-22 CLUSTERDB(1)