I am not sure how to finish OATM migration utility in timely manner. I can't afford days of downtime to do OATM migration. Is there any advise on doing this migration? I am running this utility right now and it is doing 2% a day. I am still waiting @ 4% done satge. Not sure how long will it take to finish?
Edited by: user10751491 on Jun 26, 2012 9:10 AM
Please post the details of the application release, database version and OS along with the hardware resources you have on the database server.
What is the procedure you follow to migrate to OATM?
Are you trying this in a test instance?
Have you reviewed all OATM docs? -- https://forums.oracle.com/forums/search.jspa?threadID=&q=OATM&objID=c3&dateRange=all&userID=&numResults=15&rankBy=10001
My OATM Migration Appears to Have Hung. How Can I Monitor It's Progress? [ID 1073783.1]
Oatm Conversion Is Hanging While Generating Migration Command [ID 445020.1]
Oatm Migration Is Running Very Long On Fnd_lobs_ctx Index For More Than 35hrs, How to speed Up This OATM Migration Step? [ID 1362261.1]
Thanks for quick response. Following is required info:
Application Release - 22.214.171.124
Database - 126.96.36.199
OS - Oracle Solaris SPARC 64 Bit
Hardware - 4 CPU and 16GB RAM
Yes. I am running this in test environment. I am using perl script (perl $FND_TOP/bin/fndtsmig.pl) to run this utility.
I will go over other notes you have mentioned but I can see it is running but with its own pace.
Actually I just noticed that it is not moving any further since last 4 hours. I am really confused as it is automated utility and I can't do anything about it. Can you tell me how to see what object it is working on?
I am following same document for migration. I am sort of stuck with this process. Though I have selected 10 parallel process but I don't see any log file moving.. I am really not sure what am I doing wrong?
Sorry for late response but due to time constraint I had to scarp OATM project as of now but I will continue it after a month so if I need any help at that time then I will open another case. Once again Thanks a lot for your help.
If you are still needing to work on this...
Are you getting ready to upgrade to R12? If so, complete the upgrade first and then apply the the appropriate TXK patch containing JDBC drivers for your instance and start your migration again. I am guessing that you were having numberous "Protocol Violation" errors in the log files, right?