Basis and others: Note 105047 - Support for Oracle functions in the SAP environment

Summary

Symptom
You want to use an Oracle feature that is not used in the standard SAP system.
Other terms
Dataguard, Data Guard
Reason and Prerequisites
This note provides answers to questions concerning the possible use of certain Oracle products and options that are not used in the standard R/3 system.
This note relates to the SAP products that are based on the SAP Web Application Server and SAP NetWeaver (including all SAP R/3 versions). Other rules may apply to other products (for example, those that are included in the SAP product portfolio due to acquisitions by SAP (such as Business Objects products)). If you have questions about these SAP products, you must clarify these on a case-by-case basis by creating a customer message.
Solution
This note provides information about Oracle features and tools that are not used at all in the SAP standard system or whose use is restricted in the SAP standard system. If you want to use a feature that does not appear in this list, log a customer message with SAP and refer to this note.

If a feature is tolerated by SAP, but is not officially supported by SAP Support, you can obtain support if problems occur as follows:

If you a have a support contract directly with Oracle, then contact Oracle about the problem. If SAP does not provide support for the Oracle functions listed below, Oracle will support you directly if you have obtained your Oracle database license directly from Oracle, that is, if it is not an embedded license or an application-specific full-use (ASFU) license.

If you bought the Oracle database from SAP, open a customer message to SAP. This is forwarded internally to Oracle Development Support if necessary, who will support you in solving the problem.

In addition to ensuring that SAP supports or allows the use of features, you must also make sure that the feature or procedure is covered by the license. For more information, see Notes 740897 and 581312.

Note 598678 describes new Oracle 9i features and the support for Oracle 9i features in the SAP environment. Note 828268 describes the support for Oracle 10g features.

As of Oracle Release 10g, you can use the following queries to determine which database features were already being used:

SELECT
  NAME,
  DETECTED_USAGES,
  CURRENTLY_USED,
  FIRST_USAGE_DATE
FROM
  DBA_FEATURE_USAGE_STATISTICS
WHERE
  VERSION = (SELECT VERSION FROM V$INSTANCE) AND
  (DETECTED_USAGES > 0 OR CURRENTLY_USED != 'FALSE');

If you specify features that, according to the information below, are only restricted or are no longer supported at all, you should determine in which context the feature is used and to what extent you actually require this usage.
Caution: Due to Oracle bug 5475037, the advanced security option is therefore, partially by mistake, displayed as 'used' (if there is an OPS$ user with EXTERNAL password).

When you start SQLPLUS, it may also display certain installed
options, such as

SQL*Plus: Release 10.2.0.4.0 - Production on Thu Mar 5 09:22:56 2009
Copyright (c) 1982, 2007, Oracle.  All Rights Reserved.

Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit
With the Partitioning, Data Mining and Real Application Testing options

This display does not have any direct effects on licensing. As long as you do not actually use an option, it does not have to be licensed. As standard, SAP installs many options even if you never use these in concrete situations.

1. Advanced Replication

Can be used.

2. Auditing

You can use normal auditing.

Oracle Audit Vault

You are permitted to use this only with explicit approval from SAP and only with SAP Kernel 7.10 or higher.

Database Firewall not allowed
Contact: christian.graf@sap.com

3. Automatic Shared Memory Management (ASMM)

You can use ASMM, but SAP does not recommend it.

You must note the restrictions from Note 789011 (define lower limits for DB_CACHE_SIZE and SHARED_POOL_SIZE that are high enough).

4. Automatic Storage Management (ASM)

Usage with Oracle 10g is not allowed.

Usage of ASM and ACFS as of Oracle 11.2.0.2 is supported (Note 1550133).

5. BIGFILE Tablespace

Usage is allowed and supported (Notes 1644762, 1647271).

6. Block Change Tracking (10g or higher)

Can be used (Note 964619).

7. Change Data Capture (CDC)

Use in the context of SAP Business Objects Data Services is supported.

Otherwise, it cannot be used.

8. Configuration Manager (OCM)

Its use is not supported (Note 1227404).

9. Connection Manager

Cannot be used.

10. Database Configuration Assistant (DBCA)

Not permitted to use DBCA to create a database.

11. Database File System (DBFS)

Can be used, but no SAP support is provided.

12. Database Firewall

Cannot be used.

13. Database Vault

Can be used (Note 1355140).

14. Data Guard

You can use "Physical Standby".

You cannot use "Logical Standby".

You can use Data Guard Broker.

You can use Maximum Performance Mode, Maximum Availability Mode and Maximum Protection Mode.

In the case of Maximum Availability and Maximum Protection, you must pay particular attention to a fast network connection in order to avoid performance problems.

Maximum Protection causes the primary database to terminate if problems occur in the standby database.

If you are interested in Active Data Guard, e-mail christian.graf@sap.com.

15. Data masking

If you are interested in this, e-mail christian.graf@sap.com.

16. Data Mining

Can be used, but no SAP support is provided.

17. Data Pump (expdp, impdp)

This is supported as of BRSPACE 7.00 (17) (Note 976435)

You can use EXPDP/IMPDP directly, but there is no SAP support.

18. DB_BLOCK_SIZE different from 8 KB

Block sizes smaller than 8 KB are not permitted.

An Oracle block size greater than 8 KB is allowed; the disadvantages of using larger block sizes include an increased demand for buffer pool memory and an increased volume of I/O data.

Multiple block sizes (equal to or greater than 8 KB) are allowed.

19. DBMS_OBFUSCATION_TOOLKIT

Cannot be used.

20. DBMS_SPACE_ADMIN.TABLESPACE_MIGRATE_TO_LOCAL

Cannot be used.

21. DBMS_STATS

You cannot use DBMS_STATS to create statistics directly on a regular basis.

You can use DBMS_STATS to create statistics via BRCONNECT (Note 408532).

22. DBNEWID (NID)

Can be used, but no SAP support is provided.

23. Diagnostics Pack

The activation is mandatory in the SAP environment so that the relevant ST04 functions can be used (Note 1028068).

24. Disk Manager (ODM)

The use is allowed in connection with the VERITAS implementation of ODM (for example, in connection with "VERITAS Storage Foundation for Oracle", "VERITAS Storage Foundation for Oracle RAC" (previously DBE/AC), or "HP Serviceguard Storage Management Suite for Oracle").

Otherwise, it cannot be used

25. Distributed Transactions

Can be used, but no SAP support is provided.

26. Domain Indexes

You can use this feature in connection with BugsEye / Requisite.

There is no further SAP support (see Note 740897).

27. Enterprise Manager (OEM) and other Oracle administration tools such as DBControl

Can be used, but no SAP support is provided.

You can also use optional OEM packages, but no SAP support is provided.

You can also use the Management Server, but no SAP support is provided.

You can use Enterprise Manager Grid Control for monitoring purposes, but Oracle provides support (not SAP).

You cannot use Enterprise Manager Grid Control for other purposes (Note 828268).

The use of OEM to create CBO statistics is not supported.

For more information, see Note 386413.

28. Encryption

Network Encryption: Use is supported (SAP Note 973450).

Transparent Data Encryption (TDE): Use is supported (SAP Note 974876).

29. Exadata

Can be used (Note 1590515).

30. Exadata Hybrid Columnar Compression (EHCC, HCC, compress for query, compress for archive)

Use not supported

As an alternative, you can use the OLTP tables compression. This is fully supported in the SAP environment (Note 1436352).

31. Exalogic

Can be used (Note 1617188).

32. EXP / IMP

Automatically supported if you use BRSPACE (Note 646681).

You can use them but no SAP support is provided if problems and follow-on errors occur (Note 541538).

As of Oracle 11g, you may only use this in exceptional cases (refer to SAP Note 1712612).

33. External data in the SAP database

Must be covered by an acquired database license (Note 581312).

Permitted for administration tools and monitoring tools.

In addition, we do not recommend to use an SAP database with non-SAP software, since this constellation has considerable disadvantages:

A database upgrade required for the system can only be performed if all software components that use the database can handle the new release.

Required changes to database parameters for a system result in a downtime of several systems.

Required import of database patches for a system result in a downtime of several systems.

Special SAP database parameter settings may be unsuitable for external software access.

Conflicts with CPU resources, memory resources, I/O resources and Oracle internal resources.

Conflicts with BR*TOOLS

Dependencies and unnecessary downtimes for restore scenarios and recovery scenarios

The code page must be the same for all systems.

Critical Oracle bugs, such as the problem described in Note 1107700, are possible

34. Flashback

You can use the flashback table to restore data in urgent cases if the consistency of the application can be ensured (see Note 937492, if in doubt, contact SAP).

The use of the flashback database (Oracle >= 10g) is permitted (Note 966117)

The use of the flashback archive or total recall (Oracle 11g or higher) is permitted but there is no SAP support.

35. Smart Flash cache (Oracle 11g or higher)

Using the Exadata Smart Flash cache is permitted.

You can use Database Smart Flash Cache but SAP Support is not provided.

36. Function-based indexes

Can be used, but no SAP support is provided.

No support is provided by SAP-DDIC or by monitoring transactions.

37. Golden Gate

Use is permitted in connection with Note 1508271.

Otherwise, it cannot be used.

38. Health Monitor (11g or higher)

Can be used, but no SAP support is provided.

Individual tests are useful to avoid negative side effects.

39. Index Organized Tables (IOTs)

Can be used.

For more information and details on restrictions, see Note 641435.

40. Installation media

Only SAP Oracle installation media is permitted

Customer-defined builds and Oracle standard installation media is not permitted

41. Invisible indexes

The usage for a temporary analysis of performance problems and a punctual usage are permitted.

42. Java Database Connectivity (JDBC)

Not permitted for ABAP work process connections

Default for J2EE connections

43. Java Virtual Machine (JVM)

You may use this only after receiving explicit permission from SAP.

Contact: christian.graf@sap.com

44. Cloning Oracle software

Copying or cloning Oracle software in accordance with the metalink document 300062.1 is permitted in the SAP environment.

Otherwise, copying or cloning the Oracle software is not permitted.

45. Compression (Note 1289494)

BASIC table compression: Permitted only as part of Note 701235 and Note 1231895.

OLTP table compression and Securefile compression (Oracle 11g or higher, Advanced Compression Option) are supported (Note 1436352).

The use of index compression in accordance with Note 1109743 is supported.

46. LDAP

Can be used, but no SAP support is provided.

47. Materialized Views

Can be used.

For more information, see Note 741478.

48. Monitoring Tools

You can use external monitoring tools

49. MOVE

This is supported by BRSPACE as of Release 7.00 (28) or 7.10 (4) (see Note 1080376).

You can use ALTER TABLE MOVE, but no SAP support is provided if problems and follow-on errors occur (Note 541538).

50. Objects Option

Cannot be used (Note 740897).

51. OLAP

Cannot be used (Note 740897).

52. OCFS (Oracle Cluster File System)

Can be used in the RAC environment as described in Note 527843.

53. Online backups without backup mode (BEGIN BACKUP)

Only permitted in connection with RMAN or with tools that satisfy the requirements specified in metalink document 604683.1

54. Optimal Flexible Architecture

No SAP support

Problems are likely during installation, migration, and when using SAP tools.

55. ORACLE_HOME sharing (several instances with the same Oracle binaries)

RAC: Use recommended and supported

Non-RAC, Windows: Can be used.

Non-RAC, UNIX / LINUX: Cannot be used.

Caution: There are dependencies with patches and upgrades. Therefore, in-depth tests are useful.

56. Oracle Linux (OL)

Can be used (Note 1565179).

57. Outlines/Stored Outlines

Can be used.

They are generally not recommended because performance problems can usually be solved otherwise also.

58. Parallel Execution

Can be used.

For more information, see Note 651060.

59. Parallel Server (OPS)

Cannot be used.

Alternatively: Real Application Clusters (see below)

60. Partitioning

The use of partitioning is supported within the BR*TOOLS functions (Release 6.20 or higher) and the SAP Data Dictionary function (Release 4.6C or higher).

Sub-partitioning permitted (SAP DDIC support with NetWeaver 7.00 or higher, Oracle 11g and higher, and Support Package levels from Note 742243)

System copies and table conversions lost

For more information, see Notes 722188 and 742243.

61. Read-only mode

You can use a read-only database for administrative purposes only (for example, consistency check on standby side).

You cannot start an SAP instance on a read-only database.

You cannot use read-only tablespaces

For more information, see Note 817253.

62. Real Application Clusters (RAC)

You can use this feature in accordance with Note 527843.

RAC One Node (Oracle 11g or higher) is not allowed

63. Real Application Testing (RAT) / Capture / Replay / SQL Performance Analyzer

Can be used (Note 1426980).

64. Recovery Manager (RMAN)

The use of RMAN is supported for Backup, Restore and Recovery within the BR*TOOLS functions (Release 4.5B or higher).

Otherwise, you can use RMAN, but SAP Support is not provided.

65. Recycle bin

Only pilot customers are allowed to use this (contact: christian.graf@sap.com).

It is a good idea to PURGE the recycle bin on a regular basis to prevent increasing space requirements.

66. Remote Diagnostic Agent (RDA)

Can be used (Note 1005931).

67. Resource Manager

Can be used (Note 1589924).

68. Restart:

Can be used.

69. RESUMABLE

Can be used (Note 1327890).

70. Result Cache

Server Result Cache: Can be used, but no SAP support is provided.

Client Result Cache: Cannot be used.

71. Reverse key indexes

Can be used.

For more information, see Note 915242.

72. Sequences

In certain cases, this is used in the standard SAP system (for example, in the table DDLOG).

Otherwise, it cannot be used.

73. Software Configuration Manager (SCM)

Cannot be used (Note 1227404).

74. Spatial

Cannot be used.

75. SQL Loader (SQLLDR)

Cannot be used.

76. SQL Plan Management (SPM, Oracle 11g or higher)

Can be used.

77. SQL Profiles

Can be used.

They are generally not recommended because performance problems can usually be solved otherwise also.

78. Standard Edition

SAP products always require the Oracle Enterprise edition, using Oracle Standard edition is not permitted.

79. Statspack

Can be used.

For more information, see Note 717484.

80. Streams

Cannot be used.

81. Supplemental Logging

Can be used.

Increased redo log volume must be considered.

82. Temporary Tablespace Group

Can be used, but no SAP support is provided.

Caution: The reliability of the temp-tablespace checks of BRCONNECT / RZ20 / Solution Manager is no longer guaranteed.

83. Text (previously: Intermedia)

You can use this feature in connection with BugsEye / Requisite.

There is no further SAP support (see Note 740897).

84. TimesTen

Cannot be used.

85. Transparent Gateway (DB2)

Can be used, but no SAP support is provided.

86. Transportable Tablespaces

The implicit use is supported in the BRSPACE function "-f dbcreate" (Note748434) and the "Tablespace Point in Time Recovery" function of BRRECOVER.

Explicit use as part of system copying is tolerated (service.sap.com/systemcopy -> 'Procedures').

87. Transportable database

Can be used (Note 1367451).

88. Trigger

Can be used as part of the SAP standard (for example, BW tigger /BI0/05* in accordance with Note 449891, incremental conversion ICNV)

Logon Trigger can be used in accordance with Note 712777.

Implicit use as part of Oracle features permitted (for example, online reorganisation, materialized views, GridControl/Enterprise Manager)

Otherwise, it cannot be used

Using trigger-based real-time replication is permitted in connection with an SAP HANA implementation only.

89. Tuning Pack

Can be used.

90. Virtual environments (Oracle VM, XEN, VMWare)

With regard to VMWare, see Note 1173954.

With regard to XEN, see Note 1426182.

The use of Oracle VM is supported (SAP Note 1808268).

Header Data


Release Status:	Released for Customer
Released on:	19.07.2013 06:35:34
Master Language:	German
Priority:	Recommendations/additional info
Category:	Consulting
Primary Component:	BC-DB-ORA Oracle

Affected Releases

Release-Independent

Related Notes

Note 105047 - Support for Oracle functions in the SAP environment

2 comments: