Choose this one: LINUX.X64_193000_client.zip (64-bit) (1,134,912,540 bytes) , not the one named “LINUX.X64_193000_client_home.zip” because it is a preinstalled home that does not contain the CMAN tools.
Access the OCI Console and create a new Compute instance. The default configuration is OK, just make sure that it is Oracle Linux 7
Do not forget to add your SSH Public Key to access the VM via SSH!
Access the VM using
Oracle PL/SQL
1
ssh opc@{public_ip}
Copy the Oracle Client zip in /tmp using your favorite scp program.
Install CMAN
Follow these steps to install CMAN:
Oracle PL/SQL
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
# become root
sudo su - root
# install some prereqs (packages, oracle user, kernel params, etc.):
This will create a CMAN configuration named cman-test. Beware that it is very basic and insecure. Please read the CMAN documentation if you want something more secure or sophisticated.
The advantage of having the TNS_ADMIN outside the Oracle Home is that if you need to patch CMAN, you can do it out-of-place without the need to copy the configuration files somewhere else.
The advantage of using IFILE inside cman.ora, is that you can manage easily different CMAN configurations in the same host without editing directly cman.ora, with the risk of messing it up.
Preparing the start/stop script
Create a file /u01/app/oracle/scripts/cman_service.sh with this content:
Ludovico is a member of the Oracle Database High Availability (HA), Scalability & Maximum Availability Architecture (MAA) Product Management team in Oracle.
He focuses on Oracle Data Guard, Flashback technologies, and Cloud MAA.
Thanks for posting this. Your cman_service.sh script is a bit rough around the edges, mostly because of references to functions / variables that you set in your profile that you deliver via git only after creating the cman_service.sh script: eerror and $OH are not present yet. Nevertheless this was very helpful for me.
Good article and nice to see a write up on CMAN. We have been using it for past one year (18c) and this technology perfectly fits for our architecture. Providing access to Cloud Native containers based read services accessing the on-prem based monolith Oracle DB’s.
This website uses cookies to improve your experience. We'll assume you're ok with this, but you can opt-out if you wish.Accept
Privacy & Cookies Policy
Privacy Overview
This website uses cookies to improve your experience while you navigate through the website. Out of these, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the ...
Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.
Any cookies that may not be particularly necessary for the website to function and is used specifically to collect user personal data via analytics, ads, other embedded contents are termed as non-necessary cookies. It is mandatory to procure user consent prior to running these cookies on your website.
Hi Ludovico,
If I have two CMAN installed on two nodes as HA solution, do you know what should I set for remote_listener parameter on the database instance please?
Regards,
AW
Hi Anders,
‘cman1:1521′,’cman2:1521’
If you have RAC, don’t forget to add your scan address.
—
Ludovico
Hi Ludovico —
Great job on this. Very helpful. We also had to fix the $OH missing in the script as follows:
export OH = $L_OH
Regards,
Carl
Hi Ludo,
Thanks for posting this. Your cman_service.sh script is a bit rough around the edges, mostly because of references to functions / variables that you set in your profile that you deliver via git only after creating the cman_service.sh script: eerror and $OH are not present yet. Nevertheless this was very helpful for me.
Thanks!
Jacco.
Good article and nice to see a write up on CMAN. We have been using it for past one year (18c) and this technology perfectly fits for our architecture. Providing access to Cloud Native containers based read services accessing the on-prem based monolith Oracle DB’s.
Thanks Ludo, honestly I can’t wait the 19c upgrade series
.
Regards.
GG