Data Migration Service.

Hi,


I faced a bizzard problem while runnig the migartion service using the DM tool. My flat file has a around 2 lakh records, when I ran the DM service agent, the service processed only 1 lakh records and left behind the rest of the records. There was no error log for the rest of the records. I copied the remaining records to a new file and ran the service again pointing to the new file. The service ran successfully uploading the remaining records.

Did any one came across this problem, are there any limit in selecting the records??

Thanks in advance

Pradeep

hi , Pradeep , for which Module (appliction) you are uploading the Data ???

I have faced this problem earlier with the tool.
We can instead upload four files containing 50000 records each.

@madhu

I am uploading for a locally developed application.

@bora

Did u face the problem while uploading core tables or locally developed application

Also while uploading bukk amount of records my service hangs at first... it hangs while executeing the DM.SRVICE routine. I will stop the service and restart again, after which it will continue to run normally.

At the instant when the service gets hanged i checked with job list file. It has reord with id 1 and has value "SingleThread" in it.

Any idea on this??

This can happen for many reasons including any issues with the local application.

Try checking the COMO and you may be able to find the exact reason.

Also, if it is a local application why are you not developing your own migration logic instead of going through OFS?

Shanthi

Shanti,

Finally am going to replace process with a service routine only. I checked with COMO record too, i found the following select command after the DM.SERVICE.PRE.PROCESS is over....

SELECT F.JOB.LIST.10 SAMPLE 100000.. will this select command have influence in data migration service processing limited records?? I hope its not so...
this select command happens in DM.SERVICE job

Pradeep,

After Pre Process is completed, the respective job list has to have the total number of records that you wanted to process.

The Service job itself, selects the Job list file and deletes the records in this file after processing them.

So at the end of your migration, the job list file should be empty otherwise you need to restart the Service Job.

Regards,
Shanthi

ultimately the problem should be because of the pre process routine only.... not with the DM.SERVICE routine right??

What does LIST-ITEM F.DM.SERVICE.DATA.FILE and COUNT F.DM.SERVICE.DATA.FILE show ??

I have faced the problem at times.
But never tried to dig into it. What is did is

CLEAR.FILE F.DM.SERVICE.DATA.FILE
CLEAR.FILE DM.OFS.LOGS
CLEAR.FILE F.OFS.REQUEST.DETAIL
CLEAR.FILE F.JOB.LIST.1
CLEAR.FILE F.JOB.LIST.2
CLEAR.FILE F.JOB.LIST.3
....

opened a new session and ... it worked.

hi barua

I havent tried clearing the F.DM.SERVICE.DATA file and the ofs log file... i will try doing that...

will do that when the service hangs....

any idea on pre process routine selecting records from the flat file

Service Hangs:
1. if Validatiion it can be restarted again.

2. If Upload we have a problem here mostly if we are defining the ID's as auto.

- I have faced the problem due to Locking ( used SHOW-ITEM-LOCKS , MW42 ) and find out the root cause.