Date parsed: 12/21/2001 6:45:02 AM
Date: Fri, 21 Dec 2001 13:45:02 -0600
have added comments below.
Does he have something that will allow us to trap what he is sending to the
Database?
-----Original Message-----
From: Frank Clatterbaugh
Sent: Friday, December 21, 2001 1:38 PM
To: Doug Durham
Subject: syslog update
Here is is response.
Hi,
first I must tell you that I don't have access to an Oracle DBMS, so I
can't
try to reproduce your problem.
- Why did you not use the datatype 'datetime' for DATETIMELOCAL and
DATETIMEUTC ? If you do/did, what happens/ed?
[Doug Durham]
We tried a DATE datatype and we got non-descript ODBC error notices in the
syslog server NT event log with no data in the database.
- Are you using a date datatype for DATETIMERFC822LOCAL and
DATETIMERFC822UTC ? For these two fields the datatype must be 'varchar' or
'varchar2'.
[Doug Durham]
we are using VARCHAr2(4000) for all fields
Franz
I just checked the MSDN and it seems that there's no 'datetime' datatype,
only a 'date' datatype that should be compatible with the 'datetime'
datatype provided by Access and MS SQL Server.
>(I had to change
> > them from DATE datatypes to VARCHAR2 datatypes to get around insert
> errors)
What kind of errors happened?
Franz
---------------------------------------------------