TRANSACTIONAL DATA

MANAGEMENT

TDM provides guaranteed capture ,routing, transformation, delivery and verification

of data transactions across heterogeneous environments in real time.
The key requirements of TDM are that it must:

 Enable real time sharing of transactional data.

 Support heterogeneous data environments

 Be designed to ensure the integrity of the data.

Transactional Database has the functionality or an important role required
to maintain consistency and integrity in the database.

Any database transaction (read from database or write into the database) must be Atomic,
Consistent and have Integrity, Durability popularly called in short as the ACID property of the
database design.

1) A database management system should be able to recover from any kind of failure during a
transaction automatically like power failures or other interruptions.

2) A database should provide isolation between transactions happening concurrently.

Purpose of Transactional Database:

Transactional Database performs a roll back DBMS operation whenever a WRITE function is
not completed for success. It is very important to maintain integrity and consistency in the
database design, transactional database achieves the integrity and consistency.

Imagine, you are making shopping a toy for 10 dollars. You provide your credit card to the
merchant. They swipe the card and your credit card get charged for the amount, but there is an
issue or power failure in the server where the 10 dollar is not getting credited to the merchant
account. The merchant will not be able to complete the transaction neither he is going to give
you shopped due to this unsuccessful transaction which is only half way through. You are not
going to get your money back neither you are going to get the toy which you tried to purchase. It
is going to be a loss for one or other party involved in such transactions transaction.

Transactional database provides functionality called ‘Roll back’ to overcome such losses. When
a transaction did not complete the roll back statement rolls the database to the state before
beginning of the transaction which failed. This helps to avoid any kind of loss and lets you start
the transaction again a fresh.

Transaction Database performs

1) A BEGIN statement to indicate the beginning of the transaction.
2) A set of SQL statements to indicate the required transaction to be performed over the
database.
3) If the SQL statements fail, the transactional database rolls back the database to beginning state
else if the SQL statements are successful, A commit statement would be issued in order to
confirm and complete the transaction.

DATA REPLICATION:

Database replication is the creation and maintenance of multiple copies of the same database. In
most implementations of database replication, one database server maintains the master copy of
the database and additional database servers maintain slave copies of the database. Database
writes are sent to the master database server and are then replicated by the slave database servers.
Database reads are divided among all of the database servers, which results in a large
performance advantage due to load sharing. In addition, database replication can also improve
availability because the slave database servers can be configured to take over the master role if
the master database server becomes unavailable.

Integration Overview:

Companies need a platform that allows disparate applications and databases

to benefit from real-time access to real-time information—without
compromising availability and performance. Golden Gate’s TDM platform
enables high volumes of transactional data to be moved continuously
between enterprise systems with subsecond speed, preserved data integrity,
and minimum impact.

Golden Gate TDM’s major benefits include

 Real-time data
 Continuous availability
 Heterogeneous support
 High performance with low impact
 Flexible solutions
 Transaction integrity

Transaction integrity: The degree to which a transaction flowing through a

network reaches its intended destination without impairment of its function,
content or meaning.

Integration Details

Golden Gate TDM captures Oracle’s Siebel data and applies that data to
target systems with subsecond latency. Because Golden Gate TDM operates
at the database layer, there is no need for integration or customization to
implement it with Oracle’s Siebel Customer Relationship Management (CRM)
7.7. Golden Gate TDM lives nonintrusively on the source database and
captures new and changed data from the transaction (redo) logs. On the
target, Golden Gate can Golden Gate solutions for Siebel 7.7 include

Live Reporting:
Golden Gate TDM can offload reporting activity from Siebel production
systems to a separate reporting instance (or instances) by capturing and
delivering real-time Siebel data.

Zero-Downtime Migrations:
For cross-platform or database migrations, Golden Gate TDM can nearly
eliminate “planned” downtime by synchronizing data between the old and
new environments. Both environments can run in parallel for as long as
needed, so that failback to the old system can occur at any time without
transactional data loss.

Real-Time Data Warehousing:

Golden Gate TDM provides continuous, real-time capture and delivery of
changed data from online transaction processing (OLTP) systems to the data
warehouse—with very low impact and without the need for batch windows.