4.0B to ECC 6.0; SPDD in PREPARE or UPGRADE phase?
Hi Gurus,
I am working on an upgrade from R/3 4.0 to ECC 6.0. I worked on pgrades before but am alien 4.0B. BTW, from a Developer perspective:
1) SPDD adjustments are done in which phase? PREPARE or UPGRADE?
2) Are here special cases where the adjustments need to be done before running the UPGRADE phase?
Helpful Answers will be rewarded
Hi Karthik
>
> 1) SPDD adjustments are done in which phase? PREPARE or UPGRADE?
>
SPDD is done in Upgrade ->Phase ACT_700
> 2) Are here special cases where the adjustments need to be done before running the UPGRADE phase?
>
At ACT_700 phase stop the upgrade and take a backup of the DB and the PUT<DIR> before starting the SPDD activity.
Make sure there are no pending tp request. Either release them or delete them.
All phase need to be completed successfully in PREPARE, before starting UPGRADE
Cheers
Shaji
Edited by: Shaji Jacob on May 5, 2008 9:23 PM
Similar Messages
-
Hi,
while upgrading ECC 4.7 to ECC 6.0, I am not able to start shadow instance. Following error is giving .
Aditionally I can able to open the shadow instance from GUI lavel. But unable to login through DDIC password. The ddic password has been locked. Can anyone advice me how to unlock the ddic password in the upgrade phase.
Starting shadow system ...
waiting 20 seconds for system to come up ...
testing if system is available ...
waiting 20 seconds for system to come up ...
testing if system is available ...
waiting 20 seconds for system to come up ...
testing if system is available ...
waiting 20 seconds for system to come up ...
testing if system is available ...
waiting 20 seconds for system to come up ...
testing if system is available ...
waiting 20 seconds for system to come up ...
testing if system is available ...
SAPup error message
SAPup> ERROR: Starting system failed, rc=0
To analyse the errors during start of shadow instance,
view files 'STARTSFI.LOG' and 'DEVTRACE.LOG'
in directory '/dsttemp/put/log'
Repeat phase until shadow instance is started
and you can log on instance number '21'.
- "continue"
- "cancel"
Enter one of these options [continue] :=
===============================================
===============================================
ERROR in PHASE STARTSAP_IMP
================================
=================================
SAPup> CHECKS AFTER UPGRADE PHASE STARTSAP_IMP WERE NEGATIVE !!!
It is recommended that you repeat phase STARTSAP_IMP
You can exit and restart the phase after the errors
have been corrected. Alternatively, if you know that
the error is not of concern, you may ignore it
and continue with phase REPACHK2
You are urged to repeat phase STARTSAP_IMP !
- "repeat"
- "init"
- "exit"
- "ignore"
Enter one of these options [repeat] := init
14:50:31 UPGRADE/EUIM: END OF PHASE STARTSAP_IMP
14:50:31 UPGRADE/EUIM: START OF PHASE STARTSAP_IMP
Starting system ...
waiting 20 seconds for system to come up ...
testing if system is available ...
waiting 20 seconds for system to come up ...
testing if system is available ...
waiting 20 seconds for system to come up ...
testing if system is available ...
waiting 20 seconds for system to come up ...
testing if system is available ...
waiting 20 seconds for system to come up ...
testing if system is available ...
waiting 20 seconds for system to come up ...
testing if system is available ...
SAPup error message
SAPup> SYSTEM START failed, code -2
-2: the test rfc did not work.
Try to log on to the system with user DDIC.
- "continue"
- "cancel"
Enter one of these options or "help" [continue] :=
Enter one of these options or "help" [continue] :=
SAPup message
SAPup> CHECKS AFTER UPGRADE PHASE STARTSAP_IMP WERE NEGATIVE !!!
It is recommended that you repeat phase STARTSAP_IMP
You can exit and restart the phase after the errors
have been corrected. Alternatively, if you know that
the error is not of concern, you may ignore it
and continue with phase REPACHK2
You are urged to repeat phase STARTSAP_IMP !
- "repeat"
- "init"
- "exit"
- "ignore"
Enter one of these options [repeat] :=
Appreciate for an immediate response ...
Thanks in advancewhile upgrading ECC 4.7 to ECC 6.0, I am not able to start shadow instance. Following error is giving .
Aditionally I can able to open the shadow instance from GUI lavel. But unable to login through DDIC password. The ddic password has been locked. Can anyone advice me how to unlock the ddic password in the upgrade phase.
This doesn´t make sense. If you can´t start the shadow instance then you can´t logon to the system
Try the following:
cd <put-directory>/bin
./SAPup stopshd
set the parameter
login/no_automatic_user_sapstar = 0
in the instance profile of the shadown instance
then start the shadow instance
cd <put-directory>/bin
./SAPup startshd
Unlock the shadow instance using
./SAPup unlockshd
Try to logon with user SAP* and unlock DDIC.
Markus -
Hi,
We are upgrading from 46c to ecc 6.0. Now we completed the Development upgrade and upgading QA.
We did SPDD during upgrade and we did not get umodauto.lst fine in ../bin directory.
Now I want to know the exact process to get umodauto.lst file and transport request.
We are upgrading QA and here we plan to do SPDD once again and we want to make umodauto.lst available for further upgrades.
pl. suggest up.
In SPDD we did changes and system prompted for transport request.
We did not release TR or tasks in TR.
now tell us how do we do this.Hi
If you choose strategy downtime-minimized, the ABAP Dictionary objects (tables, data elements, domains, and so on) are adjusted during production operation. If you choose
strategy resource-minimized, they are adjusted during downtime before the ABAP Dictionary is activated. The adjusted objects are collected in a repair that is released to
a transport request. You cannot release this transport request; instead you must flag it for transport in transaction SPDD. Towards the end of the upgrade, SAPup exports the request to the transport directory /usr/sap/trans and registers it for transport in the umodauto.lst file.
Once it registers in umodauto.lst. For the later upgrade boxes -> In PREPARE phase ADJUSTPRP the following screen appears
For automatically maintaining your modification in your ystem during the upgrade transport request from earlier upgrades are searched in the umoauto.lst in directory /usr/sap/trans/bin..
The file could not be read
There are several reason why this may be correct
eg: 'this is your first upgrade' or 'your system is not modified'.
Did you expect a list of transports being found?
->Confirm a list of transports to be included in the upgrade
Select Yes & OK
view umodauto.lst , should list as below eg:
SPDD 700 SIDK100001
Click on Yes to include the transport
Click Yes to stop the ACT_700 phase and check the results of SPDD -
ECC 6.0 Installation fails during Import ABAP Phase
Hi,
I am tryiing to install ECC 6.0 on windows 2003:Oracle and it is failing at phase 17 Import Abap with the following error:
ERROR 2007-11-13 16:04:09
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-11-13 16:04:09
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 .
here is the import_monitor.java.log file:
ava version "1.4.2_14"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_14-b05)
Java HotSpot(TM) Client VM (build 1.4.2_14-b05, mixed mode)
Import Monitor jobs: running 1, waiting 37, completed 0, failed 0, total 38.
Loading of 'SAPNTAB' import package: OK
Import Monitor jobs: running 0, waiting 37, completed 1, failed 0, total 38.
Import Monitor jobs: running 1, waiting 36, completed 1, failed 0, total 38.
Import Monitor jobs: running 2, waiting 35, completed 1, failed 0, total 38.
Import Monitor jobs: running 3, waiting 34, completed 1, failed 0, total 38.
Loading of 'SAPSSEXC_4' import package: OK
Import Monitor jobs: running 2, waiting 34, completed 2, failed 0, total 38.
Import Monitor jobs: running 3, waiting 33, completed 2, failed 0, total 38.
Loading of 'DOKCLU' import package: OK
Import Monitor jobs: running 2, waiting 33, completed 3, failed 0, total 38.
Import Monitor jobs: running 3, waiting 32, completed 3, failed 0, total 38.
Loading of 'SAPAPPL2_1' import package: OK
Import Monitor jobs: running 2, waiting 32, completed 4, failed 0, total 38.
Import Monitor jobs: running 3, waiting 31, completed 4, failed 0, total 38.
Loading of 'SAPSSEXC_2' import package: OK
Import Monitor jobs: running 2, waiting 31, completed 5, failed 0, total 38.
Import Monitor jobs: running 3, waiting 30, completed 5, failed 0, total 38.
Loading of 'DD03L' import package: OK
Import Monitor jobs: running 2, waiting 30, completed 6, failed 0, total 38.
Import Monitor jobs: running 3, waiting 29, completed 6, failed 0, total 38.
Loading of 'SAPAPPL1_1' import package: OK
Import Monitor jobs: running 2, waiting 29, completed 7, failed 0, total 38.
Import Monitor jobs: running 3, waiting 28, completed 7, failed 0, total 38.
Loading of 'SAPSSEXC_1' import package: OK
Import Monitor jobs: running 2, waiting 28, completed 8, failed 0, total 38.
Import Monitor jobs: running 3, waiting 27, completed 8, failed 0, total 38.
Loading of 'SAPAPPL0_3' import package: OK
Import Monitor jobs: running 2, waiting 27, completed 9, failed 0, total 38.
Import Monitor jobs: running 3, waiting 26, completed 9, failed 0, total 38.
Loading of 'SAPAPPL1_2' import package: OK
Import Monitor jobs: running 2, waiting 26, completed 10, failed 0, total 38.
Loading of 'SAPAPPL2_2' import package: OK
Import Monitor jobs: running 1, waiting 26, completed 11, failed 0, total 38.
Import Monitor jobs: running 2, waiting 25, completed 11, failed 0, total 38.
Import Monitor jobs: running 3, waiting 24, completed 11, failed 0, total 38.
Loading of 'SCPRSVALS' import package: OK
Import Monitor jobs: running 2, waiting 24, completed 12, failed 0, total 38.
Import Monitor jobs: running 3, waiting 23, completed 12, failed 0, total 38.
Loading of 'SAPAPPL0_1' import package: OK
Import Monitor jobs: running 2, waiting 23, completed 13, failed 0, total 38.
Import Monitor jobs: running 3, waiting 22, completed 13, failed 0, total 38.
Loading of 'SAPAPPL2_3' import package: ERROR
Import Monitor jobs: running 2, waiting 22, completed 13, failed 1, total 38.
Loading of 'SAPSSEXC_3' import package: ERROR
Import Monitor jobs: running 1, waiting 22, completed 13, failed 2, total 38.
Import Monitor jobs: running 2, waiting 21, completed 13, failed 2, total 38.
Import Monitor jobs: running 3, waiting 20, completed 13, failed 2, total 38.
Loading of 'SAPSSEXC_5' import package: ERROR
Import Monitor jobs: running 2, waiting 20, completed 13, failed 3, total 38.
Loading of 'SAPAPPL0_2' import package: ERROR
Import Monitor jobs: running 1, waiting 20, completed 13, failed 4, total 38.
Import Monitor jobs: running 2, waiting 19, completed 13, failed 4, total 38.
Import Monitor jobs: running 3, waiting 18, completed 13, failed 4, total 38.
Loading of 'FUPARAREF' import package: ERROR
Import Monitor jobs: running 2, waiting 18, completed 13, failed 5, total 38.
Import Monitor jobs: running 3, waiting 17, completed 13, failed 5, total 38.
Loading of 'TODIR' import package: ERROR
Import Monitor jobs: running 2, waiting 17, completed 13, failed 6, total 38.
Import Monitor jobs: running 3, waiting 16, completed 13, failed 6, total 38.
Loading of 'SAPSDIC' import package: ERROR
Import Monitor jobs: running 2, waiting 16, completed 13, failed 7, total 38.
Import Monitor jobs: running 3, waiting 15, completed 13, failed 7, total 38.
Loading of 'SEOSUBCODF' import package: OK
Import Monitor jobs: running 2, waiting 15, completed 14, failed 7, total 38.
Loading of 'SAPSSRC' import package: ERROR
Import Monitor jobs: running 1, waiting 15, completed 14, failed 8, total 38.
Loading of 'E071K' import package: ERROR
Import Monitor jobs: running 0, waiting 15, completed 14, failed 9, total 38.
Import Monitor jobs: running 1, waiting 14, completed 14, failed 9, total 38.
Import Monitor jobs: running 2, waiting 13, completed 14, failed 9, total 38.
Import Monitor jobs: running 3, waiting 12, completed 14, failed 9, total 38.
Loading of 'SAPSPROT' import package: OK
Import Monitor jobs: running 2, waiting 12, completed 15, failed 9, total 38.
Import Monitor jobs: running 3, waiting 11, completed 15, failed 9, total 38.
Loading of 'SAPPOOL' import package: ERROR
Import Monitor jobs: running 2, waiting 11, completed 15, failed 10, total 38.
Loading of 'SCPRVALS' import package: OK
Import Monitor jobs: running 1, waiting 11, completed 16, failed 10, total 38.
Loading of 'SAPSDOCU' import package: OK
Import Monitor jobs: running 0, waiting 11, completed 17, failed 10, total 38.
Import Monitor jobs: running 1, waiting 10, completed 17, failed 10, total 38.
Import Monitor jobs: running 2, waiting 9, completed 17, failed 10, total 38.
Import Monitor jobs: running 3, waiting 8, completed 17, failed 10, total 38.
Loading of 'SAPSLEXC' import package: ERROR
Import Monitor jobs: running 2, waiting 8, completed 17, failed 11, total 38.
Loading of 'SAPCLUST' import package: OK
Import Monitor jobs: running 1, waiting 8, completed 18, failed 11, total 38.
Import Monitor jobs: running 2, waiting 7, completed 18, failed 11, total 38.
Import Monitor jobs: running 3, waiting 6, completed 18, failed 11, total 38.
Loading of 'SAPAPPL0_4' import package: ERROR
Import Monitor jobs: running 2, waiting 6, completed 18, failed 12, total 38.
Loading of 'SAPUSER' import package: ERROR
Import Monitor jobs: running 1, waiting 6, completed 18, failed 13, total 38.
Loading of 'SAPSLOAD' import package: OK
Import Monitor jobs: running 0, waiting 6, completed 19, failed 13, total 38.
Import Monitor jobs: running 1, waiting 5, completed 19, failed 13, total 38.
Import Monitor jobs: running 2, waiting 4, completed 19, failed 13, total 38.
Import Monitor jobs: running 3, waiting 3, completed 19, failed 13, total 38.
Loading of 'SAPDDIM' import package: OK
Import Monitor jobs: running 2, waiting 3, completed 20, failed 13, total 38.
Loading of 'SAPDFACT' import package: OK
Import Monitor jobs: running 1, waiting 3, completed 21, failed 13, total 38.
Loading of 'SAPDODS' import package: OK
Import Monitor jobs: running 0, waiting 3, completed 22, failed 13, total 38.
Import Monitor jobs: running 1, waiting 2, completed 22, failed 13, total 38.
Import Monitor jobs: running 2, waiting 1, completed 22, failed 13, total 38.
Loading of 'SAPUSER1' import package: OK
Import Monitor jobs: running 1, waiting 1, completed 23, failed 13, total 38.
Loading of 'SAP0000' import package: OK
Import Monitor jobs: running 0, waiting 1, completed 24, failed 13, total 38.
here is a copy of import_monitor.log
INFO: 2007-11-13 14:02:09
Import Monitor is started.
CONFIG: 2007-11-13 14:02:09
Application options:
dbCodepage=4103
dbType=ORA
extFiles=yes
importDirs=C:\sapcds\inst_exp\exp1\EXP1;C:\sapcds\inst_exp\exp1\EXP2;C:\sapcds\inst_exp\exp1\EXP3;C:\sapcds\inst_exp\exp1\EXP4;C:\sapcds\inst_exp\exp1\EXP5;C:\sapcds\inst_exp\exp1\EXP6;C:\sapcds\inst_exp\exp2\EXP7;C:\sapcds\inst_exp\exp2\EXP8;C:\sapcds\inst_exp\exp2\EXP9;C:\sapcds\inst_exp\exp2\EXP10;C:\sapcds\inst_exp\exp2\EXP11
installDir=C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS
jobNum=3
loadArgs= -stop_on_error
monitorTimeout=30
orderBy=
r3loadExe=E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe
sapinst=
trace=all
tskFiles=yes
CONFIG: 2007-11-13 14:02:09
List of packages with table structure: 'SAP0000'.
CONFIG: 2007-11-13 14:02:09
List of packages with views: 'SAPVIEW'.
TRACE: 2007-11-13 14:02:09 com.sap.inst.migmon.imp.ImportStandardTask preCreate
Parse of 'C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL' template file is started.
INFO: 2007-11-13 14:02:09 com.sap.inst.migmon.imp.ImportStandardTask preCreate
Parse of 'C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL' template file is successfully completed.
Primary key creation: after load.
Index creation: after load.
INFO: 2007-11-13 14:02:10
Data codepage 1100 is determined using TOC file 'C:\sapcds\inst_exp\exp1\EXP1\DATA\SAPSSEXC_3.TOC' for package 'SAPSSEXC_3'.
INFO: 2007-11-13 14:02:12
Version table 'SVERS' is found in STR file 'C:\sapcds\inst_exp\exp2\EXP10\DATA\SAPNTAB.STR' from package 'SAPNTAB'.
INFO: 2007-11-13 14:02:12
Data conversion tables 'DDNTF,DDNTF_CONV_UC,DDNTT,DDNTT_CONV_UC' are found in STR file 'C:\sapcds\inst_exp\exp2\EXP10\DATA\SAPNTAB.STR' from package 'SAPNTAB'.
TRACE: 2007-11-13 14:02:12 com.sap.inst.migmon.LoadTask run
Loading of 'SAPNTAB' import package is started.
TRACE: 2007-11-13 14:02:12 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPNTAB' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp2\EXP10\DATA\SAPNTAB.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPNTAB.TSK ORA -l SAPNTAB.log
TRACE: 2007-11-13 14:02:12 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPNTAB' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPNTAB.cmd -dbcodepage 4103 -l SAPNTAB.log -stop_on_error
INFO: 2007-11-13 14:13:11 com.sap.inst.migmon.LoadTask run
Loading of 'SAPNTAB' import package is successfully completed.
TRACE: 2007-11-13 14:13:39 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC_3' import package is started.
TRACE: 2007-11-13 14:13:39 com.sap.inst.migmon.LoadTask run
Loading of 'DOKCLU' import package is started.
TRACE: 2007-11-13 14:13:39 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC_4' import package is started.
TRACE: 2007-11-13 14:13:39 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPSSEXC_3' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp1\EXP1\DATA\SAPSSEXC_3.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPSSEXC_3.TSK ORA -l SAPSSEXC_3.log
TRACE: 2007-11-13 14:13:39 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPSSEXC_4' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp1\EXP3\DATA\SAPSSEXC_4.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPSSEXC_4.TSK ORA -l SAPSSEXC_4.log
TRACE: 2007-11-13 14:13:39 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'DOKCLU' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp2\EXP11\DATA\DOKCLU.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" DOKCLU.TSK ORA -l DOKCLU.log
TRACE: 2007-11-13 14:13:39 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPSSEXC_3' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPSSEXC_3.cmd -dbcodepage 4103 -l SAPSSEXC_3.log -stop_on_error
TRACE: 2007-11-13 14:13:39 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPSSEXC_4' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPSSEXC_4.cmd -dbcodepage 4103 -l SAPSSEXC_4.log -stop_on_error
TRACE: 2007-11-13 14:13:39 com.sap.inst.migmon.LoadTask processPackage
Loading of 'DOKCLU' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i DOKCLU.cmd -dbcodepage 4103 -l DOKCLU.log -stop_on_error
INFO: 2007-11-13 14:28:45 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC_4' import package is successfully completed.
TRACE: 2007-11-13 14:29:09 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC_2' import package is started.
TRACE: 2007-11-13 14:29:09 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPSSEXC_2' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp1\EXP3\DATA\SAPSSEXC_2.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPSSEXC_2.TSK ORA -l SAPSSEXC_2.log
TRACE: 2007-11-13 14:29:10 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPSSEXC_2' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPSSEXC_2.cmd -dbcodepage 4103 -l SAPSSEXC_2.log -stop_on_error
INFO: 2007-11-13 14:34:56 com.sap.inst.migmon.LoadTask run
Loading of 'DOKCLU' import package is successfully completed.
TRACE: 2007-11-13 14:35:09 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL2_1' import package is started.
TRACE: 2007-11-13 14:35:09 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPAPPL2_1' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp2\EXP8\DATA\SAPAPPL2_1.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPAPPL2_1.TSK ORA -l SAPAPPL2_1.log
TRACE: 2007-11-13 14:35:12 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPAPPL2_1' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL2_1.cmd -dbcodepage 4103 -l SAPAPPL2_1.log -stop_on_error
INFO: 2007-11-13 15:02:33 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL2_1' import package is successfully completed.
TRACE: 2007-11-13 15:02:39 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL1_1' import package is started.
TRACE: 2007-11-13 15:02:39 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPAPPL1_1' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp2\EXP7\DATA\SAPAPPL1_1.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPAPPL1_1.TSK ORA -l SAPAPPL1_1.log
TRACE: 2007-11-13 15:02:43 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPAPPL1_1' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL1_1.cmd -dbcodepage 4103 -l SAPAPPL1_1.log -stop_on_error
INFO: 2007-11-13 15:08:06 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC_2' import package is successfully completed.
TRACE: 2007-11-13 15:08:09 com.sap.inst.migmon.LoadTask run
Loading of 'DD03L' import package is started.
TRACE: 2007-11-13 15:08:09 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'DD03L' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp2\EXP9\DATA\DD03L.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" DD03L.TSK ORA -l DD03L.log
TRACE: 2007-11-13 15:08:09 com.sap.inst.migmon.LoadTask processPackage
Loading of 'DD03L' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i DD03L.cmd -dbcodepage 4103 -l DD03L.log -stop_on_error
INFO: 2007-11-13 15:19:29 com.sap.inst.migmon.LoadTask run
Loading of 'DD03L' import package is successfully completed.
TRACE: 2007-11-13 15:19:39 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC_1' import package is started.
TRACE: 2007-11-13 15:19:39 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPSSEXC_1' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp1\EXP3\DATA\SAPSSEXC_1.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPSSEXC_1.TSK ORA -l SAPSSEXC_1.log
TRACE: 2007-11-13 15:19:39 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPSSEXC_1' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPSSEXC_1.cmd -dbcodepage 4103 -l SAPSSEXC_1.log -stop_on_error
INFO: 2007-11-13 15:22:34 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL1_1' import package is successfully completed.
TRACE: 2007-11-13 15:22:39 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL2_2' import package is started.
TRACE: 2007-11-13 15:22:39 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPAPPL2_2' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp2\EXP8\DATA\SAPAPPL2_2.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPAPPL2_2.TSK ORA -l SAPAPPL2_2.log
TRACE: 2007-11-13 15:22:42 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPAPPL2_2' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL2_2.cmd -dbcodepage 4103 -l SAPAPPL2_2.log -stop_on_error
INFO: 2007-11-13 15:24:18 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC_1' import package is successfully completed.
TRACE: 2007-11-13 15:24:39 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL0_3' import package is started.
TRACE: 2007-11-13 15:24:39 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPAPPL0_3' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp2\EXP7\DATA\SAPAPPL0_3.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPAPPL0_3.TSK ORA -l SAPAPPL0_3.log
TRACE: 2007-11-13 15:24:40 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPAPPL0_3' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL0_3.cmd -dbcodepage 4103 -l SAPAPPL0_3.log -stop_on_error
INFO: 2007-11-13 15:34:21 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL0_3' import package is successfully completed.
TRACE: 2007-11-13 15:34:39 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL1_2' import package is started.
TRACE: 2007-11-13 15:34:39 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPAPPL1_2' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp2\EXP7\DATA\SAPAPPL1_2.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPAPPL1_2.TSK ORA -l SAPAPPL1_2.log
TRACE: 2007-11-13 15:34:41 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPAPPL1_2' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL1_2.cmd -dbcodepage 4103 -l SAPAPPL1_2.log -stop_on_error
INFO: 2007-11-13 15:45:42 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL1_2' import package is successfully completed.
INFO: 2007-11-13 15:46:06 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL2_2' import package is successfully completed.
TRACE: 2007-11-13 15:46:09 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL0_1' import package is started.
TRACE: 2007-11-13 15:46:09 com.sap.inst.migmon.LoadTask run
Loading of 'SCPRSVALS' import package is started.
TRACE: 2007-11-13 15:46:09 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPAPPL0_1' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp2\EXP7\DATA\SAPAPPL0_1.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPAPPL0_1.TSK ORA -l SAPAPPL0_1.log
TRACE: 2007-11-13 15:46:09 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SCPRSVALS' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp1\EXP6\DATA\SCPRSVALS.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SCPRSVALS.TSK ORA -l SCPRSVALS.log
TRACE: 2007-11-13 15:46:09 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SCPRSVALS' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SCPRSVALS.cmd -dbcodepage 4103 -l SCPRSVALS.log -stop_on_error
TRACE: 2007-11-13 15:46:10 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPAPPL0_1' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL0_1.cmd -dbcodepage 4103 -l SAPAPPL0_1.log -stop_on_error
INFO: 2007-11-13 15:51:35 com.sap.inst.migmon.LoadTask run
Loading of 'SCPRSVALS' import package is successfully completed.
TRACE: 2007-11-13 15:51:39 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL2_3' import package is started.
TRACE: 2007-11-13 15:51:39 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPAPPL2_3' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp2\EXP8\DATA\SAPAPPL2_3.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPAPPL2_3.TSK ORA -l SAPAPPL2_3.log
TRACE: 2007-11-13 15:51:41 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPAPPL2_3' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL2_3.cmd -dbcodepage 4103 -l SAPAPPL2_3.log -stop_on_error
INFO: 2007-11-13 15:56:27 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL0_1' import package is successfully completed.
TRACE: 2007-11-13 15:56:39 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL0_2' import package is started.
TRACE: 2007-11-13 15:56:39 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPAPPL0_2' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp2\EXP7\DATA\SAPAPPL0_2.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPAPPL0_2.TSK ORA -l SAPAPPL0_2.log
TRACE: 2007-11-13 15:56:43 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPAPPL0_2' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL0_2.cmd -dbcodepage 4103 -l SAPAPPL0_2.log -stop_on_error
ERROR: 2007-11-13 15:56:48 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL2_3' import package is interrupted with R3load error.
Process 'E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL2_3.cmd -dbcodepage 4103 -l SAPAPPL2_3.log -stop_on_error' exited with return code 2.
For mode details see 'SAPAPPL2_3.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
ERROR: 2007-11-13 15:56:51 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC_3' import package is interrupted with R3load error.
Process 'E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPSSEXC_3.cmd -dbcodepage 4103 -l SAPSSEXC_3.log -stop_on_error' exited with return code 2.
For mode details see 'SAPSSEXC_3.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
TRACE: 2007-11-13 15:57:09 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSDIC' import package is started.
TRACE: 2007-11-13 15:57:09 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC_5' import package is started.
TRACE: 2007-11-13 15:57:09 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPSSEXC_5' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp1\EXP3\DATA\SAPSSEXC_5.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPSSEXC_5.TSK ORA -l SAPSSEXC_5.log
TRACE: 2007-11-13 15:57:09 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPSDIC' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp2\EXP9\DATA\SAPSDIC.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPSDIC.TSK ORA -l SAPSDIC.log
TRACE: 2007-11-13 15:57:10 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPSSEXC_5' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPSSEXC_5.cmd -dbcodepage 4103 -l SAPSSEXC_5.log -stop_on_error
TRACE: 2007-11-13 15:57:10 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPSDIC' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPSDIC.cmd -dbcodepage 4103 -l SAPSDIC.log -stop_on_error
ERROR: 2007-11-13 15:57:11 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC_5' import package is interrupted with R3load error.
Process 'E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPSSEXC_5.cmd -dbcodepage 4103 -l SAPSSEXC_5.log -stop_on_error' exited with return code 2.
For mode details see 'SAPSSEXC_5.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
ERROR: 2007-11-13 15:57:11 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL0_2' import package is interrupted with R3load error.
Process 'E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL0_2.cmd -dbcodepage 4103 -l SAPAPPL0_2.log -stop_on_error' exited with return code 2.
For mode details see 'SAPAPPL0_2.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
TRACE: 2007-11-13 15:57:39 com.sap.inst.migmon.LoadTask run
Loading of 'FUPARAREF' import package is started.
TRACE: 2007-11-13 15:57:39 com.sap.inst.migmon.LoadTask run
Loading of 'TODIR' import package is started.
TRACE: 2007-11-13 15:57:39 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'FUPARAREF' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp1\EXP6\DATA\FUPARAREF.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" FUPARAREF.TSK ORA -l FUPARAREF.log
TRACE: 2007-11-13 15:57:39 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'TODIR' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp1\EXP6\DATA\TODIR.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" TODIR.TSK ORA -l TODIR.log
TRACE: 2007-11-13 15:57:39 com.sap.inst.migmon.LoadTask processPackage
Loading of 'TODIR' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i TODIR.cmd -dbcodepage 4103 -l TODIR.log -stop_on_error
TRACE: 2007-11-13 15:57:39 com.sap.inst.migmon.LoadTask processPackage
Loading of 'FUPARAREF' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i FUPARAREF.cmd -dbcodepage 4103 -l FUPARAREF.log -stop_on_error
ERROR: 2007-11-13 15:57:40 com.sap.inst.migmon.LoadTask run
Loading of 'FUPARAREF' import package is interrupted with R3load error.
Process 'E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i FUPARAREF.cmd -dbcodepage 4103 -l FUPARAREF.log -stop_on_error' exited with return code 2.
For mode details see 'FUPARAREF.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
TRACE: 2007-11-13 15:58:09 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSRC' import package is started.
TRACE: 2007-11-13 15:58:09 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPSSRC' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp1\EXP6\DATA\SAPSSRC.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPSSRC.TSK ORA -l SAPSSRC.log
TRACE: 2007-11-13 15:58:09 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPSSRC' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPSSRC.cmd -dbcodepage 4103 -l SAPSSRC.log -stop_on_error
ERROR: 2007-11-13 15:58:10 com.sap.inst.migmon.LoadTask run
Loading of 'TODIR' import package is interrupted with R3load error.
Process 'E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i TODIR.cmd -dbcodepage 4103 -l TODIR.log -stop_on_error' exited with return code 2.
For mode details see 'TODIR.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
TRACE: 2007-11-13 15:58:39 com.sap.inst.migmon.LoadTask run
Loading of 'SEOSUBCODF' import package is started.
TRACE: 2007-11-13 15:58:39 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SEOSUBCODF' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp1\EXP6\DATA\SEOSUBCODF.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SEOSUBCODF.TSK ORA -l SEOSUBCODF.log
TRACE: 2007-11-13 15:58:39 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SEOSUBCODF' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SEOSUBCODF.cmd -dbcodepage 4103 -l SEOSUBCODF.log -stop_on_error
ERROR: 2007-11-13 15:58:40 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSDIC' import package is interrupted with R3load error.
Process 'E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPSDIC.cmd -dbcodepage 4103 -l SAPSDIC.log -stop_on_error' exited with return code 2.
For mode details see 'SAPSDIC.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
TRACE: 2007-11-13 15:59:09 com.sap.inst.migmon.LoadTask run
Loading of 'E071K' import package is started.
TRACE: 2007-11-13 15:59:09 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'E071K' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp1\EXP6\DATA\E071K.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" E071K.TSK ORA -l E071K.log
TRACE: 2007-11-13 15:59:09 com.sap.inst.migmon.LoadTask processPackage
Loading of 'E071K' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i E071K.cmd -dbcodepage 4103 -l E071K.log -stop_on_error
INFO: 2007-11-13 16:00:13 com.sap.inst.migmon.LoadTask run
Loading of 'SEOSUBCODF' import package is successfully completed.
ERROR: 2007-11-13 16:00:31 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSRC' import package is interrupted with R3load error.
Process 'E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPSSRC.cmd -dbcodepage 4103 -l SAPSSRC.log -stop_on_error' exited with return code 2.
For mode details see 'SAPSSRC.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
ERROR: 2007-11-13 16:00:31 com.sap.inst.migmon.LoadTask run
Loading of 'E071K' import package is interrupted with R3load error.
Process 'E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i E071K.cmd -dbcodepage 4103 -l E071K.log -stop_on_error' exited with return code 2.
For mode details see 'E071K.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
TRACE: 2007-11-13 16:00:39 com.sap.inst.migmon.LoadTask run
Loading of 'SAPPOOL' import package is started.
TRACE: 2007-11-13 16:00:39 com.sap.inst.migmon.LoadTask run
Loading of 'SCPRVALS' import package is started.
TRACE: 2007-11-13 16:00:39 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSPROT' import package is started.
TRACE: 2007-11-13 16:00:39 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SCPRVALS' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp1\EXP6\DATA\SCPRVALS.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SCPRVALS.TSK ORA -l SCPRVALS.log
TRACE: 2007-11-13 16:00:39 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPPOOL' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp1\EXP6\DATA\SAPPOOL.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPPOOL.TSK ORA -l SAPPOOL.log
TRACE: 2007-11-13 16:00:39 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPSPROT' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp1\EXP5\DATA\SAPSPROT.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPSPROT.TSK ORA -l SAPSPROT.log
TRACE: 2007-11-13 16:00:39 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SCPRVALS' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SCPRVALS.cmd -dbcodepage 4103 -l SCPRVALS.log -stop_on_error
TRACE: 2007-11-13 16:00:39 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPPOOL' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPPOOL.cmd -dbcodepage 4103 -l SAPPOOL.log -stop_on_error
TRACE: 2007-11-13 16:00:39 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPSPROT' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPSPROT.cmd -dbcodepage 4103 -l SAPSPROT.log -stop_on_error
INFO: 2007-11-13 16:01:20 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSPROT' import package is successfully completed.
TRACE: 2007-11-13 16:01:39 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSDOCU' import package is started.
TRACE: 2007-11-13 16:01:39 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPSDOCU' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp1\EXP4\DATA\SAPSDOCU.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPSDOCU.TSK ORA -l SAPSDOCU.log
TRACE: 2007-11-13 16:01:40 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPSDOCU' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPSDOCU.cmd -dbcodepage 4103 -l SAPSDOCU.log -stop_on_error
ERROR: 2007-11-13 16:01:40 com.sap.inst.migmon.LoadTask run
Loading of 'SAPPOOL' import package is interrupted with R3load error.
Process 'E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPPOOL.cmd -dbcodepage 4103 -l SAPPOOL.log -stop_on_error' exited with return code 2.
For mode details see 'SAPPOOL.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
INFO: 2007-11-13 16:01:57 com.sap.inst.migmon.LoadTask run
Loading of 'SCPRVALS' import package is successfully completed.
INFO: 2007-11-13 16:02:01 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSDOCU' import package is successfully completed.
TRACE: 2007-11-13 16:02:09 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL0_4' import package is started.
TRACE: 2007-11-13 16:02:09 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSLEXC' import package is started.
TRACE: 2007-11-13 16:02:09 com.sap.inst.migmon.LoadTask run
Loading of 'SAPCLUST' import package is started.
TRACE: 2007-11-13 16:02:09 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPSLEXC' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp1\EXP6\DATA\SAPSLEXC.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPSLEXC.TSK ORA -l SAPSLEXC.log
TRACE: 2007-11-13 16:02:09 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPCLUST' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp1\EXP6\DATA\SAPCLUST.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPCLUST.TSK ORA -l SAPCLUST.log
TRACE: 2007-11-13 16:02:09 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPAPPL0_4' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp2\EXP7\DATA\SAPAPPL0_4.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPAPPL0_4.TSK ORA -l SAPAPPL0_4.log
TRACE: 2007-11-13 16:02:09 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPSLEXC' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPSLEXC.cmd -dbcodepage 4103 -l SAPSLEXC.log -stop_on_error
TRACE: 2007-11-13 16:02:09 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPCLUST' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPCLUST.cmd -dbcodepage 4103 -l SAPCLUST.log -stop_on_error
TRACE: 2007-11-13 16:02:10 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPAPPL0_4' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL0_4.cmd -dbcodepage 4103 -l SAPAPPL0_4.log -stop_on_error
ERROR: 2007-11-13 16:02:10 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSLEXC' import package is interrupted with R3load error.
Process 'E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPSLEXC.cmd -dbcodepage 4103 -l SAPSLEXC.log -stop_on_error' exited with return code 2.
For mode details see 'SAPSLEXC.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
INFO: 2007-11-13 16:02:23 com.sap.inst.migmon.LoadTask run
Loading of 'SAPCLUST' import package is successfully completed.
TRACE: 2007-11-13 16:02:39 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSLOAD' import package is started.
TRACE: 2007-11-13 16:02:39 com.sap.inst.migmon.LoadTask run
Loading of 'SAPUSER' import package is started.
TRACE: 2007-11-13 16:02:39 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPSLOAD' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp1\EXP6\DATA\SAPSLOAD.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPSLOAD.TSK ORA -l SAPSLOAD.log
TRACE: 2007-11-13 16:02:39 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPUSER' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp1\EXP6\DATA\SAPUSER.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPUSER.TSK ORA -l SAPUSER.log
TRACE: 2007-11-13 16:02:39 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPSLOAD' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPSLOAD.cmd -dbcodepage 4103 -l SAPSLOAD.log -stop_on_error
TRACE: 2007-11-13 16:02:39 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPUSER' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPUSER.cmd -dbcodepage 4103 -l SAPUSER.log -stop_on_error
ERROR: 2007-11-13 16:02:40 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL0_4' import package is interrupted with R3load error.
Process 'E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL0_4.cmd -dbcodepage 4103 -l SAPAPPL0_4.log -stop_on_error' exited with return code 2.
For mode details see 'SAPAPPL0_4.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
ERROR: 2007-11-13 16:02:41 com.sap.inst.migmon.LoadTask run
Loading of 'SAPUSER' import package is interrupted with R3load error.
Process 'E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPUSER.cmd -dbcodepage 4103 -l SAPUSER.log -stop_on_error' exited with return code 2.
For mode details see 'SAPUSER.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
INFO: 2007-11-13 16:02:42 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSLOAD' import package is successfully completed.
TRACE: 2007-11-13 16:03:09 com.sap.inst.migmon.LoadTask run
Loading of 'SAPDDIM' import package is started.
TRACE: 2007-11-13 16:03:09 com.sap.inst.migmon.LoadTask run
Loading of 'SAPDFACT' import package is started.
TRACE: 2007-11-13 16:03:09 com.sap.inst.migmon.LoadTask run
Loading of 'SAPDODS' import package is started.
TRACE: 2007-11-13 16:03:09 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPDDIM' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp1\EXP6\DATA\SAPDDIM.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPDDIM.TSK ORA -l SAPDDIM.log
TRACE: 2007-11-13 16:03:09 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPDFACT' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp1\EXP6\DATA\SAPDFACT.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPDFACT.TSK ORA -l SAPDFACT.log
TRACE: 2007-11-13 16:03:09 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPDODS' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp1\EXP6\DATA\SAPDODS.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPDODS.TSK ORA -l SAPDODS.log
TRACE: 2007-11-13 16:03:09 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPDODS' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPDODS.cmd -dbcodepage 4103 -l SAPDODS.log -stop_on_error
TRACE: 2007-11-13 16:03:09 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPDDIM' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPDDIM.cmd -dbcodepage 4103 -l SAPDDIM.log -stop_on_error
TRACE: 2007-11-13 16:03:09 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPDFACT' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPDFACT.cmd -dbcodepage 4103 -l SAPDFACT.log -stop_on_error
INFO: 2007-11-13 16:03:10 com.sap.inst.migmon.LoadTask run
Loading of 'SAPDDIM' import package is successfully completed.
INFO: 2007-11-13 16:03:11 com.sap.inst.migmon.LoadTask run
Loading of 'SAPDFACT' import package is successfully completed.
INFO: 2007-11-13 16:03:11 com.sap.inst.migmon.LoadTask run
Loading of 'SAPDODS' import package is successfully completed.
TRACE: 2007-11-13 16:03:39 com.sap.inst.migmon.LoadTask run
Loading of 'SAPUSER1' import package is started.
TRACE: 2007-11-13 16:03:39 com.sap.inst.migmon.LoadTask run
Loading of 'SAP0000' import package is started.
TRACE: 2007-11-13 16:03:39 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAP0000' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp1\EXP6\DATA\SAP0000.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAP0000.TSK ORA -l SAP0000.log -o D
TRACE: 2007-11-13 16:03:39 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPUSER1' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp1\EXP6\DATA\SAPUSER1.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPUSER1.TSK ORA -l SAPUSER1.log
TRACE: 2007-11-13 16:03:39 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAP0000' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAP0000.cmd -dbcodepage 4103 -l SAP0000.log -stop_on_error
TRACE: 2007-11-13 16:03:39 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPUSER1' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPUSER1.cmd -dbcodepage 4103 -l SAPUSER1.log -stop_on_error
INFO: 2007-11-13 16:03:40 com.sap.inst.migmon.LoadTask run
Loading of 'SAPUSER1' import package is successfully completed.
INFO: 2007-11-13 16:03:40 com.sap.inst.migmon.LoadTask run
Loading of 'SAP0000' import package is successfully completed.
WARNING: 2007-11-13 16:04:09
Cannot start import of packages with views because not all import packages with tables are loaded successfully.
WARNING: 2007-11-13 16:04:09
13 error(s) during processing of packages.
INFO: 2007-11-13 16:04:09
Import Monitor is stopped.
how can i resolve these errors?Hi,
Here are the logs of the jobs that are failing to complete. i am selecting the recommended which is unicode
SAPALLP2_3.log
DbSl Trace: ORA-604 occurred when executing SQL statement (parse error offset=0)
(DB) ERROR: DDL statement failed
(CREATE TABLE "TN02Q" ( "MANDT" VARCHAR2(9) DEFAULT '000' NOT NULL , "EINRI" VARCHAR2(12) DEFAULT ' ' NOT NULL , "ANWEN" VARCHAR2(12) DEFAULT ' ' NOT NULL , "PARNA" VARCHAR2(30) DEFAULT ' ' NOT NULL , "PARWE" VARCHAR2(45) DEFAULT ' ' NOT NULL , "COMMT" VARCHAR2(90) DEFAULT ' ' NOT NULL ) TABLESPACE PSAPSR3 STORAGE (INITIAL 16384 NEXT 0000000040K MINEXTENTS 0000000001 MAXEXTENTS 2147483645 PCTINCREASE 0 ) )
DbSlExecute: rc = 99
(SQL error 604)
error message returned by DbSl:
ORA-00604: error occurred at recursive SQL level 2
ORA-04031: unable to allocate 4108 bytes of shared memory ("shared pool","select /*+ index(idl_sb4$ i_...","Typecheck","kgghtInit")
(DB) INFO: disconnected from DB
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe: job finished with 1 error(s)
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe: END OF LOG: 20071113155648
SAPSSEXC_3.log
DbSl Trace: ORA-1403 when accessing table SAPUSER
(DB) INFO: connected to DB
(DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): UTF8
(DB) INFO: REPOSRC created #20071113141340
DbSl Trace: ORA-604 occurred when executing SQL statement (parse error offset=0)
(IMP) ERROR: DbSlExeModify/DbSlLobPutPiece failed
rc = 99, table "REPOSRC"
(SQL error 604)
error message returned by DbSl:
ORA-00604: error occurred at recursive SQL level 1
ORA-04031: unable to allocate 4108 bytes of shared memory ("shared pool","select /*+ index(idl_sb4$ i_...","Typecheck","kgghtInit")
(DB) INFO: disconnected from DB
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe: job finished with 1 error(s)
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe: END OF LOG: 20071113155650
SAPSSEXC_5.log
DbSl Trace: Failed to register client info: orc=604
DbSl Trace: ORA-604 when accessing table SAPUSER
(DB) INFO: connected to DB
(DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): UTF8
DbSl Trace: ORA-604 occurred when executing SQL statement (parse error offset=0)
(DB) ERROR: DDL statement failed
(CREATE TABLE "TFTIT" ( "SPRAS" VARCHAR2(3) DEFAULT ' ' NOT NULL , "FUNCNAME" VARCHAR2(90) DEFAULT ' ' NOT NULL , "STEXT" VARCHAR2(222) DEFAULT ' ' NOT NULL ) TABLESPACE PSAPSR3700 STORAGE (INITIAL 34164981 NEXT 0000002560K MINEXTENTS 0000000001 MAXEXTENTS 2147483645 PCTINCREASE 0 ) )
DbSlExecute: rc = 99
(SQL error 604)
error message returned by DbSl:
ORA-00604: error occurred at recursive SQL level 1
ORA-04031: unable to allocate 4108 bytes of shared memory ("shared pool","select name,password,datats#...","Typecheck","kgghtInit")
(DB) INFO: disconnected from DB
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe: job finished with 1 error(s)
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe: END OF LOG: 20071113155711
SAPAPPL0_2.log
DbSl Trace: ORA-604 occurred when executing SQL statement (parse error offset=41)
(DB) ERROR: DDL statement failed
(CREATE UNIQUE INDEX "ECRM_REPL_KEY~0" ON "ECRM_REPL_KEY" ( "MANDT", "ISUPRODLOG", "OBJNUM" ) TABLESPACE PSAPSR3 STORAGE (INITIAL 16384 NEXT 0000002560K MINEXTENTS 0000000001 MAXEXTENTS 2147483645 PCTINCREASE 0 ) )
DbSlExecute: rc = 99
(SQL error 604)
error message returned by DbSl:
ORA-00604: error occurred at recursive SQL level 2
ORA-04031: unable to allocate 4108 bytes of shared memory ("shared pool","select con#,obj#,rcon#,enabl...","Typecheck","kgghteInit")
(DB) INFO: disconnected from DB
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe: job finished with 1 error(s)
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe: END OF LOG: 20071113155711 -
Help required in running SPAU and SPDD transactions for post upgrade
Hi All,
We are doing a system upgrade to EHP1.
We need help in SPAU and SPDD runs and why are they required in upgrade activity.
Kindly respond.
Thanks in advance
Regards
RashmiHi Rashmi,
SPDD and SPAU are modification adjustments that you need to adjust after upgrade. This is a situation where the upgrade has to enhance some structures and elements that was available in previous version (probably 3.x). The system can not determine whether to overwrite the structures or to retain the old version. If the structures are custom structures, the system might overwrite any enhancements that you have done. In this kind of situations, the system puts any such structures and elements that it can not make a decision into these 2 lists. SPDD is for dictionary objects and SPAU is for configurations. You have to fix all the issues that are produced in these transactions. You need to first fix the ones in SPDD list and then the SPAU list. Once you drill down in those lists, it asks you to take actions like "change it", "keep the old version" or "ignore the changes" (I think these are the options). You need to chosse these options based on your analysis and turn all the yellow and red ones into green. Hope this gives you some idea.
Thanks and Regards
Subray Hegde -
46C - ECC 6.0 || Problem in PREPARE
Hello All!
I'm initializing PREPARE and when running option 1 on SAPUP menu, this message is displayed:
Message . . . . : Function check. CEE9901 unmonitored by PREPAREOS4 at
statement 0000046300, instruction X'0000'.
Viewing joblog, the first error is:
Message ID . . . . . . : CPDB9C9 Severity . . . . . . . : 30
Message type . . . . . : Diagnostic
Date sent . . . . . . : 08/15/07 Time sent . . . . . . : 13:16:00
Message . . . . : Internal system error. Error code is -72.
Cause . . . . . : An internal error occurred loading i5/OS PASE program
/usr/sap/put/bin/SAPup.
Recovery . . . : Try the request again. If the problem persists, report the
problem using the Analyze Problem (ANZPRB) command.
SAPUP is up-to-date. Can anyone help me what kind of "internal error" is this?
Thank for all help!
Best Regards,
André Koji Honma
FUJIFILM da Amazônia Ltda.Hi Andre,
We got one requirement similar to the upgrade you have executed..
Operating system : OS/400
Machine Type : 825
Platform ID : 592
Database : DB400 V5R4
Source
R/3 Version : 4.6C
Target Version : ECC 6.0
In Service Marketplace it shows the upgrade guide selection as below
1)Unix DB2 UDB for UNIX and Windows
2)Unix DB2 UDB for z/OS
3)Windows DB2 UDB for UNIX and Windows
4)Windows DB2 UDB for z/OS
5)IBM eServer iSeries DB2 UDB for iSeries
I am obsolutely new to OS/400 environment. kindly suggest the relavent guide to be followed for executing the upgrade.
Regards
Kamal -
ECC Ugrade to 6.0 with no upgrade to BI 7.0
Hi Guys,
The upgrade is somewhat like this:
Old:
ECC PR1>BI PB1
New (Upgraded/New Server):
ECC PR2>BI PB1
Since its a new server BI is connected to, do we have do do any source system switch settings from the old to new?
Do I delete the old source system in PB1?
Also How do I make sure of the deltas are all working right after the ECC upgrade?
Do I have to delete the setup tables in ECC?
Are there any SAP notes that we can follow?
CheersHi,
There are many activities will be carried out by basis.
Your current Production source R/3 is getting upgraded so you need to change name of the source.This can be done through BDLS program run by basis team.
But post upgrade we need to activate source system.
carry out replication of datasources etc if required. This also normally done by them if not you need to carry olut this activity.
Nothing else needs to be done.
You have to clear delta queue from all the places post user lock in source system.So RSA7,LBWQ,SMQ1 all should be empty.
You have to run 2LIS jobs in R/3 then execute BI jobs to pull the data in BW system.
Thanks and regards -
ECC 6.0 Enhancement Pack 5 upgrade phase ADJUSTCHK faillure
When I run the Enhancement Pack Installation, I get a hard failure at the MAIN_SHDCRE/ADJUSTCHK phase. The error message says "No lines found in logfile matching "UMODPRO\.INX". The log follows...
1 ETQ201 Entering upgrade-phase "ADJUSTCHK" ("20111006131443")
4 ETQ399 Set environment for standard connect:
2 ETQ367 Connect variables are set for standard instance access
4 ETQ399 System-nr = '00', GwService = 'sapgw00'
4 ETQ399 Environment variables:
4 ETQ399 dbs_ora_schema=SAPR3
4 ETQ399 auth_shadow_upgrade=0
1 ETQ200 Executing actual phase 'MAIN_SHDCRE/ADJUSTCHK'.
1 ETQ399 Phase arguments:
2 ETQ399 Arg[0] = 'SAP_MOD_EHP'
2 ETQ399 Arg[1] = 'ADJUSTCK.ELG'
2 ETQ399 Arg[2] = 'ADJUSTMT.INF'
4 ETQ010 Date & Time: 20111006131443
4 ETQ265 Starting report "RSUMOD01" with variant "SAP_MOD_EHP" in batch
4 ETQ359 RFC Login to: System="INX", Nr="00", GwHost="fainx", GwService="sapgw00
4 ETQ232 RFC Login succeeded
4 ETQ233 Calling function module "SUBST_START_REPORT_IN_BATCH" by RFC
4 ETQ234 Call of function module "SUBST_START_REPORT_IN_BATCH" by RFC succeeded
4 ETQ239 Logging off from SAP system
4 ETQ311 Batch job "RSUMOD01" with job count "13144400" scheduled
4 ETQ359 RFC Login to: System="INX", Nr="00", GwHost="fainx", GwService="sapgw00
4 ETQ232 RFC Login succeeded
4 ETQ010 Date & Time: 20111006131819
4 ETQ234 Call of function module "SUBST_CHECK_BATCHJOB" by RFC succeeded
4 ETQ239 Logging off from SAP system
1EETQ248 Missing log file(s) of report "RSUMOD01", matching "UMODPROT\.INX"
What does this mean?
Is the backslash supposed to be in the name UMODPROT.INX?Hi,
Please check in SM37 if there is any job failure in the system. And also check if there is any dump.
Thanks
Sunny -
Warning codes generated in UCCHECK - Technical Upgrade - 4.0b to ECC 6.0
Hi SDN'ers ,
I am currently working on Technical Upgrade project from 4.0 b system to ECC 6.0 system . I am facing a
problem relating to the analysis of the warnings displayed whehn we run the UCCHECK for the client inventory by
checking the "Display lines that cannot be analyzed statically" option under the Selection-screen block
"Statements that cannot be analyzed statically" .Based on the warning codes generated during UCCHECK, they can
be classified into 12 different categories given below in the list ( Viz. ABB,MESSAGEG!C,MESSAGEG!D......MESSAGEG!P).The same are given below in the end
I want to know
- Which are the warning codes which need resolution so that the program does not encounter any runtime
errors or during Integration testing ?
- Do all the offset related errors (For example ;variable A = B+offset(length)
or variable A+offset(length) = B ) need resolution so that the program gives no runtime error.
- Also, do all statements where length is calculated using STRLEN also need changes ? I have seen offset length related warnings come under MESSAGEG!M warning code.
The objective of this is to make sure that the upgraded system ECC 6.0 in Australia ,when rolled out to
non-English speaking geographies in APAc such as Malaysia,Japan or China would only need translations and no ABAP Coding effort even when using languages such as Japanese which have double byte characters.
S.No. Error Code Message
1 ABB Syntax Check Aborted
ABB Total
2 MESSAGEG!C check at runtime. at runtime.
statement because of untyped or generic operands. It can only carry out this
The system could not perform a static convertibility check on the current
MESSAGEG!C Total
3 MESSAGEG!D out this check at runtime. It can only carry out this check at runtime.
to a table line because of untyped or generic operands. It can only carry out
The system could not perform a static check on convertibility from a work area
MESSAGEG!D Total
4 MESSAGEG!E check at runtime. at runtime.
defined by a "DATA" statement. .
statement because of untyped or generic operands. It can only carry out this
Field "ELEMENTN" is unknown. It is neither in one of the specified tables nor
The system could not perform a static comparability check on the current
MESSAGEG!E Total
5 MESSAGEG!F operand "<FELD1>" for the current statement. .
MESSAGEG!F Total
6 MESSAGEG!G current statement on incompletely typed operand "<DATA>". .
MESSAGEG!G Total
7 MESSAGEG!H for the incompletely typed operand "<S>". . - - - - - - - - -
The system cannot perform a static check on a character-type field data type
MESSAGEG!H Total
8 MESSAGEG!I incompletely-typed operand "<A>" in the current statement. .
The system cannot perform a static check on a character-type data type for the
MESSAGEG!I Total
9 MESSAGEG!J "<%_1_SYSINI>" in the current statement to check whether the operand can be
The system cannot perform a static check on incompletely-typed operand "VALUE"
MESSAGEG!J Total
Early response wil be highly appreciated.Hi Karthik
>
> 1) SPDD adjustments are done in which phase? PREPARE or UPGRADE?
>
SPDD is done in Upgrade ->Phase ACT_700
> 2) Are here special cases where the adjustments need to be done before running the UPGRADE phase?
>
At ACT_700 phase stop the upgrade and take a backup of the DB and the PUT<DIR> before starting the SPDD activity.
Make sure there are no pending tp request. Either release them or delete them.
All phase need to be completed successfully in PREPARE, before starting UPGRADE
Cheers
Shaji
Edited by: Shaji Jacob on May 5, 2008 9:23 PM -
Minimum Patch to do the upgrade
Hi Experts,
We are doing a upgrade from 4.6C to ECC 6.0.
Can you tell/mail me the Minimum Patch that much be available in 4.6C inorder to start the upgrade to ECC 6.0.
If u have any documents u can send to [email protected]
Thanks in advance,
SubaHi Suba,
Mininum level is 53, but it's recomended to be on latest patch level to avoid errors during PREPARE or UPGRADE phase.
hope this helps...
Thanks
Praveen -
Steps to follow in Upgrade from 4.7 to ECC 6.0
Hi ,
As part of Upgrade from 4.7 to ECC 6.0 , Basis team completed Prepare module.
Now Prepare module report says there are some modifications need to be done .
Do i need to make the changes to the adjustments populated in SPDD/ SPAU transaction code before basis team goes for Upgrade ?
If changes are applied to the modifications populated in SPDD / SPAU. How i need to transport these objects ?
Please let me know the steps need to take in transport of these objects .
Cheers,
ReddyDear,
Transaction SPDD allows you to adjust modifications to ABAP Dictionary objects during an upgrade, the upgrade will stop at the begin of ACT_700 phase, so you can logon to shadow instance and perform the adjustments in SPDD.
About transaction SPAU that allows you to adjust programs, function modules, screens, interfaces, documentation, and text elements after an upgrade.
You have the option to include the SPDD request from previous upgrade,
The PREPARE includes the ADJUSTPRP phase for this purpose. In this
phase, the system searches the global transport directory for comparison
requests from previous upgrades and offers these for inclusion in the
upgrade. If you do not have this request, you may go ahead with the upgrade
and the proceed with the SPDD / SPAU adjustments during the upgrade.
Please refer to the following SAP Notes for more details:
68678 Exporting modification adjustment for 2nd upgrade
610311 Importing a modification adjustment in 2nd upgrade
124522 Importing a modification adjustment in 2nd upgrade
I hope this helps.
Lucio Rodrigues -
Hi Experts,
I am working for an upgrade project from 4.6C to ECC 6.0. I need some clarifications regarding use of SPDD.
im intend to clear certain database before proceed with SPDD using new z program, can i execute this z program before SPDD completed? please kindly help.
thanks.Hi,
what is the different between SCC4 and SPAU/ SPDD function ?
is it true that during the upgrade , we didnt have to bring object from old system to new system , but instead using SCC4?
Hi Rudy,
SCC4 is the Client Administration view. The only case that you will need it during the upgrade is to allow changes to client 000 during SPDD. SCC4 has absolutely nothing to do with actually transporting objects. If you plan to transport objects from the old release to the new one, you must use STMS. But please be very careful when transporting objects between different releases of an SAP system.
SPDD is used to display and adjust the modified DDIC objects. You must process these objects ("Reset to Original" or "Adjust") as soon as you reach the upgrade phase ACT_< target release >. Once you're done adjusting the objects, you choose "Repository ok". The upgrade phase ACT activates then all the objects of your system.
1. During tech upgrade , basis choose "Continue" instead of choosing "Adjustment completed" .
should we do this SPDD during techncl upgrade process? or do this later after techncl upgrade?
SPAU is used to display and adjust the modified DE objects of the system. The phase SPAUINFO is one of the last Post Processing phases of the technical upgrade. There is a message explaining that, if you want to use the result of the adjustments for a subsequent system, you must not continue. In that case, we just exit SAPup or leave it waiting for an input. As soon as the adjustment is done for ALL objects listed in SPAU, you go back to SAPup again and choose "Adjustments completed".
Your basis consultant choose "Continue" which means that the result of the adjustments won't be used during the technical upgrade of a subsequent system. This has also been the case in almost all the upgrades I've performed myself.
Regards,
Constantina -
Hi Experts,
We are doing SPDD activity for an upgrade from 4.7 to ECC 6.0. Client has only EN language.
We have come across 2 SPDD changes :-
Request your inputs on the following points :-
1 New Field added to an Index in ECC 6.0. Should we reset to original for such change ?
2 "No Database Index" flag set in ECC 6.0. Should we reset to original ?
3 Existing Field deleted from Index . Should we reset to original ?
4 MASTERLANG field has been set with TL flag to X . How do we proceed with this.
I feel above changes would have performance impact if the indexes are used.
Please let me know how to proceed in such scenarios.
Thanks,
Best regards,
PrashantHi Prasanth,
First of all, doing reset to original or adopt modification activities are depends on client scope, iff client has given specific scope of work with all these then we should follow as per that, otherwise as per the standard
1.if any field added in ECC 6.0 by SAP then its to be reset to original
2.If "database index" flag sets in 4.7 and u need the same then go for adopt modification
iff database index flag not needed for you, then go for reset to original
3.Existing field(4.7) deleted from Index, iff the filed is used in anywhere or if you wish to continue with that field then go for adopt modification
if that field was not at all used anywhere then go for reset to original
4. "MASTERLANG field has been set with TL flag to X" if you wish to continue the as it is in 4.7, then go for adopt modification
otherwise go for reset to original.
I will give you one example,
in one of my upgrade project, as per the SAP standards some of the objects are supposed to go for "Adopt modification", but after doing that client sent mail like dont go for adopt modification with out asking us, they needs everything should be reset to original.
Like that iff client is having certain criteria then we should follow that otherwise follow Standard approaches which are mentioned above for your requirement.
Regards
Arani Bhaskar -
Experts,
What's ERP 6.0?
Is it different from ECC 6.0? HowSay during an upgrade we perform SPDD & SPAU on ECC 6.0 and ERP 6.0 comes up, what are the next steps?
NW
Edited by: NW on Aug 11, 2008 4:15 PMHi
for those with the same question:
SAP ERP 6.0 (formerly known as mySAP ERP 2005) is the name/ release of the complete SAP ERP application. The predessor is mySAP ERP 2004.
The large SAP ERP application consist of > 30 (?) installable units. One of these installable units is SAP ECC (6.0). Others are SAP NW - EP Core, SAP FSCM - Server ABAP, SAP SEM, etc.
[=> SAP ECC is a part of SAP ERP 6.0, and not only an alternative name].
SAP ECC is as well a special case, because it is the successor component of the former SAP R/3 (46c, Enterprise...)
[=> SAP R/3 is part of the very much larger SAP ERP (6.0)]
regards,
Andreas R -
SPAU SPDD Transport Strategy for following Upgrades
Hello All,
We are doing CUUC from 4.7 NUC to ECC 6 Ehp4 UC
After completing our Upgrade from 4.7 NUC to ECC 6 NUC in the original host, I stopped the Upgrade tool at the point when it asks for SPAU adjustements in Post Processing Step, did the Unicode Conversion in which we built the Target ECC 6 UC System in a separate host (host: ecctemp).
So,
1. The Upgrade Directory and ECC 6 NUC System resides on the first host.2. The Second host(ecctemp) contains only the ECC 6 UC System.
3. We started our SPAU activities in the ECC 6 UC System after CUUC process completed.
4. Now, with SPDD & SPAU activities getting completed. I want the 2 Transports to be used for rest of the Upgrades.
How do I go about this?
1. I cannot run 'SELECT FOR TRANSPORT' or run the commands as per 68678 in the ECC 6 NUC System as thats where I didnot do SPAU.
2. I cannot even run the commands as per 68678 in the host ecctemp, becuase there is no upgrade directory here.Hi,
You can add SPDD transport on your non-unicode system in umodauto.lst file and take this file to your quality system (also data file and cofile). So, when you will start upgrade on your quality system then upgrade tool will first read this umodauto.lst file and it will prompt you on the screen to has this transport as SPDD transport. And upgrade tool will then import this SPDD request.
For SAPU, you can simply move data file and cofile from your final system to quality system. And once your quality system will be ready after upgrade and UC conversion then you can simple import this transport from STMS. This will solve your issue.
Thanks
Sunny
Maybe you are looking for
-
Unable to start Windows 7 after recovering from an image
Dear community! In our office, we frequently use Windows 7 on our Mac computers. Windows 7 is installed on a Bootcamp partition. The HDD of one of our MacBooks crashed today and I recovered data from a previously made full image of that MacBook to an
-
Dual screens with x1600 mobility & open source driver
Hi, I've been trying to get a dual screen setup with two truly independent screens (not the one giant screen that xrandr gives you), but I've been having some issues. The hardware I'm attempting this on is my macbook pro 2.1 with a 1440x900 internal
-
Bug: in ManagedDataAccess while fetch from "Select .., NULL, ... From dual"
Hi, I have the problem with the new managed ODP.Net driver. If I fetch data from a select which has column with a fixed value "NULL" the driver decides after a certain amount of data that the value is not null any more. Which causes a lot of problems
-
Employee cant take leaves same date
Hi, How to restick that employee cant take leaves same date .
-
Organizational Unit is managed by Position
i want to know which organizational Unit is managed by which position i.e. which is the chief position in particular Organizational unit. In which table i can get this relation ship.