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.<\/p>\n
Note that this is the 2.3.0 base image, and that the procedure may differ somewhat for other versions.<\/p>\n
The included cleanupDeploy.pl<\/em> 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\u00a0\/root\/<\/em><\/p>\n It will remove network configuration and set the root password back to the default of\u00a0welcome1<\/em>.<\/p>\n [root@oma1 ~]# cd \/opt\/oracle\/oak\/onecmd Please enter the root password for performing cleanup: 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<\/p>\n Do you want to continue(yes\/no):<\/p><\/blockquote>\n 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\u00a0all data will be erased!<\/strong><\/p>\n After a few minutes, the script completes with<\/p>\n Exiting… and we are ready to start a new installation.<\/p>\n 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.<\/p>\n -> start \/SP\/console Serial console started. To stop, type ESC (<\/p>\n Oracle Linux Server release 5.8 Kernel 2.6.32-300.32.3.el5uek on an x86_64<\/p>\n oak1 login: root [root@oak1 ~]# cd \/opt\/oracle\/oak\/bin\/ To work around a bug with the\u00a0cleanupDeploy.pl<\/em> we need to add a localhost entry<\/em> to \/etc\/hosts\u00a0<\/em>on both nodes.<\/p>\n [root@oak1 ~]# echo 127.0.0.1 localhost.localdomain localhost >> \/etc\/hosts<\/p><\/blockquote>\n 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. \u00a0I have a configuration file stored in the \/root\u00a0<\/em>folder, so I call the deploy using that file as parameter file.<\/p>\n Connection to oma1-ilom closed. When deployment starts, depending on your network configuration, the deploy will sometimes make a mess of the default route. \u00a0If you see this line when running\u00a0route<\/em><\/p>\n default * 0.0.0.0 U 0 0 0 bond0<\/p><\/blockquote>\n 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<\/em> step, because it can’t access the DNS servers to check for the SCAN listener DNS entry.<\/p>\n [root@oak2 ~]# route delete default 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.<\/p>\n","protected":false},"excerpt":{"rendered":" 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, … Continue reading
\n[root@oma1 onecmd]# .\/cleanupDeploy.pl<\/p>\n
\nRe-enter root password:<\/p>\n
\n[root@oma1 onecmd]#
\nConnection to oma1 closed by remote host.
\nConnection to oma1 closed.<\/p><\/blockquote>\n
\nAre you sure you want to start \/SP\/console (y\/n)? y<\/p>\n
\nPassword:
\nLast login: Mon Oct 22 15:53:20 from 192.168.60.46<\/p>\n
\n[root@oak1 bin]# .\/oakcli configure firstnet<\/p><\/blockquote>\n
\nroy@kayna:~$ ssh oma1 -l root -X
\nroot@oma1’s password:
\nLast login: Tue Oct 23 13:01:39 2012 from 192.168.60.46
\n[root@oak1 ~]# cd \/opt\/oracle\/oak\/bin\/
\n[root@oak1 bin]# .\/oakcli deploy -conf \/root\/oak_deploy.params
\nLog messages in \/tmp\/oak_1350990145126.log
\nLoaded configuration file \/root\/oak_deploy.params successfully
\nRunning Oracle Appliance Manager<\/p><\/blockquote>\n
\n[root@oak2 ~]# route add default gw 192.168.0.1<\/p><\/blockquote>\n