-
Notifications
You must be signed in to change notification settings - Fork 248
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Added latest product version to few products and its install topics
- Loading branch information
1 parent
4cb40fa
commit 2b413d7
Showing
10 changed files
with
386 additions
and
9 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
157 changes: 157 additions & 0 deletions
157
product_docs/docs/epas/17/installing/linux_arm64/epas_rhel_9.mdx
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,157 @@ | ||
--- | ||
navTitle: RHEL 9 or OL 9 | ||
title: Installing EDB Postgres Advanced Server on RHEL 9 or OL 9 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: | ||
- /epas/17/epas_inst_linux/installing_epas_using_edb_repository/arm64/epas_rhel9_arm | ||
- /epas/17/epas_inst_linux/installing_epas_using_edb_repository/arm/epas_rhel9_arm | ||
--- | ||
|
||
## 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 | ||
``` | ||
|
||
- If you are also installing PostGIS, enable additional repositories to resolve dependencies: | ||
|
||
```shell | ||
ARCH=$( /bin/arch ) subscription-manager repos --enable "codeready-builder-for-rhel-9-${ARCH}-rpms" | ||
``` | ||
|
||
!!!note | ||
|
||
If you are using a public cloud RHEL image, `subscription manager` may not be enabled and enabling it may incur unnecessary charges. Equivalent packages may be available under a different name such as `codeready-builder-for-rhel-9-rhui-rpms`. Consult the documentation for the RHEL image you are using to determine how to install `codeready-builder`. | ||
|
||
!!! | ||
|
||
## Install the package | ||
|
||
```shell | ||
sudo dnf -y install edb-as<xx>-server | ||
``` | ||
|
||
Where `<xx>` is the version of the EDB Postgres Advanced Server you're installing. For example, if you're installing version 17, the package name is `edb-as17-server`. | ||
|
||
To install an individual component: | ||
|
||
```shell | ||
sudo dnf -y install <package_name> | ||
``` | ||
|
||
Where `package_name` can be any of the available packages from the [available package list](/epas/17/installing/linux_install_details/rpm_packages/). | ||
|
||
Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash`, and the user's home directory is `/var/lib/edb/as17`. | ||
|
||
## 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-as-17-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/specifying_cluster_options/#initializing-the-cluster-in-postgres-mode). | ||
|
||
```shell | ||
sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as17/bin/edb-as-17-setup initdb | ||
|
||
sudo systemctl start edb-as-17 | ||
``` | ||
|
||
To work in your cluster, log in as the enterprisedb 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 su - enterprisedb | ||
|
||
psql edb | ||
``` | ||
|
||
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, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). | ||
|
||
```sql | ||
ALTER ROLE enterprisedb IDENTIFIED BY 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__ | ||
psql (17.0.0, server 17.0.0) | ||
You are now connected to database "hr" as user "enterprisedb". | ||
``` | ||
|
||
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) | ||
``` |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
52 changes: 52 additions & 0 deletions
52
product_docs/docs/ocl_connector/17/installing/linux_arm64/ocl_rhel_9.mdx
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,52 @@ | ||
--- | ||
navTitle: RHEL 9 or OL 9 | ||
title: Installing EDB OCL Connector on RHEL 9 or OL 9 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/17/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/arm64/ocl_rhel9_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: | ||
|
||
`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 | ||
``` |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.