Thursday Nov 20, 2014

SAP w/ Oracle Database 12cR1

Oracle Database 12c Release 1 (12.1)
NEW! 12.1.0.2 planned to be first release for SAP
  • hereby breaking ‘Terminal Release’ custom valid to date
        − to ensure sufficient overlap with 11g
  • No support of base release 12.1.0.1
  • Starting from SAP NetWeaver 7.X based products
  • Rollout planned for Q1/2015

        − Base certification w/o major 12c features
        − Staged rollout for major features later

New Features planned with initial certification:

  • Windows: Support for standard user for services, database instances and Oracle Net services
  • Advanced Index Compression1

        – Automatic Prefix computation

        – Higher compression rate, Ease of Use

  • Client-Server Network Compression2
        – Less network load between App Servers and Database Instance(s)
  • Concurrent Execution of Union and Union All Branches
        – Improves BW Performance
  • ACFS Support on Exadata
        – For SAP shared file system support (/sapmnt, etc.)
  • RAC: HA-NFS support with ACFS
        – Complete SAP HA solution for shared file system
  • RMAN: Cross platform backup and restore
        – Faster and easier heterogeneous platform migration
  • Storage Snapshot Optimization
        – no more begin/end backup for certain snapshot technologies
  • Active Data Guard Far Sync 2
        – High performance zero data loss across large distance WAN

1) requires Advanced Compression Option

2) requires Active Data Guard Option

New Features not available with initial certification:

  • Rollout in staged approach
  • Information Lifecycle Management (ILM)/ADO1
  • Multitenant (aka. Pluggable Databases)2
  • In-Memory3
  • Hybrid Columnar Compression (HCC)1, 4 for Exadata
  • OCI/Database Interface: Array Row Count for Array DML Operations
  • Online Move Partition
  • Move a Datafile Online

1) requires Advanced Compression Option

2) requires new Multitenant Option

3) requires new Database In-Memory Option

4) Automatic Data Optimization (ADO) prerequisite

Wednesday Nov 19, 2014

EBS w/ Database 12cR1

1. Certification
  • Database 12.1.0.1

Database 12.1.0.1 Certified with EBS 11i
Database 12.1.0.1 Certified with EBS 12.0
Database 12.1.0.1 Certified with EBS 12.1
Database 12.1.0.1 Certified with EBS 12.2

  • Database 12.1.0.2

Database 12.1.0.2 Certified with E-Business Suite 12.1

2. Migration

  • Datapump

     Export/Import EBS release 12.0 or 12.1 with RDBMS 12c (Note ID 1585256.1)

  • TTS

     Using Transportable Tablespaces to Migrate Oracle EBS Release 12.0 or 12.1 Using Oracle Database 12.1.0 (Note ID 1945814.1)

3. Interoperability Note

  • Database Patch Set Update Overlay Patches Required for Use with PSUs and Oracle E-Business Suite (Note ID 1147107.1)
  • Interoperability Notes 11i with RDBMS 12cR1 (Note ID 1524399.1)
  • Interoperability Notes Oracle EBS Release 12.1 with Oracle Database 12c Release 1 (12.1.0) (Note ID 1930134.1)
  • Interoperability Notes Oracle EBS 12.2 with Oracle Database 12 Release 1 (Note ID 1926201.1)


4. 12c New Feature Certifications

  • Database In-Memory Option -- Certificated
  • Oracle Multitenant -- Pending

Monday Sep 23, 2013

In-Memory in Oracle

  • Oracle TimesTen In-Memory Database
    Oracle TimesTen In-Memory Database, is a memory-optimized, stand-alone relational database that empowers applications with the responsiveness and high throughput required by today's real-time enterprises and industries such as telecommunications, capital markets, and defense. Deployed in the application or middle tier as an embedded database, TimesTen uses standard structured query language (SQL) to operate on databases that fit entirely in physical memory.

 

  • Oracle In-Memory Database Cache
    Oracle In-Memory Database Cache is an Oracle Database option that is ideal for caching performance-critical subsets of an Oracle database’s frequently accessed data for improved response time in the application tier. IMDB Cache uses TimesTen as its RDBMS engine. IMDB Cache offers applications the full generality and functionality of a relational database, the transparent maintenance of cache consistency with the Oracle database, and the real-time performance of an in-memory database.

 

  • Oracle In-Memory Parallel Execution
    Oracle In-Memory Parallel Execution (In-Memory PX) introduced in Oracle Database 11g Release 2, takes advantage of this large aggregated database buffer cache. By having PX servers access objects via the database buffer cache they can scan data at least 10 X faster than they can on disk.

 

  • Oracle Exalytics In-Memory Machine
    Oracle Exalytics In-Memory Machine is the first engineered system specifically designed to deliver high performance analysis, modeling, and planning. Built by using industry-standard hardware, Oracle’s BI software, and in-memory database technology, Oracle Exalytics is an optimized system that delivers answers to all your business questions with unmatched speed, intelligence, simplicity, and manageability.

 

  • Oracle Exadata X3 Database In-Memory Machine
    Oracle Exadata X3 Database In-Memory Machine can store up to hundreds of Terabytes of compressed user data in Flash and RAM memory, virtually eliminating the performance overhead of reads and writes to slow disk drives, making Exadata X3 systems the ideal database platforms for the varied and unpredictable workloads of cloud computing.

 

  • Oracle In-Memory Applications
    Oracle In-Memory Applications are new set of application tools that provides a bottoms-up approach to maximizing profit margins by enabling near real-time insight. Oracle In-Memory Applications are built ground up to leverage Oracle’s unique hardware and technology capabilities: Exadata’s industry-leading data storage technologies, Exalogic’s middle tier technology, and Exalytics’ in-memory applications, all connected using InfiniBand technology to deliver extreme performance.

 

  • Oracle Database In-Memory Option
    Oracle Database In-Memory option is a solution for accelerating database-driven business decision-making to real-time speeds. Unlike specialized approaches that are restricted to particular workloads or applications, the unique approach of Oracle Database In-Memory leverages a new in-memory column store format to speed up analytic, data warehousing, and reporting workloads, while also accelerating transaction processing (OLTP) workloads.

Tuesday Jul 23, 2013

Exadata X3 Database12c Update

Exadata Database Machine X3-2 Data Sheet New Jun 2013

• Oracle Database 11g and 12c.

Exadata Database Machine X3-8 Data Sheet New Jun 2013

• Oracle Database 11g and 12c

Oracle In-Memory Applications Whitepapers

      

EBS

OTM

VCP

HYPERION

FUSION APPLICATIONS

JDE

PSFT

SIEBEL

BI

Monday Dec 10, 2012

Oracle Database Appliance Now Certified by SAP

All SAP products based on SAP NetWeaver 7.x that are also certified for Oracle Database 11g Release 2 (single node or RAC) can now be used with the Oracle Database Appliance. RAC One Node is NOT supported.

Only Three-Tier SAP Installations. Only the Oracle database can run on the Oracle Database Appliance.

 No SAP instance can be deployed on the Oracle Database Appliance. SAP instances have to run on different middle-tier machines of any hardware architecture and operating system.

Central Services (ASCS and/or SCS) can be configured to run on the Oracle Database Appliance for Unicode installations of SAP.

SAP BR*Tools support is now available for the Oracle Database Appliance.

For more information about SAP on ODA, please refer:

Using SAP NetWeaver with the Oracle Database Appliance New Nov2012
Note 1760737 - SAP Software and Oracle Database Appliance (ODA)
Note 1785353 - ODA 11.2.0: Patches for 11.2.0.3

 

Sunday Nov 25, 2012

How to recreate spfile on Exadata?

  1. Copy spfile from the ASM diskgroup to local disk by using the ASMCMD command line tool.
     ASMCMD> pwd
    +DATA_DM01/EDWBASE
    ASMCMD> ls -l
    Type Redund Striped Time Sys Name
    Y CONTROLFILE/
    Y DATAFILE/
    Y ONLINELOG/
    Y PARAMETERFILE/
    Y TEMPFILE/
    N spfileedwbase.ora =>
    +DATA_DM01/EDWBASE/PARAMETERFILE/spfile.355.800017117
    ASMCMD> cp +DATA_DM01/EDWBASE/spfileedwbase.ora /home/oracle/spfileedwbase.ora.bak
  2. Copy the context from spfileedwbase.ora.bak to initedwbase.ora except garbled character.
  3. Using above initedwbase.ora, start one of the RAC instances to the mount phase. 
     SQL> startup mount pfile=/home/oracle/initedwbase.ora
  4. Ensure one of the database instances is mounted before attempting to recreate the spfile. 
    SQL> select INSTANCE_NAME,HOST_NAME,STATUS from v$instance;
    INSTANCE_NAME HOST_NAME  STATUS
    ------------- ---------  ------
    edwbase1      dm01db01   MOUNTED
  5. Create the new spfile.
    SQL> create spfile='+DATA_DM01/EDWBASE/spfileedwbase.ora' from pfile='/home/oracle/initedwbase.ora';
  6. ASMCMD will show that a new spfile has been created as the alias spfilerac2.ora is now pointing to a new spfile under the PARAMETER directory in ASM.
    ASMCMD> pwd
    +DATA_DM01/EDWBASE
    ASMCMD> ls -l
    Type Redund Striped Time Sys Name
    Y CONTROLFILE/
    Y DATAFILE/
    Y ONLINELOG/
    Y PARAMETERFILE/
    Y TEMPFILE/
    N spfilerac2.ora =>
    +DATA_DM01/EDWBASE/PARAMETERFILE/spfile.356.800013581
     
  7. Shutdown the instance and restart the database using srvctl using the newly created spfile.
    SQL> shutdown immediate
    ORA-01109: database not open
    Database dismounted.
    ORACLE instance shut down.
    SQL> exit
    [oracle@dm01db01 ~]$ srvctl start database -d edwbase
    [oracle@dm01db01 ~]$ srvctl status database -d edwbase
    Instance edwbase1 is running on node dm01db01
    Instance edwbase2 is running on node dm01db02
  8. ASMCMD will now show a number of spfiles exist in the PARAMETERFILE directory for this database. The spfile containing the parameter preventing startups
    should be removed from ASM.
    In this case the file spfile.355.800017117 can be removed because spfile.356.800013581 is the current spfile.
    ASMCMD> pwd
    +DATA_DM01/EDWBASE
    ASMCMD> cd PARAMETERFILE
    ASMCMD> ls -l
    Type Redund Striped Time Sys Name
    PARAMETERFILE UNPROT COARSE FEB 19 08:00:00 Y spfile.355.800017117
    PARAMETERFILE UNPROT COARSE FEB 19 08:00:00 Y spfile.356.800013581
    ASMCMD> rm spfile.355.800017117
    ASMCMD> ls
    spfile.356.800013581

Referenece: Recreating the Spfile for RAC Instances Where the Spfile is Stored in ASM [ID 554120.1]

Monday Oct 29, 2012

Exadata X3 Expandability Update

Exadata Database Machine X3-2 Data Sheet New 10/29/2012

Up to 18 racks can be connected without requiring additional InfiniBand switches.

Exadata Database Machine X3-8 Data Sheet New 10/24/2012

Scale by connecting multiple Exadata Database Machine X3-8 racks or Exadata Storage Expansion Racks. Up to 18 racks can be connected by simply connecting via InfiniBand cables. Larger configurations can be built with additional InfiniBand switches.


 

White Paper for SAP on Oracle Database Features & Options

SAP on Oracle Development Update New Oct2013

RAT for SAP

RAC for SAP

OCFS for SAP

DG for SAP

OEM for SAP

Partition for SAP

Security for SAP

ODV for SAP 

TDE for SAP 

AC for SAP

ASM for SAP

Monday Oct 15, 2012

Using CTAS & Exchange Partition Replace IAS for Copying Partition on Exadata

Usage Scenario:

Copy data&index from one partition to another partition in a partitioned table.

Solution:

  1. Create a partition definition
    Copy data from one partition to another partiton by 'Insert as select (IAS)'
  2. Create a nonpartitioned table by 'Create table as select (CTAS)'
    Convert a nonpartitioned table into a partition of partitoned table by exchangng their data segments.
    Rebuild unusable index

Exchange Partition Convertion

  1. Mutual convertion between a partition (or subpartition) and a nonpartitioned table
  2. Mutual convertion between a hash-partitioned table and a partition of a composite *-hash partitioned table
  3. Mutual convertiton a [range | list]-partitioned table into a partition of a composite *-[range | list] partitioned table.

Exchange Partition Usage Scenario

  1. High-speed data loading of new, incremental data into an existing partitioned table in DW environment
  2. Exchanging old data partitions out of a partitioned table, the data is purged from the partitioned table without actually being deleted and can be archived separately

Exchange Partition Syntax

ALTER TABLE schema.table EXCHANGE [PARTITION|SUBPARTITION] [partition|subprtition] WITH TABLE schema.table [INCLUDE|EXCLUDING] INDEX [WITH|WITHOUT] VALIDATION UPDATE [INDEXES|GLOBAL INDEXES]

INCLUDING | EXCLUDING INDEXES Specify INCLUDING INDEXES if you want local index partitions or subpartitions to be exchanged with the corresponding table index (for a nonpartitioned table) or local indexes (for a hash-partitioned table). Specify EXCLUDING INDEXES if you want all index partitions or subpartitions corresponding to the partition and all the regular indexes and index partitions on the exchanged table to be marked UNUSABLE. If you omit this clause, then the default is EXCLUDING INDEXES.

WITH | WITHOUT VALIDATION Specify WITH VALIDATION if you want Oracle Database to return an error if any rows in the exchanged table do not map into
partitions or subpartitions being exchanged. Specify WITHOUT VALIDATION if you do not want Oracle Database to check the proper mapping of rows in the exchanged table. If you omit this clause, then the default is WITH VALIDATION. 

UPADATE INDEX|GLOBAL INDEX Unless you specify UPDATE INDEXES, the database marks UNUSABLE the global indexes or all global index partitions on the table whose partition is being exchanged. Global indexes or global index partitions on the table being exchanged remain invalidated. (You cannot use UPDATE INDEXES for index-organized tables. Use UPDATE GLOBAL INDEXES instead.)

Exchanging Partitions&Subpartitions Notes

  1. Both tables involved in the exchange must have the same primary key, and no validated foreign keys can be referencing either of the tables unless the referenced
    table is empty.
  2.  When exchanging partitioned index-organized tables:
    – The source and target table or partition must have their primary key set on the same columns, in the same order.
    – If key compression is enabled, then it must be enabled for both the source and the target, and with the same prefix length.
    – Both the source and target must be index organized.
    – Both the source and target must have overflow segments, or neither can have overflow segments. Also, both the source and target must have mapping
    tables, or neither can have a mapping table.
    – Both the source and target must have identical storage attributes for any LOB columns. 

Sunday Oct 14, 2012

Partition Table and Exadata Hybrid Columnar Compression (EHCC)

  • Create EHCC table
    • CREATE TABLE ... COMPRESS FOR [QUERY LOW|QUERY HIGH|ARCHIVE LOW|ARCHIVE HIGH];

      select owner,table_name,compress_for DBA_TABLES where compression = ‘ENABLED';
  • Convert Table/Partition/Subpartition to EHCC
    • Compress Table&Partition&Subpartition to EHCC:
      ALTER TABLE table_name MOVE COMPRESS FOR [QUERY LOW|QUERY HIGH|ARCHIVE LOW|ARCHIVE HIGH] [PARALLEL <dop>];
      ALTER TABLE table_name MOVE PARATITION partition_name COMPRESS FOR [QUERY LOW|QUERY HIGH|ARCHIVE LOW|ARCHIVE HIGH] [PARALLEL <dop>];
      ALTER TABLE table_name MOVE SUBPARATITION subpartition_name COMPRESS FOR [QUERY LOW|QUERY HIGH|ARCHIVE LOW|ARCHIVE HIGH] [PARALLEL <dop>];

      select owner,table_name,compress_for DBA_TABLES where compression = ‘ENABLED';
      select table_owner,table_name,partition_name,compress_for DBA_TAB_PARTITIONS where compression = ‘ENABLED’;
      select table_owner,table_name,subpartition_name,compress_for DBA_TAB_SUBPARTITIONS where compression = ‘ENABLED’;

    • Rebuild Unusable Index:
      select index_name from dba_indexes where status = 'UNUSABLE';
      select index_name,partition_name from dba_ind_partitions where status = 'UNUSABLE';
      select index_name,subpartition_name from dba_ind_subpartitions where status = 'UNUSABLE';

      ALTER INDEX index_name REBUILD [PARALLEL <dop>];
      ALTER INDEX index_name REBUILD PARTITION partition_name [PARALLEL <dop>];
      ALTER INDEX index_name REBUILD SUBPARTITION subpartition_name [PARALLEL <dop>];
  • Convert Table/Partition/Subpartition from EHCC to OLTP compression or uncompressed format:
    • Uncompress EHCC Table&Partition&Subpartition:
      ALTER TABLE table_name MOVE [NOCOMPRESS|COMPRESS for OLTP] [PARALLEL <dop>];
      ALTER TABLE table_name MOVE PARTITION partition_name [NOCOMPRESS|COMPRESS for OLTP] [PARALLEL <dop>];
      ALTER TABLE table_name MOVE SUBPARTITION subpartition_name [NOCOMPRESS|COMPRESS for OLTP] [PARALLEL <dop>];

      select owner,table_name,compress_for DBA_TABLES where compression = '';
      select table_owner,table_name,partition_name,compress_for DBA_TAB_PARTITIONS where compression = '';
      select table_owner,table_name,subpartition_name,compress_for DBA_TAB_SUBPARTITIONS where compression = '';
    • Rebuild Unusable Index:
      select index_name from dba_indexes where status = 'UNUSABLE';
      select index_name,partition_name from dba_ind_partitions where status = 'UNUSABLE';
      select index_name,subpartition_name from dba_ind_subpartitions where status = 'UNUSABLE';

      ALTER INDEX index_name REBUILD [PARALLEL <dop>];
      ALTER INDEX index_name REBUILD PARTITION partition_name [PARALLEL <dop>];
      ALTER INDEX index_name REBUILD SUBPARTITION subpartition_name [PARALLEL <dop>];

Friday Oct 12, 2012

SAP Software on Oracle Exadata X3

Note 1590515 - SAP Software and Oracle Exadata New v17 04.10.2012

Oracle Exadata Database Machine can be used in SAP environments when the following conditions are met:

  • Supported Oracle Exadata Database Machine models:
    • X2-2
    • X2-8
    • X3-2
    • X3-8

Wednesday Oct 10, 2012

Document Link about Database Features on Exadata

DBFS(Database File System) on Exadata

DBRM/IORM(Database Resource Manager, I/O Resource Manager) on Exadata 

EHCC(Exadata Hybrid Columnar Compression) on Exadata 
 
PX(Paralle Execution) on Exadata

Partition on Exadata

FTP on Exadata

VNC on Exadata

  • Enable database hosts in Exadata Database Machine for using up2date or yum and vncserver [ID 1234710.1]  

XP(Exchange Partition) on Exadata

OGG(Oracle Golden Gate) on Exadata

BR(Backup & Recovery) on Exadata

OEM(Oracle Enterprise Manager) on Exadata

MAA(Maximum Availability Architecture) on Exadata

DG(Data Guard) on Exadata

Consolidation on Exadata

IB(InfiniBand) on Exadata

About

Bandari Huang | Exadata Solution Consultant Phone: +86-21-2302-3838 | Mobile: +86-156-9213-8783 Oracle Exadata & Strategic Solutions Consulting, Great China

Search

Categories
Archives
« March 2015
SunMonTueWedThuFriSat
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
    
       
Today