Oracle DB specific FGLPROFILE parameters
dbi.database.dsname.ora.schema
Name of the database schema to be selected after connection is established.
dbi.database.stores.ora.schema = "store2"
Set this parameter to a specific schema in order to share the same table with all users.
For more details, see Database users.
dbi.database.dsname.ora.prefetch.rows
Maximum number of rows to prefetch.
dbi.database.stores.ora.prefetch.rows = 50
Use this parameter to increase performance by defining the maximum number of rows to be fetched into the db client buffer. However, the bigger this parameter is, the more memory that is used by each program. This parameter applies to all cursors in the program.
The default is 10 rows.
dbi.database.dsname.ora.prefetch.memory
Maximum buffer size for prefetching (in bytes).
dbi.database.stores.ora.prefetch.memory = 4096
This parameter is equivalent to prefetch.rows
, but here you can specify the
memory size instead of the number of rows. Like prefetch.rows
, this
parameter applies to all cursors in the program.
The default is 0, which means that memory size is not included in computing the number of rows to prefetch.
dbi.database.dsname.ora.sid.command
SQL command (SELECT) to generate a unique session id (used for temp table names).
dbi.database.stores.ora.sid.command =
"SELECT TO_CHAR(SID)||'_'||TO_CHAR(SERIAL#)
FROM V$SESSION WHERE AUDSID=USERENV('SESSIONID')"
By default, the driver uses "SELECT USERENV('SESSIONID') FROM DUAL
". This is the
standard session identifier in Oracle®, but it can become a very large number and cannot be reset.
This parameter gives you the freedom to provide your own way to generate a session id.
The SELECT statement must return a single row with one single column.
Value can be an integer or an identifier.
dbi.database.dsname.ora.date.ifxfetch
Controls the way an Oracle DATE is fetched into program variables, especially CHAR/VARCHAR targets.
dbi.database.stores.ora.date.ifxfetch = true
By default, since Oracle DATE type is
equivalent to DATETIME YEAR TO SECOND
, values are fetched into
CHAR
/VARCHAR
with time information and are
formatted with the style YYYY-MM-DD hh:mm:ss
. If you need to get
the IBM®
Informix® behavior, to fetch DATEs only
with the YMD part following the DBDATE environment variable, set this parameter to
true. However, this parameter is useless when fetching Oracle DATEs into DATE
or
DATETIME
variables, which is the recommended way to hold date
and time values in programs.
Default is false
(with
time information, using normalized format).
dbi.database.dsname.ora.temptables.schema.source
Defines the source of the schema name used for temporary table emulation.
"login"
: The user name specified in the connection parameters."command"
: The value returned by a SELECT statement specified in theora.temptables.schema.command
parameter.
dbi.database.stores.ora.temptables.schema.source = "login"
By default, when using the default temporary table emulation, the driver uses no schema at all. When using global temporary table emulation, the driver uses the TEMPTABS schema by default.
When specifying a "command"
source for the schema, you can provide
your own SELECT statement to produce the schema name to be used when creating a
table.
dbi.database.dsname.ora.temptables.schema.command
SQL command (SELECT) to get the schema name to be used for temporary table emulation.
dbi.database.stores.ora.temptables.schema.source = "command"
dbi.database.stores.ora.temptables.schema.command = "SELECT SYS_CONTEXT('USERENV','SESSION_USER') FROM DUAL"
This configuration parameter is only taken into account if the
ora.temptables.schema.source
parameter is defined as
"command"
.
The SELECT statement must return a single row with one single column.
Value must be a character string.
dbi.database.dsname.ora.temptables.tablespace
Defines the tablespace to be used for temporary table emulation.
dbi.database.stores.ora.temptables.tablespace = "mytemptabs"
- When using the default temporary table emulation,
the driver uses the TEMPTABS tablespace. The tablespace specified in the
ora.temptables.tablespace
entry must be a permanent tablespace. - When using global temporary table emulation, the
driver uses no tablespace by default. The tablespace specified in the
ora.temptables.tablespace
entry must be a temporary tablespace. - When using private temporary table emulation, the
driver uses no tablespace by default. The tablespace specified in the
ora.temptables.tablespace
entry must be a temporary tablespace.
For more details, see Temporary tables.