diff --git a/product_docs/docs/eprs/7/01_introduction/03_certified_supported_versions.mdx b/product_docs/docs/eprs/7/01_introduction/03_certified_supported_versions.mdx index 6c6cefbddc8..4a239de10d4 100644 --- a/product_docs/docs/eprs/7/01_introduction/03_certified_supported_versions.mdx +++ b/product_docs/docs/eprs/7/01_introduction/03_certified_supported_versions.mdx @@ -13,7 +13,7 @@ You can use the following database product versions with Replication Server: - SQL Server 2014 version 12.0.5000.0 is explicitly certified. Newer minor versions in the 12.0 line are supported as well. !!!Note - All PostgreSQL and EDB Postgres Advanced Server versions available as BigAnimal single-node and primary/standby high availability cluster types are also supported for SMR configurations. Consult the BigAnimal (EDB’s managed database cloud service) [documentation](/biganimal/latest) for more information about BigAnimal’s [supported cluster types](/biganimal/latest/overview/02_high_availability/) and [database version policy](/biganimal/latest/overview/05_database_version_policy/) for the versions of PostgreSQL and EDB Postgres Advanced Server available in BigAnimal. + All PostgreSQL and EDB Postgres Advanced Server versions available as BigAnimal single-node and primary/standby high-availability cluster types are also supported for SMR configurations. See the BigAnimal (EDB’s managed database cloud service) [documentation](/biganimal/latest) for more information about BigAnimal’s [supported cluster types](/biganimal/latest/overview/02_high_availability/). See the [database version policy documentation](/biganimal/latest/overview/05_database_version_policy/) for the versions of PostgreSQL and EDB Postgres Advanced Server available in BigAnimal. As of Replication Server 7.1.0: diff --git a/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/52_reload_conf_file.mdx b/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/52_reload_conf_file.mdx index a95c78c6c34..a7a1088dba7 100644 --- a/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/52_reload_conf_file.mdx +++ b/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/52_reload_conf_file.mdx @@ -86,7 +86,7 @@ The table shows whether a configuration property can be reloaded. This example reloads the configuration file. !!! Note Note -When you execute the reloadconf command, if any configuration options have been changed from their default values, the output includes the configuration option and its new value. +When you execute the `reloadconf` command, if any configuration options were changed from their default values, the output includes the configuration option and its new value. ```shell java -jar edb-repcli.jar -reloadconf -repsvrfile subsvr.prop diff --git a/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/01_controlling_logging_level.mdx b/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/01_controlling_logging_level.mdx index 90931a7714a..3a3889145af 100644 --- a/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/01_controlling_logging_level.mdx +++ b/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/01_controlling_logging_level.mdx @@ -67,7 +67,7 @@ Set the `logging.default.locale` option to use either the current system locale The default value is `system`. !!!Note -This option is only applicable for publication and subscription logs and isn't supported for mtk.log. +This option is applicable only for publication and subscription logs and isn't supported for `mtk.log`. The RepCLI and RepConsole logs continue showing text in the default locale. !!! diff --git a/product_docs/docs/eprs/7/eprs_rel_notes/eprs_rel_notes_7.6.0.mdx b/product_docs/docs/eprs/7/eprs_rel_notes/eprs_rel_notes_7.6.0.mdx index b9db5af9199..184dded1bb5 100644 --- a/product_docs/docs/eprs/7/eprs_rel_notes/eprs_rel_notes_7.6.0.mdx +++ b/product_docs/docs/eprs/7/eprs_rel_notes/eprs_rel_notes_7.6.0.mdx @@ -9,14 +9,14 @@ New features, enhancements, bug fixes, and other changes in Replication Server 7 | Type | Description | | ------- |------------ | -| Enhancement | EDB Replication Server now supports logging Publication and Subscription server logs in the English language, overriding the default locale, using the `logging.default.locale` configuration parameter. [Support ticket #89877] | -| Enhancement | The snapshot operation now uses the table-level parallel loading capability, which reduces overhead on the source database by using range-based criterion for loading each individual table data chunk instead of a fetch-offset approach. This optimization is applicable when the table primary key/unique constraint is based on a non-composite numeric type attribute. [Support ticket # 93360] | +| Enhancement | EDB Replication Server now supports logging publication and subscription server logs in the English language, overriding the default locale, by way of the `logging.default.locale` configuration parameter. [Support ticket #89877] | +| Enhancement | The snapshot operation now uses the table-level parallel loading capability. This capability reduces overhead on the source database by using range-based criterion for loading each individual table data chunk instead of a fetch-offset approach. This optimization applies when the table primary key/unique constraint is based on a noncomposite numeric type attribute. [Support ticket # 93360] | | Enhancement | To help investigate data synchronization gaps, Replication Server’s logging now logs when rows are skipped due to filter criteria. [Support ticket #91296] | | Bug fix | Fixed an issue where metadata from the primary controller database wasn't replicated when a SQL Server or an Oracle publication database is added as a standby controller database. [Support ticket #82050 and #91884] | -| Bug fix | Fixed the issues related to foreign key violations in the standby controller database that prevented upgrading from version 6.2.x to 7.x. [Support ticket #93129, #92056 and #91588] | +| Bug fix | Fixed the issues related to foreign key violations in the standby controller database that prevented upgrading from version 6.2.x to 7.x. [Support ticket #93129, #92056, and #91588] | | Bug fix | Corrected a few code paths to release unused resources for timely garbage collection and optimized memory utilization. [Support ticket #91588] | -| Bug fix | Fixed a Data Validator Oracle edge case resulting in a `String index out of range` error for an Oracle to EDB Postgres Advanced Server validation. | -| Bug fix | Fixed an issue resulting in a synchronization failure for `nchar`, `nvarchar`, `xml`, and `sqlvariant` when using the mssql-jdbc-10.2.1.jre8.jar file for a SQL Server to EDB Postgres Advanced Server cluster setup. | -| Bug fix | Updated database type name references of “Postgres Plus Advanced Server” in the Replication Console and Replication CLI to “EDB Postgres Advanced Server”. | -| Bug fix | Fixed an issue that prevented logging of changed configuration parameters at Publication and Subscription server start or when the `reloadconf` command is executed. | -| Bug fix | Fixed a regression that led to an `Invalid custom column type mapping` error being observed for Publication tables with no column mapping. | +| Bug fix | Fixed a data validator Oracle edge case resulting in a `String index out of range` error for an Oracle-to-EDB Postgres Advanced Server validation. | +| Bug fix | Fixed an issue resulting in a synchronization failure for `nchar`, `nvarchar`, `xml`, and `sqlvariant` when using the `mssql-jdbc-10.2.1.jre8.jar` file for a SQL Server-to-EDB Postgres Advanced Server cluster setup. | +| Bug fix | Updated database type name references of “Postgres Plus Advanced Server” in the Replication Console and Replication CLI to “EDB Postgres Advanced Server.” | +| Bug fix | Fixed an issue that prevented logging of changed configuration parameters at publication and subscription server start or when the `reloadconf` command is executed. | +| Bug fix | Fixed a regression that led to an `Invalid custom column type mapping` error being observed for publication tables with no column mapping. |