Oracle9i Net Services Reference Guide Release 1 (9.0.1) Part Number A90155-01 |
|
This chapter provides a complete listing of the cman.ora
file configuration parameters.
This chapter contains these topics:
Oracle Connection Manager configuration, stored in the cman.ora
file, consists of the following elements:
By default, the cman.ora
file is located in the $ORACLE_HOME/network/admin
directory on UNIX, and in the ORACLE_HOME
\network\admin
directory on Windows. cman.ora
can also be stored in the directory specified by the TNS_ADMIN
environment variable or in the node's global configuration directory. For Sun Solaris, this directory is /var/opt/oracle
. Windows NT does not have a central directory.
Figure 9-1 shows an example cman.ora
file.
CMAN=
(ADDRESS=(PROTOCOL=tcp)(HOST=proxysvr)(PORT=1630))
(ADDRESS=(PROTOCOL=tcps)(HOST=144.25.22.217)(PORT=2484))
CMAN_ADMIN=(ADDRESS=(PROTOCOL=tcp)(HOST=proxysvr)(PORT=1830))
CMAN_RULES=
(RULE=(SRC=206.62.226.32/27)(DST=dlsun1593)(SRV=*)(ACT=accept)))
CMAN_PROFILE=
(PARAMETER_LIST=(LOG_LEVEL=2)
(TRACING=on))
This section lists and describes the cman.ora
file parameters. Configuration parameters fall into the following categories:
The CMAN
parameter specifies the protocol addresses of the Oracle Connection Manager gateway process, CMGW.
CMAN=(ADDRESS=(PROTOCOL=tcp)(HOST=local_host)(PORT=1630))
CMAN= ([ADDRESS_LIST= ] (ADDRESS= ...) [(ADDRESS= ...)])
The CMAN_ADMIN
parameter specifies the protocol addresses of the Oracle Connection Manager administrative process, CMADMIN.
CMAN_ADMIN=(ADDRESS=(PROTOCOL=tcp)(HOST=anyhost)(PORT=1830))
CMAN_ADMIN= ([ADDRESS_LIST= ] (ADDRESS= ...) [(ADDRESS= ...)])
The access control rule list (CMAN_RULES
) filters incoming connections. It determines which connections are accepted, rejected, or dropped.
CMAN_RULES= (RULE_LIST= (RULE= (SRC=host) (DST=host) (SRV=service_name|sid) (ACT=accept|reject)) [(RULE= ...)])
The RULE
parameter filters a connection or group of connections using the following sub-parameters:
SRC
--Source host name or IP address (in dot notation)
DST
--Destination server host name or IP address (in dot notation)
SRV
--Database service name of the Oracle9i or Oracle8i database (obtained from the SERVICE_NAME
parameter in the initialization parameter file) or Oracle System Identifier (SID) value of the pre-release 8.1 database (obtained from the ORACLE_SID
environment variable or registry value).
ACT
--Accept or reject incoming requests with the previous characteristics.
*
). In the case of an IP address (d.d.d.d
), you can wildcard the individual d
's with this character.
SID
and SERVICE_NAME
parameters, then both names requested need to be permitted by the rules respectively in order for the client's access to be allowed.
CMAN_RULES= (RULE_LIST= (RULE= (SRC=client1-pc) (DST=sales-server) (SRV=sales.acme.com) (ACT=reject)) (RULE= (SRC=144.25.23.45) (DST=144.25.187.200) (SRV=db1) (ACT=accept)))
The parameter list (CMAN_PROFILE
) is used to set attributes for an Oracle Connection Manager. To override a parameter's default setting, enter the parameter and its nondefault value in the PARAMETER_LIST.
ANSWER_TIMEOUT=0
AUTHENTICATION_LEVEL=0
LOG_LEVEL=0
MAX_FREELIST_BUFFERS=0
MAXIMUM_CONNECT_DATA=1024
MAXIMUM_RELAYS=128
RELAY_STATISTICS=NO
REMOTE_ADMIN=NO
SHOW_TNS_INFO=NO
TRACE_DIRECTORY=
The $ORACLE_HOME/network/trace
directory on UNIX, and the ORACLE_HOME
\network\trace
directory on Windows NT
TRACE_FILELEN=
unlimited
TRACE_FILENO=1
TRACE_TIMESTAMP=NO
TRACING=NO
USE_ASYNC_CALL=YES
ANSWER_TIMEOUT=[0 to
n]
AUTHENTICATION_LEVEL=[0 | 1]
LOG_LEVEL=[0-4]
MAXIMUM_CONNECT_DATA=[257 to
4096]
MAX_FREELIST_BUFFERS=[0 to 10240]
MAXIMUM_RELAYS=[1
to 2048]
RELAY_STATISTICS=[YES | TRUE | ON | 1 | NO | FALSE | OFF | 0]
REMOTE_ADMIN=[YES | TRUE | ON | 1 | NO | FALSE | OFF | 0]
SHOW_TNS_INFO=[YES | TRUE | ON | 1 | NO | FALSE | OFF | 0]
TRACE_DIRECTORY=
directory
TRACE_FILELEN=
size of file in kilobytes
TRACE_FILENO=[1
to 8]
TRACE_TIMESTAMP=[YES | TRUE | ON | 1 | NO | FALSE | OFF | 0]
TRACING=[YES | TRUE | ON | 1 | NO | FALSE | OFF | 0]
USE_ASYNC_CALL=[YES | TRUE | ON | 1 | NO | FALSE | OFF | 0]
CMAN_PROFILE= (PARAMETER_LIST= (MAXIMUM_RELAYS=512) (LOG_LEVEL=1) (RELAY_STATISTICS=YES) (REMOTE_ADMIN=YES) (SHOW_TNS_INFO=YES) (USE_ASYNC_CALL=YES) (AUTHENTICATION_LEVEL=0) (TRACING=YES) (TRACE_TIMESTAMP=YES) (TRACE_FILELEN=100) (TRACE_FILENO=2))
The ANSWER_TIMEOUT
parameter determines the number of seconds that Oracle Connection Manager uses to time out the protocol handshake associated with an incoming connection request
The range is 0 to n.
The AUTHENTICATIOIN_LEVEL
parameter determines the level of security:
The LOG_LEVEL
parameter specifies the level of logging performed by Oracle Connection Manager. There are four log levels, ranging from 0 to 4:
RULE_LIST
matching lookup reporting
The default is 0, which means no logging is performed
The CMGW gateway process creates a log file called cman_
pid
.log
, and the CMADMIN administrative process creates a log file called cmadm_
pid
.log
. The log files are located in the $ORACLE_HOME/network/log
directory on UNIX, and the ORACLE_HOME
\network\log
directory on Windows NT.
The MAX_FREELIST_BUFFERS
parameter determines the maximum number of buffers that Transparent Network Substrate (TNS) keeps in its freelist for later reuse instead of returning them to the operating system after a relay gets closed.
The range is 0 to 10240.
The MAXIMUM_CONNECT_DATA
parameter limits the connect data string length of the incoming connection requests.
The range is 257 to 4096.
The MAXIMUM_RELAYS
parameter specifies the maximum number of concurrent connections supported.
The range is 1 to 2048.
The RELAY_STATISTICS
parameter determines if I/O statistics are recorded.
yes
--Instructs Oracle Connection Manager to maintain statistics pertaining to relay I/O activities, such as:
This information is stored in the cman_
pid
.log
file.
no
--Records no I/O statistics
The REMOTE_ADMIN
parameter determines if remote access to an Oracle Connection Manager is allowed.
yes
--Allows access from a remote Oracle Connection Manager Control utility session to Oracle Connection Manager
no
--Allows only access to the local Oracle Connection Manager. This value prevents a user running a remote Oracle Connection Manager Control utility session access to Oracle Connection Manager.
The SHOW_TNS_INFO
parameter determines if TNS information is to be recorded.
yes
-- Instructs Oracle Connection Manager to include TNS information in the cman_
pid
.log
file
no
--Instructs Oracle Connection Manager to not include TNS events in the log file
The TRACING
parameter determines whether or not tracing is enabled for the Oracle Connection Manager.
yes
-- Enables tracing for the Oracle Connection Manager. The CMGW gateway process creates a trace file called cman_
pid
.trc
, and the CMADMIN administrative process creates a trace file called cmadm_
pid
.trc
.
no
--Disables tracing
The TRACE_DIRECTORY
parameter specifies the destination directory for the trace files. You must set this parameter to a nondefault location if you plan to use the TRACE_FILELEN
or
TRACE_TIMESTAMP
parameters.
The TRACE_FILEN
parameter specifies the size of the trace file in kilobytes (KB). When the size is met, the trace information is written to the next file. The number of files is specified with the TRACE_FILENO
parameter.
The TRACE_FILENO
parameter specifies 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 first, 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, the CMGW gateway trace files would be named cman1_
pid
.trc
, cman2_
pid
.trc
and cman3_
pid
.trc
and the CMADMIN administrative trace files would be named cmadm1_
pid
.trc
, cmadm2_
pid
.trc
and cmadm3_
pid
.trc
.
In addition, trace events in the trace files are preceded by the sequence number of the file.
The TRACE_TIMESTAMP
parameter adds a time stamp in the form of dd-month-yyyy hh:mm:ss
to every trace event in the trace file.
Determines whether or not Oracle Connection Manager uses asynchronous functions while in the answering or calling phase of establishing an Oracle Net connection
yes
--Instructs Oracle Connection to use all asynchronous functions
no
--Instructs Oracle Connection Manager not to use asynchronous functions
|
Copyright © 1996-2001, Oracle Corporation. All Rights Reserved. |
|