Pervasive

 Hi,

 I am looking at trying out Data Exchange to synchronise data between two servers.

Not backup, but two way synchronisation.

One thing I do not understand and cannot find the answer to in the documentation is....

I am using the transactional side of the engine. Hence, no DDF files. Just a whole bunch of data (.DAT) files in

various folders.

Reading the docs for installation and setup it talks about providing a  Database Name. I can understand that when using the Relational side of the engine. I have examples of that and accessing via the PCC.

However, for transactional files (Btrieve) there is no Database Name.

Can anyone enlighten me how I point Data Exchange just to the data files/folders rather than a DBNAME with DDFs please.

Kind Regards,

Mark Bailey

You should probably be using the DataExchange Deployment wizard.  This tool accepts a bunch of input and generates the deployment for you.  On the screen where it asks for the DSN for your replication database, this DSN will be created -- so it should NOT exist already -- and it will then ask you for the database files that are to be included.

In short, just go through the normal deployment -- you do not need to have a DBName already created (or even DDF's) to deploy a DX replication network.

 Thanx Bill,

Yes, I now understand that.

 Only problem now it seems is that I have purchased the wrong version from the Pervasive online store.

The Trial provides a dialog which asks if either 1 way or 2 way.

What I purchased...there was no other product....does not ask that question upon installation and clearly does
not have the ability to perform 2 way.

Pity that was not a bit clearer that there are two versions and that the 2 way version cannot be purchased from the site.

I will have to try and sort out with Pervasive.

Thanx again for your help.

Cheers,

Mark Bailey

Contact db_cic@pervasive.com to help you sort this out.  Thanks.

Jose

As stated above, you'll need to contact Pervasive on this one.   You need DataExchange Synchronization Edition in order to do two-way replication.  The current price list shows that they should be able to swap this out at no charge.  However, with Sync Edition, you need to have TWO licenses of DX -- one for each server, and both tied to the number of database engine user licenses on each server.

 Hi Bill,

 Just as a follow up.

Now have the correct licensing I think (hope). They only sent me one key for product DX-951252-1-02. Have used on both servers and neither seem to complain.

Uninstalled previous versions and installed new versions as 2-way on the First Site and the Partner Site.

Used the Deployment Tool as you suggested to build the file set. No problems.

Connected to it from the Partner Site with no problem.

All the folders and files from the First Site were quickly replicated to the Partner Site as expected.

Only two issues.....

Not every file completely replicated. I have one large file (93mb) that refuses to replicate properly. Only has 12 records in it at the Partner Site.

Also, now when I make any changes to the data via the application at either the First Site or the Partner Site, the changes are not propagated to the other site.

 Are you able to offer any suggestions please.

Kind Regards,

Mark Bailey

If you have converted to the DX Sync Version (required for two-way replication), then you really should have a separate license for EACH server you are installing to, licensed for the maximum PSQL user count on each specific server.  (Thus, if the secondary server is a 6U license, you only need a 6U DX.)

As for troubleshooting the replication environment, you need to be aware that this is a VERY complicated animal, made even more so through the use of two-way replication.  Of course, 93MB is still a tiny file, in Pervasive terms.  I know of sites successfully using DX with GB+ files.  You probably need to start digging through the log files (DRE.LOG, MER.LOG) to see if change capture is enabled on all files, or if problems have been surfacing.  Alternatively, you can try a "Full Push" replication manually, and see if that sends the other data.  

If this is your first deployment, I might suggest deactivating everything, and re-deploying with only 4-5 tables, then digging into the data and see exactly how it is all working.  Spending some time with the product manuals is a REAL good idea.  However, two-way replication can still cause problems -- even our own DX training course never delved into the abyss of two-way sync -- way too many options, and too many things that could go wrong.

  Even though it is 93MB at the first side, how many records?  Is there anything special about the file?  And as Bill says, "anything logged about the file"?