Merge pull request #1484 from EnterpriseDB/release/2021-06-16

Release: 2021-06-16
Former-commit-id: bd73c32

product_docs/docs/epas/12/epas_compat_ora_dev_guide/01_introduction/02_edb_redwood_raw_names.mdx

@@ -8,7 +8,7 @@ legacyRedirectsGenerated:
 
 <div id="edb_redwood_raw_names" class="registered_link"></div>
 
-When `edb_redwood_raw_names` is set to its default value of `FALSE`, database object names such as table names, column names, trigger names, program names, user names, etc. appear in uppercase letters when viewed from Oracle catalogs (for a complete list of supported catalog views, see the *Database Compatibility for Oracle Catalog Views Guide*). In addition, quotation marks enclose names that were created with enclosing quotation marks.
+When `edb_redwood_raw_names` is set to its default value of `FALSE`, database object names such as table names, column names, trigger names, program names, user names, etc. appear in uppercase letters when viewed from Oracle catalogs (for a complete list of supported catalog views, see the *Database Compatibility for Oracle Developers Catalog Views Guide*). In addition, quotation marks enclose names that were created with enclosing quotation marks.
 
 When `edb_redwood_raw_names` is set to `TRUE`, the database object names are displayed exactly as they are stored in the PostgreSQL system catalogs when viewed from the Oracle catalogs. Thus, names created without enclosing quotation marks appear in lowercase as expected in PostgreSQL. Names created with enclosing quotation marks appear exactly as they were created, but without the quotation marks.
 

product_docs/docs/epas/12/epas_compat_ora_dev_guide/02_sql_tutorial/09_the_sql_language.mdx

@@ -10,7 +10,7 @@ legacyRedirectsGenerated:
 
 Advanced Server supports SQL language that is compatible with Oracle syntax as well as syntax and commands for extended functionality (functionality that does not provide database compatibility for Oracle or support Oracle-styled applications).
 
-The *Database Compatibility for Oracle Developer's SQL Guide* provides detailed information about:
+The *Database Compatibility for Oracle Developers SQL Guide* provides detailed information about:
 
 -   Compatible SQL syntax and language elements
 -   Data types

product_docs/docs/epas/12/epas_compat_ora_dev_guide/07_open_client_library.mdx

@@ -14,7 +14,7 @@ The following diagram compares the Open Client Library and Oracle Call Interface
 
 ![Open Client Library](images/open_client_library.png)
 
-For detailed usage information about the Open Client Library and the supported functions, see the EDB Postgres Advanced Server OCL Connector Guide:
+For detailed usage information about the Open Client Library and the supported functions, see the *EDB Postgres Advanced Server OCL Connector Guide*:
 
 <https://www.enterprisedb.com/docs/ocl_connector/latest/>
 

product_docs/docs/epas/12/epas_compat_ora_dev_guide/08_oracle_catalog_views.mdx

@@ -8,6 +8,6 @@ legacyRedirectsGenerated:
 
 <div id="oracle_catalog_views" class="registered_link"></div>
 
-The Oracle Catalog Views provide information about database objects in a manner compatible with the Oracle data dictionary views. Information about the supported views is now available in the *Database Compatibility for Oracle Developer’s Catalog Views Guide*, available at:
+The Oracle Catalog Views provide information about database objects in a manner compatible with the Oracle data dictionary views. Information about the supported views is now available in the *Database Compatibility for Oracle Developers Catalog Views Guide*, available at:
 
 <https://www.enterprisedb.com/docs/epas/latest/epas_compat_cat_views/>

product_docs/docs/epas/12/epas_compat_ora_dev_guide/09_tools_and_utilities.mdx

@@ -15,6 +15,6 @@ Compatible tools and utility programs can allow a developer to work with Advance
 -   EDB\*Wrap
 -   The Dynamic Runtime Instrumentation Tools Architecture (DRITA)
 
-For detailed information about the functionality supported by Advanced Server, see the *Database Compatibility for Oracle Developer’s Tools and Utilities Guide*, available at:
+For detailed information about the functionality supported by Advanced Server, see the *Database Compatibility for Oracle Developers Tools and Utilities Guide*, available at:
 
 <https://www.enterprisedb.com/docs/epas/latest/epas_compat_tools_guide/>

product_docs/docs/epas/12/epas_compat_ora_dev_guide/11_system_catalog_tables.mdx

@@ -10,6 +10,6 @@ legacyRedirectsGenerated:
 
 The system catalog tables contain definitions of database objects that are available to Advanced Server; the layout of the system tables is subject to change. If you are writing an application that depends on information stored in the system tables, it would be prudent to use an existing catalog view, or create a catalog view to isolate the application from changes to the system table.
 
-For detailed information about the system catalog tables, see the *Database Compatibility for Oracle Developer’s Catalog Views Guide*, available at:
+For detailed information about the system catalog tables, see the *Database Compatibility for Oracle Developers Catalog Views Guide*, available at:
 
 <https://www.enterprisedb.com/docs/epas/latest/epas_compat_cat_views/>

product_docs/docs/epas/12/epas_compat_ora_dev_guide/index.mdx

@@ -21,7 +21,7 @@ Database Compatibility for Oracle means that an application runs in an Oracle en
 
 For detailed information about the compatible SQL syntax, data types, and views, see the *Database Compatibility for Oracle Developers SQL Guide*.
 
-The compatibility offered by the procedures and functions that are part of the Built-in packages is documented in the *Database Compatibility for Oracle Developers Built-in Packages Guide.*
+The compatibility offered by the procedures and functions that are part of the Built-in packages is documented in the *Database Compatibility for Oracle Developers Built-in Package Guide.*
 
 For information about using the compatible tools and utilities (EDB\*Plus, EDB\*Loader, DRITA, and EDB\*Wrap) that are included with an Advanced Server installation, see the *Database Compatibility for Oracle Developers Tools and Utilities Guide.*
 

product_docs/docs/epas/12/epas_compat_reference/index.mdx

@@ -16,7 +16,7 @@ Database Compatibility for Oracle means that an application runs in an Oracle en
 This guide provides reference material about the compatible data types supported by Advanced Server. Reference information about:
 
 -   Compatible SQL Language syntax is provided in the *Database Compatibility for Oracle Developers SQL Guide*.
--   Compatible Catalog Views is provided in the *Database Compatibility for Oracle Developers Catalog View Guide*.
+-   Compatible Catalog Views is provided in the *Database Compatibility for Oracle Developers Catalog Views Guide*.
 
 Developing an application that is compatible with Oracle databases in the Advanced Server requires special attention to which features are used in the construction of the application. For example, developing a compatible application means selecting:
 

product_docs/docs/epas/12/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/06_overloading_subprograms.mdx

@@ -35,7 +35,7 @@ However, certain data types have alternative names referred to as *aliases*, whi
 
 For example, there are fixed length character data types that can be specified as `CHAR` or `CHARACTER`. There are variable length character data types that can be specified as `CHAR VARYING, CHARACTER VARYING, VARCHAR,` or `VARCHAR2`. For integers, there are `BINARY_INTEGER, PLS_INTEGER,` and `INTEGER` data types. For numbers, there are `NUMBER, NUMERIC, DEC,` and `DECIMAL` data types.
 
-For detailed information about the data types supported by Advanced Server, see the Database Compatibility for Oracle Developers Reference Guide, available from EnterpriseDB at:
+For detailed information about the data types supported by Advanced Server, see the *Database Compatibility for Oracle Developers Reference Guide*, available from EnterpriseDB at:
 
 [https://www.enterprisedb.com/docs](/epas/latest/epas_compat_reference/)
 

product_docs/docs/epas/12/epas_compat_spl/10_collections/02_nested_tables.mdx

@@ -26,7 +26,7 @@ TYPE <tbltype> IS TABLE OF { <datatype> | <rectype> | <objtype> };
 `tbltype` is an identifier assigned to the nested table type. `datatype` is a scalar data type such as `VARCHAR2` or `NUMBER`. `rectype` is a previously defined record type. `objtype` is a previously defined object type.
 
 !!! Note
-    You can use the `CREATE TYPE` command to define a nested table type that is available to all SPL programs in the database. See the Database Compatibility for Oracle Developers Reference Guide for more information about the `CREATE TYPE` command.
+    You can use the `CREATE TYPE` command to define a nested table type that is available to all SPL programs in the database. See the *Database Compatibility for Oracle Developers Reference Guide* for more information about the `CREATE TYPE` command.
 
 In order to make use of the table, a *variable* must be declared of that nested table type. The following is the syntax for declaring a table variable.
 

product_docs/docs/epas/12/epas_compat_sql/21_create_public_database_link.mdx

@@ -166,7 +166,7 @@ systemctl restart edb-as-12
 
 The particular script file that needs to be modified to include the `LD_LIBRARY_PATH` setting depends upon the Advanced Server version, the Linux system on which it was installed, and whether it was installed with the graphical installer or an RPM package.
 
-See the appropriate version of the `EDB Postgres Advanced Server Installation Guide` to determine the service script that affects the startup environment. The installation guides can be found at the following location:
+See the appropriate version of the *EDB Postgres Advanced Server Installation Guide* to determine the service script that affects the startup environment. The installation guides can be found at the following location:
 
 [https://www.enterprisedb.com/docs](/epas/latest/)
 

product_docs/docs/epas/12/epas_guide/01_introduction/index.mdx

@@ -10,11 +10,11 @@ The following features have been changed in EDB Postgres Advanced Server 11 to c
 
 -   Advanced Server introduces `COMPOUND TRIGGERS`, which are stored as a PL block that executes in response to a specified triggering event. For information, see the *Database Compatibility Stored Procedural Language Guide*.
 -   Advanced Server now supports new `DATA DICTIONARY VIEWS` that provide information that is compatible with the Oracle data dictionary views. For information, see the *Database Compatibility for Oracle Developers Catalog Views Guide*.
--   Advanced Server has added the `LISTAGG` function to support string aggregation that concatenates data from multiple rows into a single row in an ordered manner. For information, see the *Database Compatibility for Oracle Developer's Reference Guide*.
--   Advanced Server now supports `CAST(MULTISET)` function, allowing subquery output to be `CAST` to a nested table type. For information, see the *Database Compatibility for Oracle Developer's Reference Guide*.
--   Advanced Server has added the `MEDIAN` function to calculate a median value from the set of provided values. For information, see the *Database Compatibility for Oracle Developer's Reference Guide*.
--   Advanced Server has added the `SYS_GUID` function to generate and return a globally unique identifier in the form of `16-bytes` of `RAW` data. For information, see the *Database Compatibility for Oracle Developer's Reference Guide*.
--   Advanced Server now supports an Oracle-compatible `SELECT UNIQUE` clause in addition to an existing `SELECT DISTINCT` clause. For information, see the *Database Compatibility for Oracle Developers SQL Guide *.
+-   Advanced Server has added the `LISTAGG` function to support string aggregation that concatenates data from multiple rows into a single row in an ordered manner. For information, see the *Database Compatibility for Oracle Developers Reference Guide*.
+-   Advanced Server now supports `CAST(MULTISET)` function, allowing subquery output to be `CAST` to a nested table type. For information, see the *Database Compatibility for Oracle Developers Reference Guide*.
+-   Advanced Server has added the `MEDIAN` function to calculate a median value from the set of provided values. For information, see the *Database Compatibility for Oracle Developers Reference Guide*.
+-   Advanced Server has added the `SYS_GUID` function to generate and return a globally unique identifier in the form of `16-bytes` of `RAW` data. For information, see the *Database Compatibility for Oracle Developers Reference Guide*.
+-   Advanced Server now supports an Oracle-compatible `SELECT UNIQUE` clause in addition to an existing `SELECT DISTINCT` clause. For information, see the *Database Compatibility for Oracle Developers SQL Guide*.
 -   Advanced Server has re-implemented `default_with_rowids`, which is used to create a table that includes a `ROWID` column in the newly created table. For more information, see [default_with_rowids](../03_database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/11_compatibility_options/#default_with_rowids). 
 -   Advanced Server now supports logical decoding on the standby server, which allows creating a logical replication slot on a standby, independently of a primary server. For more information, see [Logical Decoding on Standby](../15_enhanced_sql_and_other_misc_features/#logical_decoding_on_standby).
 -   Advanced Server introduces `INTERVAL PARTITIONING`, which allows a database to automatically create partitions of a specified interval as new data is inserted into a table. For information, see the *Database Compatibility Table Partitioning Guide*.

product_docs/docs/epas/12/epas_guide/02_enhanced_compatibility_features.mdx

@@ -6,7 +6,7 @@ legacyRedirectsGenerated:
   - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/13/enhanced_compatibility_features.html"
 ---
 
-Advanced Server includes extended functionality that provides compatibility for syntax supported by Oracle applications. Detailed information about the compatibility features supported by Advanced Server is provided in the Database Compatibility for Oracle Developers Guide; the version-specific guides are available at:
+Advanced Server includes extended functionality that provides compatibility for syntax supported by Oracle applications. Detailed information about the compatibility features supported by Advanced Server is provided in the *Database Compatibility for Oracle Developers Guide*; the version-specific guides are available at:
 
 [https://www.enterprisedb.com/docs](/epas/latest/epas_compat_ora_dev_guide/)
 
@@ -130,7 +130,7 @@ For detailed information about the functions supported by the Open Client Librar
 
 ## Utilities
 
-For detailed information about the compatible syntax supported by the utilities listed below, see the *Database Compatibility for Oracle Developer's Tools and Utilities Guide*, available at:
+For detailed information about the compatible syntax supported by the utilities listed below, see the *Database Compatibility for Oracle Developers Tools and Utilities Guide*, available at:
 
 [https://www.enterprisedb.com/docs](/epas/latest/epas_compat_tools_guide/)
 
@@ -147,7 +147,7 @@ EDB\*Plus allows you to:
 -   Execute OS commands
 -   Record output
 
-For detailed information about EDB\*Plus, see the EDB\*Plus User's Guide available at:
+For detailed information about EDB\*Plus, see the *EDB\*Plus User's Guide* available at:
 
 [https://www.enterprisedb.com/docs/p/edbplus](/epas/latest/edb_plus/)
 
@@ -203,6 +203,6 @@ In a partitioned table, one logically large table is broken into smaller physica
 
 Table partitioning is worthwhile only when a table would otherwise be very large. The exact point at which a table will benefit from partitioning depends on the application; a good rule of thumb is that the size of the table should exceed the physical memory of the database server.
 
-For information about database compatibility features supported by Advanced Server see the *Database Compatibility for Table Partitioning Guide*, available at:
+For information about database compatibility features supported by Advanced Server see the *Database Compatibility Table Partitioning Guide*, available at:
 
 [https://www.enterprisedb.com/docs](/epas/latest/epas_compat_table_partitioning/)