Incremental Import/Export..Import & urgent Pls.

Hello experts!
Please help.....
We are running a program with and same database with same user/password in different location and branches without network.
We dont have any centralization, regularly after updating stock and sales they will send the .dmp file through e-mail, I will recieve and rename it and insert the stock and sales tables in Head Office and back to original position.
Regularly it is difficult, I want some automation Export/Import command so that I can update the recieved updated part of table or file.
The story is big, kindly help...it is important and urgent.
Thanks for help in advance,
Syed Muzzammil.

Incremental Imports are no longer supported.
You could use fast refreshable materialized views if you can use a db-link.
Do you know Oracle Streams ?
Just ideas.
But probably you will be stuck with traditional table exports.
Regards
Laurent

Similar Messages

Incremental import - is it possible?

Hi,
i'm dealing with a sort of schema replication between two db.
I have a full export and i need to do a sort of incremental import of some schemas.
No way to use dblink. There's a ..... firewall!
I'm planning to use dp, much better than exp/imp, but i'm not sure it's so smart to retrieve only the data i need.
I see that there is an option, TABLE_EXISTS_ACTION=APPEND but i suppose dp would append every rows it founds causing a duplication..
Any ideas or suggestion?
Thanks
Acr

Incremental updates won't be possible as required in this situation.
Oracle streams can be used to configure replication between the servers while considering that port 1521 or whatever port of your listener is allowed via firewall.
Regards,

Incremental Import

Hi,
Is it possible to import just the updated/changed data from one database to another(Incremental Import), if yes, where I get information about it.
Khawar

well, there is nothing like incremental import. there is incremental export, what happend when you import is, when there is a change on alrady existing table, it just wont import those changes, rather it drop the object and import fresh copy of it again.
Jaffar

IPhone - Discerning High Importance/Urgent Mail Messages

Help! I have an iPhone 3G S. I can see my work email (MS Hosted Exhcange) on my unit, but I can't figure out how to discern when I get a High Importance/Urgent message. Like on Outlook it gives you an exclamation point. Any suggestions?
Thanks much.

The iPhone mail app treats all emails equally. The importance rating thing is an Outlook thing.

I have a MacBook Pro 13.3 OS- MAC OS X LION.Whenever I am staring the computer, it says You need to restart your computer by pressing the power button.I did this number of times and everytime it freezes to the same screen.Solution needed urgently pls.

I have a MacBook Pro 13.3 OS- MAC OS X LION.
Whenever I am staring the computer, it says You need to restart your computer by pressing the power button.
I did this number of times and everytime it freezes to the same screen.Solution needed urgently pls.
Thank you for any help in this regard that comes fast.

The details of the kernel-panic report is as follows-
Interval Since Last Panic Report: 1458653 sec
Panics Since Last Report:          6
Anonymous UUID:                    70BA6A**************************************************
Sun Sep 16 23:00:13 2012
panic(cpu 0 caller 0xffffff80002c4794): Kernel trap at 0xffffff8000290560, type 14=page fault, registers:
CR0: 0x0000000080010033, CR2: 0x0000000000800028, CR3: 0x000000000a509005, CR4: 0x00000000001606e0
RAX: 0x0000000000000001, RBX: 0x0000000000820000, RCX: 0xffffff801122dc40, RDX: 0x0000000000020501
RSP: 0xffffff80ef3d3da0, RBP: 0xffffff80ef3d3dc0, RSI: 0x000000002b1d78b6, RDI: 0xffffff800342d280
R8: 0xffffff80ef3d3f08, R9: 0xffffff80ef3d3ef8, R10: 0x000000010d901000, R11: 0x0000000000000206
R12: 0xffffff800342d280, R13: 0x0000000000000000, R14: 0xffffff8011cd6500, R15: 0x0000000000800000
RFL: 0x0000000000010206, RIP: 0xffffff8000290560, CS: 0x0000000000000008, SS: 0x0000000000000000
CR2: 0x0000000000800028, Error code: 0x0000000000000000, Faulting CPU: 0x0
Backtrace (CPU 0), Frame : Return Address
0xffffff80ef3d3a50 : 0xffffff8000220792
0xffffff80ef3d3ad0 : 0xffffff80002c4794
0xffffff80ef3d3c80 : 0xffffff80002da55d
0xffffff80ef3d3ca0 : 0xffffff8000290560
0xffffff80ef3d3dc0 : 0xffffff800026c9c3
0xffffff80ef3d3f40 : 0xffffff80002c3fbb
0xffffff80ef3d3fb0 : 0xffffff80002da481
BSD process name corresponding to current thread: fsck_hfs
Mac OS version:
11E2620
Kernel version:
Darwin Kernel Version 11.4.2: Wed May 30 20:13:51 PDT 2012; root:xnu-1699.31.2~1/RELEASE_X86_64
Kernel UUID: 25EC645A-8793-3201-8D0A-23EA280EC755
System model name: MacBookPro9,2 (Mac-6F01561E16C75D06)
System uptime in nanoseconds: 4850001132
last loaded kext at 1796984176: com.apple.driver.BroadcomUSBBluetoothHCIController    4.0.7f2 (addr 0xffffff7f80e16000, size 57344)
loaded kexts:
com.apple.driver.BroadcomUSBBluetoothHCIController    4.0.7f2
com.apple.driver.AppleUSBTCButtons    227.6
com.apple.driver.AppleUSBTCKeyEventDriver    227.6
com.apple.driver.AppleUSBTCKeyboard    227.6
com.apple.driver.AppleIRController    312
com.apple.AppleFSCompression.AppleFSCompressionTypeDataless    1.0.0d1
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib    1.0.0d1
com.apple.BootCache    33
com.apple.iokit.SCSITaskUserClient    3.2.1
com.apple.driver.XsanFilter    404
com.apple.iokit.IOAHCISerialATAPI    2.0.3
com.apple.iokit.IOAHCIBlockStorage    2.0.4
com.apple.driver.AppleFWOHCI    4.8.9
com.apple.driver.AirPort.Brcm4331    560.7.21
com.apple.driver.AppleSDXC    1.2.2
com.apple.driver.AppleUSBHub    5.0.8
com.apple.iokit.AppleBCM5701Ethernet    3.2.4b8
com.apple.driver.AppleEFINVRAM    1.6.1
com.apple.driver.AppleSmartBatteryManager    161.0.0
com.apple.driver.AppleAHCIPort    2.3.0
com.apple.driver.AppleUSBEHCI    5.0.7
com.apple.driver.AppleUSBXHCI    1.0.7
com.apple.driver.AppleACPIButtons    1.5
com.apple.driver.AppleRTC    1.5
com.apple.driver.AppleHPET    1.7
com.apple.driver.AppleSMBIOS    1.9
com.apple.driver.AppleACPIEC    1.5
com.apple.driver.AppleAPIC    1.6
com.apple.driver.AppleIntelCPUPowerManagementClient    195.0.0
com.apple.nke.applicationfirewall    3.2.30
com.apple.security.quarantine    1.3
com.apple.security.TMSafetyNet    8
com.apple.driver.AppleIntelCPUPowerManagement    195.0.0
com.apple.driver.AppleUSBBluetoothHCIController    4.0.7f2
com.apple.iokit.IOBluetoothFamily    4.0.7f2
com.apple.driver.AppleFileSystemDriver    13
com.apple.driver.AppleUSBMultitouch    230.5
com.apple.driver.AppleThunderboltDPInAdapter    1.8.4
com.apple.driver.AppleThunderboltDPAdapterFamily    1.8.4
com.apple.driver.AppleThunderboltPCIDownAdapter    1.2.5
com.apple.iokit.IOUSBHIDDriver    5.0.0
com.apple.driver.AppleUSBMergeNub    5.0.7
com.apple.driver.AppleUSBComposite    5.0.0
com.apple.iokit.IOSCSIMultimediaCommandsDevice    3.2.1
com.apple.iokit.IOBDStorageFamily    1.7
com.apple.iokit.IODVDStorageFamily    1.7.1
com.apple.iokit.IOCDStorageFamily    1.7.1
com.apple.driver.AppleThunderboltNHI    1.6.0
com.apple.iokit.IOThunderboltFamily    2.0.3
com.apple.iokit.IOSCSIArchitectureModelFamily    3.2.1
com.apple.iokit.IOFireWireFamily    4.4.5
com.apple.iokit.IO80211Family    420.3
com.apple.iokit.IOEthernetAVBController    1.0.1b1
com.apple.iokit.IONetworkingFamily    2.1
com.apple.iokit.IOUSBUserClient    5.0.0
com.apple.iokit.IOAHCIFamily    2.0.8
com.apple.iokit.IOUSBFamily    5.0.8
com.apple.driver.AppleEFIRuntime    1.6.1
com.apple.iokit.IOHIDFamily    1.7.1
com.apple.iokit.IOSMBusFamily    1.1
com.apple.security.sandbox    177.5
com.apple.kext.AppleMatch    1.0.0d1
com.apple.driver.DiskImages    331.7
com.apple.iokit.IOStorageFamily    1.7.2
com.apple.driver.AppleKeyStore    28.18
com.apple.driver.AppleACPIPlatform    1.5
com.apple.iokit.IOPCIFamily    2.7
com.apple.iokit.IOACPIFamily    1.4

Global_attribute20 field in ap_payment_schedules_all table - Urgent Pls

All,
Version: 11.5.10.2
I created an invoice, from the 'Scheduled Payments' tab I checked the 'Hold' flag. After the flag is checked in the UI, I noticed the global_attribute20 field in the ap_payment_schedules_all updates to 'EP' along with the hold_flag='Y'. I want to know the significance of global_attribute20 and what are all the other possible values of this field like 'EP'??
this is quite urgent, pls help.
rgds
sen

Have you tried to enable trace on this form to find out how this column gets populated?
FAQ: Common Tracing Techniques within the Oracle Applications 11i/R12 [ID 296559.1] -- 3. How does one enable trace in the Oracle Application screens / forms?
Can you reproduce the issue with other invoices?
Do you have any other instance where you can try the same and see if the issue is reproducible?
Thanks,
Hussein

Routine in Bex - urgent pls.

I have 2 columns A and B in the report:
A     B     C
1234     1234     1234
5903     0     5903
0     3287     3287
I want to get the column C.
So, the condition for the column C would be :
if A<>0 and B <>0 then A
else if A==0 then B
else if B==0 then A
I heared that this can be done by routines . I need the code to do this . Also let me know where to put the code.
This is urgent pls.
Vaishali

Hi,
No need to write coding.....directly u can get these by unsing formula as told in the above forum....there u get all these conditions in Boolean operators. so just make use of them..
Thanks & Regards

Depreciation Posting in AFAB (urgent Pls)

Hi All,
pls let me know y the depreciation posting is not hapenning when it is showing Document created in Test run. It is not showing any errors nor is it posting. urgent pls.
Chatura.

Hi,
Thanks for replying. It did not create any RABUSH Session .
1) I created an Asset and gave the Depreciation Start date as 01.09.07.
2) then i posted an entry in F-90 with transaction type 100, on 01.09.07.
3) The periods are kept open only.
4) The number Ranges for AF Document exists.
5)i did an unplanned posting run for 1 to 8 periods. for 9th period i did the Repeat run . It generated an accounting entry with AF document type.
6) now if i'm trying to do the test run for 10 th period it shows that the Document is created but in the repeat run it is neither posting the document nor is it showing the error.
I was not able to analyse the reason.
Pls help me out. Also pls let me know where to select the direct FI posting in asset accounting. Points will be awarded infull if the issue is solved.
Regards,
Chatura.

I need one recurcive(unended loop) pl/sql example, its very urgent pls

Hi,
I need one recurcive (unended loop) pl/sql example, its very urgent pls
Thanks,
Sathis.

I suppose you'll want to know how to get out of your undended loop too (although that does stop it being unended).
Example...
SQL> ed
Wrote file afiedt.buf
1 DECLARE
2    v_cnt NUMBER := 0;
3 BEGIN
4    LOOP
5      EXIT WHEN v_cnt = 1000;
6      v_cnt := v_cnt + 1;
7    END LOOP;
8* END;
SQL> /
PL/SQL procedure successfully completed.
SQL>

Its urgent pls help me .

how can i call a portal from webdynpro application
my requirment is
i was created webdynpro application.
in that i was created one view . in that i was created one button (go).
if i click that button i want move some other portal.
how can i acchive pls help me.
its urgent.
pls send any example programe
Message was edited by:
madipadiga nagaraju
Message was edited by:
madipadiga nagaraju

hi,
there is no direct tcode for going to webdynpro component/interfaces in ecc 6.0.
but u have se58 in ecc 5.0,as webdynpro convertor.u give ur program name and click web dynpro convertor button then it takes u to se80 .but this wda(webdynpro abap) component comes as in application tree hierarchy .
i can say in wda component refers a class .if u select webdynpro component/interface,it ask u to create a class or interface.
after that it automatically generate component controller(it is also a class),
interface view and windows.all these 3 are classes.for every window one interface view will be created.ie.. window is internal visible where as interface view is external visible.
u create view and embed these views in windows.by going to the window layout,right click on the window name and click embed view.u can enbed as many view as u wish.in order to navigate from one view to other view ,click "create navigation" by right clicking the view plugs.
by default windows and view have inbound plugs.this is literally a event of that class.
if u want to navigate from view1 to view2 ,create outbound plug for view1,the click outbound plug of view1 and right click the click create navigation the select inbound plug of view2.
then create a application .this is simillar of creating an object.
click on this object and test .this will open in browser.
for deploying u have use "sap webdynpro iview".

Telnet connection---urgent pls

each time i try to telnet using my LAPTOP.I get command not recognised.can somebody help me out now.Other PC works except mine.This is very urgent pls.

Download Putty
Search on google " Putty ".... using putty telnet.
You can open Hyperterminal and choose TCP/IP option instead of COM1.
Click on OK
You will telnet into device.
Putty use is very good very secure.
Regards,
Dharmesh Purohit

EXPORT & IMPORT URGENT?

Can anyone help me with the syntax used for export & import memory ID/
I am using a User exit for functionality for COUNTRY KEY.
whne I run my report, I want to export the country key filed value(PARAMETER ID = 'MOL') from my report and IMPORT this value in the user exit..
can you please help me with the syntax wht i need to write?
Its urgent!!!!

Hi Abhay,
define field for export
First program:
data: field type char10.
field = '12345'.
export field to memory id 'TEST'.
In the other program:
data: field type char10.
import field from memory id 'TEST'.
Cheers,
Stefan.

Incremental import / export in oracle -- for a table

Hi all,
I got dump which has data for all the tables for a particular user as below
user= xx
dumps has the following tables
table1
table2
table3.....
Now i want to import on a daily basis, only the new data of table2 into different database db2.
How to do this?
eg. on day1 the table2 has (----when i import the table2 into the different data all the 3 will go(x,y,z))
name age
z 20
y 22
x 20
on day2 the table2 has
name age
z 20
y 22
x 20
a 25
when import here only the record 'a 25' of table2 has to be appended to the other database db2
Thnks and regards
S. Djeanthi

Incremental Imports are no longer supported.
You could use fast refreshable materialized views if you can use a db-link.
Do you know Oracle Streams ?
Just ideas.
But probably you will be stuck with traditional table exports.
Regards
Laurent

IDES ECC 6.0 Installation failed at IMPORT ABAP -- Urgent pls....

Hi Gurus,
ecc6 installation failed at IMPORT ABAP step (to be precise - 16th step out of 19 steps) while importing 'SAPSSEXC' package .....
snippets of following logs are below
1> IMPORT_MONITOR.LOG
2> SAPINST.LOG
3> SAPSSEXC.LOG
<h2>IMPORT_MONITOR.LOG</h2>
ERROR: 2008-01-08 01:32:31 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC' import package is interrupted with R3load error.
Process 'C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSSEXC.cmd -dbcodepage 4103 -l
SAPSSEXC.log -loadprocedure fast' exited with return code -1,073,741,819.
For mode details see 'SAPSSEXC.log' file.
Standard error output:
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
INFO: 2008-01-08 02:42:03 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL2' import package is successfully completed.
WARNING: 2008-01-08 02:42:17
Cannot start import of packages with views because not all import packages with tables are loaded
successfully.
WARNING: 2008-01-08 02:42:17
1 error(s) during processing of packages.
INFO: 2008-01-08 02:42:17
Import Monitor is stopped.
<h2>SAPINST.LOG</h2>
WARNING 2008-01-08 02:42:21
Execution of the command "C:\j2sdk1.4.2_16-x64\bin\java.exe -classpath migmon.jar -showversion
com.sap.inst.migmon.imp.ImportMonitor -dbType MSS -importDirs
F:\ECC6\InstExport1\EXP1;F:\ECC6\InstExport2\EXP2;F:\ECC6\InstExport3\EXP3;F:\ECC6\InstExp4\EXP4;F:
\ECC6\InstExport5\EXP5;F:\ECC6\InstExport6\EXP6;F:\ECC6\InstExport6\EXP7;F:\ECC6\InstExport6\EXP8;F
:\ECC6\InstExport6\EXP9;F:\ECC6\InstExport6\EXP10;F:\ECC6\InstExport6\EXP11 -installDir
C:\PROGRA1\SAPINS1\ERP\SYSTEM\MSS\CENTRAL\AS -orderBy "" -r3loadExe
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -tskFiles yes -extFiles no -dbCodepage 4103 -jobNum 3
-monitorTimeout 30 -loadArgs " -loadprocedure fast" -trace all -sapinst" finished with return code
103. Output:
Loading of 'SAPSSEXC' import package: ERROR
Import Monitor jobs: running 1, waiting 1, completed 16, failed 1, total 19.
Loading of 'SAPAPPL2' import package: OK
Import Monitor jobs: running 0, waiting 1, completed 17, failed 1, total 19.
ERROR 2008-01-08 02:42:23
CJS-30022 Program 'Migration Monitor' exits with error code 103. For details see log file(s)
import_monitor.java.log, import_monitor.log.
ERROR 2008-01-08 02:42:24
FCO-00011 The step runMigrationMonitor with step key
|NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|in
d|ind|10|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigratio
nMonitor was executed with status ERROR .
<h2>SAPSSEXC.LOG</h2>
(DB) INFO: D301T~A created
(DB) INFO: D345T created
(DB) INFO: D345T~0 created
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: import of D345T completed (6585 rows) #20080107180224
(DB) INFO: DSYST created
(DB) INFO: DSYST~0 created
(IMP) INFO: import of DSYST completed (54353 rows) #20080107194721
(DB) INFO: DYNPSOURCE created
(DB) INFO: DYNPSOURCE~0 created
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: import of DYNPSOURCE completed (190478 rows) #20080107205002
(DB) INFO: ENHSPOTCONTRACT~1 created
(DB) INFO: ENHSPOTHEADER created
(DB) INFO: ENHSPOTHEADER~0 created
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: import of ENHSPOTHEADER completed (4078 rows) #20080107205109
(DB) INFO: INDTEXT created
(DB) INFO: INDTEXT~0 created
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(DB) INFO: PERMISSION created
(DB) INFO: PERMISSION~0 created
(IMP) INFO: import of PERMISSION completed (112356 rows) #20080107214109
(DB) INFO: PERMISSION~IF created
(DB) INFO: REPOSRC created
(DB) INFO: REPOSRC~0 created
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
(IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
(IMP) INFO: DBSL will be used
ANY POINTERS WILL BE HIGHLY APPRECIATED
THANKS IN ADVANCE

no...loading was not finished....it aborted with 'Retry', 'View Log', & Stop options...i retried with no luck...
this is 'Central system ' installation btw....
it failed with below error
ERROR 2008-01-08 02:42:23
CJS-30022 Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.
<h2>IMPORT_MONITOR.LOG</h2>
INFO: 2008-01-07 16:33:26
Import Monitor is started.
CONFIG: 2008-01-07 16:33:26
Application options:
dbCodepage=4103
dbType=MSS
extFiles=no
importDirs=F:\ECC6\InstExport1\EXP1;F:\ECC6\InstExport2\EXP2;F:\ECC6\InstExport3\EXP3;F:\ECC6\InstExp4\EXP4;F:\ECC6\InstExport5\EXP5;F:\ECC6\InstExport6\EXP6;F:\ECC6\InstExport6\EXP7;F:\ECC6\InstExport6\EXP8;F:\ECC6\InstExport6\EXP9;F:\ECC6\InstExport6\EXP10;F:\ECC6\InstExport6\EXP11
installDir=C:\PROGRA1\SAPINS1\ERP\SYSTEM\MSS\CENTRAL\AS
jobNum=3
loadArgs= -loadprocedure fast
monitorTimeout=30
orderBy=
r3loadExe=C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe
sapinst=
trace=all
tskFiles=yes
CONFIG: 2008-01-07 16:33:26
List of packages with table structure: 'SAP0000'.
CONFIG: 2008-01-07 16:33:26
List of packages with views: 'SAPVIEW'.
TRACE: 2008-01-07 16:33:26 com.sap.inst.migmon.imp.ImportStandardTask preCreate
Parse of 'C:\PROGRA1\SAPINS1\ERP\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL' template file is started.
INFO: 2008-01-07 16:33:26 com.sap.inst.migmon.imp.ImportStandardTask preCreate
Parse of 'C:\PROGRA1\SAPINS1\ERP\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL' template file is successfully completed.
Primary key creation: before load.
Index creation: after load.
INFO: 2008-01-07 16:33:26
Data codepage 4103 is determined using TOC file 'F:\ECC6\InstExport1\EXP1\DATA\SAPAPPL0.TOC' for package 'SAPAPPL0'.
TRACE: 2008-01-07 16:33:26 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL1' import package is started.
TRACE: 2008-01-07 16:33:26 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC' import package is started.
TRACE: 2008-01-07 16:33:26 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPAPPL1' import package:
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -ctf I F:\ECC6\InstExport1\EXP1\DATA\SAPAPPL1.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPAPPL1.TSK MSS -l SAPAPPL1.log
TRACE: 2008-01-07 16:33:26 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL0' import package is started.
TRACE: 2008-01-07 16:33:26 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPAPPL0' import package:
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -ctf I F:\ECC6\InstExport1\EXP1\DATA\SAPAPPL0.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPAPPL0.TSK MSS -l SAPAPPL0.log
TRACE: 2008-01-07 16:33:26 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPSSEXC' import package:
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -ctf I F:\ECC6\InstExp4\EXP4\DATA\SAPSSEXC.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPSSEXC.TSK MSS -l SAPSSEXC.log
TRACE: 2008-01-07 16:33:28 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPSSEXC' import package into database:
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSSEXC.cmd -dbcodepage 4103 -l SAPSSEXC.log -loadprocedure fast
TRACE: 2008-01-07 16:33:32 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPAPPL1' import package into database:
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -i SAPAPPL1.cmd -dbcodepage 4103 -l SAPAPPL1.log -loadprocedure fast
TRACE: 2008-01-07 16:33:32 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPAPPL0' import package into database:
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -i SAPAPPL0.cmd -dbcodepage 4103 -l SAPAPPL0.log -loadprocedure fast
INFO: 2008-01-08 00:15:00 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL1' import package is successfully completed.
TRACE: 2008-01-08 00:15:18 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL2' import package is started.
TRACE: 2008-01-08 00:15:27 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPAPPL2' import package:
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -ctf I F:\ECC6\InstExp4\EXP4\DATA\SAPAPPL2.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPAPPL2.TSK MSS -l SAPAPPL2.log
INFO: 2008-01-08 00:15:31 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL0' import package is successfully completed.
TRACE: 2008-01-08 00:15:56 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSDIC' import package is started.
TRACE: 2008-01-08 00:15:56 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPSDIC' import package:
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -ctf I F:\ECC6\InstExp4\EXP4\DATA\SAPSDIC.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPSDIC.TSK MSS -l SAPSDIC.log
TRACE: 2008-01-08 00:15:58 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPAPPL2' import package into database:
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -i SAPAPPL2.cmd -dbcodepage 4103 -l SAPAPPL2.log -loadprocedure fast
TRACE: 2008-01-08 00:16:02 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPSDIC' import package into database:
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSDIC.cmd -dbcodepage 4103 -l SAPSDIC.log -loadprocedure fast
INFO: 2008-01-08 00:49:00 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSDIC' import package is successfully completed.
TRACE: 2008-01-08 00:49:18 com.sap.inst.migmon.LoadTask run
Loading of 'SAPCLUST' import package is started.
TRACE: 2008-01-08 00:49:40 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPCLUST' import package:
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -ctf I F:\ECC6\InstExp4\EXP4\DATA\SAPCLUST.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPCLUST.TSK MSS -l SAPCLUST.log
TRACE: 2008-01-08 00:50:11 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPCLUST' import package into database:
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -i SAPCLUST.cmd -dbcodepage 4103 -l SAPCLUST.log -loadprocedure fast
INFO: 2008-01-08 00:53:51 com.sap.inst.migmon.LoadTask run
Loading of 'SAPCLUST' import package is successfully completed.
TRACE: 2008-01-08 00:54:21 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSLEXC' import package is started.
TRACE: 2008-01-08 00:54:40 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPSLEXC' import package:
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -ctf I F:\ECC6\InstExport3\EXP3\DATA\SAPSLEXC.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPSLEXC.TSK MSS -l SAPSLEXC.log
TRACE: 2008-01-08 00:54:48 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPSLEXC' import package into database:
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSLEXC.cmd -dbcodepage 4103 -l SAPSLEXC.log -loadprocedure fast
INFO: 2008-01-08 01:02:26 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSLEXC' import package is successfully completed.
TRACE: 2008-01-08 01:02:45 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSRC' import package is started.
TRACE: 2008-01-08 01:02:50 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPSSRC' import package:
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -ctf I F:\ECC6\InstExport5\EXP5\DATA\SAPSSRC.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPSSRC.TSK MSS -l SAPSSRC.log
TRACE: 2008-01-08 01:03:11 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPSSRC' import package into database:
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSSRC.cmd -dbcodepage 4103 -l SAPSSRC.log -loadprocedure fast
INFO: 2008-01-08 01:09:19 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSRC' import package is successfully completed.
TRACE: 2008-01-08 01:09:46 com.sap.inst.migmon.LoadTask run
Loading of 'SAPPOOL' import package is started.
TRACE: 2008-01-08 01:09:51 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPPOOL' import package:
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -ctf I F:\ECC6\InstExport1\EXP1\DATA\SAPPOOL.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPPOOL.TSK MSS -l SAPPOOL.log
TRACE: 2008-01-08 01:09:55 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPPOOL' import package into database:
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -i SAPPOOL.cmd -dbcodepage 4103 -l SAPPOOL.log -loadprocedure fast
INFO: 2008-01-08 01:14:03 com.sap.inst.migmon.LoadTask run
Loading of 'SAPPOOL' import package is successfully completed.
TRACE: 2008-01-08 01:14:17 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSDOCU' import package is started.
TRACE: 2008-01-08 01:14:18 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPSDOCU' import package:
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -ctf I F:\ECC6\InstExport1\EXP1\DATA\SAPSDOCU.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPSDOCU.TSK MSS -l SAPSDOCU.log
TRACE: 2008-01-08 01:14:21 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPSDOCU' import package into database:
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSDOCU.cmd -dbcodepage 4103 -l SAPSDOCU.log -loadprocedure fast
INFO: 2008-01-08 01:15:50 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSDOCU' import package is successfully completed.
TRACE: 2008-01-08 01:16:18 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSPROT' import package is started.
TRACE: 2008-01-08 01:16:19 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPSPROT' import package:
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -ctf I F:\ECC6\InstExport1\EXP1\DATA\SAPSPROT.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPSPROT.TSK MSS -l SAPSPROT.log
TRACE: 2008-01-08 01:16:24 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPSPROT' import package into database:
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSPROT.cmd -dbcodepage 4103 -l SAPSPROT.log -loadprocedure fast
INFO: 2008-01-08 01:17:55 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSPROT' import package is successfully completed.
TRACE: 2008-01-08 01:18:18 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSLOAD' import package is started.
TRACE: 2008-01-08 01:18:24 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPSLOAD' import package:
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -ctf I F:\ECC6\InstExport1\EXP1\DATA\SAPSLOAD.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPSLOAD.TSK MSS -l SAPSLOAD.log
TRACE: 2008-01-08 01:18:31 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPSLOAD' import package into database:
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSLOAD.cmd -dbcodepage 4103 -l SAPSLOAD.log -loadprocedure fast
INFO: 2008-01-08 01:18:43 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSLOAD' import package is successfully completed.
TRACE: 2008-01-08 01:18:46 com.sap.inst.migmon.LoadTask run
Loading of 'SAPUSER' import package is started.
TRACE: 2008-01-08 01:18:48 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPUSER' import package:
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -ctf I F:\ECC6\InstExport5\EXP5\DATA\SAPUSER.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPUSER.TSK MSS -l SAPUSER.log
TRACE: 2008-01-08 01:18:50 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPUSER' import package into database:
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -i SAPUSER.cmd -dbcodepage 4103 -l SAPUSER.log -loadprocedure fast
INFO: 2008-01-08 01:20:09 com.sap.inst.migmon.LoadTask run
Loading of 'SAPUSER' import package is successfully completed.
TRACE: 2008-01-08 01:20:15 com.sap.inst.migmon.LoadTask run
Loading of 'SAPDDIM' import package is started.
TRACE: 2008-01-08 01:20:16 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPDDIM' import package:
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -ctf I F:\ECC6\InstExport1\EXP1\DATA\SAPDDIM.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPDDIM.TSK MSS -l SAPDDIM.log
TRACE: 2008-01-08 01:20:16 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPDDIM' import package into database:
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -i SAPDDIM.cmd -dbcodepage 4103 -l SAPDDIM.log -loadprocedure fast
INFO: 2008-01-08 01:20:26 com.sap.inst.migmon.LoadTask run
Loading of 'SAPDDIM' import package is successfully completed.
TRACE: 2008-01-08 01:20:45 com.sap.inst.migmon.LoadTask run
Loading of 'SAPDFACT' import package is started.
TRACE: 2008-01-08 01:20:45 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPDFACT' import package:
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -ctf I F:\ECC6\InstExport1\EXP1\DATA\SAPDFACT.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPDFACT.TSK MSS -l SAPDFACT.log
TRACE: 2008-01-08 01:20:46 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPDFACT' import package into database:
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -i SAPDFACT.cmd -dbcodepage 4103 -l SAPDFACT.log -loadprocedure fast
INFO: 2008-01-08 01:20:51 com.sap.inst.migmon.LoadTask run
Loading of 'SAPDFACT' import package is successfully completed.
TRACE: 2008-01-08 01:21:17 com.sap.inst.migmon.LoadTask run
Loading of 'SAPDODS' import package is started.
TRACE: 2008-01-08 01:21:22 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPDODS' import package:
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -ctf I F:\ECC6\InstExport1\EXP1\DATA\SAPDODS.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPDODS.TSK MSS -l SAPDODS.log
TRACE: 2008-01-08 01:21:23 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPDODS' import package into database:
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -i SAPDODS.cmd -dbcodepage 4103 -l SAPDODS.log -loadprocedure fast
INFO: 2008-01-08 01:21:25 com.sap.inst.migmon.LoadTask run
Loading of 'SAPDODS' import package is successfully completed.
TRACE: 2008-01-08 01:21:45 com.sap.inst.migmon.LoadTask run
Loading of 'SAPUSER1' import package is started.
TRACE: 2008-01-08 01:21:47 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPUSER1' import package:
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -ctf I F:\ECC6\InstExport5\EXP5\DATA\SAPUSER1.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPUSER1.TSK MSS -l SAPUSER1.log
TRACE: 2008-01-08 01:21:52 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPUSER1' import package into database:
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -i SAPUSER1.cmd -dbcodepage 4103 -l SAPUSER1.log -loadprocedure fast
INFO: 2008-01-08 01:21:53 com.sap.inst.migmon.LoadTask run
Loading of 'SAPUSER1' import package is successfully completed.
TRACE: 2008-01-08 01:22:16 com.sap.inst.migmon.LoadTask run
Loading of 'SAP0000' import package is started.
TRACE: 2008-01-08 01:22:16 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAP0000' import package:
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -ctf I F:\ECC6\InstExport1\EXP1\DATA\SAP0000.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAP0000.TSK MSS -l SAP0000.log -o D
TRACE: 2008-01-08 01:22:16 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAP0000' import package into database:
C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -i SAP0000.cmd -dbcodepage 4103 -l SAP0000.log -loadprocedure fast
INFO: 2008-01-08 01:22:17 com.sap.inst.migmon.LoadTask run
Loading of 'SAP0000' import package is successfully completed.
ERROR: 2008-01-08 01:32:31 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC' import package is interrupted with R3load error.
Process 'C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSSEXC.cmd -dbcodepage 4103 -l SAPSSEXC.log -loadprocedure fast' exited with return code -1,073,741,819.
For mode details see 'SAPSSEXC.log' file.
Standard error output:
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
INFO: 2008-01-08 02:42:03 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL2' import package is successfully completed.
WARNING: 2008-01-08 02:42:17
Cannot start import of packages with views because not all import packages with tables are loaded successfully.
WARNING: 2008-01-08 02:42:17
1 error(s) during processing of packages.
INFO: 2008-01-08 02:42:17
Import Monitor is stopped.

How to do incremental import via dump...

i have the table inf_products_dim.
as one time load i used .dmp option (ie export/import).
from now onwards, shall we do incremental dump ie export/import?
ex: on 20-aug-2009 we dumped using (imp/exp) 1200 records into inf_products_dim (this is as part of initial load)
now on 26-aug-2009 we need to load 6 days of data into inf_products_dim. ie (incremental which will have updated/new records based on inventory_item_id)
shall we export that 6 days of data and import (MERGE) into inf_products_dim using .dmp file?

Import will not be doing a merge. If you wanted to use export (classic or DataPump), you would have to specify a WHERE clause as a parameter to the export, import the data into a separate staging table, and write your own MERGE logic. Definitely possible, but less than ideal.
Using LAST_UPDATE_DATE like this also has the potential for problems if there is any possibility of ever having transactions that run for more than a few seconds in the OLTP system (including data clean-up/ migration transactions) or if there is ever any potential that code bugs will fail to increment LAST_UPDATE_DATE. In the former case, LAST_UPDATE_DATE could be a few seconds or minutes before the time that the transaction was actually committed and thus visible to the export process. Making sure that you don't miss an update in that scenario is tough and requires setting an absolute limit on the length of a transaction which tends to be difficult to do.
I would strongly prefer using an actual replication technology. Streams, Change Data Capture (CDC), even materialized views provide much more robust ways to track changes to rows and replicate the changes to the destination.
Justin

Incremental Import/Export..Import & urgent Pls.

Similar Messages

Maybe you are looking for