Professional Documents
Culture Documents
Patches
Parameters
Statistics
SAP Note 1503709 - Oracle 11.2.0: Patches / Patch collections for 11.2.0.2
SAP Note 1631931 - Oracle 11.2.0: Patches / Patch collections for 11.2.0.3
Managing 11g database Performance:
Parameters
Part of SAP recommends base lines
It changes whenever necessary
CBO related parameters
Events and underscore parameters
Can be different from BI to R/3
Instance Instance
1 2
Executables and
Node A archive logs on Node B
shared disks
Database files
on shared disks
Benefits of Oracle Real Application
Clusters
RAC is a natural extension for 3-tier SAP architecture.
For top-end users: High Availability
Fully use the existing hardware-based HA solution.
Have a control of hardware upgrade cycle.
Avoid certain OS limitation.
Dont forget the DG.
More cost-sensitive users: Scalability
Use Linux to replace more expensive UNIX system.
Can run multiple landscapes in a Linux based RAC system.
TAF in SAP environment
RAC
One
2 Listener level providing SCAN
Application
Server
Oracle RAC
Database
SCAN Local
Cluster
Listener
Listener
s
Clients s
2 Listener level providing SCAN
Application
Server
1
2
3
Oracle RAC
SCAN Local Database
Listeners Cluster
Clients Listeners
1. client asks the scan-listener adressed by one of the 3 scan ips for TNS
service
2. scan listener responds to client with right node-listener address
3. client asks node listener for service
11.2 network DNS connect
3
corporate
DNS
1 domain
2 DNS 4
SCAN listeners
client
Local listeners
SCAN address
Resolved by 3 fix IPs
returned in a round
robin fashion
Oracle RAC cluster - GRIDA
SCAN internal features used
Verifying scan
GNS / No GNS
IP Adresses
Listener configuration
TNS configuration
11.2 network
Hint:
check for identical MTU size on all network adapters,
1500 bytes recommended during GRID and RAC
installation
MTU can be set to 9000 after installation finished
2 posible ways to reach new SCAN listeners to connect
to database:
1. Configure new GNS service : cluster-DNS-subdomain
plus one fix IP is needed (strongly recommended)
2. Configure current DNS server to resolve SCAN address
to 3 fix IPs, many fix IPs needed!
IP adresses
GNS setup needs:
One hostname per host
One GNS-vip
One abap-vip, one java-vip
One asinst-vip per asinst
and DNS subdomain
DHCP configured
Static (DNS) setup needs
One hostname, rac-vip per host
One abap-vip, one java-vip
One asinst-vip per asinst
3 SCAN IPs (one name and 3 IPs)
Single Client Access Name
Network Configuration for SCAN - DNS
Requires a DNS adress entry to be used
In DNS, SCAN is a single name defined to resolve to 3 IP-addresses:
saprac-scan IN A 192.168.119.202
IN A 192.168.119.203
IN A 192.168.119.204
gns.clu1.saptest.pub. IN A 192.168.180.60
Verify setting of scans:
$ srvctl config scan
SCAN name: scan.clu1.saptest.pub, Network:
1/192.168.180.0/255.255.255.0/eth0
SCAN VIP name: scan1, IP: /192.168.180.122/192.168.180.122
SCAN VIP name: scan2, IP: /192.168.180.123/192.168.180.123
SCAN VIP name: scan3, IP: /192.168.180.124/192.168.180.124
Listeners
Init.ora Init.ora
Db_domain=world
Service_names=...,RAC001,...
TNS-Setup (tnsnames.ora) 11g
EDU.WORLD =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = scan-vip)(PORT = 1527))
(CONNECT_DATA =
(SERVICE_NAME = EDU.WORLD)
(GLOBAL_NAME = EDU.WORLD) - ERASE!!!!
) )
Not necessary
No address list
Scan address used only
No TAF or failover entries, provided in CRS TNS service definition
srvctl add service -d <db_unique_name> -s <service_name> -r "<preferred_instance>" -a
"<failover_instances>" -P BASIC -k <net_num> -l PRIMARY -e SELECT -z
<failover_retries> -w <failover_delay>
TNS-Setup / Services (11g)
lsnrctl status:
Service "EDU_DVEBMGS00_saprac1" has 1 instance(s).
Instance "EDU001", status READY, has 1 handler(s) for this service...
remote_listener //<SCAN-vip.domain>:<port>
<ORACLE_SID>.service_names (<DBSID>,<ORACLE_SID>)
Instance Profile
SAPSYSTEMNAME=EDU
SAPDBHOST=<node vip>
INSTANCE_NAME=D04
dbs/ora/tnsname=//saprac-scan.de.oracle.com/EDU_D02.world
Start Profile
EZCONNECT = //saprac-scan.de.oracle.com/EDU_D02.world
SETENV_03 = dbs_ora_tnsname=$(EZCONNECT)
Performance
Scalability
High availability
Load Balancing?
Distribute work manually!
All work processes within same SAP application instance
should always connect to same Oracle database instance.
Performance
Unselective indexes
NRIV
VBDATA/VBHDR/VBMOD
ARFC*
EDI*
Range partition and hash partition
Drilldown
Waits
IO
Network
Load (CPU)
Buffercache sizing
Additional CR and PI images
GRD
Need 10% more memory in buffercache
Check Buffercache:
select status, count(status)
from v$bh group by status;
RAC Performance
Tables Tables
Tablespace 0010 0010 0010 0010 0010 Tablespace
Files 0010 0010 0010 0010 0010
Files Automatic
File Systems Disk Group Storage
LVM Management
Disks Disks
Networked Storage
(SAN, NAS, DAS)
ASM Components
Disk Group
Disk A Disk B Disk C Disk D
1 2 3 4
File
5 6 7 8
Disk
Group
Disk
File
Allocation
Unit
Allocation Units
ASM disks are divided into allocation units (AU):
AU size is configurable at disk group creation
Default AU size is 1MB:
Small enough to be cached by database and large enough for
efficient sequential access
Allowable AU sizes:
1, 2, 4, 8, 16, 32, or 64 MB
Large AUs may be useful in very large database (VLDB)
scenarios or when using specialized storage hardware
Oracle recommends that the allocation unit (AU) size for
a disk group be set to 4 megabytes (MB) for large system.
SAP prefers to use default 1 MB.
4 MB on Exadata
ASM Files
ASM files:
Are a collection of AUs
Analogous to extents in a filesystem
Appear as normal files to the database kernel
Have file names that start with '+'
For example,
+DATA/P11/datafile/psapsr3.260.738399155
May be associated with an optional alias file name
For example, +DATA/P11/datafile/system01.dbf
Are evenly distributed across disks in a disk group
Are mirrored according to the policies defined in the disk group
ASM Disks
ASM disks:
Are the storage devices provisioned to ASM disk groups
Are accessed through normal O/S interfaces
Must be read and write accessible by the ASM owner
Must be accessible by all nodes in a cluster
May have different O/S names or paths on different nodes
May be:
An entire physical disk or partition of a physical disk
Logical volumes
Network-attached files (NFS)
ASM Disk Groups
Rename directory
SQL> ALTER DISKGROUP DATA RENAME DIRECTORY '+DATA/PRD/sapdata' to
'+DATA/PRD/sapdata_old';
Or
ASMCMD> mv +DATA/PRD/sapdata +DATA/PRD/sapdata_old
Drop directory
SQL> ALTER DISKGROUP DATA DROP DIRECTORY '+DATA/PRD/sapdata;
Or
ASMCMD> rm +DATA/PRD/sapdata_old
ASM Files and Directories
Create and remove alias
ASMCMD> mkalias source target
ASMCMD>rmalias
Copy a file
ASMCMD>cp <ASM_FILE> <OS_FILE>
V$ASM_DISKGROUP
V$ASM_DISK
V$ASM_FILE
V$ASM_ALIAS
V$ASM_ATTRIBUTE
What is ASM Cluster File System
ACFS is multi-platform, scalable file system, and storage
management technology
ACFS extends Oracle Automatic Storage Management (Oracle
ASM) functionality to support customer files maintained outside of
Oracle Database
ACFS supports many database and application files, including
executables, database trace files, database alert logs, application
reports
Oracle ASM is the preferred storage manager for all database
files. It is optimized for best performance for Database files
Oracle ACFS is the preferred file manager for non-database files.
It is optimized for general purpose files.
Starting with 11gR2 Oracle ASM is the preferred storage
platform for SAP (single instance and RAC)
ASM Cluster File System
Oracle Management of File System Data