In Oracle 11g RAC, it is found that both the Solaris and GSD services are in the offline status, which is the default situation of Oracle 11g RAC. Even so, the use of the database is not affected, because the resource for the WLM is used, WLM is available in 11.2.0.2. GSD is used to support interaction tools such as dbca, srvctl, and OEM. This article describes how to switch these two services to online.
1. Environment [root @ linux2 ~] # Cat/etc/issue Enterprise Linux Server Release 5.5 (Carthage) kernel \ r on an \ m [root @ linux2 bin] #. /crsctl query CRS activeversion Oracle clusterware active version on the cluster is [11.2.0.1.0] 2. The sum of the x-axis and all gsdks is offline [grid @ linux2 ~]. $ Crs_stat-T | grep offline ora. GSD ora. GSD. type offline ora. linux1.gsd application offline ora. linux2.gsd application offline ora. in the left-side navigation pane. for more information, see <G id = "1"> overview </G>. type offline 3. Start the productname service # Use srvctl to start the productname service [grid @ linux2 ~] $ Srvctl start enter the PRCR-1079: failed to start resource ora. CRS-2501: Resource 'ora. * $ Crsctl start res ora. CRS-2613: cocould not find resource 'ora. '. CRS-4000: Command start failed, or completed with errors. # Set the status to enable first [grid @ linux2 ~] $ Srvctl enable Solaris # restart successful [grid @ linux2 ~] $ Srvctl start productname [grid @ linux2 ~] $ Crs_stat-T | grep Solaris ora. in the left-side navigation pane. for more information, see <G id = "1"> overview </G>. type online linux2 4. Start the GSD service # view the status of all resources on the linux1 node. The output shows that the GSD is also disable. [grid @ linux2 ~] $ Srvctl status nodeapps-N linux1-n <node_name> option has been deprecated. VIP linux1-vip is enabled VIP linux1-vip is running on node: linux1 network is Enabled Network is running on node: linux1 GSD is disabled GSD is not running on node: linux1 ONS is enabled ons daemon is running on node: linux1 eons is enabled eons daemon is running on node: linux1 # view all the resource statuses on linux2, you can also see the output information indicating that GSD is also Able [grid @ linux2 ~] $ Srvctl status nodeapps-N linux2-n <node_name> option has been deprecated. VIP linux2-vip is enabled VIP linux2-vip is running on node: linux2 network is Enabled Network is running on node: linux2 GSD is disabled GSD is not running on node: linux2 ONS is enabled ons daemon is running on node: linux2 eons is enabled eons daemon is running on node: linux2 # Place all services in the enable State [grid @ linux2 ~] $ Srvctl enable nodeapps PRKO-2415: VIP is already enabled on node (s): linux1, linux2 PRKO-2416: network resource is already enabled. PRKO-2417: ONS is already enabled on node (s): linux1, linux2 PRKO-2418: eons is already enabled on node (s): linux1, linux2 # Check again that the GSD status has changed to enable [grid @ linux2 ~] $ Srvctl status nodeapps VIP linux1-vip is enabled VIP linux1-vip is running on node: linux1 VIP linux2-vip is enabled VIP linux2-vip is running on node: linux2 network is Enabled Network is running on node: linux1 network is running on node: linux2 GSD is enabled GSD is not running on node: linux1 GSD is not running on node: linux2 ONS is enabled ons daemon is running on node: linux1 ons daemon is Running on node: linux2 eons is enabled eons daemon is running on node: linux1 eons daemon is running on node: linux2 [grid @ linux2 ~] $ Crs_stat-T | grep offline ora. GSD ora. GSD. Type offline ora. linux1.gsd application offline ora. linux2.gsd application offline # Start the GSD service [grid @ linux2 ~] $ Srvctl start nodeapps PRKO-2421: network resource is already started on node (s): linux1, linux2 PRKO-2420: VIP is already started on node (s): linux1, linux2 PRKO-2420: VIP is already started on node (s): linux1, linux2 PRKO-2422: ONS is already started on node (s): linux1, linux2 PRKO-2423: eons is already started on node (s ): linux1 and linux2 # verify the GSD service [grid @ linux2 ~] $ Crs_stat-T | grep offline [grid @ linux2 ~] $ Crs_stat-T | grep GSD ora. GSD ora. GSD. type online linux1 ora. linux1.gsd application online linux1 ora. linux2.gsd application online linux2 # Author: Robinson # blog: http://blog.csdn.net/robinson_0612 5. About GSD the global services daemon (GSD) runs on each node with one GSD process per node. the GSD coordinates with the Cluster Manager to receive requests from clients such The dbca, em, And the srvctl utility to execute administrative job tasks such as instance startup or shutdown. the GSD is not an oracle instance background process and is therefore not started with the Oracle instance. GSD interacts with the RAC management tool dbca srvctl OEM to complete management tasks such as instance startup and shutdown. To ensure that these management tools run normally, you must start GSD on all nodes. A gsd process supports multiple RAC. GSD processes on a node in the $ ORACLE_HOME/bin directory. The log file is $ ORACLE_HOME/srvm/log/gsdaemon. log. For example, if you use an OEM tool to start an instance and the OEM delivers the task to the corresponding Intelligent engine, the Intelligent engine generates a script file containing the srvctl command, the GSD process reads the script file and executes the script. Finally, GSD returns the execution result to the intelligent engine, which returns the result to the OEM. For example, if you use the srvctl tool to close all instances, the GSD process accepts the request from the srvctl tool, executes the request on the local node, and then returns the execution result to the srvctl session.
More references
For more information about Oracle RAC, see
Use crs_setperm to modify the resource owner and permissions of RAC.
Use crs_profile to manage RAC resource configuration files
RAC database startup and Shutdown
Oracle RAC services
Services in Oracle Database 10g
Migrate datbase from single instance to Oracle RAC
Connect Oracle RAC to a specified instance
Oracle RAC load balancing test (combined with server and client)
Oracle RAC server connection Load Balance)
Load Balance)
Non-Default port listening configuration in Oracle RAC (listener. ora tnsnames. ora)
Oracle RAC Listener Configuration (listener. ora tnsnames. ora)
Configure RAC load balancing and Failover
CRS-1006, CRS-0215 fault case
Installing Oracle 10g RAC Based on Linux (RHEL 5.5)
Use runcluvfy to verify the Oracle RAC installation environment
For more information about the basics and concepts of Oracle network configuration, see:
Configure dynamic service registration for non-default ports
Configure sqlnet. ora to restrict IP Access to Oracle
Configure and manage Oracle listener logs
Set the Oracle listener password (listener)
Configure the Oracle client to connect to the database
For more information about user-managed backup and recovery, see
Oracle cold backup
Oracle Hot Backup
Concept of Oracle backup recovery
Oracle instance recovery
Oracle recovery based on user management
System tablespace management and Backup Recovery
Sysaux tablespace management and recovery
Oracle backup control file recovery (unsing backup controlfile)
For information on RMAN backup recovery and management, see
RMAN overview and architecture
RMAN configuration, Monitoring and Management
Detailed description of RMAN backup
RMAN restoration and recovery
Create and use RMAN catalog
Create RMAN storage script based on catalog
Catalog-based RMAN backup and recovery
RMAN backup path confusion
Use RMAN for recovery from different machine backups (WIN platform)
Use RMAN to migrate a file system database to ASM
Linux RMAN backup shell script
Use RMAN to migrate the database to a different machine
For the Oracle architecture, see
Oracle tablespace and data files
Oracle Password File
Oracle parameter file
Oracle online redo log file)
Oracle Control File)
Oracle archiving logs
Oracle rollback and undo)
Oracle database instance startup and Shutdown Process
Automated Management of Oracle 10g SGA
Oracle instances and Oracle databases (Oracle Architecture)