MVNTXCNV.ELG Error
Hi
We are facing the next error at the 'MVNTXCNV.ELG' phase:
Contents of 'MVNTXCNV.ELG'
2EETQ399 View latest 'TP*.ECO' files in log-directory for details.
2EETQ399 Dialogue: ERROR
2EETQ399 Log file analyse of 'tp ddlntabs' operation:
2EETQ399 -> single errors (code <= 8) found in logfile
2EETQ399 Errors are accumulated in file 'MVNTXCNV.ELG'
Contents of TP00.ECO - Latest Files
BLOCKED SIGNALS: ''
SAPup> Starting subprocess 24672 at 20080410134527
ENV <0x9ffffffffffff83c>: ORACLE_PSRV=SUP
ENV <0x9ffffffffffffb7f>: NLS_LANG=AMERICAN_AMERICA.WE8DEC
ENV <0x9ffffffffffffbac>: ORACLE_BASE=/oracle
ENV <0x9ffffffffffffbe5>: dbs_ora_tnsname=SUP
ENV <0x9ffffffffffffc05>: ORACLE_SID=SUP
ENV <0x600000000019c600>: DIR_LIBRARY=/usr/sap/put/exe
ENV <0x9ffffffffffffc7b>: ORA_NLS=/oracle/SUP/102_64/ocommon/NLS_723/admin/data
ENV <0x600000000018e590>: dbs_ora_schema=SAPR3
ENV <0x9ffffffffffffd30>: ORA_NLS32=/oracle/SUP/102_64/ocommon/NLS_733/admin/data
ENV <0x9ffffffffffffd68>: ORA_NLS33=/oracle/client/92x_64/ocommon/nls/admin/data
ENV <0x9ffffffffffffe12>: ORACLE_HOME=/oracle/SUP/102_64
ENV <0x9ffffffffffffe4d>: dbms_type=ORA
ENV <0x600000000019ca00>: LD_LIBRARY_PATH=/usr/sap/put/exe:/opt/java1.5/jre/lib/IA64N:/opt/java1.5/jre/lib/IA64N/server:/opt/java1.5/jre/../lib/IA64N
ENV <0x600000000018e990>: auth_shadow_upgrade=0
EXECUTING /usr/sap/put/exe/tp (tp) pf=/usr/sap/put/bin/XTERN_CNV.TPP ddlntabs SUP ddlmode=F step=X protyear=00 shadow_only strel=46C substext=4G -Dbuffreset=no touch=NO
This is /usr/sap/put/exe/tp version 372.03.35 (release 700)
Warning: Parameter INTERRUPT is no longer used.
Warning: Parameter DAYLIGHT_SHUTDOWN is no longer used.
Warning: Parameter WITH_TACOB is no longer used.
Warning: Parameter IMPDP_BY_EVENT is no longer used.
Warning: Parameter INTERRUPT is no longer used.
Warning: Parameter DAYLIGHT_SHUTDOWN is no longer used.
Warning: Parameter WITH_TACOB is no longer used.
Warning: Parameter IMPDP_BY_EVENT is no longer used.
Warning: Parameter DBCONFPATH is no longer used.
Warning: Parameter STARTDB is no longer used.
Warning: Parameter STOPDB is no longer used.
tp finished with return code: 8
meaning:
A tool used by tp produced errors
supadm>
can anyone help
Thanks & Regards
Senthil
Sure Will Do that Shaji.
Is PSAPTEMP tablespace used in oracle10g/ECC6.0? bcos in our upgraded development box, the used space is always Zero.
So I doubt whether PSAPTEMP is used or not?
Regards
Senthil
Similar Messages
-
Upgrade Fails in downtime Phase - MAIN_SWITCH/PARMVNT_XCNV
Dear All,
We are working on the upgrade from ECC6.0 to ECC6.0 with EHP4 and now running in the downtime phase. In the downtime phase, the upgrade stopped in the phase of MAIN_SWITCH/PARMVNT_XCNV and stated that to check the logs of MVNTXCNV.ELG. In the log file it stated that
MVNTXCNV.ELG
MVNTTABS ERRORS:ddlntabs and RETURN CODE in PD000825.FSO
SQL -error Duplicate name:SRT_MONLoG_DATA2 in DDL st
SRT_MONLOG_DATA2
error in DDL nametab for "SRT_MONLOG_DATA2 not activated
Then I have searched in SMP and in SDN and came to know that we need to implement the notes of
Note 1399438 - System upgrade stops in phase XCNV
Note 1310677 - System upgrade terminates in phase MAIN_SWITCH/PARMVNT_XCN
Hence, I have started the instance manually and unlocked the tp to login as different user for applying this note ( Because we cannot apply note usign DDIC ) . Then able to login into the system and downloaded the notes as well,
While implementing the when I try to create a request - it immediately throwing a short dump and dump states that
TRINT_INSERT_COMM_HEADER
SQL error in the database when accessing a table
Database error text: POS(40) too few values
Internal call code: RSQL/INSR/EO70C
Please check the same in SM21
In system logs the logs says that
Runtime error DBIF_RSQL_SQL_ERROR
Short dump created
Database error -1200 at PRE access to table E070c
POS (40) Too few values
Instead of creating a new request and tried to use own request but the results are same, Also i tried to change the client settings from automatic recording of changes and also changes w/o automatic recording of changes - but both are giving the same output.
Is there any other possibility to get rid off this issue? Any suggestions are highly appreciated
Regards
VijayIts fixed and I have just implemented the note 589296 - Solved our issue
select * from "SAPFSO"."DDXTT~" where TABNAME = 'SRT_MONLOG_DATA2'
or
select * from "SAPFSO"."DDXTT" where TABNAME = 'SRT_MONLOG_DATA2'
Check it approximately it should return with the FLAG value as F
update "SAPFSO"."DDXTT~" set modeflag = 'A' where TABNAME = 'SRT_MONLOG_DATA2'
Thanks for your support
Regards
Vijay -
Can't run non-UNICODE-DbSl against UNICODE database
Hi everyone. I get this error during the update of Solution Manager 7.1 SPS4 (dual stack) to SPS10. It is a green install. This happens during the
phase PREP_EXTRACT/PREIMP! Of the ABAP stack. Step 5.2. I do not see a lot of people with this problem, so I assume it is something I am doing wrong, as it is my first time using the tool SUM.
Details of the system:
Solution Manager 7.1 SPS4
Windows 2008 R2 64 bit
Microsoft SQL 2008 R2 64 bit SP1
Central installation type with all components on
the same host
Kernel level 600
Here is what I have done so far:
Downloaded the media as described in the installation
guide.
Worked my way through the install using the
Software Provision Manager 1.0
Updated the Kernel from level 401 to 600, by
copying the files from the download folder to the F:\usr\sap\SM1\SYS\exe\uc\NTAMD64
folder. This is the folder that is assigned to the DIR_CT_RUN parameter.
I start the STARTUP.BAT file in the SUM folder.
I then start the SUM GUI and run through the
steps and in step 3 I map the Stack configuration file (XML) to one listed in
the folder “51047130\DATA” called “SPS10_stack.xml”
Then I
get to 5.2 where the system stops with this error:
Severe error(s) occurred in phase PREP_EXTRACT/PREIMP!
Last error code set: Single errors (code <= 8) found in logfile 'PREIMP.ELG'
ERROR: Detected the following errors:
# F:\usr\SUM\abap\log\R710VPE.<DB>:
4 ETW000 TRACE-INFO: 19: [ dev trc,00000] Driver: sqlncli10.dll Driver release: 10.50.2769 3938 0.039733
4 ETW000 TRACE-INFO: 20: [ dev trc,00000] GetDbRelease: 10.50.2769.00 1603 0.041336
4 ETW000 TRACE-INFO: 21: [ dev trc,00000] GetDbRelease: Got DB release numbers (10,50,2769,0) 21 0.041357
4 ETW000 TRACE-INFO: 22: [ dev trc,00000] Can't run non-UNICODE-DbSl against UNICODE database 2647 0.044004
4 ETW000 TRACE-INFO: 23: [ dev trc,00000] CheckCodepageType failed. Connect terminated. 13 0.044017
2EETW169 no connect possible: "DBMS = MSSQL --- SERVER = '<SERVER>' DBNAME = '<DB>'"
Can
anyone please help?
PS:
The admin user that I use do have access to the database. It is listed with
sysadmin role and the default DB is the Solution Manager db.ERROR: Detected the following errors:
# F:\usr\SUM\abap\log\R710VPE.<DB>:
4 ETW000 TRACE-INFO: 19: [ dev trc,00000] Driver: sqlncli10.dll Driver release: 10.50.2769 3938 0.039733
4 ETW000 TRACE-INFO: 20: [ dev trc,00000] GetDbRelease: 10.50.2769.00 1603 0.041336
4 ETW000 TRACE-INFO: 21: [ dev trc,00000] GetDbRelease: Got DB release numbers (10,50,2769,0) 21 0.041357
4 ETW000 TRACE-INFO: 22: [ dev trc,00000] Can't run non-UNICODE-DbSl against UNICODE database 2647 0.044004
4 ETW000 TRACE-INFO: 23: [ dev trc,00000] CheckCodepageType failed.
As per error, you have used wrong kernel. Please make sure that you use unicode kernel as your system is also unicode.
Thanks,
Sunny -
Error in Phase MAIN_SWITCH/JOB_RSVBCHCK_D
Hello Gurus,
I am in the Downtime phase and got below error
Error Details:
Checks after phase MAIN_SWITCH/JOB_RSVBCHCK_D were negative!
Last error code set: BATCHJOB RSVBCHCK FAILED: Errors found in logfile (accumulated in file PSVBCHCK.ELG).
PSVBCHCK.ELG log is:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
CHECK OF UPDATE TASK Errors and RETURN CODE in RSVBCHCK.IJE
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
A2EEMCEX 141 Struct. appl. "02" cannot be changed due to setup table -> Long text" ""MC02M_0CGRSETUP""800"
Long text:
Cause
Changing the extract structure &V#& for application &V#& is not
permitted, because the restructure table &V#& for the extractor still
contains data in &V#&.
You cannot change the structure in this status, because when you load
an InfoPackage from BW, this leads to errors.
What to do
<DS:TRAN.LBWG>Delete</> the entries for all restructure tables for
application &V#&.
A2EEMCEX 141 Struct. appl. "02" cannot be changed due to setup table -> Long text" ""MC02M_0HDRSETUP""800"
Long text: see above
A2EEMCEX 141 Struct. appl. "02" cannot be changed due to setup table -> Long text" ""MC02M_0ITMSETUP""800"
Long text: see above
i am able to login to shadow instance with DDIC in 000client and created new user with copy of DDIC.
i tried to login with new user but it not allowing me to login and giving error as Upgrade running logon not possible.
i tried to unlock shadow system by SAPehpi unlockshd <SID> but it is not working and giving error as FATAL ERROR: Calling 'tp.exe' failed with return code 232
Please help me to solve.
Thanks,
Venkat Raja
M:8657374364Hello Venkat,
Please run the below command to unlock the instance from ..../EHPI/abap/exe directory.
tp unlocksys <SAPSID> pf=<transport profile>
tp unlock_eu <SAPSID> pf=<transport profile>
Please note that these structure application errors has to be reviewed and cleared (in transaction LBWG) by your functional team with necessary approval from the client.
Thanks,
Siva Kumar -
Hello!
Have anyone seen this PREPARE error message before?
During phase RUN_RSPTBFIL_PREP, error message "2EETG011 Kein Upgrade aktiv".
I can't find any SAP note about this specific problem. The source system is 4.6B, the target will be a non-unicode ERP6 SR3, the os/db is AIX53/ora102.
//Fredrik
root@serverX:/usr/sap/put/log:more RSPTBINI.LOG
1 ETQ201XEntering upgrade-phase "RUN_RSPTBFIL_PREP" ("20080923124421")
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
4 ETQ010 Date & Time: 20080923124422
4 ETQ265 Starting report "RSPTBFIL" with variant "SAP_PRP_PUTTB" in batch
4 ETQ359 RFC Login to: System="SNB", Nr="00", GwHost="serverX", 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 "RSPTBFIL" with job count "12442401" scheduled
4 ETQ359 RFC Login to: System="SNB", Nr="00", GwHost="serverX", GwService="sapgw00"
4 ETQ232 RFC Login succeeded
4 ETQ010 Date & Time: 20080923124428
4 ETQ234 Call of function module "SUBST_CHECK_BATCHJOB" by RFC succeeded
4 ETQ239 Logging off from SAP system
4 ETQ399 ext. env.: DIR_LIBRARY=/sapmnt/SNB/exe
4 ETQ399 ext. env.: LIBPATH=/sapmnt/SNB/exe:/usr/lib:/lib:/usr/sap/SNB/SYS/exe/run:/oracle/SNB/102_64/lib64
4 ETQ399 2008/09/23 12:44:29: put_execute: (tp) forkpid:2142240
2EETQ241 Errors found in logfiles - accumulated in file "RSPTBINI.ELG"
1EETQ203 Upgrade phase "RUN_RSPTBFIL_PREP" aborted with errors ("20080923124430")
root@serverX:/usr/sap/put/log:more RSPTBINI.ELG
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
PUTTB initial filling ERRORS and RETURN CODE in RSPTBPTB.SNB
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2EETG011 "Kein Upgrade aktiv"
2EETG011 "Kein Upgrade aktiv"
root@serverX:/usr/sap/put/log:Hello Andreas, old friend from e-motion technology!
I did open a OSS-case some days ago, and we rerun the phase successfully.
I'm now waiting to hear from SAP-support, what they did, with their magic sticks, to fix this issue.
//Fredrik -
Error while applying EHP4 to ERP6.0-phase MAIN_NEWBAS/JOB_BATCHCHECK_XPRA!
while i was applying EHP4 to my ERP6.0 system using Enhancement Package Installer i got the following error in the Downtime roadmap:
Severe error(s) occured in phase MAIN_NEWBAS/JOB_BATCHCHECK_XPRA!
Last error code set: RFC_ERROR 2: DUMP_ERROR
i checked the RSUPGBWD.LOG and here is what i found:
1 ETQ201 Entering upgrade-phase "JOB_BATCHCHECK_XPRA" ("20110503131506")
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=SAPSR3
4 ETQ399 auth_shadow_upgrade=0
1 ETQ200 Executing actual phase 'MAIN_NEWBAS/JOB_BATCHCHECK_XPRA'.
1 ETQ399 Phase arguments:
2 ETQ399 Arg[0] = 'RSUPGBWD'
2 ETQ399 Arg[1] = ''
2 ETQ399 Arg[2] = 'IGNORE'
2 ETQ399 Arg[3] = 'RSUPGBWD\.$(SAPSID)'
2 ETQ399 Arg[4] = '3'
2 ETQ399 Arg[5] = 'Batch execution checker'
2 ETQ399 Arg[6] = 'RSUPGBWD.ELG'
4 ETQ260 Starting batchjob "RSUPGBWD"
4 ETQ010 Date & Time: 20110503131506
4 ETQ260 Starting batchjob "RSUPGBWD"
4 ETQ230 Starting RFC Login to: System = "ERD", GwHost = "erp-dev", GwService = "sapgw00"
4 ETQ233 Calling function module "SUBST_START_BATCHJOB" by RFC
4 ETQ399 JOBNAME='RSUPGBWD', REPNAME='RSUPGBWD', VARNAME='', BATCHHOST='erp-dev', IV_SCHEDEVER=' '
4 ETQ234 Call of function module "SUBST_START_BATCHJOB" by RFC succeeded
4 ETQ399 Returned JOBCOUNT='13150600'
4 ETQ233 Calling function module "SUBST_CHECK_BATCHJOB" by RFC
4 ETQ010 Date & Time: 20110503131509
4 ETQ234 Call of function module "SUBST_CHECK_BATCHJOB" by RFC succeeded
4 ETQ239 Logging off from SAP system
1EETQ242 Error code "-1" during analysis of logfiles matching "RSUPGBWD\.ERD"
2EETQ262 Batchjob "RSUPGBWD" aborted
4 ETQ359 RFC Login to: System="ERD", Nr="00", GwHost="erp-dev", GwService="sapgw00"
4 ETQ232 RFC Login succeeded
4 ETQ260 Starting batchjob "RSUPGBWD"
4 ETQ230 Starting RFC Login to: System = "ERD", GwHost = "erp-dev", GwService = "sapgw00"
4 ETQ233 Calling function module "SUBST_START_BATCHJOB" by RFC
4 ETQ399 JOBNAME='RSUPGBWD', REPNAME='RSUPGBWD', VARNAME='', BATCHHOST='erp-dev', IV_SCHEDEVER=' '
4 ETQ234 Call of function module "SUBST_START_BATCHJOB" by RFC succeeded
4 ETQ399 Returned JOBCOUNT='13150600'
4 ETQ233 Calling function module "SUBST_CHECK_BATCHJOB" by RFC
4 ETQ010 Date & Time: 20110503131509
4 ETQ234 Call of function module "SUBST_CHECK_BATCHJOB" by RFC succeeded
4 ETQ239 Logging off from SAP system
1EETQ242 Error code "-1" during analysis of logfiles matching "RSUPGBWD\.ERD"
2EETQ262 Batchjob "RSUPGBWD" aborted
4 ETQ359 RFC Login to: System="ERD", Nr="00", GwHost="erp-dev", GwService="sapgw00"
4 ETQ232 RFC Login succeeded
2WETQ360 RFC of "subst_list_sys_logs" failed:
2WETQ361 code/exception : DUMP_ERROR
5 ETQ359 RFC Login to: System="ERD", Nr="00", GwHost="erp-dev", GwService="sapgw00"
4 ETQ232 RFC Login succeeded
i also check ST22 for the error and i found this:
Runtime Errors CALL_FUNCTION_CO
Date and Time 03.05.2011 13:15
Short text
RFC error when sending logon data.
What happened?
An error occurred when executing a Remote Function Call.
What can you do?
Note which actions and input led to the error.
For further help in handling the problem, contact your SAP administrator
You can use the ABAP dump analysis transaction ST22 to view and manage
termination messages, in particular for long term reference.
Error analysis
An error occurred when executing a Remote Function Call.
Status of connection.... "-"
Internal error code.... "-"
How to correct the error
So any clue with that error?Hello Waseem,
I would recommend to update to the latest disp+work but also check in sm21 and find the work process that encountered the error. Then see in the corresponding work process trace file dev_w* for the real error that occured.
e.g. If you see ERROR => RFC Signon> Failure in ab_MakeTicketSndExternal calling
check note 1532825
and the report RS_TT_CLEANUP_SECSTORE
Regards,
Paul -
XPRA_UPG ERRORS UPGRADING TO ECC6
Hello Gurus
i am getting some errors during XPRAS_UPG.Ugrading from 4.7 to ECC6sr2 on Win2k3 64,SQL2005
I have checked R3up.ECO logs entries:
STARTSAP continues...
stopping on error 12 during EXECUTION OF REPORTS AFTER PUT
tp returncode summary:
TOOLS: Highest return code of single steps was: 12
WARNS: Highest tp internal warning was: 0118
tp finished with return code: 12
meaning:
A tool used by tp aborted
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
ERROR: stopping on error 12 during EXECUTION OF REPORTS AFTER PUT
Process with ID 9616 terminated with status 12
Deleting file c:\usr\sap\put\log\XPRASUPG.ELG
Moving file c:\usr\sap\put\log\PROT.TMP to c:\usr\sap\put\log\SAPR700ZEA.NTP
Moving file c:\usr\sap\put\log\XPRASUPG.ELG to c:\usr\sap\put\tmp\XPRASUPG.ELG
Deleting file c:\usr\sap\put\tmp\MSGIN.LST
Deleting file c:\usr\sap\put\tmp\MSGOUT.LST
Deleting file c:\usr\sap\put\tmp\MSGOUT.LOG
Deleting file c:\usr\sap\put\tmp\XPRASUPG.ELG
Deleting file c:\usr\sap\put\log\TP.ECO
Deleting file c:\usr\sap\put\bin\TRLIST.DMP
Deleting file c:\usr\sap\put\tmp\upalert.log
Deleting file c:\usr\sap\put\tmp\upalert.log
Copying file c:\usr\sap\put\buffer\NDP to c:\usr\sap\put\buffer\AFTXPRAS.BUF
Then i checked ACTUPG.ELG log:
LIST OF ERRORS AND RETURN CODES *******
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DDIC ACTIVATION ERRORS and RETURN CODE in SAPAA70010.NDP
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code : "4"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DDIC ACTIVATION ERRORS and RETURN CODE in SAPAA70011.NDP
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code : "4"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DDIC ACTIVATION ERRORS and RETURN CODE in SAPAA70012.NDP
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code : "4"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DDIC ACTIVATION ERRORS and RETURN CODE in SAPAA70013.NDP
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code : "4"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DDIC ACTIVATION ERRORS and RETURN CODE in SAPAA70014.NDP
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code : "4"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DDIC ACTIVATION ERRORS and RETURN CODE in SAPAA70015.NDP
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code : "4"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DDIC ACTIVATION ERRORS and RETURN CODE in SAPAAAA700.NDP
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code : "4"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DDIC ACTIVATION ERRORS and RETURN CODE in SAPAB70010.NDP
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code : "4"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DDIC ACTIVATION ERRORS and RETURN CODE in SAPAB70011.NDP
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code : "4"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DDIC ACTIVATION ERRORS and RETURN CODE in SAPAB70012.NDP
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code : "4"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DDIC ACTIVATION ERRORS and RETURN CODE in SAPAB70013.NDP
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code : "4"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DDIC ACTIVATION ERRORS and RETURN CODE in SAPAB70014.NDP
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code : "4"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DDIC ACTIVATION ERRORS and RETURN CODE in SAPAB70015.NDP
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code : "4"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DDIC ACTIVATION ERRORS and RETURN CODE in SAPACCC700.NDP
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code : "4"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DDIC ACTIVATION ERRORS and RETURN CODE in SAPACCC701.NDP
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code : "4"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DDIC ACTIVATION ERRORS and RETURN CODE in SAPACCC702.NDP
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code : "4"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DDIC ACTIVATION ERRORS and RETURN CODE in SAPACCG700.NDP
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code : "4"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DDIC ACTIVATION ERRORS and RETURN CODE in SAPACCG701.NDP
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code : "4"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DDIC ACTIVATION ERRORS and RETURN CODE in SAPACCG702.NDP
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code : "4"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DDIC ACTIVATION ERRORS and RETURN CODE in SAPAD70024.NDP
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code : "4"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DDIC ACTIVATION ERRORS and RETURN CODE in SAPAE60008.NDP
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code : "4"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DDIC ACTIVATION ERRORS and RETURN CODE in SAPAE60009.NDP
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code : "4"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DDIC ACTIVATION ERRORS and RETURN CODE in SAPAE60010.NDP
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code : "4"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DDIC ACTIVATION ERRORS and RETURN CODE in SAPAE60011.NDP
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code : "4"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DDIC ACTIVATION ERRORS and RETURN CODE in SAPAE60012.NDP
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code : "4"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DDIC ACTIVATION ERRORS and RETURN CODE in SAPAE60013.NDP
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code : "4"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DDIC ACTIVATION ERRORS and RETURN CODE in SAPAE60014.NDP
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code : "4"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DDIC ACTIVATION ERRORS and RETURN CODE in SAPAE60015.NDP
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code : "4"
and
XPRASUPG.ELG:
LIST OF ERRORS AND RETURN CODES *******
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
XPRA ERRORS and RETURN CODE in SAPR700ZEA.NDP
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1AETR012XProgram terminated (job: "RDDEXECL", no.: "16371300")
Long text:
Cause
Program "&V#&", which was started in the background, was terminated
abnormally.
System Response
The system created a job log for the terminated program.
What to do
Proceed as follows:
Log onto the system in which the program was executed. The system is
specified at the beginning of the transport log.
Then call transaction SM37 to display the job log.
Enter "&V#&" as job name and "DDIC" as user name.
Restrict the starting date to the starting date specified in the
transport log.
For the other selection criteria, select only jobs with the status
"cancelled". Then press <LS>Execute</>.
A list of the jobs satisfying the selection criteria is displayed.
You can display the log by pressing <LS>Job log</>.
If the list contains several jobs, you can select the job with the ID "
&V#&" with <LS>Display</> -> <LS>Job details</> or define further
details for the selection criteria in the initial screen of transaction
SM37.
If the ABAP processor reports cancellation, double-clicking on the
corresponding message in the job log branches to the display of the
corresponding short dump.
1AEPU320 See job log"RDDEXECL""16371300""NTP"
1 ETP111 exit code : "12"
>>> PLEASE READ THE REPORT DOCUMENTATION OF THE REPORTS MENTIONED ABOVE <<<
XPRAs are application reports that run at the end of an upgrade.
Most XPRA reports have a report documentation that explains what
the report does and how errors can be corrected.
Call transaction se38 in the SAP system, enter the report name,
select 'Documentation' and click the 'Display' button.
>>> The problematic XPRAs are mentioned in messages of type PU132 above <<<
I tried to execute the job RDDEXECL as DDIC in client 000 and it doesn`t run it quickly cancels with an ABAP dump SYNTAX_ERROR.I checked notes 980194,905029,821032,813658
So i went and checked in SE09 ,request/task,display individually,the transport logs
c:\usr\sap\put\log\*SAPLA70010.NDP* and discovered what might be the source of the problem:in SAPKA70010
different nametabs for table SEOCLASSDF (field CLSSHAREDMEMORY).
different nametabs for table SEOCLASSDF (field WITH_UNIT_TESTS).
different nametabs for table SEOCLASSDF (field DURATION_TYPE).
different nametabs for table SEOCLASSDF (field RISK_LEVEL).
in all the listed transport requests/support packs by ACTUPG.ELG log so how do i fix this problem in order to finish the upgrade?
Any ideas are most welcomeHi Attached is the dump:
Runtime Errors SYNTAX_ERROR
Date and Time 19.04.2008 16:47:26
Short text
Syntax error in program "%_CSCPR ".
What happened?
Error in the ABAP Application Program
The current ABAP program "SAPLSCPRPR" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
The following syntax error occurred in program "%_CSCPR " in include "%_CSCPR "
in
line 17:
"The type name "SCPR_FLDV_TAB" is ambiguous, since it is also defined i"
"n the Dictionary . control structure introduced with "CLASS" . . . . ."
The include has been created and last changed by:
Created by: "SAP "
Last changed by: "SAP "
Error in the ABAP Application Program
The current ABAP program "SAPLSCPRPR" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
What can you do?
Please eliminate the error by performing a syntax check
(or an extended program check) on the program "%_CSCPR ".
You can also perform the syntax check from the ABAP Editor.
If the problem persists, proceed as follows:
Note down which actions and inputs caused the error.
To process the problem further, contact you SAP system
administrator.
Using Transaction ST22 for ABAP Dump Analysis, you can look
at and manage termination messages, and you can also
keep them for a long time.
Error analysis
The following syntax error was found in the program %_CSCPR :
"The type name "SCPR_FLDV_TAB" is ambiguous, since it is also defined i"
"n the Dictionary . control structure introduced with "CLASS" . . . . ."
How to correct the error
Probably the only way to eliminate the error is to correct the program.
If you cannot solve the problem yourself and want to send an error
notification to SAP, include the following information:
1. The description of the current problem (short dump)
To save the description, choose "System->List->Save->Local File
(Unconverted)".
2. Corresponding system log
Display the system log by calling transaction SM21.
Restrict the time interval to 10 minutes before and five minutes
after the short dump. Then choose "System->List->Save->Local File
(Unconverted)".
3. If the problem occurs in a problem of your own or a modified SAP
program: The source code of the program
In the editor, choose "Utilities->More
Utilities->Upload/Download->Download".
4. Details about the conditions under which the error occurred or which
actions and input led to the error.
System environment
SAP-Release 700
Application server... "BDX1-sap02"
Network address...... "10.50.74.207"
Operating system..... "Windows NT"
Release.............. "5.2"
Hardware type........ "8x AMD64 Level"
Character length.... 8 Bits
Pointer length....... 64 Bits
Work process number.. 11
Shortdump setting.... "full"
Database server... "BDX1-SAP02"
Database type..... "MSSQL"
Database name..... "NDP"
Database user ID.. "ndp"
Char.set.... "English_United State"
SAP kernel....... 700
created (date)... "Feb 3 2008 22:36:38"
create on........ "NT 5.2 3790 Service Pack 1 x86 MS VC++ 14.00"
Database version. "SQL_Server_8.00 "
Patch level. 146
Patch text.. " "
Database............. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"
SAP database version. 700
Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows
NT 6.0"
Memory consumption
Roll.... 16128
EM...... 29329328
Heap.... 0
Page.... 32768
MM Used. 12958608
MM Free. 3797776
User and Transaction
Client.............. 000
User................ "DDIC"
Language key........ "E"
Transaction......... " "
Transactions ID..... "E384EEDB5E10F1EC892B001A64C1074E"
Program............. "SAPLSCPRPR"
Screen.............. "SAPMSSY0 1000"
Screen line......... 6
Information on where terminated
Termination occurred in the ABAP program "SAPLSCPRPR" - in
"SCPR_DB_ATTR_GET_LIST".
The main program was "RDDEXECU ".
In the source code you have the termination point in line 1
of the (Include) program "LSCPRPRU17".
The program "SAPLSCPRPR" was started as a background job.
Job Name....... "RDDEXECL"
Job Initiator.. "DDIC"
Job Number..... 16472600
Source Code Extract
Line
SourceCde
>>>>>
FUNCTION SCPR_DB_ATTR_GET_LIST.
2
3
""Lokale Schnittstelle:
4
*" IMPORTING
5
*" VALUE(CATEGORY) TYPE SCPRATTR-CATEGORY DEFAULT SPACE
6
*" VALUE(COMPONENT) TYPE SCPRATTR-COMPONENT OPTIONAL
7
*" VALUE(RELEASE) TYPE SCPRATTR-MAXRELEASE OPTIONAL
8
*" VALUE(MAX_COUNT) TYPE I OPTIONAL
9
*" EXPORTING
10
*" REFERENCE(SEL_COUNT) TYPE I
11
*" TABLES
12
*" PROFS STRUCTURE SCPRXPROF OPTIONAL
13
*" VERSIONS STRUCTURE SCPRXVERS OPTIONAL
14
*" PROFTYPES TYPE SCPR_XPTYPES OPTIONAL
15
*" CLI_DEPS STRUCTURE SCPRXCLDEP OPTIONAL
16
*" CLI_CASS STRUCTURE SCPRXCLCAS OPTIONAL
17
*" REFTYPES STRUCTURE SCPRXRTYPE OPTIONAL
18
*" REFERENCES STRUCTURE SCPRXREF OPTIONAL
19
*" MODDATES STRUCTURE SCPRXDAT OPTIONAL
20
*" MODIFIERS STRUCTURE SCPRXMOD OPTIONAL
Contents of system fields
Name
Val.
SY-SUBRC
0
SY-INDEX
0
SY-TABIX
1
SY-DBCNT
1
SY-FDPOS
2
SY-LSIND
0
SY-PAGNO
0
SY-LINNO
1
SY-COLNO
1
SY-PFKEY
SY-UCOMM
SY-TITLE
Execute Post-Import Methods and XPRAs for Transport Request
SY-MSGTY
SY-MSGID
SY-MSGNO
000
SY-MSGV1
CORR
SY-MSGV2
MERG
SY-MSGV3
SY-MSGV4
SY-MODNO
0
SY-DATUM
20080419
SY-UZEIT
164726
SY-XPROG
SAPLSYST
SY-XFORM
SYSTEM_HOOK_OPEN_DATASET
Active Calls/Events
No. Ty. Program Include Line
Name
7 FUNCTION SAPLSCPRPR LSCPRPRU17 1
SCPR_DB_ATTR_GET_LIST
6 FUNCTION SAPLSCPRPR LSCPRPRU19 60
SCPR_DB_ATTR_GET_ADDITIONAL
5 FUNCTION SAPLSCPRCRITICAL ??? 0
SCPR_SCP2_AFTER_IMPORT
4 FORM SAPLSCTS_EXE_EXP LSCTS_EXE_EXPF02 342
CALL_IMP_METHODS_IN_CLIENT
3 FORM SAPLSCTS_EXE_EXP LSCTS_EXE_EXPF02 87
CALL_IMP_METHODS
2 FUNCTION SAPLSCTS_EXE_EXP LSCTS_EXE_EXPU02 103
TRINT_CALL_AFTER_IMP_METHOD
1 EVENT RDDEXECU RDDEXECU 168
START-OF-SELECTION
Chosen variables
Name
Val.
No. 7 Ty. FUNCTION
Name SCPR_DB_ATTR_GET_LIST
CATEGORY
S
5
3
COMPONENT
222222222222222222222222222222
000000000000000000000000000000
MAX_COUNT
0
0000
0000
RELEASE
2222222222
0000000000
SEL_COUNT
0
0000
0000
CLI_CASS[]
Table[initial]
CLI_DEPS[]
Table[initial]
MODDATES[]
Table[initial]
MODIFIERS[]
Table[initial]
ORGIDS[]
Table[initial]
PROFOUT[]
PROFS[]
PROFTYPES[]
REFERENCES[]
REFTYPES[]
VERSIONS[]
CONTEXT_CLASSIC
2
0
CF_SOL_MANAGER
M
4
D
RTYPE_CUSTREC
CREC
4544
3253
RTYPE_TRANSPORT
TRAN
5544
421E
RTYPE_COPY
COPY
4455
3F09
ACT_DELETE
06
33
06
ACT_SHOW
03
33
03
OTYPE_TABLE
S
5
3
OTYPE_TLOGO
L
4
C
OTYPE_SPECIAL
T
5
4
OTYPE_UNKNOWN
U
5
5
RTYPE_NO_REFTYPE
2222
0000
ACT_MODIFY
02
33
02
OTYPE_VIEW
V
5
6
OTYPE_CLUSTER
C
4
3
ACT_CREATE
01
33
01
COL_BLUE
1
0000
1000
%_PRINT
000 0 ##
2222333222222222222222222222222222222222222222222222222222222222222222222222222222222222223200
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
SYST-REPID
SAPLSCPRPR
5454545555222222222222222222222222222222
310C330202000000000000000000000000000000
ICON_CLI_DEP
@0V@
43542222222222222222
00600000000000000000
CFLAG_ANY
VAL
544
61C
No. 6 Ty. FUNCTION
Name SCPR_DB_ATTR_GET_ADDITIONAL
CATEGORY
S
5
3
READ_ATTR
X
5
8
READ_DOCU
2
0
READ_SWITCH
2
0
READ_TADIR
2
0
READ_TEXT
2
0
REMOVED_BCSETS
Table[initial]
PROFLIST[]
Table IT_44[10683x298]
FUNCTION=SCPR_SCP2_AFTER_IMPORTDATA=BCSETS
Table reference: 27
TABH+ 0(20) = 50C21557FE070000B0C21557FE07000000000000
TABH+ 20(20) = 1B0000002C000000BB2900002A010000FFFFFFFF
TABH+ 40(16) = 04570000080D000010000000C1248001
store = 0x50C21557FE070000
ext1 = 0xB0C21557FE070000
shmId = 0 (0x00000000)
id = 27 (0x1B000000)
label = 44 (0x2C000000)
fill = 10683 (0xBB290000)
leng = 298 (0x2A010000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000049
occu = 16 (0x10000000)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 2 (cmpSingleMcmpR)
occu0 = 1
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
isCtfyAble = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0x70FA6557FE070000
pgHook = 0x70FD6657FE070000
idxPtr = 0x0000000000000000
shmTabhSet = 0x0000000000000000
id = 33 (0x21000000)
refCount = 0 (0x00000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 16368 (0xF03F0000)
lineAlloc = 10704 (0xD0290000)
shmVersId = 0 (0x00000000)
shmRefCount = 1 (0x01000000)
>>>>> 1st level extension part <<<<<
regHook = 0x60176657FE070000
collHook = 0x0000000000000000
ext2 = 0xB0416257FE070000
>>>>> 2nd level extension part <<<<<
tabhBack = 0xF0C11557FE070000
delta_head = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
pb_func = 0x0000000000000000
pb_handle = 0x0000000000000000
SY-SUBRC
0
0000
0000
FC_CANCEL
RW
5522
2700
FC_TAKE_NEW
TAKN
5444
41BE
<%_TABLE_SCPRSATTR>
FC_VALUE_HELP
VHLP
5445
68C0
BCSET_RANGE
IEQV1_ISHER_REP_PQUSPIQ_US_NSCH_DEG
4455354544555455555554555554544544422222222222222222222222222222222
95161F93852F250F0153091F53FE338F45700000000000000000000000000000000
FC_DEL_SUBP
DELS
4445
45C3
%_DUMMY$$
2222
0000
%_ITAB_DELETE_LIST
Table[initial]
<WA_PROFLIST>
V1_ISHER_REP_PQUSPIQ_US_NSCH_DEGN00000000000000
5354544555455555554555554544544443333333333333322222222222222222222222222222222222222222222222
61F93852F250F0153091F53FE338F457E0000000000000000000000000000000000000000000000000000000000000
BCSET_RANGES
Table IT_45[10683x67]
FUNCTION=SCPR_DB_ATTR_GET_ADDITIONALDATA=BCSET_RANGES
Table reference: 28
TABH+ 0(20) = 60436257FE070000000000000000000000000000
TABH+ 20(20) = 1C0000002D000000BB29000043000000FFFFFFFF
TABH+ 40(16) = 045900003011000010000000C1248001
store = 0x60436257FE070000
ext1 = 0x0000000000000000
shmId = 0 (0x00000000)
id = 28 (0x1C000000)
label = 45 (0x2D000000)
fill = 10683 (0xBB290000)
leng = 67 (0x43000000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000068
occu = 16 (0x10000000)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 2 (cmpSingleMcmpR)
occu0 = 1
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
isCtfyAble = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0x40176757FE070000
pgHook = 0x50D89357FE070000
idxPtr = 0x0000000000000000
shmTabhSet = 0x0000000000000000
id = 34 (0x22000000)
refCount = 0 (0x00000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 16304 (0xB03F0000)
lineAlloc = 10800 (0x302A0000)
shmVersId = 0 (0x00000000)
shmRefCount = 1 (0x01000000)
>>>>> 1st level extension part <<<<<
regHook = Not allocated
collHook = Not allocated
ext2 = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack = Not allocated
delta_head = Not allocated
pb_func = Not allocated
pb_handle = Not allocated
BCSETS_ATTRS
Table[initial]
SYST
000000000000B200000000000000000000000000000000000000000000000000000000000000200000000000000000
000000001000B900000000000000000000000000100020001000000010000000000000000000A10000000000000000
ICON_CLI_CAS
@0V@
43542222222222222222
00600000000000000000
TCATEGORY_CUSY
CUSY
4555
3539
No. 5 Ty. FUNCTION
Name SCPR_SCP2_AFTER_IMPORT
IT_E071
Table IT_42[10683x180]
FUNCTION-POOL=SCTS_EXE_EXPFORM=CALL_IMP_METHODS_IN_CLIENTDATA=LT_E071
Table reference: 26
TABH+ 0(20) = 90EF1457FE07000020444C57FE07000000000000
TABH+ 20(20) = 1A0000002A000000BB290000B4000000FFFFFFFF
TABH+ 40(16) = 044C0000080D000010000000C9248001
store = 0x90EF1457FE070000
ext1 = 0x20444C57FE070000
shmId = 0 (0x00000000)
id = 26 (0x1A000000)
label = 42 (0x2A000000)
fill = 10683 (0xBB290000)
leng = 180 (0xB4000000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000049
occu = 16 (0x10000000)
access = 1 (ItAccessStandard)
idxKind = 1 (ItIndexLinear)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 2 (cmpSingleMcmpR)
occu0 = 1
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
isCtfyAble = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0xC01B6757FE070000
pgHook = 0x20276757FE070000
idxPtr = 0xD0B58457FE070000
shmTabhSet = 0x0000000000000000
id = 31 (0x1F000000)
refCount = 0 (0x00000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 16368 (0xF03F0000)
lineAlloc = 10736 (0xF0290000)
shmVersId = 0 (0x00000000)
shmRefCount = 2 (0x02000000)
>>>>> 1st level extension part <<<<<
regHook = 0xD0F75357FE070000
collHook = 0x0000000000000000
ext2 = 0x0000000000000000
>>>>> 2nd level extension part <<<<<
tabhBack = Not allocated
delta_head = Not allocated
pb_func = Not allocated
pb_handle = Not allocated
IT_E071K
Table[initial]
IV_IS_UPGRADE
X
5
8
IV_TRKORR
SAPK700ZEA
54543335442222222222
310B700A510000000000
IT_CLIENT
Table IT_39[1x4]
FUNCTION=TRINT_CALL_AFTER_IMP_METHODDATA=LS_SPEC_PARS-CLIENTS
Table reference: 18
TABH+ 0(20) = A0B91557FE070000000000000000000000000000
TABH+ 20(20) = 12000000270000000100000004000000FFFFFFFF
TABH+ 40(16) = 044C00002813000019000000C1248001
store = 0xA0B91557FE070000
ext1 = 0x0000000000000000
shmId = 0 (0x00000000)
id = 18 (0x12000000)
label = 39 (0x27000000)
fill = 1 (0x01000000)
leng = 4 (0x04000000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000077
occu = 25 (0x19000000)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 2 (cmpSingleMcmpR)
occu0 = 1
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
isCtfyAble = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0x40F75357FE070000
pgHook = 0x0000000000000000
idxPtr = 0x0000000000000000
shmTabhSet = 0x0000000000000000
id = 28 (0x1C000000)
refCount = 0 (0x00000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 25 (0x19000000)
lineAlloc = 25 (0x19000000)
shmVersId = 0 (0x00000000)
shmRefCount = 1 (0x01000000)
>>>>> 1st level extension part <<<<<
regHook = Not allocated
collHook = Not allocated
ext2 = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack = Not allocated
delta_head = Not allocated
pb_func = Not allocated
pb_handle = Not allocated
<WA_E071>
SAPK700ZEA 010684R3TRSCP2V1_ISHER_REP_PQUSPIQ_US_NSCH_DEG
5454333544222222222233333353555453535454455545555555455555454454442222222222222222222222222222
310B700A5100000000000106842342330261F93852F250F0153091F53FE338F4570000000000000000000000000000
<%_L001>
<%_L001>-PGMID
TTYPE_R3TR
R3TR
5355
2342
SYST-REPID
SAPLSCPRCRITICAL
5454545545454444222222222222222222222222
310C33023294931C000000000000000000000000
<%_L001>-OBJECT
OBJECT_TYPE_SBCSET
SCP2
5453
3302
CONTEXT_CLASSIC
2
0
ACT_STOP_ICON
@3U@
4354
0350
SCPR_AUTHORITY_CHECK
X
5
8
FLD_STATUS_FLD_NM_KEY
FLD_NM_KEY
44454454452222222222
6C4FEDFB590000000000
BCSETS
Table IT_44[10683x298]
BCSET
V1_ISHER_REP_PQUSPIQ_US_NSCH_DEGN00000000000000
5354544555455555554555554544544443333333333333322222222222222222222222222222222222222222222222
61F93852F250F0153091F53FE338F457E0000000000000000000000000000000000000000000000000000000000000
REMOVED_BCSETS
Table[initial]
PCAT_SWITCH
S
5
3
INFO_SEL_REC
4
0000
4000
INFO_NAMESPACE
7
0000
7000
INFO_EQUALIZE
8
0000
8000
INFO_COMMIT
5
0000
5000
INFO_SHOW
6
0000
6000
INFO_SEL_PROFS
9
0000
9000
INFO_COMMIT_SET
10
0000
A000
CFLAG_ANY
VAL
544
61C
T_MESSAGES
Table[initial]
T_MESSAGE
0
3222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
SWITCH_BC_SET_ICON
@C1@
4434
0310
LTYPE_FIELD
FLD
4442
6C40
T_MESSAGE-LEVEL
0
3
0
No. 4 Ty. FORM
Name CALL_IMP_METHODS_IN_CLIENT
PS_SPEC_PARS-WITH_ASYNCH_MODE
2
0
SY-XPROG
SAPLSYST
5454555522222222222222222222222222222222
310C393400000000000000000000000000000000
PS_METHOD_CALL-METHOD_FB
SCPR_SCP2_AFTER_IMPORT
545555453544545544545522222222
3302F3302F16452F9D0F2400000000
GC_SCP2_AFTER_IMP
SCPR_SCP2_AFTER_IMPORT
545555453544545544545522222222
3302F3302F16452F9D0F2400000000
PS_SPEC_PARS-ASYNCH_MODE
2
0
GC_PARTNRPR_BACK_TO_STNDRD
1A&1B&1H&1I&2I&3R
34234234234234235
11612618619629632
PV_IS_UPGRADE
X
5
8
PS_CLIENT-CLIENT
222
000
GC_GNS_NO_DIFF
/0*/
2322222222
F0AF000000
LT_E071
Table IT_42[10683x180]
GC_GNS_NO_SPECIFIC
2222222222
FAF0000000
LT_E071K
Table[initial]
RELSET
RNO
544
2EF
PS_SPEC_PARS-WITH_CL_RESULTS
X
5
8
%_ARCHIVE
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
PV_TRKORR
SAPK700ZEA
54543335442222222222
310B700A510000000000
SYST-REPID
SAPLSCTS_EXE_EXP
5454545554545455222222222222222222222222
310C3343F585F580000000000000000000000000
DEVC_PREFIXNS
N
4
E
PS_SPEC_PARS-CLIENTS
Table IT_39[1x4]
%_PRINT
000 0 ##
2222333222222222222222222222222222222222222222222222222222222222222222222222222222222222223200
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
No. 3 Ty. FORM
Name CALL_IMP_METHODS
PV_TRKORR
SAPK700ZEA
54543335442222222222
310B700A510000000000
PV_NO_WORK_FOUND
2
0
GC_XPRA_COMPLETED
C
4
3
PT_CLIENT
Table IT_21[1x4]
PROGRAM=RDDEXECUDATA=GT_CLIENT
Table reference: 16
TABH+ 0(20) = 00AD1557FE070000000000000000000000000000
TABH+ 20(20) = 10000000150000000100000004000000FFFFFFFF
TABH+ 40(16) = 040000003808000019000000C1248001
store = 0x00AD1557FE070000
ext1 = 0x0000000000000000
shmId = 0 (0x00000000)
id = 16 (0x10000000)
label = 21 (0x15000000)
fill = 1 (0x01000000)
leng = 4 (0x04000000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000027
occu = 25 (0x19000000)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 2 (cmpSingleMcmpR)
occu0 = 1
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
isCtfyAble = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0x70AC1557FE070000
pgHook = 0x0000000000000000
idxPtr = 0x0000000000000000
shmTabhSet = 0x0000000000000000
id = 19 (0x13000000)
refCount = 0 (0x00000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 25 (0x19000000)
lineAlloc = 25 (0x19000000)
shmVersId = 0 (0x00000000)
shmRefCount = 1 (0x01000000)
>>>>> 1st level extension part <<<<<
regHook = Not allocated
collHook = Not allocated
ext2 = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack = Not allocated
delta_head = Not allocated
pb_func = Not allocated
pb_handle = Not allocated
LS_CLIENT_H
2222
0000
TTRA
T
5
4
SY
000000000000B200000000000000000000000000000000000000000000000000000000000000200000000000000000
000000001000B900000000000000000000000000100020001000000010000000000000000000A10000000000000000
PV_UPDATE_LOCKFLAG
X
5
8
PV_CTC
2
0
PV_STATLOG_FILE
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
PS_METHOD_CALL
AFTER_IMP SCPR_SCP2_AFTER_IMPORT #######È#######É###########ÿÿÿÿ
445455445254555545354454554454552222222220000000C0001000C00010000000FFFF
16452F9D003302F3302F16452F9D0F24000000000000000080007000900060000000FFFF
PV_IS_UPGRADE
X
5
8
PV_TOP_LEVEL
2
3
2
PS_SPEC_PARS
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
PS_METHOD_CALL-CLIDEP
2
0
PS_SPEC_PARS-WITH_CL_RESULTS
X
5
8
%_VIASELSCR
0
4
No. 2 Ty. FUNCTION
Name TRINT_CALL_AFTER_IMP_METHOD
IS_E070
SAPK700ZEA PRSAP SYSTSAPUSER 20080418120004
5454333544222222222255545222222255555455545222223333333333333322222222222222222222
310B700A51000000000002310000000039343105352000002008041812000400000000000000000000
IT_E071
Table IT_15 -
Error in PHASE ACT_UPG: Upgrade SAP R/3 4.7 to SAP ECC 6.0 EHP
Hello,
I'm facing an error in phase MAIN_SHDRUN/ACT_UPG (see errors below).
After searching for the errors I found postings with advice to change R3trans and tp to the newest version. Strangely system did not take the newest kernelpatch I stored in upgrade folder. So I changed the files in the /usr/sap/SID/abap/exe folder and repeated the phase.
But the error is still there.
A solution was to reset the queue, but this is only possible with help by sap.
Error in phase: DDIC_ACTIVATION
So I'm waiting for their reaction since two days, but nothing happens.
My questions are now:
what happens if I use the option "initialize phase ACT_UPG to restart it from beginning"? Will the new R3trans be used? Have we got to to the SPDD again?
What happens if I use the option "accept non severe errors and repeat phase ACT_UPG? Are these language errors "non-severe"?
Errors:
In error log ACTUPG.ELG I find logs like:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DDIC ACTIVATION ERRORS and RETURN CODE in SAPA-60016INERECRUIT.REX
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code : "8"
In error log SAPup.ECO I find:
EXECUTING /usr/sap/REX/upg/abap/exe/tp (/usr/sap/REX/upg/abap/exe/tp) pf=/usr/sap/REX/upg/abap/bin/ACTUPG.TPP put REX
This is /usr/sap/REX/upg/abap/exe/tp version 376.01.14 (release 701)
Warning: Parameter INTERRUPT is no longer used.
Warning: Parameter DAYLIGHT_SHUTDOWN is no longer used.
Warning: Parameter WITH_TACOB is no longer used.
Warning: Parameter IMPDP_BY_EVENT is no longer used.
Warning: Parameter INTERRUPT is no longer used.
Warning: Parameter DAYLIGHT_SHUTDOWN is no longer used.
Warning: Parameter WITH_TACOB is no longer used.
Warning: Parameter IMPDP_BY_EVENT is no longer used.
Looking for effective putsteps ... ... ready (looking for putsteps)
tp finished with return code: 8
meaning:
A tool used by tp produced errors
Process with ID 13163 terminated with status 8
In the last touched SP-File SAPAAAA701.SID I can find errors like:
"1EEDO545 "LANG" "DTEL" "*": Object information could not be imported"
Regards,
JuliaAfter pushing the message at SAP I got the following answer:
It is the problem from note 1417505. There is no guarantee that all objects where imported with the used R3trans. A rerun of phase will be unsuccessfully because error came up in DDIC_IMPORT.
A reset of the queue is only possible if SPAM/SAINT is used for importing support packages. In case of upgrade, like here, the upgrade has got to be resetted as described in upgrade guide.
After start between phase extraction and configuration the newest R3trans has got to be copied manually in /abap/exe folder.
Regards,
Julia -
Error in phase MAIN_SHDRUN/SUBMOD_FDC_RUN/PARMVNT_FDC - EHP3 upgrade
Hello all,
Using SUM while running SCM 7.0 EHP3 upgrade I am getting error in phase MAIN_SHDRUN/SUBMOD_FDC_RUN/PARMVNT_FDC:
Checks after phase MAIN_SHDRUN/SUBMOD_FDC_RUN/PARMVNT_FDC were negative!
Last error code set: Single errors (code > 8) found in logfile 'MVNTFDC.ELG'<br/> 1 tp processes returned errors. View latest 'TP*.ECO' files in log-directory for details
ERROR: Detected the following errors:
# D:\SUM\abap\log\PD000203.SCD:
3 ETP000 NOT NULL )
3 ETP000 ON [/BIC/FZT_DEL_C1_PSCH000]
3 ETP000 WITH ( DATA_COMPRESSION = PAGE )
3 ETP000
2WETP000 11:10:14: Retcode 1: error in DDL statement for "/1CRR/TG00003781 " - repeat
2EETP345 11:10:26: Retcode 1: SQL-error "2726-Partition function '/BIC/FZT_DEL_C1_PFUN000' uses 1 c
2EETP345 olumns which does not match with the number of partition columns used to partition the tab
2EETP345 le or index." in DDL statement for "/1CRR/TG00003781 "
2 ETP000 --------------- DB-ROLLBACK() ---------------
2EETP334 11:10:26: error in DDL, nametab for "/1CRR/TG00003781" not activated
3 ETP000 NOT NULL )
3 ETP000 ON [/BIC/FZT_DEL_C2_PSCH000]
3 ETP000 WITH ( DATA_COMPRESSION = PAGE )
...skipped 18 more lines. Please see MVNTFDC.html for more information.
I checked some other log files:
MVNTFDC
1 ETQ201 Entering upgrade-phase "MAIN_SHDRUN/SUBMOD_FDC_RUN/PARMVNT_FDC" ("20150203110951")
2 ETQ367 Connect variables are set for standard instance access
4 ETQ399 System-nr = '00', GwService = 'sapgw00' Client = '000'
1 ETQ206 Executing pre-phase DB specific actions.
1 ETQ200 Executing actual phase 'MAIN_SHDRUN/SUBMOD_FDC_RUN/PARMVNT_FDC'.
1 ETQ399 Phase arguments:
2 ETQ399 Arg[0] = 'TP_MOVENTABS_SHD'
2 ETQ399 Arg[1] = 'INTDEL;INTACT;NOBUFFRESET;SHADOW_ONLY'
2 ETQ399 Arg[2] = 'MF=F,STEP=T,RANGE-TS'
2 ETQ399 Arg[3] = 'MVNTFDC.TP0'
1 ETQ399 Using error summary log 'MVNTFDC.ELG'.
1 ETQ399 Using 8 parallel processes
2 ETQ399 Empty putsteps - configuring at least parallel batches and main import processes.
2 ETQ399 Distribute 8 parallel processes to 2 tp and 4 R3trans.
4 ETQ380 computing toolpath for request "TP_MOVENTABS_SHD"
4 ETQ381 request "TP_MOVENTABS_SHD" means "tp mvntabs for shadow tables"
4 ETQ382 translates to group "R3UP_TOOL_GROUP_SHD"
4 ETQ399 Requirement for tp maps to 'exe'
4 ETQ383 translates to path "D:\SUM\abap\exe"
2 ETQ399 Starting 8 tp processes:
4 ETQ010 Starting: tp ddlntabs operation
3 ETQ121 20150203110952: PID 7444 execute 'D:\SUM\abap\exe\tp "pf=D:\SUM\abap\var\MVNTFDC.TPP" ddlntabs SCD "ddlmode=F" "step=T" "protyear=00" "seltsize=0" shadow_only "strel=701" "substext=4G" "-Dbuffreset=no"' in background, output written to 'D:\SUM\abap\log\TP00.ECO'.
2 ETQ399 Started tp ddlntabs with pid 7444
4 ETQ010 Starting: tp ddlntabs operation
3 ETQ121 20150203110952: PID 4888 execute 'D:\SUM\abap\exe\tp "pf=D:\SUM\abap\var\MVNTFDC.TPP" ddlntabs SCD "ddlmode=F" "step=T" "protyear=01" "seltsize=1" shadow_only "strel=701" "substext=4G" "-Dbuffreset=no"' in background, output written to 'D:\SUM\abap\log\TP01.ECO'.
2 ETQ399 Started tp ddlntabs with pid 4888
4 ETQ010 Starting: tp ddlntabs operation
3 ETQ121 20150203110952: PID 9100 execute 'D:\SUM\abap\exe\tp "pf=D:\SUM\abap\var\MVNTFDC.TPP" ddlntabs SCD "ddlmode=F" "step=T" "protyear=02" "seltsize=2" shadow_only "strel=701" "substext=4G" "-Dbuffreset=no"' in background, output written to 'D:\SUM\abap\log\TP02.ECO'.
2 ETQ399 Started tp ddlntabs with pid 9100
4 ETQ010 Starting: tp ddlntabs operation
3 ETQ121 20150203110952: PID 736 execute 'D:\SUM\abap\exe\tp "pf=D:\SUM\abap\var\MVNTFDC.TPP" ddlntabs SCD "ddlmode=F" "step=T" "protyear=03" "seltsize=3" shadow_only "strel=701" "substext=4G" "-Dbuffreset=no"' in background, output written to 'D:\SUM\abap\log\TP03.ECO'.
2 ETQ399 Started tp ddlntabs with pid 736
4 ETQ010 Starting: tp ddlntabs operation
3 ETQ121 20150203110952: PID 8864 execute 'D:\SUM\abap\exe\tp "pf=D:\SUM\abap\var\MVNTFDC.TPP" ddlntabs SCD "ddlmode=F" "step=T" "protyear=04" "seltsize=4" shadow_only "strel=701" "substext=4G" "-Dbuffreset=no"' in background, output written to 'D:\SUM\abap\log\TP04.ECO'.
2 ETQ399 Started tp ddlntabs with pid 8864
4 ETQ010 Starting: tp ddlntabs operation
3 ETQ121 20150203110952: PID 9264 execute 'D:\SUM\abap\exe\tp "pf=D:\SUM\abap\var\MVNTFDC.TPP" ddlntabs SCD "ddlmode=F" "step=T" "protyear=05" "seltsize=5" shadow_only "strel=701" "substext=4G" "-Dbuffreset=no"' in background, output written to 'D:\SUM\abap\log\TP05.ECO'.
2 ETQ399 Started tp ddlntabs with pid 9264
4 ETQ010 Starting: tp ddlntabs operation
3 ETQ121 20150203110952: PID 9732 execute 'D:\SUM\abap\exe\tp "pf=D:\SUM\abap\var\MVNTFDC.TPP" ddlntabs SCD "ddlmode=F" "step=T" "protyear=06" "seltsize=6" shadow_only "strel=701" "substext=4G" "-Dbuffreset=no"' in background, output written to 'D:\SUM\abap\log\TP06.ECO'.
2 ETQ399 Started tp ddlntabs with pid 9732
4 ETQ010 Starting: tp ddlntabs operation
3 ETQ121 20150203110952: PID 11492 execute 'D:\SUM\abap\exe\tp "pf=D:\SUM\abap\var\MVNTFDC.TPP" ddlntabs SCD "ddlmode=F" "step=T" "protyear=07" "seltsize=7" shadow_only "strel=701" "substext=4G" "-Dbuffreset=no"' in background, output written to 'D:\SUM\abap\log\TP07.ECO'.
2 ETQ399 Started tp ddlntabs with pid 11492
3 ETQ123 20150203110954: PID 9264 exited with status 0 (time 0.000 real)
2 ETQ399 tp ddlntabs finished with exit code 0.
3 ETQ123 20150203110954: PID 7444 exited with status 0 (time 0.000 real)
2 ETQ399 tp ddlntabs finished with exit code 0.
3 ETQ123 20150203110954: PID 4888 exited with status 0 (time 0.000 real)
2 ETQ399 tp ddlntabs finished with exit code 0.
3 ETQ123 20150203110954: PID 736 exited with status 0 (time 0.000 real)
2 ETQ399 tp ddlntabs finished with exit code 0.
3 ETQ123 20150203110954: PID 9732 exited with status 0 (time 0.000 real)
2 ETQ399 tp ddlntabs finished with exit code 0.
3 ETQ123 20150203110956: PID 11492 exited with status 0 (time 0.000 real)
2 ETQ399 tp ddlntabs finished with exit code 0.
3 ETQ123 20150203110956: PID 9100 exited with status 0 (time 0.000 real)
2 ETQ399 tp ddlntabs finished with exit code 0.
3 ETQ123 20150203110956: PID 8864 exited with status 0 (time 0.000 real)
2 ETQ399 tp ddlntabs finished with exit code 0.
2 ETQ399 Looking for pattern 'PD00....\.SCD'
2 ETQ399 Wasting log file 'D:\SUM\abap\log\PD000203.SCD'.
1 ETQ124 Scanned file 'log\PD000203.SCD' from offset 9525 to 12695 for errors.
2 ETQ399 Operation 'ddlntabs' looking for pattern 'PD00....\.SCD'
2 ETQ399 Looking for pattern 'PD01....\.SCD'
2 ETQ399 Wasting log file 'D:\SUM\abap\log\PD010203.SCD'.
1 ETQ124 Scanned file 'log\PD010203.SCD' from offset 3394 to 6564 for errors.
2 ETQ399 Operation 'ddlntabs' looking for pattern 'PD01....\.SCD'
2 ETQ399 Looking for pattern 'PD02....\.SCD'
2 ETQ399 Wasting log file 'D:\SUM\abap\log\PD020203.SCD'.
1 ETQ124 Scanned file 'log\PD020203.SCD' from offset 3394 to 6564 for errors.
2 ETQ399 Operation 'ddlntabs' looking for pattern 'PD02....\.SCD'
2 ETQ399 Looking for pattern 'PD03....\.SCD'
2 ETQ399 Wasting log file 'D:\SUM\abap\log\PD030203.SCD'.
1 ETQ124 Scanned file 'log\PD030203.SCD' from offset 3394 to 6564 for errors.
2 ETQ399 Operation 'ddlntabs' looking for pattern 'PD03....\.SCD'
2 ETQ399 Looking for pattern 'PD04....\.SCD'
2 ETQ399 Wasting log file 'D:\SUM\abap\log\PD040203.SCD'.
1 ETQ124 Scanned file 'log\PD040203.SCD' from offset 3394 to 6564 for errors.
2 ETQ399 Operation 'ddlntabs' looking for pattern 'PD04....\.SCD'
2 ETQ399 Looking for pattern 'PD05....\.SCD'
2 ETQ399 Wasting log file 'D:\SUM\abap\log\PD050203.SCD'.
1 ETQ124 Scanned file 'log\PD050203.SCD' from offset 3394 to 6564 for errors.
2 ETQ399 Operation 'ddlntabs' looking for pattern 'PD05....\.SCD'
2 ETQ399 Looking for pattern 'PD06....\.SCD'
2 ETQ399 Wasting log file 'D:\SUM\abap\log\PD060203.SCD'.
1 ETQ124 Scanned file 'log\PD060203.SCD' from offset 3394 to 6564 for errors.
2 ETQ399 Operation 'ddlntabs' looking for pattern 'PD06....\.SCD'
2 ETQ399 Looking for pattern 'PD07....\.SCD'
2 ETQ399 Wasting log file 'D:\SUM\abap\log\PD070203.SCD'.
1 ETQ124 Scanned file 'log\PD070203.SCD' from offset 3394 to 6564 for errors.
2 ETQ399 Operation 'ddlntabs' looking for pattern 'PD07....\.SCD'
2 ETQ399 Starting 1 tp processes:
4 ETQ010 Starting: tp ddlntabs operation
3 ETQ121 20150203111013: PID 8692 execute 'D:\SUM\abap\exe\tp "pf=D:\SUM\abap\var\MVNTFDC.TPP" ddlntabs SCD "ddlmode=F" "step=T" "protyear=00" shadow_only "strel=701" "substext=4G" "-Dbuffreset=no"' in background, output written to 'D:\SUM\abap\log\TP00.ECO'.
2 ETQ399 Started tp ddlntabs with pid 8692
3 ETQ123 20150203111050: PID 8692 exited with status 8 (time 0.000 real)
2EETQ399 tp ddlntabs failed with exit code 8.
2 ETQ399 Operation 'ddlntabs' looking for pattern 'PD00....\.SCD'
1 ETQ124 Scanned file 'log\PD000203.SCD' from offset 12805 to 18826 for errors.
4 ETQ399 html file conversion from 'D:\SUM\abap\log\MVNTFDC.ELG' to 'MVNTFDC.html' succeeded.
4 ETQ010 Date & Time: 20150203111051
1EETQ399 Last error code set is: Single errors (code > 8) found in logfile 'MVNTFDC.ELG'
1 tp processes returned errors. View latest 'TP*.ECO' files in log-directory for details
1EETQ203 Upgrade phase "PARMVNT_FDC" aborted with errors ("20150203111051")
TP00.ECO
SAPup> Starting subprocess in phase 'TP_ACTION_CP2SINI' at 20150202112054
ENV: PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC
ENV: PATH=D:\SUM\abap\exe;D:\sapdb\programs\bin;D:\sapdb\programs\pgm;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Windows Imaging\;C:\Program Files\System Center Operations Manager 2007\;D:\Program Files\Microsoft SQL Server\100\Tools\Binn;D:\usr\sap\SCD\SYS\exe\uc\NTAMD64
ENV: SAPSYSTEMNAME=SCD
ENV: dbms_type=mss
ENV: dbs_mss_schema=scd
PWD: D:\SUM\abap\tmp
EXECUTING D:\SUM\abap\exe\tp.EXE "pf=D:\SUM\abap\var\CP2SHDI.TPP" r3e SAPKBBF740 -s SCD u18
This is D:\SUM\abap\exe\tp.EXE version 380.27.37 (release 741, unicode enabled)
This is D:\SUM\abap\exe\R3trans.exe version 6.24 (release 741 - 11.08.14 - 17:21:00).
unicode enabled version
D:\SUM\abap\exe\R3trans.exe finished (0004).
INFO: No client specified on command line. Taking client 0 from E070C.
tp finished with return code: 4
meaning:
A tool used by tp produced warnings
SAPup> Process with PID 7592 terminated with status 4 at 20150202112055!
SAPup> Starting subprocess in phase 'PARMVNT_FDC' at 20150202213004
ENV: PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC
ENV: PATH=D:\SUM\abap\exe;D:\sapdb\programs\bin;D:\sapdb\programs\pgm;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Windows Imaging\;C:\Program Files\System Center Operations Manager 2007\;D:\Program Files\Microsoft SQL Server\100\Tools\Binn;D:\usr\sap\SCD\SYS\exe\uc\NTAMD64
ENV: SAPSYSTEMNAME=SCD
ENV: dbms_type=mss
ENV: dbs_mss_schema=scd
PWD: D:\SUM\abap\tmp
EXECUTING D:\SUM\abap\exe\tp.EXE "pf=D:\SUM\abap\var\MVNTFDC.TPP" ddlntabs SCD "ddlmode=F" "step=T" "protyear=00" "seltsize=0" shadow_only "strel=701" "substext=4G" "-Dbuffreset=no"
This is D:\SUM\abap\exe\tp.EXE version 380.27.37 (release 741, unicode enabled)
tp finished with return code: 0
meaning:
Everything OK
SAPup> Starting subprocess in phase 'PARMVNT_FDC' at 20150202213118
ENV: PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC
ENV: PATH=D:\SUM\abap\exe;D:\sapdb\programs\bin;D:\sapdb\programs\pgm;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Windows Imaging\;C:\Program Files\System Center Operations Manager 2007\;D:\Program Files\Microsoft SQL Server\100\Tools\Binn;D:\usr\sap\SCD\SYS\exe\uc\NTAMD64
ENV: SAPSYSTEMNAME=SCD
ENV: dbms_type=mss
ENV: dbs_mss_schema=scd
PWD: D:\SUM\abap\tmp
EXECUTING D:\SUM\abap\exe\tp.EXE "pf=D:\SUM\abap\var\MVNTFDC.TPP" ddlntabs SCD "ddlmode=F" "step=T" "protyear=00" shadow_only "strel=701" "substext=4G" "-Dbuffreset=no"
This is D:\SUM\abap\exe\tp.EXE version 380.27.37 (release 741, unicode enabled)
tp finished with return code: 8
meaning:
A tool used by tp produced errors
SAPup> Process with PID 5336 terminated with status 8 at 20150202213638!
SAPup> Starting subprocess in phase 'PARMVNT_FDC' at 20150203102328
ENV: PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC
ENV: PATH=D:\SUM\abap\exe;D:\sapdb\programs\bin;D:\sapdb\programs\pgm;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Windows Imaging\;C:\Program Files\System Center Operations Manager 2007\;D:\Program Files\Microsoft SQL Server\100\Tools\Binn;D:\usr\sap\SCD\SYS\exe\uc\NTAMD64
ENV: SAPSYSTEMNAME=SCD
ENV: dbms_type=mss
ENV: dbs_mss_schema=scd
PWD: D:\SUM\abap\tmp
EXECUTING D:\SUM\abap\exe\tp.EXE "pf=D:\SUM\abap\var\MVNTFDC.TPP" ddlntabs SCD "ddlmode=F" "step=T" "protyear=00" "seltsize=0" shadow_only "strel=701" "substext=4G" "-Dbuffreset=no"
This is D:\SUM\abap\exe\tp.EXE version 380.27.37 (release 741, unicode enabled)
tp finished with return code: 0
meaning:
Everything OK
SAPup> Starting subprocess in phase 'PARMVNT_FDC' at 20150203102350
ENV: PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC
ENV: PATH=D:\SUM\abap\exe;D:\sapdb\programs\bin;D:\sapdb\programs\pgm;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Windows Imaging\;C:\Program Files\System Center Operations Manager 2007\;D:\Program Files\Microsoft SQL Server\100\Tools\Binn;D:\usr\sap\SCD\SYS\exe\uc\NTAMD64
ENV: SAPSYSTEMNAME=SCD
ENV: dbms_type=mss
ENV: dbs_mss_schema=scd
PWD: D:\SUM\abap\tmp
EXECUTING D:\SUM\abap\exe\tp.EXE "pf=D:\SUM\abap\var\MVNTFDC.TPP" ddlntabs SCD "ddlmode=F" "step=T" "protyear=00" shadow_only "strel=701" "substext=4G" "-Dbuffreset=no"
This is D:\SUM\abap\exe\tp.EXE version 380.27.37 (release 741, unicode enabled)
tp finished with return code: 8
meaning:
A tool used by tp produced errors
SAPup> Process with PID 10396 terminated with status 8 at 20150203102427!
SAPup> Starting subprocess in phase 'PARMVNT_FDC' at 20150203110952
ENV: PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC
ENV: PATH=D:\SUM\abap\exe;D:\sapdb\programs\bin;D:\sapdb\programs\pgm;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Windows Imaging\;C:\Program Files\System Center Operations Manager 2007\;D:\Program Files\Microsoft SQL Server\100\Tools\Binn;D:\usr\sap\SCD\SYS\exe\uc\NTAMD64
ENV: SAPSYSTEMNAME=SCD
ENV: dbms_type=mss
ENV: dbs_mss_schema=scd
PWD: D:\SUM\abap\tmp
EXECUTING D:\SUM\abap\exe\tp.EXE "pf=D:\SUM\abap\var\MVNTFDC.TPP" ddlntabs SCD "ddlmode=F" "step=T" "protyear=00" "seltsize=0" shadow_only "strel=701" "substext=4G" "-Dbuffreset=no"
This is D:\SUM\abap\exe\tp.EXE version 380.27.37 (release 741, unicode enabled)
tp finished with return code: 0
meaning:
Everything OK
SAPup> Starting subprocess in phase 'PARMVNT_FDC' at 20150203111013
ENV: PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC
ENV: PATH=D:\SUM\abap\exe;D:\sapdb\programs\bin;D:\sapdb\programs\pgm;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Windows Imaging\;C:\Program Files\System Center Operations Manager 2007\;D:\Program Files\Microsoft SQL Server\100\Tools\Binn;D:\usr\sap\SCD\SYS\exe\uc\NTAMD64
ENV: SAPSYSTEMNAME=SCD
ENV: dbms_type=mss
ENV: dbs_mss_schema=scd
PWD: D:\SUM\abap\tmp
EXECUTING D:\SUM\abap\exe\tp.EXE "pf=D:\SUM\abap\var\MVNTFDC.TPP" ddlntabs SCD "ddlmode=F" "step=T" "protyear=00" shadow_only "strel=701" "substext=4G" "-Dbuffreset=no"
This is D:\SUM\abap\exe\tp.EXE version 380.27.37 (release 741, unicode enabled)
tp finished with return code: 8
meaning:
A tool used by tp produced errors
SAPup> Process with PID 8692 terminated with status 8 at 20150203111050!
Can someone please help ?Hi Pankaj,
did you get any solution for this issue ? I am also facing the same error in my BW upgrade to EHP3.
Please share the solution if you get any.
Regards, -
EHP installing. Error in phase MAIN_SHDRUN/JOB_MSSSPEXE_SHD
Hello all,
Dealing with ECC's EHP4 installation and having problem with step JOB_MSSSPEXE_SHD.
Firstly, want to give some system overview.
System was migrated from x32 non-Unicode to x64 Unicode through SystemCopy
OS: Windows Server 2008 SP2
DB: MS SQL Server 2008 version 10.0.2531.0
SAP: (only ABAP Web AS is installed)
NW 7.0, ECC 6.0 SPS 20, kernel version 7.0 236
java version - 1.4.2_17-x64
Now doing installation of ECC EHP 4 / NW 7.01 SPS6 .
Using SAPehpi 710 2.005.001 package 24
Using latest dbmsslib.dll (released 05/12/2010)
Had no problems till the Preprocessing Step
Error that EHPi produced is:
Severe error(s) occured in phase MAIN_SHDRUN/JOB_MSSSPEXE_SHD!
Last error code set: BATCHJOB MSSSPEXE on shadow instance FAILED: Batchjob MSSSPEXE aborted.
JOBLOG.LOG :
|Time |User |Program |Priority|Grp|N|Text |
|09:25:07|SAPSYS|RSBTCRTE| |EB |E|Failed to read step $$$$$ of job (database error code: 00064)|
|09:25:07|SAPSYS|RSBTCRTE| |EB |C|> Job MSSSPEXE |
|09:25:07|SAPSYS|RSBTCRTE| |D0 |1|Transaction Canceled 00 529 ( 001 ) |
PMSSSPEXE.LOG:
1 ETQ200 Executing actual phase 'MAIN_SHDRUN/JOB_MSSSPEXE_SHD'.
1 ETQ399 Phase arguments:
2 ETQ399 Arg[0] = 'MSSSPEXE'
2 ETQ399 Arg[1] = ''
2 ETQ399 Arg[2] = 'NO-IGNORE'
2 ETQ399 Arg[3] = ''
2 ETQ399 Arg[4] = '5'
2 ETQ399 Arg[5] = 'MSSQL SPECIFIC ACTIONS'
2 ETQ399 Arg[6] = 'PMSSSPEX.ELG'
4 ETQ260 Starting batchjob "MSSSPEXE"
4 ETQ010 Date & Time: 20100625092507
4 ETQ260 Starting batchjob "MSSSPEXE"
4 ETQ230 Starting RFC Login to: System = "PRD", GwHost = "SAP", GwService = "sapgw01"
4 ETQ233 Calling function module "SUBST_START_BATCHJOB" by RFC
4 ETQ399 JOBNAME='MSSSPEXE', REPNAME='MSSSPEXE', VARNAME='', BATCHHOST='SAP', IV_SCHEDEVER=' '
4 ETQ234 Call of function module "SUBST_START_BATCHJOB" by RFC succeeded
4 ETQ399 Returned JOBCOUNT='09250700'
4 ETQ233 Calling function module "SUBST_CHECK_BATCHJOB" by RFC
4 ETQ010 Date & Time: 20100625092512
4 ETQ234 Call of function module "SUBST_CHECK_BATCHJOB" by RFC succeeded
4 ETQ239 Logging off from SAP system
2EETQ262 Batchjob "MSSSPEXE" aborted
4 ETQ359 RFC Login to: System="PRD", Nr="01", GwHost="SAP", GwService="sapgw01"
4 ETQ232 RFC Login succeeded
Next I've connected to shadow instance, increased Trace level of batch process to 3 and went to ST11.
dev_w12 log:
L BtcAuthSet: Begin: username=DDIC
L BtcAuthSet: zttabtckln = 500
L BtcAuthSet: jobname=MSSSPEXE , jobcount=09250700, status=S
L BtcAuthSet: jobgroup=%_IMMEDIATE , stepcount=0
L BtcAuthSet: authcknam= , authckman=000
L BtcAuthSet: step_cnt=33679104
L BtcAuthSet: step_ptr->stepcount=1
B { db_rtab( fcode = 'RT_READ_ONLY', tname = 'TBTCPV' ) {btcjcntl.c:941}
B NTAB: tabname: TBTCPV , fcode: 1
M PfSetActDBConRec: record found for dbcon <>
M PfStatBegin: open DBCON rec with opcode 10
M push timestack[0] = STAT_READDIR
M pop timestack[0] = STAT_READDIR
M PfStatEnd: close DBCON rec after opcode 10
M PfSetActDBConRec: record found for dbcon <>
M PfStatBegin: open DBCON rec with opcode 10
M push timestack[0] = STAT_READDIR
M pop timestack[0] = STAT_READDIR
M PfStatEnd: close DBCON rec after opcode 10
B } db_rtab( fcode = 'RT_READ_ONLY', retcode = 64 )
L *** ERROR => BtcAuthSet: db_rtab-call failed, rc: 64 [btcjcntl.c 946]
A + SAPSYS 40088 BATCH 00 529 rlv=clean
A RFC> get SPA_SESSION_ARFC: NORMAL
A RFC> ab_RfcTraceConnInfo (OFF) (handle: 0, dump_connection_info: 0)
A ab_rfcclose_ex: closed 0 handles for owner 39368 (0 skipped)
A RFC> not running in Plugin session
Free space is about 50 Gb on server. Database files have unrestricted growth.
I have no idea what kind of error is "db_rtab-call failed, rc: 64"
Any help will be highly appreciated.
Thank you
AlexeyHi
I am getting error in MSSSPEXE job in Preprocessing phase in Ehp6 upgrade.
MAIN_SHDPREPUT/JOB_MSSSPEXE_SHD_PRE
MSSSPEXE job aborted
Batchjob 'MSSSPEXE' with id '11484300' aborted
Reviewing Short dump is says the following:
Runtime Errors SYNTAX_ERROR
Date and Time 03.11.2013 00:47:55
Short Text
Syntax error in program "SAPLMSSPROCS ".
What happened?
Error in the ABAP Application Program
The current ABAP program "MSSSPEXE" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
The following syntax error occurred in program "SAPLMSSPROCS " in inclu
"LMSSPROCSUXX " in
line 9:
"INCLUDE report "LMSSPROCSU04" not found"
The include has been created and last changed by:
Created by: "SAP "
Last changed by: "SAP "
Error in the ABAP Application Program
The current ABAP program "MSSSPEXE" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
Runtime Errors SYNTAX_ERROR
Date and Time 03.11.2013 00:47:55
Short Text
Syntax error in program "SAPLMSSPROCS ".
What happened?
Error in the ABAP Application Program
The current ABAP program "MSSSPEXE" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
The following syntax error occurred in program "SAPLMSSPROCS " in inclu
"LMSSPROCSUXX " in
line 9:
"INCLUDE report "LMSSPROCSU04" not found"
The include has been created and last changed by:
Created by: "SAP "
Last changed by: "SAP "
Error in the ABAP Application Program
The current ABAP program "MSSSPEXE" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
Regards -
Error during phase XPRAS_TRANS in module MAIN_TRANSEXEC while updating to EHP7 on HANA
Dear Gurus,
I request your help to resolve the below mentioned error.
I got the below error while updating my system from EHP6 to EHP7 SPS03.
The details of the logs and the versions are mentioned below for your reference:
SAPup_troubleticket.log
SAPup broke during phase XPRAS_TRANS in module MAIN_TRANSEXEC / Downtime for transport mode
Error Message: Detected 99 errors summarized in 'XPRASUPG.ELG'
Calling 'E:\usr\sap\ERH\DVEBMGS00\exe/tp' failed with return code 8, check F:\SUM\SUM\abap\log\SAPup.ECO for details
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
XPRA ERRORS and RETURN CODE in SAPR-617BRINSAPAPPL.ERH
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
A3 ESNHI_DELIVERY_UNIT 007 Number of deleted objects: "0"
A3 ESNHI_DELIVERY_UNIT 010 A complete HANA delivery unit was imported.
A3 ESNHI_DELIVERY_UNIT 013 Content snapshot was uploaded in source system " " at " ".
A3 ESNHI_DELIVERY_UNIT 014 Details: Vendor " ", Version " ", Support Package " ", Patch " "
A3 ESNHI_DELIVERY_UNIT 081 HANA delivery unit name: " "
A2EESNHI_DELIVERY_UNIT 080 Aggregated import of HANA Delivery Units failed
A4EESNHI_DELIVERY_UNIT 025 "Repository: Encountered an int""ernal error in the repository""code, this is most likely a bu""g in the implementation;failed"
A4EESNHI_DELIVERY_UNIT 025 "to write attached content to""file"" "" "
A3 ESNHI_DELIVERY_UNIT 007 Number of deleted objects: "0"
A3 ESNHI_DELIVERY_UNIT 010 A complete HANA delivery unit was imported.
A3 ESNHI_DELIVERY_UNIT 013 Content snapshot was uploaded in source system " " at " ".
A3 ESNHI_DELIVERY_UNIT 014 Details: Vendor " ", Version " ", Support Package " ", Patch " "
A3 ESNHI_DELIVERY_UNIT 081 HANA delivery unit name: " "
A2EESNHI_DELIVERY_UNIT 080 Aggregated import of HANA Delivery Units failed
A4EESNHI_DELIVERY_UNIT 025 "Repository: Encountered an int""ernal error in the repository""code, this is most likely a bu""g in the implementation;failed"
A4EESNHI_DELIVERY_UNIT 025 "to write attached content to""file"" "" "
2EEPU133 Errors occurred during post-handling "SNHI_DELIVERY_UNIT_IMPORT" for "NHDU" "L"
3 EPU135 "SNHI_DELIVERY_UNIT_IMPORT" belongs to package "SNHI_DELIVERY_UNIT_PROXY"
2EEPU136 The errors affect the following components:
2EEPU137 "BC-DWB-AIE-AHI" ("Tools for ABAP and HANA Integration")
1 ETP111 exit code : "8"
Details of the version:
Start Release: 731
Target Release: 740
OS Type: Windows NT X86_64
OS Version: 6.1
Database Type: hdb
Database Version: 1.00.70.00.386119
SUM Version: Patch 0 for SOFTWARE UPDATE MANAGER 1.0 SP10
As per the release note 1737650 - EHP7 for SAP ERP 6.0 SP Stacks - Release & Information Note, I have to follow the below note :
1981346 SAP HANA activation error during XPRA phase
But I am not pretty sure if I can ignore this and go ahead , and then do the actions as mentioned in the note, as the symptom says "The error message in the log file tells you that the MultipleFiles repository import failed.", which is not my case.
I have searched for SAP Notes with the below keywords but did not find any relevant , either there is a version mismatch or does not apply to the above error :
SNHI_DELIVERY_UNIT_IMPORT
SNHI_DELIVERY_UNIT_PROXY
Aggregated import of HANA Delivery Units failed
Errors occurred during post-handling "SNHI_DELIVERY_UNIT_IMPORT"
Please help me to resolve the issue.
Kind Regards,
AnujHi Anuj,
Can you check index server trace for more details into the error .
Based on the error message please check whether below SAP notes are valid
1996489 - Aggregated import of HANA Delivery Units failed with PackageStoreAccessor::createPackages
1996392 - Multiple delivery unit import fails with error code 301
Hope this helps.
Regards,
Deepak Kori -
ECC 6.0 EHP4 -- upg to EHP5 error in MAIN_NEWBAS/TABIM_UPG w/ dup key err
Experts,
We are on ECC6.0 EHP4. I'm using EHPI to go to EHP5. This is AIX/Oracle 11g.
I'm stuck on phase MAIN_NEWBAS/TABIM_UPG. This is the error in the TABIMUPG.ELG log file. See below.
I've tried re-running the phase a few times. It failes with below error or similar but table SOTR_TEXT also.
LIST OF ERRORS AND RETURN CODES *******
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
MAIN IMPORT ERRORS and RETURN CODE in SAPI-70201INSAPBSFND.RDM
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2EETW000 1 duplicate key error during insert into table SOTR_HEAD occured
2EETW000 sap_dext called with msgnr "16":
2EETW000 -
db call info -
2EETW000 function: db_setget
2EETW000 fcode: RT_GET (0)
2EETW000 tabname: SOTR_HEAD
2EETW000 len (char): 32
2EETW000 key: 801CC4EFFE841DDF809DBCE664D98822
2EETW000 ok fetches: 0
2EETW000 last entry:
2EETW000 retcode: 16
1 ETP111 exit code : "12"
I'm totally stuck. I tried reviewing these notes but no help:
Note 1341975 - Add. info. on upgrading to SAP ERP 6.0 including EHP5
ABAP
Note 819655 - Add. info.: Upgrade to SAP NW 2004s ABAP ORACLE
Any pointer much appreciated.
NICKCarsten,
Look at the /usr/sap/SID/instdir/EHPI/abap/log/SLOG702 for something like this:
WARNING: Background job RDDIMPDP could not be started or terminated abnormally.
Please check that the R/3 system is running.
Please check the system. Use transactions SM21, SM37, SM50.
WARNING: (This warning is harmless if no further warnings follow.)
If you see this a bunch of times, you will need to log in to the instance, go to SM61, make sure the background server for your instance is correct, and then also run the rddnewpp se38 report. That should resolve.
--NICK -
Error in pre processing phase MAIN_SHDIMP/SUBMOD_SH2_RUN/XPRAS_SHD_AIMMERGE
Hi Experts,
We faced below error in Pre processing phase of EHP6 Upgrade, MAIN_SHDIMP/SUBMOD_SH2_RUN/XPRAS_SHD_AIMMERGE.
Please anyone could suggest an alternative or workaround for this
Attached is screenshot of error. Below is information from the log
tail -20 XPRASSHD.ELG
3 ECD830 INCLUDE '"F_BUPR_BUR_CDF"' created
3 ECD830 INCLUDE '"F_BUPR_BUR_CDV"' created
3 ECD832 TCDRP: OBJ '"BUPR_BUR"' REPORT '"_BUPR_BUR_"' created
3 ECD834 TCDRS: REP '"_BUPR_BUR_"' TABN '"VBUT052"' created
3 ECD102 "R3TR" "CHDO" "BUPR_BUR" was imported
2EEPU133 Errors occurred during post-handling "AFTER_IMP_CHDO" for "CHDO" "L"
3 EPU135 "AFTER_IMP_CHDO" belongs to package "SZD"
2EEPU136 The errors affect the following components:
2EEPU137 "BC-SRV-ASF-CHD" ("Change Documents")
1 ETP111 exit code : "8"
>>> PLEASE READ THE REPORT DOCUMENTATION OF THE REPORTS MENTIONED ABOVE <<<
XPRAs are application reports that run at the end of an upgrade.
Most XPRA reports have a report documentation that explains what
the report does and how errors can be corrected.
Call transaction se38 in the SAP system, enter the report name,
select 'Documentation' and click the 'Display' button.
>>> The problematic XPRAs are mentioned in messages of type PU132 above <<<Hi Venkata
Could you check this SAP Note
1764234 - CD: Enhancements in generated function groups
Regards
Sriram -
ECC 6 SR3 upgrade I am getting following error at RSVBCHCK
2EETQ241 Errors found in logfiles - accumulated in file "PSVBCHCK.ELG"
1EETQ203 Upgrade phase "JOB_RSVBCHCK_D" aborted with errors
1 ETH010XRSVBCHCK: Check of open update requests
2EETG050 Update records still exist - Please process.
There is no SM13 nor SMQ1 entries in the system, also reorganiezed update records, also checked following.
SQL> select * from sapr3.VBERROR;
no rows selected
SQL> select * from SAPR3.VBERROR;
no rows selected
SQL> select * from SAPR3.VBMOD;
no rows selected
SQL> select * from SAPR3.VBHDR;
no rows selected
SQL>
Incase anyone had faced similar issues, and found a workarond please let me know
thanks.Hi Mathew,
Please check if your system has the ABAP program "RMCEXCHK" as per OSS Note no. 1083709.
Once you run this program, it exactly would let you know what are the areas which are causing the issues. Based on that you can empty out the LIS Set up tables.
Also, can you please check the update program for LIS has emptied out the entries in SMQ1.
Regards,
Anil -
Error in the PREP_GENCHECKS/NTACT_CHK phase
Hello,
I am getting an error in the PREP_GENCHECKS/NTACT_CHK phase during the "Checks" roadmap step in SAP Ehpi 700, while installing EHP4 for ERP 6.0.
This is the error it talks about:
ERROR> *** ERRORS during NAMETAB CHECK found ***
Analyze the logfile NTCHK.ELG to determine the nametab, that caused the error. Call transaction se11 for the corresponding DDIC object. Choose menu Utilities -> Runtime Object -> Check. If you repeat the phase and there is still an error, see also note Nr. 179334 for additional information.
This is what I found in NTCHK.ELG file:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
CHKANT and RETURN CODE in PN400701.EV2
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2EETP399XRead table "M_DEBI ": pgntab call: table not found.
2AETP399 Table "M_DEBI ": unknown error -9
2EETP399XRead table "M_ORDE ": pgntab call: table not found.
2AETP399 Table "M_ORDE ": unknown error -9
2EETP399XRead table "M_PRSM ": pgntab call: table not found.
2AETP399 Table "M_PRSM ": unknown error -9
2EETP399XRead table "M_ZCRD ": pgntab call: table not found.
2AETP399 Table "M_ZCRD ": unknown error -9
2EETP399XRead table "M_ZCST ": pgntab call: table not found.
2AETP399 Table "M_ZCST ": unknown error -9
2EETP399XRead table "M_ZESS ": pgntab call: table not found.
2AETP399 Table "M_ZESS ": unknown error -9
2EETP399XRead table "M_ZEST ": pgntab call: table not found.
2AETP399 Table "M_ZEST ": unknown error -9
2EETP399XRead table "M_ZINC ": pgntab call: table not found.
2AETP399 Table "M_ZINC ": unknown error -9
2EETP399XRead table "M_ZKTX ": pgntab call: table not found.
2AETP399 Table "M_ZKTX ": unknown error -9
2EETP399XRead table "M_ZMA1 ": pgntab call: table not found.
2AETP399 Table "M_ZMA1 ": unknown error -9
2EETP399XRead table "M_ZMAC ": pgntab call: table not found.
2AETP399 Table "M_ZMAC ": unknown error -9
2EETP399XRead table "M_ZMAI ": pgntab call: table not found.
2AETP399 Table "M_ZMAI ": unknown error -9
2EETP399XRead table "M_ZMAJ ": pgntab call: table not found.
2AETP399 Table "M_ZMAJ ": unknown error -9
2EETP399XRead table "M_ZMNH ": pgntab call: table not found.
2AETP399 Table "M_ZMNH ": unknown error -9
2EETP399XRead table "M_ZMNI ": pgntab call: table not found.
2AETP399 Table "M_ZMNI ": unknown error -9
2EETP399XRead table "M_ZPER ": pgntab call: table not found.
2AETP399 Table "M_ZPER ": unknown error -9
2EETP399XRead table "M_ZUOM ": pgntab call: table not found.
2AETP399 Table "M_ZUOM ": unknown error -9
1 ETP111 exit code : "12"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
CHKANT and RETURN CODE in PN410701.EV2
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code : "0"
As mentioned in SAP note 179334, when I tried to activate these table pools in the ABAP dictionary (SE11), it gave me an error "Maintain size category in SE13". After maintaining the size category and putting it in an SAP standard package, I tried to activate again in SE11. But now I am getting another error - "Table M_ZUOM: active nametab could not be read. Length of VARDATA field cannot be changed."
How do I activate these table pools and get on with the EHP4 installation?
I am on SAPKB70018, so I don't need to apply the note 695195.
Thanks,
AjayHi
> As mentioned in SAP note 179334, when I tried to activate these table pools in the ABAP dictionary (SE11), it gave me an error "Maintain size category in SE13". After maintaining the size category and putting it in an SAP standard package, I tried to activate again in SE11. But now I am getting another error - "Table M_ZUOM: active nametab could not be read. Length of VARDATA field cannot be changed."
>
> How do I activate these table pools and get on with the EHP4 installation?
As you are now getting error that length of VARDAT field cannot change. Then check on database level and if it does not contain any data then change field length manually as per in logs. Then try again
Thanks
Sunny
Maybe you are looking for
-
Error while creating Process flows in OWB 11gR2
Hi I have never faced this before and thats why it baffles me. I am trying to create a new process flow module which has already been configured to the OWF_LOCATION(Oracle workflow location). I get Java exception error window with long list of detail
-
Hi, Is it possible to localize OIM 9.1.0.2 version with language which doesnot comes OOTB? Is Localization like the Adapter Return message to be shown in the Administration Console is possible? Thanks in advance for the response.
-
New versions of ACS and ADE in the short term ??
Hello everyone, My company has several clients (publishers and libraries) that use the Adobe Content Server and Adobe Digital Editions. I would like to Know if Adobe will release new versions of these products in the short term. Our customers are ask
-
SOAP to EMAIL and sending the response to SOAP by integration process
Hi, I need to design a scenario from SOAP TO EMAIL and based on the status of the EMAIL being sent i need to send the response to SOAP using integration.If it is SUCCESSFUL message i need to send success and if the mail is not sent i need to send er
-
Deleting Address Book Notes with Automator
I imported all my contacts from Yahoo and now there's a bunch of jibberish under all my contacts notes...well most of them. Is there anything I can run from automator to delete all notes from all contacts? I don't need any notes. Thanks!