From 5cb88cd31d9e1312d04c9640137fe28ea9158d23 Mon Sep 17 00:00:00 2001 From: Josh Earlenbaugh Date: Mon, 18 Nov 2024 13:44:30 -0500 Subject: [PATCH 01/24] Added version 17 folder. --- .../17/02_supported_platforms.mdx | 9 + .../17/03_libpq_compatibility.mdx | 37 ++ .../02_forming_a_connection_string.mdx | 48 ++ .../03_compiling_and_linking_a_program.mdx | 41 ++ .../04_ref_cursor_support.mdx | 120 +++++ .../05_ocl_function_reference.mdx | 436 ++++++++++++++++++ .../06_ocl_error_codes_reference.mdx | 68 +++ .../07_multithreading_support.mdx | 25 + .../04_open_client_library/08_otl_support.mdx | 222 +++++++++ .../17/04_open_client_library/index.mdx | 20 + .../17/05_generating_the_ocl_trace.mdx | 23 + .../docs/ocl_connector/17/06_using_ssl.mdx | 41 ++ .../17/07_scram_compatibility.mdx | 8 + .../17/images/ocl_installation_complete.png | 3 + .../17/images/ocl_installation_dialog.png | 3 + .../17/images/ocl_installation_wizard.png | 3 + .../17/images/oracle_call_interface.png | 3 + .../17/images/ready_to_install.png | 3 + .../selecting_the_connectors_installer.png | 3 + .../17/images/starting_stackbuilder_plus.png | 3 + product_docs/docs/ocl_connector/17/index.mdx | 21 + .../ocl_connector/17/installing/index.mdx | 66 +++ .../17/installing/linux_arm64/index.mdx | 13 + .../installing/linux_arm64/ocl_debian_12.mdx | 47 ++ .../17/installing/linux_ppc64le/index.mdx | 28 ++ .../installing/linux_ppc64le/ocl_rhel_8.mdx | 56 +++ .../installing/linux_ppc64le/ocl_rhel_9.mdx | 56 +++ .../installing/linux_ppc64le/ocl_sles_15.mdx | 57 +++ .../17/installing/linux_x86_64/index.mdx | 56 +++ .../installing/linux_x86_64/ocl_debian_11.mdx | 47 ++ .../installing/linux_x86_64/ocl_debian_12.mdx | 47 ++ .../linux_x86_64/ocl_other_linux_8.mdx | 58 +++ .../linux_x86_64/ocl_other_linux_9.mdx | 58 +++ .../17/installing/linux_x86_64/ocl_rhel_8.mdx | 52 +++ .../17/installing/linux_x86_64/ocl_rhel_9.mdx | 52 +++ .../installing/linux_x86_64/ocl_sles_15.mdx | 57 +++ .../installing/linux_x86_64/ocl_ubuntu_20.mdx | 47 ++ .../installing/linux_x86_64/ocl_ubuntu_22.mdx | 47 ++ .../ocl_connector/17/installing/upgrading.mdx | 32 ++ .../ocl_connector/17/installing/windows.mdx | 50 ++ .../16.1.0.1_ocl_release_notes.mdx | 14 + .../16.1.0.2_ocl_release_notes.mdx | 14 + .../ocl_connector/17/ocl_rel_notes/index.mdx | 16 + 43 files changed, 2110 insertions(+) create mode 100644 product_docs/docs/ocl_connector/17/02_supported_platforms.mdx create mode 100644 product_docs/docs/ocl_connector/17/03_libpq_compatibility.mdx create mode 100644 product_docs/docs/ocl_connector/17/04_open_client_library/02_forming_a_connection_string.mdx create mode 100644 product_docs/docs/ocl_connector/17/04_open_client_library/03_compiling_and_linking_a_program.mdx create mode 100644 product_docs/docs/ocl_connector/17/04_open_client_library/04_ref_cursor_support.mdx create mode 100644 product_docs/docs/ocl_connector/17/04_open_client_library/05_ocl_function_reference.mdx create mode 100644 product_docs/docs/ocl_connector/17/04_open_client_library/06_ocl_error_codes_reference.mdx create mode 100644 product_docs/docs/ocl_connector/17/04_open_client_library/07_multithreading_support.mdx create mode 100644 product_docs/docs/ocl_connector/17/04_open_client_library/08_otl_support.mdx create mode 100644 product_docs/docs/ocl_connector/17/04_open_client_library/index.mdx create mode 100644 product_docs/docs/ocl_connector/17/05_generating_the_ocl_trace.mdx create mode 100644 product_docs/docs/ocl_connector/17/06_using_ssl.mdx create mode 100644 product_docs/docs/ocl_connector/17/07_scram_compatibility.mdx create mode 100755 product_docs/docs/ocl_connector/17/images/ocl_installation_complete.png create mode 100755 product_docs/docs/ocl_connector/17/images/ocl_installation_dialog.png create mode 100755 product_docs/docs/ocl_connector/17/images/ocl_installation_wizard.png create mode 100755 product_docs/docs/ocl_connector/17/images/oracle_call_interface.png create mode 100755 product_docs/docs/ocl_connector/17/images/ready_to_install.png create mode 100644 product_docs/docs/ocl_connector/17/images/selecting_the_connectors_installer.png create mode 100644 product_docs/docs/ocl_connector/17/images/starting_stackbuilder_plus.png create mode 100644 product_docs/docs/ocl_connector/17/index.mdx create mode 100644 product_docs/docs/ocl_connector/17/installing/index.mdx create mode 100644 product_docs/docs/ocl_connector/17/installing/linux_arm64/index.mdx create mode 100644 product_docs/docs/ocl_connector/17/installing/linux_arm64/ocl_debian_12.mdx create mode 100644 product_docs/docs/ocl_connector/17/installing/linux_ppc64le/index.mdx create mode 100644 product_docs/docs/ocl_connector/17/installing/linux_ppc64le/ocl_rhel_8.mdx create mode 100644 product_docs/docs/ocl_connector/17/installing/linux_ppc64le/ocl_rhel_9.mdx create mode 100644 product_docs/docs/ocl_connector/17/installing/linux_ppc64le/ocl_sles_15.mdx create mode 100644 product_docs/docs/ocl_connector/17/installing/linux_x86_64/index.mdx create mode 100644 product_docs/docs/ocl_connector/17/installing/linux_x86_64/ocl_debian_11.mdx create mode 100644 product_docs/docs/ocl_connector/17/installing/linux_x86_64/ocl_debian_12.mdx create mode 100644 product_docs/docs/ocl_connector/17/installing/linux_x86_64/ocl_other_linux_8.mdx create mode 100644 product_docs/docs/ocl_connector/17/installing/linux_x86_64/ocl_other_linux_9.mdx create mode 100644 product_docs/docs/ocl_connector/17/installing/linux_x86_64/ocl_rhel_8.mdx create mode 100644 product_docs/docs/ocl_connector/17/installing/linux_x86_64/ocl_rhel_9.mdx create mode 100644 product_docs/docs/ocl_connector/17/installing/linux_x86_64/ocl_sles_15.mdx create mode 100644 product_docs/docs/ocl_connector/17/installing/linux_x86_64/ocl_ubuntu_20.mdx create mode 100644 product_docs/docs/ocl_connector/17/installing/linux_x86_64/ocl_ubuntu_22.mdx create mode 100644 product_docs/docs/ocl_connector/17/installing/upgrading.mdx create mode 100644 product_docs/docs/ocl_connector/17/installing/windows.mdx create mode 100644 product_docs/docs/ocl_connector/17/ocl_rel_notes/16.1.0.1_ocl_release_notes.mdx create mode 100644 product_docs/docs/ocl_connector/17/ocl_rel_notes/16.1.0.2_ocl_release_notes.mdx create mode 100644 product_docs/docs/ocl_connector/17/ocl_rel_notes/index.mdx diff --git a/product_docs/docs/ocl_connector/17/02_supported_platforms.mdx b/product_docs/docs/ocl_connector/17/02_supported_platforms.mdx new file mode 100644 index 00000000000..0036e328fa5 --- /dev/null +++ b/product_docs/docs/ocl_connector/17/02_supported_platforms.mdx @@ -0,0 +1,9 @@ +--- +title: "Supported platforms" + +--- + + + +The EDB OCL Connector is supported on the same platforms as EDB Postgres Advanced Server. To determine the platform support for the EDB OCL Connector, you can refer either to the platform support for EDB Postgres Advanced Server on the [Platform Compatibility page](https://www.enterprisedb.com/platform-compatibility#epas) on the EDB website or to [Installing EDB OCL Connector](./installing). + diff --git a/product_docs/docs/ocl_connector/17/03_libpq_compatibility.mdx b/product_docs/docs/ocl_connector/17/03_libpq_compatibility.mdx new file mode 100644 index 00000000000..338066e6851 --- /dev/null +++ b/product_docs/docs/ocl_connector/17/03_libpq_compatibility.mdx @@ -0,0 +1,37 @@ +--- +title: "libpq cross-version compatibility" + +--- + + + +EDB OCL installation always uses the latest libpq. When upgrading to a new major release of EDB Postgres Advanced Server, the different scenarios supported under libpq cross-version compatibility are as follows: + +- If the latest libpq is installed on the machine, OCL uses it. +- If the latest libpq isn't already installed, OCL installs it. It doesn't use the existing libpq of older versions even if it's installed. +- If you upgrade the OCL version, then libpq is also upgraded to its latest version. + +If you're upgrading to a minor release, you need to manually upgrade libpq. + +## Upgrading libpq for minor releases of EDB Postgres Advanced Server + +For minor releases of EDB Postgres Advanced Server, you might need to upgrade libpq to a required version on the client machine where you installed EDB OCL Connector. (Any new libpq version dependencies are listed in the release notes.) If you need to upgrade libpq, run the appropriate command for your operating system. + +### For Ubuntu/Debian + +``` +sudo apt-get install edb-as15-libpq5 +``` + +### For RHEL and SLES + +``` +sudo install edb-as15-server-libs +``` + +Where `` is the package manager used with your operating system: + +| Package manager | Operating system | +| --------------- | -------------------------------- | +| dnf | RHEL 8/9 and derivatives | +| zypper | SLES | \ No newline at end of file diff --git a/product_docs/docs/ocl_connector/17/04_open_client_library/02_forming_a_connection_string.mdx b/product_docs/docs/ocl_connector/17/04_open_client_library/02_forming_a_connection_string.mdx new file mode 100644 index 00000000000..77ee84e425f --- /dev/null +++ b/product_docs/docs/ocl_connector/17/04_open_client_library/02_forming_a_connection_string.mdx @@ -0,0 +1,48 @@ +--- +title: "Forming a connection string" + +--- + + + +The EDB OCL Connector accepts both Oracle-style and Postgres-style connection URIs. A connection string can take the following Oracle-style form: + + `[//][host][:port][/dbname]` + +Or it can take the following Postgres-style forms: + +```text +postgres://[user[:password]@][host][:port][/dbname] +[?param1=value1&...] +``` + +```text +postgresql://[user[:password]@][host][:port][/dbname] +[?param1=value1&...] +``` + +You can also use a Postgres-style URI to specify multiple host components, each with an optional port component, in a single URI. A multi-host connection string takes the form: + + `postgresql://:@host1:port1,host2:port2,host3:port3/` + +Where: + + `user` is the name of the connecting user. + + `password` is the password associated with the connecting user. + + `host` is the host name or IP address to which you're connecting. To specify an IPV6 address, enclose the address in square brackets. + + `port` is the port number to which you're connecting. + + `dbname` is the name of the database with which you're connecting. + + `paramx=valuex` pairs specify extra, application-specific connection properties. + +For example, each of the following connection strings establishes a connection to the `edb` database on port `5444` of a system with an IP address of `10.0.0.4`: + + `//10.0.0.4:5444/edb` + `postgres://:@10.0.0.4:5444/edb` + `postgresql://:@10.0.0.4:5444/edb` + +For more information about using Postgres-style connection strings, see the [PostgreSQL core documentation](https://www.postgresql.org/docs/). diff --git a/product_docs/docs/ocl_connector/17/04_open_client_library/03_compiling_and_linking_a_program.mdx b/product_docs/docs/ocl_connector/17/04_open_client_library/03_compiling_and_linking_a_program.mdx new file mode 100644 index 00000000000..9cf803a12ba --- /dev/null +++ b/product_docs/docs/ocl_connector/17/04_open_client_library/03_compiling_and_linking_a_program.mdx @@ -0,0 +1,41 @@ +--- +title: "Compiling and linking a program" + +--- + + + +The EDB Open Client Library allows applications written using the Oracle Call Interface API to connect to and access an EDB database with minimal changes to the C source code. The EDB Open Client Library files are named: + +- On Linux: `libedboci.so` + +- On Windows: `edboci.dll` + +The files are installed in the `oci/lib` subdirectory. + +## Compiling and linking a sample program + +This example compiles and links the sample program `edb_demo.c` in a Linux environment. The `edb_demo.c` file is located in the `oci/samples` subdirectory. + +1. Set `ORACLE_HOME` to the complete pathname of the Oracle home directory, for example: + + `export ORACLE_HOME=/usr/lib/oracle/xe/app/oracle/product/10.2.0/server` + +1. Set `EDB_HOME` to the complete pathname of the home directory, for example: + + `export EDB_HOME=/usr/edb` + +1. Set `LD_LIBRARY_PATH` to the complete path of `libpthread.so`. By default, `libpthread.so` is located in `/lib64`. + + `export LD_LIBRARY_PATH=/lib64/lib:$LD_LIBRARY_PATH` + +1. Set `LD_LIBRARY_PATH` to include the EDB Postgres Advanced Server Open Client library. By default, `libedboci.so` is located in `$EDB_HOME/oci/lib`. + + `export LD_LIBRARY_PATH=$EDB_HOME/oci:$EDB_HOME/oci/lib:$LD_LIBRARY_PATH` + +1. Compile and link the OCL API program: + + ```text + cd $EDB_HOME/oci/samples + make + ``` diff --git a/product_docs/docs/ocl_connector/17/04_open_client_library/04_ref_cursor_support.mdx b/product_docs/docs/ocl_connector/17/04_open_client_library/04_ref_cursor_support.mdx new file mode 100644 index 00000000000..cb84ed028d4 --- /dev/null +++ b/product_docs/docs/ocl_connector/17/04_open_client_library/04_ref_cursor_support.mdx @@ -0,0 +1,120 @@ +--- +title: "Ref cursor support" + +--- + + + +The EDB Postgres Advanced Server Open Client Library supports the use of `REF CURSOR` as `OUT` parameters in PL/SQL procedures that are compatible with Oracle. Support is provided through the following APIs: + +- `OCIBindByName` +- `OCIBindByPos` +- `OCIBindDynamic` +- `OCIStmtPrepare` +- `OCIStmtExecute` +- `OCIStmtFetch` +- `OCIAttrGet` + +The EDB OCL Connector also supports the `SQLT_RSET` data type. + +This example invokes a stored procedure that opens a cursor and returns a `REF CURSOR` as an output parameter. The code sample assumes that a PL/SQL procedure named `openCursor`, with an `OUT` parameter of type `REF CURSOR`, was created on the database server and that the required handles were allocated: + +```c +char* openCursor = "begin \ + openCursor(:cmdRefCursor); \ + end;"; +OCIStmt* stmtOpenRefCursor; +OCIStmt* stmtUseRefCursor; +``` + +Allocate handles for executing a stored procedure to open and use the `REF CURSOR`: + +```c +/* Handle for the stored procedure to open the ref cursor */ +OCIHandleAlloc((dvoid *) envhp, + (dvoid **) &stmtOpenRefCursor, + OCI_HTYPE_STMT, + 0, + (dvoid **) NULL)); +``` + +```c +/* Handle for using the Ref Cursor */ +OCIHandleAlloc((dvoid *) envhp, + (dvoid **) &stmtUseRefCursor, + OCI_HTYPE_STMT, + 0, + (dvoid **) NULL)); +``` + +Then, prepare the PL/SQL block that's used to open the `REF CURSOR`: + +```c +OCIStmtPrepare(stmtOpenRefCursor, + errhp, + (text *) openCursor, + (ub4) strlen(openCursor), + OCI_NTV_SYNTAX, + OCI_DEFAULT)); +``` + +Bind the PL/SQL `openCursor OUT` parameter: + +```c +OCIBindByPos(stmtOpenRefCursor, + &bndplrc1, + errhp, + 1, + (dvoid*) &stmtUseRefCursor, + /* the returned ref cursor */ + 0, + SQLT_RSET, + /* SQLT_RSET type representing cursor */ + (dvoid *) 0, + (ub2 *) 0, + (ub2) 0, + (ub4) 0, + (ub4 *) 0, + OCI_DEFAULT)); +``` + +Use the `stmtOpenRefCursor` statement handle to call the `openCursor` procedure: + +```c +OCIStmtExecute(svchp, + stmtOpenRefCursor, + errhp, + 1, + 0, + 0, + 0, + OCI_DEFAULT); +``` + +At this point, the `stmtUseRefCursor` statement handle contains the reference to the cursor. To obtain the information, define output variables for the ref cursor: + +```c +/* Define the output variables for the ref cursor */ + OCIDefineByPos(stmtUseRefCursor, + &defnEmpNo, + errhp, + (ub4) 1, + (dvoid *) &empNo, + (sb4) sizeof(empNo), + SQLT_INT, + (dvoid *) 0, + (ub2 *)0, + (ub2 *)0, + (ub4) OCI_DEFAULT)); +``` + +Then, fetch the first row of the result set into the target variables: + +```c +/* Fetch the cursor data */ + OCIStmtFetch(stmtUseRefCursor, + errhp, + (ub4) 1, + (ub4) OCI_FETCH_NEXT, + (ub4) OCI_DEFAULT)) +``` diff --git a/product_docs/docs/ocl_connector/17/04_open_client_library/05_ocl_function_reference.mdx b/product_docs/docs/ocl_connector/17/04_open_client_library/05_ocl_function_reference.mdx new file mode 100644 index 00000000000..5879d6654e9 --- /dev/null +++ b/product_docs/docs/ocl_connector/17/04_open_client_library/05_ocl_function_reference.mdx @@ -0,0 +1,436 @@ +--- +title: "OCL function reference" + +--- + + + +The following tables list the functions supported by the EDB OCL connector. You must supply any header files. EDB Postgres Advanced Server doesn't supply header files. + +## Connect, authorize, and initialize functions + +| Function | Description | +| ----------------- | -------------------------------------------- | +| OCIBreak | Abort the specified OCL function. | +| OCIEnvCreate | Create an OCL environment. | +| OCIEnvInit | Initialize an OCL environment handle. | +| OCIInitialize | Initialize the OCL environment. | +| OCILogoff | Release a session. | +| OCILogon | Create a logon connection. | +| OCILogon2 | Create a logon session in various modes. | +| OCIReset | Reset the current operation/protocol. | +| OCIServerAttach | Establish an access path to a data source. | +| OCIServerDetach | Remove access to a data source. | +| OCISessionBegin | Create a user session. | +| OCISessionEnd | End a user session. | +| OCISessionGet | Get session from session pool. | +| OCISessionRelease | Release a session. | +| OCITerminate | Detach from shared memory subsystem. | + +### Using the tnsnames.ora file + +The `OCIServerAttach` and `OCILogon` methods use `NET_SERVICE_NAME` as a connection descriptor specified in the `dblink` parameter of the `tnsnames.ora` file. Use the `tnsnames.ora` file (compatible with Oracle databases) to specify database connection details. OCL searches your home directory for a file named `.tnsnames.ora`. If OCL doesn't find the `.tnsnames.ora` file there, it searches for `tnsnames.ora` on the path specified in `TNS_ADMIN` environment variable. + +You can specify multiple descriptors `(NET_SERVICE_NAME)` in the `tnsnames.ora` file. + +The sample `tnsnames.ora` file contains: + +```text +EDBX = +(DESCRIPTION = + (ADDRESS = (PROTOCOL = TCP)(HOST = localhost)(PORT = 5444)) + (CONNECT_DATA = (SERVER = DEDICATED)(SID = edb)) +) +``` + +Any parameters not included in the files are ignored by the Open Client Library. In the example, `SID` refers to the database named `edb` in the cluster running on `localhost` on port `5444`. + +A C program call to `OCIServerAttach` that uses the `tnsnames.ora` file looks like: + +```c +static text* username = (text*)"enterprisedb"; +static text* password = (text*)"edb"; +static text* attach_str = "EDBX"; +OCIServerAttach(srvhp, + errhp, + attach_str, + strlen(attach_str), + 0); +``` + +If you don't have a `tnsnames.ora` file, supply the connection string in the form `//localhost:5444/edbx`. + +!!! Note + Multiple descriptors are also supported in `tnsnames.ora`. + +## Handle and descriptor functions + +| Function | Description | +| ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| OCIAttrGet | Get handle attributes. EDB Postgres Advanced Server supports the following handle attributes: OCI_ATTR_USERNAME, OCI_ATTR_PASSWORD, OCI_ATTR_SERVER, OCI_ATTR_ENV, OCI_ATTR_SESSION, OCI_ATTR_ROW_COUNT, OCI_ATTR_CHARSET_FORM, OCI_ATTR_CHARSET_ID, EDB_ATTR_STMT_LEVEL_TX, OCI_ATTR_MODULE | +| OCIAttrSet | Set handle attributes. EDB Postgres Advanced Server supports the following handle attributes: OCI_ATTR_USERNAME, OCI_ATTR_PASSWORD, OCI_ATTR_SERVER, OCI_ATTR_ENV, OCI_ATTR_SESSION, OCI_ATTR_ROW_COUNT, OCI_ATTR_CHARSET_FORM, OCI_ATTR_CHARSET_ID, EDB_ATTR_STMT_LEVEL_TX, OCI_ATTR_MODULE, OCI_ATTR_PREFETCH_ROWS | +| OCIDescriptorAlloc | Allocate and initialize a descriptor. | +| OCIDescriptorFree | Free an allocated descriptor. | +| OCIHandleAlloc | Allocate and initialize a handle. | +| OCIHandleFree | Free an allocated handle. | +| OCIParamGet | Get a parameter descriptor. | +| OCIParamSet | Set a parameter descriptor. | + +### EDB_ATTR_EMPTY_STRINGS + +By default, EDB Postgres Advanced Server treats an empty string as a NULL value. You can use the `EDB_ATTR_EMPTY_STRINGS` environment attribute to control the behavior of the OCL connector when mapping empty strings. To modify the mapping behavior, use the `OCIAttrSet()` function to set `EDB_ATTR_EMPTY_STRINGS` to one of the following. + +| Value | Description | +| ----------------------- | ------------------------------------------------- | +| OCI_DEFAULT | Treat an empty string as a NULL value. | +| EDB_EMPTY_STRINGS_NULL | Treat an empty string as a NULL value. | +| EDB_EMPTY_STRINGS_EMPTY | Treat an empty string as a string of zero length. | + +To find the value of `EDB_ATTR_EMPTY_STRINGS`, query `OCIAttrGet()`. + +### EDB_ATTR_HOLDABLE + +EDB Postgres Advanced Server supports statements that execute as `WITH HOLD` cursors. The `EDB_ATTR_HOLDABLE` attribute specifies the statements that execute as `WITH HOLD` cursors. You can set the `EDB_ATTR_HOLDABLE` attribute to any of the following values: + +- `EDB_WITH_HOLD` — Execute as a `WITH HOLD` cursor. +- `EDB_WITHOUT_HOLD` — Execute using a protocol-level prepared statement. +- `OCI_DEFAULT` — See the definition that follows. + +You can set the attribute in an `OCIStmt` handle or an `OCIServer` handle. When you create an `OCIServer` handle or an `OCIStmt` handle, the `EDB_ATTR_HOLDABLE` attribute for that handle is set to `OCI_DEFAULT`. + +You can change the `EDB_ATTR_HOLDABLE` attribute for a handle by calling `OCIAttrSet()` and retrieve the attribute by calling `OCIAttrGet()`. + +When EDB Postgres Advanced Server executes a `SELECT` statement, it examines the `EDB_ATTR_HOLDABLE` attribute in the `OCIServer` handle. If that attribute is set to `EDB_WITH_HOLD`, the query is executed as a `WITH HOLD` cursor. + +If the `EDB_ATTR_HOLDABLE` attribute in the `OCIServer` handle is set to `EDB_WITHOUT_HOLD`, the query is executed as a normal prepared statement. + +If the `EDB_ATTR_HOLDABLE` attribute in the `OCIServer` handle is set to `OCI_DEFAULT`, EDB Postgres Advanced Server uses the value of the `EDB_ATTR_HOLDABLE` attribute in the `OCIServer` handle. (If the `EDB_ATTR_HOLDABLE` attribute in the `OCIServer` is set to `EDB_WITH_HOLD`, the query executes as a `WITH HOLD` cursor. Otherwise, the query executes as a protocol-prepared statement.) + +### EDB_HOLD_CURSOR_ACTION + +The `EDB_HOLD_CURSOR_ACTION` attribute alters the way `WITH HOLD` cursors are created using the OCL interface. You can set this attribute to any of the following values: + +- `EDB_COMMIT_AFTER_CURSOR` — Commit the transaction after creating the cursor. +- `EDB_CURSOR_WITHOUT_XACT_BLK` — Don't begin a new transaction chain. +- `OCI_DEFAULT` — See the definition that follows. + +The following describes the attribute values. + +`OCI_DEFAULT` + +Each time you execute a statement, the OCL examines the transaction state on the database server. If a transaction isn't already in progress, the OCL executes a `BEGIN` statement to create a new transaction block and then executes the statement that you provide. The transaction block remains open until you call `OCITransCommit()` or `OCITransRollback()`. + +By default, the database server closes any open cursors when you commit or roll back. If you (or the OCL) declare a cursor that includes the `WITH HOLD` clause, the cursor result set is persisted on the database server, and you can continue to fetch from that cursor. However, the database server doesn't persist open cursors when you roll back a transaction. If you try to fetch from a cursor after a `ROLLBACK`, the database server reports an error. + +`EDB_COMMIT_AFTER_CURSOR` + +If your application must read from a `WITH HOLD` cursor after rolling back a transaction, you can arrange for the OCL to commit the transaction immediately after creating the cursor by setting `EDB_HOLD_CURSOR_ACTION` to `EDB_COMMIT_AFTER_CURSOR` prior to creating such a cursor. For example: + +```c +ub4 action = EDB_COMMIT_AFTER_CURSOR; + +OCIAttrSet(stmt, + OCI_HTYPE_STMT, + &action, + sizeof(action), + EDB_ATTR_HOLD_CURSOR_ACTION, + err); + +OCIStmtExecute(...); +``` + +!!! Note + Using `EDB_COMMIT_AFTER_CURSOR` commits any pending changes. +!!! + +`EDB_CURSOR_WITHOUT_XACT_BLK` + +If your application doesn't run properly with the extra commits added by `EDB_COMMIT_AFTER_CURSOR`, you can try setting `EDB_ATTR_HOLD_CURSOR_ACTION` to `EDB_CURSOR_WITHOUT_XACT_BLK`. With this action, the OCL doesn't begin a new transaction chain. If you create a `WITH HOLD` cursor immediately after committing or rolling back a transaction, the cursor is created in its own transaction, the database server commits that transaction, and the cursor persists. + +You might still experience errors if the cursor declaration isn't the first statement in a transaction. If you execute some other statement before declaring the cursor, the `WITH HOLD` cursor is created in a transaction block and can be rolled back if an error occurs or if your application calls `OCITransRollback()`. + +You can set the `EDB_HOLD_CURSOR_ACTION` on the server level (`OCIServer`) or for each statement handle (`OCIStmt`). If the statement attribute is set to a value other than `OCI_DEFAULT`, the value is derived from the statement handle. Otherwise, if the statement attribute is set to `OCI_DEFAULT`, the value is taken from the server handle. So you can define a server-wide default action by setting the attribute in the server handle and leaving the attribute set to `OCI_DEFAULT` in the statement handles. You can use different values for each statement handle or server handle as you see fit. + +### EDB_ATTR_STMT_LVL_TX + +Unless otherwise instructed, the OCL connector rolls back the current transaction whenever the server reports an error. You can override the automatic `ROLLBACK` with the `edb_stmt_level_tx` parameter, which preserves modifications in a transaction, even if one or more statements raise an error in the transaction. + +You can use the `OCIServer` attribute with `OCIAttrSet()` and `OCIAttrGet()` to enable or disable `EDB_ATTR_STMT_LEVEL_TX`. By default, `edb_stmt_level_tx` is disabled. To enable `edb_stmt_level_tx`, the client application must call `OCIAttrSet()`: + +```c +OCIServer* server = myServer; +ub1 enabled = 1; + +OCIAttrSet(server, + OCI_HTYPE_SERVER, + &enabled, + sizeof(enabled), + EDB_ATTR_STMT_LEVEL_TX, + err); +``` + +To disable `edb_stmt_level_tx`: + +```c +OCIServer* server = myServer; +ub1 enabled = 0; + +OCIAttrSet(server, + OCI_HTYPE_SERVER, + &enabled, + sizeof(enabled), + EDB_ATTR_STMT_LEVEL_TX, + err); +``` + +## Bind, define, and describe functions + +| Function | Description | +| ----------------------- | ------------------------------------------------- | +| OCIBindByName | Bind by name. | +| OCIBindByPos | Bind by position. | +| OCIBindDynamic | Set additional attributes after bind. | +| OCIBindArrayOfStruct | Bind an array of structures for bulk operations. | +| OCIDefineArrayOfStruct | Specify the attributes of an array. | +| OCIDefineByPos | Define an output variable association. | +| OCIDefineDynamic | Set additional attributes for define. | +| OCIDescribeAny | Describe existing schema objects. | +| OCIStmtGetBindInfo | Get bind and indicator variable names and handle. | +| OCIUserCallbackRegister | Define a user-defined callback. | + +## Statement functions + +| Function | Description | +| --------------- | --------------------------------- | +| OCIStmtExecute | Execute a prepared SQL statement. | +| OCIStmtFetch | Fetch rows of data (deprecated). | +| OCIStmtFetch2 | Fetch rows of data. | +| OCIStmtPrepare | Prepare a SQL statement. | +| OCIStmtPrepare2 | Prepare a SQL statement. | +| OCIStmtRelease | Release a statement handle. | + +## Transaction functions + +| Function | Description | +| ---------------- | ------------------------ | +| OCITransCommit | Commit a transaction. | +| OCITransRollback | Roll back a transaction. | + +## XA functions + +| Function | Description | +| --------- | ------------------------------- | +| xaoEnv | Return OCL environment handle. | +| xaoSvcCtx | Return OCL service context. | + +### xaoSvcCtx + +To use the `xaoSvcCtx` function, provide extensions in the `xaoSvcCtx` or `xa_open` connection string format as follows: + +`Oracle_XA{+ ...}` + +Where `required_fields` are the following: + +`HostName=host_ip_address` specifies the IP address of the EDB Postgres Advanced Server database. + +`PortNumber=host_port_number` specifies the port number on which EDB Postgres Advanced Server is running. + +`SqlNet=dbname` specifies the database name. + +`Acc=P/username/password` specifies the database username and password. You can omit the password. To do so, specify the field as `Acc=P/username/`. + +`AppName=app_id` specifies a number that identifies the application. + +The following is an example of the connection string: + +```text +Oracle_XA+HostName=192.168.1.1+PortNumber=1533+SqlNet=XE+Acc=P/user/password+AppName=1234 +``` + +## Date and datetime functions + +| Function | Description | +| ---------------------------- | ----------------------------------------------------------------------------------------------------------------- | +| OCIDateAddDays | Add or subtract a number of days. | +| OCIDateAddMonths | Add or subtract a number of months. | +| OCIDateAssign | Assign a date. | +| OCIDateCheck | Check if the given date is valid. | +| OCIDateCompare | Compare two dates. | +| OCIDateDaysBetween | Find the number of days between two dates. | +| OCIDateFromText | Convert a string to a date. | +| OCIDateGetDate | Get the date portion of a date. | +| OCIDateGetTime | Get the time portion of a date. | +| OCIDateLastDay | Get the date of the last day of the month. | +| OCIDateNextDay | Get the date of the next day. | +| OCIDateSetDate | Set the date portion of a date. | +| OCIDateSetTime | Set the time portion of a date. | +| OCIDateSysDate | Get the current system date and time. | +| OCIDateToText | Convert a date to a string. | +| OCIDateTimeAssign | Perform datetime assignment. | +| OCIDateTimeCheck | Check if the date is valid. | +| OCIDateTimeCompare | Compare two datetime values. | +| OCIDateTimeConstruct | Construct a datetime descriptor. | +| OCIDateTimeConvert | Convert one datetime type to another. | +| OCIDateTimeFromArray | Convert an array of size `OCI_DT_ARRAYLEN` to an `OCIDateTime` descriptor. | +| OCIDateTimeFromText | Convert the given string to Oracle datetime type in the `OCIDateTime` descriptor according to the specified format. | +| OCIDateTimeGetDate | Get the date portion of a datetime value. | +| OCIDateTimeGetTime | Get the time portion of a datetime value. | +| OCIDateTimeGetTimeZoneName | Get the time zone name portion of a datetime value. | +| OCIDateTimeGetTimeZoneOffset | Get the time zone (hour, minute) portion of a datetime value. | +| OCIDateTimeSubtract | Take two datetime values as input and return their difference as an interval. | +| OCIDateTimeSysTimeStamp | Get the system current date and time as a timestamp with time zone. | +| OCIDateTimeToArray | Convert an `OCIDateTime` descriptor to an array. | +| OCIDateTimeToText | Convert the given date to a string according to the specified format. | + +## Interval functions + +| Function | Description | +| ----------------------- | -------------------------------------------------------------------------------------------- | +| OCIIntervalAdd | Add two interval values. | +| OCIIntervalAssign | Copy one interval value into another interval value. | +| OCIIntervalCompare | Compare two interval values. | +| OCIIntervalGetDaySecond | Extract days, hours, minutes, seconds and fractional seconds from an interval. | +| OCIIntervalSetDaySecond | Modify days, hours, minutes, seconds and fractional seconds in an interval. | +| OCIIntervalGetYearMonth | Extract year and month values from an interval. | +| OCIIntervalSetYearMonth | Modify year and month values in an interval. | +| OCIIntervalDivide | Divide `OCIInterval` values by `OCINumber` values. | +| OCIIntervalMultiply | Multiply `OCIInterval` values by `OCINumber` values. | +| OCIIntervalSubtract | Subtract one interval value from another interval value. | +| OCIIntervalToText | Extrapolate a character string from an interval. | +| OCIIntervalCheck | Verify the validity of an interval value. | +| OCIIntervalToNumber | Convert an `OCIInterval` value into a `OCINumber` value. | +| OCIIntervalFromNumber | Convert a `OCINumber` value into an `OCIInterval` value. | +| OCIDateTimeIntervalAdd | Add an `OCIInterval` value to an `OCIDatetime` value, resulting in an `OCIDatetime` value. | +| OCIDateTimeIntervalSub | Subtract an `OCIInterval` value from an `OCIDatetime` value, resulting in an `OCIDatetime` value. | +| OCIIntervalFromText | Convert a text string into an interval. | +| OCIIntervalFromTZ | Convert a time zone specification into an interval value. | + +## Number functions + +| Function | Description | +| -------------------- | ------------------------------------------------------------ | +| OCINumberAbs | Compute the absolute value. | +| OCINumberAdd | Adds NUMBERs. | +| OCINumberArcCos | Compute the arc cosine. | +| OCINumberArcSin | Compute the arc sine. | +| OCINumberArcTan | Compute the arc tangent. | +| OCINumberArcTan2 | Compute the arc tangent of two NUMBERs. | +| OCINumberAssign | Assign one NUMBER to another. | +| OCINumberCeil | Compute the ceiling of NUMBER. | +| OCINumberCmp | Compare NUMBERs. | +| OCINumberCos | Compute the cosine. | +| OCINumberDec | Decrement a NUMBER. | +| OCINumberDiv | Divide two NUMBERs. | +| OCINumberExp | Raise e to the specified NUMBER power. | +| OCINumberFloor | Compute the floor of a NUMBER. | +| OCINumberFromInt | Convert an integer to an Oracle NUMBER. | +| OCINumberFromReal | Convert a real to an Oracle NUMBER. | +| OCINumberFromText | Convert a string to an Oracle NUMBER. | +| OCINumberHypCos | Compute the hyperbolic cosine. | +| OCINumberHypSin | Compute the hyperbolic sine. | +| OCINumberHypTan | Compute the hyperbolic tangent. | +| OCINumberInc | Increment a NUMBER. | +| OCINumberIntPower | Raise a given base to an integer power. | +| OCINumberIsInt | Test if a NUMBER is an integer. | +| OCINumberIsZero | Test if a NUMBER is zero. | +| OCINumberLn | Compute the natural logarithm. | +| OCINumberLog | Compute the logarithm to an arbitrary base. | +| OCINumberMod | Modulo division. | +| OCINumberMul | Multiply NUMBERs. | +| OCINumberNeg | Negate a NUMBER. | +| OCINumberPower | Exponentiation to base e. | +| OCINumberPrec | Round a NUMBER to a specified number of decimal places. | +| OCINumberRound | Round a NUMBER to a specified decimal place. | +| OCINumberSetPi | Initialize a NUMBER to Pi. | +| OCINumberSetZero | Initialize a NUMBER to zero. | +| OCINumberShift | Multiply by 10, shifting specified number of decimal places. | +| OCINumberSign | Obtain the sign of a NUMBER. | +| OCINumberSin | Compute the sine. | +| OCINumberSqrt | Compute the square root of a NUMBER. | +| OCINumberSub | Subtract NUMBERs. | +| OCINumberTan | Compute the tangent. | +| OCINumberToInt | Convert a NUMBER to an integer. | +| OCINumberToReal | Convert a NUMBER to a real. | +| OCINumberToRealArray | Convert an array of NUMBER to a real array. | +| OCINumberToText | Converts a NUMBER to a string. | +| OCINumberTrunc | Truncate a NUMBER at a specified decimal place. | + +## String functions + +| Function | Description | +| ------------------- | --------------------------------------------- | +| OCIStringAllocSize | Get allocated size of string memory in bytes. | +| OCIStringAssign | Assign string to a string. | +| OCIStringAssignText | Assign text string to a string. | +| OCIStringPtr | Get string pointer. | +| OCIStringResize | Resize string memory. | +| OCIStringSize | Get string size. | + +## Cartridge services and file I/O interface functions + +| Function | Description | +| ---------------- | -------------------------------------- | +| OCIFileClose | Close an open file. | +| OCIFileExists | Test to see if the file exists. | +| OCIFileFlush | Write buffered data to a file. | +| OCIFileGetLength | Get the length of a file. | +| OCIFileInit | Initialize the `OCIFile` package. | +| OCIFileOpen | Open a file. | +| OCIFileRead | Read from a file into a buffer. | +| OCIFileSeek | Change the current position in a file. | +| OCIFileTerm | Terminate the `OCIFile` package. | +| OCIFileWrite | Write buflen bytes into the file. | + +## LOB functions + +| Function | Description | +| ----------------- | -------------------------------------------------- | +| OCILobRead | Return a LOB value (or a portion of a LOB value). | +| OCILOBWriteAppend | Add data to a LOB value. | +| OCILobGetLength | Return the length of a LOB value. | +| OCILobTrim | Trim data from the end of a LOB value. | +| OCILobOpen | Open a LOB value for use by other LOB functions. | +| OCILobClose | Close a LOB value. | + +## Miscellaneous functions + +| Function | Description | +| ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| OCIClientVersion | Return client library version. | +| OCIErrorGet | Return error message. | +| OCIPGErrorGet | Return native error messages reported by libpq or the server. The signature is:

sword OCIPGErrorGet(dvoid \*hndlp, ub4 recordno, OraText \*errcodep,ub4 errbufsiz, OraText \*bufp, ub4 bufsiz, ub4 type) | +| OCIPasswordChange | Change password. | +| OCIPing | Confirm that the connection and server are active. | +| OCIServerVersion | Get the Oracle version string. | + +## Supported data types + +| Function | Description | +| ------------------ | --------------------------------- | +| ANSI_DATE | ANSI date | +| SQLT_AFC | ANSI fixed character | +| SQLT_AVC | ANSI variable character | +| SQLT_BDOUBLE | Binary double | +| SQLT_BIN | Binary data | +| SQLT_BFLOAT | Binary float | +| SQLT_BOL | Boolean | +| SQLT_CHR | Character string | +| SQLT_DAT | Oracle date | +| SQLT_DATE | ANSI date | +| SQLT_FLT | Float | +| SQLT_INT | Integer | +| SQLT_LBI | Long binary | +| SQLT_LNG | Long | +| SQLT_LVB | Longer long binary | +| SQLT_LVC | Longer longs (character) | +| SQLT_NUM | Oracle numeric | +| SQLT_ODT | OCL date type | +| SQLT_STR | Zero-terminated string | +| SQLT_TIMESTAMP | Timestamp | +| SQLT_TIMESTAMP_TZ | Timestamp with time zone | +| SQLT_TIMESTAMP_LTZ | Timestamp with local time zone | +| SQLT_UIN | Unsigned integer | +| SQLT_VBI | VCS format binary | +| SQLT_VCS | Variable character | +| SQLT_VNU | Number with preceding length byte | +| SQLT_VST | OCL string type | diff --git a/product_docs/docs/ocl_connector/17/04_open_client_library/06_ocl_error_codes_reference.mdx b/product_docs/docs/ocl_connector/17/04_open_client_library/06_ocl_error_codes_reference.mdx new file mode 100644 index 00000000000..13360a97423 --- /dev/null +++ b/product_docs/docs/ocl_connector/17/04_open_client_library/06_ocl_error_codes_reference.mdx @@ -0,0 +1,68 @@ +--- +title: "OCL error codes (reference)" + +--- + + + +The following table lists the error code mappings defined by the OCL Connector. When the database server reports an error code or condition (shown in the first or second column), the OCL converts the value to the compatible value displayed in the third column. + +| Error code | Condition name | Oracle error code | +| ---------- | ------------------------------------------------- | ----------------- | +| 42601 | syntax_error | ORA-16945 | +| 42P01 | undefined_table | ORA-00942 | +| 02000 | no_data | ORA-01403 | +| 08000 | connection_exception | ORA-12545 | +| 08003 | connection_does_not_exist | ORA-12545 | +| 08006 | connection_failure | ORA-12545 | +| 08001 | sqlclient_unable_to_establish_sqlconnection | ORA-12545 | +| 08004 | sqlserver_rejected_establishment_of_sqlconnection | ORA-12545 | +| 25000 | invalid_transaction_state | ORA-01453 | +| 08007 | transaction_resolution_unknown | ORA-01453 | +| 0A000 | feature_not_supported | ORA-03001 | +| 22012 | division_by_zero | ORA-01476 | +| 2200B | escape_character_conflict | ORA-01424 | +| 22019 | invalid_escape_character | ORA-00911 | +| 2200D | invalid_escape_octet | ORA-01424 | +| 22025 | invalid_escape_sequence | ORA-01424 | +| 22P06 | nonstandard_use_of_escape_character | ORA-01424 | +| 2200C | invalid_use_of_escape_character | ORA-01424 | +| 22004 | null_value_not_allowed | ORA-01400 | +| 23000 | integrity_constraint_violation | ORA-00001 | +| 23505 | unique_violation | ORA-00001 | +| 40P01 | t_r_deadlock_detected | ORA-00060 | +| 42701 | duplicate_column | ORA-01430 | +| 53000 | insufficient_resources | ORA-01659 | +| 53100 | disk_full | ORA-01659 | +| 53200 | out_of_memory | ORA-82100 | +| 42P07 | duplicate_table | ORA-00955 | +| 21000 | cardinality_violation | ORA-01427 | +| 22003 | numeric_value_out_of_range | ORA-01426 | +| 22P02 | invalid_text_representation | ORA-01858 | +| 28000 | invalid_authorization_specification | ORA-01017 | +| 28P01 | invalid_password | ORA-01017 | +| 2200F | zero_length_character_string | ORA-01425 | +| 42704 | undefined_object | ORA-01418 | +| 2BP01 | dependent_objects_still_exist | ORA-02429 | +| 22027 | trim_error | ORA-30001 | +| 22001 | string_data_right_truncation | ORA-01401 | +| 22002 | null_value_no_indicator_parameter | ORA-01405 | +| 22008 | datetime_field_overflow | ORA-01800 | +| 44000 | with_check_option_violation | ORA-01402 | +| 01007 | warning_privilege_not_granted | ORA-00000 | +| 01006 | warning_privilege_not_revoked | ORA-00000 | +| 02001 | no_additional_dynamic_result_sets_returned | ORA-00000 | +| 03000 | sql_statement_not_yet_complete | ORA-00000 | +| 08P01 | protocol_violation | ORA-00000 | +| 23001 | restrict_violation | ORA-00000 | +| 23502 | not_null_violation | ORA-00000 | +| 23505 | foreign_key_violation | ORA-00000 | +| 23514 | check_violation | ORA-00000 | +| 24000 | invalid_cursor_state | ORA-01001 | +| 26000 | invalid_sql_statement_name | ORA-00000 | +| 42830 | invalid_foreign_key | ORA-00000 | +| 55006 | object_in_use | ORA-00000 | +| 55P03 | lock_not_available | ORA-00054 | +| 72000 | snapshot_too_old | ORA-01555 | + +For more information about Postgres error codes, see the [PostgreSQL core documentation](https://www.postgresql.org/docs/12/static/errcodes-appendix.html). diff --git a/product_docs/docs/ocl_connector/17/04_open_client_library/07_multithreading_support.mdx b/product_docs/docs/ocl_connector/17/04_open_client_library/07_multithreading_support.mdx new file mode 100644 index 00000000000..79e26a3b7b7 --- /dev/null +++ b/product_docs/docs/ocl_connector/17/04_open_client_library/07_multithreading_support.mdx @@ -0,0 +1,25 @@ +--- +title: "Multithreading support" + +--- + + + +OCL is supported in a multithreaded environment. You can enable and use multithreading in a multithreaded environment by making an `OCIEnvNlsCreate()` call with `OCI_THREADED` as the value of the mode parameter. + +```c +retCode = OCIEnvNlsCreate( &envp, + OCI_THREADED, + NULL, + NULL, + NULL, + NULL, + 0, + NULL, + 0, + 0 ); +``` + +All subsequent calls to `OCIEnvNlsCreate()` must also be made with `OCI_THREADED`. + +OCI library manages mutexes for the application for each environment handle if a multithreaded application is running on a thread-safe operating system. diff --git a/product_docs/docs/ocl_connector/17/04_open_client_library/08_otl_support.mdx b/product_docs/docs/ocl_connector/17/04_open_client_library/08_otl_support.mdx new file mode 100644 index 00000000000..5b5a1880ae4 --- /dev/null +++ b/product_docs/docs/ocl_connector/17/04_open_client_library/08_otl_support.mdx @@ -0,0 +1,222 @@ +--- +title: "OTL support" + +--- + + + +Oracle Template Library (OTL) is a C++ library for database access. It consists of a single header file. To know more about OTL, see the [Oracle, Odbc and DB2-CLI Template Library Programmer's Guide](http://otl.sourceforge.net/). + +## OTL certification + +The EDB OCL Connector, version 13.1.4.2, is certified with OTL 4.0. To use OTL-supported data types and for other OTL-specific behavior, define the OTL environment variable (the value isn't important) on the shell before running an OTL-based app. For example, you can export `OTL=TRUE` for conditional execution of scenarios that are related to OTL. + +EDB OCL Connector is certified with the following OTL features: + +- Connect, disconnect, commit, and roll back using `otl_connect`. +- Constant SQL statements using the static function `otl_cursor::direct_exec`. (A SQL statement is constant if it doesn't have any bind variables.) It includes most DDL statements like `CREATE TABLE` and `CREATE PROCEDURE/FUNCTION`. +- SQL statements with bind variable using `otl_stream class`. It includes most DML statements like `SELECT`, `UPDATE`, `DELETE`, `INSERT`, and `PROCEDURE/FUNCTION` calls. +- Date/Time data types using `otl_datetime`. +- Raw/Long Raw data types using `otl_long_string`. +- Ref cursors using `otl_refcur_stream`. + +## Connect and log in + +This example initializes OCL and connects to a database using a `tnsnames.ora`-based connection string: + +```c +otl_connect db; +otl_connect::otl_initialize(); + +db.rlogon("enterprisedb/edb@EDBX"); +if(db.connected) + cout<<"Connected to Database"<> strData >> dtData; + + cout << "Retrieved Value: " << data << endl; + cout << "Retrieved Value: " << data.month << "/" + << data.day << "/" << data.year << " " << data.hour + << ":" << data.minute << ":" << data.second << endl; +} +``` + +## UPDATE + +This example uses bind parameters in an `UPDATE` statement: + +```c +char* updatestmt = "UPDATE testtable SET c1=:c1 " + "WHERE c1=:c2"; + +char whereValue[50] = "test_data123"; +char data[50] = "otl test"; +otl_stream otlCur(80, updatestmt, db); +otlCur.set_commit(0); +otlCur << data << whereValue; +``` + +## Stored procedure + +This example creates a stored procedure using `otl_cursor::direct_exec` and then calls it using `otl_stream`: + +```c +otl_cursor::direct_exec( + db, + "CREATE OR REPLACE PROCEDURE my_procOneIntOut " + " (A IN NUMBER, B OUT NUMBER)" + "IS " + "BEGIN " + " B := A;" + "END;"); + +otl_stream otlCur( + 1, + "begin my_procOneIntOut(:A, :B);end;", + db); +otlCur.set_commit(0); + +int a = 10; +otlCur << a; + +int b; +otlCur >> b; +cout << "B: " << b << endl; +``` + +## Function + +This example creates a function using `otl_cursor::direct_exec` and then calls it using `otl_stream`: + +!!! Note + This example is using the `emp` table in the `edb` sample database. + +```c +otl_cursor::direct_exec( + db, + "CREATE OR REPLACE FUNCTION get_no_int(e_name character " + "varying(10)) " + "RETURNS int AS $$ " + "DECLARE retval int; " + + "BEGIN " + "SELECT empno FROM emp WHERE ename = e_name INTO retval; " + "RETURN retval; " + "END; " + + "$$ LANGUAGE plpgsql;"); + +char ename[50] = "SCOTT"; +otl_stream otlCur( + 1, + "begin " + " :rc := get_no_int(:c1);" + "end;", + db); +otlCur << ename; + +int eno; +otlCur >> eno; + +cout << "Retrieved Value: " << eno << endl; +``` + +## REF CURSOR + +This example creates a package with a procedure that returns three ref cursors as `OUT` parameters and then calls it. + +!!! Note + This example is using the `emp` table in the `edb` sample database. + +```c +otl_cursor::direct_exec( + db, + "CREATE OR REPLACE PACKAGE ref_test + IS TYPE p_cursor IS REF CURSOR; + PROCEDURE getdata(empc OUT p_cursor, + salc OUT p_cursor, + comc OUT p_cursor); + END ref_test; + " +); + +otl_cursor::direct_exec( + db, + "CREATE OR REPLACE PACKAGE BODY ref_test \ + IS \ + PROCEDURE getdata(empc OUT p_cursor, salc OUT p_cursor, comc OUT p_cursor) IS \ + BEGIN \ + open empc for select empno, ename from EMP; \ + open salc for select ename, sal from EMP; \ + open comc for select ename, comm from EMP; \ + END; \ + END ref_test;"); + +otl_stream otlCur(1, + "BEGIN \ + ref_test.getdata(:cur1, :cur2, :cur3); \ + END;", + db); +otlCur.set_commit(0); + +otl_refcur_stream + s1; // reference cursor streams for reading rows. +otl_refcur_stream + s2; // reference cursor streams for reading rows. +otl_refcur_stream + s3; // reference cursor streams for reading rows. + +otlCur >> s1; +otlCur >> s2; +otlCur >> s3; + +int e_no; +char name[11]; +double sal; +double comm; + +cout << "=====> Reading :cur1..." << endl; +while (!s1.eof()) { // while not end-of-data + s1 >> e_no >> name; + cout << "e_no=" << e_no << "\tname: " << name << endl; +} + +cout << "=====> Reading :cur2..." << endl; +while (!s2.eof()) { // while not end-of-data + s2 >> name >> sal; + cout << "name=" << name << "\tsalary: " << sal << endl; +} + +cout << "=====> Reading :cur3..." << endl; +while (!s3.eof()) { // while not end-of-data + s3 >> name >> comm; + cout << "name=" << name << "\tcommission: " << comm + << endl; +} + +s1.close(); +s2.close(); +s3.close(); +``` diff --git a/product_docs/docs/ocl_connector/17/04_open_client_library/index.mdx b/product_docs/docs/ocl_connector/17/04_open_client_library/index.mdx new file mode 100644 index 00000000000..abbf377bc34 --- /dev/null +++ b/product_docs/docs/ocl_connector/17/04_open_client_library/index.mdx @@ -0,0 +1,20 @@ +--- +title: "Open Client Library" + +--- + + + +The Open Client Library provides application interoperability with the Oracle Call Interface. An application that was formerly locked in can now work with either an EDB Postgres Advanced Server or an Oracle database with minimal to no changes to the application code. + +The following diagram compares the Open Client Library and Oracle Call Interface application stacks. + +![Comparison with Oracle Call Interface](../images/oracle_call_interface.png) + +The EDB implementation of the Open Client Library is written in C. + +
+ +installing_and_configuring_the_ocl_connector forming_a_connection_string compiling_and_linking_a_program ref_cursor_support ocl_function_reference ocl_error_codes_reference multithreading_support otl_support + +
diff --git a/product_docs/docs/ocl_connector/17/05_generating_the_ocl_trace.mdx b/product_docs/docs/ocl_connector/17/05_generating_the_ocl_trace.mdx new file mode 100644 index 00000000000..b6ef4d4b8da --- /dev/null +++ b/product_docs/docs/ocl_connector/17/05_generating_the_ocl_trace.mdx @@ -0,0 +1,23 @@ +--- +title: "Generating the OCL trace" + +--- + + + +The OCL tracing option logs direct communication (queries, updates, and so on) with the backend in the specified `OCI_DEBUG_LOG file`. It also logs the functions/APIs that were invoked. The trace files are generated in the default working directory (`oci_log_file_name`). If you append the path with a file name (`directory path/oci_log_file_name`), then the trace files are generated at that specific location. + +A trace file is generated for each connection in text-file (readable) format. + +!!! Note + OCL tracing is disabled by default. + +To generate the OCL trace: + +1. Enable the EDB client-side tracing for OCL. You can enable the OCL tracing by setting these environment variables: + + - `export OCI_DEBUG_LEVEL=4` + + - `export OCI_DEBUG_LOG=oci_log_file` + +2. After you export the environment variables, run the application. The OCL trace files are generated in the specified directory. diff --git a/product_docs/docs/ocl_connector/17/06_using_ssl.mdx b/product_docs/docs/ocl_connector/17/06_using_ssl.mdx new file mode 100644 index 00000000000..24810e0bada --- /dev/null +++ b/product_docs/docs/ocl_connector/17/06_using_ssl.mdx @@ -0,0 +1,41 @@ +--- +title: "Using SSL" +legacyRedirects: + - "/edb-docs/d/edb-postgres-ocl-connector/user-guides/ocl-guide/13.1.4.2/security_and_encryption.html" + +--- + + + +EDB Postgres Advanced Server provides native support for using SSL connections to encrypt client/server communications for increased security. In OCL, it's controlled by setting the `sslmode` parameter to `verify-full` or `verify-ca` and providing the system with a root certificate to verify against. + +## Steps of SSL configuration + +1. Configure the server and client-side certificates. For detailed information about configuring SSL client and server-side certificates, refer to the [PostgreSQL SSL documentation](https://www.postgresql.org/docs/12/libpq-ssl.html). + +2. Enable the SSL OCL connection. In an OCL client application, you can enable SSL mode by setting the `EDB_ATTR_SSL` attribute in `Session`: + +```c +char* sslmode = "verify-full"; +retValue = OCIAttrSet((dvoid*)authp, + (ub4)OCI_HTYPE_SESSION, + (dvoid*)sslmode, + (ub4)strlen((char*)sslmode), + (ub4)EDB_ATTR_SSL, + errhp); +``` + +!!! Note + `EDB_ATTR_SSL` is defined in the `edboci.h` header file available in the installation directory. + +3. After setting the SSL attribute, you can use the `OCILogon` function to create a connection: + +```c +OCILogon(pEnv,pError,&pSvc,(OraText*)pUsername,ub4)UsernameLen, + (OraText*)pPassword,(ub4)PasswordLen, + (OraText*)pDatabase,(ub4)DatabaseLen); +``` + +Once the server is authenticated, then the client is ready to pass sensitive data. + +For more information about the supported SSL mode options, see the [PostgreSQL SSL documentation](https://www.postgresql.org/docs/13/libpq-ssl.html#LIBPQ-SSL-SSLMODE-STATEMENTS). diff --git a/product_docs/docs/ocl_connector/17/07_scram_compatibility.mdx b/product_docs/docs/ocl_connector/17/07_scram_compatibility.mdx new file mode 100644 index 00000000000..76b6fb8ed5d --- /dev/null +++ b/product_docs/docs/ocl_connector/17/07_scram_compatibility.mdx @@ -0,0 +1,8 @@ +--- +title: "Scram compatibility" + +--- + + + +The EDB OCL driver provides SCRAM-SHA-256 support for EDB Postgres Advanced Server version 11 and later. This support is available in EDB OCL 11.0.1 release and later. diff --git a/product_docs/docs/ocl_connector/17/images/ocl_installation_complete.png b/product_docs/docs/ocl_connector/17/images/ocl_installation_complete.png new file mode 100755 index 00000000000..18d535b6613 --- /dev/null +++ b/product_docs/docs/ocl_connector/17/images/ocl_installation_complete.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:67fbe6582167a1866bdc942f3fa4b236d317b9449ae379295a5ae4099cf9bc66 +size 271262 diff --git a/product_docs/docs/ocl_connector/17/images/ocl_installation_dialog.png b/product_docs/docs/ocl_connector/17/images/ocl_installation_dialog.png new file mode 100755 index 00000000000..f2c1ae42a67 --- /dev/null +++ b/product_docs/docs/ocl_connector/17/images/ocl_installation_dialog.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cc1616ae47691ad7f62d9a83ff3a9d29e64764069f8f7fdb8c96519bdd32c0a3 +size 48180 diff --git a/product_docs/docs/ocl_connector/17/images/ocl_installation_wizard.png b/product_docs/docs/ocl_connector/17/images/ocl_installation_wizard.png new file mode 100755 index 00000000000..ac0f8bf3021 --- /dev/null +++ b/product_docs/docs/ocl_connector/17/images/ocl_installation_wizard.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7c58c59f17592bc5ecd2bb856b4d2ecb5bad19041902727531ed0eb39ae93e56 +size 280241 diff --git a/product_docs/docs/ocl_connector/17/images/oracle_call_interface.png b/product_docs/docs/ocl_connector/17/images/oracle_call_interface.png new file mode 100755 index 00000000000..211ceda4b45 --- /dev/null +++ b/product_docs/docs/ocl_connector/17/images/oracle_call_interface.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c18e51dcc8b9ce545d2aaeb93ebcf7e51f95898ee0d408b8502cffcc27cfa193 +size 103652 diff --git a/product_docs/docs/ocl_connector/17/images/ready_to_install.png b/product_docs/docs/ocl_connector/17/images/ready_to_install.png new file mode 100755 index 00000000000..4d2ce00c860 --- /dev/null +++ b/product_docs/docs/ocl_connector/17/images/ready_to_install.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:198309699882c30c62c23f0889a2fc4299350803c6bbde38c34a62be67e878aa +size 43327 diff --git a/product_docs/docs/ocl_connector/17/images/selecting_the_connectors_installer.png b/product_docs/docs/ocl_connector/17/images/selecting_the_connectors_installer.png new file mode 100644 index 00000000000..67355eb32a8 --- /dev/null +++ b/product_docs/docs/ocl_connector/17/images/selecting_the_connectors_installer.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5d4dc68af55433c0c695eed059160505b3ee6c7d25c7d5426f4228109d84042a +size 135650 diff --git a/product_docs/docs/ocl_connector/17/images/starting_stackbuilder_plus.png b/product_docs/docs/ocl_connector/17/images/starting_stackbuilder_plus.png new file mode 100644 index 00000000000..11665300652 --- /dev/null +++ b/product_docs/docs/ocl_connector/17/images/starting_stackbuilder_plus.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ce6bcefb865ca14239fb7e0e2ac5149ed56251cfbc5153869070d039f70857c6 +size 91989 diff --git a/product_docs/docs/ocl_connector/17/index.mdx b/product_docs/docs/ocl_connector/17/index.mdx new file mode 100644 index 00000000000..3c8dcba4dcc --- /dev/null +++ b/product_docs/docs/ocl_connector/17/index.mdx @@ -0,0 +1,21 @@ +--- +title: "EDB OCL Connector" +directoryDefaults: + description: "EDB OCL Connector Version 15.1.0.1 Documentation and release notes." +navigation: +- ocl_rel_notes +- 02_supported_platforms +- 03_libpq_compatibility +- installing +- 04_open_client_library +- 05_generating_the_ocl_trace +- 06_using_ssl +- 07_scram_compatibility +--- + +The EDB OCL Connector provides an API similar to the Oracle Call Interface. You can use EDB's OCL Connector to compile applications that are written to use the Oracle Call Interface to interact with an EDB Postgres Advanced Server database server. + +!!! Note + EDB doesn't support the use of the Open Client Library with Oracle Real Application Clusters (RAC) and Oracle Exadata. These Oracle products aren't evaluated or certified with this EDB product. + + diff --git a/product_docs/docs/ocl_connector/17/installing/index.mdx b/product_docs/docs/ocl_connector/17/installing/index.mdx new file mode 100644 index 00000000000..4b1f1965ad5 --- /dev/null +++ b/product_docs/docs/ocl_connector/17/installing/index.mdx @@ -0,0 +1,66 @@ +--- +navTitle: Installing +title: Installing EDB OCL Connector +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. +# Leaf template: products/edb-ocl-connector/index.njk + +redirects: + - /ocl_connector/16/04_open_client_library/01_installing_and_configuring_the_ocl_connector/ + - /ocl_connector/16/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/ + - /ocl_connector/16/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/11_updating_rpm_install/ + - /ocl_connector/16/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/ibm_power_ppc64le/07_ocl_connector14_rhel8_ppcle/ + - /ocl_connector/16/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/06_ocl_connector14_ubuntu18_deb9_x86/ + +navigation: + - linux_ppc64le + - linux_x86_64 + - linux_arm64 + - windows + - upgrading +--- + +Select a link to access the applicable installation instructions: + +## Linux [x86-64 (amd64)](linux_x86_64) + +### Red Hat Enterprise Linux (RHEL) and derivatives + +- [RHEL 9](linux_x86_64/ocl_rhel_9), [RHEL 8](linux_x86_64/ocl_rhel_8) + +- [Oracle Linux (OL) 9](linux_x86_64/ocl_rhel_9), [Oracle Linux (OL) 8](linux_x86_64/ocl_rhel_8) + +- [Rocky Linux 9](linux_x86_64/ocl_other_linux_9), [Rocky Linux 8](linux_x86_64/ocl_other_linux_8) + +- [AlmaLinux 9](linux_x86_64/ocl_other_linux_9), [AlmaLinux 8](linux_x86_64/ocl_other_linux_8) + +### SUSE Linux Enterprise (SLES) + +- [SLES 15](linux_x86_64/ocl_sles_15) + +### Debian and derivatives + +- [Ubuntu 22.04](linux_x86_64/ocl_ubuntu_22), [Ubuntu 20.04](linux_x86_64/ocl_ubuntu_20) + +- [Debian 12](linux_x86_64/ocl_debian_12), [Debian 11](linux_x86_64/ocl_debian_11) + +## Linux [IBM Power (ppc64le)](linux_ppc64le) + +### Red Hat Enterprise Linux (RHEL) and derivatives + +- [RHEL 9](linux_ppc64le/ocl_rhel_9), [RHEL 8](linux_ppc64le/ocl_rhel_8) + +### SUSE Linux Enterprise (SLES) + +- [SLES 15](linux_ppc64le/ocl_sles_15) + +## Linux [AArch64 (ARM64)](linux_arm64) + +### Debian and derivatives + +- [Debian 12](linux_arm64/ocl_debian_12) + +## Windows + +- [Windows Server 2019](windows) diff --git a/product_docs/docs/ocl_connector/17/installing/linux_arm64/index.mdx b/product_docs/docs/ocl_connector/17/installing/linux_arm64/index.mdx new file mode 100644 index 00000000000..15061e86556 --- /dev/null +++ b/product_docs/docs/ocl_connector/17/installing/linux_arm64/index.mdx @@ -0,0 +1,13 @@ +--- +title: "Installing EDB OCL Connector on Linux AArch64 (ARM64)" +navTitle: "On Linux ARM64" + +navigation: + - ocl_debian_12 +--- + +Operating system-specific install instructions are described in the corresponding documentation: + +### Debian and derivatives + +- [Debian 12](ocl_debian_12) diff --git a/product_docs/docs/ocl_connector/17/installing/linux_arm64/ocl_debian_12.mdx b/product_docs/docs/ocl_connector/17/installing/linux_arm64/ocl_debian_12.mdx new file mode 100644 index 00000000000..32548c1b571 --- /dev/null +++ b/product_docs/docs/ocl_connector/17/installing/linux_arm64/ocl_debian_12.mdx @@ -0,0 +1,47 @@ +--- +navTitle: Debian 12 +title: Installing EDB OCL Connector on Debian 12 arm64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. + +redirects: + - /ocl_connector/16/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/arm64/ocl_deb12_arm +--- + +## Prerequisites + +Before you begin the installation process: + +- Install Postgres on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See: + + - [Installing EDB Postgres Advanced Server](/epas/latest/installing/) + + - [Installing PostgreSQL](https://www.postgresql.org/download/) + +- Set up the EDB repository. + + Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. + + To determine if your repository exists, enter this command: + + `apt-cache search enterprisedb` + + If no output is generated, the repository isn't installed. + + To set up the EDB repository: + + 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads). + + 1. Select the button that provides access to the EDB repository. + + 1. Select the platform and software that you want to download. + + 1. Follow the instructions for setting up the EDB repository. + +## Install the package + +```shell +sudo apt-get -y install edb-oci +sudo apt-get -y install edb-oci-dev +``` diff --git a/product_docs/docs/ocl_connector/17/installing/linux_ppc64le/index.mdx b/product_docs/docs/ocl_connector/17/installing/linux_ppc64le/index.mdx new file mode 100644 index 00000000000..f11f64e7e38 --- /dev/null +++ b/product_docs/docs/ocl_connector/17/installing/linux_ppc64le/index.mdx @@ -0,0 +1,28 @@ +--- +title: "Installing EDB OCL Connector on Linux IBM Power (ppc64le)" +navTitle: "On Linux ppc64le" +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. +# Leaf template: products/edb-ocl-connector/ppc64le_index.njk + +redirects: + - /ocl_connector/latest/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/ibm_power_ppc64le/ + +navigation: + - ocl_rhel_9 + - ocl_rhel_8 + - ocl_sles_15 +--- + +Operating system-specific install instructions are described in the corresponding documentation: + +### Red Hat Enterprise Linux (RHEL) + +- [RHEL 9](ocl_rhel_9) + +- [RHEL 8](ocl_rhel_8) + +### SUSE Linux Enterprise (SLES) + +- [SLES 15](ocl_sles_15) diff --git a/product_docs/docs/ocl_connector/17/installing/linux_ppc64le/ocl_rhel_8.mdx b/product_docs/docs/ocl_connector/17/installing/linux_ppc64le/ocl_rhel_8.mdx new file mode 100644 index 00000000000..2df40e9aeb9 --- /dev/null +++ b/product_docs/docs/ocl_connector/17/installing/linux_ppc64le/ocl_rhel_8.mdx @@ -0,0 +1,56 @@ +--- +navTitle: RHEL 8 +title: Installing EDB OCL Connector on RHEL 8 ppc64le +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. + +redirects: + - /ocl_connector/16/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/ibm_power_ppc64le/ocl_rhel8_ppcle +--- + +## Prerequisites + +Before you begin the installation process: + +- Install Postgres on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See: + + - [Installing EDB Postgres Advanced Server](/epas/latest/installing/) + + - [Installing PostgreSQL](https://www.postgresql.org/download/) + +- Set up the EDB repository. + + Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. + + To determine if your repository exists, enter this command: + + `dnf repolist | grep enterprisedb` + + If no output is generated, the repository isn't installed. + + To set up the EDB repository: + + 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads). + + 1. Select the button that provides access to the EDB repository. + + 1. Select the platform and software that you want to download. + + 1. Follow the instructions for setting up the EDB repository. + +- Install the EPEL repository: + ```shell + sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm + ``` +- Refresh the cache: + ```shell + sudo dnf makecache + ``` + +## Install the package + +```shell +sudo dnf -y install edb-oci +sudo dnf -y install edb-oci-devel +``` diff --git a/product_docs/docs/ocl_connector/17/installing/linux_ppc64le/ocl_rhel_9.mdx b/product_docs/docs/ocl_connector/17/installing/linux_ppc64le/ocl_rhel_9.mdx new file mode 100644 index 00000000000..41999caf1d8 --- /dev/null +++ b/product_docs/docs/ocl_connector/17/installing/linux_ppc64le/ocl_rhel_9.mdx @@ -0,0 +1,56 @@ +--- +navTitle: RHEL 9 +title: Installing EDB OCL Connector on RHEL 9 ppc64le +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. + +redirects: + - /ocl_connector/16/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/ibm_power_ppc64le/ocl_rhel9_ppcle +--- + +## Prerequisites + +Before you begin the installation process: + +- Install Postgres on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See: + + - [Installing EDB Postgres Advanced Server](/epas/latest/installing/) + + - [Installing PostgreSQL](https://www.postgresql.org/download/) + +- Set up the EDB repository. + + Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. + + To determine if your repository exists, enter this command: + + `dnf repolist | grep enterprisedb` + + If no output is generated, the repository isn't installed. + + To set up the EDB repository: + + 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads). + + 1. Select the button that provides access to the EDB repository. + + 1. Select the platform and software that you want to download. + + 1. Follow the instructions for setting up the EDB repository. + +- Install the EPEL repository: + ```shell + sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm + ``` +- Refresh the cache: + ```shell + sudo dnf makecache + ``` + +## Install the package + +```shell +sudo dnf -y install edb-oci +sudo dnf -y install edb-oci-devel +``` diff --git a/product_docs/docs/ocl_connector/17/installing/linux_ppc64le/ocl_sles_15.mdx b/product_docs/docs/ocl_connector/17/installing/linux_ppc64le/ocl_sles_15.mdx new file mode 100644 index 00000000000..116d2d1ef98 --- /dev/null +++ b/product_docs/docs/ocl_connector/17/installing/linux_ppc64le/ocl_sles_15.mdx @@ -0,0 +1,57 @@ +--- +navTitle: SLES 15 +title: Installing EDB OCL Connector on SLES 15 ppc64le +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. + +redirects: + - /ocl_connector/16/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/ibm_power_ppc64le/ocl_sles15_ppcle +--- + +## Prerequisites + +Before you begin the installation process: + +- Install Postgres on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See: + + - [Installing EDB Postgres Advanced Server](/epas/latest/installing/) + + - [Installing PostgreSQL](https://www.postgresql.org/download/) + +- Set up the EDB repository. + + Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. + + To determine if your repository exists, enter this command: + + `zypper lr -E | grep enterprisedb` + + If no output is generated, the repository isn't installed. + + To set up the EDB repository: + + 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads). + + 1. Select the button that provides access to the EDB repository. + + 1. Select the platform and software that you want to download. + + 1. Follow the instructions for setting up the EDB repository. + +- Activate the required SUSE module: + ```shell + sudo SUSEConnect -p PackageHub/15.4/ppc64le + + ``` +- Refresh the metadata: + ```shell + sudo zypper refresh + ``` + +## Install the package + +```shell +sudo zypper -n install edb-oci +sudo zypper -n install edb-oci-devel +``` diff --git a/product_docs/docs/ocl_connector/17/installing/linux_x86_64/index.mdx b/product_docs/docs/ocl_connector/17/installing/linux_x86_64/index.mdx new file mode 100644 index 00000000000..a4cba53524f --- /dev/null +++ b/product_docs/docs/ocl_connector/17/installing/linux_x86_64/index.mdx @@ -0,0 +1,56 @@ +--- +title: "Installing EDB OCL Connector on Linux x86 (amd64)" +navTitle: "On Linux x86" +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. +# Leaf template: products/edb-ocl-connector/x86_64_index.njk + +redirects: + - /ocl_connector/latest/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ + +navigation: + - ocl_rhel_9 + - ocl_rhel_8 + - ocl_other_linux_9 + - ocl_other_linux_8 + - ocl_sles_15 + - ocl_ubuntu_22 + - ocl_ubuntu_20 + - ocl_debian_12 + - ocl_debian_11 +--- + +Operating system-specific install instructions are described in the corresponding documentation: + +### Red Hat Enterprise Linux (RHEL) and derivatives + +- [RHEL 9](ocl_rhel_9) + +- [RHEL 8](ocl_rhel_8) + +- [Oracle Linux (OL) 9](ocl_rhel_9) + +- [Oracle Linux (OL) 8](ocl_rhel_8) + +- [Rocky Linux 9](ocl_other_linux_9) + +- [Rocky Linux 8](ocl_other_linux_8) + +- [AlmaLinux 9](ocl_other_linux_9) + +- [AlmaLinux 8](ocl_other_linux_8) + +### SUSE Linux Enterprise (SLES) + +- [SLES 15](ocl_sles_15) + +### Debian and derivatives + +- [Ubuntu 22.04](ocl_ubuntu_22) + +- [Ubuntu 20.04](ocl_ubuntu_20) + +- [Debian 12](ocl_debian_12) + +- [Debian 11](ocl_debian_11) diff --git a/product_docs/docs/ocl_connector/17/installing/linux_x86_64/ocl_debian_11.mdx b/product_docs/docs/ocl_connector/17/installing/linux_x86_64/ocl_debian_11.mdx new file mode 100644 index 00000000000..9f10d8a9bd0 --- /dev/null +++ b/product_docs/docs/ocl_connector/17/installing/linux_x86_64/ocl_debian_11.mdx @@ -0,0 +1,47 @@ +--- +navTitle: Debian 11 +title: Installing EDB OCL Connector on Debian 11 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. + +redirects: + - /ocl_connector/16/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_deb11_x86 +--- + +## Prerequisites + +Before you begin the installation process: + +- Install Postgres on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See: + + - [Installing EDB Postgres Advanced Server](/epas/latest/installing/) + + - [Installing PostgreSQL](https://www.postgresql.org/download/) + +- Set up the EDB repository. + + Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. + + To determine if your repository exists, enter this command: + + `apt-cache search enterprisedb` + + If no output is generated, the repository isn't installed. + + To set up the EDB repository: + + 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads). + + 1. Select the button that provides access to the EDB repository. + + 1. Select the platform and software that you want to download. + + 1. Follow the instructions for setting up the EDB repository. + +## Install the package + +```shell +sudo apt-get -y install edb-oci +sudo apt-get -y install edb-oci-dev +``` diff --git a/product_docs/docs/ocl_connector/17/installing/linux_x86_64/ocl_debian_12.mdx b/product_docs/docs/ocl_connector/17/installing/linux_x86_64/ocl_debian_12.mdx new file mode 100644 index 00000000000..2e0d000d4ca --- /dev/null +++ b/product_docs/docs/ocl_connector/17/installing/linux_x86_64/ocl_debian_12.mdx @@ -0,0 +1,47 @@ +--- +navTitle: Debian 12 +title: Installing EDB OCL Connector on Debian 12 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. + +redirects: + - /ocl_connector/16/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_deb12_x86 +--- + +## Prerequisites + +Before you begin the installation process: + +- Install Postgres on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See: + + - [Installing EDB Postgres Advanced Server](/epas/latest/installing/) + + - [Installing PostgreSQL](https://www.postgresql.org/download/) + +- Set up the EDB repository. + + Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. + + To determine if your repository exists, enter this command: + + `apt-cache search enterprisedb` + + If no output is generated, the repository isn't installed. + + To set up the EDB repository: + + 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads). + + 1. Select the button that provides access to the EDB repository. + + 1. Select the platform and software that you want to download. + + 1. Follow the instructions for setting up the EDB repository. + +## Install the package + +```shell +sudo apt-get -y install edb-oci +sudo apt-get -y install edb-oci-dev +``` diff --git a/product_docs/docs/ocl_connector/17/installing/linux_x86_64/ocl_other_linux_8.mdx b/product_docs/docs/ocl_connector/17/installing/linux_x86_64/ocl_other_linux_8.mdx new file mode 100644 index 00000000000..ecc4a960858 --- /dev/null +++ b/product_docs/docs/ocl_connector/17/installing/linux_x86_64/ocl_other_linux_8.mdx @@ -0,0 +1,58 @@ +--- +navTitle: AlmaLinux 8 or Rocky Linux 8 +title: Installing EDB OCL Connector on AlmaLinux 8 or Rocky Linux 8 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. + +redirects: + - /ocl_connector/16/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_other_linux8_x86 +--- + +## Prerequisites + +Before you begin the installation process: + +- Install Postgres on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See: + + - [Installing EDB Postgres Advanced Server](/epas/latest/installing/) + + - [Installing PostgreSQL](https://www.postgresql.org/download/) + +- Set up the EDB repository. + + Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. + + To determine if your repository exists, enter this command: + + `dnf repolist | grep enterprisedb` + + If no output is generated, the repository isn't installed. + + To set up the EDB repository: + + 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads). + + 1. Select the button that provides access to the EDB repository. + + 1. Select the platform and software that you want to download. + + 1. Follow the instructions for setting up the EDB repository. + +- Install the EPEL repository: + + ```shell + sudo dnf -y install epel-release + ``` + +- Enable additional repositories to resolve dependencies: + ```shell + sudo dnf config-manager --set-enabled powertools + ``` + +## Install the package + +```shell +sudo dnf -y install edb-oci +sudo dnf -y install edb-oci-devel +``` diff --git a/product_docs/docs/ocl_connector/17/installing/linux_x86_64/ocl_other_linux_9.mdx b/product_docs/docs/ocl_connector/17/installing/linux_x86_64/ocl_other_linux_9.mdx new file mode 100644 index 00000000000..a303ade238d --- /dev/null +++ b/product_docs/docs/ocl_connector/17/installing/linux_x86_64/ocl_other_linux_9.mdx @@ -0,0 +1,58 @@ +--- +navTitle: AlmaLinux 9 or Rocky Linux 9 +title: Installing EDB OCL Connector on AlmaLinux 9 or Rocky Linux 9 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. + +redirects: + - /ocl_connector/16/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_other_linux9_x86 +--- + +## Prerequisites + +Before you begin the installation process: + +- Install Postgres on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See: + + - [Installing EDB Postgres Advanced Server](/epas/latest/installing/) + + - [Installing PostgreSQL](https://www.postgresql.org/download/) + +- Set up the EDB repository. + + Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. + + To determine if your repository exists, enter this command: + + `dnf repolist | grep enterprisedb` + + If no output is generated, the repository isn't installed. + + To set up the EDB repository: + + 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads). + + 1. Select the button that provides access to the EDB repository. + + 1. Select the platform and software that you want to download. + + 1. Follow the instructions for setting up the EDB repository. + +- Install the EPEL repository: + + ```shell + sudo dnf -y install epel-release + ``` + +- Enable additional repositories to resolve dependencies: + ```shell + sudo dnf config-manager --set-enabled crb + ``` + +## Install the package + +```shell +sudo dnf -y install edb-oci +sudo dnf -y install edb-oci-devel +``` diff --git a/product_docs/docs/ocl_connector/17/installing/linux_x86_64/ocl_rhel_8.mdx b/product_docs/docs/ocl_connector/17/installing/linux_x86_64/ocl_rhel_8.mdx new file mode 100644 index 00000000000..915c757fc3d --- /dev/null +++ b/product_docs/docs/ocl_connector/17/installing/linux_x86_64/ocl_rhel_8.mdx @@ -0,0 +1,52 @@ +--- +navTitle: RHEL 8 or OL 8 +title: Installing EDB OCL Connector on RHEL 8 or OL 8 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. + +redirects: + - /ocl_connector/16/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_rhel8_x86 +--- + +## Prerequisites + +Before you begin the installation process: + +- Install Postgres on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See: + + - [Installing EDB Postgres Advanced Server](/epas/latest/installing/) + + - [Installing PostgreSQL](https://www.postgresql.org/download/) + +- Set up the EDB repository. + + Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. + + To determine if your repository exists, enter this command: + + `dnf repolist | grep enterprisedb` + + If no output is generated, the repository isn't installed. + + To set up the EDB repository: + + 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads). + + 1. Select the button that provides access to the EDB repository. + + 1. Select the platform and software that you want to download. + + 1. Follow the instructions for setting up the EDB repository. + +- Install the EPEL repository: + ```shell + sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm + ``` + +## Install the package + +```shell +sudo dnf -y install edb-oci +sudo dnf -y install edb-oci-devel +``` diff --git a/product_docs/docs/ocl_connector/17/installing/linux_x86_64/ocl_rhel_9.mdx b/product_docs/docs/ocl_connector/17/installing/linux_x86_64/ocl_rhel_9.mdx new file mode 100644 index 00000000000..35742e29644 --- /dev/null +++ b/product_docs/docs/ocl_connector/17/installing/linux_x86_64/ocl_rhel_9.mdx @@ -0,0 +1,52 @@ +--- +navTitle: RHEL 9 or OL 9 +title: Installing EDB OCL Connector on RHEL 9 or OL 9 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. + +redirects: + - /ocl_connector/16/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_rhel9_x86 +--- + +## Prerequisites + +Before you begin the installation process: + +- Install Postgres on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See: + + - [Installing EDB Postgres Advanced Server](/epas/latest/installing/) + + - [Installing PostgreSQL](https://www.postgresql.org/download/) + +- Set up the EDB repository. + + Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. + + To determine if your repository exists, enter this command: + + `dnf repolist | grep enterprisedb` + + If no output is generated, the repository isn't installed. + + To set up the EDB repository: + + 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads). + + 1. Select the button that provides access to the EDB repository. + + 1. Select the platform and software that you want to download. + + 1. Follow the instructions for setting up the EDB repository. + +- Install the EPEL repository: + ```shell + sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm + ``` + +## Install the package + +```shell +sudo dnf -y install edb-oci +sudo dnf -y install edb-oci-devel +``` diff --git a/product_docs/docs/ocl_connector/17/installing/linux_x86_64/ocl_sles_15.mdx b/product_docs/docs/ocl_connector/17/installing/linux_x86_64/ocl_sles_15.mdx new file mode 100644 index 00000000000..b5940ed1e85 --- /dev/null +++ b/product_docs/docs/ocl_connector/17/installing/linux_x86_64/ocl_sles_15.mdx @@ -0,0 +1,57 @@ +--- +navTitle: SLES 15 +title: Installing EDB OCL Connector on SLES 15 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. + +redirects: + - /ocl_connector/16/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_sles15_x86 +--- + +## Prerequisites + +Before you begin the installation process: + +- Install Postgres on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See: + + - [Installing EDB Postgres Advanced Server](/epas/latest/installing/) + + - [Installing PostgreSQL](https://www.postgresql.org/download/) + +- Set up the EDB repository. + + Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. + + To determine if your repository exists, enter this command: + + `zypper lr -E | grep enterprisedb` + + If no output is generated, the repository isn't installed. + + To set up the EDB repository: + + 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads). + + 1. Select the button that provides access to the EDB repository. + + 1. Select the platform and software that you want to download. + + 1. Follow the instructions for setting up the EDB repository. + +- Activate the required SUSE module: + ```shell + sudo SUSEConnect -p PackageHub/15.4/x86_64 + + ``` +- Refresh the metadata: + ```shell + sudo zypper refresh + ``` + +## Install the package + +```shell +sudo zypper -n install edb-oci +sudo zypper -n install edb-oci-devel +``` diff --git a/product_docs/docs/ocl_connector/17/installing/linux_x86_64/ocl_ubuntu_20.mdx b/product_docs/docs/ocl_connector/17/installing/linux_x86_64/ocl_ubuntu_20.mdx new file mode 100644 index 00000000000..a4df02a1a47 --- /dev/null +++ b/product_docs/docs/ocl_connector/17/installing/linux_x86_64/ocl_ubuntu_20.mdx @@ -0,0 +1,47 @@ +--- +navTitle: Ubuntu 20.04 +title: Installing EDB OCL Connector on Ubuntu 20.04 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. + +redirects: + - /ocl_connector/16/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_ubuntu20_x86 +--- + +## Prerequisites + +Before you begin the installation process: + +- Install Postgres on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See: + + - [Installing EDB Postgres Advanced Server](/epas/latest/installing/) + + - [Installing PostgreSQL](https://www.postgresql.org/download/) + +- Set up the EDB repository. + + Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. + + To determine if your repository exists, enter this command: + + `apt-cache search enterprisedb` + + If no output is generated, the repository isn't installed. + + To set up the EDB repository: + + 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads). + + 1. Select the button that provides access to the EDB repository. + + 1. Select the platform and software that you want to download. + + 1. Follow the instructions for setting up the EDB repository. + +## Install the package + +```shell +sudo apt-get -y install edb-oci +sudo apt-get -y install edb-oci-dev +``` diff --git a/product_docs/docs/ocl_connector/17/installing/linux_x86_64/ocl_ubuntu_22.mdx b/product_docs/docs/ocl_connector/17/installing/linux_x86_64/ocl_ubuntu_22.mdx new file mode 100644 index 00000000000..c1b4f4c0fc2 --- /dev/null +++ b/product_docs/docs/ocl_connector/17/installing/linux_x86_64/ocl_ubuntu_22.mdx @@ -0,0 +1,47 @@ +--- +navTitle: Ubuntu 22.04 +title: Installing EDB OCL Connector on Ubuntu 22.04 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. + +redirects: + - /ocl_connector/16/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_ubuntu22_x86 +--- + +## Prerequisites + +Before you begin the installation process: + +- Install Postgres on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See: + + - [Installing EDB Postgres Advanced Server](/epas/latest/installing/) + + - [Installing PostgreSQL](https://www.postgresql.org/download/) + +- Set up the EDB repository. + + Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. + + To determine if your repository exists, enter this command: + + `apt-cache search enterprisedb` + + If no output is generated, the repository isn't installed. + + To set up the EDB repository: + + 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads). + + 1. Select the button that provides access to the EDB repository. + + 1. Select the platform and software that you want to download. + + 1. Follow the instructions for setting up the EDB repository. + +## Install the package + +```shell +sudo apt-get -y install edb-oci +sudo apt-get -y install edb-oci-dev +``` diff --git a/product_docs/docs/ocl_connector/17/installing/upgrading.mdx b/product_docs/docs/ocl_connector/17/installing/upgrading.mdx new file mode 100644 index 00000000000..26b0bdbaa23 --- /dev/null +++ b/product_docs/docs/ocl_connector/17/installing/upgrading.mdx @@ -0,0 +1,32 @@ +--- +title: "Upgrading a Linux installation" +navTitle: "Upgrading" +redirects: + - /ocl_connector/latest/04_open_client_library/01_installing_and_configuring_the_ocl_connector/11_updating_rpm_install/ +--- + + +If you have an existing OCL Connector installation on a Linux platform, you can upgrade your repository configuration file, which enables access to the current EDB repository. Then you can upgrade to a more recent version of OCL Connector. + +To update the `edb.repo` file: + +```shell +# Update your repository configuration file +sudo upgrade edb-repo + +# Upgrade the installed product +sudo upgrade edb-oci + +sudo upgrade edb-oci-devel +``` + +Where `` is the package manager used with your operating system: + + | Package manager | Operating system | + | --------------- | -------------------------------- | + | dnf | RHEL 8/9 and derivatives | + | zypper | SLES | + | apt-get | Debian and Ubuntu | + + + diff --git a/product_docs/docs/ocl_connector/17/installing/windows.mdx b/product_docs/docs/ocl_connector/17/installing/windows.mdx new file mode 100644 index 00000000000..3492cb8a10a --- /dev/null +++ b/product_docs/docs/ocl_connector/17/installing/windows.mdx @@ -0,0 +1,50 @@ +--- +title: "Installing on Windows" +navTitle: "On Windows" +redirects: + - /ocl_connector/latest/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_windows/ +--- + +EDB provides a graphical interactive installer for Windows. You can access it in two ways: + +- Download the graphical installer from the [Downloads page](https://www.enterprisedb.com/software-downloads-postgres#connectors), and invoke the installer directly. See [Installing directly](#installing-directly). + +- Use StackBuilder Plus with EDB Postgres Advanced Server to download the EDB installer package and invoke the graphical installer. See [Using StackBuilder Plus](#using-stackbuilder-plus). + + +## Installing directly + +After downloading the graphical installer, to start the installation wizard, assume sufficient privileges (superuser or administrator) and double-click the installer icon. If prompted, provide a password. + +In some versions of Windows, to invoke the installer with administrator privileges, you need to right-click the installer icon and select **Run as Administrator** from the context menu. + +Proceed to [Using the graphical installer](#using-the-graphical-installer). + + +## Using StackBuilder Plus + +If you're using EDB Postgres Advanced Server, you can invoke the graphical installer with StackBuilder Plus. See [Using StackBuilder Plus](/epas/latest/installing/windows/installing_advanced_server_with_the_interactive_installer/using_stackbuilder_plus/). + +1. In StackBuilder Plus, follow the prompts until you get to the module selection page. + + On the Welcome page, from the list of available servers, select the target server installation. If your network requires you to use a proxy server to access the internet, select **Proxy servers** and specify a server. Select **Next**. + +1. Expand the **Database Drivers** node, and select **EnterpriseDB OCI Connector**. + +1. Proceed to [Using the graphical installer](#using-the-graphical-installer). + + +## Using the graphical installer + +1. Select the installation language and select **OK**. + +1. On the Setup OCI page, select **Next**. + +1. Browse to a directory where you want to install OCI, or leave the directory set to the default location. Select **Next**. + +1. On the Ready to Install page, select **Next**. + + An information box shows the installation progress of the selected components. + +1. When the installation is complete, select **Finish**. + diff --git a/product_docs/docs/ocl_connector/17/ocl_rel_notes/16.1.0.1_ocl_release_notes.mdx b/product_docs/docs/ocl_connector/17/ocl_rel_notes/16.1.0.1_ocl_release_notes.mdx new file mode 100644 index 00000000000..c68fb2d8a01 --- /dev/null +++ b/product_docs/docs/ocl_connector/17/ocl_rel_notes/16.1.0.1_ocl_release_notes.mdx @@ -0,0 +1,14 @@ +--- +title: "EDB OCL Connector 16.1.0.1 release notes" +navTitle: Version 16.1.0.1 +--- + +Released: 09 Nov 2023 + +The EDB OCL Connector provides an API similar to the Oracle Call Interface. + +New features, enhancements, bug fixes, and other changes in the EDB OCL Connector 16.1.0.1 include: + +| Type | Description | +| ----------- | ----------------------------------------------------------- | +| Enhancement | Added support for EDB Postgres Advanced Server version 16.1 | diff --git a/product_docs/docs/ocl_connector/17/ocl_rel_notes/16.1.0.2_ocl_release_notes.mdx b/product_docs/docs/ocl_connector/17/ocl_rel_notes/16.1.0.2_ocl_release_notes.mdx new file mode 100644 index 00000000000..cb94ab72191 --- /dev/null +++ b/product_docs/docs/ocl_connector/17/ocl_rel_notes/16.1.0.2_ocl_release_notes.mdx @@ -0,0 +1,14 @@ +--- +title: "EDB OCL Connector 16.1.0.2 release notes" +navTitle: Version 16.1.0.2 +--- + +Released: 15 Feb 2024 + +The EDB OCL Connector provides an API similar to the Oracle Call Interface. + +New features, enhancements, bug fixes, and other changes in the EDB OCL Connector 16.1.0.2 include: + +| Type | Description | +| ----------- | ----------------------------------------------------------- | +| Enhancement | Added support for SQLT_BOL for SQL BOOLEAN. | diff --git a/product_docs/docs/ocl_connector/17/ocl_rel_notes/index.mdx b/product_docs/docs/ocl_connector/17/ocl_rel_notes/index.mdx new file mode 100644 index 00000000000..77ba9f8a562 --- /dev/null +++ b/product_docs/docs/ocl_connector/17/ocl_rel_notes/index.mdx @@ -0,0 +1,16 @@ +--- +title: "EDB OCL Connector release notes" +navTitle: Release Notes +navigation: + - 16.1.0.2_ocl_release_notes + - 16.1.0.1_ocl_release_notes +--- + +The EDB OCL connector documentation describes the latest version of the EDB OCL connector. + +Release notes describe what's new in a release. When a minor or patch release introduces new functionality, indicators in the content identify the version that introduced the new feature. + +| Version | Release date | +| -------------------------------------- | ------------ | +| [16.1.0.2](16.1.0.2_ocl_release_notes) | 15 Feb 2024 | +| [16.1.0.1](16.1.0.1_ocl_release_notes) | 09 Nov 2023 | From b9292e9f4649f24ebcfcefb7f224a6bf31b04aa4 Mon Sep 17 00:00:00 2001 From: Josh Earlenbaugh Date: Mon, 18 Nov 2024 13:50:57 -0500 Subject: [PATCH 02/24] Fixed index: --- product_docs/docs/ocl_connector/17/index.mdx | 2 +- product_docs/docs/ocl_connector/17/ocl_rel_notes/index.mdx | 6 ++---- 2 files changed, 3 insertions(+), 5 deletions(-) diff --git a/product_docs/docs/ocl_connector/17/index.mdx b/product_docs/docs/ocl_connector/17/index.mdx index 3c8dcba4dcc..320791a4102 100644 --- a/product_docs/docs/ocl_connector/17/index.mdx +++ b/product_docs/docs/ocl_connector/17/index.mdx @@ -1,7 +1,7 @@ --- title: "EDB OCL Connector" directoryDefaults: - description: "EDB OCL Connector Version 15.1.0.1 Documentation and release notes." + description: "EDB OCL Connector Version 17.1.0.1 Documentation and release notes." navigation: - ocl_rel_notes - 02_supported_platforms diff --git a/product_docs/docs/ocl_connector/17/ocl_rel_notes/index.mdx b/product_docs/docs/ocl_connector/17/ocl_rel_notes/index.mdx index 77ba9f8a562..b50aa8a9b1f 100644 --- a/product_docs/docs/ocl_connector/17/ocl_rel_notes/index.mdx +++ b/product_docs/docs/ocl_connector/17/ocl_rel_notes/index.mdx @@ -2,8 +2,7 @@ title: "EDB OCL Connector release notes" navTitle: Release Notes navigation: - - 16.1.0.2_ocl_release_notes - - 16.1.0.1_ocl_release_notes + - 17.1.0.1_ocl_release_notes --- The EDB OCL connector documentation describes the latest version of the EDB OCL connector. @@ -12,5 +11,4 @@ Release notes describe what's new in a release. When a minor or patch release in | Version | Release date | | -------------------------------------- | ------------ | -| [16.1.0.2](16.1.0.2_ocl_release_notes) | 15 Feb 2024 | -| [16.1.0.1](16.1.0.1_ocl_release_notes) | 09 Nov 2023 | +| [17.1.0.1](17.1.0.1_ocl_release_notes) | 20 Nov 2024 | From b9458c3e414f64856ef894367199f1ea343297a4 Mon Sep 17 00:00:00 2001 From: Josh Earlenbaugh Date: Mon, 18 Nov 2024 13:55:03 -0500 Subject: [PATCH 03/24] Added 17.2.0.1 --- .../ocl_rel_notes/16.1.0.2_ocl_release_notes.mdx | 14 -------------- ...se_notes.mdx => 17.2.0.1_ocl_release_notes.mdx} | 10 +++++----- .../docs/ocl_connector/17/ocl_rel_notes/index.mdx | 4 ++-- 3 files changed, 7 insertions(+), 21 deletions(-) delete mode 100644 product_docs/docs/ocl_connector/17/ocl_rel_notes/16.1.0.2_ocl_release_notes.mdx rename product_docs/docs/ocl_connector/17/ocl_rel_notes/{16.1.0.1_ocl_release_notes.mdx => 17.2.0.1_ocl_release_notes.mdx} (71%) diff --git a/product_docs/docs/ocl_connector/17/ocl_rel_notes/16.1.0.2_ocl_release_notes.mdx b/product_docs/docs/ocl_connector/17/ocl_rel_notes/16.1.0.2_ocl_release_notes.mdx deleted file mode 100644 index cb94ab72191..00000000000 --- a/product_docs/docs/ocl_connector/17/ocl_rel_notes/16.1.0.2_ocl_release_notes.mdx +++ /dev/null @@ -1,14 +0,0 @@ ---- -title: "EDB OCL Connector 16.1.0.2 release notes" -navTitle: Version 16.1.0.2 ---- - -Released: 15 Feb 2024 - -The EDB OCL Connector provides an API similar to the Oracle Call Interface. - -New features, enhancements, bug fixes, and other changes in the EDB OCL Connector 16.1.0.2 include: - -| Type | Description | -| ----------- | ----------------------------------------------------------- | -| Enhancement | Added support for SQLT_BOL for SQL BOOLEAN. | diff --git a/product_docs/docs/ocl_connector/17/ocl_rel_notes/16.1.0.1_ocl_release_notes.mdx b/product_docs/docs/ocl_connector/17/ocl_rel_notes/17.2.0.1_ocl_release_notes.mdx similarity index 71% rename from product_docs/docs/ocl_connector/17/ocl_rel_notes/16.1.0.1_ocl_release_notes.mdx rename to product_docs/docs/ocl_connector/17/ocl_rel_notes/17.2.0.1_ocl_release_notes.mdx index c68fb2d8a01..5fbd948ca93 100644 --- a/product_docs/docs/ocl_connector/17/ocl_rel_notes/16.1.0.1_ocl_release_notes.mdx +++ b/product_docs/docs/ocl_connector/17/ocl_rel_notes/17.2.0.1_ocl_release_notes.mdx @@ -1,14 +1,14 @@ --- -title: "EDB OCL Connector 16.1.0.1 release notes" -navTitle: Version 16.1.0.1 +title: "EDB OCL Connector 17.2.0.1 release notes" +navTitle: Version 17.2.0.1 --- -Released: 09 Nov 2023 +Released: 20 Nov 2024 The EDB OCL Connector provides an API similar to the Oracle Call Interface. -New features, enhancements, bug fixes, and other changes in the EDB OCL Connector 16.1.0.1 include: +New features, enhancements, bug fixes, and other changes in the EDB OCL Connector 17.2.0.1 include: | Type | Description | | ----------- | ----------------------------------------------------------- | -| Enhancement | Added support for EDB Postgres Advanced Server version 16.1 | +| Enhancement | Added support for EDB Postgres Advanced Server version 17.2 | diff --git a/product_docs/docs/ocl_connector/17/ocl_rel_notes/index.mdx b/product_docs/docs/ocl_connector/17/ocl_rel_notes/index.mdx index b50aa8a9b1f..8a526154c9c 100644 --- a/product_docs/docs/ocl_connector/17/ocl_rel_notes/index.mdx +++ b/product_docs/docs/ocl_connector/17/ocl_rel_notes/index.mdx @@ -2,7 +2,7 @@ title: "EDB OCL Connector release notes" navTitle: Release Notes navigation: - - 17.1.0.1_ocl_release_notes + - 17.2.0.1_ocl_release_notes --- The EDB OCL connector documentation describes the latest version of the EDB OCL connector. @@ -11,4 +11,4 @@ Release notes describe what's new in a release. When a minor or patch release in | Version | Release date | | -------------------------------------- | ------------ | -| [17.1.0.1](17.1.0.1_ocl_release_notes) | 20 Nov 2024 | +| [17.2.0.1](17.2.0.1_ocl_release_notes) | 20 Nov 2024 | From 552710deecef1e6113752099c2d4565b0bee5d9b Mon Sep 17 00:00:00 2001 From: Josh Earlenbaugh Date: Mon, 18 Nov 2024 12:07:55 -0500 Subject: [PATCH 04/24] Bumped folder directory to 42.7.3.2 --- .../01_jdbc_rel_notes/08_jdbc_42.3.3.1_rel_notes.mdx | 0 .../01_jdbc_rel_notes/09_jdbc_42.3.2.1_rel_notes.mdx | 0 .../01_jdbc_rel_notes/10_jdbc_42.2.24.1_rel_notes.mdx | 0 .../01_jdbc_rel_notes/12_jdbc_42.2.19.1_rel_notes.mdx | 0 .../01_jdbc_rel_notes/14_jdbc_42.2.12.3_rel_notes.mdx | 0 .../01_jdbc_rel_notes/16_jdbc_42.2.9.1_rel_notes.mdx | 0 .../01_jdbc_rel_notes/18_jdbc_42.2.8.1_rel_notes.mdx | 0 .../{42.7.3.1 => 42.7.3.2}/01_jdbc_rel_notes/index.mdx | 0 .../01_jdbc_rel_notes/jdbc_42.5.0.1_rel_notes.mdx | 0 .../01_jdbc_rel_notes/jdbc_42.5.1.1_rel_notes.mdx | 0 .../01_jdbc_rel_notes/jdbc_42.5.1.2_rel_notes.mdx | 0 .../01_jdbc_rel_notes/jdbc_42.5.4.1_rel_notes.mdx | 0 .../01_jdbc_rel_notes/jdbc_42.5.4.2_rel_notes.mdx | 0 .../01_jdbc_rel_notes/jdbc_42.7.3.1_rel_notes.mdx | 0 .../{42.7.3.1 => 42.7.3.2}/02_requirements_overview.mdx | 0 .../03_advanced_server_jdbc_connector_overview.mdx | 0 .../01_loading_the_advanced_server_jdbc_connector.mdx | 0 .../01_additional_connection_properties.mdx | 0 .../02_preferring_synchronous_secondary_database_servers.mdx | 0 .../02_connecting_to_the_database/index.mdx | 0 .../03_executing_sql_statements_through_statement_objects.mdx | 0 .../04_retrieving_results_from_a_resultset_object.mdx | 0 .../05_freeing_resources.mdx | 0 .../06_handling_errors.mdx | 0 .../index.mdx | 0 .../{42.7.3.1 => 42.7.3.2}/05a_using_advanced_queueing/index.mdx | 0 .../05a_using_advanced_queueing/jms_application.mdx | 0 .../05a_using_advanced_queueing/message_acknowledgement.mdx | 0 .../05a_using_advanced_queueing/message_types.mdx | 0 .../05a_using_advanced_queueing/non_standard_message.mdx | 0 .../05a_using_advanced_queueing/serverside_setup.mdx | 0 .../06_executing_sql_commands_with_executeUpdate().mdx | 0 .../07_adding_a_graphical_interface_to_a_java_program.mdx | 0 .../01_reducing_client-side_resource_requirements.mdx | 0 .../02_using_preparedstatements_to_send_sql_commands.mdx | 0 .../03_executing_stored_procedures.mdx | 0 .../04_using_ref_cursors_with_java.mdx | 0 .../05_using_bytea_data_with_java.mdx | 0 .../06_using_object_types_and_collections_with_java.mdx | 0 .../07_asynchronous_notification_handling_with_noticelistener.mdx | 0 .../08_advanced_jdbc_connector_functionality/index.mdx | 0 .../01_using_ssl/01_configuring_the_server.mdx | 0 .../01_using_ssl/02_configuring_the_client.mdx | 0 .../01_using_ssl/03_testing_the_ssl_jdbc_connection.mdx | 0 .../04_using_certificate_authentication_without_a_password.mdx | 0 .../09_security_and_encryption/01_using_ssl/index.mdx | 0 .../09_security_and_encryption/02_scram_compatibility.mdx | 0 .../03_support_for_gssapi_encrypted_connection.mdx | 0 .../{42.7.3.1 => 42.7.3.2}/09_security_and_encryption/index.mdx | 0 .../10_advanced_server_jdbc_connector_logging.mdx | 0 .../{42.7.3.1 => 42.7.3.2}/11_reference_jdbc_data_types.mdx | 0 .../{42.7.3.1 => 42.7.3.2}/images/core_classes_and_interfaces.png | 0 .../{42.7.3.1 => 42.7.3.2}/images/drivermanager_drivers.png | 0 .../{42.7.3.1 => 42.7.3.2}/images/jdbc_class_relationships.png | 0 .../{42.7.3.1 => 42.7.3.2}/images/the_showemployees_window.png | 0 product_docs/docs/jdbc_connector/{42.7.3.1 => 42.7.3.2}/index.mdx | 0 .../{42.7.3.1 => 42.7.3.2}/installing/configuring_for_java.mdx | 0 .../jdbc_connector/{42.7.3.1 => 42.7.3.2}/installing/index.mdx | 0 .../{42.7.3.1 => 42.7.3.2}/installing/linux_arm64/index.mdx | 0 .../installing/linux_arm64/jdbc_debian_12.mdx | 0 .../{42.7.3.1 => 42.7.3.2}/installing/linux_ppc64le/index.mdx | 0 .../installing/linux_ppc64le/jdbc_rhel_8.mdx | 0 .../installing/linux_ppc64le/jdbc_rhel_9.mdx | 0 .../installing/linux_ppc64le/jdbc_sles_12.mdx | 0 .../installing/linux_ppc64le/jdbc_sles_15.mdx | 0 .../{42.7.3.1 => 42.7.3.2}/installing/linux_x86_64/index.mdx | 0 .../installing/linux_x86_64/jdbc_debian_11.mdx | 0 .../installing/linux_x86_64/jdbc_debian_12.mdx | 0 .../installing/linux_x86_64/jdbc_other_linux_8.mdx | 0 .../installing/linux_x86_64/jdbc_other_linux_9.mdx | 0 .../installing/linux_x86_64/jdbc_rhel_8.mdx | 0 .../installing/linux_x86_64/jdbc_rhel_9.mdx | 0 .../installing/linux_x86_64/jdbc_sles_12.mdx | 0 .../installing/linux_x86_64/jdbc_sles_15.mdx | 0 .../installing/linux_x86_64/jdbc_ubuntu_20.mdx | 0 .../installing/linux_x86_64/jdbc_ubuntu_22.mdx | 0 .../{42.7.3.1 => 42.7.3.2}/installing/upgrading.mdx | 0 .../{42.7.3.1 => 42.7.3.2}/installing/using_maven.mdx | 0 .../jdbc_connector/{42.7.3.1 => 42.7.3.2}/installing/windows.mdx | 0 79 files changed, 0 insertions(+), 0 deletions(-) rename product_docs/docs/jdbc_connector/{42.7.3.1 => 42.7.3.2}/01_jdbc_rel_notes/08_jdbc_42.3.3.1_rel_notes.mdx (100%) rename product_docs/docs/jdbc_connector/{42.7.3.1 => 42.7.3.2}/01_jdbc_rel_notes/09_jdbc_42.3.2.1_rel_notes.mdx (100%) rename product_docs/docs/jdbc_connector/{42.7.3.1 => 42.7.3.2}/01_jdbc_rel_notes/10_jdbc_42.2.24.1_rel_notes.mdx (100%) rename product_docs/docs/jdbc_connector/{42.7.3.1 => 42.7.3.2}/01_jdbc_rel_notes/12_jdbc_42.2.19.1_rel_notes.mdx (100%) rename product_docs/docs/jdbc_connector/{42.7.3.1 => 42.7.3.2}/01_jdbc_rel_notes/14_jdbc_42.2.12.3_rel_notes.mdx (100%) rename product_docs/docs/jdbc_connector/{42.7.3.1 => 42.7.3.2}/01_jdbc_rel_notes/16_jdbc_42.2.9.1_rel_notes.mdx (100%) rename product_docs/docs/jdbc_connector/{42.7.3.1 => 42.7.3.2}/01_jdbc_rel_notes/18_jdbc_42.2.8.1_rel_notes.mdx (100%) rename product_docs/docs/jdbc_connector/{42.7.3.1 => 42.7.3.2}/01_jdbc_rel_notes/index.mdx (100%) rename product_docs/docs/jdbc_connector/{42.7.3.1 => 42.7.3.2}/01_jdbc_rel_notes/jdbc_42.5.0.1_rel_notes.mdx (100%) rename product_docs/docs/jdbc_connector/{42.7.3.1 => 42.7.3.2}/01_jdbc_rel_notes/jdbc_42.5.1.1_rel_notes.mdx (100%) rename product_docs/docs/jdbc_connector/{42.7.3.1 => 42.7.3.2}/01_jdbc_rel_notes/jdbc_42.5.1.2_rel_notes.mdx (100%) rename product_docs/docs/jdbc_connector/{42.7.3.1 => 42.7.3.2}/01_jdbc_rel_notes/jdbc_42.5.4.1_rel_notes.mdx (100%) rename product_docs/docs/jdbc_connector/{42.7.3.1 => 42.7.3.2}/01_jdbc_rel_notes/jdbc_42.5.4.2_rel_notes.mdx (100%) rename product_docs/docs/jdbc_connector/{42.7.3.1 => 42.7.3.2}/01_jdbc_rel_notes/jdbc_42.7.3.1_rel_notes.mdx (100%) rename product_docs/docs/jdbc_connector/{42.7.3.1 => 42.7.3.2}/02_requirements_overview.mdx (100%) rename product_docs/docs/jdbc_connector/{42.7.3.1 => 42.7.3.2}/03_advanced_server_jdbc_connector_overview.mdx (100%) rename product_docs/docs/jdbc_connector/{42.7.3.1 => 42.7.3.2}/05_using_the_advanced_server_jdbc_connector_with_java_applications/01_loading_the_advanced_server_jdbc_connector.mdx (100%) rename product_docs/docs/jdbc_connector/{42.7.3.1 => 42.7.3.2}/05_using_the_advanced_server_jdbc_connector_with_java_applications/02_connecting_to_the_database/01_additional_connection_properties.mdx (100%) rename product_docs/docs/jdbc_connector/{42.7.3.1 => 42.7.3.2}/05_using_the_advanced_server_jdbc_connector_with_java_applications/02_connecting_to_the_database/02_preferring_synchronous_secondary_database_servers.mdx (100%) rename product_docs/docs/jdbc_connector/{42.7.3.1 => 42.7.3.2}/05_using_the_advanced_server_jdbc_connector_with_java_applications/02_connecting_to_the_database/index.mdx (100%) rename product_docs/docs/jdbc_connector/{42.7.3.1 => 42.7.3.2}/05_using_the_advanced_server_jdbc_connector_with_java_applications/03_executing_sql_statements_through_statement_objects.mdx (100%) rename product_docs/docs/jdbc_connector/{42.7.3.1 => 42.7.3.2}/05_using_the_advanced_server_jdbc_connector_with_java_applications/04_retrieving_results_from_a_resultset_object.mdx (100%) rename product_docs/docs/jdbc_connector/{42.7.3.1 => 42.7.3.2}/05_using_the_advanced_server_jdbc_connector_with_java_applications/05_freeing_resources.mdx (100%) rename product_docs/docs/jdbc_connector/{42.7.3.1 => 42.7.3.2}/05_using_the_advanced_server_jdbc_connector_with_java_applications/06_handling_errors.mdx (100%) rename product_docs/docs/jdbc_connector/{42.7.3.1 => 42.7.3.2}/05_using_the_advanced_server_jdbc_connector_with_java_applications/index.mdx (100%) rename product_docs/docs/jdbc_connector/{42.7.3.1 => 42.7.3.2}/05a_using_advanced_queueing/index.mdx (100%) rename product_docs/docs/jdbc_connector/{42.7.3.1 => 42.7.3.2}/05a_using_advanced_queueing/jms_application.mdx (100%) rename product_docs/docs/jdbc_connector/{42.7.3.1 => 42.7.3.2}/05a_using_advanced_queueing/message_acknowledgement.mdx (100%) rename product_docs/docs/jdbc_connector/{42.7.3.1 => 42.7.3.2}/05a_using_advanced_queueing/message_types.mdx (100%) rename product_docs/docs/jdbc_connector/{42.7.3.1 => 42.7.3.2}/05a_using_advanced_queueing/non_standard_message.mdx (100%) rename product_docs/docs/jdbc_connector/{42.7.3.1 => 42.7.3.2}/05a_using_advanced_queueing/serverside_setup.mdx (100%) rename product_docs/docs/jdbc_connector/{42.7.3.1 => 42.7.3.2}/06_executing_sql_commands_with_executeUpdate().mdx (100%) rename product_docs/docs/jdbc_connector/{42.7.3.1 => 42.7.3.2}/07_adding_a_graphical_interface_to_a_java_program.mdx (100%) rename product_docs/docs/jdbc_connector/{42.7.3.1 => 42.7.3.2}/08_advanced_jdbc_connector_functionality/01_reducing_client-side_resource_requirements.mdx (100%) rename product_docs/docs/jdbc_connector/{42.7.3.1 => 42.7.3.2}/08_advanced_jdbc_connector_functionality/02_using_preparedstatements_to_send_sql_commands.mdx (100%) rename product_docs/docs/jdbc_connector/{42.7.3.1 => 42.7.3.2}/08_advanced_jdbc_connector_functionality/03_executing_stored_procedures.mdx (100%) rename product_docs/docs/jdbc_connector/{42.7.3.1 => 42.7.3.2}/08_advanced_jdbc_connector_functionality/04_using_ref_cursors_with_java.mdx (100%) rename product_docs/docs/jdbc_connector/{42.7.3.1 => 42.7.3.2}/08_advanced_jdbc_connector_functionality/05_using_bytea_data_with_java.mdx (100%) rename product_docs/docs/jdbc_connector/{42.7.3.1 => 42.7.3.2}/08_advanced_jdbc_connector_functionality/06_using_object_types_and_collections_with_java.mdx (100%) rename product_docs/docs/jdbc_connector/{42.7.3.1 => 42.7.3.2}/08_advanced_jdbc_connector_functionality/07_asynchronous_notification_handling_with_noticelistener.mdx (100%) rename product_docs/docs/jdbc_connector/{42.7.3.1 => 42.7.3.2}/08_advanced_jdbc_connector_functionality/index.mdx (100%) rename product_docs/docs/jdbc_connector/{42.7.3.1 => 42.7.3.2}/09_security_and_encryption/01_using_ssl/01_configuring_the_server.mdx (100%) rename product_docs/docs/jdbc_connector/{42.7.3.1 => 42.7.3.2}/09_security_and_encryption/01_using_ssl/02_configuring_the_client.mdx (100%) rename product_docs/docs/jdbc_connector/{42.7.3.1 => 42.7.3.2}/09_security_and_encryption/01_using_ssl/03_testing_the_ssl_jdbc_connection.mdx (100%) rename product_docs/docs/jdbc_connector/{42.7.3.1 => 42.7.3.2}/09_security_and_encryption/01_using_ssl/04_using_certificate_authentication_without_a_password.mdx (100%) rename product_docs/docs/jdbc_connector/{42.7.3.1 => 42.7.3.2}/09_security_and_encryption/01_using_ssl/index.mdx (100%) rename product_docs/docs/jdbc_connector/{42.7.3.1 => 42.7.3.2}/09_security_and_encryption/02_scram_compatibility.mdx (100%) rename product_docs/docs/jdbc_connector/{42.7.3.1 => 42.7.3.2}/09_security_and_encryption/03_support_for_gssapi_encrypted_connection.mdx (100%) rename product_docs/docs/jdbc_connector/{42.7.3.1 => 42.7.3.2}/09_security_and_encryption/index.mdx (100%) rename product_docs/docs/jdbc_connector/{42.7.3.1 => 42.7.3.2}/10_advanced_server_jdbc_connector_logging.mdx (100%) rename product_docs/docs/jdbc_connector/{42.7.3.1 => 42.7.3.2}/11_reference_jdbc_data_types.mdx (100%) rename product_docs/docs/jdbc_connector/{42.7.3.1 => 42.7.3.2}/images/core_classes_and_interfaces.png (100%) rename product_docs/docs/jdbc_connector/{42.7.3.1 => 42.7.3.2}/images/drivermanager_drivers.png (100%) rename product_docs/docs/jdbc_connector/{42.7.3.1 => 42.7.3.2}/images/jdbc_class_relationships.png (100%) rename product_docs/docs/jdbc_connector/{42.7.3.1 => 42.7.3.2}/images/the_showemployees_window.png (100%) rename product_docs/docs/jdbc_connector/{42.7.3.1 => 42.7.3.2}/index.mdx (100%) rename product_docs/docs/jdbc_connector/{42.7.3.1 => 42.7.3.2}/installing/configuring_for_java.mdx (100%) rename product_docs/docs/jdbc_connector/{42.7.3.1 => 42.7.3.2}/installing/index.mdx (100%) rename product_docs/docs/jdbc_connector/{42.7.3.1 => 42.7.3.2}/installing/linux_arm64/index.mdx (100%) rename product_docs/docs/jdbc_connector/{42.7.3.1 => 42.7.3.2}/installing/linux_arm64/jdbc_debian_12.mdx (100%) rename product_docs/docs/jdbc_connector/{42.7.3.1 => 42.7.3.2}/installing/linux_ppc64le/index.mdx (100%) rename product_docs/docs/jdbc_connector/{42.7.3.1 => 42.7.3.2}/installing/linux_ppc64le/jdbc_rhel_8.mdx (100%) rename product_docs/docs/jdbc_connector/{42.7.3.1 => 42.7.3.2}/installing/linux_ppc64le/jdbc_rhel_9.mdx (100%) rename product_docs/docs/jdbc_connector/{42.7.3.1 => 42.7.3.2}/installing/linux_ppc64le/jdbc_sles_12.mdx (100%) rename product_docs/docs/jdbc_connector/{42.7.3.1 => 42.7.3.2}/installing/linux_ppc64le/jdbc_sles_15.mdx (100%) rename product_docs/docs/jdbc_connector/{42.7.3.1 => 42.7.3.2}/installing/linux_x86_64/index.mdx (100%) rename product_docs/docs/jdbc_connector/{42.7.3.1 => 42.7.3.2}/installing/linux_x86_64/jdbc_debian_11.mdx (100%) rename product_docs/docs/jdbc_connector/{42.7.3.1 => 42.7.3.2}/installing/linux_x86_64/jdbc_debian_12.mdx (100%) rename product_docs/docs/jdbc_connector/{42.7.3.1 => 42.7.3.2}/installing/linux_x86_64/jdbc_other_linux_8.mdx (100%) rename product_docs/docs/jdbc_connector/{42.7.3.1 => 42.7.3.2}/installing/linux_x86_64/jdbc_other_linux_9.mdx (100%) rename product_docs/docs/jdbc_connector/{42.7.3.1 => 42.7.3.2}/installing/linux_x86_64/jdbc_rhel_8.mdx (100%) rename product_docs/docs/jdbc_connector/{42.7.3.1 => 42.7.3.2}/installing/linux_x86_64/jdbc_rhel_9.mdx (100%) rename product_docs/docs/jdbc_connector/{42.7.3.1 => 42.7.3.2}/installing/linux_x86_64/jdbc_sles_12.mdx (100%) rename product_docs/docs/jdbc_connector/{42.7.3.1 => 42.7.3.2}/installing/linux_x86_64/jdbc_sles_15.mdx (100%) rename product_docs/docs/jdbc_connector/{42.7.3.1 => 42.7.3.2}/installing/linux_x86_64/jdbc_ubuntu_20.mdx (100%) rename product_docs/docs/jdbc_connector/{42.7.3.1 => 42.7.3.2}/installing/linux_x86_64/jdbc_ubuntu_22.mdx (100%) rename product_docs/docs/jdbc_connector/{42.7.3.1 => 42.7.3.2}/installing/upgrading.mdx (100%) rename product_docs/docs/jdbc_connector/{42.7.3.1 => 42.7.3.2}/installing/using_maven.mdx (100%) rename product_docs/docs/jdbc_connector/{42.7.3.1 => 42.7.3.2}/installing/windows.mdx (100%) diff --git a/product_docs/docs/jdbc_connector/42.7.3.1/01_jdbc_rel_notes/08_jdbc_42.3.3.1_rel_notes.mdx b/product_docs/docs/jdbc_connector/42.7.3.2/01_jdbc_rel_notes/08_jdbc_42.3.3.1_rel_notes.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.7.3.1/01_jdbc_rel_notes/08_jdbc_42.3.3.1_rel_notes.mdx rename to product_docs/docs/jdbc_connector/42.7.3.2/01_jdbc_rel_notes/08_jdbc_42.3.3.1_rel_notes.mdx diff --git a/product_docs/docs/jdbc_connector/42.7.3.1/01_jdbc_rel_notes/09_jdbc_42.3.2.1_rel_notes.mdx b/product_docs/docs/jdbc_connector/42.7.3.2/01_jdbc_rel_notes/09_jdbc_42.3.2.1_rel_notes.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.7.3.1/01_jdbc_rel_notes/09_jdbc_42.3.2.1_rel_notes.mdx rename to product_docs/docs/jdbc_connector/42.7.3.2/01_jdbc_rel_notes/09_jdbc_42.3.2.1_rel_notes.mdx diff --git a/product_docs/docs/jdbc_connector/42.7.3.1/01_jdbc_rel_notes/10_jdbc_42.2.24.1_rel_notes.mdx b/product_docs/docs/jdbc_connector/42.7.3.2/01_jdbc_rel_notes/10_jdbc_42.2.24.1_rel_notes.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.7.3.1/01_jdbc_rel_notes/10_jdbc_42.2.24.1_rel_notes.mdx rename to product_docs/docs/jdbc_connector/42.7.3.2/01_jdbc_rel_notes/10_jdbc_42.2.24.1_rel_notes.mdx diff --git a/product_docs/docs/jdbc_connector/42.7.3.1/01_jdbc_rel_notes/12_jdbc_42.2.19.1_rel_notes.mdx b/product_docs/docs/jdbc_connector/42.7.3.2/01_jdbc_rel_notes/12_jdbc_42.2.19.1_rel_notes.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.7.3.1/01_jdbc_rel_notes/12_jdbc_42.2.19.1_rel_notes.mdx rename to product_docs/docs/jdbc_connector/42.7.3.2/01_jdbc_rel_notes/12_jdbc_42.2.19.1_rel_notes.mdx diff --git a/product_docs/docs/jdbc_connector/42.7.3.1/01_jdbc_rel_notes/14_jdbc_42.2.12.3_rel_notes.mdx b/product_docs/docs/jdbc_connector/42.7.3.2/01_jdbc_rel_notes/14_jdbc_42.2.12.3_rel_notes.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.7.3.1/01_jdbc_rel_notes/14_jdbc_42.2.12.3_rel_notes.mdx rename to product_docs/docs/jdbc_connector/42.7.3.2/01_jdbc_rel_notes/14_jdbc_42.2.12.3_rel_notes.mdx diff --git a/product_docs/docs/jdbc_connector/42.7.3.1/01_jdbc_rel_notes/16_jdbc_42.2.9.1_rel_notes.mdx b/product_docs/docs/jdbc_connector/42.7.3.2/01_jdbc_rel_notes/16_jdbc_42.2.9.1_rel_notes.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.7.3.1/01_jdbc_rel_notes/16_jdbc_42.2.9.1_rel_notes.mdx rename to product_docs/docs/jdbc_connector/42.7.3.2/01_jdbc_rel_notes/16_jdbc_42.2.9.1_rel_notes.mdx diff --git a/product_docs/docs/jdbc_connector/42.7.3.1/01_jdbc_rel_notes/18_jdbc_42.2.8.1_rel_notes.mdx b/product_docs/docs/jdbc_connector/42.7.3.2/01_jdbc_rel_notes/18_jdbc_42.2.8.1_rel_notes.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.7.3.1/01_jdbc_rel_notes/18_jdbc_42.2.8.1_rel_notes.mdx rename to product_docs/docs/jdbc_connector/42.7.3.2/01_jdbc_rel_notes/18_jdbc_42.2.8.1_rel_notes.mdx diff --git a/product_docs/docs/jdbc_connector/42.7.3.1/01_jdbc_rel_notes/index.mdx b/product_docs/docs/jdbc_connector/42.7.3.2/01_jdbc_rel_notes/index.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.7.3.1/01_jdbc_rel_notes/index.mdx rename to product_docs/docs/jdbc_connector/42.7.3.2/01_jdbc_rel_notes/index.mdx diff --git a/product_docs/docs/jdbc_connector/42.7.3.1/01_jdbc_rel_notes/jdbc_42.5.0.1_rel_notes.mdx b/product_docs/docs/jdbc_connector/42.7.3.2/01_jdbc_rel_notes/jdbc_42.5.0.1_rel_notes.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.7.3.1/01_jdbc_rel_notes/jdbc_42.5.0.1_rel_notes.mdx rename to product_docs/docs/jdbc_connector/42.7.3.2/01_jdbc_rel_notes/jdbc_42.5.0.1_rel_notes.mdx diff --git a/product_docs/docs/jdbc_connector/42.7.3.1/01_jdbc_rel_notes/jdbc_42.5.1.1_rel_notes.mdx b/product_docs/docs/jdbc_connector/42.7.3.2/01_jdbc_rel_notes/jdbc_42.5.1.1_rel_notes.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.7.3.1/01_jdbc_rel_notes/jdbc_42.5.1.1_rel_notes.mdx rename to product_docs/docs/jdbc_connector/42.7.3.2/01_jdbc_rel_notes/jdbc_42.5.1.1_rel_notes.mdx diff --git a/product_docs/docs/jdbc_connector/42.7.3.1/01_jdbc_rel_notes/jdbc_42.5.1.2_rel_notes.mdx b/product_docs/docs/jdbc_connector/42.7.3.2/01_jdbc_rel_notes/jdbc_42.5.1.2_rel_notes.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.7.3.1/01_jdbc_rel_notes/jdbc_42.5.1.2_rel_notes.mdx rename to product_docs/docs/jdbc_connector/42.7.3.2/01_jdbc_rel_notes/jdbc_42.5.1.2_rel_notes.mdx diff --git a/product_docs/docs/jdbc_connector/42.7.3.1/01_jdbc_rel_notes/jdbc_42.5.4.1_rel_notes.mdx b/product_docs/docs/jdbc_connector/42.7.3.2/01_jdbc_rel_notes/jdbc_42.5.4.1_rel_notes.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.7.3.1/01_jdbc_rel_notes/jdbc_42.5.4.1_rel_notes.mdx rename to product_docs/docs/jdbc_connector/42.7.3.2/01_jdbc_rel_notes/jdbc_42.5.4.1_rel_notes.mdx diff --git a/product_docs/docs/jdbc_connector/42.7.3.1/01_jdbc_rel_notes/jdbc_42.5.4.2_rel_notes.mdx b/product_docs/docs/jdbc_connector/42.7.3.2/01_jdbc_rel_notes/jdbc_42.5.4.2_rel_notes.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.7.3.1/01_jdbc_rel_notes/jdbc_42.5.4.2_rel_notes.mdx rename to product_docs/docs/jdbc_connector/42.7.3.2/01_jdbc_rel_notes/jdbc_42.5.4.2_rel_notes.mdx diff --git a/product_docs/docs/jdbc_connector/42.7.3.1/01_jdbc_rel_notes/jdbc_42.7.3.1_rel_notes.mdx b/product_docs/docs/jdbc_connector/42.7.3.2/01_jdbc_rel_notes/jdbc_42.7.3.1_rel_notes.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.7.3.1/01_jdbc_rel_notes/jdbc_42.7.3.1_rel_notes.mdx rename to product_docs/docs/jdbc_connector/42.7.3.2/01_jdbc_rel_notes/jdbc_42.7.3.1_rel_notes.mdx diff --git a/product_docs/docs/jdbc_connector/42.7.3.1/02_requirements_overview.mdx b/product_docs/docs/jdbc_connector/42.7.3.2/02_requirements_overview.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.7.3.1/02_requirements_overview.mdx rename to product_docs/docs/jdbc_connector/42.7.3.2/02_requirements_overview.mdx diff --git a/product_docs/docs/jdbc_connector/42.7.3.1/03_advanced_server_jdbc_connector_overview.mdx b/product_docs/docs/jdbc_connector/42.7.3.2/03_advanced_server_jdbc_connector_overview.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.7.3.1/03_advanced_server_jdbc_connector_overview.mdx rename to product_docs/docs/jdbc_connector/42.7.3.2/03_advanced_server_jdbc_connector_overview.mdx diff --git a/product_docs/docs/jdbc_connector/42.7.3.1/05_using_the_advanced_server_jdbc_connector_with_java_applications/01_loading_the_advanced_server_jdbc_connector.mdx b/product_docs/docs/jdbc_connector/42.7.3.2/05_using_the_advanced_server_jdbc_connector_with_java_applications/01_loading_the_advanced_server_jdbc_connector.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.7.3.1/05_using_the_advanced_server_jdbc_connector_with_java_applications/01_loading_the_advanced_server_jdbc_connector.mdx rename to product_docs/docs/jdbc_connector/42.7.3.2/05_using_the_advanced_server_jdbc_connector_with_java_applications/01_loading_the_advanced_server_jdbc_connector.mdx diff --git a/product_docs/docs/jdbc_connector/42.7.3.1/05_using_the_advanced_server_jdbc_connector_with_java_applications/02_connecting_to_the_database/01_additional_connection_properties.mdx b/product_docs/docs/jdbc_connector/42.7.3.2/05_using_the_advanced_server_jdbc_connector_with_java_applications/02_connecting_to_the_database/01_additional_connection_properties.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.7.3.1/05_using_the_advanced_server_jdbc_connector_with_java_applications/02_connecting_to_the_database/01_additional_connection_properties.mdx rename to product_docs/docs/jdbc_connector/42.7.3.2/05_using_the_advanced_server_jdbc_connector_with_java_applications/02_connecting_to_the_database/01_additional_connection_properties.mdx diff --git a/product_docs/docs/jdbc_connector/42.7.3.1/05_using_the_advanced_server_jdbc_connector_with_java_applications/02_connecting_to_the_database/02_preferring_synchronous_secondary_database_servers.mdx b/product_docs/docs/jdbc_connector/42.7.3.2/05_using_the_advanced_server_jdbc_connector_with_java_applications/02_connecting_to_the_database/02_preferring_synchronous_secondary_database_servers.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.7.3.1/05_using_the_advanced_server_jdbc_connector_with_java_applications/02_connecting_to_the_database/02_preferring_synchronous_secondary_database_servers.mdx rename to product_docs/docs/jdbc_connector/42.7.3.2/05_using_the_advanced_server_jdbc_connector_with_java_applications/02_connecting_to_the_database/02_preferring_synchronous_secondary_database_servers.mdx diff --git a/product_docs/docs/jdbc_connector/42.7.3.1/05_using_the_advanced_server_jdbc_connector_with_java_applications/02_connecting_to_the_database/index.mdx b/product_docs/docs/jdbc_connector/42.7.3.2/05_using_the_advanced_server_jdbc_connector_with_java_applications/02_connecting_to_the_database/index.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.7.3.1/05_using_the_advanced_server_jdbc_connector_with_java_applications/02_connecting_to_the_database/index.mdx rename to product_docs/docs/jdbc_connector/42.7.3.2/05_using_the_advanced_server_jdbc_connector_with_java_applications/02_connecting_to_the_database/index.mdx diff --git a/product_docs/docs/jdbc_connector/42.7.3.1/05_using_the_advanced_server_jdbc_connector_with_java_applications/03_executing_sql_statements_through_statement_objects.mdx b/product_docs/docs/jdbc_connector/42.7.3.2/05_using_the_advanced_server_jdbc_connector_with_java_applications/03_executing_sql_statements_through_statement_objects.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.7.3.1/05_using_the_advanced_server_jdbc_connector_with_java_applications/03_executing_sql_statements_through_statement_objects.mdx rename to product_docs/docs/jdbc_connector/42.7.3.2/05_using_the_advanced_server_jdbc_connector_with_java_applications/03_executing_sql_statements_through_statement_objects.mdx diff --git a/product_docs/docs/jdbc_connector/42.7.3.1/05_using_the_advanced_server_jdbc_connector_with_java_applications/04_retrieving_results_from_a_resultset_object.mdx b/product_docs/docs/jdbc_connector/42.7.3.2/05_using_the_advanced_server_jdbc_connector_with_java_applications/04_retrieving_results_from_a_resultset_object.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.7.3.1/05_using_the_advanced_server_jdbc_connector_with_java_applications/04_retrieving_results_from_a_resultset_object.mdx rename to product_docs/docs/jdbc_connector/42.7.3.2/05_using_the_advanced_server_jdbc_connector_with_java_applications/04_retrieving_results_from_a_resultset_object.mdx diff --git a/product_docs/docs/jdbc_connector/42.7.3.1/05_using_the_advanced_server_jdbc_connector_with_java_applications/05_freeing_resources.mdx b/product_docs/docs/jdbc_connector/42.7.3.2/05_using_the_advanced_server_jdbc_connector_with_java_applications/05_freeing_resources.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.7.3.1/05_using_the_advanced_server_jdbc_connector_with_java_applications/05_freeing_resources.mdx rename to product_docs/docs/jdbc_connector/42.7.3.2/05_using_the_advanced_server_jdbc_connector_with_java_applications/05_freeing_resources.mdx diff --git a/product_docs/docs/jdbc_connector/42.7.3.1/05_using_the_advanced_server_jdbc_connector_with_java_applications/06_handling_errors.mdx b/product_docs/docs/jdbc_connector/42.7.3.2/05_using_the_advanced_server_jdbc_connector_with_java_applications/06_handling_errors.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.7.3.1/05_using_the_advanced_server_jdbc_connector_with_java_applications/06_handling_errors.mdx rename to product_docs/docs/jdbc_connector/42.7.3.2/05_using_the_advanced_server_jdbc_connector_with_java_applications/06_handling_errors.mdx diff --git a/product_docs/docs/jdbc_connector/42.7.3.1/05_using_the_advanced_server_jdbc_connector_with_java_applications/index.mdx b/product_docs/docs/jdbc_connector/42.7.3.2/05_using_the_advanced_server_jdbc_connector_with_java_applications/index.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.7.3.1/05_using_the_advanced_server_jdbc_connector_with_java_applications/index.mdx rename to product_docs/docs/jdbc_connector/42.7.3.2/05_using_the_advanced_server_jdbc_connector_with_java_applications/index.mdx diff --git a/product_docs/docs/jdbc_connector/42.7.3.1/05a_using_advanced_queueing/index.mdx b/product_docs/docs/jdbc_connector/42.7.3.2/05a_using_advanced_queueing/index.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.7.3.1/05a_using_advanced_queueing/index.mdx rename to product_docs/docs/jdbc_connector/42.7.3.2/05a_using_advanced_queueing/index.mdx diff --git a/product_docs/docs/jdbc_connector/42.7.3.1/05a_using_advanced_queueing/jms_application.mdx b/product_docs/docs/jdbc_connector/42.7.3.2/05a_using_advanced_queueing/jms_application.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.7.3.1/05a_using_advanced_queueing/jms_application.mdx rename to product_docs/docs/jdbc_connector/42.7.3.2/05a_using_advanced_queueing/jms_application.mdx diff --git a/product_docs/docs/jdbc_connector/42.7.3.1/05a_using_advanced_queueing/message_acknowledgement.mdx b/product_docs/docs/jdbc_connector/42.7.3.2/05a_using_advanced_queueing/message_acknowledgement.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.7.3.1/05a_using_advanced_queueing/message_acknowledgement.mdx rename to product_docs/docs/jdbc_connector/42.7.3.2/05a_using_advanced_queueing/message_acknowledgement.mdx diff --git a/product_docs/docs/jdbc_connector/42.7.3.1/05a_using_advanced_queueing/message_types.mdx b/product_docs/docs/jdbc_connector/42.7.3.2/05a_using_advanced_queueing/message_types.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.7.3.1/05a_using_advanced_queueing/message_types.mdx rename to product_docs/docs/jdbc_connector/42.7.3.2/05a_using_advanced_queueing/message_types.mdx diff --git a/product_docs/docs/jdbc_connector/42.7.3.1/05a_using_advanced_queueing/non_standard_message.mdx b/product_docs/docs/jdbc_connector/42.7.3.2/05a_using_advanced_queueing/non_standard_message.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.7.3.1/05a_using_advanced_queueing/non_standard_message.mdx rename to product_docs/docs/jdbc_connector/42.7.3.2/05a_using_advanced_queueing/non_standard_message.mdx diff --git a/product_docs/docs/jdbc_connector/42.7.3.1/05a_using_advanced_queueing/serverside_setup.mdx b/product_docs/docs/jdbc_connector/42.7.3.2/05a_using_advanced_queueing/serverside_setup.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.7.3.1/05a_using_advanced_queueing/serverside_setup.mdx rename to product_docs/docs/jdbc_connector/42.7.3.2/05a_using_advanced_queueing/serverside_setup.mdx diff --git a/product_docs/docs/jdbc_connector/42.7.3.1/06_executing_sql_commands_with_executeUpdate().mdx b/product_docs/docs/jdbc_connector/42.7.3.2/06_executing_sql_commands_with_executeUpdate().mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.7.3.1/06_executing_sql_commands_with_executeUpdate().mdx rename to product_docs/docs/jdbc_connector/42.7.3.2/06_executing_sql_commands_with_executeUpdate().mdx diff --git a/product_docs/docs/jdbc_connector/42.7.3.1/07_adding_a_graphical_interface_to_a_java_program.mdx b/product_docs/docs/jdbc_connector/42.7.3.2/07_adding_a_graphical_interface_to_a_java_program.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.7.3.1/07_adding_a_graphical_interface_to_a_java_program.mdx rename to product_docs/docs/jdbc_connector/42.7.3.2/07_adding_a_graphical_interface_to_a_java_program.mdx diff --git a/product_docs/docs/jdbc_connector/42.7.3.1/08_advanced_jdbc_connector_functionality/01_reducing_client-side_resource_requirements.mdx b/product_docs/docs/jdbc_connector/42.7.3.2/08_advanced_jdbc_connector_functionality/01_reducing_client-side_resource_requirements.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.7.3.1/08_advanced_jdbc_connector_functionality/01_reducing_client-side_resource_requirements.mdx rename to product_docs/docs/jdbc_connector/42.7.3.2/08_advanced_jdbc_connector_functionality/01_reducing_client-side_resource_requirements.mdx diff --git a/product_docs/docs/jdbc_connector/42.7.3.1/08_advanced_jdbc_connector_functionality/02_using_preparedstatements_to_send_sql_commands.mdx b/product_docs/docs/jdbc_connector/42.7.3.2/08_advanced_jdbc_connector_functionality/02_using_preparedstatements_to_send_sql_commands.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.7.3.1/08_advanced_jdbc_connector_functionality/02_using_preparedstatements_to_send_sql_commands.mdx rename to product_docs/docs/jdbc_connector/42.7.3.2/08_advanced_jdbc_connector_functionality/02_using_preparedstatements_to_send_sql_commands.mdx diff --git a/product_docs/docs/jdbc_connector/42.7.3.1/08_advanced_jdbc_connector_functionality/03_executing_stored_procedures.mdx b/product_docs/docs/jdbc_connector/42.7.3.2/08_advanced_jdbc_connector_functionality/03_executing_stored_procedures.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.7.3.1/08_advanced_jdbc_connector_functionality/03_executing_stored_procedures.mdx rename to product_docs/docs/jdbc_connector/42.7.3.2/08_advanced_jdbc_connector_functionality/03_executing_stored_procedures.mdx diff --git a/product_docs/docs/jdbc_connector/42.7.3.1/08_advanced_jdbc_connector_functionality/04_using_ref_cursors_with_java.mdx b/product_docs/docs/jdbc_connector/42.7.3.2/08_advanced_jdbc_connector_functionality/04_using_ref_cursors_with_java.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.7.3.1/08_advanced_jdbc_connector_functionality/04_using_ref_cursors_with_java.mdx rename to product_docs/docs/jdbc_connector/42.7.3.2/08_advanced_jdbc_connector_functionality/04_using_ref_cursors_with_java.mdx diff --git a/product_docs/docs/jdbc_connector/42.7.3.1/08_advanced_jdbc_connector_functionality/05_using_bytea_data_with_java.mdx b/product_docs/docs/jdbc_connector/42.7.3.2/08_advanced_jdbc_connector_functionality/05_using_bytea_data_with_java.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.7.3.1/08_advanced_jdbc_connector_functionality/05_using_bytea_data_with_java.mdx rename to product_docs/docs/jdbc_connector/42.7.3.2/08_advanced_jdbc_connector_functionality/05_using_bytea_data_with_java.mdx diff --git a/product_docs/docs/jdbc_connector/42.7.3.1/08_advanced_jdbc_connector_functionality/06_using_object_types_and_collections_with_java.mdx b/product_docs/docs/jdbc_connector/42.7.3.2/08_advanced_jdbc_connector_functionality/06_using_object_types_and_collections_with_java.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.7.3.1/08_advanced_jdbc_connector_functionality/06_using_object_types_and_collections_with_java.mdx rename to product_docs/docs/jdbc_connector/42.7.3.2/08_advanced_jdbc_connector_functionality/06_using_object_types_and_collections_with_java.mdx diff --git a/product_docs/docs/jdbc_connector/42.7.3.1/08_advanced_jdbc_connector_functionality/07_asynchronous_notification_handling_with_noticelistener.mdx b/product_docs/docs/jdbc_connector/42.7.3.2/08_advanced_jdbc_connector_functionality/07_asynchronous_notification_handling_with_noticelistener.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.7.3.1/08_advanced_jdbc_connector_functionality/07_asynchronous_notification_handling_with_noticelistener.mdx rename to product_docs/docs/jdbc_connector/42.7.3.2/08_advanced_jdbc_connector_functionality/07_asynchronous_notification_handling_with_noticelistener.mdx diff --git a/product_docs/docs/jdbc_connector/42.7.3.1/08_advanced_jdbc_connector_functionality/index.mdx b/product_docs/docs/jdbc_connector/42.7.3.2/08_advanced_jdbc_connector_functionality/index.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.7.3.1/08_advanced_jdbc_connector_functionality/index.mdx rename to product_docs/docs/jdbc_connector/42.7.3.2/08_advanced_jdbc_connector_functionality/index.mdx diff --git a/product_docs/docs/jdbc_connector/42.7.3.1/09_security_and_encryption/01_using_ssl/01_configuring_the_server.mdx b/product_docs/docs/jdbc_connector/42.7.3.2/09_security_and_encryption/01_using_ssl/01_configuring_the_server.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.7.3.1/09_security_and_encryption/01_using_ssl/01_configuring_the_server.mdx rename to product_docs/docs/jdbc_connector/42.7.3.2/09_security_and_encryption/01_using_ssl/01_configuring_the_server.mdx diff --git a/product_docs/docs/jdbc_connector/42.7.3.1/09_security_and_encryption/01_using_ssl/02_configuring_the_client.mdx b/product_docs/docs/jdbc_connector/42.7.3.2/09_security_and_encryption/01_using_ssl/02_configuring_the_client.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.7.3.1/09_security_and_encryption/01_using_ssl/02_configuring_the_client.mdx rename to product_docs/docs/jdbc_connector/42.7.3.2/09_security_and_encryption/01_using_ssl/02_configuring_the_client.mdx diff --git a/product_docs/docs/jdbc_connector/42.7.3.1/09_security_and_encryption/01_using_ssl/03_testing_the_ssl_jdbc_connection.mdx b/product_docs/docs/jdbc_connector/42.7.3.2/09_security_and_encryption/01_using_ssl/03_testing_the_ssl_jdbc_connection.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.7.3.1/09_security_and_encryption/01_using_ssl/03_testing_the_ssl_jdbc_connection.mdx rename to product_docs/docs/jdbc_connector/42.7.3.2/09_security_and_encryption/01_using_ssl/03_testing_the_ssl_jdbc_connection.mdx diff --git a/product_docs/docs/jdbc_connector/42.7.3.1/09_security_and_encryption/01_using_ssl/04_using_certificate_authentication_without_a_password.mdx b/product_docs/docs/jdbc_connector/42.7.3.2/09_security_and_encryption/01_using_ssl/04_using_certificate_authentication_without_a_password.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.7.3.1/09_security_and_encryption/01_using_ssl/04_using_certificate_authentication_without_a_password.mdx rename to product_docs/docs/jdbc_connector/42.7.3.2/09_security_and_encryption/01_using_ssl/04_using_certificate_authentication_without_a_password.mdx diff --git a/product_docs/docs/jdbc_connector/42.7.3.1/09_security_and_encryption/01_using_ssl/index.mdx b/product_docs/docs/jdbc_connector/42.7.3.2/09_security_and_encryption/01_using_ssl/index.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.7.3.1/09_security_and_encryption/01_using_ssl/index.mdx rename to product_docs/docs/jdbc_connector/42.7.3.2/09_security_and_encryption/01_using_ssl/index.mdx diff --git a/product_docs/docs/jdbc_connector/42.7.3.1/09_security_and_encryption/02_scram_compatibility.mdx b/product_docs/docs/jdbc_connector/42.7.3.2/09_security_and_encryption/02_scram_compatibility.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.7.3.1/09_security_and_encryption/02_scram_compatibility.mdx rename to product_docs/docs/jdbc_connector/42.7.3.2/09_security_and_encryption/02_scram_compatibility.mdx diff --git a/product_docs/docs/jdbc_connector/42.7.3.1/09_security_and_encryption/03_support_for_gssapi_encrypted_connection.mdx b/product_docs/docs/jdbc_connector/42.7.3.2/09_security_and_encryption/03_support_for_gssapi_encrypted_connection.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.7.3.1/09_security_and_encryption/03_support_for_gssapi_encrypted_connection.mdx rename to product_docs/docs/jdbc_connector/42.7.3.2/09_security_and_encryption/03_support_for_gssapi_encrypted_connection.mdx diff --git a/product_docs/docs/jdbc_connector/42.7.3.1/09_security_and_encryption/index.mdx b/product_docs/docs/jdbc_connector/42.7.3.2/09_security_and_encryption/index.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.7.3.1/09_security_and_encryption/index.mdx rename to product_docs/docs/jdbc_connector/42.7.3.2/09_security_and_encryption/index.mdx diff --git a/product_docs/docs/jdbc_connector/42.7.3.1/10_advanced_server_jdbc_connector_logging.mdx b/product_docs/docs/jdbc_connector/42.7.3.2/10_advanced_server_jdbc_connector_logging.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.7.3.1/10_advanced_server_jdbc_connector_logging.mdx rename to product_docs/docs/jdbc_connector/42.7.3.2/10_advanced_server_jdbc_connector_logging.mdx diff --git a/product_docs/docs/jdbc_connector/42.7.3.1/11_reference_jdbc_data_types.mdx b/product_docs/docs/jdbc_connector/42.7.3.2/11_reference_jdbc_data_types.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.7.3.1/11_reference_jdbc_data_types.mdx rename to product_docs/docs/jdbc_connector/42.7.3.2/11_reference_jdbc_data_types.mdx diff --git a/product_docs/docs/jdbc_connector/42.7.3.1/images/core_classes_and_interfaces.png b/product_docs/docs/jdbc_connector/42.7.3.2/images/core_classes_and_interfaces.png similarity index 100% rename from product_docs/docs/jdbc_connector/42.7.3.1/images/core_classes_and_interfaces.png rename to product_docs/docs/jdbc_connector/42.7.3.2/images/core_classes_and_interfaces.png diff --git a/product_docs/docs/jdbc_connector/42.7.3.1/images/drivermanager_drivers.png b/product_docs/docs/jdbc_connector/42.7.3.2/images/drivermanager_drivers.png similarity index 100% rename from product_docs/docs/jdbc_connector/42.7.3.1/images/drivermanager_drivers.png rename to product_docs/docs/jdbc_connector/42.7.3.2/images/drivermanager_drivers.png diff --git a/product_docs/docs/jdbc_connector/42.7.3.1/images/jdbc_class_relationships.png b/product_docs/docs/jdbc_connector/42.7.3.2/images/jdbc_class_relationships.png similarity index 100% rename from product_docs/docs/jdbc_connector/42.7.3.1/images/jdbc_class_relationships.png rename to product_docs/docs/jdbc_connector/42.7.3.2/images/jdbc_class_relationships.png diff --git a/product_docs/docs/jdbc_connector/42.7.3.1/images/the_showemployees_window.png b/product_docs/docs/jdbc_connector/42.7.3.2/images/the_showemployees_window.png similarity index 100% rename from product_docs/docs/jdbc_connector/42.7.3.1/images/the_showemployees_window.png rename to product_docs/docs/jdbc_connector/42.7.3.2/images/the_showemployees_window.png diff --git a/product_docs/docs/jdbc_connector/42.7.3.1/index.mdx b/product_docs/docs/jdbc_connector/42.7.3.2/index.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.7.3.1/index.mdx rename to product_docs/docs/jdbc_connector/42.7.3.2/index.mdx diff --git a/product_docs/docs/jdbc_connector/42.7.3.1/installing/configuring_for_java.mdx b/product_docs/docs/jdbc_connector/42.7.3.2/installing/configuring_for_java.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.7.3.1/installing/configuring_for_java.mdx rename to product_docs/docs/jdbc_connector/42.7.3.2/installing/configuring_for_java.mdx diff --git a/product_docs/docs/jdbc_connector/42.7.3.1/installing/index.mdx b/product_docs/docs/jdbc_connector/42.7.3.2/installing/index.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.7.3.1/installing/index.mdx rename to product_docs/docs/jdbc_connector/42.7.3.2/installing/index.mdx diff --git a/product_docs/docs/jdbc_connector/42.7.3.1/installing/linux_arm64/index.mdx b/product_docs/docs/jdbc_connector/42.7.3.2/installing/linux_arm64/index.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.7.3.1/installing/linux_arm64/index.mdx rename to product_docs/docs/jdbc_connector/42.7.3.2/installing/linux_arm64/index.mdx diff --git a/product_docs/docs/jdbc_connector/42.7.3.1/installing/linux_arm64/jdbc_debian_12.mdx b/product_docs/docs/jdbc_connector/42.7.3.2/installing/linux_arm64/jdbc_debian_12.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.7.3.1/installing/linux_arm64/jdbc_debian_12.mdx rename to product_docs/docs/jdbc_connector/42.7.3.2/installing/linux_arm64/jdbc_debian_12.mdx diff --git a/product_docs/docs/jdbc_connector/42.7.3.1/installing/linux_ppc64le/index.mdx b/product_docs/docs/jdbc_connector/42.7.3.2/installing/linux_ppc64le/index.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.7.3.1/installing/linux_ppc64le/index.mdx rename to product_docs/docs/jdbc_connector/42.7.3.2/installing/linux_ppc64le/index.mdx diff --git a/product_docs/docs/jdbc_connector/42.7.3.1/installing/linux_ppc64le/jdbc_rhel_8.mdx b/product_docs/docs/jdbc_connector/42.7.3.2/installing/linux_ppc64le/jdbc_rhel_8.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.7.3.1/installing/linux_ppc64le/jdbc_rhel_8.mdx rename to product_docs/docs/jdbc_connector/42.7.3.2/installing/linux_ppc64le/jdbc_rhel_8.mdx diff --git a/product_docs/docs/jdbc_connector/42.7.3.1/installing/linux_ppc64le/jdbc_rhel_9.mdx b/product_docs/docs/jdbc_connector/42.7.3.2/installing/linux_ppc64le/jdbc_rhel_9.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.7.3.1/installing/linux_ppc64le/jdbc_rhel_9.mdx rename to product_docs/docs/jdbc_connector/42.7.3.2/installing/linux_ppc64le/jdbc_rhel_9.mdx diff --git a/product_docs/docs/jdbc_connector/42.7.3.1/installing/linux_ppc64le/jdbc_sles_12.mdx b/product_docs/docs/jdbc_connector/42.7.3.2/installing/linux_ppc64le/jdbc_sles_12.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.7.3.1/installing/linux_ppc64le/jdbc_sles_12.mdx rename to product_docs/docs/jdbc_connector/42.7.3.2/installing/linux_ppc64le/jdbc_sles_12.mdx diff --git a/product_docs/docs/jdbc_connector/42.7.3.1/installing/linux_ppc64le/jdbc_sles_15.mdx b/product_docs/docs/jdbc_connector/42.7.3.2/installing/linux_ppc64le/jdbc_sles_15.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.7.3.1/installing/linux_ppc64le/jdbc_sles_15.mdx rename to product_docs/docs/jdbc_connector/42.7.3.2/installing/linux_ppc64le/jdbc_sles_15.mdx diff --git a/product_docs/docs/jdbc_connector/42.7.3.1/installing/linux_x86_64/index.mdx b/product_docs/docs/jdbc_connector/42.7.3.2/installing/linux_x86_64/index.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.7.3.1/installing/linux_x86_64/index.mdx rename to product_docs/docs/jdbc_connector/42.7.3.2/installing/linux_x86_64/index.mdx diff --git a/product_docs/docs/jdbc_connector/42.7.3.1/installing/linux_x86_64/jdbc_debian_11.mdx b/product_docs/docs/jdbc_connector/42.7.3.2/installing/linux_x86_64/jdbc_debian_11.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.7.3.1/installing/linux_x86_64/jdbc_debian_11.mdx rename to product_docs/docs/jdbc_connector/42.7.3.2/installing/linux_x86_64/jdbc_debian_11.mdx diff --git a/product_docs/docs/jdbc_connector/42.7.3.1/installing/linux_x86_64/jdbc_debian_12.mdx b/product_docs/docs/jdbc_connector/42.7.3.2/installing/linux_x86_64/jdbc_debian_12.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.7.3.1/installing/linux_x86_64/jdbc_debian_12.mdx rename to product_docs/docs/jdbc_connector/42.7.3.2/installing/linux_x86_64/jdbc_debian_12.mdx diff --git a/product_docs/docs/jdbc_connector/42.7.3.1/installing/linux_x86_64/jdbc_other_linux_8.mdx b/product_docs/docs/jdbc_connector/42.7.3.2/installing/linux_x86_64/jdbc_other_linux_8.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.7.3.1/installing/linux_x86_64/jdbc_other_linux_8.mdx rename to product_docs/docs/jdbc_connector/42.7.3.2/installing/linux_x86_64/jdbc_other_linux_8.mdx diff --git a/product_docs/docs/jdbc_connector/42.7.3.1/installing/linux_x86_64/jdbc_other_linux_9.mdx b/product_docs/docs/jdbc_connector/42.7.3.2/installing/linux_x86_64/jdbc_other_linux_9.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.7.3.1/installing/linux_x86_64/jdbc_other_linux_9.mdx rename to product_docs/docs/jdbc_connector/42.7.3.2/installing/linux_x86_64/jdbc_other_linux_9.mdx diff --git a/product_docs/docs/jdbc_connector/42.7.3.1/installing/linux_x86_64/jdbc_rhel_8.mdx b/product_docs/docs/jdbc_connector/42.7.3.2/installing/linux_x86_64/jdbc_rhel_8.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.7.3.1/installing/linux_x86_64/jdbc_rhel_8.mdx rename to product_docs/docs/jdbc_connector/42.7.3.2/installing/linux_x86_64/jdbc_rhel_8.mdx diff --git a/product_docs/docs/jdbc_connector/42.7.3.1/installing/linux_x86_64/jdbc_rhel_9.mdx b/product_docs/docs/jdbc_connector/42.7.3.2/installing/linux_x86_64/jdbc_rhel_9.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.7.3.1/installing/linux_x86_64/jdbc_rhel_9.mdx rename to product_docs/docs/jdbc_connector/42.7.3.2/installing/linux_x86_64/jdbc_rhel_9.mdx diff --git a/product_docs/docs/jdbc_connector/42.7.3.1/installing/linux_x86_64/jdbc_sles_12.mdx b/product_docs/docs/jdbc_connector/42.7.3.2/installing/linux_x86_64/jdbc_sles_12.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.7.3.1/installing/linux_x86_64/jdbc_sles_12.mdx rename to product_docs/docs/jdbc_connector/42.7.3.2/installing/linux_x86_64/jdbc_sles_12.mdx diff --git a/product_docs/docs/jdbc_connector/42.7.3.1/installing/linux_x86_64/jdbc_sles_15.mdx b/product_docs/docs/jdbc_connector/42.7.3.2/installing/linux_x86_64/jdbc_sles_15.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.7.3.1/installing/linux_x86_64/jdbc_sles_15.mdx rename to product_docs/docs/jdbc_connector/42.7.3.2/installing/linux_x86_64/jdbc_sles_15.mdx diff --git a/product_docs/docs/jdbc_connector/42.7.3.1/installing/linux_x86_64/jdbc_ubuntu_20.mdx b/product_docs/docs/jdbc_connector/42.7.3.2/installing/linux_x86_64/jdbc_ubuntu_20.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.7.3.1/installing/linux_x86_64/jdbc_ubuntu_20.mdx rename to product_docs/docs/jdbc_connector/42.7.3.2/installing/linux_x86_64/jdbc_ubuntu_20.mdx diff --git a/product_docs/docs/jdbc_connector/42.7.3.1/installing/linux_x86_64/jdbc_ubuntu_22.mdx b/product_docs/docs/jdbc_connector/42.7.3.2/installing/linux_x86_64/jdbc_ubuntu_22.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.7.3.1/installing/linux_x86_64/jdbc_ubuntu_22.mdx rename to product_docs/docs/jdbc_connector/42.7.3.2/installing/linux_x86_64/jdbc_ubuntu_22.mdx diff --git a/product_docs/docs/jdbc_connector/42.7.3.1/installing/upgrading.mdx b/product_docs/docs/jdbc_connector/42.7.3.2/installing/upgrading.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.7.3.1/installing/upgrading.mdx rename to product_docs/docs/jdbc_connector/42.7.3.2/installing/upgrading.mdx diff --git a/product_docs/docs/jdbc_connector/42.7.3.1/installing/using_maven.mdx b/product_docs/docs/jdbc_connector/42.7.3.2/installing/using_maven.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.7.3.1/installing/using_maven.mdx rename to product_docs/docs/jdbc_connector/42.7.3.2/installing/using_maven.mdx diff --git a/product_docs/docs/jdbc_connector/42.7.3.1/installing/windows.mdx b/product_docs/docs/jdbc_connector/42.7.3.2/installing/windows.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.7.3.1/installing/windows.mdx rename to product_docs/docs/jdbc_connector/42.7.3.2/installing/windows.mdx From fe451bdae7856c29d6179f4b3a148ab9d409a77e Mon Sep 17 00:00:00 2001 From: Josh Earlenbaugh Date: Mon, 18 Nov 2024 12:37:14 -0500 Subject: [PATCH 05/24] Changed old version reference --- product_docs/docs/jdbc_connector/42.7.3.2/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/jdbc_connector/42.7.3.2/index.mdx b/product_docs/docs/jdbc_connector/42.7.3.2/index.mdx index d278b1b4ec3..59e60b90d46 100644 --- a/product_docs/docs/jdbc_connector/42.7.3.2/index.mdx +++ b/product_docs/docs/jdbc_connector/42.7.3.2/index.mdx @@ -1,7 +1,7 @@ --- title: "EDB JDBC Connector" directoryDefaults: - description: "EDB JDBC Connector Version 42.7.3.1 Documentation and release notes." + description: "EDB JDBC Connector Version 42.7.3.2 Documentation and release notes." navigation: - 01_jdbc_rel_notes - 02_requirements_overview From 1f3ae19deb59f39cc4a30111f1cfbf42ec46d72f Mon Sep 17 00:00:00 2001 From: Josh Earlenbaugh Date: Mon, 18 Nov 2024 13:31:08 -0500 Subject: [PATCH 06/24] Added release notes and updated support table. --- .../42.7.3.2/01_jdbc_rel_notes/index.mdx | 2 ++ .../jdbc_42.7.3.2_rel_notes.mdx | 33 +++++++++++++++++++ .../42.7.3.2/02_requirements_overview.mdx | 31 ++++++++--------- 3 files changed, 51 insertions(+), 15 deletions(-) create mode 100644 product_docs/docs/jdbc_connector/42.7.3.2/01_jdbc_rel_notes/jdbc_42.7.3.2_rel_notes.mdx diff --git a/product_docs/docs/jdbc_connector/42.7.3.2/01_jdbc_rel_notes/index.mdx b/product_docs/docs/jdbc_connector/42.7.3.2/01_jdbc_rel_notes/index.mdx index 5b204e63be2..30d732b5144 100644 --- a/product_docs/docs/jdbc_connector/42.7.3.2/01_jdbc_rel_notes/index.mdx +++ b/product_docs/docs/jdbc_connector/42.7.3.2/01_jdbc_rel_notes/index.mdx @@ -1,6 +1,7 @@ --- title: "Release notes" navigation: +- jdbc_42.7.3.2_rel_notes - jdbc_42.7.3.1_rel_notes - jdbc_42.5.4.2_rel_notes - jdbc_42.5.4.1_rel_notes @@ -15,6 +16,7 @@ These release notes describe what's new in each release. When a minor or patch r | Version | Release Date | | ---------------------------------------- | ------------ | +| [42.7.3.2](jdbc_42.7.3.2_rel_notes) | 20 Nov 2024 | | [42.7.3.1](jdbc_42.7.3.1_rel_notes) | 10 Sep 2024 | | [42.5.4.2](jdbc_42.5.4.2_rel_notes) | 26 Feb 2024 | | [42.5.4.1](jdbc_42.5.4.1_rel_notes) | 16 Mar 2023 | diff --git a/product_docs/docs/jdbc_connector/42.7.3.2/01_jdbc_rel_notes/jdbc_42.7.3.2_rel_notes.mdx b/product_docs/docs/jdbc_connector/42.7.3.2/01_jdbc_rel_notes/jdbc_42.7.3.2_rel_notes.mdx new file mode 100644 index 00000000000..0cad6a388e1 --- /dev/null +++ b/product_docs/docs/jdbc_connector/42.7.3.2/01_jdbc_rel_notes/jdbc_42.7.3.2_rel_notes.mdx @@ -0,0 +1,33 @@ +--- +title: "EDB JDBC Connector 42.7.3.2 release notes" +navTitle: Version 42.7.3.2 +--- + +Released: 20 Nov 2024 + +The EDB JDBC connector provides connectivity between a Java application and an EDB Postgres Advanced Server database. + +New features, enhancements, bug fixes, and other changes in the EDB JDBC Connector 42.7.3.2 include: + +| Type | Description +|---------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Performance | Improved parsing performance with large SQL (MTK/SQL Plus) | +| Enhancement | Added support for EDB Postgres Advanced Server 17.2 | +| Fix | The JDK 8 compatibility is broken in ver 42.7.3.1 of edb-jdbc18 driver. | +| Fix | edb-jdbc installation should not install a lower JDK version when a higher version is installed. | +| Fix | Fixed issue where Message.getJMSMessageID() returns null. | +| Fix | Fixed issue with determining the queue table for a queue when there is more than one queue defined within a single schema. | +| Fix | Fixed issue where EDBJmsMessageConsumer.receiveNoWait() always returns null even when messages are available on the queue. +| Fix | Fixed issue where EDBJmsMessageConsuder() [without time parameter] is supposed to block until a message is available. | + + + + + + + + + + + + diff --git a/product_docs/docs/jdbc_connector/42.7.3.2/02_requirements_overview.mdx b/product_docs/docs/jdbc_connector/42.7.3.2/02_requirements_overview.mdx index 35ca32891ad..8bea627e606 100644 --- a/product_docs/docs/jdbc_connector/42.7.3.2/02_requirements_overview.mdx +++ b/product_docs/docs/jdbc_connector/42.7.3.2/02_requirements_overview.mdx @@ -17,21 +17,22 @@ The JDBC Connector is supported on the same platforms as EDB Postgres Advanced S This table lists the latest JDBC Connector versions and their supported corresponding EDB Postgres Advanced Server (EPAS) versions. -| JDBC Connector | EPAS16 | EPAS 15 | EPAS 14 | EPAS 13 | EPAS 12 | EPAS 11 | -| ---------------------------------------------------------- | --------|-------- | ------- | ------- | ------- | ------- | -| [42.7.3.1](01_jdbc_rel_notes/jdbc_42.7.3.1_rel_notes) | Y | Y | Y | Y | Y | N | -| [42.5.4.2](01_jdbc_rel_notes/jdbc_42.5.4.2_rel_notes) | Y | Y | Y | Y | Y | Y | -| [42.5.4.1](01_jdbc_rel_notes/jdbc_42.5.4.1_rel_notes) | N | Y | Y | Y | Y | Y | -| [42.5.1.2](01_jdbc_rel_notes/jdbc_42.5.1.2_rel_notes) | N | Y | Y | Y | Y | Y | -| [42.5.1.1](01_jdbc_rel_notes/jdbc_42.5.1.1_rel_notes) | N | N | Y | Y | Y | Y | -| [42.5.0.1](01_jdbc_rel_notes/jdbc_42.5.0.1_rel_notes) | N | N | Y | Y | Y | Y | -| [42.3.3.1](01_jdbc_rel_notes/08_jdbc_42.3.3.1_rel_notes) | N | N | Y | Y | Y | Y | -| [42.3.2.1](01_jdbc_rel_notes/09_jdbc_42.3.2.1_rel_notes) | N | N | Y | Y | Y | Y | -| [42.2.24.1](01_jdbc_rel_notes/10_jdbc_42.2.24.1_rel_notes) | N | N | Y | Y | Y | Y | -| [42.2.19.1](01_jdbc_rel_notes/12_jdbc_42.2.19.1_rel_notes) | N | N | N | Y | Y | Y | -| [42.2.12.3](01_jdbc_rel_notes/14_jdbc_42.2.12.3_rel_notes) | N | N | N | Y | Y | Y | -| [42.2.9.1](01_jdbc_rel_notes/16_jdbc_42.2.9.1_rel_notes) | N | N | N | N | Y | Y | -| [42.2.8.1](01_jdbc_rel_notes/18_jdbc_42.2.8.1_rel_notes) | N | N | N | N | Y | Y | +| JDBC Connector | EPAS17 | EPAS16 | EPAS 15 | EPAS 14 | EPAS 13 | EPAS 12 | +| ---------------------------------------------------------- |--------|--------|-------- | ------- | ------- | ------- | +| [42.7.3.2](01_jdbc_rel_notes/jdbc_42.7.3.2_rel_notes) | Y | Y | Y | Y | Y | Y | +| [42.7.3.1](01_jdbc_rel_notes/jdbc_42.7.3.1_rel_notes) | N | Y | Y | Y | Y | Y | +| [42.5.4.2](01_jdbc_rel_notes/jdbc_42.5.4.2_rel_notes) | N | Y | Y | Y | Y | Y | +| [42.5.4.1](01_jdbc_rel_notes/jdbc_42.5.4.1_rel_notes) | N | N | Y | Y | Y | Y | +| [42.5.1.2](01_jdbc_rel_notes/jdbc_42.5.1.2_rel_notes) | N | N | Y | Y | Y | Y | +| [42.5.1.1](01_jdbc_rel_notes/jdbc_42.5.1.1_rel_notes) | N | N | N | Y | Y | Y | +| [42.5.0.1](01_jdbc_rel_notes/jdbc_42.5.0.1_rel_notes) | N | N | N | Y | Y | Y | +| [42.3.3.1](01_jdbc_rel_notes/08_jdbc_42.3.3.1_rel_notes) | N | N | N | Y | Y | Y | +| [42.3.2.1](01_jdbc_rel_notes/09_jdbc_42.3.2.1_rel_notes) | N | N | N | Y | Y | Y | +| [42.2.24.1](01_jdbc_rel_notes/10_jdbc_42.2.24.1_rel_notes) | N | N | N | Y | Y | Y | +| [42.2.19.1](01_jdbc_rel_notes/12_jdbc_42.2.19.1_rel_notes) | N | N | N | N | Y | Y | +| [42.2.12.3](01_jdbc_rel_notes/14_jdbc_42.2.12.3_rel_notes) | N | N | N | N | Y | Y | +| [42.2.9.1](01_jdbc_rel_notes/16_jdbc_42.2.9.1_rel_notes) | N | N | N | N | N | Y | +| [42.2.8.1](01_jdbc_rel_notes/18_jdbc_42.2.8.1_rel_notes) | N | N | N | N | N | Y | ## Supported JDK distribution From 8411036a8bf61b65754a847ab714b01d25ea4546 Mon Sep 17 00:00:00 2001 From: Josh Earlenbaugh Date: Tue, 19 Nov 2024 13:49:33 -0500 Subject: [PATCH 07/24] Update product_docs/docs/jdbc_connector/42.7.3.2/01_jdbc_rel_notes/jdbc_42.7.3.2_rel_notes.mdx Co-authored-by: gvasquezvargas --- .../42.7.3.2/01_jdbc_rel_notes/jdbc_42.7.3.2_rel_notes.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/jdbc_connector/42.7.3.2/01_jdbc_rel_notes/jdbc_42.7.3.2_rel_notes.mdx b/product_docs/docs/jdbc_connector/42.7.3.2/01_jdbc_rel_notes/jdbc_42.7.3.2_rel_notes.mdx index 0cad6a388e1..18aa20bb043 100644 --- a/product_docs/docs/jdbc_connector/42.7.3.2/01_jdbc_rel_notes/jdbc_42.7.3.2_rel_notes.mdx +++ b/product_docs/docs/jdbc_connector/42.7.3.2/01_jdbc_rel_notes/jdbc_42.7.3.2_rel_notes.mdx @@ -13,7 +13,7 @@ New features, enhancements, bug fixes, and other changes in the EDB JDBC Connect |---------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Performance | Improved parsing performance with large SQL (MTK/SQL Plus) | | Enhancement | Added support for EDB Postgres Advanced Server 17.2 | -| Fix | The JDK 8 compatibility is broken in ver 42.7.3.1 of edb-jdbc18 driver. | +| Bug fix | Fixes an incompatibility issue with JDK 8 that found in version 42.7.3.1 of the `edb-jdbc18` driver. | | Fix | edb-jdbc installation should not install a lower JDK version when a higher version is installed. | | Fix | Fixed issue where Message.getJMSMessageID() returns null. | | Fix | Fixed issue with determining the queue table for a queue when there is more than one queue defined within a single schema. | From be59199140eed57d57ecd997645e55404e65d051 Mon Sep 17 00:00:00 2001 From: Josh Earlenbaugh Date: Tue, 19 Nov 2024 13:50:21 -0500 Subject: [PATCH 08/24] Update product_docs/docs/jdbc_connector/42.7.3.2/01_jdbc_rel_notes/jdbc_42.7.3.2_rel_notes.mdx Co-authored-by: gvasquezvargas --- .../42.7.3.2/01_jdbc_rel_notes/jdbc_42.7.3.2_rel_notes.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/jdbc_connector/42.7.3.2/01_jdbc_rel_notes/jdbc_42.7.3.2_rel_notes.mdx b/product_docs/docs/jdbc_connector/42.7.3.2/01_jdbc_rel_notes/jdbc_42.7.3.2_rel_notes.mdx index 18aa20bb043..5b81fa27aa9 100644 --- a/product_docs/docs/jdbc_connector/42.7.3.2/01_jdbc_rel_notes/jdbc_42.7.3.2_rel_notes.mdx +++ b/product_docs/docs/jdbc_connector/42.7.3.2/01_jdbc_rel_notes/jdbc_42.7.3.2_rel_notes.mdx @@ -3,7 +3,7 @@ title: "EDB JDBC Connector 42.7.3.2 release notes" navTitle: Version 42.7.3.2 --- -Released: 20 Nov 2024 +Released: 21 Nov 2024 The EDB JDBC connector provides connectivity between a Java application and an EDB Postgres Advanced Server database. From 221c937346c418f78a38466d34abfe1ee5daf71e Mon Sep 17 00:00:00 2001 From: Josh Earlenbaugh Date: Tue, 19 Nov 2024 13:50:29 -0500 Subject: [PATCH 09/24] Update product_docs/docs/jdbc_connector/42.7.3.2/01_jdbc_rel_notes/jdbc_42.7.3.2_rel_notes.mdx Co-authored-by: gvasquezvargas --- .../42.7.3.2/01_jdbc_rel_notes/jdbc_42.7.3.2_rel_notes.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/jdbc_connector/42.7.3.2/01_jdbc_rel_notes/jdbc_42.7.3.2_rel_notes.mdx b/product_docs/docs/jdbc_connector/42.7.3.2/01_jdbc_rel_notes/jdbc_42.7.3.2_rel_notes.mdx index 5b81fa27aa9..f3cf7d9d496 100644 --- a/product_docs/docs/jdbc_connector/42.7.3.2/01_jdbc_rel_notes/jdbc_42.7.3.2_rel_notes.mdx +++ b/product_docs/docs/jdbc_connector/42.7.3.2/01_jdbc_rel_notes/jdbc_42.7.3.2_rel_notes.mdx @@ -15,7 +15,7 @@ New features, enhancements, bug fixes, and other changes in the EDB JDBC Connect | Enhancement | Added support for EDB Postgres Advanced Server 17.2 | | Bug fix | Fixes an incompatibility issue with JDK 8 that found in version 42.7.3.1 of the `edb-jdbc18` driver. | | Fix | edb-jdbc installation should not install a lower JDK version when a higher version is installed. | -| Fix | Fixed issue where Message.getJMSMessageID() returns null. | +| Fix | Fixed issue where `Message.getJMSMessageID()` returns `null`. | | Fix | Fixed issue with determining the queue table for a queue when there is more than one queue defined within a single schema. | | Fix | Fixed issue where EDBJmsMessageConsumer.receiveNoWait() always returns null even when messages are available on the queue. | Fix | Fixed issue where EDBJmsMessageConsuder() [without time parameter] is supposed to block until a message is available. | From 75b4e30bae448571a0fc3be6f68cf486057a7760 Mon Sep 17 00:00:00 2001 From: Josh Earlenbaugh Date: Tue, 19 Nov 2024 13:50:37 -0500 Subject: [PATCH 10/24] Update product_docs/docs/jdbc_connector/42.7.3.2/01_jdbc_rel_notes/jdbc_42.7.3.2_rel_notes.mdx Co-authored-by: gvasquezvargas --- .../42.7.3.2/01_jdbc_rel_notes/jdbc_42.7.3.2_rel_notes.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/jdbc_connector/42.7.3.2/01_jdbc_rel_notes/jdbc_42.7.3.2_rel_notes.mdx b/product_docs/docs/jdbc_connector/42.7.3.2/01_jdbc_rel_notes/jdbc_42.7.3.2_rel_notes.mdx index f3cf7d9d496..1b0cdc0c7af 100644 --- a/product_docs/docs/jdbc_connector/42.7.3.2/01_jdbc_rel_notes/jdbc_42.7.3.2_rel_notes.mdx +++ b/product_docs/docs/jdbc_connector/42.7.3.2/01_jdbc_rel_notes/jdbc_42.7.3.2_rel_notes.mdx @@ -12,7 +12,7 @@ New features, enhancements, bug fixes, and other changes in the EDB JDBC Connect | Type | Description |---------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Performance | Improved parsing performance with large SQL (MTK/SQL Plus) | -| Enhancement | Added support for EDB Postgres Advanced Server 17.2 | +| Enhancement | Added support for EDB Postgres Advanced Server 17.2. | | Bug fix | Fixes an incompatibility issue with JDK 8 that found in version 42.7.3.1 of the `edb-jdbc18` driver. | | Fix | edb-jdbc installation should not install a lower JDK version when a higher version is installed. | | Fix | Fixed issue where `Message.getJMSMessageID()` returns `null`. | From df608024b0eba337ae4ae5cab6244fba36431694 Mon Sep 17 00:00:00 2001 From: Josh Earlenbaugh Date: Tue, 19 Nov 2024 13:50:53 -0500 Subject: [PATCH 11/24] Update product_docs/docs/jdbc_connector/42.7.3.2/01_jdbc_rel_notes/jdbc_42.7.3.2_rel_notes.mdx Co-authored-by: gvasquezvargas --- .../42.7.3.2/01_jdbc_rel_notes/jdbc_42.7.3.2_rel_notes.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/jdbc_connector/42.7.3.2/01_jdbc_rel_notes/jdbc_42.7.3.2_rel_notes.mdx b/product_docs/docs/jdbc_connector/42.7.3.2/01_jdbc_rel_notes/jdbc_42.7.3.2_rel_notes.mdx index 1b0cdc0c7af..ecf74d565f4 100644 --- a/product_docs/docs/jdbc_connector/42.7.3.2/01_jdbc_rel_notes/jdbc_42.7.3.2_rel_notes.mdx +++ b/product_docs/docs/jdbc_connector/42.7.3.2/01_jdbc_rel_notes/jdbc_42.7.3.2_rel_notes.mdx @@ -11,7 +11,7 @@ New features, enhancements, bug fixes, and other changes in the EDB JDBC Connect | Type | Description |---------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Performance | Improved parsing performance with large SQL (MTK/SQL Plus) | +| Performance | Improved parsing performance with large SQL (MTK/SQL Plus). | | Enhancement | Added support for EDB Postgres Advanced Server 17.2. | | Bug fix | Fixes an incompatibility issue with JDK 8 that found in version 42.7.3.1 of the `edb-jdbc18` driver. | | Fix | edb-jdbc installation should not install a lower JDK version when a higher version is installed. | From 239a51538077e92a84cdf260c6b8cd802a83aa54 Mon Sep 17 00:00:00 2001 From: Josh Earlenbaugh Date: Tue, 19 Nov 2024 13:52:05 -0500 Subject: [PATCH 12/24] Update product_docs/docs/ocl_connector/17/ocl_rel_notes/17.2.0.1_ocl_release_notes.mdx Co-authored-by: gvasquezvargas --- .../17/ocl_rel_notes/17.2.0.1_ocl_release_notes.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/ocl_connector/17/ocl_rel_notes/17.2.0.1_ocl_release_notes.mdx b/product_docs/docs/ocl_connector/17/ocl_rel_notes/17.2.0.1_ocl_release_notes.mdx index 5fbd948ca93..5ae514bdb7b 100644 --- a/product_docs/docs/ocl_connector/17/ocl_rel_notes/17.2.0.1_ocl_release_notes.mdx +++ b/product_docs/docs/ocl_connector/17/ocl_rel_notes/17.2.0.1_ocl_release_notes.mdx @@ -3,7 +3,7 @@ title: "EDB OCL Connector 17.2.0.1 release notes" navTitle: Version 17.2.0.1 --- -Released: 20 Nov 2024 +Released: 21 Nov 2024 The EDB OCL Connector provides an API similar to the Oracle Call Interface. From 40efdda62ca6cb005ac977ce9c7ea3cab10dbc7c Mon Sep 17 00:00:00 2001 From: Josh Earlenbaugh Date: Tue, 19 Nov 2024 13:52:17 -0500 Subject: [PATCH 13/24] Update product_docs/docs/ocl_connector/17/ocl_rel_notes/17.2.0.1_ocl_release_notes.mdx Co-authored-by: gvasquezvargas --- .../17/ocl_rel_notes/17.2.0.1_ocl_release_notes.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/ocl_connector/17/ocl_rel_notes/17.2.0.1_ocl_release_notes.mdx b/product_docs/docs/ocl_connector/17/ocl_rel_notes/17.2.0.1_ocl_release_notes.mdx index 5ae514bdb7b..d04eaa81273 100644 --- a/product_docs/docs/ocl_connector/17/ocl_rel_notes/17.2.0.1_ocl_release_notes.mdx +++ b/product_docs/docs/ocl_connector/17/ocl_rel_notes/17.2.0.1_ocl_release_notes.mdx @@ -11,4 +11,4 @@ New features, enhancements, bug fixes, and other changes in the EDB OCL Connecto | Type | Description | | ----------- | ----------------------------------------------------------- | -| Enhancement | Added support for EDB Postgres Advanced Server version 17.2 | +| Enhancement | Added support for EDB Postgres Advanced Server version 17.2. | From 8fa1ce3bd889194826a065580fd0ac74d58da273 Mon Sep 17 00:00:00 2001 From: gvasquezvargas Date: Mon, 18 Nov 2024 11:14:31 +0100 Subject: [PATCH 14/24] EPRS:added PG and EPAS 17 support --- .../7/01_introduction/03_certified_supported_versions.mdx | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) 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 03dd21a7639..ec035a962d2 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 @@ -4,8 +4,8 @@ title: "Certified and supported product versions" You can use the following database product versions with Replication Server: -- PostgreSQL versions 12, 13, 14, 15, and 16 -- EDB Postgres Advanced Server versions 12, 13, 14, 15, and 16 +- PostgreSQL versions 12, 13, 14, 15, 16 and 17 +- EDB Postgres Advanced Server versions 12, 13, 14, 15, 16 and 17 - Oracle 11g Release 2 version 11.2.0.2.0 is explicitly certified. Newer minor versions in the 11.2 line are supported as well. - Oracle 12c version 12.1.0.2.0 is explicitly certified. Newer minor versions in the 12.1 line are supported as well. - Oracle 18c version 18.1.0.2.0 is explicitly certified. Newer minor versions in the 18.1 line are supported as well. @@ -16,7 +16,7 @@ You can use the following database product versions with Replication Server: All PostgreSQL and EDB Postgres Advanced Server versions available as EDB Postgres AI Cloud Service single-node and primary/standby high-availability cluster types are also supported for SMR configurations. See the Cloud Service [documentation](/edb-postgres-ai/cloud-service/) for more information about Cloud Service’s [supported cluster types](/edb-postgres-ai/cloud-service/references/supported_cluster_types/). See the [database version policy documentation](/edb-postgres-ai/cloud-service/references/supported_database_versions/) for the versions of PostgreSQL and EDB Postgres Advanced Server available in Cloud Service. -EDB Postgres Distributed (PGD) v5.3.0 is explicitly certified as a Publishing database for trigger mode and as Subscription database for both trigger and wal modes. +EDB Postgres Distributed (PGD) v5.6.0 is explicitly certified as a Publishing database for trigger mode and as Subscription database for both trigger and wal modes. !!! As of Replication Server 7.1.0: From a4491efb318cb6b32d782e9023baba14fe771e17 Mon Sep 17 00:00:00 2001 From: gvasquezvargas Date: Mon, 18 Nov 2024 16:31:01 +0100 Subject: [PATCH 15/24] Dropped v12 support due to n -4 support --- .../7/01_introduction/03_certified_supported_versions.mdx | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) 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 ec035a962d2..4629e17a11c 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 @@ -4,8 +4,8 @@ title: "Certified and supported product versions" You can use the following database product versions with Replication Server: -- PostgreSQL versions 12, 13, 14, 15, 16 and 17 -- EDB Postgres Advanced Server versions 12, 13, 14, 15, 16 and 17 +- PostgreSQL versions 13, 14, 15, 16, and 17 +- EDB Postgres Advanced Server versions 13, 14, 15, 16, and 17 - Oracle 11g Release 2 version 11.2.0.2.0 is explicitly certified. Newer minor versions in the 11.2 line are supported as well. - Oracle 12c version 12.1.0.2.0 is explicitly certified. Newer minor versions in the 12.1 line are supported as well. - Oracle 18c version 18.1.0.2.0 is explicitly certified. Newer minor versions in the 18.1 line are supported as well. @@ -16,7 +16,7 @@ You can use the following database product versions with Replication Server: All PostgreSQL and EDB Postgres Advanced Server versions available as EDB Postgres AI Cloud Service single-node and primary/standby high-availability cluster types are also supported for SMR configurations. See the Cloud Service [documentation](/edb-postgres-ai/cloud-service/) for more information about Cloud Service’s [supported cluster types](/edb-postgres-ai/cloud-service/references/supported_cluster_types/). See the [database version policy documentation](/edb-postgres-ai/cloud-service/references/supported_database_versions/) for the versions of PostgreSQL and EDB Postgres Advanced Server available in Cloud Service. -EDB Postgres Distributed (PGD) v5.6.0 is explicitly certified as a Publishing database for trigger mode and as Subscription database for both trigger and wal modes. +EDB Postgres Distributed (PGD) v5.3.0 is explicitly certified as a Publishing database for trigger mode and as Subscription database for both trigger and wal modes. !!! As of Replication Server 7.1.0: From c82ff15e6ef7e7c538a1ce85a98876405e310071 Mon Sep 17 00:00:00 2001 From: gvasquezvargas Date: Tue, 19 Nov 2024 12:33:46 +0100 Subject: [PATCH 16/24] EPRS: added relase notes for 7.10 --- .../eprs_rel_notes/eprs_rel_notes_7.10.0.mdx | 37 +++++++++++++++++++ .../docs/eprs/7/eprs_rel_notes/index.mdx | 2 + 2 files changed, 39 insertions(+) create mode 100644 product_docs/docs/eprs/7/eprs_rel_notes/eprs_rel_notes_7.10.0.mdx diff --git a/product_docs/docs/eprs/7/eprs_rel_notes/eprs_rel_notes_7.10.0.mdx b/product_docs/docs/eprs/7/eprs_rel_notes/eprs_rel_notes_7.10.0.mdx new file mode 100644 index 00000000000..81983306a18 --- /dev/null +++ b/product_docs/docs/eprs/7/eprs_rel_notes/eprs_rel_notes_7.10.0.mdx @@ -0,0 +1,37 @@ +--- +title: "Replication Server 7.10.0 release notes" +navTitle: Version 7.10.0 +--- + +Released: 21 Nov 2024 + +New features, enhancements, bug fixes, and other changes in Replication Server 7.10.0 include the following: + +| Type | Description | Ticket | +|--------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------| +| Enhancement | EDB Postgres Replication Server (EPRS) is now certified to work with EDB Postgres Advanced Server version 17 and PostgreSQL version 17, both as source Publication and/or target Subscription databases in trigger and WAL based replication cluster configurations. | | +| Enhancement | Enhanced to map virtual columns in the source database to virtual columns in the target database for all supported databases. | #38897 | +| Bug fix | Fixed a corner case issue for an MMR cluster where conflicts were not detected, resulting in inconsistent data in the cluster. | #39369 | +| Bug fix | Fixed an issue that caused inconsistencies when mapping Oracle `DATE` to `TIMESTAMP WITHOUT TIME ZONE` for PostgreSQL target databases. | #39901 | +| Bug fix | Fixed a corner case issue where parallel snapshot parameters were ignored for certain values. | #40191 | + +## Windows installer availability + +EDB Postgres Replication Server (EPRS) version 7.10.0 is currently available for deployment on the supported Linux distributions. The Windows installer will be made available for download from the EDB website a few days after the Linux packages. + +## End-of-support notice + +Replication Server 6.2 is no longer a supported version. + +To ensure that your usage of Replication Server is supported, upgrade any installations with version 6.2 to version 7. See the end-of-support notes that follow: + +**Software:** Replication Server + +**Version:** 6.2 + +**End of Standard Support:** June 1, 2023 + +Additional details can be found at [EDB Platform Compatibility](https://www.enterprisedb.com/resources/platform-compatibility). + +!!! Note + Version 7.x provides a non-breaking upgrade path for existing 6.2.x-based cluster deployments. However, we strongly recommend that the upgrade be verified in a staging or non-production environment before applying the upgrade in a production environment. diff --git a/product_docs/docs/eprs/7/eprs_rel_notes/index.mdx b/product_docs/docs/eprs/7/eprs_rel_notes/index.mdx index 5cc7b44f0b7..723e271bda3 100644 --- a/product_docs/docs/eprs/7/eprs_rel_notes/index.mdx +++ b/product_docs/docs/eprs/7/eprs_rel_notes/index.mdx @@ -3,6 +3,7 @@ title: "Release notes" redirects: - ../01_whats_new/ navigation: + - eprs_rel_notes_7.10.0 - eprs_rel_notes_7.9.0 - eprs_rel_notes_7.8.0 - eprs_rel_notes_7.7.0 @@ -17,6 +18,7 @@ The Replication Server documentation describes the latest version including mino | Version | Release Date | |----------------------------------|--------------| +| [7.10.0](eprs_rel_notes_7.10.0) | 21 Nov 2024 | | [7.9.0](eprs_rel_notes_7.9.0) | 22 Aug 2024 | | [7.8.0](eprs_rel_notes_7.8.0) | 17 May 2024 | | [7.7.0](eprs_rel_notes_7.7.0) | 14 Dec 2023 | From 00779c6a6ac9abe311a12f192eb431abc672a14a Mon Sep 17 00:00:00 2001 From: gvasquezvargas Date: Fri, 22 Nov 2024 10:39:53 +0100 Subject: [PATCH 17/24] Updated release date --- .../docs/eprs/7/eprs_rel_notes/eprs_rel_notes_7.10.0.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/eprs/7/eprs_rel_notes/eprs_rel_notes_7.10.0.mdx b/product_docs/docs/eprs/7/eprs_rel_notes/eprs_rel_notes_7.10.0.mdx index 81983306a18..98ce98e2ce2 100644 --- a/product_docs/docs/eprs/7/eprs_rel_notes/eprs_rel_notes_7.10.0.mdx +++ b/product_docs/docs/eprs/7/eprs_rel_notes/eprs_rel_notes_7.10.0.mdx @@ -3,7 +3,7 @@ title: "Replication Server 7.10.0 release notes" navTitle: Version 7.10.0 --- -Released: 21 Nov 2024 +Released: 22 Nov 2024 New features, enhancements, bug fixes, and other changes in Replication Server 7.10.0 include the following: From 4d4b1bd11d08a5610927a7f2b1cdf4a730009c67 Mon Sep 17 00:00:00 2001 From: gvasquezvargas Date: Fri, 22 Nov 2024 10:40:24 +0100 Subject: [PATCH 18/24] Updated release date in index --- product_docs/docs/eprs/7/eprs_rel_notes/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/eprs/7/eprs_rel_notes/index.mdx b/product_docs/docs/eprs/7/eprs_rel_notes/index.mdx index 723e271bda3..d9543443615 100644 --- a/product_docs/docs/eprs/7/eprs_rel_notes/index.mdx +++ b/product_docs/docs/eprs/7/eprs_rel_notes/index.mdx @@ -18,7 +18,7 @@ The Replication Server documentation describes the latest version including mino | Version | Release Date | |----------------------------------|--------------| -| [7.10.0](eprs_rel_notes_7.10.0) | 21 Nov 2024 | +| [7.10.0](eprs_rel_notes_7.10.0) | 22 Nov 2024 | | [7.9.0](eprs_rel_notes_7.9.0) | 22 Aug 2024 | | [7.8.0](eprs_rel_notes_7.8.0) | 17 May 2024 | | [7.7.0](eprs_rel_notes_7.7.0) | 14 Dec 2023 | From ebbc25ecc565e80cf342cd85cd549671320c6ff0 Mon Sep 17 00:00:00 2001 From: gvasquezvargas Date: Fri, 22 Nov 2024 14:43:55 +0100 Subject: [PATCH 19/24] Fixed links in EPAS --- .../17/epas_rel_notes/epas17_2_rel_notes.mdx | 34 +++++++++---------- .../02_data_types/06_xml_type.mdx | 16 ++++----- 2 files changed, 25 insertions(+), 25 deletions(-) diff --git a/product_docs/docs/epas/17/epas_rel_notes/epas17_2_rel_notes.mdx b/product_docs/docs/epas/17/epas_rel_notes/epas17_2_rel_notes.mdx index bd9b4913f68..fa8e3ce50bf 100644 --- a/product_docs/docs/epas/17/epas_rel_notes/epas17_2_rel_notes.mdx +++ b/product_docs/docs/epas/17/epas_rel_notes/epas17_2_rel_notes.mdx @@ -15,20 +15,20 @@ With the release of EPAS 17, the DRITA is being deprecated and will not be inclu The `pgAgent` and `adminpack` packages are end of life from EPAS 17 and later. !!! -| Type | Description | Category | -|----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------| -| Upstream merge | Merged with community PostgreSQL 17.2. See the [PostgreSQL 17 Release Notes](https://www.postgresql.org/docs/17/release-17-2.html) for more information. | | -| Feature | Added support for the Oracle-compatible `BFILE` native datatype and the `DBMS_LOB` package APIs. See the [DBMS_LOB](../reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/06_dbms_lob/) for more information. | | -| Feature | Added support for the Oracle-compatible `DBMS_XMLDOM` package to provide interface for HTML and XML documents. See the [DBMS_XMLDOM](../reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/dbms_xmldom) for more information. | | -| Feature | Added support for the Oracle-compatible `DBMS_ASSERT` package to validate input properties and sanitize user input, thereby reducing the risk of SQL injections. See the [DBMS_ASSERT](../reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/dbms_assert) for more information. | | -| Feature | Added support for the Oracle-equivalent `NLS_UPPER`,`NLS_LOWER`, and `NLS_INITCAP` functions. See the [NLS functions](../reference/sql_reference/03_functions_and_operators/nls_functions) for more information. | | -| Feature | Implemented `alteruser` utility to modify roles in the clusters. See the [alteruser utility](/tools/alteruser_utility/) for more information. | | -| Enhancement | Added support for the Oracle-compatible `FORALL..MERGE` and `FORALL..SAVE EXCEPTIONS`. See the [FORALL statement](../application_programming/epas_compat_spl/12_working_with_collections/03_using_the_forall_statement/) for more information. | | -| Enhancement | Added support for the `XMLType` data type to be called as an object type and has predefined member functions and constructors on it. See the [XMLType datatype](../reference/sql_reference/02_data_types/06_xml_type) for more information. | | -| Enhancement | Added support for JSON log format in the EDB Auditing. This enables to create audit reports in XML, CSV, or JSON format. | | -| Enhancement | Added support for READ and WRITE privileges for the directory objects. | | -| Enhancement | Added support for READ and WRITE directory permissions in UTL_FILE APIs. | | -| Enhancement | Implemented `IMPORT FOREIGN SCHEMA`. This command imports a foreign schema from a foreign server or a database link. | | -| Enhancement | Added support for `ANYCOMPATIBLE` and "any" pseudo type to NVL function. This allows NVL function to support more types of argument combinations now. | | -| Enhancement | Added support to audit all the EDB Postgres Advanced Server's modified external function signatures so that PostgreSQL compatible extensions can be compiled along with EDB Postgres Advanced Server. | | -| Enhancement | EDB*Loader: Enhanced terminator and delimiter matching behavior to consider the server encoding. | | +| Type | Description | Category | +|----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------| +| Upstream merge | Merged with community PostgreSQL 17.2. See the [PostgreSQL 17 Release Notes](https://www.postgresql.org/docs/17/release-17-2.html) for more information. | | +| Feature | Added support for the Oracle-compatible `BFILE` native datatype and the `DBMS_LOB` package APIs. See the [DBMS_LOB](../reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/06_dbms_lob/) for more information. | | +| Feature | Added support for the Oracle-compatible `DBMS_XMLDOM` package to provide interface for HTML and XML documents. See the [DBMS_XMLDOM](../reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/dbms_xmldom) for more information. | | +| Feature | Added support for the Oracle-compatible `DBMS_ASSERT` package to validate input properties and sanitize user input, thereby reducing the risk of SQL injections. See the [DBMS_ASSERT](../reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/01a_dbms_assert) for more information. | | +| Feature | Added support for the Oracle-equivalent `NLS_UPPER`,`NLS_LOWER`, and `NLS_INITCAP` functions. See the [NLS functions](../reference/sql_reference/03_functions_and_operators/nls_functions) for more information. | | +| Feature | Implemented `alteruser` utility to modify roles in the clusters. See the [alteruser utility](/tools/alteruser_utility/) for more information. | | +| Enhancement | Added support for the Oracle-compatible `FORALL..MERGE` and `FORALL..SAVE EXCEPTIONS`. See the [FORALL statement](../application_programming/epas_compat_spl/12_working_with_collections/03_using_the_forall_statement/) for more information. | | +| Enhancement | Added support for the `XMLType` data type to be called as an object type and has predefined member functions and constructors on it. See the [XMLType datatype](../reference/sql_reference/02_data_types/06_xml_type) for more information. | | +| Enhancement | Added support for JSON log format in the EDB Auditing. This enables to create audit reports in XML, CSV, or JSON format. | | +| Enhancement | Added support for READ and WRITE privileges for the directory objects. | | +| Enhancement | Added support for READ and WRITE directory permissions in UTL_FILE APIs. | | +| Enhancement | Implemented `IMPORT FOREIGN SCHEMA`. This command imports a foreign schema from a foreign server or a database link. | | +| Enhancement | Added support for `ANYCOMPATIBLE` and "any" pseudo type to NVL function. This allows NVL function to support more types of argument combinations now. | | +| Enhancement | Added support to audit all the EDB Postgres Advanced Server's modified external function signatures so that PostgreSQL compatible extensions can be compiled along with EDB Postgres Advanced Server. | | +| Enhancement | EDB*Loader: Enhanced terminator and delimiter matching behavior to consider the server encoding. | | diff --git a/product_docs/docs/epas/17/reference/sql_reference/02_data_types/06_xml_type.mdx b/product_docs/docs/epas/17/reference/sql_reference/02_data_types/06_xml_type.mdx index f840bc9d553..49b8b0a57fe 100644 --- a/product_docs/docs/epas/17/reference/sql_reference/02_data_types/06_xml_type.mdx +++ b/product_docs/docs/epas/17/reference/sql_reference/02_data_types/06_xml_type.mdx @@ -97,14 +97,14 @@ From version 17, XMLType can be called as an object type and has predefined memb This table summarizes member functions and constructors of XMLType. -| Method | Type | Description | -|-----------------------------------|----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| [`EXISTSNODE`](#existsnode) | Member function | It takes a `XMLType` instance and a `XPath`, returning 1 or 0 to indicate whether applying the `XPath` results in a non-empty set of nodes. | -| [`EXTRACT_XML`](#extract_xml) | Member function | It takes a `XMLType` instance and a `XPath`, applies the `XPath` expression and returns the results as an `XMLType`. | -| [`GETCLOBVAL()`](#getclobval) | Member function | It returns the value of the `XMLType` instance as a CLOB. | -| [`GETNUMBERVAL()`](#getnumberval) | Member function | The value of the `XMLType` instance is returned as a NUMBER. This operation is valid only if the input `XMLType` instance contains a simple text node and can be successfully converted to a number. | -| [`GETSTRINGVAL()`](#getstringval) | Member function | It returns the value of the `XMLType` instance as a string. | -| [`XMLTYPE`](#xmltype) | Constructor function | It constructs an instance of the `XMLType` datatype. The constructor accepts the XML as a CLOB, TEXT, or an object type. | +| Method | Type | Description | +|--------------------------------------------|----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| [`EXISTSNODE`](#existsnode) | Member function | It takes a `XMLType` instance and a `XPath`, returning 1 or 0 to indicate whether applying the `XPath` results in a non-empty set of nodes. | +| [`EXTRACT_XML`](#extract_xml) | Member function | It takes a `XMLType` instance and a `XPath`, applies the `XPath` expression and returns the results as an `XMLType`. | +| [`GETCLOBVAL()`](#getclobval) | Member function | It returns the value of the `XMLType` instance as a CLOB. | +| [`GETNUMBERVAL()`](#getnumberval) | Member function | The value of the `XMLType` instance is returned as a NUMBER. This operation is valid only if the input `XMLType` instance contains a simple text node and can be successfully converted to a number. | +| [`GETSTRINGVAL()`](#getstringval) | Member function | It returns the value of the `XMLType` instance as a string. | +| [`XMLTYPE`](#xmltype-constructor-function) | Constructor function | It constructs an instance of the `XMLType` datatype. The constructor accepts the XML as a CLOB, TEXT, or an object type. | ### EXISTSNODE From 6a9dc24b927574f2a8c29cf687ce324265663c9f Mon Sep 17 00:00:00 2001 From: gvasquezvargas Date: Fri, 22 Nov 2024 16:07:56 +0100 Subject: [PATCH 20/24] Updated release date --- .../docs/jdbc_connector/42.7.3.2/01_jdbc_rel_notes/index.mdx | 2 +- .../42.7.3.2/01_jdbc_rel_notes/jdbc_42.7.3.2_rel_notes.mdx | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/product_docs/docs/jdbc_connector/42.7.3.2/01_jdbc_rel_notes/index.mdx b/product_docs/docs/jdbc_connector/42.7.3.2/01_jdbc_rel_notes/index.mdx index 30d732b5144..d18e2a59cec 100644 --- a/product_docs/docs/jdbc_connector/42.7.3.2/01_jdbc_rel_notes/index.mdx +++ b/product_docs/docs/jdbc_connector/42.7.3.2/01_jdbc_rel_notes/index.mdx @@ -16,7 +16,7 @@ These release notes describe what's new in each release. When a minor or patch r | Version | Release Date | | ---------------------------------------- | ------------ | -| [42.7.3.2](jdbc_42.7.3.2_rel_notes) | 20 Nov 2024 | +| [42.7.3.2](jdbc_42.7.3.2_rel_notes) | 21 Nov 2024 | | [42.7.3.1](jdbc_42.7.3.1_rel_notes) | 10 Sep 2024 | | [42.5.4.2](jdbc_42.5.4.2_rel_notes) | 26 Feb 2024 | | [42.5.4.1](jdbc_42.5.4.1_rel_notes) | 16 Mar 2023 | diff --git a/product_docs/docs/jdbc_connector/42.7.3.2/01_jdbc_rel_notes/jdbc_42.7.3.2_rel_notes.mdx b/product_docs/docs/jdbc_connector/42.7.3.2/01_jdbc_rel_notes/jdbc_42.7.3.2_rel_notes.mdx index ecf74d565f4..5dfa55d500e 100644 --- a/product_docs/docs/jdbc_connector/42.7.3.2/01_jdbc_rel_notes/jdbc_42.7.3.2_rel_notes.mdx +++ b/product_docs/docs/jdbc_connector/42.7.3.2/01_jdbc_rel_notes/jdbc_42.7.3.2_rel_notes.mdx @@ -3,7 +3,7 @@ title: "EDB JDBC Connector 42.7.3.2 release notes" navTitle: Version 42.7.3.2 --- -Released: 21 Nov 2024 +Released: 22 Nov 2024 The EDB JDBC connector provides connectivity between a Java application and an EDB Postgres Advanced Server database. From e835c0fbd61445e4c3a7c3ae344a4552af1df2f9 Mon Sep 17 00:00:00 2001 From: gvasquezvargas Date: Fri, 22 Nov 2024 16:08:56 +0100 Subject: [PATCH 21/24] Updated release date --- .../17/ocl_rel_notes/17.2.0.1_ocl_release_notes.mdx | 2 +- product_docs/docs/ocl_connector/17/ocl_rel_notes/index.mdx | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/product_docs/docs/ocl_connector/17/ocl_rel_notes/17.2.0.1_ocl_release_notes.mdx b/product_docs/docs/ocl_connector/17/ocl_rel_notes/17.2.0.1_ocl_release_notes.mdx index d04eaa81273..daf9c4ea6b7 100644 --- a/product_docs/docs/ocl_connector/17/ocl_rel_notes/17.2.0.1_ocl_release_notes.mdx +++ b/product_docs/docs/ocl_connector/17/ocl_rel_notes/17.2.0.1_ocl_release_notes.mdx @@ -3,7 +3,7 @@ title: "EDB OCL Connector 17.2.0.1 release notes" navTitle: Version 17.2.0.1 --- -Released: 21 Nov 2024 +Released: 22 Nov 2024 The EDB OCL Connector provides an API similar to the Oracle Call Interface. diff --git a/product_docs/docs/ocl_connector/17/ocl_rel_notes/index.mdx b/product_docs/docs/ocl_connector/17/ocl_rel_notes/index.mdx index 8a526154c9c..383171cfb8e 100644 --- a/product_docs/docs/ocl_connector/17/ocl_rel_notes/index.mdx +++ b/product_docs/docs/ocl_connector/17/ocl_rel_notes/index.mdx @@ -11,4 +11,4 @@ Release notes describe what's new in a release. When a minor or patch release in | Version | Release date | | -------------------------------------- | ------------ | -| [17.2.0.1](17.2.0.1_ocl_release_notes) | 20 Nov 2024 | +| [17.2.0.1](17.2.0.1_ocl_release_notes) | 22 Nov 2024 | From fc8aac13edcf4d6342b488bfc40693daa59daff0 Mon Sep 17 00:00:00 2001 From: gvasquezvargas Date: Fri, 22 Nov 2024 15:05:38 +0100 Subject: [PATCH 22/24] PGE: add 17.2 branch and release notes --- .../01_setting_configuration_parameters.mdx | 95 +++++++++++ .../docs/pge/17/administration/index.mdx | 16 ++ product_docs/docs/pge/17/deploy_options.mdx | 14 ++ product_docs/docs/pge/17/extensions.mdx | 13 ++ product_docs/docs/pge/17/index.mdx | 34 ++++ .../pge/17/installing/component_locations.mdx | 43 +++++ product_docs/docs/pge/17/installing/index.mdx | 36 ++++ .../pge/17/installing/linux_arm64/index.mdx | 13 ++ .../installing/linux_arm64/pge_debian_12.mdx | 124 ++++++++++++++ .../pge/17/installing/linux_x86_64/index.mdx | 44 +++++ .../installing/linux_x86_64/pge_debian_11.mdx | 124 ++++++++++++++ .../installing/linux_x86_64/pge_debian_12.mdx | 124 ++++++++++++++ .../linux_x86_64/pge_other_linux_8.mdx | 135 +++++++++++++++ .../linux_x86_64/pge_other_linux_9.mdx | 135 +++++++++++++++ .../17/installing/linux_x86_64/pge_rhel_8.mdx | 129 +++++++++++++++ .../17/installing/linux_x86_64/pge_rhel_9.mdx | 129 +++++++++++++++ .../installing/linux_x86_64/pge_ubuntu_20.mdx | 124 ++++++++++++++ .../installing/linux_x86_64/pge_ubuntu_22.mdx | 124 ++++++++++++++ product_docs/docs/pge/17/operation.mdx | 42 +++++ product_docs/docs/pge/17/parameters.mdx | 147 +++++++++++++++++ .../docs/pge/17/release_notes/index.mdx | 15 ++ .../pge/17/release_notes/rel_notes17.2.mdx | 12 ++ product_docs/docs/pge/17/replication.mdx | 33 ++++ .../docs/pge/17/sql_features/index.mdx | 57 +++++++ .../pge/17/sql_features/jdbctxnrollback.mdx | 111 +++++++++++++ .../docs/pge/17/sql_features/txnrollback.mdx | 55 +++++++ product_docs/docs/pge/17/tde.mdx | 8 + product_docs/docs/pge/17/upgrading/index.mdx | 11 ++ .../docs/pge/17/upgrading/major_upgrade.mdx | 155 ++++++++++++++++++ .../upgrading/minor_upgrade/apt_upgrade.mdx | 65 ++++++++ .../upgrading/minor_upgrade/dnf_upgrade.mdx | 96 +++++++++++ .../pge/17/upgrading/minor_upgrade/index.mdx | 15 ++ 32 files changed, 2278 insertions(+) create mode 100644 product_docs/docs/pge/17/administration/01_setting_configuration_parameters.mdx create mode 100644 product_docs/docs/pge/17/administration/index.mdx create mode 100644 product_docs/docs/pge/17/deploy_options.mdx create mode 100644 product_docs/docs/pge/17/extensions.mdx create mode 100644 product_docs/docs/pge/17/index.mdx create mode 100644 product_docs/docs/pge/17/installing/component_locations.mdx create mode 100644 product_docs/docs/pge/17/installing/index.mdx create mode 100644 product_docs/docs/pge/17/installing/linux_arm64/index.mdx create mode 100644 product_docs/docs/pge/17/installing/linux_arm64/pge_debian_12.mdx create mode 100644 product_docs/docs/pge/17/installing/linux_x86_64/index.mdx create mode 100644 product_docs/docs/pge/17/installing/linux_x86_64/pge_debian_11.mdx create mode 100644 product_docs/docs/pge/17/installing/linux_x86_64/pge_debian_12.mdx create mode 100644 product_docs/docs/pge/17/installing/linux_x86_64/pge_other_linux_8.mdx create mode 100644 product_docs/docs/pge/17/installing/linux_x86_64/pge_other_linux_9.mdx create mode 100644 product_docs/docs/pge/17/installing/linux_x86_64/pge_rhel_8.mdx create mode 100644 product_docs/docs/pge/17/installing/linux_x86_64/pge_rhel_9.mdx create mode 100644 product_docs/docs/pge/17/installing/linux_x86_64/pge_ubuntu_20.mdx create mode 100644 product_docs/docs/pge/17/installing/linux_x86_64/pge_ubuntu_22.mdx create mode 100644 product_docs/docs/pge/17/operation.mdx create mode 100644 product_docs/docs/pge/17/parameters.mdx create mode 100644 product_docs/docs/pge/17/release_notes/index.mdx create mode 100644 product_docs/docs/pge/17/release_notes/rel_notes17.2.mdx create mode 100644 product_docs/docs/pge/17/replication.mdx create mode 100644 product_docs/docs/pge/17/sql_features/index.mdx create mode 100644 product_docs/docs/pge/17/sql_features/jdbctxnrollback.mdx create mode 100644 product_docs/docs/pge/17/sql_features/txnrollback.mdx create mode 100644 product_docs/docs/pge/17/tde.mdx create mode 100644 product_docs/docs/pge/17/upgrading/index.mdx create mode 100644 product_docs/docs/pge/17/upgrading/major_upgrade.mdx create mode 100644 product_docs/docs/pge/17/upgrading/minor_upgrade/apt_upgrade.mdx create mode 100644 product_docs/docs/pge/17/upgrading/minor_upgrade/dnf_upgrade.mdx create mode 100644 product_docs/docs/pge/17/upgrading/minor_upgrade/index.mdx diff --git a/product_docs/docs/pge/17/administration/01_setting_configuration_parameters.mdx b/product_docs/docs/pge/17/administration/01_setting_configuration_parameters.mdx new file mode 100644 index 00000000000..6a0cd8e19c1 --- /dev/null +++ b/product_docs/docs/pge/17/administration/01_setting_configuration_parameters.mdx @@ -0,0 +1,95 @@ +--- +title: "Setting configuration parameters" +navTitle: "Setting configuration parameters" +description: "Describes how to set the configuration parameters for EDB Postgres Extended Server." +--- + +Set each configuration parameter using a name/value pair. Parameter names aren't case sensitive. The parameter name is typically separated from its value by an optional equals sign (`=`). + +This example shows some configuration parameter settings in the `postgresql.conf` file: + +```ini +# This is a comment +log_connections = yes +log_destination = 'syslog' +search_path = '"$user", public' +shared_buffers = 128MB +``` + +## Types of parameter values + +Parameter values are specified as one of five types: + +- **Boolean** — Acceptable values are `on`, `off`, `true`, `false`, `yes`, `no`, `1`, `0`, or any unambiguous prefix of these. +- **Integer** — Number without a fractional part. +- **Floating point** — Number with an optional fractional part separated by a decimal point. +- **String** — Text value enclosed in single quotes if the value isn't a simple identifier or number, that is, the value contains special characters such as spaces or other punctuation marks. +- **Enum** — Specific set of string values. The allowed values can be found in the system view `pg_settings.enumvals`. Enum values are not case sensitive. + +Some settings specify a memory or time value. Each of these has an implicit unit, which is kilobytes, blocks (typically 8 kilobytes), milliseconds, seconds, or minutes. You can find default units by referencing the system view `pg_settings.unit`. You can specify a different unit explicitly. + +Valid memory units are: +- `kB` (kilobytes) +- `MB` (megabytes) +- `GB` (gigabytes). + +Valid time units are: +- `ms` (milliseconds) +- `s` (seconds) +- `min` (minutes) +- `h` (hours) +- `d` (days). + +The multiplier for memory units is 1024. + +## Specifying configuration parameter settings + +A number of parameter settings are set when the EDB Postgres Extended Server database product is built. These are read-only parameters, and you can't change their values. A couple of parameters are also permanently set for each database when the database is created. These parameters are read-only and you can't later change them for the database. However, there are a number of ways to specify the configuration parameter settings: + +- The initial settings for almost all configurable parameters across the entire database cluster are listed in the `postgresql.conf` configuration file. These settings are put into effect upon database server start or restart. You can override some of these initial parameter settings. All configuration parameters have built-in default settings that are in effect unless you explicitly override them. + +- Configuration parameters in the `postgresql.conf` file are overridden when the same parameters are included in the `postgresql.auto.conf` file. Use the `ALTER SYSTEM` command to manage the configuration parameters in the `postgresql.auto.conf` file. + +- You can modify parameter settings in the configuration file while the database server is running. If the configuration file is then reloaded (meaning a SIGHUP signal is issued), for certain parameter types, the changed parameters settings immediately take effect. For some of these parameter types, the new settings are available in a currently running session immediately after the reload. For others, you must start a new session to use the new settings. And for some others, modified settings don't take effect until the database server is stopped and restarted. See the [PostgreSQL core documentation](https://www.postgresql.org/docs/current/config-setting.html) for information on how to reload the configuration file. + +- You can use the SQL commands `ALTER DATABASE`, `ALTER ROLE`, or `ALTER ROLE IN DATABASE` to modify certain parameter settings. The modified parameter settings take effect for new sessions after you execute the command. `ALTER DATABASE` affects new sessions connecting to the specified database. `ALTER ROLE` affects new sessions started by the specified role. `ALTER ROLE IN DATABASE` affects new sessions started by the specified role connecting to the specified database. Parameter settings established by these SQL commands remain in effect indefinitely, across database server restarts, overriding settings established by the other methods. You can change parameter settings established using the `ALTER DATABASE`, `ALTER ROLE`, or `ALTER ROLE IN DATABASE` commands by either: + + - Reissuing these commands with a different parameter value. + + - Issuing these commands using the `SET parameter TO DEFAULT` clause or the `RESET parameter` clause. These clauses change the parameter back to using the setting set by the other methods. See the [PostgreSQL core documentation](https://www.postgresql.org/docs/current/sql-commands.html) for the syntax of these SQL commands. + +- You can make changes for certain parameter settings for the duration of individual sessions using the `PGOPTIONS` environment variable or by using the `SET` command in the EDB-PSQL or PSQL command-line programs. Parameter settings made this way override settings established using any of the methods discussed earlier, but only during that session. + +## Modifying the postgresql.conf file + +The configuration parameters in the `postgresql.conf` file specify server behavior with regard to auditing, authentication, encryption, and other behaviors. On Linux and Windows hosts, the `postgresql.conf` file resides in the `data` directory under your EDB Postgres Extended Server installation. + +Parameters that are preceded by a pound sign (#) are set to their default value. To change a parameter value, remove the pound sign and enter a new value. After setting or changing a parameter, you must either `reload` or `restart` the server for the new parameter value to take effect. + +In the `postgresql.conf` file, some parameters contain comments that indicate `change requires restart`. To view a list of the parameters that require a server restart, use the following query at the psql command line: + +```sql +SELECT name FROM pg_settings WHERE context = 'postmaster'; +``` + + + +## Modifying the pg_hba.conf file + +Appropriate authentication methods provide protection and security. Entries in the `pg_hba.conf` file specify the authentication methods that the server uses with connecting clients. Before connecting to the server, you might need to modify the authentication properties specified in the `pg_hba.conf` file. + +When you invoke the initdb utility to create a cluster, the utility creates a `pg_hba.conf` file for that cluster that specifies the type of authentication required from connecting clients. You can modify this file. After modifying the authentication settings in the `pg_hba.conf` file, restart the server and apply the changes. For more information about authentication and modifying the `pg_hba.conf` file, see the [PostgreSQL core documentation](https://www.postgresql.org/docs/current/static/auth-pg-hba-conf.html). + +When the server receives a connection request, it verifies the credentials provided against the authentication settings in the `pg_hba.conf` file before allowing a connection to a database. To log the `pg_hba.conf` file entry to authenticate a connection to the server, set the `log_connections` parameter to `ON` in the `postgresql.conf` file. + +A record specifies a connection type, database name, user name, client IP address, and the authentication method to authorize a connection upon matching these parameters in the `pg_hba.conf` file. Once the connection to a server is authorized, you can see the matched line number and the authentication record from the `pg_hba.conf` file. + +This example shows a log detail for a valid `pg_hba.conf` entry after successful authentication: + +```shell +2020-05-08 10:42:17 IST LOG: connection received: host=[local] +2020-05-08 10:42:17 IST LOG: connection authorized: user=u1 database=edb +application_name=psql +2020-05-08 10:42:17 IST DETAIL: Connection matched pg_hba.conf line 84: +"local all all md5" +``` diff --git a/product_docs/docs/pge/17/administration/index.mdx b/product_docs/docs/pge/17/administration/index.mdx new file mode 100644 index 00000000000..08b4255196f --- /dev/null +++ b/product_docs/docs/pge/17/administration/index.mdx @@ -0,0 +1,16 @@ +--- +title: "Database configuration" +description: "How to configure EDB Postgres Extended Server databases." +navigation: +- 01_configuration_parameters +--- + +EDB Postgres Extended Server includes features to help you to maintain, secure, and operate EDB Postgres Extended Server databases. + +You can configure grand unified configuration (GUC) parameters at runtime by modifying the `postgresql.conf` and `pg_hba.conf` files. + +- The `postgresql.conf` file allows you to make persistent changes to your database configuration. +- The `pg_hba.conf` file allows you to change access and authentication settings. + +See [Setting configuration parameters](01_setting_configuration_parameters) for more information. + diff --git a/product_docs/docs/pge/17/deploy_options.mdx b/product_docs/docs/pge/17/deploy_options.mdx new file mode 100644 index 00000000000..7499961f6ff --- /dev/null +++ b/product_docs/docs/pge/17/deploy_options.mdx @@ -0,0 +1,14 @@ +--- + +title: Deployment options +originalFilePath: index.md +description: Deployment options available for EDB Postgres Extended Server. +--- + +The deployment options include: + +- [Installing](installing) on a virtual machine or physical server using native packages + +- Deploying it with [EDB Postgres Distributed](/pgd/latest/) using [Trusted Postgres Architect](/pgd/latest/deploy-config/deploy-tpa/) + +- Deploying it on [EDB Postgres AI Cloud Service](/edb-postgres-ai/cloud-service/) with extreme-high-availability cluster types diff --git a/product_docs/docs/pge/17/extensions.mdx b/product_docs/docs/pge/17/extensions.mdx new file mode 100644 index 00000000000..86bf83bce1d --- /dev/null +++ b/product_docs/docs/pge/17/extensions.mdx @@ -0,0 +1,13 @@ +--- +navTitle: Extensions +title: Postgres extensions supported in EDB Postgres Extended Server +description: Postgres extensions supported in EDB Postgres Extended Server. +--- + +EDB provides support for several Postgres extensions on EDB Postgres Extended Server: + +- Open-source extensions +- EDB supported open-source extensions +- EDB-developed extensions + +See [Postgres extensions available by deployment](/pg_extensions/) for an overview of all supported extensions and links to their documentation sites. \ No newline at end of file diff --git a/product_docs/docs/pge/17/index.mdx b/product_docs/docs/pge/17/index.mdx new file mode 100644 index 00000000000..daaeaa72cb7 --- /dev/null +++ b/product_docs/docs/pge/17/index.mdx @@ -0,0 +1,34 @@ +--- +title: EDB Postgres Extended Server +originalFilePath: index.md +navigation: + - release_notes + - "#Get Started" + - deploy_options + - installing + - administration + - "#Features" + - tde + - replication + - extensions + - "#Upgrade" + - upgrading + - "#Reference" + - parameters + - sql_features + - operation +indexCards: simple +--- + +EDB Postgres Extended Server is a Postgres database server distribution built on open-source, community PostgreSQL. It's fully compatible with PostgreSQL. If you have applications written and tested to work with PostgreSQL, they will behave the same with EDB Postgres Extended Server. We will support and fix any functionality or behavior differences between community PostgreSQL and EDB Postgres Extended Server. + +EDB Postgres Extended Server's primary purpose is to extend PostgreSQL with a limited number of features that can't be implemented as extensions, such as [enhanced replication optimization](replication) used by [EDB Postgres Distributed](/pgd/latest/) and [Transparent Data Encryption](/tde/latest/), while maintaining parity in other respects. + +Additional value-add enterprise features include: +- Security though [Transparent Data Encryption](/tde/latest/) + +- Optional [SQL superset](sql_features) to community PostgreSQL +- [WAL pacing delays to avoid flooding transaction logs](./operation/#avoid-flooding-transaction-logs) +- [Additional tracing and diagnostics options](./operation/#additional-tracing-and-diagnostics-options) + +--- diff --git a/product_docs/docs/pge/17/installing/component_locations.mdx b/product_docs/docs/pge/17/installing/component_locations.mdx new file mode 100644 index 00000000000..90d1525fda4 --- /dev/null +++ b/product_docs/docs/pge/17/installing/component_locations.mdx @@ -0,0 +1,43 @@ +--- +title: Default component locations +navTitle: Component locations +description: "Provides information about accessing EDB Postgres Extended Server components after installation." +--- + +The package managers for the various Linux variations install EDB Postgres Extended Server components in different locations. If you need to access the components after installation, see: + +- [RHEL/OL/Rocky Linux/AlmaLinux/CentOS/SLES locations](#rhelolrocky-linuxalmalinuxcentossles-locations) +- [Debian/Ubuntu locations](#debianubuntu-locations) + +## RHEL/OL/Rocky Linux/AlmaLinux/CentOS/SLES Locations + +The RPM installers place EDB Postgres Extended Server components in the directories listed in the table. + +| Component | Location | +|-----------------------------|--------------------------------| +| Executables | `/usr/edb/pge16/bin` | +| Libraries | `/usr/edb/pge16/lib` | +| Cluster configuration files | `/var/lib/edb-pge/16` | +| Documentation | `/usr/edb/pge16/share/man` | +| Contrib | `/usr/edb/pge16/share/contrib` | +| Data | `/var/lib/edb-pge/16/data` | +| Logs | `/var/log/edb/pge16` | +| Lock files | `/var/lock/edb/pge16` | +| Backup area | `/var/lib/edb-pge/16/backups` | +| Templates | `/usr/edb/pge16/share` | +| Procedural Languages | `/usr/edb/pge16/lib` | +| Development Headers | `/usr/edb/pge16/include` | +| Shared data | `/usr/edb/pge16/share` | + +## Debian/Ubuntu Locations + +The Debian package manager places EDB Postgres Extended Server components in the directories listed in the table. + +| Component | Location | +|-----------------------------|------------------------------------| +| Executables | `/usr/lib/edb-pge/16/bin` | +| Libraries | `/usr/lib/edb-pge/16/lib` | +| Cluster configuration files | `/var/lib/edb-pge/16/main` | +| Data | `/var/lib/edb-pge/16/main` | +| Logs | `/var/log/edb-pge/` | +| Lock files | `/var/lock/edb/pge16` | diff --git a/product_docs/docs/pge/17/installing/index.mdx b/product_docs/docs/pge/17/installing/index.mdx new file mode 100644 index 00000000000..0cc88e55d5e --- /dev/null +++ b/product_docs/docs/pge/17/installing/index.mdx @@ -0,0 +1,36 @@ +--- +navTitle: Installing +title: Installing EDB Postgres Extended Server on Linux + +description: Installation instructions for EDB Postgres Extended Server on Linux. + +navigation: + - linux_x86_64 + - linux_arm64 +--- + +Select a link to access the applicable installation instructions: + +## Linux [x86-64 (amd64)](linux_x86_64) + +### Red Hat Enterprise Linux (RHEL) and derivatives + +- [RHEL 9](linux_x86_64/pge_rhel_9), [RHEL 8](linux_x86_64/pge_rhel_8) + +- [Oracle Linux (OL) 9](linux_x86_64/pge_rhel_9), [Oracle Linux (OL) 8](linux_x86_64/pge_rhel_8) + +- [Rocky Linux 9](linux_x86_64/pge_other_linux_9), [Rocky Linux 8](linux_x86_64/pge_other_linux_8) + +- [AlmaLinux 9](linux_x86_64/pge_other_linux_9), [AlmaLinux 8](linux_x86_64/pge_other_linux_8) + +### Debian and derivatives + +- [Ubuntu 22.04](linux_x86_64/pge_ubuntu_22), [Ubuntu 20.04](linux_x86_64/pge_ubuntu_20) + +- [Debian 12](linux_x86_64/pge_debian_12), [Debian 11](linux_x86_64/pge_debian_11) + +## Linux [AArch64 (ARM64)](linux_arm64) + +### Debian and derivatives + +- [Debian 12](linux_arm64/pge_debian_12) diff --git a/product_docs/docs/pge/17/installing/linux_arm64/index.mdx b/product_docs/docs/pge/17/installing/linux_arm64/index.mdx new file mode 100644 index 00000000000..230f6000758 --- /dev/null +++ b/product_docs/docs/pge/17/installing/linux_arm64/index.mdx @@ -0,0 +1,13 @@ +--- +title: "Installing EDB Postgres Extended Server on Linux AArch64 (ARM64)" +navTitle: "On Linux ARM64" + +navigation: + - pge_debian_12 +--- + +Operating system-specific install instructions are described in the corresponding documentation: + +### Debian and derivatives + +- [Debian 12](pge_debian_12) diff --git a/product_docs/docs/pge/17/installing/linux_arm64/pge_debian_12.mdx b/product_docs/docs/pge/17/installing/linux_arm64/pge_debian_12.mdx new file mode 100644 index 00000000000..5d050ad2748 --- /dev/null +++ b/product_docs/docs/pge/17/installing/linux_arm64/pge_debian_12.mdx @@ -0,0 +1,124 @@ +--- +navTitle: Debian 12 +title: Installing EDB Postgres Extended Server on Debian 12 arm64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. + +redirects: +--- + +## Prerequisites + +Before you begin the installation process: + +- Set up the EDB repository. + + Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. + + To determine if your repository exists, enter this command: + + `apt-cache search enterprisedb` + + If no output is generated, the repository isn't installed. + + To set up the EDB repository: + + 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads). + + 1. Select the button that provides access to the EDB repository. + + 1. Select the platform and software that you want to download. + + 1. Follow the instructions for setting up the EDB repository. + +## Install the package + +```shell +sudo apt-get -y install edb-postgresextended-16 +``` + +## Initial configuration + +This section steps you through getting started with your cluster including logging in, ensuring the installation was successful, connecting to your cluster, and creating the user password. + +First, you need to initialize and start the database cluster. The `edb-pge-16-setup` script creates a cluster. + +```shell +sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/lib/edb-pge/16/bin/edb-pge-16-setup initdb + +sudo systemctl start edb-pge-16 +``` + +To work in your cluster, log in as the postgres user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. + +```shell +sudo -iu postgres + +psql postgres +``` + +The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file. + +Before changing the authentication method, assign a password to the database superuser, postgres. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../administration/01_setting_configuration_parameters/#modifying-the-pg_hbaconf-file). + +```sql +ALTER ROLE postgres with PASSWORD 'password'; +``` + +## Experiment + +Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. + +First, use psql to create a database named `hr` to hold human resource information. + +```sql +# running in psql +CREATE DATABASE hr; +__OUTPUT__ +CREATE DATABASE +``` + +Connect to the `hr` database inside psql: + +``` +\c hr +__OUTPUT__ +You are now connected to database "hr" as user "postgres". +``` + +Create columns to hold department numbers, unique department names, and locations: + +``` +CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk +PRIMARY KEY, dname varchar(14) CONSTRAINT dept_dname_uq UNIQUE, loc +varchar(13)); +__OUTPUT__ +CREATE TABLE +``` + +Insert values into the `dept` table: + +``` +INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); +__OUTPUT__ +INSERT 0 1 +``` + +``` +INSERT into dept VALUES (20,'RESEARCH','DALLAS'); +__OUTPUT__ +INSERT 0 1 +``` + +View the table data by selecting the values from the table: + +``` +SELECT * FROM dept; +__OUTPUT__ +deptno | dname | loc +--------+------------+---------- +10 | ACCOUNTING | NEW YORK +20 | RESEARCH | DALLAS +(2 rows) +``` diff --git a/product_docs/docs/pge/17/installing/linux_x86_64/index.mdx b/product_docs/docs/pge/17/installing/linux_x86_64/index.mdx new file mode 100644 index 00000000000..0ec9f379e21 --- /dev/null +++ b/product_docs/docs/pge/17/installing/linux_x86_64/index.mdx @@ -0,0 +1,44 @@ +--- +title: "Installing EDB Postgres Extended Server on Linux x86 (amd64)" +navTitle: "On Linux x86" + +navigation: + - pge_rhel_9 + - pge_rhel_8 + - pge_other_linux_9 + - pge_other_linux_8 + - pge_ubuntu_22 + - pge_ubuntu_20 + - pge_debian_12 + - pge_debian_11 +--- + +Operating system-specific install instructions are described in the corresponding documentation: + +### Red Hat Enterprise Linux (RHEL) and derivatives + +- [RHEL 9](pge_rhel_9) + +- [RHEL 8](pge_rhel_8) + +- [Oracle Linux (OL) 9](pge_rhel_9) + +- [Oracle Linux (OL) 8](pge_rhel_8) + +- [Rocky Linux 9](pge_other_linux_9) + +- [Rocky Linux 8](pge_other_linux_8) + +- [AlmaLinux 9](pge_other_linux_9) + +- [AlmaLinux 8](pge_other_linux_8) + +### Debian and derivatives + +- [Ubuntu 22.04](pge_ubuntu_22) + +- [Ubuntu 20.04](pge_ubuntu_20) + +- [Debian 12](pge_debian_12) + +- [Debian 11](pge_debian_11) diff --git a/product_docs/docs/pge/17/installing/linux_x86_64/pge_debian_11.mdx b/product_docs/docs/pge/17/installing/linux_x86_64/pge_debian_11.mdx new file mode 100644 index 00000000000..189cbcad2f9 --- /dev/null +++ b/product_docs/docs/pge/17/installing/linux_x86_64/pge_debian_11.mdx @@ -0,0 +1,124 @@ +--- +navTitle: Debian 11 +title: Installing EDB Postgres Extended Server on Debian 11 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. + +redirects: +--- + +## Prerequisites + +Before you begin the installation process: + +- Set up the EDB repository. + + Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. + + To determine if your repository exists, enter this command: + + `apt-cache search enterprisedb` + + If no output is generated, the repository isn't installed. + + To set up the EDB repository: + + 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads). + + 1. Select the button that provides access to the EDB repository. + + 1. Select the platform and software that you want to download. + + 1. Follow the instructions for setting up the EDB repository. + +## Install the package + +```shell +sudo apt-get -y install edb-postgresextended-16 +``` + +## Initial configuration + +This section steps you through getting started with your cluster including logging in, ensuring the installation was successful, connecting to your cluster, and creating the user password. + +First, you need to initialize and start the database cluster. The `edb-pge-16-setup` script creates a cluster. + +```shell +sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/lib/edb-pge/16/bin/edb-pge-16-setup initdb + +sudo systemctl start edb-pge-16 +``` + +To work in your cluster, log in as the postgres user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. + +```shell +sudo -iu postgres + +psql postgres +``` + +The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file. + +Before changing the authentication method, assign a password to the database superuser, postgres. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../administration/01_setting_configuration_parameters/#modifying-the-pg_hbaconf-file). + +```sql +ALTER ROLE postgres with PASSWORD 'password'; +``` + +## Experiment + +Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. + +First, use psql to create a database named `hr` to hold human resource information. + +```sql +# running in psql +CREATE DATABASE hr; +__OUTPUT__ +CREATE DATABASE +``` + +Connect to the `hr` database inside psql: + +``` +\c hr +__OUTPUT__ +You are now connected to database "hr" as user "postgres". +``` + +Create columns to hold department numbers, unique department names, and locations: + +``` +CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk +PRIMARY KEY, dname varchar(14) CONSTRAINT dept_dname_uq UNIQUE, loc +varchar(13)); +__OUTPUT__ +CREATE TABLE +``` + +Insert values into the `dept` table: + +``` +INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); +__OUTPUT__ +INSERT 0 1 +``` + +``` +INSERT into dept VALUES (20,'RESEARCH','DALLAS'); +__OUTPUT__ +INSERT 0 1 +``` + +View the table data by selecting the values from the table: + +``` +SELECT * FROM dept; +__OUTPUT__ +deptno | dname | loc +--------+------------+---------- +10 | ACCOUNTING | NEW YORK +20 | RESEARCH | DALLAS +(2 rows) +``` diff --git a/product_docs/docs/pge/17/installing/linux_x86_64/pge_debian_12.mdx b/product_docs/docs/pge/17/installing/linux_x86_64/pge_debian_12.mdx new file mode 100644 index 00000000000..d784f6fe72e --- /dev/null +++ b/product_docs/docs/pge/17/installing/linux_x86_64/pge_debian_12.mdx @@ -0,0 +1,124 @@ +--- +navTitle: Debian 12 +title: Installing EDB Postgres Extended Server on Debian 12 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. + +redirects: +--- + +## Prerequisites + +Before you begin the installation process: + +- Set up the EDB repository. + + Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. + + To determine if your repository exists, enter this command: + + `apt-cache search enterprisedb` + + If no output is generated, the repository isn't installed. + + To set up the EDB repository: + + 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads). + + 1. Select the button that provides access to the EDB repository. + + 1. Select the platform and software that you want to download. + + 1. Follow the instructions for setting up the EDB repository. + +## Install the package + +```shell +sudo apt-get -y install edb-postgresextended-16 +``` + +## Initial configuration + +This section steps you through getting started with your cluster including logging in, ensuring the installation was successful, connecting to your cluster, and creating the user password. + +First, you need to initialize and start the database cluster. The `edb-pge-16-setup` script creates a cluster. + +```shell +sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/lib/edb-pge/16/bin/edb-pge-16-setup initdb + +sudo systemctl start edb-pge-16 +``` + +To work in your cluster, log in as the postgres user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. + +```shell +sudo -iu postgres + +psql postgres +``` + +The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file. + +Before changing the authentication method, assign a password to the database superuser, postgres. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../administration/01_setting_configuration_parameters/#modifying-the-pg_hbaconf-file). + +```sql +ALTER ROLE postgres with PASSWORD 'password'; +``` + +## Experiment + +Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. + +First, use psql to create a database named `hr` to hold human resource information. + +```sql +# running in psql +CREATE DATABASE hr; +__OUTPUT__ +CREATE DATABASE +``` + +Connect to the `hr` database inside psql: + +``` +\c hr +__OUTPUT__ +You are now connected to database "hr" as user "postgres". +``` + +Create columns to hold department numbers, unique department names, and locations: + +``` +CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk +PRIMARY KEY, dname varchar(14) CONSTRAINT dept_dname_uq UNIQUE, loc +varchar(13)); +__OUTPUT__ +CREATE TABLE +``` + +Insert values into the `dept` table: + +``` +INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); +__OUTPUT__ +INSERT 0 1 +``` + +``` +INSERT into dept VALUES (20,'RESEARCH','DALLAS'); +__OUTPUT__ +INSERT 0 1 +``` + +View the table data by selecting the values from the table: + +``` +SELECT * FROM dept; +__OUTPUT__ +deptno | dname | loc +--------+------------+---------- +10 | ACCOUNTING | NEW YORK +20 | RESEARCH | DALLAS +(2 rows) +``` diff --git a/product_docs/docs/pge/17/installing/linux_x86_64/pge_other_linux_8.mdx b/product_docs/docs/pge/17/installing/linux_x86_64/pge_other_linux_8.mdx new file mode 100644 index 00000000000..d906afce5f7 --- /dev/null +++ b/product_docs/docs/pge/17/installing/linux_x86_64/pge_other_linux_8.mdx @@ -0,0 +1,135 @@ +--- +navTitle: AlmaLinux 8 or Rocky Linux 8 +title: Installing EDB Postgres Extended Server on AlmaLinux 8 or Rocky Linux 8 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. + +redirects: +--- + +## Prerequisites + +Before you begin the installation process: + +- Set up the EDB repository. + + Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. + + To determine if your repository exists, enter this command: + + `dnf repolist | grep enterprisedb` + + If no output is generated, the repository isn't installed. + + To set up the EDB repository: + + 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads). + + 1. Select the button that provides access to the EDB repository. + + 1. Select the platform and software that you want to download. + + 1. Follow the instructions for setting up the EDB repository. + +- Install the EPEL repository: + + ```shell + sudo dnf -y install epel-release + ``` + +- Enable additional repositories to resolve dependencies: + ```shell + sudo dnf config-manager --set-enabled powertools + ``` + +## Install the package + +```shell +sudo dnf -y install edb-postgresextended16-server edb-postgresextended16-contrib +``` + +## Initial configuration + +Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. + +First, you need to initialize and start the database cluster. The `edb-pge-16-setup` script creates a cluster. + +```shell +sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/pge16/bin/edb-pge-16-setup initdb + +sudo systemctl start edb-pge-16 +``` + +To work in your cluster, log in as the postgres user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. + +```shell +sudo -iu postgres + +psql postgres +``` + +The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file. + +Before changing the authentication method, assign a password to the database superuser, postgres. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../administration/01_setting_configuration_parameters/#modifying-the-pg_hbaconf-file). + +```sql +ALTER ROLE postgres with PASSWORD 'password'; +``` + +## Experiment + +Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. + +First, use psql to create a database named `hr` to hold human resource information. + +```sql +# running in psql +CREATE DATABASE hr; +__OUTPUT__ +CREATE DATABASE +``` + +Connect to the `hr` database inside psql: + +``` +\c hr +__OUTPUT__ +You are now connected to database "hr" as user "postgres". +``` + +Create columns to hold department numbers, unique department names, and locations: + +``` +CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk +PRIMARY KEY, dname varchar(14) CONSTRAINT dept_dname_uq UNIQUE, loc +varchar(13)); +__OUTPUT__ +CREATE TABLE +``` + +Insert values into the `dept` table: + +``` +INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); +__OUTPUT__ +INSERT 0 1 +``` + +``` +INSERT into dept VALUES (20,'RESEARCH','DALLAS'); +__OUTPUT__ +INSERT 0 1 +``` + +View the table data by selecting the values from the table: + +``` +SELECT * FROM dept; +__OUTPUT__ +deptno | dname | loc +--------+------------+---------- +10 | ACCOUNTING | NEW YORK +20 | RESEARCH | DALLAS +(2 rows) +``` diff --git a/product_docs/docs/pge/17/installing/linux_x86_64/pge_other_linux_9.mdx b/product_docs/docs/pge/17/installing/linux_x86_64/pge_other_linux_9.mdx new file mode 100644 index 00000000000..5165da02a31 --- /dev/null +++ b/product_docs/docs/pge/17/installing/linux_x86_64/pge_other_linux_9.mdx @@ -0,0 +1,135 @@ +--- +navTitle: AlmaLinux 9 or Rocky Linux 9 +title: Installing EDB Postgres Extended Server on AlmaLinux 9 or Rocky Linux 9 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. + +redirects: +--- + +## Prerequisites + +Before you begin the installation process: + +- Set up the EDB repository. + + Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. + + To determine if your repository exists, enter this command: + + `dnf repolist | grep enterprisedb` + + If no output is generated, the repository isn't installed. + + To set up the EDB repository: + + 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads). + + 1. Select the button that provides access to the EDB repository. + + 1. Select the platform and software that you want to download. + + 1. Follow the instructions for setting up the EDB repository. + +- Install the EPEL repository: + + ```shell + sudo dnf -y install epel-release + ``` + +- Enable additional repositories to resolve dependencies: + ```shell + sudo dnf config-manager --set-enabled crb + ``` + +## Install the package + +```shell +sudo dnf -y install edb-postgresextended16-server edb-postgresextended16-contrib +``` + +## Initial configuration + +Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. + +First, you need to initialize and start the database cluster. The `edb-pge-16-setup` script creates a cluster. + +```shell +sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/pge16/bin/edb-pge-16-setup initdb + +sudo systemctl start edb-pge-16 +``` + +To work in your cluster, log in as the postgres user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. + +```shell +sudo -iu postgres + +psql postgres +``` + +The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file. + +Before changing the authentication method, assign a password to the database superuser, postgres. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../administration/01_setting_configuration_parameters/#modifying-the-pg_hbaconf-file). + +```sql +ALTER ROLE postgres with PASSWORD 'password'; +``` + +## Experiment + +Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. + +First, use psql to create a database named `hr` to hold human resource information. + +```sql +# running in psql +CREATE DATABASE hr; +__OUTPUT__ +CREATE DATABASE +``` + +Connect to the `hr` database inside psql: + +``` +\c hr +__OUTPUT__ +You are now connected to database "hr" as user "postgres". +``` + +Create columns to hold department numbers, unique department names, and locations: + +``` +CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk +PRIMARY KEY, dname varchar(14) CONSTRAINT dept_dname_uq UNIQUE, loc +varchar(13)); +__OUTPUT__ +CREATE TABLE +``` + +Insert values into the `dept` table: + +``` +INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); +__OUTPUT__ +INSERT 0 1 +``` + +``` +INSERT into dept VALUES (20,'RESEARCH','DALLAS'); +__OUTPUT__ +INSERT 0 1 +``` + +View the table data by selecting the values from the table: + +``` +SELECT * FROM dept; +__OUTPUT__ +deptno | dname | loc +--------+------------+---------- +10 | ACCOUNTING | NEW YORK +20 | RESEARCH | DALLAS +(2 rows) +``` diff --git a/product_docs/docs/pge/17/installing/linux_x86_64/pge_rhel_8.mdx b/product_docs/docs/pge/17/installing/linux_x86_64/pge_rhel_8.mdx new file mode 100644 index 00000000000..546c95cb66b --- /dev/null +++ b/product_docs/docs/pge/17/installing/linux_x86_64/pge_rhel_8.mdx @@ -0,0 +1,129 @@ +--- +navTitle: RHEL 8 or OL 8 +title: Installing EDB Postgres Extended Server on RHEL 8 or OL 8 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. + +redirects: +--- + +## Prerequisites + +Before you begin the installation process: + +- Set up the EDB repository. + + Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. + + To determine if your repository exists, enter this command: + + `dnf repolist | grep enterprisedb` + + If no output is generated, the repository isn't installed. + + To set up the EDB repository: + + 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads). + + 1. Select the button that provides access to the EDB repository. + + 1. Select the platform and software that you want to download. + + 1. Follow the instructions for setting up the EDB repository. + +- Install the EPEL repository: + ```shell + sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm + ``` + +## Install the package + +```shell +sudo dnf -y install edb-postgresextended16-server edb-postgresextended16-contrib +``` + +## Initial configuration + +Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. + +First, you need to initialize and start the database cluster. The `edb-pge-16-setup` script creates a cluster. + +```shell +sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/pge16/bin/edb-pge-16-setup initdb + +sudo systemctl start edb-pge-16 +``` + +To work in your cluster, log in as the postgres user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. + +```shell +sudo -iu postgres + +psql postgres +``` + +The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file. + +Before changing the authentication method, assign a password to the database superuser, postgres. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../administration/01_setting_configuration_parameters/#modifying-the-pg_hbaconf-file). + +```sql +ALTER ROLE postgres with PASSWORD 'password'; +``` + +## Experiment + +Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. + +First, use psql to create a database named `hr` to hold human resource information. + +```sql +# running in psql +CREATE DATABASE hr; +__OUTPUT__ +CREATE DATABASE +``` + +Connect to the `hr` database inside psql: + +``` +\c hr +__OUTPUT__ +You are now connected to database "hr" as user "postgres". +``` + +Create columns to hold department numbers, unique department names, and locations: + +``` +CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk +PRIMARY KEY, dname varchar(14) CONSTRAINT dept_dname_uq UNIQUE, loc +varchar(13)); +__OUTPUT__ +CREATE TABLE +``` + +Insert values into the `dept` table: + +``` +INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); +__OUTPUT__ +INSERT 0 1 +``` + +``` +INSERT into dept VALUES (20,'RESEARCH','DALLAS'); +__OUTPUT__ +INSERT 0 1 +``` + +View the table data by selecting the values from the table: + +``` +SELECT * FROM dept; +__OUTPUT__ +deptno | dname | loc +--------+------------+---------- +10 | ACCOUNTING | NEW YORK +20 | RESEARCH | DALLAS +(2 rows) +``` diff --git a/product_docs/docs/pge/17/installing/linux_x86_64/pge_rhel_9.mdx b/product_docs/docs/pge/17/installing/linux_x86_64/pge_rhel_9.mdx new file mode 100644 index 00000000000..c324e321d69 --- /dev/null +++ b/product_docs/docs/pge/17/installing/linux_x86_64/pge_rhel_9.mdx @@ -0,0 +1,129 @@ +--- +navTitle: RHEL 9 or OL 9 +title: Installing EDB Postgres Extended Server on RHEL 9 or OL 9 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. + +redirects: +--- + +## Prerequisites + +Before you begin the installation process: + +- Set up the EDB repository. + + Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. + + To determine if your repository exists, enter this command: + + `dnf repolist | grep enterprisedb` + + If no output is generated, the repository isn't installed. + + To set up the EDB repository: + + 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads). + + 1. Select the button that provides access to the EDB repository. + + 1. Select the platform and software that you want to download. + + 1. Follow the instructions for setting up the EDB repository. + +- Install the EPEL repository: + ```shell + sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm + ``` + +## Install the package + +```shell +sudo dnf -y install edb-postgresextended16-server edb-postgresextended16-contrib +``` + +## Initial configuration + +Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. + +First, you need to initialize and start the database cluster. The `edb-pge-16-setup` script creates a cluster. + +```shell +sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/pge16/bin/edb-pge-16-setup initdb + +sudo systemctl start edb-pge-16 +``` + +To work in your cluster, log in as the postgres user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. + +```shell +sudo -iu postgres + +psql postgres +``` + +The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file. + +Before changing the authentication method, assign a password to the database superuser, postgres. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../administration/01_setting_configuration_parameters/#modifying-the-pg_hbaconf-file). + +```sql +ALTER ROLE postgres with PASSWORD 'password'; +``` + +## Experiment + +Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. + +First, use psql to create a database named `hr` to hold human resource information. + +```sql +# running in psql +CREATE DATABASE hr; +__OUTPUT__ +CREATE DATABASE +``` + +Connect to the `hr` database inside psql: + +``` +\c hr +__OUTPUT__ +You are now connected to database "hr" as user "postgres". +``` + +Create columns to hold department numbers, unique department names, and locations: + +``` +CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk +PRIMARY KEY, dname varchar(14) CONSTRAINT dept_dname_uq UNIQUE, loc +varchar(13)); +__OUTPUT__ +CREATE TABLE +``` + +Insert values into the `dept` table: + +``` +INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); +__OUTPUT__ +INSERT 0 1 +``` + +``` +INSERT into dept VALUES (20,'RESEARCH','DALLAS'); +__OUTPUT__ +INSERT 0 1 +``` + +View the table data by selecting the values from the table: + +``` +SELECT * FROM dept; +__OUTPUT__ +deptno | dname | loc +--------+------------+---------- +10 | ACCOUNTING | NEW YORK +20 | RESEARCH | DALLAS +(2 rows) +``` diff --git a/product_docs/docs/pge/17/installing/linux_x86_64/pge_ubuntu_20.mdx b/product_docs/docs/pge/17/installing/linux_x86_64/pge_ubuntu_20.mdx new file mode 100644 index 00000000000..7f310a7a15a --- /dev/null +++ b/product_docs/docs/pge/17/installing/linux_x86_64/pge_ubuntu_20.mdx @@ -0,0 +1,124 @@ +--- +navTitle: Ubuntu 20.04 +title: Installing EDB Postgres Extended Server on Ubuntu 20.04 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. + +redirects: +--- + +## Prerequisites + +Before you begin the installation process: + +- Set up the EDB repository. + + Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. + + To determine if your repository exists, enter this command: + + `apt-cache search enterprisedb` + + If no output is generated, the repository isn't installed. + + To set up the EDB repository: + + 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads). + + 1. Select the button that provides access to the EDB repository. + + 1. Select the platform and software that you want to download. + + 1. Follow the instructions for setting up the EDB repository. + +## Install the package + +```shell +sudo apt-get -y install edb-postgresextended-16 +``` + +## Initial configuration + +This section steps you through getting started with your cluster including logging in, ensuring the installation was successful, connecting to your cluster, and creating the user password. + +First, you need to initialize and start the database cluster. The `edb-pge-16-setup` script creates a cluster. + +```shell +sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/lib/edb-pge/16/bin/edb-pge-16-setup initdb + +sudo systemctl start edb-pge-16 +``` + +To work in your cluster, log in as the postgres user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. + +```shell +sudo -iu postgres + +psql postgres +``` + +The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file. + +Before changing the authentication method, assign a password to the database superuser, postgres. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../administration/01_setting_configuration_parameters/#modifying-the-pg_hbaconf-file). + +```sql +ALTER ROLE postgres with PASSWORD 'password'; +``` + +## Experiment + +Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. + +First, use psql to create a database named `hr` to hold human resource information. + +```sql +# running in psql +CREATE DATABASE hr; +__OUTPUT__ +CREATE DATABASE +``` + +Connect to the `hr` database inside psql: + +``` +\c hr +__OUTPUT__ +You are now connected to database "hr" as user "postgres". +``` + +Create columns to hold department numbers, unique department names, and locations: + +``` +CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk +PRIMARY KEY, dname varchar(14) CONSTRAINT dept_dname_uq UNIQUE, loc +varchar(13)); +__OUTPUT__ +CREATE TABLE +``` + +Insert values into the `dept` table: + +``` +INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); +__OUTPUT__ +INSERT 0 1 +``` + +``` +INSERT into dept VALUES (20,'RESEARCH','DALLAS'); +__OUTPUT__ +INSERT 0 1 +``` + +View the table data by selecting the values from the table: + +``` +SELECT * FROM dept; +__OUTPUT__ +deptno | dname | loc +--------+------------+---------- +10 | ACCOUNTING | NEW YORK +20 | RESEARCH | DALLAS +(2 rows) +``` diff --git a/product_docs/docs/pge/17/installing/linux_x86_64/pge_ubuntu_22.mdx b/product_docs/docs/pge/17/installing/linux_x86_64/pge_ubuntu_22.mdx new file mode 100644 index 00000000000..61a6656848e --- /dev/null +++ b/product_docs/docs/pge/17/installing/linux_x86_64/pge_ubuntu_22.mdx @@ -0,0 +1,124 @@ +--- +navTitle: Ubuntu 22.04 +title: Installing EDB Postgres Extended Server on Ubuntu 22.04 x86_64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. + +redirects: +--- + +## Prerequisites + +Before you begin the installation process: + +- Set up the EDB repository. + + Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. + + To determine if your repository exists, enter this command: + + `apt-cache search enterprisedb` + + If no output is generated, the repository isn't installed. + + To set up the EDB repository: + + 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads). + + 1. Select the button that provides access to the EDB repository. + + 1. Select the platform and software that you want to download. + + 1. Follow the instructions for setting up the EDB repository. + +## Install the package + +```shell +sudo apt-get -y install edb-postgresextended-16 +``` + +## Initial configuration + +This section steps you through getting started with your cluster including logging in, ensuring the installation was successful, connecting to your cluster, and creating the user password. + +First, you need to initialize and start the database cluster. The `edb-pge-16-setup` script creates a cluster. + +```shell +sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/lib/edb-pge/16/bin/edb-pge-16-setup initdb + +sudo systemctl start edb-pge-16 +``` + +To work in your cluster, log in as the postgres user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. + +```shell +sudo -iu postgres + +psql postgres +``` + +The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file. + +Before changing the authentication method, assign a password to the database superuser, postgres. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../administration/01_setting_configuration_parameters/#modifying-the-pg_hbaconf-file). + +```sql +ALTER ROLE postgres with PASSWORD 'password'; +``` + +## Experiment + +Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. + +First, use psql to create a database named `hr` to hold human resource information. + +```sql +# running in psql +CREATE DATABASE hr; +__OUTPUT__ +CREATE DATABASE +``` + +Connect to the `hr` database inside psql: + +``` +\c hr +__OUTPUT__ +You are now connected to database "hr" as user "postgres". +``` + +Create columns to hold department numbers, unique department names, and locations: + +``` +CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk +PRIMARY KEY, dname varchar(14) CONSTRAINT dept_dname_uq UNIQUE, loc +varchar(13)); +__OUTPUT__ +CREATE TABLE +``` + +Insert values into the `dept` table: + +``` +INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); +__OUTPUT__ +INSERT 0 1 +``` + +``` +INSERT into dept VALUES (20,'RESEARCH','DALLAS'); +__OUTPUT__ +INSERT 0 1 +``` + +View the table data by selecting the values from the table: + +``` +SELECT * FROM dept; +__OUTPUT__ +deptno | dname | loc +--------+------------+---------- +10 | ACCOUNTING | NEW YORK +20 | RESEARCH | DALLAS +(2 rows) +``` diff --git a/product_docs/docs/pge/17/operation.mdx b/product_docs/docs/pge/17/operation.mdx new file mode 100644 index 00000000000..2fbcc4aef69 --- /dev/null +++ b/product_docs/docs/pge/17/operation.mdx @@ -0,0 +1,42 @@ +--- +title: Operations +originalFilePath: operation.md +description: Operational features of EDB Postgres Extended Server including WAL pacing delays, additional tracing and diagnostics options. +--- + +EDB Postgres Extended Server has a number of features that relate to operations. + +## Avoid flooding transaction logs + +EDB Postgres Extended Server provides WAL pacing delays to avoid flooding transaction logs. The WAL pacing configuration parameters are: + - `wal_insert_delay_enabled` + - `wal_insert_delay` + - `wal_insert_delay_size` + +When `wal_insert_delay_enabled` is enabled, a session sleeps based on the value of `wal_insert_delay` after WAL data of at least the value of `wal_insert_delay_size` is generated. The default is off. + +## Additional tracing and diagnostics options + +EDB Postgres Extended Server allows you to enable timeouts based on logging trace messages in specific code +paths. Use the `tracelog_timeout` configuration parameter to allow logging of trace messages after a timeout of +the specified time occurs. + +## Selective physical base backup and subsequent selective recovery/restore + +By default, backups are always taken of the entire database cluster. You can also back up individual databases or database objects by specifying +the `-L` option with the `pg_basebackup` utility multiple times for multiple databases. + +Template databases are backed up by default. WAL data for excluded +databases is still part of the WAL archives. + +The backup activity stores the list of database objects specified using this option +in the backup label file. The presence of these objects in the backup label file causes selective recovery of these databases. Recovery of template +databases and of global metadata related to users, languages, and so on is also carried +out as usual. WAL data belonging to excluded databases is ignored during the +recovery process. Attempts to connect to excluded databases cause errors after regular +operations start following the recovery. + + +## Additional operations feature + +- Reduced locking of `ALTER TABLE ... REPLICA IDENTITY` diff --git a/product_docs/docs/pge/17/parameters.mdx b/product_docs/docs/pge/17/parameters.mdx new file mode 100644 index 00000000000..7b4f140bb2d --- /dev/null +++ b/product_docs/docs/pge/17/parameters.mdx @@ -0,0 +1,147 @@ +--- +navTitle: Configuration parameters +title: Configuration parameters (GUCs) +originalFilePath: parameters.md +description: Configuration parameters available with EDB Postgres Extended Server. +--- + +These Grand Unified Configuration (GUC) configuration parameters are available with EDB Postgres Extended Server. + +## Backend parameters + +Backend parameters introduce a test probe point infrastructure for injecting sleeps or errors into PostgreSQL and extensions. + +Any `PROBE_POINT` defined throughout the Postgres code code marks important code paths. These probe points might be activated to signal the current backend or to elog(...) a `LOG`/`ERROR`/`FATAL`/`PANIC`. They might also, or instead, add a delay at that point in the code. + +Unless explicitly activated, probe points have no effect and add only a single optimizer-hinted branch, so they're safe on hot paths. + +When an active probe point is hit and the counter is satisfied, after any specified sleep interval, a log message is always emitted at `DEBUG1` or higher. + +### `pg2q.probe_point` + +The name of a `PROBE_POINT` in the code of 2ndQPostgres or in an extension that defines a `PROBE_POINT`. This parameter isn't validated. If a nonexistent probe point is named, it's never hit. + +Only one probe point can be active. This isn't a list, and attempting to supply a list means nothing matches. + +Probe points generally have a unique name, given as the argument to the `PROBE_POINT` macro in the code where it's defined. It's also possible to use the same `PROBE_POINT` name where multiple code paths trigger the same action of interest. A probe fires when either path is taken. + +### `pg2q.probe_counter` + +You might need to act on a probe only after a loop is run for the number of times specified with this parameter. In such cases, set this GUC to the number of iterations at which point the probe point fires, and reset the counter. + +The default value is `1`, meaning the probe points always fire when the name matches. + +### `pg2q.probe_sleep` + +Sleep for `pg2q.probe_sleep` milliseconds after hitting the probe point. Then fire the action in `pg2q.probe_action`. + +### `pg2q.probe_action` + +Action to take when the named `pg2q.probe_point` is hit. Available actions are: + +- `sleep` — Emit a `DEBUG` message with the probe name. +- `log` — Emit a `LOG` message with the probe name. +- `error` — `elog(ERROR, ...)` to raise an `ERROR` condition. +- `fatal`— `elog(FATAL, ...)`. +- `panic` — `elog(PANIC, ...)`, which generally then calls `abort()` and delivers a `SIGABRT` (signal 6) to cause the backend to core dump. The probe point tries to set the core file limit to enable core dumps if the hard ulimit permits. +- `sigint`, `sigterm`, `sigquit`, `sigkill` — Deliver the named signal to the backend that hit the probe point. + +### `pg2q.probe_backend_pid` + +If nonzero, the probe sleep and action are skipped for backends other than the backend with this ID. + +## `server_2q_version_num` and `server_2q_version` + +The `server_2q_version_num` and `server_2q_version` configuration parameters allow the 2ndQuadrant-specific version number and version substring, respectively, to be accessible to external modules. + +## Table-level compression control option + +You can set the table-level option `compress_tuple_target` to decide when to trigger compression on a tuple. Previously, you used the `toast_tuple_target` (or the compile time default) to decide whether to compress a tuple. However, this was detrimental when a tuple is large enough and has a good compression ratio but not large enough to cross the toast threshold. + + + +## `pg2q.max_tuple_field_size` + +Restricts the maximum uncompressed size of the internal representation of any one field that can be written to a table, in bytes. + +The default `pg2q.max_tuple_field_size` is 1073740799 bytes, which is 1024 bytes less than 1 GiB. This value is slightly less than the 1 GiB maximum field size usually imposed by PostgreSQL. This margin helps prevent cases where tuples are committed to disk but can't then be processed by logical decoding output plugins and sent to downstream servers. + +Set `pg2q.max_tuple_field_size` to `1GB` or `11073741823` to disable the feature. + +If your application doesn't rely on inserting large fields, consider setting `pg2q.max_tuple_field_size` to a much smaller value, such as 100MB or even less. Among other issues, large fields can: + +- Cause surprising application behavior +- Increase memory consumption for the database engine during queries and replication +- Slow down logical replication + +While this parameter is enabled, oversized fields cause queries that `INSERT` or `UPDATE` an oversized field to fail with an `ERROR` such as: + +``` +ERROR: field big_binary_field_name in row is larger than pg2q.max_tuple_field_size +DETAIL: New or updated row in relation some_table has field big_binary_field_name + (attno=2) with size 8161 bytes which exceeds limit 1073740799B configured + in pg2q.max_tuple_field_size +SQLSTATE: 53400 configuration_limit_exceeded +``` + +Only the superuser can set `pg2q.max_tuple_field_size`. You can use a `SECURITY DEFINER` function wrapper if you want to allow a non-superuser to set it. + +If you change `pg2q.max_tuple_field_size`, fields larger than the current `pg2q.max_tuple_field_size` that are already on disk don't change. You can `SELECT` them as usual. Any `UPDATE` that affects tuples with oversized fields fails, even if the oversized field isn't modified, unless the new tuple created by the update operation satisfies the currently active size limits. + +A `DELETE` operation doesn't check the field-size limit. + +The limit isn't enforced on the text-representation size for I/O of fields because doing so also prevents PostgreSQL from creating and processing temporary in-memory json objects larger than the limit. + +The limit isn't enforced for temporary tuples in tuplestores, such as set-returning functions, CTEs, and views. Size checks are deliberately not enforced for any `MATERIALIZED VIEW` either. + +!!! WARNING + `pg2q.max_tuple_field_size` is enforced for `pg_restore`. If a + database contains oversized tuples, it does a `pg_dump` as usual. However, a + subsequent `pg_restore` fails with the error shown previously. To work around + this issue, restore the dump with `pg2q.max_tuple_field_size` overridden in + connection options using `PGOPTIONS` or the `options` connection-parameter + string. For example: + + ``` + PGOPTIONS='-c pg2q.max_tuple_field_size=11073741823' pg_restore ... + ``` + +Data type specifics: + +- For a `bytea` field, the size used is the decoded binary size. It isn't the text-representation size in hex or octal escape form, that is, the `octet_length()` of the field. + + Assuming `bytea_output = 'hex'`, the maximum size of the I/O representation is `2 * pg2q.max_tuple_field_size + 2` bytes. + +- For a `text`, `json`, or `xml` field, the measured size is the number of bytes of text in the current database encoding (the `octet_length()` of the field), not the number of characters. In UTF-8 encodings, one character usually consumes one byte but might consume six or more bytes for some languages and scripts. + +- For a `jsonb` field, the measured size is that of the PostgreSQL internal jsonb-encoded datatype representation, the text representation of the json document. In some cases the `jsonb` representation for larger json documents is smaller than the text representation. This means that it's possible to insert json documents with text representations larger than any given `pg2q.max_tuple_field_size`, although it's uncommon. + +- Extension-defined data type behavior depends on the implementation of the data type. + + The field size used for this limit is the size reported by them `pg_column_size()` function, minus the 4 bytes of header PostgreSQL adds to variable-length data types, when used on a literal of the target data type. For example: + + ``` + demo=> SELECT pg_column_size(BYTEA '\x00010203040506070809') - 4; + 14 + ``` + + For example, to see the computed size of the jsonb field, use: + + ``` + SELECT pg_column_size(JSONB '{"my_json_document": "yes"}') - 4; + ``` + + Due to TOAST compression ,`pg_column_size()` often reports smaller + values when called on existing on-disk fields. Also, the header for + shorter values on disk might be 1 byte instead of 4. + +## `pg2q.max_tuple_size` + +Restricts the maximum size of a single tuple that can be written to a table. This value is the total row width, including the uncompressed width of all potentially compressible or external-storage-capable field values. Field headers count against the size, but fixed row headers don't. + +Many PostgreSQL operations, such as logical replication, work on whole rows, as do many applications. You can use this setting to impose a limit on the maximum row size you consider reasonable for your application to prevent inadvertent creation of oversized rows that might pose operational issues. + +When applied to an `UPDATE` of existing tuples, `pg2q.max_tuple_size` isn't enforced as strictly as `pg2q.max_tuple_field_size`. It doesn't count the full size of unmodified values in columns with storage other than `PLAIN`. + +!!! WARNING + `pg2q.max_tuple_size` is enforced for `pg_restore`. See the caveat for `pg2q.max_tuple_field_size`. diff --git a/product_docs/docs/pge/17/release_notes/index.mdx b/product_docs/docs/pge/17/release_notes/index.mdx new file mode 100644 index 00000000000..1b96b3cd1b5 --- /dev/null +++ b/product_docs/docs/pge/17/release_notes/index.mdx @@ -0,0 +1,15 @@ +--- +title: "Release notes" +description: "Release notes for EDB Postgres Extended Server 17." +navigation: + - rel_notes17.2 +--- +The EDB Postgres Extended Server documentation describes the latest version of EDB Postgres Extended Server 17, including minor releases and patches. These release notes cover what was new in each release. + +| Version | Release date | +|---------------------------|--------------| +| [17.2](rel_notes17.2) | 22 Nov 2024 | + + + + diff --git a/product_docs/docs/pge/17/release_notes/rel_notes17.2.mdx b/product_docs/docs/pge/17/release_notes/rel_notes17.2.mdx new file mode 100644 index 00000000000..90883c2a010 --- /dev/null +++ b/product_docs/docs/pge/17/release_notes/rel_notes17.2.mdx @@ -0,0 +1,12 @@ +--- +title: EDB Postgres Extended Server 17.2 release notes +navTitle: "Version 17.2" +--- + +Released: 22 Nov 2024 + +EDB Postgres Extended Server 17.2 includes the following enhancements and bug fixes: + +| Type | Description | Addresses | +|----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------| +| Upstream merge | Merged with community PostgreSQL 17.2. See the [PostgreSQL 17.2 Release Notes](https://www.postgresql.org/docs/17/release-17-2.html) for more information. | | diff --git a/product_docs/docs/pge/17/replication.mdx b/product_docs/docs/pge/17/replication.mdx new file mode 100644 index 00000000000..c7557bc05b4 --- /dev/null +++ b/product_docs/docs/pge/17/replication.mdx @@ -0,0 +1,33 @@ +--- +navTitle: Replication +title: Replication +originalFilePath: replication.md +description: EDB Postgres Extended Server provides the core functionality to support replication and high-availability features in EDB Postgres Distributed. +--- + + +EDB Postgres Extended Server provides the core functionality to support the following replication and high availability features in [EDB Postgres Distributed](/pgd/latest): + +- Commit At Most Once (CAMO) +- Group commit +- Eager replication +- Decoding worker +- Assessment tooling +- Lag tracker +- Lag control +- Timestamp snapshots +- Transaction streaming +- Missing partition conflict +- No need for UPDATE trigger on tables with TOAST +- Automatically hold back FREEZE + +## Asynchronous processing + +EDB Postgres Extended Server includes a `synchronous_replication_availability` parameter. +A value of `async` for this parameter enables asynchronous +processing when not enough standby +servers are available (when compared with the values as per +`synchronous_standby_names`). The behavior reverts +to synchronous replication when the required number of synchronous +standby servers reappear. + diff --git a/product_docs/docs/pge/17/sql_features/index.mdx b/product_docs/docs/pge/17/sql_features/index.mdx new file mode 100644 index 00000000000..adec227d769 --- /dev/null +++ b/product_docs/docs/pge/17/sql_features/index.mdx @@ -0,0 +1,57 @@ +--- +title: SQL enhancements +originalFilePath: compat.md +description: EDB Postgres Extended Server includes a number of SQL enhancements including rollback options, cursors with prepared statements, and PL/pgSQL compatibility. +navigation: + - txnrollback + - jdbctxnroolback +--- +EDB Postgres Extended Server includes a number of SQL enhancements. + +## Rollback options + +In PostgreSQL, any error in a transaction rolls back all actions +by that transaction. This behavior is different from other DBMS, such +as Oracle and SQL Server, where an error causes rollback of only the last +statement. This difference in transaction handling semantics +doesn't cause a problem in all cases, but it does make implementing business logic +in PostgreSQL difficult for Oracle Database and Microsoft SQL Server developers. + +One workaround is to manually introduce a savepoint, internally known as +subtransactions, into the application code. This is time consuming and +difficult to test. A savepoint is an additional statement and therefore increases +transaction latency. Given the overhead of additional development work +and slower performance, this approach isn't viable in most cases. + +EDB Postgres Extended Server allows you to roll back just the current statement. +The statement-level rollback feature provides an +optional mode to choose whether to allow rollback of the whole transaction +or just the current statement. No manual recoding is required. There's some added overhead, but it's lower than for a savepoint. + +See [`transaction_rollback_scope`](txnrollback) for information on setting the transaction rollback scope inside the database and [JDBC properties for rollback scope](jdbctxnrollback) for information on continuing past an error on a JDBC batch job. + + + +## Cursors with prepared statements + +EDB Postgres Extended Server allows declaring a cursor over a previously created prepared statement. + +For example: + + ``` + PREPARE foo AS ...; DECLARE c1 CURSOR FOR foo; + ``` + +## PL/pgSQL compatibility + +EDB Postgres Extended Server integrates with other migration tools with a number of PL/pgSQL compatibility features. + +For general simplicity, EDB Postgres Extended Server allows calling functions using plpqsl without the PERFORM keyword. + +For example, + +``` +BEGIN somefunc(); END +``` + +Where `somefunc` is not a keyword. diff --git a/product_docs/docs/pge/17/sql_features/jdbctxnrollback.mdx b/product_docs/docs/pge/17/sql_features/jdbctxnrollback.mdx new file mode 100644 index 00000000000..f2269a4ec46 --- /dev/null +++ b/product_docs/docs/pge/17/sql_features/jdbctxnrollback.mdx @@ -0,0 +1,111 @@ +--- +title: JDBC properties for setting rollback scope +originalFilePath: jdbctxnrollback.md + +--- + +If you're using a JDBC connector to connect to a client application, you use the `autosave` and `transaction_rollback_scope` properties together to specify the transaction rollback scope. + +You can specify these properties in either the connection URL or as an +additional properties object parameter to `DriverManager.getConnection`. + +## autosave + +The `autosave` parameter is a string that specifies what the driver does if a query containing +multiple statements fails. The possible values are: `server`, `always`, `never`, and `conservative`. + +- In `autosave=server` mode, JDBC relies on the server-side parameter `transaction_rollback_scope` +to save each statement by way of internal server savepoints before +executing the next. The server rolls back to the previous +statement if any statement in the query fails. If this parameter +isn't supported on the server side, JDBC rejects the connection. + +- In `autosave=always` mode, the JDBC driver first tries to use the server-side `transaction_rollback_scope` property. If it isn't supported, +then JDBC driver sets a savepoint before each query +statement and rolls back to that savepoint in case of failure. + +- In `autosave=never` mode (default), no savepoint activity is ever +carried out. In `autosave=conservative` mode, savepoint is set for +each query. However, the rollback is done only for rare cases like +'cached statement cannot change return type' or 'statement XXX is +not valid', so JDBC driver rolls back and retries. + +The default value for this property is `never`. + +This `autosave=server` property is useful only +with the PostgreSQL server providing `transaction_rollback_scope` +functionality. + +## transaction_rollback_scope + +The `autosave` parameter is a string that determines the range of +operations that roll back when an SQL statement fails. + +The default value is `TRANSACTION`, which causes the entire transaction or +current subtransaction to roll back. This is the only mode +that you can select with the `SET TRANSACTION` command. + +You can specify the other possible mode, `STATEMENT`, only during connection establishment, `ALTER USER`, or `ALTER DATABASE`. In that mode, only +the failed `SQL` statement is rolled back, and the transaction is put back in normal mode. + +## `autosave` test cases +Test cases for trying out values of the `autosave` property +are available in the `BatchAutoSaveTest.java` file. The following +SQL code shows the behavior that's expected when the +server provides `transaction_rollback_scope` functionality and +`autosave=server` is used on the JDBC side. + +With `autosave=server`, the following query inserts values `(1)`, `(3)`, and +`(4)` and disregards the `duplicate key violation` error: + +```sql +CREATE TABLE test (id INT PRIMARY KEY); +INSERT INTO test VALUES (2); +BEGIN; +INSERT INTO test VALUES (1); +INSERT INTO test VALUES (2); +INSERT INTO test VALUES (3); +INSERT INTO test VALUES (4); +COMMIT; +``` + + +The `artifacts` directory contains the `pgjdbc` jar file +`postgresql-REL2Q.42.2.3.180601.jar`. This file needs to +be added to the CLASSPATH as usual. It also contains the +`postgresql-REL2Q.42.2.3.180601-tests.jar` jar that can be used to test +the latest `autosave` functionality. + +You can test the `BatchAutoSaveTest.java` file provided in the `artifacts` as follows: + +1. Export CLASSPATH to build and run the test case: + + ```sh + cd artifacts + export CLASSPATH=$PWD:$PWD/postgresql-REL2Q.42.2.3.180601-tests.jar:$PWD/postgresql-REL2Q.42.2.3.180601.jar:$PWD/junit-4.12.jar:$PWD/hamcrest-core-1.3.jar + ``` + +1. Compile the supplied test file: + + ```sh + javac -d . BatchAutoSaveTest.java + ``` + +1. Run the test (assuming user as `test` and running on localhost): + + ```shell + java -Dusername=test -Dport=5432 -Dhost=localhost -Ddatabase=postgres org.junit.runner.JUnitCore org.postgresql.test.jdbc2.BatchAutoSaveTest + __OUTPUT__ + JUnit version 4.12 + .Configuration file /Users/altaf/pg/artifacts/../build.properties does not exist. Consider adding it to specify test db host and login + Configuration file /Users/altaf/pg/artifacts/../build.local.properties does not exist. Consider adding it to specify test db host and login + Configuration file /Users/altaf/pg/artifacts/../build.properties does not exist. Consider adding it to specify test db host and login + Configuration file /Users/altaf/pg/artifacts/../build.local.properties does not exist. Consider adding it to specify test db host and login + ......... + Time: 0.556 + + OK (10 tests) + ``` + +To modify the test cases, you can modify the `BatchAutoSaveTest.java` file +in the `artifacts` directory. Then compile and run the test cases. diff --git a/product_docs/docs/pge/17/sql_features/txnrollback.mdx b/product_docs/docs/pge/17/sql_features/txnrollback.mdx new file mode 100644 index 00000000000..c4c8feb5f79 --- /dev/null +++ b/product_docs/docs/pge/17/sql_features/txnrollback.mdx @@ -0,0 +1,55 @@ +--- +title: "transaction_rollback_scope parameter" +originalFilePath: txnrollback.md + +--- + +To set the transaction rollback scope inside the database, use the `transaction_rollback_scope` parameter. +The `transaction_rollback_scope` parameter has two possible values: + +- `transaction` — Standard Postgres behavior, where each error +aborts the whole transaction. + +- `statement`— An error while executing one statement affects only +that statement and not the status of the transaction as a whole. + +## Setting the parameter + +You can set the parameter as a user-level property, a connection option, or the mode for specific functions or procedures. + +### Set the parameter as a user-level property + +```sql +ALTER USER somebody SET transaction_rollback_scope TO statement; +``` + +### Set the parameter as a connection option + +```sh-session +PGOPTIONS="-c transaction_rollback_scope=statement" psql +``` + +### Set the mode for specific functions or procedures + +If using PL/pgSQL, you can set the mode for specific functions or procedures: + +```sql +ALTER FUNCTION myfunc SET transaction_rollback_scope TO statement; +``` + +## How subtransactions are handled + +If you select the `statement` value, then a subtransaction is opened just before each SQL +command. If the command is successful, the subtransaction is *committed*. If the command causes an error, the subtransaction is +rolled back, and the parent transaction can continue normally. The +effect is that an error during execution of one statement affects only +that statement and not the status of the transaction as a whole. + +Committing a subtransaction assigns the +resources it holds only to its parent transaction, which might be the top-level +transaction. Or it might be some other subtransaction if there are user-defined +savepoints involved. So this is not an "autonomous transaction." +Rolling back a subtransaction releases all the +resources it holds, such as any locks it acquired. + + diff --git a/product_docs/docs/pge/17/tde.mdx b/product_docs/docs/pge/17/tde.mdx new file mode 100644 index 00000000000..e5c33231759 --- /dev/null +++ b/product_docs/docs/pge/17/tde.mdx @@ -0,0 +1,8 @@ +--- +title: Transparent data encryption +description: Transparent data encryption (TDE) encrypts any user data stored in the database system. +--- + +Transparent data encryption (TDE) encrypts any user data stored in the database system. This encryption is transparent to the user. User data includes the actual data stored in tables and other objects as well as system catalog data such as the names of objects. + +See [Transparent data encryption](/tde/latest) for more information. \ No newline at end of file diff --git a/product_docs/docs/pge/17/upgrading/index.mdx b/product_docs/docs/pge/17/upgrading/index.mdx new file mode 100644 index 00000000000..094ca214b6c --- /dev/null +++ b/product_docs/docs/pge/17/upgrading/index.mdx @@ -0,0 +1,11 @@ +--- +navTitle: Upgrading +title: Upgrading EDB Postgres Extended Server +description: How to upgrade EDB Postgres Extended Server to a more recent version. +--- + +You can upgrade EDB Postgres Extended Server installations to a more recent version. + +- See [Upgrading a major version of EDB Postgres Extended Server](major_upgrade) for a major upgrade example. + +- See [Upgrading a minor version of EDB Postgres Extended Server](minor_upgrade) for minor upgrade examples according to your package format. diff --git a/product_docs/docs/pge/17/upgrading/major_upgrade.mdx b/product_docs/docs/pge/17/upgrading/major_upgrade.mdx new file mode 100644 index 00000000000..c8845a87db4 --- /dev/null +++ b/product_docs/docs/pge/17/upgrading/major_upgrade.mdx @@ -0,0 +1,155 @@ +--- +navTitle: "Major upgrades" +title: "Major version upgrade of EDB Postgres Extended Server" +description: Perform a major version upgrade of EDB Postgres Extended Server. +deepToc: true +--- + +To perform a major version upgrade, install the new version of EDB Postgres Extended Server, initialize an empty cluster and use pg_upgrade to migrate all data. + +If a problem occurs during the upgrade process, you can [revert to the previous version](/epas/latest/upgrading/major_upgrade/06_reverting_to_the_old_cluster/#reverting_to_the_old_cluster). + +## Overview + +1. [Prepare your upgrade](#preparing-your-upgrade) by performing a backup of the existing instance. +1. [Install the EDB Postgres Extended Server version](#installing-the-target-edb-postgres-extended-server-version) you're upgrading toward. +1. [Create a new database server](#creating-a-target-server): + 1. Create an empty directory for the new server and ensure postgres owns it. + 1. Initialize a server on a different port from the source server. + 1. Start the database server. + 1. Connect to the database server and ensure it's functioning. +1. [Upgrade to the target server](#upgrading-to-the-target-server): + 1. Stop both the source and the new server. + 1. Use pg_upgrade by specifying the source and target bin and data directories. + 1. Start the new database server. + 1. Connect to the encrypted database server and ensure the data was transferred. +1. [Clean up and delete the source server](#cleaning-up-after-upgrade): + 1. Clean up the database and its statistics. + 1. Remove the source EDB Postgres Extended Server cluster with the script provided by pg_upgrade. + +## Worked example + +This worked example upgrades an EDB Postgres Extended Server 15 database to EDB Postgres Extended Server 16. + +!!!note + You can perform major upgrades of EDB Postgres Extended Server instances in the same way you upgrade an EDB Postgres Advanced Server installation. If you need more information about the pg_upgrade utility, command line options, troubleshooting, and more, see [Upgrading an installation with pg_upgrade](/epas/latest/upgrading/major_upgrade/). + +### Preparing your upgrade + +Use [pg_dumpall](https://www.postgresql.org/docs/current/app-pg-dumpall.html), [pgBackRest](/supported-open-source/pgbackrest/), or [Barman](/supported-open-source/barman/) to create a backup of your source server. + +### Installing the target EDB Postgres Extended Server version + +[Install EDB Postgres Extended Server](../installing/) version 16. Only install the packages. Don't perform any other configurations. + +### Creating a target server + +If you don't want to create a new target instance but want to reuse an existing server with the target EDB Postgres Extended Server version, skip these steps and [ensure the target server is empty](/epas/latest/upgrading/major_upgrade/03_upgrading_to_advanced_server/#step-2---empty-the-target-database). + +1. As postgres, create an empty directory for the new server: + + ``` + mkdir /var/lib/edb-pge/16/upgrade_target + ``` + +1. As root, ensure the postgres user owns the directory: + + ``` + sudo chown postgres /var/lib/edb-pge/16/upgrade_target + sudo chgrp postgres /var/lib/edb-pge/16/upgrade_target + ``` + +1. As postgres, initialize the new server: + + ``` + /usr/lib/edb-pge/16/bin/initdb -D /var/lib/edb-pge/16/upgrade_target + ``` + + This command initializes a CONFIG directory with all configuration files for the encrypted server. + +1. Before you start the cluster, ensure the new database runs on a different port from the source server. To alter the port, edit `postgresql.conf` by uncommenting the line with `#port` and changing the port number, for example, to 5432. + +1. Start the target server: + + ``` + /usr/lib/edb-pge/16/bin/pg_ctl -D /var/lib/edb-pge/16/upgrade_target start + ``` + + !!!note + You can also start the server with the `logfile` option enabled to print errors into a logfile: + `/usr/lib/edb-pge/16/bin/pg_ctl -D /var/lib/edb-pge/16/upgrade_target -l logfile start` + + In this case, ensure the postgres user has rights to write to the log directory. + +1. Connect to the server: + + ``` + /usr/lib/edb-pge/16/bin/psql -p 5432 + ``` + + !!!note + If you're using two different Postgres versions, use the psql utility of the target server. Otherwise, the system will attempt to use psql from the previous instance. + +### Upgrading to the target server + +1. If you have any extensions or component services running in the source cluster, stop them before starting the upgrade. See [Stop all component services and servers](/epas/latest/upgrading/major_upgrade/03_upgrading_to_advanced_server/#step-4---stop-all-component-services-and-servers) for more information + +1. Stop both the source and target servers: + + ``` + /usr/lib/edb-pge/15/bin/pg_ctl -D /var/lib/edb-pge/15/upgrade-source stop + /usr/lib/edb-pge/16/bin/pg_ctl -D /var/lib/edb-pge/16/upgrade-target stop + ``` + +1. To test for incompatibilities, run the `pg_upgrade` command in check mode. + + With `-b` and `-B`, specify the source and target BIN directories. With `-d` and `-D`, specify the source and target CONFIG directories: + + ``` + /usr/lib/edb-pge/16/bin/pg_upgrade -b /usr/lib/edb-pge/15/bin -B /usr/lib/edb-pge/16/bin -d /var/lib/edb-pge/15/upgrade-source -D /var/lib/edb-pge/16/upgrade-target --check + ``` + + !!!note + The `--check` mode performs preliminary checks without executing the command. + +1. To copy data from the source server to the target server, run the `pg_upgrade` command in normal mode: + + ``` + /usr/lib/edb-pge/16/bin/pg_upgrade -b /usr/lib/edb-pge/15/bin -B /usr/lib/edb-pge/16/bin -d /var/lib/edb-pge/15/upgrade-source -D /var/lib/edb-pge/16/upgrade-target + ``` + +1. Start the target server: + + ``` + /usr/lib/edb-pge/16/bin/pg_ctl -D /var/lib/edb-pge/16/upgrade-target start + ``` + +1. Connect to the target database server: + + ``` + /usr/lib/edb-as/16/bin/psql -p 5432 + ``` + +1. Perform a spot check to ensure the databases, tables, schemas, and resources you had in the unencrypted server are available in the new server. For example, list all databases, explore the database objects, views, and so on. + +1. Restart the extensions or component services you disabled in the source cluster but in the target cluster. + +### Cleaning up after upgrade + +After you verify that pg_upgrade migrated the data successfully, and the services are running as expected, perform a cleanup. + +1. Clean up the database and its statistics: + + ``` + /usr/lib/edb-pge/16/bin/vacuumdb --all --analyze-in-stages + ``` + +1. Remove all data files of the unencrypted server with the script generated by `pg_upgrade`: + + ``` + ./delete_old_cluster.sh + ``` + +## More information + +Review [Upgrading an installation with pg_upgrade](/epas/latest/upgrading/major_upgrade/) for more information on pg_upgrade options, troubleshooting, and other considerations. diff --git a/product_docs/docs/pge/17/upgrading/minor_upgrade/apt_upgrade.mdx b/product_docs/docs/pge/17/upgrading/minor_upgrade/apt_upgrade.mdx new file mode 100644 index 00000000000..18cc18753e7 --- /dev/null +++ b/product_docs/docs/pge/17/upgrading/minor_upgrade/apt_upgrade.mdx @@ -0,0 +1,65 @@ +--- +title: "Minor EDB Postgres Extended Server upgrade of Debian packages" +navTitle: "Minor upgrades on Debian environments" +description: "Perform a minor version upgrade of EDB Postgres Extended Server with the apt-get package manager" +--- + +If you used `apt-get` to install a Debian package of EDB Postgres Extended Server (on Ubuntu, Debian), use `apt-get` to perform a minor version upgrade of the packages. + +## Overview + +1. Upgrade the EDB Postgres Extended Server packages with `apt-get install`. + +1. Restart the server with `pg_ctl`. + +1. Verify the server version with psql. + +## Worked example + +1. To upgrade the existing packages, open a command line, assume root privileges, and enter the command: + + ```shell + sudo apt-get install + ``` + + For example, if you want to upgrade to the latest minor version of EDB Postgres Extended Server 16, run: + + ```shell + sudo apt-get install edb-postgresextended-16 + ``` + + !!!Note + You can perform a search of the packages to ensure you update the right package beforehand. For example, to browse through all EDB Packages, you can run `sudo apt-cache edb`. For more information about using `apt-get` commands and options, enter `apt-get --help` at the command line. + +1. Confirm with `Y`. + + The output displays an overview of all performed processes, where you can see the packages that were upgraded. + +1. To finalize the upgrade, restart the server. Replace `` with the path to the data directory of the server or servers you're upgrading: + + ```shell + /usr/lib/edb-pge/16/bin/pg_ctl -D restart + ``` + + For example: + + ```shell + /usr/lib/edb-pge/16/bin/pg_ctl -D /var/lib/edb-pge/16/upgrade restart + ``` + +1. Verify the expected database version is running by connecting to psql: + + ```shell + /usr/lib/edb-pge/16/bin/psql + ``` + + Check the server version: + + ```psql + SHOW server_version; + __OUTPUT__ + server_version + -------------------------------------------------------------------- + 16.3 (EDB Postgres Extended Server 16.3.0) (Ubuntu 0:16.3-1.jammy) + (1 row) + ``` diff --git a/product_docs/docs/pge/17/upgrading/minor_upgrade/dnf_upgrade.mdx b/product_docs/docs/pge/17/upgrading/minor_upgrade/dnf_upgrade.mdx new file mode 100644 index 00000000000..c5b91cb3063 --- /dev/null +++ b/product_docs/docs/pge/17/upgrading/minor_upgrade/dnf_upgrade.mdx @@ -0,0 +1,96 @@ +--- +title: "Minor EDB Postgres Extended Server upgrade of RPM packages" +navTitle: "Minor upgrades on RPM environments" +description: "Perform a minor version upgrade of EDB Postgres Extended Server with the dnf package manager" +--- + +If you used `dnf` to install an RPM package of EDB Postgres Extended Server (on RHEL, AlmaLinux, Rocky Linux), use `dnf` to perform a minor version upgrade of the packages. + +## Overview + +1. Check for available updates with `dnf check-update`. + +1. Upgrade the EDB Postgres Extended Server packages with `dnf update`. + +1. Restart the server with `pg_ctl`. + +1. Verify the server version with psql. + +## Worked example + +1. To list the package updates available for your system, open a command line, assume root privileges, and enter the command: + + ```shell + sudo dnf check-update + ``` + + For example, if you want to upgrade to the latest minor version of EDB Postgres Extended Server 16, run: + + ```shell + sudo dnf check-update edb-postgresextended16 + ``` + + !!!Note + You can include wildcard values in the search term. For example, if you're looking for EDB Packages, you can run `sudo dnf check-update edb-*`. For more information about using `dnf` commands and options, enter `dnf --help` at the command line. + +1. Once you've figured the name and version of the package you want to install, use `dnf update` to install the package: + + ```shell + sudo dnf update edb-postgresextended16 + __OUTPUT__ + ================================================================================ + Package Arch Version Repository Size + ================================================================================ + Upgrading: + edb-postgresextended16 x86_64 16.3-2.el9 enterprisedb-enterprise 1.7 M + edb-postgresextended16-contrib x86_64 16.3-2.el9 enterprisedb-enterprise 724 k + edb-postgresextended16-libs x86_64 16.3-2.el9 enterprisedb-enterprise 330 k + edb-postgresextended16-server x86_64 16.3-2.el9 enterprisedb-enterprise 6.8 M + + Transaction Summary + ================================================================================ + Upgrade 4 Packages + + Total download size: 9.5 M + Is this ok [y/N] + ``` + +1. Confirm with `y`. The output displays an overview of all performed processes, where you can see the packages that were upgraded: + + ```shell + y + __OUTPUT__ + edb-postgresextended16-16.3-2.el9.x86_64 + edb-postgresextended16-contrib-16.3-2.el9.x86_64 + edb-postgresextended16-libs-16.3-2.el9.x86_64 + edb-postgresextended16-server-16.3-2.el9.x86_64 + ``` + +1. To finalize the upgrade, restart the server. Replace `` with the path to the data directory of the server or servers you're upgrading: + + ```shell + /usr/edb/pge16/bin/pg_ctl -D restart + ``` + + For example: + + ```shell + /usr/edb/pge16/bin/pg_ctl -D /var/lib/edb-pge/16/upgrade restart + ``` + +1. Verify the expected database version is running by connecting to psql: + + ```shell + /usr/edb/pge16/bin/psql + ``` + + Check the server version: + + ```psql + SHOW server_version; + __OUTPUT__ + server_version + -------------------------------------------- + 16.3 (EDB Postgres Extended Server 16.3.0) + ``` + \ No newline at end of file diff --git a/product_docs/docs/pge/17/upgrading/minor_upgrade/index.mdx b/product_docs/docs/pge/17/upgrading/minor_upgrade/index.mdx new file mode 100644 index 00000000000..613945baedc --- /dev/null +++ b/product_docs/docs/pge/17/upgrading/minor_upgrade/index.mdx @@ -0,0 +1,15 @@ +--- +title: "Minor EDB Postgres Extended Server upgrade" +navTitle: "Minor upgrades" +description: "Minor version upgrade of EDB Postgres Extended Server" +--- + +To perform a minor upgrade of your EDB Postgres Extended Server you only need to update your packages and restart the server. + +To update your packages, ensure you use the correct package manager for your operating system. + +- If you installed an RPM package of EDB Postgres Extended Server (on RHEL, AlmaLinux, Rocky Linux) with `dnf`, see [Minor EDB Postgres Extended Server upgrade of RPM packages](dnf_upgrade). + +- If you installed a Debian package of EDB Postgres Extended Server (on Ubuntu, Debian) with `apt-get`, see [Minor EDB Postgres Extended Server upgrade of Debian packages ](apt_upgrade). + +When you upgrade the packages, the packager manager installs the latest available minor version. For example, if you're running an xy.1 minor version, and the latest available minor version is xy.5, the package manager will install xy.5, skipping xy.2 to xy.4. From cc511ffcdaf2a1178ba65083b23c986998d6c600 Mon Sep 17 00:00:00 2001 From: Josh Heyer Date: Fri, 22 Nov 2024 16:54:13 +0000 Subject: [PATCH 23/24] add redirect for JDBC --- static/_redirects | 1 + 1 file changed, 1 insertion(+) diff --git a/static/_redirects b/static/_redirects index 0e22ae6ded5..540a03bffff 100644 --- a/static/_redirects +++ b/static/_redirects @@ -121,6 +121,7 @@ /docs/jdbc_connector/42.5.1.1/* /docs/jdbc_connector/latest/:splat 301 /docs/jdbc_connector/42.5.1.2/* /docs/jdbc_connector/latest/:splat 301 /docs/jdbc_connector/42.5.4.1/* /docs/jdbc_connector/latest/:splat 301 +/docs/jdbc_connector/42.7.3.1/* /docs/jdbc_connector/latest/:splat 301 # ODBC Connector # collapsed versions From c486e3deae72cb1e154b982ce7d36cf53fd74ce6 Mon Sep 17 00:00:00 2001 From: Josh Heyer Date: Fri, 22 Nov 2024 17:24:55 +0000 Subject: [PATCH 24/24] Update installer data for new releases Generate new installer files --- install_template/config.yaml | 70 +++++++++---------- .../docs/epas/16/installing/index.mdx | 2 +- .../ocl_connector/17/installing/index.mdx | 10 +-- .../installing/linux_arm64/ocl_debian_12.mdx | 2 +- .../installing/linux_ppc64le/ocl_rhel_8.mdx | 2 +- .../installing/linux_ppc64le/ocl_rhel_9.mdx | 2 +- .../installing/linux_ppc64le/ocl_sles_15.mdx | 2 +- .../installing/linux_x86_64/ocl_debian_11.mdx | 2 +- .../installing/linux_x86_64/ocl_debian_12.mdx | 2 +- .../linux_x86_64/ocl_other_linux_8.mdx | 2 +- .../linux_x86_64/ocl_other_linux_9.mdx | 2 +- .../17/installing/linux_x86_64/ocl_rhel_8.mdx | 2 +- .../17/installing/linux_x86_64/ocl_rhel_9.mdx | 2 +- .../installing/linux_x86_64/ocl_sles_15.mdx | 2 +- .../installing/linux_x86_64/ocl_ubuntu_20.mdx | 2 +- .../installing/linux_x86_64/ocl_ubuntu_22.mdx | 2 +- .../installing/linux_arm64/pge_debian_12.mdx | 8 +-- .../installing/linux_x86_64/pge_debian_11.mdx | 8 +-- .../installing/linux_x86_64/pge_debian_12.mdx | 8 +-- .../linux_x86_64/pge_other_linux_8.mdx | 8 +-- .../linux_x86_64/pge_other_linux_9.mdx | 8 +-- .../17/installing/linux_x86_64/pge_rhel_8.mdx | 8 +-- .../17/installing/linux_x86_64/pge_rhel_9.mdx | 8 +-- .../installing/linux_x86_64/pge_ubuntu_20.mdx | 8 +-- .../installing/linux_x86_64/pge_ubuntu_22.mdx | 8 +-- 25 files changed, 90 insertions(+), 90 deletions(-) diff --git a/install_template/config.yaml b/install_template/config.yaml index f1a52870564..4fb2dcc60c2 100644 --- a/install_template/config.yaml +++ b/install_template/config.yaml @@ -29,43 +29,43 @@ products: platforms: - name: RHEL 8 arch: ppc64le - supported versions: [42.7.3.1] + supported versions: [42.7.3.2] - name: AlmaLinux 8 or Rocky Linux 8 arch: x86_64 - supported versions: [42.7.3.1] + supported versions: [42.7.3.2] - name: RHEL 8 or OL 8 arch: x86_64 - supported versions: [42.7.3.1] + supported versions: [42.7.3.2] - name: RHEL 9 arch: ppc64le - supported versions: [42.7.3.1] + supported versions: [42.7.3.2] - name: AlmaLinux 9 or Rocky Linux 9 arch: x86_64 - supported versions: [42.7.3.1] + supported versions: [42.7.3.2] - name: RHEL 9 or OL 9 arch: x86_64 - supported versions: [42.7.3.1] + supported versions: [42.7.3.2] - name: Debian 11 arch: x86_64 - supported versions: [42.7.3.1] + supported versions: [42.7.3.2] - name: Debian 12 arch: x86_64 - supported versions: [42.7.3.1] + supported versions: [42.7.3.2] - name: Debian 12 arch: arm64 - supported versions: [42.7.3.1] + supported versions: [42.7.3.2] - name: Ubuntu 20.04 arch: x86_64 - supported versions: [42.7.3.1] + supported versions: [42.7.3.2] - name: Ubuntu 22.04 arch: x86_64 - supported versions: [42.7.3.1] + supported versions: [42.7.3.2] - name: SLES 15 arch: x86_64 - supported versions: [42.7.3.1] + supported versions: [42.7.3.2] - name: SLES 15 arch: ppc64le - supported versions: [42.7.3.1] + supported versions: [42.7.3.2] - name: Migration Toolkit platforms: - name: RHEL 8 or OL 8 @@ -111,43 +111,43 @@ products: platforms: - name: RHEL 8 arch: ppc64le - supported versions: [14, 15, 16] + supported versions: [14, 15, 16, 17] - name: RHEL 9 arch: ppc64le - supported versions: [14, 15, 16] + supported versions: [14, 15, 16, 17] - name: AlmaLinux 8 or Rocky Linux 8 arch: x86_64 - supported versions: [14, 15, 16] + supported versions: [14, 15, 16, 17] - name: AlmaLinux 9 or Rocky Linux 9 arch: x86_64 - supported versions: [14, 15, 16] + supported versions: [14, 15, 16, 17] - name: RHEL 8 or OL 8 arch: x86_64 - supported versions: [14, 15, 16] + supported versions: [14, 15, 16, 17] - name: RHEL 9 or OL 9 arch: x86_64 - supported versions: [14, 15, 16] + supported versions: [14, 15, 16, 17] - name: Debian 11 arch: x86_64 - supported versions: [14, 15, 16] + supported versions: [14, 15, 16, 17] - name: Debian 12 arch: x86_64 - supported versions: [16] + supported versions: [16, 17] - name: Debian 12 arch: arm64 - supported versions: [16] + supported versions: [16, 17] - name: Ubuntu 20.04 arch: x86_64 - supported versions: [14, 15, 16] + supported versions: [14, 15, 16, 17] - name: Ubuntu 22.04 arch: x86_64 - supported versions: [15, 16] + supported versions: [15, 16, 17] - name: SLES 15 arch: x86_64 - supported versions: [14, 15, 16] + supported versions: [14, 15, 16, 17] - name: SLES 15 arch: ppc64le - supported versions: [14, 15, 16] + supported versions: [14, 15, 16, 17] - name: EDB ODBC Connector platforms: - name: RHEL 8 @@ -357,31 +357,31 @@ products: platforms: - name: AlmaLinux 8 or Rocky Linux 8 arch: x86_64 - supported versions: [15, 16] + supported versions: [15, 16, 17] - name: AlmaLinux 9 or Rocky Linux 9 arch: x86_64 - supported versions: [15, 16] + supported versions: [15, 16, 17] - name: RHEL 8 or OL 8 arch: x86_64 - supported versions: [15, 16] + supported versions: [15, 16, 17] - name: RHEL 9 or OL 9 arch: x86_64 - supported versions: [15, 16] + supported versions: [15, 16, 17] - name: Debian 12 arch: x86_64 - supported versions: [16] + supported versions: [16, 17] - name: Debian 12 arch: arm64 - supported versions: [16] + supported versions: [16, 17] - name: Debian 11 arch: x86_64 - supported versions: [15, 16] + supported versions: [15, 16, 17] - name: Ubuntu 22.04 arch: x86_64 - supported versions: [15, 16] + supported versions: [15, 16, 17] - name: Ubuntu 20.04 arch: x86_64 - supported versions: [15, 16] + supported versions: [15, 16, 17] - name: EDB*Plus platforms: - name: AlmaLinux 8 or Rocky Linux 8 diff --git a/product_docs/docs/epas/16/installing/index.mdx b/product_docs/docs/epas/16/installing/index.mdx index 254c2681d1d..3ed032d9fa7 100644 --- a/product_docs/docs/epas/16/installing/index.mdx +++ b/product_docs/docs/epas/16/installing/index.mdx @@ -63,4 +63,4 @@ Select a link to access the applicable installation instructions: ## Windows -- [Windows Server 2019](windows) +- [Windows Server 2022](windows) diff --git a/product_docs/docs/ocl_connector/17/installing/index.mdx b/product_docs/docs/ocl_connector/17/installing/index.mdx index 4b1f1965ad5..78a2585180f 100644 --- a/product_docs/docs/ocl_connector/17/installing/index.mdx +++ b/product_docs/docs/ocl_connector/17/installing/index.mdx @@ -7,11 +7,11 @@ title: Installing EDB OCL Connector # Leaf template: products/edb-ocl-connector/index.njk redirects: - - /ocl_connector/16/04_open_client_library/01_installing_and_configuring_the_ocl_connector/ - - /ocl_connector/16/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/ - - /ocl_connector/16/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/11_updating_rpm_install/ - - /ocl_connector/16/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/ibm_power_ppc64le/07_ocl_connector14_rhel8_ppcle/ - - /ocl_connector/16/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/06_ocl_connector14_ubuntu18_deb9_x86/ + - /ocl_connector/17/04_open_client_library/01_installing_and_configuring_the_ocl_connector/ + - /ocl_connector/17/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/ + - /ocl_connector/17/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/11_updating_rpm_install/ + - /ocl_connector/17/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/ibm_power_ppc64le/07_ocl_connector14_rhel8_ppcle/ + - /ocl_connector/17/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/06_ocl_connector14_ubuntu18_deb9_x86/ navigation: - linux_ppc64le diff --git a/product_docs/docs/ocl_connector/17/installing/linux_arm64/ocl_debian_12.mdx b/product_docs/docs/ocl_connector/17/installing/linux_arm64/ocl_debian_12.mdx index 32548c1b571..dad1e12ad53 100644 --- a/product_docs/docs/ocl_connector/17/installing/linux_arm64/ocl_debian_12.mdx +++ b/product_docs/docs/ocl_connector/17/installing/linux_arm64/ocl_debian_12.mdx @@ -6,7 +6,7 @@ title: Installing EDB OCL Connector on Debian 12 arm64 # the documentation team will update the templates accordingly. redirects: - - /ocl_connector/16/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/arm64/ocl_deb12_arm + - /ocl_connector/17/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/arm64/ocl_deb12_arm --- ## Prerequisites diff --git a/product_docs/docs/ocl_connector/17/installing/linux_ppc64le/ocl_rhel_8.mdx b/product_docs/docs/ocl_connector/17/installing/linux_ppc64le/ocl_rhel_8.mdx index 2df40e9aeb9..b3e02a2e354 100644 --- a/product_docs/docs/ocl_connector/17/installing/linux_ppc64le/ocl_rhel_8.mdx +++ b/product_docs/docs/ocl_connector/17/installing/linux_ppc64le/ocl_rhel_8.mdx @@ -6,7 +6,7 @@ title: Installing EDB OCL Connector on RHEL 8 ppc64le # the documentation team will update the templates accordingly. redirects: - - /ocl_connector/16/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/ibm_power_ppc64le/ocl_rhel8_ppcle + - /ocl_connector/17/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/ibm_power_ppc64le/ocl_rhel8_ppcle --- ## Prerequisites diff --git a/product_docs/docs/ocl_connector/17/installing/linux_ppc64le/ocl_rhel_9.mdx b/product_docs/docs/ocl_connector/17/installing/linux_ppc64le/ocl_rhel_9.mdx index 41999caf1d8..82880a3afa4 100644 --- a/product_docs/docs/ocl_connector/17/installing/linux_ppc64le/ocl_rhel_9.mdx +++ b/product_docs/docs/ocl_connector/17/installing/linux_ppc64le/ocl_rhel_9.mdx @@ -6,7 +6,7 @@ title: Installing EDB OCL Connector on RHEL 9 ppc64le # the documentation team will update the templates accordingly. redirects: - - /ocl_connector/16/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/ibm_power_ppc64le/ocl_rhel9_ppcle + - /ocl_connector/17/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/ibm_power_ppc64le/ocl_rhel9_ppcle --- ## Prerequisites diff --git a/product_docs/docs/ocl_connector/17/installing/linux_ppc64le/ocl_sles_15.mdx b/product_docs/docs/ocl_connector/17/installing/linux_ppc64le/ocl_sles_15.mdx index 116d2d1ef98..ad6565f4165 100644 --- a/product_docs/docs/ocl_connector/17/installing/linux_ppc64le/ocl_sles_15.mdx +++ b/product_docs/docs/ocl_connector/17/installing/linux_ppc64le/ocl_sles_15.mdx @@ -6,7 +6,7 @@ title: Installing EDB OCL Connector on SLES 15 ppc64le # the documentation team will update the templates accordingly. redirects: - - /ocl_connector/16/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/ibm_power_ppc64le/ocl_sles15_ppcle + - /ocl_connector/17/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/ibm_power_ppc64le/ocl_sles15_ppcle --- ## Prerequisites diff --git a/product_docs/docs/ocl_connector/17/installing/linux_x86_64/ocl_debian_11.mdx b/product_docs/docs/ocl_connector/17/installing/linux_x86_64/ocl_debian_11.mdx index 9f10d8a9bd0..7a23b2ce96e 100644 --- a/product_docs/docs/ocl_connector/17/installing/linux_x86_64/ocl_debian_11.mdx +++ b/product_docs/docs/ocl_connector/17/installing/linux_x86_64/ocl_debian_11.mdx @@ -6,7 +6,7 @@ title: Installing EDB OCL Connector on Debian 11 x86_64 # the documentation team will update the templates accordingly. redirects: - - /ocl_connector/16/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_deb11_x86 + - /ocl_connector/17/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_deb11_x86 --- ## Prerequisites diff --git a/product_docs/docs/ocl_connector/17/installing/linux_x86_64/ocl_debian_12.mdx b/product_docs/docs/ocl_connector/17/installing/linux_x86_64/ocl_debian_12.mdx index 2e0d000d4ca..698c410fc60 100644 --- a/product_docs/docs/ocl_connector/17/installing/linux_x86_64/ocl_debian_12.mdx +++ b/product_docs/docs/ocl_connector/17/installing/linux_x86_64/ocl_debian_12.mdx @@ -6,7 +6,7 @@ title: Installing EDB OCL Connector on Debian 12 x86_64 # the documentation team will update the templates accordingly. redirects: - - /ocl_connector/16/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_deb12_x86 + - /ocl_connector/17/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_deb12_x86 --- ## Prerequisites diff --git a/product_docs/docs/ocl_connector/17/installing/linux_x86_64/ocl_other_linux_8.mdx b/product_docs/docs/ocl_connector/17/installing/linux_x86_64/ocl_other_linux_8.mdx index ecc4a960858..6030c853780 100644 --- a/product_docs/docs/ocl_connector/17/installing/linux_x86_64/ocl_other_linux_8.mdx +++ b/product_docs/docs/ocl_connector/17/installing/linux_x86_64/ocl_other_linux_8.mdx @@ -6,7 +6,7 @@ title: Installing EDB OCL Connector on AlmaLinux 8 or Rocky Linux 8 x86_64 # the documentation team will update the templates accordingly. redirects: - - /ocl_connector/16/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_other_linux8_x86 + - /ocl_connector/17/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_other_linux8_x86 --- ## Prerequisites diff --git a/product_docs/docs/ocl_connector/17/installing/linux_x86_64/ocl_other_linux_9.mdx b/product_docs/docs/ocl_connector/17/installing/linux_x86_64/ocl_other_linux_9.mdx index a303ade238d..55fc257ca65 100644 --- a/product_docs/docs/ocl_connector/17/installing/linux_x86_64/ocl_other_linux_9.mdx +++ b/product_docs/docs/ocl_connector/17/installing/linux_x86_64/ocl_other_linux_9.mdx @@ -6,7 +6,7 @@ title: Installing EDB OCL Connector on AlmaLinux 9 or Rocky Linux 9 x86_64 # the documentation team will update the templates accordingly. redirects: - - /ocl_connector/16/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_other_linux9_x86 + - /ocl_connector/17/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_other_linux9_x86 --- ## Prerequisites diff --git a/product_docs/docs/ocl_connector/17/installing/linux_x86_64/ocl_rhel_8.mdx b/product_docs/docs/ocl_connector/17/installing/linux_x86_64/ocl_rhel_8.mdx index 915c757fc3d..0d1ed3654f5 100644 --- a/product_docs/docs/ocl_connector/17/installing/linux_x86_64/ocl_rhel_8.mdx +++ b/product_docs/docs/ocl_connector/17/installing/linux_x86_64/ocl_rhel_8.mdx @@ -6,7 +6,7 @@ title: Installing EDB OCL Connector on RHEL 8 or OL 8 x86_64 # the documentation team will update the templates accordingly. redirects: - - /ocl_connector/16/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_rhel8_x86 + - /ocl_connector/17/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_rhel8_x86 --- ## Prerequisites diff --git a/product_docs/docs/ocl_connector/17/installing/linux_x86_64/ocl_rhel_9.mdx b/product_docs/docs/ocl_connector/17/installing/linux_x86_64/ocl_rhel_9.mdx index 35742e29644..446f10ef6bb 100644 --- a/product_docs/docs/ocl_connector/17/installing/linux_x86_64/ocl_rhel_9.mdx +++ b/product_docs/docs/ocl_connector/17/installing/linux_x86_64/ocl_rhel_9.mdx @@ -6,7 +6,7 @@ title: Installing EDB OCL Connector on RHEL 9 or OL 9 x86_64 # the documentation team will update the templates accordingly. redirects: - - /ocl_connector/16/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_rhel9_x86 + - /ocl_connector/17/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_rhel9_x86 --- ## Prerequisites diff --git a/product_docs/docs/ocl_connector/17/installing/linux_x86_64/ocl_sles_15.mdx b/product_docs/docs/ocl_connector/17/installing/linux_x86_64/ocl_sles_15.mdx index b5940ed1e85..5f53b6e77a5 100644 --- a/product_docs/docs/ocl_connector/17/installing/linux_x86_64/ocl_sles_15.mdx +++ b/product_docs/docs/ocl_connector/17/installing/linux_x86_64/ocl_sles_15.mdx @@ -6,7 +6,7 @@ title: Installing EDB OCL Connector on SLES 15 x86_64 # the documentation team will update the templates accordingly. redirects: - - /ocl_connector/16/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_sles15_x86 + - /ocl_connector/17/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_sles15_x86 --- ## Prerequisites diff --git a/product_docs/docs/ocl_connector/17/installing/linux_x86_64/ocl_ubuntu_20.mdx b/product_docs/docs/ocl_connector/17/installing/linux_x86_64/ocl_ubuntu_20.mdx index a4df02a1a47..5adec88882d 100644 --- a/product_docs/docs/ocl_connector/17/installing/linux_x86_64/ocl_ubuntu_20.mdx +++ b/product_docs/docs/ocl_connector/17/installing/linux_x86_64/ocl_ubuntu_20.mdx @@ -6,7 +6,7 @@ title: Installing EDB OCL Connector on Ubuntu 20.04 x86_64 # the documentation team will update the templates accordingly. redirects: - - /ocl_connector/16/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_ubuntu20_x86 + - /ocl_connector/17/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_ubuntu20_x86 --- ## Prerequisites diff --git a/product_docs/docs/ocl_connector/17/installing/linux_x86_64/ocl_ubuntu_22.mdx b/product_docs/docs/ocl_connector/17/installing/linux_x86_64/ocl_ubuntu_22.mdx index c1b4f4c0fc2..044572e9b13 100644 --- a/product_docs/docs/ocl_connector/17/installing/linux_x86_64/ocl_ubuntu_22.mdx +++ b/product_docs/docs/ocl_connector/17/installing/linux_x86_64/ocl_ubuntu_22.mdx @@ -6,7 +6,7 @@ title: Installing EDB OCL Connector on Ubuntu 22.04 x86_64 # the documentation team will update the templates accordingly. redirects: - - /ocl_connector/16/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_ubuntu22_x86 + - /ocl_connector/17/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/x86_amd64/ocl_ubuntu22_x86 --- ## Prerequisites diff --git a/product_docs/docs/pge/17/installing/linux_arm64/pge_debian_12.mdx b/product_docs/docs/pge/17/installing/linux_arm64/pge_debian_12.mdx index 5d050ad2748..c3832d6fa55 100644 --- a/product_docs/docs/pge/17/installing/linux_arm64/pge_debian_12.mdx +++ b/product_docs/docs/pge/17/installing/linux_arm64/pge_debian_12.mdx @@ -35,19 +35,19 @@ Before you begin the installation process: ## Install the package ```shell -sudo apt-get -y install edb-postgresextended-16 +sudo apt-get -y install edb-postgresextended-17 ``` ## Initial configuration This section steps you through getting started with your cluster including logging in, ensuring the installation was successful, connecting to your cluster, and creating the user password. -First, you need to initialize and start the database cluster. The `edb-pge-16-setup` script creates a cluster. +First, you need to initialize and start the database cluster. The `edb-pge-17-setup` script creates a cluster. ```shell -sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/lib/edb-pge/16/bin/edb-pge-16-setup initdb +sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/lib/edb-pge/17/bin/edb-pge-17-setup initdb -sudo systemctl start edb-pge-16 +sudo systemctl start edb-pge-17 ``` To work in your cluster, log in as the postgres user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. diff --git a/product_docs/docs/pge/17/installing/linux_x86_64/pge_debian_11.mdx b/product_docs/docs/pge/17/installing/linux_x86_64/pge_debian_11.mdx index 189cbcad2f9..15ead90f66e 100644 --- a/product_docs/docs/pge/17/installing/linux_x86_64/pge_debian_11.mdx +++ b/product_docs/docs/pge/17/installing/linux_x86_64/pge_debian_11.mdx @@ -35,19 +35,19 @@ Before you begin the installation process: ## Install the package ```shell -sudo apt-get -y install edb-postgresextended-16 +sudo apt-get -y install edb-postgresextended-17 ``` ## Initial configuration This section steps you through getting started with your cluster including logging in, ensuring the installation was successful, connecting to your cluster, and creating the user password. -First, you need to initialize and start the database cluster. The `edb-pge-16-setup` script creates a cluster. +First, you need to initialize and start the database cluster. The `edb-pge-17-setup` script creates a cluster. ```shell -sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/lib/edb-pge/16/bin/edb-pge-16-setup initdb +sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/lib/edb-pge/17/bin/edb-pge-17-setup initdb -sudo systemctl start edb-pge-16 +sudo systemctl start edb-pge-17 ``` To work in your cluster, log in as the postgres user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. diff --git a/product_docs/docs/pge/17/installing/linux_x86_64/pge_debian_12.mdx b/product_docs/docs/pge/17/installing/linux_x86_64/pge_debian_12.mdx index d784f6fe72e..9f268a516ff 100644 --- a/product_docs/docs/pge/17/installing/linux_x86_64/pge_debian_12.mdx +++ b/product_docs/docs/pge/17/installing/linux_x86_64/pge_debian_12.mdx @@ -35,19 +35,19 @@ Before you begin the installation process: ## Install the package ```shell -sudo apt-get -y install edb-postgresextended-16 +sudo apt-get -y install edb-postgresextended-17 ``` ## Initial configuration This section steps you through getting started with your cluster including logging in, ensuring the installation was successful, connecting to your cluster, and creating the user password. -First, you need to initialize and start the database cluster. The `edb-pge-16-setup` script creates a cluster. +First, you need to initialize and start the database cluster. The `edb-pge-17-setup` script creates a cluster. ```shell -sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/lib/edb-pge/16/bin/edb-pge-16-setup initdb +sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/lib/edb-pge/17/bin/edb-pge-17-setup initdb -sudo systemctl start edb-pge-16 +sudo systemctl start edb-pge-17 ``` To work in your cluster, log in as the postgres user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. diff --git a/product_docs/docs/pge/17/installing/linux_x86_64/pge_other_linux_8.mdx b/product_docs/docs/pge/17/installing/linux_x86_64/pge_other_linux_8.mdx index d906afce5f7..7747051e4fd 100644 --- a/product_docs/docs/pge/17/installing/linux_x86_64/pge_other_linux_8.mdx +++ b/product_docs/docs/pge/17/installing/linux_x86_64/pge_other_linux_8.mdx @@ -46,19 +46,19 @@ Before you begin the installation process: ## Install the package ```shell -sudo dnf -y install edb-postgresextended16-server edb-postgresextended16-contrib +sudo dnf -y install edb-postgresextended17-server edb-postgresextended17-contrib ``` ## Initial configuration Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. -First, you need to initialize and start the database cluster. The `edb-pge-16-setup` script creates a cluster. +First, you need to initialize and start the database cluster. The `edb-pge-17-setup` script creates a cluster. ```shell -sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/pge16/bin/edb-pge-16-setup initdb +sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/pge17/bin/edb-pge-17-setup initdb -sudo systemctl start edb-pge-16 +sudo systemctl start edb-pge-17 ``` To work in your cluster, log in as the postgres user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. diff --git a/product_docs/docs/pge/17/installing/linux_x86_64/pge_other_linux_9.mdx b/product_docs/docs/pge/17/installing/linux_x86_64/pge_other_linux_9.mdx index 5165da02a31..fb16eea337d 100644 --- a/product_docs/docs/pge/17/installing/linux_x86_64/pge_other_linux_9.mdx +++ b/product_docs/docs/pge/17/installing/linux_x86_64/pge_other_linux_9.mdx @@ -46,19 +46,19 @@ Before you begin the installation process: ## Install the package ```shell -sudo dnf -y install edb-postgresextended16-server edb-postgresextended16-contrib +sudo dnf -y install edb-postgresextended17-server edb-postgresextended17-contrib ``` ## Initial configuration Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. -First, you need to initialize and start the database cluster. The `edb-pge-16-setup` script creates a cluster. +First, you need to initialize and start the database cluster. The `edb-pge-17-setup` script creates a cluster. ```shell -sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/pge16/bin/edb-pge-16-setup initdb +sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/pge17/bin/edb-pge-17-setup initdb -sudo systemctl start edb-pge-16 +sudo systemctl start edb-pge-17 ``` To work in your cluster, log in as the postgres user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. diff --git a/product_docs/docs/pge/17/installing/linux_x86_64/pge_rhel_8.mdx b/product_docs/docs/pge/17/installing/linux_x86_64/pge_rhel_8.mdx index 546c95cb66b..8f82e772f13 100644 --- a/product_docs/docs/pge/17/installing/linux_x86_64/pge_rhel_8.mdx +++ b/product_docs/docs/pge/17/installing/linux_x86_64/pge_rhel_8.mdx @@ -40,19 +40,19 @@ Before you begin the installation process: ## Install the package ```shell -sudo dnf -y install edb-postgresextended16-server edb-postgresextended16-contrib +sudo dnf -y install edb-postgresextended17-server edb-postgresextended17-contrib ``` ## Initial configuration Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. -First, you need to initialize and start the database cluster. The `edb-pge-16-setup` script creates a cluster. +First, you need to initialize and start the database cluster. The `edb-pge-17-setup` script creates a cluster. ```shell -sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/pge16/bin/edb-pge-16-setup initdb +sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/pge17/bin/edb-pge-17-setup initdb -sudo systemctl start edb-pge-16 +sudo systemctl start edb-pge-17 ``` To work in your cluster, log in as the postgres user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. diff --git a/product_docs/docs/pge/17/installing/linux_x86_64/pge_rhel_9.mdx b/product_docs/docs/pge/17/installing/linux_x86_64/pge_rhel_9.mdx index c324e321d69..d7ca1bdc9b8 100644 --- a/product_docs/docs/pge/17/installing/linux_x86_64/pge_rhel_9.mdx +++ b/product_docs/docs/pge/17/installing/linux_x86_64/pge_rhel_9.mdx @@ -40,19 +40,19 @@ Before you begin the installation process: ## Install the package ```shell -sudo dnf -y install edb-postgresextended16-server edb-postgresextended16-contrib +sudo dnf -y install edb-postgresextended17-server edb-postgresextended17-contrib ``` ## Initial configuration Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. -First, you need to initialize and start the database cluster. The `edb-pge-16-setup` script creates a cluster. +First, you need to initialize and start the database cluster. The `edb-pge-17-setup` script creates a cluster. ```shell -sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/pge16/bin/edb-pge-16-setup initdb +sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/pge17/bin/edb-pge-17-setup initdb -sudo systemctl start edb-pge-16 +sudo systemctl start edb-pge-17 ``` To work in your cluster, log in as the postgres user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. diff --git a/product_docs/docs/pge/17/installing/linux_x86_64/pge_ubuntu_20.mdx b/product_docs/docs/pge/17/installing/linux_x86_64/pge_ubuntu_20.mdx index 7f310a7a15a..e396a6b58b7 100644 --- a/product_docs/docs/pge/17/installing/linux_x86_64/pge_ubuntu_20.mdx +++ b/product_docs/docs/pge/17/installing/linux_x86_64/pge_ubuntu_20.mdx @@ -35,19 +35,19 @@ Before you begin the installation process: ## Install the package ```shell -sudo apt-get -y install edb-postgresextended-16 +sudo apt-get -y install edb-postgresextended-17 ``` ## Initial configuration This section steps you through getting started with your cluster including logging in, ensuring the installation was successful, connecting to your cluster, and creating the user password. -First, you need to initialize and start the database cluster. The `edb-pge-16-setup` script creates a cluster. +First, you need to initialize and start the database cluster. The `edb-pge-17-setup` script creates a cluster. ```shell -sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/lib/edb-pge/16/bin/edb-pge-16-setup initdb +sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/lib/edb-pge/17/bin/edb-pge-17-setup initdb -sudo systemctl start edb-pge-16 +sudo systemctl start edb-pge-17 ``` To work in your cluster, log in as the postgres user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. diff --git a/product_docs/docs/pge/17/installing/linux_x86_64/pge_ubuntu_22.mdx b/product_docs/docs/pge/17/installing/linux_x86_64/pge_ubuntu_22.mdx index 61a6656848e..4f68a0b917a 100644 --- a/product_docs/docs/pge/17/installing/linux_x86_64/pge_ubuntu_22.mdx +++ b/product_docs/docs/pge/17/installing/linux_x86_64/pge_ubuntu_22.mdx @@ -35,19 +35,19 @@ Before you begin the installation process: ## Install the package ```shell -sudo apt-get -y install edb-postgresextended-16 +sudo apt-get -y install edb-postgresextended-17 ``` ## Initial configuration This section steps you through getting started with your cluster including logging in, ensuring the installation was successful, connecting to your cluster, and creating the user password. -First, you need to initialize and start the database cluster. The `edb-pge-16-setup` script creates a cluster. +First, you need to initialize and start the database cluster. The `edb-pge-17-setup` script creates a cluster. ```shell -sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/lib/edb-pge/16/bin/edb-pge-16-setup initdb +sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/lib/edb-pge/17/bin/edb-pge-17-setup initdb -sudo systemctl start edb-pge-16 +sudo systemctl start edb-pge-17 ``` To work in your cluster, log in as the postgres user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string.