Erase and Rewind – Redeploying Oracle Database Appliance (2.3.0 image)

After using an Oracle Database Appliance for a bit of testing, it was time to get it ready for production. I decided to start with a fresh deploy and re-initializing shared storage.

Note that this is the 2.3.0 base image, and that the procedure may differ somewhat for other versions.

The included cleanupDeploy.pl script will pretty much just shut everything down, erase everything on the shared storage and reboot both nodes. It will leave the network configuration for the iLOM and most files stored on the system drives, including deployment configuration files you may have stored in /root/

It will remove network configuration and set the root password back to the default of welcome1.

[root@oma1 ~]# cd /opt/oracle/oak/onecmd
[root@oma1 onecmd]# ./cleanupDeploy.pl

Please enter the root password for performing cleanup:
Re-enter root password:

About to clear up OAK deployment,public network connectivity will be lost,root password will be set to default and both nodes will be rebooted

Do you want to continue(yes/no):

The script starts by asking twice for the root password before requesting a final confirmation. Make no mistake, after this point all services will be shut down and all data will be erased!

After a few minutes, the script completes with

Exiting…
[root@oma1 onecmd]#
Connection to oma1 closed by remote host.
Connection to oma1 closed.

and we are ready to start a new installation.

The first thing we need to do is connect to the iLOM either by serial or ethernet, or connect a keyboard and monitor so we can set up the initial network configuration. The cleanup script will not mess with the current configuration of the iLOM ethernet interface, so web and ssh console should be available.

-> start /SP/console
Are you sure you want to start /SP/console (y/n)? y

Serial console started. To stop, type ESC (

Oracle Linux Server release 5.8 Kernel 2.6.32-300.32.3.el5uek on an x86_64

oak1 login: root
Password:
Last login: Mon Oct 22 15:53:20 from 192.168.60.46

[root@oak1 ~]# cd /opt/oracle/oak/bin/
[root@oak1 bin]# ./oakcli configure firstnet

To work around a bug with the cleanupDeploy.pl we need to add a localhost entry to /etc/hosts on both nodes.

[root@oak1 ~]# echo 127.0.0.1 localhost.localdomain localhost >> /etc/hosts

I’m connected to the iLOM serial console through ssh, so I have to reconnect to the newly configured interface to enable X support for the deployment GUI.  I have a configuration file stored in the /root folder, so I call the deploy using that file as parameter file.

Connection to oma1-ilom closed.
roy@kayna:~$ ssh oma1 -l root -X
root@oma1′s password:
Last login: Tue Oct 23 13:01:39 2012 from 192.168.60.46
[root@oak1 ~]# cd /opt/oracle/oak/bin/
[root@oak1 bin]# ./oakcli deploy -conf /root/oak_deploy.params
Log messages in /tmp/oak_1350990145126.log
Loaded configuration file /root/oak_deploy.params successfully
Running Oracle Appliance Manager

When deployment starts, depending on your network configuration, the deploy will sometimes make a mess of the default route.  If you see this line when running route

default * 0.0.0.0 U 0 0 0 bond0

you will need to immediately delete the entry and set the correct default gateway (on both nodes), less the deploy may very well fail the ValidateEnv step, because it can’t access the DNS servers to check for the SCAN listener DNS entry.

[root@oak2 ~]# route delete default
[root@oak2 ~]# route add default gw 192.168.0.1

Hopefully the deploy will now complete successfully. If not, you can always jump back to the top, clean up the deploy and start fresh for another attempt.

This entry was posted in General, ODA, Oracle and tagged , , . Bookmark the permalink.

2 Responses to Erase and Rewind – Redeploying Oracle Database Appliance (2.3.0 image)

  1. Martins Nkanga says:

    Hi,
    Thanks for the write up, great! please kindly assist, see below:

    We gave our Demo ODA to one of our business partners for POC and it came back with issues: Kindly assist to reset back to default settings.

    These steps were taken by us:
    1. We used the command to clear and start afresh: ./cleanupDeploy.pl
    Error message:
    Trying to cleanup the system, this error bumps out:

    Host oda-retail listed in file /opt/oracle/oak/onecmd/tmp/all_nodes is
    not pingable at Gridsteps.pm line 5183 unable to setup ssh
    equivalence, cannot continue.

    2. I tried configuring Firstnet where I will input the ip addresses
    which is shown below but it just won’t accept it and if afterwords you
    type ifconfig, you won’t see the ip addresses.
    You can’t ping any of the IP addresses below on the ODA, but the DNS
    has been properly configured and resolvable.
    No inter connectivity between the ODA and the DNS server. SSH not
    running !

    3. Also, I want to confirm which ip should i configure on the
    firstnet, is it ODA – 10.0.0.5 or the node1 ip – 10.0.0.10 ? ( scroll
    down to see DNS & ODA configuration used)

    4. I am not using ILOM since I don’t have serial cable, but using the KVM- (keyboard, vga, mouse)

    I need your help to get the system back to its factory settings status before it taken away for POC by the BP. I realized that the Firstnet script is corrupt and not working but tried using #ipconfig eth up to set it but not sure!

    See below the config.

    DNS & ODA Configuration

    Domain name: westconafrica.com

    DNS: 10.0.0.1

    Server Name : OracleOdalab1

    Gateway: 10.0.0.1

    Net mask: 255.0.0.0

    NODE1 name. Ip.

    Public: Oracleodalab11 10.0.0.10

    Vip Oracleodalab11- VIP 10.0.0.12

    NODE2name. Ip.

    Public: Oracleodalab12 10.0.0.11

    Vip: Oracleodalab12-VIP 10.0.0.13

    Scan : Oracleodalab1-scan. 10.0.0.14
    10.0.0.15

    For ODA:

    IP: 10.0.0.5

    Net mask: 255.0.0.0

    Gateway: 10.0.0.1

    Database Name: Oracledb

    Thanks for your anticipated cooperation.

    • Roy says:

      It seems SC0 is unable to reach SC1, and thus cannot complete the cleanupDeploy.pl

      This is interesting, as the communication should go over the internal interconnect network interfaces.

      Can you verify that both system controllers are up and running?

      Although it could be interesting to figure out the cause of this, it may be quicker to re-install the ODA using the system images available from Oracle Support. This will also save you the hassle of upgrading your ODA to the latest software release (2.4.0 at the moment, I beleive).

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>