For the example in this section, the company’s software development takes place in Boston and in a new development office in San Francisco. Work is about to begin on a new release.
Relevant characteristics of the two sites:
Location
|
Synchronization server
|
Replica name (site name)
|
---|---|---|
Boston
|
minuteman
|
boston_hub
|
San Francisco
|
goldengate
|
sanfran_hub
|
Before you create a new replica, you must perform these steps at the original site:
After you enter the activate command for a database set, users at the original database cannot access it without a MultiSite license (in addition to a ClearQuest license).
The mkreplica –export command locks the database after you start to export the replica. All users must log off before the procedure begins and log on after it is finished. Data is lost if sessions are left open during the replication process.
Replica-creation packets can be four times as large as the respective databases. Verify that the working directory you use has enough free space. You must have write permission for the directory, and the directory you specify must not exist.
The following command activates the database set in Boston. It names the clan telecomm and the site boston_hub, and it specifies minuteman as the synchronization server.
In Boston, perform the following steps.
The following command creates the sanfran_hub replica of the PRODA user database in the telecomm clan. It also creates the sanfran_hub replica of the schema repository in the telecomm clan. The synchronization server for the new site is goldengate. The administrator uses the –fship option to send the packet immediately using the Rational Shipping Server.
multiutil mkreplica –export –clan telecomm –site boston_hub –family PRODA –user susan –password passwd –maxsize 50m –fship –workdir c:\temp\packets –sclass cq_default goldengate:sanfran_hub
This backup records the fact that the database is replicated. If you try to restore a database from a backup copy that was made before the database was replicated, the replica restoration procedure fails. (Although the restorereplica command may succeed, you cannot import update packets from other replicas because the original database is marked as unreplicated.)
These steps take place in San Francisco, which has no replicas in the clan.
multiutil lspacket –short Multiutil:Packet ’d:\temp\ms_ship\incoming\mk_sanfran_hub_21-May-01_19-28-01.xml’...
In the mkreplica –import command, you must specify the pathname of the incoming packet as listed by the lspacket command. For example:
multiutil mkreplica –import –site sanfran_hub –repository ORC1 –vendor ORACLE –dbologin orcadmin password –connectopts host=sanfran_dbserver;SID=ORC1;server_ver:8.1;client_ver=8.0;log_type=long –database ORC1 –vendor ORACLE ORC1 –dbologin orcuser password –connectopts host=sanfran_dbserver;SID=ORC1;server_ver:8.1;client_ver=8.0;log_type=long –comments “Importing the initial replicas of the PRODA database and its schema repository for the San Francisco site in the telecommunication clan” d:\temp\ms_ship\incoming\mk_sanfran_hub_21-May-01_19-28-01.xml
Users in San Francisco can access the new replica in the same way they access an unreplicated database.