Tuesday 17 January 2017

Deploy ODA_BASE on Oracle Database Appliance


This doc will describe the procedure to deploy the ODA_BASE on Oracle Database Appliance.

In my case i deployed on ODA X5-2 HA.




 1)  Once the network is setup, you have initial public network setup.  Please copy the template files to /OVS on dom0 1st node (Node 0).

2)    Download “p16186172_121290_Linux-x86-64_1of2.zip” and “p16186172_121290_Linux-x86-64_2of2.zip” from MOS Patch# 16186172. 

3)    scp or use winscp to copy the  both files to oak1-dom0 to /OVS

4)    unzip p16186172_121290_Linux-x86-64_1of2.zip

5)    unzip p16186172_121290_Linux-x86-64_2of2.zip

6)    This will create two files:  oda_base_12.1.2.9.gz01 and oda_base_12.1.2.9.gz02

7)    Concatenate the above two files using the cat command. 

cat oda_base_12.1.2.9.gz01 oda_base_12.1.2.9.gz02 > oda_base_12.1.2.9.tar.gz. This file name needs to be entered in the prompt in next step

8)    From Node0 (sc0, oak1-dom0), deploy oda_base by executing “/opt/oracle/oak/bin/oakcli deploy oda_base” as rootRespond to prompts “Enter the template location:” with the absolute path i.e “/OVS/oda_base_12.1.2.9.tar.gz”



-Choosing number of cores (for example 6)  means licensing number of  Cores (6 cores ) on each node. 
-Choose memory as needed for the ODA_BASE. This is the memory that is used for the Database so ensure an appropriate value is chosen.


# /opt/oracle/oak/bin/oakcli deploy oda_baseThu May 26 18:13:23 PDT 2016INFO: Validating LSI HBA PCI Cards on node 0

INFO: Validating LSI HBA PCI Cards on node 1

Enter the template location: /OVS/oda_base_12.1.2.9.tar.gz

Core Licensing Options:

        1. 2 CPU Cores

        2. 4 CPU Cores

        3. 6 CPU Cores

        4. 8 CPU Cores

        5. 10 CPU Cores

        6. 12 CPU Cores

        7. 14 CPU Cores
        8. 16 CPU Cores
        9. 18 CPU Cores
        10. 20 CPU Cores
        11. 22 CPU Cores
        12. 24 CPU Cores
        13. 26 CPU Cores
        14. 28 CPU Cores
        15. 30 CPU Cores
        16. 32 CPU Cores
        17. 34 CPU Cores
        18. 36 CPU Cores

        Selection[1 .. 9](default 36 CPU Cores) : <your selection>

INFO: Using the default cpu cores i.e. 36 cores

        ODA base domain memory in GB(min 16, max 244)[default 244]      : <default will be displayed>

INFO: Using default memory size i.e. 244 GB

Additional vlan networks to be assigned to oda_base ? (y/n) [n]: y   <=== Here to enter the vlan info

Select the network to assign (vl200): vl200

Additional vlan networks to be assigned to oda_base ? (y/n) [n]:

INFO: Deployment in non local mode

INFO: Verifying active cores on local node

INFO: Verified active cores on local node

INFO: Verifying active cores on remote node

INFO: Verified active cores on remote node

INFO: Running the command to copy the template /OVS/oda_base_12.1.2.9.tar.gz to remote node 1

oda_base_12.1.2.9.tar.gz 100% 7475MB 62.8MB/s   01:59
INFO: Spawned the process 17035 in the deployment node 0

INFO: Spawned the process 17037 in the node 1

INFO: Validating LSI HBA PCI Cards on node 0

INFO: Validating LSI HBA PCI Cards on node 0

INFO: Validating LSI HBA PCI Cards on node 1

INFO: Validating LSI HBA PCI Cards on node 1

INFO: Deployment in local mode

INFO: Deployment in local mode

templateBuild-2016-11-16-22-45/swap.img

templateBuild-2016-11-16-22-45/swap.img

templateBuild-2016-11-16-22-45/System.img

templateBuild-2016-11-16-22-45/System.img

templateBuild-2016-11-16-22-45/u01.img

templateBuild-2016-11-16-22-45/u01.img

INFO: Extracted the image files on node 0

/root

INFO: The VM Configuration data is written to /OVS/Repositories/odabaseRepo/VirtualMachines/oakDom1/vm.cfg file

INFO: Running /sbin/losetup /dev/loop0 /OVS/Repositories/odabaseRepo/VirtualMachines/oakDom1/System.img command to mount the image file

INFO: Mount is successfully completed on /dev/loop0

INFO: Validated dom0 and odabase version

INFO: Making change to the /OVS/Repositories/odabaseRepo/VirtualMachines/oakDom1/tmpmnt/boot/grub/grub.conf file

INFO: Assigning IP to the first node...INFO: Setting up IB Fix bridge
INFO
: 192.168.18.0/24
INFO: Enabling IB fix
INFO: Successfully enabled IB fix

INFO: Created oda base pool

INFO: Starting ODA Base...

Using config file "/OVS/Repositories/odabaseRepo/VirtualMachines/oakDom1/vm.cfg".

Started domain oakDom1 (id=1)

INFO: Storing the odabase configuration information

INFO: Extracted the image files on node 1

/root

INFO: The VM Configuration data is written to /OVS/Repositories/odabaseRepo/VirtualMachines/oakDom1/vm.cfg file

INFO: Running /sbin/losetup /dev/loop0 /OVS/Repositories/odabaseRepo/VirtualMachines/oakDom1/System.img command to mount the image file

INFO: Mount is successfully completed on /dev/loop0

INFO: Validated dom0 and odabase version

INFO: Making change to the /OVS/Repositories/odabaseRepo/VirtualMachines/oakDom1/tmpmnt/boot/grub/grub.conf file

INFO: Assigning IP to the second node...INFO: Setting up IB Fix bridge
INFO
: 192.168.18.0/24
INFO: Enabling IB fix
INFO: Successfully enabled IB fix

INFO: Created oda base pool

INFO: Starting ODA Base...

Using config file "/OVS/Repositories/odabaseRepo/VirtualMachines/oakDom1/vm.cfg".

Started domain oakDom1 (id=1)

INFO: Storing the odabase configuration information

#




Once the above process completes, the ODA_BASE domain is started, this can be checked by running oakcli command #oakcli show oda_base


ODA_BASE deployment is completed now. next step is to start the  deployment. i will cover this in next post.

Thanks!!! 

No comments:

Post a Comment