HI,

I've using a very simple schema-unaware JDBC driver (3.5.2) to trigger
embeded sql statements. This works fine but I have noticed not all events
are being logged to the database (MS SQL 2005). I've looked at the logs and
I can see the following:-
____________________________
DirXML Log Event -------------------
Driver: \NONEAPPAUTH\NONEGROUP\Services\NONEAPPAUTH_Driver Set\SSPR
audit
Channel: Subscriber
Status: Retry
Message: Code(-9006) The driver returned a "retry" status indicating
that the operation should be retried later. Detail from driver:
<description>An error occurred executing statement "INSERT INTO SSPREvents
( EventTime,EventUser, EventType, EventHotID, EventBU) VALUES ( '01/06/09
14:40:19' , 'BOBBYJJ' , 'Responses updated' , 'UAB00123' , 'GROUP' )".
There is a connectivity-related problem.</description>
<jdbc:exception jdbc:class="java.sql.SQLException" jdbc:error-code="0"
jdbc:sql-state="08S01" xmlns:jdbc="urn:dirxml:jdbc">
<jdbc:message>[Microsoft][SQLServer 2000 Driver for JDBC]Connection
reset</jdbc:message>
</jdbc:exception>

[01/06/09 14:40:49.914]:Audit ST:
DirXML Log Event -------------------
Driver: \NONEAPPAUTH\NONEGROUP\Services\NONEAPPAUTH_Driver Set\SSPR
audit
Channel: Subscriber
Object: \NONEAPPAUTH\NONEGROUP\UK\GBNONEGROUP\NONE GROUP\IS\ITES
SERVICE SECURITY\BOBBYJJ
Status: Warning
Message: Unable to process command 'add' while driver is running in
schema-unaware mode. Ignoring.

__________________________

This is fine and i've seen these retrey messages before on other drivers,
problem is the retry never seems to happen. Is this how it is with
schema-unaware drivers?

Any thoughts appreciated!

Thanks,

Matt

The driver configuration is below:-

<?xml version="1.0" encoding="UTF-8"?>
<driver-config name="JDBC IDM Driver">
<driver-options>
<configuration-values>
<definitions>
<definition display-name="Third-party JDBC driver class name:" id="163"
name="jdbc-class" type="string">
<description>Specify the class name of your third-party JDBC driver.
Verify that the jar or zip file containing this class is version compatible
with the target database.</description>
<value>com.microsoft.jdbc.sqlserver.SQLServerDrive r</value>
</definition>
<group>
<!-- NOTE: you have to give all params a name, even if they're not
relevant to actual driver configuration -->
<definition display-name="Show the database scoping parameters?"
id="164" name="ignore1" type="enum">
<description>Show parameters that control how much of the database is
visible to this driver?</description>
<enum-choice display-name="show">show</enum-choice>
<enum-choice display-name="hide">hide</enum-choice>
<value>show</value>
</definition>
<subordinates active-value="show">
<group>
<definition display-name="Synchronization filter:" id="165"
name="sync-filter" type="enum">
<description>On start-up, the driver caches database metadata on a
limited number of tables or views to facilitate data synchronization. You
can cache no table or view metadata (exclude all tables or views), cache
metadata on all tables or views owned by a single database user (include by
schema membership) or cache metadata on an explicit list of table or view
names (include by table or view name). If no table or view metadata is
cached, the driver acts as a pass-through agent for embedded SQL. In this
state, standard XDS events (add, modify, delete) are ignored.</description>
<enum-choice display-name="exclude all
tables/views">empty</enum-choice>
<enum-choice display-name="include by schema
membership">schema</enum-choice>
<enum-choice display-name="include by table/view
name">list</enum-choice>
<value>empty</value>
</definition>
<subordinates active-value="schema">
<definition display-name="Schema name:" id="166" name="sync-schema"
type="string">
<description>Specify the name of the database schema that contains
the tables or views to synchronize. Schema is usually synonymous with
ownership. For example, if database user idm owns table table1, table1 is
said to be part of the idm schema. </description>
<value></value>
</definition>
<group>
<definition display-name="Use custom regular expression filters?"
id="167" name="ignore2" type="enum">
<description>Select whether you want to use regular expressions to
include or exclude tables or views. These parameters are useful when
synchronizing with a large schema and you need to reduce the number of
tables or view definitions cached by this driver. Schema filtering can
reduce start-up time as well as reduce runtime memory
utilization.</description>
<enum-choice display-name="yes">1</enum-choice>
<enum-choice display-name="no">0</enum-choice>
<value>0</value>
</definition>
<subordinates active-value="1">
<definition display-name="Include filter expression:" id="168"
name="include-table-filter" type="string">
<description>Specify a Java regular expression filter for
including tables or views.</description>
<value></value>
</definition>
<definition display-name="Exclude filter expression:" id="169"
name="exclude-table-filter" type="string">
<description>Specify a Java regular expression filter for
excluding tables or views.</description>
<value></value>
</definition>
</subordinates>
</group>
</subordinates>
<subordinates active-value="list">
<definition display-name="Table or view names:" id="170"
name="sync-tables" type="string">
<description>Specify the names of the tables or views to
synchronize. You might need to schema-qualify these names (for example
owner.table). Use a semicolon, comma, or space as a delimiter for multiple
values. This parameter is useful if you need to reduce the number of table
or view definitions cached by this driver, which can shorten driver start-up
time as well as reduce runtime memory utilization. It is also useful when
synchronizing tables or views that reside in different database schemas
(that is, are owned by multiple database users).</description>
<value>SSPREvents</value>
</definition>
</subordinates>
</group>
</subordinates>
</group>
<definition display-name="Time syntax:" id="171" name="time-syntax"
type="enum">
<description>Select whether the time-related data types are returned as
integers, canonical strings, or Java strings. The advantage of returning
time values as integers is that integer values easily map to eDirectory's
native time data types. The disadvantage is the limited range. An integer
value that represents the number of seconds since 1970 can cover a date
range from about 1910 to 2030 if interpreted as a signed value. By default,
Identity Manager interprets time-related integer data types as unsigned
values. String timestamps can cover a much broader range, like database
timestamps, and are more precise, but must be mapped to string data types in
Identity Manager. Canonical string timestamps, dates, and times are
published in the following formats: CCYYMMDDHHMMSSNNNNNNNNN, CCYYMMDD and
HHMMSS, respectively (where C = century, Y = year, M = month or minute, D =
day, H = hour, S = second, N = nano). These fixed-length formats have the
virtue of collating in chronological order on any platform in any locale.
Java string timestamps, dates, and times are published in the following
formats: yyyy-mm-dd hh:mm:ss.fffffffff, yyyy-mm-dd and hh:mm:ss,
respectively (where y = year, m = month or minute, d = day, h = hour, s =
second, f = nano).</description>
<enum-choice display-name="integer (default)">_</enum-choice>
<enum-choice display-name="canonical string">2</enum-choice>
<enum-choice display-name="java string">3</enum-choice>
<value>_</value>
</definition>
<definition display-name="State directory:" id="172" name="state-dir"
type="string">
<description>Specify the path of the folder where you want this driver
to store state information. Changing this value when using triggerless
publication can force a resync of all objects.</description>
<value>.</value>
</definition>
<group>
<definition display-name="Show connectivity parameters?" id="173"
name="ignore11" type="enum">
<description>Select whether to show connectivity-related
parameters.</description>
<enum-choice display-name="show">show</enum-choice>
<enum-choice display-name="hide">hide</enum-choice>
<value>show</value>
</definition>
<subordinates active-value="show">
<definition display-name="Use minimal number of connections?" id="174"
name="use-single-connection" type="enum">
<description>Select whether the Subscriber and Publisher share a
database connection. Normally, this driver uses three database connections
when both channels are enabled (one subscription connection and two
publication connections). This parameter reduces the number of required
connections to two (one dedicated publication connection and one shared
subscription and publication connection).</description>
<enum-choice display-name="dynamic default">_</enum-choice>
<enum-choice display-name="yes">1</enum-choice>
<enum-choice display-name="no">0</enum-choice>
<value>_</value>
</definition>
<definition display-name="Connection initialization statements:"
id="175" name="connection-init" type="string">
<description>What SQL statements, if any, should be executed
immediately after connecting to the database? Use semicolon-delimiters for
mulitple values. This parameter is useful for changing database contexts or
setting session properties.</description>
<value></value>
</definition>
<definition display-name="Connection properties:" id="176"
name="connection-properties" type="string">
<description>List connection properties as key value pairs. For
example: key=value. Use a semicolon as a delimiter for multiple values.
For example: key1=value1; key2=value2.</description>
<value></value>
</definition>
</subordinates>
</group>
<group>
<definition display-name="Show the compatibility parameters?" id="177"
name="ignore3" type="enum">
<description>Select whether to show parameters that can adjust adjust
driver behavior to enhance compatibility with various third-party JDBC
implementations and databases.</description>
<enum-choice display-name="show">show</enum-choice>
<enum-choice display-name="hide">hide</enum-choice>
<value>show</value>
</definition>
<subordinates active-value="show">
<group>
<definition display-name="Use custom descriptor files?" id="178"
name="ignore4" type="enum">
<description>Select whether you want to use custom XML descriptor
files that describe the unique properties of your third-party JDBC
implementation or database to this driver.</description>
<enum-choice display-name="yes">1</enum-choice>
<enum-choice display-name="no">0</enum-choice>
<value>0</value>
</definition>
<subordinates active-value="1">
<definition display-name="JDBC driver descriptor filename:" id="179"
name="jdbc-driver-descriptor" type="string">
<description>Specify the name of the descriptor file for your
third-party JDBC driver. The filename must have the extension .xml and be
located in a jar file whose name begins with "jdbc" (case-insensitive) and
in the runtime classpath.</description>
<value></value>
</definition>
<definition display-name="Database descriptor filename:" id="180"
name="database-descriptor" type="string">
<description>Specify the name of the descriptor file for the target
database. The filename must have the extension .xml and be located in a jar
file whose name begins with "jdbc" (case-insensitive) and in the runtime
classpath.</description>
<value></value>
</definition>
</subordinates>
</group>
<group>
<definition display-name="Show backward compatibility parameters?"
id="181" name="ignore12" type="enum">
<description>Select whether to show parameters that ensure backward
compatibility.</description>
<enum-choice display-name="show">show</enum-choice>
<enum-choice display-name="hide">hide</enum-choice>
<value>show</value>
</definition>
<subordinates active-value="show">
<definition display-name="Enable table referential attribute
support?" id="182" name="enable-refs" type="enum">
<description>Select whether table columns constrained with foreign
key constraints are interpreted as referential attributes. Referrential
attributes allow relationships, such as containment, to exist between
tables. For 1.0 backwards compatibility, referential attribute support must
be disabled.</description>
<enum-choice display-name="yes (default)">_</enum-choice>
<enum-choice display-name="no">0</enum-choice>
<value>_</value>
</definition>
<definition display-name="Enable view meta-identifier support?"
id="183" name="enable-meta-identifiers" type="enum">
<description>Select whether view column name prefixes ("pk_",
"fk_", "sv_", "mv_") are interpreted as metadata. When enabled, the
prefixes are not considered part of view column names. Meta-identifiers
allow one to define referrential relationships between views and mark view
columns as multi or single-valued. For 1.5 backwards compatibility,
meta-identifier support must be disabled.</description>
<enum-choice display-name="yes (default)">_</enum-choice>
<enum-choice display-name="no">0</enum-choice>
<value>_</value>
</definition>
</subordinates>
</group>
<group>
<definition display-name="Show transaction-related parameters?"
id="184" name="ignore5" type="enum">
<description>Select whether to show transaction-related
parameters.</description>
<enum-choice display-name="show">show</enum-choice>
<enum-choice display-name="hide">hide</enum-choice>
<value>show</value>
</definition>
<subordinates active-value="show">
<definition display-name="Use manual transactions?" id="185"
name="use-manual-transactions" type="enum">
<description>Select whether this driver uses transactions. Are
transactions supported by the target database or table implementation you
are using?</description>
<enum-choice display-name="dynamic default">_</enum-choice>
<enum-choice display-name="yes">1</enum-choice>
<enum-choice display-name="no">0</enum-choice>
<value>_</value>
</definition>
<definition display-name="Transaction isolation level:" id="186"
name="transaction-isolation-level" type="enum">
<description>Use this parameter to set advanced transaction
properties. For additional information on what these values mean, please
refer to the JDBC tutorial at
http://java.sun.com/docs/books/tutor...nsactions.html and
the documentation of your third-party JDBC driver or database.</description>
<enum-choice display-name="dynamic default">_</enum-choice>
<enum-choice display-name="unsupported">unsupported</enum-choice>
<enum-choice display-name="none">none</enum-choice>
<enum-choice display-name="read uncomitted">read
uncommitted</enum-choice>
<enum-choice display-name="read comitted">read
committed</enum-choice>
<enum-choice display-name="repeatable read">repeatable
read</enum-choice>
<enum-choice display-name="serializable">serializable</enum-choice>
<value>read committed</value>
</definition>
</subordinates>
</group>
<group>
<definition display-name="Show statement-related parameters?"
id="187" name="ignore6" type="enum">
<description>Select whether to show statement-related
parameters.</description>
<enum-choice display-name="show">show</enum-choice>
<enum-choice display-name="hide">hide</enum-choice>
<value>show</value>
</definition>
<subordinates active-value="show">
<definition display-name="Reuse statements?" id="188"
name="reuse-statements" type="enum">
<description>Should this driver reuse java.sql.Statement objects or
close and reallocate them with each use?</description>
<enum-choice display-name="dynamic default">_</enum-choice>
<enum-choice display-name="reuse">1</enum-choice>
<enum-choice display-name="close and reallocate">0</enum-choice>
<value>_</value>
</definition>
<definition display-name="Number of returned result sets:" id="189"
name="handle-stmt-results" type="enum">
<description>Specify how many result sets can be returned from an
SQL statement.</description>
<enum-choice display-name="dynamic default">_</enum-choice>
<enum-choice display-name="none">none</enum-choice>
<enum-choice display-name="one">single</enum-choice>
<enum-choice display-name="multiple">multiple</enum-choice>
<value>_</value>
</definition>
<group>
<definition display-name="Enable statement-level locking?" id="190"
name="enable-locking" type="enum">
<description>Select whether this driver explicitly locks database
resources before executing each statement.</description>
<enum-choice display-name="no (default)">0</enum-choice>
<enum-choice display-name="yes">1</enum-choice>
<value>0</value>
</definition>
<subordinates active-value="1">
<group>
<definition display-name="Use the custom lock statement generator
class?" id="191" name="ignore13" type="enum">
<description>Select whether you want to use a custom class to
generate locking statements.</description>
<enum-choice display-name="yes">1</enum-choice>
<enum-choice display-name="no">0</enum-choice>
<value>0</value>
</definition>
<subordinates active-value="1">
<definition display-name="Lock statement generator class:"
id="192" name="lock-generator-class" type="string">
<description>Specify the name of the class used to generate
locking statements.</description>
<value></value>
</definition>
</subordinates>
</group>
</subordinates>
</group>
</subordinates>
</group>
<definition display-name="Force username case:" id="193"
name="force-username-case" type="enum">
<description>Select the case of the authentication
username.</description>
<enum-choice display-name="don't force (default)">_</enum-choice>
<enum-choice display-name="to upper case">upper</enum-choice>
<enum-choice display-name="to mixed case">mixed</enum-choice>
<enum-choice display-name="to lower case">lower</enum-choice>
<value>_</value>
</definition>
<definition display-name="Left outer-join operator:" id="194"
name="left-outer-join-operator" type="enum">
<description>Select a left outer-join operator.</description>
<enum-choice display-name="dynamic default">_</enum-choice>
<enum-choice display-name="*=">*=</enum-choice>
<enum-choice display-name="(+)">(+)</enum-choice>
<enum-choice display-name="LEFT OUTER JOIN">LEFT OUTER
JOIN</enum-choice>
<value>_</value>
</definition>
<definition display-name="Retrieve minimal metadata?" id="195"
name="minimal-metadata" type="enum">
<description>Select whether this driver runs using the least amount
of database metadata possible. This parameter is useful when a given
third-party JDBC driver does not implement one of the optional metadata
method normally utilized by this driver. When set to no, referential data
and child parent relationships are no longer available to this
driver.</description>
<enum-choice display-name="dynamic default">_</enum-choice>
<enum-choice display-name="yes">1</enum-choice>
<enum-choice display-name="no">0</enum-choice>
<value>_</value>
</definition>
<definition display-name="Function return method:" id="196"
name="function-return-method" type="enum">
<description>Select how the results are returned from database
functions.</description>
<enum-choice display-name="dynamic default">_</enum-choice>
<enum-choice display-name="result set">result set</enum-choice>
<enum-choice display-name="scalar return value">return
value</enum-choice>
<value>_</value>
</definition>
<definition display-name="Supports schemas in metadata retrieval?"
id="197" name="supports-schemas-in-metadata-retrieval" type="enum">
<description>Select whether schema names are used to retrieve
database metadata.</description>
<enum-choice display-name="dynamic default">_</enum-choice>
<enum-choice display-name="yes">1</enum-choice>
<enum-choice display-name="no">0</enum-choice>
<value>_</value>
</definition>
<definition display-name="Sort column names by:" id="198"
name="column-position-comparator" type="enum">
<description>For legacy databases that don't support the notion of
column position (DB2/AS400), a backup ordering algorithm must be employed.
Sorting columns names by hexadecimal value ensures that if the this driver
is relocated to a different server, it continues to function without
modification. Sorting column names by platform or locale string collation
order is more intuitive, but might require a configuration changes if a
driver instance is relocated to a different server. The event log table
column order and compound column name order might change. In the case of
the latter, the schema-mapping rule and object association values might need
to be updated. In the case of the former, event log table columns might
have to be renamed.</description>
<enum-choice display-name="dynamic default">_</enum-choice>
<enum-choice display-name="hexadecimal
value">com.novell.nds.dirxml.driver.jdbc.util.conf ig.comp.StringByteComparator</enum-choice>
<enum-choice display-name="string collation
order">com.novell.nds.dirxml.driver.jdbc.util.conf ig.comp.StringComparator</enum-choice>
<value>_</value>
</definition>
</subordinates>
</group>
</definitions>
</configuration-values>
</driver-options>
<subscriber-options>
<configuration-values>
<definitions>
<group>
<definition display-name="Disable subscriber?" id="199" name="disable"
type="enum">
<description>Select whether you want to ignore events flowing from
Identity Manager to the database.</description>
<enum-choice display-name="no (default)">_</enum-choice>
<enum-choice display-name="yes">1</enum-choice>
<value>_</value>
</definition>
<subordinates active-value="_">
<group>
<definition display-name="Show primary key parameters?" id="200"
name="ignore10" type="enum">
<description>Select whether to show parameters that control how and
when primary key values are generated.</description>
<enum-choice display-name="show">show</enum-choice>
<enum-choice display-name="hide">hide</enum-choice>
<value>show</value>
</definition>
<subordinates active-value="show">
<definition display-name="Generation/retrieval method
(table-global):" id="201" name="key-gen-method" type="enum">
<description>Select how the primary key values are being generated
or retrieved. This setting is global for all tables or views.</description>
<enum-choice display-name="subscription event
(default)">_</enum-choice>
<enum-choice
display-name="subscriber-generated">driver</enum-choice>
<enum-choice display-name="auto-generated/identity
column">auto</enum-choice>
<value>driver</value>
</definition>
<definition display-name="Retrieval timing (table-global):" id="202"
name="key-gen-timing" type="enum">
<description>Select when the primary key values are retrieved.
Select whether the key values are retrieved before or after the row
insertion. This setting is global for all tables or views.</description>
<enum-choice display-name="before row insertion
(default)">_</enum-choice>
<enum-choice display-name="after row insertion">after</enum-choice>
<value>_</value>
</definition>
<definition display-name="Method and timing (table-local):" id="203"
name="key-gen" type="string">
<description>Specify how and when primary key values are generated
or retrieved on a per table or view basis. This parameter overrides global
method and timing settings. Use semicolon, comma, or space as the delimiter
for multiple values.</description>
<!-- split MS by database; rope-in value for MS versions < 2005 -->
<value>SSPREvents(DRIVER)</value>
</definition>
</subordinates>
</group>
<definition display-name="Disable statement-level locking?" id="204"
name="disable-locking" type="enum">
<description>Select whether to disable statement locking. Select
whether explicit locking or database resources are disabled on this
channel.</description>
<enum-choice display-name="yes">1</enum-choice>
<enum-choice display-name="no (default)">0</enum-choice>
<value>0</value>
</definition>
<definition display-name="Add default values on view insert?" id="205"
name="add-default-values-on-view-insert" type="enum">
<description>Select whether the Subscriber channel adds default
values to insert operations on views. This parameter is desirable for
satisfying instead-of-trigger constraints that require non-null values be
provided for non-nullable columns before instead-of-triggers fire. This
parameter has no effect on tables.</description>
<enum-choice display-name="dynamic default">_</enum-choice>
<enum-choice display-name="yes">1</enum-choice>
<enum-choice display-name="no">0</enum-choice>
<value>0</value>
<!-- base on direct or indirect synchronization model -->
</definition>
</subordinates>
</group>
</definitions>
</configuration-values>
</subscriber-options>
<publisher-options>
<configuration-values>
<definitions>
<group>
<definition display-name="Disable the Publisher channel?" id="206"
name="disable" type="enum">
<description>Select whether you want to ignore events flowing from the
database to Identity Manager.</description>
<enum-choice display-name="no (default)">_</enum-choice>
<enum-choice display-name="yes">1</enum-choice>
<value>1</value>
</definition>
<subordinates active-value="_">
<group>
<definition display-name="Publication mode:" id="207"
name="publication-mode" type="enum">
<description>Select whether you want to use triggered or triggerless
publication. Triggered publication uses database triggers to capture events
and log them in a table. Triggerless publication derives events by
inspecting database tables or views. Triggered publication is more
efficient, but requires substantial database-side configuration.
Triggerless publication is less efficient, but requires minimal
database-side configuration.</description>
<enum-choice display-name="triggered">_</enum-choice>
<enum-choice display-name="triggerless">2</enum-choice>
<value>_</value>
</definition>
<subordinates active-value="_">
<definition display-name="Event log table name:" id="208"
name="log-table" type="string">
<description>Specify the name of the table where publication events
are stored.</description>
<value>direct.direct_process</value>
</definition>
<definition display-name="Delete processed rows?" id="209"
name="delete-from-log" type="enum">
<description>Select whether processed rows are deleted from the
event log table. There is a significant performance hit when processed rows
are left in the event log table. The performance cost can be mitigated by
moving processed rows from the event log table into an event history table
using the "Post polling statements:" parameter.</description>
<enum-choice display-name="yes (default)">_</enum-choice>
<enum-choice display-name="no">0</enum-choice>
<value>_</value>
</definition>
<definition display-name="Optimize updates?" id="210"
name="optimize-update" type="enum">
<description>Select whether the Publisher channel optimizes update
events before sending them to the engine. When set to yes, all update
events are optimized. When set to no, select update events are not. For a
more complete explanation of this parameter, consult the driver
implementation guide.</description>
<enum-choice display-name="no (default)">_</enum-choice>
<enum-choice display-name="yes">1</enum-choice>
<value>_</value>
</definition>
<definition display-name="Allow loopback?" id="211"
name="allow-loopback" type="enum">
<description>Select whether to allow events initiated by the
Subscriber channel to loopback on the Publisher channel.</description>
<enum-choice display-name="no (default)">_</enum-choice>
<enum-choice display-name="yes">1</enum-choice>
<value>_</value>
</definition>
<definition display-name="Disable statement-level locking?" id="212"
name="disable-locking" type="enum">
<description>Select whether to disable statement locking. Select
whether explicit locking or database resources are disabled on this
channel.</description>
<enum-choice display-name="yes">1</enum-choice>
<enum-choice display-name="no (default)">0</enum-choice>
<value>0</value>
</definition>
</subordinates>
<subordinates active-value="2">
<definition display-name="Startup option:" id="213"
name="startup-option" type="enum">
<description>Determine the Publisher's behavior on
start-up.</description>
<enum-choice display-name="process all changes
(default)">_</enum-choice>
<enum-choice display-name="process future changes
only">2</enum-choice>
<enum-choice display-name="resync all objects">1</enum-choice>
<value>_</value>
</definition>
</subordinates>
</group>
<group>
<definition display-name="Enable future event processing?" id="214"
name="handle-future-events" type="enum">
<description>Select whether to process events in the event log table
based upon their effective date as opposed to order of insertion (triggered
publication) or publish database local time with each event (triggerless
publication).</description>
<enum-choice display-name="no (default)">_</enum-choice>
<enum-choice display-name="yes">1</enum-choice>
<value>_</value>
</definition>
<subordinates active-value="1">
<group>
<definition display-name="Use custom timestamp statement?" id="215"
name="ignore8" type="enum">
<description>Select whether you want to specify a custom SQL
statement that supplies the current time and date on the database server.
By default, a statement is dynamically derived.</description>
<enum-choice display-name="yes">1</enum-choice>
<enum-choice display-name="no">0</enum-choice>
<value>0</value>
</definition>
<subordinates active-value="1">
<definition display-name="Current timestamp statement:" id="216"
name="current-timestamp-stmt" type="string">
<description>Specify the SQL statement that is used to determine
the current time and date on the database server.</description>
<value></value>
</definition>
</subordinates>
</group>
</subordinates>
</group>
<group>
<definition display-name="Show polling-related parameters?" id="217"
name="ignore9" type="enum">
<description>Select whether to show parameters that control polling
behavior.</description>
<enum-choice display-name="show">show</enum-choice>
<enum-choice display-name="hide">hide</enum-choice>
<value>hide</value>
</definition>
<subordinates active-value="show">
<definition display-name="Polling interval (in seconds):" id="218"
name="polling-interval" type="string">
<!--
NOTE: can't be type="int"; this type doesn't
permit no value which is permissible
when time-of-day is used.
-->
<description>Specify the minimum number of seconds of inactivity
that elapses between polling cycles. In practice, more than the number of
specified seconds can elapse (this is a lower bound only). The default is
10 seconds.</description>
<value>10</value>
</definition>
<definition display-name="Polling time of day:" id="219"
name="time-of-day" type="string">
<description>Specify when the Publisher channel checks for new
database events each day. Mulitple formats for the Time values are
supported. The preferred format is hh:mm:ss, where h = hour, m = minute, s
= second.</description>
<value></value>
</definition>
<definition display-name="Post polling statements:" id="220"
name="post-poll-stmt" type="string">
<description>Specify the statements, if any, that are executed
after an active polling cycle. This parameter is useful for calling a
stored procedure or function that moves processed rows from the event log
table into a history table and rebuilds indexes on the event log table. Use
semicolon as the delimiter for multiple values.</description>
<value>EXECUTE direct.proc_directlog; DELETE FROM
indirect.indirect_process</value>
</definition>
<definition display-name="Batch size:" id="221" name="batch-size"
type="enum">
<description>Specify the desired number of database events that the
Publisher channel groups together in a single publication document. The
number of events per document can be less but are not greater. The upper
bound of 128 is set to minimize the likelihood of overflowing the Java heap
and to mitigate delaying termination of the Publisher thread on driver
shutdown.</description>
<enum-choice display-name="1 (default)">_</enum-choice>
<enum-choice display-name="2">2</enum-choice>
<enum-choice display-name="4">4</enum-choice>
<enum-choice display-name="8">8</enum-choice>
<enum-choice display-name="16">16</enum-choice>
<enum-choice display-name="32">32</enum-choice>
<enum-choice display-name="64">64</enum-choice>
<enum-choice display-name="128">128</enum-choice>
<value>_</value>
</definition>
</subordinates>
</group>
</subordinates>
</group>
<definition display-name="Heartbeat interval (in minutes):" id="222"
name="pub-heartbeat-interval" type="integer">
<description>Specify how many minutes of Publisher inactivity elapses
before the Publisher sends a heartbeat document. In practice, more than the
number of minutes specified can elapse. This parameter defines a lower
bound.</description>
<value>1</value>
</definition>
</definitions>
</configuration-values>
</publisher-options>
</driver-config>