Scribd
Upload
50 views

Ds Imdb Cache

Oracle In-Memory Database Cache is ideal for caching a performance-critical subset of an Oracle Database in the application tier. Applications perform read / write operations on the cache tables using SQL, PL / SQL, and Pro C. A Cache Grid consists of a collection of Oracle In-Memory Database Caches (IMDB Cache) that collectively manage an application's cached data.

Uploaded by

samydog
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
50 views

Ds Imdb Cache

Oracle In-Memory Database Cache is ideal for caching a performance-critical subset of an Oracle Database in the application tier. Applications perform read / write operations on the cache tables using SQL, PL / SQL, and Pro C. A Cache Grid consists of a collection of Oracle In-Memory Database Caches (IMDB Cache) that collectively manage an application's cached data.

Uploaded by

samydog
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

ORACLE DATA SHEET

ORACLE IN-MEMORY DATABASE CACHE


FEATURES AND BENEFITS

Oracle In-Memory Database Cache is an Oracle Database product option


 In-memory Database Cache
Grid ideal for caching a performance-critical subset of an Oracle database in the
 Preloaded and on-demand
application tier for improved response time. Applications perform read/write
SQL read/write caching
 Cache data location operations on the cache tables using SQL, PL/SQL, and Pro*C with
transparency
 Transactional consistency
automatic persistence, transactional consistency, and data synchronization
across cache grid nodes with the Oracle database. Oracle In-Memory Database Cache is built using
 Online addition/removal of
cache nodes the Oracle TimesTen In-Memory Database product.
 Automatic data
synchronization with Oracle
Database In-Memory Database Cache Grid
 Transactional replication with In-memory Database Cache Grid provides horizontal scalability in performance and capacity.
automated failover
A Cache Grid consists of a collection of Oracle In-Memory Database Caches (IMDB
Cache) that collectively manage an application’s cached data. Cached data is distributed
between the grid members and is available to the application with location transparency and
transactional consistency across all grid members. Online addition and removal of cache grid
members are performed without service interruption to the application.

Figure 1. Oracle In-Memory Database Cache Grid

Flexible Caching Options


Applications using IMDB Cache may choose to configure a combination of caching options:

- Read-only caches where updates are performed in the Oracle Database and refreshed to
the cache

- Updatable caches where transactions are performed in the cache and then propagated to
the Oracle Database

- Cache data may be loaded on-demand or preloaded, and may be shared across the cache
grid members or reside in specific cache node

Depending upon data access patterns and performance requirements, an application may
choose to allocate specific data partitions to some grid members for locality optimizations, or
it may choose to make all data available to all grid members for location transparency. The
cache grid software manages cache coherency and transactional consistency across the grid
members.

1
ORACLE DATA SHEET

Data Synchronization with Oracle Database


Data synchronization with the Oracle Database is performed automatically. Updates to the in-
memory cache tables are asynchronously or synchronously written through to the Oracle
Database, depending upon the desired trade off between performance and consistency.
Synchronous write-through will ensure that, if the Oracle Database cannot accept the
update(s), the transaction is rolled back from the cache database. Whereas asynchronous
write-through leverages the speed of Oracle TimesTen by first committing the transactions
locally, and then using asynchronous write-through to send the updates to the Oracle
Database. Asynchronous write-through cache groups provide better application response time
and transaction throughput.

For read-only cached groups, incremental updates in the Oracle Database are asynchronously
refreshed to the in-memory cache tables in the application-tier, at user-specified intervals.

Multi-User Concurrency, Persistence and Durability


IMDB Cache is built using Oracle TimesTen In-Memory Database (TimesTen) and is
deployed in the application tier for multi-user and multi-threaded applications. Applications
access the cache tables using standard SQL via JDBC, ODBC, Oracle Call Interface (OCI),
Pro*C/C++, and Oracle PL/SQL programming interfaces. Cache tables are operated like
regular relational tables inside the TimesTen database and are persistent and recoverable.
Durability is achieved through a combination of transaction logging and database
checkpointing to disk by TimesTen.

High Performance
By managing data in memory, and optimizing data structures and access algorithms
accordingly, database operations execute with maximum efficiency, achieving dramatic gains
in application performance. With IMDB Cache, a transaction that reads a database record can
take less than 5 microseconds (a microsecond is one millionth of a second), and transactions
that update or insert a record can take less than 15 microseconds (measured with Oracle
Enterprise Linux on AMD Opteron 1.8Ghz processor). Consequently, throughput is measured
in tens to hundreds of thousands of transactions per second, using commodity hardware.

Figure 2. Oracle TimesTen In-Memory Database Average Response Times

The majority of data in corporate databases is historical and infrequently accessed. However,
there are pockets of information that should be instantly accessible when requested. Your best
customers, open orders, account balance, recent transactions and product catalog are
examples. Oracle In-Memory Database Cache (IMDB Cache) enables such information to be
cached for real-time access, resulting in fast and consistent response time with very high
transaction throughput.

2
ORACLE DATA SHEET

IN-MEMORY DATABASE High Availability


CACHE
Availability is an essential requirement for most real-time applications. High availability for
REAL-TIME DATA in-memory cache tables is provided through real-time transactional replication.
MANAGEMENT FOR
- Asynchronous replication provides maximum performance. The application is
PERFORMANCE-CRITICAL
completely decoupled from the receipt process of the replicated elements on the
APPLICATIONS:
subscriber.
 Capital markets

 Customer support centers - Synchronous replication provides higher level of confidence for data consistency
 Defense and intelligence
between the active and standby databases; the application is blocked until the transaction
 Fraud Detection
has been both received and committed on the standby database.
 Health care

 Operational data stores - The standby database is always available for reads; additional read capacity can be
 Real-time billing provided by configuring additional read-only subscribers.
 Telecom and networking

 Travel and reservations - Failure detection and failover to the standby database is achieved by seamless integration
with Oracle Clusterware.

- Online upgrade allows individual server to be taken offline for software upgrades, while
other servers continue uninterrupted.

- Integration with Oracle Real Application Clusters and Oracle Data Guard provide cross-
RELATED PRODUCTS tier high availability in the application tier and the backend database tier.
AND SERVICES:
 Oracle TimesTen In- Resilience to Failures and Automatic Resynchronization
Memory Database
IMDB Cache is designed to continue running even after the Oracle Database server or
 Oracle Database

 Oracle Real Application network connection has been lost. Committed transactions to the in-memory cache tables are
Clusters tracked and, once the connection is restored, propagated to the Oracle Database. Similarly,
 Oracle Data Guard
committed transactions to the cached tables in the Oracle Database are tracked and refreshed
 Oracle Clusterware
to the in-memory cache tables, once the connection to the Oracle Database is restored.
 Oracle SQL Developer

Wide Range of Applications


Because IMDB Cache supports read/write SQL transactions for the cache tables, it can be
used for a wide range of applications where response time and throughput requirements are
business critical. For example, capturing and processing data at network speeds, online
commerce, securities trading systems, real-time billing and data analysis, fraud detection,
managing user/subscriber profiles, travels reservations, and other transactional systems.

Contact Us
For more information about Oracle In-Memory Database Cache, please visit
http://oracle.com/technology/products/timesten/imdb_cache or call +1.800.ORACLE1 to
speak to an Oracle representative.

Copyright © 2009, Oracle and/or its affiliates. All rights reserved.

This document is provided for information purposes only and the contents hereof are subject to change without notice. This document is not
warranted to be error-free, nor subject to any other warranties or conditions, whether expressed orally or implied in law, including implied
warranties and conditions of merchantability or fitness for a particular purpose. We specifically disclaim any liability with respect to this
document and no contractual obligations are formed either directly or indirectly by this document. This document may not be repro duced or
transmitted in any form or by any means, electronic or mechanical, for any purpose, without our prior written permission.

Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.
0109

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy