DOYENSYS Knowledge Portal




We Welcome you to visit our DOYENSYS KNOWLEDGE PORTAL : Doyensys Knowledge Portal




Wednesday, September 28, 2016

OATM Migration Not Completed 100% Errors With: Io exception: invalid arguments in call



  OATM Migration Not Completed 100% Errors With: Io exception: invalid arguments in call


The issue can be reproduced at will with the following steps:
1. Run the OATM migration.

CAUSE:
The fndtsmig.pl had too many threads as the thread count was set to 10.

SOLUTION:
1. Modify fndtsmig.pl and reduce number of threads from 10 to 1.
The following is an example:
Old setting:
my $ret = system("($cmd_exe $javacmd classpath
$CLASSPATH
oracle.apps.fnd.tsmig.TSMigration % SYSTEM $SYSTEM_PWD $\@jdbcStrings[0] $logfile

$PARA_CONF{APPLSYS_SCHEMA} 10 > $LOG_DIR/temp.log) &");

New setting:
my $ret = system("($cmd_exe $javacmd classpath
$CLASSPATH
oracle.apps.fnd.tsmig.TSMigration % SYSTEM $SYSTEM_PWD $\@jdbcStrings[0] $logfile
$PARA_CONF{APPLSYS_SCHEMA} 1 > $LOG_DIR/temp.log) &");


2. Ensure there are no Application tier processes running. Please run the adstpall.sh script and ensure all services have been shut down.


3. Restart the database and retry the OATM migration process as follows:
a. Verify that the OATM migration is stopped:
ps ef| grep fndtsmig
b. Stop the Queue:
exec dbms_aqadm.stop_queue('SYSTEM.TBLMIG_MESSAGEQUE');
c. Bounce the database and then restart the Queue:
exec dbms_aqadm.start_queue('SYSTEM.TBLMIG_MESSAGEQUE');

d. Start the OATM Migration one more time:

perl fndtsmig.pl
Check for error and monitor the progress.

d. Execute the steps above (a to d) several times. Migration should complete successfully.

No comments: