Re: Setting up MTS on Ora 7.3.4

From: Yass Khogaly <ykhogaly_at_us.oracle.com>
Date: Wed, 1 Dec 1999 08:10:51 -0800
Message-ID: <823dnu$r60$1@inet16.us.oracle.com>

MTS is configured on a 'per-instance' basis and is set in the init<SID>.ora file.

The main parameters are explained below:

              MTS_SERVICE
                  Defines the SERVICE name that the dispatchers will
register  with the listener. As pre-configured services use the
                  ORACLE_SID for the service name there are 2 options for

setting the MTS_SERVICE.

If you choose the SAME name as the ORACLE_SID then connections requesting a particular SID will get an MTS connection if available (Unless the client calls asking for (SERVER=DEDICATED). If MTS is not available they will get a dedicated connection.
If you choose an MTS_SERVICE different to the ORACLE_SID clients can explicitly request and MTS or a non MTS connection using separate aliases. If MTS is requested and is not available they will NOT get defaulted to a DEDICATED connection.

              MTS_LISTENER_ADDRESS or LOCAL_LISTENER
                  This should be an address on which the listener is KNOWN
to be listening as it tells the dispatchers where to
                  register.


              MTS_DISPATCHERS
                  Several lines can list the protocol and number of
dispatchers for that protocol.
                  NOTE: Some protocols do NOT support MTS. A dispatcher MUST
be able to handle existing connections AND be notified
                  of any new connect requests. If a protocol or its

operating system interface cannot support this mode of operation the protocol

                  cannot be used for MTS connections.

              MTS_MAX_DISPATCHERS
                  Maximum number of dispatchers to allow.

              MTS_MAX_SERVERS
                  Maximum number of shared servers to allow.

              MTS_SERVERS
                  Initial number of shared servers.


          Note that as shared servers and dispatchers may be started at
database startup OR at a later point in time any interim changes to
          the SQL*Net configuration files may be picked up by newly started
processes. This can lead to some confusion - it is advisable to
          restart all processes if there have been any major configuration
          changes.

Example additions to 'init<SID>.ora'

     # ---------------------------------------------------------------------


          # Example init.ora extension to start MTS dispatchers


          #
          mts_service=         "MV713"    <-- Choose a SERVICE name for MTS



          # This is the ADDRESS of a LISTENERs Listen End Point so we can


          # register our service


          mts_listener_address="(ADDRESS=(PROTOCOL=ipc)(KEY=mysid))"

          mts_dispatchers= "ipc, 1"               <-- Start 1 IPC dispatcher
          mts_dispatchers= "tcp, 1"               <-- And 1 TCP dispatcher

          mts_max_dispatchers=10                  <-- No more than 10
          mts_max_servers=10                      <-- and no more than 10
servers
          mts_servers=4                           <-- Start 4 servers at

startup

Checking an MTS connection

Configure ALL SQL*Net files and start the listener. You are advised to use the environment variable TNS_ADMIN to point to the directory where the SQL*Net configuration files reside.
Add the MTS configuration required to the init<SID>.ora file.
Start up the database.
Do a process listing to check what 'ora_..._SID' processes exist for your ORACLE_SID. There should be 'ora_sNNN_SID' and 'ora_dNNN_SID' for the shared servers and dispatchers that you have configured. If not check the 'BACKGROUND_DUMP_DEST' directory (as specified in your initSID.ora file) for RDBMS trace files or entries in the alert log. (Default location for these files is $ORACLE_HOME/rdbms/log)
Use the command:

                  lsnrctl services

             This should list the dispatchers that have registered with the
listener. If no dispatchers have registered check for RDBMS trace
             files as in step (d).

          f) Check the output of 'lsnrctl services' to ensure that all
dispatchers (or prespawned servers) show valid listen end points.
             Ie: (ADDRESS=...) shows a valid address. If not they may not be
contactable.
             Eg: For TCP/IP if (HOST=0.0.0.0) then it is likely that your
system does not have 'hostname' set OR the hostname that IS set is not
                 defined in your /etc/hosts file.


          g) Use 'sqlplus system/manager_at_mtsalias' where mtsalias is an

alias in the tnsnames.ora file that will try to connect to an MTS service for your database.

h) Once connected check that you have an MTS connection thus:

                  select username, program, server from v$session where

audsid=userenv('sessionid');

This should return a row for your session that shows server as SHARED. If it shows 'DEDICATED' you have a DEDICATED connection.

"The Views expressed here are my own and not necessarily those of Oracle Corporation"

Tony Adolph <tony.adolph_at_viaginterkom.de> wrote in message news:822ur6$423$1_at_nnrp1.deja.com...

> Hello All,
>
> Has anyone any hints, tips and/or short cuts for configuring, setting
> up and tuning Multi Threaded Server on Oracle 7.3.4?
>
> The database is running on an NT 4 server with 2 processors, there are
> about 40-50 concurrent connections at any one time.
>
> Any pointers appreciated,
>
> Cheers
> Tony
>
>
> Sent via Deja.com http://www.deja.com/

> Before you buy.

Received on Wed Dec 01 1999 - 10:10:51 CST