SAP installation-CJS-30022 FCO-00011 The step run
时间：2010-05-27 来源：wusj521
WARNING 2010-05-06 20:19:34.562
Execution of the command "C:\j2sdk1.4.2_17-x64\bin\java.exe -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -sapinst" finished with return code 103. Output:
java version "1.4.2_17"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_17-b06)
Java HotSpot(TM) 64-Bit Server VM (build 1.4.2_17-b06, mixed mode)
Import Monitor jobs: running 1, waiting 1, completed 110, failed 0, total 112.
Loading of 'TMENU01T' import package: ERROR
Import Monitor jobs: running 0, waiting 1, completed 110, failed 1, total 112.
ERROR 2010-05-06 20:19:34.578
CJS-30022 Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.
ERROR 2010-05-06 20:19:34.671
FCO-00011 The step runMigrationMonitor with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|2|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigrationMonitor was executed with status ERROR ( Last error reported by the step :Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.).
TMENU01T.log
H:\usr\sap\IDS\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20100506200822
H:\usr\sap\IDS\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#14 $ SAP
H:\usr\sap\IDS\SYS\exe\uc\NTAMD64\R3load.exe: version R7.00/V1.4 [UNICODE]
Compiled Jan 24 2008 01:41:44
H:\usr\sap\IDS\SYS\exe\uc\NTAMD64\R3load.exe -i TMENU01T.cmd -dbcodepage 4103 -l TMENU01T.log -stop_on_error
DbSl Trace: OCI-call 'OCISessionBegin' failed with rc=1034
DbSl Trace: CONNECT failed with sql error '1034'
DbSl Trace: OCI-call 'OCISessionBegin' failed with rc=1034
DbSl Trace: CONNECT failed with sql error '1034'
(DB) ERROR: db_connect rc = 256
DbSl Trace: OCI-call 'OCISessionBegin' failed with rc=1034
DbSl Trace: CONNECT failed with sql error '1034'
DbSl Trace: OCI-call 'OCISessionBegin' failed with rc=1034
DbSl Trace: CONNECT failed with sql error '1034'
(DB) ERROR: DbSlErrorMsg rc = 99
H:\usr\sap\IDS\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 1 error(s)
H:\usr\sap\IDS\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20100506200822
解决办法：
原因是oracle的共享池内存太小问题，设置如下参数。因为在SAP SR3这个版本中有些表比较大，所以在导入IMPORT ABAP 时要求有够大的共享内存。阅如下内容：
X:\oracle\<SID>\102\database\ init<SID>.ora
shared_pool_size = 734003200
shared_pool_reserved_size = 104857600
sga_max_size = 734003200
db_cache_size = 524288000
X:\oracle\<SID>\102\srvm\admin \init.ora （sid是在安DB时输入的SID）
shared_pool_size = 1073741824
如果还有问题，通过命令行进入SQLPLUS 启动数据库。
C:>sqlplus /nolog
SQL>conn sys/[email protected] as sysdba (dev是在安装时输入的SID)
SQL>startup
SQL> shutdown immediate;
SQL> startup
加大C：盘的虚拟内存，重启win系统，执行以上ORACLE启动操作
说明：中间又出现同样的问题，检查是因为文件“SAPSSEXC_4.TSK.bck”未被删除。如果
出现其他文件可以查看相关的日志查找原因。
IMPORT ABAP 提示错误：CJS-30022 error followed by FCO-00011
图1
CJS-30022 Program 'Migration Monitor' exits with error code 103. ... FCO-00011 The step runMigrationMonitor with step key ... 切记: TSK 文件只允许改最后的'ok' / 'error' 到'xeq', 其它什么也不要动
转载：http://www.iam168.com/blog/space.php?uid=1&do=blog&id=5
Execution of the command "C:\j2sdk1.4.2_17-x64\bin\java.exe -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -sapinst" finished with return code 103. Output:
java version "1.4.2_17"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_17-b06)
Java HotSpot(TM) 64-Bit Server VM (build 1.4.2_17-b06, mixed mode)
Import Monitor jobs: running 1, waiting 1, completed 110, failed 0, total 112.
Loading of 'TMENU01T' import package: ERROR
Import Monitor jobs: running 0, waiting 1, completed 110, failed 1, total 112.
ERROR 2010-05-06 20:19:34.578
CJS-30022 Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.
ERROR 2010-05-06 20:19:34.671
FCO-00011 The step runMigrationMonitor with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|2|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigrationMonitor was executed with status ERROR ( Last error reported by the step :Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.).
TMENU01T.log
H:\usr\sap\IDS\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20100506200822
H:\usr\sap\IDS\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#14 $ SAP
H:\usr\sap\IDS\SYS\exe\uc\NTAMD64\R3load.exe: version R7.00/V1.4 [UNICODE]
Compiled Jan 24 2008 01:41:44
H:\usr\sap\IDS\SYS\exe\uc\NTAMD64\R3load.exe -i TMENU01T.cmd -dbcodepage 4103 -l TMENU01T.log -stop_on_error
DbSl Trace: OCI-call 'OCISessionBegin' failed with rc=1034
DbSl Trace: CONNECT failed with sql error '1034'
DbSl Trace: OCI-call 'OCISessionBegin' failed with rc=1034
DbSl Trace: CONNECT failed with sql error '1034'
(DB) ERROR: db_connect rc = 256
DbSl Trace: OCI-call 'OCISessionBegin' failed with rc=1034
DbSl Trace: CONNECT failed with sql error '1034'
DbSl Trace: OCI-call 'OCISessionBegin' failed with rc=1034
DbSl Trace: CONNECT failed with sql error '1034'
(DB) ERROR: DbSlErrorMsg rc = 99
H:\usr\sap\IDS\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 1 error(s)
H:\usr\sap\IDS\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20100506200822
解决办法：
原因是oracle的共享池内存太小问题，设置如下参数。因为在SAP SR3这个版本中有些表比较大，所以在导入IMPORT ABAP 时要求有够大的共享内存。阅如下内容：
X:\oracle\<SID>\102\database\ init<SID>.ora
shared_pool_size = 734003200
shared_pool_reserved_size = 104857600
sga_max_size = 734003200
db_cache_size = 524288000
X:\oracle\<SID>\102\srvm\admin \init.ora （sid是在安DB时输入的SID）
shared_pool_size = 1073741824
如果还有问题，通过命令行进入SQLPLUS 启动数据库。
C:>sqlplus /nolog
SQL>conn sys/[email protected] as sysdba (dev是在安装时输入的SID)
SQL>startup
SQL> shutdown immediate;
SQL> startup
加大C：盘的虚拟内存，重启win系统，执行以上ORACLE启动操作
说明：中间又出现同样的问题，检查是因为文件“SAPSSEXC_4.TSK.bck”未被删除。如果
出现其他文件可以查看相关的日志查找原因。
IMPORT ABAP 提示错误：CJS-30022 error followed by FCO-00011
图1
CJS-30022 Program 'Migration Monitor' exits with error code 103. ... FCO-00011 The step runMigrationMonitor with step key ... 切记: TSK 文件只允许改最后的'ok' / 'error' 到'xeq', 其它什么也不要动
转载：http://www.iam168.com/blog/space.php?uid=1&do=blog&id=5
相关阅读 更多 +
