Hi,

How to verify the server i logged is a Standalone server?
Could you help me on this ?

How do you define Stand-alone server?

Frankly speaking,I am new to standalone and do not have knowledge on Standalone server.
If you can refer me some link,with that i will start gaining some knowledge about standalone server.Thanks!

Regards,
Srini

And, how do you define Stand-Alone-Server as yours?

One more question .How to verify the server i logged in is ha/os cluster ?

"Cluster" is an ambiguous term in computer industry. Depending on the vendor and specific contexts, a cluster may refer to wide a variety of environments. In computers, clustering is the use of multiple computers, typically PCs or UNIX workstations, multiple storage devices, and redundant interconnections, to form what appears to users as a single highly available system. Cluster computing can be used for load balancing as well as for high availability. Advocates of clustering suggest that the approach can help an enterprise achieve 99.999 availability in some cases. One of the main ideas of cluster computing is that, to the outside world, the cluster appears to be a single system. Clustering is the use of multiple computers to provide a single service. Load Balancing is a technique to use multiple computers in a cluster. Therefore in a nutshell, load balancing implements a computer cluster.


OS clustering (aka hardware clustering) is designed to manage hardware and os-level failures. These typically work by starting a backup server when a primary fails in such a way that it fully assumes the role of the primary. Failover generally involves re-assigning the failed server IP-Address to the backup (IP-takeover), re-permissioning file system access to the backup (if using a shared file system instead of replication) , and then running a script that you setup yourself to startup all your applications. This technology is older, takes more time to perform a failover, and is less able to fully utilize all of your hardware resources.

OS clustering gives you the following advantages:
If you have a bunch of applications which must run on the same machine, OS clustering can ensure that all these must run on the primary node in the cluster.
If your applications are dependant on "local file system" like databases need to manage their files locally - the os cluster can ensure that this file system fails over with the primary node of the cluster.
If you dont have a NAS or a file server, and you need a shared file store, you can create a share file store on the OS cluster for use by machines outside the cluster. Of course if you have a file server or are storing information in a database, then its not valid.

# rpm -q redhat-config-cluster
# rpm -q clumanager
# 

# clustat
# clustat -m <member>        Display status of <member> and exit
# clustat -s <service>            Display status of <service> and exit
# clustat -l                               Use long format for services

# cman_tool status                 Show local record of cluster status
# cman_tool nodes                  Show local record of cluster nodes
# cman_tool nodes -af

# ccs_tool lsnode                     List nodes
# ccs_tool lsfence                    List fence devices

# group_tool                           displays the status of fence, dlm and gfs groups
# group_tool ls                       displays the list of groups and their membership

# cluster status

oracle@n1$ crs_stat
oracle@n1$ crsctl check crs

CSS appears healthy
CRS appears healthy
EVM appears healthy

grid@n1$ crsctl check cluster -all 

I do not want to delete all the database files (those in v$datafile, v$tempfile, v$logfile, v$controfile)
because i want to delete only one database out of 3 databases on standalone server

1.How to check the diskgroup belongs to particular database ?

2.Is it necessary to dismount the diskgroup before drop it ?

A diskgroup does not belong to a database; it can contains files owned by different databases (not a good practice).

7.Drop the diskgroup belong to the database to be decommissioned.(Please make sure it contains only the data for that particular database)

1.How to determine the diskgroup that belong to a particular database ?

A diskgroup does not belong to a database; it can contains files owned by different databases (not a good practice).

If it contains files of other databases , then how to implement step #7 ?

2.Is it not required to drop diskgroup of database that i want to drop after i drop database

If it contains files of other databases , then how to implement step #7 ?

7.Drop the diskgroup belong to the database to be decommissioned.(Please make sure it contains only the data for that particular database)

1.How to determine the diskgroup that belong to a particular database?

2.Is it not required to drop diskgroup of database that i want to drop after i drop database ?
Regards,
Suhas

Query v$datafile and compare the result with the one given by BlackSwan's command.

It will drop all the database files (those in v$datafile, v$tempfile, v$logfile, v$controfile), it does not drop spfile, init.ora, alert.log, trace files and so on external to the database (even if related to it).

Query v$datafile and compare the result with the one given by BlackSwan's command.

Are you talking about OS cluster or Oracle cluster?

df -h |grep -i ORCL

Michel,
os cluster

Active-active
Setup: Two Adaptive Servers are configured as companion servers, each with independent workloads. These companions run on the primary and secondary nodes, respectively, as individual servers until one fails over.

Failover: When fail over occurs, the secondary companion takes over the devices, client connections, and so on from the primary companion. The secondary companion services the failed-over clients, as well as any new clients, until the primary companion fails back and resumes its activities.

Failback: Failback is a planned event during which the primary companion takes back its devices and client connections from the secondary companion to resume its services.

Client connection failover: During failover, clients connect to the secondary companion to resubmit their uncommitted transactions. During failback, clients connect to the primary companion to resubmit their transactions. Clients with the failover property reestablish their connections automatically.

Active-passive
Setup: A single Adaptive Server runs either on the primary node or on the secondary node. The Adaptive Server runs on the primary node before a fail over and the secondary node after fail over.

Failover: When a system fails over, the Adaptive Server and its associated resources are relocated to, and restarted on, the secondary node.

Failback: Failback is a planned fail over or relocation of the Adaptive Server and its resources to the primary node. Failback is not required, but can be done for administrative purposes.

Client connection failover: During failover and failback, clients connect to the same Adaptive Server to resubmit uncommitted transactions. Clients with the failover property reestablish their connections automatically.

Michel,
Quote:

Are you talking about OS cluster or Oracle cluster?

os cluster

Quote:

df -h |grep -i ORCL

This command will also tell what are all the mount points thats is related to database