Hierarchy

⤷

⤷

Basic Data
Data Element | DBCON_OPT_CONNECTIONS |
Short Description | Optimum Number of Connections |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | INT1 | |
Data Type | INT1 | 1-byte integer, integer number <= 255 |
Length | 3 | |
Decimal Places | 0 | |
Output Length | 3 | |
Value Table |
Further Characteristics
Search Help: Name | ||
Search Help: Parameters | ||
Parameter ID | ||
Default Component name | ||
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 10 | Opt. Conns |
Medium | 18 | Optimum Conns |
Long | 20 | Optimum Connections |
Heading | 35 | Optimum Number of Connections |
Documentation
Definition
Defines the optimal number of database connections. If this number is exceeded in an SAP R/3 transaction, the work process automatically ensures after completion of the transaction that the connections that exceed this number are closed again. This corresponds to an automatic DISCONNECT.
The initial value 0 has the special meaning, if DBCON_MAX_CONNECTIONS
is also set to 0: the optimum is set to the maximum value of the value range for the variables (255).
Use
A database connection cannot be shared by several SAP R/3 work processes. Each work process requires its own (private) database connections. If there are a large number of database connections and a large number of work processes, this can lead to resource problems on the database server. This parameter is suitable for being able to create a soft limit for this resource usage during production operation; a limit that can be temporarily exceeded.
Dependencies
Example
DBCON_MAX_CONNECTIONS
= 0, DBCON_OPT_CONNECTIONS
= 0: Maximum/Optimum: 255 DB connections
DBCON_MAX_CONNECTIONS
= 1, DBCON_OPT_CONNECTIONS
= 0: Maximum of 1 database conenction, optimally no database connections
DBCON_MAX_CONNECTIONS
= 5, DBCON_OPT_CONNECTIONS
= 2: Maximum of 5 database connections, optimally 2 database connections
History
Last changed by/on | SAP | 20130604 |
SAP Release Created in | 640 |