Hi,

System ruuning with very slow performance, also transports taking too long time to import.

I found some errors in SLOG , there are many entries " Background job RDDIMPDP could not be started or terminated abnormally"

As per SAP note 79518 , this standard job is not running properly. Do i need to reschedule this job in client 000 as ddic. Is there any conflict/effect for my prod system to trigger this job?

Do i need to schedule this job in all clients or only 000 is enough ?

WARNING:       Background job RDDIMPDP could not be started or terminated abnormally.

      Please check that the R/3 system is running.

      Please check the system. Use transactions SM21, SM37, SM50.

WARNING:       (This warning is harmless if no further warnings follow.)

WARNING: System QMS. Warning.        20061113154258 :

WARNING:       Background job RDDIMPDP could not be started or terminated abnormally.

      Please check that the R/3 system is running.

      Please check the system. Use transactions SM21, SM37, SM50.

WARNING:       (This warning is harmless if no further warnings follow.)

WARNING: System QMS. Warning.        20061113154759 :

WARNING:       Background job RDDIMPDP could not be started or terminated abnormally.

      Please check that the R/3 system is running.

      Please check the system. Use transactions SM21, SM37, SM50.

WARNING:       (This warning is harmless if no further warnings follow.)

WARNING: System QMS. Warning.        20061113155259 :

WARNING:       Background job RDDIMPDP could not be started or terminated abnormally.

      Please check that the R/3 system is running.

      Please check the system. Use transactions SM21, SM37, SM50.

WARNING:       (This warning is harmless if no further warnings follow.)

WARNING: System QMS. Warning.        20061113155800 :

WARNING:       Background job RDDIMPDP could not be started or terminated abnormally.

      Please check that the R/3 system is running.

      Please check the system. Use transactions SM21, SM37, SM50.

WARNING:       (This warning is harmless if no further warnings follow.)

WARNING: System QMS. Warning.        20061113160301 :

WARNING:       Background job RDDIMPDP could not be started or terminated abnormally.

      Please check that the R/3 system is running.

      Please check the system. Use transactions SM21, SM37, SM50.

WARNING:       (This warning is harmless if no further warnings follow.)

Thanks

Lisa

Any idea..

In this document you will find the latest information about the SAP kernel such as

• Announcements of SP stack kernel deliveries
• Other news related to the development, maintenance and usage of the SAP kernel versions 72X (721, 721_EXT, 722, 722_EXT) and 74X (742, 745)

If you are interested in getting notifications when this document is updated, please activate the "Receive email notifications" feature. To unsubscribe from receiving notifications, click on "Stop email notifications".

News

28.04.2016: SP Stack Kernel 742 PL 400 released

SP stack kernel 742 PL 400 is now available on SAP Support Portal. It contains various improvements and enhancements that are outlined in detail in Note 2300406.

Information on known issues in the stack kernel 742 PL 400 can be found in Note 2294986. This note will be updated on a regular basis.

14.04.2016: WebGUI issue with Google Chrome Version 50

After updating Google Chrome from Version 49 to Version 50 the Easy Access Menu (start screen) remains empty. We are working on a kernel patch to circumvent this. For details see SAP Note 2305778.

12.04.2016: Potential Issue with Kernel 742 PL 311 - 321 and Kernel 745 PL 25 - 35

In edge cases a select statement may return an unexpected result. For details see SAP Note 2273425.
It is recommended to upgrade to SP Stack Kernel 745 PL 100 or Kernel 742 PL 329 which is the last release candidate before the upcoming SP Stack Kernel 742 PL 400.

17.03.2016: Kernel 745 Released as DCK to Kernels 740, 741 and 742

After an extended validation phase kernel 745 PL#100 has been released as a downward compatible kernel (DCK) to kernels 742, 741 and 740 and can be used instead of these with SAP NetWeaver 7.4. Refer to SAP Note 2251972 for details on installation and usage of kernel 742 as DCK. The release roadmap for 74* kernels is presented in SAP Note 1969546.

17.03.2016: SP Stack Kernel 722 PL 101 released

SP stack kernel 722 PL #101 is now available on SAP Support Portal. It contains various improvements and enhancements that are outlined in detail in Note 2292019.

Information on known issues in the stack kernel 722 PL #101 can be found in Note 2292017. This note will be updated on a regular basis.

18.12.2015: SAP Kernel 721 PL 618 and SAP Kernel 722 PL 20 and PL 21 revoked

As a precaution the Kernel (dw.sar) for 721 PL 618 and 722 PL 20 and 21 have been revoked from the SAP Support Portal.

For further details see SAP Note 2259736. We are working a patch highest priority.

13.11.2015: Heads up on Kernel 745 for NetWeaver 7.4

During Q1/2016 SAP Kernel 745 will be made available as Downward Compatible Kernel for SAP NetWeaver 7.4.

SAP Kernel 745 will eventually succeed SAP Kernel 742 (and 741 and 740).

SAP Kernel 742 will be retired in Q1/2017, one year later than the availability of SAP Kernel 745 as DCK. No more patches will be provided for SAP Kernel 742 after that date.

See also Understanding Kernel Releases for the SAP NetWeaver AS ABAP and SAP Note 1969546 - Release Roadmap Kernel 740

09.11.2015: SP Stack Kernel 742 PL#300 Released

SP stack kernel 742 PL #300 is now available on SAP Support Portal. It contains various improvements and enhancements that are outlined in detail in SAP Note 2237353.

Information on known issues in the stack kernel 742 PL #300 can be found in SAP Note 2231749. This note will be updated on a regular basis.

16.10.2015: Kernel 722 PL14, PL15 and enserver PL 14 revoked

As a precaution Enqueue Server 722 PL 14 (enserver.sar) and Kernel (dw.sar) 722 PL 14 and PL 15 have been revoked from the SAP Support Portal.
The new patch of the Enqueue Server might not be 100% compatible to older clients (e.g. disp+work PL 13) and the newer disp+work starting PL 14 might not be 100% compatible with old Enqueue Servers (prior patch 14). Standard operations Enque, Dequeue and DequeueAll are NOT affected. Details can be found in SAP Note 2239931

13.10.2015: SP Stack Kernel 721 PL#600 Released

SP stack kernel 721 PL #600 is now available on SAP Support Portal. It contains various improvements and enhancements that are outlined in detail in SAP Note 2214191.

Information on known issues in the stack kernel 721 PL #600 can be found in SAP Note 2214680. This note will be updated on a regular basis.

02.10.2015: issue with Oracle lib_DBSL 722 PL 13

Please do not use patch 13 for the 722 Oracle lib_DBSL

Further details can be found in note 2220724. A fix is expected early next week.

14.09.2015: SP Stack Kernel 741 PL#300 Released

The last SP stack kernel for the 741 kernel version has been released today. Kernel 741 PL #300 can be downloaded from the archive area of SAP Support Portal. Refer to release note 2207362 for information on fixes included in this stack kernel.

As announced previously, kernel 741 has reached its end of maintenance, see note 1969546 for more detail. Future 74* kernel corrections will be delivered through 742 kernel patches.

08.07.2015: SP Stack Kernel 742 PL#200 Released

SP stack kernel 742 PL #200 is now available on SAP Support Portal. It contains various improvements and enhancements that are outlined in detail in Note 2178917.

Information on known issues in the stack kernel 742 PL #200 can be found in Note 2176515. This note will be updated on a regular basis.

07.07.2015 SAP Kernel 741 maintenance

The SAP Kernel 741 reached its end of maintenance, see note 1969546. We will continue to deliver regression fixes during July and a final stack kernel 741 PL#300 in August. After that corrections will be delivered through kernel 742 patches.

12.06.2015 SAP Kernel Archive

SAP Kernels which are out of maintenance like SAP Kernel 720 can be found in the archive https://support.sap.com/software/patches/archive.html

For SAP Kernel 720 the last version is patch level 800. Please read the release note 2158874  - SAP Support Package Stack Kernel 7.20 (EXT) Patch Level 800. Corresponding note for regression found in the future is 2138737.

20.05.2015 SAP Kernel 722 Released

SAP kernel 722 has been released for customers today. The first shipment (Kernel 722 PL#4) can now be downloaded from SAP Support Portal. With this a new release cycle has been established for 72X kernel versions that can be used with all SAP NetWeaver releases 7.00-7.31:

• Kernel 720 reached its end of maintenance, no further corrections will be provided for this kernel version
• Kernel 721 becomes the standard kernel containing only corrections/bug fixes
• Kernel 722 replaces Kernel 721 in its role as Innovation Kernel. Besides regular corrections, new features/enhancements/improvements will be delivered with Kernel 722.

Refer to SAP Note 2133909 for general information on Kernel 722 including new features and current limitations. This note will be updated on regular basis.

Kernel 722 can be applied manually as a kernel patch, see Note 2115344 - Installation of Kernel 722 (EXT) for detailed instructions. Options to apply Kernel 722 during upgrade/update are outlined in Note 2133909.

04.05.2015: SP Stack Kernel 721 PL#500 Released

A new SP stack kernel 721 PL #500 is now available on SAP Support Portal.

SAP Note 2158856 contains the list of changes and enhancements introduced in this stack kernel compared to the previous stack kernel PL #402.

All regressions known in the PL #402 have been fixed.

Review SAP Note 2155366 for known issues in the stack kernel 721 PL #500. This note will be continuously updated.

14.04.2015: Kernel 742 Released as DCK to Kernels 740 and 741

After an extended validation phase kernel 742 PL#101 has been released as a downward compatible kernel (DCK) to kernels 741 and 740 and can be used instead of these with SAP NetWeaver 7.4. Refer to Note 2128122 for details on installation and usage of kernel 742 as DCK. The release roadmap for 74* kernels is presented in Note 1969546.

31.03.2015: SP Stack Kernels 741 PL#201 and 742 PL#101 are delivered

As announced previously, SP Stack kernels for 741 and 742 kernel versions have been updated. 741 PL#201 replaces 741 PL#200 and 742 PL#101 replaces 742 PL#100. New SP stack kernels can be now downloaded from SAP Support Portal, following fixes are included:

• Regression in the Oracle DBSL Library (Note 2118448, Point 2 - Termination during secondary database connection; LRAW length error) is removed.
• CommonCryptoLib has been updated to the version 8.4.35 (see Note 2134460.)

For more details on 741 PL#201 refer to Notes 2150081 - SAP Support Package Stack Kernel 7.41 Patch Level 201 and 2100429 - Known regressions in kernel 7.41 patch level 201.

Fixes and enhancements in the SP stack kernel 742 PL#101 are listed in the note 2145156. Information on known issues with this stack kernel can be found in the Note 2134238.

19.03.2015: Update on SP Stack Kernels 741 PL#200 and 742 PL#100

The latest SP stack kernels 741 (PL#200) and 742 (PL#100) contain a regression in the Oracle DBSL Library, see Note 2118448 -Termination during secondary database connection; LRAW length error, Point 2.

As a solution you may use the latest ORA lib_dbsl available on SAP Support portal. For kernel 741 on Windows, please be aware of the issue 2142073 - Application server in Windows NT with Oracle does not start.

Updated stack kernels will be provided as soon as possible.

11.03.2015: SP Stack Kernel 721 PL#402 Released

SP Stack kernel 721 PL #402 has been released and can be downloaded from SAP Support Portal. The issues from PL#400 (Note 2118382) and PL#401 (Note 2138260) are fixed.

Refer to Note 2138680 - SAP Support Package Stack Kernel 7.21 (EXT) Patch Level 402 for overview of new features, enhancements and improvements added since PL#300. Known regressions are documented in Note 2138678.

09.03.2015: SP Stack Kernel 742 PL#100 Released

SP stack kernel 742 PL #100 is now available on SAP Support Portal. It contains various improvements and enhancements that are outlined in detail in Note 2136550.

Information on known issues in the stack kernel 742 PL #100 can be found in Note 2129327. This note will be updated on regular basis.

04.03.2015: SP Stack Kernel 721 PL#401 Revoked

SP Stack kernel 721 PL #401 has been revoked from SAP Support Portal for all platforms except for MS Windows because the kernel archives contained some files with wrong versions.

In most cases it is not necessary to replace the kernel in a system running with PL#401 because the issue has a limited impact and does not affect the kernel itself. Details are outlined in Note 2138260.

SP stack kernel PL#402 will be released as soon as possible; this document will be updated accordingly.

06.02.2015: SP Stack Kernel 741 PL#200 Released

A new SP stack kernel 741 PL #200 has been released today and can be downloaded from SAP Support Portal.

For a summary of enhancements and improvements included into this stack kernel, see SAP Note 2101802 - SAP Support Package Stack Kernel 7.41 Patch Level 200.

30.01.2015: SP Stack Kernel 721 PL#401 Replaces PL#400

Current SP stack kernel 721 PL#400 has been replaced with PL#401, see Note 2121693 - SAP Support Package Stack Kernel 7.21 (EXT) Patch Level 401.

It fixes a file permission issue that has a very limited impact:

• It occurs with 721_EXT kernel on Windows platforms only
• It has no effect at runtime, only for future system maintenance
• Workaround is easy.

This means: even if above criteria apply, it is not always necessary to replace already installed 721 kernel PL#400. Refer to Note 2118382 for more information.

Note 2084437 contains the list of known regressions in the stack kernel 721 PL #401. This note will be continuously updated.

16.12.2014: SP Stack Kernel 721 PL#400 Released

A new SP stack kernel 721 PL #400 is now available on SAP Service Marketplace.

SAP Note 2101779 contains the list of changes and enhancements introduced in this stack kernel compared to the previous stack kernel PL #300.

All regressions known in the PL #300 have been fixed.

Review SAP Note 2084436 for known issues in the stack kernel 721 PL #400. This note will be continuously updated.

Hi All,

We are not able to bring up Netweaver app server after we mounted the installation on our new server. Can you help me here in identifying the root cause ?

Here is the output we got when we troubleshoot

sapeis-dev-01:nsdadm 79> /usr/sap/NSD/SCS01/exe/sapcontrol -nr 01 -function WaitforServiceStarted 120 10

FAIL: Timeout

sapeis-dev-01:nsdadm 80> /usr/sap/NSD/SCS01/exe/sapcontrol -nr 01 -debug -function Start

[Thr 140516277884704] Wed Apr 27 19:46:24 2016

[Thr 140516277884704] NiIInit: allocated nitab (2048 at 7fcc7c951010)

[Thr 140516277884704] NiIHSBufInit: initialize hostname buffer (IPv4)

[Thr 140516277884704] NiHLInit: alloc host buf (100 entries)

[Thr 140516277884704] NiSrvLInit: alloc serv bufs (100 entries)

[Thr 140516277884704] ***LOG Q0I=> NiPGetServByName: 'sapctrl01' not found: getaddrinfo [/bas/742_REL/src/base/ni/niuxi.c 1814]

[Thr 140516277884704] NiSrvLGetServNo: service name 'sapctrl01' not found by operating system

[Thr 140516277884704] NiInit3: NI already initializes (init=1;cur=2048)

[Thr 140516277884704] addrinfo of 'localhost':

[Thr 140516277884704] 0: 127.0.0.1:0 'localhost' RAW (2-2-3-0-16)

[Thr 140516277884704] 1: <unknown family 36496>:0 RAW (2-36496-3-0-16)

[Thr 140516277884704] *** ERROR => NiPGetHostByName: invalid family 36496 [niuxi.c      1943]

[Thr 140516277884704] *** ERROR => NiHLGetNodeAddr: NiPGetHostByName failed (rc=-1) [nixxhl.cpp   284]

[Thr 140516277884704] NiHLGetNodeAddr: hostname 'localhost' not found by operating system

27.04.2016 19:46:24

Start

FAIL: NIEHOST_UNKNOWN (Address family not supported by protocol), NiRawConnect failed in plugin_fopen(

Hi experts,

we try to export a NW 7.0 instance from oracle 11 db with R3load.

Environment information:

OS info:

   Nodename: <hostname>

   Release:   HP-UX B.11.31

   Version:   U (unlimited-user license)

   Machine:   ia64

DB info:

    Oracle 11.2.0.2

Software:

SWPM 1.0 SP 10 (actual version)

While starting the export of the NW stack in phase "Run migration monitor" the export stops and creates an dump.

sapinst_dev.log:

----------------------------------------------------------------------------------------

ERROR      2016-04-27 16:07:34.181 (root/sapinst) [CSiStepExecute.cpp:1106] id=controller.step

Executed errno=FCO-00011

The step runMigrationMonitor with step key |NW_Export|ind|ind|ind|ind|0|0|NW_ABAP_Export_Dialo

g|ind|ind|ind|ind|abapUnload|0|NW_ABAP_Export|ind|ind|ind|ind|0|0|runMigrationMonitor was exec

uted with status ERROR ( Last error reported by the step: Program 'Migration Monitor' exits wi

th error code 101. For details see log file(s) export_monitor.java.log, export_monitor.log.).

----------------------------------------------------------------------------------------

export_monitor.log:

----------------------------------------------------------------------------------------

ERROR: 2016-04-26 16:11:00 com.sap.inst.migmon.exp.ExportStandardTask run

Fatal exception during execution of the Export Monitor.

1. java.lang.OutOfMemoryError: Java heap space (failed to allocate 537002000 bytes) (max heap: 1024 MB)

        at java.lang.AbstractStringBuilder.expandCapacity(AbstractStringBuilder.java:145)

        at java.lang.AbstractStringBuilder.append(AbstractStringBuilder.java:619)

        at java.lang.StringBuffer.append(StringBuffer.java:340)

        at java.io.BufferedReader.readLine(BufferedReader.java:345)

        at java.io.BufferedReader.readLine(BufferedReader.java:362)

        at com.sap.inst.migmon.imp.StrFileUtils.findPredefinedTableNames(StrFileUtils.java:54)

        at com.sap.inst.migmon.MigrationTask.collectConversionPackageNames(MigrationTask.java:1206)

        at com.sap.inst.migmon.exp.ExportStandardTask.createPredefinedPackageGroups(ExportStandardTask.java:26

4)

        at com.sap.inst.migmon.exp.ExportTask.assignGroupPackages(ExportTask.java:255)

        at com.sap.inst.migmon.exp.ExportStandardTask.doRun(ExportStandardTask.java:101)

        at com.sap.inst.migmon.MigrationTask.run(MigrationTask.java:455)

        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)

        at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)

        at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)

        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPool

1. Executor.java:98)

        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoo

1. lExecutor.java:180)

        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecuto

1. r.java:204)

        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)

        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)

        at java.lang.Thread.run(Thread.java:763)

INFO: 2016-04-26 16:11:00

Export Monitor is stopped.

----------------------------------------------------------------------------------------

We already searched in the following SAP notes and tried the solutions without positive results :

• 1768708 - Error "java.lang.OutOfMemoryError: Java heap space" during the export
• 1420809 - Inst. with SAPinst: How to patch a control.xml file
• 1173398 - jload-Export schlägt mit OutOfMemory-Ausnahme fehl
• 2022386 - Migration nach HANA. Abbruch des Software Provisioning Managers beim Ausführen der HdbSlLib: java.lang.OutOfMemoryError: Java heap space
• 
  

The MIGMON.SAR file on SWPM 1.0 SP10 is modified on 16.04.2016. We also tried to replace the MIGMON.SAR file on the SWPM ISO. But all MIGMON.SAR files on service marketplace are older.

Also this did´t work.

Any suggestions?

Kind regards

Thorsten

Hi everybody,

we are using rfcping from a netweaver 7.00 version to check whether a registered rfc destination is available.

Example:

     rfcping type=E gwhost=sapgq1 gwserv=sapgw11 tpname=BIS.GTS6

This commandline is called via a monitoring system (Nagios) which is our central monitoring system for everything.

With a Netweaver 7.02 (ABAP/Linux) installation this works fine.

Now we upgraded the ABAP system to Netweaver 7.50 (Kernel 7.45).

The monitoring calls now do not work any more, result is:

RFC Call/Exception: SYSTEM_FAILURE

Group       Error group 104

Key         RFC_ERROR_SYSTEM_FAILURE

Message     Communication with non-ABAP RFC clients is not allowed. See SAP note 1877907 for details.

The referenced note 1877907 only talks about JCo usage which is not our case.

Does anyone know a solution to make the rfcping-call via a ABAP system started at the commandline?

Thanks for attention.

Thomas

Hello,

I have been doing quite a bit of research on this - there are similar discussions on SCN (This one: HTTP 400 - Session not found error | SCN, among others, but nothing that has actually helped me resolve my specific error).

I have an SRM SLC supplier portal that I am able to access through IE with no problems.

What I want to do is download a Supplier Qualification Response - a document generally in .docx format.

I go to Supplier List -> I select the Supplier Qualification Response -> I access the Response UI -> Then I click on the document I want to download ->

Here is where my error happens. Now, I have two machines. The trick is - when I do it on one machine I have no issues at all. When I do it on the second machine, I get the following error:

So I think the issue is Browser related. So I equalize the browser settings on the second machine as I have them on the first machine. NO SUCCESS. I still get the same issue.

I have the exact same Browser settings, and I also have the same SAP AG SSL certificates.

I have tried just about everything and running out of options. Please let me know if you have any suggestions, or if you have faced this issue and know how to troubleshoot it.

Thanks!

Kind regards,

Esteban

Hi ,

We had requirement to connect our Sap Ecc6 system which is on windows 2003 server need to integrate with External system mssqlserver 2012

we had already followed the notes as per smp. and configured accordingly but still facing issues. please find the logs below.

Fri Apr 29 23:58:04 2016

B  create_con (con_name=SSGDSN)

B  New connection 3 created

B  Connect to SSGDSN as SelectTimesheet with MSSQL_SERVER=172.2.254.254 MSSQL_DBNAME=Timesheet

C  Thread ID:8932

C  dbmssslib.dll patch info

C    patchlevel  0

C    patchno      350

C    patchcomment Work process can not be cancelled (1740162)

C  Network connection used from SAP-sid-sid to 172.2.254.254 using tcp:172.2.254.254

C

C Fri Apr 29 23:58:05 2016

C  OpenOledbConnection: line 24516. hr: 0x8000ffff Login failed for user 'SelectTimesheet'.

C  sloledb.cpp [OpenOledbConnection,line 24516]: Error/Message: (err 18456, sev 0), Login failed for user 'SelectTimesheet'.

C  Procname: [OpenOledbConnection - no proc]

C  sloledb.cpp [OpenOledbConnection,line 24516]: Error/Message: (err 0, sev 0), Invalid connection string attribute

C  Procname: [OpenOledbConnection - no proc]

C  failed to establish conn to tcp:172.1.254.254.

C  Retrying without protocol specifier: 172.1.254.254

C  OpenOledbConnection: line 24516. hr: 0x8000ffff Login failed for user 'SelectTimesheet'.

C  sloledb.cpp [OpenOledbConnection,line 24516]: Error/Message: (err 18456, sev 0), Login failed for user 'SelectTimesheet'.

C  Procname: [OpenOledbConnection - no proc]

C  sloledb.cpp [OpenOledbConnection,line 24516]: Error/Message: (err 0, sev 0), Invalid connection string attribute

C  Procname: [OpenOledbConnection - no proc]

C  failed to establish conn. 0

B  ***LOG BY2=> sql error -1        performing CON        [dbds#1 @ 1044] [dbds    1044 ]

B  ***LOG BY0=> Login failed for user 'SelectTimesheet'. [dbds#1 @ 1044] [dbds    1044 ]

B  ***LOG BY1=> sql error -1        [dbacds#2 @ 1433] [dbacds  1433 ]

Kindly do the needful asap.

Hi Friends,

We have requirement wherein we want to receive emails in SAP Inbox.

We have configured all the setting in SAP system as per note 455140 -

Configuration of e-mail and also did testing as per note 607108 and we

are able to receive emails in SAP Inbox.

But when email is sent from Mail server ( Microsoft exchange 2013) its

not coming in SAP inbox, as per note 455140 To be able to receive mails

in the SAP system, you need to set our mail server so that certain mail

addresses are forwarded to one or several SAP systems or clients. For

this purpose, you need to define routing rules that assign a mail host

and/or port to address areas (generic address parts, usually the

domain),

for example: *@crm-prod.company.com --> mySAPWASHost:25000

But we are having Microsoft exchange 2013 and not able to find the

option to give mySAPWASHost:25000, could you please guide us how to do this

on Microsoft exchange 2013 or any link or document in this regards would

be a great help.

Thanks

Tabrayz

Dear experts

i want media list for install ecc6 ehp4 ides on linux_86_64  for abap system and database should be of oracle

and supporting document for installation

Regards

Hello,

we plan to do a unicode-conversion.

System is DB2 on AIX.

In the guide from IBM regarding Copy-Optimization there is a info, that the socket-Option will bring a reduction of runtime.

But in Note 2311023 there is the hint, that it's not possible to use the socket-Option with unicode-conversion.

Does someone know, which info is correct ?

Dear SAP Basis Gurus and SAP Abap Gurus,

I am executing a sap report to create business partner in SAP CRM system. Now i have used parallel processing methodology in this report for business partner creation.

This report works fine with 80% of total dialogue processors in the system(quality/development/testing sap servers) used with multiple batch jobs in parallel (example if total dialogue processes in system is 100 then i schedule this report with 10 batch jobs and 8 dialogue processor per batch job).

But in production system we have 12 application servers with (150 dialogue processors, 20 update 1, 10 update 2 and 30 batch processes) per application server. So total resource is

dialogue processor : 1800

update 1: 240

update 2 : 120

batch jobs available: 360

Now i am scheduling the business partner creation report with 84 batch jobs and assigned 17 dialogue processor per batch job.

But only 7-8 jobs are remaining active after scheduling and updating the database creating customer and rest of the jobs are finished in 1 second without updating anything (note: there is nothing wrong with data creation as we write application log for error while data creation and nothing has come up in application log). Now i reprocesses the rest of the batch jobs which completed in 1 second earlier and didn't update, again 7-8 jobs are remaining active and creating business partner and rest of them are finished in 1 second and so on.

This report is working fine in other sap systems like quality/development/testing, and this problem is only happening in production.

I am not at all familiar with basis configurations, So kindly help me out with this issue.

Thanks for your help

Sudipto

Hi, I have problems while installing new license key on my NSP demo system. Is not the first time I've done it.

I have to logged in with SAP* because license has expired.

Go to transaction SLICENSE and, after requesting new license key, next error appears when trying to install it.

This system's system number is "000000000311048508", but there is a license key for system number "000000000311107510" in the license key file.

Does anyone how to proced in order to install it correctly?

Thanks.

Hello All,

   Yesterday we got an error while reconfiguring STMS. We were getting RFC_MODIFY_R3_DESTINATION error for TMS self RFC. Everything tried, like reconfiguring STMS with SAP_ALL user, assign SAP_ALL profile to TMSADM but nothing help. Finally we got solution “1730407 - Internal error in TMS communication 5”. In systems SAP note # 1640531 was applied but SAP note # 2132461 was not applied in any of the systems. So finally we applied SAP note # 2132461 in all affected systems and issue resolved.

So if you get similar issue please verify if SAP note # 1640531 is applied if yes then check for SAP note # 2132461.

Hi All,

We are not able to bring up Netweaver app server after we mounted the installation on our new server. Can you help me here in identifying the root cause ?

Here is the output we got when we troubleshoot

sapeis-dev-01:nsdadm 79> /usr/sap/NSD/SCS01/exe/sapcontrol -nr 01 -function WaitforServiceStarted 120 10

FAIL: Timeout

sapeis-dev-01:nsdadm 80> /usr/sap/NSD/SCS01/exe/sapcontrol -nr 01 -debug -function Start

[Thr 140516277884704] Wed Apr 27 19:46:24 2016

[Thr 140516277884704] NiIInit: allocated nitab (2048 at 7fcc7c951010)

[Thr 140516277884704] NiIHSBufInit: initialize hostname buffer (IPv4)

[Thr 140516277884704] NiHLInit: alloc host buf (100 entries)

[Thr 140516277884704] NiSrvLInit: alloc serv bufs (100 entries)

[Thr 140516277884704] ***LOG Q0I=> NiPGetServByName: 'sapctrl01' not found: getaddrinfo [/bas/742_REL/src/base/ni/niuxi.c 1814]

[Thr 140516277884704] NiSrvLGetServNo: service name 'sapctrl01' not found by operating system

[Thr 140516277884704] NiInit3: NI already initializes (init=1;cur=2048)

[Thr 140516277884704] addrinfo of 'localhost':

[Thr 140516277884704] 0: 127.0.0.1:0 'localhost' RAW (2-2-3-0-16)

[Thr 140516277884704] 1: <unknown family 36496>:0 RAW (2-36496-3-0-16)

[Thr 140516277884704] *** ERROR => NiPGetHostByName: invalid family 36496 [niuxi.c      1943]

[Thr 140516277884704] *** ERROR => NiHLGetNodeAddr: NiPGetHostByName failed (rc=-1) [nixxhl.cpp   284]

[Thr 140516277884704] NiHLGetNodeAddr: hostname 'localhost' not found by operating system

27.04.2016 19:46:24

Start

FAIL: NIEHOST_UNKNOWN (Address family not supported by protocol), NiRawConnect failed in plugin_fopen(

Hello experts,

I'm in trouble with SAP SLD on solution manager. The environment details and the error stack:

#72419 05/03/2016 08:07:20.450 [SAPEngine_Application_Thread[impl:3]_23] ERROR com.sap.lcr.cimsrv.CIMOMServlet: Service method terminated abnormally. An unexpected error occurred during execution of a client WBEM request.Thrown:com.sap.engine.services.servlets_jsp.server.exceptions.InvalidSessionException: Method [setAttribute()] is called in an invalid session.at com.sap.engine.services.servlets_jsp.server.runtime.client.ApplicationSession.setAttribute(ApplicationSession.java:756)at com.sap.lcr.cimsrv.changelog.CL_Query.getChangeLogEntriesUsingLookAhead(CL_Query.java:232)at com.sap.lcr.cimsrv.changelog.CL_Query.execute(CL_Query.java:187)at com.sap.lcr.cimsrv.CIMRequestExecutor.executeCurrentRequest(CIMRequestExecutor.java:374)at com.sap.lcr.cimsrv.CIMRequestExecutor.executeRequestMessage(CIMRequestExecutor.java:98)at com.sap.lcr.cimsrv.CIMOMServlet.processCimRequest(CIMOMServlet.java:456)at com.sap.lcr.cimsrv.CIMOMServlet.doPostOrMPost(CIMOMServlet.java:301)at com.sap.lcr.cimsrv.CIMOMServlet.doPost(CIMOMServlet.java:287)at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)at com.sap.lcr.cimsrv.CIMOMServlet.service(CIMOMServlet.java:216)at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1060)at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)at java.security.AccessController.doPrivileged(AccessController.java:219)at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)

Any idea about it?

Regards,

Gustavo

Hello gurus

I appreciate if you can chime in. So far all attempts from se11 se16 ended up with dumps when trying to get the number of records for CDPOS table.

Regards

Tansu

Today I am starting a new blog series, on sizing and load testing in a SAP Netweaver environment.

In this blog, I describe the reasons for the new series of posts, the landscape I will use as a scenario and the tools I will use.

Reasons

Since 2007, I work supporting ITS (Internet Transaction Server). I also worked with WDA (Web Dynpro ABAP) and, most recently, I started supporting SAP Screen Personas.

I had some opportunities to visit SAP customers that use ITS, WDA and Personas. In such visits, there was a concern about the correct sizing of the system, to cope the expected demand.

For ITS, I use the following SAP notes:

742048 - Integrated ITS, memory requirement in application server

1888428 - Sizing for SAP GUI for HTML

2233645 - ITS Memory Trace tool

I also use SAP note 1343331 (Integrated ITS: Scaling, optimization and load test).

For Web Dynpro ABAP, the following SAP notes are valid:

1612245 - Frontend Hardware Requirements for Browser-Based SAP UI

1933805 - Stable ID for automated test

For SAP Screen Personas, this Wiki page can be used.

Therefore, for sizing, the ground is pretty well covered. Put things in practice require several coffee cups.

However, what about load tests?

For ITS, I found one note: 651581 (Load testing ITS servers), which gives some tips if you face issues while doing the load testing. Nothing on how to test itself and the same applies to Web Dynpro ABAP and to Personas.

Thus, I decided to write about load testing, starting with ITS scenarios, moving to Personas and include some WDA applications at the end (counting on the help of a few WDA co-workers).

Landscape

I will start with a simple scenario: a supported web browser reaching a SAP system:

I will gather basic information about what to test (transaction, steps involved, elapsed time, etc.). Then I will add more complexity, bit by bit: first adding another application server, load balancing using the message server; then adding a SAP Web Dispatcher (WDP) to do the load balancing; and finally adding a Portal in front of the WDP.

Tools

It seems that load testing appeared a few times in our neighborhood. I found this blog interesting. For a more hands-on approach, this blog is perfect - it shows the load testing with Web Dynpro ABAP applications.

I decided to go with the same flow and use Apache JMeter as the tool to perform my load tests.

I will use other tools to analyze the information from the tests.

More Information

Even though you can find plenty on Apache JMeter, I think a good book is also a good companion. To cover the basics, you might want to have Apache JMeter, from Emily H. Halili.

Stay tuned for my next blog on sizing & load tests.

Hello,

We are facing the error "could not read digitally signed licenses" while executing tcode - slicense on one of our app server.

Have checked the trace files dev_w* for corresponding error messages with search term "likey" but could not find any error.

Now the system is fine and the slicense tcode shows the license details without any error.

Note:- we have not made any changes later

Checked the profile parameters sec/libsapsecu and ssf/ssfapi_lib and they are fine

Regards,

Jitendhar

Dear Experts,

I am installing SAP Netweaver AS JAVA,

followed the installation instructions, but at PHASE No: 8, when installation asks for database installation i am facing following errors.

Error:

Logs:

. 11ginstall.sh - Oracle Database 11.2 Software Installation Script

. Version 11.2.0.4.0 Release Date 2013-09-23 Patch Level 043 (rel)

. Copyright (c) Oracle Corporation 2010, 2011. All Rights Reserved.

. SAP note 1524205

. Oracle Database Release: 11.2.0.4.0

.

. Host     : TMC-Javastack

. Platform : linux_x86_64 (64-bit)

. Date     : 2016_05_04 01:02:26

. User     : oratmj

. Log dir. : /home/oratmj

. Logfile  : /home/oratmj/11ginstall_11204.log

.

. 11ginstall.sh was called with the following options (command line):

. -caller RUNINSTALLER -oracle_stage /oracle/stage/112_64/database -ignoreSysPrereqs

.

. Performing pre-installation checks ...

.

. (OK)      -  Environment variable <DB_SID> is set to TMJ

. (OK)      -  Got value for <DB_SID> from environment.

. (OK)      -  Got location for Oracle base from environment.

. (OK)      -  Got location for Oracle stage from '-oracle_stage' option.

. (WARNING) -  Base directory for runtime Oracle home /oracle/TMJ does not exist.

. (OK)      -  Oracle base location /oracle exists.

. (OK)      -  Installation location /oracle/TMJ/11204 does not exist.

. (OK)      -  Runtime location /oracle/TMJ/112_64 does not exist.

. (WARNING) -  Inventory pointer file oraInst.loc is missing. You are starting your first installation on this host.

. (OK)      -  Group dba is defined.

. (OK)      -  Group oper is defined.

. (OK)      -  OUI version in stage is 11.2.0.4.0.

. (OK)      -  New response file /home/oratmj/.11ginstall_11204.rsp created.

. (INFO)    -  OUI command line option -ignoreSysPrereqs is used.

.

. Pre-installation checks completed.

.

.

. Environment settings:

.

. DB_SID                       = TMJ

. DISPLAY                      = 192.168.106.84:0.0

. ORACLE_BASE                  = /oracle

. ORACLE_STAGE                 = not set

.

. Installation Settings:

.

. Installation log file        = /home/oratmj/11ginstall_11204.log

. Oracle Release               = 11.2.0.4.0

. Oracle stage location        = /oracle/stage/112_64/database

.

. Oracle base location         = /oracle (exists)

. Oracle home install. location= /oracle/TMJ/11204 ( not existing / / not shared )

. Oracle home runtime  location= /oracle/TMJ/112_64 ( not existing / not installed )

. Inventory group              = dba

. SYSDBA    group              = dba

. SYSOPER   group              = oper

.

. OUI Settings:

.

. OUI version                  = 11.2.0.4.0

. OUI temporary directory      = /home/oratmj/.11ginstall_11204.tmp

. OUI response file            = /home/oratmj/.11ginstall_11204.rsp

. OUI output log file          = /home/oratmj/.11ginstall_11204.oui

. OUI options                  = -waitForCompletion -ignoreSysPrereqs

. OUI inventory location       = INVENTORY_LOCATION=/oracle/oraInventory

.

. Post Installation Settings:

.

. Create symbolic link         = yes - relative path

. Install MOPatch              = yes

. Clean up temp. files         = yes

.

. OUI command line:

.

. LANG=C TMP=/home/oratmj/.11ginstall_11204.tmp /oracle/stage/112_64/database/runInstaller -responseFile /home/oratmj/.11ginstall_11204.rsp -waitForCompletion -ignoreSysPrereqs | tee /home/oratmj/.11ginstall_11204.oui

.

.

. OUI response file:

. /home/oratmj/.11ginstall_11204.rsp

.

###############################################################################

## Copyright (c) Oracle Corporation 2010, 2011. All Rights Reserved.

##

## Generated by 11ginstall.sh - Oracle Database 11.2 Software Installation Script

## Version 11.2.0.4.0 Release Date 2013-09-23 Patch Level 043

##

## SAP note 1524205

## Oracle Database Release: 11.2.0.4.0

## Platform: linux_x86_64

## Date    : 2016_05_04 01:02:26

###############################################################################

oracle.install.responseFileVersion=/oracle/install/rspfmt_dbinstall_response_schema_v11_2_0

oracle.install.option=INSTALL_DB_SWONLY

ORACLE_HOSTNAME=TMC-Javastack

UNIX_GROUP_NAME=dba

SELECTED_LANGUAGES=en

ORACLE_HOME=/oracle/TMJ/11204

ORACLE_BASE=/oracle

oracle.install.db.InstallEdition=EE

oracle.install.db.EEOptionsSelection=true

oracle.install.db.optionalComponents=oracle.rdbms.partitioning:11.2.0.2.0,oracle.rdbms.rat:11.2.0.2.0

oracle.install.db.DBA_GROUP=dba

oracle.install.db.OPER_GROUP=oper

oracle.install.db.isRACOneInstall=false

SECURITY_UPDATES_VIA_MYORACLESUPPORT=false

DECLINE_SECURITY_UPDATES=true

oracle.installer.autoupdates.option=SKIP_UPDATES

INVENTORY_LOCATION=/oracle/oraInventory

.

. (INFO)    -  Starting Oracle Universal Installer in interactive mode - please wait ...

.

.

. (INFO)    -  Oracle Universal Installer finished.

. (INFO)    -  Name of OUI session log file not found.

.

. OUI output:

Starting Oracle Universal Installer...

Checking Temp space: must be greater than 120 MB.   Actual 227427 MB    Passed

Checking swap space: must be greater than 150 MB.   Actual 16385 MB    Passed

Checking monitor: must be configured to display at least 256 colors

    >>> Could not execute auto check for display colors using command /usr/bin/xdpyinfo. Check if the DISPLAY variable is set.    Failed <<<<

>>> Ignoring required pre-requisite failures. Continuing...

Preparing to launch Oracle Universal Installer from /home/oratmj/.11ginstall_11204.tmp/OraInstall2016-05-04_01-02-26AM. Please wait ....

.

. Performing clean up tasks ...

. Clean up tasks completed.

.

. Post-installation tasks are not executed.

. Reason: error during installation

. Post-installation tasks have been skipped.

.

. Installation Results

. (ERROR)   -  Oracle Database software installation finished with errors.

. The Oracle executable /oracle/TMJ/11204/bin/oracle is empty or does not exist.

. Possible cause(s): link error, installation was cancelled or interrupted, or fatal error.

. (INFO)    -  You can find the installation summary log at /home/oratmj/11ginstall_11204.log

. (EXIT)    -  Exiting with exit code 2.

From SCN Post i had created

/oracle/<SID>/11204 manually as ora<sid>

Then do the following as user ora<sid>

mkdir /oracle/<SID>/11204/dbs

mkdir /oracle/<SID>/11204/network

mkdir /oracle/<SID>/11204/network/admin

But could not resolve the Issue.

Please help me in this issue, as i have to delier my porject in next two days.

Regards,

John

Good day

We are looking to implement ESS\MSS on NetWeaver 7.5. We installed SAP NetWeaver 7.5 AS Java, deployed ESS 633, MSS 630, PCUI_GP 633. but when we wanted to patch the system, Mopz complained about not being able to recognise this components. please see attached images. Even synchronization has warning in LMBD.

I tried to read up on NetWeaver 7.5 and XSS, but there not a lot of information available. Does anyone have some infor for me. more specifically what to deploy.

https://wiki.scn.sap.com/wiki/display/ERPHCM/How+to+determine+the+correct+component+combination+in+ESS+WD+JAVA

the link above says you can choose not to deploy anything and use Web Dynpro ABAP (WDA). Any information about the role to import from backend and use it in Portal

thanks in advance

regards

Steven