| Database connections / Database vendor specific parameters in FGLPROFILE | |
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.
Maximum number of rows to be pre-fetched.
dbi.database.stores.ora.prefetch.rows = 50
You can use this parameter to increase performance by defining the maximum number of rows to be fetched automatically. However, the bigger this parameter is, the more memory is used by each program. This parameter applies to all cursors in the program.
The default is 10 rows.
Maximum buffer size for pre-fetching (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 pre-fetch.
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 can't 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.
Switch to enable scrollable cursor emulation to workaround Oracle bugs.
dbi.database.stores.ora.cursor.scroll.emul = true
A lot of customers have reported bugs with native Oracle scrollable cursors. To workaround these bugs, you can set this entry and enable client-side scrollable cursors emulation. You should however use native scroll cursors if possible, these are more efficient as the emulation. Temporary files will be created on the program server if this option is true.
Default is true for drivers designed for Oracle versions <= 9.0, false for more recent versions of Oracle.
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. Note however that 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).