EIM导入FileAttachmentTable需要注意的问题.docVIP

EIM_INVOICE import process insert transactions row by row even when SET BASED LOGGING = TRUE [ID 487631.1]??Modified 09-NOV-2004?????Type PROBLEM?????Status MODERATED?In this Document?? HYPERLINK /CSP/main/article?cmd=showtype=NOTdoctype=PROBLEMid=487631.1 \l SYMPTOM Symptoms?? HYPERLINK /CSP/main/article?cmd=showtype=NOTdoctype=PROBLEMid=487631.1 \l FIX Solution????? HYPERLINK /CSP/main/article?cmd=showtype=NOTdoctype=PROBLEMid=487631.1 \l aref1 Message 1 Applies to: Product Release: V7 (Enterprise)Version: 7.7.1 [18306] Fin SvcsDatabase: Microsoft SQL Server 2000Application Server OS: Microsoft Windows 2003 ServerDatabase Server OS: Microsoft Windows 2003 ServerThis document was previously published as Siebel SR 38-1506289131. Symptoms HiWe have been loading a lot of records in our Performance Environment. The data has been loaded in almost all the table like S_ORG_EXT, S_CONTACT, S_DOC_AGREE, S_SRV_REQ and many moreOne of the next load is to S_INVOICE Table.When we did this we noticed that the log which was created was extremely largeWe noticed that there is multiple INSERT Statements. Our Batch size was 25000 and there was 25000 Insert Statement.I checked the other logs, it is the not the sameOther EIM Jobs have written one Insert Statement for every BatchThis particular job writes Insert Statement for every record in the batch.Can you let us know what am I missing hereThank you Solution Message 1 For the benefit of other readers:Even when SET BASED LOGGING = TRUE is explicitly included in the .ifb file, the EIM_INVOICE import process will always perform row by row processing.This is because the S_INVOICE table is a file attachment table (it has file processing columns: FILE_EXT, FILE_NAME, FILE_REV_NUM, FILE_SRC_PATH and FILE_SRC_TYPE). As file attachment tables must be processed in row-by-row mode, so this has been determined to be the intended behavior.Valerie LowSiebel Systems Technical Support Related