Error in import ABAP while installing ECC6.0 on I5/os

Hi All,
I am installaing ECC 6.0 SR3 on i5. I failed first time in ABAP with 3 jobs. Than i restarted the installation and than SAPVIEW failed and all the rest 27 completed. As per the log several tables are missing in the database which should be there already. As for example TVRO is not there which should be created while importing SAPAPPL2.
I am planning to start the installation from scratch. Did any one of you faced this issue earlier or waht could be the reason behind that. I have copied all the DVD's file again on 15 server.
Thanks in advance..
Thanks,
Bhanu

Hi Bhanu,
I had NEVER had that !
Before I would start with a new installation, I would definetely would check the log files of sapappl2 or wherever it is what happened here - otherwise, it will be the same issue I would guess.
This is totally crazy - have never had, that r3load returns ok, when it "forgot" some tables ... did you check the tasks files ? did you have issue there during restart ? perhaps deleted the ".bck" files (strongly forbidden!) ?
Regards
Volker Gueldenpfennig, consolut international ag
http://www.consolut.net - http://www.4soi.de - http://www.easymarketplace.de

Similar Messages

Urgent: Error while installing ECC6.0

Hi guys,
iam getting the following error while installing ecc6.0 at importing abap stage.
ERROR 2007-10-25 23:28:45
CJS-30022 Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.
ERROR 2007-10-25 23:28:45
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|ind|ind|9|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 .
outof 59, 8 jobs failed. if u want i can post the log file.
thanks,
sandeep.

Hi guys,
i got rid of the problem,
when i want to login as sysdba in cmd, it says oracle error 01034
then tried these steps
set ORACLE_SID=XXX
sqlplus /nolog
conn system/manager as sysdba
shutdown abort
startup
then i tried to reinstall , it worked.
thanks
sandeep.

While installing ECC6.0 SR3 FOR LINUX an error occured

Hi all,
While installing ECC6.0 SR3 FOR LINUX an error occured. Error Details:
ERROR 2008-10-12 20:38:59.866
FCO-00011 The step createSecureStore 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_SecureStore|ind|ind|ind|ind|8|0|createSecureStore was executed with status ERROR .

WARNING 2008-10-13 18:17:26.006
Execution of the command "/opt/IBMJava2-amd64-142/bin/java -classpath /tmp/sapinst_instdir/ERP/SYSTEM/DB6/CENTRAL/AS/install/sharedlib/launcher.jar -Xmx256m com.sap.engine.offline.OfflineToolStart com.sap.security.core.server.secstorefs.SecStoreFS /tmp/sapinst_instdir/ERP/SYSTEM/DB6/CENTRAL/AS/install/lib:/tmp/sapinst_instdir/ERP/SYSTEM/DB6/CENTRAL/AS/install/sharedlib/exception.jar:/tmp/sapinst_instdir/ERP/SYSTEM/DB6/CENTRAL/AS/install/sharedlib/logging.jar:/tmp/sapinst_instdir/ERP/SYSTEM/DB6/CENTRAL/AS/install/sharedlib/tc_sec_secstorefs.jar create -s C31 -f /sapmnt/C31/global/security/data/SecStore.properties -k /sapmnt/C31/global/security/data/SecStore.key -enc -p XXXXXX" finished with return code 1. Output:
The java class is not found: com.sap.engine.offline.OfflineToolStart
ERROR 2008-10-13 18:17:26.011
CJS-30050 Cannot create the secure store. SOLUTION: See output of log file SecureStoreCreate.log:
The java class is not found: com.sap.engine.offline.OfflineToolStart.
ERROR 2008-10-13 18:17:26.235
FCO-00011 The step createSecureStore 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_SecureStore|ind|ind|ind|ind|8|0|createSecureStore was executed with status ERROR ( Last error reported by the step :Cannot create the secure store. SOLUTION: See output of log file SecureStoreCreate.log:
The java class is not found: com.sap.engine.offline.OfflineToolStart.).

Error on import abap phase(ecc6.0 on db2)

Hi,
Iam getting error on import abap phase : the transaction log for database is full. SQLSTATE=57011.
my log dirs are available space.guide me for same to resolve the issue.
Thanku

Hi,
I assume that
Path to log files
should read "\db2\GMI\logdir\NODE0000" ?
If yes, this is ok.
To increase the size of logspace available to the database you have to modify the parameters LOGPRIMARY and/or LOGSECOND and/or LOGFILSIZ.
The overall space consumed in "db2\GMI\logdir\NODE0000" is detemined by:
(logprimary + logsecond) * (logfilsiz + 2 ) * 4096
Assuming that there is enough free space in the above directory, you could in a first step double the amount of LOGPRIMARY and LOGFILSIZ thus increasing the available logspace by factor 4.
Please be aware: To make these changes happen, you have to deactivate / reactivate your database.

Error in Import ABAP phase on slution manager - R3load-testconnect

Hi all,
I am installing solman and got error in Import ABAP phase
here is the log
WARNING 2010-05-20 08:13:27.982 Execution of the command "/usr/sap/SM7/SYS/exe/run/R3load -testconnect" finished with return code 127. Output: /usr/sap/SM7/SYS/exe/run/R3load: error while loading shared libraries: /oracle/client/10x_64/instantclient/libnnz10.so: cannot restore segment prot after reloc: Permission denied
> R3trans -d
This is R3trans version 6.14 (release 700 - 14.02.08 - 14:55:00).
unicode enabled version
2EETW169 no connect possible: "maybe someone set invalid values for DIR_LIBRARY ('/usr/sap/SM7/SYS/exe/run') or dbms_type ('ORA')"
R3trans finished (0012).
SQL> startup;
ORACLE instance started.
Total System Global Area 4613734400 bytes
Fixed Size                  2090048 bytes
Variable Size            2315258816 bytes
Database Buffers         2281701376 bytes
Redo Buffers               14684160 bytes
Database mounted.
ORA-01092: ORACLE instance terminated. Disconnection forced
Please advice
Regards
Palle
Edited by: palle26 on May 20, 2010 11:00 AM

hi
    After insattaling oracle, i didn't apply oracle patch.
when it throwed error , r3load-testconnect, then i stoped listener & applied patch and continued with the installation .
DB is not getting started. when i used > startup;
ORACLE instance started.
Total System Global Area 4613734400 bytes
Fixed Size                  2090048 bytes
Variable Size            2315258816 bytes
Database Buffers         2281701376 bytes
Redo Buffers               14684160 bytes
Database mounted.
ORA-01092: ORACLE instance terminated. Disconnection forced
R3trans -d
This is R3trans version 6.14 (release 700 - 14.02.08 - 14:55:00).
unicode enabled version
2EETW169 no connect possible: "DBMS = ORACLE                           --- dbs_ora_tnsname = 'SM7'"
R3trans finished (0012).
SQL> select status from v$instance;
ERROR:
ORA-03114: not connected to ORACLE
one of the blog said to restart the server. i did it but now if i say hotname
it is giving full domain name as sap-server.lgcnsglobal.com instead of sap-server
Do i need to uninstall oracle and do it again , if so how do i uninstall oracle?
regards
sandhya

I am getting the following error at Import ABAP phase ...

Dear All,
I am getting the following error at Import ABAP phase when performing the system copy function (Import) via ./sapinst ( OS - LINUX and DATABASE-ORACLE 10g)...
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
/usr/sap/RXT/SYS/exe/run/R3load: START OF LOG: 20090102154030
/usr/sap/RXT/SYS/exe/run/R3load: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#6 $ SAP
/usr/sap/RXT/SYS/exe/run/R3load: version R7.00/V1.4 [UNICODE]
Compiled Apr 1 2006 00:08:29
/usr/sap/RXT/SYS/exe/run/R3load -testconnect
DbSl Trace: OCI-call 'OCIServerAttach' failed: rc = 12541
DbSl Trace: CONNECT failed with sql error '12541'
DbSl Trace: OCI-call 'OCIServerAttach' failed: rc = 12541
DbSl Trace: CONNECT failed with sql error '12541'
(DB) ERROR: db_connect rc = 256
DbSl Trace: OCI-call 'OCIServerAttach' failed: rc = 12541
DbSl Trace: CONNECT failed with sql error '12541'
DbSl Trace: OCI-call 'OCIServerAttach' failed: rc = 12541
DbSl Trace: CONNECT failed with sql error '12541'
(DB) ERROR: DbSlErrorMsg rc = 99
/usr/sap/RXT/SYS/exe/run/R3load: job finished with 1 error(s)
/usr/sap/RXT/SYS/exe/run/R3load: END OF LOG: 20090102154030
Thanx,
Amit

Dear Juan,
Trans.log is ;
isrxi:rxtadm 7> cat trans.log
4 ETW000 R3trans version 6.13 (release 700 - 20.02.06 - 16:15:00).
4 ETW000 unicode enabled version
4 ETW000 ===============================================
4 ETW000
4 ETW000 date&time   : 02.01.2009 - 16:45:09
4 ETW000 control file: <no ctrlfile>
4 ETW000 R3trans was called as follows: R3trans -d
4 ETW000 trace at level 2 opened for a given file pointer
4 ETW000 [dev trc     ,00000] Fri Jan 2 16:45:09 2009                              62 0.000062
4 ETW000 [dev trc     ,00000] db_con_init called                                    13 0.000075
4 ETW000 [dev trc     ,00000] create_con (con_name=R/3)                             21 0.000096
4 ETW000 [dev trc     ,00000] Loading DB library '/usr/sap/RXT/SYS/exe/run/dboraslib.so' ...
4 ETW000                                                                              26 0.000122
4 ETW000 [dev trc     ,00000] load shared library (/usr/sap/RXT/SYS/exe/run/dboraslib.so), hdl 0
4 ETW000                                                                            9099 0.009221
4 ETW000 [dev trc     ,00000] Library '/usr/sap/RXT/SYS/exe/run/dboraslib.so' loaded
4 ETW000                                                                              16 0.009237
4 ETW000 [dev trc     ,00000] function DbSlExpFuns loaded from library /usr/sap/RXT/SYS/exe/run/dboraslib.so
4 ETW000                                                                              30 0.009267
4 ETW000 [dev trc     ,00000] Version of '/usr/sap/RXT/SYS/exe/run/dboraslib.so' is "700.08", patchlevel (0.46)
4 ETW000                                                                              42 0.009309
4 ETW000 [dev trc     ,00000] function dsql_db_init loaded from library /usr/sap/RXT/SYS/exe/run/dboraslib.so
4 ETW000                                                                              21 0.009330
4 ETW000 [dev trc     ,00000] function dbdd_exp_funs loaded from library /usr/sap/RXT/SYS/exe/run/dboraslib.so
4 ETW000                                                                              25 0.009355
4 ETW000 [dev trc     ,00000] New connection 0 created                              16 0.009371
4 ETW000 [dev trc     ,00000] 0: name = R/3, con_id = -000000001 state = DISCONNECTED, perm = YES, reco = NO , timeout = 000, con_max = 255, con_opt = 255, occ = NO
4 ETW000                                                                              21 0.009392
4 ETW000 [dev trc     ,00000] db_con_connect (con_name=R/3)                         17 0.009409
4 ETW000 [dev trc     ,00000] find_con_by_name found the following connection for reuse:
4 ETW000                                                                              15 0.009424
4 ETW000 [dev trc     ,00000] 0: name = R/3, con_id = 000000000 state = DISCONNECTED, perm = YES, reco = NO , timeout = 000, con_max = 255, con_opt = 255, occ = NO
4 ETW000                                                                              16 0.009440
4 ETW000 [dev trc     ,00000] -->oci_initialize (con_hdl=0)                        195 0.009635
4 ETW000 [dev trc     ,00000] Client NLS settings: AMERICAN_AMERICA.UTF8          1567 0.011202
4 ETW000 [dev trc     ,00000] Logon as OPS$-user to get SAPSR3's password           14 0.011216
4 ETW000 [dev trc     ,00000] Connecting as /@RXT on connection 0 (nls_hdl 0) ... (dbsl 700 240106)
4 ETW000                                                                              15 0.011231
4 ETW000 [dev trc     ,00000] Nls CharacterSet                 NationalCharSet              C      EnvHp      ErrHp ErrHpBatch
4 ETW000                                                                              17 0.011248
4 ETW000 [dev trc     ,00000]    0 UTF8                                                      1 0x9342150 0x9349ba0 0x935a298
4 ETW000                                                                              16 0.011264
4 ETW000 [dev trc     ,00000] Allocating service context handle for con_hdl=0       15 0.011279
4 ETW000 [dev trc     ,00000] Allocating server context handle                      11 0.011290
4 ETW000 [dev trc     ,00000] Attaching to DB Server RXT (con_hdl=0,svchp=0x935a1c8,svrhp=0x935c4a8)
4 ETW000                                                                              63 0.011353
4 ETW000 [dboci.c     ,00000] *** ERROR => OCI-call 'OCIServerAttach' failed: rc = 12541
4 ETW000                                                                            1787 0.013140
4 ETW000 [dbsloci.    ,00000] *** ERROR => CONNECT failed with sql error '12541'
4 ETW000                                                                              16 0.013156
4 ETW000 [dev trc     ,00000] Try to connect with default password                  46 0.013202
4 ETW000 [dev trc     ,00000] Connecting as SAPSR3/<pwd>@RXT on connection 0 (nls_hdl 0) ... (dbsl 700 240106)
4 ETW000                                                                              15 0.013217
4 ETW000 [dev trc     ,00000] Nls CharacterSet                 NationalCharSet              C      EnvHp      ErrHp ErrHpBatch
4 ETW000                                                                              16 0.013233
4 ETW000 [dev trc     ,00000]    0 UTF8                                                      1 0x9342150 0x9349ba0 0x935a298
4 ETW000                                                                              15 0.013248
4 ETW000 [dev trc     ,00000] server_detach(con_hdl=0,stale=0,svrhp=0x935c4a8)
4 ETW000                                                                              14 0.013262
4 ETW000 [dev trc     ,00000] Detaching from DB Server (con_hdl=0,svchp=0x935a1c8,srvhp=0x935c4a8)
4 ETW000                                                                              13 0.013275
4 ETW000 [dev trc     ,00000] Deallocating server context handle 0x935c4a8          20 0.013295
4 ETW000 [dev trc     ,00000] Allocating server context handle                      20 0.013315
4 ETW000 [dev trc     ,00000] Attaching to DB Server RXT (con_hdl=0,svchp=0x935a1c8,svrhp=0x935c4a8)
4 ETW000                                                                              25 0.013340
4 ETW000 [dboci.c     ,00000] *** ERROR => OCI-call 'OCIServerAttach' failed: rc = 12541
4 ETW000                                                                             430 0.013770
4 ETW000 [dbsloci.    ,00000] *** ERROR => CONNECT failed with sql error '12541'
4 ETW000                                                                              16 0.013786
4 ETW000 [dblink      ,00431] ***LOG BY2=>sql error 12541 performing CON [dblink#3 @ 431]
4 ETW000                                                                              85 0.013871
4 ETW000 [dblink      ,00431] ***LOG BY0=>ORA-12541: TNS:no listener [dblink#3 @ 431]
4 ETW000                                                                              15 0.013886
2EETW169 no connect possible: "DBMS = ORACLE                           --- dbs_ora_tnsname = 'RXT'"
isrxi:rxtadm 8>
Regards,
Amit

Sapinst error at import abap phase

Hi experts,
i am getting error at import abap phase. please have you look and let me know your inputs
ERROR 2011-08-31 22:55:27.730 [sixxcstepexecute.cpp:937]
FCO-00011 The step runMigrationMonitor with step key |NW_Doublestack_DB|ind|ind|ind|ind|0|0|NW_CreateDBandLoad|ind|ind|ind|ind|createdbandload|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|abapload|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|
runMigrationMonitor was executed with status ERROR
( Last error reported by the step:
Execution of the command "/opt/java1.5/bin/java -classpath migmon.jar -showversion -Xmx1024m -d64 com.sap.inst.migmon.imp.ImportMonitor -sapinst"
finished with status TST_ERROR.)
Regards
Srinivas

Dear Srinivas,
I hope this may problem with as follwing
1)This had happened as a particular DVD was not copied properly You should copy it again and started it may be !
2) Please check Snote for Java : 716926 & 1426759
Thanks
Mithun

GETTING ERROR WHILE INSTALLING ECC6.0

HI
I am trying to install ecc6.0 in window2003 database is oracle10g it was fine till database creation, when it reached to IMPORT ABAP phase it started giving error.
I got the error at the beggning of the phase i checked the logs a come to know that i have to increase the shared pool memory, done the same it worked fine however it stucked in 16 subphase of import abap getting the below error
INFO 2012-12-02 10:50:22 Copied file 'C:/Program Files/sapinst_instdir/ERP/SYSTEM/MSS/CENTRAL/AS/inifile.xml' to 'C:/Program Files/sapinst_instdir/ERP/SYSTEM/MSS/CENTRAL/AS/inifile.4.xml'. INFO 2012-12-02 10:50:22 Copied file 'C:/Program Files/sapinst_instdir/ERP/SYSTEM/MSS/CENTRAL/AS/inifile.xml' to 'C:/Program Files/sapinst_instdir/ERP/SYSTEM/MSS/CENTRAL/AS/inifile.5.xml'. INFO 2012-12-02 10:50:25 Execute step Component W2K_ServicePack_Check|ind|ind|ind|indPreprocess of component |NW_Onehost|ind|ind|ind|ind|0|0|NW_First_Steps|ind|ind|ind|ind|0|0|W2K_ServicePack_Check|ind|ind|ind|ind|2|0. INFO 2012-12-02 10:50:40 Copied file 'C:/Program Files/sapinst_instdir/ERP/SYSTEM/MSS/CENTRAL/AS/keydb.xml' to 'C:/Program Files/sapinst_instdir/ERP/SYSTEM/MSS/CENTRAL/AS/keydb.3.xml'. INFO 2012-12-02 10:50:40 Execute step runMigrationMonitor of component |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|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. INFO 2012-12-02 10:50:45 Switched to user: prdadm. INFO 2012-12-02 10:50:46 Creating file C:\Program Files\sapinst_instdir\ERP\SYSTEM\MSS\CENTRAL\AS\import_monitor.java.log. INFO 2012-12-02 10:50:46 Switched to user: prdadm. INFO 2012-12-02 10:50:46 Working directory changed to C:\Program Files\sapinst_instdir\ERP\SYSTEM\MSS\CENTRAL\AS. INFO 2012-12-02 10:50:46 Output of C:\j2sdk1.4.2_07\bin\java.exe -classpath migmon.jar -showversion com.sap.inst.migmon.imp.ImportMonitor -dbType MSS -importDirs E:\EXP1;E:\EXP2;E:\EXP3;E:\EXP4;E:\EXP5;E:\EXP6;E:\EXP7;E:\EXP8;E:\EXP9;E:\EXP10;E:\EXP11 -installDir "C:\Program Files\sapinst_instdir\ERP\SYSTEM\MSS\CENTRAL\AS" -orderBy "" -r3loadExe F:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -tskFiles yes -extFiles no -dbCodepage 4103 -jobNum 1 -monitorTimeout 30 -loadArgs " -loadprocedure fast" -trace all -sapinst is written to the logfile import_monitor.java.log. WARNING 2012-12-02 14:02:13 Execution of the command "C:\j2sdk1.4.2_07\bin\java.exe -classpath migmon.jar -showversion com.sap.inst.migmon.imp.ImportMonitor -dbType MSS -importDirs E:\EXP1;E:\EXP2;E:\EXP3;E:\EXP4;E:\EXP5;E:\EXP6;E:\EXP7;E:\EXP8;E:\EXP9;E:\EXP10;E:\EXP11 -installDir "C:\Program Files\sapinst_instdir\ERP\SYSTEM\MSS\CENTRAL\AS" -orderBy "" -r3loadExe F:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -tskFiles yes -extFiles no -dbCodepage 4103 -jobNum 1 -monitorTimeout 30 -loadArgs " -loadprocedure fast" -trace all -sapinst" finished with return code 103. Output: java version "1.4.2_07"Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_07-b05)Java HotSpot(TM) Client VM (build 1.4.2_07-b05, mixed mode)Import Monitor jobs: running 1, waiting 18, completed 0, failed 0, total 19.Loading of 'SAPAPPL1' import package: OKImport Monitor jobs: running 0, waiting 18, completed 1, failed 0, total 19.Import Monitor jobs: running 1, waiting 17, completed 1, failed 0, total 19.Loading of 'SAPSSEXC' import package: OKImport Monitor jobs: running 0, waiting 17, completed 2, failed 0, total 19.Import Monitor jobs: running 1, waiting 16, completed 2, failed 0, total 19.Loading of 'SAPAPPL0' import package: ERRORImport Monitor jobs: running 0, waiting 16, completed 2, failed 1, total 19.Import Monitor jobs: running 1, waiting 15, completed 2, failed 1, total 19.Loading of 'SAPAPPL2' import package: OKImport Monitor jobs: running 0, waiting 15, completed 3, failed 1, total 19.Import Monitor jobs: running 1, waiting 14, completed 3, failed 1, total 19.Loading of 'SAPSDIC' import package: OKImport Monitor jobs: running 0, waiting 14, completed 4, failed 1, total 19.Import Monitor jobs: running 1, waiting 13, completed 4, failed 1, total 19.Loading of 'SAPCLUST' import package: OKImport Monitor jobs: running 0, waiting 13, completed 5, failed 1, total 19.Import Monitor jobs: running 1, waiting 12, completed 5, failed 1, total 19.Loading of 'SAPSLEXC' import package: OKImport Monitor jobs: running 0, waiting 12, completed 6, failed 1, total 19.Import Monitor jobs: running 1, waiting 11, completed 6, failed 1, total 19.Loading of 'SAPSSRC' import package: OKImport Monitor jobs: running 0, waiting 11, completed 7, failed 1, total 19.Import Monitor jobs: running 1, waiting 10, completed 7, failed 1, total 19.Loading of 'SAPPOOL' import package: OKImport Monitor jobs: running 0, waiting 10, completed 8, failed 1, total 19.Import Monitor jobs: running 1, waiting 9, completed 8, failed 1, total 19.Loading of 'SAPSDOCU' import package: OKImport Monitor jobs: running 0, waiting 9, completed 9, failed 1, total 19.Import Monitor jobs: running 1, waiting 8, completed 9, failed 1, total 19.Loading of 'SAPSPROT' import package: OKImport Monitor jobs: running 0, waiting 8, completed 10, failed 1, total 19.Import Monitor jobs: running 1, waiting 7, completed 10, failed 1, total 19.Loading of 'SAPSLOAD' import package: OKImport Monitor jobs: running 0, waiting 7, completed 11, failed 1, total 19.Import Monitor jobs: running 1, waiting 6, completed 11, failed 1, total 19.Loading of 'SAPUSER' import package: OKImport Monitor jobs: running 0, waiting 6, completed 12, failed 1, total 19.Import Monitor jobs: running 1, waiting 5, completed 12, failed 1, total 19.Loading of 'SAPDDIM' import package: OKImport Monitor jobs: running 0, waiting 5, completed 13, failed 1, total 19.Import Monitor jobs: running 1, waiting 4, completed 13, failed 1, total 19.Loading of 'SAPDFACT' import package: OKImport Monitor jobs: running 0, waiting 4, completed 14, failed 1, total 19.Import Monitor jobs: running 1, waiting 3, completed 14, failed 1, total 19.Loading of 'SAPDODS' import package: OKImport Monitor jobs: running 0, waiting 3, completed 15, failed 1, total 19.Import Monitor jobs: running 1, waiting 2, completed 15, failed 1, total 19.Loading of 'SAPUSER1' import package: OKImport Monitor jobs: running 0, waiting 2, completed 16, failed 1, total 19.Import Monitor jobs: running 1, waiting 1, completed 16, failed 1, total 19.Loading of 'SAP0000' import package: OKImport Monitor jobs: running 0, waiting 1, completed 17, failed 1, total 19. ERROR 2012-12-02 14:02:14 CJS-30022 Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log. ERROR 2012-12-02 14:02:15 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|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 . vmware6.5 os : windows 2003 db: sqlserver2005 memory is : 1.5g i have check the import_monitor.java.log, import_monitor.log . the log error is: F:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL1.cmd -dbcodepage 4103 -l SAPAPPL1.log -loadprocedure fast (DB) INFO: connected to DB (DB) ERROR: DDL statement failed (DROP INDEX [SWFREVTLOG].[SWFREVTLOG001]) DbSlExecute: rc = 103 (SQL error 3701) error message returned by DbSl: *can not del the index:'SWFREVTLOG.SWFREVTLOG001' Because it does not exist, or if you do not have the necessary permissions.* (IMP) INFO: a failed DROP attempt is not necessarily a problem (DB) INFO: SWFREVTLOG001 created (DB) INFO: disconnected from DB F:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPSSEXC.cmd -dbcodepage 4103 -l SAPSSEXC.log -loadprocedure fast (DB) INFO: connected to DB (DB) ERROR: DDL statement failed (DROP INDEX [TFDIR].[TFDIR1]) DbSlExecute: rc = 103 (SQL error 3701) error message returned by DbSl: 。 can not del the index:'TMDIR.TMDIR~1' Because it does not exist, or if you do not have the necessary permissions. (IMP) INFO: a failed DROP attempt is not necessarily a problem (DB) INFO: TFDIR1 created (DB) ERROR: DDL statement failed (DROP INDEX [TFDIR].[TFDIR2]) DbSlExecute: rc = 103 (SQL error 3701) error message returned by DbSl: can not del the index:'TMDIR.TMDIR~2' Because it does not exist, or if you do not have the necessary permissions. (IMP) INFO: a failed DROP attempt is not necessarily a problem (DB) INFO: TFDIR2 created (DB) ERROR: DDL statement failed (DROP INDEX [TMDIR].[TMDIRMTD]) DbSlExecute: rc = 103 (SQL error 3701) error message returned by DbSl: can not del the index:'TMDIR.TMDIR~MTD' Because it does not exist, or if you do not have the necessary permissions. (IMP) INFO: a failed DROP attempt is not necessarily a problem (DB) INFO: TMDIR~MTD created (DB) INFO: disconnected from DB TSK) ERROR: file C:\Program
is there anyone who can help me to solve this error
i would appreciate your help
Regards
Rizvi

Hi
I have to increase the shared pool memory, done the same it worked fine however it
How much you have increase it and what is the value now? it should be more than 250M
It worked in my case when i have increase the value to 300M and retried the installation btw did you installed oracle path?
Regards
Uday

Error while installing ECC6.0with PI

SAPinst ADMINISTRATOR@system:SAP ERP 2005 Support Release2 > SAP Systems > Oracle > central instance >central system installation.
in the step 4:-Execute service;phase 19 of 95----
import ABAP.
THIS IS THE ERROR IN LOG BROWSER
CJS-30022 PROGRAM 'MIGRATION MONITOR' EXITS WITH ERROR CODE 103.FOR DETAILS SEE LOG FILE(S) IMPORT_MONITOR.JAVA.LOG,IMPORT_MONITOR.LOG.
FC0-00011 THE STEP runMigrationMonitor with step key |NW_0neHost|ind|ind|ind|ind|0|0|NW_0nehost_system|ind|ind|ind|ind|1|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.
and in the log file
java version "1.4.2_12"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_12-b03)
Java HotSpot(TM) Client VM (build 1.4.2_12-b03, mixed mode)
Import Monitor jobs: running 1, waiting 18, completed 0, failed 0, total 19.
Import Monitor jobs: running 2, waiting 17, completed 0, failed 0, total 19.
Import Monitor jobs: running 3, waiting 16, completed 0, failed 0, total 19.
Loading of 'SAPAPPL0' import package: OK
Import Monitor jobs: running 2, waiting 16, completed 1, failed 0, total 19.
Import Monitor jobs: running 3, waiting 15, completed 1, failed 0, total 19.
Loading of 'SAPAPPL1' import package: OK
Import Monitor jobs: running 2, waiting 15, completed 2, failed 0, total 19.
Import Monitor jobs: running 3, waiting 14, completed 2, failed 0, total 19.
Loading of 'SAPSDIC' import package: OK
Import Monitor jobs: running 2, waiting 14, completed 3, failed 0, total 19.
Import Monitor jobs: running 3, waiting 13, completed 3, failed 0, total 19.
Loading of 'SAPCLUST' import package: OK
Import Monitor jobs: running 2, waiting 13, completed 4, failed 0, total 19.
Import Monitor jobs: running 3, waiting 12, completed 4, failed 0, total 19.
Loading of 'SAPSLEXC' import package: OK
Import Monitor jobs: running 2, waiting 12, completed 5, failed 0, total 19.
Import Monitor jobs: running 3, waiting 11, completed 5, failed 0, total 19.
Loading of 'SAPSSRC' import package: OK
Import Monitor jobs: running 2, waiting 11, completed 6, failed 0, total 19.
Import Monitor jobs: running 3, waiting 10, completed 6, failed 0, total 19.
Loading of 'SAPPOOL' import package: OK
Import Monitor jobs: running 2, waiting 10, completed 7, failed 0, total 19.
Import Monitor jobs: running 3, waiting 9, completed 7, failed 0, total 19.
Loading of 'SAPSDOCU' import package: OK
Import Monitor jobs: running 2, waiting 9, completed 8, failed 0, total 19.
Import Monitor jobs: running 3, waiting 8, completed 8, failed 0, total 19.
Loading of 'SAPSPROT' import package: OK
Import Monitor jobs: running 2, waiting 8, completed 9, failed 0, total 19.
Import Monitor jobs: running 3, waiting 7, completed 9, failed 0, total 19.
Loading of 'SAPSLOAD' import package: OK
Import Monitor jobs: running 2, waiting 7, completed 10, failed 0, total 19.
Import Monitor jobs: running 3, waiting 6, completed 10, failed 0, total 19.
Loading of 'SAPUSER' import package: OK
Import Monitor jobs: running 2, waiting 6, completed 11, failed 0, total 19.
Import Monitor jobs: running 3, waiting 5, completed 11, failed 0, total 19.
Loading of 'SAPDDIM' import package: OK
Import Monitor jobs: running 2, waiting 5, completed 12, failed 0, total 19.
Import Monitor jobs: running 3, waiting 4, completed 12, failed 0, total 19.
Loading of 'SAPDFACT' import package: OK
Import Monitor jobs: running 2, waiting 4, completed 13, failed 0, total 19.
Import Monitor jobs: running 3, waiting 3, completed 13, failed 0, total 19.
Loading of 'SAPDODS' import package: OK
Import Monitor jobs: running 2, waiting 3, completed 14, failed 0, total 19.
Import Monitor jobs: running 3, waiting 2, completed 14, failed 0, total 19.
Loading of 'SAPUSER1' import package: OK
Import Monitor jobs: running 2, waiting 2, completed 15, failed 0, total 19.
Import Monitor jobs: running 3, waiting 1, completed 15, failed 0, total 19.
Loading of 'SAP0000' import package: OK
Import Monitor jobs: running 2, waiting 1, completed 16, failed 0, total 19.
Loading of 'SAPAPPL2' import package: ERROR
Import Monitor jobs: running 1, waiting 1, completed 16, failed 1, total 19.
Loading of 'SAPSSEXC' import package: ERROR
Import Monitor jobs: running 0, waiting 1, completed 16, failed 2, total 19.

hi EXPERTS,
i want to configure PI using ECC6.0.
my hard disk space is 250gb---233 net.
RAM -
2GB.
PROCESSOR -
2.8 DUAL CORE INTEL
OPERATING SYSTEM:-WINDOWS 2003 ENTERPRISE EDITION.
PARTITIONS:-
C:-5GB         2046-3950 VIRTUAL MEMORY
D:-228GB       5000-5500 VIRTUAL MEMORY
MY SYSTEM NAME IS -
SYSTEM.
I CONFIGURED MICROSOFT LOOPBACK ADAPTER.
THEN INSTALLED j2sdk-1_4_2_12-windows-i586-p AND PUT ENVIRONMENT VARIABLES.
AFTER I INSTALLED ORACLE 10G WITH DATABASE NAME "ORCL".
AFTER THAT SELECT InsMaster\IM_WINDOWS_I386->SAPINST.EXE
THEN SAPERP2005 SUPPORT RELEASE 1->SAP SYSTEM --> ORACLE > CENTRAL SYSTEM> CENTRAL INSTANCE INSTALLATION.
AFTER THAT IN STEP 2 , I SELECTED ECC , AS ABAP , AS JAVA , PI.
ASKED FOR JAVA COMPONENTS AND I GAVE THAT ONE.
THEN JCE POLICY AND I GAVE THAT ONE.
SAP SID-->ERP.
INSTALLATION DRIVE :-D:
MASTER PASSWORD.
DB ID :--AND I GAVE THIS AS ORC.
DB HOST:- IT TAKE AUTOMATICALLY(SYSTEM-NAME OF THE SYSTEM)
THEN I GAVE THE EXPORT1 PATH
THEN EXPORT6 PATH
THEN EXPORT 2,3,4&5.
THEN IT ASKED FOR ORACLE CLIENT,KERNAL AND BS2005 AND I GAVE ALL THE DETAILS.
IT ASKED FOR TO CONFIGURE SLD AND I SELECT RADIO BUTTON " REGISTER IN EXISTING CENTRAL SLD(DEFAULT)"
THEN IN SLD:-
SELF REGISTRATION OF JAVA ENGINE IN CENTRAL SLD
      SLD HTTP HOST:- SYSTEM (I GAVE MY SYSTEM NAME)
      SLD HTTP PORT:- 50100 (I GIVE THAT PORT AS 50000)
      SLD DATA SUPPLIER USER :-SLDDSUSER(AUTOMATICALLY GENERATED).
      PASSWORD:-GENERATED.
SELF REGISTRATION OF ABAP ENGINE IN CENTRAL SLD:-
      SLD GATEWAY HOST:-SYSTEM (I GAVE MY SYSTEM NAME)
      SLD GATEWAY INSTANCE NUMBER:-02COMMUNICATION WITH CENTRAL SLD:-
      SLD ABAPAPIUSER:-SLDAPIUSER(GENERATED)
      PASSWORD:-(GENERATED)
AFTER THAT IT ASKED FOR SOLUTION MANAGER KEY AND I GIVE THAT ONE .
IN IMPORT ABAP PHASE I GOT AN ERROR. I HAVE DONE ALL THE PREVIOUS SUGGESTIONS WHICH WERE GIVEN BY EXPERTS AND I GOT THAT SAME ERROR ONCE AGAIN SO IAM POSTING THESE DETAILS TO GET THE CORRECT SOLUTION.

ECC6.0 installation error in Import ABAP Phase

Dear Experts,
I am in the process if Installing IDES for ECC 6.0 Non Unicode
Installation (SAP ERP 2005 SR2). During IMPORT ABAP
phase geting below error:
ERROR 2007-12-13 14:48:37
CJS-30022 Program 'Migration Monitor' exits with error code 103. For
details see log file(s) import_monitor.java.log, import_monitor.log.
ERROR 2007-12-13 14:48:37
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|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 .
Import_monitor.java.log:
java version "1.4.2_12"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_12-b03)
Java HotSpot(TM) Client VM (build 1.4.2_12-b03, mixed mode)
Import Monitor jobs: running 1, waiting 4, completed 31, failed 0, total 36.
Import Monitor jobs: running 2, waiting 3, completed 31, failed 0, total 36.
Import Monitor jobs: running 3, waiting 2, completed 31, failed 0, total 36.
Loading of 'SAPSSEXC_3' import package: ERROR
Import Monitor jobs: running 2, waiting 2, completed 31, failed 1, total 36.
Import Monitor jobs: running 3, waiting 1, completed 31, failed 1, total 36.
Loading of 'SAPCLUST' import package: ERROR
Import Monitor jobs: running 2, waiting 1, completed 31, failed 2, total 36.
Loading of 'SAPPOOL' import package: ERROR
Import Monitor jobs: running 1, waiting 1, completed 31, failed 3, total 36.
Loading of 'SAPSSEXC_4' import package: ERROR
Import Monitor jobs: running 0, waiting 1, completed 31, failed 4, total 36.
Import_monitor.log:
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
E:\usr\sap\EC4\SYS\exe\uc\NTI386\R3load.exe: job finished with 1 error(s)
E:\usr\sap\EC4\SYS\exe\uc\NTI386\R3load.exe: END OF LOG: 20080106214611
Please help me ASAP.
Regards,
Gajapathi Raju.

Dear Marquis,
Some body copied dumps from Hard disk to server not from original cd's.Might be copied not properly.I have copied from Original cd's,Then i was suceed in installation.
Regards,
Gajapathi Raju.
Edited by: V R Gajapathi Raju on Feb 13, 2008 9:24 AM

Error in import abap step while importing system copy.

Hi All,
My colleague had taken System copy of development server, few days back. it was completed successfully,
now we want to restore that system copy, as hardware failed. But when we start the import of system copy,
all ABAP jobs are failing in import abap step, Some DDL statement problem. can u pls help wht to do.
I found in some forums, SMIGR_create_DDL report need to be generated prior to taking system copy, but he
didnt taken tht.
OS: Windows 2003
DB: DB2
Pls find sapinst.log
INFO 2009-10-27 10:43:06.890
Output of C:\j2sdk1.4.2_13-x64\bin\java.exe -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -sapinst is written to the logfile import_monitor.java.log.
WARNING 2009-10-27 10:53:37.125
Execution of the command "C:\j2sdk1.4.2_13-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_13"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_13-b06)
Java HotSpot(TM) 64-Bit Server VM (build 1.4.2_13-b06, mixed mode)
Import Monitor jobs: running 1, waiting 63, completed 0, failed 0, total 64.
Import Monitor jobs: running 2, waiting 62, completed 0, failed 0, total 64.
Import Monitor jobs: running 3, waiting 61, completed 0, failed 0, total 64.
Loading of 'DOKCLU' import package: ERROR
Import Monitor jobs: running 2, waiting 61, completed 0, failed 1, total 64.
Loading of 'D010TAB' import package: ERROR
Import Monitor jobs: running 1, waiting 61, completed 0, failed 2, total 64.
Loading of 'REPOSRC' import package: ERROR
Import Monitor jobs: running 0, waiting 61, completed 0, failed 3, total 64.
Import Monitor jobs: running 1, waiting 60, completed 0, failed 3, total 64.
Import Monitor jobs: running 2, waiting 59, completed 0, failed 3, total 64.
Import Monitor jobs: running 3, waiting 58, completed 0, failed 3, total 64.
Loading of 'DYNPSOURCE' import package: ERROR
Import Monitor jobs: running 2, waiting 58, completed 0, failed 4, total 64.
Loading of 'SAPAPPL1_4' import package: ERROR
Import Monitor jobs: running 1, waiting 58, completed 0, failed 5, total 64.
Loading of 'SAPAPPL2_2' import package: ERROR
Import Monitor jobs: running 0, waiting 58, completed 0, failed 6, total 64.
Import Monitor jobs: running 1, waiting 57, completed 0, failed 6, total 64.
Import Monitor jobs: running 2, waiting 56, completed 0, failed 6, total 64.
Import Monitor jobs: running 3, waiting 55, completed 0, failed 6, total 64.
Loading of 'SAPNTAB' import package: ERROR
Import Monitor jobs: running 2, waiting 55, completed 0, failed 7, total 64.
Loading of 'SAPSSEXC_9' import package: ERROR
Import Monitor jobs: running 1, waiting 55, completed 0, failed 8, total 64.
Loading of 'SAPSSEXC_8' import package: ERROR
Import Monitor jobs: running 0, waiting 55, completed 0, failed 9, total 64.
Import Monitor jobs: running 1, waiting 54, completed 0, failed 9, total 64.
Import Monitor jobs: running 2, waiting 53, completed 0, failed 9, total 64.
Import Monitor jobs: running 3, waiting 52, completed 0, failed 9, total 64.
Loading of 'SAPAPPL2_6' import package: ERROR
Import Monitor jobs: running 2, waiting 52, completed 0, failed 10, total 64.
Loading of 'SAPAPPL1_3' import package: ERROR
Import Monitor jobs: running 1, waiting 52, completed 0, failed 11, total 64.
Loading of 'SAPAPPL2_5' import package: ERROR
Import Monitor jobs: running 0, waiting 52, completed 0, failed 12, total 64.
Import Monitor jobs: running 1, waiting 51, completed 0, failed 12, total 64.
Import Monitor jobs: running 2, waiting 50, completed 0, failed 12, total 64.
Import Monitor jobs: running 3, waiting 49, completed 0, failed 12, total 64.
Loading of 'D010INC' import package: ERROR
Import Monitor jobs: running 2, waiting 49, completed 0, failed 13, total 64.
Loading of 'SAPAPPL1_2' import package: ERROR
Import Monitor jobs: running 1, waiting 49, completed 0, failed 14, total 64.
Loading of 'SAPAPPL1_7' import package: ERROR
Import Monitor jobs: running 0, waiting 49, completed 0, failed 15, total 64.
Import Monitor jobs: running 1, waiting 48, completed 0, failed 15, total 64.
Import Monitor jobs: running 2, waiting 47, completed 0, failed 15, total 64.
Import Monitor jobs: running 3, waiting 46, completed 0, failed 15, total 64.
Loading of 'SAPSSEXC_2' import package: ERROR
Import Monitor jobs: running 2, waiting 46, completed 0, failed 16, total 64.
Loading of 'DYNPLOAD' import package: ERROR
Import Monitor jobs: running 1, waiting 46, completed 0, failed 17, total 64.
Loading of 'SAPSSEXC_5' import package: ERROR
Import Monitor jobs: running 0, waiting 46, completed 0, failed 18, total 64.
Import Monitor jobs: running 1, waiting 45, completed 0, failed 18, total 64.
Import Monitor jobs: running 2, waiting 44, completed 0, failed 18, total 64.
Import Monitor jobs: running 3, waiting 43, completed 0, failed 18, total 64.
Loading of 'SAPSDIC' import package: ERROR
Import Monitor jobs: running 2, waiting 43, completed 0, failed 19, total 64.
Loading of 'SAPAPPL2_14' import package: ERROR
Import Monitor jobs: running 1, waiting 43, completed 0, failed 20, total 64.
Loading of 'SAPAPPL0_2' import package: ERROR
Import Monitor jobs: running 0, waiting 43, completed 0, failed 21, total 64.
Import Monitor jobs: running 1, waiting 42, completed 0, failed 21, total 64.
Import Monitor jobs: running 2, waiting 41, completed 0, failed 21, total 64.
Import Monitor jobs: running 3, waiting 40, completed 0, failed 21, total 64.
Loading of 'SAPSSEXC_3' import package: ERROR
Import Monitor jobs: running 2, waiting 40, completed 0, failed 22, total 64.
Loading of 'SAPSSEXC_4' import package: ERROR
Import Monitor jobs: running 1, waiting 40, completed 0, failed 23, total 64.
Loading of 'SAPAPPL2_10' import package: ERROR
Import Monitor jobs: running 0, waiting 40, completed 0, failed 24, total 64.
Import Monitor jobs: running 1, waiting 39, completed 0, failed 24, total 64.
Import Monitor jobs: running 2, waiting 38, completed 0, failed 24, total 64.
Import Monitor jobs: running 3, waiting 37, completed 0, failed 24, total 64.
Loading of 'SAPSSEXC_7' import package: ERROR
Import Monitor jobs: running 2, waiting 37, completed 0, failed 25, total 64.
Loading of 'SAPAPPL0_7' import package: ERROR
Import Monitor jobs: running 1, waiting 37, completed 0, failed 26, total 64.
Loading of 'SAPAPPL0_1' import package: ERROR
Import Monitor jobs: running 0, waiting 37, completed 0, failed 27, total 64.
Import Monitor jobs: running 1, waiting 36, completed 0, failed 27, total 64.
Import Monitor jobs: running 2, waiting 35, completed 0, failed 27, total 64.
Import Monitor jobs: running 3, waiting 34, completed 0, failed 27, total 64.
Loading of 'SAPAPPL2_7' import package: ERROR
Import Monitor jobs: running 2, waiting 34, completed 0, failed 28, total 64.
Loading of 'SAPAPPL2_4' import package: ERROR
Import Monitor jobs: running 1, waiting 34, completed 0, failed 29, total 64.
Loading of 'SAPAPPL1_6' import package: ERROR
Import Monitor jobs: running 0, waiting 34, completed 0, failed 30, total 64.
Import Monitor jobs: running 1, waiting 33, completed 0, failed 30, total 64.
Import Monitor jobs: running 2, waiting 32, completed 0, failed 30, total 64.
Import Monitor jobs: running 3, waiting 31, completed 0, failed 30, total 64.
Loading of 'SAPAPPL0_3' import package: ERROR
Import Monitor jobs: running 2, waiting 31, completed 0, failed 31, total 64.
Loading of 'SAPCLUST' import package: ERROR
Import Monitor jobs: running 1, waiting 31, completed 0, failed 32, total 64.
Loading of 'SAPAPPL0_8' import package: ERROR
Import Monitor jobs: running 0, waiting 31, completed 0, failed 33, total 64.
Import Monitor jobs: running 1, waiting 30, completed 0, failed 33, total 64.
Import Monitor jobs: running 2, waiting 29, completed 0, failed 33, total 64.
Import Monitor jobs: running 3, waiting 28, completed 0, failed 33, total 64.
Loading of 'SAPSSRC' import package: ERROR
Import Monitor jobs: running 2, waiting 28, completed 0, failed 34, total 64.
Loading of 'ENHOBJCONTRACT' import package: ERROR
Import Monitor jobs: running 1, waiting 28, completed 0, failed 35, total 64.
Loading of 'SAPAPPL0_4' import package: ERROR
Import Monitor jobs: running 0, waiting 28, completed 0, failed 36, total 64.
Import Monitor jobs: running 1, waiting 27, completed 0, failed 36, total 64.
Import Monitor jobs: running 2, waiting 26, completed 0, failed 36, total 64.
Import Monitor jobs: running 3, waiting 25, completed 0, failed 36, total 64.
Loading of 'SAPSSEXC_1' import package: ERROR
Import Monitor jobs: running 2, waiting 25, completed 0, failed 37, total 64.
Loading of 'SAPSSEXC_6' import package: ERROR
Import Monitor jobs: running 1, waiting 25, completed 0, failed 38, total 64.
Loading of 'SAPAPPL2_8' import package: ERROR
Import Monitor jobs: running 0, waiting 25, completed 0, failed 39, total 64.
Import Monitor jobs: running 1, waiting 24, completed 0, failed 39, total 64.
Import Monitor jobs: running 2, waiting 23, completed 0, failed 39, total 64.
Import Monitor jobs: running 3, waiting 22, completed 0, failed 39, total 64.
Loading of 'SAPPOOL' import package: ERROR
Import Monitor jobs: running 2, waiting 22, completed 0, failed 40, total 64.
Loading of 'SAPAPPL2_1' import package: ERROR
Import Monitor jobs: running 1, waiting 22, completed 0, failed 41, total 64.
Loading of 'SAPAPPL1_5' import package: ERROR
Import Monitor jobs: running 0, waiting 22, completed 0, failed 42, total 64.
Import Monitor jobs: running 1, waiting 21, completed 0, failed 42, total 64.
Import Monitor jobs: running 2, waiting 20, completed 0, failed 42, total 64.
Import Monitor jobs: running 3, waiting 19, completed 0, failed 42, total 64.
Loading of 'REPOTEXT' import package: ERROR
Import Monitor jobs: running 2, waiting 19, completed 0, failed 43, total 64.
Loading of 'SAPAPPL0_5' import package: ERROR
Import Monitor jobs: running 1, waiting 19, completed 0, failed 44, total 64.
Loading of 'SAPAPPL2_9' import package: ERROR
Import Monitor jobs: running 0, waiting 19, completed 0, failed 45, total 64.
Import Monitor jobs: running 1, waiting 18, completed 0, failed 45, total 64.
Import Monitor jobs: running 2, waiting 17, completed 0, failed 45, total 64.
Import Monitor jobs: running 3, waiting 16, completed 0, failed 45, total 64.
Loading of 'SAPSSEXC_10' import package: ERROR
Import Monitor jobs: running 2, waiting 16, completed 0, failed 46, total 64.
Loading of 'SAPAPPL2_3' import package: ERROR
Import Monitor jobs: running 1, waiting 16, completed 0, failed 47, total 64.
Loading of 'SAPAPPL0_6' import package: ERROR
Import Monitor jobs: running 0, waiting 16, completed 0, failed 48, total 64.
Import Monitor jobs: running 1, waiting 15, completed 0, failed 48, total 64.
Import Monitor jobs: running 2, waiting 14, completed 0, failed 48, total 64.
Import Monitor jobs: running 3, waiting 13, completed 0, failed 48, total 64.
Loading of 'SAPSLEXC' import package: ERROR
Import Monitor jobs: running 2, waiting 13, completed 0, failed 49, total 64.
Loading of 'SAPAPPL0_9' import package: ERROR
Import Monitor jobs: running 1, waiting 13, completed 0, failed 50, total 64.
Loading of 'SAPAPPL2_11' import package: ERROR
Import Monitor jobs: running 0, waiting 13, completed 0, failed 51, total 64.
Import Monitor jobs: running 1, waiting 12, completed 0, failed 51, total 64.
Import Monitor jobs: running 2, waiting 11, completed 0, failed 51, total 64.
Import Monitor jobs: running 3, waiting 10, completed 0, failed 51, total 64.
Loading of 'SAPSPROT' import package: ERROR
Import Monitor jobs: running 2, waiting 10, completed 0, failed 52, total 64.
Loading of 'SAPAPPL2_13' import package: ERROR
Import Monitor jobs: running 1, waiting 10, completed 0, failed 53, total 64.
Loading of 'SAPAPPL2_12' import package: ERROR
Import Monitor jobs: running 0, waiting 10, completed 0, failed 54, total 64.
Import Monitor jobs: running 1, waiting 9, completed 0, failed 54, total 64.
Import Monitor jobs: running 2, waiting 8, completed 0, failed 54, total 64.
Import Monitor jobs: running 3, waiting 7, completed 0, failed 54, total 64.
Loading of 'SAPSLOAD' import package: ERROR
Import Monitor jobs: running 2, waiting 7, completed 0, failed 55, total 64.
Loading of 'SAPSDOCU' import package: ERROR
Import Monitor jobs: running 1, waiting 7, completed 0, failed 56, total 64.
Loading of 'SAPAPPL1_1' import package: ERROR
Import Monitor jobs: running 0, waiting 7, completed 0, failed 57, total 64.
Import Monitor jobs: running 1, waiting 6, completed 0, failed 57, total 64.
Import Monitor jobs: running 2, waiting 5, completed 0, failed 57, total 64.
Import Monitor jobs: running 3, waiting 4, completed 0, failed 57, total 64.
Loading of 'SAPDDIM' import package: ERROR
Import Monitor jobs: running 2, waiting 4, completed 0, failed 58, total 64.
Loading of 'SAPUSER' import package: ERROR
Import Monitor jobs: running 1, waiting 4, completed 0, failed 59, total 64.
Loading of 'SAPDFACT' import package: ERROR
Import Monitor jobs: running 0, waiting 4, completed 0, failed 60, total 64.
Import Monitor jobs: running 1, waiting 3, completed 0, failed 60, total 64.
Import Monitor jobs: running 2, waiting 2, completed 0, failed 60, total 64.
Import Monitor jobs: running 3, waiting 1, completed 0, failed 60, total 64.
Loading of 'SAPDODS' import package: ERROR
Import Monitor jobs: running 2, waiting 1, completed 0, failed 61, total 64.
Loading of 'SAPUSER1' import package: ERROR
Import Monitor jobs: running 1, waiting 1, completed 0, failed 62, total 64.
Loading of 'SAP0000' import package: ERROR
Import Monitor jobs: running 0, waiting 1, completed 0, failed 63, total 64.
ERROR 2009-10-27 10:53:37.125
CJS-30022 Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.
ERROR 2009-10-27 10:53:37.140
FCO-00011 The step runMigrationMonitor with step key |NW_Doublestack_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.).
Thanks.

i checked the DOKCLU log, pls find the log below:
D:\usr\sap\ATD\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20091027104307
D:\usr\sap\ATD\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#20 $ SAP
D:\usr\sap\ATD\SYS\exe\uc\NTAMD64\R3load.exe: version R7.00/V1.4 [UNICODE]
Compiled Aug 23 2009 23:42:38
D:\usr\sap\ATD\SYS\exe\uc\NTAMD64\R3load.exe -i DOKCLU.cmd -dbcodepage 4103 -k 1gage5M50Dp01eqte1]x3Qa5 -l DOKCLU.log -stop_on_error -loadprocedure fast LOAD
(DB) INFO: connected to DB
(GSI) INFO: dbname   = "ATD                                                                                "
(GSI) INFO: vname    = "DB6                             "
(GSI) INFO: hostname = "UNKNOWN                                                         "
(GSI) INFO: sysname = "Windows NT"
(GSI) INFO: nodename = "SERVER"
(GSI) INFO: release = "5.2"
(GSI) INFO: version = "3790 Service Pack 1"
(GSI) INFO: machine = "4x AMD64 Level 6 (Mod 23 Step 7)"
(DB) ERROR: DDL statement failed
( DROP TABLE "DOKCLU" )
dsql_exec_immediate returned DS_DBOBJECTUNKNOWN
(IMP) INFO: a failed DROP attempt is not necessarily a problem
(DB) ERROR: DDL statement failed
( CREATE TABLE "DOKCLU" ( "ID" SAPDB6CHAR(2) DEFAULT ' ' NOT NULL , "OBJECT" SAPDB6CHAR(60) DEFAULT ' ' NOT NULL , "LANGU" SAPDB6FIXCHAR(1) DEFAULT ' ' NOT NULL , "TYP" SAPDB6FIXCHAR(1) DEFAULT ' ' NOT NULL , "DOKVERSION" SAPDB6FIXCHAR(4) DEFAULT '0000' NOT NULL , "PAGENO" SMALLINT DEFAULT 0 NOT NULL , "TIMESTMP" SAPDB6CHAR(46) DEFAULT ' ' NOT NULL , "PAGELG" SMALLINT DEFAULT 0 NOT NULL , "VARDATA" VARCHAR(3800) FOR BIT DATA ) IN ATD#ES700D INDEX IN ATD#ES700I LONG IN ATD#ES700D )
dsql_exec_immediate returned DS_DBOBJECTUNKNOWN
(DB) INFO: disconnected from DB
D:\usr\sap\ATD\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 1 error(s)
D:\usr\sap\ATD\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20091027104307
Thanks

Error while installing ECC6

Hi All
i am trying to install ECC6.0 and i face the following error during central instance installation.
ERROR 2007-10-03 11:25:42
CJS-30022 Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.
ERROR 2007-10-03 11:25:42
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|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 .
I did find a solution to this problem on the Internet which tells us to increase the SAG_MAX_SIZE. I did try to set this parameter at the OS level in INIT<SID>.ora from 321807974 to almost double and tripple this size. The thing is i donot know what exactly this size should be set too.
My system config is
RAM - 2Gb, Hard Drive-500Gb in three partiotions(20,120,340).
Virtual Memory- Initial is 2046 final is 4024.
Os- Windows 2003
Jdk version is j2sdk1.4.2_13
Db is Oracle 10g
Could any try and help me out with this error.
Thanks in advance.

Hello Bharani,
This could be any number of problems. First of all you need to consult the logs referenced in the sapisnt log,
import_monitor.java.log
import_monitor.log.
These logs will tell you whihc tabbart is failing, and you then need to check the associated logfile for that tabbart, for example it could be sapappl.log or sapslexc.log.
These logs will provide you with detailed information as to why the tabbart is not loading correctly.
Kind Regards,
David

Error in Import Abap step for MI 7.1on AIX oracle

hi guys,
i am installing sap MI 7.1 on AIX on oracle.while installing i am getting the following error in the import abap step
INFO: 2011-01-28 04:15:08
Data codepage 1100 is determined using TOC file '/oracle/MIP/oraarch/51033237/DATA_UNITS/EXPORT_1/DATA/REPOSRC.TOC' for package 'REPOSRC'.
TRACE: 2011-01-28 04:15:09 com.sap.inst.migmon.LoadTask run
Loading of 'DOKCLU' import package is started.
TRACE: 2011-01-28 04:15:09 com.sap.inst.migmon.LoadTask processPackage
Loading of 'DOKCLU' import package into database:
/usr/sap/MIP/SYS/exe/uc/rs6000_64/R3load -i DOKCLU.cmd -dbcodepage 4102 -l DOKCLU.log -stop_on_error -loadprocedure fast
ERROR: 2011-01-28 04:15:11 com.sap.inst.migmon.LoadTask run
Loading of 'DOKCLU' import package is interrupted with R3load error.
Process '/usr/sap/MIP/SYS/exe/uc/rs6000_64/R3load -i DOKCLU.cmd -dbcodepage 4102 -l DOKCLU.log -stop_on_error -loadprocedure fast' exited with return code 2.
For mode details see 'DOKCLU.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
WARNING: 2011-01-28 04:15:38
Cannot start import of packages with views because not all import packages with tables are loaded successfully.
WARNING: 2011-01-28 04:15:38
1 error(s) during processing of packages.
INFO: 2011-01-28 04:15:38
Import Monitor is stopped.
this is the log for DOKCLU
myCluster (127.18.Imp): 650: error when retrieving table description for physical table DOKCLU.
myCluster (127.18.Imp): 651: return code received from nametab is 2
myCluster (127.18.Imp): 294: error when retrieving physical nametab for table DOKCLU.
(CNV) ERROR: data conversion failed. rc = 2
(DB) INFO: disconnected from DB
/usr/sap/MIP/SYS/exe/uc/rs6000_64/R3load: job finished with 1 error(s)
/usr/sap/MIP/SYS/exe/uc/rs6000_64/R3load: END OF LOG: 20110128090816
/usr/sap/MIP/SYS/exe/uc/rs6000_64/R3load: START OF LOG: 20110128094510
/usr/sap/MIP/SYS/exe/uc/rs6000_64/R3load: sccsid @(#) $Id: //bas/710_REL/src/R3ld/R3load/R3ldmain.c#10 $ SAP
/usr/sap/MIP/SYS/exe/uc/rs6000_64/R3load: version R7.20/V1.4 [UNICODE]
Compiled Oct 25 2007 20:54:47
/usr/sap/MIP/SYS/exe/uc/rs6000_64/R3load -i DOKCLU.cmd -dbcodepage 4102 -l DOKCLU.log -stop_on_error -loadprocedure fast
DbSl Trace: ORA-1403 when accessing table SAPUSER
(DB) INFO: connected to DB
(DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): UTF8
(RTF) ########## WARNING ###########
Without ORDER BY PRIMARY KEY the exported data may be unusable for some databases
(DB) INFO: DOKCLU deleted/truncated #20110128094511
myCluster (127.18.Imp): 650: error when retrieving table description for physical table DOKCLU.
myCluster (127.18.Imp): 651: return code received from nametab is 2
myCluster (127.18.Imp): 294: error when retrieving physical nametab for table DOKCLU.
(CNV) ERROR: data conversion failed. rc = 2
(DB) INFO: disconnected from DB
/usr/sap/MIP/SYS/exe/uc/rs6000_64/R3load: job finished with 1 error(s)
/usr/sap/MIP/SYS/exe/uc/rs6000_64/R3load: END OF LOG: 20110128094511

Hi,
Te problem seems to be a connection to Oracle.
Check the below note :
Note 400241 - Problems with ops$ or sapr3 connect to Oracle
Regards,
Nirmal.k

SAP NetWeaver 7.01 SR1 SP3 ABAP Trial Version ERROR in importing ABAP phase

Hi all,
I am trying to instal this trial version on my computer. I have tried with Windows XP Pro SP2 and with Windows XP Pro SP3 and I get the same error, in both cases, in the phase 18 wich is: Importing ABAP.
These are the errors I get:
Import Monitor jobs: running 1, waiting 27, completed 0, failed 0, total 28.
Import Monitor jobs: running 2, waiting 26, completed 0, failed 0, total 28.
Import Monitor jobs: running 3, waiting 25, completed 0, failed 0, total 28.
Loading of 'DOKCLU' import package: ERROR
Import Monitor jobs: running 2, waiting 25, completed 0, failed 1, total 28.
Loading of 'REPOSRC' import package: ERROR
Import Monitor jobs: running 1, waiting 25, completed 0, failed 2, total 28.
Loading of 'SAPSSEXC_1' import package: ERROR
Import Monitor jobs: running 0, waiting 25, completed 0, failed 3, total 28.
Import Monitor jobs: running 1, waiting 24, completed 0, failed 3, total 28.
Import Monitor jobs: running 2, waiting 23, completed 0, failed 3, total 28.
Import Monitor jobs: running 3, waiting 22, completed 0, failed 3, total 28.
Loading of 'SMIMCONT1' import package: ERROR
Import Monitor jobs: running 2, waiting 22, completed 0, failed 4, total 28.
Loading of 'SAPAPPL1' import package: ERROR
Import Monitor jobs: running 1, waiting 22, completed 0, failed 5, total 28.
Loading of 'SAPAPPL0' import package: ERROR
Import Monitor jobs: running 0, waiting 22, completed 0, failed 6, total 28.
Import Monitor jobs: running 1, waiting 21, completed 0, failed 6, total 28.
Import Monitor jobs: running 2, waiting 20, completed 0, failed 6, total 28.
Import Monitor jobs: running 3, waiting 19, completed 0, failed 6, total 28.
Loading of 'SEOCOMPODF' import package: ERROR
Import Monitor jobs: running 2, waiting 19, completed 0, failed 7, total 28.
Loading of 'SAPNTAB' import package: ERROR
Import Monitor jobs: running 1, waiting 19, completed 0, failed 8, total 28.
Loading of 'SAPAPPL2' import package: ERROR
Import Monitor jobs: running 0, waiting 19, completed 0, failed 9, total 28.
Import Monitor jobs: running 1, waiting 18, completed 0, failed 9, total 28.
Import Monitor jobs: running 2, waiting 17, completed 0, failed 9, total 28.
Import Monitor jobs: running 3, waiting 16, completed 0, failed 9, total 28.
Loading of 'SAPSSEXC_2' import package: ERROR
Import Monitor jobs: running 2, waiting 16, completed 0, failed 10, total 28.
Loading of 'ATAB' import package: ERROR
Import Monitor jobs: running 1, waiting 16, completed 0, failed 11, total 28.
Loading of 'SAPSDIC' import package: ERROR
Import Monitor jobs: running 0, waiting 16, completed 0, failed 12, total 28.
Import Monitor jobs: running 1, waiting 15, completed 0, failed 12, total 28.
Import Monitor jobs: running 2, waiting 14, completed 0, failed 12, total 28.
Import Monitor jobs: running 3, waiting 13, completed 0, failed 12, total 28.
Loading of 'REPOTEXT' import package: ERROR
Import Monitor jobs: running 2, waiting 13, completed 0, failed 13, total 28.
Loading of 'STXL' import package: ERROR
Import Monitor jobs: running 1, waiting 13, completed 0, failed 14, total 28.
Loading of 'SAPSSRC' import package: ERROR
Import Monitor jobs: running 0, waiting 13, completed 0, failed 15, total 28.
Import Monitor jobs: running 1, waiting 12, completed 0, failed 15, total 28.
Import Monitor jobs: running 2, waiting 11, completed 0, failed 15, total 28.
Import Monitor jobs: running 3, waiting 10, completed 0, failed 15, total 28.
Loading of 'WDY_CTLR_COMPO' import package: ERROR
Import Monitor jobs: running 2, waiting 10, completed 0, failed 16, total 28.
Loading of 'SAPSPROT' import package: ERROR
Import Monitor jobs: running 1, waiting 10, completed 0, failed 17, total 28.
Loading of 'SAPSDOCU' import package: ERROR
Import Monitor jobs: running 0, waiting 10, completed 0, failed 18, total 28.
Import Monitor jobs: running 1, waiting 9, completed 0, failed 18, total 28.
Import Monitor jobs: running 2, waiting 8, completed 0, failed 18, total 28.
Import Monitor jobs: running 3, waiting 7, completed 0, failed 18, total 28.
Loading of 'SAPPOOL' import package: ERROR
Import Monitor jobs: running 2, waiting 7, completed 0, failed 19, total 28.
Loading of 'SAPSLEXC' import package: ERROR
Import Monitor jobs: running 1, waiting 7, completed 0, failed 20, total 28.
Loading of 'SAPSLOAD' import package: ERROR
Import Monitor jobs: running 0, waiting 7, completed 0, failed 21, total 28.
Import Monitor jobs: running 1, waiting 6, completed 0, failed 21, total 28.
Import Monitor jobs: running 2, waiting 5, completed 0, failed 21, total 28.
Import Monitor jobs: running 3, waiting 4, completed 0, failed 21, total 28.
Loading of 'SAPDFACT' import package: ERROR
Import Monitor jobs: running 2, waiting 4, completed 0, failed 22, total 28.
Loading of 'SAPDDIM' import package: ERROR
Import Monitor jobs: running 1, waiting 4, completed 0, failed 23, total 28.
Loading of 'SAPCLUST' import package: ERROR
Import Monitor jobs: running 0, waiting 4, completed 0, failed 24, total 28.
Import Monitor jobs: running 1, waiting 3, completed 0, failed 24, total 28.
Import Monitor jobs: running 2, waiting 2, completed 0, failed 24, total 28.
Import Monitor jobs: running 3, waiting 1, completed 0, failed 24, total 28.
Loading of 'SAPUSER' import package: ERROR
Import Monitor jobs: running 2, waiting 1, completed 0, failed 25, total 28.
Loading of 'SAPDODS' import package: ERROR
Import Monitor jobs: running 1, waiting 1, completed 0, failed 26, total 28.
Loading of 'SAP0000' import package: ERROR
Import Monitor jobs: running 0, waiting 1, completed 0, failed 27, total 28.
WARNING[E] 2009-04-10 18:45:34.749
           CJSlibModule::writeError_impl()
CJS-30022 Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.
ERROR      2009-04-10 18:45:34.764 sixxcstepexecute.cpp:950
FCO-00011 The step runMigrationMonitor with step key |NW_ABAP_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|2|0|NW_CreateDBandLoad|ind|ind|ind|ind|9|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 .
I am very new on this so I probably will not understand many technical words.
Please. Can any one tell what´s going on. This is the 5th time I try to instal the program.
Thank you very much in advance.
Regards.

Hi,
I got a similar error while installing Solution Manager 7 EHP1 on Windows/Oracle. Ihave gone through the import log, and the respective logs directed to, and pasted below.
Loading of 'REPOSRC' import package: ERROR
ERROR: 2009-06-18 11:19:40 com.sap.inst.migmon.LoadTask run
Loading of 'REPOSRC' import package is interrupted with R3load error.
Process 'D:\usr\sap\SMN\SYS\exe\uc\NTAMD64\R3load.exe -i REPOSRC.cmd -dbcodepage 4103 -l REPOSRC.log -stop_on_error' exited with return code 2.
For mode details see 'REPOSRC.log' file.
REPOSRC.log
(TSK) ERROR: file C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\ORA\CENTRAL\AS\REPOSRC.TSK.bck already seems to exist
             a previous run may not have been finished cleanly
             file C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\ORA\CENTRAL\AS\REPOSRC.TSK possibly corrupted
D:\usr\sap\SMN\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 1 error(s)
REPOSRC.TSK
REPOSRC.TSK.bck
Upon inspection of the previous .TSK files, i found that it contained a list of Tables to be created: the REPOSRC.TSK.bck was a continuation of the same list. Hence the installation uses/used both to see where it had stopped.
I found a sapnote 455195 (last paragraph) which advises that i run R3load with the -merge option, but how can i do that during the installation process?

Problem while installing ECC6.0 IDES with EP

Hi,
I have successfully installed ECC6.0 IDES with ABAP+JAVA.
Now while installing the same with ABAP+JAVA and with EP &EPC , I am getting the following error while installing.can any one tell me how the problem can be resolved?
Jan 6, 2009 9:54:45 AM   Info: End of log messages of the target system.
Jan 6, 2009 9:54:45 AM   Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Jan 6, 2009 9:54:45 AM   ***Error: Aborted: development component 'irj'/'sap.com'/'SAP AG'/'7.0014.20071112134549.0000'/'1', grouped by software component 'EPBC'/'sap.com'/'SAP AG'/'1000.7.00.14.0.20071210152326''/'1':***
***Caught exception during application deployment from SAP J2EE Engine's deploy API:***
***com.sap.engine.deploy.manager.DeployManagerException: ERROR: NOT deployed. The Deploy Service returned the following error: java.lang.NullPointerException***
***Exception is:***
***java.lang.NullPointerException***        at com.sap.engine.deploy.manager.DeployManagerImpl.deployUpdateAction(DeployManagerImpl.java:666)
        at com.sap.engine.deploy.manager.DeployManagerImpl.deploy(DeployManagerImpl.java:513)
        at com.sap.sdm.serverext.servertype.inqmy.extern.EngineJ2EE620OnlineDeployerImpl.performDeployment(EngineJ2EE620OnlineDeployerImpl.java:332)
        at com.sap.sdm.serverext.servertype.inqmy.extern.EngineDeployerImpl.deploy(EngineDeployerImpl.java:96)
        at com.sap.sdm.serverext.servertype.inqmy.EngineProcessor.executeAction(EngineProcessor.java:224)
        at com.sap.sdm.app.proc.deployment.impl.PhysicalDeploymentActionExecutor.execute(PhysicalDeploymentActionExecutor.java:60)
        at com.sap.sdm.app.proc.deployment.impl.DeploymentActionImpl.execute(DeploymentActionImpl.java:186)
        at com.sap.sdm.app.proc.deployment.controllers.internal.impl.DeploymentExecutorImpl.execute(DeploymentExecutorImpl.java:48)
        at com.sap.sdm.app.proc.deployment.states.eventhandler.ExecuteDeploymentHandler.executeAction(ExecuteDeploymentHandler.java:83)
        at com.sap.sdm.app.proc.deployment.states.eventhandler.ExecuteDeploymentHandler.handleEvent(ExecuteDeploymentHandler.java:60)
        at com.sap.sdm.app.proc.deployment.states.StateBeforeNextDeployment.processEvent(StateBeforeNextDeployment.java:127)
        at com.sap.sdm.app.proc.deployment.states.InstContext.processEventServerSide(InstContext.java:73)
        at com.sap.sdm.app.proc.deployment.states.InstContext.processEvent(InstContext.java:59)
        at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.doPhysicalDeployment(DeployerImpl.java:128)
        at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.deploy(DeployerImpl.java:97)
        at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.deploy(DeployerImpl.java:68)
        at com.sap.sdm.control.command.cmds.Deploy.execute(Deploy.java:179)
        at com.sap.sdm.control.command.decorator.AssureStandaloneMode.execute(AssureStandaloneMode.java:53)
        at com.sap.sdm.control.command.decorator.AssureOneRunningSDMOnly.execute(AssureOneRunningSDMOnly.java:61)
        at com.sap.sdm.control.command.decorator.SDMInitializer.execute(SDMInitializer.java:52)
        at com.sap.sdm.control.command.decorator.GlobalParamEvaluator.execute(GlobalParamEvaluator.java:60)
        at com.sap.sdm.control.command.decorator.AbstractLibDirSetter.execute(AbstractLibDirSetter.java:46)
        at com.sap.sdm.control.command.decorator.ExitPostProcessor.execute(ExitPostProcessor.java:48)
        at com.sap.sdm.control.command.decorator.CommandNameLogger.execute(CommandNameLogger.java:49)
        at com.sap.sdm.control.command.decorator.AdditionalLogFileSetter.execute(AdditionalLogFileSetter.java:65)
        at com.sap.sdm.control.command.decorator.AbstractLogDirSetter.execute(AbstractLogDirSetter.java:54)
        at com.sap.sdm.control.command.decorator.SyntaxChecker.execute(SyntaxChecker.java:37)
        at com.sap.sdm.control.command.Command.exec(Command.java:42)
        at SDM.main(SDM.java:21)
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineJ2EE620OnlineDeployerImpl.performAction(DeploymentActionTypes).DMEXC)
Jan 6, 2009 9:54:45 AM   Info: Starting to save the repository
Jan 6, 2009 9:54:46 AM   Info: Finished saving the repository
Jan 6, 2009 9:54:46 AM   Info: Starting: Initial deployment: Selected software component 'EPBC'/'sap.com'/'SAP AG'/'1000.7.00.14.0.20071210152326''/'1' will be deployed.
Jan 6, 2009 9:54:46 AM   Error: Aborted: software component 'EPBC'/'sap.com'/'SAP AG'/'1000.7.00.14.0.20071210152326''/'1':
Failed deployment of SDAs:
development component 'irj'/'sap.com'/'SAP AG'/'7.0014.20071112134549.0000'/'1' : aborted
Please, look at error logs above for more information!
Jan 6, 2009 9:54:46 AM   Info: Starting to save the repository
Jan 6, 2009 9:54:47 AM   Info: Finished saving the repository
Jan 6, 2009 9:54:47 AM   Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process.
Jan 6, 2009 9:54:47 AM   Error: -
At least one of the Deployments failed -
Jan 6, 2009 9:54:48 AM   Info: Summarizing the deployment results:
Jan 6, 2009 9:54:48 AM   Error: Aborted: /stage/stageecc1/AS_JAVA_DVD/51033513/DATA_UNITS/JAVA_J2EE_OSINDEP_UT/EPBC14_0.SCA
Jan 6, 2009 9:54:48 AM   Error: Admitted: /stage/stageecc1/AS_JAVA_DVD/51033513/DATA_UNITS/JAVA_J2EE_OSINDEP_UT/EPBC214_0.SCA
Jan 6, 2009 9:54:48 AM   Error: Admitted: /stage/stageecc1/AS_JAVA_DVD/51033513/DATA_UNITS/JAVA_J2EE_OSINDEP_UT/EPPSERV14_0.SCA
Jan 6, 2009 9:54:48 AM   Error: Admitted: /stage/stageecc1/AS_JAVA_DVD/51033513/DATA_UNITS/JAVA_J2EE_OSINDEP_UT/EPWDC14_0.SCA
Jan 6, 2009 9:54:48 AM   Error: Admitted: /stage/stageecc1/AS_JAVA_DVD/51033513/DATA_UNITS/JAVA_J2EE_OSINDEP_UT/UWLJWF14_0.SCA
Jan 6, 2009 9:54:48 AM   Error: Admitted: /stage/stageecc1/AS_JAVA_DVD/51033513/DATA_UNITS/JAVA_J2EE_OSINDEP_UT/SAPEU14_0.SCA
Jan 6, 2009 9:54:48 AM   Error: Processing error. Return code: 4
Awaiting for early reply,
Hi ,
I would like to add some of my observations
1. I checked in jcmon that SDM status is showing stopped.
2.I tried to start the SDM by executing the command StartServer.sh and got message that it was started successfully but in jcmon it is still showing as "stopped".
I am not sure whether the above problem is due to this.
Additionally, I would like to mention that my JDK version is 1.4.2_17 and platform is HP-UX11.31
Regards,
Moulinath
Edited by: Moulinath Ray on Jan 6, 2009 8:07 AM
Edited by: Moulinath Ray on Jan 6, 2009 8:08 AM

Hi,
Thank you very much for your reply.
1. I checked the file system.One file system is showing full.
DevFS                   11      11       0 100% /dev/deviceFileSystem
Please let me know how can I reduce it / deletion of which files will not cause any harm?
2. There is space remaining in Database.So, no problem with it.
3. I found the following message from sdm_log
$ tail dev_sdm
[Thr 2] Mon Jan 5 20:47:02 2009
[Thr 2] JLaunchRequestFunc: receive command:17, argument:0 from pid:14451
[Thr 2] JLaunchIShutdownInvoke: set shutdown interval (stop:1231168622/end:1231168742/TO:120)
[Thr 2] JLaunchProcessCommand: Invoke VM Shutdown
[Thr 2] JHVM_FrameworkShutdownDirect: invoke direct shutdown
[Thr 2] JLaunchISetState: change state from [Running (3)] to [Stopping (5)]
[Thr 6] JLaunchIExitJava: exit hook is called (rc = 0)
[Thr 6] SigISetIgnoreAction : SIG_IGN for signal 18
[Thr 6] JLaunchCloseProgram: good bye (exitcode = 0)
4. In jcmon also, the status is showing as stopped.
5. I tried to start the SDM by executing command Startserver.sh fron /usr/sap/<SID>/DVEBMGS00/SDM/program
But it is not starting.The process is getting hanged.
$ ./StartServer.sh
running on HP-UX better use the '-XdoCloseWithReadPending' option
Starting SDM - Software Deployment Manager...
tc/SL/SDM/SDM/sap.com/SAP AG/7.0014.20071029094708.0000
JStartupFramework is active
Operation mode of SDM in JStartupFramework is "Standalone". Simply start the server.
Initializing Network Manager (50017)
Starting SDM Server listening on port 50018
SDM started successfully.
Redirecting output to the two files "/usr/sap/IN1/DVEBMGS00/SDM/program/log/sdm_server.out" and "/usr/sap/IN1/DVEBMGS00/SDM/program/log/sdm_server.err" respectively.
6. One more point to mention is that the value of one kernel parameter "nkthread" is not matching with prescribed value>=10000. But I could not change the value and so proceeded with the installation.Can this be a root cause? While installing ECC only with ABAP+JAVA , I did not find any problem but this time I am facing the problem.
Please let me know your valueable inputs.
Thanks and Regards,
Moulianth
N.B. I just now checked the file system size of my ECC6.0 installation with ABAP+JAVA which finished successfully.There also the device file system was full.So, it seems that this is not the problem.
Edited by: Moulinath Ray on Jan 7, 2009 5:21 AM

Error in import ABAP while installing ECC6.0 on I5/os

Similar Messages

Maybe you are looking for