I first tried to use the ISO timestamp format, but when it failed, I assumed
it was because the ISO format expect 6 digits for the millisecond part while
SQL Server uses only 5 on the export, so I tried to specify my own format
map.
Here is the loader output. BTW, is there a way to do the "null if pos" part
without having to put all these spaces?
[EMAIL PROTECTED] sapdb $ loadercli -d sos_be -u dba,dba -b dataload.scr Opened connection to Loader SERVER at node local host. Loader Server Protocol File: '/opt/sapdb/indep_data/wrk/loader.prt'
User DBA connected to database SOS_BE on local host.
DATALOAD TABLE selection
selection_id 0001-0012
brand_id 0013-0024 null if pos 0013-0024 = '
'
source_id 0025-0036
selection_type_id 0037-0048
selection_name 0049-0148
selection_desc 0149-1148 null if pos 0149-1148 = '
'
image_caption 1149-1403 null if pos 1149-1403 = '
'
image_file 1404-1453 null if pos 1404-1453 = '
'
min_price 1454-1473 null if pos 1454-1473 = '
'
max_price 1474-1493 null if pos 1474-1493 = '
'
has_options 1494-1498
has_dependents 1499-1503
date_added 1504-1528
date_deleted 1529-1553 null if pos 1529-1553 = '
'
builder_id 1554-1565 null if pos 1554-1565 = '
'
category_type_id 1566-1577 null if pos 1566-1577 = '
'
category_id 1578-1589 null if pos 1578-1589 = '
'
item_group_id 1590-1601 null if pos 1590-1601 = '
'
item_id 1602-1613 null if pos 1602-1613 = '
'
INFILE '/home/sapdb/selection.txt' FORMATTED
BOOLEAN 'True/False'
TIMESTAMP 'YYYY-MM-DD HH:MM:SS.NNNNN'
Error during execution
-->-25301
Invalid input for date or time column: 2001-01-04 15:24:28.26300
Defined maximum number of errors (1) reached
1 error(s) during execution of command file 'dataload.scr'. ---> See log file(s) for more information.
Some error(s) occurred running command. ---> See log file(s) for more information.
Content of the log file: // * // M Error at record 1 in infile. // E -25301: Invalid input for date or time column: 2001-01-04 15:24:28.26300 // M Last transaction committed at input record 0 // * // M Sum of inserted records 0, sum of rejected records 1 // * // M Releasing user connection (USER: 'DBA'). // *
On Monday 17 March 2003 02:58, Schildberg, Steffen wrote:
Hi Avi,
Avi Schwartz [mailto:[EMAIL PROTECTED] wrote:One of the problems I am having is loading timestamp fields via the loader. I generated a fixed column size export from SQL Server but when I try to load the data, I get an error that the data is incorrect for timestamp for every SS dattetime column. I tried to add the following to the loader script:
TIMESTAMP 'YYYY-MM-DD HH:MM:SS.NNNNN'
but I still get the same error. Any idea what may be the problem?
Would you mind to post the whole command here (or a snipped of the relevant part) and the respective data to see what really happens. The timestamp definition looks good - -- Steffen Schildberg SAP DB Team SAP Labs Berlinso it should work. Regards, Steffen _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
-- Avi Schwartz Universe-watching, like golf and aging, [EMAIL PROTECTED] promotes humility - William R. Everdell
-- Avi Schwartz [EMAIL PROTECTED]
_______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
