SAP on IBM i Rock Solid on...SAP on IBM i Practice, ... Supported with SAP NetWeaver 7.0 and higher ... SAP Memory Management Changes Starting with 7.4 Kernel

SAP on IBM POWER Summit DACH 2016 - © IBM Corporation 2016

Taking Your SAP Environment Forward

Kolby Hoelzle ([email protected])

SAP on IBM i Practice, IBM Systems Lab Services

SAP on IBM i – Rock Solid

mailto:[email protected]


Agenda

IT planning considerations

Leverage existing technology and capability

Overcoming barriers to progress


IT Roadmap – Planning for the Future

Driven in large part by the business

Must be reconciled with current technology and

expected future technology

Will continue to evolve as both the business and

technology change


IT Roadmap – Challenges

Certainty diminishes the further out in the future

that you have to plan

No direct control over some dependencies in

roadmap

Regardless of future plans (strategic), still need to

meet the needs of the business (and IT) today and

moving forward (tactical)


Evaluate the Current State of IT

Where am I today– What is the capability and capacity of my technology

– What is the capability and capacity of my staff

– Is it adequate to meet short-term, mid-term, and even long-

term plans

What barriers or limits do I have– Are there current or anticipated technological limitations

– Are there current or anticipated barriers to growth

– How do I anticipate the impact these barriers or limits will

have in the short term, mid term, long term


Evaluate the Current State of Your SAP Environment

Where does my SAP landscape need to be in the short-

term, mid-term, and long-term– What technologies do I have access to (through upgrades,

configuration, etc…)

– Are there technologies that are not being fully leveraged

– What barriers or limits can be mediated or eliminated

Position your SAP environment for running your business

today and be flexible to adapt to uncertainty in the future


Position Your SAP on IBM i Environment for the Future

Extend capability

Enable flexibility

Mediate barriers to progress and growth


Power Systems – Capability, Flexibility, and Scalability

Supports multiple enterprise operating system concurrently– Same skill set to manage server, regardless of operating system

Power 8 – unparalleled capacity in both scale up and scale out

Proven enterprise class reliability

Cloud enabled (advanced virtualization)


Keep Operating System Current

Current operating system releases and TRs enable most current

technology– Much new OS technology integrated by the SAP on i development team

– Removes technological obstacles for upgrades

– Enables support for latest hardware

– Allows for increased flexibility and scalability

Many OS features integrated and require no additional effort to leverage

……7.3 ………

2010

7.1

2014

i next

2016

…7.2

…Technology Refreshes


Installing or Upgrading to IBM i 7.3 with SAP

SAP NW Release Min. SAP Kernel Min. Patch Level

6.40 or older Supported up to IBM i 7.1

7.0x, 7.1x, 7.2x, 7.3x 7.21 EXT 616

7.40, 7.50 7.45 100 (≥ 113 for best performance)

New SAP installation on IBM i 7.3

Upgrade to IBM i 7.3 with an existing SAP installation (direct upgrades from 7.1 and 7.2 possible)

7.3

7.1Kernel: 7.2x → 7.21 EXT / 7.22 EXT

7.4x → 7.45

7.26.1


Key Statements for IBM i 7.3

General availability IBM i 7.3 as of April 15th, 2016

Certified by SAP since April 22nd, 2016

Supported with SAP NetWeaver 7.0 and higher

Supported SAP kernel releases: 7.21 EXT, 7.22 EXT, 7.45, and 7.49

More Information:

SAP support required PTF list for IBM i 7.3: II14816

SAPNote 2299407 – “Known Issues with OS Release IBM i 7.3”

http://service.sap.com/sap/support/notes/2299407


Operating System Upgrade Reference

SAP Notes for IBM i 7.1 (1432783), IBM i 7.2 (2011710), and IBM i 7.3 (2299407)

Review Techdocs– Check best practices

SAP on IBM i Recommendations and Review

– Clean up and archive old data Exploit Storage Resources for SAP on IBM i

Capture performance metrics for later comparison (if needed; include a typical day

and important peak periods)– IBM Insight for SAP

– IBM i Performance Collector data

– Plan cache (or SAP Database Performance Collector, according to SAPNote 1622665)



https://service.sap.com/sap/support/notes/2299407

https://www-03.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/WP101697

http://www-03.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/WP102202

https://www-356.ibm.com/partnerworld/wps/servlet/ContentHandler/techline/FAQ00000867



Leverage the Full Potential of the Database

Stay current with DB group PTF and TRs

Stay current with SAP kernel patches

Train a Database Engineer (DBE) that is familiar with DB2 optimization

and SAP– Regularly analyze and tune top ‘n’ queries


SAP Specific Transaction Data Stored in DB Plan Cache

SAP application information stored

in database plan cache– 7.2x EXT, 7.4x, or later kernel

required

– See SAPNote 2196060 for details

SAP application name, SAP user,

and SAP source code information

stored for each query

Data can be retrieved directly from

plan cache or SAP interface

Filter SQL statements from SQL plan cache dump to a specific

SAP program, SAP user, transaction or application server



Keep Your SAP Configuration Current

Leverage integrated enhancements

Avoid obstacles to upgrades– New user concept

– New memory model

– Current kernel patch level

– Standalone enqueue

– Unicode

Extend capabilities


SAP Kernel and IBM i Release Support November 2016

Kernel

OS7.20

7.20

EXT7.21

7.21

EXT7.22

7.22

EXT7.40 7.41 7.42 7.45 7.49

V5R3 Base Base

V5R4 Base Base Base

IBM i 6.1 Base Base Base

IBM i 7.1Patch

49

Patch

49Base Base Base Base Base Base Base Base Base

IBM i 7.2Patch

300Base

Patch

31Base Base Base

IBM i 7.3Patch

626

Patch

101

Patch

100Base

SAP Note 68440 – IBM i: How do I upgrade to a later OS release?

Color code: Supported No longer in maintenance DCK 12/2016 – SAP Note 2350788

https://launchpad.support.sap.com/#/notes/68440/

https://launchpad.support.sap.com/#/notes/2350788/


Standalone Enqueue Server

Central instance

DISP_WORK (ABAP Dispatcher)

MSG_SERVER (Message server)

GWRD (Gateway server)

WP00 (Dialog process)

WP01 (Update process)

WP03 (Background process)

WP02 (Enqueue server)

WP04 (Spool process)

WP05 (Update 2 process)

Primary app. server instance

DISP_WORK (ABAP dispatcher)

GWRD (Gateway server)

WP00 (Dialog process)

WP01 (Update process)

WP02 (Background process)

WP03 (Spool process)

WP04 (Update 2 process)

ASCS instance

MSG_SERVER (Message server)

ENSERVER (Enqueue)

SWPM ≥ 1.0 SP06 → SAP NetWeaver → Database →

Additional SAP System instances → Split off ASCS Instance

From Existing Primary Application Server instance

SAP Note

2013043



SAP Memory Management Changes Starting with 7.4 Kernel

Value of PHYS_MEMSIZE set based on physical memory– PHYS_MEMSIZE should be set manually if running more than one

SAP system on the same partition

Other memory parameter values calculated automatically from

PHYS_MEMSIZE

Automatically calculated values can be overridden with explicitly

set parameter valuesSAP Note

2085980



Rolling Kernel Switch

More information at Technical Operations for SAP NetWeaver →Administration of Application Server ABAP → Rolling Kernel Switch

Enqueue Replication Server (ERS)

Version 1 Version 2Restart

ASCS Instance

Version 1

Message Server

Enqueue Server

SAP Start Service

Version 2

Message Server

Enqueue Server

SAP Start Service

Restart

Application Server – Instance A

Version 1 Version 2RestartApplication Server – Instance B

Version 1 Version 2Restart

Application Server – Instance C

Version 1

SAP Start Service

Version 2

SAP Start Service

Restart

1

2

3

4 5

Controlled by SAP MMC

MMC picks „last instance“

SAPSTRSRV of last instancecontrolling order of restarts

ERS restarted first

ASCS restarted second

Application servers one by one

http://help.sap.com/saphelp_nw74/helpdata/en/e5/b90c44bd7247cda44c4f66819ce21f/frameset.htm


Setting up Rolling Kernel Switch

Separate central services (message and enqueue server) and dialog instances

Setup enqueue replication server Configure usage of sapcpe Kernel release 7.20 patch 78 or later (see SAP Note 953653) Manual restart of ASCS needed prior to 7.40 SP05 (kernel: 7.41) Logon balancing: Use profile parameter

lg/rks_strategy=prefer_restarted

ApplicationServer <n>

ApplicationServer 1

PrimaryApplication

Server

Enqueue ReplicationServer

ERS

Central Services(Message & Enqueue Server)

ASCS

...



Planning for an SAP Upgrade

Meet Minimum Requirements for Source and Target Combination• OS release• Kernel release• New user concept• Unicode only (NW 7.5 / ERP 6.0 Ehp 8 and later)• No central instance (NW 7.5 / ERP 6.0 Ehp 8 and later)• No dual stack (NW 7.5 / ERP 6.0 Ehp 8 and later)

Select Upgrade Option• Standard• Reduced downtime options• Inplace Unicode conversion followed by upgrade• Combined upgrade and Unicode conversion (CU+UC)


Upgrade Options

Standard

Near Zero Downtime Maintenance (nZDM)

Zero Downtime Option (ZDO)– ZDO option still in development

All upgrade options use the Software Update Manager (SUM)


Standard Option

SUM based

Least restrictive option

Could be only option depending on SAP product, source release, and

target release

Highest amount of downtime, but lowest amount of overall time


Reduced Downtime Options

All options require downtime, even ZDO– SAP categorizes downtime as technical and business downtime

Technical downtime refers to the actual maintenance

Business downtime encompasses any time when the system is unusable for the

business and includes technical downtime

– ZDO eliminates the technical downtime, but business downtime still exists and

must be planned for

Reduced downtime options typically extend the overall time for an

upgrade– More time is spent during uptime phases, which tends to extend the overall

upgrade time even though downtime is reduced.


Near Zero Downtime Maintenance (nZDM)

Uptime UptimeBusiness downtime

UptimeUptime Bus. downtime

Online delta replay(trigger-based)

XPRA, AIMexecution part 2

Standard

nZDM


Capabilities of nZDM

Parallel batch processing, DDL processing and R3TRANS Main import moved to uptime SGEN in the shadow instance Inclusion of customer transports (per support incident on component

BC-UPG-OCS-ZDM, see SAP Note 1759080)

In some environments: Phase TABIM_UPG reduced from 5-7 hours to ~2 hours!



nZDM Upgrade Reference

Prerequisites– IBM i 7.1 + cumulative fix pack level 13298 (C3298710)

– LIB_DBSL patch level:

– Release 7.20 LIB_DBSL patch level 519



– Profile parameter dbs/db4/auto_dsql_schema=1

– Software Logistics Toolset 1.0 SP10 (new user concept required)

Documentation– Blog entry: SAP on IBM i - Update week 18 2014: nZDM option for i

– Document: Near-Zero Downtime Maintenance for SAP Business Suite Systems

– Document: Settings to activate downtime minimization capabilities in SUM

– SAP Note 1678565 – Prerequisites, Terms and Conditions for nZDM/SUM

– SAP Note 1678564 – Restrictions, Settings and Troubleshooting of nZDM/SUM

– SAP Note 1809339 – IBM i: Support by nZDM/SUM for IBM i

http://scn.sap.com/community/ibm-i/blog/2014/04/30/sap-on-ibm-i--update-week-18-2014-nzdm-option-for-i

http://scn.sap.com/docs/DOC-32544

http://scn.sap.com/docs/DOC-49957





System Limits

All computer system have limits– Physical limits (memory, storage, CPU, etc…)

– Architectural limits (file size, field length, object name length, etc…)

– Configuration limits (memory pools, Java heap size, etc…)

Some times the architectural limit is the physical limit– For example, max number of tables and max number of schemas

In some cases, a physical limit may be reached before an architectural

limit– For example, table size


IBM i and DB2 for i Limits

Many limits are so large that they are never encountered

Often times, administrators don’t even realize that architectural limits exist

A data explosion, leading to increasingly larger databases is pushing

some systems closer and closer to limits


What Happens When a Limit Is Reached?

In most situations, the system continues to run– Objects impacted could be limited in how they are used

In some rare circumstances the system becomes unusable– For example, filling up the system ASP

It Depends!


Limits Sometimes Encountered with SAP Workloads

SQL package size – limit 1 GB

Table size – limit approximately 1.7 TB

Number of rows – limit approximately 4.2 billion rows

Number of variable length (AUX) segments – limit 65533


Tracking System Limits

Starting in IBM i 6.1, tracking system limits became much easier

System enables limit tracking for a resource when consumption exceeds

a defined “floor” and when an “increment” is met

Tracked data is stored within a DB2 table (QSYS2.SYSLIMTBL)

Tracking and storing system limit data allows you to:– Know when you are approaching a limit (instead of waiting for an error)

– See trends and take action

– Find high water marks for each limit


Monitoring System Limits Through SAP Interfaces

• Display catalog SYSLIMITS in QSYS2.

• Overview with current and maximum value.

• Break-down to processes or objects when possible.

• Selection „Pruning Controls“ available as of IBM i 7.1 for cleanup options.


IBM i and DB2 for i Limits References

IBM i Maximum Capacities:

http://www.ibm.com/support/knowledgecenter/ssw_ibm_i_71/rzamp/rzampoverview.htm

DB2 for i SQL limits:

https://www.ibm.com/support/knowledgecenter/ssw_ibm_i_71/db2/rbafzlimtabs.htm

Tracking Important System Limits:


http://www.ibm.com/support/knowledgecenter/ssw_ibm_i_71/rzamp/rzampoverview.htm




Overcoming Barriers to Growth – Some Options

Housekeeping– SAP standard housekeeping jobs

– OS housekeeping

Archiving– Requires detailed planning and coordination with the business

– Considerations for business requirements, compliance and regulations,

expectations, storage and performance

– Non trivial process

Partitioning– Considerations for design and implementation methods

– Very Large Database (VLDB) workshop recommended

http://help.sap.com/saphelp_erp60_sp/helpdata/en/d2/36e2791560ed4a96e97a3175694886/content.htm


SAP Housekeeping References

SAP Note 16083 – Standard Jobs, Reorganization Jobs

SAP Note 1411877 – New Standard jobs

SAP Note 1440439 – New Standard Jobs (2)

SAPNote 706478 – Cleanup of Basis Tables

SAP Note 70643 – Old Upgrade Directories and Client Deletion (SCC5)

SAP Note 147354 – Batch Input Reorg and Delete

SAP Note 41732 – Deletion of Data in Transport Directory

Whitepaper – Exploit Storage Resources for SAP on IBM i

SAP Note 1449715 – IBM i: Current Recommendation for Journal Configuration

SAP Note 84081 – IBM i: Reorganization of Database Tables (RGZPFM)




https://launchpad.support.sap.com/#/notes/0000706478




http://www-03.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/WP102202




Table Partitioning Reference

5770SS1 Option 27 – DB2 Multisystem require– Try and buy option available

Contact Rob Bestgen ( [email protected] ) or Scott Forstie (

[email protected] )

DB2 for i Very Large Database (VLDB) workshop and assessment

SAPNote 2187681 – IBM i: Table partitioning in non-BW systems

SAP Transaction TAANA – Table Analsys: Administration



https://ibm.box.com/v/vldb-workshop


SAP on IBM i Online Resources

SAP Community Network: SAP on IBM i

SAP on IBM i Newsletter

Social Media: LinkedIn – SAP on IBM i User Group

SAP on IBM i Portal

Twitter

SAP on IBM i Info APAR Notification

www.ibm.com/developerworks/ibmi/sap

go.sap.com/community/topic/ibm-i.html

www.twitter.com/saponibmi

www.linkedin.com/groups?home=&gid=4841927

www-03.ibm.com/systems/power/software/i/support/sap_form.html

Send e-mail to [email protected] to be added to distribution list

http://www.ibm.com/developerworks/ibmi/sap

https://go.sap.com/community/topic/ibm-i.html

http://www.twitter.com/saponibmi

http://www.linkedin.com/groups?home=&gid=4841927

http://www-03.ibm.com/systems/power/software/i/support/sap_form.html



Summary

Regardless of strategic long term plans, business continues and IT needs

to support it

Position IT infrastructure for flexibility, adaptability, and extended

capability

Leverage capabilities of technology that is either in-place or easily

transitioned to

Identify and remediate barriers or limits to progress


Questions? – Thank You!

Contact: Kolby Hoelzle ( [email protected] )

See our blog and discuss with us at http://go.sap.com/community/topic/ibm-i.html


http://go.sap.com/community/topic/ibm-i.html


Legal Information – Please Note

IBM’s statements regarding its plans, directions, and intent are subject to change or withdrawal without notice at IBM’s sole discretion. Information

regarding potential future products is intended to outline our general product direction and it should not be relied on in making a purchasing decision.

The information mentioned regarding potential future products is not a commitment, promise, or legal obligation to deliver any material, code or

functionality. Information about potential future products may not be incorporated into any contract. The development, release, and timing of any future

features or functionality described for our products remains at our sole discretion.

Performance is based on measurements and projections using standard IBM benchmarks in a controlled environment. The actual throughput or

performance that any user will experience will vary depending upon many factors, including considerations such as the amount of multiprogramming in

the user’s job stream, the I/O configuration, the storage configuration, and the workload processed. Therefore, no assurance can be given that an

individual user will achieve results similar to those stated here.

Availability. References in this presentation to IBM products, programs, or services do not imply that they will be available in all countries in which IBM

operates.

The workshops, sessions and materials have been prepared by IBM or the session speakers and reflect their own views. They are provided for

informational purposes only, and are neither intended to, nor shall have the effect of being, legal or other guidance or advice to any participant. While

efforts were made to verify the completeness and accuracy of the information contained in this presentation, it is provided AS-IS without warranty of any

kind, express or implied. IBM shall not be responsible for any damages arising out of the use of, or otherwise related to, this presentation or any other

materials. Nothing contained in this presentation is intended to, nor shall have the effect of, creating any warranties or representations from IBM or its

suppliers or licensors, or altering the terms and conditions of the applicable license agreement governing the use of IBM software.

All customer examples described are presented as illustrations of how those customers have used IBM products and the results they may have

achieved. Actual environmental costs and performance characteristics may vary by customer. Nothing contained in these materials is intended to, nor

shall have the effect of, stating or implying that any activities undertaken by you will result in any specific sales, revenue growth or other results.


Legal Information – Trademarks, Copyrights

Information contained in this material has not been submitted to any formal IBM review and is distributed on “as is” basis without any warranty either

expressed or implied. The use of this information is a customer responsibility.

IBM MAY HAVE PATENTS OR PENDING PATENT APPLICATIONS COVERING SUBJECT MATTER IN THIS DOCUMENT. THE FURNISHING OF

THIS DOCUMENT DOES NOT IMPLY GIVING LICENSE TO THESE PATENTS.

The client examples cited are presented for illustrative purposes only. Actual performance results may vary depending on specific configurations and

operating conditions. It is the user’s responsibility to evaluate and verify the operation of any other products or programs with IBM products and

programs.

IBM, the IBM logo, ibm.com, AIX, BatchPipes, BladeCenter, DB2, DB2 Connect, Netezza, GDPS, GPFS, Netfinity, Intelligent Miner, OpenPower,

Parallel Sysplex, POWER, RACF, Redbooks, RETAIN, System Storage, System p, System x, System z, Tivoli, WebSphere, zEnterprise, z9, z10, and

z/OS are trademarks or registered trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. A current list of

IBM trademarks is available on the web at “Copyright and trademark information” at: http://www.ibm.com/legal/us/en/copytrade.shtml

Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

Oracle and Java are registered trademarks of Oracle and/or its affiliates.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

SAP, R/3, SAP NetWeaver, ByDesign, SAP BusinessObjects Explorer, StreamWork, and other SAP products and services mentioned herein as well as

their respective logos are trademarks or registered trademarks of SAP SE in Germany and other countries.

All other product and service names mentioned are the trademarks of their respective companies.

Data contained in this document serves informational purposes only. National product specifications may vary.

http://www.ibm.com/legal/us/en/copytrade.shtml

Documents

SAP on IBM i Rock Solid on...SAP on IBM i Practice, ... Supported with SAP NetWeaver 7.0 and higher ... SAP Memory Management Changes Starting with 7.4 Kernel