Xref: alice comp.databases.oracle.server:41655 Path: alice!news-feed.fnsi.net!newsfeed.ecrc.net!newsfeed.nacamar.de!newsfeed.nacamar.de!nntp.news.xara.net!xara.net!baron.netcom.net.uk!netcom.net.uk!usenet.co.uk!newspeer.usenet.co.uk!post.usenet.co.uk!not-for-mail From: Alex Hudghton Newsgroups: comp.databases.oracle.server Subject: Re: What is ogms daemon? Date: Fri, 26 Feb 1999 14:08:13 +0000 Organization: Cap Gemini UK Plc Lines: 179 Message-ID: <36D6AACD.ABA0968F@capgemini.co.uk> References: <7b2qru$8fl@tbjnws.tbj.dec.com> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="------------C33E2CF8B603DC7874296318" X-Trace: hagen.cloud9.co.uk 920038094 2108 194.42.240.2 (26 Feb 1999 14:08:14 GMT) X-Complaints-To: abuse@usenet.co.uk NNTP-Posting-Date: 26 Feb 1999 14:08:14 GMT X-Mailer: Mozilla 4.5 [en] (Win95; I) X-Accept-Language: en --------------C33E2CF8B603DC7874296318 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit From Oracle 8 Parallel server Concepts Manual Alex > Using Group Membership Services > > Group Membership Services (GMS) is used by the Lock Manager (LM) and other Oracle components for inter-instance > initialization and coordination. Instances of a distributed service can register with the GMS and retrieve the current set of > instances providing the same service cluster-wide. The GMS monitors each of its clients and notifies the other instances of a > given service when one instance stops or is shut down. It obtains a view of the current cluster membership from the (system > specific) cluster management software. > > If a GMS instance or a node stops, the remaining GMS instances are informed through the cluster manager. Providers of > distributed services are then be notified by the GMS if any of their peers stopped as a result of the node stoppage. > > Platforms which use the opsctl program start GMS automatically. For other platforms, you must start this process by manually > issuing the ogmsctl command. This program has the following options: > > start > > > start up the GMS instance on the current node > > > stop > > > stop the GMS instance on the current node > > > abort > > > kill the GMS instance on the current node > > > status > > > check the status of the GMS on the current node > > > ogms_home=X > > > set the GMS home directory to X, where debugging trace files and the communication key file will be > written during its operation. The directory must be either local to its own node or different from other GMS > directories in the network environment. Multiple GMS instances could be running at the same time in a > cluster. When this option is specified, the corresponding OGMS_HOME initialization parameter needs to > be specified as well to pick up the GMS listen port id information. > > > trace=n > > > set the GMS trace level to a number n between 0 and 10 (with 10 being the highest trace level). You can > use this option with the start option or specify it separately after the GMS has been started. > > > > > > When you have installed the Oracle Parallel Server option, you must start the GMS, even to bring the instance up with parallel > server disabled. If OPS is linked in, Oracle starts the Integrated Distributed Lock Manager and connects to the GMS to obtain > a mount lock. This prevents you from accidentally mounting the database exclusive on more than one mode. > > See Also: Your Oracle system-specific documentation to determine whether GMS is started automatically, and whether it > requires additional cluster configuration. > Yuichi Matsuki wrote: > Hi ! > > I installed "Oracle8.0.4 Server" the other day. > When it started, the error message which it said as "It can't be > connected to ogms." was received. > So, a data base could be started after it started ogms daemon. > > Please teach anything about ogms. > > Thanks! > > Yuichi Matsuki --------------C33E2CF8B603DC7874296318 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit From Oracle 8 Parallel server Concepts Manual

Alex
  

Using Group Membership Services

Group Membership Services (GMS) is used by the Lock Manager (LM) and other Oracle components for inter-instance
initialization and coordination. Instances of a distributed service can register with the GMS and retrieve the current set of
instances providing the same service cluster-wide. The GMS monitors each of its clients and notifies the other instances of a
given service when one instance stops or is shut down. It obtains a view of the current cluster membership from the (system
specific) cluster management software. 

If a GMS instance or a node stops, the remaining GMS instances are informed through the cluster manager. Providers of
distributed services are then be notified by the GMS if any of their peers stopped as a result of the node stoppage. 

Platforms which use the opsctl program start GMS automatically. For other platforms, you must start this process by manually
issuing the ogmsctl command. This program has the following options: 

 start 

  
               start up the GMS instance on the current node 

                
 stop 

  
               stop the GMS instance on the current node 

                
 abort 

  
               kill the GMS instance on the current node 

                
 status 

  
               check the status of the GMS on the current node 

                
 ogms_home=X 

  
               set the GMS home directory to X, where debugging trace files and the communication key file will be
               written during its operation. The directory must be either local to its own node or different from other GMS
               directories in the network environment. Multiple GMS instances could be running at the same time in a
               cluster. When this option is specified, the corresponding OGMS_HOME initialization parameter needs to
               be specified as well to pick up the GMS listen port id information. 

                
 trace=n 

  
               set the GMS trace level to a number n between 0 and 10 (with 10 being the highest trace level). You can
               use this option with the start option or specify it separately after the GMS has been started. 

                



When you have installed the Oracle Parallel Server option, you must start the GMS, even to bring the instance up with parallel
server disabled. If OPS is linked in, Oracle starts the Integrated Distributed Lock Manager and connects to the GMS to obtain
a mount lock. This prevents you from accidentally mounting the database exclusive on more than one mode. 

See Also: Your Oracle system-specific documentation to determine whether GMS is started automatically, and whether it
requires additional cluster configuration.

Yuichi Matsuki wrote:

Hi !

I installed "Oracle8.0.4 Server" the other day.
When it started, the error message which it said as "It can't be
connected to ogms." was received.
So, a data base could be started after it started ogms daemon.

Please teach anything about ogms.

Thanks!

Yuichi Matsuki

--------------C33E2CF8B603DC7874296318--