Hello Oracle Community reader,

This article describes my experience deploying Bare Metal and Virtualized pre-X6 ODA without GUI / X11 interface needed.

I have had used it for 40+ ODA deployments , both Bare Metal (BM) and Virtualized (ODAVP) so I feel comfortable saying that it works well.

The (re)deployment process for the X6-2 and X7-2 ODAs is different though as it is rather web browser based instead of X11, although a similar logic applies there as well.


Standard ODA deployment guide is describing the process with VNC viewer needed to complete cluster deployment after the "oakcli configure firstnet" step and placing the end user bundle on the ODA.

At the same time , I had to deploy ODAs (both Bare Metal and Virtualized) in the environments where the use of X11 and VNC even more so were constrained.

It could be happening due to the network design and firewalls being setup between the network segments, for example.

The X11 processes and applications may require TCP ports 6000-6063 being opened , as per documentation, while the more typical ports range is 6000-6003.

Additionally, VNC viewer could be prohibited in several environments as it is not all that secure.


The workaround for those possible constraints around GUI / X11 steps during ODA deployment is quite simple actually.

The entire process doesn't require any additional time , it could be more streamlined too as the ODA's onecommand.params file with the configuration information could be created ahead of deployment time.


At the high level the process looks as following

Step 1. Download ODA offline configurator, which is simply a Java based tool supplied by Oracle that has all the same steps as you would see during the standard ODA deployment

Oracle Database Appliance Manager Configurator

Step 2. Complete ODA offline configurator process and create the onecommand.params file with the configuration information required to deploy ODA.

             ODA configurator could be run on practically any MS Windows server or a laptop, it doesn't have to reside in the target network for the new ODA deployment either.

Step 3. Complete ODA (re)imaging and "oakcli configure firstnet"

Step 4. Transfer (or copy/paste) the file created by ODA offline configurator to the ODA that needs to be deployed.

             ! Make sure that filename is /opt/oracle/oak/onecmd/onecommand.params

Step 5. Run ODA command /opt/oracle/oak/onecmd/GridInst.pl -l for BM or /opt/oracle/oak/onecmd/GridInst.pl -l -o for Virtualized ODA deployment

             That command will validate that the file onecommand.params is in place and is readable as well as it will provide the list of steps required to deploy ODA.

Step 6. The key for deploying ODA without having to use X11 based GUI is to use the step #0 to validate the content of the onecommand.params file.

             GridInst.pl tool could be used to run either individual steps or the range of steps in one go.

            You could use a syntax like ./GridInst.pl -s 0 for BM or ./GridInst.pl -o -s 0 for ODAVP.

Step 7. Once the onecommand.params file has been validated via performing step #0 for GridInst.pl you could complete the deployment process either by completing individual steps or the range of steps.

               For example: ./GridInst.pl -r 1-24 to complete the deployment steps 1 through 24.

More information about using ./GridInst.pl could be obtained from MOS site, for example from the MOS DocID:

ODA (Oracle Database Appliance): Deployment & Cleanup Steps (Doc ID 1409835.1)


The overall ODA (re)deployment process will differ for different hardware releases and could be estimated at 1-2 hrs, provided that no significant troubleshooting is needed.

Thank you for reading, Slava Urbanovich