diff --git a/gatsby-config.js b/gatsby-config.js index 286b6b8318f..6dee48afd63 100644 --- a/gatsby-config.js +++ b/gatsby-config.js @@ -156,7 +156,6 @@ module.exports = { }, }, }, - // 'gatsby-plugin-remove-fingerprints', // speeds up Netlify, see https://github.com/narative/gatsby-plugin-remove-fingerprints 'gatsby-plugin-sitemap', { resolve: `gatsby-plugin-manifest`, diff --git a/package.json b/package.json index 7fad275c6bc..4d4427378cf 100644 --- a/package.json +++ b/package.json @@ -44,7 +44,6 @@ "gatsby-plugin-nginx-redirect": "^0.0.11", "gatsby-plugin-react-helmet": "^4.0.0", "gatsby-plugin-react-svg": "^3.0.0", - "gatsby-plugin-remove-fingerprints": "^0.0.2", "gatsby-plugin-sass": "^4.0.2", "gatsby-plugin-sharp": "^3.0.1", "gatsby-plugin-sitemap": "^3.0.0", diff --git a/product_docs/docs/bart/2.6.2/bart_inst/04_upgrading_bart.mdx b/product_docs/docs/bart/2.6.2/bart_inst/04_upgrading_bart.mdx index e09b92f586b..1c68fe7f7a8 100644 --- a/product_docs/docs/bart/2.6.2/bart_inst/04_upgrading_bart.mdx +++ b/product_docs/docs/bart/2.6.2/bart_inst/04_upgrading_bart.mdx @@ -10,9 +10,6 @@ legacyRedirectsGenerated: This section outlines the process of upgrading BART from an existing version to the latest version. -- [Upgrading from BART 2.0](#upgrading-from-bart-20) describes the upgrade process from BART 2.0 to the latest version. -- [Upgrading from Older Versions of BART (except 2.0)](#upgrading_from_older_versions_except_2_0_to_latest_versions_of_bart) describes the upgrade process from previous BART versions (except 2.0) to the latest version. - **Upgrade Restrictions** The following restrictions apply with regard to previous BART versions. @@ -22,9 +19,9 @@ The following restrictions apply with regard to previous BART versions. -## Upgrading from Older Versions of BART (except 2.0) +## Upgrading from Older Versions of BART -Perform the following steps to upgrade from older versions of BART (except 2.0) to the latest version: +Perform the following steps to upgrade from older versions of BART to the latest version: **Step 1:** Assume the identity of the BART user account and invoke the following command to stop the BART WAL scanner program (`bart-scanner`): @@ -62,37 +59,4 @@ The `PATH` setting should be the same as set for BART 2.6.2 since all versions u !!! Note After upgrading to the latest BART version, you must take a new full backup of your system before performing an incremental backup. - - -## Upgrading from BART 2.0 - -Perform the following steps to upgrade BART 2.0 to the latest version of BART: - -**Step 1:** Install the latest version of BART. For information about how to install, see [installing BART](02_installing_bart/#installing-bart). - -**Step 2:** Save a copy of your BART 2.0 configuration file. The default location of the BART 2.0 configuration file is `/usr/edb/bart2.0/etc/bart.cfg`. - -**Step 3:** Invoke the following command to remove BART 2.0: - - On CentOS 7: - -```text -yum remove edb-bart20 -``` - -**Step 4:** Place the BART 2.0 configuration file (`bart.cfg`) that you saved in Step 2 in the newly created `/usr/edb/bart/etc` directory. You can use many of the same configuration parameters for BART 2.6.2, but note that you must use a new directory for the BART backup catalog. A new set of full backups and incremental backups taken using BART 2.6.2 must be stored in a new BART backup catalog. - -To specify an alternative configuration file name or location, use the `-c` option with BART subcommands. For more information about the `-c` option, see the EDB Backup and Recovery Us available at the [EDB website](/bart/latest/bart_user/). - -!!! Note - The `bart.cfg` configuration file is only required on the BART 2.6.2 host from which you will invoke BART subcommands. BART does not require the `bart.cfg` file on hosts on which an incremental backup will be restored. - -**Step 5:** Adjust the setting of the `PATH` environment variable to include the location of the BART 2.6.2 executable (the `bin` subdirectory) in the `~/.bashrc` or `~/.bash_profile` files for the following user accounts: - -- The BART user account on the BART host. -- The user account on the remote host to which incremental backups will be restored. For details, see the EDB Backup and Recovery User Guide available at the [EDB website](/bart/latest/bart_user/). - -**Step 6:** Perform the BART 2.6.2 installation and BART 2.0 removal process on each remote host on which an incremental backup was restored using BART 2.0. - -!!! Note - After upgrading to the latest BART version, you must take a new full backup of your system before performing an incremental backup. + \ No newline at end of file diff --git a/product_docs/docs/efm/3.5/index.mdx b/product_docs/docs/efm/3.5/index.mdx deleted file mode 100644 index e396749c88f..00000000000 --- a/product_docs/docs/efm/3.5/index.mdx +++ /dev/null @@ -1,12 +0,0 @@ ---- -title: "EDB Postgres Failover Manager" -productStub: true -directoryDefaults: - description: "EDB Postgres Failover Manager Version 3.5 Documentation and release notes. PostgreSQL replication and failover manager for achieving high availability." - -legacyRedirectsGenerated: - # This list is generated by a script. If you need add entries, use the `legacyRedirects` key. - - "/edb-docs/p/edb-postgres-failover-manager/3.5" ---- - - diff --git a/product_docs/docs/eprs/6.2/01_introduction/01_whats_new.mdx b/product_docs/docs/eprs/6.2/01_introduction/01_whats_new.mdx index 4397735f724..c3e6bcf0b0f 100644 --- a/product_docs/docs/eprs/6.2/01_introduction/01_whats_new.mdx +++ b/product_docs/docs/eprs/6.2/01_introduction/01_whats_new.mdx @@ -6,7 +6,10 @@ title: "What’s New" The following features have been added to xDB Replication Server version 6.1 to create xDB Replication Server version 6.2: -> - Registering your xDB Replication Server product with an EnterpriseDB product license key is no longer required. Thus, all components related to registering the product have been removed. The following are the removed components: 1) the Product Registration dialog box accessed from the xDB Replication Console Help menu, 2) the `license_key` parameter located in the xDB Replication Configuration file, and 3) the xDB Replication Server CLI `registerkey` command. +> - Registering your xDB Replication Server product with an EnterpriseDB product license key is no longer required. Thus, all components related to registering the product have been removed. The following are the removed components: + - The Product Registration dialog box accessed from the xDB Replication Console Help menu + - The `license_key` parameter located in the xDB Replication Configuration file + - The xDB Replication Server CLI `registerkey` command. > - Partitioned tables created using the declarative partitioning feature of PostgreSQL and Advanced Server version 10 and later can now be replicated in a log-based single-master or multi-master replication system. For more information, see [Replicating Postgres Partitioned Tables](../07_common_operations/10_replicating_postgres_partitioned_tables/#replicating_postgres_partitioned_tables). > - In a single-master replication system, removal of a table from a publication that has one or more existing subscriptions is now permitted as long as the table to be removed is not the parent referenced in a foreign key constraint from a child table that is not being removed as well. Previously, no tables from a publication in a single-master replication system could be removed if there are existing subscriptions. For more information, see [Removing Tables from a Publication](../07_common_operations/06_managing_publication/03_updating_pub/#remove_tables_from_pub). > - Versions 11 and 12 of PostgreSQL and Advanced Server are now supported. diff --git a/product_docs/docs/eprs/6.2/01_introduction/index.mdx b/product_docs/docs/eprs/6.2/01_introduction/index.mdx index 1ee5c22a4c4..9ca64e3c427 100644 --- a/product_docs/docs/eprs/6.2/01_introduction/index.mdx +++ b/product_docs/docs/eprs/6.2/01_introduction/index.mdx @@ -2,8 +2,6 @@ title: "Introduction" --- - - This document describes the installation, configuration, architecture, and operation of the EDB xDB Replication Server. EDB xDB (cross database) Replication Server (referred to hereafter as xDB Replication Server) is an asynchronous replication system available for PostgreSQL and for EDB Postgres Advanced Server. The latter will be referred to simply as Advanced Server. xDB Replication Server can be used to implement replication systems based on either of two different replication models – single-master (primary-to-secondary) replication or multi-master replication. @@ -32,10 +30,12 @@ For multi-master replication, xDB Replication Server supports the following conf - Between PostgreSQL database servers - Between PostgreSQL database servers and Advanced Servers in PostgreSQL compatible mode +- Between Advanced Servers in PostgreSQL compatible mode +- Between Advanced Servers in Oracle compatible mode The reader is assumed to have basic SQL knowledge and basic Oracle, SQL Server, or PostgreSQL database administration skills (whichever are applicable) so that databases, users, schemas, and tables can be created and database object privileges assigned. -- The remainder of Chapter 1 describes conventions used throughout this user’s guide along with suggested sections to read based upon your purpose for using this guide. +- The remainder of Chapter [Introduction](../01_introduction/#introduction) describes conventions used throughout this user’s guide along with suggested sections to read based upon your purpose for using this guide. - Chapter [Overview](../02_overview/#overview) provides an overview of xDB Replication Server including basic replication concepts and definitions, architecture and components of xDB Replication Server, and design guidelines for setting up a replication system. - Chapter [Installation and Uninstallation](../03_installation/#installation) gives instructions for installing and uninstalling xDB Replication Server. - Chapter [Introduction to the xDB Replication Console](../04_intro_xdb_console/#intro_xdb_console) provides an overview of the xDB Replication Console, the graphical user interface for using xDB Replication Server. diff --git a/product_docs/docs/eprs/6.2/02_overview/01_why_replication/01_offloading_reporting_and_bi_queries.mdx b/product_docs/docs/eprs/6.2/02_overview/01_why_replication/01_offloading_reporting_and_bi_queries.mdx index 1f9e76c2350..365b8969a96 100644 --- a/product_docs/docs/eprs/6.2/02_overview/01_why_replication/01_offloading_reporting_and_bi_queries.mdx +++ b/product_docs/docs/eprs/6.2/02_overview/01_why_replication/01_offloading_reporting_and_bi_queries.mdx @@ -2,8 +2,6 @@ title: "Offloading Reporting and Business Intelligence Queries" --- - - In this use case, users take all or just a subset of data from a production OLTP system and replicate it to another database whose sole purpose is to support reporting queries. This can have multiple benefits: 1. Reporting loads are removed from the OLTP system, improving transaction processing performance. diff --git a/product_docs/docs/eprs/6.2/02_overview/02_replication_concepts_and_definitions/01_smr_mmr_comparison.mdx b/product_docs/docs/eprs/6.2/02_overview/02_replication_concepts_and_definitions/01_smr_mmr_comparison.mdx index 11f21326332..9cfdedb8354 100644 --- a/product_docs/docs/eprs/6.2/02_overview/02_replication_concepts_and_definitions/01_smr_mmr_comparison.mdx +++ b/product_docs/docs/eprs/6.2/02_overview/02_replication_concepts_and_definitions/01_smr_mmr_comparison.mdx @@ -2,10 +2,6 @@ title: "Comparison of Single-Master and Multi-Master Replication" --- - - -In write-intensive applications, multi-master replication allows you to utilize multiple database servers on separate hosts to process write transactions independently of each other on their own primary databases. Changes can then be reconciled across primary databases according to your chosen schedule. - There are two models of replication systems supported by xDB Replication Server: - **Single-Master Replication (SMR).** Changes (inserts, updates, and deletions) to table rows are allowed to occur in a designated primary database. These changes are replicated to tables in one or more secondary databases. The replicated tables in the secondary databases are not permitted to accept any changes except from its designated primary database. (This is also known as primary-to-secondary replication.) diff --git a/product_docs/docs/eprs/6.2/02_overview/02_replication_concepts_and_definitions/02_publications_and_subscriptions.mdx b/product_docs/docs/eprs/6.2/02_overview/02_replication_concepts_and_definitions/02_publications_and_subscriptions.mdx index e1e285cb05e..c2c22e840ce 100644 --- a/product_docs/docs/eprs/6.2/02_overview/02_replication_concepts_and_definitions/02_publications_and_subscriptions.mdx +++ b/product_docs/docs/eprs/6.2/02_overview/02_replication_concepts_and_definitions/02_publications_and_subscriptions.mdx @@ -33,16 +33,28 @@ The preceding diagram illustrates that a table that has been created as a member The following diagram illustrates a multi-master replication system with three primary nodes. -![Publications in one database replicating to subscriptions in another database](/../../images/image3.png) +![Publications in one database replicating to subscriptions in another database](../../images/image3.png) -![Publications replicating to two subscription databases](/../../images/image4.png) +**Publications in one database replicating to subscriptions in another database** -![*Publications in two databases replicating to one subscription database*](/../../images/image5.png) -![*Cascading Replication: Tables used in both a subscription and a publication*](/../../images/image6.png) + +![Publications replicating to two subscription databases](../../images/image4.png) + +**Publications replicating to two subscription databases** + +![*Publications in two databases replicating to one subscription database*](../../images/image5.png) + +**Publications in two databases replicating to one subscription database** + +![*Cascading Replication: Tables used in both a subscription and a publication*](../../images/image6.png) + +**Cascading Replication: Tables used in both a subscription and a publication** The preceding diagram illustrates that a table that has been created as a member of a subscription can be used in a publication replicating to another subscription. This scenario is called cascading replication. The following diagram illustrates a multi-master replication system with three primary nodes. -![*Multi-master replication system*](/../../images/image7.png) +![*Multi-master replication system*](../../images/image7.png) + +**Multi-master replication system** diff --git a/product_docs/docs/eprs/6.2/02_overview/02_replication_concepts_and_definitions/03_smr_replication.mdx b/product_docs/docs/eprs/6.2/02_overview/02_replication_concepts_and_definitions/03_smr_replication.mdx index 7e72e181b5c..a243c1e9e7f 100644 --- a/product_docs/docs/eprs/6.2/02_overview/02_replication_concepts_and_definitions/03_smr_replication.mdx +++ b/product_docs/docs/eprs/6.2/02_overview/02_replication_concepts_and_definitions/03_smr_replication.mdx @@ -10,4 +10,6 @@ Generally, changes must not be made to the definitions of the publication tables Changes must not be made to the rows of the subscription tables. If such changes are made, they are not propagated back to the publication. If changes are made to the subscription table rows, it is fairly likely that the rows will no longer match their publication counterparts. There is also a risk that future replication attempts may fail. -![Single-Master (Primary-to-secondary) replication](/../../images/image8.png) +![Single-Master (Primary-to-secondary) replication](../../images/image8.png) + +**Single-Master (Primary-to-secondary) replication** diff --git a/product_docs/docs/eprs/6.2/02_overview/02_replication_concepts_and_definitions/04_mmr_replication.mdx b/product_docs/docs/eprs/6.2/02_overview/02_replication_concepts_and_definitions/04_mmr_replication.mdx index 5e685917155..f594f629248 100644 --- a/product_docs/docs/eprs/6.2/02_overview/02_replication_concepts_and_definitions/04_mmr_replication.mdx +++ b/product_docs/docs/eprs/6.2/02_overview/02_replication_concepts_and_definitions/04_mmr_replication.mdx @@ -23,4 +23,6 @@ Once the multi-master replication system is defined, changes (inserts, updates, Generally, changes must not be made to the table definitions in any of the primary nodes including the primary definition node. If such changes are made, they are not propagated to other nodes in the multi-master replication system unless they are made using the DDL change replication feature described in [Replicating DDL Changes](../../07_common_operations/08_replicating_ddl_changes/#replicating_ddl_changes). If changes are made to tables without using the DDL change replication feature, there is a risk that future replication attempts may fail. -![In a multi-master replication system, table rows can be updated at any primary node](/../../images/image9.png) +![In a multi-master replication system, table rows can be updated at any primary node](../../images/image9.png) + +**In a multi-master replication system, table rows can be updated at any primary node** diff --git a/product_docs/docs/eprs/6.2/02_overview/02_replication_concepts_and_definitions/09_sync_replication_trigger_based.mdx b/product_docs/docs/eprs/6.2/02_overview/02_replication_concepts_and_definitions/09_sync_replication_trigger_based.mdx index 0ef1cc6fb76..f8b3e1e4689 100644 --- a/product_docs/docs/eprs/6.2/02_overview/02_replication_concepts_and_definitions/09_sync_replication_trigger_based.mdx +++ b/product_docs/docs/eprs/6.2/02_overview/02_replication_concepts_and_definitions/09_sync_replication_trigger_based.mdx @@ -6,7 +6,13 @@ title: "Synchronization Replication with the Trigger-Based Method" If a publication in a single-master replication system is created that will be used in synchronization replications with the trigger-based method, the publication server installs an insert trigger, an update trigger, and a delete trigger on each publication table. In a multi-master replication system, each replicated table in each primary node employing the trigger-based method has an insert trigger, an update trigger, and a delete trigger. -The publication server also creates a shadow table for each source table on which triggers have been created. A shadow table is a table used by xDB Replication Server to record the changes (inserts, updates, and deletions) made to a given source table. A shadow table records three types of record ../../images: For each row inserted into the source table, the shadow table records the image of the inserted row. For each existing row that is updated in the source table, the shadow table records the after image of the updated row. For each row deleted from the source table, the shadow table records the primary key value of the deleted row. +The publication server also creates a shadow table for each source table on which triggers have been created. A shadow table is a table used by xDB Replication Server to record the changes (inserts, updates, and deletions) made to a given source table. A shadow table records three types of record images: + +- For each row inserted into the source table, the shadow table records the image of the inserted row. + +- For each existing row that is updated in the source table, the shadow table records the after image of the updated row. + +- For each row deleted from the source table, the shadow table records the primary key value of the deleted row. !!! Note In a multi-master replication system, the before image of an updated row is also stored in the shadow table in order to perform update conflict detection. See [Conflict Resolution](../../06_mmr_operation/06_conflict_resolution/#conflict_resolution) for information on conflict detection in a multi-master replication system. diff --git a/product_docs/docs/eprs/6.2/02_overview/02_replication_concepts_and_definitions/10_sync_replication_log_based/04_replication_origin.mdx b/product_docs/docs/eprs/6.2/02_overview/02_replication_concepts_and_definitions/10_sync_replication_log_based/04_replication_origin.mdx index bda34e9666e..f3b163b5097 100644 --- a/product_docs/docs/eprs/6.2/02_overview/02_replication_concepts_and_definitions/10_sync_replication_log_based/04_replication_origin.mdx +++ b/product_docs/docs/eprs/6.2/02_overview/02_replication_concepts_and_definitions/10_sync_replication_log_based/04_replication_origin.mdx @@ -40,6 +40,8 @@ The total number of primary nodes is six. Multiply the number of primary node da The following table shows the required, minimum settings for `max_replication_slots` as well as `max_wal_senders`. +**Table 2-1: Replication Origin Configuration Parameter Settings** + | | | | | ---------------------------------------------------------- | ------------------- | -------------------------------- | | **Postgres Database Server** | **max_wal_senders** | **max_replication_slots** | @@ -47,7 +49,8 @@ The following table shows the required, minimum settings for `max_replication_sl |


Cluster #2 (2 primary nodes)

| 2 |


12

| |


Cluster #3 (1 primary node)

| 1 |


6

| -**Replication Origin Configuration Parameter Settings** + + If the `max_replication_slots` parameter is not set to a high enough value, synchronization replication still succeeds, but without the replication origin performance advantage. diff --git a/product_docs/docs/eprs/6.2/02_overview/02_replication_concepts_and_definitions/11_requirements_and_restrictions.mdx b/product_docs/docs/eprs/6.2/02_overview/02_replication_concepts_and_definitions/11_requirements_and_restrictions.mdx deleted file mode 100644 index 0a72686f160..00000000000 --- a/product_docs/docs/eprs/6.2/02_overview/02_replication_concepts_and_definitions/11_requirements_and_restrictions.mdx +++ /dev/null @@ -1,32 +0,0 @@ ---- -title: "Requirements and Restrictions" ---- - - - -The following are the general requirements and restrictions when using the log-based method for any database of a single-master or multi-master replication system: - -- The selection of either the trigger-based method or the log-based method is a characteristic applicable to only the publication database. The choice is made when defining the primary database of a single-master replication system (see Section [Adding a Publication Database](../../05_smr_operation/02_creating_publication/02_adding_pub_database/#adding_pub_database)) or the primary definition node of a multi-master replication system (see [Adding the Primary definition node](../../06_mmr_operation/02_creating_publication_mmr/#adding_pdn)). -- The logical decoding feature, and hence the log-based method, is supported beginning with PostgreSQL version 9.4. Therefore, in order to use the log-based method for a publication database, that publication database must be running under PostgreSQL version 9.4 or later, or under Advanced Server version 9.4 or later. -- In a single-master replication system, whether the primary database uses the trigger-based method or the log-based method has no additional impact on the rules for choosing the subscription database. For example, even if the log-based method is chosen for the primary database, the subscription database may be running on Postgres version 9.4 as well as any supported, earlier version of Postgres, as well as Oracle or SQL Server. -- In a single-master replication system, the primary database may contain one or more publications (that is, named sets of tables for replication). This is applicable to a primary database using either the trigger-based method or the log-based method. -- It is permissible to have multiple, single-master replication systems running under a publication server where some primary databases may use the trigger-based method while others use the log-based method. -- In a multi-master replication system, the selection of either the trigger-based method or the log-based method on the primary definition node determines the method for all other primary nodes. In other words, if the trigger-based method is chosen for the primary definition node, then all other primary nodes will use the trigger-based method. If the log-based method is chosen for the primary definition node, then all other primary nodes will use the log-based method. -- As a consequence of the restriction described in the preceding bullet point, in order to use the log-based method for a multi-master replication system, all of the primary nodes of the system must be running under Postgres version 9.4 or later, and all such Postgres database clusters must be configured to use logical decoding for the log-based method. - -Selection of the log-based method for any database impacts the configuration of the Postgres database cluster containing that database. - -If you plan to use the log-based method with any publication database running under a Postgres database server, the following configuration parameter settings are required in the configuration file, `postgresql.conf`, of that Postgres database server: - -- `wal_level.` Set to logical. -- `max_wal_senders.` Specifies the maximum number of concurrent connections (that is, the maximum number of simultaneously running WAL sender processes). Set at minimum, to the total number of primary databases of single-master replication systems and primary nodes of multi-master replication systems on this database server that will use the log-based method. -- `max_replication_slots.` Specifies the maximum number of replication slots. If the database server supports both single-master replication systems and multi-master replication systems, then max_replication_slots must be set at minimum to the sum of the requirements for both replication systems. For support of SMR systems, the minimum requirement is the total number of primary databases of the single-master replication systems that will use the log-based method. For support of MMR systems, the minimum requirement is the total number of primary nodes in the multi-master replication system multiplied by the number of primary nodes residing on this database server. For information, see [Replication Origin](10_sync_replication_log_based/04_replication_origin/#replication_origin). -- `track_commit_timestamp.` Set to `on`. This configuration parameter applies only to Postgres database servers of version 9.5 and later. See [Configuration Parameter and Table Setting Requirements](../../06_mmr_operation/06_conflict_resolution/01_configuration_para_andtable_setting/#configuration_para_and_table_setting) for additional information. - -Also, see [Enabling Synchronization Replication with the Log-Based Method](../../05_smr_operation/01_prerequisites/02_enable_sync_replication_with_log-based_method/#enable_sync_replication_with_log-based_method) for setting these parameters for a single-master replication system. See [Enabling Synchronization Replication with the Log-Based Method](../../06_mmr_operation/01_pre_steps/#enabling_sync_replication_log-based_method_mmr) for a multi-master replication system. - -In addition, the `pg_hba.conf` configuration file of the Postgres database server must contain an entry permitting `REPLICATION` access for each database using the log-based method running on the database server. The access must be permitted to the publication database user specified when creating the publication database definition using the xDB Replication Console (See [Adding a Publication Database](../../05_smr_operation/02_creating_publication/02_adding_pub_database/#adding_pub_database) for a single-master replication system or [Adding the Primary definition node](../../06_mmr_operation/02_creating_publication_mmr/#adding_pdn) for a multi-master replication system) or the xDB Replication Server Command Line Interface (CLI) (see Adding a Publication Database (addpubdb) <add_pub_database>). - -See [Postgres Server Authentication](../../05_smr_operation/01_prerequisites/06_verifying_host_accessibility/#postgres_server_auth) for setting `REPLICATION` access for a single-master replication system. See [Verifying Host Accessibility](../../05_smr_operation/01_prerequisites/06_verifying_host_accessibility/#verifying_host_accessibility) for a multi-master replication system. - -For configuration options in the publication server configuration file that are specifically applicable to the log-based method see [Log-Based Method of Synchronization Options](../../10_appendix/04_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/15_log_based_sync_options/#log_based_sync_options). diff --git a/product_docs/docs/eprs/6.2/02_overview/02_replication_concepts_and_definitions/13_table_filters.mdx b/product_docs/docs/eprs/6.2/02_overview/02_replication_concepts_and_definitions/13_table_filters.mdx index e9980346e9c..824b662d5a2 100644 --- a/product_docs/docs/eprs/6.2/02_overview/02_replication_concepts_and_definitions/13_table_filters.mdx +++ b/product_docs/docs/eprs/6.2/02_overview/02_replication_concepts_and_definitions/13_table_filters.mdx @@ -122,4 +122,4 @@ For using table filters in a multi-master replication system see the following s - Section [Adding a Publication](../../06_mmr_operation/02_creating_publication_mmr/#add_pub_mmr) for information on defining the initial set of table filters that are to be available for selective enablement on primary nodes - Section [Creating Additional Primary nodes](../../06_mmr_operation/03_creating_primary_nodes/#creating_primary_nodes) for information on enabling available table filters on a newly created primary node - Section [Updating the Set of Available Table Filters in a Publication](../../07_common_operations/06_managing_publication/04_updating_table_filters_in_pub/#updating_table_filters_in_pub) for information on adding, removing, or modifying rules comprising the set of available table filters -- Section Enabling/Disabling Table Filters on a Primary node <enable_disable_table_filters> for information on changing which table filters have been enabled on an existing primary node +- Section [Enabling/Disabling Table Filters on a Subscription](../../05_smr_operation/05_managing_subscription/04_enable_filters_on_subscription/#enable_filters_on_subscription) for information on changing which table filters have been enabled on an existing primary node diff --git a/product_docs/docs/eprs/6.2/02_overview/03_replication_server_components_and_architecture/01_physical_components.mdx b/product_docs/docs/eprs/6.2/02_overview/03_replication_server_components_and_architecture/01_physical_components.mdx index 6213546576d..56ab6da1a58 100644 --- a/product_docs/docs/eprs/6.2/02_overview/03_replication_server_components_and_architecture/01_physical_components.mdx +++ b/product_docs/docs/eprs/6.2/02_overview/03_replication_server_components_and_architecture/01_physical_components.mdx @@ -8,16 +8,20 @@ xDB Replication Server is not a single, executable program, but rather a set of The following diagram illustrates the components of xDB Replication Server and how they are used to form a complete, basic, single-master replication system. -![xDB Replication Server - physical view (single-master replication system)](/../../images/image10.png) +![xDB Replication Server - physical view (single-master replication system)](../../images/image10.png) + +**Figure 2-8: xDB Replication Server - physical view (single-master replication system)** The following diagram illustrates the components of xDB Replication Server and how they are used to form a complete, basic, multi-master replication system. -![xDB Replication Server - physical view (multi-master replication system)](/../../images/image11.png) +![xDB Replication Server - physical view (multi-master replication system)](../../images/image11.png) + +**Figure 2 9: xDB Replication Server - physical view (multi-master replication system)** The minimal configuration of xDB Replication Server for a basic replication system consists of the following software components: - **Publication server.** The program that configures the publication database and primary nodes for replication and performs replication. -- Subscription server. The program that configures the subscription database for replication and initiates replication. The subscription server is used only in single-master replication systems. +- **Subscription server.** The program that configures the subscription database for replication and initiates replication. The subscription server is used only in single-master replication systems. - **xDB Replication Configuration file.** Text file containing connection and authentication information used by the publication server and subscription server upon startup to connect to a publication database designated as the controller database. Also used to authenticate registration of the publication server and subscription server from the user interface when creating a replication system. - **xDB Startup Configuration file.** Text file containing installation and configuration information used for the Java Runtime Environment when the publication server and subscription server are started. @@ -179,7 +183,7 @@ The xDB Replication Console is the graphical user interface program you can use Through a single xDB Replication Console, you can configure and operate a replication system running on the same host on which the xDB Replication Console is installed, or you can configure and operate replication systems where the xDB Replication Server components are distributed on different hosts in a networked environment. -![xDB Replication Consoles accessing multiple hosts](/../../images/image12.png) +![xDB Replication Consoles accessing multiple hosts](../../images/image12.png) In the preceding figure, there are two Postgres installations running on two networked hosts, each with its own xDB Replication Server installation. Each host is running a publication server and a subscription server. diff --git a/product_docs/docs/eprs/6.2/02_overview/03_replication_server_components_and_architecture/03_xdb_replication_system_examples.mdx b/product_docs/docs/eprs/6.2/02_overview/03_replication_server_components_and_architecture/03_xdb_replication_system_examples.mdx index 680e682ae8d..7da3fe705d6 100644 --- a/product_docs/docs/eprs/6.2/02_overview/03_replication_server_components_and_architecture/03_xdb_replication_system_examples.mdx +++ b/product_docs/docs/eprs/6.2/02_overview/03_replication_server_components_and_architecture/03_xdb_replication_system_examples.mdx @@ -12,7 +12,9 @@ In the accompanying diagrams, the logical components, represented by nodes in th The following is an illustration of a basic Oracle to PostgreSQL or Advanced Server single-master replication system. A single publication in Oracle contains tables from two schemas that are replicated to a database residing in either PostgreSQL or Advanced Server. -![Oracle to PostgreSQL or Advanced Server replication](/../../images/image13.png) +![Oracle to PostgreSQL or Advanced Server replication](../../images/image13.png) + +**Figure 2-11: Oracle to PostgreSQL or Advanced Server replication** The following describes the logical components in the preceding diagram: \* The publication server to be used is identified by registering its network location, user name, and password. @@ -24,7 +26,11 @@ The following describes the logical components in the preceding diagram: \* The The following screen capture shows how the logical components of this replication system appear in the xDB Replication Console replication tree. -![Oracle to Postgres replication tree](/../../images/image14.png) +![Oracle to Postgres replication tree](../../images/image14.png) + +**Figure 2-12: Oracle to Postgres replication tree** + + See Chapter [Introduction to the xDB Replication Console](../../04_intro_xdb_console/#intro_xdb_console) for an introduction to the xDB Replication Console. @@ -32,7 +38,9 @@ See Chapter [Introduction to the xDB Replication Console](../../04_intro_xdb_con The following is an illustration of a basic SQL Server to PostgreSQL or Advanced Server single-master replication system. A single publication in SQL Server contains tables from two schemas that are replicated to a database residing in either PostgreSQL or Advanced Server. -![SQL Server to PostgreSQL or Advanced Server replication](/../../images/image15.png) +![SQL Server to PostgreSQL or Advanced Server replication](../../images/image15.png) + +**Figure 2-13: SQL Server to PostgreSQL or Advanced Server replication** The following describes the logical components in the preceding diagram: @@ -45,7 +53,9 @@ The following describes the logical components in the preceding diagram: The following screen capture shows how the logical components of this replication system appear in the xDB Replication Console replication tree. -![SQL Server to Postgres replication tree](/../../images/image16.png) +![SQL Server to Postgres replication tree](../../images/image16.png) + +**Figure 2-14: SQL Server to Postgres replication tree** See Chapter [Introduction to the xDB Replication Console](../../04_intro_xdb_console/#intro_xdb_console) for an introduction to the xDB Replication Console. @@ -53,7 +63,9 @@ See Chapter [Introduction to the xDB Replication Console](../../04_intro_xdb_con The following is an illustration of a basic Advanced Server to Oracle single-master replication system. A single publication in an Advanced Server database contains tables from two schema that are replicated to an Oracle database. -![Advanced Server to Oracle replication](/../../images/image17.png) +![Advanced Server to Oracle replication](../../images/image17.png) + +**Figure 2-15: Advanced Server to Oracle replication** The following describes the logical components in the preceding diagram: @@ -66,7 +78,10 @@ The following describes the logical components in the preceding diagram: The following screen capture shows how the logical components of this replication system appear in the xDB Replication Console replication tree. -![Advanced Server to Oracle replication tree](/../../images/image18.png) +![Advanced Server to Oracle replication tree](../../images/image18.png) + +**Figure 2-16: Advanced Server to Oracle replication tree** + See Chapter [Introduction to the xDB Replication Console](../../04_intro_xdb_console/#intro_xdb_console) for an introduction to the xDB Replication Console. @@ -74,7 +89,9 @@ See Chapter [Introduction to the xDB Replication Console](../../04_intro_xdb_con The following is an illustration of a basic PostgreSQL to Oracle single-master replication system. A single publication in a PostgreSQL database contains tables from two schemas that are replicated to an Oracle database. WAL based method as well as trigger-based method is supported in this type of replication. -![PostgreSQL to Oracle replication](/../../images/PG_to_oracle.png) +![PostgreSQL to Oracle replication](../../images/PG_to_oracle.png) + +**Figure 2-16: PostgreSQL to Oracle replication** The following describes the logical components in the preceding diagram: @@ -87,13 +104,17 @@ The following describes the logical components in the preceding diagram: The following screen capture shows how the logical components of this replication system appear in the xDB Replication Console replication tree. -![PostgreSQL to Oracle replication tree](/../../images/PG_to_oracle_sc.png) +![PostgreSQL to Oracle replication tree](../../images/PG_to_oracle_sc.png) + +**Figure 2-17: PostgreSQL to Oracle replication tree** ## PostgreSQL or Advanced Server to SQL Server Replication The following is an illustration of a basic PostgreSQL or Advanced Server to SQL Server single-master replication system. A single publication in a PostgreSQL or Advanced Server database contains tables from two schemas that are replicated to a SQL Server database. -![PostgreSQL or Advanced Server to SQL Server replication](/../../images/image19.png) +![PostgreSQL or Advanced Server to SQL Server replication](../../images/image19.png) + +**Figure 2-18: PostgreSQL or Advanced Server to SQL Server replication** The following describes the logical components in the preceding diagram: @@ -106,7 +127,9 @@ The following describes the logical components in the preceding diagram: The following screen capture shows how the logical components of this replication system appear in the xDB Replication Console replication tree. -![Postgres to SQL Server replication tree](/../../images/image20.png) +![Postgres to SQL Server replication tree](../../images/image20.png) + +**Figure 2-19: Postgres to SQL Server replication tree** See [Introduction to the xDB Replication Console](../../04_intro_xdb_console/#intro_xdb_console) for an introduction to the xDB Replication Console. @@ -114,7 +137,9 @@ See [Introduction to the xDB Replication Console](../../04_intro_xdb_console/#in The following is an illustration of a basic Postgres multi-master replication system. A publication in a Postgres primary definition node contains tables from two schemas that are initially replicated to two other Postgres primary nodes. The tables in all three primary nodes can then be updated and synchronized with each other. -![Postgres multi-master replication system](/../../images/image21.png) +![Postgres multi-master replication system](../../images/image21.png) + +**Figure 2-20: Postgres multi-master replication system** The following describes the logical components in the preceding diagram: @@ -127,6 +152,8 @@ The following describes the logical components in the preceding diagram: The following screen capture shows how the logical components of this replication system appear in the xDB Replication Console replication tree. -![Postgres multi-master replication tree](/../../images/image22.png) +![Postgres multi-master replication tree](../../images/image22.png) + +**Figure 2-21: Postgres multi-master replication tree** See Chapter [Introduction to the xDB Replication Console](../../04_intro_xdb_console/#intro_xdb_console) for an introduction to the xDB Replication Console. diff --git a/product_docs/docs/eprs/6.2/02_overview/04_design_replication_system/02_design_considerations.mdx b/product_docs/docs/eprs/6.2/02_overview/04_design_replication_system/02_design_considerations.mdx index e884059af0d..9051ba231a9 100644 --- a/product_docs/docs/eprs/6.2/02_overview/04_design_replication_system/02_design_considerations.mdx +++ b/product_docs/docs/eprs/6.2/02_overview/04_design_replication_system/02_design_considerations.mdx @@ -19,6 +19,17 @@ Keep the following points in mind when designing a replication system: - A table that is created as a result of a subscription can be used in another publication. Thus, a publication can replicate data to a subscription which in turn, can be used in a publication to replicate to another subscription, thus creating a cascaded replication architecture. - There are restrictions on the combinations and configurations of database servers that can be used for a publication and its subscription. See [Advanced Server Compatibility Configuration Modes](../../10_appendix/02_upgrading_to_xdb6_2/01_permitted_conf_and_permutations/#adv_server_compatibility_conf_modes) for details on these restrictions. - All replication system components must be running in order for replication to occur, or before performing any configuration, operation, or modification in the replication system. (The xDB Replication Console is used for the configuration and modification of a replication system. The xDB Replication Console does not need to be running in order for replication to occur.) -- In general, the order of creation of a replication system is as follows: 1) Create the required physical databases, database user names, tables, and views to be used in the replication system. 2) Define the replication system logical components using the xDB Replication Console or xDB Replication Server CLI. 3) Perform replication. -- In general, the order of removal of a single-master replication system is as follows: 1) Remove the replication system logical components using the xDB Replication Console or xDB Replication Server CLI starting with the subscriptions (Subscription nodes) and then their parent components (Subscription Database nodes). 2) Unregister the subscription server if you no longer have any need for it. 3) Repeat the same process for the publications. 4) After all replication system logical components have been removed (except for possibly the publication server and subscription server) you can drop any of the physical database objects in Oracle, SQL Server, or Postgres. Do not drop the control schema objects manually, for example by using an SQL command line utility. Doing so may cause the xDB Replication Console and xDB Replication Server CLI to become inoperable. (See [Deleting the Control Schema and Control Schema Objects](../../10_appendix/03_resolving_problems/04_troubleshooting_areas/#del_control_schema_and%20objects) if this problem occurs.) Deleting the replication system logical components using the xDB Replication Console or xDB Replication Server CLI automatically drops the control schema objects from the physical database. -- The order of removal of a multi-master replication system is as follows: 1) Remove the replication system logical components using the xDB Replication Console or xDB Replication Server CLI starting with the publication database definitions of the non-PDN nodes. 2) Remove the publication from under the primary definition node. 3) Remove the publication database definition of the primary definition node. 4) After all replication system logical components have been removed (except for possibly the publication server) you can drop any of the physical database objects in Postgres. Do not drop the control schema objects manually, for example by using an SQL command line utility. Doing so may cause the xDB Replication Console and xDB Replication Server CLI to become inoperable. +- In general, the order of creation of a replication system is as follows: + - Create the required physical databases, database user names, tables, and views to be used in the replication system. + - Define the replication system logical components using the xDB Replication Console or xDB Replication Server CLI. + - Perform replication. +- In general, the order of removal of a single-master replication system is as follows: + - Remove the replication system logical components using the xDB Replication Console or xDB Replication Server CLI starting with the subscriptions (Subscription nodes) and then their parent components (Subscription Database nodes). + - Unregister the subscription server if you no longer have any need for it. + - Repeat the same process for the publications. + - After all replication system logical components have been removed (except for possibly the publication server and subscription server) you can drop any of the physical database objects in Oracle, SQL Server, or Postgres. Do not drop the control schema objects manually, for example by using an SQL command line utility. Doing so may cause the xDB Replication Console and xDB Replication Server CLI to become inoperable. (See [Deleting the Control Schema and Control Schema Objects](../../10_appendix/03_resolving_problems/04_troubleshooting_areas/#del_control_schema_and%20objects) if this problem occurs.) Deleting the replication system logical components using the xDB Replication Console or xDB Replication Server CLI automatically drops the control schema objects from the physical database. +- The order of removal of a multi-master replication system is as follows: + - Remove the replication system logical components using the xDB Replication Console or xDB Replication Server CLI starting with the publication database definitions of the non-PDN nodes. + - Remove the publication from under the primary definition node. + - Remove the publication database definition of the primary definition node. + - After all replication system logical components have been removed (except for possibly the publication server) you can drop any of the physical database objects in Postgres. Do not drop the control schema objects manually, for example by using an SQL command line utility. Doing so may cause the xDB Replication Console and xDB Replication Server CLI to become inoperable. diff --git a/product_docs/docs/eprs/6.2/02_overview/04_design_replication_system/03_restrictions_on_replicated_database_objects.mdx b/product_docs/docs/eprs/6.2/02_overview/04_design_replication_system/03_restrictions_on_replicated_database_objects.mdx index b3513be221e..3ecc428ee67 100644 --- a/product_docs/docs/eprs/6.2/02_overview/04_design_replication_system/03_restrictions_on_replicated_database_objects.mdx +++ b/product_docs/docs/eprs/6.2/02_overview/04_design_replication_system/03_restrictions_on_replicated_database_objects.mdx @@ -38,7 +38,6 @@ Oracle tables that include the following data types cannot be replicated: - `BINARY_DOUBLE` - `BINARY_FLOAT` - `MLSLABEL` -- `XMLTYPE` Oracle tables with the following data types can be used in snapshot-only publications, but cannot be used in synchronization replications: @@ -58,7 +57,7 @@ SQL Server tables that include the following data types cannot be replicated: - `SQL_VARIANT` !!! Note - See Replicating the SQL Server SQL_VARIANT Data Type <replicating_sql_server_sql_variant_data_type> for a method to replicate tables containing the `SQL_VARIANT` data type under certain conditions. + See [Replicating the SQL Server SQL_VARIANT Data Type](../../10_appendix/04_miscellaneous_xdb_processing_topics/06_replicating_sql_server_sql_variant_data_type/#replicating_sql_server_sql_variant_data_type) for a method to replicate tables containing the `SQL_VARIANT` data type under certain conditions. SQL Server tables with the following data types can be used in snapshot-only publications, but cannot be used in synchronization replications: diff --git a/product_docs/docs/eprs/6.2/02_overview/04_design_replication_system/05_distributed_replication.mdx b/product_docs/docs/eprs/6.2/02_overview/04_design_replication_system/05_distributed_replication.mdx index decfddc910b..12d83e7c687 100644 --- a/product_docs/docs/eprs/6.2/02_overview/04_design_replication_system/05_distributed_replication.mdx +++ b/product_docs/docs/eprs/6.2/02_overview/04_design_replication_system/05_distributed_replication.mdx @@ -18,7 +18,9 @@ The simplest implementation of a replication system is when all replication comp The Postgres publication or subscription database as the case may be, can reside in the initial database cluster that is created when Postgres is installed on the host. -![Single host replication system](/../../images/image23.png) +![Single host replication system](../../images/image23.png) + +**Figure 2-22: Single host replication system** The advantages of a single host replication system are the following: @@ -35,7 +37,10 @@ The disadvantages of a single host replication system are the following: xDB Replication Server allows you to build a replication system with either or both of the publication database and the subscription database on separate hosts. This is illustrated in the following diagram: -![Oracle database server on distributed host](/../../images/image24.png) +![Oracle database server on distributed host](../../images/image24.png) + +**Figure 2-23: Oracle database server on distributed host** + The same remote distribution can be used for the subscription database instead of, or in addition to the publication database. @@ -55,4 +60,6 @@ The disadvantages of a distributed host replication system are the following: In a multi-master replication system, the Postgres database servers running the primary nodes can be running on a single or multiple hosts. The following example illustrates two primary nodes running on database servers on separate hosts as well as a primary node running on the same database server as the publication server. -![Multi-master replication on distributed hosts](/../../images/image25.png) +![Multi-master replication on distributed hosts](../../images/image25.png) + +Figure 2-24: Multi-master replication on distributed hosts diff --git a/product_docs/docs/eprs/6.2/03_installation/01_installing_with_stackbuilder.mdx b/product_docs/docs/eprs/6.2/03_installation/01_installing_with_stackbuilder.mdx index ede0d069f13..fe315adcb3f 100644 --- a/product_docs/docs/eprs/6.2/03_installation/01_installing_with_stackbuilder.mdx +++ b/product_docs/docs/eprs/6.2/03_installation/01_installing_with_stackbuilder.mdx @@ -24,80 +24,115 @@ Follow the directions for your host operating system to install Java runtime. **Step 2:** From the host’s application menu, open the Postgres menu and choose `Stack Builder` or `StackBuilder Plus`. -![Postgres application menu](/../images/image26.png) +![Postgres application menu](../images/image26.png) + +**Figure 3-1: Postgres application menu** **Step 3 (For Linux only):** Depending upon your Linux host, a dialog box or a prompt appears requesting the root account’s password. Enter the root password and click the `OK` button. -![Enter root account password](/../images/image27.png) +![Enter root account password](../images/image27.png) + +**Figure 3-2: Enter root account password** **Step 4:** The StackBuilder Plus welcome screen appears. Select your `Postgres` installation from the drop-down list and click the `Next` button. -![StackBuilder Plus welcome screen](/../images/image28.png) +![StackBuilder Plus welcome screen](../images/image28.png) + +**Figure 3-3: StackBuilder Plus welcome screen** **Step 5 (For Advanced Server):** Expand the EnterpriseDB Tools node and check the box for Replication Server. Click the Next button. !!! Note Though the following ../images show Replication Server v6.0, use the same process for Replication Server v6.2. -![StackBuilder Plus applications](/../images/image29.png) +![StackBuilder Plus applications](../images/image29.png) + +**Figure 3-4: StackBuilder Plus applications** **Step 5 (For PostgreSQL):** Expand the Registration-Required and Trial Products node, and then expand the EnterpriseDB Tools node. Check the box for `Replication Server` under the `EnterpriseDB Tools` list and click the `Next` button. -![Stack Builder applications](/../images/image30.png) +![Stack Builder applications](../images/image30.png) -![EnterpriseDB Tools for PostgreSQL](/../images/image31.png) +**Figure 3-5: Stack Builder applications** + +![EnterpriseDB Tools for PostgreSQL](../images/image31.png) + +**Figure 3-6: EnterpriseDB Tools for PostgreSQL** **Step 6 (For Advanced Server only):** In the `Account Registration` screen, either enter your email address and password for your EnterpriseDB user account if you have one, or click the link in which case you will be directed to the registration page of the EnterpriseDB website where you can create an account. Click the `Next` button. !!! Note (For PostgreSQL only): Proceed to Step 7. If you are using PostgreSQL, account registration occurs later in the process. -![EnterpriseDB account registration](/../images/image32.png) +![EnterpriseDB account registration](../images/image32.png) + +**Figure 3-7: EnterpriseDB account registration** **Step 7:** Verify that Replication Server appears in the list of selected packages. Click the `Next` button. -![Selected packages](/../images/image33.png) +![Selected packages](../images/image33.png) + +**Figure 3-8: Selected packages** An information box appears showing the download progress of the Replication Server package. This may take a few minutes. -![Downloading progress](/../images/image34.png) +![Downloading progress](../images/image34.png) + +**Figure 3-9: Downloading progress** **Step 8:** When downloading of the Replication Server package completes, the following screen appears that starts the installation of xDB Replication Server. Click the `Next` button. !!! Note You can check the Skip Installation box if you wish to install xDB Replication Server some other time. -![Start installation](/../images/image35.png) +![Start installation](../images/image35.png) + +**Figure 3-10: Start installation** **Step 9:** Select the installation language and click the `OK` button. -![Installation language](/../images/image36.png) +![Installation language](../images/image36.png) + +**Figure 3-11: Installation language** **Step 10:** In the Setup xDB Replication Server screen, click the `Next` button. -![Installation language](/../images/image37.png) +![Installation language](../images/image37.png) + +**Figure 3-12: Setup xDB Replication Server** **Step 11:** Read the license agreement. If you accept the agreement, select the accept radio button and click the `Next` button. -![Installation language](/../images/image38.png) +![Installation language](../images/image38.png) + +**Figure 3-13: License agreement** **Step 12:** Browse to a directory where you want the xDB Replication Server components installed, or allow it to install the components in the default location shown. Click the `Next` button. -![Installation directory](/../images/image39.png) +![Installation directory](../images/image39.png) + +**Figure 3-14: Installation directory** **Step 13:** If you do not want a particular xDB Replication Server component installed on this particular host, uncheck the box `Next` to the component name. Click the `Next` button. -![Select components](/../images/image40.png) +![Select components](../images/image40.png) + +**Figure 3-15: Select components** + **Step 14:** In the Account Registration screen select the radio button that applies to you. Click the `Next` button. -![Account registration](/../images/image41.png) +![Account registration](../images/image41.png) + +**Figure 3-16: Account registration** If you do not have an EnterpriseDB user account, you will be directed to the registration page of the EnterpriseDB website. If you already have an EnterpriseDB user account, enter the email address and password for your EnterpriseDB user account as shown in the following screen. Click the `Next` button. -![My EnterpriseDB account](/../images/image42.png) +![My EnterpriseDB account](../images/image42.png) + +**Figure 3-17: My EnterpriseDB account** **Step 15:** Enter information for the xDB administrator. @@ -109,36 +144,52 @@ Enter values for the following fields: - `Admin User.` The xDB administrator user name to authenticate certain usage of the xDB Replication Server such as registering a publication server or a subscription server running on this host. Any alphanumeric string may be entered for the admin user name. The default admin user name is admin. - `Admin Password.` Password of your choice for the xDB administrator given in the Admin User field. -![xDB admin user information](/../images/image43.png) +![xDB admin user information](../images/image43.png) + +**Figure 3-18: xDB admin user information** The admin user and the admin password (in encrypted form) are saved to the xDB Replication Configuration file named `/etc/edb-repl.conf (XDB_HOME\etc\edb-repl.conf` on Windows hosts). Click the `Next` button. **Step 16 (Only if publication server is a selected component):** Enter an available port on which the publication server will run. Default port number is 9051. Click the `Next` button. -![xDB admin user information](/../images/image44.png) +![xDB admin user information](../images/image44.png) + +**Figure 3-19: Publication server details** **Step 17 (Only if subscription server is a selected component):** Enter an available port on which the subscription server will run. Default port number is 9052. Click the `Next` button. -![Subscription server details](/../images/image45.png) +![Subscription server details](../images/image45.png) + +**Figure 3-20: Subscription server details** **Step 18:** For the operating system account under which the publication server or subscription server is to run, enter `postgres` (`enterprisedb` if you are using Advanced Server installed in Oracle compatible configuration mode). -![Publication/subscription server operating system account](/../images/image46.png) +![Publication/subscription server operating system account](../images/image46.png) + +**Figure 3-21: Publication/subscription server operating system account** **Step 19:** On the Ready to Install screen, click the `Next` button. -![Ready to install](/../images/image47.png) +![Ready to install](../images/image47.png) + +**Figure 3-22: Ready to install** An information box appears showing the installation progress of the xDB Replication Server selected components. This may take a few minutes. -![Installation progress](/../images/image48.png) +![Installation progress](../images/image48.png) + +**Figure 3-23: Installation progress** **Step 20:** When installation has completed the following screen appears. Click the Finish button. -![xDB Replication Server installation completion](/../images/image49.png) +![xDB Replication Server installation completion](../images/image49.png) + +**Figure 3-24: xDB Replication Server installation completion** **Step 21:** On the `StackBuilder Plus Installation Complete` screen, click the `Finish` button. -![StackBuilder Plus installation complete](/../images/image50.png) +![StackBuilder Plus installation complete](../images/image50.png) + +**Figure 3-25: StackBuilder Plus installation complete** Successful installation of xDB Replication Server results in the creation of directory structures and files in your host environment as described in Section [Post-Installation Host Environment](05_post_installation_host_environment/#post_installation_host_environment). diff --git a/product_docs/docs/eprs/6.2/03_installation/03_installing_rpm_package.mdx b/product_docs/docs/eprs/6.2/03_installation/03_installing_rpm_package.mdx index 54d52e77719..1e83807d376 100644 --- a/product_docs/docs/eprs/6.2/03_installation/03_installing_rpm_package.mdx +++ b/product_docs/docs/eprs/6.2/03_installation/03_installing_rpm_package.mdx @@ -25,6 +25,8 @@ Each xDB Replication Server component is available as an individual RPM package. The following table lists the RPM packages and the xDB Replication Server component it contains. +**Table 3 1: xDB Replication Server Component RPM Packages** + | | | | --------------------------------------------------- | ----------------------------------------------------------------------------- | | **Package Name** | **xDB Replication Server Component** | @@ -34,7 +36,6 @@ The following table lists the RPM packages and the xDB Replication Server compon |


`ppas-xdb-subscriber`

| Subscription server | |


`ppas-xdb-libs`

| Library files required by all components | -**xDB Replication Server Component RPM Packages** The Advanced Server server libs package must be available for access by Yum when installing any xDB RPM package component. The edb-asxx-server-libs package is a component of the Advanced Server repository package for version 9.6 or later. Step 3 shows how to enable access to the Advanced Server repository so Yum can access its server libs package. @@ -108,7 +109,9 @@ To enable the appropriate repository for installing the desired version of xDB R - To install version 6.2, enable the entry for \[`enterprisedb-xdb60`]. - To install a prior version, enable the entry for \[`enterprisedb-tools`]. -Whichever version is chosen, be sure the other entries are disabled (that is, the parameter setting is enabled=0 for the non-selected entries). For example, to access xDB Replication Server version 6.2, enable the following entry: +Whichever version is chosen, be sure the other entries are disabled (that is, the parameter setting is enabled=0 for the non-selected entries). + +For example, to access xDB Replication Server version 6.2, enable the following entry: ```text [enterprisedb-xdb60] @@ -272,4 +275,4 @@ If you have an existing xDB RPM installation, you can use yum to upgrade your re `yum` will update the `edb.repo` file to enable access to the current EDB repository, configured to connect with the credentials specified in your `edb.repo` file. Then, you can use yum to upgrade any installed packages: -> `yum upgrade ppas-xdb`. +> `yum upgrade ppas-xdb` diff --git a/product_docs/docs/eprs/6.2/03_installation/05_post_installation_host_environment.mdx b/product_docs/docs/eprs/6.2/03_installation/05_post_installation_host_environment.mdx index fc13ab3eb5d..61fe37b6fab 100644 --- a/product_docs/docs/eprs/6.2/03_installation/05_post_installation_host_environment.mdx +++ b/product_docs/docs/eprs/6.2/03_installation/05_post_installation_host_environment.mdx @@ -16,6 +16,8 @@ The Postgres application menu contains a new item for the xDB Replication Consol The following files are created that you may need during the configuration process. +**Table 3-2: Post-Installation Files** + | | | | | ---------------------------------- | ------------------------------------- | ------------------------------------------------------------------------------------ | | File Name | Location | Description | diff --git a/product_docs/docs/eprs/6.2/03_installation/06_uninstalling_xdb_replication_server.mdx b/product_docs/docs/eprs/6.2/03_installation/06_uninstalling_xdb_replication_server.mdx index a334333600a..788bf14badc 100644 --- a/product_docs/docs/eprs/6.2/03_installation/06_uninstalling_xdb_replication_server.mdx +++ b/product_docs/docs/eprs/6.2/03_installation/06_uninstalling_xdb_replication_server.mdx @@ -27,29 +27,43 @@ $ ./uninstall-xdbreplicationserver **Step 2:** Click the `Yes` button to confirm uninstallation of xDB Replication Server. -![Confirm xDB Replication Server uninstallation](/../images/image51.png) +![Confirm xDB Replication Server uninstallation](../images/image51.png) + +**Figure 3-26: Confirm xDB Replication Server uninstallation** **Step 3:** The `Uninstallation Completed` dialog box appears when the process has completed. Click the `OK` button. -![Uninstallation completed](/../images/image52.png) +![Uninstallation completed](../images/image52.png) + +**Figure 3-27: Uninstallation completed** **For Windows only:** The following steps are for uninstalling xDB Replication Server from a Windows host. **Step 1:** From the `Windows Control Panel`, select `Uninstall a Program`. -![Uninstall a program](/../images/image53.png) +![Uninstall a program](../images/image53.png) + +**Figure 3-28: Uninstall a program** **Step 2:** Select the xDB Replication Server product in the list of programs to uninstall or change. Click the `Uninstall/Change` button. -![Uninstall or change a program](/../images/image54.png) +![Uninstall or change a program](../images/image54.png) + +**Figure 3-29: Uninstall or change a program** + **Step 3:** Click the `Yes` button to confirm uninstallation of xDB Replication Server. -![Confirm xDB Replication Server uninstallation](/../images/image55.png) +![Confirm xDB Replication Server uninstallation](../images/image55.png) + +**Figure 3-30: Confirm xDB Replication Server uninstallation** **Step 4:** The `Uninstallation Completed` dialog box appears when the process has completed. Click the `OK` button. -![Uninstallation completed](/../images/image56.png) +![Uninstallation completed](../images/image56.png) + +**Figure 3-31: Uninstallation completed** + **Uninstalling in Text or Unattended Mode** diff --git a/product_docs/docs/eprs/6.2/04_intro_xdb_console.mdx b/product_docs/docs/eprs/6.2/04_intro_xdb_console.mdx index d0cceb4ee9b..8082765ded8 100644 --- a/product_docs/docs/eprs/6.2/04_intro_xdb_console.mdx +++ b/product_docs/docs/eprs/6.2/04_intro_xdb_console.mdx @@ -13,7 +13,9 @@ The xDB Replication Console window consists of the following main areas: - `Replication Tree.` Replication system components represented as nodes in an inverted tree - `Information Window.` Tabbed window with information about a highlighted node in the replication tree -![xDB Replication Console window](/images/image57.png) +![xDB Replication Console window](images/image57.png) + +**Figure 4-1: xDB Replication Console window** The options that are available on the menu bar and tool bar are dependent upon the node highlighted in the replication tree. Only those options relevant to the highlighted node are available in the menu bar and tool bar. @@ -30,31 +32,42 @@ This section describes when the various tool bar icons are activated. The operat The `Refresh` icon is always activated. Click the `Refresh` icon if the replication tree or information window does not appear to display the latest information after performing an operation. Clicking the `Refresh` icon ensures that the latest information is shown in the replication tree and in the information window. -![Refresh icon](/images/image58.png) +![Refresh icon](images/image58.png) + +**Figure 4-2: Refresh icon** ### Create Publication The `Create Publication` icon is activated when a Publication Database node is highlighted in the replication tree. -![Create Publication icon](/images/image59.png) +![Create Publication icon](images/image59.png) + +**Figure 4-3: Create Publication icon** ### Publication Management The `Remove Publication` icon, `Add Publication Tables` icon, and `Remove Publication Tables` icon are activated when a Publication node is highlighted in the replication tree. -![Remove Publication, Add Publication Tables, and Remove Publication Tables icons](/images/image60.png) +![Remove Publication, Add Publication Tables, and Remove Publication Tables icons](images/image60.png) + +**Figure 4-4: Remove Publication, Add Publication Tables, and Remove Publication Tables icons** ### Create Subscription The `Create Subscription` icon is activated when a Subscription Database node is highlighted in the replication tree. -![Create Subscription icon](/images/image61.png) +![Create Subscription icon](images/image61.png) + +**Figure 4-5: Create Subscription icon** + ### Subscription Management The `Remove Subscription` icon, `Snapshot` icon, `Synchronize` icon, `Configure Schedule` icon, and `Remove Schedule` icon are activated when a Subscription node is highlighted in the replication tree. -![Remove Subscription, Snapshot, Synchronize, Configure Schedule, and Remove Schedule icons](/images/image62.png) +![Remove Subscription, Snapshot, Synchronize, Configure Schedule, and Remove Schedule icons](images/image62.png) + +**Figure 4-6: Remove Subscription, Snapshot, Synchronize, Configure Schedule, and Remove Schedule icons** @@ -72,13 +85,17 @@ The following shows the Register Publication Server dialog box where the option The values for User Name and Password that you enter are validated against the admin user name and password in the xDB Replication Configuration file residing on host `192.168.2.22`, in this case. The admin user name and password must successfully authenticate before registration of the publication server and saving of the publication server’s login information in the server login file occur. See [xDB Replication Configuration File](02_overview/03_replication_server_components_and_architecture/01_physical_components/#xdb_replication_conf_file) for information on the xDB Replication Configuration file. -![Save login information option for a publication server](/images/image63.png) +![Save login information option for a publication server](images/image63.png) + +**Figure 4-7: Save login information option for a publication server** See [Registering a Publication Server](05_smr_operation/02_creating_publication/01_registering_publication_server/#registering_publication_server) for more information on the purpose of these fields and the process of registering a publication server. The following shows the Register Subscription Server dialog box. In this example `192.168.2.22` entered in the Host field, `9052` entered in the Port field, admin entered in the User Name field, and an encrypted form of the password entered in the Password field are saved in the server login file for this subscription server if the admin user name and password validation are successful. -![Save login information option for a subscription server](/images/image64.png) +![Save login information option for a subscription server](images/image64.png) + +**Figure 4-8: Save login information option for a subscription server** See [Registering a Subscription Server](05_smr_operation/03_creating_subscription/01_registering_subscription_server/#registering_subscription_server) for more information on the purpose of these fields and the process of registering a subscription server. diff --git a/product_docs/docs/eprs/6.2/05_smr_operation/01_prerequisites/01_setting_heap_size_for_pub_and_sub.mdx b/product_docs/docs/eprs/6.2/05_smr_operation/01_prerequisites/01_setting_heap_size_for_pub_and_sub.mdx index 11bdb3040ab..42cbc575ac3 100644 --- a/product_docs/docs/eprs/6.2/05_smr_operation/01_prerequisites/01_setting_heap_size_for_pub_and_sub.mdx +++ b/product_docs/docs/eprs/6.2/05_smr_operation/01_prerequisites/01_setting_heap_size_for_pub_and_sub.mdx @@ -6,7 +6,9 @@ title: "Setting Heap Memory Size for the Publication and Subscription Servers" The publication server and the subscription server are configured to run with a default set of heap size parameters. Either the default settings for 32-bit platforms or the default settings for 64-bit platforms are set by parameter `JAVA_HEAP_SIZE` when xDB Replication Server is installed. -This parameter is configured in the xDB Startup Configuration file. See [xDB Startup Configuration File](../../02_overview/03_replication_server_components_and_architecture/01_physical_components/#xdb_startup_conf_file) for information on the xDB Startup Configuration file. The following is an example of the xDB Startup Configuration file. +This parameter is configured in the xDB Startup Configuration file. See [xDB Startup Configuration File](../../02_overview/03_replication_server_components_and_architecture/01_physical_components/#xdb_startup_conf_file) for information on the xDB Startup Configuration file. + +The following is an example of the xDB Startup Configuration file. ```text #!/bin/sh @@ -37,3 +39,16 @@ If both the publication server and subscription server are running on the same h By default, both the publication server and subscription server are started and both are required for single-master replication systems. However if only multi-master replication systems are to be configured and used, then the subscription server is not needed. In such cases, the subscription server should be stopped to avoid redundant use of memory. If both the publication server and the subscription server are running on the same host, then each server reserves its own heap buffer. Thus, the total heap size for both the publication and subscription servers, obtained by adding the maximum heap size for both servers, should comply with the available RAM on the host. + +## Tuning heap size and configuration parameters for larger rows + +When one or more publication tables contain a large size column, for example, `XMLType` (Oracle/EPAS data type), it is essential to adjust specific parameters to avoid Out Of Memory errors. The `XMLType` column is stored in Large Objects (`LOBs`). The `LOB` storage maintains content accuracy to the original XML. So it retains and stores all the white spaces present in the XML. This data occupies large space when it is loaded and held in-memory by xDB as part of the replication process. + +Tune the following parameters to reduce the data maintained in the memory for `XMLType` and other large-size columns: + +- Increase HEAP size between 4GB to 8GB depending on the maximum size of large column(4GB for column size below 30MB, 6GB for column size between 30 and 100 BM, and 8GB for column size > 100 MB). +- Set the configuration parameter `txSetMaxSize` to a lower value (10 to 50) depending on the average size of row data. For a large column (>100MB), set txSetMaxSize to less than or equal to 5. +- Set the configuration parameter `syncBatchSize` to a lower value (4 to 10 (rows)) depending on the size of the column data. For a very large column (>100MB), set syncBatchSize to less than 4. + +!!! Note + Higher values of `txSetMaxSize` and `syncBatchSize` boost the performance of the replication process; however, increasing it to a relatively larger value might result in an Out of Memory error. These values need to be tuned based on the column size. \ No newline at end of file diff --git a/product_docs/docs/eprs/6.2/05_smr_operation/01_prerequisites/03_enable_access_to_database.mdx b/product_docs/docs/eprs/6.2/05_smr_operation/01_prerequisites/03_enable_access_to_database.mdx index 3d3662bb809..e44e37514a4 100644 --- a/product_docs/docs/eprs/6.2/05_smr_operation/01_prerequisites/03_enable_access_to_database.mdx +++ b/product_docs/docs/eprs/6.2/05_smr_operation/01_prerequisites/03_enable_access_to_database.mdx @@ -17,11 +17,11 @@ No special steps are required to enable access to a Postgres database server. !!! Note The directions in this section apply only if Oracle will be used as the publication or subscription database. -An Oracle JDBC driver jar file such as, `ojdbc5.jar`, must be accessible to the Java virtual machine (JVM) on the host running the publication server and the subscription server. If the publication server and subscription server are running on separate hosts, the Oracle JDBC driver must be accessible to the JVM on each host. Oracle JDBC driver version ojdbc5 or later must be used. +An Oracle JDBC driver jar file such as, `ojdbc7.jar`, must be accessible to the Java virtual machine (JVM) on the host running the publication server and the subscription server. If the publication server and subscription server are running on separate hosts, the Oracle JDBC driver must be accessible to the JVM on each host. Oracle JDBC driver version ojdbc7 or later must be used. -**Step 1:** Download the Oracle JDBC driver, for example, ojdbc5.jar, from the Oracle download site to the host that will be running the publication server. +**Step 1:** Download the Oracle JDBC driver, for example, `ojdbc7.jar`, from the Oracle download site to the host that will be running the publication server. -**Step 2:** Copy file ojdbc5.jar to the directory `XDB_HOME/lib/jdbc.` +**Step 2:** Copy file `ojdbc7.jar` to the directory `XDB_HOME/lib/jdbc.` ```text $ su root @@ -37,7 +37,14 @@ total 4032 -rw-rw-r-- 1 root root 642809 Jan 25 02:38 postgresql-9.4-1201.jdbc4.jar ``` -Note: You may also copy the ojdbc5.jar file to the jre/lib/ext subdirectory of the location where you installed your Java runtime environment. +!!! Note + You may also copy the `ojdbc7.jar` file to the `jre/lib/ext` subdirectory of the location where you installed your Java runtime environment. + +!!! Note + Make sure to set the ODBC driver permission to a minimum of `644`. + +!!! Note + Make sure to copy `xdb6.jar` along with `ojdbc7.jar` at `/opt/PostgreSQL/EnterpriseDB-xDBReplicationServer/lib/jdbc/` if one or more tables in Oracle Publication contins an `XMLType` column when using Oracle to EDB Postgres Advanced Server/PostgreSQL replication. **Step 3:** If the subscription server is running on a different host than the publication server, repeat steps 1 and 2 for the subscription server host. diff --git a/product_docs/docs/eprs/6.2/05_smr_operation/01_prerequisites/04_preparing_pub_database.mdx b/product_docs/docs/eprs/6.2/05_smr_operation/01_prerequisites/04_preparing_pub_database.mdx index 418d647d3d4..059aea5b427 100644 --- a/product_docs/docs/eprs/6.2/05_smr_operation/01_prerequisites/04_preparing_pub_database.mdx +++ b/product_docs/docs/eprs/6.2/05_smr_operation/01_prerequisites/04_preparing_pub_database.mdx @@ -137,7 +137,9 @@ This example uses the following SQL Server login, database users, and mappings t !!! Note The sqlcmd utility program is used to execute the SQL statements in these examples. The USE command establishes the database to which the subsequent statements are to apply. The GO command executes the preceding SQL statements as a batch. Placement of the GO command within a stream of SQL statements sometimes has significance depending upon the particular SQL statements. -**Step 1:** Create a SQL Server login for the xDB Replication Server publication database user. The login must have a password. When creating the publication database definition, the SQL Server login is entered in the Publication Service – Add Database dialog box (see Section [Adding a Publication Database](../02_creating_publication/02_adding_pub_database/#adding_pub_database)). +**Step 1:** Create a SQL Server login for the xDB Replication Server publication database user. The login must have a password. + +When creating the publication database definition, the SQL Server login is entered in the Publication Service – Add Database dialog box (see Section [Adding a Publication Database](../02_creating_publication/02_adding_pub_database/#adding_pub_database). ```text USE primary; @@ -329,9 +331,7 @@ When creating the publication database definition, a database user name must be **Step 1:** Create a database superuser for the publication database user. The publication database user name must have a password, and it must have the ability to create a database session. The publication database user becomes the owner of the control schema objects that will be created in the publication database to track, control, and record the replication process and history. -When creating the publication database definition, the publication database user name is entered in the Publication Service – Add Database dialog box. - -See [Adding a Publication Database](../02_creating_publication/02_adding_pub_database/#adding_pub_database) +When creating the publication database definition, the publication database user name is entered in the `Publication Service – Add Database dialog box`, see [Adding a Publication Database](../02_creating_publication/02_adding_pub_database/#adding_pub_database). ```text CREATE ROLE pubuser WITH LOGIN SUPERUSER PASSWORD 'password'; diff --git a/product_docs/docs/eprs/6.2/05_smr_operation/01_prerequisites/05_preparing_sub_database.mdx b/product_docs/docs/eprs/6.2/05_smr_operation/01_prerequisites/05_preparing_sub_database.mdx index 0931481cadd..6e3687278f8 100644 --- a/product_docs/docs/eprs/6.2/05_smr_operation/01_prerequisites/05_preparing_sub_database.mdx +++ b/product_docs/docs/eprs/6.2/05_smr_operation/01_prerequisites/05_preparing_sub_database.mdx @@ -94,7 +94,9 @@ GRANT UNLIMITED TABLESPACE TO subuser; ## SQL Server Subscription Database -**Step 1:** Create or choose the subscription database. The names of the schemas containing the publication tables and views become the names of the SQL Server schemas for the subscription tables. The subscription server creates these schemas in the subscription database when the subscription is created. If schemas with these names already exist in the subscription database, the existing schemas will be used to store the subscription tables. +**Step 1:** Create or choose the subscription database. + +The names of the schemas containing the publication tables and views become the names of the SQL Server schemas for the subscription tables. The subscription server creates these schemas in the subscription database when the subscription is created. If schemas with these names already exist in the subscription database, the existing schemas will be used to store the subscription tables. !!! Note If the schema containing the publication tables and views is named public, then the subscription server creates a schema named `public_sql` in the SQL Server subscription database for the subscription tables. diff --git a/product_docs/docs/eprs/6.2/05_smr_operation/01_prerequisites/06_verifying_host_accessibility.mdx b/product_docs/docs/eprs/6.2/05_smr_operation/01_prerequisites/06_verifying_host_accessibility.mdx index a9d8681301b..299d16ec2ba 100644 --- a/product_docs/docs/eprs/6.2/05_smr_operation/01_prerequisites/06_verifying_host_accessibility.mdx +++ b/product_docs/docs/eprs/6.2/05_smr_operation/01_prerequisites/06_verifying_host_accessibility.mdx @@ -111,7 +111,7 @@ Use the following command for CentOS 7 or RHEL 7 and CentOS 8 or RHEL 8: `systemctl restart network` -The hostname -i command now returns the network IP address of the host: +The `hostname -i` command now returns the network IP address of the host: ```text $ hostname -i diff --git a/product_docs/docs/eprs/6.2/05_smr_operation/02_creating_publication/01_registering_publication_server.mdx b/product_docs/docs/eprs/6.2/05_smr_operation/02_creating_publication/01_registering_publication_server.mdx index c477f648002..cae0919df5c 100644 --- a/product_docs/docs/eprs/6.2/05_smr_operation/02_creating_publication/01_registering_publication_server.mdx +++ b/product_docs/docs/eprs/6.2/05_smr_operation/02_creating_publication/01_registering_publication_server.mdx @@ -59,7 +59,9 @@ Similarly, use the stop option to stop the publication server. **For Windows only:** Open Control Panel, System and Security, Administrative Tools, and then Services. The publication server runs as a service named Publication Service for xDB Replication Server. -![Windows publication service](/../../images/image65.png) +![Windows publication service](../../images/image65.png) + +**Figure 5-1: Windows publication service** Use the Start or Restart link for the service. @@ -67,9 +69,13 @@ If the publication server fails to start, see [Publication and Subscription Serv Step 2: Register the publication server. Open the xDB Replication Console from the system’s application menu. For xDB Replication Server installed from an xDB RPM package, the xDB Replication Console is started by invoking the script `XDB_HOME/bin/runRepConsole.sh`. -![xDB Replication Console menu option](/../../images/image66.png) +![xDB Replication Console menu option](../../images/image66.png) + +**Figure 5-2: xDB Replication Console menu option** + +![xDB Replication Console](../../images/image67.png) -![xDB Replication Console](/../../images/image67.png) +**Figure 5-3: xDB Replication Console** **Step 3:** Select the top level Replication Servers node. From the `File` menu, choose `Publication Server`, and then choose `Register Server`. Alternatively, click the secondary mouse button on the Replication Servers node and choose Register Publication Server. The Register Publication Server dialog box appears. @@ -84,10 +90,14 @@ Enter the values you supplied during the installation of xDB Replication Server !!! Note The user name and password combination you enter is authenticated against the admin user name and password in the xDB Replication Configuration file residing on the host with the IP address you enter in the Host field. -![Register Publication Server dialog box](/../../images/image63.png) +![Register Publication Server dialog box](../../images/image63.png) + +**Figure 5-4: Register Publication Server dialog box** Click the `Register` button after you have filled in the fields. A Publication Server node appears in the replication tree of the xDB Replication Console. Expand the Publication Server node to expose the SMR and MMR type nodes. -![Replication tree after registering a publication server](/../../images/image68.png) +![Replication tree after registering a publication server](../../images/image68.png) + +**Figure 5-5: Replication tree after registering a publication server** Continue to build the single-master replication system under the SMR type node. diff --git a/product_docs/docs/eprs/6.2/05_smr_operation/02_creating_publication/02_adding_pub_database.mdx b/product_docs/docs/eprs/6.2/05_smr_operation/02_creating_publication/02_adding_pub_database.mdx index 4fbe9920744..36682ae8de5 100644 --- a/product_docs/docs/eprs/6.2/05_smr_operation/02_creating_publication/02_adding_pub_database.mdx +++ b/product_docs/docs/eprs/6.2/05_smr_operation/02_creating_publication/02_adding_pub_database.mdx @@ -23,27 +23,35 @@ You must enter database connection information such as the database server netwo - `Password.` Password of the database user. - `Service ID (For Oracle).` Enter the Oracle System Identifier (SID) of the Oracle instance running the publication database if the SID radio button is selected. Enter the net service name of a connect descriptor as defined in the `TNSNAMES.ORA` file if the Service Name radio button is selected. Note (For Oracle 12c Pluggable Database): Use the service name. - Database (For Postgres or SQL Server). Enter the Postgres or SQL Server database name. -- `URL Options (For SSL connectivity).` Enter the URL options to establish SSL connectivity to the publication database. See Using Secure Sockets Layer (SSL) Connections <using_ssl_connections> for information on using SSL connections. +- `URL Options (For SSL connectivity).` Enter the URL options to establish SSL connectivity to the publication database. See [Using Secure Sockets Layer (SSL) Connections](../../07_common_operations/11_using_ssl_connections/#using_ssl_connections) for information on using SSL connections. - `Changeset Logging (For Postgres).` Select Table Triggers to use the trigger-based method of synchronization replication. Select WAL Stream to use the log-based method of synchronization replication. See [Synchronization Replication with the Trigger-Based Method](../../02_overview/02_replication_concepts_and_definitions/09_sync_replication_trigger_based/#sync_replication_trigger_based) for information on the trigger-based method. See [Synchronization Replication with the Log-Based Method](../../02_overview/02_replication_concepts_and_definitions/10_sync_replication_log_based/#sync_replication_log_based) for information on the log-based method. -![Publication Service - Add Database dialog box](/../../images/image69.png) +![Publication Service - Add Database dialog box](../../images/image69.png) + +**Figure 5-6: Publication Service - Add Database dialog box** !!! Note If the controller database is an Oracle or a SQL Server publication database, then a second Oracle or SQL Server publication database cannot be added to create a second single-master replication system. In order for xDB Replication Server to run more than one single-master replication systems consisting of Oracle or SQL Server publication databases, a Postgres publication database must be designated as the controller database. See [Controller Database](../../02_overview/03_replication_server_components_and_architecture/01_physical_components/#controller_database) for information on the controller database. The following is the Publication Service – Add Database dialog box for a Postgres database that shows the `Changeset Logging` option for selecting either the trigger-based method or the log-based method of synchronization replication. -![Publication Service - Add Database dialog box for Postgres](/../../images/image70.png) +![Publication Service - Add Database dialog box for Postgres](../../images/image70.png) + +**Figure 5-7: Publication Service - Add Database dialog box for Postgres** **Step 4:** Click the `Test` button. If Test Result: Success appears, click the `OK` button, then click the `Save` button. -![Successful publication database test](/../../images/image71.png) +![Successful publication database test](../../images/image71.png) + +**Figure 5-8: Successful publication database test** If an error message appears investigate the cause of the error, correct the problem, and repeat steps 1 through 4. When the publication database definition is successfully saved, a Publication Database node is added to the replication tree under the Publication Server node. -![Replication tree after adding a publication database](/../../images/image72.png) +![Replication tree after adding a publication database](../../images/image72.png) + +**Figure 5-9: Replication tree after adding a publication database** **For Oracle only:** Multiple Oracle databases can be added as publication databases by completing the Add Database dialog box for each database. It is also permissible to add the same Oracle database as two or more distinct publication database definitions if you use different publication database user names for each publication database definition. diff --git a/product_docs/docs/eprs/6.2/05_smr_operation/02_creating_publication/03_adding_publication.mdx b/product_docs/docs/eprs/6.2/05_smr_operation/02_creating_publication/03_adding_publication.mdx index 66a67e5abd6..610fedb6f10 100644 --- a/product_docs/docs/eprs/6.2/05_smr_operation/02_creating_publication/03_adding_publication.mdx +++ b/product_docs/docs/eprs/6.2/05_smr_operation/02_creating_publication/03_adding_publication.mdx @@ -16,7 +16,9 @@ Subordinate to a publication database definition, you create publications that c - `Select All.` Check this box if you want to include all tables and views in the Available Tables list in the publication. - `Use Wildcard Selection.` Click this button to use the wildcard selector to choose tables for the publication. See [Selecting Tables with the Wildcard Selector](../../07_common_operations/01_select_tables_wildcard_selector/#select_tables_wildcard_selector) for information on the wildcard selector. -![Create Publication dialog box](/../../images/image73.png) +![Create Publication dialog box](../../images/image73.png) + +**Figure 5-10: Create Publication dialog box** If you wish to use table filters during replications from this publication, follow the directions in the next step to define the initial set of available table filters, otherwise go on to Step 4. @@ -44,15 +46,21 @@ In the `Filter` dialog box, enter a descriptive filter name and the filter claus In the following example a filter rule is defined on the `DEPT` table so only rows where the `deptno` column contains 10, 20, or 30 are included in replications. All other rows are excluded from replication. -![Adding a filter rule for the DEPT table](/../../images/image74.png) +![Adding a filter rule for the DEPT table](../../images/image74.png) + +**Figure 5-11: Adding a filter rule for the DEPT table** The following shows a rule added to the `EMP` table by choosing `EDB.EMP` from the Table/View drop-down list and then entering the selection criteria for only rows with deptno containing 10 in the Filter dialog box. -![Adding a filter rule for the EMP table](/../../images/image75.png) +![Adding a filter rule for the EMP table](../../images/image75.png) + +**Figure 5-12: Adding a filter rule for the EMP table** Repeating this process, additional filter rules can be added for the EMP table. The following shows the complete set of available filter rules defined for the `DEPT` and `EMP` tables. -![Set of all available filter rules](/../../images/image76.png) +![Set of all available filter rules](../../images/image76.png) + +**Figure 5-13: Set of all available filter rules** To remove a filter rule, click the primary mouse button on the filter rule you wish to remove so the entry is highlighted and then click the Remove Filter button. @@ -62,8 +70,12 @@ When creating a subscription, you may selectively enable these table filters on **Step 4:** Click the `Create` button. If Publication Created Successfully appears, click the `OK` button, otherwise investigate the error and make the necessary corrections. -![Publication created successfully](/../../images/image77.png) +![Publication created successfully](../../images/image77.png) + +**Figure 5-14: Publication created successfully** Upon successful publication creation, a Publication node is added to the replication tree. -![Replication tree after adding a publication](/../../images/image78.png) +![Replication tree after adding a publication](../../images/image78.png) + +**Figure 5-15: Replication tree after adding a publication** diff --git a/product_docs/docs/eprs/6.2/05_smr_operation/03_creating_subscription/01_registering_subscription_server.mdx b/product_docs/docs/eprs/6.2/05_smr_operation/03_creating_subscription/01_registering_subscription_server.mdx index 708d03d63ba..c69dd1f5ffa 100644 --- a/product_docs/docs/eprs/6.2/05_smr_operation/03_creating_subscription/01_registering_subscription_server.mdx +++ b/product_docs/docs/eprs/6.2/05_smr_operation/03_creating_subscription/01_registering_subscription_server.mdx @@ -17,7 +17,9 @@ It is important that you record the login information for the subscription serve **For Windows only:** Open Control Panel, System and Security, Administrative Tools, and then Services. Use the Start or Restart link for the service named Subscription Service for xDB Replication Server. -![Windows subscription service](/../../images/image79.png) +![Windows subscription service](../../images/image79.png) + +**Figure 5-16: Windows subscription service** If the subscription server fails to start, see [Publication and Subscription Server Startup Failures](../../10_appendix/03_resolving_problems/02_where_to_look_for_errors/#pub_and_sub_startup_failures) for information. @@ -36,8 +38,12 @@ Enter the values you supplied during the installation of xDB Replication Server !!! Note The user name and password combination you enter is authenticated against the admin user name and password in the xDB Replication Configuration file residing on the host with the IP address you enter in the Host field. -![Register Subscription Server dialog box](/../../images/image64.png) +![Register Subscription Server dialog box](../../images/image64.png) + +**Figure 5-17: Register Subscription Server dialog box** Click the Register button after you have filled in the fields. A Subscription Server node appears in the replication tree of the xDB Replication Console. -![Replication tree after registering a subscription server](/../../images/image80.png) +![Replication tree after registering a subscription server](../../images/image80.png) + +**Figure 5-18: Replication tree after registering a subscription server** diff --git a/product_docs/docs/eprs/6.2/05_smr_operation/03_creating_subscription/02_adding_subscription_database.mdx b/product_docs/docs/eprs/6.2/05_smr_operation/03_creating_subscription/02_adding_subscription_database.mdx index 824b6c42ba5..093a248947e 100644 --- a/product_docs/docs/eprs/6.2/05_smr_operation/03_creating_subscription/02_adding_subscription_database.mdx +++ b/product_docs/docs/eprs/6.2/05_smr_operation/03_creating_subscription/02_adding_subscription_database.mdx @@ -28,7 +28,7 @@ Note the following restriction on the subscription database: **Step 1:** Make sure the database server in which the subscription database resides is running and accepting client connections. -**Step 2:** Select the Subscription Server node. From the Subscription menu, choose Subscription Database, and then choose Add Database. Alternatively, click the secondary mouse button on the Subscription Server node and choose Add Database. The Subscription Service – Add Database dialog box appears. +**Step 2:** Select the Subscription Server node. From the Subscription menu, choose Subscription Database, and then choose Add Database. Alternatively, click the secondary mouse button on the Subscription Server node and choose Add Database. The `Subscription Service – Add Database` dialog box appears. **Step 3:** Fill in the following fields: @@ -39,16 +39,22 @@ Note the following restriction on the subscription database: - `Password`. Password of the database user. - `Service ID (For Oracle)`. Enter the Oracle System Identifier (SID) of the Oracle instance running the subscription database if the SID radio button is selected. Enter the net service name of a connect descriptor as defined in the `TNSNAMES.ORA` file if the Service Name radio button is selected. Note (For Oracle 12c Pluggable Database): Use the service name. - `Database (For Postgres or SQL Server)`. Enter the Postgres or SQL Server database name. -- `URL Options (For SSL connectivity)`. Enter the URL options to establish SSL connectivity to the subscription database. See Using Secure Sockets Layer (SSL) Connections <using_ssl_connections> for information on using SSL connections. +- `URL Options (For SSL connectivity)`. Enter the URL options to establish SSL connectivity to the subscription database. See [Using Secure Sockets Layer (SSL) Connections](../../07_common_operations/11_using_ssl_connections/#using_ssl_connections) for information on using SSL connections. -![Subscription Service - Add Database dialog box](/../../images/image81.png) +![Subscription Service - Add Database dialog box](../../images/image81.png) + +**Figure 5-19: Subscription Service - Add Database dialog box** **Step 4:** Click the `Test` button. If Test Result: Success appears, click the OK button, then click the Save button. -![Successful subscription database test](/../../images/image82.png) +![Successful subscription database test](../../images/image82.png) + +**Figure 5-20: Successful subscription database test** If an error message appears investigate the cause of the error, correct the problem, and repeat steps 1 through 4. When the subscription database definition is successfully saved, a Subscription Database node is added to the replication tree under the Subscription Server node. -![Replication tree after adding a subscription database](/../../images/image83.png) +![Replication tree after adding a subscription database](../../images/image83.png) + +**Figure 5-21: Replication tree after adding a subscription database** diff --git a/product_docs/docs/eprs/6.2/05_smr_operation/03_creating_subscription/03_adding_subscription.mdx b/product_docs/docs/eprs/6.2/05_smr_operation/03_creating_subscription/03_adding_subscription.mdx index 4c905196daa..de932872903 100644 --- a/product_docs/docs/eprs/6.2/05_smr_operation/03_creating_subscription/03_adding_subscription.mdx +++ b/product_docs/docs/eprs/6.2/05_smr_operation/03_creating_subscription/03_adding_subscription.mdx @@ -17,7 +17,9 @@ Subordinate to a subscription database definition, you create subscriptions. A s - `Password`. Password of the admin user. This is the same value entered in the Password field in Step 3 of [Registering a Publication Server](../02_creating_publication/01_registering_publication_server/#registering_publication_server). - `Publication Name`. Click the `Load` button to get a list of available publications. Select the publication to which to subscribe. -![Create Subscription dialog box](/../../images/image84.png) +![Create Subscription dialog box](../../images/image84.png) + +**Figure 5-22: Create Subscription dialog box** **Step 3 (Optional):** If you defined a set of available table filters for the publication, you have the option of enabling these filters on this subscription. See [Adding a Publication](../02_creating_publication/03_adding_publication/#adding_publication) for instructions on defining table filters. If you do not wish to filter the rows that are replicated to this subscription, go to Step 4. @@ -25,16 +27,24 @@ Click the Filter Rules tab to enable one or more filter rules on the subscriptio In the following example the filter named `dept_10_20_30` is enabled on the dept table and the filter named dept_30 is enabled on the `emp` table of this subscription. -![Enabling filter rules on a subscription](/../../images/image85.png) +![Enabling filter rules on a subscription](../../images/image85.png) + +**Figure 5-23: Enabling filter rules on a subscription** **Step 4:** Click the `Create` button. If `Subscription Created Successfully` appears, click the `OK` button, otherwise investigate the error and make the necessary corrections. -![Subscription created successfully](/../../images/image86.png) +![Subscription created successfully](../../images/image86.png) + +**Figure 5-24: Subscription created successfully** Upon successful subscription creation, a Subscription node is added to the replication tree. -![Replication tree after adding a subscription](/../../images/image87.png) +![Replication tree after adding a subscription](../../images/image87.png) + +**Figure 5-25: Replication tree after adding a subscription** The tables and views from the publication are created in the subscription database, but without any rows. Rows are populated into the subscription tables when the first snapshot replication occurs. -![Table definitions in the subscription database](/../../images/image88.png) +![Table definitions in the subscription database](../../images/image88.png) + +**Figure 5-26: Table definitions in the subscription database** diff --git a/product_docs/docs/eprs/6.2/05_smr_operation/03_creating_subscription/04_subscription_metadata_object.mdx b/product_docs/docs/eprs/6.2/05_smr_operation/03_creating_subscription/04_subscription_metadata_object.mdx index 46f73e6cdbb..5040c039ff4 100644 --- a/product_docs/docs/eprs/6.2/05_smr_operation/03_creating_subscription/04_subscription_metadata_object.mdx +++ b/product_docs/docs/eprs/6.2/05_smr_operation/03_creating_subscription/04_subscription_metadata_object.mdx @@ -4,7 +4,7 @@ title: "Subscription Metadata Object" -After you have added a subscription database definition you will find a single table named rrep_txset_health has been created as the subscription metadata object. +After you have added a subscription database definition you will find a single table named `rrep_txset_health` has been created as the subscription metadata object. **For Oracle only:** The `RREP_TXSET_HEALTH` table is created in the subscription database user’s schema as shown in the following output: diff --git a/product_docs/docs/eprs/6.2/05_smr_operation/04_on_demand_replication/01_perform_replication.mdx b/product_docs/docs/eprs/6.2/05_smr_operation/04_on_demand_replication/01_perform_replication.mdx index a41cee003bd..6d2a18f8ac5 100644 --- a/product_docs/docs/eprs/6.2/05_smr_operation/04_on_demand_replication/01_perform_replication.mdx +++ b/product_docs/docs/eprs/6.2/05_smr_operation/04_on_demand_replication/01_perform_replication.mdx @@ -8,7 +8,9 @@ The very first replication must be performed using snapshot replication. After t **Step 1:** Select the Subscription node of the subscription for which you wish to perform snapshot replication. -![Selecting a subscription for an on demand snapshot](/../../images/image89.png) +![Selecting a subscription for an on demand snapshot](../../images/image89.png) + +**Figure 5-27: Selecting a subscription for an on demand snapshot** **Step 2:** Open the `Snapshot` dialog box in any of the following ways: @@ -16,11 +18,15 @@ The very first replication must be performed using snapshot replication. After t - Click the secondary mouse button on the Subscription node and choose `Snapshot`. - Click the primary mouse button on the Snapshot icon. -![Opening the Snapshot dialog box](/../../images/image90.png) +![Opening the Snapshot dialog box](../../images/image90.png) + +**Figure 5-28: Opening the Snapshot dialog box** **Step 3:** Select the `Verbose Output` check box only if you want to display the output from the snapshot in the dialog box. This option should be left unchecked in a network address translation (NAT) environment as a large amount of output from the snapshot may delay the response from the Snapshot dialog box. Click the Snapshot button to start snapshot replication. -![Snapshot dialog box](/../../images/image91.png) +![Snapshot dialog box](../../images/image91.png) + +**Figure 5-29: Snapshot dialog box** **Step 4:** Snapshot Taken Successfully appears if the snapshot was successful. Click the `OK` button. If the snapshot was not successful, scroll through the messages in the Snapshot dialog box window if Verbose Output was selected or check the log files. @@ -36,6 +42,8 @@ The status messages of each snapshot are saved in the Migration Toolkit log file `POSTGRES_HOME` is the home directory of the Windows postgres account (enterprisedb account for Advanced Server installed in Oracle compatible configuration mode). The specific location of `POSTGRES_HOME` is dependent upon your version of Windows. The xDB Replication Server version number is represented by `x.x`. -![Successful on demand snapshot](/../../images/image92.png) +![Successful on demand snapshot](../../images/image92.png) + +**Figure 5-30: Successful on demand snapshot** The publication has now been replicated to the subscription database. A record of the snapshot is maintained in the replication history. See [Viewing Replication History](../../07_common_operations/04_view_replication_history/#view_replication_history) for information on how to view replication history. diff --git a/product_docs/docs/eprs/6.2/05_smr_operation/04_on_demand_replication/02_perform_sync_replication.mdx b/product_docs/docs/eprs/6.2/05_smr_operation/04_on_demand_replication/02_perform_sync_replication.mdx index 96b9657e6cf..a2c5c08b1f6 100644 --- a/product_docs/docs/eprs/6.2/05_smr_operation/04_on_demand_replication/02_perform_sync_replication.mdx +++ b/product_docs/docs/eprs/6.2/05_smr_operation/04_on_demand_replication/02_perform_sync_replication.mdx @@ -10,7 +10,9 @@ After the first snapshot replication, subsequent replications can be performed u When the log-based method of synchronization replication is in use, select the Subscription node of any subscription. For the log-based method, the synchronization replication will be performed on all subscriptions regardless of which one is selected. -![Selecting a subscription for an on demand synchronization](/../../images/image89.png) +![Selecting a subscription for an on demand synchronization](../../images/image89.png) + +**Figure 5-31: Selecting a subscription for an on demand synchronization** **Step 2:** Open the `Synchronize` dialog box in any of the following ways: @@ -18,14 +20,20 @@ When the log-based method of synchronization replication is in use, select the S - Click the secondary mouse button on the Subscription node and choose Synchronize. - Click the primary mouse button on the `Synchronize` icon. -![Opening the Synchronize dialog box](/../../images/image93.png) +![Opening the Synchronize dialog box](../../images/image93.png) + +**Figure 5-32: Opening the Synchronize dialog box** **Step 3:** Click the `Synchronize` button to start synchronization replication. -![Synchronize dialog box](/../../images/image91.png) +![Synchronize dialog box](../../images/image91.png) + +**Figure 5-33: Synchronize dialog box** **Step 4:** `Subscription Synchronized Successfully` appears if the synchronization was successful. Click the `OK` button. If the synchronization was not successful, scroll through the messages in the Synchronize dialog box window. -![Successful on demand synchronization](/../../images/image94.png) +![Successful on demand synchronization](../../images/image94.png) + +**Figure 5-34: Successful on demand synchronization** The operations that were applied to the subscription tables can be seen in the replication history. See [Viewing Replication History](../../07_common_operations/04_view_replication_history/#view_replication_history) for information on how to view replication history. diff --git a/product_docs/docs/eprs/6.2/05_smr_operation/05_managing_subscription/01_updating_subscription_server.mdx b/product_docs/docs/eprs/6.2/05_smr_operation/05_managing_subscription/01_updating_subscription_server.mdx index 51b2dc026f2..0ee24e5c0fb 100644 --- a/product_docs/docs/eprs/6.2/05_smr_operation/05_managing_subscription/01_updating_subscription_server.mdx +++ b/product_docs/docs/eprs/6.2/05_smr_operation/05_managing_subscription/01_updating_subscription_server.mdx @@ -10,7 +10,9 @@ The steps described in this section show you how to update the subscription serv It is assumed that the xDB Replication Console is open on your computer and the subscription server whose login information you wish to alter in the server login file, appears as a Subscription Server node in the xDB Replication Console’s replication tree. -![Subscription Server node](/../../images/image95.png) +![Subscription Server node](../../images/image95.png) + +**Figure 5-35: Subscription Server node** You can perform the following actions on the server login file: @@ -25,7 +27,9 @@ The subscription server whose login information you want to save, change, or del **Step 2:** Click the secondary mouse button on the Subscription Server node and choose Update. The Update Subscription Server dialog box appears. -![Update Subscription Server dialog box](/../../images/image96.png) +![Update Subscription Server dialog box](../../images/image96.png) + +**Figure 5-36: Update Subscription Server dialog box** **Step 3:** Complete the fields in the dialog box according to your purpose for updating the server login file: @@ -33,6 +37,8 @@ The subscription server whose login information you want to save, change, or del - If you want to delete previously saved login information, make sure the network location shown in the dialog box is still correct. Re-enter the admin user name and password saved in the xDB Replication Configuration file that resides on the host identified by the IP address in the Host field. Leave the Save Login Information box unchecked. Access to the subscription server is available for this session, but subsequent sessions will require you to register the subscription server again. - If you want to save the current login information shown in the dialog box, make sure the network location shown in the dialog box is correct. Re-enter the admin user name and password saved in the xDB Replication Configuration file that resides on the host identified by the IP address in the Host field. Check the Save Login Information box. -![Updated subscription server location](/../../images/image97.png) +![Updated subscription server location](../../images/image97.png) + +**Figure 5-37: Updated subscription server location** **Step 4:** Click the `Update` button. If the dialog box closes, then the update to the server login file was successful. Click the `Refresh` icon in the xDB Replication Console tool bar to show the updated Subscription Server node. If an error message appears after clicking the `Update` button, the server login file is not modified. Investigate and correct the cause of the error. Repeat steps 1 through 4. diff --git a/product_docs/docs/eprs/6.2/05_smr_operation/05_managing_subscription/02_updating_subscription_database.mdx b/product_docs/docs/eprs/6.2/05_smr_operation/05_managing_subscription/02_updating_subscription_database.mdx index 71057c7b5c2..cc6a87fa1d0 100644 --- a/product_docs/docs/eprs/6.2/05_smr_operation/05_managing_subscription/02_updating_subscription_database.mdx +++ b/product_docs/docs/eprs/6.2/05_smr_operation/05_managing_subscription/02_updating_subscription_database.mdx @@ -30,20 +30,28 @@ Attributes you may change include the following: **Step 3:** Select the Subscription Database node corresponding to the subscription database definition that you wish to update. -![Selecting a subscription database definition for update](/../../images/image98.png) +![Selecting a subscription database definition for update](../../images/image98.png) + +**Figure 5-38: Selecting a subscription database definition for update** **Step 4:** From the Subscription menu, choose Subscription Database, and then choose Update Database. Alternatively, click the secondary mouse button on the Subscription Database node and choose Update Database. The Update Database Source dialog box appears. **Step 5:** Enter the desired changes. See Step 3 of Section [Adding a Subscription Database](../03_creating_subscription/02_adding_subscription_database/#adding_subscription_database) for the precise meanings of the fields. -![Update Database Source dialog box](/../../images/image99.png) +![Update Database Source dialog box](../../images/image99.png) + +**Figure 5-39: Update Database Source dialog box** **Step 6:** Click the `Test` button. If Test Result: Success appears, click the `OK` button, then click the `Save` button. -![Successful subscription database test](/../../images/image100.png) +![Successful subscription database test](../../images/image100.png) + +**Figure 5-40: Successful subscription database test** If an error message appears investigate the cause of the error, correct the problem, and repeat steps 1 through 6. **Step 7:** Click the `Refresh` icon in the xDB Replication Console tool bar to show the updated Subscription Database node and any of its subscriptions. -![Updated subscription database](/../../images/image101.png) +![Updated subscription database](../../images/image101.png) + +**Figure 5-41: Updated subscription database** diff --git a/product_docs/docs/eprs/6.2/05_smr_operation/05_managing_subscription/03_updating_subscription.mdx b/product_docs/docs/eprs/6.2/05_smr_operation/05_managing_subscription/03_updating_subscription.mdx index 9ff3e0abd71..07fb16e7182 100644 --- a/product_docs/docs/eprs/6.2/05_smr_operation/05_managing_subscription/03_updating_subscription.mdx +++ b/product_docs/docs/eprs/6.2/05_smr_operation/05_managing_subscription/03_updating_subscription.mdx @@ -17,15 +17,21 @@ The following directions show how to update the publication server network IP ad **Step 2:** Select the Subscription node whose attributes you wish to update. -![Selecting a subscription to update](/../../images/image102.png) +![Selecting a subscription to update](../../images/image102.png) + +**Figure 5-42: Selecting a subscription to update** **Step 3:** From the `Subscription` menu, choose `Update` Subscription. Alternatively, click the secondary mouse button on the Subscription node and choose Update Subscription. The `Update Subscription` dialog box appears. -![Update Subscription dialog box](/../../images/image103.png) +![Update Subscription dialog box](../../images/image103.png) + +**Figure 5-43: Update Subscription dialog box** **Step 4:** If the publication server now runs on a host with a different IP address or port number than what is shown in the dialog box, enter the correct information. You must also enter the admin user name and password saved in the xDB Replication Configuration file that resides on the host on which the publication server is running. Click the `Update` button. -![Subscription successfully updated](/../../images/image104.png) +![Subscription successfully updated](../../images/image104.png) + +**Figure 5-44: Subscription successfully updated** **Step 5:** If Subscription Updated Successfully appears, click the `OK` button, otherwise investigate the error and make the necessary corrections. diff --git a/product_docs/docs/eprs/6.2/05_smr_operation/05_managing_subscription/04_enable_filters_on_subscription.mdx b/product_docs/docs/eprs/6.2/05_smr_operation/05_managing_subscription/04_enable_filters_on_subscription.mdx index ea1479dd669..36b23267448 100644 --- a/product_docs/docs/eprs/6.2/05_smr_operation/05_managing_subscription/04_enable_filters_on_subscription.mdx +++ b/product_docs/docs/eprs/6.2/05_smr_operation/05_managing_subscription/04_enable_filters_on_subscription.mdx @@ -12,30 +12,41 @@ The following are the steps for enabling or disabling table filters on an existi **Step 2:** Select the Subscription node of the subscription on which you wish to enable or disable individual filter rules. -![Selecting a subscription on which to enable or disable filter rules](/../../images/image89.png) +![Selecting a subscription on which to enable or disable filter rules](../../images/image89.png) + +**Figure 5-45: Selecting a subscription on which to enable or disable filter rules** + **Step 3:** Open the Filter Rules tab in any of the following ways: -- Choose **Update Filter Rule** from the **Subscription** menu. -- Click the secondary mouse button on the Subscription node and choose **Update Filter Rule**. +- Choose `Update Filter Rule` from the `Subscription` menu. +- Click the secondary mouse button on the Subscription node and choose `Update Filter Rule`. + +![Opening the Filter Rules tab on a subscription](../../images/image105.png) -![Opening the Filter Rules tab on a subscription](/../../images/image105.png) +**Figure 5-46: Opening the Filter Rules tab on a subscription** -**Step 4:** In the **Filter Rules** tab check or uncheck the boxes to specify the filter rules to enable or disable on the subscription. At most one filter rule may be enabled any given subscription table. Click the **Update** button. +**Step 4:** In the `Filter Rules` tab check or uncheck the boxes to specify the filter rules to enable or disable on the subscription. At most one filter rule may be enabled any given subscription table. Click the `Update` button. -![Filter Rules tab](/../../images/image106.png) +![Filter Rules tab](../../images/image106.png) + +**Figure 5-47: Filter Rules tab** **Step 5:** A confirmation box appears presenting a warning message and a recommendation to perform a snapshot replication to any subscription on which you changed the filtering criteria. -Click the **Ok** button in the confirmation box to proceed with the update to the filter rule selections. Click the **Cancel** button to return to the **Filter Rules** tab if you wish to modify your filter rule selections. +Click the `Ok` button in the confirmation box to proceed with the update to the filter rule selections. Click the `Cancel` button to return to the `Filter Rules` tab if you wish to modify your filter rule selections. + +![Change filter rule confirmation](../../images/image107.png) + +**Figure 5-48: Change filter rule confirmation** -![Change filter rule confirmation](/../../images/image107.png) +**Step 6:** If you clicked the `Ok` button in the preceding step, the `Filter Rules updated successfully` confirmation message appears if the update was successful. -**Step 6:** If you clicked the **Ok** button in the preceding step, the **Filter Rules updated successfully** confirmation message appears if the update was successful. +![Successful update of filter rules](../../images/image108.png) -![Successful update of filter rules](/../../images/image108.png) +**Figure 5-49: Successful update of filter rules** -If you clicked the **Cancel** button in the preceding step, the **Filter Rules** tab reopens. You can modify your filter rule selections by repeating Step 4, or you can click the Cancel button in the Filter Rules tab to abort the filter rule updates on the subscription. +If you clicked the `Cancel` button in the preceding step, the `Filter Rules` tab reopens. You can modify your filter rule selections by repeating Step 4, or you can click the Cancel button in the Filter Rules tab to abort the filter rule updates on the subscription. **Step 7:** It is strongly recommended that a snapshot replication be performed to the subscription that contains tables on which the filtering criteria has changed. diff --git a/product_docs/docs/eprs/6.2/05_smr_operation/05_managing_subscription/05_removing_subscription.mdx b/product_docs/docs/eprs/6.2/05_smr_operation/05_managing_subscription/05_removing_subscription.mdx index da8aa72ac0d..de1cbb8135f 100644 --- a/product_docs/docs/eprs/6.2/05_smr_operation/05_managing_subscription/05_removing_subscription.mdx +++ b/product_docs/docs/eprs/6.2/05_smr_operation/05_managing_subscription/05_removing_subscription.mdx @@ -12,7 +12,9 @@ Removing a subscription does not delete the subscription tables in the subscript **Step 2:** Select the Subscription node of the subscription that you wish to remove. -![Selecting a subscription to remove](/../../images/image89.png) +![Selecting a subscription to remove](../../images/image89.png) + +**Figure 5-50: Selecting a subscription to remove** **Step 3:** Remove the subscription in any of the following ways: @@ -20,12 +22,18 @@ Removing a subscription does not delete the subscription tables in the subscript - Click the secondary mouse button on the Subscription node and choose `Remove Subscription`. - Click the primary mouse button on the `Remove Subscription` icon. -![Removing the subscription using the toolbar](/../../images/image109.png) +![Removing the subscription using the toolbar](../../images/image109.png) + +**Figure 5-51: Removing the subscription using the toolbar** **Step 4:** In the Remove Subscription confirmation box, click the `Yes` button. -![Remove Subscription confirmation](/../../images/image110.png) +![Remove Subscription confirmation](../../images/image110.png) + +**Figure 5-52: Remove Subscription confirmation** The Subscription node no longer appears under the Subscription Database node. -![Replication tree after removing a subscription](/../../images/image111.png) +![Replication tree after removing a subscription](../../images/image111.png) + +**Figure 5-53: Replication tree after removing a subscription** diff --git a/product_docs/docs/eprs/6.2/05_smr_operation/05_managing_subscription/06_removing_subscription_database.mdx b/product_docs/docs/eprs/6.2/05_smr_operation/05_managing_subscription/06_removing_subscription_database.mdx index 23f9a14c5ca..99b1b42875d 100644 --- a/product_docs/docs/eprs/6.2/05_smr_operation/05_managing_subscription/06_removing_subscription_database.mdx +++ b/product_docs/docs/eprs/6.2/05_smr_operation/05_managing_subscription/06_removing_subscription_database.mdx @@ -12,14 +12,20 @@ Removing a Subscription Database node does not delete the physical database from **Step 2:** Select the Subscription Database node that you wish to remove. -![Selecting a subscription database definition for removal](/../../images/image98.png) +![Selecting a subscription database definition for removal](../../images/image98.png) -**Step 3:** From the **Subscription** menu, choose **Subscription Database**, then **Remove Database**. Alternatively, click the secondary mouse button on the Subscription Database node and choose Remove Subscription. The **Remove Subscription Database** confirmation box appears. +**Figure 5-54: Selecting a subscription database definition for removal** -**Step 4:** In the **Remove Subscription Database** confirmation box, click the **Yes** button. +**Step 3:** From the `Subscription` menu, choose `Subscription Database`, then `Remove Database`. Alternatively, click the secondary mouse button on the Subscription Database node and choose Remove Subscription. The `Remove Subscription Database` confirmation box appears. -![Remove Subscription Database confirmation](/../../images/image112.png) +**Step 4:** In the `Remove Subscription Database` confirmation box, click the `Yes` button. + +![Remove Subscription Database confirmation](../../images/image112.png) + +**Figure 5-55: Remove Subscription Database confirmation** The Subscription Database node no longer appears under the Subscription Server node. -![Replication tree after removal of a subscription database](/../../images/image113.png) +![Replication tree after removal of a subscription database](../../images/image113.png) + +**Figure 5-56: Replication tree after removal of a subscription database** diff --git a/product_docs/docs/eprs/6.2/05_smr_operation/06_performing_switchover.mdx b/product_docs/docs/eprs/6.2/05_smr_operation/06_performing_switchover.mdx index 76c6b11cdc0..a341ba54bec 100644 --- a/product_docs/docs/eprs/6.2/05_smr_operation/06_performing_switchover.mdx +++ b/product_docs/docs/eprs/6.2/05_smr_operation/06_performing_switchover.mdx @@ -63,7 +63,75 @@ Delete or disable these triggers on node 1. Delete this schema from the subscription database on node 2 after the backup has been made. -**Step 8:** Restore the backups of `schemas _edb_replicator_pub`, \_edb_replicator_sub`, and`\_edb_scheduler`created in Step 5 to the subscription database on node 2. Also restore the backup of the replication triggers and trigger functions created in Step 6 to the subscription database on node 2. **Step 9:** Restore the backup of schema`\_edb_replicator_sub`created in Step 7 to the publication database on node 1. **Step 10:** Update the control schema objects so that the publication database definition references the new publication database (that is, the former subscription database) on node 2 and the subscription database definition references the new subscription database (that is, the former publication database) on node 1. The connection information that may require updating includes the following: * Host IP address * Port number * User name * Password These updates must be made in the control schema of all publication databases to ensure consistency of the control schema information should the controller database be switched at some later point in time. For example, the following shows the update to the publication database definition so that its network IP address is now node 2 (`192.168.2.20`). .. code-block:: text UPDATE _edb_replicator_pub.xdb_pub_database SET db_host = '192.168.2.20'; The following shows the update to the subscription database definition so that its network IP address is now node 1 (192.168.2.19). .. code-block:: text UPDATE _edb_replicator_sub.xdb_sub_database SET db_host = '192.168.2.19'; **Step 11:** If you decide to use a publication server or subscription server on a new host, perform the following step, otherwise go to Step 12. The following example assumes you decide to use the publication server and subscription server running on node 2. Update the subscription metadata to the new location of the publication server managing its associated publication. .. code-block:: text UPDATE _edb_replicator_sub.xdb_subscriptions SET pub_server_ip = '192.168.2.20'; Update the publication metadata to the new location of the subscription server managing its associated subscription. .. code-block:: text UPDATE _edb_replicator_pub.xdb_sub_servers SET sub_server_ip = '192.168.2.20'; **Step 12:** Edit the xDB Replication Configuration file on the publication server and subscription server host so that it contains the controller database connection and authentication information for the new publication database now running on node 2. The following is the modified xDB Replication Configuration file with the network location and authentication information of the new controller database now running on node 2. .. code-block:: text #xDB Replication Server Configuration Properties #Fri Jan 30 17:34:06 GMT-05:00 2015 port=5444 admin_password=ygJ9AxoJEX854elcVIJPTw\=\= user=enterprisedb admin_user=enterprisedb type=enterprisedb database=edb password=ygJ9AxoJEX854elcVIJPTw\=\= host=192.168.2.20 **Step 13:** Update the`pg_hba.conf\` files of the database servers to allow access to the subscription database now on node 1 and the publication database now on node 2 in accordance with Section \`Postgres Server Authentication <#postgres_server_auth>\_. +**Step 8:** Restore the backups of `schemas _edb_replicator_pub`, \_edb_replicator_sub`, and`\_edb_scheduler`created in Step 5 to the subscription database on node 2. Also restore the backup of the replication triggers and trigger functions created in Step 6 to the subscription database on node 2. + +**Step 9:** Restore the backup of schema`\_edb_replicator_sub`created in Step 7 to the publication database on node 1. + +**Step 10:** Update the control schema objects so that the publication database definition references the new publication database (that is, the former subscription database) on node 2 and the subscription database definition references the new subscription database (that is, the former publication database) on node 1. + +The connection information that may require updating includes the following: + +* Host IP address +* Port number +* User name +* Password + +These updates must be made in the control schema of all publication databases to ensure consistency of the control schema information should the controller database be switched at some later point in time. + +For example, the following shows the update to the publication database definition so that its network IP address is now node 2 (`192.168.2.20`). + +``` + +UPDATE _edb_replicator_pub.xdb_pub_database SET db_host = '192.168.2.20'; + +``` + +The following shows the update to the subscription database definition so that its network IP address is now node 1 (192.168.2.19). + +``` + +UPDATE _edb_replicator_sub.xdb_sub_database SET db_host = '192.168.2.19'; + +``` + +**Step 11:** If you decide to use a publication server or subscription server on a new host, perform the following step, otherwise go to Step 12. + +The following example assumes you decide to use the publication server and subscription server running on node 2. Update the subscription metadata to the new location of the publication server managing its associated publication. + +``` + +UPDATE _edb_replicator_sub.xdb_subscriptions SET pub_server_ip = '192.168.2.20'; + +``` + +Update the publication metadata to the new location of the subscription server managing its associated subscription. + +``` + +UPDATE _edb_replicator_pub.xdb_sub_servers SET sub_server_ip = '192.168.2.20'; + +``` + +**Step 12:** Edit the xDB Replication Configuration file on the publication server and subscription server host so that it contains the controller database connection and authentication information for the new publication database now running on node 2. + +The following is the modified xDB Replication Configuration file with the network location and authentication information of the new controller database now running on node 2. + +``` + +#xDB Replication Server Configuration Properties +#Fri Jan 30 17:34:06 GMT-05:00 2015 +port=5444 +admin_password=ygJ9AxoJEX854elcVIJPTw\=\= +user=enterprisedb +admin_user=enterprisedb +type=enterprisedb +database=edb +password=ygJ9AxoJEX854elcVIJPTw\=\= +host=192.168.2.20 + +``` + +**Step 13:** Update the`pg_hba.conf` files of the database servers to allow access to the subscription database now on node 1 and the publication database now on node 2 in accordance with Section [Postgres Server Authentication](../06_verifying_host_accessibility/03_postgres_server_auth/#postgres_server_auth). **Step 14:** When using the log-based method, create a replication slot on the database server that now contains the publication database. diff --git a/product_docs/docs/eprs/6.2/06_mmr_operation/02_creating_publication_mmr.mdx b/product_docs/docs/eprs/6.2/06_mmr_operation/02_creating_publication_mmr.mdx index 8b0de947ef3..764d6ebdc44 100644 --- a/product_docs/docs/eprs/6.2/06_mmr_operation/02_creating_publication_mmr.mdx +++ b/product_docs/docs/eprs/6.2/06_mmr_operation/02_creating_publication_mmr.mdx @@ -17,7 +17,7 @@ Creating a publication requires the following steps: Registering a publication server is done in a manner identical to single-master replication. See [Registering a Publication Server](../05_smr_operation/02_creating_publication/01_registering_publication_server/#registering_publication_server) for directions on registering a publication server. -![Replication tree after registering a publication server](/../images/image68.png) +![Replication tree after registering a publication server](../images/image68.png) After you have successfully registered a publication server, the replication tree of the xDB Replication Console displays a Publication Server node under which are the SMR and MMR type nodes. @@ -49,17 +49,17 @@ You must enter database connection information such as the database server netwo - `Changeset Logging (For Postgres)`. Select Table Triggers to use the trigger-based method of synchronization replication. Select WAL Stream to use the log-based method of synchronization replication. See [Synchronization Replication with the Trigger-Based Method](../02_overview/02_replication_concepts_and_definitions/09_sync_replication_trigger_based/#sync_replication_trigger_based) for information on the trigger-based method. See [Synchronization Replication with the Log-Based Method](../02_overview/02_replication_concepts_and_definitions/10_sync_replication_log_based/#sync_replication_log_based) for information on the log-based method. - `Node Priority Level`. An integer from 1 to 10, which is the priority level assigned to this primary node for conflict resolution based on node priority. The highest priority is 1 while the lowest is 10. See [Conflict Resolution Strategies](06_conflict_resolution/04_conflict_resolution_strategies/#conflict_resolution_strategies) for information on conflict resolution strategies. The default is 1 for the primary definition node. -![Publication Service - Add Database dialog box for the primary definition node](/../images/image114.png) +![Publication Service - Add Database dialog box for the primary definition node](../images/image114.png) **Step 4:** Click the `Test` button. If `Test Result: Success` appears, click the `OK` button, then click the `Save` button. -![Successful primary definition node test](/../images/image115.png) +![Successful primary definition node test](../images/image115.png) If an error message appears investigate the cause of the error, correct the problem, and repeat steps 1 through 4. When the publication database definition is successfully saved, a Publication Database node is added to the replication tree under the MMR type node of the Publication Server node. -![Replication tree after adding the primary definition node](/../images/image116.png) +![Replication tree after adding the primary definition node](../images/image116.png) The label `PDN` appears at the end of the node in the replication tree and in addition, the `PDN` field is set to Yes in the Property window to indicate this is the primary definition node. @@ -78,7 +78,7 @@ Subordinate to the primary definition node, you create a publication that contai - `Select All`. Check this box if you want to include all tables in the Available Tables list in the publication. - `Use Wildcard Selection`. Click this button to use the wildcard selector to choose tables for the publication. See [Selecting Tables with the Wildcard Selector](../07_common_operations/01_select_tables_wildcard_selector/#select_tables_wildcard_selector) for information on the wildcard selector. -![Create Publication dialog box](/../images/image117.png) +![Create Publication dialog box](../images/image117.png) If you wish to use table filters during replications between primary nodes in this multi-master replication system, follow the directions in the next step to define the initial set of available table filters, otherwise go on to Step 4. @@ -106,15 +106,15 @@ In the `Filter` dialog box, enter a descriptive filter name and the filter claus In the following example a filter rule is defined on the dept table so only rows where the `deptno` column contains `10, 20,` or `30` are included in replications. All other rows are excluded from replication. -![Adding a filter rule for the dept table](/../images/image118.png) +![Adding a filter rule for the dept table](../images/image118.png) The following shows a rule added to the `emp` table by choosing `edb.emp` from the Table/View drop-down list and then entering the selection criteria for only rows with `deptno` containing 10 in the Filter dialog box. -![Adding a filter rule for the emp table](/../images/image119.png) +![Adding a filter rule for the emp table](../images/image119.png) Repeating this process, additional filter rules can be added for the `emp` table. The following shows the complete set of available filter rules defined for the `dept` and `emp` tables. -![Set of all available filter rules](/../images/image120.png) +![Set of all available filter rules](../images/image120.png) To remove a filter rule, click the primary mouse button on the filter rule you wish to remove so the entry is highlighted and then click the `Remove Filter` button. @@ -131,7 +131,7 @@ If you wish to change the conflict resolution options from their default setting **Step 4 (Optional):** If you want to modify or see the current conflict resolution options, click the `Conflict Resolution Options` tab. For each table, you can select the primary conflict resolution strategy and a standby strategy by clicking the primary mouse button over the appropriate box to expose a drop-down list of choices. -![Conflict Resolution Options tab](/../images/image121.png) +![Conflict Resolution Options tab](../images/image121.png) If during synchronization replication, conflicting changes are pending against the same row from different primary nodes, the conflict resolution strategy determines which of the conflicting changes is accepted and replicated to all primary nodes. The conflicting changes that are not accepted are discarded. @@ -153,8 +153,8 @@ See [Conflict Resolution Strategies](06_conflict_resolution/04_conflict_resoluti **Step 6:** Click the `Create` button. If `Publication Created Successfully` appears, click the `OK` button, otherwise investigate the error and make the necessary corrections. -![Publication created successfully](/../images/image122.png) +![Publication created successfully](../images/image122.png) Upon successful publication creation, a Publication node is added to the replication tree. -![Replication tree after adding a publication](/../images/image123.png) +![Replication tree after adding a publication](../images/image123.png) diff --git a/product_docs/docs/eprs/6.2/06_mmr_operation/03_creating_primary_nodes.mdx b/product_docs/docs/eprs/6.2/06_mmr_operation/03_creating_primary_nodes.mdx index c55eb556362..3c1ea69a5ae 100644 --- a/product_docs/docs/eprs/6.2/06_mmr_operation/03_creating_primary_nodes.mdx +++ b/product_docs/docs/eprs/6.2/06_mmr_operation/03_creating_primary_nodes.mdx @@ -30,14 +30,14 @@ You must enter database connection information such as the database server netwo - `Replicate Publication Schema.` Check this box if you want the publication server to create the publication table definitions in the new primary node by copying the definitions from the primary definition node. If you do not check this box, it is assumed that you have already created the table definitions in the primary node. If you are using the offline snapshot technique to create this primary node, do not check this box. See Loading Tables From an External Data Source (Offline Snapshot) <offline_snapshot>) for information on using an offline snapshot. - `Perform Initial Snapshot.` Check this box if you want the publication server to perform a snapshot from the primary definition node to this primary node when you click the Save button. If you do not check this box, the tables on the primary node will not be loaded until you perform a replication at some later time. If you are using the offline snapshot technique to create this primary node, you should have already loaded the table rows. Therefore do not check this box unless you want to reload the data. See Loading Tables From an External Data Source (Offline Snapshot) <offline_snapshot> for information on using an offline snapshot. -![Publication Service - Add Database dialog box for an additional primary node](/../images/image124.png) +![Publication Service - Add Database dialog box for an additional primary node](../images/image124.png) !!! Note Unless you intend to use the offline snapshot technique (see Loading Tables From an External Data Source (Offline Snapshot) <offline_snapshot>), it is suggested that you check the Perform Initial Snapshot box. An initial snapshot replication must be performed from the primary definition node to every other primary node before performing synchronization replications on demand (see [Performing Synchronization Replication](05_on_demand_replication_mmr/#perform_synchronization_replication_mmr)) or by a schedule (see [Creating a Schedule](../07_common_operations/02_creating_schedule/#creating_schedule)). If a newly added primary node did not undergo an initial snapshot, any subsequent synchronization replication may fail to apply the transactions to that primary node. The initial snapshot can also be taken by performing an on demand snapshot (see [Performing Snapshot Replication](05_on_demand_replication_mmr/#perform_snapshot_replication_mmr)). **Step 4:** Click the `Test` button. If `Test Result: Success` appears, click the `OK` button. -![Successful primary node test](/../images/image125.png) +![Successful primary node test](../images/image125.png) If an error message appears investigate the cause of the error, correct the problem, and repeat steps 1 through 4. @@ -50,7 +50,7 @@ Click the `Filter Rules` tab to apply one or more filter rules to the primary no In the following example the filter named `dept_10_20_30` is enabled on the dept table and the filter named dept_30 is enabled on the `emp` table of this primary node. -![Enabling filter rules on a primary node](/../images/image126.png) +![Enabling filter rules on a primary node](../images/image126.png) **Step 6:** Check the Perform Initial Snapshot box if you want the publication server to perform a snapshot from the primary definition node to this primary node when you click the Save button. If you do not check this box, the tables on the primary node will not be loaded until you perform a replication at some later time. @@ -58,11 +58,11 @@ If you are using the offline snapshot technique to create this primary node, you If you do check the Perform Initial Snapshot check box, the Verbose Output check box appears as shown by the following: -![Initial snapshot with verbose output option](/../images/image127.png) +![Initial snapshot with verbose output option](../images/image127.png) If you skipped the enabling of table filters as described in Step 5, and you checked the `Perform Initial Snapshot` check box after Step 4, the `Verbose Output` check box is displayed as well: -![Initial snapshot with verbose output option](/../images/image128.png) +![Initial snapshot with verbose output option](../images/image128.png) Select the `Verbose Output` check box only if you want to display the output from the snapshot in the dialog box. This option should be left unchecked in a network address translation (NAT) environment as a large amount of output from the snapshot may delay the response from the Snapshot dialog box. @@ -70,7 +70,7 @@ Click the `Save` button. When the publication database definition is successfully saved, a Publication Database node is added to the replication tree under the MMR type node of the Publication Server node. -![Replication tree after adding an additional primary node](/../images/image129.png) +![Replication tree after adding an additional primary node](../images/image129.png) Unlike the primary definition node, the label PDN does not appear at the end of the node in the replication tree. The PDN field is set to No in the Property window to indicate this is not the primary definition node. @@ -78,7 +78,7 @@ In addition, a Publication node appears under the newly added primary node. This If in Step 6, you checked the `Perform Initial Snapshot` check box, an initial snapshot replication is performed. If you checked the `Verbose Output` check box, the log of the snapshot is displayed as well. -![- Adding a primary node with an initial snapshot](/../images/image130.png) +![- Adding a primary node with an initial snapshot](../images/image130.png) If the snapshot is successful, the replicated tables in the primary node are loaded with the rows from the publication tables of the primary definition node. diff --git a/product_docs/docs/eprs/6.2/06_mmr_operation/05_on_demand_replication_mmr.mdx b/product_docs/docs/eprs/6.2/06_mmr_operation/05_on_demand_replication_mmr.mdx index 01970d3476c..0ba501b5afe 100644 --- a/product_docs/docs/eprs/6.2/06_mmr_operation/05_on_demand_replication_mmr.mdx +++ b/product_docs/docs/eprs/6.2/06_mmr_operation/05_on_demand_replication_mmr.mdx @@ -21,18 +21,18 @@ When you create a primary node for the first time, you have the option of perfor **Step 1:** Select the Publication node under the primary node for which you wish to perform snapshot replication. -![Selecting a primary node publication for an on demand snapshot](/../images/image131.png) +![Selecting a primary node publication for an on demand snapshot](../images/image131.png) **Step 2:** Open the `Snapshot` dialog box in any of the following ways: - Click the secondary mouse button on the Publication node and choose Snapshot. - Click the primary mouse button on the Snapshot icon. -![Opening the Snapshot dialog box](/../images/image132.png) +![Opening the Snapshot dialog box](../images/image132.png) **Step 3:** Select the `Verbose Output` check box only if you want to display the output from the snapshot in the dialog box. This option should be left unchecked in a network address translation (NAT) environment as a large amount of output from the snapshot may delay the response from the Snapshot dialog box. Click the `Snapshot` button to start snapshot replication. -![Snapshot dialog box](/../images/image133.png) +![Snapshot dialog box](../images/image133.png) **Step 4:** `Snapshot Taken` Successfully appears if the snapshot was successful. Click the `OK` button. If the snapshot was not successful, scroll through the messages in the Snapshot dialog box window if Verbose Output was selected or check the log files. @@ -48,7 +48,7 @@ The status messages of each snapshot are saved in the Migration Toolkit log file `POSTGRES_HOME` is the home directory of the Windows postgres account (enterprisedb account for Advanced Server installed in Oracle compatible configuration mode). The specific location of POSTGRES_HOME is dependent upon your version of Windows. The xDB Replication Server version number is represented by `x.x`. -![Successful on demand snapshot](/../images/image134.png) +![Successful on demand snapshot](../images/image134.png) The publication has now been replicated from the primary definition node to the selected primary node. A record of the snapshot is maintained in the replication history. See [Viewing Replication History](../07_common_operations/04_view_replication_history/#view_replication_history) for information on how to view replication history. @@ -76,22 +76,22 @@ The following steps describe how to initiate on demand synchronization replicati **Step 1:** Select the Publication node under any primary node. Regardless of the primary node chosen, synchronization is applied to every primary node pair in the replication system. -![Selecting a primary node publication for an on demand synchronization](/../images/image131.png) +![Selecting a primary node publication for an on demand synchronization](../images/image131.png) **Step 2:** Open the `Synchronize` dialog box in any of the following ways: - Click the secondary mouse button on the Publication node and choose `Synchronize`. - Click the primary mouse button on the Synchronize icon. -![Opening the Synchronize dialog box](/../images/image135.png) +![Opening the Synchronize dialog box](../images/image135.png) **Step 3:** Click the `Synchronize` button to start synchronization replication. -![Synchronize dialog box](/../images/image136.png) +![Synchronize dialog box](../images/image136.png) **Step 4:** `Publication Synchronized Successfully(())` appears if the synchronization was successful. Click the `OK` button. If the synchronization was not successful, an error message is displayed. -![Successful on demand synchronization](/../images/image137.png) +![Successful on demand synchronization](../images/image137.png) The operations that were applied to the publication tables can be seen in the replication history. See [Viewing Replication History](../07_common_operations/04_view_replication_history/#view_replication_history) for information on how to view replication history. diff --git a/product_docs/docs/eprs/6.2/06_mmr_operation/06_conflict_resolution/06_conflict_prevention_mmr_ready/02_mmr_ready_example.mdx b/product_docs/docs/eprs/6.2/06_mmr_operation/06_conflict_resolution/06_conflict_prevention_mmr_ready/02_mmr_ready_example.mdx index 27c38465de0..0f4d639e2d3 100644 --- a/product_docs/docs/eprs/6.2/06_mmr_operation/06_conflict_resolution/06_conflict_prevention_mmr_ready/02_mmr_ready_example.mdx +++ b/product_docs/docs/eprs/6.2/06_mmr_operation/06_conflict_resolution/06_conflict_prevention_mmr_ready/02_mmr_ready_example.mdx @@ -129,7 +129,7 @@ The multi-master replication system is created with the Replicate Publication Sc The resulting primary nodes are shown in the xDB Replication Console. -![Publication table with MMR-ready sequence](/../../../images/image138.png) +![Publication table with MMR-ready sequence](../../../images/image138.png) !!! Note The Default Value property of the id column uses the `MMR_sequence_nextval` function. diff --git a/product_docs/docs/eprs/6.2/06_mmr_operation/06_conflict_resolution/08_custom_conflict_handling/02_adding_custom_conflict_handling_function.mdx b/product_docs/docs/eprs/6.2/06_mmr_operation/06_conflict_resolution/08_custom_conflict_handling/02_adding_custom_conflict_handling_function.mdx index 128168204de..ed75adb772a 100644 --- a/product_docs/docs/eprs/6.2/06_mmr_operation/06_conflict_resolution/08_custom_conflict_handling/02_adding_custom_conflict_handling_function.mdx +++ b/product_docs/docs/eprs/6.2/06_mmr_operation/06_conflict_resolution/08_custom_conflict_handling/02_adding_custom_conflict_handling_function.mdx @@ -17,18 +17,18 @@ CREATE FUNCTION **Step 3:** Open the `Conflict Resolution Options` tab in any of the following ways: -![Opening the Conflict Resolution Options tab](/../../../images/image139.png) +![Opening the Conflict Resolution Options tab](../../../images/image139.png) - From the `Publication` menu, choose `Update Publication`, then `Conflict Resolution Options`. - Click the secondary mouse button on the Publication node, choose `Update Publication`, and then choose `Conflict Resolution Options`. **Step 4:** For the table on which you want to use custom conflict handling, select Custom from the appropriate drop-down list. In the Custom Handler text box, enter the schema and function name used in the `CREATE FUNCTION` statement. -![Setting conflict resolution to custom conflict handling](/../../../images/image140.png) +![Setting conflict resolution to custom conflict handling](../../../images/image140.png) **Step 5:** Click the `Update` button, and then click `OK` in response to the `Conflict Resolution Options Updated Successfully` confirmation message. -![Successfully updated conflict resolution options](/../../../images/image141.png) +![Successfully updated conflict resolution options](../../../images/image141.png) !!! Note If the multi-master replication system uses custom conflict handling, and you subsequently switch the role of the primary definition node to another primary node, you must re-add the functions to the new primary definition node. That is, you must repeat Step 2 on the new primary definition node. diff --git a/product_docs/docs/eprs/6.2/06_mmr_operation/06_conflict_resolution/08_custom_conflict_handling/03_custom_conflict_handling_examples.mdx b/product_docs/docs/eprs/6.2/06_mmr_operation/06_conflict_resolution/08_custom_conflict_handling/03_custom_conflict_handling_examples.mdx index 673204c09b1..cdc586c514e 100644 --- a/product_docs/docs/eprs/6.2/06_mmr_operation/06_conflict_resolution/08_custom_conflict_handling/03_custom_conflict_handling_examples.mdx +++ b/product_docs/docs/eprs/6.2/06_mmr_operation/06_conflict_resolution/08_custom_conflict_handling/03_custom_conflict_handling_examples.mdx @@ -44,7 +44,7 @@ MMRnode=# SELECT * FROM dept; After a synchronization replication, the update/update conflict is detected and resolved as shown in the Conflict History tab: -![Conflict resolved by custom conflict handling](/../../../images/image142.png) +![Conflict resolved by custom conflict handling](../../../images/image142.png) In the source primary node the `loc` column of department 50 loses the value set in its UPDATE statement. The column is reset to the value from the target primary node. diff --git a/product_docs/docs/eprs/6.2/06_mmr_operation/06_conflict_resolution/09_manual_conflict_resolution_trigger_based_method/01_find_conflict.mdx b/product_docs/docs/eprs/6.2/06_mmr_operation/06_conflict_resolution/09_manual_conflict_resolution_trigger_based_method/01_find_conflict.mdx index bc9390023be..f0133b1864e 100644 --- a/product_docs/docs/eprs/6.2/06_mmr_operation/06_conflict_resolution/09_manual_conflict_resolution_trigger_based_method/01_find_conflict.mdx +++ b/product_docs/docs/eprs/6.2/06_mmr_operation/06_conflict_resolution/09_manual_conflict_resolution_trigger_based_method/01_find_conflict.mdx @@ -6,13 +6,13 @@ title: "Finding Conflicts" Conflicts can be found using the `Conflict History` tab as described in Section [Viewing Conflict History](../../07_view_conflict_history/#view_conflict_history). The following is an example of the Conflict History tab. Click the Refresh button to reveal all of the latest conflicts. -![Conflict History tab for trigger-based method](/../../../images/image143.png) +![Conflict History tab for trigger-based method](../../../images/image143.png) The `Source DB` and `Target DB` columns provide the IP address and database names of the source and target primary nodes involved in the conflict. Click the `View Data link` to show the details of the transactions involved in a particular conflict as shown by the following: -![Conflict Details window](/../../../images/image144.png) +![Conflict Details window](../../../images/image144.png) You can also obtain this information from a SQL query rather than from the xDB Replication Console graphical user interface. The following query can be run from a primary node to display information regarding pending (unresolved) conflicts: diff --git a/product_docs/docs/eprs/6.2/06_mmr_operation/06_conflict_resolution/09_manual_conflict_resolution_trigger_based_method/03_overview_correction_strategies.mdx b/product_docs/docs/eprs/6.2/06_mmr_operation/06_conflict_resolution/09_manual_conflict_resolution_trigger_based_method/03_overview_correction_strategies.mdx index 74227f84afe..df39c4b2e3f 100644 --- a/product_docs/docs/eprs/6.2/06_mmr_operation/06_conflict_resolution/09_manual_conflict_resolution_trigger_based_method/03_overview_correction_strategies.mdx +++ b/product_docs/docs/eprs/6.2/06_mmr_operation/06_conflict_resolution/09_manual_conflict_resolution_trigger_based_method/03_overview_correction_strategies.mdx @@ -107,7 +107,7 @@ MMRnode_c=# SELECT * FROM dept; The Conflict History tab shows the following entry: -![Conflict History tab with a uniqueness conflict](/../../../images/image145.png) +![Conflict History tab with a uniqueness conflict](../../../images/image145.png) The following is the output from the SQL query described in Section [Finding Conflicts](01_find_conflict/#find_conflict). diff --git a/product_docs/docs/eprs/6.2/06_mmr_operation/06_conflict_resolution/09_manual_conflict_resolution_trigger_based_method/04_manual_publication_table_correction.mdx b/product_docs/docs/eprs/6.2/06_mmr_operation/06_conflict_resolution/09_manual_conflict_resolution_trigger_based_method/04_manual_publication_table_correction.mdx index 7f3f0be055d..4b79a8fd464 100644 --- a/product_docs/docs/eprs/6.2/06_mmr_operation/06_conflict_resolution/09_manual_conflict_resolution_trigger_based_method/04_manual_publication_table_correction.mdx +++ b/product_docs/docs/eprs/6.2/06_mmr_operation/06_conflict_resolution/09_manual_conflict_resolution_trigger_based_method/04_manual_publication_table_correction.mdx @@ -182,13 +182,13 @@ rrep_tx_conflict_status | P The following shows the `rrep_tx_conflict_status` column marked `P` (pending) in the Postgres Enterprise Manager Client. -![Shadow table entry with pending conflict](/../../../images/image146.png) +![Shadow table entry with pending conflict](../../../images/image146.png) Modify column `rrep_tx_conflict_status` by changing the value to `D` (discarded) to show that the pending conflict has been resolved. A value of D also ensures that the shadow table entry will not be replicated during any future synchronization replications. Make this change to the shadow tables in both `MMRnode_a` and `MMRnode_b`. -![Discarded shadow table entry](/../../../images/image147.png) +![Discarded shadow table entry](../../../images/image147.png) Be sure to qualify the row with the correct `rrep_sync_id` value if you perform the update using a SQL statement such as in the following: @@ -216,7 +216,7 @@ Note the following points regarding the `xdb_conflicts` table: The following shows the Conflict History tab prior to updating the `xdb_conflicts` table. -![Pending uniqueness conflict](/../../../images/image145.png) +![Pending uniqueness conflict](../../../images/image145.png) The conflict entry for synchronization from `MMRnode_a` to `MMRnode_b` can be located in xdb_conflicts with the following query for this example: @@ -317,7 +317,7 @@ target_rrep_sync_id | 0 These entries appear in the Postgres Enterprise Manager Client as shown by the following: -![Pending conflict in xdb_conflicts](/../../../images/image147.png) +![Pending conflict in xdb_conflicts](../../../images/image147.png) Change the value in column resolution_status from P (pending) to C (completed) to indicate this conflict has been resolved. The value in winning_db_id is changed to 4 to indicate primary node `MMRnode_b` contains the winning transaction. The value in `winning_rrep_sync_id` is changed to the value of rrep_sync_id for the shadow table entry of the transaction in `MMRnode_b` since this is the one deemed to be correct. @@ -361,8 +361,8 @@ WHERE pk_value = 'deptno=50' The following are the updated xdb_conflicts entries: -![Resolved conflict in xdb_conflicts](/../../../images/image149.png) +![Resolved conflict in xdb_conflicts](../../../images/image149.png) When viewed in the Conflict History tab, the entries now show Resolved instead of Pending in the Resolution Status column, and the Winning DB column shows the address of primary node `MMRnode_b`. -![Resolved uniqueness conflict](/../../../images/image150.png) +![Resolved uniqueness conflict](../../../images/image150.png) diff --git a/product_docs/docs/eprs/6.2/06_mmr_operation/06_conflict_resolution/09_manual_conflict_resolution_trigger_based_method/05_correction_using_new_txn.mdx b/product_docs/docs/eprs/6.2/06_mmr_operation/06_conflict_resolution/09_manual_conflict_resolution_trigger_based_method/05_correction_using_new_txn.mdx index 59fee144751..587ce7ed0ee 100644 --- a/product_docs/docs/eprs/6.2/06_mmr_operation/06_conflict_resolution/09_manual_conflict_resolution_trigger_based_method/05_correction_using_new_txn.mdx +++ b/product_docs/docs/eprs/6.2/06_mmr_operation/06_conflict_resolution/09_manual_conflict_resolution_trigger_based_method/05_correction_using_new_txn.mdx @@ -166,17 +166,17 @@ Change the `rrep_tx_conflict_status` column from `P` (pending) to `D` (discarded The resulting change for the shadow table on `MMRnode_a` is as follows. -![Discarded shadow table entry](/../../../images/image151.png) +![Discarded shadow table entry](../../../images/image151.png) !!! Note The second entry for the accepted transaction you ran in Step 2 where `rrep_tx_conflict_status` is set to null indicating there was no conflict. The resulting change for the shadow table on `MMRnode_b` is as follows. -![Discarded shadow table entry](/../../../images/image152.png) +![Discarded shadow table entry](../../../images/image152.png) There is no shadow table entry in `MMRnode_c`, since an insert transaction was not performed in that primary node by the application. **Step 5:** In the control schema of the publication database currently designated as the controller database, modify the entries in the `xdb_conflicts` table to indicate the conflict has been resolved as in Step 3 of Section [Manual Publication Table Correction](04_manual_publication_table_correction/#manual_publication_table_correction). -![Resolved conflict in xdb_conflicts](/../../../images/image153.png) +![Resolved conflict in xdb_conflicts](../../../images/image153.png) diff --git a/product_docs/docs/eprs/6.2/06_mmr_operation/06_conflict_resolution/09_manual_conflict_resolution_trigger_based_method/06_correction_using_shadow_table_txn.mdx b/product_docs/docs/eprs/6.2/06_mmr_operation/06_conflict_resolution/09_manual_conflict_resolution_trigger_based_method/06_correction_using_shadow_table_txn.mdx index 70f54160dca..582d93f6015 100644 --- a/product_docs/docs/eprs/6.2/06_mmr_operation/06_conflict_resolution/09_manual_conflict_resolution_trigger_based_method/06_correction_using_shadow_table_txn.mdx +++ b/product_docs/docs/eprs/6.2/06_mmr_operation/06_conflict_resolution/09_manual_conflict_resolution_trigger_based_method/06_correction_using_shadow_table_txn.mdx @@ -151,7 +151,7 @@ MMRnode_c=# SELECT * FROM emp WHERE empno = 9001; Change the `rrep_tx_conflict_status` column from `P` (pending) to `D` (discarded) on the losing node, `MMRnode_b` as shown by the following: -![Losing shadow table entry](/../../../images/image154.png) +![Losing shadow table entry](../../../images/image154.png) **Step 3:** On winning node `MMRnode_c`, inspect the shadow table for the `emp` publication table. @@ -159,19 +159,19 @@ The objective is to use the shadow table entries for the insert and three update The leftmost columns of the shadow table appear as follows: -![Shadow table with multiple transactions](/../../../images/image155.png) +![Shadow table with multiple transactions](../../../images/image155.png) Make note of the `rrep_sync_id` values for these four entries, which are 1, 2, 3, and 4 in this example. The following shows the rightmost columns of the shadow table from the prior figure. Note the contents of column `rrep_tx_conflict_status` furthest to the right. -![Shadow table with multiple transactions (continued)](/../../../images/image156.png) +![Shadow table with multiple transactions (continued)](../../../images/image156.png) Make sure the `rrep_tx_conflict_status` column is null for these four entries. In this case, for the insert transaction, you will need to change the `P` (pending) value to null. The resulting change for the `rrep_tx_conflict_status` column in the shadow table on `MMRnode_c` is shown by the following: -![Shadow table transactions set to replicate](/../../../images/image157.png) +![Shadow table transactions set to replicate](../../../images/image157.png) **Step 4:** In order to replicate these four shadow table entries during the next synchronization, one or more entries must be added to the control schema table `_edb_replicator_pub.rrep_MMR_txset` on `MMRnode_c` to indicate pending status for synchronization to the target primary nodes (`MMRnode_a` and `MMRnode_b`) of the four shadow table entries identified by the rrep_sync_id values of 1, 2, 3, and 4 noted in Step 3. @@ -356,4 +356,4 @@ WHERE pk_value = 'empno=9001' When viewed in the Conflict History tab, the entry now shows Resolved in the Resolution Status column, and the Winning DB column shows the address of primary node `MMRnode_c`. -![Resolved uniqueness conflict](/../../../images/image158.png) +![Resolved uniqueness conflict](../../../images/image158.png) diff --git a/product_docs/docs/eprs/6.2/06_mmr_operation/06_conflict_resolution/10_manual_conflict_resolution_log_based_method/01_finding_conflict.mdx b/product_docs/docs/eprs/6.2/06_mmr_operation/06_conflict_resolution/10_manual_conflict_resolution_log_based_method/01_finding_conflict.mdx index e82bb411c55..8dec2d5660b 100644 --- a/product_docs/docs/eprs/6.2/06_mmr_operation/06_conflict_resolution/10_manual_conflict_resolution_log_based_method/01_finding_conflict.mdx +++ b/product_docs/docs/eprs/6.2/06_mmr_operation/06_conflict_resolution/10_manual_conflict_resolution_log_based_method/01_finding_conflict.mdx @@ -6,7 +6,7 @@ title: "Finding Conflicts" Conflicts can be found using the `Conflict History` tab as described in Section [Viewing Conflict History](../../07_view_conflict_history/#view_conflict_history). The following is an example of the Conflict History tab. Click the `Refresh` button to reveal all of the latest conflicts. -![Conflict History tab for log-based method](/../../../images/image159.png) +![Conflict History tab for log-based method](../../../images/image159.png) !!! Note The `View Data link and Conflict Details` window displayed for multi-master replication systems configured with the trigger-based method of synchronization replication are not available for multi-master replication systems configured with the log-based method of synchronization replication. diff --git a/product_docs/docs/eprs/6.2/06_mmr_operation/06_conflict_resolution/10_manual_conflict_resolution_log_based_method/03_overview_correction_strategies_log_based.mdx b/product_docs/docs/eprs/6.2/06_mmr_operation/06_conflict_resolution/10_manual_conflict_resolution_log_based_method/03_overview_correction_strategies_log_based.mdx index cbac81de740..53994837988 100644 --- a/product_docs/docs/eprs/6.2/06_mmr_operation/06_conflict_resolution/10_manual_conflict_resolution_log_based_method/03_overview_correction_strategies_log_based.mdx +++ b/product_docs/docs/eprs/6.2/06_mmr_operation/06_conflict_resolution/10_manual_conflict_resolution_log_based_method/03_overview_correction_strategies_log_based.mdx @@ -94,7 +94,7 @@ MMRnode_c=# SELECT * FROM dept; The Conflict History tab shows the following entry: -![Conflict History tab with a uniqueness conflict](/../../../images/image160.png) +![Conflict History tab with a uniqueness conflict](../../../images/image160.png) The following is the output from the SQL query described in Section [Finding Conflicts](../09_manual_conflict_resolution_trigger_based_method/01_find_conflict/#find_conflict). diff --git a/product_docs/docs/eprs/6.2/06_mmr_operation/06_conflict_resolution/10_manual_conflict_resolution_log_based_method/04_manual_publication_table_correction_log_based.mdx b/product_docs/docs/eprs/6.2/06_mmr_operation/06_conflict_resolution/10_manual_conflict_resolution_log_based_method/04_manual_publication_table_correction_log_based.mdx index b6893a7aaf4..638c0e062d1 100644 --- a/product_docs/docs/eprs/6.2/06_mmr_operation/06_conflict_resolution/10_manual_conflict_resolution_log_based_method/04_manual_publication_table_correction_log_based.mdx +++ b/product_docs/docs/eprs/6.2/06_mmr_operation/06_conflict_resolution/10_manual_conflict_resolution_log_based_method/04_manual_publication_table_correction_log_based.mdx @@ -113,7 +113,7 @@ Note the following points regarding the `xdb_conflicts` table: The following shows the **Conflict History** tab prior to updating the `xdb_conflicts` table. -![Pending uniqueness conflict](/../../../images/image160.png) +![Pending uniqueness conflict](../../../images/image160.png) The entry for the pending insert/insert conflict on the deptno primary key value of 50 can be located in xdb_conflicts with the following query for this example: @@ -142,7 +142,7 @@ pk_value | deptno=50 This entry appears in the Postgres Enterprise Manager Client as shown by the following: -![Pending conflict in xdb_conflicts](/../../../images/image161.png) +![Pending conflict in xdb_conflicts](../../../images/image161.png) Change the value in column resolution_status from P (pending) to C (completed) to indicate this conflict has been resolved. The value in winning_db_id is changed to 22 to indicate primary node `MMRnode_b` contains the winning transaction. @@ -159,8 +159,8 @@ WHERE pk_value = 'deptno=50' The following is the updated xdb_conflicts entry: -![Resolved conflict in xdb_conflicts](/../../../images/image162.png) +![Resolved conflict in xdb_conflicts](../../../images/image162.png) When viewed in the **Conflict History** tab, the entry now shows Resolved instead of `Pending` in the **Resolution Status** column, and the **Winning DB** column shows the address of primary node `MMRnode_b`. -![Resolved uniqueness conflict](/../../../images/image163.png) +![Resolved uniqueness conflict](../../../images/image163.png) diff --git a/product_docs/docs/eprs/6.2/06_mmr_operation/06_conflict_resolution/10_manual_conflict_resolution_log_based_method/05_correction_using_new_txn_log_based.mdx b/product_docs/docs/eprs/6.2/06_mmr_operation/06_conflict_resolution/10_manual_conflict_resolution_log_based_method/05_correction_using_new_txn_log_based.mdx index e9aa4e33d97..7e0cad3b2cb 100644 --- a/product_docs/docs/eprs/6.2/06_mmr_operation/06_conflict_resolution/10_manual_conflict_resolution_log_based_method/05_correction_using_new_txn_log_based.mdx +++ b/product_docs/docs/eprs/6.2/06_mmr_operation/06_conflict_resolution/10_manual_conflict_resolution_log_based_method/05_correction_using_new_txn_log_based.mdx @@ -143,4 +143,4 @@ MMRnode_c=# SELECT * FROM dept; **Step 4:** In the control schema of the publication database currently designated as the controller database, modify the entry in the `xdb_conflicts` table to indicate the conflict has been resolved as in Step 2 of Section [Conflict Resolution Concept for the Log-Based Method](02_conflict_resolution_for_log_based/#conflict_resolution_for_log_based). -![Resolved conflict in xdb_conflicts](/../../../images/image164.png) +![Resolved conflict in xdb_conflicts](../../../images/image164.png) diff --git a/product_docs/docs/eprs/6.2/06_mmr_operation/07_view_conflict_history.mdx b/product_docs/docs/eprs/6.2/06_mmr_operation/07_view_conflict_history.mdx index 04dd1a96fce..6aec78d2ccb 100644 --- a/product_docs/docs/eprs/6.2/06_mmr_operation/07_view_conflict_history.mdx +++ b/product_docs/docs/eprs/6.2/06_mmr_operation/07_view_conflict_history.mdx @@ -22,19 +22,19 @@ The following steps describe how to view the conflict history. **Step 1:** Select any Publication node under a Database node representing a primary node. Tabs labeled `General, Realtime Monitor, Replication History`, and `Conflict History` appear. -![Selecting a publication on which to view conflict history](/../images/image165.png) +![Selecting a publication on which to view conflict history](../images/image165.png) **Step 2:** Click the `Conflict History` tab to show conflict history. Click `Refresh` to ensure all the conflicts are listed. -![Conflict History tab](/../images/image166.png) +![Conflict History tab](../images/image166.png) **Step 3:** Use the `Conflict Display` Criteria drop-down list to display only conflicts of the chosen status. -![Selecting conflict history by status](/../images/image167.png) +![Selecting conflict history by status](../images/image167.png) **Step 4:** Click the `View Data` link to show the details of a particular conflict. !!! Note The `View Data` link and `Conflict Details` window are available only for multi-primary replication systems configured with the trigger-based method of synchronization replication. There is no `View Data` link or `Conflict Details` window for multi-primary replication systems configured with the log-based method of synchronization replication. -![Conflict Details window](/../images/image168.png) +![Conflict Details window](../images/image168.png) diff --git a/product_docs/docs/eprs/6.2/06_mmr_operation/08_update_conflict_resolution_options.mdx b/product_docs/docs/eprs/6.2/06_mmr_operation/08_update_conflict_resolution_options.mdx index 962eac2911f..2a021410b83 100644 --- a/product_docs/docs/eprs/6.2/06_mmr_operation/08_update_conflict_resolution_options.mdx +++ b/product_docs/docs/eprs/6.2/06_mmr_operation/08_update_conflict_resolution_options.mdx @@ -10,19 +10,19 @@ A current conflict resolution option on a publication table can be changed. See **Step 2:** Select the Publication node under the Publication Database node representing the primary definition node. -![Selecting a publication in which to update conflict resolution options](/../images/image169.png) +![Selecting a publication in which to update conflict resolution options](../images/image169.png) **Step 3:** Open the `Conflict Resolution Options` dialog box in any of the following ways: - From the `Publication` menu, choose `Update Publication`, then `Conflict Resolution Options`. - Click the secondary mouse button on the `Publication` node, choose `Update Publication`, and then choose `Conflict Resolution Options`. -![Opening the Conflict Resolution Options dialog box](/../images/image170.png) +![Opening the Conflict Resolution Options dialog box](../images/image170.png) **Step 4:** For each table, you can select the primary conflict resolution strategy and a standby strategy by clicking the master mouse button over the appropriate box to expose a drop-down list of choices. -![Updating conflict resolution strategies](/../images/image171.png) +![Updating conflict resolution strategies](../images/image171.png) **Step 5:** Click the `Update` button, and then click `OK` in response to Conflict Resolution Options Updated Successfully. -![Successfully updated conflict resolution options](/../images/image172.png) +![Successfully updated conflict resolution options](../images/image172.png) diff --git a/product_docs/docs/eprs/6.2/06_mmr_operation/09_enable_disable_table_filters.mdx b/product_docs/docs/eprs/6.2/06_mmr_operation/09_enable_disable_table_filters.mdx index dca9d41a268..237c5d14058 100644 --- a/product_docs/docs/eprs/6.2/06_mmr_operation/09_enable_disable_table_filters.mdx +++ b/product_docs/docs/eprs/6.2/06_mmr_operation/09_enable_disable_table_filters.mdx @@ -15,11 +15,11 @@ The following are the steps for enabling or disabling table filters on an existi **Step 2:** Select the Publication Database node corresponding to the primary node on which you wish to enable or disable individual filter rules. -![Selecting a primary node on which to enable or disable filter rules](/../images/image173.png) +![Selecting a primary node on which to enable or disable filter rules](../images/image173.png) **Step 3:** Click the secondary mouse button on the Publication Database node and choose `Update Filter Rule`. -![Opening the Filter Rules tab on a primary node](/../images/image174.png) +![Opening the Filter Rules tab on a primary node](../images/image174.png) !!! Note If you wish to enable or disable filter rules on the current primary definition node, you must first switch the role of the primary definition node to another primary node in order to expose the Update Filter Rule option in the primary node context menu. See Section [Switching the Primary definition node](10_switching_pdn/#switching_pdn) for directions on switching the primary definition node. @@ -28,17 +28,17 @@ The primary node you choose as the new primary definition node should contain a **Step 4:** In the `Filter Rules` tab check or uncheck the boxes to specify the filter rules to enable or disable on the primary node. At most one filter rule may be enabled on any given table. Click the `Save` button. -![Filter Rules tab](/../images/image175.png) +![Filter Rules tab](../images/image175.png) **Step 5:** A confirmation box appears presenting a warning message and a recommendation to perform a snapshot replication to any primary node on which you changed the filtering criteria. Click the `Ok` button in the confirmation box to proceed with the update to the filter rule selections. Click the Cancel button to return to the Filter Rules tab if you wish to modify your filter rule selections. -![Change filter rule confirmation](/../images/image176.png) +![Change filter rule confirmation](../images/image176.png) **Step 6:** If you clicked the `Ok` button in the preceding step, the Filter Rules updated successfully confirmation message appears if the update was successful. -![Successful update of filter rules](/../images/image177.png) +![Successful update of filter rules](../images/image177.png) If you clicked the `Cancel` button in the preceding step, the Filter Rules tab reopens. You can modify your filter rule selections by repeating Step 4, or you can click the `Cancel` button in the Filter Rules tab to abort the filter rule updates on the primary node. diff --git a/product_docs/docs/eprs/6.2/06_mmr_operation/10_switching_pdn.mdx b/product_docs/docs/eprs/6.2/06_mmr_operation/10_switching_pdn.mdx index 98d50295a26..cdfa8a1896a 100644 --- a/product_docs/docs/eprs/6.2/06_mmr_operation/10_switching_pdn.mdx +++ b/product_docs/docs/eprs/6.2/06_mmr_operation/10_switching_pdn.mdx @@ -10,26 +10,26 @@ After the multi-master replication system is created, you can switch the role of **Step 2:** Select the Publication Database node corresponding to the primary node that you wish to set as the primary definition node. -![Selecting the primary node to set as the master definition node](/../images/image178.png) +![Selecting the primary node to set as the master definition node](../images/image178.png) **Step 3:** Click the secondary mouse button on the Publication Database node and choose `Set as PDN`. -![Setting the master definition node](/../images/image179.png) +![Setting the master definition node](../images/image179.png) **Step 4:** In the `Set as PDN` confirmation box, click the `Yes` button. -![Set as PDN confirmation](/../images/image180.png) +![Set as PDN confirmation](../images/image180.png) **Step 5:** The selected master node is now the master definition node. -![Database promoted to master definition node](/../images/image181.png) +![Database promoted to master definition node](../images/image181.png) **Step 6:** The value `Yes` in the PDN field of the Property window indicates this database is the primary definition node. !!! Note The new primary definition node is moved to the top of the replication tree in the xDB Replication Console. -![Master definition node (PDN) indicated by ‘Yes’ in the Property window](/../images/image182.png) +![Master definition node (PDN) indicated by ‘Yes’ in the Property window](../images/image182.png) !!! Note You should now perform a synchronization replication to ensure that the new primary definition node is synchronized with the other primary nodes. See [Performing Synchronization Replication](05_on_demand_replication_mmr/#perform_synchronization_replication_mmr) for directions on performing a synchronization replication. diff --git a/product_docs/docs/eprs/6.2/07_common_operations/01_select_tables_wildcard_selector.mdx b/product_docs/docs/eprs/6.2/07_common_operations/01_select_tables_wildcard_selector.mdx index 9a6bc05ca83..8f4f759dccf 100644 --- a/product_docs/docs/eprs/6.2/07_common_operations/01_select_tables_wildcard_selector.mdx +++ b/product_docs/docs/eprs/6.2/07_common_operations/01_select_tables_wildcard_selector.mdx @@ -37,7 +37,7 @@ Interpretation of pattern characters is described by the following: The wildcard pattern definitions and examples can be seen from a help screen displayed by clicking the secondary mouse button on the Filter Pattern text field of the Wildcard Selector dialog box: -![Filter Pattern Help screen](/../images/image183.png) +![Filter Pattern Help screen](../images/image183.png) The following section describes the basic steps for using the wildcard selector. @@ -61,27 +61,27 @@ The tables that you have preselected are included in the local list used by the For example, the following is the Create Publication dialog box from which the wildcard selector can be used: -![Invoking the wildcard selector from a calling dialog box](/../images/image184.png) +![Invoking the wildcard selector from a calling dialog box](../images/image184.png) **Step 2:** The Available Tables field displays the filtered list matching the pattern used in the Filter Pattern text field. When the Wildcard Selector dialog box is initially opened, the default filter pattern is the percent sign (`%`), which returns all eligible, unselected tables. -![Wildcard Selector dialog box](/../images/image185.png) +![Wildcard Selector dialog box](../images/image185.png) **Step 3:** Enter a pattern in the `Filter Pattern` text field to narrow down your desired table selection. Click the `Filter List` button to display the tables that match the pattern. -![Tables matching a filter pattern](/../images/image186.png) +![Tables matching a filter pattern](../images/image186.png) **Step 4:** Select tables from the `Available Tables` list that you want to add to the local list by placing a check mark in each such table’s check box. You can also click the Select `All` check box to select all tables and then individually deselect certain tables by removing its check mark. -![Tables selected for the local list](/../images/image187.png) +![Tables selected for the local list](../images/image187.png) **Step 5:** Click the `Apply Selections to Local List button` to add the selected tables to the local list. The following example shows that the selected tables have been removed from the Available Tables list after the Apply Selections to Local List button was clicked since they are no longer unselected. -![Selected tables added to the local list](/../images/image188.png) +![Selected tables added to the local list](../images/image188.png) !!! Note You can click the `Cancel` button at any time to terminate the wildcard selector without applying the local list changes to the table list of the calling dialog box. @@ -90,41 +90,41 @@ The following example shows that the selected tables have been removed from the The following example shows a second filter pattern and the returned filter list. -![Tables matching a second filter pattern](/../images/image189.png) +![Tables matching a second filter pattern](../images/image189.png) All tables are then selected from this filtered list by clicking the `Select All` check box. -![Select all tables](/../images/image190.png) +![Select all tables](../images/image190.png) The `Apply Selections to Local List` button is clicked to add all tables to the local list. After applying the selections, there are no unselected tables remaining that match the filter pattern. -![All filter list tables added to the local list](/../images/image191.png) +![All filter list tables added to the local list](../images/image191.png) By using the asterisk after the pattern, you can display previously selected tables comprising the local list. Each selected table has a check mark its check box. -![Display selected and unselected tables matching the filter pattern](/../images/image192.png) +![Display selected and unselected tables matching the filter pattern](../images/image192.png) You can remove selected tables from the local list by clicking on each such table’s check box to remove the check mark. The following filter pattern includes the tables to be removed from the local list. -![List selected tables to be removed](/../images/image193.png) +![List selected tables to be removed](../images/image193.png) The check marks are removed from the selected tables to be removed from the local list. -![Deselect tables to be removed from the local list](/../images/image194.png) +![Deselect tables to be removed from the local list](../images/image194.png) The removal of the deselected tables from the local list occurs along with the addition of any newly selected tables when you click the `Apply Selections to Local List` button. -![Deselected tables removed from the local list now shown as unselected](/../images/image195.png) +![Deselected tables removed from the local list now shown as unselected](../images/image195.png) The deselected tables still appear in the Available Tables list since they still match the pattern, but as unselected tables (that is, with no check mark in each such table’s check box). **Step 7:** When the local list contains all of your desired, selected tables, click the Done button. The Wildcard Selector dialog box closes, and the local list becomes the list of selected tables displayed by the calling dialog box. -![Create Publication calling dialog box with applied local list](/../images/image196.png) +![Create Publication calling dialog box with applied local list](../images/image196.png) -![Create Publication calling dialog box with applied local list (continued)](/../images/image197.png) +![Create Publication calling dialog box with applied local list (continued)](../images/image197.png) Alternatively, if you decide that you do not wish to apply the local list, click the `Cancel` button. The local list changes are discarded and the table list of the calling dialog box remains unchanged. @@ -132,10 +132,10 @@ Alternatively, if you decide that you do not wish to apply the local list, click The following example verifies that if you were to invoke the wildcard selector a second time, the local list includes the table list created from the prior closure of the wildcard selector. -![Local list includes selected tables from the calling dialog box table list](/../images/image198.png) +![Local list includes selected tables from the calling dialog box table list](../images/image198.png) **Step 9:** When the calling dialog box contains the complete list of your desired tables, click the appropriate button of the calling dialog box to complete the operation with the selected tables. The following shows the publication created from the selected tables. -![Publication created with the selected tables](/../images/image199.png) +![Publication created with the selected tables](../images/image199.png) diff --git a/product_docs/docs/eprs/6.2/07_common_operations/02_creating_schedule.mdx b/product_docs/docs/eprs/6.2/07_common_operations/02_creating_schedule.mdx index f1cd998db45..e44dd21df20 100644 --- a/product_docs/docs/eprs/6.2/07_common_operations/02_creating_schedule.mdx +++ b/product_docs/docs/eprs/6.2/07_common_operations/02_creating_schedule.mdx @@ -32,15 +32,15 @@ For snapshot replications, skipped, scheduled replications present no problem si **Step 1 (For SMR only):** Select the Subscription node of the subscription for which you wish to create a schedule. -![Selecting a subscription on which to set a schedule](/../images/image109.png) +![Selecting a subscription on which to set a schedule](../images/image109.png) **Step 1 (For MMR only):** Select the Publication Database node designated as the controller database. (The Controller database field in the Property window is set to Yes for the controller database.) -![Selecting the controller database on which to set a schedule](/../images/image200.png) +![Selecting the controller database on which to set a schedule](../images/image200.png) **Step 2 (For SMR only):** Open the Scheduled Task Wizard dialog box in any of the following ways: -![Opening the Scheduled Task Wizard dialog box on a subscription](/../images/image201.png) +![Opening the Scheduled Task Wizard dialog box on a subscription](../images/image201.png) - From the `Subscription` menu, choose `Schedule`, then `Configure Schedule`. - Click the secondary mouse button on the Subscription node and choose `Configure Schedule`. @@ -51,7 +51,7 @@ For snapshot replications, skipped, scheduled replications present no problem si - Click the secondary mouse button on the Publication Database node and choose `Configure Schedule`. - Click the primary mouse button on the `Configure Schedule icon`. -![Opening the Scheduled Task Wizard dialog box on a subscription](/../images/image202.png) +![Opening the Scheduled Task Wizard dialog box on a subscription](../images/image202.png) **Step 3:** In the `Scheduled Task Wizard` dialog box, select the radio button for either synchronization replication or snapshot replication. @@ -61,7 +61,7 @@ For snapshot replications, skipped, scheduled replications present no problem si !!! Note In a multi-master replication system, only Synchronize may be chosen. -![Scheduled Task Wizard dialog box](/../images/image203.png) +![Scheduled Task Wizard dialog box](../images/image203.png) **Step 4:** Step 4: Select the radio button for the scheduled replication frequency, or select `Cron Expression` to write your own cron expression. The frequency choices have the following meanings: @@ -73,14 +73,14 @@ For snapshot replications, skipped, scheduled replications present no problem si The following example shows the selection of a weekly schedule. -![Selecting a weekly schedule](/../images/image204.png) +![Selecting a weekly schedule](../images/image204.png) **Step 5:** After completing the `Scheduled Task Wizard` dialog box, click the `Next` button. **Step 6:** Your selected schedule will appear. Click the `Finish` button to accept the schedule. -![Scheduled Task Wizard summary](/../images/image205.png) +![Scheduled Task Wizard summary](../images/image205.png) If you click the `Refresh` icon, you will see the schedule properties in the `General` tab. -![Information window with the replication schedule](/../images/image206.png) +![Information window with the replication schedule](../images/image206.png) diff --git a/product_docs/docs/eprs/6.2/07_common_operations/03_managing_schedule.mdx b/product_docs/docs/eprs/6.2/07_common_operations/03_managing_schedule.mdx index e76107894c2..e0be22e44d7 100644 --- a/product_docs/docs/eprs/6.2/07_common_operations/03_managing_schedule.mdx +++ b/product_docs/docs/eprs/6.2/07_common_operations/03_managing_schedule.mdx @@ -18,11 +18,11 @@ The following steps illustrate how to change an existing schedule. **Step 2 (For SMR only):** Select the Subscription node of the subscription for which you wish to update the schedule. -![Selecting a subscription whose schedule is to be updated](/../images/image207.png) +![Selecting a subscription whose schedule is to be updated](../images/image207.png) **Step 2 (For MMR only):** Select the Publication Database node designated as the controller database for which you wish to update the schedule. -![Selecting the controller database whose schedule is to be updated](/../images/image208.png) +![Selecting the controller database whose schedule is to be updated](../images/image208.png) **Step 3 (For SMR only):** Open the `Scheduled Task Wizard` dialog box in any of the following ways: @@ -35,15 +35,15 @@ The following steps illustrate how to change an existing schedule. - Click the secondary mouse button on the Publication Database node and choose `Configure Schedule`. - Click the primary mouse button on the `Configure Schedule` icon. -![Opening the Scheduled Task Wizard dialog box from the tool bar](/../images/image209.png) +![Opening the Scheduled Task Wizard dialog box from the tool bar](../images/image209.png) **Step 4:** The `Configure Scheduler` confirmation box appears. Click the `Yes` button. -![Configure Scheduler confirmation](/../images/image210.png) +![Configure Scheduler confirmation](../images/image210.png) **Step 5:** In the Scheduled Task Wizard dialog box, create the new schedule. See Step 3 of Section [Creating a Schedule](02_creating_schedule/#creating_schedule) for details on how to create a new schedule. -![Scheduled Task Wizard dialog box](/../images/image211.png) +![Scheduled Task Wizard dialog box](../images/image211.png) @@ -57,11 +57,11 @@ If you no longer wish replication to take place automatically, you must remove t **Step 2 (For SMR only):** Select the Subscription node of the subscription for which you wish to remove the schedule. -![Selecting a subscription for removal of a schedule](/../images/image207.png) +![Selecting a subscription for removal of a schedule](../images/image207.png) **Step 2 (For MMR only):** Select the Publication Database node designated as the controller database for which you wish to remove the schedule. -![Selecting the controller database for removal of a schedule](/../images/image208.png) +![Selecting the controller database for removal of a schedule](../images/image208.png) **Step 3 (For SMR only):** Remove the schedule in any of the following ways: @@ -71,12 +71,12 @@ If you no longer wish replication to take place automatically, you must remove t **Step 3 (For MMR only):** Remove the schedule in any of the following ways: \* Click the secondary mouse button on the Publication Database node and choose Remove Schedule. \* Click the primary mouse button on the Remove Schedule icon. -![Removing the schedule](/../images/image212.png) +![Removing the schedule](../images/image212.png) **Step 4:** In the Removing Schedule confirmation box, click the `Yes` button. -![Removing Schedule confirmation](/../images/image213.png) +![Removing Schedule confirmation](../images/image213.png) If you click the `Refresh` icon in the tool bar, you will notice that schedule information no longer appears in the information window. -![- Information window after schedule removal](/../images/image214.png) +![- Information window after schedule removal](../images/image214.png) diff --git a/product_docs/docs/eprs/6.2/07_common_operations/04_view_replication_history.mdx b/product_docs/docs/eprs/6.2/07_common_operations/04_view_replication_history.mdx index 5e7870d2b9d..2bb286102b5 100644 --- a/product_docs/docs/eprs/6.2/07_common_operations/04_view_replication_history.mdx +++ b/product_docs/docs/eprs/6.2/07_common_operations/04_view_replication_history.mdx @@ -24,15 +24,15 @@ The following steps describe how to view the replication history of the events i **Step 1 (For SMR only):** Select the node beneath the Subscription node. Tabs labeled `General, Realtime Monitor`, and `Replication History` appear. -![Selecting a subscription on which to view replication history](/../images/image215.png) +![Selecting a subscription on which to view replication history](../images/image215.png) **Step 1 (For MMR only):** Select any Publication node under a Database node representing a primary node. Tabs labeled `General, Realtime Monitor, Replication History`, and `Conflict History` appear. -![Selecting a publication on which to view replication history](/../images/image216.png) +![Selecting a publication on which to view replication history](../images/image216.png) **Step 2:** Click the `Replication History` tab to show a history of replications. -![Selecting a publication on which to view replication history](/../images/image217.png) +![Selecting a publication on which to view replication history](../images/image217.png) !!! Note Every snapshot replication and each synchronization replication with at least one update produces a history record that is maintained in replication history tables in the control schema. Over time the size of the replication history tables will grow. Replication history records can be periodically deleted. See Section [Cleaning Up Replication History](05_managing_history/#clean_up_replication_history) for information on cleaning up replication history. @@ -41,13 +41,13 @@ The following steps describe how to view the replication history of the events i You may notice synchronization replications with transaction counts of zero. These records indicate that there were no changes to synchronize at the time the replication occurred. For scheduled replications that occur frequently, this may result in a large number of lines in the `Replication History` tab, thus obscuring the more meaningful replications with non-zero transaction counts as shown below. -![Replication history with zero transaction counts](/../images/image218.png) +![Replication history with zero transaction counts](../images/image218.png) While viewing the `Replication History` tab, you can hide the records with zero transaction counts as follows: **Step 1:** Check the `Show History With Transactions Count > 0` check box located at the bottom of the `Replication History` tab. -![Setting replication history to hide zero transaction count records](/../images/image219.png) +![Setting replication history to hide zero transaction count records](../images/image219.png) **Step 2:** The next time the `Replication History` tab refreshes, only the replications with non-zero transaction counts appear in the `Replication History`. @@ -66,11 +66,11 @@ Expanding the nodes under the Subscription node of a single-master replication s Step 1: Select a table to reveal tabs that contain general information about the table and the replication history of the table. Expand a Table node to reveal the columns in the table. -![Table properties and columns](/../images/image220.png) +![Table properties and columns](../images/image220.png) Step 2: Click the `Replication History` tab to show a history of replications for this table. -![Table replication history tab](/../images/image221.png) +![Table replication history tab](../images/image221.png) **Step 3:** Click the `View Data` link to show a list of each change made to the table during the synchronization replication. The `Synchronize History` window shows two update operations followed by one insert operation against the `emp` target table that correspond to the following set of SQL statements executed on the `emp` source table: @@ -79,7 +79,7 @@ UPDATE emp SET hiredate = TO_DATE('07-JUN-15'), mgr = 7698 WHERE empno IN (9001, INSERT INTO emp (empno, ename, job, mgr, deptno) VALUES (9003, 'JOHNSON', 'SALESMAN', 7698, 30); ``` -![Synchronize History window](/../images/image222.png) +![Synchronize History window](../images/image222.png) !!! Note Since all insert, update, and delete operations on all source tables are recorded in shadow tables, the size of the shadow tables may grow considerably over time for volatile source tables. The rows shown in the Synchronize History window are obtained from these shadow tables. Rows in the shadow tables can be periodically deleted. See [Cleaning Up Shadow Table History](../08_xdb_cli/03_xdb_cli_commands/49_clean_shadow_table_history/#clean_shadow_table_history) for information on cleaning up the shadow tables. diff --git a/product_docs/docs/eprs/6.2/07_common_operations/05_managing_history.mdx b/product_docs/docs/eprs/6.2/07_common_operations/05_managing_history.mdx index a888e57cdbc..a64e3fe8703 100644 --- a/product_docs/docs/eprs/6.2/07_common_operations/05_managing_history.mdx +++ b/product_docs/docs/eprs/6.2/07_common_operations/05_managing_history.mdx @@ -55,15 +55,15 @@ The following steps show how to alter the default setting. **Step 2:** Select the Publication Database node for which you want to set the cleanup scheduling preference. -![Selecting the publication database for cleanup scheduling](/../images/image223.png) +![Selecting the publication database for cleanup scheduling](../images/image223.png) **Step 3:** From the `Publication` menu, choose `Preferences`. Alternatively, click the secondary mouse button on the Publication Database node and choose `Preferences`. The `Publication Server Preferences` dialog box appears. -![Publication Server Preferences dialog box](/../images/image224.png) +![Publication Server Preferences dialog box](../images/image224.png) **Step 4:** In the `Publication Server Preferences` dialog box, uncheck the box if you do not want to run a scheduled shadow table history cleanup job. Click the `OK` button and skip the remaining steps. -![Disabled schedule for shadow table history cleanup](/../images/image225.png) +![Disabled schedule for shadow table history cleanup](../images/image225.png) **Step 5:** If you want to schedule shadow table history cleanup, make sure the Run Cleanup Job check box is selected. Select the radio button for the cleanup frequency. The frequency choices have the following meanings: @@ -75,7 +75,7 @@ The following steps show how to alter the default setting. !!! Note A configuration option is available to force shadow table history cleanup after every synchronization replication. See [Forcing Immediate Shadow Table Cleanup](../10_appendix/04_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/09_forcing_shadow_table_cleanup/#forcing_shadow_table_cleanup) for information on this option. -![Cleanup Job dialog box](/../images/image226.png) +![Cleanup Job dialog box](../images/image226.png) **Step 6:** Click the `OK` button to accept the schedule. @@ -106,23 +106,23 @@ The following are the steps to run shadow table history cleanup on demand for a **Step 2:** Select the Publication node of the publication for which you want to clean up the shadow table history. -![Selecting a publication for shadow table history cleanup](/../images/image227.png) +![Selecting a publication for shadow table history cleanup](../images/image227.png) **Step 3:** From the `Publication` menu, choose `Cleanup Shadow Table History`. Alternatively, click the secondary mouse button on the Publication node and choose `Cleanup Shadow Table History`. The `Cleanup Synchronization History` confirmation box appears. -![Cleaning up shadow table history](/../images/image228.png) +![Cleaning up shadow table history](../images/image228.png) **Step 4:** Click the `Yes` button in the `Cleanup Synchronization History` confirmation box. -![Cleanup Synchronization History confirmation](/../images/image229.png) +![Cleanup Synchronization History confirmation](../images/image229.png) **Step 5:** Click the `Yes` button in response to `Shadow Table’s Transaction History Removed Successfully`. -![Successful cleanup of shadow table history](/../images/image230.png) +![Successful cleanup of shadow table history](../images/image230.png) After shadow table history cleanup, if you click the `View Data` link of the `Replication History` tab, an information message appears stating that there is no synchronization history to view. -![View Data link after shadow table history cleanup](/../images/image231.png) +![View Data link after shadow table history cleanup](../images/image231.png) @@ -139,23 +139,23 @@ The following are the steps to run replication history cleanup for a chosen publ **Step 2:** Select the Publication node of the publication for which you want to clean up replication history. -![Selecting a publication for replication history cleanup](/../images/image227.png) +![Selecting a publication for replication history cleanup](../images/image227.png) **Step 3:** From the `Publication` menu, choose `Cleanup Replication History`. Alternatively, click the secondary mouse button on the Publication node and choose Cleanup Replication History. The `Cleanup Replication History` confirmation box appears. -![Cleaning up replication history](/../images/image232.png) +![Cleaning up replication history](../images/image232.png) **Step 4:** Click the `Yes` button in the Cleanup Replication History confirmation box. -![Cleanup Replication History confirmation](/../images/image233.png) +![Cleanup Replication History confirmation](../images/image233.png) **Step 5:** Click the `Yes` button in response to Replication History Has Been Removed. -![Successful cleanup of replication history](/../images/image234.png) +![Successful cleanup of replication history](../images/image234.png) After replication history cleanup, if you click the `Replication History` tab, no history records appear. -![Successful cleanup of replication history](/../images/image235.png) +![Successful cleanup of replication history](../images/image235.png) diff --git a/product_docs/docs/eprs/6.2/07_common_operations/06_managing_publication/01_updating_publication_server.mdx b/product_docs/docs/eprs/6.2/07_common_operations/06_managing_publication/01_updating_publication_server.mdx index 1224fa8626d..8ed6bcb0b82 100644 --- a/product_docs/docs/eprs/6.2/07_common_operations/06_managing_publication/01_updating_publication_server.mdx +++ b/product_docs/docs/eprs/6.2/07_common_operations/06_managing_publication/01_updating_publication_server.mdx @@ -19,7 +19,7 @@ The steps described in this section show you how to update the publication serve It is assumed that the xDB Replication Console is open on your computer and the publication server whose login information you wish to alter in the server login file, appears as a Publication Server node in the xDB Replication Console’s replication tree. -![Publication Server node](/../../images/image236.png) +![Publication Server node](../../images/image236.png) You can perform the following actions on the server login file: @@ -33,7 +33,7 @@ The following steps change only the content of the server login file residing on **Step 2:** Click the secondary mouse button on the Publication Server node and choose Update. The `Update Publication Server` dialog box appears. -![Update Publication Server dialog box](/../../images/image237.png) +![Update Publication Server dialog box](../../images/image237.png) **Step 3:** Complete the fields in the dialog box according to your purpose for updating the server login file: @@ -41,7 +41,7 @@ The following steps change only the content of the server login file residing on - If you want to delete previously saved login information, make sure the network location shown in the dialog box is still correct. Re-enter the admin user name and password saved in the xDB Replication Configuration file that resides on the host identified by the IP address in the Host field. Leave the Save Login Information box unchecked. Access to the publication server is available for this session, but subsequent sessions will require you to register the publication server again. - If you want to save the current login information shown in the dialog box, make sure the network location shown in the dialog box is correct. Re-enter the admin user name and password saved in the xDB Replication Configuration file that resides on the host identified by the IP address in the Host field. Check the Save Login Information box. -![Updated publication server location](/../../images/image238.png) +![Updated publication server location](../../images/image238.png) **Step 4:** Click the `Update` button. If the dialog box closes, then the update to the server login file was successful. Click the `Refresh` icon in the xDB Replication Console tool bar to show the updated Publication Server node. @@ -60,7 +60,7 @@ This network information enables the publication server to communicate with the If the network location of a subscription server changes after subscriptions have been created, the publication server metadata must be updated with the new network location, otherwise a communication failure occurs between the publication server and the subscription server that is made apparent by the following message that appears when you open the xDB Replication Console. -![Subscription server connection failure](/../../images/image239.png) +![Subscription server connection failure](../../images/image239.png) The following are the steps to update the subscription server network location within a publication server’s metadata. @@ -71,11 +71,11 @@ The following are the steps to update the subscription server network location w !!! Note If the error message box reappears, click the `OK` button and repeat Step 2. -![Update Subscription Servers dialog box](/../../images/image240.png) +![Update Subscription Servers dialog box](../../images/image240.png) **Step 3:** Enter the new network location for each subscription server in the list whose network location has changed. -![Updated subscription server location](/../../images/image241.png) +![Updated subscription server location](../../images/image241.png) **Step 4:** Click the `Update` button. If the dialog box closes, then the update to the publication server’s metadata was successful. diff --git a/product_docs/docs/eprs/6.2/07_common_operations/06_managing_publication/02_updating_pub_database.mdx b/product_docs/docs/eprs/6.2/07_common_operations/06_managing_publication/02_updating_pub_database.mdx index cb2bea31ec5..dda20278931 100644 --- a/product_docs/docs/eprs/6.2/07_common_operations/06_managing_publication/02_updating_pub_database.mdx +++ b/product_docs/docs/eprs/6.2/07_common_operations/06_managing_publication/02_updating_pub_database.mdx @@ -29,22 +29,22 @@ Attributes you may change include the following: **Step 3:** Select the Publication Database node corresponding to the publication database definition that you wish to update. -![Selecting a publication database definition for update](/../../images/image242.png) +![Selecting a publication database definition for update](../../images/image242.png) **Step 4:** From the `Publication` menu, choose `Publication Database`, and then choose `Update Database`. Alternatively, click the secondary mouse button on the Publication Database node and choose Update Database. The `Update Database Source` dialog box appears. **Step 5:** Enter the desired changes. See Step 3 of [Adding a Publication Database](../../05_smr_operation/02_creating_publication/02_adding_pub_database/#adding_pub_database) for the precise meanings of the fields for a single-master replication system. See sections [Adding the Primary definition node](../../06_mmr_operation/02_creating_publication_mmr/#adding_pdn) and [Creating Additional Primary nodes](../../06_mmr_operation/03_creating_primary_nodes/#creating_primary_nodes) for a multi-master replication system. -![Update Database Source dialog box for a single-master replication system](/../../images/image243.png) +![Update Database Source dialog box for a single-master replication system](../../images/image243.png) **Step 6:** Click the `Test` button. If `Test Result: Success` appears, click the `OK` button, then click the `Save` button. If an error message appears investigate the cause of the error, correct the problem, and repeat steps 1 through 6. -![Successful publication database test](/../../images/image244.png) +![Successful publication database test](../../images/image244.png) **Step 7:** Restart the publication server. See [Registering a Publication Server](../../05_smr_operation/02_creating_publication/01_registering_publication_server/#registering_publication_server) for directions on restarting the publication server. **Step 8:** Click the `Refresh` icon in the xDB Replication Console tool bar to show the updated Publication Database node and any of its publications. -![Updated publication database](/../../images/image245.png) +![Updated publication database](../../images/image245.png) diff --git a/product_docs/docs/eprs/6.2/07_common_operations/06_managing_publication/03_updating_pub.mdx b/product_docs/docs/eprs/6.2/07_common_operations/06_managing_publication/03_updating_pub.mdx index da87b83fcd2..730124d14b6 100644 --- a/product_docs/docs/eprs/6.2/07_common_operations/06_managing_publication/03_updating_pub.mdx +++ b/product_docs/docs/eprs/6.2/07_common_operations/06_managing_publication/03_updating_pub.mdx @@ -24,7 +24,7 @@ The following are the steps to add tables to an existing publication. **Step 2 (For MMR only):** Select the Publication node under the Publication Database node representing the primary definition node. -![Selecting a publication to which to add tables](/../../images/image246.png) +![Selecting a publication to which to add tables](../../images/image246.png) **Step 3:** Open the Add Tables dialog box in any of the following ways: @@ -32,7 +32,7 @@ The following are the steps to add tables to an existing publication. - Click the secondary mouse button on the Publication node, choose Update Publication, and then choose Add Tables. - Click the primary mouse button on the Add Publication Tables icon. -![Opening the Add Tables dialog box](/../../images/image247.png) +![Opening the Add Tables dialog box](../../images/image247.png) **Step 4:** Fill in the following fields in the Add Tables tab of the Add Tables dialog box: @@ -40,7 +40,7 @@ The following are the steps to add tables to an existing publication. - Select All. Check this box if you want to include all tables and views in the Available Tables list in the publication. - Use Wildcard Selection. Click this button to use the wildcard selector to choose tables for the publication. See [Selecting Tables with the Wildcard Selector](../01_select_tables_wildcard_selector/#select_tables_wildcard_selector) for information on the wildcard selector. -![Add Tables dialog box](/../../images/image248.png) +![Add Tables dialog box](../../images/image248.png) If you wish to omit certain rows of the publication tables or views from being replicated follow the directions in the next step to create a filter, otherwise go on to Step 6. @@ -52,7 +52,7 @@ For a multi-master replication system, see [Adding a Publication](../../06_mmr_o **Step 6 (For SMR only):** Click the `Add Tables` button. If Publication Updated Successfully appears, click the `OK` button, otherwise investigate the error and make the necessary corrections. -![Successfully added tables to publication](/../../images/image249.png) +![Successfully added tables to publication](../../images/image249.png) **Step 6 (For MMR only):** Click the `Add Tables` button. The `Data Sync Check` dialog box appears warning you that synchronization replication is performed before the table is added. @@ -60,11 +60,11 @@ If you wish to perform synchronization at some later point in time then add the If you wish to proceed, click the `Yes` button. If Publication Updated Successfully appears, click the `OK` button, otherwise investigate the error and make the necessary corrections. -![Data Sync Check dialog box](/../../images/image250.png) +![Data Sync Check dialog box](../../images/image250.png) **Step 7:** The replication tree appears as follows with the newly added table under the Publication node. Click the `Refresh` icon. The newly added table appears under the Subscription nodes of a single-master replication system or the additional primary nodes of a multi-master replication system. -![Publication and subscription with added table](/../../images/image251.png) +![Publication and subscription with added table](../../images/image251.png) **Step 8 (For MMR only):** If you want to modify or see the default conflict resolution options assigned to the newly added table, follow the directions in Section [Updating the Conflict Resolution Options](../../06_mmr_operation/08_update_conflict_resolution_options/#update_conflict_resolution_options). @@ -82,7 +82,7 @@ You can remove one or more tables from a publication, but only if the following - The tables to be removed are not parent tables referenced by foreign key constraints of child tables that are not selected for removal as well. -![Entity relationship diagram of tables with foreign key constraints](/../../images/image252.png) +![Entity relationship diagram of tables with foreign key constraints](../../images/image252.png) In the preceding entity relationship diagram, the `emp` table has a foreign key constraint referencing the dept table, and the `jobhist` table has two foreign key constraints. One constraint references the `emp` table and the other references the `dept` table. @@ -97,7 +97,7 @@ If all three tables are in the publication, then you can remove the following co **Step 2 (For MMR only):** Select the Publication node under the Publication Database node representing the primary definition node. -![Selecting a publication from which to remove tables](/../../images/image253.png) +![Selecting a publication from which to remove tables](../../images/image253.png) **Step 3:** Open the `Remove Tables` dialog box in any of the following ways: @@ -105,23 +105,23 @@ If all three tables are in the publication, then you can remove the following co - Click the secondary mouse button on the Publication node, choose `Update Publication`, and then choose `Remove Tables`. - Click the primary mouse button on the `Remove Publication Tables` icon. -![Opening the Remove Tables dialog box by clicking the toolbar icon](/../../images/image254.png) +![Opening the Remove Tables dialog box by clicking the toolbar icon](../../images/image254.png) **Step 4:** Use the `Remove Tables` dialog box as follows: -![Remove Tables dialog box](/../../images/image255.png) +![Remove Tables dialog box](../../images/image255.png) - Remove. Check the boxes next to the table names from the Available Tables list that are to be removed from the publication. If the publication is a snapshot-only publication, then views would appear in the Available Tables list as well. Alternatively or in addition, click the `Use Wildcard Selection` button to use wildcard pattern matching for selecting tables to be removed from the publication. - Use Wildcard Selection. Click this button to use the wildcard selector to choose tables to remove from the publication. See [Selecting Tables with the Wildcard Selector](../01_select_tables_wildcard_selector/#select_tables_wildcard_selector) for information on the wildcard selector. **Step 5:** Click the `Remove` button, then click the `Yes` button of the confirmation box. -![Remove Tables dialog box](/../../images/image256.png) +![Remove Tables dialog box](../../images/image256.png) **Step 6:** Click the `OK` button in response to Tables Removed Successfully. -![Successfully removed tables from publication](/../../images/image257.png) +![Successfully removed tables from publication](../../images/image257.png) The replication tree appears as follows without the removed table under the Publication node. -![Publication minus removed table](/../../images/image258.png) +![Publication minus removed table](../../images/image258.png) diff --git a/product_docs/docs/eprs/6.2/07_common_operations/06_managing_publication/04_updating_table_filters_in_pub.mdx b/product_docs/docs/eprs/6.2/07_common_operations/06_managing_publication/04_updating_table_filters_in_pub.mdx index 31b4d85b4b7..6970887c6c2 100644 --- a/product_docs/docs/eprs/6.2/07_common_operations/06_managing_publication/04_updating_table_filters_in_pub.mdx +++ b/product_docs/docs/eprs/6.2/07_common_operations/06_managing_publication/04_updating_table_filters_in_pub.mdx @@ -25,18 +25,18 @@ The following are the steps to update the set of available filter rules in a pub **Step 2 (For MMR only):** Select the Publication node under the Publication Database node representing the primary definition node. -![Selecting a publication in which to update the set of available table filters](/../../images/image259.png) +![Selecting a publication in which to update the set of available table filters](../../images/image259.png) **Step 3:** Open the **Update Filters** dialog box in any of the following ways: - From the **Publication** menu, choose **Update Publication**, then **Update Filters**. - Click the secondary mouse button on the Publication node, choose **Update Publication**, and then choose **Update Filters**. -![Opening the Update Filters dialog box](/../../images/image260.png) +![Opening the Update Filters dialog box](../../images/image260.png) **Step 4:** The set of all available filter rules defined in the publication are listed under the **Table Filters** tab. -![- Set of all available filter rules](/../../images/image261.png) +![- Set of all available filter rules](../../images/image261.png) To add a new filter rule, from the Table/View drop-down list select the table or view for which you wish to add a filter and click the Add Filter button. Fill in the information in the dialog box that appears. (See [Adding a Publication](../../05_smr_operation/02_creating_publication/03_adding_publication/#adding_publication) for more details on adding individual filter rules in a single-master replication system. See [Adding a Publication](../../06_mmr_operation/02_creating_publication_mmr/#add_pub_mmr) for a multi-master replication system.) @@ -48,6 +48,6 @@ When you are satisfied with the updated set of available table filters, click th Click the **Ok** button in the confirmation box to proceed with the update to the filter rules. Click the **Cancel** button to return to the **Filter Rules** tab if you wish to modify your filter rule updates. -![Change filter rule confirmation](/../../images/image262.png) +![Change filter rule confirmation](../../images/image262.png) **Step 6:** You may selectively enable any new filter rules to the corresponding tables of the associated subscriptions or primary nodes. See Enabling/Disabling Table Filters on a Subscription <enable_filters_on_subscription> for information on enabling table filters on a subscription. See Enabling/Disabling Table Filters on a Primary node <enable_disable_table_filters> for enabling table filters on a primary node. diff --git a/product_docs/docs/eprs/6.2/07_common_operations/06_managing_publication/05_validating_publication.mdx b/product_docs/docs/eprs/6.2/07_common_operations/06_managing_publication/05_validating_publication.mdx index 23d4479a401..f3a6aa3b53d 100644 --- a/product_docs/docs/eprs/6.2/07_common_operations/06_managing_publication/05_validating_publication.mdx +++ b/product_docs/docs/eprs/6.2/07_common_operations/06_managing_publication/05_validating_publication.mdx @@ -78,11 +78,11 @@ The following steps show how to validate a single publication: **Step 3:** From the `Publication` menu, choose `Validate Publication`. Alternatively, click the secondary mouse button on the Publication node and choose `Validate Publication`. -![Validating a selected publication](/../../images/image263.png) +![Validating a selected publication](../../images/image263.png) **Step 4:** If All Schema of Published Tables in Publication 'publication_name' Are Up-To-Date appears, click the `OK` button. If an error appears, determine which tables were changed and what changes were made to the table definitions. These issues need to be resolved on a case by case basis as discussed earlier in this section. -![Successful validation of all tables in the selected publication](/../../images/image264.png) +![Successful validation of all tables in the selected publication](../../images/image264.png) @@ -104,12 +104,12 @@ All publications under a single Publication Database node can be validated in on **Step 3:** From the `Publication` menu, choose `Validate All Publications`. Alternatively, click the secondary mouse button on the Publication Database node and choose `Validate All Publications`. -![Validating all publications subordinate to a selected publication database](/../../images/image265.png) +![Validating all publications subordinate to a selected publication database](../../images/image265.png) **Step 4:** If there were no modified tables, click the `OK` button. -![Successful validation of all tables in all publications subordinate to a selected publication database](/../../images/image266.png) +![Successful validation of all tables in all publications subordinate to a selected publication database](../../images/image266.png) If there were modified tables, a list of publications that contain the modified tables is displayed. Determine which tables were changed and what changes were made to the table definitions. These issues need to be resolved on a case by case basis as discussed earlier in this section. -![List of publications with modified tables](/../../images/image267.png) +![List of publications with modified tables](../../images/image267.png) diff --git a/product_docs/docs/eprs/6.2/07_common_operations/06_managing_publication/06_removing_pub.mdx b/product_docs/docs/eprs/6.2/07_common_operations/06_managing_publication/06_removing_pub.mdx index 1c273b4406c..48b90df527c 100644 --- a/product_docs/docs/eprs/6.2/07_common_operations/06_managing_publication/06_removing_pub.mdx +++ b/product_docs/docs/eprs/6.2/07_common_operations/06_managing_publication/06_removing_pub.mdx @@ -18,7 +18,7 @@ The publication database user name is also left intact along with some of the xD **Step 2 (For MMR only):** Select the Publication node under the Publication Database node representing the primary definition node. -![Selecting a publication to remove](/../../images/image268.png) +![Selecting a publication to remove](../../images/image268.png) **Step 3:** Remove the publication in any of the following ways: @@ -26,12 +26,12 @@ The publication database user name is also left intact along with some of the xD - Click the secondary mouse button on the Publication node and choose **Remove Publication**. - Click the primary mouse button on the **Remove Publication** icon. -![Removing the publication using the menu bar](/../../images/image269.png) +![Removing the publication using the menu bar](../../images/image269.png) **Step 4:** In the **Remove Publication** confirmation box, click the **Yes** button. -![Remove Publication confirmation](/../../images/image270.png) +![Remove Publication confirmation](../../images/image270.png) The Publication node no longer appears under the Publication Database node. -![Replication tree after removing a publication](/../../images/image271.png) +![Replication tree after removing a publication](../../images/image271.png) diff --git a/product_docs/docs/eprs/6.2/07_common_operations/06_managing_publication/07_removing_pub_database.mdx b/product_docs/docs/eprs/6.2/07_common_operations/06_managing_publication/07_removing_pub_database.mdx index 207dcdbb59c..9ba10c101c1 100644 --- a/product_docs/docs/eprs/6.2/07_common_operations/06_managing_publication/07_removing_pub_database.mdx +++ b/product_docs/docs/eprs/6.2/07_common_operations/06_managing_publication/07_removing_pub_database.mdx @@ -40,14 +40,14 @@ The following are the steps to remove the Publication Database node and equivale **Step 2:** Select the Publication Database node that you wish to remove. -![Selecting a publication to remove](/../../images/image271.png) +![Selecting a publication to remove](../../images/image271.png) **Step 3:** From the Publication menu, choose Publication Database, then Remove Database. Alternatively, click the secondary mouse button on the Publication Database node and choose Remove Database. The **Remove Publication** Database confirmation box appears. **Step 4:** In the **Remove Publication Database** confirmation box, click the **Yes** button. -![Remove Publication confirmation](/../../images/image273.png) +![Remove Publication confirmation](../../images/image273.png) The Publication Database node no longer appears under the Publication Server node. -![Replication tree after removing a publication database](/../../images/image274.png) +![Replication tree after removing a publication database](../../images/image274.png) diff --git a/product_docs/docs/eprs/6.2/07_common_operations/07_switching_controller_db.mdx b/product_docs/docs/eprs/6.2/07_common_operations/07_switching_controller_db.mdx index 4d8adc61e34..a9ce54fbaaa 100644 --- a/product_docs/docs/eprs/6.2/07_common_operations/07_switching_controller_db.mdx +++ b/product_docs/docs/eprs/6.2/07_common_operations/07_switching_controller_db.mdx @@ -25,23 +25,23 @@ The following are the steps to set another publication database as the controlle **Step 2:** Select the Publication Database node corresponding to the publication database that you wish to set as the controller database. -![Selecting the publication database to set as the controller database](/../images/image275.png) +![Selecting the publication database to set as the controller database](../images/image275.png) Step 3: Click the secondary mouse button on the Publication Database node and choose Set as Controller database. -![Setting the controller database](/../images/image276.png) +![Setting the controller database](../images/image276.png) Step 4: In the Set as Controller database confirmation box, click the `Yes` button. -![Set as Controller database confirmation](/../images/image277.png) +![Set as Controller database confirmation](../images/image277.png) Step 5: The selected publication database has now been set as the controller database. -![Publication database promoted to controller database](/../images/image278.png) +![Publication database promoted to controller database](../images/image278.png) Step 6: The value Yes in the Controller database field of the `Property` window indicates this database is the controller database. -![Controller database indicated by Yes in the Property window](/../images/image279.png) +![Controller database indicated by Yes in the Property window](../images/image279.png) The following shows the xDB Replication Configuration file after the controller database has been switched to the primary node database `MMRnode_b`. diff --git a/product_docs/docs/eprs/6.2/07_common_operations/08_replicating_ddl_changes/02_ddl_change_replication_using_xdb_console.mdx b/product_docs/docs/eprs/6.2/07_common_operations/08_replicating_ddl_changes/02_ddl_change_replication_using_xdb_console.mdx index 7b0b250426e..786de0fee9a 100644 --- a/product_docs/docs/eprs/6.2/07_common_operations/08_replicating_ddl_changes/02_ddl_change_replication_using_xdb_console.mdx +++ b/product_docs/docs/eprs/6.2/07_common_operations/08_replicating_ddl_changes/02_ddl_change_replication_using_xdb_console.mdx @@ -14,19 +14,19 @@ Alternatively, you can copy and paste, or directly type in the `ALTER TABLE` sta **Step 3:** Under the publication database of a single-master replication system, or under the primary definition node of a multi-master replication system, open the Alter Publication Table dialog box by clicking the secondary mouse button on the Table node of the table to be modified and choose Alter Table. -![Selecting a table to alter](/../../images/image280.png) +![Selecting a table to alter](../../images/image280.png) **Step 4:** In the `Alter Publication Table` dialog box, if you saved the `ALTER TABLE` statements in a text file, make sure the DDL Script File option is selected, browse for this file, and click the `OK` button. -![Alter Publication Table dialog box with DDL script file](/../../images/image281.png) +![Alter Publication Table dialog box with DDL script file](../../images/image281.png) Alternatively, if you are directly entering the `ALTER TABLE` statements, select the DDL Script option instead of the DDL Script File option. Directly type in, or copy and paste the ALTER TABLE statements from your source into the text box. Click the `OK` button. -![Alter Publication Table dialog box with copy and paste](/../../images/image282.png) +![Alter Publication Table dialog box with copy and paste](../../images/image282.png) **Step 5:** If the `DDL replicated successfully message` box appears, the DDL change was successful across all databases. Click the `OK` button. -![DDL replicated successfully](/../../images/image283.png) +![DDL replicated successfully](../../images/image283.png) If DDL replication was not successful, the problem must be investigated and resolved on a case by case basis. Factors to look for include the following: diff --git a/product_docs/docs/eprs/6.2/07_common_operations/10_replicating_postgres_partitioned_tables.mdx b/product_docs/docs/eprs/6.2/07_common_operations/10_replicating_postgres_partitioned_tables.mdx index 751fbeb5213..8133eef332e 100644 --- a/product_docs/docs/eprs/6.2/07_common_operations/10_replicating_postgres_partitioned_tables.mdx +++ b/product_docs/docs/eprs/6.2/07_common_operations/10_replicating_postgres_partitioned_tables.mdx @@ -278,17 +278,17 @@ Follow the directions in Section [Creating a Publication](../06_mmr_operation/02 When creating the publication you must select the parent table along with the child tables. -![Creating a publication for a Postgres 9.x partitioned table](/../images/image284.png) +![Creating a publication for a Postgres 9.x partitioned table](../images/image284.png) The following shows the resulting replication tree for the partitioned table in the primary definition node: -![Publication containing a Postgres 9.x partitioned table](/../images/image285.png) +![Publication containing a Postgres 9.x partitioned table](../images/image285.png) Create additional primary nodes as described in Section [Creating Additional Primary nodes](../06_mmr_operation/03_creating_primary_nodes/#creating_primary_nodes). (For a single-master replication system, create the subscription database and subscription according to the directions in Section [Creating a Subscription](../05_smr_operation/03_creating_subscription/#creating_subscription).) The following shows the resulting multi-master replication system after you have added an additional primary node. -![MMR system with a Postgres 9.x partitioned table](/../images/image286.png) +![MMR system with a Postgres 9.x partitioned table](../images/image286.png) The partitioned table can now be kept synchronized on the primary nodes of the multi-master replication system. @@ -311,16 +311,16 @@ Follow the directions in Section [Creating a Publication](../06_mmr_operation/02 When creating the publication, only the parent table appears and is selected. -![Creating a publication for a Postgres 10 or later partitioned table](/../images/image287.png) +![Creating a publication for a Postgres 10 or later partitioned table](../images/image287.png) The following shows the resulting replication tree for the partitioned table in the primary definition node: -![Publication containing a Postgres 10 or later partitioned table](/../images/image288.png) +![Publication containing a Postgres 10 or later partitioned table](../images/image288.png) Create additional primary nodes as described in Section [Creating Additional Primary nodes](../06_mmr_operation/03_creating_primary_nodes/#creating_primary_nodes). (For a single-master replication system, create the subscription database and subscription according to the directions in Section [Creating a Subscription](../05_smr_operation/03_creating_subscription/#creating_subscription).) The following shows the resulting multi-master replication system after you have added an additional primary node. -![MMR system with a Postgres 10 or later partitioned table](/../images/image289.png) +![MMR system with a Postgres 10 or later partitioned table](../images/image289.png) The partitioned table can now be kept synchronized on the primary nodes of the multi-master replication system. diff --git a/product_docs/docs/eprs/6.2/07_common_operations/11_using_ssl_connections.mdx b/product_docs/docs/eprs/6.2/07_common_operations/11_using_ssl_connections.mdx index b2f7d1b785d..402b2c72253 100644 --- a/product_docs/docs/eprs/6.2/07_common_operations/11_using_ssl_connections.mdx +++ b/product_docs/docs/eprs/6.2/07_common_operations/11_using_ssl_connections.mdx @@ -348,7 +348,7 @@ For publication, subscription, and primary node databases, in the URL Options fi The following is an example of the Add Database dialog box with the `ssl=true` URL option. -![Add Database with SSL URL option](/../images/image290.png) +![Add Database with SSL URL option](../images/image290.png) !!! Note If you no longer wish to use an SSL connection to an xDB Replication Server database, you must completely delete the `ssl=true` text from the URL Options field of the Add Database or Update Database dialog box. Simply changing true to false does not have the effect of disabling the SSL option. diff --git a/product_docs/docs/eprs/6.2/09_data_validator/02_perform_datavalidation.mdx b/product_docs/docs/eprs/6.2/09_data_validator/02_perform_datavalidation.mdx index b9006aaeb2f..4b168ce6a6e 100644 --- a/product_docs/docs/eprs/6.2/09_data_validator/02_perform_datavalidation.mdx +++ b/product_docs/docs/eprs/6.2/09_data_validator/02_perform_datavalidation.mdx @@ -438,7 +438,7 @@ The log file contains the same content as displayed when the Data Validator is i The following is the diff file as displayed in a text editor: -![Data Validator diff file](/../images/image291.png) +![Data Validator diff file](../images/image291.png) The following example includes only tables `dept` and `emp` with the `-it` option when comparing the Oracle EDB schema against the Advanced Server public schema. diff --git a/product_docs/docs/eprs/6.2/10_appendix/02_upgrading_to_xdb6_2/02_upgrading_with_gui_installer.mdx b/product_docs/docs/eprs/6.2/10_appendix/02_upgrading_to_xdb6_2/02_upgrading_with_gui_installer.mdx index 7fe6f84d6e9..9c9edf7e84e 100644 --- a/product_docs/docs/eprs/6.2/10_appendix/02_upgrading_to_xdb6_2/02_upgrading_with_gui_installer.mdx +++ b/product_docs/docs/eprs/6.2/10_appendix/02_upgrading_to_xdb6_2/02_upgrading_with_gui_installer.mdx @@ -14,15 +14,15 @@ Perform the following steps to upgrade to xDB Replication Server 6.2 using the g **Step 4:** Following the acceptance of the license agreement in Step 11 of Section [Installing With Stack Builder or StackBuilder Plus](../../03_installation/01_installing_with_stackbuilder/#installing_with_stackbuilder), the Select Components screen appears, but with the entries grayed out. The old xDB Replication Server components are replaced by the new ones in the old xDB Replication Server’s directory location. Click the `Next` button. -![Select components](/../../images/image292.png) +![Select components](../../images/image292.png) **Step 5:** The Existing Installation screen confirms that an existing xDB Replication Server installation was found. Click the `Next` button to proceed with the upgrade. -![Existing installation](/../../images/image293.png) +![Existing installation](../../images/image293.png) **Step 6:** On the `Ready to Install` screen, click the `Next` button. -![Ready to install](/../../images/image294.png) +![Ready to install](../../images/image294.png) **Step 7:** The remaining screens that appear confirm completion of the installation process and allow you to exit from Stack Builder or StackBuilder Plus. diff --git a/product_docs/docs/eprs/6.2/10_appendix/03_resolving_problems/04_troubleshooting_areas.mdx b/product_docs/docs/eprs/6.2/10_appendix/03_resolving_problems/04_troubleshooting_areas.mdx index bc69c0868d0..c82339282bf 100644 --- a/product_docs/docs/eprs/6.2/10_appendix/03_resolving_problems/04_troubleshooting_areas.mdx +++ b/product_docs/docs/eprs/6.2/10_appendix/03_resolving_problems/04_troubleshooting_areas.mdx @@ -62,7 +62,7 @@ In the following example, the SMR publication database edb as well as the three The control schema must be removed from all four publication databases if it is determined that the control schema is corrupted in any of the four publication databases. -![Publication databases with shared controller database](/../../images/image295.png) +![Publication databases with shared controller database](../../images/image295.png) Finally, the subscription databases of SMR systems contain a control schema object, which must be deleted as well. @@ -409,7 +409,7 @@ admin_user=enterprisedb **Step 12:** In the replication tree you should see the following: -![Replication tree after removal of all control schema objects](/../../images/image296.png) +![Replication tree after removal of all control schema objects](../../images/image296.png) All the nodes under the SMR and MMR type nodes beneath the Publication Server node, and under the Subscription Server node no longer appear. diff --git a/product_docs/docs/eprs/6.2/10_appendix/04_miscellaneous_xdb_processing_topics/04_disable_foreign_key_constraints_for_snapshot_replication.mdx b/product_docs/docs/eprs/6.2/10_appendix/04_miscellaneous_xdb_processing_topics/04_disable_foreign_key_constraints_for_snapshot_replication.mdx index 834c01f64b9..cce6c4143dc 100644 --- a/product_docs/docs/eprs/6.2/10_appendix/04_miscellaneous_xdb_processing_topics/04_disable_foreign_key_constraints_for_snapshot_replication.mdx +++ b/product_docs/docs/eprs/6.2/10_appendix/04_miscellaneous_xdb_processing_topics/04_disable_foreign_key_constraints_for_snapshot_replication.mdx @@ -13,8 +13,8 @@ No user (not even a superuser) is allowed to directly modify the data in a Postg To verify that a user has the privilege to update the system catalog tables, select the user name under the Login Roles node in pgAdmin (Postgres Enterprise Manager Client in Advanced Server). The Update Catalogs property should be set to Yes. -![User with privilege to update system catalogs](/../../images/image297.png) +![User with privilege to update system catalogs](../../images/image297.png) If the Update Catalogs property is set to No, click the secondary mouse button on the user name in the Object Browser and choose Properties from the menu. Select the Role Privileges tab, check the **Can Modify Catalog Directly** box, and click the **OK** button. -![Granting system catalog update privilege](/../../images/image298.png) +![Granting system catalog update privilege](../../images/image298.png) diff --git a/product_docs/docs/eprs/6.2/10_appendix/04_miscellaneous_xdb_processing_topics/06_replicating_sql_server_sql_variant_data_type.mdx b/product_docs/docs/eprs/6.2/10_appendix/04_miscellaneous_xdb_processing_topics/06_replicating_sql_server_sql_variant_data_type.mdx index e02050173f3..e4687f6798e 100644 --- a/product_docs/docs/eprs/6.2/10_appendix/04_miscellaneous_xdb_processing_topics/06_replicating_sql_server_sql_variant_data_type.mdx +++ b/product_docs/docs/eprs/6.2/10_appendix/04_miscellaneous_xdb_processing_topics/06_replicating_sql_server_sql_variant_data_type.mdx @@ -61,4 +61,4 @@ At the bottom of the following Object Browser window, note the presence of the s > `CREATE TABLE MyTable …` would result in an object identifier name of mytable. > -> ![Subscription table with sql_variant column](/../../images/image299.png) +> ![Subscription table with sql_variant column](../../images/image299.png) diff --git a/src/components/advanced-search/results.js b/src/components/advanced-search/results.js index 3e61fc56a37..665b914eb42 100644 --- a/src/components/advanced-search/results.js +++ b/src/components/advanced-search/results.js @@ -109,7 +109,7 @@ export const AdvancedSearchResults = connectStateResults( if (queryLength === 0) { return (

- Please enter a search query to begin. + Enter a search query to begin.

); } diff --git a/src/components/card-decks.js b/src/components/card-decks.js index e465d68a475..1319233cede 100644 --- a/src/components/card-decks.js +++ b/src/components/card-decks.js @@ -13,7 +13,7 @@ const FullCard = ({ card }) => { iconName={iconName} className={`${ iconName === iconNames.DOTTED_BOX && 'opacity-1' - } mt-3 ml-3`} + } mt-3 ml-3 fill-orange`} width="100" height="100" /> diff --git a/src/components/search/formComps.js b/src/components/search/formComps.js index fd3bc77c59e..e42b3a1edd2 100644 --- a/src/components/search/formComps.js +++ b/src/components/search/formComps.js @@ -11,7 +11,7 @@ const Results = connectStateResults( ); const TryAdvancedSearch = connectStateResults(({ searchResults: res }) => ( -
+
{res && res.nbHits > 0 ? 'Not finding what you need?' : 'No results found.'} Try Advanced Search diff --git a/src/components/search/index.js b/src/components/search/index.js index adb5f5a9c79..84a819ad319 100644 --- a/src/components/search/index.js +++ b/src/components/search/index.js @@ -157,7 +157,7 @@ const SearchForm = ({ currentRefinement, refine, query }) => {
0 && focus && 'show' }`} > diff --git a/src/constants/product-stubs.js b/src/constants/product-stubs.js index 6deecd0d9fe..a37ed3103a8 100644 --- a/src/constants/product-stubs.js +++ b/src/constants/product-stubs.js @@ -2124,23 +2124,6 @@ export const productStubs = { }, ], }, - 3.5: { - sections: [ - { - title: 'User Guides', - column: 1, - links: [ - { - text: 'User Guide', - href: - 'https://www.enterprisedb.com/edb-docs/d/edb-postgres-failover-manager/user-guides/user-guide/3.5/toc.html', - pdf: - 'https://www.enterprisedb.com/edb-docs/static/docs/efm/3.5/EDB_Failover_Manager_Guide_v3.5.pdf', - }, - ], - }, - ], - }, }, hadoop_data_adapter: { '2.0.5': { diff --git a/src/styles/_dark.scss b/src/styles/_dark.scss index e675373584d..9ea595481cd 100644 --- a/src/styles/_dark.scss +++ b/src/styles/_dark.scss @@ -46,11 +46,13 @@ html.dark { border-top-color: $gray-800; } .search-form { - border-color: $gray-800 !important; + border: 1px solid $blue !important; background-color: $gray-900 !important; + border-width: 1px; #search-input { background-color: $gray-900 !important; + border-color: pink; } .form-control { @@ -162,6 +164,54 @@ html.dark { content: url('data:image/svg+xml;utf8,'); } } + + //Alert banner + .topbar.alert-primary { + background-color: $gray-800 !important; + border-color: $gray-700 !important; + border-left: none; + border-right: none; + color: $light; + } + + //Close icon on search + button.false.btn.btn-link { + svg.opacity-5 { + fill: $light; + } + } + + //Quick Search + .quick-search-container { + background: $gray-900; + border-top-color: $gray-700; + + //highlight + .dropdown-item.arrow-focus { + background-color: rgba($orange,.1); + } + //dropdown item + .dropdown-item, + .search-prompt { + color: $light; + } + .dropdown-item:hover, + .dropdown-item:active { + background-color: $gray-800; + color: $light !important; + } + } + + //Marks + .search-content mark { + color: rgba($orange, .5); + } + + //Advanced search badge counts + .search-filter-badge { + background-color: $gray-800; + color: $light; + } } .sun, @@ -206,3 +256,4 @@ html.dark { background-color: $gray-800 !important; cursor: pointer !important; } + diff --git a/src/styles/_search.scss b/src/styles/_search.scss index b3e794e0ca7..77d2a7fc166 100644 --- a/src/styles/_search.scss +++ b/src/styles/_search.scss @@ -6,13 +6,13 @@ } li { - margin-bottom: map-get($spacers, 3); + margin-bottom: map-get($spacers, 4); } mark { background-color: rgba($orange, 0.05); - border-bottom: 1px solid $orange; - font-weight: bolder; + font-weight: bold; + padding:0; } .dropdown-item { @@ -27,9 +27,8 @@ } .search-form { - border: 1px solid transparent; + border: 1px solid $blue; border-radius: $border-radius; - background-color: $input-bg; } .search-form.open, .search-form:focus-within { @@ -62,16 +61,35 @@ box-shadow: 0 1rem 1rem rgba(0, 0, 0, 0.15); } -.dropdown-item.arrow-focus { - @extend .dropdown-item, :focus; +.search-pane { + .dropdown-item { + font-size: 1.3rem; + } + + .dropdown-item.arrow-focus { + background-color: $gray-100; + } + + .dropdown-item:hover { + background: $gray-100; + } } .search-text-summary { - font-size: 1.1rem; + font-size: 1.4rem; } .badge.search-filter-badge { background-color: #ebeff2; color: #787D81; + font-weight: normal; +} + +#search-input { + background-color: white; } +.ais-Highlight { + font-size: 1.1rem; + font-weight: 500; +}