Error: END PHASE 002**************************
hi
i'm trying to maintain 2LIS_13_VDHDR .
i'm also trying to enhance 2 fields in to this extract structure.
i get error:: end phase 002*******************************.
error looks exactly the same with stars..
why did i get this error..
am i doing anything wrong??
can someone plz help...
Check This:
Re: End phase 002 *******************
End phase 002
assign points if it helps..
Similar Messages
-
RFPOSXEXTEND generation ends with Error: End Phase 002 Msg No. D0 322
Hi All
Offsetting Account Description in RFITEMGL (FBL3N).
To include GKONT_LTXT we appended and activated the RFPOS and RFPOSX structures and when generating RFPOSXEXTEND in SE38 I am getting following error message;
END PHASE 002***********************************************
Message No D0322
This message is some thing new to me. Also the Offset Account Name field does'nt figure out in Change layout for FBL3N Report. I am sure the above error is stopping me. I could understand that to display the values in the chage layout we need to append the structures and to populate the same, in the report we need to copy the function module in T.Code BERE and assign it in BF34.
Please do provide your valuable inputs on how to resolve the above error message.
Thanks in Advance
Regards
KIMHi Renan Correa
Thanks for the prompt reply.
Table: T012S is updated from T. Code: O7R3.
We have appended the Structures RFPOS & RFPOSX but still RFPOSXEXT is not getting populated with the appended fields.
We also tried regenerating RFPOSXEXTEND but failing with the End Phase 002 message.
As per your instructions below
(Regarding the error message D0322 please check special fields definition table T021S and check if the fields are correctly defined. Review and check if the 'field names' and 'table name' are filled and input correctly in the table. MOST of the times it's the origin of this error);
I tried to update T021S but the field GKONT_LTXT is not available and following is error message....
Field name GKNOT_LTXT is not allowed
Message no. FICORE405.
I have even checked SAP Note: 676338 (got this # from your replies to one of the threads with FICORE405 message).
Waiting for your valuable inputs.
Regards
K I M. -
End phase 002 *******************
Hi,
I am getting again this error(End phase 002*******), when a field shifting from pool to selection criteria in LBWE , when using 2LIS_13_VDHDR dataSource.
First time i got the same error, when using 2LIS_13_VDKON DataSource then implemented Note 757923. successfully field was shifted from pool to selection criteria.
Note 623411 cannot be applied. so, further what is the sloution....
Pls help me....
Thanks a lot
Please suggest me for this time error...Hi...
try this
2LIS_13_VD0ITM
LBWE transaction
Addition of existing fields from communication structure (MCVBKD)
Activation problem. -
Error in phase import_proper with error reason TP_STEP_FAILURE
Hi, I need to install Enhancement Package 3 for ECC 6 and it show me the problem as below:
Anyone has an idea of it? Thanks
"Invalid operation CNV for GLSP (object type:SQLT)"
*********SLOG************
INFO: event SAP_IMPORT_START triggered successfully
START DD IMPORT EC6 H 20080623133109 EC6ADM nbg-ws-ecc6 20080623133109
STOP DD IMPORT EC6 H 20080623133109 EC6ADM nbg-ws-ecc6 20080623133109
START TBATG CONVERSION OF EC6 N 20080623133110 EC6ADM nbg-ws-ecc6 20080623133109
START tp_getprots EC6 N 20080623133110 EC6ADM nbg-ws-ecc6 20080623133109
ERROR ALL EC6 N 0008 20080623133111 EC6ADM nbg-ws-ecc6 20080623133109
STOP tp_getprots EC6 N 20080623133113 EC6ADM nbg-ws-ecc6 20080623133109
STOP TBATG CONVERSION OF EC6 N 20080623133113 EC6ADM nbg-ws-ecc6 20080623133109
ERROR: stopping on error 8 during TBATG CONVERSION OF DD-OBJECTS
STOP imp all EC6 0008 20080623133113 EC6ADM nbg-ws-ecc6 20080623133109
***************NLOG**************
1 ETP166 CONVERSION OF DD OBJECTS (TBATG)
1 ETP101 transport order : "ALL"
1 ETP102 system : "EC6"
1 ETP108 tp path : "tp"
1 ETP109 version and release : "372.04.10" "700"
1 ETP198
1 ED0317XProgram start============================================================
1 ED0314
1 ED0314 DD: Execution of Database Operations
1 ED0314
1 ED0302 =========================================================================
1 ED0327 Process..................: "nbg-ws-ecc6_13"
1 ED0303 User.....................: "DDIC"
1 ED0305 Date, time...............: "23.06.2008", "13:31:11"
1 ED0307 Platform.................: "CUSTOMER"-"EC6"("700")/"ADABASD/WindowsNT/nbg-ws-ecc6"
1 ED0311 Tool.....................: "BATCH"/"RADBAT01"
1 ED0315 Log......................: "F", "
nbg-ws-ecc6\sapmnt\trans\tmp\N080623.EC6"
1 ED0314
1 ED0316 Program parameters:
1 ED0314 Process cat..............: parallel
1 ED0302 =========================================================================
1 ED0320XStart phase "001" **********************************************************
1 ED0306 "Preprocessing of TBATG"
1 ED0301 *************************************************************************
1 ED0301X*************************************************************************
1 ED0306 "Preprocessing of TBATG"
1 ED0322 End phase "001" ***********************************************************
1 ED0320XStart phase "002" **********************************************************
1 ED0306 "Partitioning"
1 ED0301 *************************************************************************
1 EGT014XNumber of objects: "2", partition: "2"
1 ED0301X*************************************************************************
1 ED0306 "Partitioning"
1 ED0322 End phase "002" ***********************************************************
1 ED0327XProcess..................: "nbg-ws-ecc6_13"
2 EGT054XRequest: Convert "SQL table GLSP (DDIC/23.06.08/13:31)"
2EEGT131 Invalid operation "CNV" for "GLSP" (object type:"SQLT")
1 ED0327XProcess..................: "nbg-ws-ecc6_13"
2 EGT054XRequest: Convert "SQL table GLTP (DDIC/23.06.08/13:31)"
2EEGT131 Invalid operation "CNV" for "GLTP" (object type:"SQLT")
1 ED0302X=========================================================================
1 ED0314 DD: Execution of Database Operations
1 ED0302 =========================================================================
1 ED0327 Process..................: "nbg-ws-ecc6_13"
1 ED0319 Return code..............: "0"
1 ED0314 Phase 001................: < 1 sec. (Preprocessing of TBATG)
1 ED0314 Phase 002................: < 1 sec. (Partitioning)
1 ED0309 Program runtime..........: "< 1 sec."
1 ED0305 Date, time...............: "23.06.2008", "13:31:11"
1 ED0318 Program end==============================================================
1 ETP166 CONVERSION OF DD OBJECTS (TBATG)
1 ETP110 end date and time : "20080623133111"
1 ETP111 exit code : "8"
1 ETP199 ######################################Refer to note 686357 and repair the table pools like mentioned in the solution there.
According to the import log the system decided that theses pool tables
GLSP, GLTP had to be converted because it found a difference between the table definition being imported and that that existed in the system.
Because conversion of tablesu2019 pools is not possible in general, these 2 tables were marked with status error in the control table TBATG. Any subsequent restart of the import now fails because there are TBATG entries in status error.
So when GLTP and GLSP are consistent after running RATPONTC (DDIC, NAMETAB and DB level)you can remove the entries for GLTP and GLSP from table TBATG and the import should proceed now. -
ACTIVATION Error during phase MAIN_SHDRUN/ACT_UPG
Hello Experts,
I am facing an activation error during upgrade o ECC 6.0 EHP 6 in shadow instance.
ERROR: Detected the following errors:
# F:\SUM\abap\log\SAPA702EPU.UAS: 3 EDT012XActivate table "PTRV_UTIL_VPFPS_VPFPA_P" 3 EDT402 Append structure "PTRV_VPFPS_VPFPA_P_APPEND" appended to table "PTRV_UTIL_VPFPS_VPFPA_P" 1EEDT963 Field "TIME_DURATION" in table "PTRV_UTIL_VPFPS_VPFPA_P" is specified twice. Please check 2WEDT135 Flag: 'Incorrect enhancement category' could not be updated 3 EDT013 Table "PTRV_UTIL_VPFPS_VPFPA_P" was not activated 1EEDO519X"Table" "PTRV_UTIL_VPFPS_VPFPA_P" could not be activated 3 EMC738XActivate view "V_T706S_EHP" 1EEMC560 Field "T706S"-"D2100" does not exist 1EEMC560 Field "T706S"-"EXCHANGE_DATE" does not exist 1EEMC560 Field "T706S"-"TRIP_BREAK_CNTRY" does not exist 3 EMC742 View "V_T706S_EHP" was not activated 1EEDO519 "View" "V_T706S_EHP" could not be activated
...skipped 13 more lines. Please see ACTUPG.html for more information.
SAPup_troubleticket.log
This trouble ticket was created by SAPup on 20140801092425
SAPup broke during phase ACT_UPG in module MAIN_SHDRUN / Shadow System Operations: SPDD and Activation
Error Message: Detected 5 errors summarized in 'ACTUPG.ELG'
Calling 'F:\SUM\abap\exe/tp' failed with return code 8, check F:\SUM\abap\log\SAPup.ECO for details
tp used shadow connect
ACTUPG.ELG:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DDIC ACTIVATION ERRORS and RETURN CODE in F:\SUM\abap\log\SAPA-10202INPOASBC.UAS
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
<NO ERROR LINES FOUND, BUT HIGHEST EXIT CODE WAS: "8">
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DDIC ACTIVATION ERRORS and RETURN CODE in SAPA702EPU.UAS
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
3 EDT012XActivate table "PTRV_UTIL_VPFPS_VPFPA_P"
3 EDT402 Append structure "PTRV_VPFPS_VPFPA_P_APPEND" appended to table "PTRV_UTIL_VPFPS_VPFPA_P"
1EEDT963 Field "TIME_DURATION" in table "PTRV_UTIL_VPFPS_VPFPA_P" is specified twice. Please check
2WEDT135 Flag: 'Incorrect enhancement category' could not be updated
3 EDT013 Table "PTRV_UTIL_VPFPS_VPFPA_P" was not activated
1EEDO519X"Table" "PTRV_UTIL_VPFPS_VPFPA_P" could not be activated
3 EMC738XActivate view "V_T706S_EHP"
1EEMC560 Field "T706S"-"D2100" does not exist
1EEMC560 Field "T706S"-"EXCHANGE_DATE" does not exist
1EEMC560 Field "T706S"-"TRIP_BREAK_CNTRY" does not exist
3 EMC742 View "V_T706S_EHP" was not activated
1EEDO519 "View" "V_T706S_EHP" could not be activated
3 EDT014XActivate dependent table "/MRSS/T_CUP_OBJECT"
1EEDT242 Field "FIELD_DESCRIPTIONS": Component type or domain used not active or does not exist
2WEDT183 Field "INSTANCE"-"/MRSS/IF_CUP_OBJECTS": Reference type used is not active
1EEDT005 Nametab for table "/MRSS/T_CUP_OBJECT" cannot be generated
3 EDT015 Dependent table "/MRSS/T_CUP_OBJECT" was not activated
1EEDO519 "Table" "/MRSS/T_CUP_OBJECT" could not be activated
3 EDT014XActivate dependent table "T706S"
1EEDT963 Field "TRIP_BREAK" in table "T706S" is specified twice. Please check
3 EDT015 Dependent table "T706S" was not activated
1EEDO519 "Table" "T706S" could not be activated
1 ETP111 exit code : "8"
SAPA702EPU.SID
ent tables)
2WEDO549 "View" "V_TWGVALE" was activated (warning for the dependent tables)
2WEDO549 "View" "V_TWH01" was activated (warning for the dependent tables)
2WEDO549 "View" "V_TWICSCMF" was activated (warning for the dependent tables)
2WEDO549 "View" "V_TWICSCMF0100" was activated (warning for the dependent tables)
2WEDO549 "View" "V_TWICSCMF0200" was activated (warning for the dependent tables)
2WEDO549 "View" "V_TWICSCMF0250" was activated (warning for the dependent tables)
2WEDO549 "View" "V_TWICSCMF0260" was activated (warning for the dependent tables)
2WEDO549 "View" "V_TWICSCMF501" was activated (warning for the dependent tables)
2WEDO549 "View" "V_TWICSCMF600" was activated (warning for the dependent tables)
2WEDO549 "View" "V_TWICSCMF8003" was activated (warning for the dependent tables)
2WEDO549 "View" "V_TWLOF" was activated (warning for the dependent tables)
2WEDO549 "View" "V_TWMWQ" was activated (warning for the dependent tables)
2WEDO549 "View" "V_TWPC_COLHEAD" was activated (warning for the dependent tables)
2WEDO549 "View" "V_TWPC_COLHEAD_C" was activated (warning for the dependent tables)
2WEDO549 "View" "V_TWRF2" was activated (warning for the dependent tables)
2WEDO549 "View" "V_TWSD" was activated (warning for the dependent tables)
2WEDO549 "View" "V_TWTFMA" was activated (warning for the dependent tables)
2WEDO549 "View" "V_TWZLA" was activated (warning for the dependent tables)
2WEDO549 "View" "V_TXW_AD01D" was activated (warning for the dependent tables)
2WEDO549 "View" "V_TZB0W" was activated (warning for the dependent tables)
2WEDO549 "View" "V_TZB6D" was activated (warning for the dependent tables)
2WEDO549 "View" "V_TZBABG" was activated (warning for the dependent tables)
2WEDO549 "View" "V_TZBABGZB" was activated (warning for the dependent tables)
2WEDO549 "View" "V_TZD0B" was activated (warning for the dependent tables)
2WEDO549 "View" "V_TZD0BI" was activated (warning for the dependent tables)
2WEDO549 "View" "V_TZD0BW" was activated (warning for the dependent tables)
2WEDO549 "View" "V_TZE02" was activated (warning for the dependent tables)
2WEDO549 "View" "V_TZE03D" was activated (warning for the dependent tables)
2WEDO549 "View" "V_TZONE_M" was activated (warning for the dependent tables)
2WEDO549 "View" "V_TZPAB3" was activated (warning for the dependent tables)
2WEDO549 "View" "V_TZT01" was activated (warning for the dependent tables)
2WEDO549 "View" "V_TZT01D" was activated (warning for the dependent tables)
2WEDO549 "View" "V_TZV04" was activated (warning for the dependent tables)
2WEDO549 "View" "V_UEBER" was activated (warning for the dependent tables)
2WEDO549 "View" "V_USCOMP" was activated (warning for the dependent tables)
2WEDO549 "View" "V_USCOMPA" was activated (warning for the dependent tables)
2WEDO549 "View" "V_USR_NAME" was activated (warning for the dependent tables)
2WEDO549 "View" "V_VGNVA" was activated (warning for the dependent tables)
2WEDO549 "View" "V_VGNWA" was activated (warning for the dependent tables)
2WEDO549 "View" "V_VIGWVOBW" was activated (warning for the dependent tables)
2WEDO549 "View" "V_VIGWVOBW_BUK" was activated (warning for the dependent tables)
2WEDO549 "View" "V_VIGWVOBW_GE" was activated (warning for the dependent tables)
2WEDO549 "View" "V_VIGWVOBW_GFL" was activated (warning for the dependent tables)
2WEDO549 "View" "V_VIGWVOBW_GR" was activated (warning for the dependent tables)
2WEDO549 "View" "V_VIGWVOBW_GRA" was activated (warning for the dependent tables)
2WEDO549 "View" "V_VIGWVOBW_WE" was activated (warning for the dependent tables)
2WEDO549 "View" "V_VIOB01" was activated (warning for the dependent tables)
2WEDO549 "View" "V_VIOB02" was activated (warning for the dependent tables)
2WEDO549 "View" "V_VIOB03" was activated (warning for the dependent tables)
2WEDO549 "View" "V_VITXT" was activated (warning for the dependent tables)
2WEDO549 "View" "V_VLBLTD" was activated (warning for the dependent tables)
2WEDO549 "View" "V_VLTD" was activated (warning for the dependent tables)
2WEDO549 "View" "V_VTDST" was activated (warning for the dependent tables)
2WEDO549 "View" "V_VTSPLS" was activated (warning for the dependent tables)
2WEDO549 "View" "V_WBEW" was activated (warning for the dependent tables)
2WEDO549 "View" "V_WCUSDOC_RELA" was activated (warning for the dependent tables)
2WEDO549 "View" "V_WITH_CTNCOT005" was activated (warning for the dependent tables)
2WEDO549 "View" "V_WLFBA" was activated (warning for the dependent tables)
2WEDO549 "View" "V_WLFBB" was activated (warning for the dependent tables)
2WEDO549 "View" "V_WLFKC" was activated (warning for the dependent tables)
2WEDO549 "View" "V_WLFRA" was activated (warning for the dependent tables)
2WEDO549 "View" "V_WLFRB" was activated (warning for the dependent tables)
2WEDO549 "View" "V_WLFZA" was activated (warning for the dependent tables)
2WEDO549 "View" "V_WLFZB" was activated (warning for the dependent tables)
2WEDO549 "View" "V_WLFZUC10" was activated (warning for the dependent tables)
2WEDO549 "View" "V_WRBLA" was activated (warning for the dependent tables)
2WEDO549 "View" "V_WRGLA" was activated (warning for the dependent tables)
2WEDO549 "View" "V_WRGLB" was activated (warning for the dependent tables)
2WEDO549 "View" "V_WRLBA" was activated (warning for the dependent tables)
2WEDO549 "View" "V_WRSZ" was activated (warning for the dependent tables)
2WEDO549 "View" "WB2_V_VBRK_WBGT" was activated (warning for the dependent tables)
2WEDO549 "View" "WB2_V_WBRK_WBRP" was activated (warning for the dependent tables)
2WEDO549 "View" "WB2_V_WBRK_WBRP2" was activated (warning for the dependent tables)
2WEDO549 "View" "WCVAP" was activated (warning for the dependent tables)
2WEDO549 "View" "WCVHE" was activated (warning for the dependent tables)
2WEDO549 "View" "WCVITX" was activated (warning for the dependent tables)
2WEDO549 "View" "WCVJ" was activated (warning for the dependent tables)
2WEDO549 "View" "WCVM1" was activated (warning for the dependent tables)
2WEDO549 "View" "WCVN1" was activated (warning for the dependent tables)
2WEDO549 "View" "WCVO1" was activated (warning for the dependent tables)
2WEDO549 "View" "WCVO2" was activated (warning for the dependent tables)
2WEDO549 "View" "WCVO3" was activated (warning for the dependent tables)
2WEDO549 "View" "WCVO4" was activated (warning for the dependent tables)
2WEDO549 "View" "WCVO5" was activated (warning for the dependent tables)
2WEDO549 "View" "WCVO6" was activated (warning for the dependent tables)
2WEDO549 "View" "WCVO7" was activated (warning for the dependent tables)
2WEDO549 "View" "WCVO8" was activated (warning for the dependent tables)
2WEDO549 "View" "WCVO9" was activated (warning for the dependent tables)
2WEDO549 "View" "WCVOA" was activated (warning for the dependent tables)
2WEDO549 "View" "WCVOC" was activated (warning for the dependent tables)
2WEDO549 "View" "WCVOD" was activated (warning for the dependent tables)
2WEDO549 "View" "WCVODX" was activated (warning for the dependent tables)
2WEDO549 "View" "WCVOE" was activated (warning for the dependent tables)
2WEDO549 "View" "WCVOF" was activated (warning for the dependent tables)
2WEDO549 "View" "WCVOI" was activated (warning for the dependent tables)
2WEDO549 "View" "WCVP0" was activated (warning for the dependent tables)
2WEDO549 "View" "WCVP1" was activated (warning for the dependent tables)
2WEDO549 "View" "WCVP2" was activated (warning for the dependent tables)
2WEDO549 "View" "WCVP3" was activated (warning for the dependent tables)
2WEDO549 "View" "WCVP4" was activated (warning for the dependent tables)
2WEDO549 "View" "WCVP5" was activated (warning for the dependent tables)
2WEDO549 "View" "WCVP6" was activated (warning for the dependent tables)
2WEDO549 "View" "WCVP7" was activated (warning for the dependent tables)
2WEDO549 "View" "WCVP8" was activated (warning for the dependent tables)
2WEDO549 "View" "WCVPN1" was activated (warning for the dependent tables)
2WEDO549 "View" "WCVPU1" was activated (warning for the dependent tables)
2WEDO549 "View" "WCVW" was activated (warning for the dependent tables)
2WEDO549 "View" "WCVWA1" was activated (warning for the dependent tables)
2WEDO549 "View" "WCVWA2" was activated (warning for the dependent tables)
2WEDO549 "View" "WCVZ1" was activated (warning for the dependent tables)
2WEDO549 "View" "YWM_VSNACH_LIKP" was activated (warning for the dependent tables)
2WEDO549 "View" "YWTY_V_DLR_BR" was activated (warning for the dependent tables)
2WEDO549 "View" "YWTY_V_DLR_PROOR" was activated (warning for the dependent tables)
2WEDO549 "View" "YWTY_V_EMGAR_DC" was activated (warning for the dependent tables)
2WEDO549 "View" "YWTY_V_USR_DISTR" was activated (warning for the dependent tables)
2WEDO549 "View" "YWTY_V_WORKBY" was activated (warning for the dependent tables)
2WEDO549 "View" "ZZLIB_V_HKTK" was activated (warning for the dependent tables)
2WEDO549 "View" "ZZLIB_V_LIFNR_C" was activated (warning for the dependent tables)
1 ED0301X*************************************************************************
1 ED0306 "Final log"
1 ED0322 End phase "006" ***********************************************************
1 ED0320XStart phase "007" **********************************************************
1 ED0306 "Statistics on Activated and Deleted Objects"
1 ED0301 *************************************************************************
1 EDO601XNumber of objects to be activated............: "35325"
1 EDO605 Objects not activated........................: "4"
1 EDO606 Activated objects with errors in dependencies: "4"
1 EDO604 Objects activated with warning...............: "5531"
1 EDO603 Successfully activated objects...............: "29786"
1 EDO602 Number of objects to be deleted..............: "128"
1 EDO608 Objects not successfully deleted.............: "0"
1 EDO607 Successfully deleted objects.................: "128"
1 EDO609 Tables/views with DROP/CREATE................: "0"
1 EDO610 No. of them marked for DROP/CREATE: "0"
1 EDO611 Not marked for DROP/CREATE: "0"
1 EDO620 Number of nametabs to be deleted.............: "0"
1 EDO622 Successfully deleted nametabs................: "0"
1 EDO621 Nametabs that were not successfully deleted..: "0"
1 ED0301X*************************************************************************
1 ED0306 "Statistics on Activated and Deleted Objects"
1 ED0322 End phase "007" ***********************************************************
1 ED0302X=========================================================================
1 ED0314 Mass Activation
1 ED0302 =========================================================================
1 ED0327 Process..................: "defnsv1466_14_59636"
1 ED0319 Return code..............: "8"
1 ED0313 Phase 001..................: 00:00:13 (Take Over Switch-Dependent Objects)
1 ED0314 Phase 002..................: < 1 sec. (Deletion of objects: 1th call)
1 ED0314 Phase 003..................: 00:00:47 (Berechnung der Abhängigen:)
1 ED0313 Phase 004..................: 00:15:00 (Object Activation)
1 ED0314 Phase 005..................: < 1 sec. (Puffer Sync für Abhängige refTo ...)
1 ED0314 Phase 006..................: < 1 sec. (Final log)
1 ED0314 Phase 007..................: < 1 sec. (Statistics on Activated and ...)
1 ED0309 Program runtime..........: "00:16:01"
1 ED0305 Date, time...............: "01.08.2014", "09:23:55"
1 ED0318 Program end==============================================================
1 ETP155 ACTIVATION OF DD-OBJECTS
1 ETP110 end date and time : "20140801092355"
1 ETP111 exit code : "8"
1 ETP199 ######################################
4 EPU202XEND OF SECTION BEING ANALYZED END OF ACT_UPG =====================================================
Please suggest.
Regards,
AlokHi Divyanshu,
thanks for your prompt reply,
As per the error occurred, PTRV_UTIL_VPFPS_VPFPA_P is the table but when I check in SE16 its saying PTRV_UTIL_VPFPS_VPFPA_P not a table its a STRUCTURE
In SE11 its saying "PTRV_UTIL_VPFPS_VPFPA_ "does not exist.Check name.
Here it is not taking full name of table "PTRV_UTIL_VPFPS_VPFPA_P".
Pl suggest.
BR,
Alok -
Error in phase XPRA_EXECUTION while updating the SAP_BASIS patch !4
Hi ,
I am trying to update the sap_basis patch from level 13 to 14 . While updating I am getting
Error in phase: XPRA_EXECUTION
Reason for error: TP_STEP_FAILURE
Return code: 0012
Error message: OCS Package SAPKB70014, tp step R, return code
0012
In ST22 It says Syntax error in program "CL_CLS_ATTR_VALUE_ASSIGNMENT==CP
any help would be appreciated..
Regards,
PradeepThis is what I get in the import log
The Syntax Error is given below
Execution of programs after import (XPRA)
Transport request : SAPKB70014
System : DEV
tp path : tp
Version and release: 372.04.59 700
Program terminated (job: RDDEXECL, no.: 17163300)
See job log
Execution of programs after import (XPRA)
End date and time : 20090518171648
Ended with return code: ===> 12 <===
untime Errors SYNTAX_ERROR
Date and Time 18.05.2009 17:16:34
Short text
Syntax error in program "CL_CLS_ATTR_VALUE_ASSIGNMENT==CP ".
What happened?
Error in the ABAP Application Program
The current ABAP program "SAPLCLS_AFTER_IMPORT" had to be terminated because it
has
come across a statement that unfortunately cannot be executed.
The following syntax error occurred in program
"CL_CLS_ATTR_VALUE_ASSIGNMENT==CP " in include
"CL_CLS_ATTR_VALUE_ASSIGNMENT==CM00D " in
line 1:
"Method "GET_DETAILS_OF_ASSIGNMENT" does not exist. The following simil"
"arly-named methods do exist: "GET_DESCRIPTION_OF_ASSIGNMENT", "GET_PAC"
"KAGES_OF_ASSIGNMENTS" and "GET_CLIENT_ASSIGNMENTS"."
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 "SAPLCLS_AFTER_IMPORT" 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 "CL_CLS_ATTR_VALUE_ASSIGNMENT==CP
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
CL_CLS_ATTR_VALUE_ASSIGNMENT==CP :
"Method "GET_DETAILS_OF_ASSIGNMENT" does not exist. The following simil"
"arly-named methods do exist: "GET_DESCRIPTION_OF_ASSIGNMENT", "GET_PAC"
"KAGES_OF_ASSIGNMENTS" and "GET_CLIENT_ASSIGNMENTS"."
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. -
EHP4 upgrade: Error in Phase ACT_UPG
Hi All,
While upgrading to EHP4 on ECC 6 system, we got error in phase MAIN_SHDRUN/ACT_UPG
Checks after phase MAIN_SHDRUN/ACT_UPG were negative!
Last error code set: Unresolved requests in buffer RH4 Check logfiles 'ACTUPG.ELG' and '/sapdump/SAPehpi/EHPI/abap/log/SAPehpi.ECO'
ACT_UPG log:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DDIC ACTIVATION ERRORS and RETURN CODE in SAPA-604DMINISPSCA.RH4
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code : "12"
Log of SAPA-604DMINISPSCA.RH4
1 ETP155 ACTIVATION OF DD-OBJECTS
1 ETP101 transport order : "SAPK-604DMINISPSCA"
1 ETP102 system : "RH4"
1 ETP108 tp path : "/sapdump/SAPehpi/EHPI/abap/exe/tp"
1 ETP109 version and release : "372.04.70" "700"
1 ETP198
3 EPU324 See log for request "/sapdump/SAPehpi/EHPI/abap/tmp/SAPAB70015.RH4" (timestamp "01:26:08", system "RH4")
1AETR012XProgram terminated (job: "RDDMASGL", no.: "01260600")
1AEPU320 See job log"RDDMASGL""01260600""RH4"
1 ETP155 ACTIVATION OF DD-OBJECTS
1 ETP110 end date and time : "20091012033215"
1 ETP111 exit code : "12"
1 ETP111 exit code : "12"
Job RDDMASG log :
Job cancelled with following log
2.10.2009 01:26:07 Job started 00 516 S
2.10.2009 01:26:07 Step 001 started (program RDDMASGL, variant IMPACTMRG, user ID DDIC) 00 550 S
2.10.2009 01:26:08 Start of mass activation 01:26:08 AD 010 S
when tried to log into shadow instance after getting error, it is giving error
RH4: system message
work process restarted; session terminated;
we restarted shadow system. There is no dumps in the shadow system.
Work process getting killed after 7800s
checked in work directory of Shadow system: devdisp log :_*
Mon Oct 12 04:49:46 2009
rdisp/http_min_wait_dia_wp : 1 -> 1
***LOG CPS=> DpLoopInit, ICU ( 3.0 3.0 4.0.1) [dpxxdisp.c 1694]
***LOG Q0K=> DpMsAttach, mscon ( HW136799) [dpxxdisp.c 12639]
DpStartStopMsg: send start message (myname is >HW136799_RH4_22 <)
DpStartStopMsg: start msg sent
Warning: Swap space is configured quite small with 20477 MB.
It should be configured with at least 20 GB on 64 bit systems.
See note 153641 for more information.
Warning: tmpfs at /dev/shm is configured quite small with 1972 MB!
Minimum value is 8192 MB.
Recommended size is 75 % of RAM + swap.
CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.
Mon Oct 12 04:49:47 2009
DpMsgAdmin: Set release to 7000, patchlevel 0
MBUF state PREPARED
MBUF component UP
DpMBufHwIdSet: set Hardware-ID
***LOG Q1C=> DpMBufHwIdSet [dpxxmbuf.c 1050]
DpMsgAdmin: Set patchno for this platform to 221
Release check o.K.
MBUF state ACTIVE
DpModState: change server state from STARTING to ACTIVE
Mon Oct 12 06:57:01 2009
ERROR => DpWPCheck: W8 (pid 9769) died (severity=0, status=7) [dpxxdisp.c 15776]
child (pid=9769) killed with signal 7
Mon Oct 12 06:57:43 2009
ERROR => DpWPCheck: W7 (pid 9768) died (severity=0, status=7) [dpxxdisp.c 15776]
child (pid=9768) killed with signal 7
Please let us know what needs to be cheked for the problem
Thanks,
Ramesh RamagowniHi Markas and All,
Thanks for the information. /dev/shm was 100% full. now, the issue is solved after deleting its contents. and we have finished with EHP4 upgrade.
After upgrade, SAP_AP component still showing as 700
SAP_AP - 700 - 0015 - SAPKNA7015 -SAP Application Platform
Can we delete old tablespace PSAPSR3700, it is showing as 0% used in brspace at present.
Also while trying to move some datafiles using brtools after upgrade we are getting following error,
BR0280I BRTOOLS time stamp: 2009-10-20 01.45.52
BR0670I Enter 'c[ont]' to continue, 'b[ack]' to go back, 's[top]' to abort:
c
BR0280I BRTOOLS time stamp: 2009-10-20 01.45.54
BR0257I Your reply: 'c'
BR0259I Program execution will be continued...
BR0252E Function fopen() failed for '/oracle/RH4/sapbackup/.user.pas' at location BrToolCall-2
BR0253E errno 13: Permission denied
BR0669I Cannot continue due to previous warnings or errors - you can go back to repeat the last action
BR0280I BRTOOLS time stamp: 2009-10-20 01.45.54
BR0671I Enter 'b[ack]' to go back, 's[top]' to abort:
There is no file in the directory '/oracle/RH4/sapbackup/.user.pas'
Please suggest what needs to be for this issue..Do we need to upgrade BRTOOLS..
Thanks,
Ramesh R -
Error in phase: XPRA_EXECUTION
I am in the process of applying the latest HR support packages
and have an error in error in SAPKE60438.
error log**************************************************************************************
The following details help you to analyze the problem:
- Error in phase: XPRA_EXECUTION
- Reason for error: TP_STEP_FAILURE
- Return code: 0008
- Error message: OCS Package SAPKE60438, tp step "R", return code 0008
detailed log*********************************************************************************
BC Set HRLOCUN_T512T_S: The BC Set is not assigned to a switch
BC Set HRLOCUN_T512T_S: Procedure ended with errors
Does anyone have any suggestions of what to try next? Your input would be appreciated.
Thanks,
Inho.
Edited by: In-Ho Jun on Dec 11, 2011 12:10 PMHi All,
I understand that the solution is already described above, but just for the information
purpose ,
This is a known issue and the Note 1667851 is already released for this issue.
1667851 - XPRA_EXECUTION error with SAPKE60438 support package
I hope this information helps to all who visit the thread.
Regards,
Gaurav -
Phaer 8850 error code 36,002.46:119281
Hi there, Came in this morning sent a two page document to my Phaser 8860, one page printed out with two blanks that appeared to have fuser oil on them and there was a message with this error code 36,002.46:119281. I did what every good techie does - reboot! Alas, no such luck. Google was no help with this particular error code either. What does this code mean? Thanks! Amy
Drum Maintenance Kit faultIt's the unit in the little door on the right side. Possibly needs to be replaced, possibly just dirty, try wiping the plastic blade with a soft, no lint, cloth and put it back in. I couldn't find the code anywhere either, even internally, but a co-worker did.
-
Error in phase XPRAS_AIMMRG for Upgrade from 4.7 to ERP6 ehp5 sps5
Hi All,
We are in process in upgrading our sandbox system from 4.7 to ERP6.0
EHP5 SPS5.
During the downtime step we are facing an error in phase XPRAS_AIMMRG
Upon investigation we found that there are short dumps in the system
due to this error.
Below is the extract of the short dumps generated by the job RDDEXECL
Category Internal Kernel Error
Runtime Errors DDIC_TYPE_INCONSISTENCY
Application Component BC-ABA-LA
Date and Time 05.12.2011 08:58:48
Short text
Inconsistency in the dictionary for the structure "KOMG".
What happened?
Error in the SAP kernel.
The current ABAP "SAPLF82V" program had to be terminated because
the
ABAP processor detected an internal system error.
Also, We I try to check the Table KOMG in SE11 is get the below messages.
Check table KOMG (DDIC/05.12.11/10:00)
Append structure OILKOMG appended to table KOMG
Append structure OIUKOMG appended to table KOMG
No customer or SAP include SI_KOMK_CM exists
No customer or SAP include SI_KOMP_CM exists
No customer or SAP include CI_PRS_CPILS_2 exists
Enhancement category 3 possible, but include or subty. not
yet classified
Field LGORT in table KOMG is specified twice. Please check
KOMG-ZZMVGR4: Table TVM1T in search help attachment differs
from table of search field
Check on table KOMG resulted in errors
Has anyone received the below message in XPRAS phase during the upggrade.
Any suggestion would be most welcome.
Regards,
Nilesh JagtapDear Nilesh,
The reason for this issue is that the component 'LGORT' is indeed specified twice in structure KOMG on your system.
It might be definied in the standard include as well as in your customer include.
Please bear in mind, that if you append customer own structures to SAP standad structures, that the component names should start with 'Z' or even better 'ZZ'.
That prevents the case which might have happened here, that the field you have added on customer side has also been delivered as part of an SAP standard include.
So you should change your structure accordingly.
Note 531835 describes how to add an own field to such structures. It might also be helpful for you.
After you have repaired your structure you can activate the structure KOMG and the issue should be solved.
Best Regards,
Abhishek -
Error in phase: ADD_TO_BUFFER in SPAM during import of SAPKB70017 and 18
Hello
What is problem in this case? During import of SAPKB70017 and SAPKB70018 I get following error(there is no SLOG file in /usr/sap/trans/log):
The import was stopped, since an error occurred during the phase
ADD_TO_BUFFER, which the Support Package Manager is unable to resolve
without your input.
After you have corrected the cause of the error, continue with the
import by choosing Support Package -> Import queue from the initial
screen of the Support Package Manager.
The following details help you to analyze the problem:
- Error in phase: ADD_TO_BUFFER
- Reason for error:
- Return code: 0211
- Error message:
Notes on phase ADD_TO_BUFFER
In this phase the queue is placed in the transport buffer of your
system. This phases can terminate due to the following reasons:
o TP_INTERFACE_FAILURE: The tp interface could not be called. There is
an RFC error.
o CANNOT_ADD_PATCH_TO_BUFFER: A Support Package could not be included
in the transport buffer. The program tp is trying to open a file in
the file system. For more information, refer to the SLOG log file in
the directory /usr/sap/trans/log.
A prerequisite of the Support Package Manager is that the Change and
Transport System (CTS) is configured correctly. For more detailed
information, read the online documentation available from Help -> SAP
Library -> mySAP Technology Components -> SAP Web Application Server ->
Change and Transport System .
A list of the most important SAP Notes for Online Correction Support
(OCS) is available in SAP Note 97620, which is updated regularly.Hi Jan,
First, check whether your STMS is configured properly. Next check the transport directory and the transport tool from within STMS (system -> check in menu options).
If these 2 are ok, then you might check from within the OS layer by manually adding to buffer (tp add to buffer <Request No> <SID>).
Also, I am assuming you are doing this from client 000 with a non-standard user having proper authorizations.
I believe this to be an issue of permissions at the OS layer.
Regards
Siva -
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, -
SAINT Error in Phase CHECK_REQUIREMENTS
Hi.Experts,
In a new SAP component installation with "t-cd:SAINT", an error occurred.
ERROR MESSAGE
=============================================
Phase CHECK_REQUIREMENTS: Explanation of Errors
Open conversion requests still exist in the ABAP Dictionary for the
following ABAP Dictionary objects. To avoid inconsistencies and loss of
data, you must process these conversions first.
Proceed as follows:
- Open a new session.
- Start the Database Utility (transaction SE14).
- Correct the inconsistencies for the specified objects.
- Repeat the import phase. If no more inconsistencies are found, the
import continues.
=============================================
I have already checked 4 things of below
1.SE14－－＞BSEG
I can see the message below on the screen.
Request:"Adjust" Error in step2 -see object log and analysis
2.SPAU
The contents related to BSEG are already modified (Green)
3.SPDD
The contents related to BSEG are already modified (Green)
4.SE10
There is no modifiable request related BSEG.
Could someone tell me about how to deal this error?
Best Regards,
NaomiHi Naomi
Could you check this SAP Note about your issue
1839881 - SPAM/SAINT error during CHECK_REQUIREMENTS regarding open conversion request still existing
BR
SS -
MAXDB backup failed with error: end of file reached -917
Hi I am performing a complete data backup for a database which is about 230 GB.
Previously it had run successfully for many days, but since yesterday, I began to receive such error:
Error: end of file reached(-917)
The backup stopped itself after running for 1 hour, and from backup history I just saw above error message.
I also had a look at the logs, and found below, could someone help me look into this issue?
Appreciate your kind help in advance!
2008-11-25 22:08:09 0xBE4 ERR 52012 SAVE error occured, basis_err 5750
2008-11-25 22:08:09 0xBE4 ERR 3 Backup Data backup failed
2008-11-25 22:08:09 0xBE4 ERR 1 Backup + Backupmedium #1 (F:\Dbbackup\QAS_data_01) end of file reached
2008-11-25 22:08:09 0xBE4 ERR 6 KernelCo + Backup error occured, Error code 5750 "write_task_crash"
2008-11-25 04:00:27 0x16A0 52024 SAVE 30462712 pages -> "F:\DBbackup\QAS_DATA"
2008-11-25 04:00:28 0x1BE4 19626 IO Async I/O thread stopped, 'F:\DBbackup\QAS_DATA'
2008-11-25 04:00:28 0x1FC4 19626 IO Async I/O thread stopped, 'E:\sapdb\QAS\DAT_0001'
2008-11-25 04:00:28 0x1688 19626 IO Async I/O thread stopped, 'E:\sapdb\QAS\DAT_0002'
2008-11-25 04:00:28 0x15D4 19626 IO Async I/O thread stopped, 'E:\sapdb\QAS\DAT_0003'
2008-11-25 04:00:28 0xAEC 19626 IO Async I/O thread stopped, 'E:\sapdb\QAS\DAT_0004'
2008-11-25 04:00:28 0x179C 19626 IO Async I/O thread stopped, 'E:\sapdb\QAS\DAT_0005'
2008-11-25 04:00:28 0xDD4 19626 IO Async I/O thread stopped, 'E:\sapdb\QAS\DAT_0006'
2008-11-25 04:00:28 0x1AE8 19626 IO Async I/O thread stopped, 'E:\sapdb\QAS\DAT_0007'
2008-11-25 04:00:28 0x176C 19626 IO Async I/O thread stopped, 'E:\sapdb\QAS\DAT_0008'
2008-11-25 04:00:28 0x11B8 19626 IO Async I/O thread stopped, 'G:\sapdb\QAS\DAT_0009'
2008-11-25 04:00:28 0x1B4C 19626 IO Async I/O thread stopped, 'G:\sapdb\QAS\DAT_0010'
2008-11-25 04:00:28 0x1F60 19626 IO Async I/O thread stopped, 'G:\sapdb\QAS\DAT_0011'
2008-11-25 04:00:35 0xB8C 52012 SAVE ready
2008-11-25 04:00:35 0xB8C 19651 CONNECT Connection released, T113
Thanks,
vivianHello Shaun,
Thank you so much for your reply. But I've checked that my F drive still have more than 480GB free space, so the space should not be the problem.
And I've just run the backup once again, this time it keeps running for 2 hours, and then failed again with the same error.
Is there other possible reasons of this error?
Thanks a lot,
Vivian
Maybe you are looking for
-
Lock screen no longer works on iOS 8.0.2
Updated to iOS 8.0.2 Now my ipad2 never goes to lock screen after 2 mins, or when I close the cover. "Genius bar tech" seems to think that the functionality has been removed. So when you close the cover tye screen stays on what ever app you were usin
-
Mac mini mid 2011 boot stops at gray screen
I have a mid 2011 mini running 10.9.5 that's stopping at a gray screen. Waiting for it hasn't worked yet On start up I get the apple logo, the wriggling worm and after a bit the screen goes black for a few seconds then comes up gray and is completely
-
Function to get the interest rate
hi; iam trying to develop a function to return te rate of a loan knowing the original ammount, monthly payment, term. basically what i need is the same as rate function in excel but i cant find the matematical function to calculate the rate thanks or
-
I have a PBG4 12". I use a Samsung ML-1740. The printer is connected to my AEBS, I have been able to use it finesince I got this printer a year ago. However, since a couple weeks ago, the printer was not responding. >When I go to Network Diagnnostics
-
Hello, I'm trying to bind my menu bar (af:menubar) to a menu model. I created the menu model from my main unbounded task flow (adfc-config.xml) : right click -> "Create ADF Menu Model..." giving me root_menu.xml. My menu bar is currently defined in a