TRIAS SAP Prod Build ODG v0.3 by Sugik

Sample Design Work Book

SAMPLE SECTIONError! Reference source not found.TRIAS SAP Prod Build ODG v0.3 by Sugik

Final Preparation

Oracle Dataguard ConfigurationDraftApr 2011

Document Control

Author Aswin Cahyadi

File NameTRIAS SAP Prod Build ODG v0.1.doc

Path

First CreatedAswin Cahyadi

Last Saved

Last Printed

Number of Pages40

Version Control

VersionRevision DateRevision DescriptionAuthorSign-off

0.220.08.2011Modification point 11 & 12Sugik

Document Approval

RoleNameSignatureDate

Basis ConsultantAswin Cahyadi

Basis ConsultanHilman20.08.11

Target Readership

Project Management, Basis Team

Table of Contents

51Introduction

Purpose of Document52Overview of Oracle Data Guard63Requirements74Naming Convention85Configuring SQL*Net file95.1Primary Database95.1.1Sqlnet.ora95.1.2Listener.ora95.1.3Tnsnames.ora125.2Standby Database145.2.1Sqlnet.ora145.2.2Listener.ora155.2.3Tnsnames.ora176Checking the SQL*Net configuration197Additional Parameter for init.ora227.1Database parameters of relevance to Data Guard, primary database227.2Database parameters of relevance to Data Guard, standby database238Create a Password File249Restoring All SAP Data to standby database2710Recover standby database2811Creating a standby control file on the primary database2812Distributing on the standby host3013Mounting the standby database for the first time3114Start Redo Apply3115Defining the protection mode3216Check Applied Redo in Standby database3217Check Redo Shipping3418Deploying the transfer of logs and function checkError! Bookmark not defined.19Disaster handling / role transition3419.1Preparations3419.2How long does the role transition take?3519.3Switchover3619.3.1Switchover without Data Guard Broker3719.4Failover to standby databaseError! Bookmark not defined.19.4.1Failover without Data Guard BrokerError! Bookmark not defined.20Daily Monitoring37

1 Introduction

Purpose of Document

The purpose of this document is to provide documentation of setting Oracle Dataguard for SAP 4.7 Oracle 10.2.4 and standard operation procedure for performing switch over or fail over in case of disaster.The document provides step-by-step instructions for how to set up an Oracle Data Guard solution with a physical standby database.

Intended audience for this document is SAP Administrator (Basis) and Project Manager.

2 Overview of Oracle Data GuardOracle Data Guard is the management, monitoring, and automation software infrastructure that creates, maintains, and monitors one or more standby databases to protect enterprise data from failures, disasters, errors, and data corruptions.

Data Guard maintains standby databases as consistent copies of the production database as far as transactions are concerned. These standby databases can be located at remote disaster recovery sites thousands of miles away from the production data center, or they may be located in the same city, same campus, or even in the same building. If the production database becomes unavailable because of a planned or an unplanned outage, Data Guard can switch any standby database to the production role, thus minimizing the downtime associated with the outage, and preventing any data loss.

A Data Guard configuration consists of a production database, also known as the primary database, and up to nine standby database(s), which are consistent copies of the primary database as far as transactions are concerned. Data Guard maintains this transactional consistency using redo data. As transactions occur in the primary database, redo data is generated and written to the local redo log files. With Data Guard, this redo data is also transferred to the standby sites and applied to the standby databases, keeping them synchronized with the primary database.

Data Guard allows the administrator to choose whether this redo data is sent synchronously or asynchronously to a standby site.

The underlying technologies for standby databases are Data Guard Redo Apply (physical standby database), and Data Guard SQL Apply (logical standby database). A physical standby database has on-disk database structures that are identical to the primary database on a block-for-block basis, and is updated using Oracle media recovery. A logical standby database is an independent database that contains the same data as the primary database. It is updated using SQL statements, and has the advantage that it can be used for recovery and for other tasks such as reporting and queries at the same time.

Data Guard enables role transitions between the primary database and a chosen standby database, reducing overall downtime during planned outages and unplanned failures.

3 Requirements

A second database host, configured in exactly the same way as the first, is needed to operate Oracle Data Guard. This means:

Same operating system, e.g. AIX 6.1 on both hosts

Same parameter settings on database and operating system (e.g. nfiles)

Identical Oracle version, currently the 10.2.0.4 database patch set with individual patches as recommended in SAP note 1137346.

Identical file system structure, especially for SAP data and Oracle home.

The databases must be operated in ARCHIVELOG mode

Use of server parameter file (SPFILE)

Please read SAP note 105047 for supported Oracle Data Guard configurations in an SAP environment ( .4 Naming ConventionIDENTIFIERPRIMARY DATABASEPHYSICAL STANDBY DATABASECOMMENTS

DB-SIDP01P01Listener.ora

Host nametrstp1db_aixtrstp1db_drListener / tnsnames.ora

DG config.p01p01Configuration name for Broker

Service nameP01_PRMP01_SBYTnsnames.ora

Listener nameLISTENER_P01LISTENER_P01Listener.ora

Listener port15271527Listener.ora

Global_Dbname (listener.ora) see

also SQL*Net configurationP01_PRM_DGMGRL

P01_PRM_DGB

P01_PRM_XPT P01_SBY_DGMGRL

P01_SBY_DGB

P01_SBY_XPTListener.ora

DB_Unique_nameP01_PRMP01_SBYspfileQAS.ora

Oracle base/oracle/oracleOracle base

Data filessapdata*sapdata*Data files

5 Configuring SQL*Net file5.1 Primary Database5.1.1 Sqlnet.ora

Ensure sqlnet.ora configuration as follow:################

# Filename......: sqlnet.ora

# Created.......: created by SAP AG, R/3 Rel. >= 4.0A

# Name..........:

# Date..........:

################

AUTOMATIC_IPC = ON

TRACE_LEVEL_CLIENT = OFF

SQLNET.EXPIRE_TIME = 0

#NAMES.DEFAULT_DOMAIN = WORLD ( this parameter should not be activatedNAMES.DIRECTORY_PATH = (TNSNAMES) ( neededNAME.DEFAULT_ZONE = WORLDTCP.NODELAY=YES

5.1.2 Listener.ora################

# Filename......: listener.ora

# Created.......: created by SAP AG, R/3 Rel. >= 6.10

# Name..........:

# Date..........:

# @(#) $Id: //bc/640-2/src/ins/SAPINST/impl/tpls/ora/ind/LISTENER.ORA#4 $

################

ADMIN_RESTRICTIONS_LISTENER_P01 = on

LISTENER_P01 =

(ADDRESS_LIST =

(ADDRESS =

(PROTOCOL = IPC)

(KEY = P01.WORLD)

)

(ADDRESS=

(PROTOCOL = IPC)

(KEY = P01)

)

(ADDRESS =

(COMMUNITY = SAP.WORLD)

(PROTOCOL = TCP)

(HOST = trstp1db_aix)

(PORT = 1527)

(SEND_BUF_SIZE = 9375000)

(RECV_BUF_SIZE = 9375000)

)

)

STARTUP_WAIT_TIME_LISTENER_P01 = 0

CONNECT_TIMEOUT_LISTENER_P01 = 0

TRACE_LEVEL_LISTENER_P01 = OFF

SID_LIST_LISTENER_P01 =

(SID_LIST =

(SID_DESC =

(SID_NAME = P01)

(GLOBAL_DBNAME=P01_PRM)

(ORACLE_HOME = /oracle/P01/102_64)

)

(SID_DESC =

(SID_NAME = P01)

(GLOBAL_DBNAME=P01_PRM_DGMGRL)


)

(SID_DESC =

(SID_NAME = P01)

(GLOBAL_DBNAME=P01_PRM_DGMGRL.WORLD)


)

(SID_DESC =

(SID_NAME = P01)

(GLOBAL_DBNAME=P01_PRM_XPT.WORLD)


)

(SID_DESC =

(SID_NAME = P01)

(GLOBAL_DBNAME=P01_PRM_DGB.WORLD)


)

)

5.1.3 Tnsnames.ora

################

# Filename......: tnsnames.ora


# Name..........:

# Date..........:

# @(#) $Id: //bc/640-2/src/ins/SAPINST/impl/tpls/ora/ind/TNSNAMES.ORA#4 $

################

P01=

(DESCRIPTION =

(ADDRESS_LIST =

(ADDRESS =


(PROTOCOL = TCP)


(PORT = 1527)

)

)

(CONNECT_DATA =

(SID = P01)

(GLOBAL_NAME = P01)

(SERVICE_NAME = P01_PRM)

)

)

P01_SBY=

(DESCRIPTION =

(ADDRESS_LIST =

(ADDRESS =


(PROTOCOL = TCP)

(HOST = trstp1db_dr)

(PORT = 1527)

(SDU=32768)

)

)

(CONNECT_DATA =

(SID = P01)

(SERVICE_NAME= P01_SBY)

)

)

5.2 Standby Database

5.2.1 Sqlnet.ora

Ensure sqlnet.ora configuration as follow:################

# Filename......: sqlnet.ora

# Created.......: created by SAP AG, R/3 Rel. >= 4.0A

# Name..........:

# Date..........:

################

AUTOMATIC_IPC = ON

TRACE_LEVEL_CLIENT = OFF

SQLNET.EXPIRE_TIME = 0

#NAMES.DEFAULT_DOMAIN = WORLD ( this parameter should not be activatedNAMES.DIRECTORY_PATH = (TNSNAMES) ( neededNAME.DEFAULT_ZONE = WORLD

5.2.2 Listener.ora################

# Filename......: listener.ora


# Name..........:

# Date..........:

# @(#) $Id: //bc/640-2/src/ins/SAPINST/impl/tpls/ora/ind/LISTENER.ORA#4 $

################

ADMIN_RESTRICTIONS_LISTENER_P01 = on

LISTENER_P01 =

(ADDRESS_LIST =

(ADDRESS =

(PROTOCOL = IPC)

(KEY = P01.WORLD)

)

(ADDRESS=

(PROTOCOL = IPC)

(KEY = P01)

)

(ADDRESS =


(PROTOCOL = TCP)


(PORT = 1527)

(SEND_BUF_SIZE = 9375000)

(RECV_BUF_SIZE = 9375000)

)

)

STARTUP_WAIT_TIME_LISTENER_P01 = 0

CONNECT_TIMEOUT_LISTENER_P01 = 0

TRACE_LEVEL_LISTENER_P01 = OFF

SID_LIST_LISTENER_P01 =

(SID_LIST =

(SID_DESC =

(SID_NAME = P01)

(GLOBAL_DBNAME=P01_SBY)


)

(SID_DESC =

(SID_NAME = P01)

(GLOBAL_DBNAME=P01_SBY_DGMGRL)


)

# optional

(SID_DESC =

(SID_NAME = P01)

(GLOBAL_DBNAME=P01_SBY_DGMGRL.WORLD)


)

(SID_DESC =

(SID_NAME = P01)

(GLOBAL_DBNAME=P01_SBY_XPT.WORLD)


)

(SID_DESC =

(SID_NAME = P01)

(GLOBAL_DBNAME=P01_SBY_DGB.WORLD)


)

# end optional

)

5.2.3 Tnsnames.ora

################

# Filename......: tnsnames.ora


# Name..........:

# Date..........:

# @(#) $Id: //bc/640-2/src/ins/SAPINST/impl/tpls/ora/ind/TNSNAMES.ORA#4 $

################

P01=

(DESCRIPTION =

(ADDRESS_LIST =

(ADDRESS =


(PROTOCOL = TCP)


(PORT = 1527)

)

)

(CONNECT_DATA =

(SID = P01)

(GLOBAL_NAME = P01)

(SERVICE_NAME = P01_SBY)

)

)

P01_PRM=

(DESCRIPTION =

(ADDRESS_LIST =

(ADDRESS =


(PROTOCOL = TCP)


(PORT = 1527)

(SDU=32768)

)

)

(CONNECT_DATA =

(SID = P01)

(SERVICE_NAME= P01_PRM)

)

)

6 Checking the SQL*Net configurationOnce the configuration files have been created and implementation on the hosts is complete, you must check whether the databases can be accessed by the other partner host using SQL*Net. The TNSPING Oracle tool is used for this purpose.

tnsping

lsnrctl services Perform the following:

PRIMARY HOSTSTANDBY HOST

lsnrctl start LISTENER_P01lsnrctl start LISTENER_P01

tnsping P01_SBY

TNS Ping Utility for IBM/AIX RISC System/6000: Version 10.2.0.4.0 - Production on 23-MAR-2011 12:48:22

Copyright (c) 1997, 2007, Oracle. All rights reserved.

Used parameter files:

/oracle/P01/102_64/network/admin/sqlnet.ora

Used TNSNAMES adapter to resolve the alias

Attempting to contact (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (COMMUNITY = SAP.WORLD) (PROTOCOL = TCP) (HOST = trstp1db_dr) (PORT = 1527) (SDU=32768))) (CONNECT_DATA = (SID = P01) (SERVICE_NAME= P01_SBY)))

OK (10 msec)tnsping P01_PRM

TNS Ping Utility for IBM/AIX RISC System/6000: Version 10.2.0.4.0 - Production on 23-MAR-2011 12:47:34


Used parameter files:

/oracle/P01/102_64/network/admin/sqlnet.ora

Used TNSNAMES adapter to resolve the alias

Attempting to contact (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (COMMUNITY = SAP.WORLD) (PROTOCOL = TCP) (HOST = trstp1db_aix) (PORT = 1527) (SDU=32768))) (CONNECT_DATA = (SID = P01) (SERVICE_NAME= P01_PRM)))

OK (20 msec)

lsnrctl services LISTENER_P01LSNRCTL for IBM/AIX RISC System/6000: Version 10.2.0.4.0 - Production on 09-MAR-2011 14:58:18


Connecting to (ADDRESS=(PROTOCOL=IPC)(KEY=P01.WORLD))

Services Summary...

Service "P01_PRM" has 1 instance(s).

Instance "P01", status UNKNOWN, has 1 handler(s) for this service...

Handler(s):

"DEDICATED" established:0 refused:0

LOCAL SERVER

Service "P01_PRM_DGB.WORLD" has 1 instance(s).


Handler(s):


LOCAL SERVER

Service "P01_PRM_DGMGRL" has 1 instance(s).


Handler(s):


LOCAL SERVER

Service "P01_PRM_DGMGRL.WORLD" has 1 instance(s).


Handler(s):


LOCAL SERVER

Service "P01_PRM_XPT.WORLD" has 1 instance(s).


Handler(s):


LOCAL SERVER

The command completed successfullylsnrctl services LISTENER_P01LSNRCTL for IBM/AIX RISC System/6000: Version 10.2.0.4.0 - Production on 09-MAR-2011 14:50:54


Connecting to (ADDRESS=(PROTOCOL=IPC)(KEY=P01.WORLD))

Services Summary...

Service "P01_SBY" has 1 instance(s).


Handler(s):


LOCAL SERVER

Service "P01_SBY_DGB.WORLD" has 1 instance(s).


Handler(s):


LOCAL SERVER

Service "P01_SBY_DGMGRL" has 1 instance(s).


Handler(s):


LOCAL SERVER

Service "P01_SBY_DGMGRL.WORLD" has 1 instance(s).


Handler(s):


LOCAL SERVER

Service "P01_SBY_XPT.WORLD" has 1 instance(s).


Handler(s):


LOCAL SERVER

The command completed successfully

Try to start SAP at primary database to ensure that your configuration is set up correctlyShutdown SAP and Oracle again for next setting

7 Additional Parameter for init.ora

7.1 Database parameters of relevance to Data Guard, primary database#activate ODG#

*.db_unique_name='P01_PRM'

*.FAL_CLIENT='P01_PRM'

*.FAL_SERVER='P01_SBY'

*.local_listener='(ADDRESS = (PROTOCOL = TCP)(HOST = trstp1db_aix)(PORT = 1527))'

*.LOG_ARCHIVE_CONFIG='DG_CONFIG=(P01_PRM,P01_SBY)'

*.log_archive_dest_1='LOCATION="/oracle/P01/oraarch/P01arch", valid_for=(ALL_LOGFILES,ALL_ROLES)'

*.log_archive_dest_2='service="(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP) (HOST=trstp1db_dr)(PORT=1527)))(CONNECT_DATA=(SERVICE_NAME=P01_SBY_DGMGRL) (INSTANCE_N

AME=P01) (SERVER=dedicated)))"',' ARCH NODELAY OPTIONAL max_failure=100 max_connections=2 reopen=60 db_unique_name="P01_SBY" register net_timeout=10 valid_for=(online_l

ogfile,primary_role)'

*.log_archive_dest_state_1='ENABLE'


*.log_archive_format='P01arch%t_%s_%r.dbf'

*.log_archive_max_processes=2

*.log_archive_min_succeed_dest=1

*.log_archive_trace=0

*.log_file_name_convert='P01','P01'

*.REMOTE_LOGIN_PASSWORDFILE='EXCLUSIVE'

*.standby_file_management='AUTO'

*.standby_archive_dest='/oracle/P01/oraarch/P01arch/stby'

7.2 Database parameters of relevance to Data Guard, standby databaseSave as initP01.ora.odg*.workarea_size_policy='AUTO'

*.db_unique_name='P01_SBY'

*.FAL_CLIENT='P01_SBY'

*.FAL_SERVER='P01_PRM'

*.local_listener='(ADDRESS = (PROTOCOL = TCP)(HOST = trstp1db_dr)(PORT = 1527))'

*.LOG_ARCHIVE_CONFIG='DG_CONFIG=(P01_PRM,P01_SBY)'

*.log_archive_dest_1='LOCATION="/oracle/P01/oraarch/P01arch", mandatory valid_fo

r=(ALL_LOGFILES,ALL_ROLES)'

*.log_archive_dest_2='service="(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP

) (HOST=trstp1db_aix)(PORT=1527)))(CONNECT_DATA=(SERVICE_NAME=P01_PRM_DGMGRL) (I

NSTANCE_NAME=P01) (SERVER=dedicated)))"',' ARCH NODELAY=180 OPTIONAL max_failure

=100 max_connections=2 reopen=60 db_unique_name="P01_PRM" register net_timeout=1

0 valid_for=(online_logfile,primary_role)'



*.log_archive_format='P01arch%t_%s_%r.dbf'

*.log_archive_max_processes=2

*.log_archive_min_succeed_dest=1

*.log_archive_trace=0

*.log_file_name_convert='P01','P01'

*.REMOTE_LOGIN_PASSWORDFILE='EXCLUSIVE'

*.standby_file_management='AUTO'

*.standby_archive_dest='/oracle/P01/oraarch/P01arch/stby'

8 Create a Password FileCreate a password file if one does not already exist. Every database in a Data Guard configuration must use a password file, and the password for the SYS user must be identical on every system for redo data transmission to succeed.Check your sys user have the same password at both primary and standby server by using this command:

sqlplus /nolog

SQL> connect sys as sysdba

Enter password: syspassConnected.If you have dont know user sys password change the password using :

Alter useridentified byNEW_PASSWORD

trstp1db_aix:orap01 9> sqlplus /nolog

SQL*Plus: Release 10.2.0.4.0 - Production on Wed Apr 13 15:22:32 2011

Copyright (c) 1982, 2007, Oracle. All Rights Reserved.

SQL> conn /as sysdba

Connected.

SQL> alter user sys identified by syspass

2 ;

User altered.You can create a password file using the password file creation utility, ORAPWD.

orapwd FILE=orapwP01 ENTRIES=30

Copy the passwordfile : orapw to standby Oracle Home destination:

$ORACLE_HOME/dbs

The password can not be changed at standby side, as the database will be normally not opened.trstp1db_aix:orap01 10> pwd

/oracle/P01/102_64/dbs

trstp1db_aix:orap01 11> orapwd FILE=orapwP01 password=syspass entries=30

trstp1db_aix:orap01 12> ls -ltr

total 368

-rw-r----- 1 orap01 dba 8385 Sep 11 1998 init.ora

-rw-r--r-- 1 orap01 dba 12920 May 03 2001 initdw.ora

-rw-r-xr-x 1 orap01 dba 20102 Oct 31 2003 initP01.dba

-rw-rw---- 1 orap01 dba 24 Jan 20 16:06 lkP01

-rw-r-xr-x 1 orap01 dba 19501 Jan 20 17:11 initP01.sap

-rw-r--r-- 1 root system 1746 Jan 20 17:15 initP01.1.ora

-rw-r--r-- 1 orap01 dba 2533 Jan 29 12:35 initP01.ora.migration

-rw-r--r-- 1 root system 18040 Jan 29 14:21 initP01_gu.sap

-rw-r--r-- 1 root system 18040 Jan 29 14:21 initP01_disk.sap

-rw-r--r-- 1 orap01 dba 1793 Feb 10 03:00 initP01.ora.10022011

-rw-r--r-- 1 root system 1797 Feb 10 13:53 initP01.ora.10022011-2

-rw-r----- 1 orap01 dba 4608 Feb 10 13:59 spfileP01.ora.20110216



-rw-r--r-- 1 orap01 dba 1797 Feb 18 11:14 initP01.ora.aftermigration

-rw-r--r-- 1 orap01 dba 2308 Mar 29 14:50 initP01.ora.orig

-rw-r----- 1 orap01 dba 5632 Apr 06 14:05 spfileP01.ora

-rw-r--r-- 1 orap01 dba 3198 Apr 07 11:31 initP01.ora.odg

-rw-r--r-- 1 orap01 dba 2198 Apr 13 03:00 sapP01.ora

-rw-rw---- 1 orap01 dba 1544 Apr 13 15:00 hc_P01.dat

-rw-r--r-- 1 orap01 dba 2709 Apr 13 15:15 initP01.ora

-rw-r----- 1 orap01 dba 5120 Apr 13 15:25 orapwP01Transfer orapwP01 to standby database.9 Restoring All SAP Data to standby database

Copy backP01.log & from /sapbackup/dataP01/P01 to /oracle/P01/sapbackup/

cp backP01.log /oracle/P01/sapbackupcp befmqveb.and /oracle/P01/sapbackupRestore all sapdata* to standby databaseExecute

/oracle/P01/sapbackup/umount.sh

/oracle/P01/sapbackup/mount_before_restore.shUsing below command as orap01:brrestore -b -d disk -r /oracle/P01/102_64/dbs/initP01_disk.sap -m allExecute


/oracle/P01/sapbackup/mount.sh

Copy backup controlfile

cd /sapbackup/dataP01/

cp cntrlP01.dbf /oracle/P01/sapdata1/cntrl/

cp cntrlP01.dbf /oracle/P01/saparch/cntrl/

cp cntrlP01.dbf /oracle/P01/origlogA/cntrl/10 Recover standby database Hence we are using backup online, first database need to be consistent.

Copy archive log from primary database to standby then we need to recover using command:SQL> startup mount

SQL> recover database until cancel using backup controlfile;

SQL>shutdown immediate;

11 Creating a standby control file on the primary databaseCarry out on: trstp1db_aix as orap01SQL> alter database create standby controlfile as '/oracle/P01/sapreorg/stdby_controlf.dbf' reuse;

12 Distributing on the standby hostThe file is copied into the directories which are stated in the database parameter file using the CONTROLFILES= parameter.So, copy as following:

Catatan by Sugik :Start listener sebelum startup mount dan jalan apply log di server DR

lsnrctl start

lsnrctl start LISTENER_TRP

13 Mounting the standby database for the first time This is done to test the function. It tests whether all database parameters match and whether the control files are in the right place and are readable. Also we can now take the chance to create a SPFILE from the copied initQAS.ora.

SQL> connect / as sysdba

SQL> create spfile from pfile;

SQL> startup mount14 Start Redo ApplyOn the standby database, issue the following command to start Redo Apply:

SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE NODELAY DISCONNECT FROM SESSION;

The statement includes the DISCONNECT FROM SESSION option so that Redo Apply runs in a background session15 Defining the protection mode

The transfer mode for the redo log files depends on the protection mode selected. Also refer to the documentation "Managing Data Protection mode".

First of all you should find out which protection mode Data Guard should be used in. Unless configured otherwise, the "Maximum Performance" default is used.

16 Check Applied Redo in Standby databaseRun SQL Statement to see archive log that has been applied

SQL> SELECT SEQUENCE#, APPLIED from V$ARCHIVED_LOG;

17 Check Redo Shipping

18 Disaster handling / role transition18.1 PreparationsAlso refer to "Oracle Data Guard Concepts and Administration" chapter 7.1.1 Preparing for a Role Transition (failover or switchover).

Verify that the initialization parameters for each database are configured correctly.

The database, which takes on the role of the primary database, must run in ARCHIVELOG mode.

Make sure that all files, which belong to a tablespace with temporary files, also exist on the standby side before the role transition takes place.18.2 How long does the role transition take?

Data Guard provides the V$DATAGUARD_STATS view, which can estimate how long the process, will take.

Example:

SQL> COLUMN NAME FORMAT A18

SQL> COLUMN VALUE FORMAT A16

SQL> COLUMN TIME_COMPUTED FORMAT A24

SQL> SELECT * FROM V$DATAGUARD_STATS;

The example shows that there is no delay in the transfer of redo logs, but this is of importance only if another standby database is being cascaded. The active media recovery currently needs another 15:51 minutes.

The role transition will only take place once it is complete.Try it in our P01 system.

18.3 Switchover During a switchover the roles of the databases are usually swa pped. The previous standby database becomes the primary database and the previous primary one the standby one.

This is done by parameterization and changing the control file.18.3.1 Failover TRIAS ODG Failover Procedure Document (

19 Daily Monitoring

Check for archive gap in Standby database:

SQL> SELECT THREAD#, LOW_SEQUENCE#, HIGH_SEQUENCE# FROM V$ARCHIVE_GAP;

If there are missing archivelogs, check the root cause of the problem. Possibilities are:

1. Network problem

2. Archivelogs are missing in primary database (deleted by DB13)

3. Etc.

Check for applied archivelogs in standby database

SQL> SELECT SEQUENCE#, APPLIED FROM V$ARCHIVED_LOG;

SEQUENCE# APP

---------- ---

7919 YES

7920 YES

7921 YES

564 rows selected.

Determine the cause if there archivelog with status NO for applied.

Ensure there are enough space in the filesystem for /oracle/P01/oraarch/P01arch in standby database

Note: When adding new datafiles in primary database, make sure there are enough space in the filesystem on the standby database since Oracle Data Guard automatically replicates the new datafile from primary to standby database.

If there is not enough free space, add using smitty jfs2Never perform startup on standby database on normal situation, always use startup mount20 HousekeepingHousekeeping is performed automatically using crontab

# crontab -l

0 23 * * * /oracle/P01/sapbackup/script/cleanarch.sh#/oracle/P01/sapbackup/script/cleanarch.sh will remove all applied archivelogs except the last 100 archivelogs. Log file of cleanarch.sh is located at /oracle/P01/sapbackup/log/cleanarch.log_

Cleanarch.sh script content (

Trias SAP Prod Simulation Build ODG

SAP Implementation Project

Page 12 of 40Version eg. 1.1 D:\Backup Data Sugik - 2 Des 2011\Dokument-SAP-BASIS\SAP Project 2011 - SAP OSDB Migration\Rimgkasan Sugik\TRIAS SAP Prod Build ODG v0.3 by Sugik.doc11/7/2012 10:17:00 AM

_1364817776/tnsnames.ora################# Filename......: tnsnames.ora# Created.......: created by SAP AG, R/3 Rel. >= 6.10# Name..........:# Date..........:# @(#) $Id: //bc/640-2/src/ins/SAPINST/impl/tpls/ora/ind/TNSNAMES.ORA#4 $################P01= (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (COMMUNITY = SAP.WORLD) (PROTOCOL = TCP) (HOST = trstp1db_aix) (PORT = 1527) ) ) (CONNECT_DATA = (SID = P01) (GLOBAL_NAME = P01) (SERVICE_NAME = P01_PRM) ) )P01_SBY=(DESCRIPTION =(ADDRESS_LIST =(ADDRESS =(COMMUNITY = SAP.WORLD)(PROTOCOL = TCP)(HOST = trstp1db_dr)(PORT = 1527) (SDU=32768)))(CONNECT_DATA =(SID = P01)(SERVICE_NAME= P01_SBY)))

_1364817843/listener.ora################# Filename......: listener.ora# Created.......: created by SAP AG, R/3 Rel. >= 6.10# Name..........:# Date..........:# @(#) $Id: //bc/640-2/src/ins/SAPINST/impl/tpls/ora/ind/LISTENER.ORA#4 $################ADMIN_RESTRICTIONS_LISTENER_P01 = onLISTENER_P01 = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = IPC) (KEY = P01.WORLD) ) (ADDRESS= (PROTOCOL = IPC) (KEY = P01) ) (ADDRESS = (COMMUNITY = SAP.WORLD) (PROTOCOL = TCP) (HOST = trstp1db_dr) (PORT = 1527) (SEND_BUF_SIZE = 9375000) (RECV_BUF_SIZE = 9375000) ) )STARTUP_WAIT_TIME_LISTENER_P01 = 0CONNECT_TIMEOUT_LISTENER_P01 = 0TRACE_LEVEL_LISTENER_P01 = OFFSID_LIST_LISTENER_P01 = (SID_LIST = (SID_DESC = (SID_NAME = P01)(GLOBAL_DBNAME=P01_SBY)(ORACLE_HOME = /oracle/P01/102_64) ) (SID_DESC =(SID_NAME = P01)(GLOBAL_DBNAME=P01_SBY_DGMGRL)(ORACLE_HOME = /oracle/P01/102_64) ) (SID_DESC =(SID_NAME = P01)(GLOBAL_DBNAME=P01_SBY_DGMGRL.WORLD)(ORACLE_HOME = /oracle/P01/102_64) ) (SID_DESC =(SID_NAME = P01)(GLOBAL_DBNAME=P01_SBY_XPT.WORLD)(ORACLE_HOME = /oracle/P01/102_64) ) (SID_DESC =(SID_NAME = P01)(GLOBAL_DBNAME=P01_SBY_DGB.WORLD)(ORACLE_HOME = /oracle/P01/102_64) ) )

_1364817941/initP01.ora######################################################################### This init.ora profile is a transparent copy of Oracle spfile. ## It was created by BRARCHIVE at 2011-04-20 14.20.01. ## Please do not change this file! Maintain only the spfile. ## You can use BRSPACE for the altering of database parameters: ## brspace -f dbparam #########################################################################*._b_tree_bitmap_plans=FALSE*._bloom_filter_enabled=FALSE*._index_join_enabled=FALSE*._optim_peek_user_binds=FALSE*._optimizer_mjc_enabled=FALSE*._sort_elimination_cost_ratio=10*._table_lookup_prefetch_size=0*.background_dump_dest='/oracle/P01/saptrace/background'*.compatible='10.2.0'*.control_file_record_keep_time=30*.control_files='/oracle/P01/origlogA/cntrl/cntrlP01.dbf','/oracle/P01/saparch/cntrl/cntrlP01.dbf','/oracle/P01/sapdata1/cntrl/cntrlP01.dbf'*.core_dump_dest='/oracle/P01/saptrace/background'*.cursor_space_for_time=FALSE*.db_block_size=8192*.db_cache_size=16492674417*.db_files=1000*.db_name='P01'*.db_unique_name='P01_PRM'*.db_writer_processes=2*.dbwr_io_slaves=0*.disk_asynch_io=TRUE*.dml_locks=2500*.event='10191 trace name context forever, level 1','10027 trace name context forever, level 1','10028 trace name context forever, level 1','10183 trace name context forever, level 1','14532 trace name context forever, level 1','38087 trace name context forever, level 1','10891 trace name context forever, level 1','10091 trace name context forever, level 1'#Recommendation from SAP, ASWIN, 06/04/11*.FAL_CLIENT='P01_PRM'*.FAL_SERVER='P01_SBY'*.filesystemio_options='setall'*.java_pool_size=67108864*.large_pool_size=33554432*.local_listener='(ADDRESS = (PROTOCOL = TCP)(HOST = trstp1db_aix)(PORT = 1527))'*.LOG_ARCHIVE_CONFIG='DG_CONFIG=(P01_PRM,P01_SBY)'*.log_archive_dest_1='LOCATION="/oracle/P01/oraarch/P01arch", valid_for=(ALL_LOGFILES,ALL_ROLES)'*.log_archive_dest_2='service="(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP) (HOST=trstp1db_dr)(PORT=1527)))(CONNECT_DATA=(SERVICE_NAME=P01_SBY_DGMGRL) (INSTANCE_NAME=P01) (SERVER=dedicated)))"',' ARCH NODELAY OPTIONAL max_failure=100 max_connections=2 reopen=60 db_unique_name="P01_SBY" register net_timeout=10 valid_for=(online_logfile,primary_role)'*.log_archive_dest_state_1='ENABLE'*.log_archive_dest_state_2='ENABLE'*.log_archive_format='P01arch%t_%s_%r.dbf'*.log_archive_max_processes=2*.log_archive_min_succeed_dest=1*.log_archive_trace=0*.log_buffer=1524736*.log_checkpoint_interval=0*.log_checkpoints_to_alert=TRUE*.log_file_name_convert='P01','P01'*.max_dump_file_size='20000'*.open_cursors=800*.optimizer_index_caching=50*.optimizer_index_cost_adj=20*.parallel_execution_message_size=16384*.parallel_max_servers=40*.parallel_threads_per_cpu=1*.pga_aggregate_target=1073741824*.processes=260*.query_rewrite_enabled='FALSE'*.recyclebin='off'*.REMOTE_LOGIN_PASSWORDFILE='EXCLUSIVE'*.remote_os_authent=TRUE*.replication_dependency_tracking=FALSE*.session_max_open_files=20*.sessions=520*.sga_max_size=29686813950*.shared_pool_size=16492674417*.sort_area_retained_size=0*.sort_area_size=2097152*.standby_archive_dest='/oracle/P01/oraarch/P01arch/stby'*.standby_file_management='AUTO'*.star_transformation_enabled='TRUE'*.streams_pool_size=50331648*.timed_statistics=TRUE*.undo_management='AUTO'*.undo_retention=43200*.undo_tablespace='PSAPUNDO'*.user_dump_dest='/oracle/P01/saptrace/usertrace'*.workarea_size_policy='AUTO'

_1364818917/cleanarch.sh#!/usr/bin/kshdt=$( date +%Y%m%d%H%M%S )ARCH_DIR=/oracle/P01/oraarch/P01arch/stbylogfile="/oracle/P01/sapbackup/log/cleanarch.log_${dt}"echo $logfileecho "ODG Housekeeping Script Version 1.00" >> $logfileecho "Date = $dt" >> $logfileecho "===============================" >> $logfileecho "===== DELETED LOG FILES =======" >> $logfileecho "===============================" >> $logfile#take the log number to be appliedLogNo=`tail -30000 /oracle/P01/saptrace/background/alert_P01.log | grep "Media Recovery Log" | cut -d " " -f 4 | cut -d "_" -f 2 | tail -1ècho "Oracle applied LogNo is $LogNo"

#extract 10let SecLogNo=${LogNo}-100echo "new backlog log No: $SecLogNo"

#delete small numbers from this in arch dircd $ARCH_DIRfor i in `ls P01arch1*.dbf`do

Newi=ècho $i | cut -d "_" -f 2ìf [ $Newi -lt $SecLogNo ] ; thenecho "$i to be deleted..." echo $i >> $logfilerm $ifidoneecho "===============================" >> $logfileecho "end of execution" >> $logfile

_1364819322.docSAMPLE SECTIONError! Reference source not found.MKM Finance & Accounting Blueprint, v2.0

Final Preparation

Oracle Dataguard Configuration

Draft

Mar 2011

Document Control

Author

Aswin Cahyadi

File Name

TRIAS SAP ODG Failover v0.1.doc

Path

First Created

Aswin Cahyadi

Last Saved

Last Printed

Number of Pages

15

Version Control

Version

Revision Date

Revision Description

Author

Sign-off

Document Approval

Role

Name

Signature

Date

Basis Consultant

Aswin Cahyadi

Target Readership

Project Management, Basis Team

Table of Contents

41Introduction

Purpose of Document4

2Overview of Oracle Data Guard5

3Requirements6

4Failover to standby database7

5Rebuild standby database9

5.1Restoring All SAP Data to standby database9

5.2Copy Required Archive log10

5.3Recover standby database10

5.4Mounting Back to Mode cio10

5.5Creating a standby control file on the primary database11

5.6Distributing on the standby host11

5.7Mounting the standby database for the first time11

5.8Start Redo Apply12

6Check Applied Redo in Standby database12

7Check Redo Shipping14

1 Introduction

Purpose of Document

The purpose of this document is to provide documentation of setting Oracle Dataguard for SAP 4.6 C Oracle 10.2.4 and standard operation procedure for performing switch over or fail over in case of disaster.

The document provides step-by-step instructions for how to set up an Oracle Data Guard solution with a physical standby database. This should enable the user to manage the Data Guard system created using the Data Guard Broker.

Intended audience for this document is SAP Administrator (Basis) and Project Manager.

2 Overview of Oracle Data Guard

Oracle Data Guard is the management, monitoring, and automation software infrastructure that creates, maintains, and monitors one or more standby databases to protect enterprise data from failures, disasters, errors, and data corruptions.

Data Guard maintains standby databases as consistent copies of the production database as far as transactions are concerned. These standby databases can be located at remote disaster recovery sites thousands of miles away from the production data center, or they may be located in the same city, same campus, or even in the same building. If the production database becomes unavailable because of a planned or an unplanned outage, Data Guard can switch any standby database to the production role, thus minimizing the downtime associated with the outage, and preventing any data loss.

A Data Guard configuration consists of a production database, also known as the primary database, and up to nine standby database(s), which are consistent copies of the primary database as far as transactions are concerned. Data Guard maintains this transactional consistency using redo data. As transactions occur in the primary database, redo data is generated and written to the local redo log files. With Data Guard, this redo data is also transferred to the standby sites and applied to the standby databases, keeping them synchronized with the primary database.

Data Guard allows the administrator to choose whether this redo data is sent synchronously or asynchronously to a standby site.

The underlying technologies for standby databases are Data Guard Redo Apply (physical standby database), and Data Guard SQL Apply (logical standby database). A physical standby database has on-disk database structures that are identical to the primary database on a block-for-block basis, and is updated using Oracle media recovery. A logical standby database is an independent database that contains the same data as the primary database. It is updated using SQL statements, and has the advantage that it can be used for recovery and for other tasks such as reporting and queries at the same time.

Data Guard enables role transitions between the primary database and a chosen standby database, reducing overall downtime during planned outages and unplanned failures.

3 Requirements

A second database host, configured in exactly the same way as the first, is needed to operate Oracle Data Guard. This means:

Same operating system, e.g. AIX 6.1 on both hosts

Same parameter settings on database and operating system (e.g. nfiles)

Identical Oracle version, currently the 10.2.0.4 database patch set with individual patches as recommended in SAP note 1137346.

Identical file system structure, especially for SAP data and Oracle home.

The databases must be operated in ARCHIVELOG mode

Use of server parameter file (SPFILE)

Please read SAP note 105047 for supported Oracle Data Guard configurations in an SAP environment (

.

4 Failover to standby database

Step 1

Identify and resolve any gaps in the archived redo log files. To determine if there are gaps in the archived redo log files on the target standby database, query the V$ARCHIVE_GAP view.

For example:

SQL> SELECT THREAD#, LOW_SEQUENCE#, HIGH_SEQUENCE# FROM V$ARCHIVE_GAP;

Copy all missing log files (90,91,92) to log destination manually.

Register them:

SQL> ALTER DATABASE REGISTER PHYSICAL LOGFILE 'filespec1';

Step 2

Repeat Step 1 until all gaps are resolved.

Step 3

Copy any other missing archived redo log files.

SQL> SELECT UNIQUE THREAD# AS THREAD, MAX(SEQUENCE#) OVER (PARTITION BY thread#) AS LAST from V$ARCHIVED_LOG;

Step 4

Initiate a failover on the target physical standby database. Issue the following statement to initiate the failover:

SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE FINISH FORCE;

FORCE keyword terminates active RFS processes on the target physical standby database

Note:

Failover adds an end-of-redo marker to the header of the last log file being archived and sends the redo to all enabled destinations that are valid for the primary role (specified with the VALID_FOR=(PRIMARY_ROLE, *_LOGFILES) or the VALID_FOR=(ALL_ROLES, *_LOGFILES) attributes).

Note:

The FINISH keyword must follow all other keywords in the SQL statement, except for FORCE, WAIT, or NOWAIT.

Step 5

Convert the physical standby database to the primary role.

After the recovery has finished, change the role of database to primary:

SQL> ALTER DATABASE COMMIT TO SWITCHOVER TO PRIMARY;

Step 6

Finish the transition of the standby database to the primary database role. The task you perform in this step depends on whether the physical standby database was ever opened in read-only mode:

If the physical standby database has not been opened in read-only mode since the last time it was started, issue the SQL ALTER DATABASE OPEN statement to open the new primary database:

SQL> ALTER DATABASE OPEN;

Then, go to step 7.

If the physical standby database has been opened in read-only mode since the last time it was started, you must shut down the target standby database and restart it:

SQL> SHUTDOWN IMMEDIATE;

SQL> STARTUP;

The target physical standby database has now undergone a transition to the primary database role.

5 Rebuild standby database

5.1 Restoring All SAP Data to standby database

Copy backP01.log & from /sapbackup/dataP01/P01 to /oracle/P01/sapbackup/

cp backP01.log /oracle/P01/sapbackup

cp befmqveb.and /oracle/P01/sapbackup

Restore all sapdata* to standby database

Execute


/oracle/P01/sapbackup/mount_before_restore.sh

Using below command as oraP01:

brrestore -b -d disk -r /oracle/P01/102_64/dbs/initP01_disk.sap -m all

Execute


/oracle/P01/sapbackup/mount.sh

Copy backup controlfile

cd /sapbackup/dataP01/

cp cntrlP01.dbf /oracle/P01/sapdata1/cntrl/

cp cntrlP01.dbf /oracle/P01/saparch/cntrl/

cp cntrlP01.dbf /oracle/P01/origlogA/cntrl/

5.2 Copy Required Archive log

Copy required archive log file from Primary Database to /oracle/P01/oraarch/P01arch.

5.3 Recover standby database

Hence we are using backup online, first database need to be consistent.

Copy archive log from primary database to standby then we need to recover using command:

SQL> startup mount

SQL> recover database until cancel using backup controlfile;

SQL>shutdown immediate;

5.4 Mounting Back to Mode cio

Execute


/oracle/P01/sapbackup/mount-normal.sh

5.5 Creating a standby control file on the primary database

Carry out on: trstp1db_aix as oraP01

SQL> alter database create standby controlfile as '/oracle/P01/sapreorg/stdby_controlf.dbf' reuse;

The standby control file created now has to be copied to the standby host.

Do ftp that file to /oracle/P01/sapreorg at standby server (trstp1db_dr)

5.6 Distributing on the standby host

The file is copied into the directories which are stated in the database parameter file using the CONTROLFILES= parameter.

So, copy as following:

cp /oracle/P01/sapreorg/stdby_controlf.dbf /oracle/P01/sapdata1/cntrl/cntrlP01.dbf

cp /oracle/P01/sapreorg/stdby_controlf.dbf /oracle/P01/origlogA/cntrl/cntrlP01.dbf

cp /oracle/P01/sapreorg/stdby_controlf.dbf /oracle/P01/saparch/cntrl/cntrlP01.dbf

5.7 Mounting the standby database for the first time

This is done to test the function. It tests whether all database parameters match and whether the control files are in the right place and are readable. Also we can now take the chance to create a SPFILE from the copied initQAS.ora.

SQL> connect / as sysdba

SQL> create spfile from pfile;

SQL> startup mount

5.8 Start Redo Apply

On the standby database, issue the following command to start Redo Apply:

SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE NODELAY DISCONNECT FROM SESSION;

The statement includes the DISCONNECT FROM SESSION option so that Redo Apply runs in a background session

6 Check Applied Redo in Standby database

Run SQL Statement to see archive log that has been applied

SQL> SELECT SEQUENCE#, APPLIED from V$ARCHIVED_LOG;

7 Check Redo Shipping

Trias SAP ODG Failover

SAP Implementation Project

Page 12 of 1

Version eg. 1.1 E:\B. PROJECT DOCUMENTS\02 Blueprint\08 Deliverables\Draft Deliverables\MKM Draft 1.0\MKM Finance & Accounting Blueprint, v2.0.doc

30/10/2002 9:21 AM

_1311019510.pdf

24.07.2009 Page 1 of 11

SAP Note 105047 - Support for Oracle functions in the SAPenvironment

Note Language: English Version: 117 Validity: Valid Since15.06.2009

The displayed SAP Note is not up to date in the selected language /

Summary

SymptomYou want to use an Oracle feature that is not used in the standard SAPsystem.

More Terms

Cause and PrerequisitesThis note provides answers to questions concerning the possible use ofcertain Oracle products and options that are not used in the standard R/3system.

SolutionThis note provides information about Oracle features and tools that are notused at all in the SAP standard system or whose use is restricted in theSAP standard system. If you want to use a feature that does not appear inthis 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 SAPSupport, you can obtain support if problems occur as follows:

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

o If you bought the Oracle database from SAP, open a customer messageto SAP. This is forwarded internally to Oracle Development Supportif 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 thelicense. For more information, see Notes 740897 and 581312.

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

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

SELECT NAME, DETECTED_USAGES, CURRENTLY_USED, FIRST_USAGE_DATE

24.07.2009 Page 2 of 11


FROM DBA_FEATURE_USAGE_STATISTICSWHERE 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 onlyrestricted or are no longer supported at all, you should determine in whichcontext the feature is used and to what extent you actually require thisusage.Caution: Due to Oracle bug 5475037, the advanced security option istherefore, partially by mistake, displayed as 'used' (if there is an OPS$user with EXTERNAL password).

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

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

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

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

1. Advanced Security Option (ASO)

o Can be used (Note 973450).

2. Auditing

o You can use normal auditing.

o You cannot use Audit Vault.

3. Automatic Shared Memory Management (ASMM)

o Can be used.

o You must note the restrictions from Note 789011 (define lowerlimits for DB_CACHE_SIZE and SHARED_POOL_SIZE that are highenough).

4. Automatic Storage Management (ASM)

o Usage with Oracle 10g is not allowed.

o The usage of ASM in the SAP environment for Oracle 11 is planned.

5. BIGFILE Tablespace

o Cannot be used.

6. Block Change Tracking (10g or higher)

24.07.2009 Page 3 of 11



7. Change Data Capture (CDC)

o Cannot be used.

8. Configuration Support Manager (CSM)

o Its use is not supported (Note 1032636).

9. Database Configuration Assistant (DBCA)

o Not permitted to use DBCA to create a database.

10. Database Vault

o This is still in the pilot phase (see Note 828268)

o Open an SAP customer message for more information.

11. DB_BLOCK_SIZE different from 8 KB

o Block sizes smaller than 8 KB are not permitted.

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

o Multiple block sizes (equal to or greater than 8 KB) may be used,however: BR*TOOLS = 10g) is permitted(Note 966117)

25. Function-based indexes

o Can be used, but no SAP support is provided.

24.07.2009 Page 6 of 11


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

26. Index Organized Tables (IOTs)

o Can be used.

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

27. Installation media

o Only SAP Oracle installation media is permitted

o Customer-defined builds and Oracle standard installation media isnot permitted

28. Intermedia

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

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

29. Cloning Oracle software

o Copying or cloning Oracle software (for example, as described inthe metalink document 300062.1) is not permitted in the SAPenvironment.

o For more information, see Note 551542 (2).

30. Compression (Note 1289494)

o You can only use table compression in the cases described in Note701235.

o You can use table compression on PSA tables within piloting inaccordance with Note 1231895.

o You can use index compression in accordance with Note 1109743.

31. Materialized Views

o Can be used.

o For more information, see Note 741478.

32. MOVE

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

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

33. Objects Option

o Cannot be used (Note 740897).

24.07.2009 Page 7 of 11


34. OLAP


35. OCFS (Oracle Cluster File System)

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

36. ORACLE_HOME sharing

o Not permitted (that is, each database must have its own set ofOracle executables).

o Reason: This avoids dependencies with patches and upgrades.

37. Oracle Enterprise Linux (OEL)

o Cannot be used.

38. Parallel Execution

o Can be used.


39. Parallel Server (OPS)

o Cannot be used.

o Alternatively: Real Application Cluster (see below)

40. Partitioning

o 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).

o Subpartitioning permitted, but no SAP support. This is lost duringsystem copies and table conversions.

o For more information, see Notes 722188 and 742243.

41. Read-only mode

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

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

o You cannot use read-only tablespaces


42. Real Application Cluster (RAC)

o You can use this feature in accordance with Note 527843.

24.07.2009 Page 8 of 11


43. Recovery Manager (RMAN)

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

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

44. Recycle bin

o Cannot be used.

45. Remote Diagnostic Agent (RDA)


46. Resource Manager

o Cannot be used.

47. RESUMABLE


48. Reverse key indexes

o Can be used.


49. Sequences

o Can be used for customer-defined tables, but no SAP support isprovided.

o Cannot be used for SAP tables

50. Spatial

o Cannot be used.

51. SQL Loader (SQLLDR)

o Cannot be used.

52. Standard Edition

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

53. Statspack

o Can be used.


54. Streams

24.07.2009 Page 9 of 11


o Cannot be used.

55. Transparent Data Encryption (TDE)

o The prerequisites that are mentioned in Note 974876 are permitted.

56. Transparent Gateway (DB2)


57. Transportable Tablespaces

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

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

58. Trigger

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

o Logon Trigger can be used in accordance with Note 712777.

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

o Otherwise, it cannot be used

o You cannot use trigger-based real-time replication either.

59. Tuning Pack

o Can be used.

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

o Cannot be used in production environments (see Note 1173954).

Header DataRelease Status: Released for CustomerReleased on: 23.07.2009 14:13:40Original Lang.: GermanPriority: Recommendations/additional infoCategory: Consulting

Main Component: BC-DB-ORA Oracle

24.07.2009 Page 10 of 11


The Note is release-independent

Related Notes

Number Short Text1327890 Oracle resumable space allocation feature1289494 FAQ: Oracle compression1109743 Use of Index Key Compression for Oracle Databases1080376 Enhancements for reorganization and rebuild1032636 Oracle configuration manager1013049 FAQ: Oracle Data Pump1005931 Oracle Remote Diagnostic Agent (RDA)997990 Oracle Enterprise Linux / Oracle Unbreakable Linux990955 Oracle database 10g: Oracle Data Mining (ODM)976435 Support for Oracle Data Pump in BRSPACE974876 Transparent Data Encryption (TDE)973450 Oracle Advanced Security: Network encryption966117 Oracle Database 10g: Flashback Database964619 RMAN: Incremental backups with Block Change Tracking937492 FAQ: Oracle Flashback915242 FAQ: Reverse key indexes912620 FAQ: Oracle indexes817253 FAQ: Open a Database Read only789011 FAQ: Oracle memory areas742243 General table partitioning as of SAP_BASIS 46C741478 FAQ: Materialized views740897 Info about the Oracle license scope; Required Oracle options722188 FAQ: Oracle partitioning717484 FAQs: Oracle statspack712777 MCOD operation of R3 and BW in a database701235 Usage of Oracle compression and BW651060 FAQ: Oracle Parallel Execution641435 FAQ: Oracle Index Organized Tables (IOTs)598678 Oracle 9i: New functions592393 FAQ: Oracle588668 FAQ: Database statistics581312 Oracle database: licensing restrictions527843 Oracle RAC support in the SAP environment408532 Using the DBMS_STATS package for collecting statistics386413 Oracle Enterprise Manager (OEM) in the SAP environment355770 Oracle Enterprise Manager Database Control

24.07.2009 Page 11 of 11


Attributes

Attribut ValueDatabase system ORACLE

_1364818263/initP01.ora######################################################################### This init.ora profile is a transparent copy of Oracle spfile. ## It was created by BRARCHIVE at 2011-04-06 14.15.00. ## Please do not change this file! Maintain only the spfile. ## You can use BRSPACE for the altering of database parameters: ## brspace -f dbparam #########################################################################*._b_tree_bitmap_plans=FALSE*._bloom_filter_enabled=FALSE*._index_join_enabled=FALSE*._optim_peek_user_binds=FALSE*._optimizer_mjc_enabled=FALSE*._sort_elimination_cost_ratio=10*._table_lookup_prefetch_size=0*.background_dump_dest='/oracle/P01/saptrace/background'*.compatible='10.2.0'*.control_file_record_keep_time=30*.control_files='/oracle/P01/origlogA/cntrl/cntrlP01.dbf','/oracle/P01/saparch/cntrl/cntrlP01.dbf','/oracle/P01/sapdata1/cntrl/cntrlP01.dbf'*.core_dump_dest='/oracle/P01/saptrace/background'*.cursor_space_for_time=FALSE*.db_block_size=8192*.db_cache_size=16492674417*.db_files=1000*.db_name='P01'*.db_writer_processes=2*.dbwr_io_slaves=0*.disk_asynch_io=TRUE*.dml_locks=2500*.event='10191 trace name context forever, level 1','10027 trace name context forever, level 1','10028 trace name context forever, level 1','10183 trace name context forever, level 1','14532 trace name context forever, level 1','38087 trace name context forever, level 1','10891 trace name context forever, level 1','10091 trace name context forever, level 1'#Recommendation from SAP, ASWIN, 01/04/11*.filesystemio_options='setall'*.java_pool_size=67108864*.large_pool_size=33554432*.log_buffer=1524736*.log_checkpoint_interval=0*.log_checkpoints_to_alert=TRUE*.max_dump_file_size='20000'*.open_cursors=800*.optimizer_index_caching=50*.optimizer_index_cost_adj=20*.parallel_execution_message_size=16384*.parallel_max_servers=40*.parallel_threads_per_cpu=1*.pga_aggregate_target=1073741824*.processes=260*.query_rewrite_enabled='FALSE'*.recyclebin='off'*.remote_os_authent=TRUE*.replication_dependency_tracking=FALSE*.session_max_open_files=20*.sessions=520*.sga_max_size=29686813950*.shared_pool_size=16492674417*.sort_area_retained_size=0*.sort_area_size=2097152*.star_transformation_enabled='TRUE'*.streams_pool_size=50331648*.timed_statistics=TRUE*.undo_management='AUTO'*.undo_retention=43200*.undo_tablespace='PSAPUNDO'*.user_dump_dest='/oracle/P01/saptrace/usertrace'*.workarea_size_policy='AUTO'*.db_unique_name='P01_SBY'*.FAL_CLIENT='P01_SBY'*.FAL_SERVER='P01_PRM'*.local_listener='(ADDRESS = (PROTOCOL = TCP)(HOST = trstp1db_dr)(PORT = 1527))'*.LOG_ARCHIVE_CONFIG='DG_CONFIG=(P01_PRM,P01_SBY)'*.log_archive_dest_1='location="/oracle/P01/oraarch/P01arch" mandatory valid_for=(all_logfiles,all_roles)'*.log_archive_dest_2='service="(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=trstp1db_aix)(PORT=1527)))(CONNECT_DATA=(SERVICE_NAME=P01_PRM_DGMGRL)(INSTANCE_NAME=P01)(SERVER=dedicated)))"',' ARCH delay=180 OPTIONAL max_failure=100 max_connections=2 reopen=60 db_unique_name="P01_PRM" register net_timeout=10 valid_for=(online_logfile,primary_role)'*.log_archive_dest_state_1='ENABLE'*.log_archive_dest_state_2='ENABLE'*.log_archive_format='P01arch%t_%s_%r.dbf'*.log_archive_max_processes=2*.log_archive_min_succeed_dest=1*.log_archive_trace=0*.log_file_name_convert='P01','P01'*.REMOTE_LOGIN_PASSWORDFILE='EXCLUSIVE'*.standby_file_management='AUTO'*.standby_archive_dest='/oracle/P01/oraarch/P01arch/stby'

_1364817905/tnsnames.ora################# Filename......: tnsnames.ora# Created.......: created by SAP AG, R/3 Rel. >= 6.10# Name..........:# Date..........:# @(#) $Id: //bc/640-2/src/ins/SAPINST/impl/tpls/ora/ind/TNSNAMES.ORA#4 $################P01= (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (COMMUNITY = SAP.WORLD) (PROTOCOL = TCP) (HOST = trstp1db_dr) (PORT = 1527) ) ) (CONNECT_DATA = (SID = P01) (GLOBAL_NAME = P01) (SERVICE_NAME = P01_SBY) ) )P01_PRM=(DESCRIPTION =(ADDRESS_LIST =(ADDRESS =(COMMUNITY = SAP.WORLD)(PROTOCOL = TCP)(HOST = trstp1db_aix)(PORT = 1527) (SDU=32768)))(CONNECT_DATA =(SID = P01)(SERVICE_NAME= P01_PRM)))

_1364817818/sqlnet.ora################# Filename......: sqlnet.ora# Created.......: created by SAP AG, R/3 Rel. >= 6.10# Name..........:# Date..........:# @(#) $Id: //bc/640-2/src/ins/SAPINST/impl/tpls/ora/ind/SQLNET.ORA#4 $################AUTOMATIC_IPC = ONTRACE_LEVEL_CLIENT = OFF#NAMES.DEFAULT_DOMAIN = WORLDNAMES.DIRECTORY_PATH = (TNSNAMES)NAME.DEFAULT_ZONE = WORLDSQLNET.EXPIRE_TIME = 0TCP.NODELAY=YES

_1364817660/sqlnet.ora################# Filename......: sqlnet.ora# Created.......: created by SAP AG, R/3 Rel. >= 6.10# Name..........:# Date..........:# @(#) $Id: //bc/640-2/src/ins/SAPINST/impl/tpls/ora/ind/SQLNET.ORA#4 $################AUTOMATIC_IPC = ONTRACE_LEVEL_CLIENT = OFF#NAMES.DEFAULT_DOMAIN = WORLDNAMES.DIRECTORY_PATH = (TNSNAMES)NAME.DEFAULT_ZONE = WORLDSQLNET.EXPIRE_TIME = 0TCP.NODELAY=YES

_1364817696/listener.ora################# Filename......: listener.ora# Created.......: created by SAP AG, R/3 Rel. >= 6.10# Name..........:# Date..........:# @(#) $Id: //bc/640-2/src/ins/SAPINST/impl/tpls/ora/ind/LISTENER.ORA#4 $################ADMIN_RESTRICTIONS_LISTENER_P01 = onLISTENER_P01 = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = IPC) (KEY = P01.WORLD) ) (ADDRESS= (PROTOCOL = IPC) (KEY = P01) ) (ADDRESS = (COMMUNITY = SAP.WORLD) (PROTOCOL = TCP) (HOST = trstp1db_aix) (PORT = 1527) (SEND_BUF_SIZE = 9375000) (RECV_BUF_SIZE = 9375000) ) )STARTUP_WAIT_TIME_LISTENER_P01 = 0CONNECT_TIMEOUT_LISTENER_P01 = 0TRACE_LEVEL_LISTENER_P01 = OFFSID_LIST_LISTENER_P01 = (SID_LIST = (SID_DESC = (SID_NAME = P01)(GLOBAL_DBNAME=P01_PRM)(ORACLE_HOME = /oracle/P01/102_64) ) (SID_DESC =(SID_NAME = P01)(GLOBAL_DBNAME=P01_PRM_DGMGRL)(ORACLE_HOME = /oracle/P01/102_64) ) (SID_DESC =(SID_NAME = P01)(GLOBAL_DBNAME=P01_PRM_DGMGRL.WORLD)(ORACLE_HOME = /oracle/P01/102_64) ) (SID_DESC =(SID_NAME = P01)(GLOBAL_DBNAME=P01_PRM_XPT.WORLD)(ORACLE_HOME = /oracle/P01/102_64) ) (SID_DESC =(SID_NAME = P01)(GLOBAL_DBNAME=P01_PRM_DGB.WORLD)(ORACLE_HOME = /oracle/P01/102_64) ) )

_1311019510.pdf

24.07.2009 Page 1 of 11


Note Language: English Version: 117 Validity: Valid Since15.06.2009

The displayed SAP Note is not up to date in the selected language /

Summary

SymptomYou want to use an Oracle feature that is not used in the standard SAPsystem.

More Terms

Cause and PrerequisitesThis note provides answers to questions concerning the possible use ofcertain Oracle products and options that are not used in the standard R/3system.

SolutionThis note provides information about Oracle features and tools that are notused at all in the SAP standard system or whose use is restricted in theSAP standard system. If you want to use a feature that does not appear inthis 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 SAPSupport, you can obtain support if problems occur as follows:

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

o If you bought the Oracle database from SAP, open a customer messageto SAP. This is forwarded internally to Oracle Development Supportif 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 thelicense. For more information, see Notes 740897 and 581312.

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

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

SELECT NAME, DETECTED_USAGES, CURRENTLY_USED, FIRST_USAGE_DATE

24.07.2009 Page 2 of 11


FROM DBA_FEATURE_USAGE_STATISTICSWHERE 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 onlyrestricted or are no longer supported at all, you should determine in whichcontext the feature is used and to what extent you actually require thisusage.Caution: Due to Oracle bug 5475037, the advanced security option istherefore, partially by mistake, displayed as 'used' (if there is an OPS$user with EXTERNAL password).

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

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

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

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

1. Advanced Security Option (ASO)


2. Auditing

o You can use normal auditing.

o You cannot use Audit Vault.

3. Automatic Shared Memory Management (ASMM)

o Can be used.

o You must note the restrictions from Note 789011 (define lowerlimits for DB_CACHE_SIZE and SHARED_POOL_SIZE that are highenough).

4. Automatic Storage Management (ASM)

o Usage with Oracle 10g is not allowed.

o The usage of ASM in the SAP environment for Oracle 11 is planned.

5. BIGFILE Tablespace

o Cannot be used.

6. Block Change Tracking (10g or higher)

24.07.2009 Page 3 of 11



7. Change Data Capture (CDC)

o Cannot be used.

8. Configuration Support Manager (CSM)

o Its use is not supported (Note 1032636).

9. Database Configuration Assistant (DBCA)

o Not permitted to use DBCA to create a database.

10. Database Vault

o This is still in the pilot phase (see Note 828268)

o Open an SAP customer message for more information.

11. DB_BLOCK_SIZE different from 8 KB

o Block sizes smaller than 8 KB are not permitted.

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

o Multiple block sizes (equal to or greater than 8 KB) may be used,however: BR*TOOLS = 10g) is permitted(Note 966117)

25. Function-based indexes


24.07.2009 Page 6 of 11


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

26. Index Organized Tables (IOTs)

o Can be used.

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

27. Installation media

o Only SAP Oracle installation media is permitted

o Customer-defined builds and Oracle standard installation media isnot permitted

28. Intermedia

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

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

29. Cloning Oracle software

o Copying or cloning Oracle software (for example, as described inthe metalink document 300062.1) is not permitted in the SAPenvironment.

o For more information, see Note 551542 (2).

30. Compression (Note 1289494)

o You can only use table compression in the cases described in Note701235.

o You can use table compression on PSA tables within piloting inaccordance with Note 1231895.

o You can use index compression in accordance with Note 1109743.

31. Materialized Views

o Can be used.


32. MOVE

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

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

33. Objects Option


24.07.2009 Page 7 of 11


34. OLAP


35. OCFS (Oracle Cluster File System)

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

36. ORACLE_HOME sharing

o Not permitted (that is, each database must have its own set ofOracle executables).

o Reason: This avoids dependencies with patches and upgrades.

37. Oracle Enterprise Linux (OEL)

o Cannot be used.

38. Parallel Execution

o Can be used.


39. Parallel Server (OPS)

o Cannot be used.

o Alternatively: Real Application Cluster (see below)

40. Partitioning

o 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).

o Subpartitioning permitted, but no SAP support. This is lost duringsystem copies and table conversions.

o For more information, see Notes 722188 and 742243.

41. Read-only mode

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

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

o You cannot use read-only tablespaces


42. Real Application Cluster (RAC)

o You can use this feature in accordance with Note 527843.

24.07.2009 Page 8 of 11


43. Recovery Manager (RMAN)

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

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

44. Recycle bin

o Cannot be used.

45. Remote Diagnostic Agent (RDA)


46. Resource Manager

o Cannot be used.

47. RESUMABLE


48. Reverse key indexes

o Can be used.


49. Sequences

o Can be used for customer-defined tables, but no SAP support isprovided.

o Cannot be used for SAP tables

50. Spatial

o Cannot be used.

51. SQL Loader (SQLLDR)

o Cannot be used.

52. Standard Edition

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

53. Statspack

o Can be used.


54. Streams

24.07.2009 Page 9 of 11


o Cannot be used.

55. Transparent Data Encryption (TDE)

o The prerequisites that are mentioned in Note 974876 are permitted.

56. Transparent Gateway (DB2)


57. Transportable Tablespaces

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

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

58. Trigger

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

o Logon Trigger can be used in accordance with Note 712777.

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

o Otherwise, it cannot be used

o You cannot use trigger-based real-time replication either.

59. Tuning Pack

o Can be used.

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

o Cannot be used in production environments (see Note 1173954).

Header DataRelease Status: Released for CustomerReleased on: 23.07.2009 14:13:40Original Lang.: GermanPriority: Recommendations/additional infoCategory: Consulting

Main Component: BC-DB-ORA Oracle

24.07.2009 Page 10 of 11


The Note is release-independent

Related Notes

Number Short Text1327890 Oracle resumable space allocation feature1289494 FAQ: Oracle compression1109743 Use of Index Key Compression for Oracle Databases1080376 Enhancements for reorganization and rebuild1032636 Oracle configuration manager1013049 FAQ: Oracle Data Pump1005931 Oracle Remote Diagnostic Agent (RDA)997990 Oracle Enterprise Linux / Oracle Unbreakable Linux990955 Oracle database 10g: Oracle Data Mining (ODM)976435 Support for Oracle Data Pump in BRSPACE974876 Transparent Data Encryption (TDE)973450 Oracle Advanced Security: Network encryption966117 Oracle Database 10g: Flashback Database964619 RMAN: Incremental backups with Block Change Tracking937492 FAQ: Oracle Flashback915242 FAQ: Reverse key indexes912620 FAQ: Oracle indexes817253 FAQ: Open a Database Read only789011 FAQ: Oracle memory areas742243 General table partitioning as of SAP_BASIS 46C741478 FAQ: Materialized views740897 Info about the Oracle license scope; Required Oracle options722188 FAQ: Oracle partitioning717484 FAQs: Oracle statspack712777 MCOD operation of R3 and BW in a database701235 Usage of Oracle compression and BW651060 FAQ: Oracle Parallel Execution641435 FAQ: Oracle Index Organized Tables (IOTs)598678 Oracle 9i: New functions592393 FAQ: Oracle588668 FAQ: Database statistics581312 Oracle database: licensing restrictions527843 Oracle RAC support in the SAP environment408532 Using the DBMS_STATS package for collecting statistics386413 Oracle Enterprise Manager (OEM) in the SAP environment355770 Oracle Enterprise Manager Database Control

24.07.2009 Page 11 of 11


Attributes

Attribut ValueDatabase system ORACLE

Documents

TRIAS SAP Prod Build ODG v0.3 by Sugik