Skip to Content

SAP on Oracle Solaris News Archive

Solaris, SPARC, and Compliance Technology Updates Available for Download

Oracle had three partner sessions at this year's TechEd EMEA in Amsterdam to give an update on latest developments in the Solaris platform area. You can see the presentations here:
If you have questions, feel free to contact us directly.

Oracle Exalogic Now Available with Solaris for SAP Software

Tests for SAP software running on Exalogic with Solaris have been successful. Official support is now documented in SAP Note 1617188 - SAP Software and Oracle Exalogic.
The main minimum requirements are:
  • Oracle Solaris 11.1 SRU 3.4
  • SAP NetWeaver Kernel 7.20_EXT
  • Oracle Client on Exalogic
  • Oracle Database Server on Exadata
For more information on Exalogic, see Oracle Engineered Systems for SAP: Exalogic.

Oracle Directory Server Enterprise Edition 11g (formerly Sun Directory Server) Certified by SAP

Oracle Corporation announced on December 12, 2012 that its Oracle Directory Server Enterprise Edition 11g (ODSEE) has achieved SAP certification as powered by the SAP NetWeaver technology platform, based on the SAP integration scenario BC-LDAP-USR 630. The solution has been proven to integrate with SAP® solutions, providing secure, high-available, scalable directory services for storing and managing accurate and reliable identity data with SAP systems. This successfully completed integration certification project is now listed online in the SAP Partner Information Center or here.
For more product-related information, see

SAP Now Released on Oracle Solaris 11 for both Solaris SPARC and Solaris X64

After the initial SAP release, we now support Solaris 11 with a main SAP release for the Oracle and SAP MaxDB databases, subject to the following requirements:
  • Oracle database version with Oracle Client
  • SAP MaxDB version 7.8 or 7.9, depending on the SAP application release

The supported SAP releases are offered for SPARC and X64 and start with products using SAP Kernel 6.40 and upwards. All releases prior to SAP Netweaver 7.0 require Kernel 640EX2; as of NW 7.0, the 720_EXT Kernel is required.
For more information on how to install SAP on Solaris 11, see SAP Note 1669684 "SAP on Solaris 11".
For more information on product versions supported by SAP, see the SAP Product Availability Matrix (PAM).

SPARC SuperCluster Supported by SAP

SAP now supports the following configurations:

  • SAP on SPARC SuperCluster has the same basis as other SPARC SuperCluster configurations - either a full rack or a half rack with 4 or 2 T4-4 with storage cells and a ZFS storage appliance.
  • There are two LDPMs on each T4-4:
    • One with Solaris 11 for the Oracle RAC database
    • One with Solaris 10 for the SAP application server, ASCS or SCS
      (Solaris 11 for the application server on the SuperCluster will be supported later this year)
  • Oracle Solaris Cluster 3.3 provides high availability for the SAP system.

For more information, see these SAP Notes (SMP login required):

·        Note 1693680 - Running SAP Software on Oracle SPARC SuperCluster

·        Note 1696570 - Oracle SPARC SuperCluster: Patches for

·        Note 1696716 - Creating a modified Solaris kernel medium

This includes Unicode and non-Unicode versions as well as SAP kernel 6.40 and higher (the SAP Notes provide more information).

Share Ideas and Information by Joining a Solaris Special Interest Group

If you would like to get more information faster, share ideas and experience amongst your peers, we encourage you to join one of the Solaris Special Interest Groups (SIGs). There is one in the US/Americas and another one being set up in Germany (in German). These SIGs are by SAP customers for SAP customers they are completely independent of SAP or Oracle.

You can register for the new SIG (German "Arbeitskreis") at the German SAP User Group. You can find the SAP on Oracle/Solaris SIG here

Deploying SAP NetWeaver Master Data

Management on Oracle Solaris Containers

SAP NetWeaver Master Data Management offers a flexible solution that provides centralized access to master data across the enterprise. SAP NetWeaver Master Data Management aggregates master data from disparate sources, both SAP and non-SAP, using predefined or customizable data models for customers, vendors and suppliers, employees, products, material, and so forth. You can import entire master data schema or structures, as well as master-data values and taxonomy information. During data cleansing, you can carry out various operations, such as deduplication and normalization, ID mapping, matching and merging, staging, interactive data-quality analysis, and ad-hoc consolidation services. SAP NetWeaver Master Data Management harmonizes master data using a powerful syndication model that updates master data in systems running SAP and non-SAP software. Syndication uses industry standard XML and can be configured to run interactively or automatically.

By using Oracle Solaris Containers technology, the customers of SAP NetWeaver Master Data Management can consolidate the SAP NetWeaver Master Data Management server and database server, or multiple SAP NetWeaver Master Data Management servers on a same physical server irrespective on how to allocated the CPUs and memory resources. Oracle Solaris is able to allocate them automatically depending on each zone consuming. The SAP NetWeaver Master Data Management installation process on a local zone is the same as on a physical server making the zones technologies transparent to the user. Thus, the customer is able to enjoy more flexibly, higher efficiency and lower cost of ownership.

For more information, please go to

This document describes how Master Data Management server behaves into Oracle Solaris Containers. We'll describe how to install Master Data Management into a local zone, how to achieve maximum system utilization while running SAP NetWeaver Master Data Management in a local zone and what are the advantages of Master Data Management customers when using Oracle Solaris Containers technology.

11 Aug 2010

Expert Tip for SAP Users: Reduce Downtime of Your SAP NetWeaver Portal

Oracle‘s Upgrade Approach Avoids Interruptions to Your Ongoing Operations

Our global economy is generating a demand for more round-the-clock services, shrinking the time available for even scheduled system downtime - the majority of which is for updates and system maintenance. Yet updates are a complete necessary part of keeping a business both innovative and competitive. So what IT needs is a balance - IT managers must now look for ways to limit their portal downtime during an update without cutting back on the upgrade‘s scope.

Minimize the Downtime of your SAP NetWeaver Portal for Your Next Major Update

To decrease the length of an update, SAP and Oracle Sun have developed a best practice upgrade approach that uses Solaris Containers and Solaris ZFS, which are innovative virtualization technologies that are included in the Solaris 10 operating system. This procedure helps to reduce the overall SAP environment‘s downtime during an update and enhance the efficiency of IT operations.
Let‘s look at an example of Oracle‘s approach: Many companies are performing or planning a SAP NetWeaver Portal update and they often allow only a certain amount of downtime for it. But IT can minimize this downtime by using Solaris Containers and ZFS to complete five critical steps (see figure):

Step1: Start the process: Using LM-tool to switch to Maintenance Mode

Step 2: Create a clone. Using Solaris Containers with Solaris ZFS, create a clone of the portal environment. This step does not impact the operational process of the source system.

Step 3: Upgrade the clone. Perform the software upgrade on the clone environment. During this process, the original production system will still be available to the users. End-Users can still access the source system; either in Read-Only or in Record&Replay mode. Administrators can perform maintenance work on the cloned system.

Step 4: Switch source to the clone. Setup replication and "replay" changes. After successful testing and quality assurance on the clone environment, switch all users to the cloned, Updated system. End-users now work on the new software version

Step 5: Work continues uninterrupted.
New: while there was before a window where users could apply changes to the original system, which were lost when they switched to the new Updated system, now it is possible to log the changes and apply them to the new, Updated cloned system, and thus have virtually zero downtime.

Because in many cases SAP NetWeaver Portal environments do not store dynamic data, no data is lost when you switch from the source to the cloned, Updated environment. This way, the switch from one system to the other does not impact the end user. The clone behaves identically to the original and is readily available for full use - only the clone‘s IP address is different. Thus, the clone environment can be redefined as primary environment after the Update by changing the domain system name entry.

Additionally, the clone functionality works with any Solaris Container, so users can apply cloning to other SAP NetWeaver components for QA, training, and backup.

Oracle‘s upgrade approach using Solaris Containers helps customers reduce system downtime; using it, companies can take advantage of any new SAP functionality without worrying about slowing down their day-to-day operations.

Expert-Tip for SAP Users: How to use Solaris eTude for early SAP applications

Introduction: Solaris eTude started as an internal project of the Sun Solaris team which you can use to your benefits as well. It has been developed as a Solaris 8 Migration Assistant.
It is based on the most powerful OS virtualization technologies, Solaris Containers. Solaris has for many years supported running multiple operating system images on high end SPARC enterprise servers with hardware domains. Solaris Containers run not only on our high-end SPARC servers, but on any SPARC server, as well as on x86 servers from Sun, IBM, Dell, HP and other vendors.

To date, however, Solaris Containers have only supported applications that are already running Solaris 10. So Sun engineers developed something called BrandZ . BrandZ is a framework that extends the Solaris Containers infrastructure to create Branded Containers, which are containers (also called zones) that contain non-native operating environments. To allow Solaris 8 applications to run in a Solaris 10 container this BrandZ technology is used. While many Solaris 8 customers have already completely migrated to Solaris 10, we still have a number of customers running old Solaris 8 applications, like SAP customers who are running some older versions of SAP still in Solaris 8 or 9. Sometimes those apps are planned for near-term retirement and it doesn't make sense to migrate them fully to Solaris 10. In other cases the customer plans to migrate the application but has a shorter term need to reduce cost and complexity and would like to consolidate an older Solaris 8 based application onto a newer, more efficient hardware platform, i.e. latest server technology with higher performance and less cost.

Oracle will fully support Solaris 8 applications running with the Solaris 8 Migration Assistant when the customer purchases a Solaris 8 Migration Services package, as well as the underlying Solaris support subscriptions.
For productive use you need of course the approval of SAP as well.

Please provide feedback:
Please let us know whether you find this helpful for your SAP use; are you using this feature already or do you plan to use it?
If we would make this available for the next Solaris version, would you find this interesting and plan to use it (Solaris 10 based applications running in a Solaris-next container)?
Please provide information to or alternatively to

Configuring SAP BusinessObjects for Scalability and Performance on Oracle Systems

Thomas Schuele, Sherry Yu, Oracle Systems

The Oracle Sun Business Intelligence Solutions integrate specific services around Extraction, Transformation and Loading, Database, Reporting, On-Line Analytical Processing, Technical architectures, Proof-of-Concept and Benchmarks. Together with partners around the world, Sun - until February 2010, since then Oracle Systems - has developed a network of competencies and expertise in Business Intelligence and Data Warehousing. In this context, engineering teams from Sun performed extensive performance analysis, tests and tuning of SAP BO systems running on Solaris and Sun Servers with the help of engineering teams from SAP and SAP COIL
The resulting Technical Blueprint "Configuring SAP BusinessObjects for Scalability and Performance on Oracle Systems"
helps you to improve performance and provides best practices to customers on how to configure and run SAP BO on Oracle systems and Solaris and can be found here.
This blueprint is targeted at technical IT managers and system architects who are responsible for implementing, managing, or recommending SAP BusinessObjects solutions.

Oracle Virtualization Technologies and the SAP NetWeaver Adaptive Computing Controller

Implementing SAP landscapes using Oracle virtualization technologies can help IT organizations reduce costs, respond to green computing initiatives, and improve service levels. For example, Solaris Containers enable multiple applications-including SAP product components such as SAP R/3 Enterprise applications, application server, and database servers-to each run securely on a single virtual system, potentially improving IT efficiencies and reducing costs. The SAP NetWeaver Adaptive

Computing Controller manages all of the SAP instances across containers within a predefined SAP NetWeaver Adaptive Computing Controller pool.

Learn how the combination of the SAP NetWeaver Adaptive Computing Controller and Solaris Containers allows IT administrators to quickly respond to increasing demand, and to flexibly utilize excess capacity from otherwise idle servers.

Using the Solaris Operating System to Upgrade SAP Environments

This document uses concrete examples to describe the architecture of a system landscape based on SolarisTM Containers and Solaris ZFS technologies. This architecture allows enterprises running Solaris to operate an SAP environment at lower cost in a more flexible way, while retaining high availability. It is the objective of this
architecture to minimize operating expenditures pertaining to administration, complexity, and down time.

The Sun SPARC Enterprise T5440 Server delivers New Four-Processor Record on Two-Tier SAP Sales and Distribution (SD) Standard Application Benchmark.

The Sun SPARC Enterprise T5440 server (4 processors/32 cores/256 threads) running the Solaris 10 OS and Oracle(R) Database 10g delivered the highest four-processor result on the two-tier SAP® Sales and Distribution (SD) Standard Application Benchmark, an industry standard measure of ERP performance. This breakthrough score confirms the Sun SPARC Enterprise T5440 server as the leading four-processor server on the two-tier SAP SD benchmark running the new SAP enhancement package 4 for the SAP ERP 6.0 application (Unicode), as of July 21, 2009

The Role of Solaris in Support of SAP Enterprise Applications

The current environment represents the next in the series of challenges that demand a new structure for the enterprise computing platform. Cloud computing offerings at various levels of the software stack, the viability of virtualization at scale, new generations of enterprise software such as SAP Business Suite 7, and the increasing corporate emphasis on Green IT and sustainability are forces sufficient to initiate a new era of platform restructuring. When these forces are amplified by an economic downturn, the urgency of defining a new computing platform rises dramatically.
This paper briefly surveys the forces driving IT departments to re-design their computing platforms, examines the various design issues at hand, and provides a detailed analysis of the role that the Solaris operating system can play in meeting the new requirements.

Leveraging the Power of Solaris 10 on Intel Xeon Processors for SAP Solutions

Learn how the innovative features of the open source Solaris 10 OS-DTrace, Solaris Predictive Self Healing, Solaris Containers, and the ZFS file system-supply the foundation for building, deploying, and managing efficient, secure, and reliable enterprise-class SAP environments.

You'll also learn how the Solaris Operating System, the first commercial OS release optimized for the Intel Core Microarchitecture, can help improve manageability and resource utilization with its sophisticated services for an SAP environment.

Get the details in this recently released white paper.

Former Member

No comments