You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: Archive/ContainerCloud/images/rolling-router-sticky-sessions/README.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ This image is a specialized load balancer for doing [rolling, or canary deployme
6
6
7
7
This is an extended version of <ahref="https://github.com/oracle/docker-images/tree/master/ContainerCloud/images/rolling-router">the original image</a> that supports session affinity. The sticky sessions module used is <ahref="https://bitbucket.org/nginx-goodies/nginx-sticky-module-ng">nginx-sticky-module-ng</a>.
8
8
9
-
Besides the the Nginx module above this version adds a new key value <ahref="https://github.com/mikarinneoracle/docker-images/blob/master/ContainerCloud/images/rolling-router/deploy_keyvalues.sh#L23">stickyness</a> and based on the value, either 0 or 1:
9
+
Besides the Nginx module above this version adds a new key value <ahref="https://github.com/mikarinneoracle/docker-images/blob/master/ContainerCloud/images/rolling-router/deploy_keyvalues.sh#L23">stickyness</a> and based on the value, either 0 or 1:
10
10
11
11
<ol>
12
12
<li>First call from a client is load balanced based on <ahref="https://github.com/mikarinneoracle/docker-images/blob/master/ContainerCloud/images/rolling-router/deploy_keyvalues.sh#L19">blendpercent</a> e.g. 10% (90/10 split)</li>
If you want to use Jumbo Frames MTU Network Configuration as similar as with Oracle RAC containers networks, then refer [Jumbo Frames MTU Network Configuration](../OracleRealApplicationClusters/README.md#jumbo-frames-mtu-network-configuration) section
87
87
88
88
## How to deploy Oracle Connection Manager Container
89
-
The Oracle Connection manager container (CMAN) can be used with either an Oracle Real Application Clusters (Oracle RAC) database or with an Oracle Database Single instance database. However, you must ensure that the the SCAN Name or the Single host instance database Hostname is resolvable from the connection manager container.
89
+
The Oracle Connection manager container (CMAN) can be used with either an Oracle Real Application Clusters (Oracle RAC) database or with an Oracle Database Single instance database. However, you must ensure that the SCAN Name or the Single host instance database Hostname is resolvable from the connection manager container.
90
90
Oracle highly recommends that you use a DNS Server so that name resolution can happen successfully.
Copy file name to clipboardExpand all lines: OracleDatabase/RAC/OracleRealApplicationClusters/dockerfiles/12.2.0.1/sshUserSetup.sh
+1-1
Original file line number
Diff line number
Diff line change
@@ -16,7 +16,7 @@
16
16
# confirmations.
17
17
#Please note that the script would remove write permissions on the remote hosts
18
18
#for the user home directory and ~/.ssh directory for "group" and "others". This
19
-
# is an SSH requirement. The user would be explicitly informed about this by teh script and prompted to continue. In case the user presses no, the script would exit. In case the user does not want to be prompted, they can use the -confirm option.
19
+
# is an SSH requirement. The user would be explicitly informed about this by the script and prompted to continue. In case the user presses no, the script would exit. In case the user does not want to be prompted, they can use the -confirm option.
20
20
# As a part of the setup, the script would use SSH to create files within ~/.ssh
21
21
# directory of the remote node and to setup the requisite permissions. The
22
22
#script also uses SCP to copy the local host public key to the remote hosts so
Copy file name to clipboardExpand all lines: OracleDatabase/RAC/OracleRealApplicationClusters/dockerfiles/18.3.0/sshUserSetup.sh
+1-1
Original file line number
Diff line number
Diff line change
@@ -16,7 +16,7 @@
16
16
# confirmations.
17
17
#Please note that the script would remove write permissions on the remote hosts
18
18
#for the user home directory and ~/.ssh directory for "group" and "others". This
19
-
# is an SSH requirement. The user would be explicitly informed about this by teh script and prompted to continue. In case the user presses no, the script would exit. In case the user does not want to be prompted, they can use the -confirm option.
19
+
# is an SSH requirement. The user would be explicitly informed about this by the script and prompted to continue. In case the user presses no, the script would exit. In case the user does not want to be prompted, they can use the -confirm option.
20
20
# As a part of the setup, the script would use SSH to create files within ~/.ssh
21
21
# directory of the remote node and to setup the requisite permissions. The
22
22
#script also uses SCP to copy the local host public key to the remote hosts so
Copy file name to clipboardExpand all lines: OracleDatabase/RAC/OracleRealApplicationClusters/dockerfiles/19.3.0/sshUserSetup.sh
+1-1
Original file line number
Diff line number
Diff line change
@@ -16,7 +16,7 @@
16
16
# confirmations.
17
17
#Please note that the script would remove write permissions on the remote hosts
18
18
#for the user home directory and ~/.ssh directory for "group" and "others". This
19
-
# is an SSH requirement. The user would be explicitly informed about this by teh script and prompted to continue. In case the user presses no, the script would exit. In case the user does not want to be prompted, he can use -confirm option.
19
+
# is an SSH requirement. The user would be explicitly informed about this by the script and prompted to continue. In case the user presses no, the script would exit. In case the user does not want to be prompted, he can use -confirm option.
20
20
# As a part of the setup, the script would use SSH to create files within ~/.ssh
21
21
# directory of the remote node and to setup the requisite permissions. The
22
22
#script also uses SCP to copy the local host public key to the remote hosts so
Now create the Oracle RAC containers using the image. For the details of environment variables, refer to [Environment Variables Explained](#section-9-environment-variables-for-oracle-rac-on-containers)
201
-
**Note**: Before creating the containers, you need to make sure you have edited teh file `/scratch/common_scripts/podman/rac/envfile_racnodep1` and set the variables based on your environment.
201
+
**Note**: Before creating the containers, you need to make sure you have edited the file `/scratch/common_scripts/podman/rac/envfile_racnodep1` and set the variables based on your environment.
202
202
203
203
You can use the following example to create the first Oracle RAC container:
204
204
```bash
@@ -236,7 +236,7 @@ podman create -t -i \
236
236
localhost/oracle/database-rac:21c-slim
237
237
```
238
238
239
-
**Note**: Before creating the containers, you need to make sure you have edited teh file `/scratch/common_scripts/podman/rac/envfile_racnodep2` and set the variables based on your enviornment.
239
+
**Note**: Before creating the containers, you need to make sure you have edited the file `/scratch/common_scripts/podman/rac/envfile_racnodep2` and set the variables based on your enviornment.
240
240
241
241
Create another Oracle RAC Container -
242
242
@@ -340,7 +340,7 @@ podman create -t -i \
340
340
localhost/oracle/database-rac:21c-slim
341
341
```
342
342
343
-
**Note**: Before creating the containers, you need to make sure you have edited teh file `/scratch/common_scripts/podman/rac/envfile_racnodep2` and set the variables based on your enviornment.
343
+
**Note**: Before creating the containers, you need to make sure you have edited the file `/scratch/common_scripts/podman/rac/envfile_racnodep2` and set the variables based on your enviornment.
344
344
345
345
To create another container, use the following command:
346
346
@@ -406,7 +406,7 @@ You can skip this step if you are planning not to use **User Defined Response Fi
406
406
407
407
Follow the below instructions to setup Oracle RAC on Podman using Slim Image for using user-defined response files.
408
408
409
-
**Note**: Before creating the containers, you need to make sure you have edited teh file `/scratch/common_scripts/podman/rac/envfile_racnodep1` and set the variables based on your enviornment.
409
+
**Note**: Before creating the containers, you need to make sure you have edited the file `/scratch/common_scripts/podman/rac/envfile_racnodep1` and set the variables based on your enviornment.
410
410
411
411
You can use the following example to create the first Oracle RAC container:
412
412
```bash
@@ -446,7 +446,7 @@ podman create -t -i \
446
446
localhost/oracle/database-rac:21c-slim
447
447
```
448
448
449
-
**Note**: Before creating the containers, you need to make sure you have edited teh file `/scratch/common_scripts/podman/rac/envfile_racnodep1` and set the variables based on your enviornment.
449
+
**Note**: Before creating the containers, you need to make sure you have edited the file `/scratch/common_scripts/podman/rac/envfile_racnodep1` and set the variables based on your enviornment.
450
450
451
451
To create another container, use the following command:
452
452
@@ -565,7 +565,7 @@ Refer to [README](./docs/CONNECTING.md) for instructions on how to connect to Or
565
565
Below is the example of adding 1 more node to the existing Oracle RAC 2 node cluster using Slim image and without user-defined files -
566
566
- Create envfile [envfile_racnodep3](withoutresponsefiles/blockdevices/envfile_racnodep3) for additional node and keep it here `/scratch/common_scripts/podman/rac/envfile_racnodep3`
567
567
568
-
**Note**: Before creating the containers, you need to make sure you have edited teh file `/scratch/common_scripts/podman/rac/envfile_racnodep3` and set the variables based on your enviornment.
568
+
**Note**: Before creating the containers, you need to make sure you have edited the file `/scratch/common_scripts/podman/rac/envfile_racnodep3` and set the variables based on your enviornment.
569
569
570
570
- Prepare Folder for additional node-
571
571
```bash
@@ -626,7 +626,7 @@ Below is the example of adding 1 more node to the existing Oracle RAC 2 node clu
626
626
627
627
### Section 8.1: Sample of Addition of Nodes to Oracle RAC Containers based on Oracle RAC Image Without Response File
628
628
Below is an example of adding one more node to the existing Oracle RAC 2 node cluster using the Oracle RAC image and without user-defined files.
629
-
**Note**: Before creating the containers, you need to make sure you have edited teh file `/scratch/common_scripts/podman/rac/envfile_racnodep3` and set the variables based on your enviornment.
629
+
**Note**: Before creating the containers, you need to make sure you have edited the file `/scratch/common_scripts/podman/rac/envfile_racnodep3` and set the variables based on your enviornment.
Copy file name to clipboardExpand all lines: OracleDatabase/SingleInstance/FAQ.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,7 @@ For such versions, if you require the runtime functionality documented in this r
10
10
## How do I change the timezone of my container
11
11
12
12
As of Docker 17.06-ce, Docker does not yet provide a way to pass down the `TZ` Unix environment variable from the host to the container. Because of that all containers run in the UTC timezone. If you would like to have your database run in a different timezone you can pass on the `TZ` environment variable within the `docker run` command via the `-e` option.
13
-
An example would be: `docker run ... -e TZ="Europe/Vienna" oracle/database:12.2.0.1-ee`. Another option would be to specify two read-only volume mounts: `docker run ... -v /etc/timezone:/etc/timezone:ro -v /etc/localtime:/etc/localtime:ro oracle/database:12.2.0.1-ee`. This will synchronize the timezone of the the container with that of the Docker host.
13
+
An example would be: `docker run ... -e TZ="Europe/Vienna" oracle/database:12.2.0.1-ee`. Another option would be to specify two read-only volume mounts: `docker run ... -v /etc/timezone:/etc/timezone:ro -v /etc/localtime:/etc/localtime:ro oracle/database:12.2.0.1-ee`. This will synchronize the timezone of the container with that of the Docker host.
14
14
15
15
## Can I run Oracle Database containers on Apple M1 (Arm) devices?
0 commit comments