SUM DMO Cannot create named pipe

[#1]

It can be as simple as 123 but I'm on this error since 2 days :(. I hope someone can help me get out of this.

I setup permission on the folder to 777 but it still not able to continue.

[RolandKramer]

Nevertheless, the SAP Kernel you are using is four years old, your SUM was outdated. How should this work? ALWAYS update you binaries first, despite what you are doing ...

[babuilyas]

I doubt, please confirm, BASIS 731 supports 754 Kernel?

[babuilyas]

Can you explain it in little detail of binaries update?. a bit confused with this error and asking myself why I need to update source system kernel binaries? Correct me if I'm wrong, SUM copies source kernel to SUM/abap/exe and then apply latest kernel for source system as it asked during extraction. Should I confirm SUM/abap/exe got the right binaries or not?!

[RolandKramer]

it is not relevant what the SAP Kernel says.
btw: the SAP Kernel 7.22 you are using is almost four years old! are Y kidding me?
PLEASE update the source binaries as well and check the result in tx. SPUMG in the source system

Best Regards Roland

[babuilyas]

Hehe. no way.

I'm following this scenario in test.

EHP6 (linora) to S4.

SAP Kernel is as per PAM. You can quickly find it below:

[RolandKramer]

Hi muhammad.ilyas,

Is the Source System on Oracle based on UC or NUC?
It seems there are some inconsistencies ...

Nevertheless the findings in the Blog - optimizing system downtime is timeless … should be adapted to the latest version.

Best Regards Roland

[babuilyas]

It is confirmed Unicode and I can see it in System > Status. I confirmed it via R3tran -version as well.

[babuilyas]

this 722 is source system kernel. i think you took as SUM/abap/bin kernel. I checked it again and found it is by default 7.53 patch level 601 for SUM 2.0 SP08 PL1.

and exe and exe_2nd both has target kernel i.e. 754.

[RolandKramer]

Ok,

can you please share the detail about source and target configuration:

- OS
- DB, UC or NUC, Version
- SAP Application from - to
- SAP Kernel Version from - to

there are always two SAPup processes running, don't worry

best regards Roland

[babuilyas]

Thanks for swift reply. It is UC.

System and Host Information: ============================ -

SID: R3P - Host: erpehp6 - Instance No.: 00 - Shadow Instance No.: 03 - OS Type: Linux X86_64 - OS Version: 2.26 - Kernel Path: /usr/sap/R3P/DVEBMGS00/exe - SUM Directory Path: /usr/sap/R3P/SUM/abap - Start Release: 731 - Target Release: 754

Database Information: ===================== -

DB Type: ora - DB Version: 19.7.0.0.0 - DB Host: erpehp6 - DB SID: R3P - Target DB Type: HDB - Target DB Version: 2.00.047.00.1586595995 - Target DB Host: s41909hdb - Target DB SID: HDB

[nicholas_chang]

can't open those files.

And do you check the os log, memory usage on SAP PAS?

[babuilyas]

I also think it is due to memory utilization but I didn't find this in available logs to me from hana and sum. Perhaps OS logs may be helpful but for now, i'm closing it and I will resume the process again after adding 64gb additional ram to the system.

[nicholas_chang]

Hi,

First of all, can you check the memory utilization on both SAP AS and HANA server? And i believe checking the all relevant *00002_DDNTF* files might give you some hints, as well as the indexserver trace..

[babuilyas]

Thank you for responding to it. I didn't find any error message in the hana and I found the tables are created. I tried to collect log files from the sum so that may be helpful. I read log files in sum/migrate_sot folder but didn't find any clue to the error. Log files are more than one, so i quickly made it available on http://sum.hopto.org:6421/.

[babuilyas]

Hi nicholas.chang , i read your dmo blogs. Hope you may have dealt with this error.

[babuilyas]

I could apply the latest patch for 722 to the source system and system could start and confirmed applied.

There was a glitch with sapcpe so I copied kernel to DVEBMGS00/exe as well.

Then I killed SAPup processes and restarted SUM and it resumes but stuck again at same position.

Please guide, I doubt it has some link with SGEN or R3load is failing for DDNTT tables. Any log files which can help to find reason for this error 😞 I read ../MIGRATE_SOT_00002_DDNTF_EXP.LOG and others but so far no luck.

@Roland, Special thanks for your time and help.

[babuilyas]

it wasn't a problem with sapcpe but in fact, 722 kernel directory structure is like this.

[babuilyas]

As per note: 837173

Follow the description in chapter 'Nametab Handling'. Report RADCUCNT will be
executed in background to generate the Unicode nametabs in both Single Code Page
and MDMP systems right before the database export.

So this may be the cause, so i'm running this report to generate DDNTT/F tables and content.

[RolandKramer]

Hello Muhammad Ilyas,

Please make sure that the current SAP Kernel 7.22 is applied in your SAP Source System as follows. The binaries will be unpacked to the Directory /usr/sap/R3P/SYS/exe/uc/<platform>.
when restarting the Source System R3P the current kernel will be copied to the Directory /usr/sap/R3P/DVEBMGS00/exe.

SAP System Directories on UNIX

the latest SAP Kernel 7.22_EX2 64-Bit UC for Oracle

It seem you missed to download these files as well in the SAP Maintenance Transaction.

Best Regards Roland

[babuilyas]

Hi david.gabel, i believe port forwarding to my sum run can help find root cause.

https://sum.hopto.org:6420/lmsl/sumabap/R3P/slui/

The underline system is very fresh without any data.

Please DM if possible, I can't from here.

[babuilyas]

I started as root.

./SUMSTART confighostagent

But SLUI was logged on with <sid>adm,

[babuilyas]

SUM 2.0 SP08 PL1 process in the system right now. I followed same start command and SLUI login, so probably i didn't notice this before and may be would the cause. Anyways. lets how this react in preprocessing phase.

[babuilyas]

I will close this with feedback as pass through the error with SP08 PL1.

[RolandKramer]

Ok, thanks. Please mark the Solution as "correct answer" ...

[Former Member]

It would have been interesting to determine the root cause of the named pipe error, typically this error can occur when the SUM is extracted as root rather than <SID>adm. Is it possible the SUM 2.0 SP 7 (PL2) was extracted as root ?

[RolandKramer]

Hi,

please use the latest Version of the SUM 2.0 SP07 Patch which is PL09 or a higher Version.
Note 2790229 – Central Note – Software Update Manager 2.0 SP07 [lmt_023]

Note 2489550 -EU_CLONE_MIG_UT_RUN phase fails with "write_to_pipe" error during upgrade

Note 2240098 - Wrongdata / missing data after unclustering tables

The Problem is already fixed since a while. If you are patching within the same SP the PL level, simply stop the SAPup and overwrite the existing binaries. It will not overwrite your own files from the DMO run.

If you want to use the latest Version of the SUM/DMO like SP08 PL01 or higher, then I would recommend to start over again. So in your case use the latest PL Version for SUM 2.0 SP07

Nevertheless check the Document - SAP First Guidance – Using the new DMO to migrate to BW on HANA for Keywords like pipe or cluster

Best Regards Roland

[babuilyas]

Thanks for swift response. I think I should follow recommendation. Heading to download latest SP08.

I already checked the doc for your blog post and searched for pipe and find nothing relevant for my case.

[babuilyas]

Again at same stage. I think there is something else which causes this. This may be the ram cap. Can I schedule to run one job at a time. I can provide access to the SUM process if you have a chance to look into.

[babuilyas]

Hi roland.kramer, can you help me with this error in DMO.