Real Time Information Director User Documentation

RTID Management
Hewlett-Packard Company 27 529618 - 001
operating correctly. Also, use the management client to check the processing
mode for the source system, to see whether you’ve deferred or shut off
processing from the source system in question. (The server log will also reflect
the processing mode for a given feed.) For information about processing
modes, see “Setting the Director Processing Mode.”
5. If the server log is empty, it makes sense to verify that the client or source
system actually sent the data to the correct URL.
6. If you still can’t find the problem, try using the HttpPost test driver to submit the
rejected document or documents. (You’ll find the rejected document or
documents in the error folder, configured in the Director properties file.) If you
are successful with HttpPost, the problem is likely to be on the source system or
client side.
S
S
Q
Q
L
L
E
E
x
x
c
c
e
e
p
p
t
t
i
i
o
o
n
n
s
s
Some of the most common SQL exceptions are data truncation errors and unique
constraints. Others are transient errors.
Data Truncation
In the case of data truncation, the server log identifies the record that was truncated, but
you must still identify the column. One way to isolate the problem to a column is to
compare the record output with the DDL that defines the data. Another is use SQL
statement tracing in a Director test driver. (Because the test drivers are used mainly in
the context of metadata development, they are described in the document entitled “RTID
Extensibility,” rather than in this document.)
Once you’ve identified the column, consider whether the input data was valid for the
field type. If not, discuss the problem with the party responsible for the input. If the
problem cannot be addressed by the source system or client, you can update the
document definition to truncate the data appropriately. (Of course, you should first make
sure the truncated data will be acceptable to downstream users of the data.)
If the best solution to the data truncation problem is to change the data model, you can
usually rely on the Director to re-query the schema. Alternatively, you can use the
management client to load the schemas for tables you have modified.
Unique Constraint
An error message of this type means that the input data contained two instances of
something when the data model allows only one.
If the client or source system is sending duplicate data, the best approach to this problem
is to correct the problem on the client side. Alternatively, you can
• Change the data model to accept more instances of the item, if that makes sense