Oracle Only
The following parameters apply only to the Oracle gateway.
dbevent_poll_rate
ii.hostname.gateway.oracle.dbevent_poll_rate: integer
Specifies the rate in seconds at which the gateway polls for target DBMS events while waiting for user input. A dbevent_poll_rate of zero turns off Database Event Polling, which means that when a database event is raised, the client application will not be notified ever.
The default value for this parameter is zero. If you are using database events in your installation, set dbevent_poll_rate to a positive value. The lower the number for the dbevent_poll_rate, the more frequently the gateway polls for DBMS events resulting in more database IO and CPU usage for the gateway. For more information on database events, see the Ingres OpenSQL Reference Guide.
Default: 0 (zero)
nls_date_format
ii.hostname.gateway.oracle.nls_date_format: string
Specifies the DBMS (Oracle) date format.
When using string date literals without date typecasts, the date must be in a pre-determined format. II_DATE_FORMAT has no effect on the interpretation of strings without typecasts. The host DBMS is responsible for date interpretation.
The setting for this variable is the Oracle setting for NLS_DATE_FORMAT for the session.
Only the following settings are valid:
'YYYY-MM-DD HH24:MI:SS' (ANSI format)
'DD-MON-YYYY HH24:MI:SS' (only valid if English language is used)
'DD.MM.YYYY HH24:MI:SS'
The settings are similar to the output (and input) format for II_DATE_FORMAT settings of:
FINLAND
US
Default: ANSI setting of 'YYYY-MM-DD HH24:MI:SS'.
The default returns dates numerically, and the time component is specified in 24 hour format.
This setting also affects the format that dates are returned when typecast into strings. For example:
select char(date('now'));
Important! Modifying the default ANSI setting will render client applications non-portable. There is also performance overhead associated with the execution of the Oracle UDF that underlies the implementation. You should only use this parameter for the initial application migration from the OpenROAD 3.5 Oracle driver. For the long term, it is recommended that user applications be modified to use the date data type when passing dates to Enterprise Access. This modification allows the same application to be deployed against different database back ends.