Home

IBP Replicator 4.1

1. 97 Management Tools sms 98 Replication Monitor lt u u 99 Replication Scheduler 101 2013 IBPhoenix Editors 4 IBP Replicator 4 1 Notify 1 147 RC 105 Conflict Resolution u u u 106 License Manager 108 Schema View 111 Reporting Errors 113 Chapter 9 Advanced Topics 116 Schema Numbering ET CE ueq sasay qas CO PO PERS DE EL E g 116 Metadata Changes PEER EEE PELLE UD EN ES LUTTE PTT TE a CEST ELLE PRE LE SERRE DEEE D CET asagi aaa aka Zk e p a Z Ea 119 Adding Timefields 119 Advanced Mapping Techniques 121 Complex SCHEMAS RITTER 123 Off line Replication and Synchronization eene eene eene u 127 Configuring the Offline Schema uuu uuu uuu 129 Running an Offline Replication NER LEIES E PE EE AS A EL GE TE EEE NEVELE A AA EE A E A AER S ES
2. LOG_ID BANK CODE CURRENCY REF OMMENT TIMEFIELD Sp Source 1125 DPG ERU 0 NULL gt 7 10 2012 12 12 31 AM FEB Target 1125 DPG ERU 0 NULL gt 1 6 10 2012 11 48 40 PM Source database gt My Source Every conflict for this table is the same so we select a record and click the Show Data button at the right to find out the offending field A new panel opens beneath the Detail display and shows the conflict for this record Ah yes we previously used a synchronization to get all the records from the source table over to this table but the server clock at the target was 20 minutes fast Resolution If any conflicts are listed you can click on one to highlight it and select a button from the Options menu to resolve it 2013 IBPhoenix Editors 108 IBP Replicator 4 1 8 3 5 Force All IBP Replicator will try to replicate all the problem rows during its next Replications scheduled replication Force If you want to force replication on some but not all of the conflicting Selected records use the checkboxes at the left of the detail display to Replications select deselect Then the button will become enabled and you can use it to tell IBP Replicator to try to replicate those rows during its next scheduled replication Force IBP Replicator will try to replicate the problem row during its next Replication schedul
3. 50 IBP Replicator 4 1 File Configuration View Database Replication Tools Help N Source Database 6 Defined Replication Schemata i Shift up Target Database B E My Initial Schema 8 95 Source database i a Target databases 2 8 My Second Schema 8 8 Source database mE Target databases Shift current object one position up Z Click on the Shift Up button to move the selected schema up the order or Shift Down to move it down amp Source Database Defined Replication Schemata Target Database 8 4 My Second Schema H E My Initial Schema 7 2 Choosing the Source Database The source database is the one in your replicant pair that will be replicated from You already defined at least your source database at an earlier step when registering databases Editing Database Attributes Suppose we decide that our descriptive names Source Database and Target Database are not to our liking We can use the the Edit option on each of their nodes in the left pane to change them 2013 IBPhoenix Editors Chapter 7 Defining a Replication Schema 51 Source Database Target Database Add Edi Remove a My Initial Schema S Source database 7 8j Source Database mE Target databases My Second Schema Test connection Disconnect We ll change Source Database to My Source File Configuration View Database Repli
4. Working with Sequences Generators ADD SEQUENCE Add a replicated sequence to a replication schema By default the same sequence name is added to the current schema and the current target database Syntax ADD SEQUENCE FROM sequence name lt sequence parameters gt Sequence parameters FROM source sequence name the name of the generator in the source database that you want added to the schema It is mandatory although the FROM keyword is optional For Oracle databases the sequence name can include the database schema in the format SCHEMA SEQUENCE Both parts of the sequence name are case sensitive TO target sequence name the name of the corresponding sequence in the target database This parameter can be omitted if the target sequence name matches that of the source sequence SCHEMA schema number or name Use this parameter if your command is directed at a schema other than the current one or if you are not sure TARGET target db number or name Use this parameter if the target database is not the current target database or if you are not sure NUMBER sequence number each sequence in a schema is assigned an integer ordinal number automatically If you want the sequences to fit in with a customised order instead use this parameter to pass a unique new number x You can modify the numbering later with MODIFY SEQUENCE 2013 IBPhoenix Editor
5. mee T DC 1 Fields with character set OCTETS are copied as is others must be in hexadecimal form gt Sourc afdal pp gt Janay pounce P De EE RR TON 2 For DATE and TIMESTAMP types string is expected in ANSI format not current NLS 3 For INTERVAL types string must fit current client NLS format 2013 IBPhoenix Editors Appendices 143 Table 4 Oracle Interbase Firebird Destination types w lt O r lt LL gt pere res px x x x x X X z o a a BLOB LOAT INTEGER NUMERIC BINARY_DOUBLE BINARY_FLOAT BLOB CEN IE mc EH ROUGES MUCE MOCE e e EXCUDENENCUE DRL DE i INTERVAL DAY TO BBESEH SECOND ES E TO MONTH B LOCAL TZ Uz SSBBBDUBEIBBBBDDE waa XIX X X x x x x x x x tx 4 If a destination field has character set OCTETS its content is copied as is otherwise it is converted into hexadecimal representation Source types gt gt EG jijiji in D iii 2013 IBPhoenix Editors 144 IBP Replicator 4 1 10 2 Appendix Il Command Line Editor cfged The command line application cfged cfged exe on Windows enables the Replicator savvy administrator to create and manage a replication configuration without
6. Remove Clone Create system objects Remove System Objects AutoGenerate View conflicts Monitor Synchronize Symmetric synchronize RA Replication Monitor Graphica Tasks Settings Help Erase Start Item My Target 1 l ACCOUNT UPDATE LOG I BANK ACCOUNT ll CORPORATION ti COUNTRY TRANSACTION Click Start to monitor 2013 IBPhoenix Editors Chapter 8 Managing Replication 101 Activating and Stopping the Monitor Click the Start button to begin monitoring the selected types While monitoring is going on the button caption changes to Stop Click this button again to stop the graphing process Keeping Things Rolling Along You can graph just one type of replication statistic or any combination of types While the monitoring and graphing is going on you can gt clear the display by clicking the Erase button select schemata in the tree at any time set or unset a flag to receive a message box when a conflict occurs Menu Settings Show message box on conflict Replication Monitor Graphical Displ Tasks Help Fe Show message box on conflict Erase Star Click the button to set the message box flag on Click it again to toggle the flag off 8 3 2 Replication Scheduler The Scheduler provides the ability to manage replication at custom periods by setting a predefined interval in minutes
7. generate successive definitions in your new schema The Replication Tree The replication tree the right pane of the Replications tab in Replication Manager provides the running details of everything you define in the currently selected configuration database As you progress through your definitions the tree will expand and enable you to access aspects of your schema at each level of detail Ways to Work on Definitions The interface provides several different ways you can approach definition and maintenance tasks at various levels gt using the right click context menus on the tree nodes gt double clicking the tree node gt making selections from the Replication menu You can mix the tricks in whatever way suits you best Following are some examples of the various approaches IBPReplicator File Configuration View Database Replication Tools Help si 2 S Source Database Target Database Global settings Monitor Type Firebird Descriptive name Source Database Displays replication schemata in the current configuration database Here the root node of the replication tree is selected and the user right clicks on it to display the context menu The New option is selected and a left click will provide the input dialog for defining a new schema 2013 IBPhoenix Editors 48 IBP Replicator 4 1 IBPReplicator Schema settings
8. new icon in the Tasks pane enabling you to add another target database to the schema As with other nodes you also have similar contextual options by selecting and right clicking the schema s node directly in the the tree In each approach you will be able to edit the name of the schema or delete it entirely File Configuration View Database Replication Tools Help At Fe O Hh 65 5 Source Database Defined Replication Schemata Target Database El My Initial Schema 9 52 Source database Edit Target databases Delete View conflicts Monitor Allows you to change the name given to a collection of replicated databases Be aware that deleting a schema will remove all replication information for that schema including anything stored in lower nodes Once the schema is gone the replication cannot occur Expanding the schema node reveals two new nodes labelled source database and target database These nodes can be approached in the succeeding steps Adding More Schemata and Ordering Them To add another schema simply select the Defined Replication Schemata node again and repeat what you did for the initial one Once you have more than one schema the Shift Up and Shift Down buttons are enabled in the toolbar when a schema node is selected They provide the means to alter the order in which your replications will take place in the cycle 2013 IBPhoenix Editors
9. IBP Replicator 4 1 2013 IBPhoenix Editors User Manual Build 4 1 12 29 01 2013 Replication for Firebird InterBase and Oracle databases ficator va q IBPhoenix Build 4 112 29 01 2013 2013 IBPhoenix Editors IBPhoenix Replicator is a toolset for implementing and controlling database replication in all Firebird versions Borland Embarcadero InterBase 5 x and higher and Oracle 9 and higher versions It is software that integrates with your databases allowing users to replicate data seamlessly and transparently between databases on both local and remote sites This manual provides an overview of IBP Replicator and how IBP Replicator and its tools can be used to meet your replication needs It provides a step by step breakdown on how to install configure and use the Replicator software Included are descriptions of the various replication models you can implement and how to use the Replication Manager tool to set up your replication schemas and to operate and schedule replications Version notes for this release can be found at the end of this document Chapter 1 describes the platform database engine system and licensing requirements Chapter 2 is an overview of the IBP Replicator toolset Chapter 3 describes the architecture and terminology of IBP Replicator and Chapter 4 goes on to explain how the replication actually works In Chapter 5 you will find a discussion of the planning you w
10. ze S Notify server m My Source Scheduler My Target 1 Schema view License Manager APP OT arent late base an Click the License Manager item to start the applet then click the Add button to add your first licence 2013 IBPhoenix Editors 110 IBP Replicator 4 1 License ID License Type EVAL Paste from Clipboard Evaluation license License ID REPL 001 License Key Ge DILi n794 336k gt SU G e0 gt RhXhNT EmYWhb82GBf5OQXAH i VOXlMlhgZeNQ6ha 95cNjM aX a5EkXQ n5D KLn4UWY EXDC E6 24f514cd3FX GL3jDFjXP84m8045VPK6 j fM8I Ej3T4XMAR aZhJQi y Lkhnk gt 1 nL KORnZ1PioLZG6D MiPg31 RjdE 8 c YJ fOmXoOa4B HF9 mFilhgm9PRHUMj1 cl Evaluation License Enter EVAL as the License ID and leave the License Key field to be filled automatically Normal Licensing Type in or copy paste the first of the License ID and License Key value pairs from your licensing document and press OK The first licence registration appears in the display with a success message License Manager License ID License Type EVAL REPL 001 Evaluation license Server license 2013 IBPhoenix Editors Chapter 8 Managing Replication 111 If you get an error message try again The codes are case sensitive Continue to add each of your licences in the same fashion until you have registered all of them They should
11. TRANSACTION TRA gt Filter The excluded items have not been unmapped they are simply invisible If you use Ctrl A or the conventional Shift click Ctrl click to select multiple items only the visible ones are selected Changing the Table Order Another trick for managing large lists is to use Tables order option in the View menu of the main screen s toolbar to switch the table ordering from User defined to By name By Name v User defined ee My Target 1 a The Tables order setting is persistent Later you may need revert to User defined if it is necessary to set a custom order for synchronizing table objects For more information about custom ordering for synchronization refer to the topic Customising the Order of Tables later in this chapter Mapping the Tables Now you can map the tables in the source database by selecting and dragging table objects from the Target objects panel to the Source objects and mappings panel 2013 IBPhoenix Editors 64 IBP Replicator 4 1 r x Replicated tables My Target 17 Wika mm Source objects and mappings Target objects amp ACCOUNT UPDATE LOG amp ACCOUNT UPDATE LOG amp BANK ACCOUNT amp BANK ACCOUNT CORPORATION amp CORPORATION COUNTRY COUNTRY CURRENCY F_TRANSACTION S amp F TRANSACTION S MEMBER S MEMBER S MGROUP S MGROUP PERIOD amp PERIOD S PERSON S PERSON
12. The format for supplying switches and their arguments is XxX parameter where x is a hyphen followed by a character representing the switch and parameter is the actual value for the argument Required Switches The replserver command must include these switches 2013 IBPhoenix Editors Chapier 8 Managing Replication 95 Switch and Argument a application u username Optional Switches Parameter Comment Run as application Use this switch when you want to run replserver as an application NOTE In application mode the logs are placed in the in working directory lt type gt interbase Case insensitive firebird oracle Should be the name of the Make sure this user exists in the user that is connecting to security database on the server the configuration where the configuration database database resides Not case sensitive The password of this user Passwords are case sensitive Because events are used to communicate with a running replication server it is essential to use the same configuration database parameter when performing each action regarding a specific instance of the replication server cfg is the connection string for the configuration database that is to be used for this process instance Remember that filesystem names on Linux are case sensitive These switches are optional 2013 IBPhoenix Editors 96
13. will appear similar to that used for creating a new configuration database R IBPReplicator View Help dE New configuration Open configuration 7 Close co nfiguratic n LISE x Drop configuration Exit Alt X My Replication Config Select Configuration Database Server type Interbase Y Connection string E User Name Password 658 Comment v Cancel If you need to remind yourself what to enter into these input fields refer back to the notes about filling these fields when creating your first configuration database The Tools Replication Monitor Replication Scheduler Schema View Notify Server View Conflicts License Manager 8 3 4 Replication Monitor The Replication monitor displays a graph of replication activity for the replication schema that is currently selected in its tree 2013 IBPhoenix Editors 100 IBP Replicator 4 1 By default from this version forward monitoring is disabled by default to reduce performance overhead Specified tables can be tagged and untagged for monitoring by setting the Keep Statistics flag in the Table Settings area of configuration If monitoring is enabled open the monitor by right clicking on the Target database you want to monitor and selecting the Monitor option from the context menu Tools Help 88dmmu naus ec AYv a f Source database Target databases B
14. My Target 1 DBNO 1 DBPath E Customers IBP databases source fdb DBName My Source Admin User sysdba Admin Role Priority 10 Charset NONE DBType 3 You can pick up a database icon and drag it to somewhere meaningful on your background image and then drop it where you want it Of course this would be so much more meaningful to most of us if the map were on a smaller scale So the tool allows you to use any image you like as your background perhaps a map of your region country plant server room whatever works for you To Use Your Own Picture as Background Create or copy the image bmp jpg etc into a convenient location and scale it to suit Click the Image button in the toolbar 2013 IBPhoenix Editors Chapier 8 Managing Replication 113 fi IBPReplicator Schema View Open picture This will open a file browser dialog enabling you to locate and select your image Other Layout Options To open a dialog where you can customise your display click the Options button fg IBPReplicator Schema View Remember to Save Your Settings If you wish to save your layout simply click on the Save button To restore the original default layout simply click the Reset button You can also restore the original layout from the Options dialog by checking Use Defaults there 8 3 7 Reporting Errors Whenever an error occurs during interactive activity configuration using Re
15. 2013 IBPhoenix Editors 24 IBP Replicator 4 1 Source Target SDatsbass I Heplicatar amp urce Ta P Ex qpuroe Terg t F Database p Database 9 Hub and Spoke d t oun uree Ta tJ Database Ma n 5 2 Database Design Issues Certain aspects of your database design and structure will be important as you prepare for replication particularly the unique or primary key constraints that will logically link source and target sets and the TIMESTAMP columns that you may wish to use for conflict resolution Unique Keys All tables must have unique column sets as keys As a rule the unique key used to map a source row to a target row should be the primary key although it can be any column set that resolves as unique IMPORTANT Firebird and Oracle allow null elements in uniquely constrained keys keys cannot be used for mapping source and target tables for replication Distributed Primary Keys Maintaining keys that are unique across database boundaries are always going to be the 2013 IBPhoenix Editors Chapter 5 Planning for Replication 25 major issue when you are setting out to merge records from different databases In scenarios where rows are being inserted in multiple databases using generated primary keys it will be necessary to implement some changes to avoid unresolvable key violation conflicts e In a Central
16. SCHEMA lt schema number or name gt Use this parameter if your command is directed at a schema other than the current one or if you are not sure COMMENT lt table comment Optional text comment use it for any notes you want to keep about this addition Enclose text in quotes or square brackets DISABLED ENABLED Signals whether this table is to be included in any batch synchronization Normally there is no need to set it explicitly at ADD time as it is enabled by default It can be modified as required using MODIFY TABLE TIME FIELD TS field name the name of the time field column that is used for timestamp based conflict resolution It must be the same in both the source and target tables or it won t work Only needed if this table pair uses a different time field name than the one set for the schema CONDITION row level replication condition use for applying a condition to the replication of this table pair For more information see the topic Row level Condition TARGET target db number or name Use this parameter if the target database is not the current target database or if you are not sure 2013 IBPhoenix Editors 164 IBP Replicator 4 1 SEPARATOR lt separator character code gt Use this if you need to change the character that will be used in the replication log table to separate the segments of multi segment keys in the text representation of records changed Neede
17. Working with Replicated Tables ADD TABLE Add a replicated table to a replication schema By default a table is added to the current schema and the current target database Most of the settings are effective only during the creation of system objects If you alter 2013 IBPhoenix Editors Appendices 163 them afterwards it will be necessary to remove and recreate the system objects Syntax ADD TABLE FROM lt source table name gt TO lt target table parameter gt lt other table parameters gt Table parameters For Oracle databases table or procedure names can include the database schema in the format SCHEMA TABLE Both parts of the table name are case sensitive The FROM parameter with the name of the source table as its argument comes first and is obligatory The keyword FROM is optional TO TABLE PROCEDURE VIEW lt target table parameter gt The table stored procedure or view that is to receive the replicated data Use of the respective keyword TABLE PROCEDURE or VIEW is optional This parameter can be omitted if it matches the source NUMBER lt table number gt each table in a schema is assigned an integer ordinal number automatically If you want the table to fit in with a customised order instead use this parameter to pass a unique new number Use SHOW TABLES n where n is the schema number to list the currently defined tables with their ordinal numbers
18. G PP TRANSAC ID PERSO Synchronizing G P KEY gt G P KEY gt BEN Synchronizing G TRANSACTION ID gt G TRANSACTION ID ID Finished select all When it is done you can check the contents of your outbound directory There should be one synch file for each table defined in the replication Synchronizing from an Off load For synchronizing from an off load just as with replicating from one you need a replication server licence and two replicant licences available on the server where the database to be synchronized is located Define a replication in the config file at the target replication server To use the off loaded files to synchronize a database set up a File type of database as the source pointing to the folder where the Replication Manager can find your off loaded files If you already have a schema set up for an offline up replication simply use the same schema It won t interfere with any waiting replication since the file extensions are different When you are ready just right click on it in the tree panel and choose Synchronize The monitor list will pop up and show you what it is doing The up synchronization will stop and roll back if dependency problems are encountered Make sure that the table order defined in the target is correct for the referential integrity dependencies in your database parent tables must precede their children Use the Up and Down buttons in the toolbar to r
19. IBP Replicator stores the primary keys in text format The separator character is used to separate the values in primary keys with multiple columns Thus it is essential that this be a character that cannot appear in a key value The default character is lt TAB gt ASCII 9 a non printable character sometimes represented by the musical minim symbol or Ctrl I In the unlikely event that ASCII 9 would conflict with values in your data s primary keys provide the code for one that is suitably improbable Comments The comment field is entirely for your own convenience Use it for any form of documentation that is useful to you Event Logging Use the default logging strategy or specify a specific logging strategy for this source target pair A newly configured source database is initialised to use the server defaults P IBPReplicator Schema settings Connection Settings Event logging 3 Information 3 Information REPLICATE LOG Default logging causes the run time replication log to be named replication log and to be written to default locations 2013 IBPhoenix Editors Chapter 7 Defining a Replication Schema 55 gt On Windows replicate log is written to c Programs and Settings All Users Application Data IBPReplicator if a custom location was not defined for it gt On Linux replicate log is written to var log if Replicator runs as a service otherwise it is written to
20. receive a row Refer to the previous topic Advanced Mapping Techniques for some guidelines for writing such procedures Example Row level Replication Condition To illustrate the row level replication condition we will use the following scenario as an example The head office is in London and there are two branch offices in Leeds and Manchester Sales data needs to be replicated from the branch offices to the head office and certain other specific data needs to be replicated from the head office to the branch offices The Leeds branch office is designated as DeptNo 10 whilst Manchester is Deptno 20 Manchester source gt All Data gt London target All Data Leeds source Manchester target DeptNo 20 lt London source gt DeptNo 10 Leeds target On the Leeds target database we need to define a row level replication condition for each table based on the DeptNo This is done via in the table settings in the Table mapping properties dialog DeptNo 10 Note the colon in front of the field name DeptNo 20 would be applied in the same way to the Manchester target database Example Hub and Spoke Replication In this scenario a central database controls the replication fetching and sending data from spoke databases to and from the hub 2013 IBPhoenix Editors Chapter 9 Advanced Topics 125 Manchester Leeds London Birmingham Thi
21. Connection Settings Event logging Replication enabled Schema name My Initial Schema Conflict resolution strategy Priority based C Time stamped Master slave Use default conflict resolution strategy Separator character Decimal ASCII code Comments First schema set up by the boss Needs checkingl After you click OK the new schema appears in the tree with nodes for the source and target databases File Configuration View Database Replication Tools Help AFIS B5 9 Hi li SSS Be Bag eelaAv Source Database Defined Replication Schemata Target Database E My Initial Schema Source database L Target databases EM As another approach you could have double clicked on the New schema icon in the task bar or you could have used the Replication Schema New in the Menu bar TIP Use schema names that will be meaningful not just to you but to anyone else who is going to manage your replications Note that you could have stayed within the schema definition dialog to develop the schema definition further as described below clicking OK once you were ready to save the work Tasks Pane Context Notice how the icons in the Tasks pane change according to where the focus in the tree pane is For example if you single click the newly created Schema node you will see a 2013 IBPhoenix Editors Chapter 7 Defining a Replication Schema 49
22. Customers BP filesin E Customers BP files c My Source Inbound folder Outbound folder Use metadata from Now you are ready to set up the file that you prepared as a pseudo database previously to be the target of this outbound replication Select the Target node and choose Add Setting Up the Outbound Target Choose the Offline target and complete the dialog 2013 IBPhoenix Editors 130 IBP Replicator 4 1 9 6 2 ee c IBPReplicator Target database settings Connection Settings Event logging Registered database ass B B MR eo be You may click the Test connection button to confirm that the database you named as the one from which to borrow definitions is online Set Up Tables Keys and Fields Proceed to set up keys and fields just as you would for the target of a database to database replication When you are done you are ready to create the system objects Create System Objects Again this step behaves just as you would expect if you were setting up a database to database schema Creating the system objects in the Source database defines the procedures and permissions needed to write records to the REPL LOG table and identifies the mappings that will be rendered to the destination file Running an Offline Replication An offline replication can be run in any of the normal ways according to your requirements under the replication service or appli
23. For example Debug level 5 can be useful when you need to troubleshoot a configuration Same as above writing to the log file You can log to window and log to file simultaneously if you wish Enables troubleshooting for cases where replserver has problems loading the configuration but the default location for the log file is unavailable for some reason Default when only one instance of replserver is running is var run IBPReplicator pid Use different names for multiple instances A process can be controlled using signals sent via the ki11 and ki11a11 commands 2013 IBPhoenix Editors Chapter 8 Managing Replication 97 Use ki11 to target a specific process by its process ID pid or kii1a11i to target all processes named replserver The available parameters are TERM TERM terminate 15 is the default signal It stops the current replication and shuts down the replication server kill TERM pid or killall TERM replserver HUP HUP hang up 01 allows you to pause the process and reload the configuration kill HUP pid or killall HUP replserver USRI USRI is a custom signal allowing you to request an immediate replication kill USRI pid or killall USR1 replserver Multiple Concurrent Replication Processes Multiple replication processes can run concurrently on the same host system provided each instance of the replication server uses a different configur
24. MODIFY SCHEDULE schedule item number SET schedule params g Use SHOW SCHEDULE to list all the current schedule items REMOVE SCHEDULE 2013 IBPhoenix Editors 168 IBP Replicator 4 1 Use to remove a replication schedule item Syntax REMOVE SCHEDULE lt schedule id gt SHOW SCHEDULE Displays the replication schedule No parameters Syntax SHOW SCHEDULE Customing Global Settings MODIFY GLOBAL Use to customise the global settings Syntax MODIFY GLOBAL SET lt global parameters gt Global parameters CRS lt strategy number DEFAULT gt Conflict resolution strategy to be used unless overridden at schema or database level If you provide the strategy number explicitly then possible strategies are gt 0 priority based gt 1 timestamp based gt 2 master slave default LOG lt log levels gt DEFAULT one of two possible LOG parameters available This one sets the logging levels and takes two integer arguments for logging to the window first argument and logging to the log file second argument Q Log levels are from no log to 5 for ordinary builds of the Replicator server If you are running a debug build the highest logging level is 7 LOG log file name allows the name of the log file to be customised By default it will be REPLICATE LOG and you do not have to specify that 2013 IBPhoenix Edito
25. MODIFY TARGET DATABASE lt db number or name gt OF SCHEMA schema number or name gt SET lt target DB parameters gt Target DB parameters If the parameter DATABASE lt db number or name gt is omitted the current database will be used If the OF SCHEMA parameter is omitted the current schema will be used The keyword OF is optional REMOVE TARGET Use to remove a target database from a replication schema Syntax REMOVE TARGET DATABASE lt db name or number gt FROM SCHEMA lt schema number or name gt SILENTLY 2013 IBPhoenix Editors 158 IBP Replicator 4 1 If the number or name properties of the TARGET or FROM SCHEMA parameters are omitted the current ones are used Be certain you are directing the changes to the right target Use of the keyword FROM is optional If SILENTLY is used there will be no warnings about any failures during the removal of the target SHOW TARGET Shows information about a target database Syntax SHOW TARGET DATABASE db number or name gt OF SCHEMA schema number or name gt Description If a database number or name is omitted then the current target database is used If the schema number or name is omitted then the current schema is used G When specifying the schema explicitly either of the keywords OF and SCHEMA may be omitted but it is recommended to use one or both SHOW
26. UserName REPL Row Level Replication Condition USER lt gt REPL MAN Birmingham UserName REPL Row Level Replication Condition USER lt gt REPL_BIR Leeds UserName REPL Row Level Replication Condition USER lt gt REPL_LEE 9 6 Off line Replication and Synchronization It is possible to perform what is termed off line replication where one party in the replication is a database and the other party is a file It enables you to do a form of asynchronous replication between two databases that are not in a connected client server transaction This feature will be useful where it is not possible to maintain a connection between the source server and the replicant database that is sufficiently fast or reliable At the source server you replicate outbound to a target file transport the file or a batch of files to the target server by your preferred means SFTP HTTP or some transportable medium such as DVD or flash card At the destination you have a file defined as the inbound source and the replication server will pull the replications into the target database On each server you will need replicant licences for both the source or target database and the outbound or inbound file respectively Setup Steps Configure Directory Locations for the Files On the servers create the appropriate directories to which your offline replications are to be written e g outbound and or from which files are to be read e g
27. amp TRANSAC GROUP amp TRANSAC GROUP amp TRANSAC TYPE amp TRANSAC TYPE Filter Cancel When the target object is dropped onto the source object the mapping is added and the object disappears from the list of target objects x Replicated tables My Target 7 eiue 5 objects and mappings Target objects ACCOUNT_UPDATE_LOG gt You can multi select more than one table view or procedure using shift click or ctrl click as required and drag them as whole gt Alternatively just double click on the target object to set the mapping s automatically between objects with identical names gt Dragging from the source database to the target allows you to break an already established mapping gt Double clicking on a mapped source table will also break its mapping ORACLE Only stand alone procedures can be replicated to not procedures packets The function must have a minimum of three input parameters and exactly one output parameter an integer whose OK result shall be 0 its conflict result 1 and error for any other value 2013 IBPhoenix Editors Chapter 7 Defining a Replication Schema 65 Example R EPL PROC Kl INTE GE R K2 VARCHAR2 D1 DATE D2 CLOB OLD K1 I OP CHAR R LD K2 VARCHAR2 ESULT O Mapping in Bulk UT INTE GE The mapping of sequences genera
28. edited or deleted as required Always remember to Reload Schedule if an existing schedule is in effect TIP If you need only occasional replications you need not schedule replications at all simply use the menu option Tools Notify Server Replicate Now to replicate whenever it suits you 8 3 3 Notify Server It is possible to intervene in the running Replication Server s activity and instruct it to perform certain actions You can do this intervention via the Notify Server utility from the main menu of the Replication Manager On Firebird and InterBase this utility uses events to alert the server It is essential to open ports in your firewall on both the server and the target database hosts for the event traffic On Oracle it uses Publish Subscribe notification in anonymous namespace The Notify Server Options Tools Notify Server offers three options Replication BIJE ha i ft Reload parameters Ctrl P mn e Replicate now Ctrl R Scheduler V Schema view EJ Shutdown Server trl U amp License Manager B Target databases E Rail My Target 1 E Replicated tables and procedures 7r 5 T 2013 IBPhoenix Editors 106 IBP Replicator 4 1 8 3 4 Reload Parameters Ctrl P Instructs the server to reload all its settings from the current configuration database usually because the configuration has been altered and there is no need to sh
29. or by frequency Once Only Periodically Hourly Daily Week days Weekly or Monthly Setting up a Schedule To set up a replication schedule select Tools Scheduler 2013 IBPhoenix Editors 102 IBP Replicator 4 1 Scheduler enabled Beep when Replicate Replication schedule Frequency Add or Delete Replication Schedules Adding a Schedule To add a schedule either gt drop down the Options menu and select Add or gt click the Add button on the toolbar or gt simply press the Ins ert key on your keyboard 2013 IBPhoenix Editors Chapter 8 Managing Replication 103 p Replication Schedule Schedule Frequency Schedule Frequency Once Y Once Periodicall Schedule Frequency Every hour Y Initially the add dialog shows the default schedule which is to replicate once at midnight on the current day which won t happen today of course In this example we are choosing an hourly replication which we can choose to be on the hour or at a selected number of minutes after the hour Of course you can drop down the options and pick the ones that you need Click OK to add the schedule You can add more schedules Any schedules you create are enabled by default meaning that they will all be scheduled For example you might want to include an hourly and a daily schedule and keep both
30. this could be done would depend on considerations such as the impact if records that had been locally inserted by the target changed their primary keys after replication whether a target s original key needed to persist for local usage and so on Timestamps for Replication Use If your chosen method of conflict resolution is going to be by Timefield it will be necessary to include a column in every replicated table both source and target to record the date and time of the changes Triggers should be included to ensure that every INSERT and UPDATE operation on those tables gets timestamped It is recommended that the timefield in each case be defined as TIMESTAMP However the source target pairs can be of any comparable data types IMPORTANT The identifier name of the Timefield columns is case sensitive in the replication schema All Timefield identifiers must be identical and must be entered into the schema without double quotes exactly as they are defined in the database DATE vs TIMESTAMP Timefield conflict resolution does not fail if either or both of the compared fields are of DATE type rather than TIMESTAMP However use of the date only type is not recommended because replication might not occur where the source and target rows 2013 IBPhoenix Editors 26 IBP Replicator 4 1 5 3 have the same date in the timefield The choice is not an issue if the databases are all Dialect 1 since a d
31. 33 About Licences D 25 10155572 41 Chapter 7 Defining a Replication Schema 45 Creating the Schema lt U u uu 46 Choosing the Source Database sms 50 Choosing the Target Database nn 55 Choosing Replicated Tables 60 Table Settings 70 One time Synchronization Q u uuu uuu 74 Creating Source System Objects TQ U u uu 78 Customising the Global Settings 80 Chapter 8 Managing Replication 85 Windows Operation 85 Command Line Operation 89 Linux Operation Q u u u u uuu u uu uu u 91 Installing and Configuring on Linux 92 Controlling replserver Processes 93 Loading Licences Manually
32. ACCOUNT UPDATE LOG failed Reason Failed Row exists with NEWER TimeStamp Delete selected records Insert ACCOUNT LIPDATE LOG failed Reason Failed Row exists with NEWER TimeStamp Insert ACCOUNT LIPDATE LOG failed Reason Failed Row exists with NEWER TimeStamp Delete all records Insert ACCOUNT_UPDATE_LOG failed Reason Failed Row exists with NEWER TimeStamp Insert ACCOUNT_UPDATE_LOG failed Reason Failed Row exists with NEWER TimeStamp Insert ACCOUNT_UPDATE_LOG failed Reason Failed Row exists with NEWER TimeStamp Insert ACCOUNT_UPDATE_LOG failed Reason Failed Row exists with NEWER TimeStamp Insert ACCOUNT_UPDATE_LOG failed Reason Failed Row exists with NEWER TimeStamp Insert ACCOUNT_UPDATE_LOG failed Reason Failed Row exists with NEWER TimeStamp Insert ACCOUNT_UPDATE_LOG failed Reason Failed Row exists with NEWER TimeStamp Insert ACCOUNT_UPDATE_LOG failed Reason Failed Row exists with NEWER TimeStamp Insert ACCOUNT_UPDATE_LOG failed Reason Failed Row exists with NEWER TimeStamp Insert ACCOUNT_UPDATE_LOG failed Reason Failed Row exists with NEWER TimeStamp Insert ACCOUNT UPDATE LOG failed Reason Failed Row exists with NEWER TimeStamp Insert ACCOUNT_UPDATE_LOG failed Reason Failed Row exists with NEWER TimeStamp Insert ACCOUNT TIPDATF 1 failed Reason Failed Row exists with NFWFR TimeStamn Source database gt My Source
33. For Oracle it can be set to a character set different to the system wide default NLS LANG if the source and target databases have incompatible character sets An example would be where one database in a replication pair was created with WE8WIN252 and loaded with data in CL8WIN1251 With other replicators the faulty database could not be replicated to one that had the correct character set The drop down list of character sets is not comprehensive The name of a missing character set can be entered manually Time field Used when time stamped conflict resolution is being set for the replication If you require this form of conflict resolution your tables should all include a column with exactly the same name for each that contains the date and time when each row was inserted or last updated If this functionality has been implemented IBP Replicator will ensure that the more recent row is preserved when conflicts arise Refer to the design notes about Timefields for discussion about choosing the right date time type for this style of resolution IMPORTANT The Timefield name is case sensitive AND it should be entered without double quotes You must type the name of the field exactly as the server sees it in the database That means it should be in all upper case characters unless the field has been defined with a quoted identifier For example if it was defined by ADD TimeFieldForRepl TIMESTAMP enter it as TimeFieldForRepl without the
34. IBP Replicator 4 1 r lt role gt log_to_window logginglevel log_to_file logginglevel log file file path or l file path pid file filespec Valid role identifier of a role package of privileges optionally defined in the configuration database for the user doing the replication Help no parameters Run in debug mode Start replication automatically and quit after replication is complete 1 Errors Only 2 Warnings and Detailed Error Description 3 Information 4 Detailed Information 5 Debug to 5 as above Provides an initial log file for use between server start and configuration load lt filespec gt Location and name of the file that Replicator uses to prevent multiple instances from running concurrently out of the same config file Controlling Running replserver Processes The environment variable ISC ROLE if defined will be used as the default role if the r switch is not used otherwise the role is treated as a no op ROLE NONE on Firebird Displays a tight summary of these switches and parameters This is logging level 7 the most verbose level If a support consultant asks you for a debug log run your replication process with this switch Convenient for running replication from another application script The logging switches are optional You can use a logging level switch here to override the default logging level defined in the configuration
35. IBPhoenix Editors Chapter 2 Overview Chapter 2 Overview 9 Chapter 2 Overview IBPhoenix Replicator is a management system that is is added to servers hosting Firebird Interbase or Oracle databases It keeps track of data changes in databases designated as sources and enables users to synchronise two or more databases at one or more sites locally or remotely Replication makes it possible to maintain identical copies of databases database tables or even pre selected sets between source databases and target databases The Replication Server s typical activity is to work behind the scenes replicating data at set intervals or according to a schedule or in response to specific events Replicator is designed as a software layer transparent to ordinary users that sits between databases and applications For Firebird and InterBase servers data integrity is managed by using the two phase commit protocol The effect of two phase commit is that data for a replication remains uncommitted on the target until the replication transaction has been committed on the source database This ensures data integrity should there be a problem in the source or target database or a network failure Since version 3 Replicator has had the ability to replicate to or from a file to cater for conditions where two tier networks connections are too slow or unreliable to sustain live replication An important component of the Replicat
36. REMOVE TABLE Use to remove a table object from a replication schema Syntax REMOVE TABLE lt target table name or number gt FROM SCHEMA schema number or name gt TARGET lt target db number or name gt SILENTLY If the number or name properties of the SCHEMA or TABLE parameters are omitted the current ones are used Be certain you are directing the changes to the right target If SILENTLY is used there will be no warnings about any failures during the removal of the table SHOW TABLE Shows information about the specified replicated table Syntax SHOW TABLE lt target table name or number gt OF SCHEMA schema number or name gt TARGET lt target db number or name gt SHOW TABLES Lists the replicated tables for a given or current schema and target database Syntax SHOW TABLES FOR SCHEMA lt schema number or name gt 2013 IBPhoenix Editors 166 IBP Replicator 4 1 TARGET lt target db number or name gt i In contrast with other commands if target database number or name is omitted tables for all target databases will be shown not just the current Working with System Objects CREATE SYSTEM OBJECTS Create system objects such as log tables and triggers for a given configuration If a schema number or name is omitted the current schema is used No defaults for the target database and ta
37. Start Replication RRR RRR RRR RRR Replicate My Initial Schema My Source gt My Target 1 09 26 12 15 24 36 Connected to DB E Customers IBP databases source fdb 09 26 12 15 24 37 Connected to DB babe d databases IBP target fdb 09 26 12 15 24 38 Disconnected from DB babe d databases IBP target fdb 09 26 12 15 24 38 Disconnected from DB E Customers IBP databases source fd TOTAL STATISTICS Hours O Minutes 0 187 Seconds The Toolbar Buttons You can use the toolbar buttons to load a different set of parameters and run a different replication File Options Help gt Replicate Clear Parameters Replication Timer Reload Configuration Parameters In the example the Timer button is depressed indicating that the configuration is doing or will do a timed replication If you are going to do a different replication as a one off you would click this button off Click the Clear Parameters button Note that the application will start to nag at you to enter something if you wait around too long Proceed to make your alternative entries gt In the Config Database field browse for or type in the full connection path to an alternative configuration database gt Fill in the User and Password fields and if needed the Role gt Change the default log to a different valid path and filename if you wish Click the Reload button to load the new parameters Click the Replicate button to start r
38. TARGETS Lists the target databases for one or all schemas Syntax SHOW TARGETS FOR SCHEMA lt schema number or name gt i In contrast with other commands if schema number or name is omitted target databases for all schemas will be shown not just the current one Working with Data Fields and Keys ADD DATA Add a data field definition for a table Syntax ADD DATA lt field parameters gt Field parameters 2013 IBPhoenix Editors Appendices 159 FIELD source field name The name of the column to add means All fields The keyword FIELD is optional NUMBER field number A number for the field that is unique amongst the fields in the replicated record Use a number that is the same as the field number used by the database engine in the metadata of the target database It is not mandatory to have these field numbers matching but it does reduce the CO risk of errors when later editing the field definitions in the Replication Manager program TO target field name The name of the field in the target record If the target field name is not set it is assumed to be the same as the source field name Omit this parameter if the FIELD argument is SCHEMA schema number or name required if the configuration has more than one schema TARGET target database number or name required if the configuration has more than one target database TABLE table number or name requir
39. THEN 2013 IBPhoenix Editors Chapter 9 Advanced Topics 123 UPDATE T SET K1 K1_NEW K2 K2_NEW K3 K3_NEW Fl Fl F2 F2 F3 F3 F4 F4 F5 F5 F6 F6 F7 F7 WHERE K1 K1 AND K2 K2 AND K3 K3 IF ACTION_TYPE D THEN DELETE FROM T WHERE K1 K1 AND K2 K2 AND K3 K3 EXIT END Comments In real life a less simplistic rendering of example above would need to test the parameters K1 K2 K1 NEW K2_NEW and K3_NEW for null and ensure that the local variables were initialized and reset in a timely way to avoid the constraint exceptions and unpredictable effects that null matching and inserts into non nullable table columns could cause 9 5 Complex Schemas Schema scenarios are usually a bit more complex than the simple one used to illustrate the general usage in the earlier topics In this topic are some tips about approaching the issues when schemas involve n way replications and heterogeneous scenarios Peer to Peer or Bi Directional Replication Bi directional replication is used when source databases need to send changes to target databases and vice versa The target databases become source databases to the original sources which become targets Although the concept is straightforward enough care needs to be taken to prevent changes from bouncing backwards and forwards ina continuous loop A change made to a source database gets replicated to a
40. Tools Help ki es mulu aw Defined Replication Schemata H E My Initial Schema Outbound Be Source database i My Source Ee Target databases cum e Remove eshi wes Clone Create system objects Remove System Objects urce AutoGenerate View conflicts Monitor Synchronize Symmetric synchronize Notice that the Symmetric synchronize option is disabled for obvious reasons As with the online synchronization A monitor window will pop up and display the synchronization as it happens The window will fill up very fast but you can scroll back to check what has been done 2013 IBPhoenix Editors Chapter 9 Advanced Topics 137 Work commited gt ACCC Rows processed 31 X ACCOL Synchronizing MEMBER gt MEMBER RATION Rows processed 256 v Synchronizing F TRANSACTION gt F TRANSACTION ANSAC Rows processed 1776 SAC TY Synchronizing GEN DOC ID gt GEN DOC ID Synchronizing GEN DONATION ID gt GEN DONATION ID 3ANSACT Synchronizing GEN GRANT ALLOCATION gt GEN GRANT ALLO Synchronizing GEN GRANT PAYMENT GEN GRANT PAYMEN C ID Synchronizing GEN MEMBER SER NUM gt GEN MEMBER SER N DON Synchronizing GEN PERSON ID GEN PERSON ID N gt GEI Synchronizing GEN PERSON ROLE ID GEN PERSON ROLE Synchronizing G_BATCH_ID gt G_BATCH_ID M gt GEN Synchronizing G PP TRANSAC ID
41. are a random 8 character alphanumeric string e g ROOjy82nu dat During replication the file name has the suffix tmp If the transaction is rolled back for some reason this temporary version of the file is deleted Should something untoward happen that leaves the file in place with this tmp suffix do not use it What Comes Next Once the file has been renamed with the dat suffix it is ready for its journey to the target server That file must be used to replicate to a database in a schema that is within a different configuration database IBP Replicator does not provide any tools for porting the offline files between the servers it is your responsibility to design and set up a 2013 IBPhoenix Editors 132 IBP Replicator 4 1 9 6 3 transport mechanism to suit your conditions The next section contains brief instructions for configuring the target server to receive the inbound file Inbound Offline Replication Setting up and running the inbound side of offline replication is similar to what you did in setting up the outbound side You configure it in a configuration database at the target side You must of course have a replication server licence with two replicant licences available there It is strongly recommended that you read the whole of the Offline Replication topic The outbound side of offline replication is described in detail Since the procedure at each side is almost identical this
42. b SET ECHO Controls whether cfged displays executed commands ECHO ON is useful in batch mode when standard input has been redirected Syntax SET ECHO boolean value Equivalent switch e The equivalent switch when passed from the command shell is e SET PROMPT Controls whether cfged should display the input prompt PROMPT OFF Is useful in batch mode Syntax SET PROMPT boolean value Working with Configurations CREATE CONFIGURATION Use to create a new configuration If a configuration is already open it will be closed For the Oracle driver the command CREATE CONFIGURATION is equivalent to OPEN INIT Syntax CREATE CONFIGURATION cfg connection string TYPE lt cfg type gt 2013 IBPhoenix Editors Appendices 149 USER lt user name gt PASSWORD lt user password gt ROLE lt user role gt The first parameter is the absolute path or for Firebird the alias for the location of the configuration database The keyword CONFIGURATION is optional The remaining parameters can be in any order Any that is omitted will be taken from the default configuration The default configuration if it is set is taken from the Windows registry or the Linux config file usually etc IBPReplicator conf Other parameters TYPE with either INTERBASE ORACLE FIREBIRD as the argument as appropriate USER either the database owner or the user name of
43. column mappings by matching column names in source and target iu Use this to unmap a column pair Use this to work with the mappings of sequences generators Primary Keys and Column Mappings The best guess mappings for the primary keys have occurred where primary key names and the key fields involved are the same in both source and target or key mappings were deduced from foreign key metadata The heuristics of this best guessing are not infallible you should verify the mappings Tables that do not yet have their primary keys mapped are marked with a red exclamation point In tables that have no primary keys but a matching UNIQUE constraint exists in both tables that mapping will show instead You can use the edit tools to tidy up individual key and field mappings as required 2013 IBPhoenix Editors 70 IBP Replicator 4 1 7 5 Once a field has been mapped as a key or as an element in a multi column key it requires no other mapping and is removed from the list of mappable columns Make sure that all the elements of the key are mapped Heterogeneous Mappings It is entirely feasible to create heterogenous table mappings where source and target tables have different table names and even if they have the same table names but different column names However both tables must have unique sets of same named columns that identify key the rows to be replicated and the columns bei
44. control the way foreign key violations are handled set the conflict resolution strategy set the levels of logging you want for replication events configure email notification of failed or interrupted replications 2013 IBPhoenix Editors Chapter 7 Defining a Replication Schema 81 ation Config E Database Tools Help ation Tools Help 1 Schema Defined Replication Schemata poo wn ww owe 5 1 My Initial Sch New gt Source d 2 Target d Global settings D Monitor Global settings S To begin modifying any of the global default settings either 1 Access them from the menu via Replication Global settings OR 2 Right click on the root node labelled Defined Replication Schemata and select Global settings from the context menu Global Settings If you are upgrading from an old version of IBP Replicator you may notice that the default replication scheduling attributes no longer appear in this display It disappeared in v 2 5 when replication scheduling was moved into a new engine within Replication Manager Please refer to the revised notes about the Scheduler Conflict resolution strategy When replicating new data from a source database to a target database where the primary key for the replicated row already exists IBP Replicator can be defaulted to use a specific strategy to resolve conflicts between source and t
45. increase in the possibility of duplicated replication Regardless of the setting two phase commit will be used only if both the Z source and the target database in a replication pairing are of the same type both Firebird or both InterBase and both have this setting turned on otherwise it will not be used InteBaseO 2 ACL Server required This is the network path where applicable and the full file path or database alias for Firebird of the database It follows the syntax used by the Firebird InterBase or Oracle client respectively to connect to databases It should accord correctly with the format required by the network transport protocol and the file system of the host server that is running the database engine For Oracle this will be the URL TNS or equivalent that will find the database according to your server s configuration For Firebird and InterBase suppose the database file name is source fdb 2013 IBPhoenix Editors Chapter 6 Installation and Setup 37 and it is located on a Windows server named dev in a directory called G IBPhoenix IBP Replicator data For TCP IP protocol the server entry should be dev G IBPhoenix IBP Replicator data source fdb For Named Pipes sometimes referred to as NetBEUI protocol the server entry should be dev G IBPhoenix IBP Replicator data source fdb For an older InterBase database named source gdb on Novel
46. issue if you are on loading and moving files around at the command line on some POSIX platforms Non ANSI Table Names If non ANSI characters were used in defining tables in either database there is the possibility of problems occurring with the names of the OLS files at filesystem level if the target platform is not configured to interpret those characters correctly This is not Replicator s problem per se but it will need to be checked to ensure that your OLS can proceed smoothly Character Sets The off loaded files are in a binary format so there should not be any character set issues at application level If you are using OLS to populate a new empty database make sure that the character set and collation attributes of the target database and all relevant objects in it are the same as those in the source database Running an Off load As with off line replication you need to define a target database that is a folder somewhere in your filesystem If you have already set one up for off line replication it is possible to use that Otherwise go to the start of this section for instructions on how to do this setup Once this target structure exists the approach for an off line synchronization is no different from that for an on line one In the Replication tab select the offline database and right click on it Select Synchronize 2013 IBPhoenix Editors 136 IBP Replicator 4 1 Replication
47. log file name and location at server start for use until the configuration loads for troubleshooting purposes Full conflict resolution options for off line replication Conflicts in any operation insert update delete can be resolved according to the same rules as for on line conflicts The integrity of offline data files is now protected with CRC go switch implemented for Linux On Linux the replserver program can now be executed on demand using the go switch Improved Diagnostic Messages Text in some replserver diagnostic messages has been improved Monitoring is Disabled by Default Table Settings Keep Statistics is flagged OFF by default for all tables Since the Replication Monitor feature requires the statistics in order to report this means monitoring is disabled The idea is to reduce the performance overhead induced when the server program has to write statistics to the configuration database at each replication cycle Copy Paste Support for Error Dialogs Details in graphical error dialogs in Windows environments can be selected and copied to the clipboard for pasting into text files or email messages Separated Server Licensing Licences for the three database server vendor options are distributed separately For details about installing licences please refer to the topic License Manager Licences can also be installed and removed using the configuration editor Known Issues Byte length det
48. quotes If it was defined by ADD TimeFieldForRepl TIMESTAMP enter it as TIMEFIELDFORREPL SEir pir dt IneBase Administrative role Similarly to the administrative user name and password this is the SQL role that is used by the Replication Manager tool when administering the database being registered The replication server uses another replication role that is provided when databases are specified in a replication schema Remote Access Parameters IBP Replicator can use the Windows Remote Access Services RAS to replicate across a dial up connection The following database parameters control how it works ir bird IateBaseCO 2 ACL 2013 IBPhoenix Editors Chapter 6 Installation and Setup 39 RAS name This is the unique name of the dial up connection as defined in the Windows Dial up Networking dialog RAS The dial up username that the replication should use when username dialling out RAS The password that the replication should use when dialling out password Keep Controls whether the replication hangs up as soon as it is connection disconnected from the database or stays connected until the end of the replication cycle all schemas leaving a user to terminate the RAS connection Fields for Replicating to Files If you select Files as the Database type the fields that appear are fewer a RE Database properties Type File Descriptive name New database Comm
49. representation of your longest primary key However setting it to an unnecessarily large value will degrade database performance eSEir pir dt fnferBase Use 2 phase Commit Normally if both the source and target databases are of the same database type a replication is executed in a single transaction across connections to each of the participating source and target databases The Firebird or InterBase database engine does some extra steps when such transactions are committed to ensure that the work is actually committed in all the involved databases If any connection is lost before the second phase the transaction is flagged limbo in all of the databases This style known as a two phase commit transaction is configured True by default when you begin configuration with a Firebird or Interbase database or add to one that contains only databases of the same type Two phase commit can be optionally turned off by setting this property to False All replications will then be performed with discrete transactions in each source and target Conditions may exist wherein the use of discrete transactions might be a useful option even when the sources and targets are homogeneous For example if the network is prone to instability and causes replication to produce limbo transactions frequently it could be worth setting two phase commit to False to test whether the avoidance of limbo transactions is an acceptable trade off against the slight
50. select the task you want Cloning Targets A schema can support one or multiple target databases for a source database and different data can be replicated to different targets see Choosing replicated tables next A separate definition of the tables primary keys columns and rows to be replicated is required for each target database involved That makes it possible to have very fine grained control for any schema It is common for a schema to encompass a number of targets that are going to be replicated with the same or very similar data Because setting up numerous such target databases manually could be repetitious and time consuming it is possible to set up one target it and clone its definitions to other targets Cloning a target can be done several ways much as you do with other tasks already discussed You can gt drag the specific target database node that you want to clone and drop it onto the general target database node or another schema node gt select the specific target database right click and choose Clone from the context menu gt use Replication Target Clone from the replication menu Once the new target is in the tree supply the name by selecting from the list of databases that has been registered Click OK and a copy of the schema defined for the original target database will be created for the cloned target database Any differences required can be tidied up by editing the cloned definitions TIP Per
51. settings Connection Settings Event logging Log to window level 3 Information v Log to file level 3 Information Y Log file targett LOG a Browse Check off Use default logging and adjust the event logging settings to suit your needs When you are done click OK to save the details of the target database node to the tree The descriptive name of your target database appears along with two new nodes Replicated Tables and Procedures and Replicated Sequences File Configuration View Database Replication Tools Help t um Defined Replication Schemata y Target 1 B E My Initial Schema i Q gt Source database E Target databases E My Target 1 i tul Replicated tables and procedures Po m Replicated sequences H E My Second Schema In the following sections you can find out how to gt select and map the tables and procedures for the replication gt identify the primary keys choose which columns are to be replicated tell the Replication Manager to create the system objects in the source database 2013 IBPhoenix Editors 60 IBP Replicator 4 1 7 4 Accessing the Node Again Whenever you need to access a particular target database again for these tasks or you want to edit or remove the target just select it in the Target databases node and use one of the previously described methods to
52. the contents into the correct sub directories as long as you include the P switch in your tar command tar zxPf IBPReplicator 4 0 n i586 tar gz The n n character in the tarball name will vary according to sub release version The replserver executable will be installed into opt IBPReplicator e The IBPReplicator conf configuration file will go into etc e The IBP Replicator shell script will go into into etc init d Important The default replication server configuration is made to run replserver at OS runlevel 3 If your Linux distro is running at runlevel 2 the installation default for Ubuntu for example replserver will not run on system boot You can either raise the runlevel to 3 in the file etc inittab or edit the file etc init d IBPReplicator change the lines Default Start and Default Stop and then reinstall the service Configuring the Daemon You need to configure some information that the replication daemon uses to start up To make these settings open the configuration file etc IBPReplicator conf as root using any plain text editor you prefer such as mcedit or nano Some sample entries are there commented with To make a setting delete the comment marker and type in the appropriate value taking care to observe case correctness and to follow the format as written Parameters settings to start replicator Uncomment and modify as appropriate Configuration type Can be interbase or firebird C
53. the current working directory If you are defining multiple replication schemas you might wish to have the server log each one to its own log file In that case check off Use Default Logging and enter a path that exists on the filesystem of the IBP Replicator host machine and if needed a different log file name that can be identified easily by the system administrator IBPReplicator Schema settings Connection Settings Event logaing Log to window level 3 Information Y Log to file level 3 Information Y Log file Je admin logs replicator replag log Browse Use default logging Cancel Click OK to update the details of the source database node The commands for creating a removing system objects are discussed in Creating Source System Objects Each schema can only have one source database so you need to define a schema for each of your replications A source database in one schema can be a target database in another schema and a single source can replicate to multiple targets 73 Choosing the Target Database A target database is a database to which replicated data is sent When identical data is to be sent to multiple target databases it possible to define an initial target database and then copy clone that definition and apply it to other target databases To define a target database right click the Target databases node and select the Add 20
54. to Branch scenario a multi segment primary key can be implemented consisting of a Branch code a generated ID For existing databases this solution will entail a large amount of work both in the databases and in existing applications e An alternative to augmenting the primary keys is to use GUIDs Implementing a GUID primary key would avoid impacting the existing single column PK structure and possibly reduce the amount of change required in application code On the database side it requires a type change simpler to do if you are using domains and alteration of any trigger and stored procedure code that you have to generate values for keys e It is possible to use a uniquely constrained key that is the primary key This might be necessary in some heterogeneous schemas e Another alternative is to replicate changes from all of the targets that are going to receive an update replication back to the central database first before anything gets replicated back out to the targets All inserts from the targets go into the central database via an insert trigger which generates a new primary key for them from the central database Replication out to the targets just has to be able to ascertain which of the new inserts originated from the target in focus and treat them as updates The main need would be to tag records on both sides so that both the central and the target databases know that they need special treatment How or whether
55. 13 IBPhoenix Editors 56 IBP Replicator 4 1 Target task File Configuration View Database Replication Tools Help B 5 Defined Replication Schemata My Target 1 E My Initial Schema B gt Ace database My Second Schem Alternatively you could drag the target database from the list of registered databases in the left pane over to the Target databases node File Configuration View Database Replication Tools A PEBE Olhe 12585 mr Y Defined Replication Schemata QC Target 1 EF My Initial Schema D gt Source database i m d Target databases My 1 B iH My Second Schema R or you could click the Add Target Database button Target Database Settings Connection Tab 2013 IBPhoenix Editors Chapter 7 Defining a Replication Schema 57 IBPReplicator Target database settings Connection Settings Event logging Registered database My Target 1 T Replication username REPL Replication password panee ooo Replication role i Test connection gt If necessary drop down the list of registered databases and choose the one that is to be the target database gt Supply the username password and if used the role to be used by the replication server when it connects to the target database The name of the replication user does not have to b
56. 2n4 KLMN3 GPRPdTELHe gKD1 c6b Y7w 983H jWR OKVZG73 CbmF amp cM w jEYA4dXIa XDWNiQO0A8CGBbGBM FN RjFU K83781c I BNCH2108 e558J aPob 6 al gt Continue to add any additional licences you have in the same manner Use EXIT to end your cfged session For more information about cfged refer to the Configuration Editor topic in Chapter 9 Advanced Topics Management Tools The Replication Manager encompasses a number of utilities through which you can manage and monitor replications in your network at any time Accessing the Replication Setups All of the replication setups that you can access on your network are available through Replication manager Each setup is in a configuration database Recently visited configurations are stored in the Registry of the machine from which they are accessed Replication manager retrieves the paths to these configurations enabling quickstart access to the config database via a picklist in the File menu J fx IBPReplicator My Replication Config Configuration View Database y i zz New configuration D Open configuration an Close configuration Drop configuration F exit Alt X My Replication Config For existing configuration databases that have not been accessed before from this machine you can use File Open or click the Open button on the toolbar An input form 2013 IBPhoenix Editors Chapier 8 Managing Replication 99
57. 3 IBPhoenix Editors Chapter 3 IBP Replicator Architecture 12 IBP Replicator 4 1 Chapter 3 IBP Replicator Architecture This chapter introduces the components of IBP Replicator and explains the role of each in the replication system Replicator Server The IBPhoenix Replicator Server ReplServer is the program that performs replication operations To determine what schemas need to be replicated where it uses a configuration database A single server can replicate multiple source databases cyclically On Windows server platforms it can be run as a Service recommended or as an application Replication Manager The Replication Manager is a Windows graphical tool for the user to define manage and monitor replication schemas Configuration Database IBP Replicator s configuration database is where the program saves and maintains the details of what is to be replicated and where it should be replicated from the source and to the target The specifications for a replication operation are referred to as a replication schema You can have Replicator create multiple configuration databases to handle multiple schemas or you can store multiple schemas in one single configuration database Replication Processing Tables IMPORTANT For IBPhoenix Replicator to work properly each base table that is to be involved in replication must be uniquely identifiable Ideally each table involved should have its own un
58. 6 Replication one way 26 Replication planning for 20 Replication sequence of events 16 Replication synchronous 13 Replication timestamps for 24 Replication tree 46 Replicator 12 Replicator definition of 13 replserver switches Linux 94 ReplServer exe 85 Requirements 6 Requirements database engine 6 Requirements disk space 6 Requirements licensing 6 Requirements minimum database installation Requirements operating system 6 Role 33 Role Administrative 38 Role for source database 50 Role for target database 55 Row level condition 72 Row level conditions 70 Row level replication condition 72 Row level replication condition global 58 o Scheduler tool 101 Schema View tool 111 Schema creating 46 Schema numbering 116 Schema complex 123 Schema defining 16 Security 9 Separator character 54 73 Separator character global 54 Separator character table level 73 Sequence of events 16 2013 IBPhoenix Editors SET AS DEFAULT cfged 150 SET BAIL cfged 147 SET CURRENT cfged 147 SET ECHO cfged 148 SET PROMPT cfged 148 SHOW CURRENT cfged 147 SHOW DATABASE cfged 153 SHOW DATABASES cfged 153 SHOW FIELDS cfged 160 SHOW GLOBAL cfged 169 SHOW LICENSES cfged 151 SHOW SCHEDULE cfged 168 SHOW SCHEMA cfged 155 SHOW SCHEMAS cfged 156 SHOW SEQUENCES cfged 162 SHOW TABLE cfged 165 SHOW TABLES cfged 165 SHOW TARGET cfged 158 SHOW TARGE
59. AS DECLARE VARIABLE ROW_EXISTS SMALLINT BEGIN RESULT 0 default return value ROW EXISTS 0 initialize IF EXISTS SELECT 1 FROM T WHERE K1 K1 AND K2 K2 AND K3 K3 THEN ROW EXISTS 1 Tj z Gc cm Inserts If the row already exists then exit with result 1 This causes the Replication Server to apply conflict rules which will probably cause the procedure to be called again but now with ACTION_TYPE of U An alternative approach would be to simply change the ACTION_TYPE to U and proceed to update the row instead IF ACTION_TYPE I AND ROW_EXISTS 1 THEN BEGIN RESULT 1 EXIT END Updates If the row does not exist then exit with result 1 This causes the Replication Server to apply conflict rules which will probably cause the procedure to be called again but with ACTION_TYPE of I An alternative approach would be to simply change ACTION_TYPE to I and proceed to insert the row instead IF ACTION_TYPE U AND ROW_EXISTS 0 THEN BEGIN RESULT 1 EXIT END Deletes If the row does not exist then exit with result 1 The Replication Server will log the error but otherwise ignore it IF ACTION_TYPE D AND ROW_EXISTS 0 THEN BEGIN RESULT 1 EXIT END IF ACTION_TYPE I THEN INSERT INTO T K1 K2 K3 F1 F2 F3 F4 F5 F6 F7 VALUES K1_NEW K2_NEW K3_NEW Fl F2 F3 F4 F5 F6 F7 IF ACTION_TYPE U
60. ATION gt CORP ff COUNTRY gt COUNTRY 2 ff CURRENCY gt CURRENT t fl F TRANSACTION gt F_T Create system o The Table Settings Dialog rri re ees NN M Bow level replication condition Settings Synchronization enabled Keep statistics Time field name TIMEFIELD Conflict resolution strategy E Default Priority based Time stamped Master slave Separator character decimal ASCII code B r Foreign Key Violation behavior C Default Error Conflict C Ignore m Replicated operations Inserts Updates Deletes Comments Cancel Fields on the Table mapping properties Dialog 2013 IBPhoenix Editors 71 72 IBP Replicator 4 1 Row level replication condition This is a condition that would be inserted into the IF predicate of a branching statement in a trigger to limit the rows selected Given the basic syntax of a PSQL condition IF some condition THEN BEGIN END you might for example replicate only unpaid invoices using IF NEW PAID lt gt Y THEN You would pick up the some condition part of the predicate and enter that into the row level replication condition as PAID lt gt y Note the colon prefixed to the column name Although this example is simple there is no limit to the complexity of the condition any condition that would be v
61. COMMENTS My Initial Schema 1N REPLNO 2013 IBPhoenix Editors Chapter 9 Advanced Topics 117 So far we have only one schema in the schemata table Its replication number is 1 Next we look at the databases defined Relations Procedures Domains Generators Exceptions UDFs MONS TRANSACTIONS Tables System Inf REPLSCONFIG Z Views Domain Inf dE r DC REPL DATAFIELDS Fields Data Indexes Constraints Triggers Source Desc Depend Field Names List Desc DBNO DBPATH DBNAME ADMINUSER ADMINPAS 5 29 Ai E Customers IBP databases source fdb My Source sysdba oMHE a L Es REPL RELATIONS 2 babed as ere Dee My Target 1 sysdba BMHE a 0 REPL SCHEDULE 3 Offline REPL SCHEMATA REPL SEQUENCES REPL SUBSCRIBEDDB Here we see two databases and our offline target in the order that they were defined Now we look at the subscribed databases databases in the configuration that have actually been defined as targets Relations Procedures Domains Generators Exceptions UDFs MONSTRANSACTIONS I met mm ARE ET ENT wee T1 REPL DATABASES I D M H EP IITSKT TY 4 YY ae REPL DATAFIELDS Fields Data Indexes Constraints Triggers Source Desc Depend Field Names List Description REPLIKEYFIELDS DBNO USERNAME PSW
62. J Edit Database is for doing any modifications required to the database currently selected amp Remove Database is for taking a database out of the configuration It doesn t drop the database of course 9 Test Connection does the same thing as right clicking on a database and selecting Test Connection i New Schema launches the creation of the replication schema that you are about to define 2013 IBPhoenix Editors 4 IBP Replicator 4 1 Registering a Database Click the Add button in the toolbar Replication Tools Help ado 6 8 e E wawawan gt Edit Remove Test connection Connected users count Gr m m eplication Schemata A new database record is initiated in the fields editor ready for adding the necessary information for the replication server to find the database Desariptive name Interbese 13 Because of variations between the different database drivers the set of fields displayed may not be exactly as shown in the screenshots Fields for the Database Record 2013 IBPhoenix Editors Chapter 6 Installation and Setup 35 2 RE Database properties Database Type Select the server type Firebird InterBase Oracle File of the database you are registering The fields that appear after this selection has been chosen will vary accordi
63. MBER gt MEMBER E MGROUP gt MGROUP v PERIOD gt PERIOD v PERSON gt PERSON v TRANSAC GROUP TRANSAC_G TYPE gt TRANSAC_TYF Replicated sequences v GEN DOC ID gt GEN DOC ID v GEN DONATION ID gt GEN DON v GEN GRANT ALLOCATION gt GEN GEN GRANT PAYMENT gt GEN G v GEN MEMBER SER NUM gt GEN Select al Unselect all lt Generate N Check off any objects you do not want to autogenerate objects for e g because you do not want to replicate them 4 Replicating sequences in a multi master scenario will corrupt targets in I a heartbeat If your schema is replicating in such a scenario you MUST check all sequences generators OFF Use asterisk Check Use asterisk if you would like to have Replication Manager also map all of the source and target objects automatically at the same time by mapping column names to column names Although this is a time saver if your source and target databases have the same structure its main purpose is to enable mappings to be easily updated if the table structure should change In that event editing of the schema would not be required it would be enough just to reload the configuration Click the Generate button 2013 IBPhoenix Editors Chapter 7 Defining a Replication Schema Replicated sequences Select all Unselect all Use asterisk TABLE PERSON gt PERSON Key Field
64. N REPL LOG We find some triggers have been created for our replicated tables The prefix is REPL 1 and the number following it is the replication number of the table it was the fourth table we defined in the schema Each configuration database numbers its objects independently As long as the internal Schema Numbers are unique across all configuration databases no conflicts can occur Setting Your Own Schema Number When creating a new Configuration Database you can ensure that the Current Schema Number is set to a number that will prevent two configuration databases using the same numbers Do this task before you save the new schema record It is necessary only if one or more source databases are included as sources in more than one configuration database Use Configuration Current Schema No from the main menu For example ConfigOne fdb could start at 1 whilst ConfigTwo fdb could start at 500 2013 IBPhoenix Editors Chapter 9 Advanced Topics 119 9 2 9 3 Multiple Schemas within One Configuration Database Each new Schema created within any configuration database will cause the internal Schema number to be incremented by one the default Current Schema No that you see when this dialog pops up is generated internally by a generator called REPL GEN so there is no risk of conflict with multiple schemas inside the same configuration database Most configuration databas
65. ONFIG TYPE interbase Configuration DB connection path CONFIG_DB opt IBPReplicator Config fdb path to default configuration database 2013 IBPhoenix Editors Chapter 8 Managing Replication 93 Configuration DB user CONFIG_USER SYSDBA see note below Configuration DB password CONFIG_PASSWORD masterkey see note below Configuration DB role ROLE repl admin see note below Name and location of pid file optional PID_FILE var run IBPReplicator pid see note below User and Password The settings CONFIG_USER and CONFIG_PASSWORD refer to the user name and password for the adminstrator of the configuration database as you defined them or have yet to define when setting up the configuration using the Replication Manager utility either from a Windows client on the network or installed locally under wine Configuration Database Role If you needed to create an SQL role with permissions to enable a non SYSDBA and non Owner user to operate on the configuration database then configure this parameter otherwise ignore it WARNING Never use the name REPL for a role Location of PID File This setting determines where the replserver will write the pid file that behaves as a lock to prevent two instances running concurrently It can be reconfigured here or alternatively with a command line switch Starting replserver Automatically as a Daemon To set up replserver to run aut
66. ORD USERROLE COMMITCDUN pes 2 REPL REPL_ADMIN 3 REPL gtGa H REPL ADMIN REPL RELATIONS REPL SCHEDULE REPL SCHEMATA REPL SEQUENCES Again no surprises We don t see our Source database here because it is the published database for this configuration i e the one that is replicating its data to the targets In the next shot we look at some system objects created in our source database 2013 IBPhoenix Editors 118 IBP Replicator 4 1 Relations Procedures Domains Generators Exceptions UDFs ACCOUNT_UPDATE_LOG Tables System Inf PR s BANK_ACCOUNT M Views Domain Inf er Ru 4 CORPORATION COUNTRY Fields Data Indexes Constraints Triggers Source Desc Depend Field Names List Descriptic New Edit sea 32760 AFTERINSERT OR UPDATE OR DELET CURRENCY F_TRANSACTION MEMBER B ACCOUNT UPDATE LO MGROUP MON ATTACHMENTS 3 ECLARE VARIABLE C OP CHAR l MONS CALL STACK GIN C_OP CASE WHEN INSERTING THEN I WHEN UPDATING THEN U WHEN DELETING THEN D END IF USER lt gt REPL THEN BEGIN INSERT INTO REPL LOG REPLNO SUBDBNO RELATIONNO REPTYPE NEWKEY OLDKEY SEP VALUES 1 4 77 C_OP NEW LOG ID OLD LOG ID Dy MON CONTEXT_VARIABLE MON DATABASE MON IO STATS MON MEMORY_USAGE MON RECORD_STATS MON STATEMENTS MON TRANSACTIONS PERIOD PERSO
67. TES ETE 130 Inbound Offline Replication 132 Off line Synchronization 134 Appendices 140 Appendix I Supported Data Types and Compatibilites sn 140 Appendix 11 Command Line Editor cfged 144 Appendix Ill Version Notes a U u uuu 170 Index 174 2013 IBPhoenix Editors Chapter 1 IBP Replicator Requirements 6 IBP Replicator 4 1 Chapter 1 IBP Replicator Requirements Operating System IBPhoenix Replicator Server 4 runs on e Microsoft Windows all 32 bit and 64 bit versions as a 32 bit application e Linux 32 bit and 64 bit platforms both 32 bit and 64 bit versions available as appropriate The current version of the Replication Manager needs to run on a Windows host which may be a Wine environment on a Linux server It can access a remote Replicator server on Linux Database Engine Replicator supports replication to and from databases running under e Firebird any released version e InterBase 5 x and later versions e Oracle 9 and later versions Names of Client Libraries The client libraries must be named according to their native conventions On Windows this means fbclient dll for Firebird gds32 dll for InterBase and oci dll for Oracle on Linux it means libfbclient so for Firebird libgds so for InterBase and libcintsh so for Oracle versions that can run on Linux Disk Space To install the IBPhoenix Replicator software you need at least 5 25MB o
68. TRANSACTION has to go to the very last position because it depends on all of the other tables 2013 IBPhoenix Editors 76 IBP Replicator 4 1 5 Target databases E My Target 1 Ci fff Replicated tables and procedures f ACCOUNT UPDATE LOG gt ACCOUNT UPDA 1 BANK ACCOUNT gt BANK ACCOUNT 1 PERIOD gt PERIOD E CORPORATION gt CORPORATION 0 COUNTRY gt COUNTRY 1 CURRENCY gt CURRENCY MGROUP gt MGROUP PERSON gt PERSON 1 _ TRANSAC GROUP gt TRANSAC_GROUP 1 _ TRANSAC TYPE gt TRANSAC_TYPE 1 MEMBER gt MEMBER F TRANSACTION TRANSACTION ff TRANSACTION ID gt TRANSACTION ID L ttg y md Replicated sequences D E Ee z E E RR Ee E HE E Simply continue to shift tables and procedures down and up until you are happy that you have taken care of the dependency issues Performing a Global Synchronization Select the database node of the target you want to synchronize with the source right click and select the type of synchronization you want on Tools Help eBB5mu mus ec AY 4 Defined Replication Schemata My Initial Schema Er gt Source database fi My Source Target databases E My Target 1 EF t Replicated tables and procedures Define AutoGenerate View conflicts Synchronize Symmetric synchronize The dialog window shows all of the synchronizations checked for the mapped table
69. TS cfged 158 SIGNAL SERVER cfged 170 Source database 12 Source database choosing 50 Source database event logging 50 Source database settings 50 Stored procedures 121 Synchronization 12 Synchronization of tables 74 Synchronization order 74 Synchronization off line 134 Synchronous replication 13 System Objects 16 System Objects creating 78 System Objects removing 78 zT Tables mapping source and target 60 Tables synchronization 74 Target database 12 Target database choosing 55 Target database Generaltab 55 Target database periodic commit 55 Target database settings 55 TCP IP protocol 30 Timefields for timestamping 119 Timefields generating a script for 119 178 IBP Replicator 4 1 Timestamps for conflict resolution 24 Tools 98 Tools Conflict viewer 106 Tools License Manager 108 Tools Notify server utility 105 Tools Replication Monitor 99 Tools Replication Scheduler 101 Tools Schema Viewer 111 Tree nodes 46 Two phase commit 16 oe Unique keys 24 UPGRADE cfged 150 Username for source database 50 Username for target database 55 Using synch files for Replication 132 Utilities 98 View Conflicts tool 106 LW x Working on definitions 47 2013 IBPhoenix Editors 2013 IBPhoenix Editors
70. Use this parameter if you need to override the conflict resolution strategy that is set for the schema for this table only Available strategies are gt 0 priority based gt 1 timestamp based gt 2 master slave FK BEHAVIOR DEFAULT ERROR CONFLICT IGNORE The global default for dealing with foreign key violations is selected by default You don t need to use this parameter unless you want a foreign key violation to be treated differently for this relation than the specified global method Choose an alternative behavior as follows Error causes an error to be written to the log and the record will not be replicated Conflict treats the violation as a conflict that will be resolved according to the resolution strategy applicable to the table 2013 IBPhoenix Editors Appendices 165 Ignore the offending record will not be replicated Default reverts the setting to the default global behavior MODIFY TABLE Use to modify properties for replicated table Parameters follow the same rules as for ADD TABLE above Syntax MODIFY TABLE lt table number or target table name gt OF SCHEMA schema number or name gt TARGET target db number or name gt SET lt table parameters gt If the number or name properties of the SCHEMA or TARGET parameters are LZ omitted the current ones are used Be certain you are directing the changes to the right target
71. a in the source database If you don t want to proceed click No to abandon the idea NOTE Normally you won t want the overhead of performing all replication instantly it is perfectly OK to break your replications out so that most of the replication runs asynchronously and the source database configures just the essential 2013 IBPhoenix Editors Chapter 6 Installation and Setup 33 close to real time replication The database will be added to the selection list beneath the File menu 6 2 Registering Databases The registration of a database identifies the database to IBP Replicator and provides all the information needed to connect to the relevant databases All databases that are involved in replication need to be registered both source databases and target databases Once the configuration database has been created you can register the databases that are going to be involved in replication To start registering a database stay on the Databases tab Above the panes is a toolbar The Toolbar The toolbar gives access to the commands available during database registration They provide shortcuts to the same commands that are available from the Databases menu The active buttons at any point appear in an enabled state while unavailable buttons are greyed out Hover hints are available on all of the buttons Sas H amp Add Database is for adding a new database to the configuration E
72. a user with SYSDBA privileges If you need this you will also need to include PASSWORD along with the password as its argument ROLE role_name if the user credentials are to be tied to a role for access to configuration structures DROP Drop the configuration database It takes no parameters or arguments Syntax DROP ORACLEFor the Oracle driver the command DROP is equivalent to CLEAR EXTRACT Export the current configuration into a file or a console The resulting output is a script that can be used for cfged Syntax EXTRACT INTO lt file name gt The keyword INTO is optional If the file name is not set output will go to the console INIT Initialise configuration structures in a currently opened user database that is nota dedicated configuration database This command takes no parameters Syntax 2013 IBPhoenix Editors 150 IBP Replicator 4 1 INIT CLEAR Use to clear a replication configuration from a user database without dropping the database It takes no parameters or arguments Syntax CLEAR SET AS DEFAULT Set the currently opened configuration as the default one Syntax SET AS DEFAULT On Windows versions higher than XP and Server2000 cfged exe must be running with Run As Administrator privileges for this command to work UPGRADE Upgrades the configuration structures in the currently opened database to the current version Use this command af
73. alid in a normal IF statement in PSQL can be used as a replication condition Synchronization enabled By default when synchronization is performed this object is synchronized Uncheck it only if you want to exclude this object from synchronization Keep statistics Check this box to use the Monitor tool to review IBP Replicator s performance By default it is checked OFF for all tables to reduce performance overhead by allowing replserver to work with read only access to the tables in the configuration database NOTE Monitoring of the table is disabled while Keep Statistics is checked off Conflict resolution strategy By default conflicts are resolved using the default method for the schema If a source and target pair of tables needs a different strategy for resolving conflicts it can be specified individually here by checking the required strategy instead of the one selected from the existing default Priority based Resolution the relation in the higher priority database takes precedence For example if a source relation has precedence conflicts are resolved as follows e An update finding no identical key record in the target database is converted into an insert 2013 IBPhoenix Editors Chapter 7 Defining a Replication Schema 73 e An insert finding a record in the target database with an identical key is converted into an update e A delete finding no identical key record in the targe
74. ame is added to the list It takes at least two registered databases to make a replication configuration so carry on and register each database as required 2013 IBPhoenix Editors Chapter 6 Installation and Setup 41 IBPReplicator My Replication Config File Configuration View Database Replication Tools Help PEBE hk t 555 muaj mas AY Source Database Defined Replication Schemata arget Database Firebird Descriptive name Target Database Comments Priority Highest Key size 128 Use 2 phase commit True Server babe repltarget Administrative user name SYSDBA Administrative password Character set NONE Time field RAS name RAS username RAS password Keep connection Administrative role List of registered databases Once you save the last of your databases you are ready to move on and define a replication schema This is the Toolbar button that launches the creation of the replication schema You can also right click on the legend in the right hand pane and select New from its context menu or use Replication gt Schema gt New in the menu at the top of the screen 6 2 1 About Licences You can use the Replication Manager for many of your initial configuration tasks without needing to install your licences However you won t be able to start a replication server or activate any of your replications until you install your licences Existin
75. ameters Syntax SHOW CURRENT SET CURRENT Set the specified object DATABASE SCHEMA TARGET TABLE to be the current one of its type Syntax SET CURRENT object TO object number or name object DATABASE SCHEMA TARGET TABLE Take care with this command if specifying the object number as the argument as no existence check is performed n Neither is there any check to verify whether specified table or target database belongs to the current schema Program Settings SET BAIL Controls whether cfged should exit immediately after an error occurs Useful during script debugging it is alternatively available as a command switch Syntax SET BAIL lt boolean value gt 2013 IBPhoenix Editors 148 IBP Replicator 4 1 Use of SET BAIL ON in interactive mode is probably not very useful c Programs IBPhoenix Replicator gt cfged IBPhoenix Replicator version 4 1 0 Root directory is c Programs IBPhoenix Replicator gt set bail on gt open cfg Error I O error during CreateFile open operation for file cfg f Jae Error while trying to open file The system cannot find the file specified Unsuccessful execution caused by a system error that precludes succe ssful execution of subsequent statements c Programs IBPhoenix Replicator gt Equivalent switch b The equivalent switch when passed from the command shell is
76. ameters must be in strict order ADD KEY Add a key field definition for a table Syntax ADD KEY field parameters NUMBER field number A number for the field that is unique amongst the fields in the replicated record Use a number that is the same as the field number used by the database engine in the metadata of the target database lt is not mandatory to have these field numbers matching but it does reduce the risk of errors and confusion when later editing the field definitions in the Replication Manager program FIELD source field name The name of the key column segment to add TO target field name The name of the corresponding key field in the target record If the target field name is not set it is assumed to be the same as the source field name SCHEMA schema number or name required if the configuration has more than one schema TARGET target database number or name required if the configuration has more than one target database TABLE table number or name required if more than one table is replicated in the schema 2013 IBPhoenix Editors Appendices 161 MODIFY KEY Use to modify a key field definition Field parameters follow the same rules as ADD KEY above Syntax MODIFY KEY FIELD target field name or number OF SCHEMA schema number or name TARGET target db number or name TABLE table number or target table name SET field parameters
77. appear on the display as a list Don t worry about the order in which the licences are registered When the time comes for action each server is only concerned that there are enough available licences of each type to perform the tasks it is asked to do When you are finished click the Close button to terminate the applet You can access the License Manager any time by returning to the Tools menu or running it from the Start Menu Loading Licences Without Windows If you have completed your configuration for running IBP Replicator on a non Windows host and no longer have Windows or Wine available to run the License Manager you can load your licences manually from a script For more details please refer to the topic Loading Licences Manually 8 3 6 Schema View Schema View accessed from the Tools menu provides a way of storing a visual map of the physical layout of your replication servers Although this tool is aware of how the sources and targets in a configuration relate to one another at this point it is not a visual doorway to your replication schemas However it can be useful as a quick way to identify information about the databases in your replication system and to store it diagrammatically Click on a database icon 2013 IBPhoenix Editors 112 IBP Replicator 4 1 1BPReplicator Schema View gt a bak CHAAR 2 C Offline CANADA UNITED STATES
78. arameters Working with Target Databases ADD TARGET Add a new target database to the schema If a schema or a database name is omitted current values are used Syntax ADD TARGET DATABASE lt database name or number gt lt target DB parameters gt lt database name or number gt is mandatory and must be either the case sensitive friendly name you used when registering the database or the database number that was auto generated You can check these using SHOW DATABASES Target database parameters TO SCHEMA lt schema name or number gt if you have multiple schemas use this to designate the schema to which the new target is to be added The keywords TO and SCHEMA are optional The three parameters USER lt user name gt PASSWORD lt user password gt and if required ROLE lt user role gt are for the credentials of the replication user normally REPL COMMIT lt commit count gt sets the number of records that constitute a batch that is to be committed if and only if you need to use the periodic commit provision Don t use this parameter unless it is actually necessary It can impact the general performance of the database over time and breaking a replication into numerous separate transactions breaks the overall atomicity of a replication For more information see the topic Periodic Commit P Ifthe conditions are sufficiently poor to necessitate resorting to periodic commit it recommended that you use
79. arget records A Settings Event logging Error Notification IBPReplicator Global settings m Conflict resolution strategy C Priority based C Time stamped Master slave Foreign Key Violation behavior Error Conflict C Ignore Cancel Priority based When you register a database you can give it a priority so that when conflicts occur the database with the higher priority number takes precedence If the source database has the higher precedence the conflicted row is over written on the target but if the target has the higher priority the conflicted row is preserved in the target and the replicated row is queued for manual conflict resolution 2013 IBPhoenix Editors 82 IBP Replicator 4 1 Time stamped The more recent of the conflicting rows is preserved This strategy requires the presence of matching timestamp fields in both source and target rows Master slave The source database s row always replaces the conflicting row in the target Conflicts that cannot be resolved directly by the conflict resolution strategy are logged for manual intervention using the Conflicts tool Foreign Key Violation behavior The default behaviour when the Replicator encounters a Foreign Key Violation is to log an error in the replication log and abort the replication You can configure different behaviour Conflict Treat it as a conflict and write the replic
80. atabase that are to receive data from each particular source object e the rules for running the replications As a replication schema is defined the Replication Manager stores its details in a configuration database Once a schema s outline is defined you tell the Replication Manager to create system objects in the specified source database s and the schema is completed System Objects System Objects can be regarded as the metadata of a replication schema They comprise triggers and tables that ensure that for each changed row in the source database the table identifier primary key and the action insert update delete are logged The logic of the triggers handles new updated or deleted data created on the local source database and if applicable incoming data from other databases that are replicating back to the local database The log table forms a queue of committed work waiting to be replicated As an insert update or delete takes place on a specified table or set a trigger fires to write information to a log table when the transaction is committed It is this underlying mechanism that prevents information from being replicated before it is committed in the source database no commit no log entry no replication Executing Replication The replication server can receive the instruction to replicate from these sources e the internal scheduler e an explicit request to replicate e in response to an event Sequence of even
81. ate only type is not supported there Clock Synchronisation Don t overlook the need to implement mechanisms to synchronise the system clocks of the source and target computers and where necessary to adjust for time zone differences Physical Distribution Considerations The general purpose of replication is to ensure that changes made to a source database are duplicated to another database so that the target database contains the same data as the source Although the source and target databases can be on the same system they are usually spread around a local network or distributed across a wider network Distribution Conditions Replication can be organised to distribute data to meet distribution needs in a virtually infinite variety of ways One way Replication In one way replication one database is always the source In physical terms its targets receive data that they do not overwrite append to or delete Replication refreshes the content of the targets without further modifying the source database N way Replication Multi master An n way replication scheme also known as multi master replication involves databases that act as both a source and a target to other databases One form of n way replication is where two databases replicate back and forth to each other The n can be more than 2 since reciprocal replication schemes often involve schemas where the same databases can be sources and targets to a number of ot
82. ation database Trying to run multiple instances of replserver against the same configuration database will have unpredictable results 8 2 3 Loading Licences Manually Installing Licences for a Linux Host If you are already using a Windows client or a Wine server to run Replication Manager for configuring your replications this section need not apply In the event that you have created or restored your configuration database on a Linux server and you don t have the Windows Replication Manager connected you can install your licences manually using the command line configuration editor cfged In a graphics terminal go to the directory where the Replicator executables are installed and start cfged Open the text email attachment file that contains your licences in a text editor Note the licence ID e g REPL 99 in our example and start the ADD LICENSE command as indicated in the screenshot Type a backslash followed by a Return to get a 2013 IBPhoenix Editors 98 IBP Replicator 4 1 8 3 continuation prompt Copy the license key to your clipboard application and paste it beside the gt continuation prompt me tp43 cfged IBPhoenix Repli cator version 4 1 0 Root directory is opt IBPhoenix Replicator gt REPLCFG gt ADD LICENSE REPL 999 a8 8gf U26 d2 EKATX 3EUDNXj_199W CEL e PYSUO4SgUhVH 740XA1 dW Hb 7 8i1K E WFU1N 4g5F7Cn78V HdH7D HQo m 05V CdAUY
83. ation record to the manual log table Ignore Skip over the offending record without logging anything i You can override the foreign key violation behaviour for specific tables in specific schemas For information see the topic Foreign key violation behavior in Table Settings Event Logging IBPReplicator Global settings amp m Settings Event logging Error Notification Log to window level E 3 Information 0 No log Log to file level 1 Errors only Infomation y 2 Warnings and detailed errors description Ronis 4 Detailed information isi 5 Debug REPLICATE LOG Browse Each configuration database can have its own error information logging settings and log file Allowing IBP Replicator to record its activity in either a window and or on a log file on disk The user defines what is written level and where logs are written The logging levels are 0 No Logging 1 Errors Only 2 Warnings and Detailed Error Description 3 Information 4 Detailed Information 2013 IBPhoenix Editors Chapter 7 Defining a Replication Schema 83 5 Debug Logs can be written to a disk file in either the default path which depends on platform and run mode or in a different one which you you specify The default log file named Replicate log is placed as follows Q Linux in var log if Replicator is running in daemon mode in the cur
84. ations 49 Override log file per target 58 _p Password for source database 50 Password for target database 55 Peer to peer 20 123 Planning for replication 20 Primary keys 24 69 Primary keys distributed 24 Priority 35 R RAS parameters 38 Registered database 50 55 Registering a database 12 Registering databases 13 33 Remote Access RAS 38 Remote access parameters 33 Remote configuration to access 98 REMOVE DATA FIELD cfged 159 REMOVE DATABASE cfged 153 REMOVE LICENSE cfged 150 REMOVE SCHEDULE cfged 167 REMOVE SCHEMA cfged 155 REMOVE SEQUENCE cfged 162 REMOVE SYSTEM OBJECTS cfged 166 REMOVE TABLE cfged 165 REMOVE TARGET cfged 157 REPL user 123 Replicant 12 Replicant definition of 13 Replication 12 Replication Monitor tool 99 Replication order 49 Replication Scheduler tool 101 Replication schema defining 16 Replication scheme 20 Replication scheme Cascade 20 Replication scheme Central to branch 20 Replication scheme Central to standby 20 Replication scheme Hub and spoke 20 Replication scheme Peer to peer 20 Replication tree 46 Replication ad hoc 101 Replication asynchronous 13 2013 IBPhoenix Editors Index 177 Replication bi directional 123 Replication controling 85 Replication executing 16 Replication heterogeneous 26 Replication intervals 80 Replication managed 101 Replication managing 85 Replication n way 2
85. be A SEPARATOR lt separator character code gt Use this if you need to change the character that will be used in the replication log table to separate the segments of multi segment keys in the text representation of records changed By default the value is 9 indicating ASCII decimal 9 TAB Don t change this unless there is real reason to do so ORDER number This parameter enables you to set the order of multiple schemas in your configuration corresponding to moving them up and down in the Replication Manager program view topic MODIFY SCHEMA Use to modify a replication schema Parameters and arguments follow the same rules as ADD SCHEMA above Syntax MODIFY SCHEMA lt schema name or number gt SET lt schema parameters gt E If the schema number or name is omitted the current schema is modified REMOVE SCHEMA Use to remove a replication schema from a configuration Syntax REMOVE SCHEMA lt schema number or name gt SILENTLY If SILENTLY is used any warnings about possible failures during the removal of the schema are suppressed SHOW SCHEMA Shows information about the schema If the schema number or name is omitted the 2013 IBPhoenix Editors 156 IBP Replicator 4 1 information about the current schema is displayed Syntax SHOW SCHEMA lt schema number or name gt SHOW SCHEMAS Lists all of the schemas in the configuration No p
86. ble Syntax CREATE SYSTEM OBJECTS FOR SCHEMA schema number or name gt TARGET target db number or name gt TABLE lt target table number or name gt SILENTLY Parameters FOR SCHEMA lt schema number or name gt Use this parameter if the schema is not the current one or if you are not sure The keyword FOR is optional TARGET lt target db number or name gt Use this parameter if the target database is not the only target database The keyword TARGET is optional TABLE lt target table number or name gt optionally create system objects for just a specified table If this parameter is omitted system objects will be created for all tables If TABLE is specified with no argument system objects will not be created If SILENTLY is used pending replications and conflicts are removed instead of showing an error REMOVE SYSTEM OBJECTS Use to remove a system object or all system objects for a given configuration On completion all pending replications and unresolved conflicts for the specified part of the schema are dropped Syntax REMOVE SYSTEM OBJECTS FOR SCHEMA lt schema number or name gt TARGET lt target db number or name gt TABLE lt target table number or name gt Parameters FOR SCHEMA lt schema number or name gt Use this parameter if the schema is not the current one or if you are not sur
87. cation Tools Help E86 eo Hh i 9 osls mulm mu amp Source Database i icati Target Database You can change other attributes of registered databases too If you change the path of a database don t forget to test the connection before clicking OK to save the changes Source Database If you want to edit some characteristics of the source database with respect to the schema or just check those characteristics expand the schema node right click the named node beneath the Source database node and select Edit 2013 IBPhoenix Editors 52 IBP Replicator 4 1 File Configuration View Database Replication Tools Help 165 51 Y Defined Replication Schemata My Target 1 B E My Initial Schema B gt Source database E iod Edit Create meus eum Remove System Objects View conflicts Descriptive name My Source The Edit dialog that appears contains the characteristics spread across three tabs IBPRepkicator Schema settings Poco Connection Settings Event lagging Registered database My Source Replication username REPL Replication password i pues Replication role REPL_ADMIN Test connection Connection Tab The first tab of the dialog shows the database that will be the source of your replication Registered database Because there can be only one source database for a replication
88. cation by a repeating or Once only schedule as a one off in a Replication Manager session through the Tools menu 2013 IBPhoenix Editors Chapter 9 Advanced Topics 131 Ei File Configuration View Database Replication MIE Help E 8i O Hh il Reload parameters Ctrl P Replicate now Ctri R My Source B Shutdown Sever Ctrl U amp My Target 1 Schema view E offline License Manager 8 My Source B Target databases For off line replication 9 1 Replicated tables and procedures Highest Replicated sequences Inbound folder E SCustomersN BP files ir Dutbound folder E CustomersNBP files c Use metadata from My Source Descriptive name Offline Instruct the server to replicate immediately in Windows as a one off or scheduled operation from the Replicator application interface replserver exe Replication Server File Options Help ls l o infig Type Firebird Config Database e Customers BP databases replctg fdb Running the Replication Now the replication is ready to go just like a normal 2 tier replication You can verify it by checking the Outbound directory and the replication log In the Outbound directory a fresh file is created for each replication cycle The file names are of the form Rxxxxxxxx dat where the x s
89. cator no configuration opened New configuration a Open configuration F Exit Alt X Some previous config My Replication Config If a default configuration database is currently assigned it appears in bold face You can change the default one by selecting a different one from the list Select the configuration database you want to be the default and click to open it Now select Configuration from the menu and simply click on Set as Default f IBPReplicator My Replication Config gt File 778 View Database Repl 2 Set as default ut Current Schema No So amp Target Database Next Your next step will be to create the Schema for your replication However you may wish to look over the default settings first and decide whether you want to customise the options Creating the Schema A replication schema contains information about what should be replicated from where to where For the purposes of this help document we ll assume that you are working through the steps previously described and are creating your first schema However you can define multiple schemata for multiple replications that are to be cycled through in order Typically you would already have registered databases defaults etc already defined and would wish to pick up definitions from some level of the tree to 2013 IBPhoenix Editors Chapter 7 Defining a Replication Schema 47
90. d only if a different character has to be used for the key of this table than the one defined for the schema for some reason KEEP STATS boolean value Set True to enable the GUI performance monitor tool By default it is disabled for all tables to reduce performance overhead by allowing replserver to work with read only access to the tables in the configuration database Omit this parameter unless you want to set it True immediately It can be enabled later using MODIFY TABLE ORDER number Use this parameter if you want the table to occupy a specific position within the replication order e g to precede other tables that have foreign key dependencies on it You can use SHOW TABLES SCHEMA n to view the order of tables already defined lt You may wish to omit this parameter and defer changing the order of the tables C until you have finished defining them all A unique number will be auto generated if you don t set it here explicitly OPERATIONS lt replicated operations list gt A string value containing the letters U D for inserts updates and deletes respectively By default all operations are replicated so if this is the behaviour you want you can ignore this parameter Use this parameter to disable replication of a specific operation by providing the list with only the desired operations You can use MODIFY TABLE later to alter the set of desired operations CRS strategy number DEFAULT
91. defines the type of action required insert U update D delete Output Argument Provide an integer RETURNS argument that indicates the result of the action Possible return values are 0 Success If the stored procedure handles conflicts itself e g by converting an insert into an update on a key violation the procedure should also return 0 1 Unresolvable conflict The record is moved to MANUAL LOC 2 Fatal error The replication will not proceed A Simplistic Example The example here is simplistic and should not be used as a boilerplate that would cover your requirements Refer to the comments at the end of this topic if the reasons for that are not obvious The source database contains the following table definition CREATE TABLE T K1 INTEGER NOT NULL K2 VARCHAR 10 NOT NULL 2013 IBPhoenix Editors 122 IBP Replicator 4 1 3 DATE NOT NULL F1 VARCHAR 20 F2 DOUBLE PRECISION F3 INTEGER F4 VARCHAR 100 F5 NUMERIC 4 1 F6 NUMERIC 9 2 F7 NUMERIC 15 2 PRIMARY KEY K1 K2 K3 A stored procedure can then be defined on a target database with the same structure as the source table as follows CREATE PROCEDURE REPLICATE T 1l NEW INTEGER 2 NEW VARCHAR 10 3 NEW DATE F1 VARCHAR 20 F DOUBLE PRECISION F3 INTEGER F4 VARCHAR 100 ERIC 4 1 ERIC 9 2 ERIC 15 2 INTEGER VARCHAR 10 3 DATE ACTION_TYPE CHAR 1 RETURNS RESULT SMALLINT
92. des for opening and closing configuration databases and for dropping deleting 2013 IBPhoenix Editors 32 IBP Replicator 4 1 them When you are ready to create your configuration database just click the Create button and you re done Using an Existing Database It is possible to store a replication configuration in an existing database specifically the source database for an event triggered replication For this use the Open configuration dialog from the File menu i IBPReplicator no configuration opened Arie View Help 2 New configuration Open configuration N F Exit Alt X You will get a dialog almost exactly like the one for creating the regular configuration database Fill in the fields to access the database remembering to include a valid username and password and submit it You might like to include a useful nickname for the configuration in the Comment field e g Synch Checkouts might be appropriate for a replication that is to be used to keep point of sale terminals in synch with a Sales database You will be asked if you want to make it into a configuration database 2 IBPReplicator question This is not a configuration database Click Yes to convert it now or No WEB to exit and start again vo For Oracle the message may differ slightly but the same question is implicit Click Yes to have the program create the replication metadat
93. ds and no longer comes with the separate replication manager script The tarball installation can be unpacked directly to the correct file system locations The replserver executable can run as a service under chkconfig control or can be run as an application or service directly from the command line For details please refer to the topic Linux Operation Improvements Command line Configuration Editor The new command line configuration editor cfged provides the means to configure and modify replication details on either Linux or Windows without a graphical user interface Besides providing the administrator with a quick way to make small changes it also gives Linux administrators the option of accessing all of the configuration utilities without requiring a Windows box The configuration editor can be run interactively or as single commands from a command shell Single commands can also be batched into scripts The program includes a command to extract an entire configuration as a script simplifying the cloning of replications for multi target scenarios Simplified Windows for Replication Manager The main window of Replication Manager has been streamlined to reduce steps and improve workflow Drag and drop can be used to shorten the definition of registered databases into the schema tree Display and behaviour of icons in toolbars have been improved In the data windows missing keys are highlighted Enhancements to the mapping window i
94. e The keyword FOR is optional 2013 IBPhoenix Editors Appendices 167 TARGET lt target db number or name gt Use this parameter if the target database is not the only target database The keyword TARGET is optional TABLE lt target table number or name gt optionally remove system objects for just a specified table If this parameter is omitted all system objects for the schema will be removed If TABLE is specified with no argument no system objects will be removed Working with the Replication Schedule ADD SCHEDULE Add a schedule item Syntax ADD SCHEDULE NUMBER lt item number gt schedule item ENABLED DISABLED lt schedule item gt ONCE lt date gt lt time gt PERIODICALLY EVERY lt period gt SECONDS HOURLY AT lt minute number gt MINUTE DAILY lt time gt WEEKDAYS lt time gt WEEKLY lt week day gt lt time gt MONTHLY lt day of month gt lt time gt Anew schedule is enabled by default Include DISABLED if you just want to add the schedule item without enabling it Argument Formats Date US format MM DD YYYY Time HH MM SS Week day may be in numeric 1 Monday 7 Sunday or in literal form MODIFY SCHEDULE Use to modify an item in the replication schedule Parameters and arguments follow the same rules as ADD SCHEDULE above Syntax
95. e in a target database to accept replication parameters from the source database Complex Schemas summarises some more complex replication models and works through an example of n way replication using the Hub and Spoke model Schema Numbering In many replication environments it is possible to have the same database being referred to as source database in more than one schema Each schema configuration will cause its own system objects to be created in the source database Unless precautions are taken the identifiers of SOs for one schema could conflict with those for another Each schema that is created in a configuration database is referred to by an internal number This number is used in the naming of triggers etc when the System Objects are created The following screenshots from a graphical DB browser tool illustrate how the numbering is set automatically In this shot we are looking at the configuration database for the replication used in this manual 1 mq Relations Procedures Domains Generators Exceptions UDFs MON TRANSACTIONS Tables System Inf REPLSCONFIG M Views Domainlnf amp e idi REPL DATABASES REPL DATAFIELDS Fields Data Indexes Constraints Triggers Source Desc Depend Field REPL KEYFIELDS REPL KEYWORDS REPL LICENSES REPL RELATIONS REPL SCHEDULE REPL SCHEMATA REPL SEQUENCES REPL SUBSCRIBEDDB NAME PUBDBNO DISABLED
96. e such file for each conflict which will be listed by the Conflict Resolution tool if it is invoked on the database that is defined as the offline replication source Conflict files are written during the up replication as each conflict occurs Since the data in the conflict files is not under transaction control a rollback of the replication does not delete any conflict files that were created before the rollback Thus careful management of these files is needed to avoid accidentally processing the same conflicts more than once s s 1 Manual conflict resolution arge E Hep gt replications EMBER PERS EMBER PERS EMBER PERS EMBER PERS EMBER PERS M EMBER PERS Delete all records EMBER PERS O nsen IMIEIIDET riedsuri rs mEMBER PERS Insert MEMBER failed Reason FK MEMBER PERS Insert MEMBER failed Reason FK MEMBER PERS Insert MEMBER failed Reason FK MEMBER PERS Insert MEMBER failed Reason FK MEMBER PERS Insert MF MRFR failed Reason Source database Inbound 2013 IBPhoenix Editors 134 IBP Replicator 4 1 9 6 4 Off line Synchronization Synchronization allows the IBP Replicator to get the source and target tables into the state where data matches in both i e a one time global replication It is possible to perform an asymmetric synchronization off line How Off line Synchronizatio
97. e the SYSDBA or that of an Administrator of the operating system The default user provided in the dialog is REPL which can be used with a suitable role for any replication and must be used if you plan to implement bi directional or n way replication Settings Tab IBPReplicator Target database settings Connection Settings Event logging Periodic commit Periodic commit after records Row level replication condition sITE 10 100 Periodic commit Ordinarily IBP Replicator commits changes once per replication after all the logged changes have been successfully replicated to the target database If a network error occurs during replication all of the changes will be rolled back and IBP Replicator will try again If the network connection is unreliable or the number of changes to be replicated is large you can specify for changes to be committed periodically as the replication proceeds 2013 IBPhoenix Editors 58 IBP Replicator 4 1 In the field labelled Periodic commit after records set a positive value representing the number of successfully replicated rows that IBP Replicator is to group and commit together CAVEAT Don t implement this option unless it is actually necessary It can impact the general performance of the database over time and breaking a replication into numerous separate transactions breaks the overall atomicity of a replication If the conditions a
98. each synch file is the same as that used for the replication dat file If the synch extension on these files is renamed to dat the Replicator can process them as 2013 IBPhoenix Editors Chapter 9 Advanced Topics 133 an off line replication Gotchas An original Rnnnnn dat file is the output from processing all of the specified tables in the order specified when the replication was defined However offline replication does not respect the order in which tables were defined the replicator service simply starts at the beginning of the directory and works its way through it in alphabetical order deleting each file as it finishes with it The architectural layout of a set of renamed synch files in a filesystem directory is obviously quite different to the internal architecture of an offline replication file When the replication service processes a set of files it has no way to know either which tables it is processing or what is the correct dependency order If you need the files to be processed in a specific order you also need to rename the main part of each file name so that their alphabetical order reflects their dependency order Manual Conflict Resolution After Off line Replication It is possible to perform a manual conflict resolution following an inbound replication from a Files type database Conflicts are stored in files with the suffix conflict in the inbound directory There will be on
99. earrange the table order 2013 IBPhoenix Editors 138 IBP Replicator 4 1 2013 IBPhoenix Editors Chapter 1 Appendices 140 IBP Replicator 4 1 Appendices 10 1 Appendix I Supported Data Types and Compatibilites Table 1 Interbase Firebird Destination types Source types z 5 E T x pp smn varcHar x x x x X e Ix x xx 1 No datatype or dimension transformation Total size of data must fit available RAM 2 In Interbase only 3 Segmented BLOBs only Streamed BLOBs are transformed to segmented 2013 IBPhoenix Editors Appendices 141 Table 2 Oracle Destination types INTERVAL DAY TO SECOND INTERVAL YEAR TO MONTH TIMESTAMP WITH LOCAL TZ TIMESTAMP WITH TIME ZONE a 2 gt H al ES 1 e e 2013 IBPhoenix Editors 142 IBP Replicator 4 1 Table 3 Interbase Firebird Oracle Destination types SECOND INTERVAL YEAR LOCAL TZ TIMESTAMP WITH TIME ZONE TO MONTH VARCHAR2 NUMBER TIMESTAMP WITH INTERVAL DAY TO ARRAY BOOLEAN BLOB CHAR DATE DECIMAL DOUBLE PRECISION FLOAT INTEGER fi i i pos fafi fi i jeha faf etos xfi JEJEJE S E a SSS Sass ES ERES SS tnn SSS SENE ER ERES BSEC
100. ed Conflict treats the violation as a conflict that will be resolved according to the resolution strategy applicable to the table Ignore the offending record will not be replicated SHOW GLOBAL Shows the global settings It takes no parameters Syntax SHOW GLOBAL 2013 IBPhoenix Editors 170 IBP Replicator 4 1 10 3 SIGNAL SERVER Sends a notification to the replication server to perform the specified action The action parameter REPLICATION RELOAD EXIT is mandatory Syntax SIGNAL SERVER TO REPLICATE RELOAD EXIT The keywords SERVER and TO are optional Appendix Ill Version Notes Replication Server 4 1 IMPORTANT The configuration database structure in version 4 and higher releases of this software is not compatible with those of previous releases Please take copies of your configuration databases before installing The newer Replication Manager will automatically upgrade old configuration databases on opening If the configuration editor cfged is used executing the command UPGRADE will achieve the same thing Changes to Note When Upgrading Existing IBPhoenix Replicator V 3 licences are valid for V 4 and will be preserved Licences from versions prior to V 3 are not valid for Replicator 4 and will be removed from the configuration altogether If you are upgrading from 2 1 or lower versions you will find that the Replication schedu
101. ed if more than one table is replicated in the schema MODIFY DATA FIELD Use to modify data field definitions Syntax MODIFY DATA FIELD target field name or number OF SCHEMA schema number or name TARGET target db number or name TABLE table number or target table name SET field parameters The parameters for SET in this command follow the same rules as for ADD DATA above REMOVE DATA FIELD Use to remove a non key data field from a list of replicated fields in a record The parameters and arguments follow the same rules as for ADD DATA and MODIFY DATA FIELD above Syntax REMOVE DATA FIELD field number or name OF SCHEMA schema number or name TARGET target db number or name TABLE target table number or name 2013 IBPhoenix Editors 160 IBP Replicator 4 1 P Key fields cannot be removed with this command The entire table must be N removed to undefine a key field SHOW FIELDS Lists the replicated fields for the specified target database and table in the specified schema Syntax SHOW FIELDS OF SCHEMA schema number or name TARGET target db number or name TABLE target table SP number or name All parameters must be specified The keyword OF is optional gt N The keywords SCHEMA TARGET and TABLE are optional but if any keyword is omitted the par
102. ed replication Delete Delete the selected conflict Data in source and target tables will stay as record they are Delete If you want to delete groups of conflict records select those you want selected deleted This will enable the button ready for you to click it to have the records conflict records abandoned Delete all Delete all the conflicts Data in source and target tables will stay as they records are After an option is executed the record in the manual log will be deleted and the conflict will disappear from the display considered to have been resolved Finally the view reports the all clear and you can close it Off line Replication It is possible to perform manual conflict resolution following an off line upward replication from a Files type database Instead of being written to the manual log table the conflicts are written to conflict files in the inbound directory that was used as the source database The resolution options are limited to Force All Replications and Delete all records For more information refer to the topic Manual Conflict Resolution After Off line Replication in the next chapter License Manager About Licensing Evaluation Licence No specific restrictions are placed on the distribution of the Evaluation version except for the following Once entered the evaluation licence lasts for a period of 14 days The evaluation licence is limited to one server and four replicant licence
103. enabled Any that you want to keep for alternative or occasional use can be disabled by deselecting Enabled on the final window Disabled schedules appear as greyed out in the list 2013 IBPhoenix Editors 104 IBP Replicator 4 1 Replication Schedule Options Help 718 9 Scheduler enabled Beep when Replicate Replication schedule Frequency Periodically Once Every hour Every hour at 30th minute Add or Delete Replication Schedules ix Replication Schedule a Delete Ctrl Del Reload Me F5 Frequency Every hour at 30th mu On Monday August 2 Loading and reloading the Scheduler gt Check on Scheduler enabled In future you can select a schedule item in the list and use Options gt Edit to change the parameters including enabling or disabling the item 6 gt If you want to hear an audible signal when a replication starts also check on Beep when Replicate gt To update the Scheduler and replace any schedule that is currently in effect select Reload Schedule from the Options menu press F5 or click the Reload Schedule button on the toolbar 2013 IBPhoenix Editors Chapter 8 Managing Replication 105 pu x Replication Schedule _ w w ee Options Help v Scheduler Every hour at Altering the Scheduling Schedules can be added
104. ents Priority Inbound folder Outbound folder Use metadata from Highest Test connection OK Cancel These fields refer only to off line replication For more information see the advanced topic Offline Replication and Synchronization in Chapter 9 Use metadata from You first need to have registered a database whose table definitions will be used to determine the format of data to be replicated off line When you focus in this field the descriptive names of registered databases will be available to select from Inbound folder the full path to the folder where replicated data in off line files will be received Outbound folder the full path to the folder where replicated data in files will be written for subsequent transfer by external means Checking the Connection 2013 IBPhoenix Editors 40 IBP Replicator 4 1 When you have defined the database test the connection to make sure that you have input the details correctly You can do this before saving the current parameters Click on the button in the registration pane or click the e button on the toolbar If all is well you should see this message IBPReplicator Information If the connection attempt fails check and correct the parameters until the connection test succeeds Registering the Database Finally to register the database just click the OK button The newly registered database s descriptive n
105. eplicating or to do a one off replication if the Timer button is off Managing the Server Once the server is running you can stop and restart it How you do so depends on whether it is running as an application or a service 2013 IBPhoenix Editors Chapier 8 Managing Replication 89 To stop the server when it is running as a service Either gt Method 1 Open the Replication Manager and connect to the appropriate configuration database Execute from the Menu Replication Tools Notify Server Shutdown Server or press Ctrl U For InterBase or Firebird the events mechanism must be working gt Method 2 Stop the service from the Services applet in the Administration Tools Note also that you can stop and restart the service from the Services applet by choosing Restart To stop the server when it is running as an application Simply close Exit the application You can do this either gt from the menu of the graphical interface program or gt by selecting it in the Windows Task Manager list and clicking End Task 8 1 1 Command Line Operation The server program on Windows ReplServer exe can be run as an application from the command line using option switches Program Switches for ReplServer exe The default is for it to run asa service recommended if available However you can run a non default replication as an application whenever needed It is probably a good idea to avoid running two rep
106. eplication There are two types gt asymmetric where the target table is synchronized from the source table The target table becomes an exact copy of the source table with IBP Replicator performing all the necessary inserts and deletes The source database for an asymmetric synchronization can be a suite of files previously off loaded to a Files target database This off line asymmetric synchronization is described in more detail in a later chapter symmetric which does not perform any deletes but instead inserts any records missing on the target from the source and vice versa It also performs updates according to the current conflict resolution strategy Synchronization is not replication It is a one time operation that can be run for a new or modified schema Customising the Order of Tables It is not necessary to synchronize tables one by one to avoid the dependency conflicts that could occur when a bulk operation follows the default alphabetical order that accords with the system tables You can define your own order for the synchronization to avoid these conflicts and then perform the synchronization for all tables in one hit 2013 IBPhoenix Editors Chapter 7 Defining a Replication Schema 75 You won t be able to perform this customisation if you have the interface explicitly set up to order the objects alphabetically Before you start you will r need to use the View gt Tables order opt
107. ermination for National Character columns in Oracle It appears Oracle does not currently provide a way to determine the maximum size in bytes for characters in character sets other than the main one Replicator therefore ignores the value of the Oracle environment variable NLS NCHAR and takes the maximum byte length values for columns defined as NVARCHAR2 NCHAR or NCLOB from the main character set as defined by NLS LANG 2013 IBPhoenix Editors 174 IBP Replicator 4 1 Index conflict files 106 132 synch files 134 A Access existing configurations 98 ADD DATA cfged 158 ADD DATABASE cfged 151 ADD KEY cfged 160 ADD LICENCE cfged 150 ADD SCHEDULE cfged 167 ADD SCHEMA cfged 153 ADD SEQUENCE cfged 161 ADD TABLE cfged 162 ADD TARGET cfged 156 Administrative Role 33 38 Architecture of IBReplicator 12 Asynchronous replication 13 Autogenerate mappings 65 _B Benefits of IBReplicator 9 Bi directional 123 Bulk mapping of tables 65 Byte length determination in Oracle DBs 173 Ox Cascade 20 Central to branch 20 Central to standby 20 cfged configuration editor 144 cfged Commands 146 cfged Common Rules 145 cfged Customising Global Settings 168 cfged Database Registration 151 cfged On Line Help 146 cfged Program Settings 147 cfged Starting 144 cfged Where Am 1 147 cfged Working with Configurations 148 cfged Working with Data F
108. error causes cfged to terminate if an error occurs It is equivalent to the SET BAIL command in interactive mode By default bail on error is OFF e ON OFF controls command echo It is equivalent to SET ECHO in interactive mode By default command echo is ON h lt command gt ALL displays terse or detailed documentation It is equivalent to HELP in interactive mode q be quiet instructs cfged to execute without returning output or errors to the console Commands The cfged application has a command vocabulary consisting of keywords for a number of verbs and operands and parameters All commands start with a verb Some verbs are self contained while others require objects parameters or both 4 The and lt gt symbols that appear in the Syntax sections are not syntactic elements On line Help HELP Use HELP to display the cfged on line documentation Syntax 2013 IBPhoenix Editors Appendices 147 HELP lt command gt ALL Used alone HELP displays some usage notes and a list of the available commands HELP lt command gt gives detailed help for the requested command HELP ALL gives detailed help for all of the commands in alphabetical order Equivalent switches h amp The equivalent switches when passed from the command shell are h and Where Am I SHOW CURRENT Shows the numbers of the current database schema target database and table It takes no par
109. ers The first represents the major release number e g 3 the second the sub release number and the third if present identifies it as a patch release The installer program may be compressed in Winzip format and distributed as an archive named IBPReplicatorSetup n n n Win32 zip Decompress the archive into a temporary location of your choice using your favourite decompression tool WinZip 7Zip WinRAR etc Ca To install IBP Replicator to your hard disk double click the IBPReplicatorSetup n n n Win32 exe file s icon in its directory Follow the dialogs as the installer runs providing a custom root location for the software if you don t want the defaults Once the installer has finished close it If instructed to do so close down any applications you have running and reboot the machine Start Menu Shortcuts The installer program should have installed these shortcuts for you d HyperSnap 6 elp and Suppo k IBPReplicator R a Replication Server y Libre Office 3 5 As a quick summary here is what each of the shortcuts takes you to 2013 IBPhoenix Editors 30 IBP Replicator 4 1 6 1 Configuration Database Starts the Replicator Server as an application Used when running a replication R Starts the Replication Manager console program See the next topic First c that is not the default one First Configuration Database The Replication Server will use the co
110. es about 41 Licensing about 41 Limbo transactions 16 Linux operation 91 Linux controlling replserver processes 93 Linux installing and configuring 92 Local protocol 30 Log file override 58 Logging 80 M Managing replication 85 Manual conflict resolution after offline replication 132 176 IBP Replicator 4 1 Mapping tables bulk 60 Mapping tables heterogeneous 60 Mapping tables removing mappings 60 Mapping with stored procedures 121 Metadata changes 119 MODIFY DATA FIELD cfged 159 MODIFY DATABASE cfged 152 MODIFY GLOBAL cfged 168 MODIFY KEY cfged 161 MODIFY SCHEDULE cfged 167 MODIFY SCHEMA cfged 155 MODIFY SEQUENCE cfged 162 MODIFY TABLE cfged 165 MODIFY TARGET cfged 157 Monitor tool 99 Monitoring 72 N Named Pipes protocol 30 NetBEUI protocol 30 Network protocol IPX SPX 30 Network protocol local 30 Network protocol Named Pipes 30 Network protocol NetBEUI 30 Network protocol TCP IP 30 Notify Server utility 105 N way replication 26 Offline replication 127 Offline replication from inbound files 132 Offline replication using synch file sets 132 Offline replication running 130 Offline replication schema 129 Off line synchronization 134 One way replication 26 OPEN cfged 144 Operations to replicate 74 Operations Linux 91 Operations Windows 85 Oracle byte length determination 173 Ordering of replic
111. es have fewer than 10 replication schemas defined so an easy rule would be to start each configuration database with values separated by 100 IMPORTANT When you do have multiple configuration databases use the command line switches with ReplServer exe replserver to set the one to use for a specified instance Metadata Changes Metadata changes performed after the creation of a replication schema are not propagated between the source and target databases by IBP Replicator you must take care of this by your own devices Replication schemata are not automatically updated to reflect changes in metadata Tips for Smooth Changes Prepare a DDL script to implement metadata changes in the source database and use the same script with modifications if necessary to update the target database s Ad hoc changes performed with interactive tools are prone to human error when duplicated in multiple locations Plan a down time window for the IBP Replicator service Enter the window by disabling the IBP Replicator service before you run the DDL script on the source Allow enough time in this window to apply the script to all affected databases test their effects and modify or replace all affected replication schemata It is strongly recommended that you use a tidy shutdown to remove all users including other administrative users from the affected systems while databases and replication configurations are being altered You might wis
112. ew Database Replication Tools Help 6lg8 55o tutsssisummuns eelAY My Source Defined Replication Schemata My Target 1 B E My Initial Schema El gt Source database i lt Target datab ER Create system objects N Remove System Objects View conflicts TIP You can create all of the system objects globally by using the main menu option If there are any problems for example missing primary key assignments you will see an error message and no system objects will be created in this operation Since each successful operation is committed previously created system objects will persist Correct the source of the current exception and try again If all goes well you should see the success message t Defined Replication Schemata B E My Initial Schema p Source database d y Source IBPReplicator Information o System objects were successfully created Creating System Objects from a Target Node You can also create the system objects when a target database node or even a target table is selected In that case system objects will be created in the source database for just that selected database or table if initiated from a table node Removing System Objects Select the source database in the Replication tree and double click on the Remove system objects icon to remove all the IBP Replicator defined system objects from a source 2013 IBPhoenix Editors 80 IBP Replicato
113. f available disk space Database Installation Both the Replication Server and the Manager require at least the appropriate client library for the database to be installed Installation and configuration will involve creating a configuration database so these activities must take place on a running instance of the database server Licensing There are two types of licence Server and Replicant Licences must be installed into the configuration database that you want used for your active replication a Server licence allows the Replicator application to run a Replicant licence allows a database to be accessed as a source or target 2013 IBPhoenix Editors Chapter 1 IBP Replicator Requirements 7 gt free evaluation licensing is included in the software supplying a minimal single Server licence and four Replicant licences They are valid for 14 days from the date the IBPhoenix Replicator software is installed Existing Licences Existing IBPhoenix Replicator V 3 licences are valid for V 4 and will be preserved Licences from versions prior to V 3 are not valid for Replicator 4 and will be removed from the configuration altogether There are more notes about licences in Chapter 6 About Licences Instructions for installing them can be found in the topic about the License Manager tool Chapter 5 describes some possible configuration models which may help to clarify the licensing requirements 2013
114. f existing registered databases use SHOW DATABASES CHARSET connection character set ORACLE If this parameter is not used or is empty the default character set from the environment variable NLS LANG is used COMMENT Quoted or bracketed passage of text containing anything you like PRIORITY database priority from 0 to 10 A higher number means higher priority KEEP CONNECTION whether to keep RAS connection after a database disconnect 2013 IBPhoenix Editors 152 IBP Replicator 4 1 KEY SIZE the size of the field in the log tables to store the values of the key field s USER administrative user name PASSWORD administrative user password RAS NAME the name of the RAS connection to dial before connect RAS PASSWORD the password for the RAS connection RAS USER the RAS connection user name SERVER the entire connection string including the host name and port number if applicable to the connection protocol Required TIME FIELD the name of the timestamp field for timestamp based conflict resolution strategy Parameters applicable to InterBase and Firebird only ROLE administrative role USE2PC use 2 phase commit for replication transaction InterBase only DIALECT SQL dialect for the connection Must be AUTO the default 3 or 1 Don t use this parameter unless there is a real reason to do so Don t use this parameter for Firebird databases Firebird selects t
115. form any cloning once you have defined most or all of the mappings for your base target Choosing Replicated Tables Replication is essentially a matter of identifying data changes in tables in the source database and writing the effects of those changes to tables in one or more target databases This step is the key one in defining your replication schema deciding which source tables you want to replicate in your target s It is probably stating the obvious to remind you that you do need to start out with both a source database and a target database that already have at least the relation objects you want to replicate defined in their database schemata Don t forget the two essential metadata attributes needed in tables you are going to be 2013 IBPhoenix Editors Chapter 7 Defining a Replication Schema 61 replicating from and to they must have compatible sets of unique columns and if you intend to use timestamping for conflict resolution both the source and target tables must have compatible TIMEFIELD columns that can be referred to for an age reference x IBPReplicator File Configuration View Database Replication Tools Help Ae 2 FOF CEE H OD amp DE Defined Replication Schemata My Target 1 Ei My Initial Schema D gt Source database Target databases 3j My Target 1 Replicated tables and procedures Define AutoGenerate View conf
116. g IBPhoenix Replicator V 3 licences are valid for V 4 and will be preserved Licences from versions prior to V 3 are not valid for Replicator 4 and will be removed from the configuration altogether 2013 IBPhoenix Editors 42 IBP Replicator 4 1 Licences Required Two types of licence are needed for replication Server and Replicant Licences must be installed into the configuration database that is to be used for your active replication gt a Server licence enables the Replicator application to run gt a Replicant licence allows a database to be accessed as a source or target Licenses are entered using the License Manager dialog which you access from the Tools Menu of Replication Manager As a rule of thumb you require one Replicator licence to run a replication server and one Replicant licence for each database that is a source or a target Replicator server and Replicant licences are bundled in denominations to suit your particular needs One Replicant licence is needed for each database that is involved including the Source database For example the minimum IBP Replicator configuration of one source database being replicated one way to one target database requires a single Server licence and two Replicant licences A Replication Server licence is bundled with one Replicant licence automatically For this version of Replicator the included Replicant licence is issued separately to facilitate its use
117. generated System Objects Use row level replication conditions to achieve the effects indicated in the examples Trigger sets created in the source database for London for each target would be modified by row level conditions to take the localised username into account when determining what to replicate CREATE TRIGGER REPL XYZ FOR ATABLE ACTIVE AFTER INSERT POSITION 32760 AS BEGIN IF USER lt gt REPL THEN row level condition USER lt gt REPL BEGIN IF USER REPL MAN THEN row level condition USER lt gt REPL MAN BEGIN INSERT INTO REPLSLOG VALUES END END END This logic can be tabulated as follows This ensures that data is replicated from one branch into the hub in London The hub then replicates this data to the other branches but not back to the originating branch Replication Schema Definition The defined replication schema for such a scenario would look something like this Manchester To London Source Database in Manchester UserName REPL Target Database in London UserName REPL MAN Birmingham To London Source Database in Birmingham UserName REPL Target Database in London UserName REPL BIR Leeds To London 2013 IBPhoenix Editors Chapter 9 Advanced Topics 127 Source Database in Leeds UserName REPL Target Database in London UserName REPL LEE London to the Rest Source Database in London UserName REPL Target Databases Manchester
118. h to archive the replication log file s before resuming services Put the database online and restart IBP Replicator once you are happy that the revision is complete Adding Timefields If you plan to use timestamping for as your replication conflict strategy you will need to add a Timefield column to every source and target table involved in the replication and write Before Insert or Update triggers for each table to perform the actual timestamping 2013 IBPhoenix Editors 120 IBP Replicator 4 1 For large databases this could be a very tedious and error prone task involving an extended period of downtime for the users at all of the replication sites However you can prepare a script ahead of time to speed up the task You can reduce the effort involved by defining and executing a stored procedure to generate the DDL and export the required statements into an external table Generating a Script Start by defining an external table in the database that the timefield value is going to be applied to create table ext data external file inject timestamps sql data char 90 character set NONE commit Our sample procedure takes as input the timefield identifier that we have set up for the configuration The generated script depends on all table names having lengths of 28 characters If you have any table names that are longer you will need to edit the script later to replace the trigger names in t
119. he installer will set everything up to run the service according to your preferences For running IBP Replicator as an application a graphical interface is available from the Start Menu to set up how you want it to run Some control aspects can also be run from the command shell either directly or in a bat file If you need to control IBP Replicator wholly in Linux only a command line interface is available currently for controlling the services 8 1 Windows Operation The Windows Executable The executable that provides the replication services on Windows is ReplServer exe It incorporates the scheduler Essentials Before the Replication Server Will Run Make sure that your configuration is in a sufficiently complete state that replication can occur your server and replicant licences are installed and that you have enough replicants to perform the configured replication s the source and target databases have the necessary permissions granted for the REPL user or if you are using a role e g REPL ADMIN as in our examples that the role has been created and the permissions granted And remember to grant the role to REPL you have set the default configuration database otherwise it won t be found and the server program will refuse to start for Firebird or InterBase sources and targets the respective servers are running Running IBP Replicator The replication server program can run on Windows as a service or as a
120. he correct a client dialect automatically Parameters specific to file INBOUND the name of inbound directory The directory must exist OUTBOUND the name of outbound directory The directory must exist STRUCTURE the number or descriptive name of the database to use as a source of metadata information If you want to look up the numbers and descriptive names of existing databases LN use SHOW DATABASES or SHOW SCHEMAS MODIFY DATABASE Modify database registration information Rules and parameters follow those for ADD DATABASE above If the database number or name is omitted the current database is modified 2013 IBPhoenix Editors Appendices 153 Syntax MODIFY DATABASE lt db number or name gt SET lt db params gt lt db params gt lt param name gt lt param value gt lt db params gt REMOVE DATABASE Remove the database registration info from a configuration All replication schemas that use this database will also be removed Syntax REMOVE DATABASE lt db number or name gt A System objects associated with the removed schemas will remain SHOW DATABASE Shows the registration information about databases Syntax SHOW DATABASE lt db number or name gt SHOW DATABASE without a parameter displays information about the current database SHOW DATABASE lt db number or name gt shows information about the specified database SHOW DATABASES Lists the names numbe
121. he corresponding keys or key like sets must be compatible Two phase Commit To ensure the integrity of the distributed replicated data and the consistency of database state on both sides the replicator makes use of the two phase commit feature of Firebird and InterBase transactions Two phase commit is analogous to a contract between both or all of the databases involved in a distributed transaction Each database commits its part of the transaction and waits for the other or others to signal that they have committed their part s before each proceeds to secure its own commit The replication is complete when the whole log has been processed and both or all sides of the transaction have completed the commit and verification phases of the commit The server deletes the rows from the the replication log queue when it has finished with them Because of the two phase commit any problem that arises while the queue is being processed causes an error That in turn prompts a rollback Hence the queue is always retrievable for a re run with the secure knowledge that the replication has either run through to a successful completion and emptied the queue or has failed as a whole and retained the queue Limbo Transactions Firebird and InterBase If a failure occurs during the two phase commit it is possible that you may get left with a limbo transaction That means that the pieces of work committed or rolled back by the 2013 IBPhoen
122. he generated script create procedure inject timestamps timefield id varchar 31 as declare variable tablename varchar 31 declare variable crlf char 2 declare variable data varchar 90 declare variable date_today varchar 24 begin crlf literally hit the Enter Return key between 2 apostrophes No spaces date today CAST CAST NOW AS TIMESTAMP AS VARCHAR 24 data One time script for applying Timefield metadata to tables insert into ext data data values data data crlf generated by procedure INJECT TIMESTAMPS date today insert into ext data data values data data crlf insert into ext data data values data data crlf SET TERM insert into ext data data values data for select RDBSRELATION NAME from RDBSRELATIONS where RDBSRELATION NAME not starting with RDBS and RDBSVIEW SOURCE IS NULL and RDBSRELATION NAME lt gt EXT DATA into tablename do begin data crlf ALTER TABLE tablename ADD timefield id TIMESTAMP insert into ext data data values data data crlf COMMIT insert into ext data data values data data crlf r insert into ext data data values data data crlf CREATE TRIGGER BI5 tablename FOR tablename insert into ext data data values data data crlf ACTIVE BEFORE INSERT OR UPDATE POSITION 5 insert into ext data da
123. hers Heterogenous Replication Source and target databases do not always have the same structure One may contain tables that don t exist in the other Tables may have different numbers of columns and different names for columns A source dataset may replicate different sets of data to different targets Any of these heterogeneous schemas is possible 2013 IBPhoenix Editors Chapter 5 Planning for Replication 27 5 4 Conflict Resolution Sometimes a replication server may find a problem in trying to replicate an update to a row that is either missing or has already been updated This is likely to show up in situations where the users of a target database are performing inserts deletes and updates without being aware that changes may be happening elsewhere in a source database Issues like this generate conflicts during replication Not all conflicts will be of the same type and different types of conflicts can be handled in various ways Each source and target pair of databases can have its own conflict resolution settings Handling Conflicts IBP Replicator provides three mechanisms for handling potential conflicts Priority based Resolution Databases can be given priorities The database with the higher priority number takes precedence For example if a source database has precedence conflicts are resolved as follows e An update finding no identical key record in the target database is converted into an inse
124. ields and Keys 158 cfged Working with Replicated Tables 162 cfged Working with Schemas 153 cfged Working with Sequences Generators 161 cfged Working with System Objects 166 cfged Working with Target Databases 156 cfged Working with the Schedule 167 Choosing replicated tables 60 Choosing source database 50 Choosing target database 55 CLEAR cfged 150 Command line configuration editor 144 Command line operation Linux 91 Command line operation Windows 89 Command line switches cfged 146 Command line switches Linux 94 Command line switches Linux 91 Command line switches Windows 89 Configuration database 30 Configuration database default 45 Configuration editor 144 Configuration default 45 Configure Foreign Key violation behaviour 80 Configuring Linux 92 Conflict resolution 27 Conflict resolution after offline replication 133 Conflict resolution master slave 27 Conflict resolution priority based 27 Conflict resolution setting default strategy 80 Conflict resolution timestamping 27 Conflict resolution timestamps for 24 Conflict viewer tool 106 Connection for source database 50 Connection for target database 55 Context menus 46 Controlling replication 85 CREATE CONFIGURATION cfged 148 Create schema 46 CREATE SYSTEM OBJECTS cfged 166 Customising table order 74 2013 IBPhoenix Editors Index 175 zs Database features supportfor 9 Database priority 35 Da
125. ill need to consider in designing your custom Replicator system Chapter 6 contains instructions for installing the pieces of your replication system on source and target servers In Chapter 7 you will find the details for defining a replication schema the rules Chapter 8 explains how to run and manage your replication server In Chapter 9 you will find a miscellany of topics concerning issues that will arise in more complex setups and how to deal with them The Version Notes at the end of this volume contain details of new features in Version 4 Known Issues and also important notes about sub releases that may affect you V 4 0 3 regarding byte length determination of national characters in Oracle databases Contents 3 Table of Contents Chapter 1 IBP Replicator Requirements 6 Chapter 2 Overview 9 Chapter 3 IBP Replicator Architecture 12 Terminology 13 Chapter 4 How IBP Replicator Works 16 Chapter 5 Planning for Replication 20 Choosing a Replication Scheme 20 Database Design Issues Q Q U u u u 24 Physical Distribution Considerations I I U uu uu 26 Conflict R solutions en An mn nn tte ne nn at ne ler tin ne 27 Chapter 6 Installation and Setup 29 First Configuration Database u uu 30 Registering Databases mms
126. inbound If your replications are going to be one way you will not need both The Outbound and Inbound directories can be any file system location to which the replserver process is allowed to write directly including a mountable network directory that is on line You can write to a removable storage device such as a flash drive or a media card When writing to mountable or removable storage devices it is your responsibility to ensure that the device is on line whenever it needs to be accessed which includes any time when you are configuring the pseudo database and that the device has enough available capacity for the file s that will be written 2013 IBPhoenix Editors 128 IBP Replicator 4 1 Register Directory as a Database In the examples that follow we will set up an Outbound offline replication Source database to file For setting up and Inbound replication file to Target database the procedure is similar Use a selection method to invoke the database registration tool Replication Tools B Edit L t2 Remove My Target 1 Test connection e Connected users count In the Database Type list choose File Decide on a friendly descriptive name for this pseudo database e g Offline Dutbound or whatever you like Fill in the fields defining the full paths to the inbound and or outbound folders and selecting the database fro
127. ion then type TIMEFIELDFORREPLICATION here The Time field name is where you name and map this column for the two tables Separator character Use this if the separator character for the elements of composite primary keys in an individual table need to be different from the global separator character Foreign key violation behavior If you want a foreign key violation to be treated differently for this relation than the method specified in Global Settings you can specify it here Initially the global setting is selected by default Choose an alternative behavior as follows Error causes an error to be written to the log and the record will not be 2013 IBPhoenix Editors 74 IBP Replicator 4 1 7 6 replicated Conflict treats the violation as a conflict that will be resolved according to the resolution strategy applicable to the table Ignore the offending record will not be replicated Default reverts the setting to the default behavior Replicated operations By default all operations insert update and delete will be replicated You can choose to exclude an operation by checking it off Comments Use this box for any free form documentation about the object that could be useful to you and others in future One time Synchronization Synchronization allows the IBP Replicator to get the source and target tables into the state where data matches in both i e a one time global r
128. ion Server suite is a graphical Windows based Replication Manager program for defining managing and monitoring the operations and for resolving replication issues Replicator connects to database servers directly through the client APIs No middleware or third party driver is used overhead is low and the system is small robust and fast Support for Database Features Replicator s replication can handle any data type supported by Firebird or InterBase including BLOBs and arrays columns defined using quote delimited reserved words as identifiers other SQL quote delimited identifiers multi segment primary keys international character sets Replication can be configured to respond to database events Replicator 4 is the first version that supports replication to or from databases other than Firebird or InterBase introducing support for Oracle 9 and higher Replicator Security Security provisions use the same mechanisms as those used to secure your normal databases User names and passwords that Replicator uses to connect to source and 2013 IBPhoenix Editors 10 IBP Replicator 4 1 target databases are stored in the regular server security structures of the respective server installations Benefits of Replicator Replication can enhance the usability of your system in a number of ways For example Data availability Work groups can have their own copy of a replicated database enabling them to fu
129. ion in the toolbar of the main display to switch to User defined ordering Select the Replicated Tables and Procedures node of the target database and select a table that you want to move Then click either the Up or the Down button in the toolbar to shift it up or down one position r i IBPReplicator File Configuration View Replication Tools Help 3 amp amp 8o SSS mms AY My Source i Defined Replication Schemata My Target 1 B E My Initial Schema B Source database My Source B Target databases My Target 1 70 Replicated tables and procedures xir ACCOUNT_UPDATE_LOG gt ACCOUNT_UPDA BANK ACCOUNT gt BANK ACCOUNT CORPORATION gt CORPORATION COUNTRY gt COUNTRY CURRENCY gt CURRENCY Firebird F TRANSACTION gt F TRANSACTION MEMBER MEMBER Descriptive name My Source 0 ifm MEMBER SER NUM gt MEMBER SER NI Comments The source database l Heo 8 1 MGROUP gt MGROUP ig PERIOD gt PERIOD I PERSON gt PERSON TRANSAC GROUP gt TRANSAC GROUP TRANSAC TYPE gt TRANSAC TYPE m E H E 8 E Friority Highest Key size 128 Use 2 phase commit True Server E Customers IBP datab A A A Administrative user name adm m Shift current object one position down In this example we want to move MEMBER down because it has dependencies on nearly all of the other tables F
130. ique or primary key However unique identification in the absence of keys is sufficient Refer to the Appendix Supported Data Types and their Compatibilities for information about matching columns with non identical data types The Create System Objects function generates potentially three kinds of triggers insert update and or delete triggers to track changes that are made to the database tables Changes are recorded in the Log Table The Log Table stores the key information on all the changes that have been made to the tables in the source database The Manual Conflict Resolution Log contains a list of operations from the Log Table that were not successfully replicated because of a data conflict problem and now require manual user intervention to correct the problem 2013 IBPhoenix Editors Chapter 3 IBP Replicator Architecture 13 3 1 Terminology Source database When we talk about the source database we refer to the database containing the master version of data that is intended to be copied to one or more other databases Target database A target database is one that that receives changes to the contents of its tables inserts updates and deletions from a source database generally on a regular basis Replication Replication is the process of passing newer versions of table data from a source to a target database thus replaying changes that have occurred in the source tables Rep
131. isplays them 2013 IBPhoenix Editors Chapier 8 Managing Replication 107 Schema objects Conflicts No E My Initial Schema 133 5 My Target 133 OUNT_UPDATE_LOG OUNT_UPDATE LOG 1 Source database gt My Source Here we see that the target database had 133 conflicts We want to open the Detail tab to see what those conflicts were ig Manual conflict resolution My nitial Schema Options Help Summary Detail Conflicts Log Key values Insert ACCOUNT UPDATE LOG failed Reason Failed Row exists with NEWER TimeStamp 019 key values Gn Insert ACCOUNT_UPDATE_LOG failed Reason Failed Row exists with NEWER TimeStamp Force all replications Insert ACCOUNT_UPDATE_LOG failed Reason Failed Row exists with NEWER TimeStamp New key values Insert ACCOUNT UPDATE LOG failed Reason Failed Row exists with NEWER TimeStamp 1125 Force selected replications OUNT UPDATE LOG failed Reason F Ste gt TES Insert ACCOUNT UPDATE LOG failed Reason Fail i NEWER TimeStamp I Force Replication Insert ACCOUNT_UPDATE_LOG failed Reason Failed Row exists with NEWER TimeStamp Insert ACCOUNT_UPDATE_LOG failed Reason Failed Row exists with NEWER TimeStamp Insert ACCOUNT_UPDATE_LOG failed Reason Failed Row exists with NEWER TimeStamp 4 5 Delete Record Insert ACCOUNT_UPDATE_LOG failed Reason Failed Row exists with NEWER TimeStamp Insert
132. it True GEN DONATION ID gt GEN DONATION Il Server E Customers IBP datab GEN_GRANT_ALLOCATION gt GEN_GRAN GEN GRANT PAYMENT gt GEN GRANT Administrative user name New Toolbar Icons Notice that icons now appear for adding editing and removing objects when you select a lower level node in the tree 2013 IBPhoenix Editors Chapter 7 Defining a Replication Schema 69 Help mmu e Replication Schemata Initial Schema Source database sp My Source Target databases 3j My Target 1 5 1 Replicated tables and procedures gl ACCOUNT UPDATE LOG gt ACCOUNT f BANK ACCOUNT gt BANK amp CCOUNT an BANK CODE BANK CODE m CORPORATION gt CORPORATION QU 11 PERSON gt PERSON m TRANSAC_GROUP gt TRANSAC GROUP TRANSAC TYPE gt TYPE Replicated sequences GEN DOC 10 gt GEN DOC ID GEN DONATION ID gt GEN DONATION Il 0 a This button takes you to a dialog where you can map or remap the columns involved in primary keys or unique constraints In the tree a similar icon marks the node where you can do that task m This one takes you to the dialog for mapping the non key fields manually Similar icons in the tree mark the nodes for each non key column or for the asterisk mapping as in the screenshot which does all of the
133. ix Editors 18 IBP Replicator 4 1 first phase of the commit are left in each database in an unresolved state Although the database engine can tell whether the intention was to commit the transaction or to roll it back it does not presume to complete the second phase on its own initiative To correct a limbo transaction you need to use the automated two phase recovery mechanism provided by the t wo phase switch of the gfix command line utility that is installed in the bin directory of a full Firebird or InterBase server installation To have gfix try to resolve all limbo transactions in the databases automatically go to the bin directory of the respective database servers involved and use the command as follows Windows gfix t all database filespec Linux gfix t all database filespec The order in which you attend to each database is not important There are other options for recovering or resolving limbo transactions Consult The Firebird Book Second Edition Chapter 35 or the InterBase Operations Guide OpGuide pdf for details 2013 IBPhoenix Editors Chapter 5 Planning for Replication 20 IBP Replicator 4 1 Chapter 5 Planning for Replication 5 1 This chapter describes the planning and preparations that are necessary for implementing replication schemas that IBP Replicator can manage and process Choosing a Replication Scheme Database Design Issues Phy
134. ize although not the entire database the synchronizations need to be performed one by one There is no way to multi select a sub set of tables Missing Tables If the whole database is selected for synchronization and there is a mismatch between the source table names available and those configured for the target database a stop error will occur and the synchronization will be rolled back Operating System Environment Since off line synchronization is a routine of Replication Manager you will need a Windows machine as the client For Linux users with no Windows machine available it should be possible to run a Replication Manager instance in the Wine emulator File Names on Non Windows Servers Suppose you have a table created with CREATE TABLE Holy Mackerel The Replication Manager running on Windows will off load a synchronization file named SHoly 2013 IBPhoenix Editors Chapter 9 Advanced Topics 135 Mackerel synch Windows does not care about case sensitivity or the presence of spaces in a name You will run the up load part of the operation from Replication Manager as well so the application will not be bothered by either issue Where there might be an issue with such file names is in a server environment that requires them to be single quoted in entirety e g SHoly Mackerel synch or to have spaces and other special characters escaped e g SHoly Mackerel synch You might bump into such an
135. kconfig control or as an application launched with command line switches the command line switches are in line with those used with the Windows version although not all of the Windows switches apply to Linux the Replicator program causes a pid file to be created which is used as a locking mechanism to prevent another instance of the program from being started Refer to the list of command line switches for details of the options available You can also just run replserver help for a succinct list of these options Replication Management on Linux The former Replication Manager command line utility has gone and all management tasks for the Linux server can be done either through the daemon interface or via direct commands with switches Process instances not under daemon control are stopped using the Linux kill killall commands with signals NOTE IF you do not have a Windows machine available for defining your schemas and installing licences it is possible to run the Windows ReplMgr exe program in Wine the Linux Windows emulation compatibility system 2013 IBPhoenix Editors 92 IBP Replicator 4 1 8 2 1 Topics Installing and Configuring on Linux Controlling replserver Processes Loading Licences Manually Installing and Configuring on Linux Installing the Tarball As root download the tarball to any repository location that is convenient for you Unpacking the tarball will place
136. l with the G drive mapped as vol5 it should be dev vol5 IBPhoenix IBP Replicator data source gdb For a Linux or UNIX host our example path would be of the form dev IBPhoenix IBP Replicator data source fdb Q When focus is in the Server field you can click a button to launch a Find File dialog Administrative user name x Administrative user name required for InterBase optional for Firebird and Oracle if using trusted authentication The database server authentication username that the Replication Manager should use when connecting to and administering the database being registered It can be a different user name from the Replication username Administrative password required for InterBase optional for Firebird and Oracle if using trusted authentication The password for the administrative user name The username and password belong together as the two parts of a user login defined in the security database of Firebird or InterBase See also Administrative Role below When you start to make an entry in one of these fields a dialog will pop up for completion of both entries Character set required if the default character set of the database is other than NONE or for Oracle is not the same as the one in the environment variable NLS_LANG It should be a character set that is compatible with the DEFAULT CHARACTER SET for the database 2013 IBPhoenix Editors IBP Replicator 4 1 ORACLE
137. ler is now built into the Replication Server and no longer runs as a separate service Configuring and applying a schedule are now done using the Scheduler tool or the configuration editor Upgrading from a pre 2 5 configuration will convert a regular interval Replication into a Schedule If you are currently using Replicator 2 1 or older you must uninstall the old Replicator Scheduler service before upgrading It was superseded at v 2 5 and is no longer a component of the product Support for Replication to from and between Oracle Servers IBPhoenix Replicator 4 introduced support for including Oracle database servers in replications Oracle versions 9 and higher are supported 2013 IBPhoenix Editors Appendices 171 Server Type Option Replicator 4 uses a separate drivers for access to each of the three supported database engines Firebird InterBase and Oracle to allow the Replicator program to to take advantage of useful features in each The client libraries must be named according to their native conventions On Windows this means fbclient dll for Firebird gds32 dll for InterBase and oci dll for Oracle on Linux it means libfbclient so for Firebird libgds so for InterBase and libcintsh so for Oracle versions that can run on Linux Simplified Installation Configuration and Process Control on Linux The Linux version of the Replication Server has been revamped to comply with several platform standar
138. lication of subsets parts of records filtered sets is also possible This process is sometimes referred to as log shipping Synchronization Synchronization is an occasional usually once only method of replication where the entire contents of tables from a source database are pumped into tables in the target Synchronization is useful for adding data to a new target database from a source database to ensure that the two databases are in synch If a target database has simply been offline there is no need to perform synchronization as normal replication will catch up with any backlog of changes If the target tables are empty before synchronization the process is referred to as symmetric synchronization Replicant A replicant is a database that participates in replication Registering a database is the action of configuring an IBP Replicator installation to find and recognise a database Asynchronous Replication Replication is described as asynchronous where the architecture of the database engine and or the method of replication precludes a situation wherein the target database is kept in synch with the source data in real time IBPhoenix Replicator works with transactional database engines and is event or schedule driven Thus even though the process of replication can be effectively continual the replication performed is always asynchronous Synchronous Replication In situations where databases must always be kept up t
139. lications simultaneously though in case it causes lock conflicts application pp Run the server as an application t lt type gt type interbase firebird Case insensitive oracle file Minimises the shell window to the Run with a minimised Task Bar 2013 IBPhoenix Editors 90 IBP Replicator 4 1 log_to_file n log_to_window n log file file path or l file path p lt password gt lt gt r lt role gt debug Start replication automatically and quit after replication is complete n 1 Errors Only 2 Warnings and Detailed Error Description 3 Information 4 Detailed Information 5 Debug 6 amp 7 Thorough debug applicable to debug builds only Values for n as above Echoes the log to the command shell Provides an initial log file for use between server start and configuration load lt cfg gt is the full connection string for a specified configuration database lt password gt may be needed if it the config database specified is not the default one and the access password is different to that of the default config DB lt username gt if needed for the situation described above lt role gt if needed for the situation described above Run in debug mode Convenient for running replication from another application script Default is 2 warnings and detailed error description If a support consultant a
140. licts Synchronize Symmetric synchronize Expand the node for a specific target database and select the Replicated tables and procedures node To open the Replicated tables and procedures dialog either right click and select Define from the context menu or double click on the Define Tables icon the toolbar or gt select Replication Tables Define from the Replication menu You can use this selection to access the mappings pane at any time once you fN have table objects defined in your schema The Mapping Panels 2013 IBPhoenix Editors 62 IBP Replicator 4 1 TRANSAC_TYPE lt You can use Ctrl A to select all items in a pane Filtering If the lists of objects are too big to manage conveniently you can set a filter on the lists in the two panes Click the Filter button to display the filter bar below the lists f TFi amp N3AU BRULIF iRaNSAC GHOUP amp TRANSAC TYPE TRANSAC TYPE Do ED Filter Cancel Type in letters to filter the list down to just names containing those letters You can aim at single letters or substrings the filtering takes place as you type 2013 IBPhoenix Editors Chapter 7 Defining a Replication Schema 63 x Replicated tables My Target 1 Source objects and mappings Ta TRANSAC_GROUP TRANSAC GROUP amp TRANSAC TYPE TRANSAC amp F TRANSACTION
141. m whose metadata you want to borrow metadata definitions Click OK to save the configuration so that the pseudo database is registered Now you are ready to begin defining your offline replication schema 2013 IBPhoenix Editors Chapter 9 Advanced Topics 129 9 6 1 Configuring the Offline Schema Configuring an offline replication schema is virtually identical to configuring an online one For simplicity we ll assume here that your purpose in using offline replication is to substitute the 2 tier database to database schema entirely It is possible to include an offline replication in an existing schema to meet a specific need You can ask in the users support list about any aspects of your specific case that might not be obvious Create a new schema and assign the database that you want to be the Source IBPReplicator Schema settings Connection Settings Event logging v Replication enabled Schema name Conflict resolution strategy Priority Dmeraped Mast M Use default conflict resolution strategy Separator character Decimal ASCII code Replication Tools Help PESE 2551 Be Defined Replication Schemata E My Initial Schema Source database Target databases Offline For off line replication Descriptive name Comments Priority Highest E
142. n Works The target table is synchronized using data off loaded to files from the source database one table per file A pull synchronization from the files at the target server results in target tables that are exact copies of the source tables IBP Replicator performs any necessary inserts and deletes It is similar to a data pump operation except that the target table need not be empty Any records in the target table that do not exist in the source are deleted These synch files can be saved for use or re use as backups for point in time recovery for a whole database or just selected tables Each time a file is re used it will reset the target table to the state of the source table when the file was off loaded Synchronization vs Replication The synchronization files have the same structure as files created for off line replication The off loaded files are named as STableName synch where TableName is the name of atable By renaming the synch extension to dat and passing them to the Replicator process as an off line replication you can preserve the pre existing records in the target table For more information about replicating from synch files refer to the topic Replicating from an Offline Synchronization Set in the previous section Synchronizing Multiple Tables You can synchronize all of the tables configured for the target database whole database or just one table If you have more than one table to synchron
143. n application As a Service As a rule on the Windows service capable platforms Windows NT 2000 XP Professional and the 200X Server versions you will be running replication as a service 2013 IBPhoenix Editors 86 IBP Replicator 4 1 Starting the Service The Windows installer should have installed the service for you You can check this by inspecting the Services display by way of the administration tools on your server File Action View Help e s RAR Replication Server Name Description Status Startup Type Log Or amp Remote Procedur TheRPCSS Started Automatic Netwo Stop the service Remote Procedur In Windows Manual Netwo Restart the service Remote Registry 4 Replication Server Enables rem Manual Local Started Manual Local Routing and Rem Offers routi Disabled Local gt If you elected to have the service start automatically it will have the Startup Type Automatic and should be running Started unless someone has stopped it gt If you elected to have it start manually or it has been stopped shut down you can start it the same way as you would start any other service i e by right clicking on its entry in the list and selecting Start or Restart or by selecting its property sheet and manipulating it from there As an Application Resources permitting it is possible to run ReplServer exe as a
144. n this schema CRS strategy number DEFAULT Conflict resolution strategy to be used under this schema If DEFAULT is provided or implied by being omitted the global default strategy will be used when replication is performed under this schema If you provide the strategy number explicitly then possible strategies are gt 0 priority based gt 1 timestamp based gt 2 master slave default LOG lt log levels gt DEFAULT one of two possible LOG parameters available This one sets the logging levels and takes two integer arguments for logging to the window first argument and logging to the log file second argument For example ADD SCHEMA My Initial Schema SOURCE 1 USER REPL PASSWORD xxxxxxx ROLE REPL_ADMIN CRS 1 LOG 3 4 LOG INISCHEMA LOG ORDER 0 specifies level 3 logging to the window and level 4 to the log file 2013 IBPhoenix Editors Appendices 155 Log levels are from 0 log to 5 for ordinary builds of the Replicator server If you are running a debug build the highest logging level is 7 If DEFAULT is provided or implied by being omitted the global default level will be used for logging under this schema LOG log file name allows the name of the log file to be customised By default it will be REPLICATE LOG and you do not have to specify that 1 You can use both LOG parameters in a single command if need
145. nclude the ability to filter the display if the lists are inconveniently long and to configure via View Tables order in the main toolbar the order in which objects are displayed A keyboard shortcut Ctrl A was added to speed selection of groups of objects in the mapping panes Some extra intelligence has been incorporated into heuristics for auto generating object mappings While it is not infallible it should help to speed up the configuration of new schemas Replication of sequences generators 2013 IBPhoenix Editors 172 IBP Replicator 4 1 Sequence values can be replicated and synchronized in any configuration including in heterogeneous and offline schemas Table specific Foreign Key Violation Behaviour The foreign key violation behaviour that is configured in the global settings can now be overridden at individual table level Two phase Commit can be turned off For Firebird and InterBase databases two phase commit can be optionally turned off Two phase commit will be used only if both the source and the target database ina replication pairing are of the same type both Firebird or both InterBase and both have this setting turned on otherwise it will not be used Improved Support for Oracle Replication into Oracle stand alone procedures is supported now Character set can be set at connection level when registering databases to enable replication between databases with incompatible charac
146. nction independently within a larger network A local copy of a database means that the work group does not have to compete for larger network resources or suffer response delays by accessing databases on remote sites Decision support applications can be separated from high volume transactional applications if necessary which can reduce network traffic and improve data availability and system performance Reliability load balancing and failover Replicated databases can be maintained for load balancing and or improved system fault tolerance Applications can switch from original source databases to replicated copies in the event of system overload or outright failure Partially replicated databases can be dedicated to heavy read only operations freeing up resources for interactive users Flexibility of data distribution Any organisation has its own replication requirements and could be operating over a variety of databases With IBP Replicator you can replicate full databases a subset of tables selected rows and columns from tables in a source database to a number of target databases You can specify when you want automatic replication to occur on a time based schedule hourly daily weekly or when a specific event occurs or you can specify to initiate replication manually You can define multiple replication schemas if you need to that will enable different source database subsets to be replicated to specific multiple targets 201
147. nfiguration database to determine what it is supposed to replicate where it should find the data the source and where the data is to be replicated to the target Creating a Configuration Database from Scratch To create a configuration database start Replication Manager from the Start Menu ds HyperSnap 6 k IBPReplicator RA Replication Manager m Server UN tibreNffire 2 When the Replication Manager console appears use File New Configuration D Open configuration Close configuration IIN Drop configuration Create a new Configuration Database 1 Exit Server type Interbase Connection string Browse D User Name Password Comment aa Create new configuration database coed The configuration database doesn t have to be on the same host server as the replication 2013 IBPhoenix Editors Chapter 6 Installation and Setup 31 service The dialog starts by prompting you to select the server type actual list depends on DBMS clients you have installed in your system that the database will run on This enables the programs to take advantage of features in Firebird 1 5 and higher that are not available on InterBase such as database aliasing P Create a new Configuration Database Server type Interbase N Interbase Firebird Oracle Browse The rest of the configuration dialog pr
148. ng mapped must have compatible data types Refer to the Appendix Supported Data Types and their Compatibilities for information about matching columns with non identical data types Removing Mappings To remove replicated tables select the table node then either gt right click and select Remove from the context menu or gt double click on the Remove table mapping icon or gt select Replication Tables Remove from the Replication menu Primary key column and generator mappings can be similarly removed by selecting the appropriate node and working with the tools activated at that level Table Settings The Table settings dialog allows you to change the default settings for your source target mappings for an individual table To access this dialog select the table s node in the tree and either gt right click and select Settings or gt double click on the Table settings icon or gt choose Replication Tables Settings from the Replication menu 2013 IBPhoenix Editors Chapter 7 Defining a Replication Schema ication Tools Help 5 96 mu m m Y Defined Replication Schemata em My Initial Schema 5 9 Source database 0 f My Source Ed Target databases c5 My Target 1 Replicated tables and procedures E 1 amp CCOUNT UPDATE LOG gt ACCOUNT EilBANK ACCOUNT gt BANK ACCOUNT s BANK CODE gt Te i x gt x amp f CORPOR
149. ng to the database type selected Versions of IBPReplicator before v 4 1 did not behave correctly with the Firebird driver if the source database was Dialect 1 The Firebird driver now e Fir bird selects the correct dialect automatically Previous workarounds that involved using the InterBase driver for dialect 1 databases should be corrected to use the Firebird driver regardless of dialect Descriptive name required A user friendly name not the database file name that will be meaningful to anyone managing the replications For example Head Office Source is more meaningful than New database It is not a formal identifier so you may include spaces and punctuation as you wish Comments not required This property is entirely for your convenience to document and explain each database you register Priority Used when priority based conflict resolution is being set for the replication In this case replication conflicts are resolved by ensuring that data from the database with the higher priority number is preserved when conflicts arise ir bircii 29 trteBbaseORACLE 2013 IBPhoenix Editors 36 IBP Replicator 4 1 Key Size Size of the fields in the operation log table that contain the old and new key values of every replicated record This setting is used with other system objects during creation of the table and is ignored later The value must be big enough to allow the field to contain a string
150. o date synchronous replication would replicate changes as and when they occurred IBPhoenix Replicator does not 2013 IBPhoenix Editors 14 IBP Replicator 4 1 support synchronous replication Event driven replication can be employed whereby critical data is replicated in near to real time in response to an event The cost is a heavy overhead in resource usage Generally a compromise would be reached to replicate the critical data in response to an event while continuously replicating less critical data at suitable intervals according to a schedule Data Subset ting When only certain rows in a table are replicated to a target it is called data subsetting It is entirely possible that replication from a single source table could replicate different subsets to multiple targets 2013 IBPhoenix Editors Chapter 4 How IBP Replicator Works 16 IBP Replicator 4 1 Chapter 4 How IBP Replicator Works The purpose of IBPhoenix Replicator is to create and maintain identical data in database tables distributed across multiple local and remote sites This chapter provides a technical overview of how the various replication components work together to allow replication to take place Replication Schema Definition A replication schema defines e a source and target pair of databases e the objects in the source database that are to provide data for replication e the objects in the target d
151. of a user with SYSDBA privileges If you need this you will also need to include PASSWORD along with the password as its argument ROLE role_name if the user credentials are tied to a role for access to configuration structures 2013 IBPhoenix Editors Appendices 145 SILENTLY can be included to stop cfged from showing warnings about a missing configuration or a wrong version If a configuration is already open it will be closed before the requested one is opened In the screenshot two cfged commands have been submitted gt SHOW SCHEMAS lists the schemas that have been defined in this configuration database gt EXTRACT file destination requests that the entire configuration be extracted to the file path in the argument TIP EXTRACT produces a full extract of the configuration as it stands currently as a batch of cfged commands It is handy not just as a quick review of the whole configuration but also as a quick tool for cloning a configuration Common Rules Although there is variation in the keywords syntax and parameters for different commands discussed later a small set of rules is common to all commands 1 Keywords are case insensitive Parameters may be case sensitive or not according to purpose and usage Boolean parameters are case insensitive and may be in any of the following forms true false yes no onloff or 110 2 Multi line commands are allowed as long as a back
152. offline replication instead CONDITION lt row level replication condition use for a row level replication condition that needs to be applied to all relations in the target database For more information about this parameter refer to the topic Row level replication condition 2013 IBPhoenix Editors Appendices 157 LOG lt log levels gt DEFAULT one of two possible LOG parameters available if you need to override the schema setting for this target One sets the logging levels and takes two integer arguments for logging to the window first argument and logging to the log file second argument i Log levels are from 0 no log to 5 for ordinary builds of the Replicator server If you are running a debug build the highest logging level is 7 If DEFAULT is provided or implied by being omitted the level set for the schema will be used for logging replication to this target LOG log file name allows the name of the log file for replications to this target to be customised 1 You can use both LOG parameters in a single command if need be A ORDER lt number gt This parameter enables you to set the order of replication when this target not the only one Use SHOW TARGETS to view the current order of replication per schema MODIFY TARGET Use to modify a specified target database in a specified replication schema Parameters follow the same rules as for ADD TARGET above Syntax
153. omatically as a daemon at boot up chkconfig IBPReplicator on TIP You can run multiple replserver daemons as long as each uses its own PID file 8 2 2 Controlling replserver Processes Controlling replserver as a Daemon When the replication daemon is under chkconfig control you can use the following service commands to control it during operation To start the daemon service IBPReplicator start 2013 IBPhoenix Editors 94 IBP Replicator 4 1 To stop and restart the daemon service IBPReplicator restart To stop the daemon without restarting it service IBPReplicator stop To reload the configuration without stopping the daemon service IBPReplicator reload Log Files If replserver is run as a daemon the replication log is written in var 1og Controlling replserver with Switches You can use the command replserver with the appropriate switches to start the replication server directly as a daemon or as an application Some switches are required others are optional and some take parameters You can use this method to run multiple instances of replserver as applications You should not try to run it as a daemon if there is a service already running under chkconfig control Switch Format Note that the syntax and semantics of the switches are now the same as those used for command line operation on Windows although not all of the switches available on Windows are available on Linux
154. ompts you to define connection string for the configuration database and a valid username and password The Comment field is optional it may be used in the title bar of some displays For example suppose you decide to store your configuration databases in a subdirectory databases in some folder structure on your server Your setup entries might be similar to this Create a new Configuration Database Server type Firebird Y Connection string Browse E Customers BP databases replefg fdb User Name REPL Password Comment My Replication Config The server connection string in the screenshot is an example only using a serverless protocol that is available locally with some models of Firebird and InterBase Use the connection string that is appropriate for the client server environment in which you are working If you are uncertain about it check with your network administrator or advisor For Firebird consult the Quick Start Guide applicable to your server version The User Name is that of a user on the server that is to be the owner of the new database The user ADMIN in the example is an ordinary user name on the host server Some sites might prefer that the SYSDBA user be the owner of replication configuration databases Creating configuration database adds it to the list of known configuration databases any of which can be accessed quickly and simply through the File menu The menu also provi
155. ort errors to the support list ibp replicator amp lists ibphoenix com please use the method described here to post error details in your problem description Please do not post screenshots of error dialogs into the list Subscribing to the Support List Support questions will be answered in the list free of charge even if you are just at the stage of evaluating IBPhoenix Replicator To subscribe click the link below and send the email that is generated into your default email client ibp replicator requestlists ibphoenix com subject subscribe Alternatively visit the web interface to fill in and submit a subscription form 2013 IBPhoenix Editors Chapter 9 Advanced Topics 116 IBP Replicator 4 1 Chapter 9 Advanced Topics 9 1 This chapter examines an assortment of topics that will be of interest to the replication designer when addressing more complex replication requirements As time goes by more articles and How tos will be added gt Schema Numbering explains why the internal numbers assigned to configurations by the Replication Manager might be interesting to the replication designer Metadata Changes describes what happens when metadata changes occur in the source database Adding Timefields provides a way to generate a script that you can run to add Timefields to all of the tables in a database Advanced Mapping Techniques provides a simple example of writing a stored procedur
156. plication Manager or Replicator execution as an application a dialog box should appear If details are available a Details button will be visible to display any accompanying error message You can use Ctrl C to copy the entire message including its details to the Windows clipboard IBPReplicator Error Cannot open configuration database of type Firebird A database error occurred Details Error code 902 Unsuccessful execution caused by a system error that predudes successful execution of subsequent statements Your user name and password are not defined Ask your database administrator to set up a Firebird login 2013 IBPhoenix Editors 114 IBP Replicator 4 1 The message can then be pasted into a text file or directly into an email using Ctrl V The screenshot below shows the content of the message above pasted from the clipboard into Notepad 2 33 New Text Docu fit Notepad lt File Edit Format View Help Cannot open configuration database of type Firebird database error occurred Unsuccessful execution caused by a system error that precludes successful execution of subsequent statements Your user name and password are not defined Ask your database administrator to set up a Firebird login S LCode 902 Version 4 1 0 FB client 2 5 1 26351 0 client 6 3 1 26351 Oracle client Not installed Reporting Errors to Support When you rep
157. r 4 1 7 8 database You can also choose to remove just one or more system objects selectively Select the object in the Target Database node and then right click Remove System Objects Target databases Pail My Target 1 E Replicated tables and procedures EI ACCOUNT UPDATE LOG gt ACCOUNT_UPDA ff BANK ACCOUNT gt BANK ACCOUNT is f PERIOD gt PERIOD 1 Pa Define Qn PN Remove gt CORPO Settings gs col fo Create system objects H COUNT Remove System Objects m CURRE gt m Keys m PERSO Data Poa Click OK to confirm and a message will inform you that the object has been excluded I E FR E Customising the Global Settings The global settings are stored in the configuration database when it is created Although optional custom global settings will be useful if you are running multiple replications with the same settings You can configure settings for any individual schema with its own settings if you like it will overrule the server s global settings for that schema only Changing the global settings does not change the settings of schemata that have already been defined only newly defined schemata will have their settings initialized to the new values For schemata you are going to define in future custom default behaviour can be set up to
158. re sufficiently poor to necessitate resorting to periodic commit it recommended that you use offline replication instead Row level replication condition This is an optional setting that allows rows to be selected for replication on the basis of some value in the data For example if you have defined a multi site database with conditional replication in view you might have a key on some tables that identifies the site when the data in a record pertains to that site and not to other sites in the schema This setting can define this condition To implement this any tables that you want to apply this global condition to should include a column with an identifier that is the same for all such tables Express the condition like a predicate inside an IF clause In the example illustrated the condition SITE ID 100 will tell IBP Replicator to look out for columns named SITE ID in the replications it performs to this target and ignore any rows that have any value other than 100 in this column Row level conditioning can also be done at individual table level For details and more information about the row level conditioning expressions to use look here Event Logging Tab You can optionally override the default log file and define a specific log file and logging levels for this particular target database 2013 IBPhoenix Editors Chapter 7 Defining a Replication Schema 59 IBPReplicator Target database
159. re to be involved in your replication schema the next task is to identify the data that will be replicated Summary of Steps The steps involved are 1 Creating the schema 2 Choosing the source database 3 Choosing the target database 4 Choosing replicated tables 5 Table settings 6 One time synchronization 7 Identifying primary keys 8 Choosing replicated columns 9 Creating system objects in the source database 10 Customising the global settings optional Assigning the Default Configuration Database One configuration database should be assigned as the default Once the Replication Server is running it will automatically connect to your default configuration database and use the information there to do its work Important This task will write to the Windows Registry which requires Replication Manager to run with escalated privileges on Windows 7 Windows 2008 server and higher Windows versions To do this right click on the shortcut for Replication Manager and select Run as administrator A Computer Management m Replication Manager c Replication Server Wy Run as administrator Pin to Taskbar and answer YES in the security dialog that appears In Replication Manager you can pick up the configuration you want to work with by 2013 IBPhoenix Editors 46 IBP Replicator 4 1 7 1 clicking File on the menu bar and selecting one from the drop down list s RA IBPRepli
160. rent directory if in application mode Q Windows in the IBPReplicator subfolder of the All Users Application Data folder If you are setting up more than one replication you will probably want to specify non default paths and or file names for each one s log Error Notification by Email To enable email notification make sure the Mail Sysdba checkbox is checked An email notification will be sent to the designated TO address each time Replicator encounters an error Once you have set up the notification details click the Test Mail button to verify that it works IBPReplicator Global settings ns Settings Event logging Error Notification SMTP server 50 From Address 550 From Name 505 To Address PO Test Mail Min time between mails min To prevent your mailbox from overflow you can set a minimum interval in minutes between email notifications If it is set Replication Server will swallow mail messages for the specified number of minutes after successfully sending one The default setting of 0 minutes disables this protection 2013 IBPhoenix Editors Chapter 8 Managing Replication Chapier 8 Managing Replication 85 Chapter 8 Managing Replication The topics in this chapter concern the actual running of your replication services and the tools and utilities provided to do so On Windows you will ideally run IBP Replicator as a service On Windows t
161. rs Appendices 169 You can use both LOG parameters in a single command if need be SCHEDULER ON OFF Enable or disable the replication scheduler MAIL ENABLED DISABLED Enable or disable email notification from the server to an administrator MAIL TO lt e mail address gt An email address for the administrator who wants the notifications The keyword MAIL is optional if this is not the first MAIL parameter contained in the command MAIL HOST lt SMTP server host name gt Host name of the sending email server MAIL FROM lt e mail address gt A Sender email address that has been set up for IBPReplicator s use MAIL NAME visible name The Sender name that is to appear in the headers of emails sent by IBPReplicator MAIL PERIOD lt minimum time between mails gt To prevent your mailbox from overflow you can set a minimum interval in minutes between email notifications If it is set IBPReplicator will swallow mail messages for the specified number of minutes after successfully sending one The default setting of 0 minutes disables this protection BEEP boolean value Set to True if you want the server to give an audible signal when it begins replicating FK BEHAVIOR ERROR CONFLICT IGNORE Use to set the global default for dealing with foreign key violations Valid settings are Error causes an error to be written to the log and the record will not be replicat
162. rs and types of all registered databases It takes no parameters Syntax SHOW DATABASES Working with Schemas ADD SCHEMA Add a new schema with a given set of parameters Some parameters may be omitted In that case default values will be used Syntax ADD SCHEMA lt schema name gt lt schema parameters gt 2013 IBPhoenix Editors 154 IBP Replicator 4 1 Schema parameters NAME schema name gt your own user friendly name for a new schema It is required Make sure it is different from other schema names in the configuration Use of the keyword NAME is optional if the schema name is the first parameter NUMBER schema number if you are managing your own schema numbering system use this parameter to provide a unique number If this parameter is omitted a new number will be autogenerated SOURCE source database number or name provide either the number or the friendly name of a registered database If this parameter is omitted the current database will be used ENABLED DISABLED By default the new schema will become the active one Use this parameter to control this option COMMENT schema comments Option comments you can include with the schema USER user name PASSWORD user password ROLE user role User name password and if required the name of the role that is authorised to read the source database and write to the target databases to be included i
163. rt e An insert finding a record in the target database with an identical key is converted into an update e A delete finding no identical key record in the target database is ignored Master Slave The source database always takes precedence resolution will be as described in the example above Timestamping This method determines the newer version of data by comparing server timestamps written into the data It needs a suitable timestamp column defined in both source and target tables Older rows in the source database will not overwrite newer rows in the target 2013 IBPhoenix Editors Chapter 6 Installation and Setup Chapter 6 Installation and Setup 29 Chapter 6 Installation and Setup IMPORTANT The configuration database structure in IBP Replicator 4 is not compatible with those of previous releases Please take copies of your configuration databases before installing The newer Replication Manager will automatically upgrade old configuration databases on opening Licences from previous versions of the Replicator are not valid for Replicator 4 Existing version 3 licences will be preserved and marked invalid Any licences older than version 3 will be removed from the configuration altogether Windows Installer Program The IBP Replicator software for Windows comes as an executable Windows installer program named IBPReplicatorSetup n n n Win32 exe where the n characters represent numb
164. s 162 IBP Replicator 4 1 MODIFY SEQUENCE Use to modify the properties of a replicated sequence Parameters follow the same rules as for ADD SEQUENCE above Syntax MODIFY SEQUENCE lt sequence number gt lt target sequence name gt OF SCHEMA lt schema number or name gt TARGET lt target db number or name gt SET lt sequence parameters gt If the number or name properties of the SCHEMA or TARGET parameters are Zn omitted the current ones are used Be certain you are directing the changes to the right target REMOVE SEQUENCE Use to remove a replicated sequence from a replication schema Syntax REMOVE SEQUENCE sequence number target sequence name FROM SCHEMA schema number or name gt TARGET target db number or name gt If the number or name properties of the SCHEMA or TARGET parameters are Zh omitted the current ones are used Be certain you are directing the changes to the right target SHOW SEQUENCES List the replicated sequences for a given or current schema and target database Syntax SHOW SEQUENCES FOR SCHEMA schema number or name gt TARGET target db number or name gt or name is omitted sequences for all target databases will be shown not just 4 In contrast with the behaviour of other commands if the target database number the current
165. s 1 PERSON_ID Data Fields All TABLE TRANSAC_GROUP gt TRANSAC GROUP Key Fields 1 TRANSAC_GROUP Data Fields All TABLE TRANSAC TYPE gt TRANSAC_TYPE Key Fields 1 TRANSAC_TYPE Data Fields All I SEQUENCE GEN DOC ID gt GEN_DOC_ID SEQUENCE GEN DONATION ID gt GEN DONATION ID SEQUENCE GEN GRANT ALLOCATION gt GEN GRANT ALLOCATION SEQUENCE GEN GRANT PAYMENT gt GEN GRANT PAYMENT Generate and it is done Now the mappings appear in new nodes in the tree 2013 IBPhoenix Editors 68 IBP Replicator 4 1 File Configuration View Database Replication Tools Help gt PB E Defined Replication Schemata 5 1 My Initial Schema B gt Source database My Source Target databases e My Target 1 E Replicated tables and procedures B BJ ACCOUNT UPDATE LOG gt ACCOUNT_UF 1 BANK ACCOUNT gt BANK ACCOUNT gm BANK CODE gt BANK CODE HN tt gt x 1 CORPORATION gt CORPORATION 1 COUNTRY gt COUNTRY 1 CURRENCY gt CURRENCY M F TRANSACTION gt F_TRANSACTION 1 MEMBER gt MEMBER 1 MGROUP gt MGROUP E PERIOD gt PERIOD PERSON gt PERSON TRANSAC GROUP gt TRANSAC_GROUP Firebird Descriptive name My Source Comments The source database d 1 TRANSAC TYPE gt TRANSAC TYPE Priority Highest B 1 Replicated sequences Key size 128 GEN DOC ID gt GEN DOC ID Use 2 phase comm
166. s Normal Licensing On each host machine that acts as a replication server a server licence must be installed Each database whether source or target needs a replicant license The minimum server licence needs two replicant licences One is bundled with the server licence automatically and issued separately You should order your initial Server licence with enough Replicant licences attached to cover all of the databases that will be involved in a 2013 IBPhoenix Editors Chapter 8 Managing Replication 109 single replication cycle So for example a machine that acts as the replication server and has a single Source database and which is replicating to one remote Target database will need only a Server licence with the bundled Replicant licence plus one more replicant licence purchased separately Same database used as multiple replicants No database needs more than one Replicant licence If the same Source or Target database is being controlled by more than one instance of the Replication server then you need to account for one database only once as a replicant when calculating the replicant denominations for your server licences Installing Licences Once you have created your first configuration database the Tools menu of the Replication Manager becomes visible It contains the License Manager applet for installing your licences as I U U lt File Configuration View Database Replication
167. s and Oracle procedures If you want to synchronize sequences generators as well check them on manually You can also check off any objects you don t want synchronized 2013 IBPhoenix Editors Chapter 7 Defining a Replication Schema 77 R IBPReplicator Synchronize Replicated tables and procedures v ACCOUNT LUIPDATE LOG gt ACCC v BANK ACCOUNT gt BANK ACCOL v PERIOD gt PERIOD v CORPOP4T OM gt COSP RATION Source database My Source Target database My Target 1 Replicated sequences GEN DOC ID gt GEN DOC ID GEN DONATION ID gt GEN DON GEN_GRANT ALLOCATION gt GEI Unselect all Select all Add timestamps C Users dbadmin4ppD ataLocal BPReplicator S ynchronize log Show message every thousands of records 100 Options Write detailed log to file Check this on if you want a log of the synchronization The field beneath shows the default location for logs on your system according to your global or schema level setting When logging is selected this field becomes writable and you can specify a custom location for this log if you wish Make sure you enter a file path that already exists Add timestamps Select this if you want the screen and log messages to include timestamps Show message every the process will return a progress message to the window every 100 000 records Change this if you want me
168. s means that London acts both as a source and as a target for Leeds Manchester and Birmingham In this illustration London the central database fetches changes made by Manchester and forwards those changes onto Leeds and Birmingham The same is true for Leeds and Birmingham To prevent changes from Manchester Leeds Birmingham bouncing back to Manchester Leeds Birmingham respectively through London you would normally use the special user REPL in a simple Peer to Peer schema However that generates a problem because we do want to forward Manchester s changes to Leeds and Birmingham Leeds changes to Manchester and Birmingham and Birmingham s changes to Leeds and Manchester In this case we cannot use the username REPL since data would for example replicate from Leeds to London but would not get forwarded to the other branches On the other hand we do not want data to be replicated from Leeds to London and then from London back to Leeds Our solution is to have more than one dedicated replication user in our systems e g REPL_BIR REPL_LEE and REPL_MAN for our three spokes and use the applicable alternative replication user as our username The Source Database Triggers 2013 IBPhoenix Editors 126 IBP Replicator 4 1 CAVEAT These examples are for guidance toward a custom solution to a complex business problem They are in no way intended to be templates or a recommendation to meddle with the
169. section is merely a brief overview of the inbound side Databases At this side the on line database is configured as the Target while the pseudo database inbound directory will be configured with Files as the Source Schema Configuration Configuring the schema for the inbound replication will be the reverse of what you did when configuring the outbound one No system objects are created in the on line Target for this replication Preparing for an Inbound Replication The IBP Replicator package does not provide any tools for porting the offline files between the servers It is up to you to set up a mechanism for picking up a file from the source server and delivering it to the configure Inbound directory Do not overlook the fact that the inserts updates and deletes replicated from the file will be timestamped with the source server s timestamps which may have a bearing on their age relative to the timestamps on any records affected by the inbound replication and or on any REPL LOG records awaiting a downstream replication Replicating from an Offline Synchronization Set Offline synchronization generates a set of files containing all of the data from tables specified for an offline replication After such a synchronization the specified outbound database directory will contain one file for each table specified The off loaded files are named as STableName synch where TableName is the name of a table The binary format of
170. sical Distribution Considerations Conflict Resolution Choosing a Replication Scheme You can choose from a variety of replication models to propagate data throughout your network Your choice will reflect the requirements of your system Models can be combined to fulfil needs that are too complex to be satisfied by a single scheme Multiple schemas can be set up to fulfil different requirements too Central to Standby This simple model fulfils a requirement to replicate one way from a source database to a target It is the scheme typically used to fulfil a failover requirement whereby a standby database must be available to resume activity if a source database should fail m A Central to Standby scheme can be set up with a Peer to Peer schema see below to enable changes in a failover database to be applied to the source database once it comes back on line Peer to Peer In a Peer to Peer environment bi directional two way replication allows source databases to send changes to targets and vice versa Each database source or target can function autonomously at its own site Changes from one database are replicated to the other to bring all databases up to date 2013 IBPhoenix Editors Chapter 5 Planning for Replication Cascade eplicatar q S erver uroe 8 ji e Database t Q 9 21 Cascade replication takes data from a source database and moves it to a target that t
171. sks you for a debug log level 7 is the one to generate Logging levels above 5 apply to a debug build which is not part of the normal software distribution Default is 2 warnings and detailed error description Enables troubleshooting for cases where ReplServer exe has problems loading the configuration but the default location for the log file is unavailable for some reason Can be used to run an alternatively configured replication This is logging level 7 the most verbose level If a support consultant asks you for a debug log this is the one to generate help or h Prints succint help for these switches Installation Switches 2013 IBPhoenix Editors Chapter 8 Managing Replication 91 In case you need to know the installation switches for making your own service installer script they are as follows instal Install the replicator service uninstall Uninstall the replicator service This uninstalls the service not the software auto Have the service start automatically dep lt service Used for passing the lt service name gt of a service that the name gt replication service depends on 8 2 Linux Operation The Linux Executable In this version there is just one executable replserver for running IBP Replicator on a Linux server If you ran a previous version of IBP Replicator on Linux some things have changed replserver can now be run as a service under ch
172. slash is included as a new line signal at the end of each line For example when adding a licence which requires the licence ID and the licence key to be separated you would include the backslash before pressing Enter gt ADD LICENSE REPL_999 gt The continuation sign gt that appears is ready to receive the pasted licence key from the clipboard gt ADD LICENSE REPL 999 X a8 8qf U26 d2 EKATX 3EUDNX1i 199W CELeG 8 PY8U04SqUhVH 40XA1 dw Hb 7 81K E WFU1N 4g5F7Cn78V HdH7D HQo m 05 V Cd Y n4 KLMN3 GP PdTELHe aKD1 c b Y7w 8983H JWR OKVZG7 3 Cbm cM w jEY4dXIa XDWNi1QOAB8cGBbGBM FN RjFULK83781c I BNcH2108 SS amp JaPob 6Xal 7AUFG e gt 3 Words must be separated by white space for example OPEN REPLCFG good OPENREPLCFG rejected 2013 IBPhoenix Editors 146 IBP Replicator 4 1 4 Parameters that contain spaces such as file paths must be delimited by pairs of quotes single or double or by square brackets For example INIT C Customer Data SMITHDB FDB or INIT usr Customer Data SMITHDB FDB g White space between quoted or bracketed segments is ignored If a closing quote or bracket at the end of an otherwise valid command is omitted cfged will allow it Command line Switches When you start cfged in either interactive or direct mode or within a batch script some switches are available to control the way the program runs b ON OFF bail on
173. ssages to be more or less frequent Numbers are in thousands A monitor window will pop up and display the synchronization as it happens The window will fill up very fast but you can scroll back to check what has been done 2013 IBPhoenix Editors 78 IBP Replicator 4 1 7 7 nize Work commited gt ACCC Rows processed 31 X ACCOL Synchronizing MEMBER gt MEMBER RATION Rows processed 256 v Synchronizing F TRANSACTION gt F TRANSACTION ANSAC Rows processed 1776 TY Synchronizing GEN DOC ID gt DOC ID Synchronizing GEN DONATION ID gt GEN DONATION ID 3ANSACT Synchronizing GEN GRANT ALLOCATION gt GEN GRANT ALLO Synchronizing GEN GRANT PAYMENT GEN GRANT PAYMEN C ID Synchronizing GEN MEMBER SER NUM gt GEN MEMBER SER N DON Synchronizing GEN PERSON ID GEN PERSON ID 111 N gt GEI Synchronizing GEN PERSON ROLE ID GEN PERSON ROLE I Synchronizing G_BATCH_ID gt G_BATCH_ID M gt GEN Synchronizing G PP TRANSAC ID G PP TRANSAC ID E PERSOJ Synchronizing G_P_KEY gt G_P_KEY gt 1 Synchronizing G_TRANSACTION_ID gt G_TRANSACTION_ID ID Finished PP m select all Single table Synchronization If you just want to synchronize an individual table select the table in the Replicated Tables and Procedures node of the tree right click and select a synchroni
174. stand alone application It can be started from the supplied graphical interface or from the command line including a batch file On Windows 9x and ME you have no alternative since these platforms do not support services On the other platforms you can run it as an application to perform occasional replication runs that can use an alternative configuration database if necessary To start ReplServer exe as an application from the graphical interface click its icon in the Start Menu 2013 IBPhoenix Editors Chapier 8 Managing Replication 87 ib HyperSnap 6 elp and Suppo k IBPReplicator x Replication Manager g Replication Server s y Libre Office 3 5 The Application Interface The graphical interface appears populated with the parameters for the default replication that it has started re Replication Server File Options Help gt 40 Config Type Firebird gt Config Database E Customers IBP databases epicigfdb gt E User Role REPL ADMIN Password Log File C ProgramData IBPReplicator REPLICATE LOG If you watch long enough the log window will fill up with an account of the replication that is going on If it is doing what you want just minimise the display and let er rip You can maximise it and look in on your replication at your pleasure 2013 IBPhoenix Editors 88 IBP Replicator 4 1 09 26 12 15 24 35 RRR RRR RRR RR SE
175. t database is ignored Master Slave the source object always takes precedence regardless of the priority settings resolution will be as described above for the higher priority database Timestamping this method determines the newer version of data by comparing server timestamps written on records It needs a suitable timestamp column defined in both source and target tables Older rows in the source database will not overwrite newer rows in the target Default if you later want the strategy for this object to revert to that specified for the schema select this option Time field name If you are using the time stamped conflict resolution strategy both the source and target tables need a timestamp column from which IBP Replicator is to read for comparing the ages of the rows to resolve conflicts It should be a TIMESTAMP type DATE type in IB 5 x into which a regular Before Insert or Update trigger separate triggers for InterBase writes the system timestamp CAST NOW AS TIMESTAMP whenever an insert or update occurs IMPORTANT The time field must have the same name identifier in both the source and target tables The field name is case sensitive it must be entered without quotes exactly as it is seen by the server Thus for example if the identifier was defined with double quotes as TimeFieldForReplication then type TimeFieldForReplication here If it was defined without the quotes e g TimeFieldForReplicat
176. ta values data data crlf AS BEGIN insert into ext data data values data data crlf NEW timefield id CAST NOW AS TIMESTAMP insert into ext data data values data data crlf END insert into ext data data values data data crlf insert into ext data data values data data crlf COMMIT 2013 IBPhoenix Editors Chapter 9 Advanced Topics 121 insert into ext_data data values data data crlf insert into ext_data data values data end data crlf SET TERM insert into ext_data data values data data crlf End script insert into ext_data data values data data crlf insert into ext_data data values data end 94 Advanced Mapping Techniques Replicating to Stored Procedures Sophisticated users can customise IBP Replicator to handle specialised replication conditions by defining stored procedures to manipulate the data that the replication will insert update and delete data in the target database Requirements In designing a Stored Procedure that IBP Replicator can use you need to make provision for everything that will be wanted for the operations Input Arguments Provide one input argument for o each key column o each data column that will be replicated o an OLD value for each key column if an update might be involved o a final parameter that
177. tabase choosing a source 50 Database choosing a target 55 Database design issues 24 Databases registering 13 3 Default global settings 80 Default configuration database 45 Definitions ways to work on 47 Definitions ways to work on 46 Distributed primary keys 24 DROP cfged 149 E Email notification 80 83 Enable Disable Monitor 72 Event logging 82 event triggered replication 30 Exclude an operation 74 Executables Windows 85 Existing configuration to access 98 EXTRACT cfged 149 _F Foreign Key Violation behaviour 80 82 Foreign key violation behaviour table level 73 zs Getting email notification 80 Global settings 80 Global settings customising 80 H Handling conflicts 27 HELP cfged 146 Heterogeneous replication 26 Hub and spoke 20 2013 IBPhoenix Editors IBReplicator architecture 12 IBReplicator benefits 9 IBReplicator security 9 IBReplicator terminology 13 Inbound offline replication 132 INIT cfged 149 Installation 29 Installation Start Menu shortcuts 29 Installation Windows installer 29 Installer switches 89 Installing licences 108 Installing on Linux 92 Intervals replication 80 IPX SPX protocol 30 K Keep Statistics 72 Key mappings 69 kill parameters 91 killall parameters 91 zx Licences loading manually 97 Licences loading without Windows 97 Licences installing 108 License Manager tool 108 Licens
178. target If the target also acts as a source database to the original source now a target this change will get picked up on the target and be replicated back and so on The REPL User The solution to the looping problem is to have the user REPL defined on the servers REPL is a special user within the IBP Replicator application as IBP Replicator recognises REPL as myself Any change made by a REPL user will not get replicated to the target database NOTE To use the REPL user you do need to set the user up in the server s authentication system with the appropriate privileges it needs to do its job 2013 IBPhoenix Editors 124 IBP Replicator 4 1 Replicating Subsets of Data Some scenarios require the rows that are to be replicated from one database to another to be restricted For example in a Head Office London to Branch Office scenario Leeds the branch office needs only to receive replication of data applicable to Leeds not London specific data nor data specific to other branches There are two ways to implement this in IBP Replicator gt The simplest is to place a row level replication condition on each table to exclude all but the applicable rows gt The other method usually used for very complex situations is to replicate all data to a Stored Procedure on the target database and let the logic of the rules implemented in the procedure target database decide whether it wants to
179. ter installing a new version of IBPReplicator over an older version Replicator 3 or higher It takes no parameters Syntax UPGRADE ADD LICENSE Add a license to a configuration Syntax ADD LICENSE lt license id gt lt license key gt S Separate the license id from the license key with a backslash followed by Enter and paste the license key into the new line REMOVE LICENSE Use to remove a licence from a configuration Syntax 2013 IBPhoenix Editors Appendices 151 REMOVE LICENSE license Id 1 You can use SHOW LICENSES to identify the licence you want to remove You N cannot remove EVAL licence SHOW LICENSES Lists the licences installed in the configuration database No parameters Database Registration ADD DATABASE Register a database in a configuration The set of allowed parameters depends on the database TYPE INTERBASE ORACLE FIREBIRD Syntax ADD DATABASE OF TYPE lt db type gt lt db params gt db type INTERBASE ORACLE FIREBIRD FILE Required db params lt param name gt lt param value gt lt db params gt Common parameters This group of parameters is common to all database types NUMBER database number If not provided it will be set from a sequence generator NAME descriptive name for the database Required If you want to look up the numbers and descriptive names o
180. ter sets An issue with passwords in Oracle configurations was fixed An issue with replication of tables without data fields was fixed Replication into Views Replication to views is supported from v 4 1 bringing a benefit for some admins who find it simpler to manage custom replications with triggers instead of writing and debugging complicated procedures Views are displayed in lists of potential target objects in the graphical utilities and VIEW is supported as a target relation type in cfged Full Dialect 1 3 Support in Firebird Driver The Firebird driver now selects the correct SQL dialect automatically Previous workarounds that involved using the InterBase driver for dialect 1 databases should be updated to use the Firebird driver regardless of dialect InterBase Driver Improvements The default SQL dialect setting for the InterBase driver is now AUTO signalling automatic detection of the client dialect based on the database dialect Interbase long object names are now supported Synchronization Improvements A timestamping option is available for logging synchronization to the Synchronization window and the frequency of the log messages can be configured Fully detailed logging of a synchronization can now be optionally directed to a file 2013 IBPhoenix Editors Appendices 173 Set a Temporary Log File Name in Server Start Command The replserver executable now has an optional switch to set an initial
181. the friendly name of your source database is greyed out and not editable Username password and role You can change the username password and role if needed to be used by the replication server when it connects to the source database The name of the replication user does not have to be the SYSDBA or that of an Administrator of the operating system For example the REPL replicator user can be used for any replication It must be used if you plan to implement bi directional or n way replication 2013 IBPhoenix Editors Chapter 7 Defining a Replication Schema 53 About the REPL user The user named REPL is recognised by IBP Replicator as a special user Any changes made to the source database by the user REPL will NOT be replicated This is by design to prevent replications from a target database back to a source from going into a loop Test the connection Whatever user you assign make sure that it is added to the relevant security databases on each machine involved in the replication Once you have done that click the Test Connection button If login is unsuccessful review your entries and make any necessary corrections before trying again It is pointless proceeding now unless you can make a successful connection test Settings The second tab enables you to customise settings for this source target pairs in this schema They are initialised to the global default settings but can be modified wi
182. thout affecting either the defaults you have already set or any settings you might have customised for another replication IBPReplicator Schema settings Connection Settings Event logging Schema name My Initial Schema Conflict resolution strategy C C G M Use default conflict resolution strategy Separator character Decimal ASCII code ee Comments First schema set up by the boss Needs checking You can add any free form comments you like in the Comments box to augment or override any comments inherited from the defaults Replication enabled This check box should be checked ON unless you need to prevent replication from occurring For example you would check it off if you were taking the network down or powering one of the servers down for maintenance 2013 IBPhoenix Editors 54 IBP Replicator 4 1 Conflict resolution strategy The replication is initalised to use the default conflict resolution strategy that you might have customised previously refer back to Customising the Default Settings The current default setting appears above greyed out In the illustration it is Master slave You can override the default conflict resolution strategy by checking off Use default conflict resolution strategy and specifying one Don t select Time stamped unless you have the necessary Timefield columns in all of your source and target tables Separator character
183. tors tables primary keys and fields can be done automatically by double clicking on the G enerate Tables Keys and Fields icon or selecting Tables Autogenerate from the Replication menu or any context menu that offers it This choice causes all tables keys and fields in the source database to be automatically selected for mapping to corresponding objects of the same name in the target database Previous mappings will be respect ed You can multi select a selective group of tables and autogenerate the mappings and objects for them cation Tools Help 555 Defined Replication Schemata F E My Initial Schema D gt Source database 8j My Source Target databases Ej My Target 1 Replicated tables and procedures Replicate Define AutoGenerate View conflicts Synchronize Symmetric synchronize The Autogenerate dialog appears with all of your unmapped objects tables primary keys procedures views and sequences generators selected with best guess source target mappings based on object names 2013 IBPhoenix Editors 66 IBP Replicator 4 1 Bx Auto Generate Tables oe oe aa Replicated tables and procedures W ACCOUNT UPDATE LOG gt v BANK ACCOUNT gt BANK ACCOUI v CORPORATION gt CORPORATION COUNTRY gt COUNTRY v CURRENCY gt CURRENCY F TRANSACTION gt F TRANSACTI ME
184. ts 2013 IBPhoenix Editors Chapter 4 How IBP Replicator Works 17 Whenever the server receives the instruction to replicate it follows this sequence 1 It looks at the data that has been read from the configuration database to determine the source and target pairs of databases 2 Next it looks at the replication log table in the source database to find out which changes in the source database need to be replicated to the target 3 The server processes the rows by querying their data from the source database tables and duplicating the logged action insert update delete to the target database according to the specifications defined by the replication schema Rows are processed in FIFO order i e in exactly the same order that they were put into the log by the triggers The operation specified by the log record is applied to rows and columns of the tables in the target database gt An insert is duplicated by inserting a new target row having the same primary key values and the same values for each column that is specified for replication gt An update is replicated by finding the row with the same primary key and updating the replicated columns to their new values gt A delete is replicated by finding the row with the same primary key and deleting it Clearly it is essential that both source and target table must have primary keys or at least unique column sets that can be treated as keys T
185. urn becomes a source for another target and so on down a hierarchy An example of cascading replication might be where Head Office replicates to a regional office which then replicate to a branch The cascade model might be combined with a Central to Branch schema see below so that each level is replicating separate sets of data to a number of levels below it 2013 IBPhoenix Editors 22 IBP Replicator 4 1 Source bl 9 IBReplicator Server Cascade Le ESI In a Central to Branch schema subsets of the central database are designated for replication to branch sites Data at the centre is horizontally partitioned branch by branch Usually centrral data sent to branches is read only However this schema is sometimes combined with Peer to Peer so that branches update their sets locally and it is replicated back to the centre Central to Branch 2013 IBPhoenix Editors Chapter 5 Planning for Replication 23 DataSet Data Set E Central to Branch Data Set l Data Set 1 z Hub and Spoke In a Hub and Spoke schema a central database the hub replicates bi directionally to multiple databases It has a Peer to Peer relationship with each of its spokes Cascade replication is implicit in this environment because each of the spokes receives replicated data whenever the hub database or any of the other spokes is updated
186. using Replication Manager It can be used interactively from a simple text console or in batch or cron jobs It has obvious benefits if you need to set up the same configuration on multiple sites For Linux installations cfged provides a Windows free way to configure replication For all platforms it provides a dedicated toolset for making ad hoc modification of configurations Starting cfged Using a graphical window or a shell on Linux or a command window on Windows change to the directory where the Replicator executables are located and enter the command cfged c Programs IBPhoenix Replicator gt cfged IBPhoenix Replicator version 4 1 0 Root directory is c Programs IBPhoenix Replicator gt OPEN REPLCFG gt SHOW SCHEMAS Number Name 1 My Initial Schema 3 Outbound gt EXTRACT E Customers IBP databases replcfg TXT gt The OPEN command The OPEN command opens a configuration for editing The first parameter which is the only one not accompanied by a keyword is the absolute path or for Firebird the alias for the location of the configuration database In this screenshot a Firebird configuration database with the alias REPLCFG has been opened Any parameter that is omitted other than ROLE will be taken from the default configuration if it is set Other parameters can include TYPE with either INTERBASE ORACLE FIREBIRD as the argument as appropriate USER either the database owner or the user name
187. ut the server down and restart it Replicate now Ctrl R Instructs the server to replicate immediately without waiting for its next scheduled replication If you need only occasional replications you need not schedule replications at all simply use this command to replicate whenever you like Notifications have no effect if the replication server is not running Shutdown server Ctrl U Instructs the Replication Server to shut down immediately Conflict Resolution When something goes wrong because of a conflict between the source data and the target data you want to know about and fix it If you are checking the log you will be aware of any conflicts encountered because they are summarised there after each replication There are other places in Replication Manager where conflict information can be viewed in more detail Viewing Conflicts With the replication schema you are interested in selected either click Replication Tools View Conflicts or right click on the schema node of a defined source or target database in the Replication tree or anywhere else within that schema branch and choose View conflicts from the context menu NOTE to focus on all conflicts that may have occurred when replicating from a particular source database or to a particular target database have that database node selected If there are no conflicts the conflict viewer simply says so If there are unresolved conflicts the viewer d
188. with off line replication Replicant licences are counted when the Server process checks that there are enough Replicant licences available for all of the databases defined in the current replication schema Once a database is licensed for replication it can be involved in multiple replication schemas without the need to add more Replicant licences for it Licences are server agnostic you do not need different licences for Firebird InterBase or Oracle Licence Counting Many configurations are possible Checking is concerned only with ensuring that the count of Replicant licences is at least equal to the number of databases configured in the schema Additional Replicant licences are available Evaluation Licences You do not need to buy licences for testing IBPhoenix Replicator Just start by using the EVAL license for testing a simple one way replication schema It will supply four Replicant licences for your tests for 14 days gt For more details about IBP Replicator licensing see the topic in the IBP Replicator Requirements section gt For instructions about installing licences go to the License Manager topic 2013 IBPhoenix Editors Chapter 6 Installation and Setup 2013 IBPhoenix Editors 43 Chapter 7 Defining a Replication Schema Chapter 7 Defining a Replication Schema 45 Chapter 7 Defining a Replication Schema After registering all the databases that a
189. zation option form the context menu The same dialog appears but this time with just that table selected Creating Source System Objects The final step once the rest of the replication schema has been defined is to ask the Replication Manager to create the tables triggers etc in the source database that will be used for the replication operations These structures are referred to as System Objects It is recommended that you perform Create system objects when you are the exclusive user on the source database particularly if the source database is on a Firebird Classic server The triggers created by IBP Replicator will be seen by other database users when the database metadata cache is refreshed On Classic each client has its own cache and won t see the changes until next time that user logs in It is less of an issue with Superserver since the cache is shared by all clients and none will see the changes until after all users have logged out As usual you have several ways to make this request This time you will be operating on the Source database so select it in the Replication tree and do one of the following gt right click on the Source database node and select Create System Objects from the context menu gt choose Replication Source Create system objects from the menu 2013 IBPhoenix Editors Chapter 7 Defining a Replication Schema 79 ix IBPReplicator File Configuration Vi

IBP Replicator 4.1

Contents

Download Pdf Manuals

Related Search

Related Contents