Objective:

This FAQ provide answers to commonly asked questions regarding SGEN. We have gathered few commonly asked questions about SGEN from our customers.  Please review the information below:

What is SGEN?

SGEN is the transaction to generate ABAP loads for large numbers of programs, function groups, module pools, and so on as well as Business Server Page applications (BSP applications).

SAP Note 379918 contains report name and table name which are used during SGEN execution. Report RSPARAGENLOD, RSPARAGENJOB and  RSPARAGENER8 are replaced by RSPARAGENLODM, RSPARAGENJOBM and RSPARAGENER8M respectively in the latest version. table GENSETC is replaced by GENSETM.

SGEN execution consists two parts. The first part determines the so-called generation set through the options given in the first screen. generation set is stored in table GENSETC or GENSETM. The second part is compiling source code into load. this part is triggered by  background job RSPARAGENER8 or RSPARAGENER8M.

Where can I find more information about SGEN?

You can go to SGEN transaction and click the pushbutton Information. there is detail explanation about how to use the transaction. You can also go to SAP online help and search SGEN.

When should I run SGEN?

SGEN is designed for large-scale program generations. You can consider to use SGEN in following scenarios. SAP Note 438038 and 162991 explains other generation tools as well.

How to improve SGEN performance?

Compared against the calculation of SGEN generation set, the second part of SGEN takes longer time. However, the second part is out of control of SGEN. This is SAP system related and depends on resources of the system itself like main memory, number of CPU  and last but not least, the database performance. The runtime of the generation jobs is heavily depending on the database performance of the system. If you noticed that generation job long time, you can following  below:

1. Make sure there is enough system resource (CPU, memory) and free background  work processes. SAP Note 1651645 describes a known issue.
2. Make sure that database performance is fine. Please involve your database expert if necessary.

How to handle generation system error?

You need to analyze SM37(Job name:RSPARAGENER8 or RSPARAGENER8M), SM21, ST22 and ST11.

How much free space is required in database for SGEN execution?

If you want to regenerate loads, make sure that there is enough space available in the database. The space required can be several hundred MB. Generation over all components requires around 2 GB of free space.

See Also:

162991 - Generation tools for ABAP programs
379918 - Redesign of the SGEN transaction
413912 - Shorter runtime for specifying generating quantity
438038 - Automatic regeneration of invalidated loads
589124 - Performance improvements when Support Package imported
1132507 - SGEN: Using maximum number of free work processes
1147789 - SGEN does not generate all loads after release upgrade
1230076 - Generation of ABAP loads: Tips for the analysis
1630356 - SGEN terminates after 500 generation errors
1645864 - SGEN generation errors do not cause an error message
1651645 - Maximum number of SGEN processes cannot be greater than 9
1869363 - SGEN: Correction for selection of WebDynpros / BSPs

Please leave any feedback in the comments section below. You can also post any questions in the SL discussion forums. 

James Wong

SAP Topic Communicator

Hi All,

When running SUM sometimes you want to ignore errors (for example in phases ACT_UPG or XPRAS_UPG). Ignoring such errors when using SUM SP11 PL7 can lead to severe issues later which may lead to a reset of the SUM run.

To prevent this, please avoid the use of the ignore button.  This issue is expected to be fixed in SUM SP11 PL8.  I expect the SUM SP11 PL8 to be found on SAP SMP site in the next couple of days. I will update this blog when it is available.

Note:

For more information please refer to SAP Note 2083179 - Problems Ignoring Phases in SUM SP11 PL7

Best regards,

James Wong

SAP Topic Communicator

Hi All,

During the generation of certain programs, syntax errors or runtime errors  occur in Coverage Analyzer programs. It can happen during run of the shadow instance or 2^nd shadow instance that the upgrade does not work due to syntax errors or run time errors (one symptom is that RFC into the system return error and do not start batch jobs).  If you find something like COVREF or RSGENCOV in the dev_* traces refer to SAP Note 1650093.

Note:

For more information please refer to SAP Note 1650093 - Syntax error or runtime error in Coverage Analyzer

Best regards,

James Wong

Hi guys.

In the past we had serious issues in adjusting notes which have manual activities. After the adjustment in SPAU they still appear in SNOTE with a wrong status ('Obsolete version Implemented').

The workaround until now was to deimplement the notes in SNOTE. This was a pseudo-deimplementation which had to be done to confirm the cancellation of manual activities.

This bug has been fixed and rolled out with note #2077553. Please proceed as described in that note to avoid that error in the future.

Best regards,
Andreas

Objective:

This FAQ provide a list of commonly asked questions regarding SPAU adjustment.

Selection screen

[1] What should I bear in mind during the selection on the selection screen?
[2] Why do the modification browser (transaction SE95) and the modification adjustment (transaction SPAU) display an object with "Last changed by" or with the last change request, even though other selection conditions were entered on the initial screen?

Modification adjustment

[3] Why does the system display such a large number of objects in transactions SE95 and SPAU after upgrading from a Release lower than Release 4.5A to Release 4.5A or higher?
[4] Why does transaction SPAU display objects with a question mark?
[5] Can I save the transferred changes in the modification adjustment so that another developer can transfer further changes?
[6] Do I have to perform a modification adjustment after each upgrade or Support Package import?
[7] When do I have to import the SPAU adjustment transport of a development system into the consolidation system or production system?
[8] Can I also retrieve versions of objects in the modification adjustment?
[9] How do I proceed if versions of modifications with Modification Assistant were still retrieved?
[10] How can I mark the objects of an advance development in the system so that they can be provided in transaction SPAU for an adjustment during the next upgrade or Support Package import?
[11] Why does transaction SPAU display Dictionary objects?
[12] How can I quickly delete objects from transaction SPAU or SE95?
[13] Does the system change the active object when resetting to original?

Resetting to original

[14] How can I display objects that were reset to original?
[15] Why was the "Return to SAP standard" function replaced with "Reset to Original"?
[16] Why does the system have to be modifiable for resetting to original?
[17] Why does the system require a transport request when resetting to original?

SPAU and note corrections

[18] Which are the advantages of the Note Assistant?
[19] Can I also install the Note Assistant in a system with a large number of modifications?
[20] Which requirements must be met for installing the Note Assistant?
[21] How can I find out in which notes an object is used?
[22] Why can I not reset to original a note correction with a yellow or green traffic light symbol in transaction SPAU?
[23] Why can I not reset to original a modification with Modification Assistant if the object is contained in a note correction?
[24] Why can I not adjust a modification in transaction SPAU if the object is contained in a note correction?

Tips and tricks

[25] Where do I find documentation about transaction SE95_UTIL?
[26] Where should I check in the event of problems?
[27] How can I display the change history of an object?
[28] How can I display the developers that have modified an object?
[29] How can I display the requests in which the object was processed or imported?
[30] Which versions should I compare if a problem occurs in the modification adjustment?
[31] What should I bear in mind when I compare versions in version management?
[32] What is important when comparing modification versions?
[33] Which information can I obtain from the transport logs?
[34] Under which components should I open a message if problems occur?

The answer to the above list of questions are located in the SAP System Upgrade & Update troubleshooting wiki page.

Direct link to the above questions:Handbook for SPDD and SPAU adjustment and FAQs for the SPAU-Adjustment

Additional Info:

1. Rami Kumar Munagala has written a handbook describing the SPDD and SPAU adjustment. Link to:SPDD & SPAU Adjustments Handbook

2. There was a program bug, which lead to obsolete notes de-implemented during SPAU adjustment. For details, you can read SAP Note 1928534.

Best regards,

James Wong

Short summary

To simplify the handling, usage types as structuring element got deprecated for the installation and maintenance process of systems based on SAP NetWeaver 7.30 including Enhancement Package 1 and higher releases. By eliminating one abstraction layer and using a harmonized model for the provisioning and the maintenance of SAP systems, customer experience of all lifecycle management processes is improved and the number of issues due to inconsistencies can be reduced.

Background

With SAP NetWeaver 7.0x, we introduced usage types as structuring element for SAP software on a technical level. Per definition, usage types determine the role an SAP system plays in a given (distributed) scenario and represent the capabilities offered by a collection of installed and configured (technical) software components.

Examples of usage types are AS ABAP, AS Java, Enterprise Portal Core, and BI Java. The installation procedure offered to select required usage types during the installation procedure accordingly.

Motivation for Deprecation

While the installation and the initial configuration used a model with usage types, later processes in the lifecycle of a Java system use other models (based on our Production and Product Management System, PPMS).

Let’s take a more detailed look at the lifecycle of a Java system from customer perspective:

1. You as a customer had to select usage types with specific names during the installation to define the role that the Java system is intended to fulfill in your landscape.
2. After the installation, you had to select and execute configuration templates based on usage types for the initial setup of the installed Java system.
3. As prerequisite for any maintenance activity, you had to ensure that PPMS entities were maintained in the Landscape Management Database (LMDB) – as these entities use different names than the usage types used before, this represented the first break in naming.
4. When this prerequisite was fulfilled, you could plan a maintenance task in the Maintenance Optimizer (MOpz), again using PPMS entities.
5. Finally, for delta package deployments (such as an upgrade), you had to consider both PPMS entities and usage types.

Overall, this break of used entities lead to confusion, additional efforts and possible inconsistencies, resulting in longer projects and additional costs due to issues in handling PPMS data and in maintenance projects.

Therefore, we decided to remove dependencies towards usage types for the installation and configuration of Java systems based on SAP NetWeaver 7.31 and higher – instead, we switched to a representation based on the same data model as used by the maintenance procedure (using product instances based on PPMS data). This change is reflected in the corresponding tools (such as software provisioning manager 1.0) as provided with Software Logistics Toolset 1.0 SPS12. The change leads to a harmonized internal modeling for both ABAP and Java systems and to the elimination of most of the issues caused by inconsistencies in customer landscapes, as now, harmonized structures/entities based on one reliable model can be used everywhere, as shown on the following figure:

Even if the visible changes for you in the affected procedures might be minor, we are sure that the procedure got more reliable and that a consistent model and naming will make the overall handling smoother and easier for you.

As already mentioned in the blog posts DMO: introducing the new UI and SUM: extending the new UI to AS Java scenarios a new, exciting user interface (UI) is available for the Software Update Manager (SUM) bringing flexibility and a fresh, modern look to your desktop.
This user interface has been released for usage in the database migration option (DMO) scenario.
With SUM scenarios for upgrades, EHP installations and applying SPs the SL Common UI is now not only available on request for AS Java based systems, but also for AS ABAP based systems.

The new SL Common UIis based on SAPUI5. It is running in a web browser and does not require any java UI component anymore (see figure below).

The usage is “available on request”, that means that currently you will have to register to use the new UI. If you would like to take part in the piloting, create an incident on component BC-UPG-TLS-TLA with title “Registration request for new UI” and specify your project time line.

Did you know when customers are reviewing a KBA via the SAP Service Marketplace, they have the ability of rating the KBAs by using a5-starrating system?

INFO: if you find a KBA deserves some recognition, you can give it a star rating. You can provide this via the Overall Rating at the top right hand corner of the KBA. (Refer to image below)

The purpose of this document is to provide the top 20 highest star rated knowledge base articles (KBA's) from the Upgrade component.  The goal here is to provide you the highest rated and voted KBAs from our customers. This blog is planned to get updated regularly.

Please leave any feedback in the comments section.

** The top KBA notes does not include SNotes because of a limitation on the system.

Please note, in order to view the contents of the SAP Notes, you will need to be logged into Service Marketplace.

Overview on tools delivered with SL Toolset 1.0 SPS 12

Availability: SL Toolset 1.0 SPS 12 is available since November 24th 2014.

What's in:

• compared with SPS 11, no new tool joined the SL Toolset 1.0
• existing tools are improved and updated: some tools are delivered in a new SP, some without (when only minor fixes where done)

Further information on the SL Toolset SPS 12:

• SAP Note 1975575 (Release Note for SL Toolset 1.0 SPS 12; logon required)
• Quick link /sltoolset on SAP Service Marketplace (logon required)
• Idea Space for the Software Logistics Toolset and its tools

"nZDM for SAP NetWeaver Java" 1.0 SP12

Offering

• implement Support Packages and patches for SAP Java-stack systems with minimal technical downtime
• Target Products:
  • SAP NetWeaver Portal 7.02, 7.3x, 7.4
  • on request: SAP Business Process Management and SAP Process Orchestration
    releases 7.3 incl. EHPs, and 7.4 (see SAP Note 2039886; logon required)

Changes with SL Toolset SPS 12

• No changes

More information

• SAP Note 2090615

"nZDM for SAP Process Integration" 1.0 SP06

Offering

• implement Support Packages for SAP Process Integration (SAP PI) with minimal technical downtime of appr. 30 minutes
• Target Products: SAP PI dual stack 7.10, 7.11, 7.30, 7.31

Changes with SL Toolset SPS 12

• No changes

More information

• SAP Note 1435235
• SCN content: Near Zero Downtime Management for SAP Netweaver Process Integration (nZDM/PI) available on Service Marketplace

Software Provisioning Manager 1.0 SP 07

Offering

With software provisioning manager, get latest SAPinst version that enables provisioning processes for several products and releases for all supported platforms – get support of latest products, versions and platforms, including latest fixes in tool and supported processes + benefit from unified process for different product versions.

Changes with SL Toolset SPS 12

• Success dialog offers link to send feedback + statistical runtime data to SAP
• Declustering/depooling during installation + copy now supported for all database platforms but SAP MaxDB
• Installation:
  • Usage Type deprecation for Java-based systems based on SAP NetWeaver 7.31 and higher (see blog)
  • Adaptive installation enabled for systems based on SAP NetWeaver 7.1x and higher, allowing to set virtual host names for each SAP system instance
  • ABAP temporary license no longer installed by software provisioning manager, but handled by kernel automatically for installation of systems based on SAP NetWeaver  ≥ 7.40 using kernel 7.42
  • Further improvements for up-to-date installation (including initial basic configuration of transport management, basic and simple option to apply transports as part of installation, starting of Software Update Manager, update of SPAM to latest version)
• System copy:
  • Extended export options (option to re-use files for easier and faster repetition of export,  ability to provide DBSIZE.XML instead of running r3szchk)
  • Further improved migration to SAP HANA (FTP-based migrations now also support  declustering at export)
  • You can optionally use table comparison with Software Update Manager instead of table checker
• Dual-stack split:
  • Optionally, connection between AS ABAP and AS Java can be configured automatically
  • Split of systems based on SAP NetWeaver 7.1x and higher, running on IBM DB2 for Linux,  UNIX, and Windows with Microsoft Cluster Services (MSCS) now supported
• Rename of systems based on SAP NetWeaver AS ABAP 7.1x now supported

More information

• SAP Note 1680045 (Central Release Note Software Provisioning Manager 1.0)
• SAP Note 1619720 on System Rename
• SAP Note 1797362 (Dual Stack Split for Systems based on SAP NetWeaver)
• SCN content Software Provisioning Manager 1.0
• SCN content System Rename
• SCN content Dual-Stack Split

Software Update Manager 1.0 SP 12

Offering

• Consolidation of different software logistics tools into one unified software logistics tool
• Runtime reduction: Higher degree of parallelization for certain phase types
• Downtime reduction: Enhanced Shadow System capabilities for specific use cases
• Combine SAP system update with migration to SAP HANA (DMO: database migration option)

Changes with SL Toolset SPS 12

• SUM ABAP: new dialog for system switch to productive usage
• SUM ABAP: usage of new user interface (SAPUI5 based; available on request; see blog)
• DMO: support for SAP ASE as target database (available on request)
• DMO: MS SQL 2005 as source database version (available on request)
• DMO: support for i5 as source ("DB2 for IBM i" / "DB2 for IBM iSeries" / "DB2 for IBM i5/OS")
• SUM Java: Usage Types deprecation for systems based on SAP NetWeaver 7.3 Enhancement Package 1 and higher
• SUM Java: Repeating steps with increased logging
• SUM Java: Downtime optimization through parallel starting of additional application server instances

More information

• SAP Note 1981278 (Central Release Note SUM SP12)
• SCN content: Software Update Manager (SUM): introducing the tool for software maintenance
• SCN content: Database Migration Option (DMO) of SUM - Introduction

Standalone Task Manager for Lifecycle Management Automation 1.0 SP 01

Offering

Stand-alone task manager for lifecycle management automation is a framework to execute below automated configuration templates

• SSL configuration templates validates the SSL configuration settings both, for ABAP and for Java environments and generates HTML reports that can be used for further analysis. It also performs SSL configuration automatically and describes required manual tasks.(SAP Note 1891360)
• ERP <-> CRM, template to establish connectivity between ERP system and CRM
• Mobile Configuration templates for Backend, Gateway and SUP (SAP Note 1891358)
• HANA user management and SLT (System Landscape Transformation) configuration (SAP Note 1891393)

Changes with SL Toolset SPS 12

• No changes

More information

• SAP Note 1891353: SAP Note for Standalone Task Manager for LM Automation-1.0 (Framework)
• SAP Note 1783372: Central Release SAP Note Standalone Task Manager for LM Automation -1.0
• SCN content: Secure Technical Configuration with the Lifecycle Management

SAPSetup 9.0

Offering

SAPSetup offers easy and reliable functionality for installations of different scales:

• Installation of frontend products without administrator permissions
• Remote installations from Administration PC
• Configuration and export of installation packages containing multiple products
• Consistency check
• Central log file analysis

Changes with SL Toolset SPS 12

• SAPSetup with the latest corrections as outlined in the SAP Notes below

Further information:

• SAP Note 1583967 (Release Information Note for SAPSetup 9.0)
• SAP Note 1587566 (Installation Problems with SAPSetup 9.0)

CTS Plug-In 2.0 SP14

Offering

• Generic CTS to connect your non-ABAP applications with CTS
• New user interfaces and new features for CTS
• Central Change and Transport System (cCTS) as technical infrastructure for Change Request Management (ChaRM) and Quality Gate Management (QGM) in SAP Solution Manager 7.1 SPS 10 and higher

Changes with SL Toolset SPS 12

• No changes

More information

• SAP Note 1665940 (Central Release Note CTS Plug-In 2.0)
• CTS Plug-In 2.0 Tool Documentation: http://help.sap.com/nwcts
• SCN content:Resources on CTS+

AddOn Installation Tool and Support Package Manager

Offering

SPAM/SAINT provides easy access to lifecycle management processes by being part of the SAP NetWeaver AS ABAP stack and by being accessible directly via SAP GUI.  This way you are able to control different kinds of implementation processes, such as installing, upgrading or updating ABAP software components. SPAM/SAINT Updates themselves can be applied to ABAP-based systems independent of underlying SAP NetWeaver component versions.

Changes with SL Toolset SPS12

• No changes

More information

• SAP Note 2011192: Deinstalling ABAP add-ons
• SAP Note 2009316: Product information in system status is missing
• SPAM/SAINT Documentation: http://help.sap.com/spmanager

New scenario "Unified Consumption Experience"

This scenario is not a new tool, but important to mention:
Unified Consumption Experience (UCE) aims at simplifying the process of installation for a new system on a specific target software level.

See the following blog for more information: Unified Consumption Experience

Boris Rubarth

Product Management SAP SE, Software Logistics

Within SAP HANA SP9, everything is about the new feature “multitenant database containers“.

The latest software provisioning manager SP 7 provided with SL Toolset 1.0 SPS 12 already supports this new feature. This is a brief overview about how to work through the corresponding dialog phase, when you are using the new SAP HANA SP9 feature: Multi-Tenant Database Containers.

Choose the procedure you want to execute like you normally do.

In case of MultiDB, on the dialog you are used to enter the connectivity data for the SAP HANA database, you now have to enter the connectivity data for the specific database tenant. In this example, the SAP HANA database I installed is called MUL. But the name of the tenant inside shall be MU1.

As the tenant does not exist, an error message shows up. In one of the next deliveries of the software provisioning manager, it will be possible to create the tenant within the procedure.

Right now, you have to create the database tenant by hand using the SAP HANA studio or hdbsql.The statement for creating a tenant is shown above.

Once the tenant is created, the error will not appear again and you proceed to the next dialog. Here, you have to enter the password of the Administrator of the System database. That is the password you entered while you installed the SAP HANA instance. After this, the installation is the same as it is on a single SAP HANA database.

Unfortunately, you might encounter the following error during the installation:

The reason for this is a change in the version handling of SAP HANA. If you execute “R3trans –x” as user sidadm, you will receive the same error:

The trans.log would look similar to the following:

To fix this, you can simply update the dbsl in the exe directory of the new SAP system.

After that, the installation moves on after pressing the Retry button.

Hi All,

There are few incidents reported recently with error message:

ERROR: DB version 11.2.0.2.0 out of range (too low) Upgrade the database system at least to version 11.2.0.3.

When performing an upgrade of a NetWeaver (NW) based system using Software Update Manager (SUM). During the upgrade in the CHECKS phase an error is reported the database system version is too low.

The cause of this error is because Oracle Patchset 11.2.0.2 is out of maintenance, the SUM follows the strategy of the database vendor.  To resolve this please update the database Patchset to 11.2.0.3 or higher.

Best regards,

James Wong

This article is about the connectivity data of an SAP Netweaver ABAP instance which uses a SAP HANA instance as its primary database.

To get everybody on board, MDC stands for HANA Multi Tenant Database Containers which is available with SP9.

These are the parameters of the system:

SAP ABAP instance

Hostname of PAS:   plx101

SID:                         GTO

HANA database

Hostname:               ld2426

Instance number:     00

SID:                         MUL

SQL Schema:          SAPABAP1

The connection data to between the ABAP kernel and the HANA database instance is done via the so-called hdbuserstore which is part of the HANA client software.

The connection is always established via the userstore key with the name DEFAULT.

For non MDC HANA instances (single database instances), only the hostname and the instance number are necessary to build the connection string which is: <hostname> + 3 + <instance number> + 15 . In our case it is: ld2426.wdf.sap.corp:30015

In case of HANA Multi Database Containers it gets a little more complicated.

In case a HANA instance is installed as MDC it becomes the host for multiple instances which are called: Tenants.

To be able to provide seperate connectivity to each tenant, 15 can't be the only indexserver port. Due to this the connection string gets another variable:

<hostname> + 3 + <instance number> + <tenant port> . There is only one fixed tenant port which is 13 . This is the port to the so-called system database.

The system database is some kind of master tenant used only for administrative purposes like:

• creating, dropping tenants and
• starting or stopping tenants.

In case you are about to migrate your single database to MDC you don't have to worry about the connectivity.

The current port 15 will also be the port of the tenant which hosts all data of the former single database.

The HANA database from above is currently a single database instance:

After the upgrade to SP9 the migration to MDC is very simple.

As you see in the picture above the Statisticsserver process needs to get migrated to run inside the indexserver.
Check the note for more information: 1917938 - Migration of the statistics server for Revision 74 or higher

Once the Statisticsserver runs inside of the indexserver the process is gone.

Now the convertion to MDC can start after the HANA has been shutdown.

After that you have to add two new systems in HANA Studio.

1. System database:
   
   As user / password combination use: system / manager.
   
   After the system database is added you can start it. After the startup it looks like this:
   
2. After that add a second system, the tenant, which contains all data of the former single database.
   In case of converting a single database to MDC the name of tenant is the same as the SID which was used during the installation of the software.
   
   Use the known password for user system.

To start the tenant you have to run the following sql command in an SQL session using the system database:

Once the tenant has started the processes look like this:

Now you can test the connection from the SAP instance:

As the connection is still working the indexserver must still listen on the same port ?

Let's check:

That means the connectivity of the SAP system doesn't have to be changed.

In case additional tenants are created the SQL_PORT will be different:

and it also has its own indexserver process.

To get an overview about all tenants this query might be helpfull:

That's it for now.

Introduction

The purpose of this document is to provide a list of the top knowledge base articles (KBA's) from the Upgrade component.  I'll be including the top KBAs of the month and also the most recently added/updated KBAs and SAP Notes.  The goal here is to keep you up to date on the most frequently searched and the most recent added/updated UPGRADE issues that we are seeing in Product Support.

Please leave any feedback in the comments section.

Top Upgrade KBAs for November 2014

** The top KBA notes does not include SAP Notes because of a limitation on the system.

Recently Added/Updated Upgrade KBAs/SAP Notes

** The hyperlinks will require access to the SAP Service Marketplace **

This blog tries to provide an overview about how HANA Multitenant Database Container (MDC) is used in a Scale-out scenario.

Given a five node Scale-out system:

     ld9968 (Master), ld9969 (Worker), ld2431 (Worker), ld2432 (Worker), ld9970(Standby)

Scale-out scenario

In this Scale-out system there are three potential masternodes:

So from the perspective of the client application the userstore, which contains the connectivity data to the database, needs to have these three hosts to make sure it always gets a connect to a master node. So the userstore has to look like this:

If the Scale-out system is using Multitenant Database Containers the failover concept is still the same. That means if a master host fails another host takes over. During fail over the services are moved from the failing node to the node which is taking over.

Tenant creation

In the above system three tenants were created:

For creation enter the internal communication port. The SQL port will be port+1, the XS port will be port+2.

There is one exception though: internal communication port 03 -> SQL port 15 -> XS port 08.

Example: ld9968:3+<Instance Number>+<port> = ld9968:30040

This the overview about all tenants in that database.

Installation of the SAP systems

During installation of the three SAP systems the following entries were made on the database dialog:

Within software provisioning manager the connection to the HANA database is done via JDBC. The JDBC connection allows to use a database tenant name instead of the SQL port. By using the database tenant name the JDBC driver switches automatically to the corresponding database tenant. Due to this you have to enter the host where the system database is running which is the initial Master host. In this case it is ld9968.

<software provisioning manager installation directory>/HdbCmdOut.log:

...

....JdbcDriver | URI: file:/home/emroot/install/ngdbc.jar

....JdbcConnection | Start new connection with connect URL: jdbc:sap://ld9968:30013 connect user: SYSTEM

....JdbcConnection | Instance is a multitenant database.

....JdbcConnection | Start new connection with connect URL: jdbc:sap://ld9968:30013?databaseName=ERP connect user: SYSTEM

....JdbcConnection | Start new connection with connect URL: jdbc:sap://ld9968:30013 connect user: SYSTEM

...

The software provisioning manager recognizes that the instance is using MDC and brings up the dialog to enter the data for the System Database:

The same is for the other SAP systems:

For the SAP JAVA server the connectURL also contains the database tenant name. In this case it is:

jdbc:sap://ld9968:30013?databaseName=JAV

Unfortunately this only works as long as node ld9968 is available and hosts the system database which does the redirection to the tenant.

There should be a solution for this soon.

hdbuserstore

After the installation the hdbuserstore for the ERP and the BW system look like the following scrennshots.

In case of MDC unfortunately the current software provisioning manager only puts the first node into the hdbuserstore.
That means to have all relevant hosts in the userstore a manual adaption has to be made which is quite simple.

Logon as sidadm on the application host and run the command:

hdbuserstore set DEFAULT "ld9968.wdf.sap.corp:30041;ld2432.wdf.sap.corp:30041;ld9970.wdf.sap.corp:30041" SAPABAP1 <Password>

System BW9

System ERP

That means the userstore contains the initial host of the tenant plus the potential masterhosts of the Scale-out system.

Failover

To simulate the failover we simply shutdown the instance.

Again the complete overview of the system:

Now node ld2432 is shutting down.

ld2432:/usr/sap/OQT/HDB00/ld2432/trace > HDB stop

As ld9970 is the standby node all services from node ld2432 are moved to ld9970

Once the failover is complete:

The SAP system is still able to connect. The details can be checked in file trans.log.

After bringing the failing node back up it becomes the new standby node. To get to the initial layout a complete restart of the system is necessary.

During the system restart you might recognize that the indexserver services on ld9970 still exist:

Due to this the system might not come up completely:

To get around this simply restart the instance on node ld9970:

Once the instance is started the indexserver srvices are gone and the system should be green:

More information about MDC can be found in the SAP HANA Administration Guide

This post should give you an overview about the SAP HANA client software and the settings inside the hdbuserstore-container when you are using virtual hostnames for the SAP application server.

Presumed that the installation is done with the software provisioning manager.

To use virtual hostnames you have to add a parameter when you start:

/DVDs/IM_LINUX_X86_64/sapinst SAPINST_USE_HOSTNAME=<virtual hostname>

By using the parameter the <virtual hostname> will be used as server name:

sidadm>cdpro

sidadm>grep <virtual hostname> DEFAULT.PFL

SAPGLOBALHOST = <virtual hostname>

rdisp/mshost = <virtual hostname>

enque/serverhost = <virtual hostname>

Relating to SAP HANA two additional actions are done during the installation.

1. The SAP HANA client software will be installed with the additional parameter --hostname=<virtual hostname>
   You can check the file HdbCmdOut.log for this:
   
   By using the parameter a special file called installation.ini is created by hdbinst:
   
2. The hdbuserstore-container is created in a subdirectory named after the <virtual hostname>. For that the parameter -H <virtual hostname> is used.
   To see the call check file sapinst_dev.log:
   
   To see the content of the hdbuserstore container logon as sidadm and run the follwoing command:
   
   As you can see you also have to use the parameter -H <virtual hostname> to list the content of the hdbuserstore-container.

That means when the SAP kernel software loads the SAP HANA client software the content from file installation.ini is used to find the directory in the home directory of user sidadm to read the connection data from the hdbuserstore-container.

As the file installation.ini is unique there is a restriction to the SAP HANA client installation!
It is not possible to install the client software in the central directory of the SAP instance in case you are using the sapinst option SAPINST_USE_HOSTNAME

You might also want to check Oss-note: 2120226 for further information.

Hi All,

When performing an upgrade of a NetWeaver (NW) based system using Software Update Manager (SUM), there are few incidents reported recently with error message:

ERROR: DB version 11.2.0.2.0 out of range (too low) Upgrade the database system at least to version 11.2.0.3.

The cause of this error is because Oracle Patchset 11.2.0.2 is out of maintenance, the SUM follows the strategy of the database vendor.  To resolve this please update the database Patchset to 11.2.0.3 or higher.

Note:

For more information please refer to SAP Note 1503709 - Oracle 11.2.0: Patches / Patch collections for 11.2.0.2

Best regards,

James Wong

Hi All,

The SAP Support Portal is your one stop for all support and service-related needs: Use it to access your software, request license keys, get technical support, and find the documentation you need to run your business better.

The existing version had gotten rather long, so we've launched a brand new one based on your feedback. With the availability of the new SAP Support Portal, the Upgrade
Information Center has also moved.

SAP Upgrade & Innovations Newsletter

Stay up to date with the latest information and insight related to SAP Business Suite application upgrades, SAP innovations, support and maintenance and other related SAP offerings

Get started with the new SAP Support Portal

Access the new Upgrade Information Center

Best regards,

James Wong

Are you having an issue with one of the following tools/procedures and unable to decide which BC-UPG/BC-EHP sub-component you need to choose when creating your support incident?

• Upgrade (using SAPup/SAPJup/SUM)
• Update (using SPAM/SUM)
• Enhancement package installation using SUM

To help with the above problems, there is a Knowledgebase Article (KBA) created 1528337.

Here is a short guideline on how to choose the correct BC-UPG/BC-EHP sub-component.

After performing a Note search, use the component specified in the "Header Data" of the most relevant note returned.bIf note search does not help use the following guidelines, for issues:

• related to ABAP stack release upgrade using SAPup/SUM post an incident under BC-UPG-TLS-TLA support component.
• related to JAVA stack upgrade using SAPJup/SUM post an incident under BC-UPG-TLS-TLJ support component.
• related to ABAP support package import using SPAM you may use BC-UPG-OCS and BC-UPG-OCS-SPA.
• related to JAVA support package update using SUM you may use BC-UPG-OCS-SPJ support component.
• related to ABAP enhancement package installation you may use BC-EHP-INS and BC-EHP-INS-TLA.
• related to JAVA enhancement package installation using SUM you may use BC-EHP-INS-TLJ support component.
• related to ABAP Addon import using SPAM you may use BC-UPG-ADDON.

Note:

For more information please refer to SAP Note 1528337- Choosing correct BC-UPG/BC-EHP sub-component

Related KBAs:

When performing an SAP system upgrade, the information you obtain from warning messages and error log files will often only help you diagnose the issues without providing a remedy. In order to help you perform smoother SAP system upgrades, we have developed the SAP System UPGRADE & UPDATE Troubleshooting Guides to guide you through the steps you could take to solve the problems.

This blog contains information and hyperlinks to the guides that would help you troubleshoot the problems you encounter with your SAP System upgrade. It has been split up into six categories.

1.      Note Assistant
2.      SAPJup
3.      SPAM and Saint
4.      SUM for ABAP
5.      SUM for JAVA
6.      JSPM

The following table lists out the six categories and their subtopics that make up the UPGRADE System troubleshooting guides.

Note: Not all troubleshooting guides are complete yet.  Please revisit those pages again as we are currently working on those contents.

For more information, please visit the SAP System Upgrade & Update Troubleshooting Wiki Space.  This Wiki Space includes information needed before a system upgrade & update. Information includes:

• Upgrade troubleshooting guides in Wiki Space
• Latest News
• PS Social Media Channel (Product Support Facebook page, Twitter page , Weibo blog, YouTube channel)
• Meet-the-Expert sessions (MTE)
• Tools supporting upgrades and enhancement package implementations
• Release, Upgrade and Maintenance Information
• List of Feature SAP Notes / List of Feature SCN Blogs

Please bookmark this page if you wish to regularly check for updates.

Your feedback is important to us. It will allow us to continuously improve the troubleshooting guides and progressively improve the experience we deliver to you.  Please make use the comment section below to send us your feedback and ideas on how we could improve.