Oracle Tips by
opinion, the largest benefit of running EnterpriseDB is the ability to
offload less critical tasks from expensive Oracle databases to cheaper
EnterpriseDB databases. For example, you can offload workgroup
reporting and analytics from your warehouse and push it out to smaller
workgroup servers running EnterpriseDB.
use is to replicate your OLTP databases to OLTP audit, reporting and
historical databases running EnterpriseDB. These EnterpriseDB
databases might be large multi-CPU databases running on slower, cheap
arrays of disks where speed of access is not as important as
maintaining data availability for infrequent access (I'm thinking
EnterpriseDB provides the answer to these needs with the EnterpriseDB
Replication Server. The EnterpriseDB Replication Server provides
a replication console to configure and monitor replication from Oracle
EnterpriseDB Replication Server provides a repository-based solution
that allows you to maintain the configuration of all of your
replication jobs in a single location. You can configure
multiple destinations for a single source and you can create multiple
replication jobs from a single database.
future, the replication server will support bi-directional replication
and replication between different types of databases (Oracle,
EnterpriseDB, PostgreSQL, etc). For now (Build 27), the
replication server only supports Oracle to EnterpriseDB replication.
verify your version of the EnterpriseDB Replication Server by
selecting the About option under the help menu.
7.1: EnterpriseDB Replication Server
Replication via the EnterpriseDB Replication Server is accomplished in
a publish/subscribe model. The EnterpriseDB Replication provides
an additional level of abstraction by inserting a replication
repository between the sources and destinations.
example, you can configure the replication server on a host different
from both the source and target databases. The replication
server can run on one host, the source on another and the target on
yet another. The replication server is a one-stop replication
hub. In a production environment, you will likely want to run
the DBA Management Server for all of your instances and the
replication server on an instance together, separate from your
Most activity in the Replication Console is performed via a
right-click, smart menu.
install the replication server when you install EnterpriseDB Network
and is available to premium subscribers at an additional charge.
It is ready to run out of the box. You can start the
EnterpriseDB Replication Console (Figure 7.2) from the EnterpriseDB
menu. You will begin with an empty console ready for
7.2: EnterpriseDB Replication Studio
replication console is a Java application that will connect to your
databases via JDBC. You will be connecting to three databases.
Database 1 is the repository database (usually the local database),
database 2 is the publisher (in this case Oracle) and database 3 is
the target database (possibly the same as database 1 but not
recommended in a production environment).
examples in the book, I will be using a local version of EnterpriseDB
as both database 1 and database 3. I will be connecting to an
Oracle 9iR2 database as database 2. I didn't choose 9iR2 for any
particular reason. The example below would work just as well on
a 10g instance and, while I didn't personally test it, probably on an
8i instance also.
be using the HR sample schema that comes with Oracle. I will
replicate some of the tables in the HR schema but not all.
this working example, I will first verify my schemas (Figure 7.3).
I have no HR schema in my EDB instance and I do have an HR instance in
my Ora92 instance. If you do have an HR schema already, right
click on the schema and choose Drop Cascade to remove it.
7.3: Developer Studio Display
is an excerpt from the book "EnterpriseDB:
The Definitive Reference" by Rampant TechPress.