Example of Oracle start parameters

Oracle only requires an open string, no close string.

Multi-instance mode is possible, i.e. several open strings can be specified for the Resource Manager in the start parameter file of a UTM application.

The following start parameters, for example, can be specified in the start parameter file for an Oracle database:

.RMXA Oracle_XA OS="Oracle_XA+Acc=P//+SesTm=60"

This statement must be written in one line without a line feed.

How you obtain DEBUG information for the connection to the database is described in section "Debug parameters".

Only the mandatory parameters are listed in the open string. In addition, you can specify other optional parameters. These are listed further below.
The parameters in the open string are separated by the “+” character.

Meaning of the mandatory parameters:

Oracle_XA	Name of the Resource Manager prescribed by Oracle, as contained in the xa_switch structure.
Acc=P//	Information for data access control to the database (user access information). If Acc=P// is specified as in the example, neither a user ID nor a password are transferred for data access control.
	An Oracle database can also request database-specific information (user and pwd) which must be transferred with Acc=P/user/pwd. For further information, see the Oracle manual.
SesTm=	Maximum time in seconds available for a transaction (60 s in the example). Possible specifications for SesTm can be found in the Oracle manual.
	Specifying SesTM=0 means that there is no restriction on the duration of the transaction. It is therefore recommended to specify a value > 0 for SesTm.

The parameters listed below are optional. Please refer to the Oracle manual for an explanation and description of possible definitions.

DB=	Name of the Oracle database.
	You must specify this parameter if the UTM application is to be linked with more than one Oracle database (multi-instance mode).
GPwd=P/	Group password; specified in the form GPwd=P/password.
LogDir=	Path name of the logging directory.
MaxCur=	Maximum number of open cursors.
SqlNet=	Network connection string.

No action is required if the application is terminated abnormally, because openUTM automatically carries out a common recovery phase before the UTM application is restarted.

Please note that, on Windows systems, the RMXA statement needs the DLLIMPORT=YES operand when generating with KDCDEF.

Information on the objects/libraries to be linked and on the start parameters (openstring) can be found in the Oracle documentation.

Using the Oracle user name and Oracle password from the UTM generation

The access authorization for an Oracle database should be defined via KDCDEF generation for security reasons.

Please note the following:

• The Oracle user name for the connection to Oracle and the associated Oracle password must be generated in KDCDEF (KDCDEF statement RMXA, USERID and PASSWORD operands).

  The Oracle password is stored as a hashcode in the UTM system tables (masked) and is therefore not present in clear text in the UTM dump.

• In the openstring for the start parameter, specify the placeholder *UTMUSER in place of the Oracle user name and the placeholder *UTMPASS instead of the Oracle password. These placeholders are replaced in accordance with the following rules:

  • If the openstring contains at least one of the placeholders *UTMUSER or *UTMPASS, then UTM replaces the placeholders with the values generated for the specific database system on an xa_open() call. I.e. in the open string, *UTMUSER is replaced by the generated Oracle user name and *UTMPASS by the generated Oracle password.
    For security reasons, the Oracle password is converted into clear text only immediately prior to use on an xa_open() call and is then deleted in the process memory immediately after the xa_open() call.

  • If the openstring of the start parameter does not contain either *UTMUSER or *UTMPASS then it is passed unchanged to the xa_open() call.

   Please note that processing is case-sensitive!

Example

You want to use the Oracle user name and the Oracle password from the UTM generation:

OS="Oracle_XA+SqlNet=O11+ACC=P/*UTMUSER/*UTMPASS+DbgFl=15"

Behavior if the Oracle access data is not generated

• If the USERID and PASSWORD operands were not specified during UTM generation, and if the Oracle database requires a user name and/or a password, the setup of the connection to the database is refused.

• If you specify *UTMUSER or *UTMPASS in the start parameter even though the USERID and PASSWORD operands were not specified during UTM generation then UTM uses an empty Oracle user name or empty Oracle password. As a result, the attempt to establish the connection to the database will generally be unsuccessful.