From 02fd5fc255bdd02f8bbbc233e16439f3e109ab30 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Wed, 30 Mar 2022 07:22:25 -0400 Subject: [PATCH 01/11] EPRS: 6.2.18 release --- .../10_printing_pdn_node_db_id.mdx | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/product_docs/docs/eprs/6.2/08_xdb_cli/03_xdb_cli_commands/10_printing_pdn_node_db_id.mdx b/product_docs/docs/eprs/6.2/08_xdb_cli/03_xdb_cli_commands/10_printing_pdn_node_db_id.mdx index 163f984b12f..112473615df 100644 --- a/product_docs/docs/eprs/6.2/08_xdb_cli/03_xdb_cli_commands/10_printing_pdn_node_db_id.mdx +++ b/product_docs/docs/eprs/6.2/08_xdb_cli/03_xdb_cli_commands/10_printing_pdn_node_db_id.mdx @@ -1,27 +1,27 @@ --- -title: "Printing the Primary definition node Database ID (printpdndbid)" +title: "Printing the Primary definition node Database ID (printmdndbid)" --- -**For MMR only:** The `printpdndbid` command prints the publication database ID of the primary definition node. +**For MMR only:** The `printmdndbid` command prints the publication database ID of the primary definition node. Synopsis -> `-printpdndbid -repsvrfile pubsvrfile` +`-printmdndbid -repsvrfile pubsvrfile` Parameters `pubsvrfile` -> The file containing the publication server login information. +The file containing the publication server login information. Examples The following example prints the publication database ID of the primary definition node. ```text -$ java -jar edb-repcli.jar -printPDNdbid -repsvrfile ~/pubsvrfile.prop -Printing PDN Publication database id... +$ java -jar edb-repcli.jar -printmdndbid -repsvrfile ~/pubsvrfile.prop +Printing MDN Publication database id... 3 ``` From 0b6c4a923fa42b07bbd6ce0783b7e3bb7bf3fe4d Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Wed, 30 Mar 2022 10:31:51 -0400 Subject: [PATCH 02/11] added stub file for the release notes --- .../6.2/eprs_rel_notes/11_eprs_rel_notes_6.2.18.mdx | 13 +++++++++++++ product_docs/docs/eprs/6.2/eprs_rel_notes/index.mdx | 1 + 2 files changed, 14 insertions(+) create mode 100644 product_docs/docs/eprs/6.2/eprs_rel_notes/11_eprs_rel_notes_6.2.18.mdx diff --git a/product_docs/docs/eprs/6.2/eprs_rel_notes/11_eprs_rel_notes_6.2.18.mdx b/product_docs/docs/eprs/6.2/eprs_rel_notes/11_eprs_rel_notes_6.2.18.mdx new file mode 100644 index 00000000000..08e4a791c61 --- /dev/null +++ b/product_docs/docs/eprs/6.2/eprs_rel_notes/11_eprs_rel_notes_6.2.18.mdx @@ -0,0 +1,13 @@ +--- +title: "Version 6.2.18" +--- + + +New features, enhancements, bug fixes, and other changes in EDB Postgres Replication Server 6.2.18 include the following: + +| Type | Description | +| ----------- |------------ | +| | | + + + diff --git a/product_docs/docs/eprs/6.2/eprs_rel_notes/index.mdx b/product_docs/docs/eprs/6.2/eprs_rel_notes/index.mdx index 77f62517dea..52292165aa3 100644 --- a/product_docs/docs/eprs/6.2/eprs_rel_notes/index.mdx +++ b/product_docs/docs/eprs/6.2/eprs_rel_notes/index.mdx @@ -8,6 +8,7 @@ The EDB Postgres Replication Server documentation describes the latest version o | Version | Release Date | | ------- | ------------ | +| [6.2.18](11_eprs_rel_notes_6.2.18) | 2022 Apr 01 | | [6.2.17](12_eprs_rel_notes_6.2.17) | 2022 Mar 03 | | [6.2.16](13_eprs_rel_notes_6.2.16) | 2021 Dec 09 | | [6.2.15](14_eprs_rel_notes_6.2.15) | 2021 Aug 30 | From 8dd3a521088be02e90154dd72c4f3d0d6978e678 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Sat, 2 Apr 2022 08:29:21 -0400 Subject: [PATCH 03/11] first attempt at XDB-1349 --- .../04_mmr_replication.mdx | 2 +- .../13_table_filters.mdx | 2 +- .../01_physical_components.mdx | 2 +- .../02_design_considerations.mdx | 2 +- .../02_creating_publication_mmr.mdx | 2 +- .../03_creating_primary_nodes.mdx | 2 +- .../6.2/06_mmr_operation/10_switching_pdn.mdx | 28 ++++--------------- .../06_removing_pub.mdx | 2 +- .../07_removing_pub_database.mdx | 2 +- .../09_offline_snapshot.mdx | 2 +- .../11_using_ssl_connections.mdx | 6 ++-- .../06_add_pub_database.mdx | 6 ++-- .../20_adding_tablefilters_to_publication.mdx | 6 ++-- ...1_updating_tablefilters_to_publication.mdx | 2 +- ...2_removing_tablefilters_to_publication.mdx | 2 +- .../03_xdb_cli_commands/25_set_pdn_node.mdx | 8 +++--- ...ilters_on_subscription_or_non_pdn_node.mdx | 4 +-- .../01_error_messages.mdx | 6 ++-- .../04_troubleshooting_areas.mdx | 6 +--- ..._of_table_level_user_privileges_on_mmr.mdx | 10 +++---- 20 files changed, 40 insertions(+), 62 deletions(-) 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 31040ac60f1..f371ae11655 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 @@ -10,7 +10,7 @@ The following definitions are used when referring to multi-master replication sy A primary node is a database participating in a multi-master replication system. -The database (primary node) in which the publication is initially defined is specially designated as the `primary definition node (PDN)`. There can be only one primary definition node at any given time, however, it is possible to change which primary node is the primary definition node. When it is important to make a distinction between the primary definition node and all other primary nodes that are not the primary definition node, the latter are referred to as `non-PDN nodes`. +The database (primary node) in which the publication is initially defined is specially designated as the `primary definition node (MDN)`. There can be only one primary definition node at any given time, however, it is possible to change which primary node is the primary definition node. When it is important to make a distinction between the primary definition node and all other primary nodes that are not the primary definition node, the latter are referred to as `non-MDN nodes`. The primary definition node has the following significance: 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 72ae973966a..6bdd83ef3f0 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 @@ -95,7 +95,7 @@ The `REPLICA IDENTITY FULL` setting is required on tables in the following datab - In a single-master replication system, table filters are defined in the primary database. Thus, the publication tables in the primary database requiring filter definitions must be altered to a `REPLICA IDENTITY FULL` setting, but only if the publication is not a snapshot-only publication. See [Snapshot-Only Publications](07_snapshot_only_publications/#snapshot_only_publications) for information on snapshot-only publications. - In a multi-master replication system, table filters are defined in the primary definition node. Thus, publication tables in the primary definition node requiring filter definitions must be altered to a `REPLICA IDENTITY FULL` setting. -- In a multi-master replication system, non-PDN nodes should not have their tables’ `REPLICA IDENTITY` option set to `FULL` unless transactions are expected to be targeted on those non-PDN nodes, and the transactions are to be filtered when they are replicated to the other primary nodes. +- In a multi-master replication system, non-MDN nodes should not have their tables’ `REPLICA IDENTITY` option set to `FULL` unless transactions are expected to be targeted on those non-MDN nodes, and the transactions are to be filtered when they are replicated to the other primary nodes. The `REPLICA IDENTITY FULL` setting on a source table ensures that certain types of transactions on the source table result in the proper updates to the target tables on which filters have been enabled. 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 cf740068959..f879485ac2e 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 @@ -48,7 +48,7 @@ The following sections describe each component in more detail. The publication server creates and manages the metadata for publications. When a publication is created, the publication server creates database objects in the control schema of the publication database to record metadata about the publication. -Whenever a primary node is added to a multi-master replication system, the publication server creates database objects in the control schema of the primary node for recording metadata. For non-PDN nodes, the publication server also calls EnterpriseDB’s Migration Toolkit to create the publication table definitions if so chosen at primary node creation time. +Whenever a primary node is added to a multi-master replication system, the publication server creates database objects in the control schema of the primary node for recording metadata. For non-MDN nodes, the publication server also calls EnterpriseDB’s Migration Toolkit to create the publication table definitions if so chosen at primary node creation time. !!! Note See [Control Schema and Control Schema Objects](#control_schema_and_objects) for information on the control schema. 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 6377f6e7354..7c41f6cc465 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 @@ -29,7 +29,7 @@ Keep the following points in mind when designing a replication system: - 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 replication system logical components using the xDB Replication Console or xDB Replication Server CLI starting with the publication database definitions of the non-MDN 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/06_mmr_operation/02_creating_publication_mmr.mdx b/product_docs/docs/eprs/6.2/06_mmr_operation/02_creating_publication_mmr.mdx index 54b5584a97f..2e0248594cd 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 @@ -69,7 +69,7 @@ When the publication database definition is successfully saved, a Publication Da **Figure 6-4: Replication tree after adding the primary definition node** -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. +The label `MDN` appears at the end of the node in the replication tree and in addition, the `MDN` field is set to Yes in the Property window to indicate this is the primary definition node. 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 de8c9047ac2..fd6e8730675 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 @@ -87,7 +87,7 @@ When the publication database definition is successfully saved, a Publication Da **Figure 6-17: Replication tree after adding an additional primary node** -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. +Unlike the primary definition node, the label MDN does not appear at the end of the node in the replication tree. The MDN field is set to No in the Property window to indicate this is not the primary definition node. In addition, a Publication node appears under the newly added primary node. This Publication node represents the publication in the primary definition node, which is replicated to 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 3c92f2ec88c..ac7d0d80c8c 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,36 +10,18 @@ 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) -**Figure 6-69: Selecting the primary node to set as the primary definition node** +**Step 3:** Click the secondary mouse button on the Publication Database node and choose `Set as MDN`. -**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) +**Step 4:** In the `Set as MDN` confirmation box, click the `Yes` button. -**Figure 6-70: Setting the primary definition node** - -**Step 4:** In the `Set as PDN` confirmation box, click the `Yes` button. - -![Set as PDN confirmation](../images/image180.png) - -**Figure 6-71: Set as PDN confirmation** **Step 5:** The selected master node is now the master definition node. -![Database promoted to master definition node](../images/image181.png) - -**Figure 6-72: Database promoted to primary definition node** - -**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) +**Step 6:** The value `Yes` in the MDN field of the Property window indicates this database is the primary definition node. -**Figure 6-73: Primary definition node (PDN) indicated by ‘Yes’ in the Property window** +The new primary definition node is moved to the top of the replication tree in the xDB Replication Console. -!!! 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. +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/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 93781338483..c85a436c5a8 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 @@ -6,7 +6,7 @@ title: "Removing a Publication" In a single-master replication system, a publication can be removed before its associated subscriptions are removed. See [Removing a Subscription](../../05_smr_operation/05_managing_subscription/05_removing_subscription/#removing_subscription) for directions to remove a subscription. -In a multi-master replication system, the publication is removed from under the Publication Database node representing the primary definition node. Before a publication can be removed, all non-PDN nodes must be removed. See [Removing a Publication Database](07_removing_pub_database/#removing_pub_database) for directions to remove a publication database definition of a primary node. +In a multi-master replication system, the publication is removed from under the Publication Database node representing the primary definition node. Before a publication can be removed, all non-MDN nodes must be removed. See [Removing a Publication Database](07_removing_pub_database/#removing_pub_database) for directions to remove a publication database definition of a primary node. Removing a publication does not delete the publication tables in the publication database. It removes the identity and association of these tables to xDB Replication Server so the tables remain in the database until the DBA deletes them with the `DROP TABLE SQL` statement. 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 1091888d612..2f2cdf43a78 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 @@ -20,7 +20,7 @@ Removing the Publication Database node representing the primary definition node - If the multi-master replication system is the only xDB replication system (that is, there are no single-master replication systems), then switch the controller database to the primary definition node if the designated controller database is not currently the same database as the primary definition node. - If there are one or more single-master replication systems in addition to the multi-master replication system, switch the controller database to a Postgres publication database of a single-master replication system. If none of the single-master publication databases is of type Postgres, and there are more than one Oracle or SQL Server publication databases, then you must create a Postgres publication database for a single-master replication system just for the purpose of designating it as the controller database. -- All Publication Database nodes representing non-PDN nodes must be removed. Repeat the process described in this section for each such primary node. +- All Publication Database nodes representing non-MDN nodes must be removed. Repeat the process described in this section for each such primary node. - The publication under the Publication Database node representing the primary definition node must be removed. See [Removing a Publication](06_removing_pub/#removing_pub) for directions on removing a publication. - Remove the Publication Database node representing the primary definition node using the process described in this section. diff --git a/product_docs/docs/eprs/6.2/07_common_operations/09_offline_snapshot.mdx b/product_docs/docs/eprs/6.2/07_common_operations/09_offline_snapshot.mdx index d7ddcb08167..3a4a9d5f0db 100644 --- a/product_docs/docs/eprs/6.2/07_common_operations/09_offline_snapshot.mdx +++ b/product_docs/docs/eprs/6.2/07_common_operations/09_offline_snapshot.mdx @@ -4,7 +4,7 @@ title: "Loading Tables From an External Data Source (Offline Snapshot)" -There may be circumstances when you want to initially load your target tables (subscription tables of a single-master replication system, or non-PDN nodes of a multi-master replication system) using a method other than the snapshot replication functionality of xDB Replication Server. This is referred to as using an offline snapshot. +There may be circumstances when you want to initially load your target tables (subscription tables of a single-master replication system, or non-MDN nodes of a multi-master replication system) using a method other than the snapshot replication functionality of xDB Replication Server. This is referred to as using an offline snapshot. For example, you might initially load the tables by running the Migration Toolkit from the command line or by using a backup from an external data source. When you load the target tables using an offline snapshot, special preparations must be taken to account for the following deviations from the default target table creation and loading process: 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 ed55ba346af..7b6fb946edc 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 @@ -16,8 +16,8 @@ For a single-master replication system, the following connections can be made to For a multi-master replication system, the following connections can be made to Postgres databases enabled with SSL: -- Publication server connection to the primary definition node and the non-PDN nodes. -- Migration Toolkit connection to the primary definition node and the non-PDN nodes. +- Publication server connection to the primary definition node and the non-MDN nodes. +- Migration Toolkit connection to the primary definition node and the non-MDN nodes. !!! Note SSL connections are not used from the xDB Replication Console or the xDB Replication Server Command Line Interface. The xDB user interfaces communicate with the publication server and subscription server, which in turn connect to the publication/subscription databases or primary nodes. @@ -376,7 +376,7 @@ The SSL URL option informs Java to use SSL when the publication server or subscr The configuration steps where these options are specified are as follows: - For using SSL connections in a single-master replication system, the URL options must be specified as shown in Section [Adding a Publication Database](../05_smr_operation/02_creating_publication/02_adding_pub_database/#adding_pub_database) for the publication database and in Section [Adding a Subscription Database](../05_smr_operation/03_creating_subscription/02_adding_subscription_database/#adding_subscription_database) for the subscription databases. -- For using SSL connections in a multi-master replication system, the URL options must be specified as shown in Section [Adding the Primary definition node](../06_mmr_operation/02_creating_publication_mmr/#adding_pdn) for the primary definition node and in Section [Creating Additional Primary nodes](../06_mmr_operation/03_creating_primary_nodes/#creating_primary_nodes) for the non-PDN nodes. +- For using SSL connections in a multi-master replication system, the URL options must be specified as shown in Section [Adding the Primary definition node](../06_mmr_operation/02_creating_publication_mmr/#adding_pdn) for the primary definition node and in Section [Creating Additional Primary nodes](../06_mmr_operation/03_creating_primary_nodes/#creating_primary_nodes) for the non-MDN nodes. Earlier we created self-signed certificates for the database server by specifying the value of the CN field as the database user name (for example, postgres or enterprisedb, and so on). In this case, we use the “verify-ca” value for sslmode parameter to indicate the server certificate is validated against the CA. We do this because the hostname given in the command Add Database or Update Database could not be verified against CN value present certificate, which is the database user name. diff --git a/product_docs/docs/eprs/6.2/08_xdb_cli/03_xdb_cli_commands/06_add_pub_database.mdx b/product_docs/docs/eprs/6.2/08_xdb_cli/03_xdb_cli_commands/06_add_pub_database.mdx index cc31e300d92..60b5c769e2e 100644 --- a/product_docs/docs/eprs/6.2/08_xdb_cli/03_xdb_cli_commands/06_add_pub_database.mdx +++ b/product_docs/docs/eprs/6.2/08_xdb_cli/03_xdb_cli_commands/06_add_pub_database.mdx @@ -79,7 +79,7 @@ Parameters `filterid_n` -> **For MMR only:** Applies to non-PDN nodes. Comma-separated list of filter IDs identifying the filter rules from the set of available table filters to enable on the corresponding tables in the new primary node. Use the printpubfilterslist command to obtain the filter IDs for the available filter rules in the publication (see [Printing a List of Filters in a Publication](17_print_publications_filters_list/#print_publications_filters_list)). Note: There must be no white space between the comma and filter IDs.' +> **For MMR only:** Applies to non-MDN nodes. Comma-separated list of filter IDs identifying the filter rules from the set of available table filters to enable on the corresponding tables in the new primary node. Use the printpubfilterslist command to obtain the filter IDs for the available filter rules in the publication (see [Printing a List of Filters in a Publication](17_print_publications_filters_list/#print_publications_filters_list)). Note: There must be no white space between the comma and filter IDs.' `-repgrouptype` @@ -87,14 +87,14 @@ Parameters `-replicatepubschema` -> **For MMR only:** Applies to non-PDN nodes. Set this option to true if you want the publication table definitions replicated from the primary definition node when creating a new primary node. Set this option to false if you have already created the table definitions in the new primary node. If omitted, the default is true. Do not specify this parameter when creating the primary definition node. +> **For MMR only:** Applies to non-MDN nodes. Set this option to true if you want the publication table definitions replicated from the primary definition node when creating a new primary node. Set this option to false if you have already created the table definitions in the new primary node. If omitted, the default is true. Do not specify this parameter when creating the primary definition node. > > !!! Note > (For MMR only): Unless you intend to use the offline snapshot technique (see [Loading Tables From an External Data Source (Offline Snapshot)](../../07_common_operations/09_offline_snapshot/#offline_snapshot), it is suggested that you specify this option. 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 a Synchronization](42_perform_synchronization/#perform_synchronization)) or by a schedule (see [Configuring a Multi-Master Schedule](44_configure_mmr_schedule/#configure_mmr_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 [Take a Multi-Master Snapshot](41_taking_mmr_snapshot/#taking_mmr_snapshot)). `-initialsnapshot` -> **For MMR only:** Applies to non-PDN nodes. Specify this option if you want an initial snapshot replication to be performed when creating the primary node. Omit this option if you do not want an initial snapshot replication to be performed when creating the primary node. +> **For MMR only:** Applies to non-MDN nodes. Specify this option if you want an initial snapshot replication to be performed when creating the primary node. Omit this option if you do not want an initial snapshot replication to be performed when creating the primary node. !!! Note **(For MMR only)** Unless you intend to use the offline snapshot technique (see [Loading Tables From an External Data Source (Offline Snapshot)](../../07_common_operations/09_offline_snapshot/#offline_snapshot)), it is suggested that you specify this option. 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 a Synchronization](42_perform_synchronization/#perform_synchronization)) or by a schedule (see [Configuring a Multi-Master Schedule](44_configure_mmr_schedule/#configure_mmr_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 Section [Take a Multi-Master Snapshot](41_taking_mmr_snapshot/#taking_mmr_snapshot)) or by a schedule (see [Configuring a Multi-Master Schedule](44_configure_mmr_schedule/#configure_mmr_schedule)). diff --git a/product_docs/docs/eprs/6.2/08_xdb_cli/03_xdb_cli_commands/20_adding_tablefilters_to_publication.mdx b/product_docs/docs/eprs/6.2/08_xdb_cli/03_xdb_cli_commands/20_adding_tablefilters_to_publication.mdx index 77ece7c5b6d..714cd178190 100644 --- a/product_docs/docs/eprs/6.2/08_xdb_cli/03_xdb_cli_commands/20_adding_tablefilters_to_publication.mdx +++ b/product_docs/docs/eprs/6.2/08_xdb_cli/03_xdb_cli_commands/20_adding_tablefilters_to_publication.mdx @@ -6,11 +6,11 @@ title: "Adding Table Filters to a Publication (addfilter)" The `addfilter` command adds the definition of table filter rules to the specified publication. -This makes the filter rules available for subsequent enablement on target subscriptions or non-PDN nodes. +This makes the filter rules available for subsequent enablement on target subscriptions or non-MDN nodes. -Enabling a filter rule on a specified, target subscription or non-PDN node results in the filtering of data during replication from the source table to the target table. +Enabling a filter rule on a specified, target subscription or non-MDN node results in the filtering of data during replication from the source table to the target table. -If the filter rule is not enabled on a target subscription or non-PDN node, then it has no impact during replication on such subscription or non-PDN node. See [Enabling Filters on a Subscription or Non-PDN Node](38_enable_filters_on_subscription_or_non_pdn_node/#enable_filters_on_subscription_or_non_pdn_node) for information on enabling table filter rules. +If the filter rule is not enabled on a target subscription or non-MDN node, then it has no impact during replication on such subscription or non-MDN node. See [Enabling Filters on a Subscription or Non-MDN Node](38_enable_filters_on_subscription_or_non_pdn_node/#enable_filters_on_subscription_or_non_pdn_node) for information on enabling table filter rules. Synopsis diff --git a/product_docs/docs/eprs/6.2/08_xdb_cli/03_xdb_cli_commands/21_updating_tablefilters_to_publication.mdx b/product_docs/docs/eprs/6.2/08_xdb_cli/03_xdb_cli_commands/21_updating_tablefilters_to_publication.mdx index deab19aca42..2143098b6d7 100644 --- a/product_docs/docs/eprs/6.2/08_xdb_cli/03_xdb_cli_commands/21_updating_tablefilters_to_publication.mdx +++ b/product_docs/docs/eprs/6.2/08_xdb_cli/03_xdb_cli_commands/21_updating_tablefilters_to_publication.mdx @@ -16,7 +16,7 @@ Synopsis [ "filterid_2:filterclause_2" ] ... ``` -The next, subsequent replication to any target subscriptions or non-PDN nodes on which these filter rules had been enabled reflects the changes to the filter clauses. +The next, subsequent replication to any target subscriptions or non-MDN nodes on which these filter rules had been enabled reflects the changes to the filter clauses. See [Table Filters](../../02_overview/02_replication_concepts_and_definitions/13_table_filters/#table_filters) for additional information on table filters. diff --git a/product_docs/docs/eprs/6.2/08_xdb_cli/03_xdb_cli_commands/22_removing_tablefilters_to_publication.mdx b/product_docs/docs/eprs/6.2/08_xdb_cli/03_xdb_cli_commands/22_removing_tablefilters_to_publication.mdx index 3e96a605fb0..025cf9e28d2 100644 --- a/product_docs/docs/eprs/6.2/08_xdb_cli/03_xdb_cli_commands/22_removing_tablefilters_to_publication.mdx +++ b/product_docs/docs/eprs/6.2/08_xdb_cli/03_xdb_cli_commands/22_removing_tablefilters_to_publication.mdx @@ -14,7 +14,7 @@ Synopsis -filterid filterid ``` -The removed filter rule no longer applies to any target subscriptions or non-PDN nodes on which the filter rule had been enabled. +The removed filter rule no longer applies to any target subscriptions or non-MDN nodes on which the filter rule had been enabled. See [Table Filters](../../02_overview/02_replication_concepts_and_definitions/13_table_filters/#table_filters) for additional information on table filters. diff --git a/product_docs/docs/eprs/6.2/08_xdb_cli/03_xdb_cli_commands/25_set_pdn_node.mdx b/product_docs/docs/eprs/6.2/08_xdb_cli/03_xdb_cli_commands/25_set_pdn_node.mdx index 6da01806a05..8f619416dde 100644 --- a/product_docs/docs/eprs/6.2/08_xdb_cli/03_xdb_cli_commands/25_set_pdn_node.mdx +++ b/product_docs/docs/eprs/6.2/08_xdb_cli/03_xdb_cli_commands/25_set_pdn_node.mdx @@ -9,7 +9,7 @@ title: "Setting the master definition node (setasmdn)" Synopsis ```text --setaspdn pubdbid +-setasmdn pubdbid –repsvrfile pubsvrfile ``` @@ -30,7 +30,7 @@ Examples The following example sets the primary node with publication database `ID 9` as the primary definition node. ```text -$ java -jar edb-repcli.jar -setasPDN 9 -repsvrfile ~/pubsvrfile.prop -Updating the database node to be promoted as the new PDN node. -The database has been successfully promoted as the new PDN node. +$ java -jar edb-repcli.jar -setasMDN 9 -repsvrfile ~/pubsvrfile.prop +Updating the database node to be promoted as the new MDN node. +The database has been successfully promoted as the new MDN node. ``` diff --git a/product_docs/docs/eprs/6.2/08_xdb_cli/03_xdb_cli_commands/39_disable_filters_on_subscription_or_non_pdn_node.mdx b/product_docs/docs/eprs/6.2/08_xdb_cli/03_xdb_cli_commands/39_disable_filters_on_subscription_or_non_pdn_node.mdx index 9f9b5de0dd7..b5938f085b2 100644 --- a/product_docs/docs/eprs/6.2/08_xdb_cli/03_xdb_cli_commands/39_disable_filters_on_subscription_or_non_pdn_node.mdx +++ b/product_docs/docs/eprs/6.2/08_xdb_cli/03_xdb_cli_commands/39_disable_filters_on_subscription_or_non_pdn_node.mdx @@ -25,7 +25,7 @@ Disable the filter rule as follows: **For MMR:** Use the disablefilter command or the xDB Replication Console. (see [Enabling/Disabling Table Filters on a Primary node](../../06_mmr_operation/09_enable_disable_table_filters/#enable_disable_table_filters)). -Disabling a filter rule does not remove its definition from the publication. Thus, the filter rule still exists and can still be enabled on target subscriptions or non-PDN nodes. +Disabling a filter rule does not remove its definition from the publication. Thus, the filter rule still exists and can still be enabled on target subscriptions or non-MDN nodes. To remove a filter rule so that it no longer exists, perform the following: For either SMR or MMR: Use the `removefilter` command (see [Removing a Table Filter from a Publication](22_removing_tablefilters_to_publication/#removing_tablefilters_to_publication)) or the xDB Replication Console (see [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)). @@ -41,7 +41,7 @@ The file containing the publication server login information. `dbid` -> **For MMR only:** The publication database ID of the non-PDN node containing the tables on which the filter rules are to be disabled. +> **For MMR only:** The publication database ID of the non-MDN node containing the tables on which the filter rules are to be disabled. `filterid_n` diff --git a/product_docs/docs/eprs/6.2/10_appendix/03_resolving_problems/01_error_messages.mdx b/product_docs/docs/eprs/6.2/10_appendix/03_resolving_problems/01_error_messages.mdx index 5960bf4af2c..b0cb1d193ad 100644 --- a/product_docs/docs/eprs/6.2/10_appendix/03_resolving_problems/01_error_messages.mdx +++ b/product_docs/docs/eprs/6.2/10_appendix/03_resolving_problems/01_error_messages.mdx @@ -132,7 +132,7 @@ Occurs when attempting to add a subscription database. Verify that the xDB Repli **Problem** -The database type for the selected database is different than that of the PDN database. Each database should be of the same type in a MMR cluster. +The database type for the selected database is different than that of the MDN database. Each database should be of the same type in a MMR cluster. **Resolution** @@ -220,7 +220,7 @@ Occurs when creating an Oracle publication or subscription database definition. **Problem** -`No Publication found on PDN node, additional Primary node cannot join MMR cluster.` +`No Publication found on MDN node, additional Primary node cannot join MMR cluster.` **Resolution** @@ -236,7 +236,7 @@ Synchronization replication failed due to the unavailability of a target databas **Problem** -`One or more primary database node(s) are defined against this publication. Removing the publication will invalidate the PDN.` +`One or more primary database node(s) are defined against this publication. Removing the publication will invalidate the MDN.` **Resolution** 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 2a669a2ae0f..5c2f84fc6b1 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 @@ -58,14 +58,10 @@ The same control schema deletion procedure must be performed in all publication From the viewpoint of the xDB Replication Console replication tree, a publication server that connects to the controller database has subordinate to it, the publication databases sharing the same control schema information. -In the following example, the SMR publication database edb as well as the three MMR primary node databases `PDNnode`, `MMRnode_a`, and `MMRnode_b` are all managed by the same publication server, which connects to the controller database designated in the xDB Replication Configuration file. Thus, all publication databases `edb`, `PDNnode`, `MMRnode_a`, and `MMRnode_b` contain what should be the same control schema information. +In the following example, the SMR publication database edb as well as the three MMR primary node databases `mdnnode`, `MMRnode_a`, and `MMRnode_b` are all managed by the same publication server, which connects to the controller database designated in the xDB Replication Configuration file. Thus, all publication databases `edb`, `mdnnode`, `MMRnode_a`, and `MMRnode_b` contain what should be the same control schema information. 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) - -**Figure 10-4: Publication databases with shared controller database** - Finally, the subscription databases of SMR systems contain a control schema object, which must be deleted as well. In the preceding example, subscription database `subdb` contains a control schema object that may have to be deleted if control schema deletion is performed on the publication database. diff --git a/product_docs/docs/eprs/6.2/10_appendix/04_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/13_skipping_grants_of_table_level_user_privileges_on_mmr.mdx b/product_docs/docs/eprs/6.2/10_appendix/04_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/13_skipping_grants_of_table_level_user_privileges_on_mmr.mdx index 88471bb6cd5..34ea1d632ee 100644 --- a/product_docs/docs/eprs/6.2/10_appendix/04_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/13_skipping_grants_of_table_level_user_privileges_on_mmr.mdx +++ b/product_docs/docs/eprs/6.2/10_appendix/04_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/13_skipping_grants_of_table_level_user_privileges_on_mmr.mdx @@ -7,15 +7,15 @@ title: "Skipping Grants of Table Level User Privileges on MMR Target Tables" !!! Note This option applies to the publication server only. -When creating non-PDN nodes in a multi-master replication system, the publication server creates the publication tables and their corresponding shadow tables in the non-PDN node database. +When creating non-MDN nodes in a multi-master replication system, the publication server creates the publication tables and their corresponding shadow tables in the non-MDN node database. -When `skipTablePrivileges` is set to false, which is the default value, the database user privileges on the publication tables in the primary definition node are granted to the same database users on the publication tables in the newly created non-PDN node. +When `skipTablePrivileges` is set to false, which is the default value, the database user privileges on the publication tables in the primary definition node are granted to the same database users on the publication tables in the newly created non-MDN node. -The required privileges are also granted to these database users on the corresponding shadow tables in the non-PDN node so these database users can perform updates on the publication tables and the changes are recorded in the corresponding shadow tables. This enables proper synchronization replication of any such changes. +The required privileges are also granted to these database users on the corresponding shadow tables in the non-MDN node so these database users can perform updates on the publication tables and the changes are recorded in the corresponding shadow tables. This enables proper synchronization replication of any such changes. -This granting of privileges occurs only for database users with privileges on the primary definition node publication tables at the time the non-PDN node is defined using the xDB Replication Console or the xDB Replication Server CLI. If you do not want the publication server to grant these database user privileges to the non-PDN publication tables and shadow tables when defining the non-PDN node, set `skipTablePrivileges` to true. In this case, you must explicitly grant the privileges on the publication tables and corresponding shadow tables in the non-PDN node for any database user that you wish to provide update access to on these tables. See Step 2 of Section [Postgres Publication Database](../../../05_smr_operation/01_prerequisites/04_preparing_pub_database/#postgres_pub_db) for information regarding the required privileges. +This granting of privileges occurs only for database users with privileges on the primary definition node publication tables at the time the non-MDN node is defined using the xDB Replication Console or the xDB Replication Server CLI. If you do not want the publication server to grant these database user privileges to the non-MDN publication tables and shadow tables when defining the non-MDN node, set `skipTablePrivileges` to true. In this case, you must explicitly grant the privileges on the publication tables and corresponding shadow tables in the non-MDN node for any database user that you wish to provide update access to on these tables. See Step 2 of Section [Postgres Publication Database](../../../05_smr_operation/01_prerequisites/04_preparing_pub_database/#postgres_pub_db) for information regarding the required privileges. -This usage would typically be for the case where different database users are to access the non-PDN node publication tables than the database users who access the primary definition node publication tables. +This usage would typically be for the case where different database users are to access the non-MDN node publication tables than the database users who access the primary definition node publication tables. `skipTablePrivileges={true | false}` From 9efcf6b5736ebbaf4b359213ef3e71fcb99c51a9 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Sat, 2 Apr 2022 09:31:53 -0400 Subject: [PATCH 04/11] missed one --- ...nable_filters_on_subscription_or_non_pdn_node.mdx | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/product_docs/docs/eprs/6.2/08_xdb_cli/03_xdb_cli_commands/38_enable_filters_on_subscription_or_non_pdn_node.mdx b/product_docs/docs/eprs/6.2/08_xdb_cli/03_xdb_cli_commands/38_enable_filters_on_subscription_or_non_pdn_node.mdx index 47ba18b6558..ade05300f83 100644 --- a/product_docs/docs/eprs/6.2/08_xdb_cli/03_xdb_cli_commands/38_enable_filters_on_subscription_or_non_pdn_node.mdx +++ b/product_docs/docs/eprs/6.2/08_xdb_cli/03_xdb_cli_commands/38_enable_filters_on_subscription_or_non_pdn_node.mdx @@ -1,12 +1,12 @@ --- -title: "Enabling Filters on a Subscription or Non-PDN Node (enablefilter)" +title: "Enabling Filters on a Subscription or Non-MDN Node (enablefilter)" --- The `enablefilter` command enables one or more filter rules on a single-master replication system subscription or on a multi-master replication system primary node other than the primary definition node. -The `enablefilter` command is used when it is desired to apply a filter rule to a subscription or a non-pdn node, but the filter rule did not yet exist or it was neglected to be included with the subscription or the non-pdn node when these components were initially created. +The `enablefilter` command is used when it is desired to apply a filter rule to a subscription or a non-MDN node, but the filter rule did not yet exist or it was neglected to be included with the subscription or the non-MDN node when these components were initially created. Synopsis @@ -17,7 +17,7 @@ Synopsis -filterids filterid_1 [ filterid_2 ] ... ``` -Enabling a filter rule applies it to the specified, target subscription or non-pdn node, and thus filters the data during replication from the source table to the target table. +Enabling a filter rule applies it to the specified, target subscription or non-MDN node, and thus filters the data during replication from the source table to the target table. See [Table Filters](../../02_overview/02_replication_concepts_and_definitions/13_table_filters/#table_filters) for additional information on table filters. @@ -39,7 +39,7 @@ Enable the filter rule as follows: **For MMR:** Use the `enablefilter` command or the xDB Replication Console (see [Enabling/Disabling Table Filters on a Primary node](../../06_mmr_operation/09_enable_disable_table_filters/#enable_disable_table_filters). -Once a filter rule has been enabled, it filters the data during replication from the source table to the target table. A filter rule can subsequently be disabled so that it no longer filters the data during replication to the target table (see [Disabling Filters on a Subscription or Non-PDN Node](39_disable_filters_on_subscription_or_non_pdn_node/#disable_filters_on_subscription_or_non_pdn_node)). +Once a filter rule has been enabled, it filters the data during replication from the source table to the target table. A filter rule can subsequently be disabled so that it no longer filters the data during replication to the target table (see [Disabling Filters on a Subscription or Non-MDN Node](39_disable_filters_on_subscription_or_non_pdn_node/#disable_filters_on_subscription_or_non_pdn_node)). Parameters @@ -53,11 +53,11 @@ Parameters `dbid` -> **For MMR only:** The publication database ID of the non-PDN node containing the tables on which the filter rules are to be enabled. +> **For MMR only:** The publication database ID of the non-MDN node containing the tables on which the filter rules are to be enabled. `filterid_n` -> One or more filter IDs separated by space characters identifying the filter rules from the set of available table filters to enable on the corresponding tables in the SMR subscription specified by subname or in the MMR non-PDN node specified by `dbid`. Use the `printpubfilterslist` command to obtain the filter IDs for the available filter rules in the publication (see [Printing a List of Filters in a Publication](17_print_publications_filters_list/#print_publications_filters_list)). +> One or more filter IDs separated by space characters identifying the filter rules from the set of available table filters to enable on the corresponding tables in the SMR subscription specified by subname or in the MMR non-MDN node specified by `dbid`. Use the `printpubfilterslist` command to obtain the filter IDs for the available filter rules in the publication (see [Printing a List of Filters in a Publication](17_print_publications_filters_list/#print_publications_filters_list)). Examples From fe05caeb37d542cfc36c5f430ea3ce633192dcbf Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Sun, 3 Apr 2022 06:02:06 -0400 Subject: [PATCH 05/11] addressed XDB-1378 --- .../01_prerequisites/04_preparing_pub_database.mdx | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) 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 8f07d7a371a..3fdb53fa788 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 @@ -36,14 +36,14 @@ The setup instructions for using an Oracle 12c publication database or subscript **Step 1:** Create a database user name 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. -!!! Note - (For Oracle 12c Pluggable Database): The publication database user can be an Oracle local user or a common user. The local user exists within and has access to only a single, user-created pluggable database (PDB), which is to be used as the publication database. Common user names typically begin with `C##` or `c##` and can access multiple pluggable databases. +!!! Note Notes + - (For Oracle 12c Pluggable Database): The publication database user can be an Oracle local user or a common user. The local user exists within and has access to only a single, user-created pluggable database (PDB), which is to be used as the publication database. Common user names typically begin with `C##` or `c##` and can access multiple pluggable databases. -!!! Note - (For Oracle 12c Pluggable Database): Creation and granting of privileges for a local user must be done while connected to the pluggable database to be used as the publication database. Creation of a common user must be done within the Oracle 12c root container `CDB$ROOT`. Granting of privileges to the common user must be done while connected to the pluggable database to be used as the publication database. + - (For Oracle 12c Pluggable Database): Creation and granting of privileges for a local user must be done while connected to the pluggable database to be used as the publication database. Creation of a common user must be done within the Oracle 12c root container `CDB$ROOT`. Granting of privileges to the common user must be done while connected to the pluggable database to be used as the publication database. -!!! Note - (For Oracle 12c Non-Container Database): Creation and granting of privileges to the publication database user are performed in the same manner as for Oracle versions prior to 12c. + - (For Oracle 12c Non-Container Database): Creation and granting of privileges to the publication database user are performed in the same manner as for Oracle versions prior to 12c. + + - If you enable flashback functionality for the Oracle published table, you must also give the publication database user flashback privileges for the table. 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)). From c2be2376dc6440250d7f654359ee80040ffe2a16 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Sun, 3 Apr 2022 06:07:08 -0400 Subject: [PATCH 06/11] updated rel notes --- .../eprs/6.2/eprs_rel_notes/11_eprs_rel_notes_6.2.18.mdx | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/product_docs/docs/eprs/6.2/eprs_rel_notes/11_eprs_rel_notes_6.2.18.mdx b/product_docs/docs/eprs/6.2/eprs_rel_notes/11_eprs_rel_notes_6.2.18.mdx index 08e4a791c61..9e973fe3378 100644 --- a/product_docs/docs/eprs/6.2/eprs_rel_notes/11_eprs_rel_notes_6.2.18.mdx +++ b/product_docs/docs/eprs/6.2/eprs_rel_notes/11_eprs_rel_notes_6.2.18.mdx @@ -5,9 +5,10 @@ title: "Version 6.2.18" New features, enhancements, bug fixes, and other changes in EDB Postgres Replication Server 6.2.18 include the following: -| Type | Description | -| ----------- |------------ | -| | | +| Type | Description | +| ------------ |------------ | +| Security Fix | The log4j component version bundled with Replication Server 6.2 has been identified as being affected by CVE-2019-17571. The log4j version has been upgraded to the latest patched version to address this vulnerability. | +| Bug Fix | Fixed the issue that caused the Publication creation failure when index name of the Publication table is same as of another table index in a different schema [Support Ticket #79822]. | From b852f00327e08bc1de3fa2f0aa19198bfd6c2eb4 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Sun, 3 Apr 2022 06:36:23 -0400 Subject: [PATCH 07/11] added code to note --- .../01_prerequisites/04_preparing_pub_database.mdx | 3 +++ 1 file changed, 3 insertions(+) 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 3fdb53fa788..a0e9402a14a 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 @@ -44,6 +44,9 @@ The setup instructions for using an Oracle 12c publication database or subscript - (For Oracle 12c Non-Container Database): Creation and granting of privileges to the publication database user are performed in the same manner as for Oracle versions prior to 12c. - If you enable flashback functionality for the Oracle published table, you must also give the publication database user flashback privileges for the table. + ``` + GRANT flashback ON schema_name.table_name to pubuser; + ``` 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)). From 6c23508f204c56f3c057757e7e4ad935a023b1f7 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Mon, 4 Apr 2022 07:09:40 -0400 Subject: [PATCH 08/11] added note to 7 (XDB-1378) --- .../04_preparing_pub_database.mdx | 15 +++++++++------ 1 file changed, 9 insertions(+), 6 deletions(-) diff --git a/product_docs/docs/eprs/7/05_smr_operation/01_prerequisites/04_preparing_pub_database.mdx b/product_docs/docs/eprs/7/05_smr_operation/01_prerequisites/04_preparing_pub_database.mdx index 9c26e672bbc..f19541a8ac1 100644 --- a/product_docs/docs/eprs/7/05_smr_operation/01_prerequisites/04_preparing_pub_database.mdx +++ b/product_docs/docs/eprs/7/05_smr_operation/01_prerequisites/04_preparing_pub_database.mdx @@ -34,14 +34,17 @@ The setup instructions for using an Oracle 12c publication database or subscript **Step 1:** Create a database user name for the publication database user. The publication database user name must have a password, and it must be able to create a database session. The publication database user becomes the owner of the control schema objects that are created in the publication database to track, control, and record the replication process and history. -!!! Note - For Oracle 12c pluggable database: The publication database user can be an Oracle local user or a common user. The local user exists in and has access to only a single, user-created pluggable database (PDB) to use as the publication database. Common user names typically begin with `C##` or `c##` and can access multiple pluggable databases. +!!! Note Notes + - (For Oracle 12c Pluggable Database): The publication database user can be an Oracle local user or a common user. The local user exists within and has access to only a single, user-created pluggable database (PDB), which is to be used as the publication database. Common user names typically begin with `C##` or `c##` and can access multiple pluggable databases. -!!! Note - For Oracle 12c pluggable database: You must create and grant privileges for a local user while connected to the pluggable database to use as the publication database. Create a common user in the Oracle 12c root container `CDB$ROOT`. Grant privileges to the common user while connected to the pluggable database to use as the publication database. + - (For Oracle 12c Pluggable Database): Creation and granting of privileges for a local user must be done while connected to the pluggable database to be used as the publication database. Creation of a common user must be done within the Oracle 12c root container `CDB$ROOT`. Granting of privileges to the common user must be done while connected to the pluggable database to be used as the publication database. -!!! Note - For Oracle 12c non-container database: Create and grant privileges to the publication database user in the same manner as for Oracle versions prior to 12c. + - (For Oracle 12c Non-Container Database): Creation and granting of privileges to the publication database user are performed in the same manner as for Oracle versions prior to 12c. + + - If you enable flashback functionality for the Oracle published table, you must also give the publication database user flashback privileges for the table. + ``` + GRANT flashback ON schema_name.table_name to pubuser; + ``` When creating the publication database definition, enter the publication database user name in the Publication Service – Add Database dialog box (see [Adding a publication database](../02_creating_publication/02_adding_pub_database/#adding_pub_database)). From 847fb5480c010f4854c9fd3f1e02a417a72a5653 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Mon, 4 Apr 2022 07:42:24 -0400 Subject: [PATCH 09/11] fixed case in 6.2 -setasmdn started 7 changes --- .../eprs/6.2/08_xdb_cli/03_xdb_cli_commands/25_set_pdn_node.mdx | 2 +- .../04_mmr_replication.mdx | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/product_docs/docs/eprs/6.2/08_xdb_cli/03_xdb_cli_commands/25_set_pdn_node.mdx b/product_docs/docs/eprs/6.2/08_xdb_cli/03_xdb_cli_commands/25_set_pdn_node.mdx index 8f619416dde..3acc2aeed06 100644 --- a/product_docs/docs/eprs/6.2/08_xdb_cli/03_xdb_cli_commands/25_set_pdn_node.mdx +++ b/product_docs/docs/eprs/6.2/08_xdb_cli/03_xdb_cli_commands/25_set_pdn_node.mdx @@ -30,7 +30,7 @@ Examples The following example sets the primary node with publication database `ID 9` as the primary definition node. ```text -$ java -jar edb-repcli.jar -setasMDN 9 -repsvrfile ~/pubsvrfile.prop +$ java -jar edb-repcli.jar -setasmdn 9 -repsvrfile ~/pubsvrfile.prop Updating the database node to be promoted as the new MDN node. The database has been successfully promoted as the new MDN node. ``` diff --git a/product_docs/docs/eprs/7/02_overview/02_replication_concepts_and_definitions/04_mmr_replication.mdx b/product_docs/docs/eprs/7/02_overview/02_replication_concepts_and_definitions/04_mmr_replication.mdx index 546197bd585..43de28eb555 100644 --- a/product_docs/docs/eprs/7/02_overview/02_replication_concepts_and_definitions/04_mmr_replication.mdx +++ b/product_docs/docs/eprs/7/02_overview/02_replication_concepts_and_definitions/04_mmr_replication.mdx @@ -10,7 +10,7 @@ The following definitions are used when referring to multi-master replication sy A primary node is a database participating in a multi-master replication system. -The database (primary node) in which the publication is initially defined is specially designated as the *primary definition node (PDN)*. There can be only one primary definition node at a time. However, you can change which primary node is the primary definition node. When it's important to make a distinction between the primary definition node and all other primary nodes, we refer to the latter as `non-PDN nodes`. +The database (primary node) in which the publication is initially defined is specially designated as the *primary definition node (MDN)*. There can be only one primary definition node at a time. However, you can change which primary node is the primary definition node. When it's important to make a distinction between the primary definition node and all other primary nodes, we refer to the latter as `non-MDN nodes`. The primary definition node has the following significance: From 5b94875854ed57e69de5e48773dabdd1f7abeeb9 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Mon, 4 Apr 2022 08:43:38 -0400 Subject: [PATCH 10/11] updated 7 with pdn changes --- .../13_table_filters.mdx | 2 +- .../01_physical_components.mdx | 2 +- .../02_design_considerations.mdx | 2 +- .../06_mmr_operation/02_creating_publication_mmr.mdx | 2 +- .../7/06_mmr_operation/03_creating_primary_nodes.mdx | 2 +- .../eprs/7/06_mmr_operation/10_switching_pdn.mdx | 4 ++-- .../06_managing_publication/06_removing_pub.mdx | 2 +- .../07_removing_pub_database.mdx | 2 +- .../7/07_common_operations/09_offline_snapshot.mdx | 2 +- .../11_using_ssl_connections.mdx | 6 +++--- .../03_xdb_cli_commands/06_add_pub_database.mdx | 6 +++--- .../10_printing_pdn_node_db_id.mdx | 8 ++++---- .../20_adding_tablefilters_to_publication.mdx | 6 +++--- .../21_updating_tablefilters_to_publication.mdx | 2 +- .../22_removing_tablefilters_to_publication.mdx | 2 +- .../03_xdb_cli_commands/25_set_pdn_node.mdx | 8 ++++---- ...nable_filters_on_subscription_or_non_pdn_node.mdx | 12 ++++++------ ...sable_filters_on_subscription_or_non_pdn_node.mdx | 4 ++-- .../03_resolving_problems/01_error_messages.mdx | 6 +++--- .../04_troubleshooting_areas.mdx | 2 +- ..._grants_of_table_level_user_privileges_on_mmr.mdx | 10 +++++----- 21 files changed, 46 insertions(+), 46 deletions(-) diff --git a/product_docs/docs/eprs/7/02_overview/02_replication_concepts_and_definitions/13_table_filters.mdx b/product_docs/docs/eprs/7/02_overview/02_replication_concepts_and_definitions/13_table_filters.mdx index 98359934f4f..2885b2d6328 100644 --- a/product_docs/docs/eprs/7/02_overview/02_replication_concepts_and_definitions/13_table_filters.mdx +++ b/product_docs/docs/eprs/7/02_overview/02_replication_concepts_and_definitions/13_table_filters.mdx @@ -156,7 +156,7 @@ The `REPLICA IDENTITY FULL` setting is required on tables in the following datab - In a single-master replication system, you define table filters in the primary database. Thus, the publication tables in the primary database requiring filter definitions must be altered to a `REPLICA IDENTITY FULL` setting but only if the publication is not a snapshot-only publication. See [Snapshot-only publications](07_snapshot_only_publications/#snapshot_only_publications). - In a multi-master replication system, table filters are defined in the primary definition node. Thus, publication tables in the primary definition node requiring filter definitions must be altered to a `REPLICA IDENTITY FULL` setting. -- In a multi-master replication system, don't set non-PDN nodes tables `REPLICA IDENTITY` options to `FULL` unless transactions are expected to be targeted on those non-PDN nodes. In addition, the transactions will be filtered when they're replicated to the other primary nodes. +- In a multi-master replication system, don't set non-MDN nodes tables `REPLICA IDENTITY` options to `FULL` unless transactions are expected to be targeted on those non-MDN nodes. In addition, the transactions will be filtered when they're replicated to the other primary nodes. The `REPLICA IDENTITY FULL` setting on a source table ensures that certain types of transactions on the source table result in the proper updates to the target tables on which filters are enabled. diff --git a/product_docs/docs/eprs/7/02_overview/03_replication_server_components_and_architecture/01_physical_components.mdx b/product_docs/docs/eprs/7/02_overview/03_replication_server_components_and_architecture/01_physical_components.mdx index 0e77e972b63..810f038d699 100644 --- a/product_docs/docs/eprs/7/02_overview/03_replication_server_components_and_architecture/01_physical_components.mdx +++ b/product_docs/docs/eprs/7/02_overview/03_replication_server_components_and_architecture/01_physical_components.mdx @@ -41,7 +41,7 @@ Any number of primary nodes can participate in a multi-master replication system The publication server creates and manages the metadata for publications. When a publication is created, the publication server creates database objects in the control schema of the publication database to record metadata about the publication. -Whenever a primary node is added to a multi-master replication system, the publication server creates database objects in the control schema of the primary node for recording metadata. For non-PDN nodes, the publication server also calls Migration Toolkit to create the publication table definitions if you choose this option when creating the primary node. +Whenever a primary node is added to a multi-master replication system, the publication server creates database objects in the control schema of the primary node for recording metadata. For non-MDN nodes, the publication server also calls Migration Toolkit to create the publication table definitions if you choose this option when creating the primary node. !!! Note See [Control schema and control schema objects](#control_schema_and_objects) for information on the control schema. diff --git a/product_docs/docs/eprs/7/02_overview/04_design_replication_system/02_design_considerations.mdx b/product_docs/docs/eprs/7/02_overview/04_design_replication_system/02_design_considerations.mdx index ae0eafa276e..072f009f21a 100644 --- a/product_docs/docs/eprs/7/02_overview/04_design_replication_system/02_design_considerations.mdx +++ b/product_docs/docs/eprs/7/02_overview/04_design_replication_system/02_design_considerations.mdx @@ -50,7 +50,7 @@ CREATE TABLE dept_uk2 ( 1. Repeat the same process for the publications. 1. After all replication system logical components are 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. Don't drop the control schema objects manually, for example by using an SQL command line utility. Doing so can cause the Replication Server console and CLI to stop working. 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 Replication Server console or CLI drops the control schema objects from the physical database. - The order of removing a multi-master replication system is as follows: - 1. Remove the replication system logical components using the Replication Server console or CLI starting with the publication database definitions of the non-PDN nodes. + 1. Remove the replication system logical components using the Replication Server console or CLI starting with the publication database definitions of the non-MDN nodes. 1. Remove the publication from under the primary definition node. 1. Remove the publication database definition of the primary definition node. After all replication system logical components are removed (except for possibly the publication server) you can drop any of the physical database objects in Postgres. Don't drop the control schema objects manually, for example by using an SQL command line utility. Doing so can cause the Replication Server console and CLI to stop working. diff --git a/product_docs/docs/eprs/7/06_mmr_operation/02_creating_publication_mmr.mdx b/product_docs/docs/eprs/7/06_mmr_operation/02_creating_publication_mmr.mdx index 2b98b5f59fd..d0c524d84bc 100644 --- a/product_docs/docs/eprs/7/06_mmr_operation/02_creating_publication_mmr.mdx +++ b/product_docs/docs/eprs/7/06_mmr_operation/02_creating_publication_mmr.mdx @@ -51,7 +51,7 @@ You must enter database connection information such as the database server netwo 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. -The label **PDN** appears at the end of the node in the replication tree. In addition, the **PDN** field is set to **Yes** in the Property window to indicate this is the primary definition node. +The label **MDN** appears at the end of the node in the replication tree. In addition, the **MDN** field is set to **Yes** in the Property window to indicate this is the primary definition node. diff --git a/product_docs/docs/eprs/7/06_mmr_operation/03_creating_primary_nodes.mdx b/product_docs/docs/eprs/7/06_mmr_operation/03_creating_primary_nodes.mdx index 522dda29d2b..6106d550772 100644 --- a/product_docs/docs/eprs/7/06_mmr_operation/03_creating_primary_nodes.mdx +++ b/product_docs/docs/eprs/7/06_mmr_operation/03_creating_primary_nodes.mdx @@ -54,7 +54,7 @@ Select **Save**. 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. -Unlike the primary definition node, the label PDN doesn't 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. +Unlike the primary definition node, the label MDN doesn't appear at the end of the node in the replication tree. The **MDN** field is set to **No** in the Property window to indicate this is not the primary definition node. In addition, a Publication node appears under the newly added primary node. This Publication node represents the publication in the primary definition node, which is replicated to the primary node. diff --git a/product_docs/docs/eprs/7/06_mmr_operation/10_switching_pdn.mdx b/product_docs/docs/eprs/7/06_mmr_operation/10_switching_pdn.mdx index 43f69951cae..e173a9423a4 100644 --- a/product_docs/docs/eprs/7/06_mmr_operation/10_switching_pdn.mdx +++ b/product_docs/docs/eprs/7/06_mmr_operation/10_switching_pdn.mdx @@ -10,11 +10,11 @@ After you create the multi-master replication system, you can switch the role of 1. Select the Publication Database node corresponding to the primary node that you want to set as the primary definition node. -1. From the context menu, select **Set as PDN**. +1. From the context menu, select **Set as MDN**. 1. In the confirmation box, select **Yes**. The selected master node is now the master definition node. - The value **Yes** in the **PDN** field of the Property window indicates this database is the primary definition node. + The value **Yes** in the **MDN** field of the Property window indicates this database is the primary definition node. The new primary definition node moves to the top of the replication tree. diff --git a/product_docs/docs/eprs/7/07_common_operations/06_managing_publication/06_removing_pub.mdx b/product_docs/docs/eprs/7/07_common_operations/06_managing_publication/06_removing_pub.mdx index 5dc622a4b51..1af0a91391e 100644 --- a/product_docs/docs/eprs/7/07_common_operations/06_managing_publication/06_removing_pub.mdx +++ b/product_docs/docs/eprs/7/07_common_operations/06_managing_publication/06_removing_pub.mdx @@ -6,7 +6,7 @@ title: "Removing a publication" In a single-master replication system, you can remove a publication before removing its associated subscriptions. See [Removing a subscription](../../05_smr_operation/05_managing_subscription/05_removing_subscription/#removing_subscription) for more information. -In a multi-master replication system, remove the publication from under the Publication Database node representing the primary definition node. Before you can remove a publication, you must remove all non-PDN nodes. See [Removing a publication database](07_removing_pub_database/#removing_pub_database) for information about removing a publication database definition of a primary node. +In a multi-master replication system, remove the publication from under the Publication Database node representing the primary definition node. Before you can remove a publication, you must remove all non-MDN nodes. See [Removing a publication database](07_removing_pub_database/#removing_pub_database) for information about removing a publication database definition of a primary node. Removing a publication doesn't delete the publication tables in the publication database. It removes the identity and association of these tables to Replication Server so the tables remain in the database until the DBA deletes them with the `DROP TABLE SQL` statement. diff --git a/product_docs/docs/eprs/7/07_common_operations/06_managing_publication/07_removing_pub_database.mdx b/product_docs/docs/eprs/7/07_common_operations/06_managing_publication/07_removing_pub_database.mdx index 6e7e25c52ca..bc89521114b 100644 --- a/product_docs/docs/eprs/7/07_common_operations/06_managing_publication/07_removing_pub_database.mdx +++ b/product_docs/docs/eprs/7/07_common_operations/06_managing_publication/07_removing_pub_database.mdx @@ -20,7 +20,7 @@ Removing the Publication Database node representing the primary definition node - If the multi-master replication system is the only Replication Server replication system (that is, there are no single-master replication systems), then switch the controller database to the primary definition node if the designated controller database isn't currently the same database as the primary definition node. - If there are one or more single-master replication systems in addition to the multi-master replication system, switch the controller database to a Postgres publication database of a single-master replication system. If none of the single-master publication databases is of type Postgres, and there are more than one Oracle or SQL Server publication databases, then you must create a Postgres publication database for a single-master replication system just for the purpose of designating it as the controller database. -- You must remove all Publication Database nodes representing non-PDN nodes. Repeat the process for each such primary node. +- You must remove all Publication Database nodes representing non-MDN nodes. Repeat the process for each such primary node. - You must remove the publication under the Publication Database node representing the primary definition node. See [Removing a publication](06_removing_pub/#removing_pub) for details. - Remove the Publication Database node representing the primary definition node. diff --git a/product_docs/docs/eprs/7/07_common_operations/09_offline_snapshot.mdx b/product_docs/docs/eprs/7/07_common_operations/09_offline_snapshot.mdx index b8cd4128b47..b70c3e708c7 100644 --- a/product_docs/docs/eprs/7/07_common_operations/09_offline_snapshot.mdx +++ b/product_docs/docs/eprs/7/07_common_operations/09_offline_snapshot.mdx @@ -4,7 +4,7 @@ title: "Loading tables from an external data source (offline snapshot)" -You might want to initially load your target tables (subscription tables of a single-master replication system, or non-PDN nodes of a multi-master replication system) using a method other than the snapshot replication functionality of Replication Server. This method is referred to as using an offline snapshot. +You might want to initially load your target tables (subscription tables of a single-master replication system, or non-MDN nodes of a multi-master replication system) using a method other than the snapshot replication functionality of Replication Server. This method is referred to as using an offline snapshot. For example, you might at first load the tables by running the Migration Toolkit from the command line or by using a backup from an external data source. When you load the target tables using an offline snapshot, you must take into account special preparations for the following deviations from the default target table creation and loading process: diff --git a/product_docs/docs/eprs/7/07_common_operations/11_using_ssl_connections.mdx b/product_docs/docs/eprs/7/07_common_operations/11_using_ssl_connections.mdx index 8d61c8bde51..5bce4c9c58c 100644 --- a/product_docs/docs/eprs/7/07_common_operations/11_using_ssl_connections.mdx +++ b/product_docs/docs/eprs/7/07_common_operations/11_using_ssl_connections.mdx @@ -16,8 +16,8 @@ For a single-master replication system, you can make the following connections t For a multi-master replication system, you can make the following connections to Postgres databases enabled with SSL: -- Publication server connection to the primary definition node and the non-PDN nodes -- Migration Toolkit connection to the primary definition node and the non-PDN nodes +- Publication server connection to the primary definition node and the non-MDN nodes +- Migration Toolkit connection to the primary definition node and the non-MDN nodes !!! Note SSL connections aren't used from the Replication Server console or CLI. The Replication Server user interfaces communicate with the publication server and subscription server, which in turn connect to the publication/subscription databases or primary nodes. @@ -375,7 +375,7 @@ The SSL URL option informs Java to use SSL when the publication server or subscr The configuration steps where these options are specified are as follows: - For using SSL connections in a single-master replication system, specify the URL options as shown in [Adding a publication database](../05_smr_operation/02_creating_publication/02_adding_pub_database/#adding_pub_database) for the publication database and in [Adding a subscription database](../05_smr_operation/03_creating_subscription/02_adding_subscription_database/#adding_subscription_database) for the subscription databases. -- For using SSL connections in a multi-master replication system, you must specify the URL options as shown in [Adding the primary definition node](../06_mmr_operation/02_creating_publication_mmr/#adding_pdn) for the primary definition node and in [Creating more primary nodes](../06_mmr_operation/03_creating_primary_nodes/#creating_primary_nodes) for the non-PDN nodes. +- For using SSL connections in a multi-master replication system, you must specify the URL options as shown in [Adding the primary definition node](../06_mmr_operation/02_creating_publication_mmr/#adding_pdn) for the primary definition node and in [Creating more primary nodes](../06_mmr_operation/03_creating_primary_nodes/#creating_primary_nodes) for the non-MDN nodes. Earlier we created self-signed certificates for the database server by specifying the value of the CN field as the database user name (for example, postgres or enterprisedb, and so on). In this case, we use the “verify-ca” value for sslmode parameter to indicate the server certificate is validated against the CA. We do this because the hostname given in the command Add Database or Update Database could not be verified against CN value present certificate, which is the database user name. diff --git a/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/06_add_pub_database.mdx b/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/06_add_pub_database.mdx index 8bae1e26f3b..b78b01b7c85 100644 --- a/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/06_add_pub_database.mdx +++ b/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/06_add_pub_database.mdx @@ -86,7 +86,7 @@ Extended usage of JDBC URL parameters such as for support of SSL connectivity. S `filterid_n` -**For MMR only:** Applies to non-PDN nodes. Comma-separated list of filter IDs identifying the filter rules from the set of available table filters to enable on the corresponding tables in the new primary node. Use the `printpubfilterslist` command to get the filter IDs for the available filter rules in the publication (see [Printing a list of filters in a publication](17_print_publications_filters_list/#print_publications_filters_list)). Do not use any white space between the comma and filter IDs. +**For MMR only:** Applies to non-MDN nodes. Comma-separated list of filter IDs identifying the filter rules from the set of available table filters to enable on the corresponding tables in the new primary node. Use the `printpubfilterslist` command to get the filter IDs for the available filter rules in the publication (see [Printing a list of filters in a publication](17_print_publications_filters_list/#print_publications_filters_list)). Do not use any white space between the comma and filter IDs. `-repgrouptype` @@ -94,13 +94,13 @@ Specify `s` if this command applies to a single-master replication system. Speci `-replicatepubschema` -**For MMR only:** Applies to non-PDN nodes. Set this option to `true` if you want the publication table definitions replicated from the primary definition node when creating a new primary node. Set this option to `false` if you already created the table definitions in the new primary node. The default is `true`. Don't specify this parameter when creating the primary definition node. +**For MMR only:** Applies to non-MDN nodes. Set this option to `true` if you want the publication table definitions replicated from the primary definition node when creating a new primary node. Set this option to `false` if you already created the table definitions in the new primary node. The default is `true`. Don't specify this parameter when creating the primary definition node. Unless you intend to use the offline snapshot technique (see [Loading tables from an external data source (offline snapshot)](../../07_common_operations/09_offline_snapshot/#offline_snapshot), we suggest that you specify this option. You must perform an initial snapshot replication from the primary definition node to every other primary node before performing synchronization replications on demand (see [Performing a synchronization](42_perform_synchronization/#perform_synchronization)) or by a schedule (see [Configuring a multi-master schedule](44_configure_mmr_schedule/#configure_mmr_schedule)). If a newly added primary node didn't undergo an initial snapshot, any later synchronization replication might not apply the transactions to that primary node. You can also take the initial snapshot by performing an on-demand snapshot (see [Take a multi-master snapshot](41_taking_mmr_snapshot/#taking_mmr_snapshot)). `-initialsnapshot` -**For MMR only:** Applies to non-PDN nodes. Specify this option if you want an initial snapshot replication performed when creating the primary node. Omit this option if you don't want an initial snapshot replication performed when creating the primary node. +**For MMR only:** Applies to non-MDN nodes. Specify this option if you want an initial snapshot replication performed when creating the primary node. Omit this option if you don't want an initial snapshot replication performed when creating the primary node. !!! Note Unless you intend to use the offline snapshot technique (see [Loading tables from an external data source (offline snapshot)](../../07_common_operations/09_offline_snapshot/#offline_snapshot)), we suggest that you specify this option. You must perform an initial snapshot replication from the primary definition node to every other primary node before performing synchronization replications on demand (see [Performing a synchronization](42_perform_synchronization/#perform_synchronization)) or by a schedule (see [Configuring a multi-master schedule](44_configure_mmr_schedule/#configure_mmr_schedule)). If a newly added primary node didn't undergo an initial snapshot, any later synchronization replication might not apply the transactions to that primary node. You can also take the initial snapshot by performing an on-demand snapshot (see [Take a multi-master snapshot](41_taking_mmr_snapshot/#taking_mmr_snapshot)) or by a schedule (see [Configuring a multi-master schedule](44_configure_mmr_schedule/#configure_mmr_schedule)). diff --git a/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/10_printing_pdn_node_db_id.mdx b/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/10_printing_pdn_node_db_id.mdx index c42696cd783..727421b12dd 100644 --- a/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/10_printing_pdn_node_db_id.mdx +++ b/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/10_printing_pdn_node_db_id.mdx @@ -4,11 +4,11 @@ title: "Printing the primary definition node database ID (printpdndbid)" -**For MMR only:** The `printpdndbid` command prints the publication database ID of the primary definition node. +**For MMR only:** The `printmdndbid` command prints the publication database ID of the primary definition node. ##Synopsis -`-printpdndbid -repsvrfile pubsvrfile` +`-printmdnbid -repsvrfile pubsvrfile` ## Parameters @@ -21,7 +21,7 @@ The file containing the publication server login information. This example displays the publication database ID of the primary definition node. ```text -$ java -jar edb-repcli.jar -printPDNdbid -repsvrfile ~/pubsvrfile.prop -Printing PDN Publication database id... +$ java -jar edb-repcli.jar -printmdndbid -repsvrfile ~/pubsvrfile.prop +Printing MDN Publication database id... 3 ``` diff --git a/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/20_adding_tablefilters_to_publication.mdx b/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/20_adding_tablefilters_to_publication.mdx index 286c1452147..c07b20baec3 100644 --- a/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/20_adding_tablefilters_to_publication.mdx +++ b/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/20_adding_tablefilters_to_publication.mdx @@ -4,11 +4,11 @@ title: "Adding table filters to a publication (addfilter)" -The `addfilter` command adds the definition of table filter rules to the specified publication. This addition makes the filter rules available to enable later on target subscriptions or non-PDN nodes. +The `addfilter` command adds the definition of table filter rules to the specified publication. This addition makes the filter rules available to enable later on target subscriptions or non-MDN nodes. -Enabling a filter rule on a specified, target subscription or non-PDN node results in the filtering of data from the source table to the target table during replication. +Enabling a filter rule on a specified, target subscription or non-MDN node results in the filtering of data from the source table to the target table during replication. -If the filter rule isn't enabled on a target subscription or non-PDN node, then it has no impact on that subscription or non-PDN node during replication. See [Enabling filters on a subscription or non-PDN node](38_enable_filters_on_subscription_or_non_pdn_node/#enable_filters_on_subscription_or_non_pdn_node) for information on enabling table filter rules. +If the filter rule isn't enabled on a target subscription or non-MDN node, then it has no impact on that subscription or non-MDN node during replication. See [Enabling filters on a subscription or non-MDN node](38_enable_filters_on_subscription_or_non_pdn_node/#enable_filters_on_subscription_or_non_pdn_node) for information on enabling table filter rules. ## Synopsis diff --git a/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/21_updating_tablefilters_to_publication.mdx b/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/21_updating_tablefilters_to_publication.mdx index 94b5507dd03..e84993ab5c7 100644 --- a/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/21_updating_tablefilters_to_publication.mdx +++ b/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/21_updating_tablefilters_to_publication.mdx @@ -16,7 +16,7 @@ The `updatefilter` command changes the filter clauses of the specified tables or [ "filterid_2:filterclause_2" ] ... ``` -The next replication to any target subscriptions or non-PDN nodes on which these filter rules were enabled reflects the changes to the filter clauses. +The next replication to any target subscriptions or non-MDN nodes on which these filter rules were enabled reflects the changes to the filter clauses. See [Table filters](../../02_overview/02_replication_concepts_and_definitions/13_table_filters/#table_filters) for more information. diff --git a/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/22_removing_tablefilters_to_publication.mdx b/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/22_removing_tablefilters_to_publication.mdx index 3eeb77e5924..591c8656f95 100644 --- a/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/22_removing_tablefilters_to_publication.mdx +++ b/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/22_removing_tablefilters_to_publication.mdx @@ -14,7 +14,7 @@ The `removefilter` command removes the table filter from the specified publicati -filterid filterid ``` -The removed filter rule no longer applies to any target subscriptions or non-PDN nodes on which the filter rule was enabled. +The removed filter rule no longer applies to any target subscriptions or non-MDN nodes on which the filter rule was enabled. See [Table filters](../../02_overview/02_replication_concepts_and_definitions/13_table_filters/#table_filters) for more information. diff --git a/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/25_set_pdn_node.mdx b/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/25_set_pdn_node.mdx index 19a07a46737..f7f4b0b1828 100644 --- a/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/25_set_pdn_node.mdx +++ b/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/25_set_pdn_node.mdx @@ -9,7 +9,7 @@ title: "Setting the master definition node (setasmdn)" ## Synopsis ```text --setaspdn pubdbid +-setasmdn pubdbid –repsvrfile pubsvrfile ``` @@ -30,7 +30,7 @@ The file containing the publication server login information. This example sets the primary node with publication database `ID 9` as the primary definition node. ```text -$ java -jar edb-repcli.jar -setasPDN 9 -repsvrfile ~/pubsvrfile.prop -Updating the database node to be promoted as the new PDN node. -The database has been successfully promoted as the new PDN node. +$ java -jar edb-repcli.jar -setasmdn 9 -repsvrfile ~/pubsvrfile.prop +Updating the database node to be promoted as the new MDN node. +The database has been successfully promoted as the new MDN node. ``` diff --git a/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/38_enable_filters_on_subscription_or_non_pdn_node.mdx b/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/38_enable_filters_on_subscription_or_non_pdn_node.mdx index 41e5566aeb4..785890d07ea 100644 --- a/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/38_enable_filters_on_subscription_or_non_pdn_node.mdx +++ b/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/38_enable_filters_on_subscription_or_non_pdn_node.mdx @@ -1,12 +1,12 @@ --- -title: "Enabling filters on a subscription or non-PDN node (enablefilter)" +title: "Enabling filters on a subscription or non-MDN node (enablefilter)" --- The `enablefilter` command enables one or more filter rules on a single-master replication system subscription or on a multi-master replication system primary node other than the primary definition node. -Use the `enablefilter` command when you want to apply a filter rule to a subscription or a non-PDN node, but the filter rule didn't yet exist or it wasn't included with the subscription or the non-PDN node when these components were created. +Use the `enablefilter` command when you want to apply a filter rule to a subscription or a non-MDN node, but the filter rule didn't yet exist or it wasn't included with the subscription or the non-MDN node when these components were created. ## Synopsis @@ -17,7 +17,7 @@ Use the `enablefilter` command when you want to apply a filter rule to a subscri -filterids filterid_1 [ filterid_2 ] ... ``` -Enabling a filter rule applies it to the specified, target subscription or non-PDN node and thus filters the data during replication from the source table to the target table. +Enabling a filter rule applies it to the specified, target subscription or non-MDN node and thus filters the data during replication from the source table to the target table. See [Table filters](../../02_overview/02_replication_concepts_and_definitions/13_table_filters/#table_filters) for more information. @@ -39,7 +39,7 @@ Enable the filter rule as follows: **For MMR:** Use the `enablefilter` command or the Replication Server console (see [Enabling and disabling table filters on a primary node](../../06_mmr_operation/09_enable_disable_table_filters/#enable_disable_table_filters). -After you enable a filter rule, it filters the data during replication from the source table to the target table. You can disable a filter rule so that it no longer filters the data during replication to the target table (see [Disabling filters on a subscription or non-PDN node](39_disable_filters_on_subscription_or_non_pdn_node/#disable_filters_on_subscription_or_non_pdn_node)). +After you enable a filter rule, it filters the data during replication from the source table to the target table. You can disable a filter rule so that it no longer filters the data during replication to the target table (see [Disabling filters on a subscription or non-MDN node](39_disable_filters_on_subscription_or_non_pdn_node/#disable_filters_on_subscription_or_non_pdn_node)). ## Parameters @@ -53,11 +53,11 @@ The file containing the publication server login information. `dbid` -**For MMR only:** The publication database ID of the non-PDN node containing the tables on which to enable the filter rules. +**For MMR only:** The publication database ID of the non-MDN node containing the tables on which to enable the filter rules. `filterid_n` -One or more filter IDs separated by space characters. These IDs identify the filter rules from the set of available table filters. You can enable these filters on the corresponding tables in the SMR subscription specified by `subname` or in the MMR non-PDN node specified by `dbid`. Use the `printpubfilterslist` command to obtain the filter IDs for the available filter rules in the publication (see [Printing a list of filters in a publication](17_print_publications_filters_list/#print_publications_filters_list)). +One or more filter IDs separated by space characters. These IDs identify the filter rules from the set of available table filters. You can enable these filters on the corresponding tables in the SMR subscription specified by `subname` or in the MMR non-MDN node specified by `dbid`. Use the `printpubfilterslist` command to obtain the filter IDs for the available filter rules in the publication (see [Printing a list of filters in a publication](17_print_publications_filters_list/#print_publications_filters_list)). ## Examples diff --git a/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/39_disable_filters_on_subscription_or_non_pdn_node.mdx b/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/39_disable_filters_on_subscription_or_non_pdn_node.mdx index 83646aa7690..ea9d7518456 100644 --- a/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/39_disable_filters_on_subscription_or_non_pdn_node.mdx +++ b/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/39_disable_filters_on_subscription_or_non_pdn_node.mdx @@ -25,7 +25,7 @@ Disable the filter rule as follows: **For MMR:** Use the `disablefilter` command or the Replication Server console (see [Enabling and disabling table filters on a primary node](../../06_mmr_operation/09_enable_disable_table_filters/#enable_disable_table_filters)). -Disabling a filter rule doesn't remove its definition from the publication. The filter rule still exists and you can still enable it on target subscriptions or non-PDN nodes. +Disabling a filter rule doesn't remove its definition from the publication. The filter rule still exists and you can still enable it on target subscriptions or non-MDN nodes. To remove a filter rule so that it no longer exists, use the `removefilter` command (see [Removing a table filter from a publication](22_removing_tablefilters_to_publication/#removing_tablefilters_to_publication)) or the Replication Server console (see [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)). @@ -41,7 +41,7 @@ The file containing the publication server login information. `dbid` -**For MMR only:** The publication database ID of the non-PDN node containing the tables on which to disable the filter rules. +**For MMR only:** The publication database ID of the non-MDN node containing the tables on which to disable the filter rules. `filterid_n` diff --git a/product_docs/docs/eprs/7/10_appendix/03_resolving_problems/01_error_messages.mdx b/product_docs/docs/eprs/7/10_appendix/03_resolving_problems/01_error_messages.mdx index 7182b1a18d1..d0dfb8587e6 100644 --- a/product_docs/docs/eprs/7/10_appendix/03_resolving_problems/01_error_messages.mdx +++ b/product_docs/docs/eprs/7/10_appendix/03_resolving_problems/01_error_messages.mdx @@ -124,7 +124,7 @@ Occurs when attempting to add a subscription database. Verify that the Replicati **Problem** -`The database type for the selected database is different than that of the PDN database. Each database should be of the same type in a MMR cluster.` +`The database type for the selected database is different than that of the MDN database. Each database should be of the same type in a MMR cluster.` **Resolution** @@ -212,7 +212,7 @@ Occurs when creating an Oracle publication or subscription database definition. **Problem** -`No Publication found on PDN node, additional Primary node cannot join MMR cluster.` +`No Publication found on MDN node, additional Primary node cannot join MMR cluster.` **Resolution** @@ -228,7 +228,7 @@ Synchronization replication failed due to the unavailability of a target databas **Problem** -`One or more primary database node(s) are defined against this publication. Removing the publication will invalidate the PDN.` +`One or more primary database node(s) are defined against this publication. Removing the publication will invalidate the MDN.` **Resolution** diff --git a/product_docs/docs/eprs/7/10_appendix/03_resolving_problems/04_troubleshooting_areas.mdx b/product_docs/docs/eprs/7/10_appendix/03_resolving_problems/04_troubleshooting_areas.mdx index e774c81c609..fe9899412a1 100644 --- a/product_docs/docs/eprs/7/10_appendix/03_resolving_problems/04_troubleshooting_areas.mdx +++ b/product_docs/docs/eprs/7/10_appendix/03_resolving_problems/04_troubleshooting_areas.mdx @@ -58,7 +58,7 @@ The same control schema deletion procedure must be performed in all publication From the viewpoint of the Replication Server console replication tree, a publication server that connects to the controller database has subordinate to it the publication databases sharing the same control schema information. -In the following example, the SMR publication database edb as well as the three MMR primary node databases `PDNnode`, `MMRnode_a`, and `MMRnode_b` are all managed by the same publication server, which connects to the controller database designated in the Replication Server configuration file. Thus, all publication databases `edb`, `PDNnode`, `MMRnode_a`, and `MMRnode_b` contain what should be the same control schema information. +In the following example, the SMR publication database edb as well as the three MMR primary node databases `mdnnode`, `MMRnode_a`, and `MMRnode_b` are all managed by the same publication server, which connects to the controller database designated in the Replication Server configuration file. Thus, all publication databases `edb`, `mdnnode`, `MMRnode_a`, and `MMRnode_b` contain what should be the same control schema information. 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. diff --git a/product_docs/docs/eprs/7/10_appendix/04_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/13_skipping_grants_of_table_level_user_privileges_on_mmr.mdx b/product_docs/docs/eprs/7/10_appendix/04_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/13_skipping_grants_of_table_level_user_privileges_on_mmr.mdx index f04765d8c52..51a66137603 100644 --- a/product_docs/docs/eprs/7/10_appendix/04_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/13_skipping_grants_of_table_level_user_privileges_on_mmr.mdx +++ b/product_docs/docs/eprs/7/10_appendix/04_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/13_skipping_grants_of_table_level_user_privileges_on_mmr.mdx @@ -7,15 +7,15 @@ title: "Skipping grants of table-level user privileges on MMR target tables" !!! Note This option applies only to the publication server. -When creating non-PDN nodes in a multi-master replication system, the publication server creates the publication tables and their corresponding shadow tables in the non-PDN node database. +When creating non-MDN nodes in a multi-master replication system, the publication server creates the publication tables and their corresponding shadow tables in the non-MDN node database. -When `skipTablePrivileges` is set to `false`, which is the default value, the database user privileges on the publication tables in the primary definition node are granted to the same database users on the publication tables in the newly created non-PDN node. +When `skipTablePrivileges` is set to `false`, which is the default value, the database user privileges on the publication tables in the primary definition node are granted to the same database users on the publication tables in the newly created non-MDN node. -The required privileges are also granted to these database users on the corresponding shadow tables in the non-PDN node so these database users can perform updates on the publication tables. The changes are recorded in the corresponding shadow tables. This enables proper synchronization replication of any such changes. +The required privileges are also granted to these database users on the corresponding shadow tables in the non-MDN node so these database users can perform updates on the publication tables. The changes are recorded in the corresponding shadow tables. This enables proper synchronization replication of any such changes. -This granting of privileges occurs only for database users with privileges on the primary definition node publication tables at the time the non-PDN node is defined using the Replication Server console or CLI. If you don't want the publication server to grant these database user privileges to the non-PDN publication tables and shadow tables when defining the non-PDN node, set `skipTablePrivileges` to `true`. In this case, you must explicitly grant the privileges on the publication tables and corresponding shadow tables in the non-PDN node for any database user that you want to provide update access to on these tables. See Step 2 of [Postgres publication database](../../../05_smr_operation/01_prerequisites/04_preparing_pub_database/#postgres_pub_db) for information about the required privileges. +This granting of privileges occurs only for database users with privileges on the primary definition node publication tables at the time the non-MDN node is defined using the Replication Server console or CLI. If you don't want the publication server to grant these database user privileges to the non-MDN publication tables and shadow tables when defining the non-MDN node, set `skipTablePrivileges` to `true`. In this case, you must explicitly grant the privileges on the publication tables and corresponding shadow tables in the non-MDN node for any database user that you want to provide update access to on these tables. See Step 2 of [Postgres publication database](../../../05_smr_operation/01_prerequisites/04_preparing_pub_database/#postgres_pub_db) for information about the required privileges. -This usage is typically for the case when database users who access the non-PDN node publication tables are different from the database users who access the primary definition node publication tables. +This usage is typically for the case when database users who access the non-MDN node publication tables are different from the database users who access the primary definition node publication tables. `skipTablePrivileges={true | false}` From dfdcd37f44f88111de4f86f0510780329b4dc2b8 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Mon, 4 Apr 2022 08:54:08 -0400 Subject: [PATCH 11/11] changed release date to April 5. Will update if date changes --- product_docs/docs/eprs/6.2/eprs_rel_notes/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/eprs/6.2/eprs_rel_notes/index.mdx b/product_docs/docs/eprs/6.2/eprs_rel_notes/index.mdx index 52292165aa3..11c3ba8d5c5 100644 --- a/product_docs/docs/eprs/6.2/eprs_rel_notes/index.mdx +++ b/product_docs/docs/eprs/6.2/eprs_rel_notes/index.mdx @@ -8,7 +8,7 @@ The EDB Postgres Replication Server documentation describes the latest version o | Version | Release Date | | ------- | ------------ | -| [6.2.18](11_eprs_rel_notes_6.2.18) | 2022 Apr 01 | +| [6.2.18](11_eprs_rel_notes_6.2.18) | 2022 Apr 05 | | [6.2.17](12_eprs_rel_notes_6.2.17) | 2022 Mar 03 | | [6.2.16](13_eprs_rel_notes_6.2.16) | 2021 Dec 09 | | [6.2.15](14_eprs_rel_notes_6.2.15) | 2021 Aug 30 |