P. 1
SAP Business Objects Data services Designer Guide

SAP Business Objects Data services Designer Guide

|Views: 38,300|Likes:
Published by anuragsharma83

More info:

Published by: anuragsharma83 on Mar 25, 2010
Copyright:Attribution Non-commercial

Availability:

Read on Scribd mobile: iPhone, iPad and Android.
download as PDF, TXT or read online from Scribd
See more
See less

09/16/2015

pdf

text

original

With Oracle 9i or higher, SAP BusinessObjects Data Services manages the
CDC environment by accessing Oracle's Publish and Subscribe packages.
Oracle publishes changed data from the original table to its CDC table.

The Designer allows you to create or import CDC tables and create
subscriptions to access the data in the CDC table. Separate subscriptions
allow each user to keep track of the last changed row that he or she
accessed.

You can also enable check-points for subscriptions so that the software only
reads the latest changes in the CDC table.

Oracle uses the following terms for Change Data Capture:

SAP BusinessObjects Data Services Designer Guide 783

22

Techniques for Capturing Changed Data

Using CDC with Oracle sources

Description

Term

A relational table that contains changed data that results from DML
operations performed on a source table.

Change (CDC) table

AgroupofCDCtablesthataretransactionallyconsistent.Forexample,
SalesOrderandSalesItemtablesshouldbeinachangesettoensure
that changes to an order and its line items are captured together.

Change set

The database that contains one or more change sets.

Change source

The person who captures and publishes the changed data. The pub-
lisher is usually a database administrator (DBA) who creates and
maintains the schema objects that make up the source database and
staging database.

Publisher

Specifies when and how to capture the changed data. For details,
see the following table of publishing modes.

Publishing mode

The production database that contains the data that you extracted for
your initial load. The source database contains the source tables.

Source database

The database where the changed data is published. Depending on
the publishing mode, the staging database can be the same as, or
different from, the source database.

Staging database

A user that can access the published data in the CDC tables.

Subscriber

Controls access to the change data from one or more source tables
within a single change set. A subscription contains one or more sub-
scriber views.

Subscription

Thechangeddatathatthepublisherhasgrantedthesubscriberaccess
to use.

Subscriber view

Oracle supports the following publishing modes:

Asynchronous AutoLog

• Data is captured using redo logs managed by log transport
services that automate transfer from source database to staging
database.

784 SAP BusinessObjects Data Services Designer Guide

Techniques for Capturing Changed Data

22 Using CDC with Oracle sources

• Availability of captured data depends on the frequency of redo
log switches on the source database.
• A change set contains multiple CDC tables and can be remote
or local to the source database.

Considerations:

• Improves performance because data is captured offline.
• Available in Oracle 10G only.

Asynchronous HotLog

• Data is captured using redo or archive logs from the source
database.
• Captured data is available in near real-time.
• AchangesetcontainsmultipleCDCtablesandmustresidelocally
in the source database.

Considerations:

• Improves performance because data is captured offline.
• Available in Oracle 10G only.

Synchronous

• Data is captured using internal triggers on the source tables to
store changes in CDC tables.
• Captured data is available in real-time.
• CDC tables must reside in the source database.

Considerations:

• Adds overhead to source database at capture time.
• Available in Oracle 9i and 10G.

Oracle CDC in synchronous mode

The following diagram shows how the changed data flows from Oracle CDC
tables to SAP BusinessObjects Data Services in synchronous mode.

SAP BusinessObjects Data Services Designer Guide 785

22

Techniques for Capturing Changed Data

Using CDC with Oracle sources

When a transaction changes a source table, internal triggers capture the
changed data and store it in the corresponding CDC table.

Oracle CDC in asynchronous HotLog mode

The following diagram shows how the changed data flows from Oracle CDC
tablestoSAPBusinessObjectsDataServicesinasynchronousHotLogmode.

786 SAP BusinessObjects Data Services Designer Guide

Techniques for Capturing Changed Data

22 Using CDC with Oracle sources

When a transaction changes a source table, the Logwriter records the
changes in the Online Log Redo files. Oracle Streams processes
automatically populate the CDC tables when transactions are committed.

Oracle CDC in asynchronous AutoLog mode

The following diagram shows how the changed data flows from Oracle CDC
tables to SAP BusinessObjects Data Services in asynchronous AutoLog
mode.

SAP BusinessObjects Data Services Designer Guide 787

22

Techniques for Capturing Changed Data

Using CDC with Oracle sources

When the log switches on the source database, Oracle archives the redo
log file and copies the Online Log Redo files to the staging database. Oracle
Streams processes populate the CDC tables from the copied log files.

Note:

The Oracle archive process requires uninterrupted connectivity through
Oracle Net to send the redo log files to the remote file server (RFS).

You're Reading a Free Preview

Download
scribd
/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->