on 05-19-2013 6:33 PM
Hello,
Please, has anyone been able to apply any support package to SAP ERP 6.0 EHP6 IDES?
I have been trying to do that...but the phase IMPORT_PROPER is taking a long time.
Some people say it is not possible to apply support package to SAP IDES system....but I know it is possible as I have an SAP IDES ERP 6.04 that I normally apply support package on.
Any idea will be appreciated.
Hi John,
Did you finally managed to solve this? I'm facing the same issue but in DDIC_ACTIVATION phase. Our system is an IDES ERP 6.0 EHP 6 and the SPs being imported are SP6, SP7 and SP8 for component ST-PI 2008_1_700 (requested by RTCCTOOL report).
The tp and R3trans have been updated to the latest available patch. No errors have been detected in wp dev_traces nor in tp logs. Also, not updates present in /usr/sap/trans/tmp.
Could you please advise on what to check to solve this issue?
Thanks and regards
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi John,
To keep it short, we have installed new add-ons, upgraded the Support Packs as well on ECC6 EHP6 IDES System without much issues.
At one instant we were really troubled, so we restored the backup and again proceeded.
If you keep all the check points in place you shall be able to finish it irrespective of this being an IDES system.
Ensure, you are running latest Kernel, R3trans, tp, SPAM/SAINT update before doing any upgrade activity. Also have a backup.
-Akshay
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Akshay,
Can you suggest what's the latest releases of these components are? (ie Kernel, R3trans, tp, SPAM/SAINT).
I thought that R3trans and tp are updating with the kernel relese, aren't they?
Also, would you suggest exact paths for those components download, I have an access, but I have no ieda where to look for them.
Can you answer how long BASIS update lasts? (I was waiting for two days and got nothing).
Server configuration: MB: ASUS Z87PRO, Proc. Intel i7 3.5Ghz (4 cores, 8 streams), RAM 16Gb, HDD VelociRaptor 10000rpm, 1Tb x4 (RAID 0). Windows Server 2008R2, SQL SERVER 2008 R2 SP1.
Thank you in advance!
Hi Aleks,
Assuming your Kernel Release is 720_REL 64B UNICODE for IDES ERP6 EHP6, latest patch of Kernel on SMP is Patch 402 under path:
SAP Market Place => Software Downloads => Support Packages & Patches => A-Z Index => K => SAP Kernel 64 Bit Unicode => SAP KERNEL 7.20 64-BIT UNICODE => <Your OS>
Further check your R3trans/tp version using R3trans -V/ tp -V (Should be same as that of your Kernel i.e. 720_REL 64B UNI) and you can get the latest patch same as in above path, just extend it further to Database Independent i.e.
SAP Market Place => Software Downloads => Support Packages & Patches => A-Z Index => K => SAP Kernel 64 Bit Unicode => SAP KERNEL 7.20 64-BIT UNICODE => <Your OS> => #Database independent
Latest R3trans and tp both are at patch level 437
I hope you got the Kernel right on!
Check your SPAM/SAINT Release in initial screen of t-code SPAM
For SPAM/SAINT Release 731, latest patch is 50, as per below path:
SAP Market Place => Software Downloads => Support Packages & Patches => Browse our Download Catalog => Additional Components => SAP SPAM/SAINT Update => SPAM/SAINT Update 731 => Support Packages
When you update the Kernel, the R3trans/tp bundled with that Kernel release comes into the system, but the thing is that R3trans & tp patches are developed and released more frequently than the bundled kernel release, so its always crucial to be on the latest R3trans/tp for SAP Upgrade activity i.e. You might on be the latest Kernel 402, but still your R3trans might not be latest 437, so do that explicitly.
All the path details are mentioned above with the screen-shots, you should be able to get that now!
BASIS Updates! Hmmmm.. Tell you frankly, these are the longest painstaking patches.
My suggestion, apply one patch at a time or max two, dont go for the whole queue unless you believe in your system's capacity. We have a decently powered server 4 Cores, 32 Gigs Mem, 64G Swap and we observed the optimum was taking two Basis patches at once and nothing else along with them. So here you go, apply BASIS stand-along as the first in seq. taking 1 or 2 at a time.
Make sure you have a full backup.
Did you monitor the work processes, checked the logs?
Something must be pointed out if it got stuck somewhere.
Couple of key checks:
1) Monitor File System
2) Monitor Work Processes
3) Check if logs are updating or not.
4) Check Oracle Alert log and SAP Work logs
-Akshay
Hi Aleks
sorry for the delay but I can't answer of your reply to me. Can you please sent me an e-mail to oliver.ruckober@sap.com and we will check an possible connection through team viewer or antother network tool.
regards Oliver
Is there any solution for this issue?
I am facing the same problem now. I'm trying to apply new SAP_ABAP/SAP_BASIS packages now and IMPORT_PROPER phase is endless... During upgrade the GUI became unavailable (any attempt to access it gives ABAP runtime error). As I know it is normal while SP is installing. I was monitoring update progress through 'dpmon' utility (btw., is this only way to see/monitor the progress?) and it was saying that SAPLSTPA process is running. I was waiting for about two days but the status of this process suddenly changed to 'stop' (by some reason time counter were running despite this fact). So, I decided that upgrade is done and rebooted the system. Nothing happened, the GUI is broken (gives ABAP runtime error) and it means that process was not completed
the system is SAP ERP6 EHP 6, release 731, current patch level is 0002 and I'm trying to upgrade to 0003 and then to 0004.
The questions is next:
- what am I doing wrong?
- is it possible to jump over the patch level, ie to upgrade right to 0004 or it should be sequential process?
- How I can speed up the process (apart from hardware, as my server fast enough to perform any update)
- Any clue what's going on with IMPORT_PROPER pahse? (the logs looks just fine, no errors, but as we can see- no results as well).
I have already patched to the latest release of kernel and SPAM/SAINT (0049)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Abap & Basis Patches are which troubles most of the time so the queue definition should be based on the SAP Note. You cannot jump over the patch level it should go sequentially.
Note 1597767 - Known problems with Support Packages in SAP NW 7.3 AS ABAP
You can use the downtime minimized option with more parallel process. But at this time you have to keep looking the lastes logs if they are updating.
Regards,
Subhash
Hi Subhash,
Thanks for you reply. I have checked this note... and found nothing useful as I didn't faced any issues from those described in the note. In my case everything goes just fine till IMPORT_PROPER step and the main problem is that it lasts for ages.
Like I said before, I was trying to track progress through 'dpmon' but it doesn't seem a good idea.
Could you explain your last paragraph, ie how I can track that SPAM is doing something useful, ie package update.
How I can use more parallel processes?
Is it matters what to update first, ie ABAP component or BASIS? ... maybe it;s because I'm trying to update BASIS first? Thanks!
Hi Aleks,
You will have to keep digging the log directory for any file with recent time stamp to understand if there is any progress. Also if my understanding is currect you would not be able to login into system due to SYNTAX_ERROR. So at this time you cannot set any parallel process.
This is an IDES system, so may be you can give it a try through OS. Please see the last answer of this thread.
http://scn.sap.com/thread/727388
Regards,
Subhash
Dear John,
It is technically possible to apply support packages to IDES but it is not recommended.
What is the list of support package being imported?
Are the logs in
usr/sap/trans/tmp
and
usr/sap/trans/log
being updated regularly ?
What is being written to the current SLOG?
regards,
Paul
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Paul,
Thanks for the reply.
The SLOG only updates onces I restarted SAINT.
The only error in the SLOG is ERROR: RFC function TRINT_PROGRESS_INDICATOR returned 18.
I have checked every where online for a fix but there seems to be no answer yet in all the links I have checked.
I will apreciate your help.
I am just applying QIE at the moment - K-20000INQIE.SAR...I intend to put EWN 7.02 on it.
I mean't EWM not EWN.
The log is here below:
START CMDIMPORT | CEG L | 20130519144820 | CEGADM | ACCE 20130519144819978 | |
STOP CMDIMPORT | CEG L | 20130519144826 | CEGADM | ACCE 20130519144819978 | |
START DD IMPORT | CEG H | 20130519145402 | CEGADM | ACCE 20130519145402123 | |
STOP DD IMPORT | CEG H | 20130519145602 | CEGADM | ACCE 20130519145402123 | |
START DD ACTIVATION | CEG A | 20130519145605 | CEGADM | ACCE | |
START tp_getprots | CEG J | 20130519145606 | CEGADM | ACCE | |
STOP tp_getprots | CEG J | 20130519153152 | CEGADM | ACCE | |
STOP DD ACTIVATION | CEG A | 20130519153153 | CEGADM | ACCE | |
START imp all | CEG | 20130519153155 | CEGADM | ACCE 20130519153154888 |
INFO: event SAP_IMPORT_START triggered successfully
START DD IMPORT | CEG H | 20130519153155 | CEGADM | ACCE 20130519153154888 |
STOP DD IMPORT | CEG H | 20130519153155 | CEGADM | ACCE 20130519153154888 |
START DISTRIBUTION OF DD-O CEG S | 20130519153155 | CEGADM | ACCE 20130519153154888 | |
START tp_getprots | CEG S | 20130519153156 | CEGADM | ACCE 20130519153154888 |
STOP tp_getprots | CEG S | 20130519153206 | CEGADM | ACCE 20130519153154888 |
STOP DISTRIBUTION OF DD-O CEG S | 20130519153206 | CEGADM | ACCE 20130519153154888 | |
INFO TBATG CONVERSION OF CEG N | not needed | CEGADM | ACCE 20130519153154888 |
INFO: apg locked (anticipatory program generation)
START MOVE NAMETABS | CEG 6 | 20130519153206 | CEGADM | ACCE 20130519153154888 |
START tp_getprots | CEG P | 20130519153207 | CEGADM | ACCE 20130519153154888 |
STOP tp_getprots | CEG P | 20130519153252 | CEGADM | ACCE 20130519153154888 |
STOP MOVE NAMETABS | CEG 6 | 20130519153252 | CEGADM | ACCE 20130519153154888 |
START MAIN IMPORT | CEG I | 20130519153252 | CEGADM | ACCE 20130519153154888 |
STOP imp all | CEG 7006 20130519171247 | CEGADM | ACCE 20130519153154888 |
ERROR: RFC function TRINT_PROGRESS_INDICATOR returned 18
START imp all | CEG | 20130519172103 | CEGADM | ACCE 20130519172102993 |
INFO: event SAP_IMPORT_START triggered successfully
START DD IMPORT | CEG H | 20130519172104 | CEGADM | ACCE 20130519172102993 |
STOP DD IMPORT | CEG H | 20130519172104 | CEGADM | ACCE 20130519172102993 |
INFO TBATG CONVERSION OF CEG N | not needed | CEGADM | ACCE 20130519172102993 | |
START MOVE NAMETABS | CEG 6 | 20130519172105 | CEGADM | ACCE 20130519172102993 |
START tp_getprots | CEG P | 20130519172105 | CEGADM | ACCE 20130519172102993 |
STOP tp_getprots | CEG P | 20130519172108 | CEGADM | ACCE 20130519172102993 |
STOP MOVE NAMETABS | CEG 6 | 20130519172109 | CEGADM | ACCE 20130519172102993 |
START MAIN IMPORT | CEG I | 20130519172109 | CEGADM | ACCE 20130519172102993 |
START imp all | CEG | 20130519191308 | CEGADM | ACCE 20130519191308186 |
INFO: event SAP_IMPORT_START triggered successfully
START DD IMPORT | CEG H | 20130519191308 | CEGADM | ACCE 20130519191308186 |
STOP DD IMPORT | CEG H | 20130519191309 | CEGADM | ACCE 20130519191308186 |
INFO TBATG CONVERSION OF CEG N | not needed | CEGADM | ACCE 20130519191308186 | |
STOP imp all | CEG 7006 20130519194109 | CEGADM | ACCE 20130519172102993 |
ERROR: RFC function TRINT_PROGRESS_INDICATOR returned 18
STARTSTOP imp all | CEG 7006 20130519194111 | CEGADM | ACCE 20130519191308186 |
ERROR: RFC function TRINT_PROGRESS_INDICATOR returned 18
START imp all | CEG | 20130519201758 | CEGADM | ACCE 20130519201758536 |
INFO: event SAP_IMPORT_START triggered successfully
START DD IMPORT | CEG H | 20130519201759 | CEGADM | ACCE 20130519201758536 |
STOP DD IMPORT | CEG H | 20130519201759 | CEGADM | ACCE 20130519201758536 |
INFO TBATG CONVERSION OF CEG N | not needed | CEGADM | ACCE 20130519201758536 | |
START tp_getprots | CEG P | 20130519201800 | CEGADM | ACCE 20130519201758536 |
STOP tp_getprots | CEG P | 20130519202015 | CEGADM | ACCE 20130519201758536 |
START MOVE NAMETABS | CEG 6 | 20130519202015 | CEGADM | ACCE 20130519201758536 |
START tp_getprots | CEG P | 20130519202015 | CEGADM | ACCE 20130519201758536 |
STOP tp_getprots | CEG P | 20130519202017 | CEGADM | ACCE 20130519201758536 |
STOP MOVE NAMETABS | CEG 6 | 20130519202017 | CEGADM | ACCE 20130519201758536 |
START MAIN IMPORT | CEG I | 20130519202017 | CEGADM | ACCE 20130519201758536 |
START imp all | CEG | 20130519205336 | CEGADM | ACCE 20130519205335930 |
INFO: event SAP_IMPORT_START triggered successfully
START DD IMPORT | CEG H | 20130519205336 | CEGADM | ACCE 20130519205335930 |
STOP DD IMPORT | CEG H | 20130519205336 | CEGADM | ACCE 20130519205335930 |
INFO TBATG CONVERSION OF CEG N | not needed | CEGADM | ACCE 20130519205335930 |
Hi John,
It doesnt look like its causing the issue but TRINT_PROGRESS_INDICATOR returned 18 is often due to using tp and R3trans tools which are old (over 4 months old I would consider updating to the latest available patch levels for your release)
Could you attach screenshots of the current contents of
usr/sap/trans/tmp
and
usr/sap/trans/log
regards,
Paul
Hi Paul,
I actually upgraded the kernel to 402 (SAPEXE_402-20006748.SAR and SAPEXEDB_402-20006747.SAR) before I started the addon installation. So I am on the latest Kernel SP.
I already uninstalled the system and started afresh again. What I have noticed is that I get the RFC error (RFC function TRINT_PROGRESS_INDICATOR) in SLOG when I terminate the SAINT operation and re-start it without deleting the content of tmp folder. If I restore from a backup for example, and initiate the SAINT operation the first time, I do not get the RFC error.
One more thing I have noticed is that the file SAPRUPGM in /tmp stops updating once it gets to the message - "Object still has to be migrated"
Before it gets here...it was just "Delete flag set" for all objects. Is this an issue?
4 E 531 Unknown message with "LIMU" "WAPP" "Z_BAIO_SUE_1 | WEBBROWSER.HTM" "Delete flag set" |
4 E 531 Unknown message with "R3TR" "SXCI" "/SAPSLL/BP_HR_BANK" "Object still has to be migrated"
4 E 531 Unknown message with "R3TR" "SXCI" "/SAPSLL/BP_HR_GEN" "Object still has to be migrated"
4 E 531 Unknown message with "R3TR" "SXCI" "/SAPSLL/BP_HR_ROLES" "Object still has to be migrated"
4 E 531 Unknown message with "R3TR" "SXCI" "/OPT/VIM_CHECK_MIGO" "Object still has to be migrated"
4 E 531 Unknown message with "R3TR" "SXCI" "ZPUR_DOCUMENT_BADI" "Object still has to be migrated"
4 E 531 Unknown message with "R3TR" "SXCI" "DPR_TTO_STAT" "Object still has to be migrated"
4 E 531 Unknown message with "R3TR" "SXCI" "ZHRWPC_PCR" "Object still has to be migrated"
4 E 531 Unknown message with "R3TR" "SXCI" "ZISR_RU01" "Object still has to be migrated"
4 E 531 Unknown message with "R3TR" "SXCI" "ZISR_RU03" "Object still has to be migrated"
4 E 531 Unknown message with "R3TR" "SXCI" "ZP00" "Object still has to be migrated"
4 E 531 Unknown message with "R3TR" "SXCI" "ZQISR1_IF01" "Object still has to be migrated"
content of tmp and log path are attached.
Hi John,
It is not recommended and supported to install the addon using the tp command in the system. The addons should be installed or upgraded using the SAINT or SUM tool.
Regarding the hanging status of the import_proper can you please check if the below steps assist
you in resolving the issue.
Ensure that no tp processes are running at the OpSys level before proceeding with the next steps.
Ensure that there exists no clogged entries in TRBAT,TRJOB,TRBATS & TPSTAT table entries. If exists remove them.
Please rename all the files under /trans/tmp, or relocate them to another temp directory.
Ensure that RDDIMPDP job is scheduled in ALL clients including
client 000 as DDIC user.
Repeat the hanging phase.
Thank You.
Regards,
Deepika
User | Count |
---|---|
86 | |
10 | |
10 | |
9 | |
6 | |
6 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.