- SAP Community
- Products and Technology
- Technology
- Technology Q&A
- Solution Manager Upgrade to Enp1 through saint get...
- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
Solution Manager Upgrade to Enp1 through saint get syntax erros
- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
on 07-31-2009 8:37 AM
Dear all,
during upgrade through transaction saint of solution manager system we got syntax errors.
Restart of transaction saint is not possible - it gives short dump
Log on to system get short dump, but it is possible.
Please assist as I cannot restart saint and procceed with the import.
Short dump when trying to start transaction saint is the following:
Runtime Errors SYNTAX_ERROR
Date and Time 31.07.2009 10:38:36
-
-
Short text |
Syntax error in program "SAPLSUNI ". |
-
-
What happened? |
Error in the ABAP Application Program |
The current ABAP program "SAPLSAINT_UI" had to be terminated because it has |
come across a statement that unfortunately cannot be executed. |
The following syntax error occurred in program "SAPLSUNI " in include |
"CL_WB_SOURCE==================CU " in |
line 258: |
"Type "SEDI_SUB_CONT_TAB" is unknown" |
" " |
" " |
" " |
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 "SAPLSAINT_UI" had to be terminated because it has |
come across a statement that unfortunately cannot be executed. |
-
-
Error analysis |
The following syntax error was found in the program SAPLSUNI : |
"Type "SEDI_SUB_CONT_TAB" is unknown" |
" " |
" " |
" " |
-
-
Trigger Location of Runtime Error |
Program SAPLSAINT_UI |
Include LSAINT_UIO01 |
Row 2.966 |
Module type (MODULE PBO) |
Module Name CHECK_MT_MODE |
-
-
Source Code Extract |
-
Line | SourceCde |
-
2936 | |
2937 | PERFORM read_n_check_ocs_semaphore. |
2938 | |
2939 | ENDMODULE. " read_ocs_semaphore OUTPUT |
2940 | &---- |
2941 | *& Module read_batch_jobs OUTPUT |
2942 | &---- |
2943 |
|
2944 | ---- |
2945 | MODULE read_batch_jobs OUTPUT. |
2946 | |
2947 | IF gv_tenant_mode <> on. |
2948 | PERFORM read_n_check_batch_jobs. |
2949 | ELSE. |
2950 |
|
2951 | REFRESH: gt_batch_sema, |
2952 | gt_active_jobs. |
2953 | gv_job_scheduled = off. |
2954 | ENDIF. |
2955 | |
2956 | ENDMODULE. " read_batch_jobs OUTPUT |
2957 | &---- |
2958 | *& Module check_mt_mode OUTPUT |
2959 | &---- |
2960 |
|
2961 | ---- |
2962 | MODULE check_mt_mode OUTPUT. |
2963 | |
2964 |
|
2965 | SET EXTENDED CHECK OFF. |
>>>>> | CALL FUNCTION 'FUNCTION_EXISTS' |
2967 | EXPORTING |
2968 | funcname = 'TR_CHECK_FOR_MT_SYS' |
2969 | EXCEPTIONS |
2970 | function_not_exist = 1. |
2971 | IF sy-subrc = 0. |
2972 | CALL FUNCTION 'TR_CHECK_FOR_MT_SYS' "#EC EXISTS |
2973 | IMPORTING "#EC EXISTS |
2974 | tenancy = gv_tenant_mode "#EC EXISTS |
2975 | EXCEPTIONS "#EC EXISTS |
2976 | OTHERS = 0. "#EC EXISTS |
2977 | ELSE. |
2978 | gv_tenant_mode = off. |
2979 | ENDIF. |
2980 | SET EXTENDED CHECK ON. |
2981 | |
2982 | ENDMODULE. " check_mt_mode OUTPUT |
2983 | &---- |
2984 | *& Module initialize_addon_installed OUTPUT |
2985 | &---- |
-
Please assist
- SAP Managed Tags:
- SAP Solution Manager
Accepted Solutions (0)
Answers (18)
Answers (18)
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Now i am waiting for the result, but i guess it won't be solved by itself.
Is there any way to fix this bug? or we have to restore or reinstall.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
the following is deadlock file,
cnsolman:smpadm 147% tail -50 SAPI-701DRINSAPBASIS.SMP|more
4 ETW000 1 entry for TADIR updated (R3TRCLASCL_GUI_ALV_GRID_BASE ).
3WETW000 CL_GUI_ALV_GRID_BASE==========CI is included by 172 master programs, therefore the buffer synchronisati
on may take some time.
4 ETW000 REPOS CL_GUI_ALV_GRID_BASE==========CI A replaced.
4 ETW000 REPOS CL_GUI_ALV_GRID_BASE==========CL A replaced.
3WETW000 CL_GUI_ALV_GRID_BASE==========CO is included by 172 master programs, therefore the buffer synchronisati
on may take some time.
4 ETW000 REPOS CL_GUI_ALV_GRID_BASE==========CO A replaced.
3WETW000 CL_GUI_ALV_GRID_BASE==========CT is included by 4149 master programs, therefore the buffer synchronisat
ion may take some time.
4 ETW000 REPOS CL_GUI_ALV_GRID_BASE==========CT A replaced.
4 ETW000 [ dev trc,00000] Thu Sep 29 11:53:37 2011 1529923743
3128.189139
4 ETW000 [ dev trc,00000] OCIStmtExecute() failed with -1=OCI_ERROR 97 31
28.189236
4 ETW000 [ dev trc,00000] SQL error 60: 40 31
28.189276
4 ETW000 [ dbsloci.,00000] *** ERROR => Error 60 in stmt_execute() from oci_execute_stmt(), orpc=0
4 ETW000 80 31
28.189356
4 ETW000 [ dbsloci.,00000] *** ERROR => ORA-60 occurred when executing SQL stmt (parse error offset=0)
4 ETW000 62 31
28.189418
4 ETW000 [ dev trc,00000] sc_p=101151f28,no=99,idc_p=1011673b0,con=0,act=1,slen=154,smax=256,#vars=7,stmt=
1020bd790,table=REPOSRC
4 ETW000 236 31
28.189654
4 ETW000 [ dev trc,00000] UPDATE "REPOSRC" SET "SDATE" = :A0 , "STIME" = :A1 WHERE "PROGNAME" = :A2 AND "R
3STATE" = :A3 AND ( \
4 ETW000 61 31
28.189715
4 ETW000 [ dev trc,00000] "SDATE" < :A4 OR ( "SDATE" = :A5 AND "STIME" < :A6 ) ); 41 31
28.189756
4 ETW000 [ dev trc,00000] sc_p=101151f28,no=99,idc_p=1011673b0,con=0,act=1,slen=154,smax=256,#vars=7,stmt=
1020bd790,table=REPOSRC
4 ETW000 77 31
28.189833
4 ETW000 [ dev trc,00000] prep=0,lit=0,nsql=0,lobret=0,#exec=186431,dbcnt=0,upsh_p=0,ocistmth_p=1020be350
4 ETW000 60 31
28.189893
4 ETW000 [ dev trc,00000] IN : cols=7,rmax=1,xcnt=1,rpc=0,rowi=0,rtot=1,upto=4294967295,rsize=77,vmax=32,b
ound=1,iobuf_p=101118e10,vda_p=1020bf9f0
4 ETW000 62 31
28.189955
4 ETW000 [ dev trc,00000] lobs=0,lmax=0,lpcnt=0,larr=0,lcurr_p=0,rret=0 38 31
28.189993
4 ETW000 [ dev trc,00000] OUT: cols=0,rmax=0,xcnt=0,rpc=0,rowi=0,rtot=0,upto=0,rsize=0,vmax=0,bound=0,iobu
f_p=0,vda_p=0
4 ETW000
4 ETW000 60 31
28.190053
4 ETW000 [ dev trc,00000] lobs=0,lmax=0,lpcnt=0,larr=0,lcurr_p=0,rret=0 37 31
28.190090
4 ETW000 [ dev trc,00000] UPDATE "REPOSRC" SET "SDATE" = :A0 , "STIME" = :A1 WHERE "PROGNAME" = :A2 AND "R
3STATE" = :A3 AND ( \
4 ETW000 57 31
28.190147
4 ETW000 [ dev trc,00000] "SDATE" < :A4 OR ( "SDATE" = :A5 AND "STIME" < :A6 ) ); 36 31
28.190183
4 ETW000 [ dbrepo ,03856] ***LOG BY4=>sql error 60 performing UPD on table REPOSRC [dbrepo#2 @ 3856
]
4 ETW000 97 31
28.190280
4 ETW000 [ dbrepo ,03856] ***LOG BY0=>ORA-00060: deadlock detected while waiting for resource [dbrepo#2 @
3856]
4 ETW000 60 31
28.190340
2EETW000 sap_dext called with msgnr "1":
2EETW000 -
db call info -
2EETW000 function: db_report_interface
2EETW000 fcode: CLOSE_LINE_MODE
2EETW000 tabname: SOURCE
2EETW000 len: 40
2EETW000 key: CL_GUI_ALV_GRID_BASE==========CU
2EETW000 retcode: 1
2EETW125 SQL error "60" during "" access: "ORA-00060: deadlock detected while waiting for resource"
1 ETP154 MAIN IMPORT
1 ETP110 end date and time : "20110929115403"
1 ETP111 exit code : "12"
1 ETP199 ######################################
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi,
Now I got the same error as Rommy mentioned. I tried to use the following command,
tp r3i all SMS pf=D:\usr\sap\trans\bin\TP_DOMAIN_SMS.PFL -Dclientcascade=yes -Dstoponerror=8 -Dsourcesystems=
tag=SPAM U06
It solved repair issue and passed SAPK-701DOINSAPBASIS, but I didn't managed to quit, tp still run. Now it
stoped at sapi-701drinsapbasis.smp phase with the oracle deadlock as follows,
cnsolman:smpadm 147% tail -50 SAPI-701DRINSAPBASIS.SMP|more
4 ETW000 1 entry for TADIR updated (R3TRCLASCL_GUI_ALV_GRID_BASE ).
3WETW000 CL_GUI_ALV_GRID_BASE==========CI is included by 172 master programs, therefore the buffer synchronisati
on may take some time.
4 ETW000 REPOS CL_GUI_ALV_GRID_BASE==========CI A replaced.
4 ETW000 REPOS CL_GUI_ALV_GRID_BASE==========CL A replaced.
3WETW000 CL_GUI_ALV_GRID_BASE==========CO is included by 172 master programs, therefore the buffer synchronisati
on may take some time.
4 ETW000 REPOS CL_GUI_ALV_GRID_BASE==========CO A replaced.
3WETW000 CL_GUI_ALV_GRID_BASE==========CT is included by 4149 master programs, therefore the buffer synchronisat
ion may take some time.
4 ETW000 REPOS CL_GUI_ALV_GRID_BASE==========CT A replaced.
4 ETW000 [ dev trc,00000] Thu Sep 29 11:53:37 2011 1529923743
3128.189139
4 ETW000 [ dev trc,00000] OCIStmtExecute() failed with -1=OCI_ERROR 97 31
28.189236
4 ETW000 [ dev trc,00000] SQL error 60: 40 31
28.189276
4 ETW000 [ dbsloci.,00000] *** ERROR => Error 60 in stmt_execute() from oci_execute_stmt(), orpc=0
4 ETW000 80 31
28.189356
4 ETW000 [ dbsloci.,00000] *** ERROR => ORA-60 occurred when executing SQL stmt (parse error offset=0)
4 ETW000 62 31
28.189418
4 ETW000 [ dev trc,00000] sc_p=101151f28,no=99,idc_p=1011673b0,con=0,act=1,slen=154,smax=256,#vars=7,stmt=
1020bd790,table=REPOSRC
4 ETW000 236 31
28.189654
4 ETW000 [ dev trc,00000] UPDATE "REPOSRC" SET "SDATE" = :A0 , "STIME" = :A1 WHERE "PROGNAME" = :A2 AND "R
3STATE" = :A3 AND ( \
4 ETW000 61 31
28.189715
4 ETW000 [ dev trc,00000] "SDATE" < :A4 OR ( "SDATE" = :A5 AND "STIME" < :A6 ) ); 41 31
28.189756
4 ETW000 [ dev trc,00000] sc_p=101151f28,no=99,idc_p=1011673b0,con=0,act=1,slen=154,smax=256,#vars=7,stmt=
1020bd790,table=REPOSRC
4 ETW000 77 31
28.189833
4 ETW000 [ dev trc,00000] prep=0,lit=0,nsql=0,lobret=0,#exec=186431,dbcnt=0,upsh_p=0,ocistmth_p=1020be350
4 ETW000 60 31
28.189893
4 ETW000 [ dev trc,00000] IN : cols=7,rmax=1,xcnt=1,rpc=0,rowi=0,rtot=1,upto=4294967295,rsize=77,vmax=32,b
ound=1,iobuf_p=101118e10,vda_p=1020bf9f0
4 ETW000 62 31
28.189955
4 ETW000 [ dev trc,00000] lobs=0,lmax=0,lpcnt=0,larr=0,lcurr_p=0,rret=0 38 31
28.189993
4 ETW000 [ dev trc,00000] OUT: cols=0,rmax=0,xcnt=0,rpc=0,rowi=0,rtot=0,upto=0,rsize=0,vmax=0,bound=0,iobu
f_p=0,vda_p=0
4 ETW000
4 ETW000 60 31
28.190053
4 ETW000 [ dev trc,00000] lobs=0,lmax=0,lpcnt=0,larr=0,lcurr_p=0,rret=0 37 31
28.190090
4 ETW000 [ dev trc,00000] UPDATE "REPOSRC" SET "SDATE" = :A0 , "STIME" = :A1 WHERE "PROGNAME" = :A2 AND "R
3STATE" = :A3 AND ( \
4 ETW000 57 31
28.190147
4 ETW000 [ dev trc,00000] "SDATE" < :A4 OR ( "SDATE" = :A5 AND "STIME" < :A6 ) ); 36 31
28.190183
4 ETW000 [ dbrepo ,03856] ***LOG BY4=>sql error 60 performing UPD on table REPOSRC [dbrepo#2 @ 3856
]
4 ETW000 97 31
28.190280
4 ETW000 [ dbrepo ,03856] ***LOG BY0=>ORA-00060: deadlock detected while waiting for resource [dbrepo#2 @
3856]
4 ETW000 60 31
28.190340
2EETW000 sap_dext called with msgnr "1":
2EETW000 -
db call info -
2EETW000 function: db_report_interface
2EETW000 fcode: CLOSE_LINE_MODE
2EETW000 tabname: SOURCE
2EETW000 len: 40
2EETW000 key: CL_GUI_ALV_GRID_BASE==========CU
2EETW000 retcode: 1
2EETW125 SQL error "60" during "" access: "ORA-00060: deadlock detected while waiting for resource"
1 ETP154 MAIN IMPORT
1 ETP110 end date and time : "20110929115403"
1 ETP111 exit code : "12"
1 ETP199 ######################################
The deadlock was caused by update on table REPOSRC and
i tried to logon system, but it got the dump, i couldn't do anything now.
afterwards, i replace the kenel patch from 7.01 69 to 7.01 150, and restart following command without U06,
tp r3i all SMS pf=D:\usr\sap\trans\bin\TP_DOMAIN_SMS.PFL -Dclientcascade=yes -Dstoponerror=8 -Dsourcesystems=
tag=SPAM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi,
Now I got the same error as Rommy mentioned. I tried to use the following command,
tp r3i all SMS pf=D:\usr\sap\trans\bin\TP_DOMAIN_SMS.PFL -Dclientcascade=yes -Dstoponerror=8 -Dsourcesystems=
tag=SPAM U06
It solved repair issue and passed SAPK-701DOINSAPBASIS, but I didn't managed to quit, tp still run. Now it
stoped at sapi-701drinsapbasis.smp phase with the oracle deadlock as follows,
cnsolman:smpadm 147% tail -50 SAPI-701DRINSAPBASIS.SMP|more
4 ETW000 1 entry for TADIR updated (R3TRCLASCL_GUI_ALV_GRID_BASE ).
3WETW000 CL_GUI_ALV_GRID_BASE==========CI is included by 172 master programs, therefore the buffer synchronisati
on may take some time.
4 ETW000 REPOS CL_GUI_ALV_GRID_BASE==========CI A replaced.
4 ETW000 REPOS CL_GUI_ALV_GRID_BASE==========CL A replaced.
3WETW000 CL_GUI_ALV_GRID_BASE==========CO is included by 172 master programs, therefore the buffer synchronisati
on may take some time.
4 ETW000 REPOS CL_GUI_ALV_GRID_BASE==========CO A replaced.
3WETW000 CL_GUI_ALV_GRID_BASE==========CT is included by 4149 master programs, therefore the buffer synchronisat
ion may take some time.
4 ETW000 REPOS CL_GUI_ALV_GRID_BASE==========CT A replaced.
4 ETW000 [ dev trc,00000] Thu Sep 29 11:53:37 2011 1529923743
3128.189139
4 ETW000 [ dev trc,00000] OCIStmtExecute() failed with -1=OCI_ERROR 97 31
28.189236
4 ETW000 [ dev trc,00000] SQL error 60: 40 31
28.189276
4 ETW000 [ dbsloci.,00000] *** ERROR => Error 60 in stmt_execute() from oci_execute_stmt(), orpc=0
4 ETW000 80 31
28.189356
4 ETW000 [ dbsloci.,00000] *** ERROR => ORA-60 occurred when executing SQL stmt (parse error offset=0)
4 ETW000 62 31
28.189418
4 ETW000 [ dev trc,00000] sc_p=101151f28,no=99,idc_p=1011673b0,con=0,act=1,slen=154,smax=256,#vars=7,stmt=
1020bd790,table=REPOSRC
4 ETW000 236 31
28.189654
4 ETW000 [ dev trc,00000] UPDATE "REPOSRC" SET "SDATE" = :A0 , "STIME" = :A1 WHERE "PROGNAME" = :A2 AND "R
3STATE" = :A3 AND ( \
4 ETW000 61 31
28.189715
4 ETW000 [ dev trc,00000] "SDATE" < :A4 OR ( "SDATE" = :A5 AND "STIME" < :A6 ) ); 41 31
28.189756
4 ETW000 [ dev trc,00000] sc_p=101151f28,no=99,idc_p=1011673b0,con=0,act=1,slen=154,smax=256,#vars=7,stmt=
1020bd790,table=REPOSRC
4 ETW000 77 31
28.189833
4 ETW000 [ dev trc,00000] prep=0,lit=0,nsql=0,lobret=0,#exec=186431,dbcnt=0,upsh_p=0,ocistmth_p=1020be350
4 ETW000 60 31
28.189893
4 ETW000 [ dev trc,00000] IN : cols=7,rmax=1,xcnt=1,rpc=0,rowi=0,rtot=1,upto=4294967295,rsize=77,vmax=32,b
ound=1,iobuf_p=101118e10,vda_p=1020bf9f0
4 ETW000 62 31
28.189955
4 ETW000 [ dev trc,00000] lobs=0,lmax=0,lpcnt=0,larr=0,lcurr_p=0,rret=0 38 31
28.189993
4 ETW000 [ dev trc,00000] OUT: cols=0,rmax=0,xcnt=0,rpc=0,rowi=0,rtot=0,upto=0,rsize=0,vmax=0,bound=0,iobu
f_p=0,vda_p=0
4 ETW000
4 ETW000 60 31
28.190053
4 ETW000 [ dev trc,00000] lobs=0,lmax=0,lpcnt=0,larr=0,lcurr_p=0,rret=0 37 31
28.190090
4 ETW000 [ dev trc,00000] UPDATE "REPOSRC" SET "SDATE" = :A0 , "STIME" = :A1 WHERE "PROGNAME" = :A2 AND "R
3STATE" = :A3 AND ( \
4 ETW000 57 31
28.190147
4 ETW000 [ dev trc,00000] "SDATE" < :A4 OR ( "SDATE" = :A5 AND "STIME" < :A6 ) ); 36 31
28.190183
4 ETW000 [ dbrepo ,03856] ***LOG BY4=>sql error 60 performing UPD on table REPOSRC [dbrepo#2 @ 3856
]
4 ETW000 97 31
28.190280
4 ETW000 [ dbrepo ,03856] ***LOG BY0=>ORA-00060: deadlock detected while waiting for resource [dbrepo#2 @
3856]
4 ETW000 60 31
28.190340
2EETW000 sap_dext called with msgnr "1":
2EETW000 -
db call info -
2EETW000 function: db_report_interface
2EETW000 fcode: CLOSE_LINE_MODE
2EETW000 tabname: SOURCE
2EETW000 len: 40
2EETW000 key: CL_GUI_ALV_GRID_BASE==========CU
2EETW000 retcode: 1
2EETW125 SQL error "60" during "" access: "ORA-00060: deadlock detected while waiting for resource"
1 ETP154 MAIN IMPORT
1 ETP110 end date and time : "20110929115403"
1 ETP111 exit code : "12"
1 ETP199 ######################################
The deadlock was caused by update on table REPOSRC and
i tried to logon system, but it got the dump, i couldn't do anything now.
afterwards, i replace the kenel patch from 7.01 69 to 7.01 150, and restart following command without U06,
tp r3i all SMS pf=D:\usr\sap\trans\bin\TP_DOMAIN_SMS.PFL -Dclientcascade=yes -Dstoponerror=8 -Dsourcesystems=
tag=SPAM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hello Everyone,
It's really good solution and it works for me as well, but Just wanted to share you that after execution of
tp r3i all SMP pf=/usr/sap/trans/bin/TP_DOMAIN_SMP.PFL -Dclientcascade=yes -Dstoponerror=8 -Dsourcesystems= tag=SPAM
I have faced another syntax error as below, while re-executing saint tcode.
Syntax error in program "SAPLSFW_COMMON ".
The following syntax error occurred in program "SAPLSFW_COMMON " in include "LSFW_COMMONU25 " in line 18:
"Type "SFW_SWITCH_DETERMINE_OBJ" is unknown"
Solution- I had activated the Enhancement spot "SFW_SWITCH_DETERMINE_OBJ" as per Note 1366282. and then re-executed the SAINT and continue with upgrade and has been completed successfully.
Cheers!!
Best regards,
Sudhir Kumar
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi Pedro,
I have followed the below steps to run the command.
1) tp r3i command from OS level
2) To activate the Enhancement spot, I did following steps:-
Call Transaction SE18
Enter ' SFW_SWITCH_DETERMINE_OBJ' for Enhancement Spot
Click button 'display '
In screen 'Enhancement Spot Display' click Button 'activate' (even though the enhancement spot is already displayed to be active)
Thanks,
Sudhir Kumar
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
We experienced the same thing on our sandbox. However, in our case we had an earlier error during DDIC Activation. We upgraded from Solution Manager 7.0 SPS 17 to EhP 1 SPS 20. The DDIC Activation got resolved by implementing Note 1256384 manually. However the request was not released when we resumed the SAINT. This caused the IMPORT_PROPER to stop at SAPK-701DOINSAPBASIS.
At this point the system was basically paralized. No Easy Access menu, no SAINT, only dumps. SE10 could not be used to release the repair request and resulted in dump. Since we know that the only request still open in our system is this repair request, we tried running:
tp r3i all SMS pf=D:\usr\sap\trans\bin\TP_DOMAIN_SMS.PFL -Dclientcascade=yes -Dstoponerror=8 -Dsourcesystems= tag=SPAM U06
I believe the U06 option forces overwrite. This overwrote the open repair request. We stopped the tp once SAPK-701DOINSAPBASIS was successfully imported per the log. After this, we managed to sign on the system and resumed the IMPORT_PROPER via SAINT.
Again, we used this method since we had nothing to lose. This is our sandbox, which already backed up prior to upgrade. We just chose not to restore from backup.
After upgrade, we implemented procedures in Note 1244225 - Solution Manager 7.0 EhP 1: recommended corrections.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Excellent solution for me !!!, tnankyou very much guys !!!,
firstly I ran this command:
tp r3i all SMP pf=D:\usr\sap\trans\bin\TP_DOMAIN_SMP.PFL -Dclientcascade=yes -Dstoponerror=8 -Dsourcesystems= tag=SPAM
and then I was able to continue with saint and finish sucesfully my EH1 implementation.
in my case tha cause of dump was the space on disc..... (<disc:>/usr/sap/...... etc.).
Edited by: Jose Rivera on Dec 7, 2009 5:55 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi,
I have the same problem. Before a few weeks we migrated the SOLMAN from Windows to Linux and created the transport system again. But when I started the command:
tp r3i all SLM pf=/usr/sap/trans/bin/TP_DOMAIN_SLM.PFL -Dclientcascade=yes -Dstoponerror=8 -Dsourcesystems= tag=SPAM
I noticed that we have an error in TP_DOMAIN_SLM.PFL.
In fact I had to do this:
#TRANSDIR =
solman\sapmnt\trans
TRANSDIR = /usr/sap/trans
I don't know why but the old path stayed there!!! After I fixed that tp was able to find its files, but it said that it could not continue because of an error 8 during previous run.
10x
We restore from backup.....
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi George / Bob / Markus / Shiva
SAP have given me a solution to my problem which was basically 2 options.
Option 1. Restore system.
Option 2. Try using this command
tp r3i all SMP pf=D:\usr\sap\trans\bin\TP_DOMAIN_SMP.PFL -Dclientcascade=yes -Dstoponerror=8 -Dsourcesystems= tag=SPAM
(please note the space between the = and tag)
(also remember to change the SID and profile path to match your system)
I opted to give the command a try and it has worked. TP picked up the patch implementation where SAINT left it after it failed and continued on to complete the IMPORT_PROPER phase.
I was then able to go into SAINT again and complete the final phases that way.
Cautionary notes: r3i can produce an inconsistent stae if used incorrectly (but in my case it wouldn't have been any worse than I already had). My original queue was up to EHP1 SPS02 (not sure how it will behave if you've included SPS03).
Finally, I am now updating to SPS04 using SPAM in the normal way.
I hope this helps guys
Best of luck.
Steve
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi George,
Is your issue resolved?
Shiva
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hello All
I too have encountered this problem. The patch update errored in phase MAIN_IMPORT and I am unable to restart SAINT, it just short dumps. I have raised a customer message with SAP and am waiting for a solution.
When I started SAINT and performed the queue calculation I accepted the queue that was offered to me up to SAPKB70102 and did not include SAPKB70103 or SAPKB70104. Most of the SAP notes that I've found on this problem seem to suggest it is a problem with SAPKB70103 and that if you include SAPKB70104 as well the problem does not occur. So really I should not have had the problem unles the problem is deeper and can only be prevented by going straight up to SAPKB70104. I did not know this before I started.
The moral here is be vary careful with EHP1 for 7.00 and read the notes very carefully. A bit too late for some of us but hey if it helps someone else then fine.
Steve
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi,
Following are the OSS notes which needs to be referred thoroughly before proceeding with Stack upgrade of SolMan to EhP1:
Note 822380 - Problems w/ add-on inst/upgrade to SAP NW 7.0 AS ABAP
Note 822379 - Known problems with Support Packages in SAP NW 7.0x AS ABAP
Note 1146578 - Central Note: Upgrade to Systems on SAP NetWeaver 7.0 EHP1
Note 1169247 - Enhancements to Solution Manager 7.0 EHP1 upgrade (SPS18,19)
If you have not referred any of the above notes, I strongly recommend to go through above notes as it says so many OSS notes to be applied before upgrade in order to avoid issues.
Could you please send the list of the files along with timestamp from the path "/usr/sap/trans/tmp" for further analysis.
Regards
Shiva
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Request help from SAP Support, ceate a message on component BC-UPG-OCS-SPA.
Best regards,
Ruediger
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
I have the same ERROR !
Any solutions for this problem ?
Some transactions are working, but if you call SAINT/SPAM/... -> Short dump.
Also TP (out from STMS) is not running any more...
regards
Markus
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
I have the same problem.
Any solutions known?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi
Did bounce the server and cross check whether you are able to execute any Tcode,if that wont work i would suggest to raise this to SAP so that they can look into this issue
Regards
Uday
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
for the tp command ---> tag=spam not saint
Sorry for that
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi
Was the patch upgrade stopped in the middle due to any reason?
Regards
Uday
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
No,
it stopped during main import I guess.
In the usr\sap\trans\log I find SAPI-701DOINSAPBASIS.SMG with return code 8,
but by running command
tp showbuffer SMG tag=saint pf=/usr/sap/trans/bin/TP_DOMAIN_SMG.PFL
I get that it has been already imported completely and I cannot find any other with rc8 or higher
Please assist.
- ABAP Cloud Developer Trial 2022 Available Now in Technology Blogs by SAP
- SAP Solution Manager System Availability Reports in Technology Q&A
- Hack2Build on Business AI – Highlighted Use Cases in Technology Blogs by SAP
- SAP Partners unleash Business AI potential at global Hack2Build in Technology Blogs by SAP
- Magic Numbers : A Solution to Foreign Characters in SAP CPI in Technology Blogs by Members
| User | Count |
|---|---|
| 93 | |
| 10 | |
| 10 | |
| 9 | |
| 9 | |
| 7 | |
| 6 | |
| 5 | |
| 5 | |
| 4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.