autocommit
|
Gives the client application transactional control in
passthrough mode. If
autocommit = 0 in the
configuration file, the client application has transactional
control in passthrough mode. If
autocommit = 1 then
DirectConnect for Oracle autocommits each SQL statement from the
client application.
For example: autocommit = 1
This parameter is dynamic.
|
1
|
array_size
|
Specifies the number of rows retrieved with a single fetch. This
parameter is dynamic.
|
50
|
connect_string
|
Defines a connection to the target Oracle database. Each service
defines a connect_string.
Oracle provides a way of connecting to a target Oracle database
using SQLNET8. It searches for the
tnsnames.ora file in the
<install_dir>/DCO-15_0/network/admin
directory.
For this, you need an entry in the
tnsnames.ora file that describes the
instance to which you will connect in these
form: DCSERVER.world =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL=TCP) (HOST = dixville) (PORT = 1521))
(CONNECT_DATA =
(SERVICE_NAME = DCSERVER.world)
)
)
where: -
ORA_HOST is the name of the host
running Oracle RDBMS. ORACLE_SRV
is the SID of the RDBMS you intend to connect to. It
is analogous to the subnetwork name: PORT, which is
the socket number on which the TNS listener is
listening for connection requests.
-
ORACLE_SERVER is the alias used to
connect to the Oracle RDBMS. The alias name can be
any logical name. It is the same as the server name
in Sybase terminology. You can have multiple entries
for different services in the
tnsnames.ora, just as in the
Sybase sql.ini file.
In this example, the connect string required by ECDA
Option for Oracle is
ORACLE_SERVER. This is used
when defining the connect_string
parameter in the configuration
file: connect_string = ORACLE_SERVER
This parameter is dynamic.
|
|
csp_uppercase
|
Before querying Oracle, this converts names to uppercase in the
catalog stored procedures sp_tables,
sp_columns,
sp_statistics, and
sp_stored_procedures.This parameter is
dynamic.
|
1
|
date_format
|
Specifies the date format used in SQL statements. This setting is
ignored for connections from Adaptive Server. See your Oracle
documentation for more information on date format strings.
The syntax for date_format
is: date_format=Oracle_Date_Format_String
This parameter is dynamic. Note:
The configuration parameter setting
date_format is reserved for all
ECDA Option for Oracle client connections in
passthrough mode, for example,
ISQL, which excludes Adaptive
Server/CIS clients.
|
MON DD YYYY HH:MI:SSAM
|
default_precision
|
Specifies the Sybase precision when an Oracle number datatype is
defined without precision or scale. This parameter affects proxy
table datatype mappings and sp_columns results.
You can define a distinct default_precision
setting for each service. Valid Sybase precision range is 1–38.
This parameter is dynamic.
|
38
|
default_scale
|
Specifies the Sybase scale when an Oracle number
datatype is defined without precision or scale. This parameter
affects proxy table datatype mappings and
sp_columns results.
You can define a distinct default_precision
setting for each service. Valid Sybase scale range is 0–38. This
parameter is dynamic.
|
0
|
insert_array_size
|
Specifies the number of rows to batch before issuing an insert.
This represents the number of rows that ECDA Option for Oracle
buffers before calling Oracle to insert them. Array inserts are
performed when a bulk load event is sent to the ECDA Option for
Oracle.This parameter is dynamic.
|
50
|
number_mode
|
Determines the behavior for converting Oracle data with a
datatype number. You can define a distinct
number_mode setting for each service.
With a setting of 1, ECDA Option for Oracle
attempts to return data as tinyint,
smallint, int,
float or numeric.
Overflows are possible.
A setting of 0 was used to support pre-System
10™ servers. However, because pre-System 10 servers are no
longer supported by ECDA Option for Oracle, a setting of
2 causes all numbers to be returned as
numeric. This setting gives the best
performance.
This parameter is dynamic.
|
2
|
|
session_time_limit
|
Specifies the maximum length of time that a two-phase commit
transaction can be inactive before it is automatically aborted
by the Oracle system. The unit for this time limit is in seconds
and the value of 0 indicates no limit.
The syntax for session_time_limit
is: session_time_limit=value
This parameter is dynamic.
|
60
|
timestamp_format
|
Specifies the timestamp format used in SQL
statements. This setting is ignored for connections from
Adaptive Server. The timestamp format depends
on the value of the timestamp_ms_support:
-
If the value = 0, the
timestamp format is: MON DD YYYY
HH:MI:SSAM
-
If the value = 1, the
timestamp format is: MON DD YYYY
HH:MI:SS.FFAM
Note: The configuration parameter setting
timestamp_format is reserved
for all ECDA Option for Oracle client connections
in passthrough mode, for
example, ISQL, which excludes
Adaptive Server/CIS clients.
|
MON DD YYYY HH:MI:SSAM
|
timestamp_ms_support
|
Specifies whether the timestamp_format is used
in SQL statements. A value of 1 indicates
that the timestamp_format is used, and a
value of 0 indicates it is not used. This
parameter is dynamic.
|
0
|
timestamp_tz_format
|
Normalizes the data value returned to the time zone of ECDA
Option for Oracle. The timestamp_tz_format
default is independent of the timestamp
millisecond support configuration parameter.
The Oracle timestamp_tz_format is sent back to
the client as a character string, and is formatted depending on
these: -
If the client is a non-Adaptive Server/CIS client and
the timestamp_tz_format was
changed, the new format is used.
-
If the client is a non-Adaptive Server/CIS client and
the timestamp_tz_format was not
changed, the default format is used.
-
If the client is an Adaptive Server/CIS client, the
character string is returned using the default
format.
In CIS, to map a proxy_table to an existing Oracle table that
contains a column with the timestamp_tz_format
datatype, the create proxy_table command maps
the column to a char (64) and if the create existing
table command is used, a char (64) must be
specified for the column representing the
timestamp_tz_format.
|
MON DD YYYY HH:MI:SS.FFAM TZH:TZM
|
traceflags
|
Controls the types of messages written to the log file.
Specify multiple trace flags using
commas: traceflags = 1,2,3,4,5,6
This parameter is dynamic.
|
|
triggers
|
For internal use only.
|
0
|
two_phase_commit
|
Enables the two-phase commit feature. This parameter is
static.
|
0
|