Lesson 4	cman.ora file
Objective	Describe the Structure and Function of the cman.ora File

Structure and Function of cman.ora File

The CMAN utility is controlled by the cman.ora file. The cman.ora file contains all of the configuration directives that are used when CMAN is started.
The cman.ora file consists of three sections:

CMAN (which defines the listening address for the Connection Manager)
CMAN_PROFILE (which defines general configuration parameters)
CMAN_RULES (which defines rules for filtering incoming connection requests)

The cman.ora file is very similar in function to the listener.ora file. Earlier in this course, you learned to configure the listener.ora to listen on separate addresses. The cman.ora file can also be configured to listen on separate addresses.
The example below illustrates how the Connection Manager configuration file would look if you configured it to listen on two addresses, SPX and TCP/IP. Note that a Connection Manager can listen on any protocol that Oracle supports.

CMAN=  
    (ADDRESS_LIST=  
       (ADDRESS=  
            (PROTOCOL=SPX)  
            (SERVICE=CMAN)  
       )  
       (ADDRESS=  
           (PROTOCOL=TCP)  
           (HOST=CMAN.DILBERT)  
           (PORT=1600)  
       )  
    )

cman.ora Trace Parameters

Table 6-4 describes the trace parameters settings for Oracle Connection Manager that can be set in the cman.ora file.
Table 6-4 cman.ora Trace Parameters

cman.ora Parameter	Description
TRACE_DIRECTORY	The destination directory for trace files. By default, the directory is ORACLE_HOME/network/trace.
TRACE_FILELEN;	The size of the trace file in KB. When the size is reached, the trace information is written to the next file. The number of files is specified with the TRACE_FILENO parameter.
TRACE_FILENO	The number of trace files for tracing. When this parameter is set along with the TRACE_FILELEN parameter, trace files are used in a cyclical fashion. The first file is filled, then the second file, and so on. When the last file has been filled, the first file is reused, and so on. The trace file names are distinguished from one another by their sequence number. For example, if this parameter is set to 3, then the Oracle Connection Manager trace files for the gateway processes would be named instance-name_cmgw1_pid.trc, instance-name_cmgw2_pid.trc and instancename_cmgw3_pid.trc. In addition, trace events in the trace files are preceded by the sequence number of the file.
TRACE_LEVEL	The level of detail the trace facility records for the listener. The trace level value can either be a value within the range of 0 (zero) to 16 where 0 is no tracing and 16 represents the maximum amount of tracing or one of the following values: off (equivalent to 0) provides no tracing. user (equivalent to 4) traces to identify user-induced error conditions. admin (equivalent to 6) traces to identify installation-specific problems. support (equivalent to 16) provides trace information for troubleshooting by Oracle Support Services. The Oracle Connection Manager listener, gateway, and CMADMIN processes create trace files on both Linux and Microsoft Windows.
TRACE_TIMESTAMP	If the TRACING parameter is enabled, then a time stamp in the form of dd-mon-yyyy hh:mi:ss:mil is created for every trace event in the listener trace file.

The next lesson shows you how to use CMAN’s connection concentration feature.