Kbase P26508: How to manage schema changes while using PeerDirect replicat
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
04/06/2003 |
|
Status: Unverified
GOAL:
How to manage schema changes while using PeerDirect replication ?
FIX:
These are the steps needed to manage the changes in the schema while running PeerDirect replication.
- Disable access to databases to all users
- Do a Final replication on all databases
- Make schema changes on the schema only database
- Create a new rule file using PD Designer
Use script or just open schema DB if it has current rules to import
current rule set.
- Duninst all databases in the network:
Example :
duninst PDZIJ05001
- Apply the schema changes to all databases
- Import the new rule file to all the sites
Example :
dimprule /da=progress /db=<hostname>:<port-number>:<dbname>
/odbcp="" /logwide /v <rulesfle.rul>
- Mark all database as synchronized:
adhoc <DSN> pduser "" "UPDATE dCnf SET CnfValue = 'synched'
WHERE CnfName = 'PDC_PREPPED_IMAGE'"
- Activate First site database:
dinst /da=progress /db=<hostname>:<portnum>:<dbname> /odbcp="" /logwide /v
/first /disablepreprocessing /pnl=<license_file.pnl>
- Activate Second site:
dinst /da=progress /db=<hostname>:<portnum>:<dbname> /odbcp="" /logwide /v /sitetype=complete /sub=y /pa=<hostname_of_firstsite>
- Enable access to databases to all users