1. Deploy a hybrid DR topology for an on-premises Oracle Exadata
  2. Validate Connectivity Between Exadata Systems

Validate Connectivity Between Exadata Systems

Ensure that you can connect to both the primary Oracle Exadata Database Machine on-premises and the standby Oracle Database Exadata Cloud Service in the cloud using a key.

Connect to the Primary Oracle Exadata Database Machine

Connect to the primary, on-premises Oracle Exadata Database Machine.

Generate a key to use to connect your on-premises and cloud instances. In this example, the key is cluster.key.

  1. Connect to Node 1 using the key.
    bash-4.4$ ssh -i cluster.key oracle@10.136.74.2
  2. Confirm that Oracle is running in Node 1 of the primary Oracle Exadata Database Machine.
    [oracle@exa11db01 ~]$ ps -ef | grep pmon
    The output will look similar to the following
    oracle    71561      1  0 Jan07 ?        00:01:12 asm_pmon_+ASM1
oracle    80014      1  0 Jan07 ?        00:02:18 ora_pmon_db11
oracle   169965 162482  0 17:00 pts/0    00:00:00 grep --color=auto pmon
  3. Edit the oratab file in the /etc directory on Node 1 and add this line so that you don't need to set the env variables every time.
    db11:/u01/app/oracle/product/19.0.0.0/dbhome_1:N
+ASM1:/u01/app/19.0.0.0/grid:N
  4. Edit the oratab file in the /etc directory on Node 2 and add this line so that you don't need to set the env variables every time.
    db12:/u01/app/oracle/product/19.0.0.0/dbhome_1:N
+ASM1:/u01/app/19.0.0.0/grid:N
  5. Source the Env variable on Node 1. 
    [oracle@exa11db01 ~]$ . oraenv
ORACLE_SID = [oracle] ? db11
    The Oracle base has been set to /u01/app/oracle
  6. Log in to sqlplus as a sysdba on Node 1.
    [oracle@exa11db01 bin]$ ./sqlplus / as sysdba
  7. Connect to Node 2 from the primary node (Node 1).
    [oracle@exa11db01 ~]$ ssh exa11db02
  8. Source the Env variable. 
    [oracle@exa11db01 ~]$ . oraenv
ORACLE_SID = [oracle] ? db12
    The Oracle base has been set to /u01/app/oracle

Connect to the Standby Oracle Database Exadata Cloud Service

Connect to the standby Oracle Database Exadata Cloud Service in the cloud.

Generate a key to use to connect your on-premises and cloud instances. In this example, the key is cluster.key.

  1. Connect to Oracle Database Exadata Cloud Service Node 1 using the key.
    bash-4.4$ ssh -i cluster.key oracle@10.255.195.131
  2. Confirm that Oracle is running in Node 1 of the primary Oracle Exadata Database Machine.
    [oracle@exa11db01 ~]$ ps -ef | grep pmon
    The output will look similar to the following
    oracle    71561      1  0 Jan07 ?        00:01:12 asm_pmon_+ASM1
oracle    80014      1  0 Jan07 ?        00:02:18 ora_pmon_db11
oracle   169965 162482  0 17:00 pts/0    00:00:00 grep --color=auto pmon
  3. Edit the oratab file in the /etc directory on Node 1 and add the following line so that you don't need to set the env variables every time.
    ORACLE utilities uses the oratab file. It is created by root.sh and updated by either Database Configuration Assistant while creating a database or ASM Configuration Assistant while creating an ASM instance.
    Entries are of the form: $ORACLE_SID:$ORACLE_HOME:<N|Y>:
    A colon, ':', is used as the field terminator. A new line terminates the entry. The first and second fields are the system identifier and home directory of the database respectively. The third field indicates to the dbstart utility that the database should be brought up at system boot time (Y), or not (N). Multiple entries with the same $ORACLE_SID are not allowed. 
    +ASM1:/u01/app/19.0.0.0/grid:N
jcdbt1_phx3gd:/u02/app/oracle/product/19.0.0.0/dbhome_2:Y
jcmdb_phx3f8:/u02/app/oracle/product/19.0.0.0/dbhome_4:Y
DB1_phx3g7:/u02/app/oracle/product/19.0.0.0/dbhome_5:
  4. Log into the DB node, then list the directories.
    $ sudo su – oracle
$ ls -lrt
    The output might look similar to the following:
    -rw-r--r-- 1 oracle oinstall 694 Jan 16 11:10 gCxNOObq.env
-rw-rw---- 1 oracle oinstall 683 Jan 17 09:55 jcdbt1.env
-rw-rw---- 1 oracle oinstall 680 Jan 19 07:56 jcmdb.env
-rw-rw---- 1 oracle oinstall 674 Jan 20 10:16 DB1.env
  5. Source the DB1 environment.
    $ source DB1.env
  6. Verify that the database is encrypted
    An Oracle Database Exadata Cloud Service database is encrypted by default. 
    SQL> select TABLESPACE_NAME, ENCRYPTED from dba_tablespaces;

    The output might look similar to the following:

    TABLESPACE_NAME      ENC
------------------------------                     ---
SYSTEM                                               NO
SYSAUX                                               NO
UNDOTBS1                                             NO
TEMP                                                 NO
USERS                                                YES
UNDOTBS2                                             NO
  7. Check the current setting of the encrypt parameter.
    SQL> show parameter encrypt;

    The output might look similar to the following:

    NAME      TYPE     VALUE
------------------------------------ ----------- ------------------------------
encrypt_new_tablespaces               string      ALWAYS
  8. Log into Node 2.
    $ ssh exacs82-vm3sv1

Create Directories on the Source Database System

If the on-premises Oracle Exadata system does not have a wallet, then create the wallet directory on each node.

  1. Log into Node 1 of the Oracle Exadata system and determine if it has a wallet. Navigate to the /u01/app/oracle/admin/db1/ directory, then perform the command ls -lrt to display the directories.
  2. Log into Node 2 of the Oracle Exadata system. Navigate to the /u01/app/oracle/admin/db1/ directory, then perform the command ls -lrt to display the directories. 
    [oracle@exa11db02 ~]$ cd /u01/app/oracle/admin/
[oracle@exa11db02 admin]$ ls -lrt
[oracle@exa11db02 admin]$ cd db1/
[oracle@exa11db02 db1]$ ls -lrt
    The output will look similar to the following:
    total 12
drwxr-x--- 2 oracle oinstall 4096 Jan 7 18:02 dpdump
drwxr-x--- 2 oracle oinstall 4096 Jan 7 18:03 hdump
drwxr-x--- 2 oracle oinstall 4096 Jan 7 18:03 pfile
  3. Display a list of the admin directory and the db1 directory.
    /home/oracle
[oracle@exa11db01 ~]$ cd /u01/app/oracle/admin/db1/
[oracle@exa11db01 db1]$ ls -lrt
  4. Create a wallet directory on Node 1 (db1). 
    [oracle@exa11db02 db1]$ mkdir wallet
    The output will look similar to the following:
    total 20
drwxr-x--- 2 oracle oinstall 4096 Jan 7 18:02 dpdump
drwxr-x--- 2 oracle oinstall 4096 Jan 7 18:03 hdump
drwxr-x--- 2 oracle dba 4096 Jan 7 18:03 xdb_wallet
drwxr-x--- 2 oracle oinstall 4096 Jan 7 18:14 pfile
drwxr-xr-x 2 oracle oinstall 4096 Jan 19 22:59 wallet
  5. Log into Node 2 of the Oracle Exadata system.
  6. Display a list of the admin directory and the db1 directory.
    [oracle@exa11db02 ~]$ cd /u01/app/oracle/admin/
[oracle@exa11db02 admin]$ ls -lrt
[oracle@exa11db02 admin]$ cd db1/
[oracle@exa11db02 db1]$ ls -lrt
    total 12
drwxr-x--- 2 oracle oinstall 4096 Jan 7 18:02 dpdump
drwxr-x--- 2 oracle oinstall 4096 Jan 7 18:03 hdump
drwxr-x--- 2 oracle oinstall 4096 Jan 7 18:03 pfile
  7. Create a wallet directory.
    [oracle@exa11db02 db1]$ mkdir wallet

Create Directories on the Backup Database System

Create a wallet directory on each node of the backup Oracle Database Exadata Cloud Service.

  1. Connect to cloud instance using the ssh key that you created earlier. In this example, the key is cluster.key.
    ssh -i cluster.key opc@10.255.195.132
  2. Log into Node 1 of the Oracle Database Exadata Cloud Service as the oracle user with root privileges, then display the directories.
    $ sudo su - oracle
$ ls -lrt
    The output might look similar to the following:
    -rw-r--r-- 1 oracle oinstall 694 Jan 16 11:10 gCxNOObq.env
-rw-rw---- 1 oracle oinstall 683 Jan 17 09:55 jcdbt1.env
-rw-rw---- 1 oracle oinstall 680 Jan 19 07:56 jcmdb.env
-rw-rw---- 1 oracle oinstall 674 Jan 20 10:16 DB1.env
  3. Source Node 1.
    In this example, the node is DB1.env. 
    $ source DB1.env
  4. Navigate to the /u02/app/oracle/admin/DB1/ directory, then display the directories. 
    $ cd /u02/app/oracle/admin/DB1/
$ ls -lrt
    The output might look similar to the following:
    drwxr-xr-x 2 oracle oinstall 4096 Jan 20 10:16 adump
drwxr-xr-x 2 oracle oinstall 4096 Jan 21 18:15 db_wallet
  5. Make a wallet directory, then confirm the new directory.
    $ mkdir wallet
$ ls -lrt
    The output might look similar to the following:
    total 12
drwxr-xr-x 2 oracle oinstall 4096 Jan 20 10:16 adump
drwxr-xr-x 2 oracle oinstall 4096 Jan 21 18:15 db_wallet
drwxr-xr-x 2 oracle oinstall 4096 Jan 21 18:52 wallet
  6. Log into Node 2.
    ssh node2
  7. Repeat Step 2 - Step 5 to create a wallet in the /u02/app/oracle/admin/DB1 directory of Node 2.