From: Jonathan C. <cra...@pc...> - 2003-02-21 17:20:49
|
Arnaud Kerhornou wrote: > INSERT INTO Core.AlgorithmInvocation ( end_time, row_user_id, > user_write, group_write, algorithm_implementation_id, row_project_id, > algorithm_invocation_id, group_read, row_group_id, result, other_read, > cpus_used, start_time, modification_date, user_read, > row_alg_invocation_id, other_write, machine_id ) > VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, SYSDATE, ?, ?, ?, ? ) > bindValues (2002/12/6, 1, 1, 1, 2, 1, 2, 1, 1, meta, 1, 1, 2002/12/6, 1, > 1, 0, 0) > <--------------------------------- > Arnaud- The error you got was "literal does not match format string", which I think means that the two dates in the above INSERT command ("2002/12/6" for end_time and "2002/12/6" for start_time) do not conform to the default NLS_DATE_FORMAT of your Oracle instance. I don't know how (or where) these date strings are being generated, but they appear to be incorrect. I don't think they're being hard-coded, because I don't think those dates would work in our system either. We use the following default date format: nls_date_format = "YYYY-MM-DD HH24:MI:SS" Anyway, hope this helps in the debugging; Steve and Jonathan Schug are probably the most familiar with ga, so I'll let them take it from here. Jonathan -- Jonathan Crabtree Center for Bioinformatics, University of Pennsylvania 1406 Blockley Hall, 423 Guardian Drive Philadelphia, PA 19104-6021 215-573-3115 |