Skip Headers
Oracle® Transparent Gateway for Informix Administrator's Guide
10g Release 2 (10.2) for HP-UX

Part Number B14274-01
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

D Heterogeneous Services Initialization Parameters

The Oracle database server initialization parameters in the init.ora file are distinct from heterogeneous services (HS) initialization parameters. Set HS parameters in the initialization parameter file using an agent-specific mechanism, or set them in the Oracle data dictionary using the DBMS_HS package.

This appendix contains information about the following Heterogeneous Services initialization parameters:

The HS initialization parameter file must be available when the gateway is started. During installation, the following default HS initialization parameter file is created:

$ORACLE_HOME/tg4ifmx/admin/inittg4ifmx.ora

where $ORACLE_HOME is the directory under which the gateway is installed.

D.1 HS Initialization Parameter File Syntax

The syntax for the initialization parameter file is as follows:

  1. The file is a sequence of commands.

  2. Each command should start on a separate line.

  3. End of line is considered a command terminator (unless escaped with a backslash).

  4. Each command can have one of the following forms:

    1. <param> = <value>

    2. set <param> = <value>

    3. private <param> = <value>

    4. set private <param> = <value>

    Where:

    <param> is an initialization parameter name.

    <value> is the initialization parameter value.

    'set' and 'private' are keywords.

  5. The keywords 'set' and 'private' are reserved. You cannot use either as an initialization parameter name. The 'set' keyword indicates that the initialization parameter should be set as an environment variable in the agent. The 'private' keyword indicates that the initialization parameter should be private to the agent and should not be uploaded to the server. Most initialization parameters should not be private. If, however, you are storing something sensitive like a password in the initialization parameter file, then you may not want it uploaded to the server because the initialization parameters and values are not encrypted when uploaded. Making these initialization parameters private prevents the upload from happening.

  6. An initialization parameter name is a string of characters starting with a letter and consisting of letters, digits and underscores. Initialization parameter names are case sensitive.

  7. An initialization parameter value is either:

    1. A string of characters that does not contain any backslashes, white space or double quotation marks (")

    2. A quoted string beginning with a double quotation mark and ending with a double quotation mark. The following can be used inside a quoted string:

      • backslash (\) is the escape character

      • \n inserts a new line

      • \t inserts a tab

      • \" inserts a double quotation mark

      • \\ inserts a backslash

      A backslash at the end of the line continues the string on the next line. If a backslash precedes any other character then the backslash is ignored.

If there is a syntax error in an initialization parameter file, none of the settings take effect.

D.2 HS_FDS_CONNECT_INFO

Default Value Range of Values
None Not Applicable

Specifies the information needed to connect to the Informix database.

This is a required parameter, whose format is:

HS_FDS_CONNECT_INFO=database_name@server_name

Where:

database_name is the name of the database and server_name is the name of the server machine for the Informix data.

The entries for both the database_name and server_name are case-sensitive.

If you specify only database_name, omitting server_name, the gateway binds to the database residing on the local Informix server (as specified in the environment variable INFORMIXSERVER).

D.3 HS_FDS_PARSER_TOKEN_SIZE

Default Value Range of Values
1,000 Characters Any positive integer value

Used for setting the parser token size in case the default size is not sufficient. The default value can be changed in cases when the following error occurs:

pclex input buffer overflowed, try to increase the variable tokenSize in your evironment.

With default value of 1000, the gateway could handle SQL statements close to 2M. Note that the SQL statements sent to the gateway could be very different from the SQL statements issued by the users. If in doubt, turn on gateway trace. Increase this parameter to handle larger SQL statements sent to gateways

D.4 HS_FDS_RECOVERY_ACCOUNT

Default Value Range of Values
RECOVER Any valid userid

Specifies the name of the recovery account used for the commit-confirm transaction model. An account with user name and password must be set up at Informix. For more information about the commit-confirm model, see the HS_FDS_TRANSACTION_MODEL parameter.

The name of the recovery account is case-sensitive.

D.5 HS_FDS_RECOVERY_PWD

Default Value Range of Values
RECOVER Any valid password

Specifies the password of the recovery account used for the commit-confirm transaction model set up at Informix. For more information about the commit-confirm model, see the HS_FDS_TRANSACTION_MODEL parameter.

The name of the password of the recovery account is case-sensitive.

D.6 HS_FDS_TRACE_LEVEL

Default Value Range of Values
OFF OFF, ON

Specifies whether error tracing is turned on or off for gateway connectivity.

The following values are valid:

D.7 HS_FDS_TRANSACTION_LOG

Default Value Range of Values
HS_TRANSACTION_LOG Any valid table name

Specifies the name of the table created in the Informix database for logging transactions. For more information about the transaction model, see the HS_FDS_TRANSACTION_MODEL parameter.

D.8 HS_FDS_TRANSACTION_MODEL

Default Value Range of Values
COMMIT_CONFIRM COMMIT_CONFIRM, READ_ONLY, or SINGLE_SITE

Specifies the type of transaction model that is used when the Informix database is updated by a transaction.

The following values are possible: