Hi All,

I have been installing Netweaver 7.4 SR2 for Java on Windows 8.1 Enterprise SAP - Image Version: 2014.06 64-bit 16GB ram, using MSSQL, the install runs happily up to the step where it tries to start the instance, however it fails after trying to start for 5 minutes.

Looking through the error logs on the log analyser the error I have found is:

FCO-00011

ERROR      2015-04-30 12:29:41.93 [csistepexecute.cpp:1158]

FCO-00011  The step startJava with step key NW_CI_Instance_StartJava -> startJava  was executed with status ERROR

ERROR 2015-04-30 12:29:41.93 [csistepexecute.cpp:1158]
FCO-00011 The step startJava with step key |NW_Java_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|onehost|0|NW_CI_Instance|ind|ind|ind|ind|ci|0|NW_CI_Instance_StartJava|ind|ind|ind|ind|17|0|startJava was executed with status ERROR ( Last error reported by the step: Java process server0 of instance A01/J00 reached state Stopped after having state Waiting to start. Giving up.).

I have tried all the usual things like restarting the install, trying a completely fresh install, starting the instance manually but it will always fail at this point.

Has anyone else encountered this error, or can suggest further logs to inspect?

Many thanks in advance!

Hanif

Dear friends,

I am trying to install SAP Netweaver 7.4 Support Relase 2> SAP HANA> Application Server ABAP > Standard System but at Phase "Import ABAP" I am getting the below error message. I really appreciate your help in solving this problem. Thanks in advance.There they are the SAPINST.LOG with error and next, follow this, the two log file with details import_monitor.java.log , import_monitor.log

--> SAPINST.LOG :

Import Monitor jobs: running import of package: SAPNTAB

Loading of 'SAPNTAB' import package: OK

Import Monitor jobs: running 1, waiting 27, completed 1, failed 0, total 29.

Import Monitor jobs: running 2, waiting 26, completed 1, failed 0, total 29.

Import Monitor jobs: running 3, waiting 25, completed 1, failed 0, total 29.

Loading of 'SMIMCONT1' import package: OK

Import Monitor jobs: running 2, waiting 25, completed 2, failed 0, total 29.

Import Monitor jobs: running 3, waiting 24, completed 2, failed 0, total 29.

Loading of 'DOKCLU' import package: OK

Import Monitor jobs: running 2, waiting 24, completed 3, failed 0, total 29.

Import Monitor jobs: running 3, waiting 23, completed 3, failed 0, total 29.

Loading of 'SEOCOMPODF' import package: OK

Import Monitor jobs: running 2, waiting 23, completed 4, failed 0, total 29.

Import Monitor jobs: running 3, waiting 22, completed 4, failed 0, total 29.

Loading of 'SAPAPPL1' import package: OK

Import Monitor jobs: running 2, waiting 22, completed 5, failed 0, total 29.

Import Monitor jobs: running 3, waiting 21, completed 5, failed 0, total 29.

Loading of 'SAPSPROT' import package: OK

Import Monitor jobs: running 2, waiting 21, completed 6, failed 0, total 29.

Import Monitor jobs: running 3, waiting 20, completed 6, failed 0, total 29.

Loading of 'SAPAPPL0' import package: OK

Import Monitor jobs: running 2, waiting 20, completed 7, failed 0, total 29.

Import Monitor jobs: running 3, waiting 19, completed 7, failed 0, total 29.

Loading of 'SAPAPPL2' import package: OK

Import Monitor jobs: running 2, waiting 19, completed 8, failed 0, total 29.

Import Monitor jobs: running 3, waiting 18, completed 8, failed 0, total 29.

Loading of 'E071' import package: OK

Import Monitor jobs: running 2, waiting 18, completed 9, failed 0, total 29.

Import Monitor jobs: running 3, waiting 17, completed 9, failed 0, total 29.

Loading of 'SAPPOOL' import package: OK

Import Monitor jobs: running 2, waiting 17, completed 10, failed 0, total 29.

Import Monitor jobs: running 3, waiting 16, completed 10, failed 0, total 29.

Loading of 'DD03L' import package: OK

Import Monitor jobs: running 2, waiting 16, completed 11, failed 0, total 29.

Import Monitor jobs: running 3, waiting 15, completed 11, failed 0, total 29.

Loading of 'SEOSUBCODF' import package: OK

Import Monitor jobs: running 2, waiting 15, completed 12, failed 0, total 29.

Import Monitor jobs: running 3, waiting 14, completed 12, failed 0, total 29.

Loading of 'SAPSSRC' import package: OK

Import Monitor jobs: running 2, waiting 14, completed 13, failed 0, total 29.

Import Monitor jobs: running 3, waiting 13, completed 13, failed 0, total 29.

Loading of 'TODIR' import package: OK

Import Monitor jobs: running 2, waiting 13, completed 14, failed 0, total 29.

Import Monitor jobs: running 3, waiting 12, completed 14, failed 0, total 29.

Loading of 'WDY_UI_PROPERTY' import package: OK

Import Monitor jobs: running 2, waiting 12, completed 15, failed 0, total 29.

Import Monitor jobs: running 3, waiting 11, completed 15, failed 0, total 29.

Loading of 'SCPRSVALS' import package: OK

Import Monitor jobs: running 2, waiting 11, completed 16, failed 0, total 29.

Import Monitor jobs: running 3, waiting 10, completed 16, failed 0, total 29.

Loading of 'SAPSDOCU' import package: OK

Import Monitor jobs: running 2, waiting 10, completed 17, failed 0, total 29.

Import Monitor jobs: running 3, waiting 9, completed 17, failed 0, total 29.

Loading of 'SAPSDIC' import package: OK

Import Monitor jobs: running 2, waiting 9, completed 18, failed 0, total 29.

Import Monitor jobs: running 3, waiting 8, completed 18, failed 0, total 29.

Loading of 'SAPSLEXC' import package: OK

Import Monitor jobs: running 2, waiting 8, completed 19, failed 0, total 29.

Loading of 'SAPCLUST' import package: OK

Import Monitor jobs: running 1, waiting 8, completed 20, failed 0, total 29.

Import Monitor jobs: running 2, waiting 7, completed 20, failed 0, total 29.

Import Monitor jobs: running 3, waiting 6, completed 20, failed 0, total 29.

Loading of 'DD08B' import package: OK

Import Monitor jobs: running 2, waiting 6, completed 21, failed 0, total 29.

Loading of 'SAPSLOAD' import package: OK

Import Monitor jobs: running 1, waiting 6, completed 22, failed 0, total 29.

Import Monitor jobs: running 2, waiting 5, completed 22, failed 0, total 29.

Import Monitor jobs: running 3, waiting 4, completed 22, failed 0, total 29.

Loading of 'SAPDDIM' import package: OK

Import Monitor jobs: running 2, waiting 4, completed 23, failed 0, total 29.

Loading of 'SAPDFACT' import package: OK

Import Monitor jobs: running 1, waiting 4, completed 24, failed 0, total 29.

Import Monitor jobs: running 2, waiting 3, completed 24, failed 0, total 29.

Import Monitor jobs: running 3, waiting 2, completed 24, failed 0, total 29.

Loading of 'SAPDODS' import package: OK

Import Monitor jobs: running 2, waiting 2, completed 25, failed 0, total 29.

Loading of 'SAPUSER' import package: OK

Import Monitor jobs: running 1, waiting 2, completed 26, failed 0, total 29.

Import Monitor jobs: running 2, waiting 1, completed 26, failed 0, total 29.

Loading of 'SAP0000' import package: OK

Import Monitor jobs: running 1, waiting 1, completed 27, failed 0, total 29.

Loading of 'SAPSSEXC' import package: ERROR

Import Monitor jobs: running 0, waiting 1, completed 27, failed 1, total 29.

ERROR      2014-11-05 13:51:52.252

           CJSlibModule::writeError_impl()

CJS-30022  Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.

ERROR      2014-11-05 13:51:52.393 [csistepexecute.cpp:1158]

FCO-00011  The step runMigrationMonitor with step key|NW_ABAP_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|onehost|0|NW_CreateDBandLoad|ind|ind|ind|ind|createdbandload|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|abapload|0|NW_ABAP_Import|ind|ind|ind|ind|nw_abap_import|0|runMigrationMonitor was executed with status ERROR ( Last error reported by the step: Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.).

I need to install an additional application server for our BW abap and BW-java system on the same host.

Presently we have 2 application server for each system.The OS is windows and DB is MYSQL.

Now the situation is the 2 app servers are installed in 2008 R2 and the new one is in 2012.

So can we go ahead and install the application server or the versions should be same?

Hi experts,

I have some problems by starting the SUM, the Operating System is Linux and the database is MaxDB.

/usr/sap/P01/SUM

harensapnw:p01adm 81> ./STARTUP

chmod: changing permissions of `/usr/sap/P01/SUM/sdt/data/.sdt_keystore': Operation not permitted

chmod: changing permissions of `/usr/sap/P01/SUM/sdt/data/.sdt_storage': Operation not permitted

*** Checking if C++ runtime is installed ...

*** Starting from /usr/sap/P01/SUM/sdt...

** Checking username "p01adm" for compliance...

Sep 27, 2014 12:18:09 AM [Info]: *************************

Sep 27, 2014 12:18:09 AM [Info]: Starting Server

Sep 27, 2014 12:18:09 AM [Info]: Reading server configuration.

Sep 27, 2014 12:18:10 AM [Info]: Reading service configuration UseCaseService.

Sep 27, 2014 12:18:10 AM [Info]: Configuring LogManager ...

Sep 27, 2014 12:18:10 AM [Info]: *************************************************

Sep 27, 2014 12:18:10 AM [Info]: Starting SL Controller listening on port 4241 ...

Sep 27, 2014 12:18:10 AM [Info]: Starting StorageService ...

Sep 27, 2014 12:18:10 AM [Info]: Initializing SecurityManager ...

Sep 27, 2014 12:18:10 AM [Info]: Server certificate fingerprint is 28 50 0D D9 B6 C4 38 56 4A D7 3C DF 66 73 5A 4E

Sep 27, 2014 12:18:10 AM [Info]: Configuring HTTPManager ...

Sep 27, 2014 12:18:10 AM [Info]: Starting WebstartService ...

Sep 27, 2014 12:18:10 AM [Info]: Starting RoleService ...

Sep 27, 2014 12:18:10 AM [Info]: Starting AlertService ...

Sep 27, 2014 12:18:10 AM [Info]: Starting NotesService ...

Sep 27, 2014 12:18:10 AM [Info]: Starting ProcessService ...

Sep 27, 2014 12:18:10 AM [Info]: Starting MIDService ...

Sep 27, 2014 12:18:10 AM [Info]: Starting FileService ...

Sep 27, 2014 12:18:10 AM [Info]: LogService switched off.

Sep 27, 2014 12:18:10 AM [Info]: Starting MailService ...

Sep 27, 2014 12:18:10 AM [Info]: Starting services ...

Sep 27, 2014 12:18:10 AM [Info]: Starting service "UseCaseService" ...

Sep 27, 2014 12:18:10 AM [Error]: com.sap.sdt.util.diag.DevelopmentSupportRequiredException: Assertion failed for (com.sap.sdt.util.security.DecryptException: Unable to decrypt the given string

javax.crypto.BadPaddingException: Given final block not properly padded

com.sap.sdt.util.security.DecryptException: Unable to decrypt the given string

javax.crypto.BadPaddingException: Given final block not properly padded

javax.crypto.BadPaddingException: Given final block not properly padded

) at com.sap.sdt.util.sic.EncryptedSharedInputCatalogEntry.handleCrypterException(EncryptedSharedInputCatalogEntry.java:124).

Sep 27, 2014 12:18:10 AM [Error]: com.sap.sdt.util.diag.DevelopmentSupportRequiredException: Assertion failed for (com.sap.sdt.util.security.DecryptException: Unable to decrypt the given string

javax.crypto.BadPaddingException: Given final block not properly padded

com.sap.sdt.util.security.DecryptException: Unable to decrypt the given string

javax.crypto.BadPaddingException: Given final block not properly padded

javax.crypto.BadPaddingException: Given final block not properly padded

) at com.sap.sdt.util.sic.EncryptedSharedInputCatalogEntry.handleCrypterException(EncryptedSharedInputCatalogEntry.java:124).

Sep 27, 2014 12:18:10 AM [Error]: Start of "UseCaseService" failed.

Sep 27, 2014 12:18:10 AM [Fatal]: Error during controller startup.

Sep 27, 2014 12:18:10 AM [Fatal]: SL Controller exiting.

In the upgrade i am in phase Execution.

And i don't how to solve this problem...

Thanks in advance,

Cheung

We are trying to install ECC 6 EHP 7 IDES on SQL Server Windows 2012.  We are following 1244548 - IDES ERP 6.0 ECC 6.0 SR3.  No errors occur when providing the parameters but so far 20 out of 165 load jobs have failed.  I have attached to import_monitor.log.

You help is appreciated.

Regards,

Josie Spencer

BASIS Team Lead

Hello experts,

we have a BI Java system with a SCS00 instance and Sybase ASE database running under Linux and a separate PAS (instance number 04) running on a separate server under HPUX (distributed system). I want to re-integrate the PAS to the Linux server.

Is it possible to migrate the PAS to the LINUX server ? I tried to install a PAS using SWPM, but this will also re-install the database content.

Is it possible to  install an additional instance via SWPM on the Linux server and delete the HPUX instance ? What is the technical difference between a PAS and a simple instance ?

Thank you for your help.

Hi everybody!

I recently have installed SAP NW 7.3 PI in windows+sql server

I have patched java stack to sps10 and I'm currently patching sps10 of abap stack

My problem is: I'm trying to access to NWA with url http://localhost:50000/nwa (my instance is 00) but internet browser isn't showing anything. It looks that there is nothing running over port 50000 (firewall is disabled)

I tried with useradmin (http://localhost:50000/useradmin) and it happens the same

SAPMMC shows in green all my instances and java log is not showing me anything

What can I check?

Why can't I see anything?

thanks in advance

Hi All

Can you help me to create a sap router service in Windows 2012 R2 Std 64 bit?

My SAP Router Version is 740.

SAPRouter.exe patch is D:\SAPRouter\USR\SAP\SAPRouter

Routtab path is D:\SAPRouter\USR\SAP\SAPRouter

And please clarify this saprouter will be compatible with our running SAP ECC6.0 7.0 ?

or  SAP Router version will be depended on SAP ECC6.0?

Note: We have installed and built SAP Router in separate stand lone machine with Windows 2012 R2 64 bit version. Previous it was in other machine with Windows 2003 R2 32 bit version.

Thanks in advance

Sel

SAP Kernel

Kernel upgrade is a keen and effective process to keep SAP system health in a high.

As part of Basis, we all come across kernel upgrade. I would like to share my experience in a kernel upgrade, process.

In general, what is Kernel?

In computing, the kernel is a computer program that manages I/O (input/output) requests from software, and translates them into data processing instructions for the central processing unit and other electronic components of a computer. The kernel is a fundamental part of a modern computer's operating system.

Now how we relate a kernel to SAP:

Running Applications: All ABAP applications run on software processors (virtual machines) within this component.

User and process administration: This component is responsible for the tasks that usually belong to an operating system.

Database access: Each NetWeaver AS ABAP is linked to a database system, consisting of a database management system (DBMS) and the database itself.

Communication: ABAP applications can communicate both with other SAP Systems and with external systems.

Downloads:

Types of Kernel are available in service market place.

• 32/64 bit Unicode & extended
• 32/64 non Unicode systems & extended

By executing disp+work in a cmd line of OS level we can easily get the kernel version, release, Unicode or non Unicode, real or extended. We need to log as a SIDADM or navigate to existing kernel directory to get this information.

Need to download the exact kernel as per:

• Operating system
• Unicode/Non Unicode
• Real/extended

Kernel files are divided in to 2 parts:

• Kernel Part I (database independent)
• Kernel Part II (database specific)

Before Kernel Upgrade:

In the above example: We need to Upgrade N-1. ( N is the latest version)

SAP kernel 7.21 64 BIT Unicode files / patch 402 Part 1 and Part 2, once we downloaded the file we can extract.

Process:

STOPSAP and stop services – disable SAP services before we implement a new kernel.

                Reason behind is few files and executables are responsible to start and run SAP application server and few executables are responsible to write logs or update. If we try to replace SAP kernel on fly it may prompt an error file in use.

We have caused a corruption in the kernel directory; new files might be overwritten already.  It’s a severe error that we leave a corrupted kernel directory. Few scenarios we may need to restart SAP or if any cause of system shutdown. SAP may through some errors while starting up back when it has a corrupted kernel directory.

Recommended process to STOP SAP, stop SAP services and disable SAP services in services.msc.

Take a back up of existing kernel directory and keep in a safe place. Just in case if we need to revert back to older kernel

Replace existing kernel directory with a new kernel files.

Kernel directory will be located in

\usr\sap\SID\SYS\exe\uc\NTAMDXX

After implementing new kernel we can start SAP

To verify kernel use same CMD: disp+work

Tricky Part:

After replacing kernel if it’s failed to start SAP service:

• Check the kernel file whether we have downloaded the appropriate one if there is a mismatch in Unicode to non Unicode.
• Replace with old back up file by renaming back to same before; do not try to copy and paste again with kernel directory as of few files might have been overwritten already.
• If we still have error in starting SAP. We can try to replace with dev/Qas/prd kernel in the same landscape for time being.

Wrapping up:

Replacing kernel upgrade is a small effort but it’s important one to keep system up and running in a stabilized manner. Though we get a minimal down time to upgrade kernel, utilize time by preparing it before  with guidelines and read kernel upgrade Note first and follow it up for a smoother implementation of new kernel.

Regards,

Rathish Soundrapandian.

Hi,

I am trying to migrate my servlet from Netweaver 7.0 to 7.3. However, when I try to run it in NW7.3, it gives the error :

Error: Servlet with class <i>[xxx]</i> cannot be loaded.

Troubleshooting Guide https://sdn.sap.com/irj/sdn/wiki?path=/display/jstsg/home

Details:     You can not invoke the Servlet only by using its name

I have run out of idea what could be the problem. Please help.

Thanks.

Hello Experts,

Our ECC system is on EHP7 and currently we have requirement to activate the spreadsheet option in ML84 tcode.

Currently

List -->Export -->Spreadsheet is grayed out in ML84.

We need you views on how we can activate it without using any customizations or enhacement or we can suggest any other tcode instead of ml84 to display service entry sheets.

Thanks in Advance.

Regards

Sushant Goel

Hello you experts,

we have a problem with importing a client transport request via STMS after implementing Support Packages - the client export has been done before the SP implementation.

Because it's already NW 7.02 with ECC 6.05 the component versions are checked for every transport request - also for client imports.

Due to this fact we cannot import that client import request because of version mismatch.

Unfortunately you do not have the chance to just check the box for ignoring that mismatch like with other requests...

Do you know any other possibilities to get this client import implemented?

I searched for the unconditional mode number for ignoring the version mismatch - but I couldn't find anything - maybe you know it, so I can modify the buffer...?

Many thanks for your (hopefully quick) replies.

Best wishes

Marie

Environment:

OS = Windows 2008 R2

DB: DB2

IdM: Sp9

NW JAVA 7.3

SWPM: 07

I am attempting to install a JAVA stack on a sandbox for a client that I already fully installed IdM on.  I installed the DB2 instance and then completed the installation of IdM to the point where I can do everything  in the MMC.

Now, when I go to install the JAVA stack, the new Software Provisioning (Install software) from SAP does one of the following:

Install standard JAVA - installs everything CSC, DB and Primary Application Server

Install Distributed - Installs the CSC and Primary on an existing DB

Install High Availability - Self Explanatory

I've gotten to a point in the install where its asking for the SecStore.Key file.

Since DB2 was installed manually and not via the SAPinst.  Where would I find this file?

We don't have any other JAVA stack in the enterprise to get a copy of any existing file.

Hi guys,

I have an issue right now , my team wants to access HTTP and HTTPS version as well and here is the challenge.

The pictures which must be in the website can't be loaded in the HTTP version of the site...seems like by default it is taking the https version ,

So my question is where and what are the pentameters that are required to be changed accordingly.

Thnaks and Regards

Kaushik G

Dear Experts

we are trying to open MSS pages in HCM  Portal it throws igs cummunication error then i found some documents related to this by which i went al11 and open DIR_PROFILE = /usr/sap/SID/SYS/profile from there i went start profile of particular instance i found the IGS server line in commented

Kindly find the attachment for the same and suggest some thing on this our dev and qua werver IGS server works properly but in PRD it throws error

Prd Application server IGS

Prd Central server IGS

Quality server IGS where IGS working

Kindly give me some suggestions to rectify the issue..

Regards

Hi,

We have archived some scanned PDF and attached to concern's persons id in 4.6c. After that we have upgraded 4.6c to 6.0 and now we try to retrieve through persons ID but system appear " cannot be read PDF". Please hint me in this regards.

Thanks

Regards,

Arshad Mehmood

Hi All

We built new SAP Router Server and new certificate is installed on it with old network setup and SAP infrastructure.

There is no other changes except SAPRouter. SAP Router Version is 740.

Now the SAPRouter is up and running.

But the connection test from SM59 to SAPOSS is failed.

It gives the following error,

Steps to reproduce the issue:

logged into SAP

run the tcode SM59

select SAPOSS rfc

click on Test Connection

Please help me to resolve this issue urgently.

Thanks in Advance

Sel

Dear Experts,

There is one integration project in which I should convince client on oData services over SOAP services, How can we justify oData services are efficient than SOAP services ? 

Can you please elaborate.

Thanks & Regards,

Bhushan Ghule

Summary

This document contains  steps to be performed to install, configuring and testing  an ERS instance failover.

Applies to NetWeaver Web AS Java 2004s onwards (Unix system)

Divided the article in below sections:-

1. Preparation

2. Setting Up the Replication Server

3. Checking the Installation (Replication Server)

4. Commands to check status of ERS/SCS instances

5. Log Files

6. Related Content

Introduction

The standalone enqueue server (SAP Central Services - SCS) is used in NetWeaver Web AS Java to provide a locking service based on the enqueue function. The enqueue clients (SAP application servers) and the enqueue server communicate directly, that is, the work process has a TCP connection to the enqueue server. They no longer communicate via the dispatchers and the message server.

The enqueue server keeps critical data (that is, all locks currently in use by users in the system) in the lock table in the main memory. If the host fails, this data is lost and cannot be restored even when the enqueue server is restarted. All transactions that have held locks must therefore be reset.

For this reason, the enqueue replication server (ERS) is started on another machine which together with the standalone enqueue server (SCS) provides a high availability solution.

This document contains all the steps to be performed for preparing, configuring, testing and trouble-shooting an ERS instance.

1. Preparation

Profile Parameters for the Standalone Enqueue Server (SCS)

Activate replication by setting parameter enque/server/replication = true in the in the instance profile of the standalone enqueue server (<SID>_SCS<Instance_no>_hostname).

Profile Parameters for the Enqueue Clients

Set the parameter enque/deque_wait_answer = TRUE for the enqueue clients (application server instances) in the default profile.

The parameter enque/deque_wait_answer determines whether dequeue (removal of locks) is done synchronously or asynchronously. The parameter can have the following values:

TRUE:  Waits for response from the enqueue server (synchronous)

FALSE: Does not wait for response (asynchronous)

2. Setting Up the Replication Server

Under administrator user <sid>adm perform the following steps on the both physical servers.

Identify Executable Directory

• The directory determined by DIR_CT_RUN for the system with DIR_CT_RUN in the SCS instance profile. The DIR_CT_RUN for the ERS instance profile to be created should then be the same as for the SCS instance.
• The directory determined by DIR_EXECUTABLE for the system without DIR_CT_RUN in the SCS instance profile. The DIR_CT_RUN for the ERS instance profile to be created should then be the DIR_EXECUTABLE of the SCS instance.

Create directory structure

Create the following directory structure on the enqueue replication server (ERS):

/usr/sap/<SID>/ERS<inst.no>

                  +--- exe

                  |     +--- servicehttp

                  |               +----- sapmc

                  +--- log

                  +--- data

                  +--- work

Where:

• ERS: prefix for the enqueue replication server
• <SID>: System ID of the SAP system to which the new instance belongs
• <inst.no>: Instance number of the new instance (here 11)

Copy executable files

1. Copy the following files from the executable directory /sapmnt/<SID>/exe into directory /usr/sap/<SID>/ERS11/exe:

• enqt
• enrepserver
• ensmon
• libicudata.so.30
• libicui18n.so.30
• libicuuc.so.30
• libsapu16_mt.so
• librfcum.so
• sapcpe
• sapstart
• sapstartsrv
• sapcontrol

The files can have different extensions on different UNIX platforms. Depending on the platform and whether Unicode is used, there may not be as many files.

1. Copy the following files from the executable directory /sapmnt/<SID>/exe/servicehttp/sapmc into directory /usr/sap/<SID>/ERS11/exe/servicehttp/sapmc:

• sapmc.jar
• sapmc.html
• frog.jar
• soapclient.jar

1. Create a sapcpe list file with the name ers.lst in directory /usr/sap/<SID>/ERS11/exe. This file has the following content:

Create ERS Start & Instance profiles

1. Create a new start profile (not a symbolic link to a common file – it does not work) for the ERS instance in the profile directory.

The SCS instance could also have the following parameters:

SAPSYSTEMNAME = <SID>

SAPSYSTEM = <Instance_no>

INSTANCE_NAME = SCS<Instance_no>

SAPLOCALHOST = <SCS_Host_name >

The corresponding replication instance might look like this:

ERS SAPSID         = <SID>

ERS INST.NO.     = 11

ERS HOST             =  ERS_host_name

The corresponding start profile START_ERS11_<Host_name> will look like:

If you are using a local profile directory  insert the following profile parameter into the start profile of the ERS instance: DIR_PROFILE = $(DIR_INSTANCE)/profile

2. Create an instance profile (not a symbolic link to a common file – it does not work) in the profile directory.

Parameters for the SCS instance (example):

SCS SAPSID               = <SID>

SCS INST.NO.           = 04

SCS HOST  = <SCS_Host_name >

Parameters for the replication instance (example):

ERS SAPSID               = <SID>

ERS INST.NO.           = 11

ERS HOST  = <ershostname>

Associated instance profile <SID>_ERS11_ershostname:

If you are using a local profile directory insert the following profile parameter into the instance profile of the ERS instance: DIR_PROFILE = $(DIR_INSTANCE)/profile

Configure the control mechanism for the replication server

The following options are available:

1. Self-control with HA Polling

Here the replication server uses the HA software to periodically request information about the physical host on which the SCS instance is running. Depending on this information the ERS instance is activated or deactivated. To do this a tool (a script or a library from the HA hardware partner) is needed.

If you use an enqtest.sh script in directory DIR_EXECUTABLE you must insert the following lines in the instance profile.

1. HA Software Control

With this solution the HA software will start the ERS instance, whenever required. The monitoring of the ERS instance and subsequent, if required, is handled by HA software.

Configure the persistency of the replication table in the file system

This has the advantage that the replication table can be distributed across several hosts by means of the cluster software (shared file system), and that following a failover the enqueue server does not necessarily have to be restarted on the same host on which the active replication was running beforehand.

To also save the replication table in a shadow file in the file system, insert the following lines in the instance profile:

Note: Storing the replication table in the file system can lead to a severe drop in enqueue server performance.  Beforehand, you should always check whether performance will be sufficient with this option.

Parameter for preventing automatic ERS restart

It was noticed that, on SCS failover, the SCS process would read the replication table and terminate the ERS process, as expected. However, within 15 seconds, the ERS process would restart on its own. Based on an analysis of the process ids, it was concluded that the ERS process was being restarted by the sapstart process.

If a program managed by sapstart is restarted within 10 minutes, an internal counter is incremented. By default, sapstart no longer starts the program as soon as this counter is larger than 5 . This value can also be changed using the parameter 'Max_Restart_Program=xx' where xx represents the number of restarts.

To prevent this automatic restart of ERS, the parameter Max_Restart_Program=00 was added to the ERS start profile parameter.

Start the ERS instance

Start the ERS server with below command

<sid>adm$ startsap ERS11

Check the startup log with the command

<sid>adm$ cat /home/<SID>adm/startsap_ERS11.log

Check the ERS processes at the OS level

<sid>adm$ grep –ef| grep –I ERS11

It should show you some processes .

Setup automatic start of ERS instance

To start the ERS instance automatically when the system is rebooted, insert the following line in file /usr/sap/sapservices based on the UNIX shell used by user root:

setenv LIBPATH /usr/sap/<SID>/ERS11/exe:$LIBPATH;        (CSH)

LIBPATH=/usr/sap/<SID>/ERS11/exe:$LIBPATH; export LIBPATH;                                (BSH)

/usr/sap/<SID>/ERS11/exe/sapstartsrv pf=/usr/sap/<SID>/SYS/profile/START_ERS11_<ershostname> -D -u <SID>adm

This only works if:

NetWeaver AS version 7.00 has already been installed on this host

(Under UNIX) you have already performed the steps described in SAP Note 823941 (Configuring SAP Start Services as UNIX Daemons)

Repeat these steps for all the physical hosts in the HA failover cluster. If you want to make another SCS instance more fail-safe, you have to set up a separate set of ERS instances.

3. Checking the Installation (Replication Server)

Once the Replication Server has been setup, check that it functions properly to be sure that the replication server will work correctly if the enqueue server fails. The following tests are performed on the host where the replication server is running.

Check the status of connection between the enqueue server and the replication server

The SCS instance of the SAP system has been started. Start program ensmon on the host on which the replication server is installed. To determine the replication server enter the following command:

ensmon pf=/usr/sap/<SID>/SYS/profile/<SID>_ERS11_<hostname>

If your ERS replication is running this connand will give below information

• General information (configuration info)
• Runtime statistics for replication thread:
• Information from the replication server  side:
• replication table statistics:
• request statistics:
• Network parameter and statistics:

If the connection is OK, the output would look like:

If the connection is not OK, the output would look like:

If the connection is not ok, first check whether the replication server has been started at all (using the operating system or the cluster software.)

If the replication server has been started, check files dev_enqrepl on the enqueue server or dev_enrepsrv on the replication server (in the work directory of the SCS or ERS instance). Use the error messages and profile files here to narrow down the cause of the problem.

Monitoring the Lock Table at Failover

Use program enqt to check the fill level of the lock table and the failover ID. The SCS instance of the SAP system has been started.

Start program enqt on the server on which the replication server is installed. Then use the enqt options described here. Otherwise you could damage the content of the lock table.

Monitoring the Fill Level of the Lock Table at Failover

...

1. 1. Enter the command below to fill the lock table of the enqueue server with 20 locks: enqt pf=/usr/sap/<SID>/SYS/profile/<SID>_ERS11__<hostname> 11 20

1. Monitor the fill level of the lock table by executing the command:

enqt pf=/usr/sap/<SID>/SYS/profile/<SID>_ERS11_<hostname> 20 1 1 9999

This command permanently reads the content of the lock table and shows the number of lock entries on the

1. console.

Monitoring Lock Table ID at Failover

...

1. Enter the following command on the ERS host to output the lock table ID before the failover:

enqt pf=/usr/sap/<SID>/SYS/profile/<SID>_ERS11__<hostname> 97

1. Trigger a failover of the SCS instance.

1. Enter the command

enqt pf=/usr/sap/<SID>/SYS/profile/<SID>_ERS11__<hostname> 97

The output for the row containing EnqTabCreaTime/RandomNumber should be exactly same before and after failover should be different .

1. Make sure that the lock table ID is the same before and after the failover. If it isn’t, the replica has not been copied .

4. Commands to check status of ERS/SCS instances

To monitor the status of ERS/SCS instances, the commands described below may be used (for example in HA scripts):

ERS Commands

To determine the replication server enter the following command:

  ensmon pf=/usr/sap/<SID>/SYS/profile/<SID>_ERS11_<hostname> 2

If replication server is active and connected to SCS, the following message is displayed in the first few lines of the output:

  Replication is enabled in server, repl. server is connected

  Replication is active

The status may also be checked with the command "startsap check", however, this command seems to check only the process at the OS level, not for the functioning of the process.

SCS Commands

Send a dummy request to the server, to check if it is alive:

  ensmon –H < scshostname> pf=/sapmnt/<SID>/profile/<SID>_SCS04_< scshostname>  1

Last line of output contains the message "Dummy request executed successfully with rc=0

The status may also be checked with the command "startsap check", however, this command seems to check only the process at the OS level, not for the functioning of the process.

5. Log Files

Enqueue Server

You can find the following information in the enqueue server files:

• dev_enqsrv: This file is written only when the enqueue server is started up. All problems occurring when the enqueue server is started (for example, when the replica is read or the lock table created) are analyzed with this file.
• dev_enqio_*: The threads that handle communication with enqueue clients write to this file (there may be more than one file - they are numbered sequentially).
• dev_enqwork: Problems arising from the actual enqueue processing are written to this file.
• dev_enqrepl: Communication with the replication server is set up from this thread; replication problem messages can be found here.
• dev_enqsig: This file does not exist in Windows. Here the processing of asynchronous signals is recorded by the operating system. Shutdowns triggered from an external source can be found in this file.

There may be further dev* files that are not usually important. You should deliver these files to support anyway when you open a problem message.

Replication Server

You can find the following information in the replication server files:

• dev_enrepsrv: Almost all components of the replication server that do not write to one of the files specified below write to this file.
• dev_enrepsig: As with the enqueue server this file does not exist in Windows. Asynchronous signals from the operating system are processed here too.
• dev_enrepha: All events of HA pollings (more information: Polling Concept) are written to this file.

6. Related Content

SAP notes

• 1249256 - Locks are lost during failover
• 920979 - Out of memory in standalone enqueue server
• 1082584 - Return codes of the enqueue replication server
• 1047180 - Troubleshooting for the standalone enqueue server
• 1018968 - Enqueue replication server does not terminate after failover
• 897583 - SAP WebAS Java 6.40 SP15 - List of corrections
• 1043968 - Standalone enqueue Problems during resource bottleneck
• 1064290 - Standalone enqueue server and standalone gateway
• 928637 - Enqueue replication not possible due to connection problem
• 1077883 - Pool 10 is too small
• 112 - Trace and error information in the dev_ files

Others

Setting Up the Replication Server

Standalone Enqueue Server

Hi experts,

we experience for a specific RFC-connection to our R/3 system (4.7) sometimes CPIC-223 (network read error) in SM21 and "connection to partner broken" in SAP-Gateway-Trace. The connection works fine for most of the time, but for some data it generates that error. We allready checked the connectivity on the network layer (DNS, ping ...) - all OK. The call doesnt reach the function module, because we dump the input first, and no dump exists. It looks like, that the RFC, CPIC or even lower the IP procoll produces this problem.

Do you have any hints for me ?

thx

Richard