Activation is the process of creating a new database for replication, or enabling an existing one, and establishing the database as belonging to a site within a replication network so that it can replicate.
Note Because activation associates a database with a site, activating a database and activating a site mean the same thing.
When you activate a database, Pervasive DataExchange creates a system data source name (DSN) to point to the activated copy. The DSNs with the prefix xPD are created by the design process. The activation process creates DSNs with names like PDxxxxxxxx.
Another system database is the Database Network Analysis (DNA), which is the replication database called PDDNA. It is created during DataExchange installation. The database appears in Pervasive PSQL Explorer with the DNA icon in its Replication node.
Specific information about using each of the DataExchange deployment utilities mentioned in this chapter is available in Chapter 7, Using the DataExchange Utilities and Services. The following table provides specific reference information.
The /FI option specifies you are activating the First Site, but you should always run dxact.exe from the site you want to activate—remote activations are not available in DataExchange. For the complete list of dxact.exe options available, see dxact.
Deactivation is the disabling of an activated database in a replication network. Deactivation uses the dxdeact utility as explained in Chapter 7, Using the DataExchange Utilities and Services.
This example deactivates the demodata database using the dxdeact utility. By default, messages from dxdeact are written to the dxdeact.log file, not to the screen. To view the messages on the screen while dxdeact runs, use the /LOGFILE= option just as you did earlier with dxact.exe. It’s helpful to note that all the DataExchange Utilities provide the /LOGFILE= option to control logging output. For the complete list of dxdeact.exe options available, see dxdeact.
Reactivation is the reenabling of a deactivated site for replication. A database must be deactivated before it can be reactivated. Reactivation is, in essence, the same as activation in that you use the dxact utility in the same manner as you did when you activated.
Tip For a detailed discussion about the types of expressions you can use as include and exclude patterns with dxdynpath, see Types of Expressions.
If you’re unfamiliar with expressions or have had little exposure to working with them, we strongly recommend you first review Types of Expressions to gain a basic understanding of how to work with the different types of expressions.
In our example database, demodata, we’ll be automatically generating a set of tables every day that contain the attendance records for each campus. This is important data that must be included in the replication. We’ll add an include pattern using dxdynpath so these tables get replicated as well. The tablename uses a naming convention of attend<campusid>.mkd, where <campusid> is the three letter campus code.
These are simple examples to illustrate how dxdynpath uses pattern matching to determine what files are replicated. For a detailed discussion on using dxdynpath and the different types of expressions you can use, see dxdynpath.
Tip For information on using the BUTIL utility to clone tables, see the Advanced Operations Guide in the Pervasive PSQL user documentation.
DXACT /FI <Database_DSN>
For example, if you wanted to active the DEMODATA sample database, the command is DXACT /FI DEMODATA.
DXSYNCTABLES <TableName> <DSN>
|
2
|
Activate each Partner Site using dxact.exe and the
/PA[RTNERADDRESS]=<string> option, to designate the site with which you will replicate. |
DXACT /pa=SiteA <Database_DSN>
This folder is located at <Installation Directory >\Replication\LogFiles.