Parameters for Setting Up the Database Connection 
Each SAP System in the transport environment needs parameters that enable
tp to log on to the databases belonging to the SAP Systems. These parameters depend on the particular database system and should therefore be defined specifically for each SAP System.tp
identifies the database system type on the basis of the parameter dbtype , whose default value corresponds to the acronym of the database. The value of this parameter can be one of the acronyms allowed for specifying database-specific parameters.The following applies for all databases:
CONNECT_MODE
Default: Not set
Possible values:
use_envYou can use this parameter to stop
tp from setting environment variables. tp requires some environment variables to set up the connection to the database.If you have not set
CONNECT_MODE , the parameters set in the transport profile are evaluated to set these environment variables correctly.If you set
CONNECT_MODE = use_env , the environment variables are not changed. In this case, you need to set the appropriate parameters correctly at the operating system level.dblibpath
UNIX
Default: /usr/sap/$(system)/SYS/exe/run/
Possible values: Paths
This parameter lets you inform the transport control program of the value of the directory in which the dynamic SAP database interface is located. In the standard system, these files are always in the Executable directory of the application server. This means that you do not have to change the default value. The transport control program tp derives the value of the environment variables dir_library from the value of this parameter.
Windows NT
Under Windows NT, the parameter dblibpath is not evaluated.
The dynamic SAP database interface is searched in the following sequence:
DB2 for OS/390
The following parameters are required for DB2 for OS/390 databases:

Note that how you use these parameters depends on your operating system (AIX, Windows NT or OS/390 Unix).
Operating system: AIX, Windows NT
Value range: Text
Here you can enter the host name where the database runs.
Operating system: AIX, Windows NT
Value range: Text
Default:
/usr/sap/<SAPSID>/SYS/exe/run/icliptThis parameter specifies the absolute path to the Signon file. This file is required to perform PassTicket Signon.
You can find more information in the IBM document Planning and Repairing R/3: DB2 for OS/390.
Operating system: AIX, Windows NT
Value range: Text
Default: Not set
This parameter enables you to switch off the PassTicket Signon function. If the parameter is not set, the ICLI client assumes that the ICLI server demands PassTicket Signon and behaves accordingly. If the parameter is set to 1, PassTicket Signon is switched off.
You can find more information in the IBM document Planning and Repairing R/3: DB2 for OS/390.
Operating system: AIX, Windows NT, OS/390 Unix
Value range: Text
Default: SAP system name (<SAPSID>)
This parameter specifies the DB2 group attachment name if this name differs from the SAP System name (<SAPSID>).
You can find more information on this topic in R/3 Installation Guide for UNIX/Windows NT - DB2 for OS/390.
Operating system: AIX, Windows NT
Value range: Text
Default: Port number that is specified under the service name
sapdb2<SAPSID> in the file /etc/services .This parameter specifies the ICLI connection port.
You can find more information in the IBM document Planning and Repairing R/3: DB2 for OS/390.
Operating system: AIX, Windows NT
Value range: Text
Default:
sapdb2<SAPSID>This parameter specifies the service name that defines the ICLI connection port in the file
/etc/services . The transport profile parameter r3_port overwrites this parameter.Operating system: AIX, Windows NT
Value range: Text
Default:
/usr/sap/<SAPSID>/SYS/exe/run/ibmiclic.oThis parameter specifies the absolute path to the shared library of the ICLI client.
You can find more information on this topic in R/3 Installation Guide for UNIX/Windows NT - DB2 for OS/390.
Operating system: OS/390 Unix
Value range: Text
Default: Not set
This parameter specifies the DB2/390 plan name of the dynamic SAP database interface.
Operating system: OS/390 Unix
Value range: Text
Default: Not set
This parameter must be set. It specifies the absolute path to the library of the DB2 Performance Monitor.
DB2 Universal Database
The two parameters
dbname and dbhost are required for DB2 Universal Databases:Value range: Text
Here, you can enter the host name where the database processes run.
In Windows NT, it is the TCP/IP name of the host.
Value range: Text
Here, you can enter the name of the database instance.
You must also install the DB2 Universal Database Client Application Enabler software on the host where
tp runs.DB2/400
Only
dbhost is required for AS/400 databases:Value range: Text
Here, you can enter the system name of the host where the database runs.
If you use TCP/IP instead of
opticonnect , you must also specify the following:opticonnect = 0
INFORMIX
The two parameters
dbname and dbhost are also needed for INFORMIX databases with a standard installation:Value range: Text
Here you can enter the host name where the database runs.
Value range: Text
Here, you can enter the name of the database instance. The name is case-sensitive.
Generally, it is sufficient to specify the parameters
dbname and dbhost . Default values are defined for the following Informix-specific parameters. In this case, you do not have to specify them in the transport profile.Default:
/informix/<sapsid> .Value range: Text
Here, you can enter the directory name where the database software is located.
Default (UNIX):
$(informixdir)/etc/sqlhosts[.tli|.soc]Value range: Text
This parameter is used to specify the name of the SQL hosts file with a complete path.
Default:
$(dbhost)$(dbname)shmValue range: Text
Here, you can enter the database server name for a local connection.
Default:
$(dbhost)$(dbname)tcpValue range: Text
Here, you can enter the database server name for a remote connection.
Microsoft SQL Server
The two parameters
dbname and dbhost are also needed for SQL Server databases:Value range: Text
Here, you can enter the TCP/IP host name where the database runs.
Value range: Text
Here, you can enter the name of the database instance.
Microsoft SQL Server has 2 ways of connecting:
SQL Server user and password are defined (
No user or password is necessary. The NT security descriptor is used and the NT user connects itself.
As of Release 4.5A, Windows NT authentication is used by default. For
<SID>adm and SapService<SID> , the corresponding logins are created during the upgrade and the installation (see Note 116735). The parameters mssql_user and mssql_passwd are no longer evaluated in normal circumstances.However, by setting the environment variable
MSSQL_USEINTEGRATEDSECURITY to zero, you can cause the process to log on via SQL Server authentication. If a tp user is running under a non- <SID>adm , the user can work with a SQL Server database by setting MSSQL_USEINTEGRATEDSECURITY=0 via a user name and password. You can also define a Windows NT login for this user with the SQL Server Enterprise Manager. We recommend using this option.Value range: Text
Here, you can enter the connection to the database for a specific user.
Value range: Text
The parameter
mssql_user lets you enter the password for a specific user here.ORACLE
Only the parameter
dbname is required for Oracle databases, if your installation does not differ to the SAP standard. Other parameters relevant to the configuration of the database connection are dbconfpath and dblogicalname . Due to the Oracle software used, ORACLE-NET-V2 is used to connect to the database.The NLS (National Language Support) and TNS (Transparent Network Substrat) files are installed in the directory ORACLE_HOME. Oracle only supports the installation with this configuration. (Oracle uses TNS to implement the SQL*NET V2 database connection.)
SAP’s own database interface is in a dynamic library that is linked to the user only at runtime.
Value range: Text
Here, you can enter the host name where the database processes run. In Windows NT, it is the TCP/IP name of the host.
This parameter is no longer required for Release 4.x SAP Systems.
Default:
dbnameValue range: Text
Here, you can enter the logical name that identified the instance in the Oracle network during configuration.
Default:
$transdirValue range: Text
Possible values: Paths
You can use this parameter to inform
tp as to where the configuration files for ORACLE SQL*NET V2 are located. The default value $transdir mirrors the fact that SAP has already stored these files centrally in the transport directory. From this parameter, tp derives the value of the environment variables TNS_ADMIN . However, if the parameter DBSWPATH is set, dbconfpath is ignored.
This parameter is not evaluated under Windows NT.
Value range: Text
Here, you can enter the name of the database instance.

In a standard SAP System installation, it is enough to specify the parameter
Default:
american_america.us7asciiValue range: Text
Here, you can enter the code page of the database instance.
The Oracle databases are installed with the code page
we8dec . In this case, you must enter the value american_america.we8dec in the transport profile.When upgrading a Release from 3.x or a later Release to a 4.x, the code page
us7ascii is retained.Value range: Text
Possible values: Paths
This parameter lets you inform the transport control program of the value of the directory in which the Oracle client software is installed. If the parameter is set,
tp derives the following environment variables:ORACLE_HOME = $(dbswpath)
TNS_ADMIN = $(dbswpath)/network/admin (on UNIX)
ORA_NLS = $(dbswpath)/ocommon/nls/admin/data (on UNIX)
ORA_NLS32 = $(dbswpath)/ocommon/nls32/admin/data (on UNIX)
ORA_NLS33 = $(dbswpath)/ocommon/nls33/admin/data (on UNIX)

This parameter is not evaluated under Windows NT.
SAP DB
The parameters
dbname , dbhost , and dbuserkey are needed for SAP DB databases with a standard installation:Value range: Text
Here you can enter the host name where the database runs. In Windows NT, it is the TCP/IP name of the host.
Value range: Text
Here, you can enter the name of the database instance.
Here, you can enter the name of the SAP instance.
The relevant connection information is read from the
xuser file after the userkey entry. The xuser file format is stored in file $HOME/.XUSER62 for UNIX and in the Registry for Windows NT.The database connection is established using the following strategies:
The connection occurs using the corresponding
The database logon uses the default entry (
The database logon uses the default entry in the
For the test import in a system group, you must define additional
userkeys for all xuser information in the group.
USERKEY: |
<Instance name of the SAP System> |
USERID: |
sapr3 |
PASSWORD: |
<Database password of sapr3> |
repeat passw: |
<Database password of sapr3> |
SERVERDB: |
<Name of the database instance> |
SERVERNODE: |
<Name of the host on which the database is running> |
SQLMODE: |
SAPR3 |
CACHELIMIT: |
1 |
TIMEOUT: |
0 |
ISOLATION: |
0 |