Hello,
I've got some trouble with a SELECT statement. It works fine if I
execute it via the SQL studio or through ODBC(under Windows). It fails
under linux with the direct SAP access(SuSE Linux 8.2). We are using
the
sapdb 7.3.0.46.
The SQL command:
SELECT s.slot_id, s.delivery_day, s.unit, g.gate_index, t.time_from,
d.billing_number, d.quantity, d.in_out, d.description,
d.carrier_company_id, d.disponent_id, d.driver_name, d.arrival_time,
d.departure_time, d.radio_number, sd.tour_id, d.delivery_id ,s.status,
g.gate_index, t.time_to, t.time_id, s.gate_id, s.viewed, s.location_id,
s.lock_id, tt.number, tt.necessary_slots, d.status, d.arrival_date,
d.departure_date
FROM tab_tislot_slot s
JOIN tab_tislot_slot_delivery sd ON (sd.slot_id = s.slot_id)
JOIN tab_tislot_delivery d ON (d.delivery_id = sd.delivery_id)
JOIN tab_tislot_gates g ON (g.gate_id=s.gate_id)
JOIN tab_tislot_time t ON (t.time_id=s.time_id)
JOIN tab_tour tt ON (tt.tour_id=sd.tour_id)
WHERE d.carrier_company_id = 221612 and d.datetime >= '2004-06-20
01:01:01'
leads to:
220070
[SAP AG][LIBSQLOD SO] Invalid datetime format.
My problem is how to find out what exactly is going wrong. The datetime
format is IMHO correct, so the problem is probably somewhere else.
Could someone give me a hint how to trace the bug? I already looked at
the knltrace.dat but it doesn't tell me very much, except maybe that
the
conflicting SQL statement leads to a *** key_not_found *** message.
(The knltrace is too big to post it here, but I could provide it if
requested)
Thanks a lot
Andreas Klenk
