There is an easy solution -- use the DXDYNPATH tool to specify the new
table to the database, then go and open it and make a simple change.
The next replication cycle will create the table at the secondary site,
and the replication window following will push the data across.
Once the file is part of your replication list, you can remove it from
DXDYNPATH.
Goldstar Software Inc.
Pervasive-based Products, Training & Services
Bill Bach
BillBach@[EMAIL PROTECTED]
Chicago: Pervasive Service & Sup****t Class - 11/13/2007 ***
Karl A. Sxrensen wrote:
> We are in the process of deploying DataExchange 2.8 at a customer
> site, but I can't figure out a simple routine to add a table to a
> replicated database. This is a one way backup (first site --> partner
> site), where the database at the partner should function as a backup,
> in case of hardware failures and so on.
>
> How to modify a table:
> 1. Stop replication service at the partner site.
> 2. Upgrade the database at first and partner site.
> 3. Start replication service at the partner site.
> This works.
>
> I then try to add a new table to the database like this:
> 1. Stop replication service at the partner site.
> 2. Add new table, both at first, and partner site.
> 3. Start replication service at the partner site.
>
> This does not work. When I add records to the new table at the first
> site, they don't appear in the database at the partner site. I'm
> quite sure that the reason for this, is that the replication engine
> don't know about this new table. My problem is that I don't know how
> to make the replication engine aware of this new table to replicate.
>
> This database is quite large. It contains > 700 tables, and is around
> 100GB, so running the DX Deployment tool again (for the whole
> database) is not an option. There has to be an easy way of adding
> this new table to the replication engine.
>
> TIA
> Karl
--
|
