Hi guys,

while trying to install the SSL Certificate to the SAP Web Dispatcher  through CMD I am getting an import Error Installation

"import_own_cert: Installation of certificate failed"

I checked the expiration certificate and it's good to go.

Thanks in advance.

Kaushik G

Hi experts:

I am doing system copy through export / import copy through SWPM , While importing java migration tool phase giving me java error.

Hostname same from Source System so I can't take in current LAN of target server  , Hence I install a loop-back adapter.

Kindly check and resolve.

Kind Regards,

N S Rathore

Hi gurus,

Im trying to migrate SAP ERP EHP7 from MaxDB to DB2 database and while import ABAP phase I received error, that migration key is wrong. I was generating key via OSS, but it is always wrong. In log file I see something weird:

process id 3722

(DB) INFO: connected to DB

(GSI) INFO: dbname   = "NAO                                                                                                                             "

(GSI) INFO: vname    = "DB6                             "

(GSI) INFO: hostname = "UNKNOWN                                                         "

(GSI) INFO: sysname  = "Linux"

(GSI) INFO: nodename = "bpx-nao"

(GSI) INFO: release  = "3.0.13-0.27-default"

(GSI) INFO: version  = "#1 SMP Wed Feb 15 13:33:49 UTC 2012 (d73692b)"

(GSI) INFO: machine  = "x86_64"

(VK)  INFO: installation number = "0000000000"

(VK) ERROR: invalid migration key

/usr/sap/NAO/SYS/exe/uc/linuxx86_64/R3load: job finished with 1 error(s)

/usr/sap/NAO/SYS/exe/uc/linuxx86_64/R3load: END OF LOG: 20140825185045

I think that this is the problem, how can I solve it?

Thanks in advance

Hello Colleagues,

I have a requirement of migrating SAP Netweaver 7.0 system from Windows 2003 to 2008 R2 .

Source System Details :

Even though it will support backup restore as a homogeneous migration , but to carry all netweaver settings well we are planning to proceed with EXPORT IMPORT with SWPM . As per note 789220 , SAP netweaver 7.0 SR3 contains following component:

SAP NetWeaver 7.0 Support Release 3

===================================

SAP_BASIS                      700              0014

SAP_ABA                        700               0014

SAP_BW                         700               0016

PI_BASIS                       2005_1_700    0014

We can see difference in SP level in both the cases , so will it be OK if I export & import the system by choosing SAP Netweaver 7.0 Support Release 3 -> system copy (available in 70SWPM SL Toolset) ?

Will it automatically update the SAP_BASIS, SAP_ABA etc components , once after importing the EXPORT in target system even though I select "SAP Netweaver 7.0 Support Release 3" option ?

Kindly help !!

Regards,

Nilutpal Sharmah

Is it possible to mass import TRs with import single strategy? We have a ChaRM track and a project system which isn't part of it. The problem is that we have to use import single strategy, so we can't plan a job for periodical mass import.

I am trying to install TREX instance on existing SAP ABAP host. But i get error that SID already exists. My question is:

1. How can i select existing SID with different instance number?

Thanks

Vik

Hi All,

I configured biller direct on net weaver system  while connecting biller direct it is showing error. Below is the log file

Java exception "java.lang.NullPointerException: while trying to invoke the method com.sap.fin.webbase.context.ExecutionContext.getOptions() of an object returned from com.sap.fin.webbase.context.ECUtil.getCurrentExecutionContext()" has occurred; Check the trace file for location "com.sap.fin.webbase.taglib.LogExceptionTag". See also SAP Note 786367.
[EXCEPTION]
java.lang.NullPointerException: while trying to invoke the method com.sap.fin.webbase.context.ExecutionContext.getOptions() of an object returned from com.sap.fin.webbase.context.ECUtil.getCurrentExecutionContext()
at com.sap.fin.ebpp.global.ContextUtil.getDefaultBORObjectType(ContextUtil.java:133)
at JEE_jsp_public__frameset_5f_top_5f_html_842797150_1415280478000_1415340849103._jspService(JEE_jsp_public__frameset_5f_top_5f_html_842797150_1415280478000_1415340849103.java:96)
at com.sap.engine.services.servlets_jsp.lib.jspruntime.JspBase.service(JspBase.java:102)
at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:152)
at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:428)
at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:147)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:202)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:103)
at com.sap.xsrf.filter.XSRFProtectorFilter.doFilter(XSRFProtectorFilter.java:62)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:79)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:432)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:210)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:441)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:430)
at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:38)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:81)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:276)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:81)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.SessionSizeFilter.process(SessionSizeFilter.java:26)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:57)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:43)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:475)
at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:269)
at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:56)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)

Can any one help on this.

Thanks,

Narendar.

We are doing a SystemCopy here for a Portal NW7.01 SP14 system.

The point is that we will change the Hostname and also there will be a Operational System Upgrade from W2k3-SQL2k5 to W2k8R2-SQL2k8R2.

We are confortable with the OS thing. Thats Ok!
(But if you guys have any issue regarding it, it's welcome here!)

1. What are the attention points on Hostname Change for the Portal?

Regarding the connections:

2. From Portal to external system, do you guys know any issue?

3. From external systems to Portal, what are the strategies to get it working after a hostname change? How to figure the external connections from outside?

Regards,

Gabriel

Hi,

First of all I would like to begin by saying that I am new to the world of SAP NW I come from traditional understanding of SAP R/3 and ECC versions, BUT, nothing about NW.

So i know that SAP NW is for HCM, SCM and CRM and such.

And ECC 6.0 is for the traditional modules like FICO, PM and such

So my question is this. Currently I have a IDES ECC 6.0 ehp4 on windows2008r2 and it is running fine. Oh, btw it is running on ABAP stack, below image might be more descriptive this is using Oracle DB btw

So i want to install SAP NW 7.4 using Oracle, so was wondering can i install on the same Virtual Machine as my IDES ECC 6.0? or have to be on a spearate machine? Tks

So am I right to say that this NW 7.4 can run on its own with out having a ECC 6.0 system? Cause what I am thinking is that lets say HR module is already present in the ECC version and HCM is part of NW buisness suite, so the data of HR have to be used for HCM (this might be really a silly question but sorry I am more of a HW and then slowly progressed to SAP Basis guy)

I also know that it is possible to have dual-stack, but this has been continued from NW 7.4, except for PI, so what does that mean?

We are doing a System copy here as follows:

System Source (A), a physical system with EP running on it.

System Target (B), a virtual machine on vSphere tech.

1. The migration has a upgrade of the Operational System and SQL (Win 2003 SQL2005 to Win 2008R2 SQL 2008 R2). That's OK, this is a Homogeneous systemcopy, we are confortable with it.

2. The A and B system must coexist, the strategy is that, the B system will be created with BHostName, we are going get this machine on domain, log with the A System SIDADM to get all the user parameters THEN we will remove it to another vlan in order to change the BHostName to AHostName and the we will follow the Import migration process.

The point is: When executing the systemcopy, the interface asks if the user is Local or from Domain, at this point what is your advise?

What should I care of?

If I say to use the Local Domain, what problems I would have to face when I take this system to the Domain?

If I say to use another domain and insert the domain "domain.corp", will the systemcopy check if the user really exist on the domaing? What I regard here is if the systemcopy will check inside the domain, since the system will be out of domain until the "Go-Live".

Best regards,

Gabriel

hi

does anybody have the same problem with installation of latest version netweaver 70.02 32bit version on win XP,i tried to install but i gor the message-condition not met,if you are running win xp 32 you have to stop the installation blabla bla

but under system requirements it schould be compatible with win XP as well

.

there is a attachement file below

can anybody help?

Dear consultants,

Need guidence...

I am with SAP BW on windows 08-ms cluster and sql server..is having enque server replication disabled issue while checking post install verification check -

command as per Inst. guide -

ensmon pf=
SGSGSAV0S0057\sapmnt\BPA\SYS\profile\BPA_ERS43_SGSGSAV0S0039 2

Getting message -

C:\Users\sapinstall\Desktop\ers_test>ensmon pf=
SGSGSAV0S0057\sapmnt\BPA\SYS\pr

ofile\BPA_ERS43_SGSGSAV0S0039 2

Try to connect to host sgsgsav0s0057 service sapdp42

get replinfo request executed successfully

Replication is disabled in server!

============================================================

Verified all parameters with other prodcuts installtion....Its enable in SRM,CRM,PI,ECC etc.

Thanks in advance for help!

Hello,

I don't want to use HTTPS because it is only an internal test Server. At the Logon Screen there is a message, that there was no switching to HTTPS.

Is there are possibility to disable this message?

(You can see a screenshot below.)

Thanks and Regards,

Simon

Dear Experts,

This is the first time I am configuring SAP WEB DISPATCHER, i followed some docs and reviewed lot of blogs, still something is missing.

http is working fine

I am trying to configure SSL Termination or SSL re-encryption to ECC Abap server from stand alone sap web dispatcher

Created sap web dispatcher profile, created parameters

created pse files

generated pse files with CA

created sec login for service user

I am pasting the logs of dev_webdisp, Please help me to resolve this.

not able to activate https port, its giving the error, all the errors are shown below.

[Thr 1276] Mon Jun 01 12:25:17 2015

[Thr 1276] started security log to file ./dev_icm_sec

[Thr 1276] SAP Web Dispatcher running on: AMBRISAPWD-D

[Thr 1276] MtxInit: 30001 0 2

[Thr 1276] ***LOG IM1=> IcmInit, Startup (SAP Web Dispatcher&AMBRISAPWD-D&3372&) [icxxman.c    2085]

[Thr 1276] IcmInit: listening to admin port: 65000

[Thr 1276] MPI: dynamic quotas disabled.

[Thr 1276] MPI init: pipes=4000 buffers=1279 reserved=383 quota=10%

[Thr 1276] CCMS: SemInMgt: Semaphore Management initialized by AlAttachShm_Ext.

[Thr 1276] CCMS: SemInit: Semaphore 38 initialized by AlAttachShm_Ext.

[Thr 1276] IcrIAddSingleSystem: Added backend system: SID=000, MSHOST=bid, MSPORT=8100, MSSPORT=44300, SRCURL=/, SSL_ENCRYPT=0, SSL_IGNORE_HOST_MISMATCH=false

[Thr 1276] IcrCoreInitSessionTable: Session table initialized

[Thr 3036] Adding HttpAdminHandler: PREFIX=/sap/admin,DOCROOT=D:\usr\sap\BWS\W00\data\icmandir,AUTHFILE=D:\usr\sap\BWS\SYS\global\security\data\icmauth.txt,PORT=8100

[Thr 3036] HttpExtractArchive: files from archive D:\usr\sap\BWS\SYS\exe\nuc\NTAMD64/wdispadmin.SAR in directory D:/usr/sap/BWS/W00/data/icmandir are up to date

[Thr 3036] HttpAdmHandlerInit: admin restricted to the port(s): 8100

[Thr 3036] HttpISubHandlerAdd: Added handler HttpAdminHandler(0000000003CE7520), slot=0, flags=45061) for /sap/admin, active: 1, table 000000001089AA20

[Thr 3036] Adding HttpModHandler: PREFIX=/

[Thr 3036] CsiInit(): Initializing the Content Scan Interface

[Thr 3036]            PC with Windows NT (mt,ascii,SAP_CHAR/size_t/void* = 8/64/64)

[Thr 3036] CsiInit(): CSA_LIB = "D:\usr\sap\BWS\SYS\exe\nuc\NTAMD64\sapcsa.dll"

[Thr 3036] HttpISubHandlerAdd: Added handler HttpModHandler(0000000003CE7480), slot=1, flags=12293) for /, active: 1, table 000000001089AA20

[Thr 3036] Adding HttpAuthHandler: PREFIX=/,FILTER=SAP

[Thr 3036] HttpISubHandlerAdd: Added handler HttpAuthHandler(0000000003CFAD40), slot=2, flags=12293) for /, active: 1, table 000000001089AA20

[Thr 3036] HttpISubHandlerAdd: Added handler HttpWebDispHandler(0000000003D08BD0), slot=3, flags=1060869) for /, active: 1, table 000000001089AA20

[Thr 3036] WebSocketPlugInInit: WebSocket Plugin initialized

[Thr 3036] IcmAddHiddenService: Hidden service WEBSOCKET started

[Thr 3036] Started service HOST=AMBRISAPWD-D,PORT=8100,PROT=HTTP,TIMEOUT=60,PROCTIMEOUT=60

[Thr 3036] IcmAddHiddenService: Hidden service WEBSOCKETS started

[Thr 3036] =================================================

[Thr 3036] = SSL Initialization    platform tag=(ntamd64-msc16)

[Thr 3036] =   (742_REL,May 22 2015,mt,ascii,SAP_UC/size_t/void* = 8/64/64)

[Thr 3036]   DIR_INSTANCE="D:\usr\sap\BWS\W00"

[Thr 3036]   DIR_LIBRARY="D:\usr\sap\BWS\SYS\exe\nuc\NTAMD64"

[Thr 3036] Mon Jun 01 12:25:18 2015

[Thr 3036]   ssl/ssl_lib="D:\usr\sap\BWS\SYS\exe\nuc\NTAMD64\sapcrypto.dll"

[Thr 3036]   profile param "ssl/ssl_lib" = "D:\usr\sap\BWS\SYS\exe\nuc\NTAMD64\sapcrypto.dll"

[Thr 3036]            resulting Filename = "D:\usr\sap\BWS\SYS\exe\nuc\NTAMD64\sapcrypto.dll"

[Thr 3036] =   found CommonCryptoLib (SAPCRYPTOLIB) Version 8.4.37 pl40 (May 12 2015) MT-safe

[Thr 3036] =   current UserID: AMBRISAPWD-D\SAPServiceBWS

[Thr 3036] =   found SECUDIR environment variable

[Thr 3036] =   using SECUDIR=D:\usr\sap\BWS\W00\sec

[Thr 3036]   ssl/ciphersuites="HIGH:MEDIUM:+e3DES:!aNULL"

[Thr 3036]   ssl/client_ciphersuites="HIGH:MEDIUM:+e3DES:!aNULL"

[Thr 3036] *** ERROR =>   secussl_Create_SSL_CTX():  PSE "D:\usr\sap\BWS\W00\sec\SAPSSLS.pse": unable to use! [ssslsecu.c   2395]

[Thr 3036] No LastError / ErrorStack available!

[Thr 3036] *** ERROR => SapISSLAddCredential(): Error SSSLERR_PSE_ERROR trying to create SERVER Credential

        for "D:\usr\sap\BWS\W00\sec\SAPSSLS.pse" [ssslxxi.c    2805]

[Thr 3036] *** ERROR => Initialization of SSL library failed -- NO SSL available!

[Thr 3036] =================================================

[Thr 3036]

[Thr 3036] <<- ERROR: SapSSLInit(read_profile=1)==SSSLERR_PSE_ERROR

[Thr 3036] = SSL Server PSE (SAPSSLS.pse) created with DN=(CN=AMBRISAPWD-D), rc=(5)

[Thr 3036] *** WARNING => IcmServInitSSL: Creation of default PSE files failed: (rc=-40) [icxxserv.c   378]

[Thr 3036] =================================================

[Thr 3036] = SSL Initialization    platform tag=(ntamd64-msc16)

[Thr 3036] =   (742_REL,May 22 2015,mt,ascii,SAP_UC/size_t/void* = 8/64/64)

[Thr 3036]   DIR_INSTANCE="D:\usr\sap\BWS\W00"

[Thr 3036]   DIR_LIBRARY="D:\usr\sap\BWS\SYS\exe\nuc\NTAMD64"

[Thr 3036] =   found CommonCryptoLib (SAPCRYPTOLIB) Version 8.4.37 pl40 (May 12 2015) MT-safe

[Thr 3036] =   current UserID: AMBRISAPWD-D\SAPServiceBWS

[Thr 3036] =   found SECUDIR environment variable

[Thr 3036] =   using SECUDIR=D:\usr\sap\BWS\W00\sec

[Thr 3036]   ssl/ciphersuites="HIGH:MEDIUM:+e3DES:!aNULL"

[Thr 3036]   ssl/client_ciphersuites="HIGH:MEDIUM:+e3DES:!aNULL"

[Thr 3036] *** ERROR =>   secussl_Create_SSL_CTX():  PSE "D:\usr\sap\BWS\W00\sec\SAPSSLS.pse": unable to use! [ssslsecu.c   2395]

[Thr 3036] No LastError / ErrorStack available!

[Thr 3036] *** ERROR => SapISSLAddCredential(): Error SSSLERR_PSE_ERROR trying to create SERVER Credential

        for "D:\usr\sap\BWS\W00\sec\SAPSSLS.pse" [ssslxxi.c    2805]

[Thr 3036] *** ERROR => Initialization of SSL library failed -- NO SSL available!

[Thr 3036] =================================================

[Thr 3036]

[Thr 3036] <<- ERROR: SapSSLInit(read_profile=1)==SSSLERR_PSE_ERROR

[Thr 3036] *** ERROR => IcmServInitSSL: SapSSLInit (rc=-40): SSSLERR_PSE_ERROR [icxxserv.c   390]

[Thr 3036] *** WARNING => IcmAddService: Could not start service (rc=-14) HOST=AMBRISAPWD-D,PORT=44300,PROT=HTTPS,TIMEOUT=60,PROCTIMEOUT=60,VCLIENT=1 [icxxserv.c   1034]

[Thr 1276] IcmCreateWorkerThreads: created worker thread 0

[Thr 1276] IcmCreateWorkerThreads: created worker thread 1

[Thr 1276] IcmCreateWorkerThreads: created worker thread 2

[Thr 1276] IcmCreateWorkerThreads: created worker thread 3

[Thr 1276] IcmCreateWorkerThreads: created worker thread 4

[Thr 1276] Mon Jun 01 12:25:18 2015

[Thr 1276] IcmCreateWorkerThreads: created worker thread 5

[Thr 1276] IcmCreateWorkerThreads: created worker thread 6

[Thr 1276] IcmCreateWorkerThreads: created worker thread 7

[Thr 1276] IcmCreateWorkerThreads: created worker thread 8

[Thr 1276] IcmCreateWorkerThreads: created worker thread 9

[Thr 4720] IcmWatchDogThread: watchdog started

Regards,

Surya

Hi,

     Is it possible to take Online Backup in application level for every 1 hours. If so, Please explain the steps?

Regards

Gopinath G

Hi,

    I want to configure two Landscape in SAP Bais. Like SAP Hana, SAP HR?

How to do it. Please give in Step by Step.?

Regards

Gopinath G

Use of Additional Hosts during Export

Why we need Additional Host? How does it help?

Especially for the migration to SAP HANA, it has become common to use an SAP HANA standby server for the import into the database instance. As SAP HANA servers are very powerful, the import is delayed because it has to wait for the relatively slow data delivery from the export. To increase the performance of the export you can use more than one SAP application server of the source system for the export. For example, you can use the hosts of the existing additional application server instances of the source system.

You can do this by choosing Database Instance Export on Additional Host in the SWPM installer.

With this option you can distribute the packages (to be exported) among the Central Instance and Dialog Instances of Source Host. An important Note that this option is only valid with Target DB as HANA.

Process Flow of Export:-

When performing the export you create a MIGRATION EXPORT image, which contains the data of the exported system, and which you use to install the target system.

The following figure shows the export options and the resulting output files.

Options To Be Selected On the HOSTS:-

The following options are selected on the Hosts and the screens that follow up after that need to be handled accordingly.

   1) Running SWPM on Central Instance Host:-

Select Database Instance Export on Source System (Central Instance Host)

In the below mentioned screen Select “Use Additional Hosts”

In the next Screen Hostnames of Central Instances and Dialog Instances are mentioned. Make sure the Checkbox of “Use this Host” is marked for the Host on which SWPM is currently running.

The below screen mentions the Filename “package_filter_%hostname%.txt” which is generated by SWPM automatically (based on Size or Runtime) under the Export Installation Directory and Export Dump Directory (/<Export-DUMP>/ABAP/DB/HDB)

Once the below stage has been reached the Package Filter files are automatically created at the Export Installation Directory and Export Dump Directory by SWPM.

The following files are created in the Installation Directory and Export Dump Directory:-

• package_splitter_cmd.properties
• package_filter_visual_%hostname%:-Mentions the size of various packages/table/table_splits to be executed via a particular “hostname”.
• package_filter_%hostname%:- Mentions the name of packages/table/table_splits to be executed via a particular “hostname”.
• package_filter_files

Contents of package_filter_visual_%hostname%:-

Contents of package_filter_%hostname%

In case you want to change the list of Package Distribution to some Custom List then replace the package_filter_%hostname% file under
Export Installation and Export Dump Directory with your Custom List at the below mentioned stage:-

2) Running SWPM on Additional Host (Dialog Instance):-

Select Database Instance Export on Source System (Additional Host). Once the offloading of packages has started on the Central Instance Host SWPM has to be triggered on the Additional Hosts and the following Option is selected.

The Package Filter file for that particular Host is selected and SWPM is continued from there. The packages mentioned in the Package Filter file will occupy the resources only of that particular host.

Hello, everybody.

Standart TCP/IP connection named "MDX Parser" doesn't work. It says "timeout during allocate / CPIC-CALL: 'ThSAPCMRCV' : cmRc=20 thRc=456 Timeout dur".

When I try to run mdxsvr in command line it says that librfc32.dll could not be found.

And there is no such dll in the directory with mdxsvr, but there is a librfc32u.dll.

How can I solve this problem?

P.S.

My server parameters:

- IA64

- Windows 2003

- SAP NetWeaver 2004s

--

best regards,

Dmitry

Everybody, who knows about In-memory databases (like SAP HANA DB), is aware about their enormous speed and throughput one can achieve from In-memory database engine. If I say only about SAP HANA in-memory database engine, it can process data 3600 times faster than any traditional RDBMS.

As a proof point it has been tested than HANA in-memory engine can process as maximum as 460 billion data line item in a second.(This is equivalent to calculating amount of taxes paid by everyone on this planet, since 1950, in one second.)

Looking at these proof points, C.I.O. or IT manager of any organization would definitely wish to switch from their traditional RDBMS to SAP HANA in-memory database, to add a significant value proposition to their business from technical standpoint.

Only point, that might bring saturnine expression on the face of an IT manager or technical administrator, is the BUSINESS DOWNTIME they may need to migrate their existing SAP solution to HANA database.

Now, speaking a bit more technically, complete migration cycle comprises of two main processes,

1. ) Exporting Source Database and 2.) Import into target HANA database

As target is an in-memory database, so processing time for import is a lot smaller than of what exporting source system would take. So here, I would put more emphasis on improving export time on source system.

There are many already proven ways, in which SWPM tool of SAP can improve on export process timings.

To have a quick look at those traditional ways:

1. ) Performing table splitting on source system
2. ) Doing export package splitting
3. ) Updating database statistics
4. ) Cleaning un-wanted monitoring logs, temp tables beforehand
5. ) Leveraging R3load parallel processing

Along with these traditional ways, migration to HANA can be optimized further by using another option “using additional hosts for export” that is available when you choose to export source system towards HANA DB as target in SWPM tool.

How it would effect positively:-

1. ) Any available additional application server can be used for export along with central system
2. ) Packages can be distributed to all available hosts for export
3. ) We can further sort packages and decides number of R3load processes for larger and small packages differently
4. ) Export sorting can be done By SIZE, By TIME (taken in previous system export or dry run), By Name or By any manually customized export sequence
5. ) A common export directory is mounted across all available hosts, so final export dumps files always remain intact
6. ) Export Logs are stored in installation directory on different location (like .../EXP directory for CI & in .../EXP-FILTER directory for additional host), so error analysis & issue handling of packages running on each host is easy

Using this you can reduce total export time by significant amount.

For example, say SWPM tool is taking 12hours to export 2Terbytes of your source database from a single Central Instance, then using another application instance host of similar configuration, would help to reduce this to half of it i.e. to 6hours. Adding more hosts & distributing packages evenly across all hosts, would contribute by equal proportion in reducing overall export time.

Therefore, if you are planning to move your existing SAP solution to HANA, the use of this option would definitely make a great contribution to reduce overall HANA migration timings.

If you are interested in knowing more technically or step-by-step procedure, you can check following technical document on SCN. http://scn.sap.com/docs/DOC-64433

Remember that proper preparation is always the key point that would decide your success or time taken to achieve that success.

Applies to

Migration / Support / Upgrade project where installation number is changed from source to target system

Summary

The objective of this document is to explain the steps required to be taken in order to migrate secstore data, which is required in case installation number of system is changed.

Purpose

The installation number is part of the system-dependent data with which the key is generated. If your installation number changes, the data created with the previous installation number can no longer be read.

It is possible for the installation number to change even in a system used productively. This is accompanied by the importing of a new license (however, not every importing of a new license means the changing of the installation number).

To be able to continue working with existing entries in the secure storage in a case like this, you receive a release key from SAP together with the new license (if this will change the installation number). You can use this to migrate the entries in the secure storage. The migration key is not a skeleton key. It only releases the conversion of data from another installation number to your current installation number.

We assign the release key only if the installation number of a production system changes. You cannot request the release key for other situations (test systems, transporting database entries between systems).

Overview

The secure storage is a component of the SAP Web Application Server ABAP. It allows the encrypted storage of sensitive data that SAP applications require when logging on to other systems.

The encrypted storage of the data in the database prevents unauthorized persons or programs being able to access this data.

Integration

The following SAP applications use the secure storage to store passwords:

• RFC destinations
• Exchange Infrastructure (XI)
• LDAP system users
• SAPphone
• SAPconnect
• CCMS (Generic Request and Message Generator)

For legal reasons, only SAP applications may use the secure storage. We therefore use technical measures to prevent the secure storage being used in customer developments.

Checking SecStore Entries

You can check the entries in the secure storage across clients in transaction SECSTORE (without seeing their contents). The check consists of several steps:

• The technical check checks whether the system can read the entries and the internal administration structures of the secure storage are consistent. This check applies to the entries in all clients.
• The application that created the entry performs an application check. During this, the application checks, for example, whether the entry is still required, or that the access authorizations specified by the application are sufficient for the entry.

The application may not perform a check in the following cases:

• The creating application does not provide a check function.
• The check function of the application can only check entries in the logon client.

To be able to execute the transaction, you require the authorization object S_RZL_ADM (system administration) with activity 03.

1. Choose the Check Entries tab.
2. Specify the entries to be checked.
   • Specify entries for a particular application in the Selected Application field.
   • Specify the names of individual entries in the Record ID fields.
3. Choose Execute.

The Contents of Secure Storage result list appears. The result list lists the entries contained in the secure storage. In the navigation tree on the left, the entries are grouped by client and creating application. For the program to be able to group an entry under a particular application, the application must provide a function with which transaction SECSTORE can assign the entry. Entries that cannot be assigned are shown under Others. The following functions are also available in the result list:

• If the creating application supports doing so, you can branch from the message list to the editing of the entry. To do this, double-click the message line.
• You can delete all entries for which the application check found that they are no longer required by choosing Clean Up.
• You can delete the entries selected in the message list from the secure storage by choosing Delete. To do this, you require authorization S_RZL_ADM with activity. The system log logs the deletion.

Migrating Encrypted Data After Changing Installation Number

During project exercise, there was a requirement of system copy from production system, which was apparently done by customer and customer refreshed his quality system with production system.

During the time when system was refreshed, customer number was changed and also while doing system refresh instead of using existing installation number, customer decided to use new installation number.

Since, secure storage is an ABAP-kernel function for storing encoded data. The function is used by applications in the SAP system in order to securely store access data for external systems.

The installation number of the system and the system ID are used when creating the key for the secure storage. If one or more of these values changes, the data in the secure storage can no longer be read.

Under certain circumstances, you can migrate the data. You need the migration key to be able to carry out the migration.

If the change of the installation number is caused by importing a new license, SAP automatically generates the migration keys and sends it with the mail for the new license.

Alternatively, the migration key can be generated in SAP Service Marketplace.

You can find this application in SAP Support Portal under "Keys & Requests --> Migration Keys --> Secure Storage Migration".

After you log on, you can select the old and new installation numbers assigned to your user, and can generate the migration key.

If the old installation number and the new installation number are assigned to different customer numbers, and these customers are not linked to each other by the corporate group functions, you cannot create the migration key as described above.

Due to change in customer number and installation number, all RFC’s started failing.

This error is because of change in installation number and customer number.

Earlier installation number for DR2 system was: XXXXXX46

However, the same has been changed to: XXXXXX39

Hence, all securestore data has been invalidated and needs to be migrated to updated system configuration.

To check the same, please execute T-Code: SECSTORE & Execute.

Execute All RFC destination are inconsistent

Similar problem has been explained in SAP Note: Note 816861 - Migrating entries in the secure storage

To resolve the same below steps has to be performed:

• Customer systems with SAP_BASIS 7.00 or higher
  Start Transaction SECSTORE and switch to the "System data changed" tab.
  Fill the fields "Old system name", "Old installation number" and "Release Key" (referred to as "migration key" in the text of this note) and choose "Execute".

Following above mentioned note, T-code: SECSTORE executed

Go to TAB: System Data Changed

Enter old System SID.

Enter old Installation Number.

Generate Migration key from service marketplace. And provide the same in release key box.

And execute.

However, since secstore is used for all secured interfaces and data exchange, hence any change in secstore should be validated by testing relevant connected systems and interfaces.