From b9da4daf4da7d6a6cda9ffdf2e4ecdfb859058cb Mon Sep 17 00:00:00 2001 From: Betsy Gitelman <93718720+ebgitelman@users.noreply.github.com> Date: Mon, 10 Jul 2023 17:45:21 -0400 Subject: [PATCH] More fixes to link text In multiple releases Also renamed some topics Edited one topic --- .../09_tools_and_utilities.mdx | 3 +- .../11/epas_compat_ora_dev_guide/index.mdx | 6 +- .../09_tools_and_utilities.mdx | 3 +- .../12/epas_compat_ora_dev_guide/index.mdx | 6 +- .../09_tools_and_utilities.mdx | 3 +- .../13/epas_compat_ora_dev_guide/index.mdx | 4 +- .../03_built-in_packages/14_dbms_rls.mdx | 2 +- .../03_built-in_packages/index.mdx | 2 +- .../02_edb_redwood_raw_names.mdx | 2 +- .../02_sql_tutorial/09_the_sql_language.mdx | 2 +- .../08_oracle_catalog_views.mdx | 2 +- .../09_tools_and_utilities.mdx | 2 +- .../11_system_catalog_tables.mdx | 2 +- .../14/epas_compat_ora_dev_guide/index.mdx | 4 +- .../01_sql_syntax/01_lexical_structure.mdx | 2 +- .../epas/14/epas_compat_spl/14_packages.mdx | 2 +- .../14/epas_compat_sql/34_create_sequence.mdx | 2 +- .../14/epas_compat_sql/36_create_table.mdx | 2 +- .../epas/14/epas_compat_sql/71_select.mdx | 2 +- .../02_enhanced_compatibility_features.mdx | 8 +- .../12_customized_options.mdx | 2 +- .../reference_command_line_options.mdx | 80 +++++++++---------- .../01_command_line_options_reference.mdx | 2 +- 23 files changed, 68 insertions(+), 77 deletions(-) diff --git a/product_docs/docs/epas/11/epas_compat_ora_dev_guide/09_tools_and_utilities.mdx b/product_docs/docs/epas/11/epas_compat_ora_dev_guide/09_tools_and_utilities.mdx index f8468531325..77241f48ada 100644 --- a/product_docs/docs/epas/11/epas_compat_ora_dev_guide/09_tools_and_utilities.mdx +++ b/product_docs/docs/epas/11/epas_compat_ora_dev_guide/09_tools_and_utilities.mdx @@ -15,5 +15,4 @@ 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 EDB Postgres Advanced Server, see [Database Compatibility for Oracle -Developers Tools and Utilities](/epas/latest/epas_compat_tools_guide/). +For detailed information about the functionality supported by EDB Postgres Advanced Server, see [Tools, utilities, and components](/epas/latest/epas_compat_tools_guide/). diff --git a/product_docs/docs/epas/11/epas_compat_ora_dev_guide/index.mdx b/product_docs/docs/epas/11/epas_compat_ora_dev_guide/index.mdx index baa6151b27c..fec6bfb39a3 100644 --- a/product_docs/docs/epas/11/epas_compat_ora_dev_guide/index.mdx +++ b/product_docs/docs/epas/11/epas_compat_ora_dev_guide/index.mdx @@ -17,10 +17,10 @@ Database Compatibility for Oracle means that an application runs in an Oracle en - SQL statements that are compatible with Oracle SQL - System catalog views that are compatible with Oracle’s data dictionary -For detailed information about the compatible SQL syntax, data types, and views, see the [Database Compatibility for Oracle Developers SQL Guide](/epas/latest/epas_compat_sql/). +For detailed information about the compatible SQL syntax, data types, and views, see [SQL reference](/epas/latest/epas_compat_sql/). -The compatibility offered by the procedures and functions that are part of the Built-in packages is documented in [Database Compatibility for Oracle Developers Built-in Packages](/epas/latest/epas_compat_bip_guide/). +The compatibility offered by the procedures and functions that are part of the Built-in packages is documented in [Built-in packages](/epas/latest/epas_compat_bip_guide/). -For information about using the compatible tools and utilities (EDB\*Plus, EDB\*Loader, DRITA, and EDB\*Wrap) that are included with an EDB Postgres Advanced Server installation, see [Tools and utilities](/epas/latest/epas_compat_ora_dev_guide/09_tools_and_utilities/). +For information about using the compatible tools and utilities (EDB\*Plus, EDB\*Loader, DRITA, and EDB\*Wrap) that are included with an EDB Postgres Advanced Server installation, see [Tools, utilities, and components](/epas/latest/epas_compat_ora_dev_guide/09_tools_and_utilities/). For applications written using the Oracle Call Interface (OCI), EDB’s Open Client Library (OCL) provides interoperability with these applications. For detailed information about using the Open Client Library, see [EDB OCL Connector](/ocl_connector/latest/). diff --git a/product_docs/docs/epas/12/epas_compat_ora_dev_guide/09_tools_and_utilities.mdx b/product_docs/docs/epas/12/epas_compat_ora_dev_guide/09_tools_and_utilities.mdx index aafc09abda2..a4fc8aaf53a 100644 --- a/product_docs/docs/epas/12/epas_compat_ora_dev_guide/09_tools_and_utilities.mdx +++ b/product_docs/docs/epas/12/epas_compat_ora_dev_guide/09_tools_and_utilities.mdx @@ -15,5 +15,4 @@ 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 EDB Postgres Advanced Server, see [Database Compatibility for Oracle -Developers Tools and Utilities](/epas/latest/epas_compat_tools_guide/). +For detailed information about the functionality supported by EDB Postgres Advanced Server, see [Tools, utilities, and components](/epas/latest/epas_compat_tools_guide/). diff --git a/product_docs/docs/epas/12/epas_compat_ora_dev_guide/index.mdx b/product_docs/docs/epas/12/epas_compat_ora_dev_guide/index.mdx index afde71195b5..fefbc3d4d11 100644 --- a/product_docs/docs/epas/12/epas_compat_ora_dev_guide/index.mdx +++ b/product_docs/docs/epas/12/epas_compat_ora_dev_guide/index.mdx @@ -17,10 +17,10 @@ Database Compatibility for Oracle means that an application runs in an Oracle en - SQL statements that are compatible with Oracle SQL - System catalog views that are compatible with Oracle’s data dictionary -For detailed information about the compatible SQL syntax, data types, and views, see the [Database Compatibility for Oracle Developers SQL Guide](/epas/latest/epas_compat_sql/). +For detailed information about the compatible SQL syntax, data types, and views, see [SQL reference](/epas/latest/epas_compat_sql/). -The compatibility offered by the procedures and functions that are part of the Built-in packages is documented in [Database Compatibility for Oracle Developers Built-in Packages](/epas/latest/epas_compat_bip_guide/). +The compatibility offered by the procedures and functions that are part of the Built-in packages is documented in [Built-in packages](/epas/latest/epas_compat_bip_guide/). -For information about using the compatible tools and utilities (EDB\*Plus, EDB\*Loader, DRITA, and EDB\*Wrap) that are included with an EDB Postgres Advanced Server installation, see [Tools and utilities](/epas/latest/epas_compat_ora_dev_guide/09_tools_and_utilities/). +For information about using the compatible tools and utilities (EDB\*Plus, EDB\*Loader, DRITA, and EDB\*Wrap) that are included with an EDB Postgres Advanced Server installation, see [Tools, utilities, and components](/epas/latest/epas_compat_ora_dev_guide/09_tools_and_utilities/). For applications written using the Oracle Call Interface (OCI), EDB’s Open Client Library (OCL) provides interoperability with these applications. For detailed information about using the Open Client Library, see the *EDB Postgres Advanced Server OCL Connector Guide*. diff --git a/product_docs/docs/epas/13/epas_compat_ora_dev_guide/09_tools_and_utilities.mdx b/product_docs/docs/epas/13/epas_compat_ora_dev_guide/09_tools_and_utilities.mdx index ced473dd3be..811bd191eac 100644 --- a/product_docs/docs/epas/13/epas_compat_ora_dev_guide/09_tools_and_utilities.mdx +++ b/product_docs/docs/epas/13/epas_compat_ora_dev_guide/09_tools_and_utilities.mdx @@ -15,5 +15,4 @@ 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 EDB Postgres Advanced Server, see [Database Compatibility for Oracle -Developers Tools and Utilities](/epas/latest/epas_compat_tools_guide/). +For detailed information about the functionality supported by EDB Postgres Advanced Server, see [Tools, utilities, and components](/epas/latest/epas_compat_tools_guide/). diff --git a/product_docs/docs/epas/13/epas_compat_ora_dev_guide/index.mdx b/product_docs/docs/epas/13/epas_compat_ora_dev_guide/index.mdx index 23750ce8f15..d1979de07f4 100644 --- a/product_docs/docs/epas/13/epas_compat_ora_dev_guide/index.mdx +++ b/product_docs/docs/epas/13/epas_compat_ora_dev_guide/index.mdx @@ -19,9 +19,9 @@ Database Compatibility for Oracle means that an application runs in an Oracle en - SQL statements that are compatible with Oracle SQL - System catalog views that are compatible with Oracle’s data dictionary -For detailed information about the compatible SQL syntax, data types, and views, see the [Database Compatibility for Oracle Developers SQL Guide](/epas/latest/epas_compat_sql/). +For detailed information about the compatible SQL syntax, data types, and views, see the [SQL reference](/epas/latest/epas_compat_sql/). -The compatibility offered by the procedures and functions that are part of the Built-in packages is documented in [Database Compatibility for Oracle Developers Built-in Packages](/epas/latest/epas_compat_bip_guide/). +The compatibility offered by the procedures and functions that are part of the Built-in packages is documented in [Built-in packages](/epas/latest/epas_compat_bip_guide/). For information about using the compatible tools and utilities (EDB\*Plus, EDB\*Loader, DRITA, and EDB\*Wrap) that are included with an EDB Postgres Advanced Server installation, see [Tools and utilities](/epas/latest/epas_compat_ora_dev_guide/09_tools_and_utilities/). diff --git a/product_docs/docs/epas/14/epas_compat_bip_guide/03_built-in_packages/14_dbms_rls.mdx b/product_docs/docs/epas/14/epas_compat_bip_guide/03_built-in_packages/14_dbms_rls.mdx index 9be05914a1d..e9a28663066 100644 --- a/product_docs/docs/epas/14/epas_compat_bip_guide/03_built-in_packages/14_dbms_rls.mdx +++ b/product_docs/docs/epas/14/epas_compat_bip_guide/03_built-in_packages/14_dbms_rls.mdx @@ -51,7 +51,7 @@ The process for implementing Virtual Private Database is as follows: 1. Use the `ENABLE_POLICY` procedure to disable or enable an existing policy. 1. Use the `DROP_POLICY` procedure to remove an existing policy. The `DROP_POLICY` procedure doesn't drop the policy function or the associated database object. -Once you create policies, you can view them in the catalog views compatible with Oracle databases: `ALL_POLICIES`, `DBA_POLICIES`, or `USER_POLICIES`. The supported compatible views are listed in [Database Compatibility for Oracle Developers Catalog Views](/epas/latest/epas_compat_cat_views/). +Once you create policies, you can view them in the catalog views compatible with Oracle databases: `ALL_POLICIES`, `DBA_POLICIES`, or `USER_POLICIES`. The supported compatible views are listed in [Catalog views](/epas/latest/epas_compat_cat_views/). The `SYS_CONTEXT` function is often used with `DBMS_RLS`. The signature is: diff --git a/product_docs/docs/epas/14/epas_compat_bip_guide/03_built-in_packages/index.mdx b/product_docs/docs/epas/14/epas_compat_bip_guide/03_built-in_packages/index.mdx index 27bc0cb91c2..27fd12ec1e5 100644 --- a/product_docs/docs/epas/14/epas_compat_bip_guide/03_built-in_packages/index.mdx +++ b/product_docs/docs/epas/14/epas_compat_bip_guide/03_built-in_packages/index.mdx @@ -7,7 +7,7 @@ legacyRedirectsGenerated: Built-in packages are provided with EDB Postgres Advanced Server. For certain packages, non-superusers must be explicitly granted the `EXECUTE` privilege on the package before using any of the package’s functions or procedures. For most of the built-in packages, `EXECUTE` privilege is granted to `PUBLIC` by default. -For information about using the `GRANT` command to provide access to a package, see [Database Compatibility for Oracle Developers SQL](/epas/latest/epas_compat_sql/). +For information about using the `GRANT` command to provide access to a package, see [SQL reference](/epas/latest/epas_compat_sql/). All built-in packages are owned by the special `sys` user that must be specified when granting or revoking privileges on built-in packages: diff --git a/product_docs/docs/epas/14/epas_compat_ora_dev_guide/01_introduction/02_edb_redwood_raw_names.mdx b/product_docs/docs/epas/14/epas_compat_ora_dev_guide/01_introduction/02_edb_redwood_raw_names.mdx index 653cf341308..daecfb55d11 100644 --- a/product_docs/docs/epas/14/epas_compat_ora_dev_guide/01_introduction/02_edb_redwood_raw_names.mdx +++ b/product_docs/docs/epas/14/epas_compat_ora_dev_guide/01_introduction/02_edb_redwood_raw_names.mdx @@ -4,7 +4,7 @@ title: "edb_redwood_raw_names" -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, and user names appear in uppercase letters when viewed from Oracle catalogs. For a complete list of supported catalog views, see [Database Compatibility for Oracle Developers Catalog Views](/epas/latest/epas_compat_cat_views/). 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, and user names appear in uppercase letters when viewed from Oracle catalogs. For a complete list of supported catalog views, see [Catalog views](/epas/latest/epas_compat_cat_views/). 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 stored in the PostgreSQL system catalogs when viewed from the Oracle catalogs. Thus, names created without quotation marks appear in lowercase as expected in PostgreSQL. Names created in quotation marks appear exactly as they were created but without the quotation marks. diff --git a/product_docs/docs/epas/14/epas_compat_ora_dev_guide/02_sql_tutorial/09_the_sql_language.mdx b/product_docs/docs/epas/14/epas_compat_ora_dev_guide/02_sql_tutorial/09_the_sql_language.mdx index 53c4a7c3fbd..27653132522 100644 --- a/product_docs/docs/epas/14/epas_compat_ora_dev_guide/02_sql_tutorial/09_the_sql_language.mdx +++ b/product_docs/docs/epas/14/epas_compat_ora_dev_guide/02_sql_tutorial/09_the_sql_language.mdx @@ -9,7 +9,7 @@ legacyRedirectsGenerated: EDB Postgres Advanced Server supports SQL language that's compatible with Oracle syntax as well as syntax and commands for extended functionality. Extended functionality doesn't provide database compatibility for Oracle or support Oracle-styled applications. -[Database Compatibility for Oracle Developers SQL](/epas/latest/epas_compat_ora_dev_guide) provides detailed information about: +[SQL reference](/epas/latest/reference/sql_reference/) provides detailed information about: - Compatible SQL syntax and language elements - Data types diff --git a/product_docs/docs/epas/14/epas_compat_ora_dev_guide/08_oracle_catalog_views.mdx b/product_docs/docs/epas/14/epas_compat_ora_dev_guide/08_oracle_catalog_views.mdx index 816b1529f93..0fb4ad2cd00 100644 --- a/product_docs/docs/epas/14/epas_compat_ora_dev_guide/08_oracle_catalog_views.mdx +++ b/product_docs/docs/epas/14/epas_compat_ora_dev_guide/08_oracle_catalog_views.mdx @@ -9,6 +9,6 @@ legacyRedirectsGenerated: -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 available in [Database Compatibility for Oracle Developers Catalog Views](/epas/latest/). +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 available in [Catalog views](/epas/latest/reference/oracle_compatibility_reference/epas_compat_cat_views/). diff --git a/product_docs/docs/epas/14/epas_compat_ora_dev_guide/09_tools_and_utilities.mdx b/product_docs/docs/epas/14/epas_compat_ora_dev_guide/09_tools_and_utilities.mdx index cdad86a63f2..bb12a54c905 100644 --- a/product_docs/docs/epas/14/epas_compat_ora_dev_guide/09_tools_and_utilities.mdx +++ b/product_docs/docs/epas/14/epas_compat_ora_dev_guide/09_tools_and_utilities.mdx @@ -14,5 +14,5 @@ Compatible tools and utility programs allow you to work with EDB Postgres Advanc - EDB\*Wrap - The Dynamic Runtime Instrumentation Tools Architecture (DRITA) -For detailed information about the functionality supported by EDB Postgres Advanced Server, see [Database Compatibility for Oracle Developers Tools and Utilities](/epas/latest/epas_compat_tools_guide/). +For detailed information about the functionality supported by EDB Postgres Advanced Server, see [Tools, utilities, and components](/epas/latest/epas_compat_tools_guide/). diff --git a/product_docs/docs/epas/14/epas_compat_ora_dev_guide/11_system_catalog_tables.mdx b/product_docs/docs/epas/14/epas_compat_ora_dev_guide/11_system_catalog_tables.mdx index 0d4271a7d13..c171060fa0f 100644 --- a/product_docs/docs/epas/14/epas_compat_ora_dev_guide/11_system_catalog_tables.mdx +++ b/product_docs/docs/epas/14/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 EDB Postgres Advanced Server. The layout of the system tables is subject to change. If you're writing an application that depends on information stored in the system tables, it's 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 Developers Catalog Views](/epas/latest/). +For detailed information about the system catalog tables, see the [Catalog views](/epas/latest/reference/oracle_compatibility_reference/epas_compat_cat_views/). diff --git a/product_docs/docs/epas/14/epas_compat_ora_dev_guide/index.mdx b/product_docs/docs/epas/14/epas_compat_ora_dev_guide/index.mdx index 81dfa887775..a86f3a6b1cd 100644 --- a/product_docs/docs/epas/14/epas_compat_ora_dev_guide/index.mdx +++ b/product_docs/docs/epas/14/epas_compat_ora_dev_guide/index.mdx @@ -18,9 +18,9 @@ Database compatibility for Oracle means that an application runs in an Oracle en - SQL statements that are compatible with Oracle SQL - System catalog views that are compatible with Oracle’s data dictionary -For detailed information about the compatible SQL syntax, data types, and views, see [Database Compatibility for Oracle Developers SQL](/epas/latest/epas_compat_sql/). +For detailed information about the compatible SQL syntax, data types, and views, see [SQL reference](/epas/latest/epas_compat_sql/). -For the compatibility offered by the procedures and functions that are part of the built-in packages, see [Database Compatibility for Oracle Developers Built-in Packages](/epas/latest/epas_compat_bip_guide/). +For the compatibility offered by the procedures and functions that are part of the built-in packages, see [Built-in packages](/epas/latest/epas_compat_bip_guide/). For information about using the compatible tools and utilities (EDB\*Plus, EDB\*Loader, DRITA, and EDB\*Wrap) that are included with an EDB Postgres Advanced Server installation, see [Tools and utilities](/epas/latest/epas_compat_ora_dev_guide/09_tools_and_utilities/). diff --git a/product_docs/docs/epas/14/epas_compat_reference/02_the_sql_language/01_sql_syntax/01_lexical_structure.mdx b/product_docs/docs/epas/14/epas_compat_reference/02_the_sql_language/01_sql_syntax/01_lexical_structure.mdx index c8a747b7183..8ec4a0b67b2 100644 --- a/product_docs/docs/epas/14/epas_compat_reference/02_the_sql_language/01_sql_syntax/01_lexical_structure.mdx +++ b/product_docs/docs/epas/14/epas_compat_reference/02_the_sql_language/01_sql_syntax/01_lexical_structure.mdx @@ -24,4 +24,4 @@ INSERT INTO MY_TABLE VALUES (3, 'hi there'); This is a sequence of three commands, one per line, although that format isn't required. You can enter more than one command on a line, and commands can usually split across lines. -The SQL syntax isn't very consistent regarding the tokens that identify commands and the ones that are operands or parameters. The first few tokens are generally the command name, so the example contains a `SELECT`, an `UPDATE`, and an `INSERT` command. But, for instance, the `UPDATE` command always requires a `SET` token to appear in a certain position, and this variation of `INSERT` also requires a `VALUES` token to be complete. The precise syntax rules for each command are described in [Database Compatibility for Oracle Developers SQL](/epas/latest/epas_compat_sql/). +The SQL syntax isn't very consistent regarding the tokens that identify commands and the ones that are operands or parameters. The first few tokens are generally the command name, so the example contains a `SELECT`, an `UPDATE`, and an `INSERT` command. But, for instance, the `UPDATE` command always requires a `SET` token to appear in a certain position, and this variation of `INSERT` also requires a `VALUES` token to be complete. The precise syntax rules for each command are described in [SQL reference](/epas/latest/epas_compat_sql/). diff --git a/product_docs/docs/epas/14/epas_compat_spl/14_packages.mdx b/product_docs/docs/epas/14/epas_compat_spl/14_packages.mdx index ebb259ce59e..dde4471edc6 100644 --- a/product_docs/docs/epas/14/epas_compat_spl/14_packages.mdx +++ b/product_docs/docs/epas/14/epas_compat_spl/14_packages.mdx @@ -17,4 +17,4 @@ A *package* is a named collection of functions, procedures, variables, cursors, - You can declare Other functions, procedures, variables, types, and so on in the package as *private*. Private entities can be referenced and used by function and procedures in the package but not by other external applications. Private entities are for use only by programs in the package. - You can overload function and procedure names in a package. One or more functions or procedures can be defined with the same name but with different signatures. This ability lets you create identically named programs that perform the same job but on different types of input. -For more information about the package support provided by EDB Postgres Advanced Server, see [Database Compatibility for Oracle Developers: Built-in Package](/epas/latest/epas_compat_bip_guide/). \ No newline at end of file +For more information about the package support provided by EDB Postgres Advanced Server, see [Built-in packages](/epas/latest/epas_compat_bip_guide/). \ No newline at end of file diff --git a/product_docs/docs/epas/14/epas_compat_sql/34_create_sequence.mdx b/product_docs/docs/epas/14/epas_compat_sql/34_create_sequence.mdx index fae7aeba5de..5d09b411cd4 100644 --- a/product_docs/docs/epas/14/epas_compat_sql/34_create_sequence.mdx +++ b/product_docs/docs/epas/14/epas_compat_sql/34_create_sequence.mdx @@ -27,7 +27,7 @@ CREATE SEQUENCE [ INCREMENT BY ] If you include a schema name, then the sequence is created in the specified schema. Otherwise it's created in the current schema. The sequence name differ from the name of any other sequence, table, index, or view in the same schema. -After you create a sequence, use the functions `NEXTVAL` and `CURRVAL` to operate on it. These functions are documented in [Database Compatibility for Oracle Developers: Reference](/epas/latest/epas_compat_reference/02_the_sql_language/03_functions_and_operators/09_sequence_manipulation_functions/). +After you create a sequence, use the functions `NEXTVAL` and `CURRVAL` to operate on it. These functions are documented in [SQL reference](/epas/latest/epas_compat_reference/02_the_sql_language/03_functions_and_operators/09_sequence_manipulation_functions/). ## Parameters diff --git a/product_docs/docs/epas/14/epas_compat_sql/36_create_table.mdx b/product_docs/docs/epas/14/epas_compat_sql/36_create_table.mdx index e3286f37b46..13970152ed5 100644 --- a/product_docs/docs/epas/14/epas_compat_sql/36_create_table.mdx +++ b/product_docs/docs/epas/14/epas_compat_sql/36_create_table.mdx @@ -97,7 +97,7 @@ You can define table constraints and column constraints. A column constraint is `data_type` - The data type of the column. This can include array specifiers. For more information on the data types included with EDB Postgres Advanced Server, see [Database Compatibility for Oracle Developers: Reference](/epas/latest/epas_compat_reference/02_the_sql_language/02_data_types/). + The data type of the column. This can include array specifiers. For more information on the data types included with EDB Postgres Advanced Server, see [SQL reference](/epas/latest/epas_compat_reference/02_the_sql_language/02_data_types/). `DEFAULT default_expr` diff --git a/product_docs/docs/epas/14/epas_compat_sql/71_select.mdx b/product_docs/docs/epas/14/epas_compat_sql/71_select.mdx index 2756683a0ea..1276ee800b2 100644 --- a/product_docs/docs/epas/14/epas_compat_sql/71_select.mdx +++ b/product_docs/docs/epas/14/epas_compat_sql/71_select.mdx @@ -57,7 +57,7 @@ You must have `SELECT` privilege on a table to read its values. The use of `FOR `optimizer_hint` - Comment-embedded hints to the optimizer for selecting an execution plan. See [Database Compatibility for Oracle Developers](/epas/latest/epas_compat_ora_dev_guide/) for information about optimizer hints. + Comment-embedded hints to the optimizer for selecting an execution plan. See [Database compatibility for Oracle developers](/epas/latest/epas_compat_ora_dev_guide/) for information about optimizer hints. ## FROM clause diff --git a/product_docs/docs/epas/14/epas_guide/02_enhanced_compatibility_features.mdx b/product_docs/docs/epas/14/epas_guide/02_enhanced_compatibility_features.mdx index 0bfc6529a11..477fe9d18db 100644 --- a/product_docs/docs/epas/14/epas_guide/02_enhanced_compatibility_features.mdx +++ b/product_docs/docs/epas/14/epas_guide/02_enhanced_compatibility_features.mdx @@ -19,7 +19,7 @@ legacyRedirectsGenerated: - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.026.html" --- -EDB Postgres Advanced Server includes extended functionality that provides compatibility for syntax supported by Oracle applications. See [Database Compatibility for Oracle Developers](/epas/latest/epas_compat_ora_dev_guide/) for detailed information about the compatibility features supported by EDB Postgres Advanced Server. +EDB Postgres Advanced Server includes extended functionality that provides compatibility for syntax supported by Oracle applications. See [Database compatibility for Oracle developers](/epas/latest/epas_compat_ora_dev_guide/) for detailed information about the compatibility features supported by EDB Postgres Advanced Server. ## Enabling compatibility features @@ -38,7 +38,7 @@ EDB Postgres Advanced Server supports a highly productive procedural language th - Provides a seamless development and testing environment. - Allows you to create reusable code. -See [Database Compatibility: Stored Procedural Language](/epas/latest/epas_compat_spl/) for more information. +See [Stored procedural language](/epas/latest/epas_compat_spl/) for more information. ## Optimizer hints @@ -123,7 +123,7 @@ For detailed information about the functions supported by the Open Client Librar ## Utilities -For detailed information about the compatible syntax supported by these utilities, see [Database Compatibility for Oracle Developers: Tools and Utilities](/epas/latest/epas_compat_tools_guide/). +For detailed information about the compatible syntax supported by these utilities, see [Tools, utilities, and components](/epas/latest/epas_compat_tools_guide/). ### EDB\*Plus @@ -189,4 +189,4 @@ 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 benefits from partitioning depends on the application. A good estimation is when the size of the table exceeds the physical memory of the database server. -For information about database compatibility features supported by EDB Postgres Advanced Server, see [Database Compatibility: Table Partitioning](/epas/latest/epas_compat_table_partitioning/). +For information about database compatibility features supported by EDB Postgres Advanced Server, see [Table partitioning](/epas/latest/epas_compat_table_partitioning/). diff --git a/product_docs/docs/epas/14/epas_guide/03_database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/12_customized_options.mdx b/product_docs/docs/epas/14/epas_guide/03_database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/12_customized_options.mdx index a02046c155e..1be5e8d5e2c 100644 --- a/product_docs/docs/epas/14/epas_guide/03_database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/12_customized_options.mdx +++ b/product_docs/docs/epas/14/epas_guide/03_database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/12_customized_options.mdx @@ -339,7 +339,7 @@ Use the `edbldr.empty_csv_field` parameter to specify how EDB\*Loader treats an | `empty_string` | An empty field is treated as a string of length zero. | | `pgsql` | An empty field is treated as a `NULL` if it doesn't contain quotes and as an empty string if it contains quotes. | -For more information about the `edbldr.empty_csv_field` parameter in EDB\*Loader, see the [Database Compatibility for Oracle Developers: Tools and Utilities](/epas/latest/epas_compat_tools_guide/). +For more information about the `edbldr.empty_csv_field` parameter in EDB\*Loader, see the [Tools, utilities, and components](/epas/latest/epas_compat_tools_guide/). ## utl_encode.uudecode_redwood diff --git a/product_docs/docs/epas/15/installing/windows/installing_advanced_server_with_the_interactive_installer/invoking_the_graphical_installer_from_the_command_line/reference_command_line_options.mdx b/product_docs/docs/epas/15/installing/windows/installing_advanced_server_with_the_interactive_installer/invoking_the_graphical_installer_from_the_command_line/reference_command_line_options.mdx index e4c089adb67..1c8084887d1 100644 --- a/product_docs/docs/epas/15/installing/windows/installing_advanced_server_with_the_interactive_installer/invoking_the_graphical_installer_from_the_command_line/reference_command_line_options.mdx +++ b/product_docs/docs/epas/15/installing/windows/installing_advanced_server_with_the_interactive_installer/invoking_the_graphical_installer_from_the_command_line/reference_command_line_options.mdx @@ -1,5 +1,5 @@ --- -title: "Reference: Command line options" +title: "Installation command line options" redirects: - /epas/latest/epas_inst_windows/03_installing_advanced_server_with_the_interactive_installer/02_invoking_the_graphical_installer_from_the_command_line/03_reference_command_line_options/ - /epas/latest/epas_inst_windows/installing_advanced_server_with_the_interactive_installer/invoking_the_graphical_installer_from_the_command_line/reference_command_line_options/ @@ -7,48 +7,44 @@ redirects: -You can optionally include the following parameters for an EDB Postgres Advanced Server installation on the command line, or in a configuration file when invoking the EDB Postgres Advanced Server installer. +You can optionally include the following parameters for an EDB Postgres Advanced Server installation on the command line or in a configuration file when invoking the EDB Postgres Advanced Server installer. `--create_samples { yes | no }` -Use the `--create_samples` option to specify whether the installer should create the sample tables and procedures for the database dialect specified with the `--databasemode` parameter. The default is `yes`. +Specifies whether the installer creates the sample tables and procedures for the database dialect specified with the `--databasemode` parameter. The default is `yes`. `--databasemode { oracle | postgresql }` -Use the `--databasemode` parameter to specify a database dialect. The default is `oracle`. +Specifies a database dialect. The default is `oracle`. `--datadir data_directory` -Use the `--datadir` parameter to specify a location for the cluster's data directory. `data_directory` is the name of the directory; include the complete path to the desired directory. +Specifies a location for the cluster's data directory. `data_directory` is the name of the directory. Include the complete path to the desired directory. `--debuglevel { 0 | 1 | 2 | 3 | 4 }` -Use the `--debuglevel` parameter to set the level of detail written to the `debug_log` file (see `--debugtrace`). Higher values produce more detail in a longer trace file. The default is `2`. +Sets the level of detail written to the `debug_log` file (see `--debugtrace`). Higher values produce more detail in a longer trace file. The default is `2`. `--debugtrace debug_log` -Use the `--debugtrace` parameter to troubleshoot installation problems. `debug_log` is the name of the file that contains troubleshooting details. +Helps with troubleshooting installation problems. `debug_log` is the name of the file that contains troubleshooting details. `--disable-components component_list` -Use the `--disable-components` parameter to specify a list of EDB Postgres Advanced Server components to exclude from the installation. By default, `component_list` contains '' (the empty string). `component_list` is a comma-separated list containing one or more of the following components: +Specifies a list of EDB Postgres Advanced Server components to exclude from the installation. By default, `component_list` contains '' (the empty string). `component_list` is a comma-separated list containing one or more of the following components: -`dbserver` +- `dbserver` — EDB Postgres Advanced Server. -EDB Postgres Advanced Server. - -`pgadmin4` - -The EDB Postgres pgAdmin 4 provides a powerful graphical interface for database management and monitoring. +- `pgadmin4` — The EDB Postgres pgAdmin 4 provides a powerful graphical interface for database management and monitoring. `--enable_acledit { 1 | 0 }` The `--enable_acledit 1` option instructs the installer to grant permission to the user specified by the `--serviceaccount` option to access the EDB Postgres Advanced Server binaries and `data` directory. By default, this option is disabled if `--enable_acledit 0` is specified or if the `--enable_acledit` option is completely omitted. !!! Note - Specification of this option is valid only when installing on Windows. The `--enable_acledit 1` option should be specified when a `discretionary access control list` (DACL) needs to be set for allowing access to objects on which EDB Postgres Advanced Server is to be installed. See the following for information on a DACL: https://msdn.microsoft.com/en-us/library/windows/desktop/aa446597(v=vs.85).aspx + Specifying this option is valid only when installing on Windows. Specify the `--enable_acledit 1` option when a discretionary access control list (DACL) needs to be set for allowing access to objects on which to install EDB Postgres Advanced Server. For information on a DACL, see [DACLs and ACEs](https://msdn.microsoft.com/en-us/library/windows/desktop/aa446597(v=vs.85).aspx) in the Microsoft documentation. -In order to perform future operations such as upgrading EDB Postgres Advanced Server, access to the `data` directory must exist for the service account user specified by the `--serviceaccount` option. By specifying the `--enable_acledit 1` option, access to the `data` directory by the service account user is provided. +To perform future operations, such as upgrading EDB Postgres Advanced Server, access to the `data` directory must exist for the service account user specified by the `--serviceaccount` option. By specifying the `--enable_acledit 1` option, access to the `data` directory by the service account user is provided. `--enable-components component_list` @@ -60,11 +56,11 @@ Include the `--extract-only` parameter to indicate that the installer should ext `--help` -Include the `--help` parameter to view a list of the optional parameters. +Displays a list of the optional parameters. `--installer-language { en | ja | zh_CN | zh_TW | ko }` -Use the `--installer-language` parameter to specify an installation language for EDB Postgres Advanced Server. The default is `en`. +Specifies an installation language for EDB Postgres Advanced Server. The default is `en`. `en` specifies English. @@ -78,7 +74,7 @@ Use the `--installer-language` parameter to specify an installation language for `--install_runtimes { yes | no }` -Include `--install_runtimes` to specify whether the installer should install the Microsoft Visual C++ runtime libraries. Default is `yes`. +Specifies whether to install the Microsoft Visual C++ runtime libraries. Default is `yes`. `--locale locale` @@ -86,15 +82,15 @@ Specifies the locale for the EDB Postgres Advanced Server cluster. By default, t `--mode { unattended }` -Use the `--mode unattended` parameter to specify that the installer should perform an installation that requires no user input during the installation process. +Specifies for the installer to perform an installation that requires no user input during the installation process. `--optionfile config_file` -Use the `--optionfile` parameter to specify the name of a file that contains the installation configuration parameters. `config_file` must specify the complete path to the configuration parameter file. +Specifies the name of a file that contains the installation configuration parameters. `config_file` must specify the complete path to the configuration parameter file. `--prefix installation_dir/as14` -Use the `--prefix` parameter to specify an installation directory for EDB Postgres Advanced Server. The installer appends a version-specific sub-directory (that is, `as14`) to the specified directory. The default installation directory is: +Specifies an installation directory for EDB Postgres Advanced Server. The installer appends a version-specific subdirectory (that is, `as14`) to the specified directory. The default installation directory is: ```text C:\Program Files\edb\as14 @@ -102,70 +98,70 @@ C:\Program Files\edb\as14 `--serverport port_number` -Use the `--serverport` parameter to specify a listener port number for EDB Postgres Advanced Server. +Specifies a listener port number for EDB Postgres Advanced Server. -If you are installing EDB Postgres Advanced Server in unattended mode, and don't specify a value using the `--serverport` parameter, the installer uses port `5444`, or the first available port after port `5444` as the default listener port. +If you're installing EDB Postgres Advanced Server in unattended mode and don't specify a value using the `--serverport` parameter, the installer uses port `5444` or the first available port after port `5444` as the default listener port. `--server_utilization {33 | 66 | 100}` -Use the `--server_utilization` parameter to specify a value for the `edb_dynatune` configuration parameter. The `edb_dynatune` configuration parameter determines how EDB Postgres Advanced Server allocates system resources. +Specifies a value for the `edb_dynatune` configuration parameter. The `edb_dynatune` configuration parameter determines how EDB Postgres Advanced Server allocates system resources. - A value of `33` is appropriate for a system used for development. A low value dedicates the least amount of the host machine’s resources to the database server. -- A value of `66` is appropriate for an application server with a fixed number of applications. A mid-range value dedicates a moderate amount of system resources to the database server. The default value is 66. -- A value of `100` is appropriate for a host machine that is dedicated to running EDB Postgres Advanced Server. A high value dedicates most of the system resources to the database server. +- A value of `66` is appropriate for an application server with a fixed number of applications. A midrange value dedicates a moderate amount of system resources to the database server. The default value is 66. +- A value of `100` is appropriate for a host machine that's dedicated to running EDB Postgres Advanced Server. A high value dedicates most of the system resources to the database server. When the installation is complete, you can adjust the value of `edb_dynatune` by editing the `postgresql.conf` file, located in the `data` directory of your EDB Postgres Advanced Server installation. After editing the `postgresql.conf` file, you must restart the server for the changes to take effect. `--serviceaccount user_account_name` -Use the `--serviceaccount` parameter to specify the name of the user account that owns the server process. +Specifies the name of the user account that owns the server process. - If `--databasemode` is set to `oracle` (the default), the default value of `--serviceaccount` is `enterprisedb`. - If `--databasemode` is `postgresql`, the default value of `--serviceaccount` is set to `postgres`. -For security reasons, the `--serviceaccount` parameter must specify the name of an account that does not hold administrator privileges. +For security reasons, the `--serviceaccount` parameter must specify the name of an account that doesn't hold administrator privileges. -If you specify both the `--serviceaccount` option and the `--enable_acledit 1` option when invoking the installer, the database service and pgAgent uses the same service account, thereby having the required permissions to access the EDB Postgres Advanced Server binaries and `data` directory. +If you specify both the `--serviceaccount` option and the `--enable_acledit 1` option when invoking the installer, the database service and pgAgent uses the same service account. They therefore have the required permissions to access the EDB Postgres Advanced Server binaries and `data` directory. !!! Note If you don't include the `--serviceaccount` option when invoking the installer, the `NetworkService` account owns the database service, and the pgAgent service is owned by either `enterprisedb` or `postgres` (depending on the installation mode). `--servicename service_name` -Use the `--servicename` parameter to specify the name of the EDB Postgres Advanced Server service. The default is `edb-as-14`. +Specifies the name of the EDB Postgres Advanced Server service. The default is `edb-as-14`. `--servicepassword user_password` -Use `--servicepassword` to specify the OS system password. If unspecified, the value of `--servicepassword` defaults to the value of `--superpassword`. +Specifies the OS system password. If unspecified, the value of `--servicepassword` defaults to the value of `--superpassword`. `--superaccount super_user_name` -Use the `--superaccount` parameter to specify the user name of the database superuser. +Specifies the user name of the database superuser. - If `--databasemode` is set to `oracle` (the default), the default value of `--superaccount` is `enterprisedb`. - If `--databasemode` is set to `postgresql`, the default value of `--superaccount` is set to `postgres`. `--superpassword superuser_password` -Use `--superpassword` to specify the database superuser password. If you are installing in non-interactive mode, `--superpassword` defaults to `enterprisedb`. +Specifies the database superuser password. If you're installing in non-interactive mode, `--superpassword` defaults to `enterprisedb`. `--unattendedmodeui { none | minimal | minimalWithDialogs }` -Use the `--unattendedmodeui` parameter to specify installer behavior during an unattended installation. +Specifies installer behavior during an unattended installation. -Include `--unattendedmodeui none` to specify that the installer should not display progress bars during the EDB Postgres Advanced Server installation. +Include `--unattendedmodeui none` to specify for the installer not to display progress bars during the EDB Postgres Advanced Server installation. -Include `--unattendedmodeui minimal` to specify that the installer should display progress bars during the installation process. This is the default behavior. +Include `--unattendedmodeui minimal` to specify for the installer to display progress bars during the installation process. This is the default behavior. -Include `--unattendedmodeui minimalWithDialogs` to specify that the installer should display progress bars and report any errors encountered during the installation process (in additional dialogs). +Include `--unattendedmodeui minimalWithDialogs` to specify for the installer to display progress bars and report any errors encountered during the installation process in additional dialog boxes. `--version` -Include the `--version` parameter to retrieve version information about the installer: +Retrieves version information about the installer. `--workload_profile {oltp | mixed | reporting}` -Use the `--workload_profile` parameter to specify an initial value for the `edb_dynatune_profile` configuration parameter. `edb_dynatune_profile` controls aspects of performance-tuning based on the type of work that the server performs. +Specifies an initial value for the `edb_dynatune_profile` configuration parameter. `edb_dynatune_profile` controls aspects of performance-tuning based on the type of work that the server performs. - Specify `oltp` if the EDB Postgres Advanced Server installation is used to support heavy online transaction processing workloads. - The default value is `oltp`. @@ -174,6 +170,4 @@ Use the `--workload_profile` parameter to specify an initial value for the `edb_ After the installation is complete, you can adjust the value of `edb_dynatune_profile` by editing the `postgresql.conf` file, located in the `data` directory of your EDB Postgres Advanced Server installation. After editing the `postgresql.conf` file, you must restart the server for the changes to take effect. -For more information about `edb_dynatune` and other performance-related topics, see the *EDB Postgres Advanced Server Guide* available at: - -[https://www.enterprisedb.com/docs](/epas/latest/) +For more information about `edb_dynatune` and other performance-related topics, see [Managing performance](/epas/latest/managing_performance/). diff --git a/product_docs/docs/epas/15/upgrading/04_upgrading_an_installation_with_pg_upgrade/02_invoking_pg_upgrade/01_command_line_options_reference.mdx b/product_docs/docs/epas/15/upgrading/04_upgrading_an_installation_with_pg_upgrade/02_invoking_pg_upgrade/01_command_line_options_reference.mdx index 053609d6f69..adb0e2d782a 100644 --- a/product_docs/docs/epas/15/upgrading/04_upgrading_an_installation_with_pg_upgrade/02_invoking_pg_upgrade/01_command_line_options_reference.mdx +++ b/product_docs/docs/epas/15/upgrading/04_upgrading_an_installation_with_pg_upgrade/02_invoking_pg_upgrade/01_command_line_options_reference.mdx @@ -1,5 +1,5 @@ --- -title: "Command line options: Reference" +title: "Command line options for pg_upgrade" redirects: - /epas/latest/epas_upgrade_guide/04_upgrading_an_installation_with_pg_upgrade/02_invoking_pg_upgrade/01_command_line_options_reference/ ---